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.

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

Move to CircleCI 2.0 #3333

Merged
merged 22 commits into from
Sep 1, 2018
Merged

Move to CircleCI 2.0 #3333

merged 22 commits into from
Sep 1, 2018

Conversation

bboreham
Copy link
Collaborator

@bboreham bboreham commented Aug 25, 2018

Fixes #3217

Once the changes are merged to master I will update the image: lines to a master tag, the same tag for both images.

@bboreham bboreham force-pushed the circle-2.0 branch 5 times, most recently from 8a3b718 to c727710 Compare August 26, 2018 21:32
@bboreham
Copy link
Collaborator Author

@guyfedwards I took your starting-point, adapted it to multi-step in the same pattern as weaveworks/weave, then got it to build and pass tests.

I haven't tried the deployment step yet; it's set to run on master branch only.

@bboreham bboreham mentioned this pull request Aug 27, 2018
# PATH must be set here as circle currently does not support string interpolation
# for environment
# https://discuss.circleci.com/t/bin-sh-mkdir-command-not-found/8710
- run: export PATH="$PATH:$HOME/.local/bin"

This comment was marked as abuse.

This comment was marked as abuse.

steps:
- checkout
- run: GOARCH=arm make BUILD_IN_CONTAINER=false GO_BUILD_INSTALL_DEPS= prog/scope
- run: GOOS=darwin make BUILD_IN_CONTAINER=false GO_BUILD_INSTALL_DEPS= prog/scope

This comment was marked as abuse.

This comment was marked as abuse.

client-defaults: &client-defaults
working_directory: /home/weave/scope
docker:
- image: weaveworks/scope-ui-build:circle-2.0-2885645

This comment was marked as abuse.

This comment was marked as abuse.

<<: *defaults
steps:
- checkout
- run: make BUILD_IN_CONTAINER=false lint

This comment was marked as abuse.

This comment was marked as abuse.


unit-test:
<<: *defaults
parallelism: 1

This comment was marked as abuse.

This comment was marked as abuse.

guyfedwards and others added 17 commits August 30, 2018 10:13
Try to balance the parallelism more
…R=false

Why do you care?  You're either inside it or not using it.
and run client lint and test in the same job, after client-build,
to reduce the number of jobs running in parallel.
* Build 'runner' program in build job and save to workspace;
* Save build outputs - externalui, staticui, codecgen output;
* Install required tools in test VM;
* Call 'make deps' in integration-tests-job and touch 'runner' from
  workspace so it doesn't rebuild.
Reduces the size of the resulting image
This lets it run at the same time as GCE VMs are deleted, and saves us
having to run up another job just for coverage.
saves spinning up another container
Simplify deploy shell scripts;
Run yarn bundle as part of client-build step;
Install awscli as part of deploy step;
Don't run ui-upload in another container.
@bboreham
Copy link
Collaborator Author

I tested the deploy step and addressed comments, so I think this is good to go now.

Copy link
Contributor

@leth leth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🏅

@bboreham
Copy link
Collaborator Author

Just realised I included the commit from #3334 in here to stop tests failing, so I won't merge this until #3334 is approved.

@bboreham bboreham merged commit fda40b8 into master Sep 1, 2018
@bboreham bboreham deleted the circle-2.0 branch September 1, 2018 12:48
@rade
Copy link
Member

rade commented Sep 1, 2018

Yeah!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants