Skip to content

Commit 9abd6df

Browse files
authored
Merge pull request #3 from aws4embeddedlinux/2023-11-21_doc
rename DemoPipeline to EmbeddedLinuxPipeline
2 parents ab273bf + d8614b3 commit 9abd6df

File tree

5 files changed

+54
-59
lines changed

5 files changed

+54
-59
lines changed

README.md

Lines changed: 18 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# aws4embeddedlinux-ci-examples
22

33
## Getting Started
4-
This repository shows ways to use the [aws4embeddedlinux-ci](https://github.com/aws4embeddedlinux/aws4embeddedlinux-ci.git) library.
4+
This repository shows ways to use the [aws4embeddedlinux-ci](https://github.com/aws4embeddedlinux/aws4embeddedlinux-ci.git) library.
55

66
In order to use these examples, you must setup [CDK](https://docs.aws.amazon.com/cdk/v2/guide/getting_started.html) including installing the CDK tool and bootstrapping the account you wish to deploy to. Additionally, you must have [Node](https://nodejs.org/en/) installed.
77

@@ -20,10 +20,10 @@ Note that while often CDK projects do not require separately invoking the build
2020
To deploy _all_ the pipeline examples, you can use the CDK deploy command:
2121

2222
```bash
23-
cdk deploy --all
23+
cdk deploy --all --require-approval never
2424
```
2525

26-
The pipelines can be found in the `Developer Tools > Code Pipeline > Pipelines` Console page. The newly created pipeline `ubuntu_22_04BuildImagePipeline` should start automatically. If not, it will need to be run before other pipelines will work correctly. Once it is complete, the DemoPipeline in the CodePipeline console page is ready to run.
26+
The pipelines can be found in the `Developer Tools > Code Pipeline > Pipelines` Console page. The newly created pipeline `ubuntu_22_04BuildImagePipeline` should start automatically. If not, it will need to be run before other pipelines will work correctly. Once it is complete, the EmbeddedLinuxPipeline in the CodePipeline console page is ready to run.
2727

2828
### Removing Pipelines
2929
The `cdk destroy` command can be used to remove individual pipelines and their related resources. This can also be done in the CloudFormation Console Page.
@@ -44,18 +44,29 @@ The recommended place to view this is from the `Developer Tools > Code Pipeline
4444
#### Using Kas
4545
The Kas example shows how to use a [Kas Config](https://github.com/aws4embeddedlinux/aws4embeddedlinux-ci/blob/main/source-repo/kas/kas.yml) to manage layers. This tool can help programatically manage layers and config with tighter Yocto integration than Git Submodules or the Repo tool.
4646

47-
See AWS CodeBuild pipeline: KasPipeline-DemoPipeline*
47+
See AWS CodeBuild pipeline: KasPipeline-EmbeddedLinuxPipeline*
4848

4949
#### A slightly modified version building a qemu pipeline:
50-
This example builds a Qemu based image using [meta-aws-demos](https://github.com/aws4embeddedlinux/meta-aws-demos). The Qemu image can be run in the CodeBuild environment. Using SLIRP networking, [OEQA testing](https://docs.yoctoproject.org/singleindex.html#performing-automated-runtime-testing) such as ptest can be run in the pipeline.
50+
This example builds a Qemu based image using [meta-aws-demos](https://github.com/aws4embeddedlinux/meta-aws-demos). The Qemu image can be run in the CodeBuild environment. Using SLIRP networking, [OEQA testing](https://docs.yoctoproject.org/singleindex.html#performing-automated-runtime-testing) such as ptest can be run in the pipeline.
5151

52-
See AWS CodeBuild pipeline: QemuDemoPipeline-DemoPipeline*
52+
See AWS CodeBuild pipeline: QemuEmbeddedLinuxPipeline-EmbeddedLinuxPipeline*
5353

5454
### A Poky Based EC2 AMI Pipeline
5555
Yocto can be used to create an EC2 AMI. This example builds an AMI based on Poky and meta-aws and exports it to your AMI registry using the [VM Import/Export Service](https://docs.aws.amazon.com/vm-import/latest/userguide/what-is-vmimport.html).
5656

5757
The pipeline name starts with `PokyAmiPipeline-` in the CodePipeline page.
5858

59+
### A NXP / IMX Pipeline
60+
This example will build an image for the [i.MX 6ULL EVK](https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/evaluation-kit-for-the-i-mx-6ull-and-6ulz-applications-processor:MCIMX6ULL-EVK) board.
61+
62+
Accepting the EULA is required. For this you need to uncomment the
63+
```
64+
# - EULA=y
65+
```
66+
line in the build.buildspec.yml file in the nxp-imx-layer-repo CodeCommit repo.
67+
68+
The pipeline name starts with `NxpImxPipeline-` in the CodePipeline page.
69+
5970
### Using pre-built, proprietary artifacts in a Pipeline
6071

6172
This example is based on this [work](https://elinux.org/R-Car/Boards/Yocto-Gen3/v5.9.0) to build an image for Renesas R-Car-H3 Starter Kit Premier (unofficial name - H3ULCB) board including the proprietary graphics and multimedia drivers from Renesas.
@@ -76,7 +87,7 @@ Create a folder named `proprietary` in the root of the source repo. Put those tw
7687

7788
Now a build should automatically start, succeed and you will get an image containing the proprietary graphics and multimedia drivers.
7889

79-
See AWS CodeBuild pipeline: RenesasPipeline-DemoPipeline*
90+
See AWS CodeBuild pipeline: RenesasPipeline-EmbeddedLinuxPipeline*
8091

8192
##
8293

Lines changed: 19 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
#!/usr/bin/env node
22
import * as cdk from "aws-cdk-lib";
33
import {
4-
DemoPipelineStack,
4+
EmbeddedLinuxPipelineStack,
55
BuildImageDataStack,
66
BuildImagePipelineStack,
77
BuildImageRepoStack,
@@ -57,7 +57,7 @@ const vpc = new PipelineNetworkStack(app, {
5757
/**
5858
* Create a poky distribution pipeline.
5959
*/
60-
new DemoPipelineStack(app, "PokyPipeline", {
60+
new EmbeddedLinuxPipelineStack(app, "PokyPipeline", {
6161
...defaultProps,
6262
imageRepo: buildImageRepo.repository,
6363
imageTag: ImageKind.Ubuntu22_04,
@@ -67,7 +67,7 @@ new DemoPipelineStack(app, "PokyPipeline", {
6767
/**
6868
* Create a meta-aws-demos pipeline for the Qemu example.
6969
*/
70-
new DemoPipelineStack(app, "QemuDemoPipeline", {
70+
new EmbeddedLinuxPipelineStack(app, "QemuEmbeddedLinuxPipeline", {
7171
...defaultProps,
7272
imageRepo: buildImageRepo.repository,
7373
imageTag: ImageKind.Ubuntu22_04,
@@ -79,7 +79,7 @@ new DemoPipelineStack(app, "QemuDemoPipeline", {
7979
/**
8080
* Create an AMI based on Poky.
8181
*/
82-
new DemoPipelineStack(app, "PokyAmiPipeline", {
82+
new EmbeddedLinuxPipelineStack(app, "PokyAmiPipeline", {
8383
...defaultProps,
8484
imageRepo: buildImageRepo.repository,
8585
imageTag: ImageKind.Ubuntu22_04,
@@ -91,7 +91,7 @@ new DemoPipelineStack(app, "PokyAmiPipeline", {
9191
/**
9292
* Create an kas based image.
9393
*/
94-
new DemoPipelineStack(app, "KasPipeline", {
94+
new EmbeddedLinuxPipelineStack(app, "KasPipeline", {
9595
...defaultProps,
9696
imageRepo: buildImageRepo.repository,
9797
imageTag: ImageKind.Ubuntu22_04,
@@ -101,13 +101,25 @@ new DemoPipelineStack(app, "KasPipeline", {
101101
});
102102

103103
/**
104-
* Create an renesas based image.
104+
* Create an renesas image.
105105
*/
106-
new DemoPipelineStack(app, "RenesasPipeline", {
106+
new EmbeddedLinuxPipelineStack(app, "RenesasPipeline", {
107107
...defaultProps,
108108
imageRepo: buildImageRepo.repository,
109109
imageTag: ImageKind.Ubuntu22_04,
110110
vpc: vpc.vpc,
111111
layerRepoName: "renesas-layer-repo",
112112
projectKind: ProjectKind.Renesas,
113113
});
114+
115+
/**
116+
* Create an nxp image.
117+
*/
118+
new EmbeddedLinuxPipelineStack(app, "NxpImxPipeline", {
119+
...defaultProps,
120+
imageRepo: buildImageRepo.repository,
121+
imageTag: ImageKind.Ubuntu22_04,
122+
vpc: vpc.vpc,
123+
layerRepoName: "nxp-imx-layer-repo",
124+
projectKind: ProjectKind.NxpImx,
125+
});

0 commit comments

Comments
 (0)