-
Notifications
You must be signed in to change notification settings - Fork 578
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
GHA: build RHEL and Amazon Linux #9266
Conversation
de3d77c
to
e388bc4
Compare
to have all info at one place in the file.
64833f1
to
e1f0503
Compare
e1f0503
to
394d507
Compare
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.
Can you try if it's possible to keep the old job names by using the matrix variables in the name
option? This suggests that this might be possible and hopefully this would let us avoid having to mess around with the branch protection rules too much (and thus avoid a mess in all older PRs).
.github/workflows/rpm.yml
Outdated
docker login registry.icinga.com -u build-docker/sles --password-stdin <<<"$GITLAB_REGISTRY_RO_TOKEN" | ||
docker login registry.icinga.com -u github --password-stdin <<<"$GITLAB_RO_TOKEN" |
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.
https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html says that personal access tokens are supposed to be used with the username (even though the username is ignored at the moment, but given that there's a hint about this, I think that this might be changed in the future).
with more permissions and URL-friendlier login name.
"old job names" like the ones below next to "Expected — Waiting for status to be reported"? Likely possible. But I consider them not worth it and the mess reasonable. Just read the summary ignoring the expected checks: "22 successful and 6 expected checks" Also I don’t expect more of such refactories soon and we shall change the rules for each new distro anyway despite old PRs. So I opt for letting them as is. Even if we shall set the names explicitly, they shall be actual names, not the current ones. |
394d507
to
b6d2234
Compare
Yes.
So even more reasons for having fixed names.
That's something different. ".rpm (centos, 7)" and ".rpm (centos, 7, false)" is fundamentally the same check
I'd also be okay with making this the PR changing it to "actual names", though I think the previous names are fine. The new names just add a useless true/false without context that's just an implementation detail (.deb actually suffers from that same problem already). |
Errm... no? Actually it's the opposite.
Yes... ? And... what's the point? Old PRs should be rebased anyway for the sake of the actually added checks. Same for future refactories we don’t know of, yet.
It... suffers? |
Sorry, ignore that part, I somehow missed the important word "don't" when reading this.
Well, "should" is the important word here, we don't always do. When the names stay the same, you get a good summary of what is missing, rather than some chaos.
I consider ".rpm (centos, 7)" a better name than ".rpm (centos, 7, false)", so this alone would be reason enough for me to change this. |
No description provided.