-
Improvement
-
Resolution: Duplicate
-
Minor
-
None
I like the plugin to scan and find new Jenkinsfiles in my github org and create any jobs but not to automatically trigger them which seems to be the case.
Is it possible to disable the automatic trigger today (I may well have missed this) or would you consider it as an enhancement?
- duplicates
-
JENKINS-32396 Option to suppress automatic SCM trigger
-
- Resolved
-
[JENKINS-33909] Prevent automatic trigger of of jobs once scan has created them
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 169917 ] | New: JNJira + In-Review [ 198729 ] |
I would like to see something like this. We are moving Jenkins instances and every time we add a new GitHub Enterprise organization it kicks off every job. Its make me hurry and stop each one if I can.
Essentially when I add a new github org I should be able to state yes scan for each repo and branch but do not initially kick off a first build. Which means it wont kick off until a webhook, manual start, etc.