-
Notifications
You must be signed in to change notification settings - Fork 816
Add RPM and deb packaging for cortex binary #2838
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, feel free to ping me when you get the DCO sorted out and I'll approve it. The test failure looks like unrelated flake.
Thanks @jtlisi, I've sorted out the DCO now.
|
@pracucci I have fixed up the The packages end up in the dist directory after a |
I've just run
Could you take a look, please? |
I think this is the right approach tbh! Interesting
|
Signed-off-by: Jack Baldry <[email protected]>
…ners Signed-off-by: Jack Baldry <[email protected]>
@pracucci I'm unable to reproduce your issue with either @gouthamve I don't know much about how you are supposed to test RPM/deb packages so I'm not super pleased with the smoke tests as they are. I'm happy to implement any alternatives if you have ideas. In the mean time, I've upped the retry timeout for the test-packages script and added a variable that will leave the containers around for debugging. All it does is make a curl request to the cortex ready endpoint and expects a ready response, retrying every second for ~ten seconds. Unfortunately, I'm also struggling to reproduce this locally, it just works on my machine haha. Thanks to you both for being so patient with this PR! |
Signed-off-by: Marco Pracucci <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jdbaldry. I tried with the latest version and both make packages
and make test-packages
worked. I've pushed a commit to update RELEASE process, mentioning we should build packages and attach them to the release on GitHub (which looks an easy win). Approved!
What this PR does:
Adds tooling that can be used to build RPM and deb packages for cortex configured using the single-process-config.yaml. Continuing the practice in the Makefile, building the packages only requires access to a Docker runtime.
It also includes makeshift integration tests that confirm that the packages can be installed on CentOS or Debian and that the cortex service can be started. Dockerfiles for these images are also included.
This PR achieves the goal of providing a mechanism for building packages for cortex but needs CI integration. I want to see if this is the direction we would like to head in.
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]