Create pipeline for creating deb packages for prometheus node exporter
This issue tracks the idea of creating the complete pipeline for:
- Maintaining (needs docs)
-
Building (works, but needs something better than
dpkg-deb, although its fine for low complexity packages) - Testing (using InSpec as part of the CI)
-
Publishing to
aptly.gitlab.com - Installing with chef across our infrastructure
- Cleaning obsolete versions
and probably something else for prometheus node exporter. The repo itself is here: https://gitlab.com/gitlab-pkg/gitlab-node-exporter
Related: #2426
Activity
Some progress update:
- aptly rocks
- I created the s3 bucket with separate user with write access to it
- I was able to sign and publish some debian packages
Meaning that we can have this pipeline:
- CI builds debian pacakge (done)
- CI fires up DO instance, installs debian package there and runs automated tests (done)
- CI uses aptly to automatically sign and upload package to repo at s3 (needs more tests)
And that's it -- all the nodes that have that repo specified can install the package.
/cc @pcarranza the future is near :)
/cc @victorcete
assigned to @ilyaf
changed milestone to %WoW
This was done some time ago in a minimal way that allows us to push packages from pipelines (https://gitlab.com/gitlab-pkg), and the multi-component self-cleaning documented awesome tied-to-chef solution will be determined during https://gitlab.com/gitlab-com/infrastructure/issues/2048, I guess. Closing this issue before it becomes [META]
😄
