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

Revamp GitHub workflows using Ember.js native implementation #144

Merged
merged 11 commits into from
Oct 13, 2021

Conversation

MrChocolatine
Copy link
Member

@MrChocolatine MrChocolatine commented Oct 12, 2021

CI

Reset GitHub workflow file to Ember.js native implementation (#144)

Ember.js implementation:
https://github.com/ember-cli/ember-addon-output/blob/v4.0.0-beta.1/.github/workflows/ci.yml

We used to manually handle the caching of dependencies while actions/setup-node natively handles it, with a few parameters, making our life easier.

One tiny addition compared to Ember.js implementation: jobs got a timeout of 20 minutes to avoid burning the default limit of 6 hours.

Remove scenario ember-default in ember-try (#144)

This scenario has been removed in ember-cli v3.20.0:
ember-cli/ember-addon-output@1ed3342

Update name of ember-try scenarios (#144)

To make them match with Ember.js native implementation and with the names usually used in the Ember.js ecosystem.

Fixes

Fix npm-script lint in package.json (#144)

See https://github.com/ember-cli/ember-cli/pull/9500/files

@MrChocolatine MrChocolatine added the ci Continuous Integration label Oct 12, 2021
@MrChocolatine MrChocolatine force-pushed the revamp-gh-workflows branch 4 times, most recently from effd1e4 to 0d61c5b Compare October 12, 2021 16:50
@MrChocolatine MrChocolatine marked this pull request as ready for review October 12, 2021 17:02
@MrChocolatine MrChocolatine changed the title revamp gh workflows Revamp GitHub workflows using Ember.js native implementation Oct 12, 2021

env:
NODE_VERSION: '12.x'
NODE_VERSION: '12'
Copy link
Member Author

Choose a reason for hiding this comment

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

The syntax 12 is enough if we just want to use the lastest major version.


- name: Lint
run: yarn lint
- uses: actions/checkout@v2
Copy link
Member Author

Choose a reason for hiding this comment

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

uses: actions/setup-node@v2
with:
node-version: ${{ env.NODE_VERSION }}
cache: yarn
Copy link
Member Author

Choose a reason for hiding this comment

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

with:
node-version: '${{ env.NODE_VERSION }}'
- name: Run Tests
run: yarn run test:ember
Copy link
Member Author

Choose a reason for hiding this comment

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

We used to run the following command: (source)

run: yarn test:ember --launch chrome

( ⬆️. because strategy.browser only has the value chrome)

I am not convinced --launch chrome is really needed, can someone confirm?

Copy link
Member

Choose a reason for hiding this comment

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

It seems useful when you have multiple browsers in testem.js launch_in_ci prop and you only want to run your test on one specific browser, as we only have Chrome in testem.js launch_in_ci prop, it seems ok to remove it

Copy link
Member Author

Choose a reason for hiding this comment

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

Noice, thanks.


- name: Run Tests
run: yarn run test:ember
Copy link
Member Author

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

Answer provided, see the related link ✅ .

@MrChocolatine MrChocolatine requested a review from a team October 12, 2021 17:24
with:
node-version: '${{ env.NODE_VERSION }}'
- name: Run Tests
run: yarn run test:ember
Copy link
Member

Choose a reason for hiding this comment

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

It seems useful when you have multiple browsers in testem.js launch_in_ci prop and you only want to run your test on one specific browser, as we only have Chrome in testem.js launch_in_ci prop, it seems ok to remove it


try-scenarios:
name: Tests - ${{ matrix.ember-try-scenario }}
name: ${{ matrix.try-scenario }}
Copy link
Member

Choose a reason for hiding this comment

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

As we are updating this file, wondering if we should add timeout-minutes option, to avoid having issues with some scenarios running for 360 minutes (default value) because there is an issue in tests and no output is generated, see https://github.com/peopledoc/ember-cli-embedded/runs/3443628551?check_suite_focus=true for example

Was happening mainly for Beta/Canary but could be a "security" for "ember-release" scenario 🤷‍♂️

Copy link
Member Author

Choose a reason for hiding this comment

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

Indeed, I actually thought about it yesterday and forgot to add it, thanks.

@MrChocolatine MrChocolatine merged commit 21c61e2 into master Oct 13, 2021
@MrChocolatine MrChocolatine deleted the revamp-gh-workflows branch October 13, 2021 13:10
@MrChocolatine MrChocolatine mentioned this pull request Oct 13, 2021
MrChocolatine added a commit to peopledoc/ember-metrics-pendo that referenced this pull request Oct 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Continuous Integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants