Add deployments and automated tagging
- Jul 31, 2019
-
-
Sjoerd Simons authored
Apertis doesn't (yet?) update the gbp.conf file for packages in git; which means depending on what the Debian package has the CI tooling might well get confused. Force a dummy gbp configuration file so that we end up with the defaults for all packages. Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
2249122a -
Sjoerd Simons authored
Let the environment name depend on the branch that was deployed such that we get seperate environments per release Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
85dccc5e -
Sjoerd Simons authored
The --mirror argument was dropped from apertis-pkg-merge-updates as it was unused. Drop it from the gitlab yml as well Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
90137506 -
Sjoerd Simons authored
Before actually tagging a package release check if the last changelog entry still contains the "PLEASE SUMMARIZE" placeholder. If that's the case error out rather then tagging. Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
12d146f4 -
Sjoerd Simons authored
This revamps the non-scheduled jobs (aka those running on branches) quite a bit. The new pipeline for those starts with a similar build stage, which now only builds. This allows it to run in far more cases, e.g. to run on topic branches to give them a minimal round of testing. After build for the apertis branches there is a postbuild stage which runs one job that uploads the snapshot build straight away while a second job blocks on a manual trigger to do a release of the package. When that job is manually triggered the package gets tagged and rebuild followed by a further job that will upload that build and does a submit-request to OBS. Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
87bdfbfd
-