![]() ![]() Plugin install still triggers server restart, even if no plugins were updated/installed.You didn’t want to know when that error happened. Defaults to port 8080 … way too common a port for DEV’s.No PreTested Commit – a TC standard that’s integrated with Intellij/Eclipse – Jenkins progress.No Password masking by default, you’ll need the masking plugin.NO SECURITY by default? Why? TC secures out of the box.Some other things that Jenkins could improve: This is sad given that the configurations TC has out of the box could have skipped $10K in developer efforts over the last two years. Or, there will be three plugins to do almost the same task, and most of it might work, but check the GitHub page and recompile if you want that functionality. A non-code reviewed plugin that does part of what you want and was last updated 19 months ago and a few major releases hence. They will counter “but there’s a plugin for that!” Perhaps there is. But stand back if you ask a Jenkins fan about this. ![]() Everything folks had wasted their time on via various scripts and manual efforts was a standard, default, out of the box feature in TeamCity. And throw in a bi-weekly inopportune crash for good measure. Hacks and hacks and duct tape scripts to make the build chains we used. For example, hand written jobs to do nothing but free up space from other jobs. I had inherited a mature Jenkins installation where all quotidian tasks were either manual or cumbersome. My first production encounter with Jenkins was a comedy of errors. But that would completely ignore the fact that JetBrains gives away everything for FREE to open source projects. CloudBees, BuildHive, Travis or your own Jenkins Instance? Fatuously such groups write off TeamCity since it would cost cheddar they don’t have. And I frequently spar over what CI tool to use. We’re an OSS Project, We Can’t Afford Paid Anything Why do you use those rather than the FOSS solution? Perhaps it’s for the quality of the tool or the paid support behind it. Remember, many of us work for profit. Anyone bought Visual Studio lately? Anyone use the many $5K/seat tools out there? Anyone…use Windows (Debian lover myself) ? They all cost a ton more than Jenkins. And that you’re only out $100/agent thereafter and $1000 for the CI server. They’ll not mention you can use the TeamCity CI server and three (3) build agents for FREE. The Jenkins fan will note that Jenkins is free, but TeamCity costs money. Just because other options are Open Source doesn’t make the whole tool chain better in practice. Why does a company write code with 23 FOSS tools/languages on closed source Windows desktops? Probably because it works for them and that special accounting application or antiquated, but stable, engineering software that’s core to the business. Inevitably, people use the best tool for the job at hand. Much like one can imagine RMS foregoing a life saving treatment if the medical apparatus didn’t run open source code he’d compiled himself.īe careful though as there are few absolute FOSS purists in practice. If there is an open source solution, perhaps buggy or poorly maintained, they feel compelled to use it. Let’s knock the legs from under this myth. What’s in a UI? Not much if you’re technical, but geeze, Jenkins still has the aura of an app knocked together during an all night hackathon in 1997. Recently, I downloaded and installed it again and was shocked to see that little appears to have changed in so many years. I started using Jenkins when it was called Hudson, before the Oracle naming spat. Let’s dispel the myth about Jenkins being the gold standard continuous integration tool. I’m sorry, TeamCity is much better. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |