CI/CD integration

Application deployment isn’t usually triggered by human interaction. Typically it is executed automatically as part of a CI/CD pipeline. Jaws Deploy facilitates integration into existing CI/CD environments by exposing a simple HTTP API.

Note: JawsDeploy API contains minimal amount of endpoints which only cover control over deployments. More endpoints related to infrastructure will be implemented gradually over time as we expand our platform.

You can call API endpoints directly from your build pipeline using your preferred language and coding style. Please refer to our API Reference for more details.

If your builds are based on PowerShell or your CI platform supports PowerShell it is recommended to take advantage of our PowerShell SDK which is a very lightweight, zero-dependency wrapper over Jaws Deploy Rest API. You can find it in our GitHub repository: JawsDeploy/powershell-sdk (github.com)

‍Here is a short snippet which deploys a specific project to Staging environment using service-account authentication:

$env:JAWS_API_LOGIN = "service_account_id"
$env:JAWS_API_PASSWORD = "SecretPa55w0rd"
Import-Module -Name JawsDeploySdk.psm1
$projectId = "id_of_a_project_to_deploy"
$version = "version_generated_during_the_build" # e.g. "5.27.1-RC2"

$resp = Invoke-ReleaseAndDeployProject -projectId $projectId -version $version -environmentName Staging

Write-Host $resp