-
Notifications
You must be signed in to change notification settings - Fork 806
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
fix(bake): Log when bake request amiSuffix and stage context amiSuffix values are different and resolve the difference #3960
Merged
jonsie
merged 1 commit into
spinnaker:master
from
jonsie:warn-resolve-amiSuffix-difference
Oct 9, 2020
Merged
fix(bake): Log when bake request amiSuffix and stage context amiSuffix values are different and resolve the difference #3960
jonsie
merged 1 commit into
spinnaker:master
from
jonsie:warn-resolve-amiSuffix-difference
Oct 9, 2020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…x values are different and resolve the difference
jonsie
force-pushed
the
warn-resolve-amiSuffix-difference
branch
from
October 9, 2020 01:06
be85a3a
to
afe8bff
Compare
jonsie
commented
Oct 9, 2020
String rebake = shouldRebake(stage) ? "1" : null | ||
|
||
if (stage.context.amiSuffix != null && bake.amiSuffix != null && bake.amiSuffix != stage.context.amiSuffix) { |
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.
No trust.
cfieber
approved these changes
Oct 9, 2020
deverton
pushed a commit
to deverton/orca
that referenced
this pull request
Oct 12, 2020
…x values are different and resolve the difference (spinnaker#3960)
amanya
pushed a commit
to amanya/orca
that referenced
this pull request
Oct 23, 2020
…x values are different and resolve the difference (spinnaker#3960)
mergify bot
added a commit
that referenced
this pull request
Oct 28, 2020
* fix(wait): Fix wait for up instances task This change in clouddriver spinnaker/clouddriver#4681 added a boolean `pinned` field to the `Capacity` object in `ServerGroup`. However there's some code in the `WaitForUpInstancesTask` in Orca that depends on the types all being `Integer`. The end result is that the wait task fails with a stack trace like: ``` org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'true' with class 'java.lang.Boolean' to class 'java.lang.Integer' ``` This patch updates the task to just get the fields it needs to compare and adds a test for this case. * chore(kork): update kork dependency (now w/ moniker) (#3958) * test(preconfigured): include integration test for preconfigured job (#3945) * test(preconfigured): include integration test for preconfigured job with kubernetes provider * refactor(preconfigured): refactor test * feat(clouddriver): Look ahead region detection for "aws" can be disabled (#3959) Similar to the bake stage, `skipRegionDetection` can be used to determine whether or not additional regions are inferred from downstream deploy stages. The default value is `false` which preserves the existing behavior. ``` { ... "skipRegionDetection": true } ``` * feat(orca): Add support for Redis SSL (#3934) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> * feat(queue): Add command to cleanup zombie executions (#3946) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> * fix(bake): Log when bake request amiSuffix and stage context amiSuffix values are different and resolve the difference (#3960) * chore(dependencies): Autobump spinnakerGradleVersion (#3962) Co-authored-by: root <root@877703f80d77> Co-authored-by: Michael Plump <plumpy@google.com> Co-authored-by: Edgar Garcia <63310723+edgarulg@users.noreply.github.com> Co-authored-by: Adam Jordens <adam@jordens.org> Co-authored-by: tompiscitell <tompiscitell@users.noreply.github.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Rob Zienert <rzienert@netflix.com> Co-authored-by: Chris Smalley <csmalley@netflix.com> Co-authored-by: spinnakerbot <spinbot@spinnaker.io> Co-authored-by: root <root@877703f80d77>
KathrynLewis
pushed a commit
to KathrynLewis/orca
that referenced
this pull request
Jan 31, 2021
…x values are different and resolve the difference (spinnaker#3960)
KathrynLewis
pushed a commit
to KathrynLewis/orca
that referenced
this pull request
Jan 31, 2021
* fix(wait): Fix wait for up instances task This change in clouddriver spinnaker/clouddriver#4681 added a boolean `pinned` field to the `Capacity` object in `ServerGroup`. However there's some code in the `WaitForUpInstancesTask` in Orca that depends on the types all being `Integer`. The end result is that the wait task fails with a stack trace like: ``` org.codehaus.groovy.runtime.typehandling.GroovyCastException: Cannot cast object 'true' with class 'java.lang.Boolean' to class 'java.lang.Integer' ``` This patch updates the task to just get the fields it needs to compare and adds a test for this case. * chore(kork): update kork dependency (now w/ moniker) (spinnaker#3958) * test(preconfigured): include integration test for preconfigured job (spinnaker#3945) * test(preconfigured): include integration test for preconfigured job with kubernetes provider * refactor(preconfigured): refactor test * feat(clouddriver): Look ahead region detection for "aws" can be disabled (spinnaker#3959) Similar to the bake stage, `skipRegionDetection` can be used to determine whether or not additional regions are inferred from downstream deploy stages. The default value is `false` which preserves the existing behavior. ``` { ... "skipRegionDetection": true } ``` * feat(orca): Add support for Redis SSL (spinnaker#3934) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> * feat(queue): Add command to cleanup zombie executions (spinnaker#3946) Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> * fix(bake): Log when bake request amiSuffix and stage context amiSuffix values are different and resolve the difference (spinnaker#3960) * chore(dependencies): Autobump spinnakerGradleVersion (spinnaker#3962) Co-authored-by: root <root@877703f80d77> Co-authored-by: Michael Plump <plumpy@google.com> Co-authored-by: Edgar Garcia <63310723+edgarulg@users.noreply.github.com> Co-authored-by: Adam Jordens <adam@jordens.org> Co-authored-by: tompiscitell <tompiscitell@users.noreply.github.com> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> Co-authored-by: Rob Zienert <rzienert@netflix.com> Co-authored-by: Chris Smalley <csmalley@netflix.com> Co-authored-by: spinnakerbot <spinbot@spinnaker.io> Co-authored-by: root <root@877703f80d77>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We encountered an issue wherein the
amiSuffix
sent in the bake request was different than theamiSuffix
value set in the stage context. I have not found a logical reason for how this could happen, but if it does happen let's just set it to what is in the stage context and log it out.