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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBDS-3163:
-------------------------------------------

" Would skip only ONE step in the release process, but it would certainly save some time." ..I read that as you are saying that even if we dont co-locate the installers and updatesites this will still save time in the process, correct ?

And I assume when installers are built it knows where its updatesites will be so could cross link from it if need be. 

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