How to use continuous integration code

I just started working in a continuous integration environment (TeamCity). I understand the basic idea of ​​not abstracting your code so much that you can never build it to test functionality, etc. However, when deep coding occurs, sometimes it will take me several days to get the embedded code - but in the interim other members of the team may have to see my code.

If I check the code, it breaks the assembly. However, if I do not test it, my team members will not be able to see the latest work. I am wondering how best to deal with this situation.

+3
source share
4 answers

A tool like Collaborator for codes (Google link, smartbear.com is missing ..) will allow your peers to see your code if you do not execute it. Instead, you simply submit it for viewing.

This is a bit of a problem to run .

Alternatively, configure the second branch / fork of your code base so that you can work, your peers can synchronize with it and will not break the build server. When you finish work in your branch, you can combine it with mainline / trunk / whatever.

+4
source

, , , - . , . , , , .

+1

, , - . , , , . , ( , , , ).

/ , .

0

, . -, .

, /. @Dolph Mathews tbh, .

  • "" . branch_team_a, branch_team_b, branch_team_c
  • teamcity . , : Project Main, Project Team A, Project Team B, Project Team C
  • -, , .. TC . IntelliJ VS.

3- . - Developer kick pre-commit . , , branch_team_a - A ; branch_team_A - Main !

, . - , a, b c. . . .

0
source

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


All Articles