We've been happy teamcity users for years.
Concourse CI
81–90 of 158 posts
Re: Concourse CI
#82During my Jenkins build I am creating a file with the number of database queries per test, since I am generating the file it can be in any format.
How can I feed this to Jenkins and plot it over time?
Re: Concourse CI
#83Mostly off-topic but I've been looking for more than a CI for some quite time, more on the CD side. How are you guys handling some of these cases? Bonus points for hosted options. - Truly a pipeline based stages. No messing around with git branches/tags for each environment release. - Ability to combine multiple builds together. - Build dependencies. Ability to trigger project-B build when project-A build succeeds. (…
Check out CDDirector[0]. I've been using it to model release pipelines and enjoying it quite a bit. Disclaimer, I work for CA Technologies though not on this product.
Re: Concourse CI
#84I know everyone hates on Jenkins these days, but (at least for the workloads I am building) Concourse feels like a toy. My issues: - everything has to be in a docker container (not all things can run in garden) - Just trying to find logs is a pain, and getting the UI to show a full log output is basically impossible - each install of concourse may need an entirely different version of fly - There was no way of retrig…
Jenkins has some serious problems when you want to work with CD.
Its currently impossible* to use Jenkins in a CD environment where you want to deploy by tagging your git project[1] and allow rollbacks because Jenkins doesn't treat tag's hashes (only the commits the tag points to).
Unfortunately, hack such a fix is not very pleasant either, because Java, and i don't think the Jenkins developers are interested in it either, at least not if just a few people ask for it.
It may look as a silly usecase, but i believe its one that mostly fits when you have a dynamic server farm (hosting on aws with autoscalling, for example) and don't want to auto-deploy on master commit.
[1]https://groups.google.com/d/msg/jenkinsci-users/mYxtDNMz1ZI/...
edit-> * aktually its not impossible, but pretty hacky and ugly, it would be nice to be able to rely on jenkins own tools for this.
Re: Concourse CI
#85I know everyone hates on Jenkins these days, but (at least for the workloads I am building) Concourse feels like a toy. My issues: - everything has to be in a docker container (not all things can run in garden) - Just trying to find logs is a pain, and getting the UI to show a full log output is basically impossible - each install of concourse may need an entirely different version of fly - There was no way of retrig…
Jenkins has some serious problems when you want to work with CD. Its currently impossible* to use Jenkins in a CD environment where you want to deploy by tagging your git project[1] and allow rollbacks because Jenkins doesn't treat tag's hashes (only the commits the tag points to). Unfortunately, hack such a fix is not very pleasant either, because Java, and i don't think the Jenkins developers are interested in it e…
> Jenkins has some serious problems when you want to work with CD.
When you want to work with CD in a particular way.
A simple fix to the above issue would be to have a "production" branch. When you want to do a release, you merge to the production branch. A roll back would just be a revert of the commits since the last merge to production, and could even be tagged.
If you are doing CD by allowing devs to tag random branches, cool, but I would not call it a "failure" on the Jenkins side.
> Unfortunately, hack such a fix is not very pleasant either, because Java, and i don't think the Jenkins developers are interested in it either, at least not if just a few people ask for it.
Its a webhook - that can be in any language, or if you use Git(hub|lab) a config item.
Re: Concourse CI
#86We're using Buddy - https://buddy.works/ - and it seems to be easier, faster and more reliable than most of these other CI solutions so far.
Interesting. How does it compare to other CI software like Jenkins? I'm always a bit skeptic about tools that look nice but turn out to be limited when put to real work.
Re: Concourse CI
#87Earlier quoted context omitted.
Jenkins has some serious problems when you want to work with CD. Its currently impossible* to use Jenkins in a CD environment where you want to deploy by tagging your git project[1] and allow rollbacks because Jenkins doesn't treat tag's hashes (only the commits the tag points to). Unfortunately, hack such a fix is not very pleasant either, because Java, and i don't think the Jenkins developers are interested in it e…
> Jenkins has some serious problems when you want to work with CD. When you want to work with CD in a particular way. A simple fix to the above issue would be to have a "production" branch. When you want to do a release, you merge to the production branch. A roll back would just be a revert of the commits since the last merge to production, and could even be tagged. If you are doing CD by allowing devs to tag random…
>> Jenkins has some serious problems when you want to work with CD.
> When you want to work with CD in a particular way.
> A simple fix to the above issue would be to have a "production" branch. When you want to do a release, you merge to the production branch. A roll back would just be a revert of the commits since the last merge to production, and could even be tagged.
> If you are doing CD by allowing devs to tag random branches, cool, but I would not call it a "failure" on the Jenkins side.
Well, i must confess i agree with you and my first idea was this, i will probably end up pushing for that anyway, but i will have to convince some devs that they should not be afraid of git reverts. When i first mentioned the idea, some devs with deploy rights said they were skeptical about this because they were afraid of having a git revert shitstorm in a SOS situation.
>> Unfortunately, hack such a fix is not very pleasant either, because Java, and i don't think the Jenkins developers are interested in it either, at least not if just a few people ask for it.
> Its a webhook - that can be in any language, or if you use Git(hub|lab) a config item.
Not exactly, on this case github only lets me create webhooks with 'create' action, which is trigerred "Any time a Branch or Tag is created.", so new branches would trigger deploys.
Re: Concourse CI
#88Earlier quoted context omitted.
> not all things can run in garden Can you provide an example of what you'd want to do but you aren't able to?
Booting VMs is kind of the main one.
Booting VMs on your worker seems like exactly the kind of debris concourse is encouraging the avoidance of by enforcing the containerisation of your builds. That said, I can't think of a reason why you couldn't boot a VM in a privileged Garden container, have you tried?
Re: Concourse CI
#89My number one complaint with Concourse (which I suspect is due to Go) is that you need to have it hosted with a valid TLS/SSL cert in order to use the fly command. At least this was an issue in the 2.6.0 days, but I couldn't see anything to change this in the recent versions. This is rather annoying if you want to run a copy on your local network say at home. Its very frustrating because the fly command solves the bi…
I must be doing something wrong, but I have been running Concourse without a cert since 1.6.0.
Re: Concourse CI
#90We're using Buddy - https://buddy.works/ - and it seems to be easier, faster and more reliable than most of these other CI solutions so far.
Interesting. How does it compare to other CI software like Jenkins? I'm always a bit skeptic about tools that look nice but turn out to be limited when put to real work.
Works well for us, docker/container native so every step in a pipeline is a persistent volume with the environment changing based on what image you need. Also easily builds/pushes your own images and lots of other built-in task runners to make pipelines. Has .yaml or ui config and they have an enterprise version which runs on-prem.