Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Concourse CI

concourse.ci

Post reply on HN
Print view View original

21–30 of 158 posts

Re: Concourse CI

#21

Post by rukenshia »

We are using concourse at work right now and have 50-ish pipelines for various repositories. IMO, there's definitely some work you have to put into it because you'll sooner or later run into a problem with the existing resources and need a custom one. Writing custom resources is pretty easy however.

Concourse also isn't really made to work well with the Git Flow, there is no builtin way to run the CI on multiple branches (there's a git-multibranch community resource which requires redis at some point). we're basically thinking about changing our workflow to trunk-based, but it still feels weird to me that we might change our workflow to fit our CI better.

that being said, I personally still really like concourse and it's fun to work with.

Re: Concourse CI

#22

Post by sytse »

webo wrote: post #11

Mostly 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. (…

GitLab CI has multi project pipeline, triggers, artifacts, and manually approved next steps. But I'm not sure what your first requirement means, GitLab CI always composes pipelines from individual projects so it probably doesn't meet your criteria. I'm interested to hear what you ran into with previous systems that made this your nr 1 criteria.

Re: Concourse CI

#23

Post by witten »

sytse wrote: post #20
witten wrote: post #14

I took part in evaluating Concourse CI for the needs of my company (30+ devs). While it has amazing CI pipeline capabilities, we ultimately didn't select Concourse because it felt much more like a CI toolbox, requiring some development to put those tools to use. And what we really wanted was more of a turnkey CI product. Perhaps ironically, we ended up doing some development around the edges of the CI product we ulti…

Cool to hear you selected GitLab. We recently added multi project pipeline visualization. That was partially inspired by concourse CI. Is there anything else you would like to see?

Interesting you should mention that. Right around the time you implemented multi-project pipeline visualization, we built a bot that listens for GitLab build completion events, hits the (undocumented /unsupported) internal GitLab global code search ElasticSearch index, finds downstream dependencies of the completed build (as declared in setup.py/package.json), and triggers their builds as well.. Taking full advantage of your nifty visualization.

So I think the feature we'd want to make that easier is an actual global code search API!

Re: Concourse CI

#24

Post by Amelia55 »

rukenshia wrote: post #21

We are using concourse at work right now and have 50-ish pipelines for various repositories. IMO, there's definitely some work you have to put into it because you'll sooner or later run into a problem with the existing resources and need a custom one. Writing custom resources is pretty easy however. Concourse also isn't really made to work well with the Git Flow, there is no builtin way to run the CI on multiple bran…

I'm making $86 an hour working from home. I was shocked when my neighbour told me she was averaging $95 but I see how it works now. I feel so much freedom now that I'm my own boss. This is what I do, ====http://ow.ly/P0wk30aVXfN

Re: Concourse CI

#25

Post by jackfraser »

rjzzleep wrote: post #16

I've been eyeing Concourse and Go.CD over Jenkins for a while. The main criticism I saw on Jenkins and Go.CD vs. Concourse was that Jenkins Pipelines aren't first class and that it's easier to export configuration(in that regard Concourse > Go.CD > Jenkins). On the other hand Jenkins and Go.CD supports extensions, which Concourse touts as a feature. I also want the CI builds to create my base boxes with packer in mul…

I've worked with GoCD in production a bit. It's a bit of a beast to keep running, the UI is very strange, but the pipelines are extremely powerful and make for good separation of stages. I found it awkward to configure jobs, though, and the documentation is not excellent. There's also a much smaller plugin ecosystem than with Jenkins. We ended up having a guy spend a good lot of his time, nearing 50% some weeks, just keeping GoCD happy for a couple hundred devs.

Overall, I would choose Jenkins first unless you know there's something GoCD can handle significantly better.

Re: Concourse CI

#26

Post by EngineerBetter »

fenollp wrote: post #4
bdcravens wrote: post #2

Kind of odd to see the homepage show Vagrant as the install mechanism, even though it supports Docker as well. In 2017, I'd think more developers are likely to run Docker than Vagrant workloads on their machine.

Probably easier to run Docker inside Vagrant than Docker inside Docker.

Concourse doesn't run Docker, it uses something called Garden to run OCI containers from Docker images.

Those containers can run the Docker daemon though, if you like.

Re: Concourse CI

#27

Post by EngineerBetter »

paloaltokid wrote: post #5

Concourse is a really amazing piece of software, but the BOSH requirement I think will keep adoption low for small companies.

We made Concourse-Up so you don't need to learn BOSH.

https://github.com/EngineerBetter/concourse-up

It'll give you a working, upgradable, auto-healing Concourse in one command.

Re: Concourse CI

#28

Post by org3432 »

We looked at Concourse deeply, while we didn't go with it, it's inspired a number of projects I know and I think has pointed out the obvious; representing how you think about a problem is how you should represent it visually, great insight that has been overlooked in CI.

Re: Concourse CI

#29

Post by voltagex_ »

captn3m0 wrote: post #13
boyter wrote: post #10

My 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 issue valid TLS certs for my internal servers using letsencrypt DNS challenge (there is a nice cloudflare hook for dehydrated that I use). Runs on cron, haven't had to worry about it once I set it up. (Haven't tried with concourse, but don't think that would be a problem)

Do you worry about your internal names being exposed via Certificate Transparency?
Post reply on HN