Pick up forkCount fix from acceptance-test-harness

[jglick]

Follows up #1327 by picking up jenkinsci/acceptance-test-harness#885. Would appreciate a release. @basil @uhafner

[uhafner]

How does a release of the warnings plugin help here? A release currently is executed in the plugin folder only. The UI tests are not affected by a release up to now. Or how do you use the UI tests together with the plugin in your PCT? Wouldn't it make more sense to simply ignore the UI tests in PCT?

[jglick]

Currently the UI tests do seem to get run in PCT. Perhaps it would make sense to ignore them, but I would need to explore how to do that. At any rate, it seems worth a shot at having them just pass.

[jglick]

How does a release of the warnings plugin help here?

Simply by having a different release tag. PCT checks out plugin sources from the version tag before running tests.

[codecov]

Codecov Report

Merging #1332 (8b5ab73) into master (42a03ba) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1332   +/-   ##
=========================================
  Coverage     79.78%   79.78%           
  Complexity     1448     1448           
=========================================
  Files           251      251           
  Lines          5611     5611           
  Branches        427      427           
=========================================
  Hits           4477     4477           
  Misses          983      983           
  Partials        151      151           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[uhafner]

Release is in progress...

[jglick]

https://github.com/jenkinsci/warnings-ng-plugin/runs/7789365123?check_suite_focus=true#step:5:28 hmm

[jglick]

jenkinsci/acceptance-test-harness#885 (comment) I guess this was merged without CI passing?

[uhafner]

Yes, I thought it is urgent to get the release out. Since there were no changes in the plugin I thought that it was safe. Since GitHub actions sometimes have problems when accessing Jenkins resources I thought it would not harm.

[jglick]

Well I certainly appreciate the prompt response, but it looks like this was actually broken. 😬

[jglick]

jenkinsci/acceptance-test-harness#885 (comment) try again

[uhafner]

https://github.com/jenkinsci/warnings-ng-plugin/releases/tag/v9.17.0