-
Notifications
You must be signed in to change notification settings - Fork 426
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
Unable to use test_commands in my pipeline #4768
Comments
Hi @qnm, thanks for reporting this issue. Do you think you could share a little more information about your setup? For example, did you recently upgrade your Copilot version? And could you share the buildspec.yml which was generated by the If you've recently upgraded your Copilot version you may be getting bit by a mismatch between the docker version in the buildspec (18, last supported by AL2 Standard 2.0 Codebuild image and specified by default on Copilot <=1.13.0) and the docker versions available to the current Codebuild image (AL2 Standard 4.0). The fix would be to update the docker version in your buildspec.yml to 20. |
This could be the lines that needs updating? copilot-cli/internal/pkg/template/templates/cicd/pipeline_cfn.yml Lines 302 to 304 in e1afe39
Manually trying to override/add version 20 in the buildspec does not work. |
For ⬆️ issue by @lominming, see #4721! |
This issue is stale because it has been open 60 days with no response activity, and is tagged with |
This issue is closed due to inactivity. Feel free to reopen the issue if you have any follow-ups! |
Hi,
I have configured a pipeline with a
test_commands
option which I intend to use to notify systems of a deployment.I have run
copilot pipeline update
which I think ensures the latest template.Having added a basic command to the YML, I am seeing the following error:
Buildspec contains:
Manifest contains:
The file
bin/deploy-integration-completed
is executable and contains a call toenv
only.I'm not using anything other than the defaults, and a custom ruby version using
rbenv
The text was updated successfully, but these errors were encountered: