[
https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-22757:
---------------------------------------
[~nickboldt], it seems that you changed the RedDeer jobs already, so nothing to do here,
thanks.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
{code}
BUILD_TIMESTAMP=`date -u +%Y-%m-%d_%H-%M-%S`
publishingPath=neon/snapshots/builds/${JOB_NAME}/${BUILD_TIMESTAMP}-B${BUILD_NUMBER}/all/repo/
publishingPathLatest=${publishingPath/${BUILD_TIMESTAMP}-B${BUILD_NUMBER}/latest}
{code}
Regarding
https://github.com/jboss-reddeer/reddeer/pull/1424 - I posted a question for you
there.
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)