dependabot[bot] on maven
Caused by: javaposse.jobdsl.plugin.structs.ParameterMissingException: No signature of method: periodicFolderTrigger() is applicable for argument types: (script$_run_closure1$_closure6$_closure14$_closure15) values: [script$_run_closure1$_closure6$_closure14$_closure15@754dee7a]
@jbouse
I'm having to pull 3 plugins directly from ci.jenkins.io to get around issues and custom war packager looked like it might make it easier to deal with
If you want to use pom.xml as an input, better to wait for Custom WAR Packager 1.6.1 or 2.0.0 alpha. There are some fixes and performance inprovements for that mode. If you want to use it, 1.5 is probably a better option.
@jbouse
I'm having to pull 3 plugins directly from ci.jenkins.io to get around issues and custom war packager looked like it might make it easier to deal with
In Jenkins there is support of "Incremental" releases now. If the plugins in subject have been already updated to use incrementals, You can use unreleased versions (and even versions from PRs) using plugins.txt
@MarkEWaite
When @oleg-nenashev touches something, it improves. The Java 11 support work, the custom war packager, and now JCasC. Thanks @oleg-nenashev !
Thanks for the feedback :) For the record, my patches broke Jenkins weekly releases only 3 times in past 5 years :( I do not eve mention "my merges"
is there a way to get JCasC to keep Jenkins from starting up when there's an error with the config due to a plugin upgrade?
Not currently, there's an issue for it though
@casz mock release in https://github.com/jenkinsci/hashicorp-vault-plugin/releases/tag/hashicorp-vault-plugin-2.2.0 broke Release Drafter generation. Due to wwhatever reason it calculates changelog since the activation time if there is a GitHub Release. I would expect it to generate it starting from the last release label, but I do not understand machinery. Might be a quick fix
Already reported at toolmantim/release-drafter#222 never got around to it :sweat: