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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBDS-3163:
----------------------------------

Yes, the intent here is easier releng & testing. 

But having to push installers to www.qa (internal) and the update sites to devstudio.redhat.com (public) may make the releng process more confusing since installers are on one server and update sites another.

OR, we push everthing BUT the EAP bundles to ds.rh.com, but also keep a folder w/ all the installers (including EAP) on an internal server so that when it's time to stage for CSP, we don't have to tell Christ to get the bits from two different servers. That will only confuse QE when they go looking to test the installers on ds.rh.com and can't find the EAP bundles, only the standalone ones. :(



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