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 Github Actions #90

Merged
merged 38 commits into from
Jan 7, 2021
Merged

Move to Github Actions #90

merged 38 commits into from
Jan 7, 2021

Conversation

rolljee
Copy link
Contributor

@rolljee rolljee commented Dec 7, 2020

This PR move away from travis ci in favour of Github actions

@rolljee rolljee self-assigned this Dec 7, 2020
Comment on lines 15 to 16
- run: npm install --silent --unsafe-perm
- run: npm install --silent --unsafe-perm --only=dev
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- run: npm install --silent --unsafe-perm
- run: npm install --silent --unsafe-perm --only=dev
- run: npm install --silent --unsafe-perm

Comment on lines 27 to 28
- run: npm install --silent --unsafe-perm
- run: npm install --silent --unsafe-perm --only=dev
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- run: npm install --silent --unsafe-perm
- run: npm install --silent --unsafe-perm --only=dev
- run: npm install --silent --unsafe-perm

@Aschen Aschen changed the title Feat/move to gh actions Move to Github Actions Dec 8, 2020
@Aschen Aschen changed the base branch from develop to master December 8, 2020 06:52
@Aschen Aschen changed the base branch from master to develop December 8, 2020 06:52
using: "composite"
steps:
- run: npm install --silent --unsafe-perm
shell: bash
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a way to not specify bash all the time?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not that i now of, i'll keep looking and update if i found something

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thats about the workflow, not a composite action.yml file

The docs about it is https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/creating-a-composite-run-steps-action and i'll have a deeper look into it, but in their example all of them have duplicate shell:bash

Comment on lines 8 to 11
- run: npm pack
shell: bash
- run: tar xf kourou-$(node -e 'console.log(require("./package.json").version)').tgz
shell: bash
Copy link
Contributor

Choose a reason for hiding this comment

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

Why not just run typescript compile instead of packing and unpacking?

Suggested change
- run: npm pack
shell: bash
- run: tar xf kourou-$(node -e 'console.log(require("./package.json").version)').tgz
shell: bash
- run: tsc
shell: bash

Copy link
Contributor

Choose a reason for hiding this comment

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

Because we want to test the generated NPM package and not the source code

@rolljee rolljee marked this pull request as draft December 10, 2020 16:46
.github/workflows/pull_request.workflow.yml Outdated Show resolved Hide resolved
.github/workflows/pull_request.workflow.yml Outdated Show resolved Hide resolved
.github/workflows/pull_request.workflow.yml Outdated Show resolved Hide resolved
@alexandrebouthinon
Copy link
Member

alexandrebouthinon commented Jan 5, 2021

@rolljee being very busy, I took over his job and added:

  • Using a single Github Action for functional testing
  • Test only the output artifact of the build job
  • Formatting YAML files

Copy link
Member

@alexandrebouthinon alexandrebouthinon left a comment

Choose a reason for hiding this comment

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

Having worked on this branch, my review doesn't count anymore. I approve only to not be blocked by Github checks

@alexandrebouthinon alexandrebouthinon marked this pull request as draft January 7, 2021 12:16
@alexandrebouthinon alexandrebouthinon marked this pull request as ready for review January 7, 2021 12:21
@Njuelle Njuelle merged commit 9d13c22 into develop Jan 7, 2021
@Njuelle Njuelle deleted the feat/move-to-gh-actions branch January 7, 2021 13:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants