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

issue with parameter not initializing environment variable on schedule execution

    XMLWordPrintable

Details

    Description

      Hi,

      I ran into an issue where the second schedule ran at the scheduled time but did not initialize the environment variable. The format looks correct and the first schedule did initialize the same environment variable just fine.

      Attachments

        Activity

          jg1000c Jason Goyer added a comment -

          You can close. The issue was due to a space after the comma in choice parameter setting values.

          jg1000c Jason Goyer added a comment - You can close. The issue was due to a space after the comma in choice parameter setting values.
          jg1000c Jason Goyer added a comment -

          Caused by extended choice parameter values.

          jg1000c Jason Goyer added a comment - Caused by extended choice parameter values.

          People

            batmat Baptiste Mathus
            jg1000c Jason Goyer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: