[JBoss JIRA] (JBIDE-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?
- First Post
- Replies
- Stats
-
Go to
- ----- 2026 -----
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2006 -----
- December
- November
- October
- September
[
https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13672:
------------------------------------
Currently it's just logged in the console log. I tried to use Build Description plugin
to trap for the console log text saying that the GIT_REVISION was unchanged and therefore
publishing was cancelled, but that didn't work as I'm already using Build
Description to set the name of the TP used in the build.
HOWEVER... I could:
* produce a property file to record if the Git revision check resulted in a new publish or
not, then
* check that file's contents and
* use ${PROPFILE,file="FILENAME",property="PROPERTYNAME"} in the Build
Name field to define the publishing status
could publish.sh check previous build's GIT_REVISION.txt or
ALL_REVISIONS.txt before overriding existing update site w/ new content?
------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13672
URL: https://issues.jboss.org/browse/JBIDE-13672
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.1.0.Alpha2
Before we rsync new content from the job's workspace to www.qa or download.jboss.org,
we should compare the previous build's git revision(s) to decide if the new build
needs to be published.
May want to add an override flag in the job to FORCE a publish (ie., a manually built
aggregate).
Sample files to check:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo...
http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4771
days inactive
4771
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
tags (0)
participants (1)
-
Nick Boldt (JIRA)