Skip to content
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

Integrate the alls-green action into the main GHA CI workflow #1639

Merged
merged 3 commits into from
Jun 25, 2024

Conversation

x1101
Copy link
Contributor

@x1101 x1101 commented Jun 24, 2024

Resolves #1284.

Testing shows that this doesn't surfaces which part of the nox matrix fails, but does fail the workflow when any of them do.

Copy link
Member

@webknjaz webknjaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Almost there! Just drop the non-existing references…

.github/workflows/ci.yaml Outdated Show resolved Hide resolved
@webknjaz
Copy link
Member

Testing shows that this doesn't surfaces which part of the nox matrix fails, but does fail the workflow when any of them do.

GitHub does not provide us with this context, so it's not possible to retrieve.

@webknjaz webknjaz changed the title Integrating all-green into ci.yml Integrate the alls-green action into the main GHA CI workflow Jun 24, 2024
When rebuilding this work after repo cleanup, I missed removing these. Thanks for catching that.

Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <wk.cvs.github@sydorenko.org.ua>
@x1101
Copy link
Contributor Author

x1101 commented Jun 24, 2024

Testing shows that this doesn't surfaces which part of the nox matrix fails, but does fail the workflow when any of them do.

GitHub does not provide us with this context, so it's not possible to retrieve.

Yeah, I was just highlighting the results of my testing and the limits of what this can provide, because the issue requesting doesn't really specify what information we were trying to get and I wanted it to be obvious what this does/doesn't do

@gotmax23
Copy link
Collaborator

I'm honestly fine with the current approach. We already require the two docs build/checker jobs in the branch protection settings.

.github/workflows/ci.yaml Outdated Show resolved Hide resolved
@webknjaz
Copy link
Member

I'm honestly fine with the current approach. We already require the two docs build/checker jobs in the branch protection settings.

But it requires somebody with proper access to continuously watch for the need to update the branch protection rules whenever workflows change, vs. having a transparent record of what's required.

@oraNod oraNod merged commit a732a1e into ansible:devel Jun 25, 2024
8 of 9 checks passed
@oraNod
Copy link
Contributor

oraNod commented Jun 25, 2024

Thanks very much for doing the work here @x1101 and thanks for the review @webknjaz 🎉

@samccann
Copy link
Contributor

@oraNod can you add any appropriate backport labels (if we want this in anything other than devel for how)?

@oraNod oraNod added the backport-2.17 Automatically create a backport for the stable-2.17 branch label Jun 25, 2024
Copy link

patchback bot commented Jun 25, 2024

Backport to stable-2.17: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2.17/a732a1ee7cabf5971c1933d9ad6e2e691aa2455f/pr-1639

Backported as #1647

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback bot pushed a commit that referenced this pull request Jun 25, 2024
* Integrating all-greens into ci.yml

* removing non-existing references

When rebuilding this work after repo cleanup, I missed removing these. Thanks for catching that.

Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <wk.cvs.github@sydorenko.org.ua>

* Update .github/workflows/ci.yaml

---------

Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <wk.cvs.github@sydorenko.org.ua>
Co-authored-by: Don Naro <dnaro@redhat.com>
(cherry picked from commit a732a1e)
@oraNod
Copy link
Contributor

oraNod commented Jun 25, 2024

@samccann Shoot. Guess I forgot the backport. Thanks for the reminder. Maybe we should just keep this on devel and stable-2.17.

oraNod pushed a commit that referenced this pull request Jun 25, 2024
… (#1647)

* Integrating all-greens into ci.yml

* removing non-existing references

When rebuilding this work after repo cleanup, I missed removing these. Thanks for catching that.

Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <wk.cvs.github@sydorenko.org.ua>

* Update .github/workflows/ci.yaml

---------

Co-authored-by: Sviatoslav Sydorenko (Святослав Сидоренко) <wk.cvs.github@sydorenko.org.ua>
Co-authored-by: Don Naro <dnaro@redhat.com>
(cherry picked from commit a732a1e)

Co-authored-by: Lyle McKarns <x1101@users.noreply.github.com>
@x1101 x1101 deleted the issue1284_integrate_allgreens branch June 25, 2024 21:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-2.17 Automatically create a backport for the stable-2.17 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Integrate alls-green into the repository
5 participants