[
https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22757:
------------------------------------
Yes, it's a blocker. Timestamped folders are composited automatically as /latest/
folders, eg., [1], which are then used to create the JBT aggregate [2]. The JBT aggregate
compares the version of source in the built binaries to the version in github, and if
there's a disconnect, the build fails [3]. This check is designed to prevent
accidentally including the wrong sources in the source zip.
[1]
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-fre...
http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-fre...
[2]
jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Ma...
[3]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
{code}
[ERROR] Failed to execute goal
org.jboss.tools.tycho-plugins:repository-utils:0.25.1-SNAPSHOT:fetch-sources-from-manifests
(fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream
buildinfo.json files!
[ERROR]
/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-freemarker.json
[ERROR] contains cf8c8ba5b9c79bf5d72920d913e372befe1c6bbf, but upstream
jbosstools-freemarker project's MANIFEST.MF has Eclipse-SourceReferences
[ERROR] commitId 1048bbb0ef4ef287a6250d5e75cc86998158a102.
[ERROR] If you have locally built projects which are aggregated here,
[ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch.
[ERROR] Or, use -DskipCheckSHAs=true to bypass this check.
{code}
The property is wrapped because of this [4], but the bug may no longer be an issue with
Maven 3.x.
[4]
https://stackoverflow.com/questions/13228472/how-to-acces-maven-build-tim...
jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
-----------------------------------------------------------------
Key: JBIDE-22757
URL:
https://issues.jboss.org/browse/JBIDE-22757
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.4.1.AM2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.4.1.AM2
Attachments: buildID-broken.png
Due to an upstream bug in Jenkins [1], [2], BUILD_ID now = BUILD_NUMBER.
[1]
https://issues.jenkins-ci.org/browse/JENKINS-26520
[2]
https://issues.jenkins-ci.org/browse/JENKINS-26626
So instead of timestamped build folders, we're seeing things like this:
!buildID-broken.png|thumbnail!
Workaround until fixed in Jenkins:
{code}BUILD_ID=`date -u +%Y-%m-%d_%H-%M-%S`{code}
Or, try using BUILD_TIMESTAMP instead?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)