1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
2
I think you need to take a step back and review. When using CodePipeline there needs to be a source stage. The source stage will then produce an artifact which is passed to the CodeBuild stage.
Also, I am going to assume that you are using aws_codepipeline_actions and not pipelines CDK constructs. Personally, I prefer aws_codepipeline_actions since it provides more control.
Below is some typescript that shows how you could add the docker_build_project to a build action step. Notice it has a variable called "sourceOutput" which is the output from the prior step (not shown), which is the source stage. This "sourceOutput" is ultimately input to CodeBuild
const buildAction = new aws_codepipeline_actions.CodeBuildAction({
actionName: `actionname`,
docker_build_project,
input: sourceOutput,
outputs: [s3BucketArtifact],
});
Hope this helps, if it does please accept this answer.
con risposta 10 mesi fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 7 mesi fa
- AWS UFFICIALEAggiornata un anno fa
Thanks Bryant your suggestion pointed me in the right direction. I was conflating the CDK constructs and aws_codepipeline_actions mainly because I wanted to use the GitHubV2 connection method and at first the aws_codepipeline_actions did not look to support the CodeStarConnectionsSourceAction. Deeper down in the documentation there is a caveat where you can use the CodeStarConnectionsSourceAction with GitHub but you have to specify action_name="Bitbucket_Source".
That's great news, Simon! I am glad you have things going in the correct direction! Happy coding!