41–50 of 72 posts
Earlier quoted context omitted.
Is Windows support on the roadmap?
Woops, typo'd in my original comment: it supports Linux, Windows , and OS X. :) Binaries here: http://concourse.ci/downloads.html
Full Disclosure: I also work at Pivotal on a team that has done a large amount of automation using Concourse (check out our pipelines [1]) Things that we've done so far with Concourse: * A dependency check notifier that based on an RSS feed from various language maintainers: Sends an email, updates our pivotal tracker account, sends a message to our slack channel * A job, that based on the completion of a build will…
Earlier quoted context omitted.
Woops, typo'd in my original comment: it supports Linux, Windows , and OS X. :) Binaries here: http://concourse.ci/downloads.html
I've been trying to figure this out from the docs, but how does it support Windows? In the sense that for now (until Server 2016 comes out), you don't really have "container support".
There's a proper Garden Windows backend in the works which we'll switch to at some point once we better understand it: https://github.com/cloudfoundry/garden-windows
I 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…
Concourse really seems like a nicer Go.CD, in terms of how pipelines, jobs and resources work. I'm quite interested to see how it can work for a fully Docker-based workflow (each git repo has a Dockerfile in the root, that we want to rebuild whenever the master branch receives a new commit. Then we run the image in a container, execute our tests, then if the pass export the Docker image and pass it on to the staging…
Buildbot can integrate with Docker to run tasks on containers, create complex conditional flows with triggered builds/steps (among others), and has been in use for many years at organizations large & small.
While the YAML based Concourse configurations seem very useful, we've found that for many non-trivial pipeline style builds are better served by being written in a fully functional language like Python. It has some disadvantages compared to a declarative approach taken by Travis & Concourse, but I feel that they outweigh the limitations imposed by the latter.
The next version of buildbot is also being refactored into a core + plugins system, which should allow for some pretty impressive flexibility that should serve the needs of almost everyone.
--
1. https://concourse.ci/concourse-vs.html 2. http://docs.buildbot.net/latest/
Full Disclosure: I also work at Pivotal on a team that has done a large amount of automation using Concourse (check out our pipelines [1]) Things that we've done so far with Concourse: * A dependency check notifier that based on an RSS feed from various language maintainers: Sends an email, updates our pivotal tracker account, sends a message to our slack channel * A job, that based on the completion of a build will…
Hey Danny, would you mind pointing to some of those resources if they're 1) open-source and 2) not in the main concourse org?
For 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 very much appreciate the "Concourse vs." page[1] which compares Concourse to several other CI solutions, but I wish they would include Buildbot[2]. Everyone always forgets about Buildbot! Buildbot can integrate with Docker to run tasks on containers, create complex conditional flows with triggered builds/steps (among others), and has been in use for many years at organizations large & small. While the YAML based Co…
This is similar to how some Concourse Resources are implemented with Shell[1] scripts, and some in Go[2]. -- 1. https://github.com/concourse/git-resource 2. https://github.com/concourse/tracker-resource
I very much appreciate the "Concourse vs." page[1] which compares Concourse to several other CI solutions, but I wish they would include Buildbot[2]. Everyone always forgets about Buildbot! Buildbot can integrate with Docker to run tasks on containers, create complex conditional flows with triggered builds/steps (among others), and has been in use for many years at organizations large & small. While the YAML based Co…
I very much appreciate the "Concourse vs." page[1] which compares Concourse to several other CI solutions, but I wish they would include Buildbot[2]. Everyone always forgets about Buildbot! Buildbot can integrate with Docker to run tasks on containers, create complex conditional flows with triggered builds/steps (among others), and has been in use for many years at organizations large & small. While the YAML based Co…
I'd love to see a Concourse.io vs. GitLab CI though... https://about.gitlab.com/gitlab-ci/
GitLab CI is similar to Travis CI in how it works. The page lists three things about Travis CI:
1. Unfortunately it still doesn't have support for pipelines
2. only very simple builds are possible.
3. if something doesn't pass in CI you normally need to send up lots of little debugging commits to work out why it's behaving differently
GitLab CI has does the following to address this:
1. As mentioned GitLab earlier has triggers and we're working on per project pipeline views
2. Builds in GitLab can have many stages with parallelism per stage, since today you can pass build artifacts between stages and cache items https://about.gitlab.com/2016/03/29/gitlab-runner-1-1-releas...
3. You can test the runner locally with exec https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/...
Please let me know what is missed and what people need that we need to add to GitLab CI