Details
-
New Feature
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
Description
So that the properties step can be used to define, for example, a daily build schedule for some or all branch projects.
Attachments
Issue Links
- causes
-
JENKINS-69057 The 'Build Triggers' button is missing from the sidebar on pipeline jobs
-
- Open
-
- depends on
-
JENKINS-30519 Declarative job properties in multibranch
-
- Resolved
-
- is blocking
-
JENKINS-34725 Multibranch Plugin: Shouldn't run every branch on re-index
-
- Closed
-
- is duplicated by
-
JENKINS-33378 Support triggers definition in Jenkinsfile
-
- Resolved
-
- is related to
-
JENKINS-32396 Option to suppress automatic SCM trigger
-
- Resolved
-
-
JENKINS-37477 PipelineTriggersJobProperty / pipelineTriggers() - snippet generator and syntax doc fail
-
- Resolved
-
- relates to
-
JENKINS-45067 PipelineTriggersJobProperty#startTriggers() throws NPE when the property is not assigned to job
-
- Resolved
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue depends on |
Link |
This issue is duplicated by |
Link |
This issue is related to |
Epic Link | JENKINS-35386 [ 171179 ] |
Link |
This issue is blocking |
Assignee | Jesse Glick [ jglick ] | Andrew Bayer [ abayer ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Remote Link | This issue links to "workflow-job-plugin PR #9 (Web Link)" [ 14625 ] |
Remote Link | This issue links to "workflow-multibranch-plugin PR #20 (Web Link)" [ 14629 ] |
Workflow | JNJira [ 170021 ] | JNJira + In-Review [ 185710 ] |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Link |
This issue is related to |
Component/s | pipeline-general [ 21692 ] |
Component/s | workflow-plugin [ 18820 ] |
Link |
This issue relates to |
Link | This issue causes JENKINS-69057 [ JENKINS-69057 ] |
Mentioning in this enhancement request that this one would be important for those people who are not allowed to setup github hooks:
In my project, we are not allowed any incoming hooks (long story, not negotiable) – so for us it is important to be able to configure a git polling interval for projects in a multi-branch configuration.
As a firm example: We do a full scan of our github projects for new projects with Jenkinsfiles twice a day, but would like to configure those jobs to start polling github for changes every 15 minutes. This would allow the full scan to occur just once a day, but the job to be configured to poll and build on any changes in those projects more frequently.
As I read and understand this, polling triggers would also be part of the configured job properties – just wanted to mention this specific use case.