You can download Jenkins plugin by using one of the links below depending on the version you want. The top is the most recent available version.
NOTE: When migrating from 9.5.5 or 9.5.6 to version 10.0.1, downgrading will no longer be possible. However, any configuration to your jobs or credentials will be saved from those versions.
NOTE: Minimum Jenkins Version Required is 2.0.
Plugin Installation Steps
You can either watch this narrated video or follow the written instructions below:
1. Go to Manage Jenkins > Plugins
2. Click Advanced Settings and click Choose File, then select the file downloaded from the table on top of this article.
3. Click Deploy
4. Wait for the plugin to finish installing (restart is not always necessary)
5. After the plugin is installed, you need to create a credential. Go to Manage Jenkins > Configure Credentials on the left menu in Jenkins.
6. Hover your mouse over Global, click on the arrow that appears next to it and click Add credentials.
7. From Kind, choose Subject7 API Key Credentials or Subject7 Basic Credentials according to your preference. You can get your API key by hovering over your platform username and clicking Manage API Key.
8. Here are parameters
Platform Host: The URL you are using to access Subject7. For example: https://platform.subject7.com
Username: YOUR-SUBJECT7-USERNAME
Password: YOUR-SUBJECT7-PASSWORD
API Key: YOUR-SUBJECT7-API-KEY
ID: NOT_USED
Description: Optional
9. Once finished, click Create.
How to use Subject7 Jenkins Plugin
1. Subject7 should now appear in the post-build action after creating a new project on Jenkins:
2. After you select it from the menu, you will see the following form:
3. Here are the parameters that you need to fill in once the plugin is added and available as a step in the build process:
Server: This is what you have set up as credentials earlier. Select from the drop-down at this point you should probably have only one item.
Sync Execution: If checked, the build will not complete until all test cases are passed in the provided Execution Set or we reach the timeout parameter. If not checked, the build will continue without waiting for the result.
Report Format: The test execution report returned in Jenkins can be in HTML or in JSON format.
Build Number: Optional parameter. If your Jenkins generates build numbers you can use ${BUILD_NUMBER}. This is just metadata and it will show up in the execution reports and can be used for tracking purposes.
Timeout (s): Number of seconds before the build waits for automation tests to complete. If it reaches more, the build will fail.
Delay (s): Number of seconds to wait before starting to execute the tests. Sometimes, deployments take a little longer because they depend on 3rd party system outside of the build process control, and hence waiting is required.
Callback: In case you want to make a REST call after your build is complete to a third party system.
CallBack Payload: Payload of the REST callback.
Execution Set Name: The name of the set you want to kick-off
Suggested Articles:
Comments
Please sign in to leave a comment.