3 ms·
Strange example. We use Jenkins at work with somewhere around 100 workers. I can't remember the last time Jenkins itself failed. Nodes in a bade state because t
by patrick451 5y ago
Strange example. We use Jenkins at work with somewhere around 100 workers. I can't remember the last time Jenkins itself failed. Nodes in a bade state because they are too much like pets? Sure. But the Jenkins master is rock solid.
- trasz 5y agoWith enough thrust pigs will fly - sure, you can work around Jenkins' deficiencies, but in general it's optimized for shooting yourself in the foot. Everything it does can be done with a small shell script, which will be easier to understand, maintain, and fix if it ever goes wrong. And if you use Jenkins in a maintainable way, you're writing scripts anyway - except you have to use a made-up language instead of something standard.
- patrick451 5y agoSome examples for this hyperbole would be helpful. We aren't doing anything in particular to work around whatever deficiencies you're talking about. It just works. Maybe our definition of a "small" shell script are different, but to me the following very useful features sounds like a monstrously complex shell script: - Load balance builds over scores of distributed build servers - Present a UI where I can glance over recent CI results. - Expose REST api that my ETL pipeline can query. - Let devs manually run integration tests against their branch without providing them ssh access