<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>garenp</author><text>Of the CI tools I&amp;#x27;ve used (most of them) TeamCity was my personal favorite--but the advantage of Jenkins is that it&amp;#x27;s very widely used, has a greater breadth of capabilities due to the huge plethora of plugins, and a huge amount of support info readily available online.  Some plugins are even maintained by an external vendor that produces the tool you&amp;#x27;re trying to integrate with and are either better supported or the first to get timely updates.&lt;p&gt;Bamboo on the other hand is IMO the worst of the commercial CI tools by far and where I work has gone down for us the most.  Atlassian itself doesn&amp;#x27;t appear to be investing in it much anymore judging by the slow pace of development in recent years and at their most recent conference, you can hardly find it mentioned or see much presence for it anywhere.&lt;p&gt;In all the CI systems I&amp;#x27;ve used though, there has not been one that I haven&amp;#x27;t encountered some major difficulties with.&lt;p&gt;Beyond that, anything to do with build automation for a large number of users always quickly becomes a support &amp;amp; maintenance quagmire.  Users frequently want to install a new (barely maintained) plugin to solve a problem they have, complex interactions lead to difficult to understand failure modes that require time consuming investigations (&amp;quot;your CI tool is the problem and broke my build&amp;quot; ... &amp;quot;No, your build is broken&amp;quot; ...).</text><parent_chain><item><author>user5994461</author><text>TeamCity from JetBrains is the same thing as jenkins, except the core features are working core features instead of broken plugins. It&amp;#x27;s paid software though, you get what you pay for. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;teamcity&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;teamcity&amp;#x2F;&lt;/a&gt;&lt;p&gt;On the other hand there is Bamboo from Atlassian. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.atlassian.com&amp;#x2F;software&amp;#x2F;bamboo&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.atlassian.com&amp;#x2F;software&amp;#x2F;bamboo&lt;/a&gt;&lt;p&gt;I really don&amp;#x27;t understand this mentality of there is no better tools when there are better tools than jenkins and they&amp;#x27;ve been around for a while.</text></item><item><author>FrenchyJiby</author><text>I sincerely wish I could move away from Jenkins for the reasons stated in TFA (GUI-oriented, slow, hard to backup&amp;#x2F;config, test-in-production mentality and boundless plugins) but I&amp;#x27;ve never found something that fits the bill.&lt;p&gt;The much-touted repo integrations (travis, circle...) all have an exclusive focus on build-test-deploy CI of single repos.&lt;p&gt;But when you have many similar repos (modules) with similar build steps you want to manage, and want to have a couple of pipelines around those, and manage the odd Windows build target, these just give up (it&amp;#x27;s docker or bust).
Sadly, only Jenkins is generic enough, much as it pains me to admit.&lt;p&gt;Anyone got a sane alternative to jenkins for us poor souls?</text></item></parent_chain></comment><story><title>Jenkins Is Getting Old</title><url>https://itnext.io/jenkins-is-getting-old-2c98b3422f79</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>AnthonBerg</author><text>Hear hear.&lt;p&gt;And actually, you can get quite far with the free TeamCity license of three build agents and 100 build configs. I’m also fairly sure that Jetbrains would take kindly to license requests from open-source projects and academia.</text><parent_chain><item><author>user5994461</author><text>TeamCity from JetBrains is the same thing as jenkins, except the core features are working core features instead of broken plugins. It&amp;#x27;s paid software though, you get what you pay for. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;teamcity&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.jetbrains.com&amp;#x2F;teamcity&amp;#x2F;&lt;/a&gt;&lt;p&gt;On the other hand there is Bamboo from Atlassian. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.atlassian.com&amp;#x2F;software&amp;#x2F;bamboo&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.atlassian.com&amp;#x2F;software&amp;#x2F;bamboo&lt;/a&gt;&lt;p&gt;I really don&amp;#x27;t understand this mentality of there is no better tools when there are better tools than jenkins and they&amp;#x27;ve been around for a while.</text></item><item><author>FrenchyJiby</author><text>I sincerely wish I could move away from Jenkins for the reasons stated in TFA (GUI-oriented, slow, hard to backup&amp;#x2F;config, test-in-production mentality and boundless plugins) but I&amp;#x27;ve never found something that fits the bill.&lt;p&gt;The much-touted repo integrations (travis, circle...) all have an exclusive focus on build-test-deploy CI of single repos.&lt;p&gt;But when you have many similar repos (modules) with similar build steps you want to manage, and want to have a couple of pipelines around those, and manage the odd Windows build target, these just give up (it&amp;#x27;s docker or bust).
Sadly, only Jenkins is generic enough, much as it pains me to admit.&lt;p&gt;Anyone got a sane alternative to jenkins for us poor souls?</text></item></parent_chain></comment><story><title>Jenkins Is Getting Old</title><url>https://itnext.io/jenkins-is-getting-old-2c98b3422f79</url></story>