All Classes and Interfaces

Class
Description
For builds/deployments rejected from the API, it includes an appropriate message on why it was rejected (eg.
 
Combination of Client ID and Secret generated by creating an OAuth app from Jira admin page
The entities to associate the Deployment information with.
 
Available association types
This class should listen to the events from Jenkins pipeline and send 2 builds: one in "IN_PROGRESS" state and the other one in the "final" or "resulting" state.
 
 
Extract SCM revision which triggered the build.
When a build is submitted via the API, the response includes the list of accepted builds (which will appear in the respective Jira issue view), rejected builds (with appropriated reason on why it was not accepted), unknown issue keys (which are not present in the configured Jira Cloud site)
Unique combination of builds (i.e pipeline ID and build number) that is used in representing both accepted and rejected builds
 
This represents the payload for the API request to submit list of builds
 
Parses the change log from the current build and extracts the issue keys from the commit messages.
Resolves the Jira site URL provided by the Jenkins user into Cloud ID.
This represents a command record in the request
Commit represents the changes contained in the build
Combines multiple issue key extractors.
 
 
 
A SaveableListener implementation that listens for changes in saveable objects, specifically instances of com.atlassian.jira.cloud.jenkins.config.JiraCloudPluginConfig.
 
When a deployment is submitted via the API, the response includes the list of accepted deployments (which will appear in the respective Jira issue view), rejected deployments (with appropriated reason on why it was not accepted), unknown associations (which are not present in the configured Jira Cloud site)
Unique combination of deployments (i.e pipeline ID, environment ID and deploymentSequenceNumber) that is used in representing both accepted and rejected deployments
 
This represents the payload for the API request to submit list of deployments
 
 
Environment to which the current deployment is targeted.
 
 
 
 
 
 
 
 
 
 
 
 
 
OkHttpClient with appropriate default timeouts
 
 
Represents an issue key from Jira (eg.
 
Extracts issue keys (eg.
 
 
 
A request that we can send to the Jenkins app to check the connection.
A request that we can send to the Jenkins app to check the connection.
 
 
 
 
 
Common HTTP client to talk to Jira Build and Deployment APIs in Jira
Includes the necessary info representing a build that has completed.
 
 
 
 
Implementation of JiraBuildInfoSender to send build updates to Jira by building the payload, generating the access token, sending the request and parsing the response.
Implementation of the "checkGatingStatus" step that can be used in Jenkinsfile to check gating status managed by Jira Service Desk.
 
 
Global configuration to store all Jira Software Cloud site settings (site name and the corresponding credentials).
This class encapsulates Jira Cloud site configuration to be used to send build information to Jira.
 
 
 
Includes the necessary info representing a deployment that has completed.
 
 
 
 
Implementation of JiraDeploymentInfoSender to send build updates to Jira by building the payload, generating the access token, sending the request and parsing the response.
 
 
 
 
Implementation of the "jiraSendBuildInfo" step that can be used in Jenkinsfile to send build updates to a Jira site.
 
 
Implementation of the "jiraSendDeploymentInfo" step that can be used in Jenkinsfile to send deployment updates to a Jira site.
 
 
 
 
 
 
 
Generated localization support class.
 
 
ObjectMapper with a configuration not to fail on unknown properties.
 
 
The pipeline to which the deployment belongs to.
 
A logger that logs output into the Jenkins pipeline logs.
 
 
 
Represents Jira update result, which can be either a successful response or an error message.
Metadata properties that can be attached to a build or a deployment when submitting to Jira.
This object represents provider metadata, i.e.
The reference to the repository the commits are contained
Represents the commit and the repository it is present in.
Any builds that were rejected when submitting to the API.
Any deployments that were rejected when submitting to the API.
 
 
 
 
"Single" means that a single instance of a class that implements this interface will be handling events that belong only to a single pipeline.
 
 
 
 
 
Response object when resolving Jira site URL to cloud ID
Represents the test info.
 
Utility class for handling XML-related operations such as parsing XML files and extracting values from XML elements.