Concourse CI Hits 1.0.0
concourse.ci
Concourse CI Hits 1.0.0
1–10 of 72 posts
Re: Concourse CI Hits 1.0.0
#2I work at Pivotal, which sponsors Concourse development, so I got one of the fancy t-shirts we made for this occasion.
I wore it to the office today. Other people in the office were coming up to me and raving about Concourse. I've been proselytising it, but I feel like pretty soon I just won't have to. One of my colleagues was telling me that in two days he got an iOS CI pipeline that he never managed to achieve with weeks of tinkering with TeamCity.
I suspect that pretty soon the default choice for CI/CD in Pivotal Labs projects will be Concourse, and that will seed it pretty widely.
If you want to get in on the ground floor of something great, here's a good opportunity.
If you're wondering about what the heck it is, go to the homepage for the 40,000 view: http://concourse.ci/
If you're wondering why the heck another CI system, look at "Concourse Vs.": http://concourse.ci/concourse-vs.html
After that my advice is to look at public Concourse pipelines and pop the hood. And drop into the Slack channel, the team are in there now posting funny gifs. I'm in there too, under jchester_robojar, if you want to ask me anything.
Re: Concourse CI Hits 1.0.0
#3I work at Pivotal, which sponsors Concourse development, so I got one of the fancy t-shirts we made for this occasion. I wore it to the office today. Other people in the office were coming up to me and raving about Concourse. I've been proselytising it, but I feel like pretty soon I just won't have to. One of my colleagues was telling me that in two days he got an iOS CI pipeline that he never managed to achieve with…
More links:
Concourse's own CI: https://ci.concourse.ci and Concourse Slack: http://slack.concourse.ci
Re: Concourse CI Hits 1.0.0
#4I'm looking forward to experimenting with this.
At least in the documentation, there seems to be a lot of focus on extra tools. BOSH seems very off-putting. Having to use the "fly" CLI command to update pipeline configuration seems unnecessary - can I just update the files on the filesystem myself, either via my configuration management tool or a git repository?
Re: Concourse CI Hits 1.0.0
#5I'm looking forward to experimenting with this. At least in the documentation, there seems to be a lot of focus on extra tools. BOSH seems very off-putting. Having to use the "fly" CLI command to update pipeline configuration seems unnecessary - can I just update the files on the filesystem myself, either via my configuration management tool or a git repository?
Using the `fly` CLI allows you to know what changes are being made when you update the pipeline (it shows a diff), and when your configuration is invalid (or when the update fails for another reason).
Re: Concourse CI Hits 1.0.0
#6I'm looking forward to experimenting with this. At least in the documentation, there seems to be a lot of focus on extra tools. BOSH seems very off-putting. Having to use the "fly" CLI command to update pipeline configuration seems unnecessary - can I just update the files on the filesystem myself, either via my configuration management tool or a git repository?
I have a handy heuristic about this: if you are interacting (directly or via a third party) with the filesystem of a service in order to use it, said service is probably solving your problem wrong.
Try `fly`. It's worth it.
Re: Concourse CI Hits 1.0.0
#7For anyone else that got excited about having a Jenkins alternative, this project seems to be only about containers and not other workloads that VMs could tackle, such as running browser or desktop-based software tests. At least that's my understanding after giving the documentation a cursory glance. Could someone familiar with the project please confirm (or hopefully correct) this?
Re: Concourse CI Hits 1.0.0
#8For anyone else that got excited about having a Jenkins alternative, this project seems to be only about containers and not other workloads that VMs could tackle, such as running browser or desktop-based software tests. At least that's my understanding after giving the documentation a cursory glance. Could someone familiar with the project please confirm (or hopefully correct) this?
I am running a browser-based test in Concourse as we speak :)
Re: Concourse CI Hits 1.0.0
#9I'm looking forward to experimenting with this. At least in the documentation, there seems to be a lot of focus on extra tools. BOSH seems very off-putting. Having to use the "fly" CLI command to update pipeline configuration seems unnecessary - can I just update the files on the filesystem myself, either via my configuration management tool or a git repository?
I have a handy heuristic about this: if you are interacting (directly or via a third party) with the filesystem of a service in order to use it, said service is probably solving your problem wrong. Try `fly`. It's worth it.
Funny, I use the opposite approach. If I can't configure and manage something via the filesystem, I usually stay clear of it.
Specifically, not relying on the filesystem means I can't easily browse configuration, I can't have version control, and I can't use my configuration manager to have events trigger when things change.
Re: Concourse CI Hits 1.0.0
#10I'm looking forward to experimenting with this. At least in the documentation, there seems to be a lot of focus on extra tools. BOSH seems very off-putting. Having to use the "fly" CLI command to update pipeline configuration seems unnecessary - can I just update the files on the filesystem myself, either via my configuration management tool or a git repository?
Using the `fly` CLI allows you to know what changes are being made when you update the pipeline (it shows a diff), and when your configuration is invalid (or when the update fails for another reason).
I get the exact same features from my configuration manager, as long as there is a command I can run to validate the configuration file(s).