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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-22757:
----------------------------------------

Referencing BUILD_ID is fine and isn't the cause of the issue as far as I understand. The issue is more in the scripts that have assumption that BUILD_ID is a timestamp. Although fixing BUILD_ID to look again as it used to is valid, maybe we should also consider it as an opportunity to think about reducing coupling from the scripts to such conventions. For example, rather than looking at timestamps in URL, scripts could just assume URLs alphabetical order is the same as temporary one to decide what to clean/publish.
Most of the linked scripts/pom do not assume much about the format or value of BUILD_ID and could work with any kind of value in it. So it's more likely "only" the publish and cleanup jobs that cause all the trouble and might be worth considering for a reduced coupling.

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