Travis & parallelize autogenerated versionCompatibility scenarios

Open
#202 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
ci-cd, testing

Research direction

Start with the linked Mirage .travis.yml section and the interaction between versionCompatibility and ember try:each. Research whether Ember Try can expose autogenerated scenarios as separate Travis jobs, and compare the configurations used by popular projects. Done means documenting or implementing a supported parallel Travis setup.

Written by the indexing model from the issue text.

Description

Is there a way to use versionCompatibility with ember try:each and have the jobs run parallel on Travis?

Mirage's current .travis.yml looks like this and I'm wondering if there's a way to leverage the autogeneration piece from Ember Try, but still get parallel test runs in Travis.

Alternatively, is there a current "best practice" around these setups? I'm seeing 2 or 3 different configs being used across popular projects.

Dominant language
JavaScript
Stars
180
Forks
57
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ember-cli/ember-try

All issues in ember-cli/ember-try

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.