Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce single-command create-env based deployment #1380

Closed
vito opened this issue Jul 14, 2017 · 2 comments
Closed

Introduce single-command create-env based deployment #1380

vito opened this issue Jul 14, 2017 · 2 comments
Assignees
@vito @clarafu
Milestone
v3.4.0

Comments

@vito
Copy link
Member

vito commented Jul 14, 2017 •
edited
Loading

Feature Request

What challenge are you facing?

The Vagrant box is no longer shippable and has been a substantial burden to maintain and test. It requires a dedicated machine to build its images.

A Modest Proposal

I want to be able to download a single .yml file from our GitHub releases and pass it right to bosh create-env with no additional steps to get a single-VM Concourse deployed locally in 5-10 minutes.

We should then update the docs to reflect this workflow rather than Vagrant, and spin down our dedicated machine.

Let's build on https://github.com/concourse/concourse-deployment for this.

Sub-goal

Having pre-compiled packages may be important to achieving that 5-10 minute goal. @pivotal-topher-bullock did some work on that - ping them for context if needed. We'll probably have to start doing this as part of our pipeline. Not sure what the actual CI mechanics would be.
@vito vito added this to the v3.4.0 milestone Jul 14, 2017
This was referenced Jul 14, 2017
Closed
Closed
@jtarchie jtarchie mentioned this issue Jul 18, 2017
Open
@clarafu clarafu self-assigned this Aug 3, 2017
@clarafu
Copy link
Contributor

clarafu commented Aug 3, 2017

I was able to use the concourse-deployment virtualbox step and shortened it to bosh create-env concourse.yml --state vbox-state.json. The state option is required in order to store the current deployment state and needs to be used for deleting the deployment using bosh delete-env ....

clarafu added a commit to concourse/concourse-bosh-deployment that referenced this issue Aug 4, 2017
@clarafu @mhuangpivotal
remove tls and template out versions of releases
4fdc949 
We want to pull in the latest versions of the releases that this
manifest depends on (concourse, garden runc, bosh virtualbox cpi, and
stemcell) so we templated them out in order to fill in the versions in
the pipeline.

concourse/concourse#1380

Signed-off-by: Mark Huang <mhuang@pivotal.io>
clarafu added a commit that referenced this issue Aug 4, 2017
@clarafu
add task for building create env manifest
d197194 
#1380

Signed-off-by: Mark Huang <mhuang@pivotal.io>
clarafu added a commit to vmware-archive/pipelines that referenced this issue Aug 4, 2017
@clarafu
add job to main pipeline for building create env manifest
cfa05c2 
concourse/concourse#1380

Signed-off-by: Mark Huang <mhuang@pivotal.io>
clarafu added a commit to vmware-archive/pipelines that referenced this issue Aug 4, 2017
@clarafu @mhuangpivotal
Remove passed constraint for concourse in build-create-env-manifest
b7f78eb 
concourse/concourse#1380

Signed-off-by: Mark Huang <mhuang@pivotal.io>
vito added a commit to vmware-archive/pipelines that referenced this issue Aug 8, 2017
@vito @clarafu
publish concourse-lite.yml, ship compiled releases
cd59c9f 
concourse/concourse#1380

Signed-off-by: Clara Fu <cfu@pivotal.io>
@vito
Copy link
Member Author

vito commented Aug 15, 2017

Works!

@vito vito closed this as completed Aug 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vito vito

@clarafu clarafu

Labels
None yet
Projects
None yet
Milestone
v3.4.0
Development

No branches or pull requests
2 participants
@vito @clarafu