-
Notifications
You must be signed in to change notification settings - Fork 2
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
Build system #21
Build system #21
Conversation
ebeb8d4
to
7cfb0fd
Compare
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.
A few fixes are necessary, as per the discussion above, so I'm turning my review status into “Request changes”.
8f23c5e
to
a8246c9
Compare
6f09590
to
68047cd
Compare
I think I have addressed everything you discussed before. Let me know what you think |
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.
Looks good, awesome work! 🚀
The PR is too big to really dig into the details. I pulled the changes and validated that I can still build and pass the tests with both glibc/musl (Note that I get a few warnings for the tests). I'd normally complain that this needs to be split up into logical commits, but I understand the plan is to wipe the Git history so far anyway.
I've got a few nits below, but we can address them as follow-ups. I think we should go ahead and merge this PR, we can do some more polishing afterwards.
.github/workflows/bump.yml
Outdated
# The primary point of this workflow is to ensure that the developer experience is good. | ||
# We take a very vanilla ubuntu image, install all necessary dependencies via "normal" means, | ||
# and then run the build and test steps as described in the README.md file. | ||
|
||
# The artifacts produced by these builds are not intended to be used for anything other than | ||
# ensuring that the developer experience is good. | ||
|
||
# Production artifacts are produced in a sterile environment (in another CI workflow). |
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.
This comment seems copy-pasted from dev.yml but I don't think it applies to this workflow.
@@ -0,0 +1,90 @@ | |||
# Hedgehog Dataplane |
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.
Next step: We need a cool logo :)
This comment hasn't been addressed 😛
Note: I have a follow-up PR based on yours, and some of the |
I think this is because I used a _branch := `git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "sterile"` |
I've got a fix for this branch name thing: diff --git a/justfile b/justfile
index d87adb36099a..2c9be0c97c4c 100644
--- a/justfile
+++ b/justfile
@@ -66,7 +66,7 @@ _commit := `git rev-parse HEAD 2>/dev/null || echo "sterile"`
# The git branch we are currnetly on
# We allow this command to fail in the sterile environment because git is not available there
-_branch := `git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "sterile"`
+_branch := `(git rev-parse --abbrev-ref HEAD 2>/dev/null || echo "sterile") | tr -c '[:alnum:]\n' '-'`
# The git tree state (clean or dirty)
# We allow this command to fail in the sterile environment because git is not available there I'll do a follow-up PR after your branch is merged. |
nice |
79553c4
to
8870716
Compare
basically the whole project up to this point. looking to squash and start clean after this lands