We've got a very small dev team with tight timetables and would really like a lot of the benefits that crucible has to offer for code review (inline comments/response capability). However we can't be hamstrung by sending out commits to our repository and needing to wait on a code review/sign off before the commits are in the repo.
My question is, is it possible to send the commits to the repository and then use the reviewing functionality after we've cut the latest deployment from our developers?
Thanks in advance for any answers!
FishEYe/Crucible connect to an existing repository in a read-only way. It does not prevent a user from committing or restrict visibility of what has been committed - it instead provides review functionality after-the-fact, along with tools to audit what has and hasn't been through a review.
PS. Incidentallly, if you DID want to hold up commits by a code review process, you could look at pull requests in Stash. Stash can block pushes to the master branch except by certain users, and can require code to be merged by a reviewed pull request.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs