-
Notifications
You must be signed in to change notification settings - Fork 75
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Extract jobGroup creation to a separate method
Avoid duplicating code that is common between uses. Use a job group name that is distinct for each test so that the single JenkinsRule instance does not risk having the tests collide in their use of the job group.
- Loading branch information
1 parent
1c2dbb4
commit 4ae7296
Showing
1 changed file
with
20 additions
and
12 deletions.
There are no files selected for viewing
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
4ae7296
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.
Hey @MarkEWaite you told to Use a job group name distinct for each test then why did you change
ViewBasedJobInclusionStrategy("existingView") and removed ViewBasedJobInclusionStrategy("defaultView")
4ae7296
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 catch! For safety, the new view based job inclusion strategy should use a distinct name just as the job group does. I'll submit a pull request to fix that mistake.
4ae7296
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.
Mistake corrected in: