[jbosstools-issues] [JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025322#comment-13025322 ] 

Nick Boldt commented on JBDS-3208:
----------------------------------

OK, then we just need [~maxandersen] and [~mickael_istria] and [~fbricon] to +1 this and we can proceed.

I'm thinking that the eclipse.org mirrors we have currently in /updates/requirements/ [1] could move to /\{quality\}/updates/requirements/ since we only need them to build target platforms and when target platforms are Final and moved to /static/, we could purge them based on their quality (eg., snapshots & development can go away after GA; but we should keep the R builds that go into our target platforms. 

[1] http://download.jboss.org/jbosstools/updates/requirements/

*BIG DISCLAIMER* re: implementing an aggressive cleanup policy for these mirrored upstream requirements: if a mirrored upstream snapshot or dev milestone is used in a GA or a version of the IS we support through Central, we need to keep it much longer.

Therefore:

* /\{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>/
*****     /<build-version = B123, B124, B125...>/

I'd also be happy renaming "requirements" to "upstream" or "mirrors" if people prefer that term.


> 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.luna/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_8.0.luna/job/jbosstools-composite-install_4.2.luna/



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)