-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add gitlab pipeline and remove plus building from github #1601
Conversation
fd3c506
to
6703ad7
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.
I'm not sure about having edge and nightly in the same file, I think it makes it harder to read. I don't see less duplicated code as you mentioned? It's only the Build binary
step?
needs: [binary, unit-tests] | ||
if: | ||
github.event.pull_request.head.repo.full_name == 'nginxinc/kubernetes-ingress' || |
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.
Wasn't this here to prevent builds from forks? We don't need it anymore?
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.
As far as I recall, we wanted to skip smoke tests from forks because they couldn't access secrets. We're not using secrets here any more, so smoke tests on OSS is probably a good idea before we review anything.
I've noticed that the link to the pipeline doesn't bring you directly to the run if gitlab needs to reauthenticate, but works fine after that. We should report a bug 😄 |
This comment has been minimized.
This comment has been minimized.
71f0e1e
to
b6eee90
Compare
- os: ubuntu-20.04 | ||
image: debian-plus | ||
tag: ${{ github.sha }} | ||
- image: alpine |
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.
Should we run all tests on debian
only? because of runs-on: ubuntu-20.04
?
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.
runs-on: ubuntu-20.04
is the just the runner OS - we always used ubuntu-20.04 runner for all of our jobs. The image is which IC image version we are using in the KinD cluster.
@@ -0,0 +1,7 @@ | |||
kind: Cluster |
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.
is this going outside of pipleines?
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.
It's so we are using the same configuration in github and gitlab
@@ -0,0 +1,14 @@ | |||
#!/bin/bash |
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.
same as above
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.
Same answer as above 👍🏼
ac23bc5
to
7a6babf
Compare
7a6babf
to
e134841
Compare
@@ -362,70 +254,15 @@ jobs: | |||
path: ${{ github.workspace }}/tests/tests-${{ steps.k8s.outputs.cluster }}.html | |||
if: always() | |||
|
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.
So much removed! Brilliant!
Proposed changes
Remove plus building from GitHub; remove some of the CI logic from the workflows to the test folder; add a gitlab-ci.yml file for the Gitlab integration,
Checklist
Before creating a PR, run through this checklist and mark each as complete.