The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bamboo plan continuable state

pBogey
December 16, 2024

I am wondering what does the ”continuable” state means in the response from the result REST API endpoint.

 

In the documentation for another endpoint it says: 

continuable

boolean

 

filter only results that may be continued (stopped on Manual Stage)

 

I have a plan in which I manually stop a job via the queue DEL endpoint and try to retrigger it via the PUT request in the queue endpoint.

 

All works well and state of the plan is continuable: false in normal situation, but once I add a final manual stage after the job that I am stopping, continuable will be set as true and the PUT rest api request doesn't succeed anymore.

 

I will get a message like:

{"message":"Nothing to run\nPlan 'PROJECT-PLAN' did not start","status-code":400}

But the job can still be retriggered via the GUI.

 

Is this a bug or some kind of hidden behaviour? I was expecting that, if the job can be restarted via GUI, it could also be done via rest api.

 

EDIT:

I have changed my final manual stage and disabled the FINAL attribute and now the stopped job can be retriggered, but continuable state is still false, when the job is stopped, so I don't think it has anything to do with it. Still I don't get why I cannot restart the job when the next stage is FINAL.

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
pBogey
April 2, 2025

Update: the issue has been fixed in https://jira.atlassian.com/browse/BAM-25979

TAGS
AUG Leaders

Atlassian Community Events