-
Notifications
You must be signed in to change notification settings - Fork 23
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
Revisit running gitlint in the CI #298
Revisit running gitlint in the CI #298
Conversation
13b303d
to
a7f7860
Compare
Unlike the other tools gitlint is python, but that's not much of a stretch to install it like the other Go based tools. The naming is now a bit wrong, but that's a problem that can be fixed later. Signed-off-by: John Mulligan <jmulligan@redhat.com>
13517e5
to
23410b9
Compare
@synarete what do you think? I think the big differences between this and #274 is that I added gitlint to be auto installed like many of the other tools and then the thing that "makes it work" in the CI is to use the |
@phlogistonjohn Installing gitlint locally (like we do with other bin tools) looks great. That said, |
It's possible I overlooked something but I don't think the version you are testing is setting the
Try setting |
On second thought, I think I understand now. You're basing this run off of my commits but you are not running them as part of a PR. So while I think you have the key specified in the job, the value |
@phlogistonjohn Yor made a test with |
@phlogistonjohn Good catch! |
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.
LGTM
23410b9
to
e96e85e
Compare
/retest centos-ci/sink-clustered/mini-k8s-1.26 |
What happened to this part? Don't we need to differentiate pull_request and other events? |
Hah. I apparently added it to the sambacc version instead of this PR: Will fix. |
e96e85e
to
a5e2ac8
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.
looks good in general but found one typo ...
/retest centos-ci/sink-clustered/mini-k8s-1.26 |
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.
typofix mentioned previously
I don't see how my change would have broken the install for kustomize... but I did touch the file that makes it happen. |
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.
after more careful review, the PR lgtm, but a ci check is failing. this needs to be fixed to meet all requirements
Even my local run completed successfully with the patch. I'll take a look at it later. |
If a dependency of the script (go, python) is missing the script would silently fail very early on. This change tries to avoid any failure unless the tool in question actually depends on that dependency while also making the missing dependency more obvious with more output. Signed-off-by: John Mulligan <jmulligan@redhat.com>
Don't assume local branches exist, but do assume branches in origin. Signed-off-by: John Mulligan <jmulligan@redhat.com>
Install gitlint into the "GOBIN_ALT" dir if gitlint is not present. Signed-off-by: John Mulligan <jmulligan@redhat.com>
Based-On: 07e30e2 Credit-To: Shachar Sharon <ssharon@redhat.com> Signed-off-by: John Mulligan <jmulligan@redhat.com>
a5e2ac8
to
52a775e
Compare
I fixed the CI failure. install-tools.sh broke silently when either go (not in this case) or python3 (which failed in this case) were not on the system it also didn't matter if that was being used or not, so I updated the script with a 2nd patch. |
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.
lgtm.
Awesome find 👏🏻 Especially I liked the part where you added another commit instead of squashing the dependency change into previous one which kind of helped me easily understand the "missing python3" error in CentOS CI. |
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.
lgtm
After having to fight with actions/checkout in another repo for other reasons I learned a few things that may help us run the commit checks in the github ci