[
https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-13672 at 3/1/13 12:55 PM:
-------------------------------------------------------------
Now, if the previous build's git revision (SHA) is the same as the current one, it
won't bother to push the new bits to the staging/\{jobname\}/all/repo site, which
means the composite site will not change, and therefore the downstream aggregation will
not happen. This minimizes builds for the sake of building, but still allows us to
rebuild/retest as a result of upstream changes (like a new target platform or a possible
API change).
So, should Base change, you can manually kick off Server to ensure everything still
builds. But if the CODE in Server is unchanged, Server will not be *published*, only built
& tested. You can scan the build logs for this message:
{code}
=======================================================================================================
GIT revision(s) UNCHANGED. Publish cancelled (nothing to do). Skip this check with
'EXPORT skipRevisionCheckWhenPublishing=true;
=======================================================================================================
{code}
was (Author: nickboldt):
Now, if the previous build's git revision (SHA) is the same as the current one, it
won't bother to push the new bits to the staging/{jobname}/all/repo site, which means
the composite site will not change, and therefore the downstream aggregation will not
happen. This minimizes builds for the sake of building, but still allows us to
rebuild/retest as a result of upstream changes (like a new target platform or a possible
API change).
So, should Base change, you can manually kick off Server to ensure everything still
builds. But if the CODE in Server is unchanged, Server will not be *published*, only built
& tested. You can scan the build logs for this message:
{code}
=======================================================================================================
GIT revision(s) UNCHANGED. Publish cancelled (nothing to do). Skip this check with
'EXPORT skipRevisionCheckWhenPublishing=true;
=======================================================================================================
{code}
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