Hi all,
I am trying to get this pull request
merged: https://github.com/jenkinsci/parameterized-scheduler-plugin/pull/4
It fixes JENKINS-42224 and enables the parameterizedCron trigger in
declarative pipelines.
Also happy to volunteer as maintainer for this plugin if the current
maintainers are tied up. I think it is more or less under a feature freeze.
I was surprised this is not a more common use case - one pipeline with
scheduled runs with different parameter sets.
What would be the best approach for this functionality?
Since we already have 'when' conditional blocks for stages, would it make
sense to support multiple predefined environments? e.g.
environment = switch("BRANCH_NAME")
case'master':return { BUILD_SNAPSHOT = true, DEPLOY = true }
default: return { BUILD_SNAPSHOT = true, DEPLOY = true }
We can support patameterized-scheduler like functionality using the build
timestamp plugin:
environment = switch("BUILD_TIMESTAMP")
case /08:\d{2}:\d{2}/: return { BUILD_SNAPSHOT = true, DEPLOY = true }
default: return { BUILD_SNAPSHOT = true, DEPLOY = true }
If there's some interest I can have a go at implementing. Otherwise, stick
with the plugin I guess!
This would also address having to maintain different Jenkinsfiles in
multibranch projects for different branches just to have different
parameter defaults or environments.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/c6ccf2a4-4ba3-4a5b-9639-42c001faf3e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
