-
Notifications
You must be signed in to change notification settings - Fork 19
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
chore: remove obsolete job params and scripts #215
Conversation
fd201be
to
f24b239
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.
As we discussed, we should keep GOVERSION in the package source and use that value every time we pull the source from s3.
jobs/ci-run/unittest/unittests.yml
Outdated
builders: | ||
- wait-for-cloud-init | ||
- install-common-tools | ||
- apt-install: | ||
packages: gcc squashfuse | ||
- detect-commit-go-version |
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.
instead of using github api, move get-s3-source-payload up to here, then install go
jobs/ci-run/unittest/unittests.yml
Outdated
builders: | ||
- wait-for-cloud-init | ||
- install-common-tools | ||
- apt-install: | ||
packages: gcc squashfuse | ||
- detect-commit-go-version |
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 here
5f12200
to
29261d4
Compare
29261d4
to
bd99347
Compare
The ci test jobs do not need BOOTSTRAP_SERIES params. If we want to test a controller on a specific Juju version that will be in a bespoke test.
We also don't need the params bloat in passing around GOVERSION all over the place - just detect it from the commit sha where needed using the existing script and export it.
Also delete obsolete windows and centos scripts.