|
I'm trying to switch my team to Atlassian Stash (enterprise Bitbucket), since we already license other Atlassian products like JIRA and Confluence. We currently use SVN and everyone commits directly to trunk. It feels like going back in time to the Stone Age. I keep asking my supervisor how I can send him a pull request so he can review my code before it goes into the mainline branch. He has no idea. However, he does want to start using SonarQube for code review. Baby steps, he tells me. I'm hoping that perhaps we can use some of the tips here: http://blogs.atlassian.com/2013/01/atlassian-svn-to-git-migration-technical-side/ I feel like proper code quality and CI is an insurmountable task until we switch to a pull request based workflow.
|
#
¿
Jun 2, 2015 23:20
|
|
|
|
| # ¿ Apr 30, 2024 22:33 |
|
|
If anything, DevOps could be someone's part-time role reviewing Pull Requests to your infrastructure automation scripts. Everyone should be encouraged to contribute. If the deploy fails due to someone loving up the Ansible playbook, blue/green rollout and integration tests should cover it.
|
|
#
¿
Jan 14, 2016 03:39
|
|
|
Pollyanna posted:Try working in finance and insurance. Heroku, JIRA, and BitBucket were all banned until recently. At my job Heroku is still banned. JIRA is hosted on premise so it's fine. BitBucket is marketed as a fork called Atlassian Stash if it's hosted on premise.
|
|
#
¿
Feb 1, 2016 00:40
|
|