Skip to end of metadata
Go to start of metadata

Plugin Information

View Parameterized Scheduler on the plugin site for more information.

Lets you define many cron-like formatted entries, but with additional parameters for each definition.Warning: the plugin configuration is only visible for jobs with parameters. This means you'll to first add at least one parameter, then save, then get back to configuring.

See more documentation including usage examples in the README.

CHANGELOG

  • No labels

19 Comments

  1. This plugin is not working for me (jenkins 2.7.2)
    My build flow has parameter named as "slackChannel" and i setup build flow to run every 5 minutes like below, but its not triggering.

    H/5 * * * * %slackChannel=survey

    Please help here..
    Thanks.

    1. I think you are missing the (sometimes not shown in the examples) space following the '%' character.  Try something like the following and it may resolve your issue.

      #M HH DD MM WD  %  Variables
      H/10 08-15  *  *  * % VAR_1=Primary; VAR_2=Secondary;VAR_3=Tertiary
      H/10 08-15  *  *  * % VAR_1=Primus; VAR_2=Secondus;VAR_3=Tertius 

      1. Please generally avoid using comments here for "support" issues, prefer using the users mailing list, or IRC. Thank you!

        1. Perhaps the links to the "support" mailing list or IRC could be added to this page so everyone will be able to find them?

          It would also be a good idea to modify the page to add examples and other needed usage information and thus avoid these "support" issues in the first place.  Given the number of issues listed in this section, some additional information is clearly needed.

          1. Hi,

            • I think B.M. means the standard Jenkins mailing lists, or createa JIRA ticket using the Issue Tracking link above. 
            • Usage examples are under the README, which is linked here. Anyone using this plugin is welcome to become a maintainer and/or improve documentation.
            • That said, I don't see any unresolved 'support' issues here that are not addressed by the latest release and the README.
  2. When I start Jenkins (2.23 and earlier releases) on my RHEL5 machine I see the following information in the log file.

         50 Sep 20, 2016 3:15:51 PM org.jenkinsci.plugins.parameterizedscheduler.Cron getRecurrencePeriod
         51 WARNING: period set to 60000
         52 Sep 20, 2016 3:15:51 PM org.jenkinsci.plugins.parameterizedscheduler.Cron getRecurrencePeriod
         53 WARNING: period set to 60000
         50 Sep 20, 2016 3:15:51 PM org.jenkinsci.plugins.parameterizedscheduler.Cron getRecurrencePeriod
         51 WARNING: period set to 60000
         52 Sep 20, 2016 3:15:51 PM org.jenkinsci.plugins.parameterizedscheduler.Cron getRecurrencePeriod
         53 WARNING: period set to 60000

    My Jenkins instance has only one task on it, and this task has two times set to run with different options (I mention this because I see the warning twice).  There is nothing with "60000" defined in any xml file (that I can see) and I don't see anything mentioning "getRecurrencePeriod" in my Jenkins instance either.  I'm suspecting this is some kind of default, but wonder why there is a warning and how I may get rid of this message.

  3. I cannot run my jobs from this plugin. They fail with the following exception:

    07:19:31 ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com
    07:19:31 java.lang.IllegalArgumentException: can't parse argument number: environmentParam=QA

    My cron syntax is this:

    19 7 * * * % environmentParam=QA; browserParam=Chrome

  4. Installed the plugin but the "Build periodically with parameters" option does not appear on a pipeline job definition.

    The extra option does appear on other, non-pipeline, jobs.

    Is this not usable for pipeline jobs ?


  5. My team is seeing some unexpected output for this plugin:

    H 8 * * * % SPRING_PROFILE="qa"; TEST_SUITE="Regression.xml"
    H 8 * * * % SPRING_PROFILE="prodlive"; TEST_SUITE="ProdSmoke.xml"

    displays "You can only use one percent sign to separate the cron from the parameters." even though there is clearly only one '%' character on each line.  I'm guessing that the contents of the schedule text area are being processed as a single stream of characters rather than on a line by line basis.

    Looks like this needs to be fixed right away or this plugin isn't going to be very useful.

  6. Above validation is only kind of warning because i am also using these multiple lines and it works like charm.

  7. I am seeing the same issue that Brian is above (only one percent sign) except my jobs never get scheduled.  Is there something I have to do besides enable the job to get them scheduled?  Rich

  8. @jwmach1 has a fix for JENKINS-44031, which I have merged into my pull request: https://github.com/jenkinsci/parameterized-scheduler-plugin/pull/4

    I uploaded a build with the fix - in my brief testing, it resolves the 'more than one percent sign' error and the multi line schedule is triggered correctly.

    Please try it out and comment on the pull request. Writing to the jenkinsci-dev list to find someone who can merge it!

  9. Please generally avoid using comments here for "support" issues, prefer using the users mailing list, or IRC. Thank you!

  10. I m unable to find the option "Build periodically with parameter" 

    Can u plz help me 

    i m using latest version of Jenkins 2.73

    if this plugin is not compatible to this version then tell me the substitute of this pulgin

  11. Hi all,

    Im  using extended choice parameter plugin with json input but this plugin return the error:Null pointer exception

     

    FATAL: null
    java.lang.NullPointerException
    	at hudson.model.ParametersAction.filter(ParametersAction.java:328)
    	at hudson.model.ParametersAction.getParameters(ParametersAction.java:183)
    	at hudson.model.ParametersAction.iterator(ParametersAction.java:178)
    	at hudson.model.AbstractBuild.getSensitiveBuildVariables(AbstractBuild.java:957)
    	at org.jenkinsci.plugins.envinject.util.RunHelper.getSensitiveBuildVariables(RunHelper.java:55)
    	at org.jenkinsci.plugins.envinject.service.EnvInjectActionSetter.addEnvVarsToRun(EnvInjectActionSetter.java:69)
    	at org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:83)
    	at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:44)
    	at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542)
    	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462)
    	at hudson.model.Run.execute(Run.java:1724)
    	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    	at hudson.model.ResourceController.execute(ResourceController.java:97)
    	at hudson.model.Executor.run(Executor.java:421)
    Finished: FAILURE

    any idea?

    1. caglar cglr please file a JIRA issue with the corresponding components on https://issues.jenkins-ci.org/browse/JENKINS thanks

  12. Im created an issue  JENKINS-49372 - Getting issue details... STATUS

    thanks:)

  13. Hello thanks for this plugin.

    Do you know if there is a plugin like Cron Column Plugin that allows cron-like formatted entries to be shown into a column view ?