Re:Advice to my younger self: become allergic to the churn
by danesparza on Thursday August 08, 2019 @09:15AM
(#20644182)
The problem isn't the libraries. The problem is you don't have CI (with a dashboard your team is paying attention to). Check-in -> automatic build -> automatic unit test execution -> signals if the build is ready
[ Parent
| on HN ]
Re:Advice to my younger self: become allergic to the churn
by tonyedgecombe on Thursday August 08, 2019 @10:39AM
(#20644998)
The problem is you don't have CI
Having CI won't stop the developer of the dependency changing the interface.
Re:Advice to my younger self: become allergic to the churn
by mffnbs on Thursday August 08, 2019 @03:10PM
(#20647568)
Why are developers mindlessly upgrading major versions of dependencies and expecting everything to be okay?
Re:Advice to my younger self: become allergic to the churn
by Ididntdothis on Thursday August 08, 2019 @09:31AM
(#20644349)
Until your CI pipeline causes churn because something doesn’t work anymore....
Re:Advice to my younger self: become allergic to the churn
by umvi on Thursday August 08, 2019 @09:42AM
(#20644447)
We use GitLab CI, and it's been working maintenance free for 3 years now. We configured the test runners in 2016, and haven't touched them since and they have never randomly broken - even across GitLab updates (of course, YMMV depending on if you like to be on the bleeding edge all the time; we are always 1 cycle behind the bleeding edge).
Re:Advice to my younger self: become allergic to the churn
by pritianka on Thursday August 08, 2019 @12:57PM
(#20646222)
What an awesome compliment for our team. Thank you!
Re:Advice to my younger self: become allergic to the churn
by danesparza on Thursday August 08, 2019 @12:57PM
(#20646220)
Your CI pipeline should be simple, relatively unchanging and therefore trusted. When shit breaks (and it will) you should get a signal much earlier. This signal should strongly relate to your most recent changes -- and your changes should be small because you commit early and often, right?
Re:Advice to my younger self: become allergic to the churn
by xemdetia on Thursday August 08, 2019 @01:31PM
(#20646560)
Some of us deal with the fact that the people maintaining the CI solution keep breaking our pipelines without any code changes in of our scope of responsibility. This becomes the churn as you push empty commits trying to troubleshoot why your builds don't work and it takes >1 day to get things working again. Most hosted CI solutions are entirely inappropriate for some organization's business goals and requirements, so you end up dealing with it being a B or C tier service in an organization that is changing.
I would suggest that there are definitely some organizations where you can't trust the pipeline to work reliably, and the cost of figuring out what went wrong becomes the churn.