[jbosstools-issues] [JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-14610:
------------------------------------

Are we done here? We:

* deploy to nexus,
* publish a /mars/snapshots/builds/JOB_NAME/BUILD_NUMBER/ for each build, with automated cleanup,
* publish a composite site in /mars/snapshots/builds/JOB_NAME/ pointing into all the BUILD_NUMBER/all/repo/ folders,
* publish a /mars/snapshots/builds/JOB_NAME/latest/ symlink to the latest job
* produce buildinfo.json inside the /all/repo/ folder

But we still have composite sites (for now), as this is so far the best way to provide a "gatekeeper" build to decide when to rebuild/republish the aggregate sites:

* http://download.jboss.org/jbosstools/mars/snapshots/builds/_composite_/core/4.3.mars/compositeArtifacts.xml
* http://download.jboss.org/jbosstools/mars/snapshots/builds/_composite_/core/master/compositeArtifacts.xml

Alternatively, we could trigger aggregate builds based on upstream SCM changes. See JBIDE-19598.

For more on ongoing cleanup of convention and reorging/refactoring, see JBDS-3208.

> Design http://download.jboss.org/jbosstools structure
> -----------------------------------------------------
>
>                 Key: JBIDE-14610
>                 URL: https://issues.jboss.org/browse/JBIDE-14610
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build, updatesite
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Denis Golovin
>            Priority: Blocker
>             Fix For: 4.3.x
>
>
> We have several types of objects which names should be presented in site stucture:
> # Project: jbosstools
> # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final
> # Subproject: core, soatools
> # Module: base, javaee, central, freemarker and etc.
> # Distribution Type: updates|builds
> # Bits Type: stable|development|nightly
> # Targeted Eclipse: indigo|juno|kepler
> # You name it ...
> Now we mostly use following patterns to publish nightly bits, but not always and not for every project:
> # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\}
> # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure
> # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)