Skip to content
This repository has been archived by the owner on Feb 15, 2024. It is now read-only.

NodeJS verison in buildspec #58

Open
s1mrankaur opened this issue Mar 13, 2021 · 1 comment
Open

NodeJS verison in buildspec #58

s1mrankaur opened this issue Mar 13, 2021 · 1 comment
Assignees
Labels
question Further information is requested wontfix This will not be worked on

Comments

@s1mrankaur
Copy link

[Container] 2021/03/13 02:58:08 Waiting for agent ping
2 | [Container] 2021/03/13 02:58:11 Waiting for DOWNLOAD_SOURCE
3 | [Container] 2021/03/13 02:58:12 Phase is DOWNLOAD_SOURCE
4 | [Container] 2021/03/13 02:58:12 CODEBUILD_SRC_DIR=/codebuild/output/src418621371/src
5 | [Container] 2021/03/13 02:58:12 YAML location is /codebuild/readonly/buildspec.yml
6 | [Container] 2021/03/13 02:58:12 No commands found for phase name: install
7 | [Container] 2021/03/13 02:58:12 Processing environment variables
8 | [Container] 2021/03/13 02:58:12 Selecting 'nodejs' runtime version '15' based on manual selections...
9 | [Container] 2021/03/13 02:58:12 Phase complete: DOWNLOAD_SOURCE State: FAILED
10 | [Container] 2021/03/13 02:58:12 Phase context status code: YAML_FILE_ERROR Message: Unknown runtime version named '15' of nodejs. This build image has the following versions: 10, 12

We are using node 15 in our application that will be deployed with the CICD. I tried to set


          install: {
            'runtime-versions': {
              nodejs: '15'
            }
          },

but get the error:
10 | [Container] 2021/03/13 02:58:12 Phase context status code: YAML_FILE_ERROR Message: Unknown runtime version named '15' of nodejs. This build image has the following versions: 10, 12

Why is that? Can we not use node15?

@srijitm srijitm self-assigned this Mar 15, 2021
@srijitm srijitm added question Further information is requested wontfix This will not be worked on labels Mar 15, 2021
@srijitm
Copy link
Contributor

srijitm commented Mar 15, 2021

You can see what CodeBuild supports here: https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html

You have two options:

  1. Provide node installation commands in your build/test/deploy.sh scripts.
  2. Provide a customer docker image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants