This API endpoint deploys a specific release version of a given project to specified environments or using specific lifecycle phase. If no release version is provided then Jaws Deploy will pick an existing release with the highest version number (according to SemVer 2.0 rules). In such case the specified project needs to have at least one release. Otherwise an error will occur.
This endpoint is especially useful in CI/CD scenarios, where the build server does not track Jaws Deploy release identifiers. In such case it is enough to provide only project ID and the environment name to promote the latest release.
Similar to Release - Deploy response contains unique identifier of the created deployment entity.
Release version comparison and sorting is based on SemVer 2.0. More information: Semantic Versioning 2.0.0 | Semantic Versioning (semver.org)
environments must be provided.environments instead.phaseName must be provided.POST /release/promote
{
"projectId": "139118d5-bcac-4c92-b1d1-da755d7e78ff",
"version": "1.0.5-rc2",
"phaseName": "First phase",
"environmentName": "Staging",
"environments": ["Staging", "UAT"],
"redownloadPackages": false,
"deploymentDateUnixMillis": 1744308919000,
"excludeStepNames": ["step A", "step C"]
}
{
"deploymentIds": [
"603af550-e241-4a3f-9545-5971c2f455ff",
"603af550-e241-4a3f-9545-5971c2f45500"
]
}