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

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

Yes, the act of pre-pushing staging bits to ds.jh.com would save a step at QE-staging time.

[0] https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_guide/8.0/JBDS8.0.0_Staging_For_QE.adoc#stage-files-to-devstudioredhatcom

No, installers don't need to be crosslinked to where update sites are; the installer's build folder [1] contains update site ZIPs (not the unpacked ones) so we could simply continue to link to that folder [2] when it's for CSP staging.

[1] http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/installer/
[2] http://www.qa.jboss.com/binaries/RHDS/builds/development/8.0.0.GA-build-core/

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