I have done the first part of Jenkins build, sign and deploy.
- CI job is a multi-branch pipeline, as the develop branch is merged to other branches they will automatically start building because of the presence of nightly.Jenkinsfile.
- Builds are signed and published to a nightly build location on download.eclipse.org, with a subdirectory per branch built: https://download.eclipse.org/embed-cdt/nightly/ (e.g. develop branch's p2 repo is https://download.eclipse.org/embed-cdt/nightly/develop/ with zipped version of the repo in ilg.gnumcueclipse.repository.zip)
- I updated the shield and link in the README.md with the above URLs.
- The EF will soon have a web app to manage the download server, see Bug 546528. In the meantime we can do simple cp commands wrapped in a Jenkins job.
- I can look into remote triggering of the job later. I have minimal experience doing this.
- If/when we want Jenkins to do PR builds I can enable that too
The above maps to your original request as follows:
A simple copy using the soon to arrive web interface from nightly to pre-release name
> In a second step, when hopefully I'll have more experience with Jenkins, we'll consider how to build the EPP packages, and what are the requirements to later align with the simrel rules.
As for EPP - I hope that we can just add it as a new project on the existing EPP at Eclipse so that it can be managed as part of the Eclipse Release Train and be available on
https://www.eclipse.org/downloads/ and in Eclipse Installer. In the meantime it may be easiest to just continue managing as is currently in place, rather than do two migrations.
Let me know if you see something awry.
Jonah