5 ms·

It's more than just a bad VCS. It's a bad bug tracker, a bad build system and a bad workflow system as well. But yeah, if I wanted a set of three letters than

by moomin 9y ago

It's more than just a bad VCS. It's a bad bug tracker, a bad build system and a bad workflow system as well. But yeah, if I wanted a set of three letters than suggested quality and reliability, TFS would be near the bottom of my list.

pjmlp 9y ago
Actually I am yet to find a CI system that allows the TFS workflow of preventing checkins if the unit tests fail. All the other ones I know require creating scripts that will manage branches and merges into the main branch. On TFS I select a check box and go off doing something else.
- flukus 9y ago
  The more you discourage checking in the harder merging becomes.
  - pjmlp 9y ago
    In some type of enterprise projects I am quite glad that merge never takes place. I don't want to have a CI build that is green only a few days when all planets are aligned.
    - flukus 9y ago
      > In some type of enterprise projects I am quite glad that merge never takes place. Surprise! Now you have 2 versions of an app to support, with twice the resource requirements.
      - pjmlp 9y ago
        No I don't. I and everyone else on the team enjoys the fact that broken code produced by offshore developers that should have been fired in first place, never touches the official development repository. Those developers will eventually produce something that passes the unit tests and gets merged, instead of borking the build for weeks. Should the process done in another form with code reviews and such, yes but that isn't how many enterprise projects are managed. Note that I am only referring to those that can't learn to code even if we ELI5 them. There are others on the offshore teams that are highly skilled, but like us onsite, cannot do anything to change the rules of the game.
- moomin 9y ago
  This thread has got quite long but no-one's mentioned the fact you can achieve the same thing with triggered merges: https://blog.jetbrains.com/teamcity/2013/10/automatic-merge/ https://blog.jetbrains.com/teamcity/2013/10/automatic-merge/
  - pjmlp 9y ago
    Thanks for sharing, I wasn't aware of it.

by moomin 9y ago

pjmlp 9y ago

Actually I am yet to find a CI system that allows the TFS workflow of preventing checkins if the unit tests fail. All the other ones I know require creating scripts that will manage branches and merges into the main branch. On TFS I select a check box and go off doing something else.

flukus 9y ago
The more you discourage checking in the harder merging becomes.
- pjmlp 9y ago
  In some type of enterprise projects I am quite glad that merge never takes place. I don't want to have a CI build that is green only a few days when all planets are aligned.
  - flukus 9y ago
    > In some type of enterprise projects I am quite glad that merge never takes place. Surprise! Now you have 2 versions of an app to support, with twice the resource requirements.
    - pjmlp 9y ago
      No I don't. I and everyone else on the team enjoys the fact that broken code produced by offshore developers that should have been fired in first place, never touches the official development repository. Those developers will eventually produce something that passes the unit tests and gets merged, instead of borking the build for weeks. Should the process done in another form with code reviews and such, yes but that isn't how many enterprise projects are managed. Note that I am only referring to those that can't learn to code even if we ELI5 them. There are others on the offshore teams that are highly skilled, but like us onsite, cannot do anything to change the rules of the game.
moomin 9y ago
This thread has got quite long but no-one's mentioned the fact you can achieve the same thing with triggered merges: https://blog.jetbrains.com/teamcity/2013/10/automatic-merge/ https://blog.jetbrains.com/teamcity/2013/10/automatic-merge/
- pjmlp 9y ago
  Thanks for sharing, I wasn't aware of it.