Giter Site home page Giter Site logo

Comments (4)

adamralph avatar adamralph commented on May 22, 2024

No need to be alarmed by all the current build failures. The build configs have now been changed to pick up all branches and pull requests and they picked up all the old ones and tried to run concurrently. I've throttled each build config down to 1 simultaneous build and I'm now going through the 'pending' changes and letting TC build from history. It will take a while to catch up but everything should be green a little later which needs to be.

from fakeiteasy.

adamralph avatar adamralph commented on May 22, 2024

FYI I initially set up the pull request builds with a display pattern of pull/*/head pull/*/merge but this was too long and was being truncated in the TC UI. I've since changed it to */head and */merge.

Unfortunately TC still sees them as two different things so some PR's have two lines in the display. However, as these PR's age, they will gradually fall away from the display as TC will deem them to be 'inactive'.

from fakeiteasy.

adamralph avatar adamralph commented on May 22, 2024

I decided to switch off the building of the head of the pull request. The problem here was that if the building of the PR head was successful, the 'Report change status to GitHub' build feature would mark the PR as safe to merge which clearly may not be the case.

So now we are only building the PR merge, which is the branch that GitHub creates when does a test merge of the PR to determine whether or not it can mark the PR as being able to automatically merge. Ultimately this is what we want as an indicator as to whether the PR can be safely merged as well.

Also, I had to turn off the 'Report change status to GitHub' build feature for now because the 3 different build configs interfere with each other, i.e. the build might pass on one config and fail on another and then it's a case of most recent wins with the status update on the pull request. We should be able to switch this build feature back on as part of #2 - I've updated that issue to reflect this. Until then, we will have to navigate to the build server to see the outcome of the PR build before merging.

from fakeiteasy.

adamralph avatar adamralph commented on May 22, 2024

Marvel at the wonderful output ;-) http://teamcity.codebetter.com/project.html?projectId=project152

from fakeiteasy.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.