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

Add additional Rubies using Workflows. #1032

Merged
merged 1 commit into from
Jan 26, 2018
Merged

Conversation

nickcharlton
Copy link
Member

@nickcharlton nickcharlton commented Nov 24, 2017

A recent issue (#1010) highlighted a deprecation under certain Ruby
versions that we should be aware of. So far, we've been using CircleCI
for running tests and previously they didn't support multiple builds.

With Circle CI 2.0, Workflows allows for something like this to be setup. This
uses YAML inheritance to share a job definition across multiple build
types (defined as different Docker configurations).

This introduces Ruby 2.3 and 2.4.3 in addition to 2.5.0 and using Postgres 9.5.

Notable caveat to this approach is that you must set different databases
for each environment (here named like the Ruby versions) to avoid test
state-based errors.

@nickcharlton nickcharlton force-pushed the nc-circle-multiple-ruby branch 5 times, most recently from 6f3900b to 288e982 Compare November 24, 2017 18:36
Copy link
Contributor

@croaky croaky left a comment

Choose a reason for hiding this comment

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

Postgres upgrade could maybe be its own PR?

A recent issue (#1010) highlighted a deprecation under certain Ruby
versions that we should be aware of. So far, we've been using CircleCI
for running tests and previously they didn't support multiple builds.

With Circle CI 2.0, Workflows allows for something like this to be setup. This
uses YAML inheritance to share a job definition across multiple build
types (defined as different Docker configurations).

This introduces Ruby 2.3 and 2.4.3 in addition to 2.5.0 and using Postgres 9.5.

Notable caveat to this approach is that you must set different databases
for each environment (here named like the Ruby versions) to avoid test
state-based errors.
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.

2 participants