-
Enhancement
-
Resolution: Done
-
Critical
-
4.2.0.CR2
Currently, the site we use for staging are organized much differently from what will be shipped to end-users. This results in making tests against staging behaving differently to how release will believe, so making tests confusing, error-prone and useless.
We need to rework the staging process so that its output is similar to what will be the output of a release:
- updates/staging/luna , compositing
- target-platform
- JBT core
- Central TP
- earlyaccess site (location still to be decided?), currently 'http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/4.40.0.CR1-SNAPSHOT/REPO/
Those sites are the one that need to be used respectively for jboss.discovery.site.ul and jboss.discovery.earlyaccess.site.url in ide-config.properties
Then the process of releasing to development isn't much more than a cp -r and some sed /staging/development/
- is related to
-
JBDS-3163 change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server
- Closed
-
JBIDE-18577 Examples - Hybrid Mobile Tools requirement is not fulfilled even when installed
- Closed
-
JBIDE-18590 Split /discovery/ staging site into 3 sites: Core+Central, EA, and Discovery
- Closed
- relates to
-
JBIDE-18590 Split /discovery/ staging site into 3 sites: Core+Central, EA, and Discovery
- Closed