[JENKINS-68370] issue with parameter not initializing environment variable on schedule execution - Jenkins Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Minor
Resolution: Fixed
Component/s: parameterized-scheduler-plugin
Labels:
None
Environment:
Jenkins 2.319.2, Linux, parameterized scheduler 1.0

Similar Issues:

Show

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

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

Screen Shot 2022-04-29 at 11.02.34 AM.png
54 kB
2022-04-29 15:31
Screen Shot 2022-04-29 at 11.03.17 AM.png
36 kB
2022-04-29 15:32
Screen Shot 2022-04-29 at 11.03.57 AM.png
40 kB
2022-04-29 15:32
Screen Shot 2022-05-02 at 10.48.38 AM.png
49 kB
2022-05-02 20:22

Activity

Ascending order - Click to sort in descending order

Jason Goyer added a comment - 2022-05-02 20:21

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

Jason Goyer added a comment - 2022-05-02 20:21 You can close. The issue was due to a space after the comma in choice parameter setting values.

Jason Goyer added a comment - 2022-05-02 20:22

Caused by extended choice parameter values.

Jason Goyer added a comment - 2022-05-02 20:22 Caused by extended choice parameter values.

People

Assignee:: Baptiste Mathus

Reporter:: Jason Goyer

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2022-04-29 15:32

Updated:: 2022-05-02 20:22

Resolved:: 2022-05-02 20:22