tests: Add upstream terraform trigger#1444
Conversation
139feae to
069f63f
Compare
5931e1a to
926bc28
Compare
|
Forgot to do some code updates. Moving back to WIP. |
9b3ddec to
323b380
Compare
|
@s-urbaniak @cpanato Ready for review. |
images/tectonic-builder/README.md
Outdated
|
|
||
| ## Upstream and CoreOS Terraform | ||
|
|
||
| We are currently using a custom terraform version for our default CI pipeline |
s-urbaniak
left a comment
There was a problem hiding this comment.
no objections, just a wording nit.
images/tectonic-builder/Dockerfile
Outdated
| # docker tag <resulting-image-id> quay.io/coreos/tectonic-builder:<next-semver> | ||
| # docker push quay.io/coreos/tectonic-builder:<next-semver> | ||
| # | ||
| # docker build --build-arg TERRAFORM_URL=<upstream terraform download url> -f builder/Dockerfile . |
There was a problem hiding this comment.
the path for the Dockerfile is not right
There was a problem hiding this comment.
also dont need to use the -t quay.io/coreos/tectonic-builder:v1.33-upstream-terraform as described in the readme?
There was a problem hiding this comment.
Its up to you if you build and then tag, or just tag during building via -t. But probably easier in two steps. Adjusted accordingly. Thanks.
cpanato
left a comment
There was a problem hiding this comment.
LGTM, just my comment need to check but it is a non blocker
323b380 to
82a60f6
Compare
|
@s-urbaniak @cpanato Thanks for the review. Addressed all suggestions. Let me know if you see anything else. |
|
@squat @Quentin-M @estroz Feel free to merge if you have no objections. |
squat
left a comment
There was a problem hiding this comment.
Everything looks good except for a small nit in documentation
images/tectonic-builder/README.md
Outdated
|
|
||
| The Tectonic CI is currently using a custom terraform version for the default | ||
| pipeline (See https://github.com/coreos/tectonic-installer/pull/1247). As end | ||
| users of Tectonic installer use upstream terraform we need to test with upstream |
There was a problem hiding this comment.
let's be consistent with the casing of Terraform. Either terraform or Terraform but we should not switch.
82a60f6 to
7bc232b
Compare
|
@squat Thanks for the catch. Adjusted accordingly. Let me know if you have any other objections. |
|
@mxinden could you please rebase |
7bc232b to
044d20f
Compare
|
@cpanato Sorry for the delay and thanks for the reminder. Rebased. Let me know what you think. |
|
This will not turn green until #1558 is merged. |
|
The only breaking change of this PR is In build number 13 everything is green except:
Both of these stages succeeded in build number 15. Instead of retriggering the tests until all are green on this minor change, I would prefer to merge, even though the current build is not fully green. @squat If you feel comfortable with this, please merge. |
044d20f to
4659a6c
Compare
| # docker push quay.io/coreos/tectonic-builder:<next-semver> | ||
| # | ||
| # docker build \ | ||
| # --build-arg TERRAFORM_URL=<upstream terraform download url> \ |
There was a problem hiding this comment.
Is this the release bundle or the binary itself?
There was a problem hiding this comment.
Nevermind, I saw it below 👍
upstream-terraform-trigger.groovy
Outdated
| @@ -0,0 +1,3 @@ | |||
| node { | |||
| build job: 'tectonic-installer/master', parameters: [string(name: 'builder_image', value: 'quay.io/coreos/tectonic-builder:v1.36-upstream-terraform')] | |||
There was a problem hiding this comment.
This is hard to comprehend on one line.
Any chance we could break it down into multiple lines?
We are currently using a custom terraform version for our default CI pipeline (See coreos#1247). As end users of Tectonic installer use upstream terraform we need to test with upstream terraform as well. We are building and publishing the Tectonic builder image both with CoreOS Terraform as well as upstream Terraform. This is done via docker `--build-arg` `TERRAFORM_URL`. CoreOS Terraform is used for normal PR and branch tests, upstream Terraform is used once per day on master. * Add `--build-arg` `TERRAFORM_URL` to Tectonic builder Docker file * Update documentation in tectonic-builder/README.md * Add upstream-terraform-trigger.groovy pipeline job With this commit v1.36 and v1.36-upstream-terraform of the Tectonic builder images are pushed to quay.io/coreos/tectonic-builder. There are no functional changes, but changes to the build order in the Dockerfile. You can find the Jenkins job [here](https://jenkins-tectonic-installer.prod.coreos.systems/job/upstream-terraform-trigger/).
4659a6c to
15394f8
Compare
|
@alexsomesan Broke it down to multiple lines. Let me know if there is anything else? |
alexsomesan
left a comment
There was a problem hiding this comment.
Looks good!
Let get this in.
Concerns were only related to documentation. They have been addressed. In addition Alex looked over all new changes.
These were added in 15394f8 (tests: Add upstream terraform trigger, 2017-07-21, coreos/tectonic-installer#1444), but we returned to upstream Terraform in all cases in 379fd19 (Bump Terraform to 0.10.7, 2017-10-04, coreos/tectonic-installer#2041). Remove the stale docs.
These were added in 15394f8 (tests: Add upstream terraform trigger, 2017-07-21, coreos/tectonic-installer#1444), but we returned to upstream Terraform in all cases in 379fd19 (Bump Terraform to 0.10.7, 2017-10-04, coreos/tectonic-installer#2041). Remove the stale docs.
We are currently using a custom terraform version for our default CI
pipeline (See #1247).
As end users of Tectonic installer use upstream terraform we need to
test with upstream terraform as well. We are building and publishing the
Tectonic builder image both with CoreOS Terraform as well as upstream
Terraform. This is done via docker
--build-argTERRAFORM_URL. CoreOSTerraform is used for normal PR and branch tests, upstream Terraform is
used once per day on master.
--build-argTERRAFORM_URLto Tectonic builder Docker fileWith this commit v1.36 and v1.36-upstream-terraform of the Tectonic
builder images are pushed to quay.io/coreos/tectonic-builder. There
are no functional changes, but changes to the build order in the Dockerfile.
You can find the Jenkins job here.