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

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-22757:
---------------------------------------

Thanks, [~nickboldt], PR 124 is merged and we don't require a similar fix for RedDeer 1.0.x since we don't plan on using it much longer (in fact we just released 1.0.2 and will put the branch on hold for now) and it's set in jenkins, so it's fine.
So I consider all is done for RedDeer wrt this JIRA.

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