-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Fix build wheels workflow to allow triggering it on workflow dispatch #21985
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
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
The following files, which will be shipped with the agent, were modified in this PR and You can ignore this if you are sure the changes in this PR do not require QA. Otherwise, consider removing the label. List of modified files that will be shipped with the agent |
This reverts commit 71154ef.
Review from lucia-sb is dismissed. Related teams and files:
- agent-integrations
- .github/workflows/resolve-build-deps.yaml
- .github/workflows/scripts/resolve_deps_check_should_run.sh
- .github/workflows/scripts/resolve_deps_define_diff_commits.sh
Review from HadhemiDD is dismissed. Related teams and files:
- agent-integrations
- .github/workflows/resolve-build-deps.yaml
- .github/workflows/scripts/resolve_deps_check_should_run.sh
- .github/workflows/scripts/resolve_deps_define_diff_commits.sh
Review from iliakur is dismissed. Related teams and files:
- agent-integrations
- .github/workflows/resolve-build-deps.yaml
- .github/workflows/scripts/resolve_deps_check_should_run.sh
- .github/workflows/scripts/resolve_deps_define_diff_commits.sh
iliakur
left a comment
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.
Sooo much easier to read the workflow file now!
|
The backport to To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-7.74.x 7.74.x
# Navigate to the new working tree
cd .worktrees/backport-7.74.x
# Create a new branch
git switch --create backport-21985-to-7.74.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 15351d3c2121a5a3c6b4c7a43f403a20447b0d58
# Push it to GitHub
git push --set-upstream origin backport-21985-to-7.74.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-7.74.xThen, create a pull request where the |
…#21985) * Fix build wheels workflow to allow running on dispatch * Ensure image digest is persisted if we are going to build and lock files * Unindent EOF * Pin krb5 to avoid the failed build * Revert "Pin krb5 to avoid the failed build" This reverts commit 71154ef. * Try new krb5 pin * wip: Work in Progress * Add back dependency on dcb alongside requests-kerberos * Remove pin and opened a separate PR for that * Remove redundant if condition and chomping pipes * Extract complex logic to separate bash scripts * Ensure we checkout the repo to get the scritps
What does this PR do?
This PR updates the build wheels workflow to allow us running it on
workflow_dispatch.The way this work is as follows:
We decide this based on the
Check if build should runjob. This job will skip the files changed validation on workflow dispatch, which is more expensive, and define the following variables:should_run_build=truebuilder_changed=falseThis ensures that we do not rebuild builders when running on demand, which is only done to build wheels but triggers the build down the line.
If we are running on a push or PR,
builder_changedwill only be true if we have modified the builders code and a new image needs to be recreated. Theshould_run_buildvariable is set to true only if we have modified theagent_requirements.infile or if the builders have changed (since we need to make sure to build with the latest version).Motivation
We recently updated it to be able to run always, since we need it to always run to produce a standard workflow when generating sizes (i.e. run sizes calculation after this finishes and use the sizes built by it when needed or not but ensure it always finish running before size calculation starts).
We forgot that we need to be able to run this workflow also on demand if we need to resolve dependencies in master or a release branch. This changes brings back this feature while maintaining what we need.
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged