[
https://issues.jboss.org/browse/JBDS-3163?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-3163:
----------------------------------
Did you mean updates/9.0/staging/, updates/9.0/development/, and updates/9.0/stable/ ?
[~maxandersen] doesn't like the word "releases".
Otherwise, the above makes sense, with ONE problem:
The builds/ folder today includes the installers - both the standalone and the *EAP
bundles*.
Maybe we need to make sure those are .htaccess-restricted?
[~burrsutter] [~maxandersen] [~pmuir] Do you care if we put pre-GA JDBS 9 installers,
bundled with EAP, on the public-facing
devstudio.redhat.com, or do they need to stay on a
non-public server until ready for GA and exposed via CDN/GoldenGate/CSP?
Making them public makes it easier for QE & CAT to test pre-GA stuff; also makes it
easier for people w/o VPN to test. But it risks getting EAP into the hands of people who
haven't signed up for the
jboss.org Ts&Cs.
Is that a problem?
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)