-
Notifications
You must be signed in to change notification settings - Fork 198
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
Finish migrating packaging pipeline to Github Actions. #753
Conversation
@gregdenton @larsbijl @DiegoTavares Ping, could I get a review on this? Nothing new here, just migrating existing CI logic to Github Actions. |
How can I run the action @bcipriano to test? |
This pipeline relies on secrets which are stored at the ASWF level, so I don't think it will run in a fork or as a PR-driven action. In general that's ok because the pipeline is really only meant to run when new commits are merged into As a committer you should be able to do the following:
I used a setup like this to test the pipeline while I was working on it. See for example https://github.com/AcademySoftwareFoundation/OpenCue/actions/runs/199732120. |
LGTM! |
Link the Issue(s) this Pull Request is related to.
#715
Summarize your change.
This migrates all remaining build steps from the Azure file to the Github Actions pipeline. All artifacts now get uploaded to S3, to be used later by the release pipeline when creating the release.