]
Max Rydahl Andersen commented on JBDS-3208:
-------------------------------------------
"I don't understand why we need that." -> to avoid install/updates to
fail when nightly/snapshots are being updated.
"cleaning up stuff isn't high priority" -> I wish that was true. But we
need to be aware how much we use. And whatever schema we setup the clean up needs to be
easy to automate. Try to avoid being magical/complex since we don't have full access
to the filesystem/shell to do too much logic.
I have same concerns as you about the updates/mars pointing to updates/mars/stable. Why
do we need updates/mars or updates/9.0 to point at any p2 content ?
And yes, would be best /snapshots actually points to the current related central, tp, etc.
so it mimicks what staging, development and stable will contain.
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.Alpha1
Be it resolved - we should reorg directories for consistency across JBT/JBDS:
{code}
download.jboss.org
<earlyaccess,updates,discovery>/mars
/snapshots [replace nightly]
/staging [rename content for QE, moves to development when approved]
/development
/stable (updates/mars/stable is a pointer back into updates/mars)
drop /integration (not used)
builds/<jobname>/<buildid>
builds/<jobname>/composite*.xml for last 2 builds
targetplatforms/<type>/<version>
{code}
and
{code}
devstudio.redhat.com
<earlyaccess,updates,discovery>/9.0
/snapshots
/staging
/development
/stable (updates/9.0/stable is a pointer back into updates/9.0)
builds/<jobname>/<buildid>
builds/<jobname>/composite*.xml for last 2 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...