reorg/refactor directories for consistency across JBT/JBDS ---------------------------------------------------------- Key: JBDS-3208 URL: https://issues.jboss.org/browse/JBDS-3208 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: build Affects Versions: 9.0.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 9.0.0.Alpha2 Be it resolved - we should reorg directories for consistency across JBT/JBDS: Latest suggestion: * /\{mars,9.0}/ ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/ *** /*updates*/ **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/ ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/ *** /*builds*/ **** /<job-name>/ ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/ --- Older idea: {code} <download.jboss.org,devstudio.redhat.com> <earlyaccess,updates,discovery>/<mars,9.0> /snapshots [replace nightly] /staging [rename content for QE, moves to development when approved] /development /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler drop /integration (not used) builds/<jobname>/<buildid> builds/<jobname>/composite*.xml for last N builds targetplatforms/<type>/<version> {code} Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...