How to create a Build?
2017-08-16 09:35:58
  • Visit: 4
  • Join Date: 2017-09-15
  • Last Login: 2017-10-20
How to create a Build?
Last edited by Max on 2017-09-15 13:19:45
2017-09-15 16:01:44
  • Visit: 325
  • Join Date: 2017-05-12
  • Last Login: 2017-11-03

When some functions are completed, it’s time to create a build which is related to software configuration management. It is an optional process, but it is recommended that the teams use build management.

Build is used to identify to the test scope and make it easier for communications between thetesting teams and the development teams, and to solve the problems of build releasing and bug fixing.

Since it is for build management, can ZenTao be used to manage source codes? Sorry, ZenTao cannot be used to manage source code, because it is a professional management and there are available open source software to do it, such as Subversion and Git. You can deploy it according to you own needs. Builds in ZenTao are just records.

1. The build process is, 

  • The Dev teams finish stories or fix bugs
  • A tag is created in Subversion or Git. Take ZenTao tag as an example,

  • When a tag is created, a build can be created by someone who is in charge of releasing in ZenTao.

2. Create a build

Go to  Project- >Build and click  Create.

You need to create a build at first. Once saved, relate it to stories and bugs on the page of build details.

If there is no Relate button on on the detailed page of a build, contact the administrator to assign privileges by going to  Company ->  Groups.

  • Name and ID. Teams should have their own management standards. For example, they can use product name_version number_status (stble, beta) _date to name builds.
  • It can be different for builds due to different development language. Some builds need to be adapted, while other builds only need source code. So you have to fill the SCM  path or the file path for downloading according to the actual situations of your company.
  • In ZenTao, you need to create a build first and then relate it to stories and bugs. Then the build is submitted to be tested after being related , the testing scope will be defined.
  • You can add notes, keynotes and so on to description for testing teams.