Disable comprehensive tests option in Jenkinsfile#455
Merged
MichaelLueken merged 1 commit intoNov 4, 2022
Merged
Conversation
MichaelLueken
approved these changes
Nov 4, 2022
Collaborator
MichaelLueken
left a comment
There was a problem hiding this comment.
This is the same as PR #454, but disabling the comprehensive tests in the release branch. Approving update.
This file contains hidden or 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.
DESCRIPTION OF CHANGES:
The current method of scheduling workflow tests via cron in combination with the number of tests in the comprehensive suite is overwhelming the nodes that run the test scripts. This change disables the comprehensive test option in the Jenkins pipeline to prevent this from happening. The comprehensive test option can be re-enabled once the WE2E test scripts and/or comprehensive test configuration are updated to handle the job scheduling more efficiently.
Type of change
TESTS CONDUCTED:
CHECKLIST
LABELS (optional):
A Code Manager needs to add the following labels to this PR: