-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add GitHub actions #61
Conversation
55050a3
to
d62461b
Compare
Dockerfile
Outdated
|
||
# Run unit tests | ||
CMD ["cmake", "--build", "/tmp/arbitration_graphs/build", "--target", "test"] |
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.
👌
6127504
to
d8e9b4f
Compare
Changed the base to |
Alright @orzechow , this one is ready for review. It should be very analogous to the util_caching pipelines now. Feel free to push your release-test-pipeline onto this branch if we want to do that in one go. |
Thanks! One quick remark: the dockerfile is missing the release_builder stage etc. Yeah, I'll add the release test pipeline after finishing the cpack PR |
You're right. I think it's easier if one person just does it. I have moved the PR back to draft to wait until you finished the cpack PR. I will then rebase this PR, add the Docker stage and release test pipeline and ping you once the PR is actually done. |
fa3fbc6
to
c0eb7ba
Compare
After rebasing, the gui now also needs to be copied into the testing container.
We now provide pre-built images so this is no longer necessary and only clutters up the compose file.
0b980e6
to
afac93c
Compare
Rebased on main |
Fix gui release test
afac93c
to
5ffeaf7
Compare
The ghcr version of the image might not represent the current state of the library and possibly does not even exist for the version of a dev branch.
476c101
to
3d38df2
Compare
Ok @orzechow this one should truly be ready now. See the edited PR description for all the things that are now going on the workflows. I tested the workflow on a test branch where I didn't need a PR to trigger the workflow, see 82b31a0. Other than that, the branch is identical to this one and the last run was succesful. A couple of noteworthy changes I made since we last talked about this:
Before merging, I'll delete the tag, release and docker images created by the test branch. I will then merge this as a #minor release. |
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.
Great! Thanks for the good work 🫶
Release deb & tar.gz look good 👌
Couldn't test the ghcr.io docker images (bad connectivity), but I trust that you did.
Let's go 🚀
See #59 for details.
This adds automated workflows to
version
file according to the version string in the commit messages (#major
,#minor
,#patch
,#none
).#minor
by default.