Skip to content

ci: ci mode shouldnt wait for resources with auto_init=false [ch7838]#3485

Merged
maiamcc merged 4 commits into
masterfrom
maiamcc/autoinit-ci
Jun 19, 2020
Merged

ci: ci mode shouldnt wait for resources with auto_init=false [ch7838]#3485
maiamcc merged 4 commits into
masterfrom
maiamcc/autoinit-ci

Conversation

@maiamcc

@maiamcc maiamcc commented Jun 19, 2020

Copy link
Copy Markdown
Contributor

addresses #3478

Not sure that an integration test is the best way to verify this behavior--
@nicks are there better structures already in the code for testing ci mode?

@maiamcc
maiamcc requested review from landism and nicks June 19, 2020 20:49
// If any of the resources are in error, exit.
allOK := true
for _, mt := range state.ManifestTargets {
// don't wait on resources requiring manual trigger for initial build

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it might make sense to have a unit test for this

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(see the tests under controller_test.go)

Maia added 2 commits June 19, 2020 17:15
@maiamcc

maiamcc commented Jun 19, 2020

Copy link
Copy Markdown
Contributor Author

Ah I didn't realize there was such solid unit testing for this code. In that case, I'd rather leave it as just a unit test and not add another integration test (tho if either of you are particularly into the idea of there being an integration test @nicks @landism I can put it back!)

@maiamcc
maiamcc merged commit 7a1a9ff into master Jun 19, 2020
@maiamcc
maiamcc deleted the maiamcc/autoinit-ci branch June 19, 2020 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants