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

CircleCI: Set special s3 buckets after unit tests #21616

Merged
merged 2 commits into from Apr 3, 2018

Conversation

islemaster
Copy link
Contributor

Noticed in the Circle run for #21608 that the new Circle-specific subdirectory names that make our UI tests more reliable on Circle are actually breaking our shared "unit" tests that use VCR to mock exact requests to S3.

This wasn't caught when that configuration change went in because changes to .circleci/config.yml don't cause any of our unit test suites to run.

image

So here I'm making two changes:

  1. Set Circle-specific S3 directory configuration after the unit tests, but before the UI tests.
  2. Make changes to .circleci/config.yml run all tests.

Don't set up special v3 api s3 directories until after the unit tests, before the ui tests.  We need these for reliable UI tests but they mess with VCR in our ruby tests that check exact server requests, including the expected buckets, etc.
Copy link
Member

@davidsbailey davidsbailey left a comment

Choose a reason for hiding this comment

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

It looks like the new change-detection logic was triggered by the config.yml changes in this PR. Nice combo! Thanks for doing this!

@islemaster islemaster merged commit 531e101 into staging Apr 3, 2018
@islemaster islemaster deleted the circle-s3-bucket-after-unit-tests branch April 3, 2018 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants