Moving job runner section out of conditional block #39
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
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.
Currently the Job_Runner call is in the conditional block of Load_Platform so if people choose not to generate example workspace, Job_Runner also won't be called which is incorrect behaviour. This PR will move it out of that block so it will always be called.
To test this, you can spin up an ADOP instance by changing the Jenkins image to have the tag dsingh07/adop-jenkins:load_platform
A valid test would be to spin it up with the --without-load flag and then to run "Load_Platform" without "Generate_Example_Workspace" ticked.