Closed
Conversation
NVIDIA is blocking local runners to access the Jetpack tarballs, let's move them to a local server. GRUB as well, so let's move to local server and use gnulib mirror. Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Use Zededa tocken for building PRs. Signed-off-by: Nikolay Martyanov <nikolay@zededa.com>
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
This commit changes the assets workflow to: 1. Produce assets for arm64 platform variants: nvidia-jp5 and nvidia-jp6 2. Fix the assets for IPXE installer 3. Create a sha256sum for all files Signed-off-by: Renê de Souza Pinto <rene@renesp.com.br>
Introduce a GitHub Actions workflow that enables authorized users to trigger a CI rerun by commenting `/rerun-ci` on a pull request. The workflow verifies the commenter against the list in CODEOWNERS before proceeding. It identifies failed workflow runs for the PR and attempts to rerun them. This aims to streamline CI management and restricts rerun capabilities to approved users, improving security and workflow efficiency. Signed-off-by: Nikolay Martyanov <nikolay@zededa.com>
Update the workflow to use the GitHub CLI (gh) instead of direct curl calls to the GitHub API for interacting with workflow runs. This change streamlines authentication, error handling, and parsing. Additionally, improve how failed runs are identified by filtering on the correct event type (pull_request_target) and branch using `gh run list`, making the rerun logic more accurate and robust. The logic for canceling and rerunning workflow runs via comment commands is also updated to work with the new approach. Introduce a /rerun-ci cancel command that cancels all in-progress or queued runs for the current pull request and then re-runs any runs that were canceled, giving users more control over workflow execution directly from PR comments. Signed-off-by: Nikolay Martyanov <nikolay@zededa.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Provide a clear and concise description of the changes in this PR and
explain why they are necessary.
If the PR contains only one commit, you will see the commit message above:
fill free to use it under the description section here, if it is good enough.
For Backport PRs, a full description is optional, but please clearly state
the original PR number(s). Use the #{NUMBER} format for that, it makes it easier
to handle with the scripts later. For example:
Title of a backport PR must also follow the following format:
where
x.y-stableis the name of the target stable branch, andOriginal PR titleis the title of the original PR.For example, for a PR that backports a PR with title
Fix the nasty bugtobranch
13.4-stablethe title should be:[13.4-stable] Fix the nasty bug.PR dependencies
List all dependencies of this PR (when applicable, otherwise remove this
section).
How to test and validate this PR
Please describe how the changes in this PR can be validated or verified. For
example:
This will be used
The first is especially important, so, please make sure to provide as much
detail as possible.
If it's covered by an automated test, please mention it here.
Changelog notes
Text in this section will be used to generate the changelog entry for
release notes. The consumers of this are end users, not developers.
So, provide a clear and short description of what is changed in the PR from
the end user perspective. If it changes only tooling or some internal
implementation, put a note like "No user-facing changes" or "None".
PR Backports
For all current LTS branches, please state explicitly if this PR should be
backported or not. This section is used by our scripts to track the backports,
so, please, do not omit it.
Here is the list of current LTS branches (it should be always up to date):
For example, if this PR fixes a bug in a feature that was introduced in 14.5,
you can write:
Also, to the PRs that should be backported into any stable branch, please
add a label
stable.Checklist
For backport PRs (remove it if it's not a backport):
And the last but not least:
check them.
Please, check the boxes above after submitting the PR in interactive mode.