After a Deployment, we usually click on "Approved" or "Broken" button on the Release to mark success / failure for the deployment. However, sometimes, I notice that the Flagged value in the Release History will be changed into INCOMPLETE after a few days.
Why is this value changed to INCOMPLETE? What are the possible reasons?
Thank you @rsperafico. I think it must be the case when artifact(s) of Deployment Version gets removed. Is there any setting to change this behavior of overwriting the status?
Hello @phanthucanh,
I am afraid there is no setting to change this behaviour, however, you could make use of Bamboo's REST API to update the status:
https://docs.atlassian.com/atlassian-bamboo/REST/6.3.0/#d2e3091
# replace {username} to authenticate against Bamboo.
Username provided must have permissions over deployment
# replace {bamboo_base_url} e.g. http://localhost:8085
# replace {deploymentVersionId}
# replace {newStatus} e.g. UNKNOWN, APPROVED, BROKEN, INCOMPLETE
curl -k -u {username} -p \
-X POST {bamboo_base_url}/deploy/version/{deploymentVersionId}/status/{newStatus}
Kind regards,
Rafael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @phanthucanh,
...in the Release History will be changed into INCOMPLETE after a few days.
Could you please confirm whether the deployment was ever released? And do you have Bamboo Expiry set up? If artifact(s) of Deployment Version gets removed, release gets marked as incomplete.
Kind regards,
Rafael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.