release management - thoughtworks go vs atlassian bamboo -
does have comments on 1 vs other.
we're looking @ trying automate our release process dev test uat production, including running unit tests, having code reviews , enforcing permissions on allowed push builds uat production.
disclaimer: product manager of bamboo
@bernard: provide more details around process?
- are uat tests manual tests?
- what pushing production mean in case?
- do expect single build result @ end of deployment?
bamboo 2.7 our first release allows divide build different stages , execute jobs within stages in parallel. can improve overall turnaround time of builds. working on artifact passing, allow pass build artifacts between different stages. again, reduce overall build time , important step towards continuous deployment process.
unfortunately not have "out of box" way enforce permissions on parts of build. again, there ways work around plugins , setting build in way. it's hard provide suggestions without knowing process in more details. if willing share details of process us, love speak in person (jens @ atlassian dot com).
@jgritty: problems pointing out partially know issues our perforce integration , partially seem unknown bugs. please feel free create support request on support.@atlassian.com or raise bug report on jira.atlassian.com.
since perforce less commonly used (compared cvs & svn) amongst bamboo users, less feedback , hear less existing issues. please raise problems directly , our best fix them in 1 of our upcoming releases.
cheers,
jens schumacher
Comments
Post a Comment