Community
Participate
Working Groups
Due to signing issues, we need to remove the compare-to baseline-repository in both builds, the Runtime and the Tools builds. This is required in order to ensure that signed bundles are not replaced by unsigned counterparts from the baseline repository during the build.
With the new setup on our build servers it is now possible to use a baseline repository. The solution is relatively simple: Run two consecutive builds, the first one unsigned but with tests enabled, the second one without tests but signed *and* with a baseline-repository set to the last known good milestone release build. The content from the second build is copied to the nightly build p2 repository. With this approach we fix two issues at once: The content that we publish (even the builds on the nightly p2 repositories) is always signed, and we can start using the baseline-repository feature.
