All geek questions in one place

Any best practices for integrated use of svn, Jira and Bamboo?

I am currently focused on setting up a software configuration management process using svn, Jira, and Bamboo. Unfortunately, I cannot find any specific or standard practice using the specified tools. I am definitely looking for a set of best practices, including:

  • Best branching method
  • The best examples of conservation of development lines
  • Best ways to use jira problems with svn commits
  • ...

Good configuration management practice is one that Microsoft has proposed for its TFS solution. Any known set of best practices for these tools?

+6
source share
1 answer

I recommend that you read the Subversion online book, which contains a wealth of material about best practices for using Subversion.

I also recommend the book Practice . Perforce is another version control system, but it is very similar to Subversion, and the book has great ideas on how to branch and code. This is all very applicable to Subversion.

As for Jira, the best advice is to keep it simple: indeed, very simple. Jira works best for developers, not for a general corporate organization. Workflows should be simple.

There is no good book on the Jira, but if you have never used the Jira, please understand that certain fields have very special meanings, and you must respect their meaning:

  • Resolution is used to designate a problem as open or closed (rather than state). If the problem has a solution, it closes. Period. This is used for many built-in reports, so they should be respected.
  • The heart of every Jira project is its version number, another special concept. Defects are tracked by the version they report and the version in which they are fixed.
  • The status field cannot be changed, except as a transition to another state. Therefore, I recommend that you have a reverse flow that can reset the problem in the previous state. Someone is going to shift the wrong problem, and you have to fix it.
  • Use a continuous integration system like Jenkins or Bamboo. Jenkins and Bamboo blend perfectly with Gira. In fact, I will argue that this is a much more important integration than the direct integration of Subversion to Jira. Almost no one ever bothered to search for source code directly from Jira, but QA people loved the fact that they could look at the Jira problem and see which one was fixed.
  • If you are going to look at Atlassian products, think about Fisheye while you are on it. It provides a way to view code over the Internet and display differences. It goes well with Bamboo and Jenkins. This is where developers usually look at the difference in code, etc. A good substitute for Fisheye is Sventon . Jira integrates with Swenton, and Jenkins does too. I don't know if bamboo does.
  • Join the Subversion user mailing list. Discussions there may help. In addition, the people on this list are generally very helpful.
+5
source

Source: https://habr.com/ru/post/895320/

More articles:


All Articles