[
https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22757:
------------------------------------
Oops, just checked and the 1.0.x job was set to push into neon/snapshots/ not
mars/snapshots. So, I fixed that.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--> line 148
re: PR 124, I've updated it per comments in the PR. Since Luna convention is no longer
being used, and since we have the option to override in Jenkins, I've removed the line
and updated it to use neon/ instead of mars/.
If you're still building in your 1.0.x branch/job, we'll need to apply a similar
fix there too, but using mars/ instead of neon/ as the folder prefix.
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)