Go to file
Ciro S. Costa f97e085e80 docker-compose: bump db's shm_size
it seems like postgres by default might need to resize the amount of
shared memory that it uses for performing parallel work.

i've hit this when making 100's of concurrent requests to certain api
endpoints:

	 could not resize shared memory segment "/PostgreSQL.<..>"
	 to $N bytes: No space left on device

after applying the change (which makes docker go from 64MB to 1GB), , I
can then execute those requests w/ no problems.

Signed-off-by: Ciro S. Costa <cscosta@pivotal.io>
2020-03-23 14:30:20 -04:00
.github don't mark milestoned issues as stale 2019-11-05 09:22:23 -05:00
atc Merge pull request #5332 from concourse/fix-needs-v6-migration 2020-03-19 17:50:20 -04:00
cmd cmd/init: add missing library 2020-02-11 16:58:42 -05:00
fly Merge pull request #4168 from concourse/fly-sync 2020-03-16 11:59:06 -04:00
go-concourse go-concourse: Reduce overall diff of PR 2020-02-20 14:05:31 -05:00
hack web: convert mdi-icons script to module 2020-02-28 09:56:22 -05:00
release-notes add release note 2020-03-05 17:32:37 -05:00
screenshots add 2x scaled screenshot for hidpi laptops 2018-09-19 10:36:30 -04:00
skymarshal skymarshal: strictly parsing redirect URI 2020-03-17 15:34:53 -04:00
testflight testflight: lowercase check timeout err msg 2020-03-04 10:18:05 -05:00
topgun Merge pull request #5237 from concourse/contributing-topgun 2020-03-19 11:09:32 -04:00
tracing add tracing package 2020-01-21 13:58:46 -05:00
tsa Merge pull request #3936 from cycloidio/gl_3551 2020-01-17 17:03:47 -05:00
vars vars: use go std err wrapping 2020-03-04 10:18:05 -05:00
web web: behaviour: narrow scope on resource ui 2020-03-16 16:52:53 -04:00
worker worker: fix container-sweeper test 2020-02-27 09:58:34 -05:00
.dockerignore flesh out CONTRIBUTING.md 2018-09-25 14:18:48 -04:00
.env run watsjs/testflight against prebuilt Concourse 2018-10-01 17:10:35 -04:00
.gitignore web: add elm setup bundle to .gitignore 2020-02-28 11:13:11 -05:00
CODE_OF_CONDUCT.md move important docs to root 2018-11-20 11:17:20 -05:00
CONTRIBUTING.md Merge pull request #5237 from concourse/contributing-topgun 2020-03-19 11:09:32 -04:00
Dockerfile remove containerd dependencies from Dockerfile 2020-03-12 13:43:01 -04:00
LICENSE.md re-init 2018-09-18 15:26:17 -04:00
NOTICE.md say "Present" in NOTICE.md 2019-04-09 16:08:20 -04:00
README.md update link to new helm chart location 2020-01-09 09:26:12 -05:00
docker-compose.yml docker-compose: bump db's shm_size 2020-03-23 14:30:20 -04:00
go.mod Bump golang.org/x/crypto 2020-02-21 12:30:30 -05:00
go.sum Bump golang.org/x/crypto 2020-02-21 12:30:30 -05:00
package.json web: add build-js to yarn build 2020-02-28 09:56:22 -05:00
tools.go Add tools.go to keep track of tool versions 2019-04-08 15:57:27 -04:00
versions.go concourse/#3819 using zstd to streamIn/Out between workers 2019-06-24 23:08:10 -04:00
webpack.config.js web: babel-ify javascript bundle 2020-02-28 09:56:22 -05:00
yarn.lock build(deps): bump acorn from 6.4.0 to 6.4.1 2020-03-16 03:01:31 +00:00

README.md

Concourse: the continuous thing-doer.

Concourse is an automation system written in Go. It is most commonly used for CI/CD, and is built to scale to any kind of automation pipeline, from simple to complex.

booklit pipeline

Concourse is very opinionated about a few things: idempotency, immutability, declarative config, stateless workers, and reproducible builds.

Installation

Concourse is distributed as a single concourse binary, available on the Releases page.

If you want to just kick the tires, jump ahead to the Quick Start.

In addition to the concourse binary, there are a few other supported formats. Consult their GitHub repos for more information:

Quick Start

$ wget https://concourse-ci.org/docker-compose.yml
$ docker-compose up
Creating docs_concourse-db_1 ... done
Creating docs_concourse_1    ... done

Concourse will be running at 127.0.0.1:8080. You can log in with the username/password as test/test.

Next, install fly by downloading it from the web UI and target your local Concourse as the test user:

$ fly -t ci login -c http://127.0.0.1:8080 -u test -p test
logging in to team 'main'

target saved

Configuring a Pipeline

There is no GUI for configuring Concourse. Instead, pipelines are configured as declarative YAML files:

resources:
- name: booklit
  type: git
  source: {uri: "https://github.com/vito/booklit"}

jobs:
- name: unit
  plan:
  - get: booklit
    trigger: true
  - task: test
    file: booklit/ci/test.yml

Most operations are done via the accompanying fly CLI. If you've got Concourse installed, try saving the above example as booklit.yml, target your Concourse instance, and then run:

fly -t $target set-pipeline -p booklit -c booklit.yml

These pipeline files are self-contained, maximizing portability from one Concourse instance to the next.

Learn More

Contributing

Our user base is basically everyone that develops software (and wants it to work).

It's a lot of work, and we need your help! If you're interested, check out our contributing docs.