Jenkins Plugin → Use Cases for the Jenkins Plugin
Before you use the Jenkins plugin, you must ensure Jenkins is configured to match the way you configured the Jenkins plugin to be used with it.
The plugin interacts with Jenkins based on whether an ExecutionID Job Parameter is being passed and generated and whether Polling and Wait Complete are set to true or false. Use this topic along with Jenkins Plugin Configuration Details and Configuration for Each Use Case to complete the configuration.
The following table gives the fields that control the use cases for the Jenkins plugin.
| Use Case
Number |
ExecutionID Job
Parameter |
Polling | Wait
Complete |
Use Case |
|---|---|---|---|---|
| 1 | Blank | false | false | Start the Jenkins job and forget |
| 2 | Blank | false | true | Not a valid configuration |
| 3 | Blank | true | false | Use the URL and complete from the provider |
| 4 | Blank | true | true | Use the URL as execution ID and complete by using the post Groovy script |
| 5 | RLC_Execution_Id | false | false | Start the Jenkins job and forget |
| 6 | RLC_Execution_Id | false | true | Start by using the pre Groovy script and complete by using the post Groovy script |
| 7 | RLC_Execution_Id | true | false | Wait for the URL and complete from the provider |
| 8 | RLC_Execution_Id | true | true | Wait for the URL and complete by using the post Groovy script |
Copyright © 2012–2016 Serena Software, Inc. All rights reserved.