CI/CD
DevDynamics tracks builds using post-build metadata provided through the specified curl request.
Firewall Configuration
To enable CI/CD tools(Jenkins) connection to DevDynamics, permit outbound traffic for:
IP Address:
3.131.112.244
Prerequisites
Get your OrgID and API key from https://app.devdynamics.ai/settings/organisation.
The server's IP address, where the agent will be running, must be whitelisted in Jenkins.
API Details
Endpoint:
https://api.devdynamics.ai/api/v1/deployment/{your-devdynamics-orgId}/notify
Method: POST
Important Note: Request must be called in the POST-BUILD STEP of your Jenkins pipeline
Payload Fields Explanation
id
: Execution Id (mandatory)name
: Name of the pipeline/job (mandatory)pipelineId: Pipeline/Job (if you don't have id , send name) (mandatory)
timeStamp
: Timestamp of the event (mandatory)startedAt
: Start Timestamp when the build started (mandatory)completedAt
: End Timestamp when the build completed (mandatory)htmlUrl
: URL to the build or deployment detailssource
: Source of the deployment (example "Jenkins")status
: Deployment status (e.g., "success", "failed") (mandatory)repository
: Name of the repository (mandatory)artifact
: Version or identifier of the deployed artifactenvironment
: Deployment environment (e.g., "production") (mandatory in case of cd event)commit
: Latest commit hash (mandatory)additionalInfo
: Optional additional metadata (e.g., a tag)stages
: Array of deployment stages with their detailstags
: (Optional)
Headers
X-api-key: YOUR_API_KEY get it from https://app.devdynamics.ai/settings/organisation
X-delivery: Unique Execution Id
X-event: cd or ci. cd for deployment, ci for build
Samples
Note: The request must be called in the POST-BUILD STEP of your Jenkins pipeline to track deployment events accurately.
Support
For any questions, contact: support@devdynamics.ai
Last updated