[jbosstools-issues] [JBoss JIRA] (JBIDE-18833) luna nightly are not being updated preventing QE to do easy testing of committed code

Max Rydahl Andersen (JIRA) issues at jboss.org
Thu Nov 27 14:08:39 EST 2014


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

Max Rydahl Andersen commented on JBIDE-18833:
---------------------------------------------

No. I do not want a url with updates in it. *we* want a URL that is consistent with the other urls we have (for staging, development, and stable) that does not change just because the git branch changes from master to 4.2.x so everyone midstream need to know to change to some different URL. 

  I don't see any conflicts with this having updates in the URL - since it updates just fine and is an update site. 

And yes I think the page to find various builds for subcomponents etc. Are great and it's been suggested in a few Jiras before but I think the one you opened will work fine and we can just mark the others as duplicate when/if we see it. But this does not -*remove* the ancient old requirement on not changing uodatesite urls for our vanity/stream urls. 

Thanks for restoring  the URL!

> luna nightly are not being updated preventing QE to do easy testing of committed code
> -------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18833
>                 URL: https://issues.jboss.org/browse/JBIDE-18833
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 4.2.1.Final
>
>
> http://download.jboss.org/jbosstools/updates/nightly/luna/ composite*.xml was updated 26-nov but latest build there is from 28-oct-2014 (29 days ago)
> I could not  spot updates in https://github.com/jbdevstudio/jbdevstudio-ci related to this.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


More information about the jbosstools-issues mailing list