StiltSoft is the Atlassian Verified vendor that develops TeamCity Integration for JIRA add-on. When you reference config files in plugins in bamboo, you always have to remember the relative path and what was the current working directory again? In Teamcity, you click on the tiny icon next to the config settings and boom: it lists you the latest checked out source tree from your repository.StiltSoft is a small team of Atlassian Experts and avid fans of JIRA and Confluence. I cannot list all the things in the UI that make you feel like: “Oh! That’s handy”. Why did no one thought of it in the first place? “Pick a file”-dialogs It then creates an ssh-agent, which allows you to use ssh in inline scripts. Have you ever had problems accessing your private repos when installing with composer? Have you ever had the need to issue ssh commands in your builds? All the time? Right! A Teamcity build feature allows you to add ssh credentials to your build. Manage an ssh agent directly for your builds So easy, so well thought - I wish only they would provide a vault for them. Then you use the keys everywhere for ssh tasks, scp or rsync. You can upload keys by UI or just copy them into a folder, that you mount to the docker image. It’s so hard to use ssh credentials in bamboo. run phpunit run yarn tests, analyze test reports and cleanup. If only I knew this a few years ago: would have saved me a lot of stress! I use meta runners to bundle the build steps to run my whole test suite. It’s possible to provide parameters to the meta runner. Apply the meta runner to other build configs and the exact same steps will be called everytime the build is run. The meta runner is provided as xml, which you can adjust. You can extract them from one of your build configurations and use it as a collection of build-steps that will be bundled for other build configurations. Teamcity has THE feature for you: it’s called meta runners. Meta Runners (will blow your mind)ĭo you have a LOT of build configurations? They build differently, but you always execute your tests the same way? (for example: yarn run tests). It’s possible to inherit settings and variables from parent projects as well - a killer feature. This organizes your Projects-Dashboard so well. But the project itself could be part of a bigger projects-hierarchy, like: “Projects for customer A”, or “Projects with Symfony backend”. In Teamcity the first citizen is a build configuration. Bamboo’s documentation listed all the variables, but TC’s idea is much better: But they are always so difficult to remember. There are so many variables in each CI-Server, that want to be used. Here’s the list of features that are crushing bamboo for my use case: Auto completion for variables and Configurations Parameters I always thought Teamcity is the underdog in CI and too oldschool, but it wasn’t. You can customize everything and I could not only move all my projects from bamboo to Teamcity but enhance my whole setup. I was a bit skeptical but then sold on the huge number of options for everything. The user interface is a bit oldschool, but it’s PACKED with stuff. The installation was easy to make with docker and everything started to feel very natural. In the end I looked at the licensing for Jetbrains Teamcity and was surprised, that there’s a free tier for small businesses. But they all felt like I’m missing a whole piece of workflow I had with bamboo. I started to evaluate the known SaaS like Circle and Semaphore and whatnot. Jenkins because of the interface (even with blue ocean), GOCD because of missing integrations and inflexibility. I started with open source, but Jenkins and GOCD we’re a serious nightmare for me. I couldn’t afford another build agent, I couldn’t afford bamboo in the first place, because I’m only a one man developer team. I used way to many inline script tasks, because there weren’t enough plugins for my use cases. I wasn’t satisfied with the feature development on bamboo. When Atlassian raised their prices for Bamboo as well I decided to evaluate a new CI-Solution. I ran a self hosted bamboo for more than 4 years, integrated with Jira and Bitbucket server and was satisfied, not happy. I take testing and continuous deployment very seriously and have strong demands to my build server. I used Jenkins, Bamboo, Travis, tried Circle, Jenkins, GOCD, Semaphore and BuildBot. I’ve been using Continuous Integration Servers for over a decade. Atlassian Bamboo vs Jetbrains Teamcity - there’s a clear winner
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |