Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bamboo services and agents should not restart while building #26

Open
wolf31o2 opened this issue Jul 7, 2015 · 3 comments
Open

Bamboo services and agents should not restart while building #26

wolf31o2 opened this issue Jul 7, 2015 · 3 comments

Comments

@wolf31o2
Copy link
Contributor

wolf31o2 commented Jul 7, 2015

Changing a capability on the agent or a configuration on the server causes a service restart. For agents, you lose the running job. For the server, you lose all running jobs.

Agent 'bamboo-agent07.prod.continuuity.net' went offline while building CDAP-DUT2169-JOB1-1. The results of that build will not be available.

😢

@ramonskie
Copy link
Collaborator

yes this is something atlassian should fix
the best option is to file a bug at atlassian

@wolf31o2
Copy link
Contributor Author

wolf31o2 commented Jul 9, 2015

Atlassian says we should shut down instances from the API, which will stop them after the current job is completed. There's not really a way to tell an agent to restart, but the restarts the cookbook's triggering on configuration change is probably not the way to go. I'll see what I can come up with to resolve this. It's bitten us several times, unfortunately.

@ramonskie
Copy link
Collaborator

i will also check if i can find a solution
and maby disable the restart on changes for the capabilities file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants