3 ms·
> Quite false. How do you expect developers to take you seriously when you essentially say "you can't properly do CI/CD with your current approach"? I sure am e
by SideburnsOfDoom 10y ago
> Quite false. How do you expect developers to take you seriously when you essentially say "you can't properly do CI/CD with your current approach"? I sure am enjoying CI/CD right now.
Do you not understand that the "Integration" in continuous integration literally means "merge to master". Please read the first paragraph https://en.wikipedia.org/wiki/Continuous_integration https://en.wikipedia.org/wiki/Continuous_integration
What you do might work well for you, but if you build long-lived branches then it's not CI. Let's not call it something that it's not: words have meaning if we are to communicate, and we're not doing post-truth software development.
- vemv 10y agoThese days CI vastly means test-on-commit over anything else. Please google "CI platform" and see how Codeship, Circle, Travis etc self-advertise as CI platforms. None of them require TBD (not even nearly).
- SideburnsOfDoom 10y ago> These days CI vastly means test-on-commit over anything else. Quite false. That is a miscommunication. I know what those "CI servers" do, I have worked with a few of them them daily for years and had this exact same issue come up. These tools enable the continuous integration workflow, and lately they also enable other workflows such as "build and test the branches but don't integrate". If that's what you do fine, but let's not confuse it with something that it is not. Words have meaning. CI is not a tool, it's in how you use the tools. But if you still think that wikipedia is wrong, I suggest that you edit it. Good luck.
- paul_h 10y agoQuite correct. Snap-CI is configurable to test every active branch, on first commit/push - https://trunkbaseddevelopment.com/game-changers/#snap-ci-s-per-commit-speculative-mergability-verification-2013 https://trunkbaseddevelopment.com/game-changers/#snap-ci-s-p... Of course doing that will expose problems that lead the dev team to reconsider Trunk Based Development.