Closed
Description
ππ» GitHub Action Artifacts
π
Monday, May 3rd, 2021
π noon Pacific Time (in your timezone)
ποΈ with @reconbot
π·οΈ Action
Subscribe to this issues to get a notification before the show begins and a summary after the show concludes.
GitHub Action Artifacts
Iβd like to have a job run after a few others finish and use their artifacts. Eg build serialport with all architectures and ship them in a single npm package.
β @reconbot on twitter
In this show, we will create an releases setup which requires native operating systems bindings to be created on their respective target operating systems. After all bindings are created, they will all be published as part of an npm package using GitHub Actions and @semantic-release.
Outline
- Introductions
- What are native bindings for Node.js, why do they need to be created on the same operating system version that they will be used on?
- Creating the different bindings using a GitHub Actions Workflow matrix in reconbot/bindings-cpp
- Upload bindings from all build matrix jobs to as GitHub Artifacts
- Download all GitHub Artifacts in a final step
- Setup automatic releases of the package with the native bindings to npm using @semantic-releas
- Bonus: apply the same setup to serialport/node-serialport
Preparation
- Get confirmation from @reconbot on the summary above to make sure we are on the same page in terms of scope for the show
- Prepare a repository for a minimal npm package that requires native operating system bindings: reconbot/bindings-cpp
- Create a minimal repository to showcase artifacts & GitHub Actions Workflow matrix: gr2m/github-actions-artifacts-test