Re: CF deployment environments available for CF incubating projects to use?
Amit Kumar Gupta
Yes and yes. It is ready to be given a try, and it is still under change
and development. There are several tools in mega-ci:
1. provision AWS for BOSH and Concourse (and optionally CF), and deploy
2. deploy Concourse into that environment
3. provision AWS for BOSH and CF (without Concourse), and deploy BOSH.
The "provision AWS" parts are done via CloudFormation templates. I'm not
sure how to characterize the dependency on AWS API there, but the
CloudFormation templates have a format version, and we currently use the
only valid format, which has been stable for 5 years:
Tools 1 (
and 2 (https://github.com/cloudfoundry/mega-ci/#deploying-concourse)
mentioned above get you a concourse ready to run builds that deploy CF.
Depending on how well you understand AWS, BOSH, Concourse, and CF, the
pipeline config ymls and CI scripts in the same mega-ci repo can be
modified and used to continuously deploy CF to your environment. But they
are not ideal for the onboarding experience.
As for your point about whether other projects have to figure out
individually how to operate CI builds, that's a very poignant question.
Currently, the answer is yes. There is a dojo program designed to allow
people in the foundation to pair with the core teams to learn the system,
CI practices, etc. I would love to get to a world that deploying CF is so
easy that the public documentation suffices for any individual team to set
up their own CI easily.
Among the 20 or so core development teams, distributed around the world,
comprised of 100+ developers from several different companies, there
actually is a fairly robust, well integrated set of tools and practices
around CI and how we consume and produce assets for other pipelines. As
the foundation grows, the onboarding story will need to be improved. But
this is no small problem.
There are 100s of v219+ builds happening every day (and next week, there
will be v220+ builds). For now, I'd recommend opening up mailing list
issues or Github issues (e.g. here:
https://github.com/cloudfoundry/cf-release/issues) with the specific errors
you're encountering, the core development teams are happy to help the
community past the initial technical and conceptual bootstrapping hurdles.
And to address your question about the financials, I don't know the
complete picture, but the question "who foots the bills for all the current
CIs?" and "who should foot the bill for a publicly available pool of CI
environments?" probably have different answers.
Amit, OSS Release Integration PM
On Wed, Oct 7, 2015 at 3:48 PM, Jean-Sebastien Delfino <jsdelfino(a)gmail.com>
Hi Amit,We're working on making deploying CF itself less burdensome, but thatwill take more time.