| Summary: | Publish target platform definitions that downsteam projects can reuse | ||
|---|---|---|---|
| Product: | [Modeling] Sirius | Reporter: | Pierre-Charles David <pierre-charles.david> |
| Component: | Releng | Assignee: | Pierre-Charles David <pierre-charles.david> |
| Status: | CLOSED FIXED | QA Contact: | Maxime Porhel <maxime.porhel> |
| Severity: | normal | ||
| Priority: | P3 | CC: | maxime.porhel |
| Version: | 1.0.0M6 | Keywords: | triaged |
| Target Milestone: | 1.0.0M7 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Pierre-Charles David
For each update-site we publish, we could also publish the sirius_xxx.targetplatform file we used for the build as sirius-deps_xxx.targetplatform, and a separate sirius.targetplatform which references the content of the build. This shows that the current naming of our targets is not ideal: sirius_juno.targetplatform for example is not "Juno with Sirius" as the name would imply, but the dependencies needed to build Sirius on top of Juno. Also, publishing the second file, sirius.targetplatform, requires knowing the URL through which it will be exposed. Should it reference an exact build ID (e.g. nightly/1.0.0-N201403250900), a branch (e.g. nightly/1.0.x), or just point to the latest (e.g. nightly/lastest)? See commit 1f03ee4238990ae51fbe86ba2d53db0c6c6d539b for a first iteration. The nightly builds' promotion script now publishes all the target definitions and the targets themselves at http://download.eclipse.org/sirius/updates/nightly/targets/ Downstream projects can do something like this: include "http://download.eclipse.org/sirius/updates/nightly/targets/sirius_kepler.targetplatform" in their *.targetplatform files to include the same dependencies as the ones used by Sirius. They can also pick specific dependencies from http://download.eclipse.org/sirius/updates/nightly/targets/modules if they do now want/need everything. Moving to M7 as this is actually mostly finished. Fixed here, and validated with downstream (internal) projects which now use targets generated using these published definitions. Available in Sirius 1.0.0M7 (see https://wiki.eclipse.org/Sirius/1.0.0M7 & http://git.eclipse.org/c/sirius/org.eclipse.sirius.git/tag/?id=v1.0.0M7). |