[jbosstools-issues] [JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)
Mickael Istria (JIRA)
issues at jboss.org
Tue Jul 19 12:06:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267623#comment-13267623 ]
Mickael Istria commented on JBIDE-22757:
----------------------------------------
Is this really a blocker? What does it prevent from working?
The proposed change is good IMO. I also like the fact that we have a more explicit name (BUILD_TIMESTAMP rather than BUILD_ID). Why not using directly the maven.build.timestamp property directly though?
> 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)
More information about the jbosstools-issues
mailing list