[Build] Define cron-trigger for DockerImagesBuild in Job definition #2398
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
The triggers defined in a Jenkins-pipeline are only applied to the Job-configuration after the first execution of the pipeline. This has the consequence that after each execution of the seed job the configuration of the 'DockerImagesBuild' is reset to have no triggers and consequently it would require a manual execution of that job to restore the cron-trigger each execution of the seed job.
|
This is not verified at all by verification builds so I submit this immediately and re-run the seed job in the |
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.
The triggers defined in a Jenkins-pipeline are only applied to the Job-configuration after the first execution of the pipeline. This has the consequence that after each execution of the seed job the configuration of the 'DockerImagesBuild' is reset to have no triggers and consequently it would require a manual execution of that job to restore the cron-trigger each execution of the seed job.