There is an awesome TeamCity plugin “ TeamCity.GitHub” written Eugene Petrenko. Please refer to this official post “ Commit Status API” for details.ĭon’t worry! You don’t have to worry about reading the spec or writing any code for it. Github provides us the API for updating the commit status. Would it be even nicer if you can see it on github itself? pretty cool, huh? But of course, you will have to open your TeamCity home page to see the results. You will see the statuses of all branches (including merges) in your TeamCity dashboard. All you need to do is adding two lines as below in “Branch specification” textbox and trigger the “run” button again. In the version control setting of your TeamCity project configuration, you can specify the branch specification. If the answer is yes, here is the solution for you. Do we have to pull the latest, merge the code manually and run the tests to see the result? Would it be nice if your CI can tell you automatically after you’ve done your pull request? The challenge here is that we like to know whether there is any conflict or test failures before we merge the code or not.
So, another guy can review the code and merge it to the stable branch. We keep the master as a stable branch and if we need to work on new feature or bug fixes, we create another branch and push it as a pull request once we’ve done the job. Let’s talk about how we work with github. Merging all pull requests and build all branches
0 kommentar(er)
