[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=13022157#comment-13022157 ] 

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

The devstudio installers with EAP was not intended to be part of this. Only the p2 plugins - at least at first, and that is also only what CAT have been testing until now. Thus I agree with Pete - the installers need to stay behind the 0$ wall and security through obscurity is not an option. 

Pete - devstudio have been publishing its milestone builds for years so its not new. 
What we are trying to here is that since we are public anyway we can save several hours if not days of the time spent just moving bits around. Plus it gets much simpler to maintain and avoid having to do expensive workarounds between staging and prod releasing. 




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