Prerequisites Step 1: Create source files and push to your GitHub repository Step 2: Create your pipeline Step 3: Run your pipeline and verify build commands

Tutorial: Create a pipeline that runs commands with compute

In this tutorial, you configure a pipeline that continuously runs provided build commands using the Commands action in a build stage. For more information about the Commands action, see Commands action reference.

Important

As part of creating a pipeline, an S3 artifact bucket provided by the customer will be used by CodePipeline for artifacts. (This is different from the bucket used for an S3 source action.) If the S3 artifact bucket is in a different account from the account for your pipeline, make sure that the S3 artifact bucket is owned by AWS accounts that are safe and will be dependable.

Prerequisites

You must already have the following:

A GitHub repository. You can use the GitHub repository you created in Tutorial: Use full clone with a GitHub pipeline source.

Step 1: Create source files and push to your GitHub repository

In this section, you create and push your example source files to the repository that the pipeline uses for your source stage. For this example, you produce and push the following:

A README.txt file.

To create source files

Create a file with the following text:
```
Sample readme file
```
Save the file as README.txt.

To push files to your GitHub repository

Push or upload the files to your repository. These files are the source artifact created by the Create Pipeline wizard for your deployment action in AWS CodePipeline. Your files should look like this in your local directory:
```
README.txt
```
To use the Git command line from a cloned repository on your local computer:
1. Run the following command to stage all of your files at once:
```
git add -A
```
2. Run the following command to commit the files with a commit message.
```
git commit -m "Added source files"
```
3. Run the following command to push the files from your local repo to your repository:
```
git push
```

Step 2: Create your pipeline

In this section, you create a pipeline with the following actions:

A source stage with a GitHub (Version 2) action for the repository where the source files are stored.
A build stage with the Commands action.

To create a pipeline with the wizard

Sign in to the AWS Management Console and open the CodePipeline console at http://console.aws.amazon.com/codesuite/codepipeline/home.
On the Welcome page, Getting started page, or the Pipelines page, choose Create pipeline.
On the Step 1: Choose creation option page, under Creation options, choose the Build custom pipeline option. Choose Next.
In Step 2: Choose pipeline settings, in Pipeline name, enter MyCommandsPipeline.
CodePipeline provides V1 and V2 type pipelines, which differ in characteristics and price. The V2 type is the only type you can choose in the console. For more information, see pipeline types. For information about pricing for CodePipeline, see Pricing.
In Service role, choose New service role to allow CodePipeline to create a service role in IAM.
Note
If you are using an existing service role, to use the Commands action, you will need to add the following permissions for the service role. Scope down the permissions to the pipeline resource level by using resource-based permissions in the service role policy statement. For more information, see the policy example in Service role policy permissions.
- logs:CreateLogGroup
- logs:CreateLogStream
- logs:PutLogEvents
Leave the settings under Advanced settings at their defaults, and then choose Next.
In Step 3: Add source stage, in Source provider, choose AWS CodeCommit. In Repository name, choose the name of the CodeCommit repository you created in Step 1: Create a CodeCommit repository. In Branch name, choose the name of the branch that contains your latest code update.

After you select the repository name and branch, a message shows the Amazon CloudWatch Events rule to be created for this pipeline.

Choose Next.
In Step 4: Add build stage, choose Commands.

Note
Running the Commands action will incur separate charges in AWS CodeBuild.

Enter the following commands:
```
ls
echo hello world
cat README.txt
echo pipeline Execution Id is #{codepipeline.PipelineExecutionId}
```
Choose Next.
Choose to skip the Deploy step.

Choose Next.
In Step 6: Review, review the information, and then choose Create pipeline.
As a final step for creating your action, add an environment variable to the action that will result in an output variable for the action. On the Commands action, choose Edit. On the Edit screen, specify a variable namespace for your action by entering compute in the Variable namespace field.

Add the CodeBuild output variable AWS_Default_Region, and then choose Add variable.

Step 3: Run your pipeline and verify build commands

Release a change to run your pipeline. Verify that the build commands ran by viewing the execution history, the build logs, and the output variables.

To view action logs and output variables

After the pipeline runs successfully, you can view the logs and output for the action.
To view the output variables for the action, choose History, and then choose Timeline.

View the output variable that was added to the action. The output for the Commands action shows the output variable resolved to the action Region.
To view the logs for the action, choose View details on the successful Commands action. View the logs for the Commands action.