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

feat(superchain): also build a superchain image with Node 14 #2741

Merged
merged 6 commits into from
Mar 26, 2021

Conversation

rix0rrr
Copy link
Contributor

@rix0rrr rix0rrr commented Mar 25, 2021

For CDKv2, we want to require (and test) against a newer version of
Node. We've attempted to build multiple Node versions into a single
Docker image, but because we cannot control the entrypoint there is no
reliable way of switching between the Node versions at execution time.

Therefore, we will now build two versions of the "superchain" image.
The Node version built into each is controlled by the NODE_VERSION
build argument.

Workflow has been changed to build and push the following images:

  • Nightlies:
    • jsii/superchain:node10-nightly
    • jsii/superchain:node14-nightly
    • jsii/superchain:nightly will remain an alias for :node10-nightly
  • Releases:
    • jsii/superchain:node10
    • jsii/superchain:node14
    • jsii/superchain:latest will remain an alias for :node10.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

For CDKv2, we want to require (and test) against a newer version of
Node. We've attempted to build multiple Node versions into a single
Docker image, but because we cannot control the entrypoint there is no
reliable way of switching between the Node versions at execution time.

Therefore, we will now build two versions of the "superchain" image.
The Node version built into each is controlled by the `NODE_VERSION`
build argument.

Workflow has been changed to build and push the following images:

* Nightlies:
    * `jsii/superchain:node10-nightly`
    * `jsii/superchain:node14-nightly`
    * `jsii/superchain:nightly` will remain an alias for `:node10-nightly`
* Releases:
    * `jsii/superchain:node10`
    * `jsii/superchain:node14`
    * `jsii/superchain:latest` will remain an alias for `:node10`.

(Multiple images are built in a `for` loop instead of having parallel
workflows because as far as I know there's no way to parameterize the
rather complex GitHub Action Workflow, so the alternative would be
copy/pasting which I'd rather not do).
@rix0rrr rix0rrr requested a review from a team March 25, 2021 10:42
@rix0rrr rix0rrr self-assigned this Mar 25, 2021
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Mar 25, 2021
Comment on lines 16 to 17
`Javascript` | `node >= 10.19.0` with `npm >= 6.13.4` (default)
| OR `node >= 14.16.0` with `npm >= 6.14.11` (`--build-arg NODE_VERSION=14`)
Copy link
Contributor

Choose a reason for hiding this comment

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

This won't render properly... Seems like the rendering engine does not like when the first column is empty.

Also - you don't want to make this relative to --build-arg, instead refer to the tag names.

Perhaps we should actually extract the node and npm info to a sub-section - and in the table mention this is tag-dependent, and link to it?

@rix0rrr rix0rrr requested a review from RomainMuller March 25, 2021 11:12
--network=host \
-v${{ github.workspace }}:${{ github.workspace }} \
-w${{ github.workspace }} \
"jsii/superchain:node${{ matrix.node }}-nightly" \
Copy link
Contributor

Choose a reason for hiding this comment

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

You could have left ' here - the ${{}} stuff gets interpolated before the job runs.

@rix0rrr rix0rrr merged commit 6364d51 into main Mar 26, 2021
@rix0rrr rix0rrr deleted the huijbers/node14-take-2 branch March 26, 2021 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contribution/core This is a PR that came from AWS.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants