[jbosstools-issues] [JBoss JIRA] (JBDS-3163) change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server

[Pete Muir (JIRA)]

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

Pete Muir commented on JBDS-3163:
---------------------------------

[~nickboldt] if you include any EAP version other than an alpha it needs to be behind the t&c. To be clear, even then you should only be putting x.y.0 EAP versions in JBDS, micro releases are not released under the developer subscription.

> change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-3163
>                 URL: https://issues.jboss.org/browse/JBDS-3163
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 8.0.0.CR1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 8.0.1.GA, 9.0.0.Alpha1
>
>
> To simplify release/publishing process, we ought to start publishing nightlies and builds staged for QE onto devstudio.redhat.com (filemgmt) instead of the internal www.qa box. This will also allow us to use nightly URLs in ide-config.properties. 
> See https://github.com/jbosstools/jbosstools-download.jboss.org/pull/409/files for a bad solution to this problem. 
> Better solution is to move that content onto the new filemgmt instance and update promote.sh to push to the new location.



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