[
https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin....
]
Mickael Istria edited comment on JBDS-3163 at 11/19/14 6:49 AM:
----------------------------------------------------------------
Suggested URLs
*
http://devstudio.redhat.com/
** builds/<jobName> _populating this folder would be handled by the current
publish.sh and friends,_
** staging/<stagingVersion> (such as 9.0.0.Alpha1) _populating this folder would
be described in the JBDS_Staging_for_QE document of jbdevstudio-devdoc, content is derived
from the content of builds/ folder_
** developement/ _populating this folder would be described in the JBDS_Release document
of jbdevstudio-devdoc, and content is derived from the staging folder_
*** <developmentVersion>
*** composite*.xml (pointing to latest)
** releases/ _populating this folder would be described in the JBDS_Release document of
jbdevstudio-devdoc and content is derived from that staging folder_
*** <releasesVersion>
*** composite*.xml (pointing to latest)
was (Author: mickael_istria):
Suggested URLs
*
http://devstudio.redhat.com/
** builds/<jobName>
** staging/<stagingVersion> (such as 9.0.0.Alpha1)
** developement/
*** <developmentVersion>
*** composite*.xml (pointing to latest)
** releases/
*** <releasesVersion>
*** composite*.xml (pointing to latest)
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)