Tag : concourseci
Learn a little about Concourse CI and get your own Concourse CI running on your laptop with Docker Compose (previously these instructions showed Vagrant). NOTE: the instructions below have been updated in 2020 to use Docker Compose, rather than Vagrant. Learn more from our Concourse Tutorial. NOTE: The https://concourse-ci.org/ has been given a new name
You might be surprised at how quickly you can go from nothing to having a full production environment with BOSH. Very surprised. I’d like to share with you a walk thru of getting started with BUCC – the fabulous tool to run BOSH/UAA/CredHub/Concourse locally or in production. It’s like a treat to yourself. Why add
BUCC is the convention over configuration tool to make it easy to deploy the best, securest, most backupable BOSH/Concourse on a single VM. The Problem The bosh-deployment is the fantastic tool for deploying a BOSH VM to any infrastructure. A vanilla BOSH or one with UAA/CredHub. A BOSH that can deploy normal infrastructure VMs or
A typical web application will need services, such as databases and caches, to run. It will probably also need these services to run its test suite. In this blog post, we will look at how to set up and run PostgreSQL within Concourse CI prior to running our application’s test suite. The Problem For a
When MKB and I were pairing on concourse-tutorial task 12, the following error occurred when we ran the pipeline. resource script ‘/opt/resource/check []’ failed: exit status 1 stderr: failed to fetch digest: 401 Unauthorized In the tutorial, there is a bump-timestamp-file.yml which was using the following docker image resource: image_resource: type: docker-image source: { repository:
At Stark & Wayne, we love Concourse pipelines! We use them for testing/releasing CLI utilities, deploying Cloud Foundry apps, building docker images, creating and testing BOSH releases, and vetting changes to BOSH deployments in an automated fashion starting in sandbox environments all the way to production. Uh-oh! credentials.yml file got committed? One of the most
Using Cloud Config enables you to remove a lot out of your BOSH manifests to simplify them. However, it’s an all-or-nothing approach. You either use it for all your deployments on a director, or none. When Concourse CI hit the magic 1.0.0, they switched over to using a lot of the BOSH 2.0 features, including
BOSH makes a whole lot of tasks in the operations / systemsmanagement space way easier than ever before. Combine that with tools like Spruce and Genesis, and you have a really powerful paradigm for managing your deployments. Pair that with Concourse and it seems like the sky is the limit! Then you run into the
As part of a project, a client wants to have a self-deploying Concourse. Basically that means that once everything is set up, the alpha Concourse will deploy the beta Concourse and, if that completes successfully, the beta Concourse will then update/deploy the alpha Concourse. Because automation is shiny. Current Goal Ensure that the the beta
