-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Run CI using image built in incubator-nuttx-testing and enable esp32 build #611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| # Licensed under the Apache License, Version 2.0 (the "License"); | ||
| # you may not use this file except in compliance with the License. | ||
| # You may obtain a copy of the License at | ||
| # | ||
| # http://www.apache.org/licenses/LICENSE-2.0 | ||
| # | ||
| # Unless required by applicable law or agreed to in writing, software | ||
| # distributed under the License is distributed on an "AS IS" BASIS, | ||
| # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| # See the License for the specific language governing permissions and | ||
| # limitations under the License. | ||
| # | ||
|
|
||
| name: ci-container | ||
| runs: | ||
| using: 'docker' | ||
| image: 'docker.pkg.github.com/apache/incubator-nuttx-testing/nuttx-ci-linux' | ||
| args: | ||
| - "-c" | ||
| - ${{ inputs.run }} | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,7 +18,6 @@ on: | |
| jobs: | ||
| check: | ||
| runs-on: ubuntu-18.04 | ||
| container: liuguo09/ubuntu-nuttx:18.04 | ||
|
|
||
| steps: | ||
| - name: Checkout nuttx repo | ||
|
|
@@ -60,12 +59,12 @@ jobs: | |
|
|
||
| build: | ||
| runs-on: ubuntu-18.04 | ||
| container: liuguo09/ubuntu-nuttx:18.04 | ||
| env: | ||
| DOCKER_BUILDKIT: 1 | ||
|
|
||
| strategy: | ||
| matrix: | ||
| boards: [arm-01, arm-02, arm-03, arm-04, arm-05, arm-06, arm-07, arm-08, arm-09, arm-10, arm-11, arm-12, arm-13, arm-14, arm-15, mips-riscv-x86, sim] | ||
|
|
||
| boards: [arm-01, arm-02, arm-03, arm-04, arm-05, arm-06, arm-07, arm-08, arm-09, arm-10, arm-11, arm-12, arm-13, arm-14, arm-15, mips-riscv-x86-xtensa, sim] | ||
| steps: | ||
| - name: Checkout nuttx repo | ||
| uses: actions/checkout@v2 | ||
|
|
@@ -91,7 +90,21 @@ jobs: | |
| repository: apache/incubator-nuttx-testing | ||
| path: testing | ||
|
|
||
| - name: Docker Login | ||
| uses: azure/docker-login@v1 | ||
| with: | ||
| login-server: docker.pkg.github.com | ||
| username: ${GITHUB_ACTOR} | ||
| password: ${{ secrets.GITHUB_TOKEN }} | ||
|
|
||
| - name: Run Pull Container | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "Run builds already use ci-container at line 104, why we need another similar "Run Pull Container"?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It is basically zero cost. I left this so that we can see what the time for pull is, I'm worried that this is going to get quite large so I want to be able to keep an eye on it outside of test execution. It will be local after this so the next step does not have to download again. |
||
| uses: ./nuttx/.github/actions/ci-container | ||
|
|
||
| - name: Run builds | ||
| run: | | ||
| cd testing | ||
| ./cibuild.sh -x testlist/${{matrix.boards}}.dat | ||
| uses: ./nuttx/.github/actions/ci-container | ||
| env: | ||
| BLOBDIR: /tools/blobs | ||
| with: | ||
| run: | | ||
| cd testing | ||
| ./cibuild.sh -x testlist/${{matrix.boards}}.dat | ||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add linux into the name to distinguish the upcoming windows doc?
And we need add copyright in this file too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll add the copyright, but I will probably just expose an input to the action so that it can have the correct container tag used. I would like to wait until we know how that will work, I have not done windows builds in a container via github actions, I have only done them on the runner directly.