31–40 of 72 posts
Earlier quoted context omitted.
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).
Earlier quoted context omitted.
Some of my colleagues at Pivotal are running iOS builds with it. That is, they're running builds on a Mac which has an iOS device plugged into it. The workers are run using Houdini, which is a container management daemon that, er doesn't use containers: https://github.com/vito/houdini There's a blog post by someone else at Pivotal, although the details are probably a bit out of date by now: https://blog.pivotal.io/la…
As the author of that blog post I can confirm some of that is out of date. Hopefully I can find some time to update the post for 1.0, but the main concepts still work. At Pivotal Toronto we're running iOS and Android builds using a mac mini as an external worker. What's been a great built in feature is using the pool resource to "check-out" a device and lock it from other tests while a suite is running.
Also, if you have some free time I would love to chat about your experience so far -- I work about 15 minutes away from Pivotal's Toronto office. My email address is listed in my profile.
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…
I saw this page (http://concourse.ci/architecture.html) but it's turtles all the way down...
Or just validate if my understanding is correct:
Concourse has the following components:
* ATC: web UI + job scheduler; can be clustered; uses PostgreSQL as data storage; => this would be a part of the "master" in Jenkins terminology
* TSA: simple SSH server, used by workers to register and presumably be controlled; => this would be the second part of the "master" in Jenkins terminology, in a sort of JNLP Jenkins setup where the workers register with the master instead of vice versa (Jenkins SSH connection)
* workers: Cloud Foundry type containers (WTF is Cloud Foundry exact? their page is totally confusing); "slaves" in Jenkins terminology
Also, if I read the features correctly, Concourse supports both Linux and Windows builds, right?
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…
Are there any plans to support OS X workers? This would be extremely helpful for Mac and iOS apps.
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…
Can you ELI5 Concourse's architecture? (I haven't installed it yet, it's possible that some of my follow up questions are answered by installing Concourse and testing it a bit) I saw this page ( http://concourse.ci/architecture.html ) but it's turtles all the way down... Or just validate if my understanding is correct: Concourse has the following components: * ATC: web UI + job scheduler; can be clustered; uses Postg…
Workers are just machines running a container management daemon (much like a Docker daemon) and a volume manager (a custom daemon for managing caches and efficient artifact propagation between containers). Not sure how you got to Cloud Foundry though, it's not really related. Garden lives in the Cloud Foundry GitHub organization, as it's also used by Cloud Foundry, but you don't need to know anything about CF to use Concourse.
Concourse supports Linux, Windows, and OS X. You can see an example of this here:
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…
Can you ELI5 Concourse's architecture? (I haven't installed it yet, it's possible that some of my follow up questions are answered by installing Concourse and testing it a bit) I saw this page ( http://concourse.ci/architecture.html ) but it's turtles all the way down... Or just validate if my understanding is correct: Concourse has the following components: * ATC: web UI + job scheduler; can be clustered; uses Postg…
I'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?
This is very much a trait of BOSH. When BOSH manages a machine, it owns that machine. It deploys the stuff that's specified in the manifest, but that has to come out of one or more 'releases', ie precisely structured tarballs of stuff, and there's no way to manage a file here or a setting there. You could push out a file by packing into a release, uploading that, and adding it to the manifest, but that's quite a ritu…
Earlier quoted context omitted.
Can you ELI5 Concourse's architecture? (I haven't installed it yet, it's possible that some of my follow up questions are answered by installing Concourse and testing it a bit) I saw this page ( http://concourse.ci/architecture.html ) but it's turtles all the way down... Or just validate if my understanding is correct: Concourse has the following components: * ATC: web UI + job scheduler; can be clustered; uses Postg…
You pretty much got it right. That page is still a bit rough; we'll give it some TLC soon. Workers are just machines running a container management daemon (much like a Docker daemon) and a volume manager (a custom daemon for managing caches and efficient artifact propagation between containers). Not sure how you got to Cloud Foundry though, it's not really related. Garden lives in the Cloud Foundry GitHub organizatio…
Earlier quoted context omitted.
You pretty much got it right. That page is still a bit rough; we'll give it some TLC soon. Workers are just machines running a container management daemon (much like a Docker daemon) and a volume manager (a custom daemon for managing caches and efficient artifact propagation between containers). Not sure how you got to Cloud Foundry though, it's not really related. Garden lives in the Cloud Foundry GitHub organizatio…
Is Windows support on the roadmap?