Fix load error

[Konboi]

Context

While I was implementing this plugin, a plugin loading error occurred.

First, I tried to update v2.361.4 because Pipeline API required it

https://gyazo.konboi.com/e588d921ce117e8781b7763e22b5efca.png

However, the error still occurred. So, I updated to v2.387.3.

Unfortunately, error wasn't resolved

Finally, I updated to the Jenkins version to v2.401.3 and loading error was resolved.

Ask

• Could you try to reproduce this issue on your local environment? If you cannot reproduce this issue, I'll fix my local env.
• Honestly, I'm not sure these version combinations and what should we choose the Jenkins version. Could you review around that carefully?

[Konboi]

Can we use Java v11?

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[kohsuke]

We intentionally depend on older version of Jenkins in order to maintain compatible with a wide range of Jenkins. There's nothing in this plugin that requires new version of Jenkins, so it's important to stick to the current base Jenkins version.

[kohsuke]

Jenkins store everything in a directory, called "$JENKINS_HOME", including all the plugins installed. When you are developing a plugin like this, $JENKINS_HOME is ./work.

When I start Jenkins clean with empty home, I do not get any errors, which suggests you probably have accidentally updated some plugin versions. Without the logs showing the plugin loading failure, it's hard to precisely pin down why, but probably there's no point.

I suggest you start by rm -rf ./work/plugins which just wipes the plugins, forcing the plugin dev environment to start with its default set of compatible plugins. I believe that should fix the problem.

[Konboi]

thank you, I'll try to do rm -rf ./work/plugins.

[Konboi]

Thank you, the original error was resolved!