-
Notifications
You must be signed in to change notification settings - Fork 679
makefile target + script for creating demo k8s instances #4127
Conversation
Codecov Report@@ Coverage Diff @@
## master #4127 +/- ##
=======================================
Coverage 86.21% 86.21%
=======================================
Files 144 144
Lines 8877 8877
Branches 1187 1187
=======================================
Hits 7653 7653
Misses 990 990
Partials 234 234
Continue to review full report at Codecov.
|
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 wondering if we should change demo.groovy
to skip the deploy stage if the branch name doesn't satisfy Deis' app name rules (must only contain numbers, hyphens, and lowercase letters, must start with a lowercase letter, and can't end with a hyphen)?
@escattone that is a fantastic idea, I'll add that to this PR |
I'm not a Groovy programmer, but could something like this be used for doing that?
|
@escattone yes, that's excellent. We're prepending |
props to @escattone for the suggestion
@metadave The Jenkins doesn't report (in the curated output) that the failure was due to the
|
- if a corresponding k8s namespace -> branch does not exist, offer to: - delete the namespace - add an annotation to keep the namespace. The next run of this script won't offer to delete the namespace, and a command will be displayed (but not run) to clear the annotation. - ignore the namespace - if a corresponding k8s namespace -> branch DOES exist, don't do anything
I added one more piece to this PR: add
|
any more thoughts on this? |
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, nice work as usual @metadave.
@escattone will you please take a final look and merge if you don't find any issues I missed?
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.
Nice @metadave! This looks good to me!
I decided not to replace the assert in demo.groovy
with something that would do the same thing but display more user-friendly output on failure, since we check the branch name when we create the demo.
No description provided.