Details

Description

In Jenkins, when setting the cron expression for a job's periodic build schedule, Jenkins conveniently tells me when the previous job would have ran and when the next job would run:

However, if Jenkins finds a problem with the expression it will instead display a warning:

Can a change be made so that, if it can still evaluate the expression, Jenkins will show both the warning and the example build times? For instance, I am aware of the issues with using short month cycles, but I still wish to, and I'd like to see when the next time would be. This is also an issue when Jenkins warns me that I should be using H instead of *.

In Jenkins, when setting the cron expression for a job's periodic build schedule, Jenkins conveniently tells me when the previous job would have ran and when the next job would run:

!2015-06-24_07h44_37.png|thumbnail!

However, if Jenkins finds a problem with the expression it will instead display a warning:

!2015-06-24_07h44_27.png|thumbnail!

Can a change be made so that, if it can still evaluate the expression, Jenkins will show both the warning and the example build times? For instance, I am aware of the issues with using short month cycles, but I still wish to, and I'd like to see when the next time would be. This is also an issue when Jenkins warns me that I should be using H instead of *.

In Jenkins, when setting the cron expression for a job's periodic build schedule, Jenkins conveniently tells me when the previous job would have ran and when the next job would run:

!2015-06-24_07h44_37.png!

However, if Jenkins finds a problem with the expression it will instead display a warning:

!2015-06-24_07h44_27.png|thumbnail!

Can a change be made so that, if it can still evaluate the expression, Jenkins will show both the warning and the example build times? For instance, I am aware of the issues with using short month cycles, but I still wish to, and I'd like to see when the next time would be. This is also an issue when Jenkins warns me that I should be using H instead of *.

In Jenkins, when setting the cron expression for a job's periodic build schedule, Jenkins conveniently tells me when the previous job would have ran and when the next job would run:

!2015-06-24_07h44_37.png!

However, if Jenkins finds a problem with the expression it will instead display a warning:

!2015-06-24_07h44_27.png|thumbnail!

Can a change be made so that, if it can still evaluate the expression, Jenkins will show both the warning and the example build times? For instance, I am aware of the issues with using short month cycles, but I still wish to, and I'd like to see when the next time would be. This is also an issue when Jenkins warns me that I should be using H instead of *.

In Jenkins, when setting the cron expression for a job's periodic build schedule, Jenkins conveniently tells me when the previous job would have ran and when the next job would run:

!2015-06-24_07h44_37.png!

However, if Jenkins finds a problem with the expression it will instead display a warning:

!2015-06-24_07h44_27.png!

Can a change be made so that, if it can still evaluate the expression, Jenkins will show both the warning and the example build times? For instance, I am aware of the issues with using short month cycles, but I still wish to, and I'd like to see when the next time would be. This is also an issue when Jenkins warns me that I should be using H instead of *.