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 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 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?