Erik Håkansson
Erik Håkansson
Yeah that sound's like a plan. And I was almost done with fixing the master branch the old way 😏
I'll still do it twofold, though, although the steps will be 1. Bump Jenkins version to 2.46.3 and fix everything 2. Implement future-testing
Status update: I've bumped the Jenkins version to 2.46.3, the org.jenkins-ci.plugins:plugin parent to 3.8 and the jenkins-test-harness to 2.38. The bumped parent pom includes a lot of new Maven Enforcer...
Another status update: I've gotten 6 of 11 tests to work. It has mostly been updating selenium tests that has been necessary. I've also had to wrestle some with getting...
@jan-molak and @dcendents please have a look at #369. Note that I have ONLY bumped the Jenkins version in that. I haven't merged the #365 PR, nor have I made...
Thanks guys! I'm on to step two, which is "future"-testing with the latest LTS. There were some changes in AbstractBuild (on the Jenkins side) that required some additional mocks for...
I've solved compatibility with both 2.46.3 and 2.107.2, but I managed to broke a couple of tests in the process so I'm working on solving them. However, I'm having some...
Unless I misunderstand, plugin-compat-tester isn't really for automated testing, right? I went with your first suggestion, splitting upp acceptance into two modules. PR #370 is waiting for review 😄 @jan-molak...
#370 is updated. I noticed that an old version of maven-enforcer-plugin was hardcoded in one of the submodules so I removed that to enable inheritance from the parent pom. I...
Ping @jan-molak had any time to check the PR? I'm running it locally at work here (Well actually, I'm running #293 , but I've rebased that on #370) and it...