Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

CID/CD Pipeline to production after last failed

0

My pipeline failed because I have not approved nor disapproved the step from staging to production. I left it open and then I run a change in GitHub which started a new pipeline. All went correctly in this new pipeline and I approved the manual step between staging and production as staging was working fine.

However, as I went check production, it was still running the app version as of before the version I did not approve (nor disapprove).

Looking at the older pipeline, which was 5 days old already. I showed that step between stagging to production as failed. There are two buttons there: "try again" and "Repeat failed action" . Hit both but none of them had any effect.

I also tried "Execute again" and "interrupt execution".

Trying to "interrupt execution" gave the error message "The pipeline execution with ID xxxxx ' in 'pipeline-yyyy' can't be stopped now. Either it does not exist in the pipeline, or the pipeline execution has no action executions in progress.

Trying the "Execute again" gave me the erro messages "Source revisions can only be used with V2 pipelines." .

What can I do to have my pipeline back working into production?

Topics
Developer Tools
Tags
AWS CodePipeline
Language
English
asked 2 years ago578 views
2 Answers
0

If the pipeline execution is stuck and you cannot interrupt it from the console, you can try using the AWS CLI to terminate it.

aws codepipeline stop-pipeline-execution --pipeline-name pipeline-yyyy --pipeline-execution-id xxxxx --abandon

The --abandon flag ensures that the resources created by the execution are left intact, but the execution itself is stopped.

Then, you can manually start a new pipeline execution from the source or staging stage to ensure your latest changes are deployed to production.

aws codepipeline start-pipeline-execution --name pipeline-yyyy

When the pipeline reaches the manual approval step between staging and production, ensure you approve it in a timely manner.

EXPERT
answered 2 years ago
  • rePost-User-2570738
    2 years ago

    Thanks of the answer. I had tried that before, however without the --abandon . I tried it again as you mentioned but in both cases the response has been that the pipeline "can't be stopped now. Either it does not exist in the pipeline, or the pipeline execution has no action executions in progress.".

    I am trying to simply delete the pipeline and start all over again. I will be posting if I get a final result.

0

What SOLVED: Starting it all over...

I deleted the pipeline and the service and then init the service all over again.

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content