[jbosstools-issues] [JBoss JIRA] (JBIDE-22968) if a build fails to publish, future builds may think there's nothing new and also not publish

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-22968 at 8/9/16 11:33 AM:
-------------------------------------------------------------

What happened:

* !openshift-failed-future-builds-did-not-publish.png!

What should have happened:

* build 1482 should have been published into http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-openshift_master/



was (Author: nickboldt):
What happened:

* !openshift-failed-future-builds-did-not-publish.png!

What should have happened:

* build 1478 should have been published into http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-openshift_master/


> if a build fails to publish, future builds may think there's nothing new and also not publish
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22968
>                 URL: https://issues.jboss.org/browse/JBIDE-22968
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>            Reporter: Nick Boldt
>         Attachments: openshift-failed-future-builds-did-not-publish.png
>
>
> When publishing snapshots to download.jboss.org via Jenkins jobs, we need to add a check for "did the last build fail? if so, set skipRevisionCheckWhenPublishing = true"
> That way we don't get situations where the Openshift build fails (because failed enforcer check) and then the next 4-5 builds are NOT published (because as far as the current tests are concerned, the latest SHA in Jenkins == latest SHA in github... but NOT the latest SHA on download.jboss.org/.../snapshots/JOB_NAME/latest/.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)