-
Notifications
You must be signed in to change notification settings - Fork 164
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
RFC: Github Actions? #105
Comments
Total +1 from me. Let's wait for @fntlnz's opinion (but I suppose he will be +1 too) :) |
BTW I can work on it since I'd like to play a bit with GH actions finally :) |
Awesome! I added it to iovisor/bcc and iovisor/bpftrace, so you can check out those workflow files as a starting point. Some things are a little unituitive (eg, checkout action isn't default like on travis), but it's just as flexible as travis I think, and IMO a little nicer. There is an SSH action you can use to ssh in and debug, which I gotta admin I really love. We can also automate release actions on tags I think too, so could probable automate the process in docs/release.md to trigger when there is a tagged release? |
to add the QUAY_TOKEN we need someone with more privs in the iovisor org |
Yup, I know Thanks for all this idea and all the suggestions, btw :) |
I have a Github action in Inspektor Gadget here to build a new container image, push it to a container registry, and build the CLI with that exact image reference, so that the artifact could be downloaded on one's laptop and just try it without fearing to use the wrong tag of the container image. Since kubectl-trace and IG have similar architecture, that could help here. At the moment, my setup only really works with people who have rights on the upstream GitHub organization but that's something that I want to improve (inspektor-gadget/inspektor-gadget#31). I am interested in testing on different Linux versions & Kubernetes versions too. I wanted to explore the self hosted runner but haven't so far. If you find how to set it up, I am interested :) |
I like this idea too! |
This moves the CI and release process to github actions from Travis
This moves the CI and release process to github actions from Travis
Github actions is now available and its been enabled for the iovisor github org.
Someone with admin access to this repo can add the QUAY_TOKEN to it like what is been done with travis.
The major advantage of actions over travis that I see are:
WDYT @leodido @fntlnz
The text was updated successfully, but these errors were encountered: