[jbosstools-issues] [JBoss JIRA] (JBIDE-22757) jenkins jobs no longer using BUILD_ID = a timestamp (Jenkins bug)

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267109#comment-13267109 ] 

Nick Boldt commented on JBIDE-22757:
------------------------------------

This affects parent pom and jbosstools-cleanup.sh too:

{code}
<deployTargetFolder>${jbosstools-build-type}/${JOB_NAME}/${BUILD_ID}-B${BUILD_NUMBER}/all/repo/</deployTargetFolder>
{code}

https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.3.x/util/cleanup/jbosstools-cleanup.sh#L151

So... yeah. This is big.

> 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
>             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)