[JENKINS-49502] trigger properties in scripted pipeline require 2 builds to get registered

When defining trigger in a declarative pipeline, it will suffice to write

pipeline {
 agent any

 triggers {
   cron('H H(0-7) * * *')
 }
}

and build once.

After the first build accessing the job config UI will show the trigger configuration.

However if you do the same thing with a scripted pipeline

node {
    properties([pipelineTriggers([cron('H H(0-7) * * *')])])
}

you need two builds to register the trigger (it won't appear in the UI and won't be working until the second manual build).

valentina armenise created issue - 2018-02-12 11:03

valentina armenise made changes - 2018-02-12 11:03

Summary

Original: trigger properties in scripted pipeline require 2 builds to be registered in the UI

New: trigger properties in scripted pipeline require 2 builds to get registered

mike cirioli made changes - 2018-09-07 13:12

Assignee

New: mike cirioli [ mikecirioli ]

mike cirioli made changes - 2018-09-13 18:48

Resolution		New: Cannot Reproduce [ 5 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Liam Rae-McLauchlan made changes - 2018-09-28 10:50

Assignee	Original: mike cirioli [ mikecirioli ]
Resolution	Original: Cannot Reproduce [ 5 ]
Status	Original: Closed [ 6 ]	New: Reopened [ 4 ]

Jenkins