On This Page
AWS CodePipeline is a fully managed continuous delivery service that helps you automate your release pipelines for fast and reliable application and infrastructure updates.
CodePipeline automates the build, test, and deploy phases of your release process every time there is a code change, based on the release model you define.
You can easily integrate AWS CodePipeline with third-party services such as GitHub or with your own custom plugin. With AWS CodePipeline, you only pay for what you use.
- Travis CI.
- Azure DevOps Server.
- Google Cloud Build.
A workflow that describes how software changes go through the release process.
- Files or changes that will be worked on by the actions and stages in the pipeline.
- Each pipeline stage can create “artifacts”.
- Artifacts are passed, stored in Amazon S3, and then passed on to the next stage.
- Pipelines are broken up into stages, e.g., build stage, deployment stage.
- Each stage can have sequential actions and or parallel actions.
- Stage examples would be build, test, deploy, load test etc.
- Manual approval can be defined at any stage.
Stages contain at least one action, these actions take some action on artifacts and will have artifacts as either an input, and output, or both.
The progressing from one stage to another inside of a pipeline.
You are configuring a Jenkins project that is installed on an Amazon EC2 instance running a Windows operating system. You want this Jenkins project to integrate with AWS CodePipeline.
Which actions should you take to make this function perform correctly? (2 answers)
- Restart all Amazon EC2 instances that are running a Windows operating system.
- Provide the IAM user credentials to integrate AWS CodePipeline.
- Fill out the required fields for your proxy host.
- Modify the PATH variable to include the directory where you installed Jenkins on all Amazon EC2 instance that are running a Windows operating system.