8

CircleCI now allows you to use a machine executor which provisions a separate VM for you, with Ubuntu 14.04 and Docker version 17.06.0-ce installed. This allows you to turn on experimental features for the Docker daemon. You need to use the machine key instead of the docker key, to run your job in a separate virtual machine instead of just a Docker ...


5

You are running into the limitations of managed services. Many managed services are great to start experimenting with ideas and can show a great value for the casual user. But they trade ease of use for flexibility and functionality, therefore as soon as we start to have serious needs and are ready to spent a significant amount of effort building up on these ...


5

I still don't get how your config.yml could launch ansible without a step part. Here is my findings, but I'm unsure it is what you're after, but that was too long for a comment. According to the documentation here you have to add a add_ssh_keys with the fingerprint of your key as seen in the UI. - add_ssh_keys: fingerprints: - "48:a0:87:54:ca:75:...


3

This discussion gives a pretty good suggestion on how to accomplish what I want. https://discuss.circleci.com/t/does-circleci-2-0-work-with-monorepos/10378/11


3

Running your config.yml through yamllint, produced the following: 1:1 warning missing document start "---" (document-start) 13:3 error duplication of key "build" in mapping (key-duplicates) 25:19 error syntax error: mapping values are not allowed here When I add colons to the entry on lines 25 and 28: workflows: version: 2 ...


2

We're using CircleCI with Go monorepo. Here’s how it’s done: Define a job for each service in circle config yaml. A git push triggers CircleCI job that finds which services are part of the change. For each service run a CircleCI job with: { "build_parameters": { "CIRCLE_JOB": "my-service" } } Also, published as an open source: https://github....


2

You simply have an incorrect yaml syntax in your workflows jobs list. From what I could very quickly understand on circleCI's documentation, jobs names are accepted as a shorthand if you don't define any parameters. If you have parameters, the list element is a hashmap with top element being the job name. In your specific case, this should give (note the ...


1

I removed the service account and recreated it (with same name and roles). Generated a new key and updated the CI and suddenly it worked. gcloud glitch.


1

Due to the fact that build had a branch filter... Even though no error message on additional info is shown... Hence I needed to add the branch like so: workflows: version: 2 build_deploy_test: jobs: - build: filters: branches: only: - develop - devops-docker-intial - ...


1

This is the approach I came up with. It's kinda ugly, but it does work: - run: name: Create unique build identifier command: | GIT_SHA=$( git rev-parse --short HEAD ) echo "export GIT_SHA=${GIT_SHA}" >> "${BASH_ENV}" # the always-increasing counter, based on CIRCLE_BUILD_NUM BUILD_COUNTER="${CIRCLE_BUILD_NUM}" ...


1

A closer reading of the documentation about using environment variables in cache keys reveals the issue (emphasis mine): The environment variable variableName (supports any environment variable exported by CircleCI or added to a specific Context—not any arbitrary environment variable). "exported by CircleCI" seems to mean the list of mostly-CIRCLE_...-...


1

Try adding,- steup_remote_docker before - aws-ecr/build-image:


1

With docker compose (or docker swarm if you want to distribute the containers) create a container for each Git repository. This should map well to docker’s philosophy of each container being used for a single purpose. As far as examples go, I can recommend you have a look at veleda (shameless self-promotion) which combines 3 databases, a flask app, a ruby ...


1

The answer, no. The best ways to rollback would be to use git revert, which then adds the rollback to history (which is a good thing), and then push that like any other commit. The other would be to use the git hash of the commit you'd like to rollback to and build it with the CircleCI API. Right now, you could also attempt to rebuild and older build via ...


Only top voted, non community-wiki answers of a minimum length are eligible