Closed krische closed 4 years ago
This pull request follows #50 which missed to change required settings and therefore the HPI file still contains Groovy 2.4.8.
@darxriggs Something is wrong with ci again. Can you refire this PR to kick off the job again
@markyjackson-taulia it's not my pull request so I cannot do so. You can close it, wait for some seconds, reopen it. Then ci.jenkins.io will be triggered again.
@krische let's wait some time for an answer from @nickgrealy and then adapt the pull request accordingly.
After the above investigations my goal would be to get rid of forceGroovy
completely. Otherwise the plugin would hit the same problem (2 different Groovy versions) from time to time again. I just tested with Jenkins LTS 2.204.1 which provides Groovy 2.4.12 and a custom plugin version which for example provides Groovy 2.4.17.
Leaving this as WIP until we have consensus
@krische Could you update the pull request with the slight adaptions I suggested or is there still something from your side to discuss?
@krische Do you know when you will have time to go on with this or should I take over?
As I lately also cleaned up the Gradle files in #60 there are now also merge conflicts to be resolved.
@darxriggs I don't have time to work on this soon, if you want to take over that would be great.
@krische Ok. I'll create a new pull request and add you as co-author to pay some contribution.
@darxriggs Should I close this one then?
@krische Yes, please close it. It is superseded by #61.
Thanks @darxriggs . Working on jenkins 2.204.3
Fixes #49
Changes proposed
Checklist
Notify
@markyjackson-taulia