Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-56385

allow setting of env. variables or parameters in triggered runs

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: pipeline
    • Labels:
      None
    • Similar Issues:

      Description

      While it's useful to be able to trigger a pipeline run based on a cron schedule, it would be even more useful, if along with the cron schedule, parameters or environment variables could be defined so that one could define different run models with the triggers.

      Probably a common example of this would be to run different sets of testing at pre-defined times, such as running more comprehensive (and resource intensive) testing on weekends when resource contention is low.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              brianjmurrell Brian J Murrell
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: