-
Notifications
You must be signed in to change notification settings - Fork 233
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
Prototype VCS CI running on AWS #2236
base: master
Are you sure you want to change the base?
Changes from all commits
23c3476
f1e490f
026e84b
de472eb
92362a3
6dc6070
49de774
dfe0c3d
32bc0a6
ee399c8
4f1db65
a544267
fadd215
953ffe7
6c192d5
550341c
60ae70a
7edd4d0
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,28 @@ | ||
name: aws | ||
on: push | ||
|
||
# on: | ||
# push: | ||
# branches: | ||
# - 'dev' | ||
|
||
jobs: | ||
aws: | ||
name: AWS Pipeline (private) | ||
if: github.actor == 'davideschiavone' || github.actor == 'MikeOpenHWGroup' || github.actor == 'zarubaf' | ||
runs-on: ubuntu-latest | ||
# These permissions are needed to interact with GitHub's OIDC Token endpoint. | ||
permissions: | ||
id-token: write | ||
contents: read | ||
steps: | ||
- name: Configure AWS Credentials | ||
uses: aws-actions/configure-aws-credentials@v4 | ||
with: | ||
role-to-assume: ${{ secrets.AWS_ROLE_TO_ASSUME }} | ||
aws-region: eu-west-1 | ||
- name: Run AWS Pipeline | ||
uses: aws-actions/aws-codebuild-run-build@v1 | ||
with: | ||
project-name: core-v-verif | ||
hide-cloudwatch-logs: true |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
# Copyright 2023, OpenHW Group | ||
# SPDX-License-Identifier:Apache-2.0 WITH SHL-2.0 | ||
# | ||
# Build-specification for the aws.yml workflow. | ||
|
||
version: 0.2 | ||
|
||
phases: | ||
|
||
build: | ||
commands: | ||
- chown -R florian:florian . | ||
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. I do not fully comprehend everything here, but are these scripts tied to a specific users account? should/could this be generalized? 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. This is a good question. The CI runs on a AWS VM instance that only OpenHW staff have access to. It could be any of us, but it cannot be "just anyone". It probably makes sense to create a generic "openhw-ci-runner" account that has its access privileges tuned to the CI requirements (and no more). |
||
# - su florian -c "source /synopsys/scripts/env.sh; echo $PATH" | ||
# VCS environment | ||
- yum -y install gcc gcc-c++ make | ||
- export VCS_HOME=/synopsys/vcs/S-2021.09-SP1 | ||
- export PATH=$VCS_HOME/bin:$PATH | ||
- vcs -id | ||
# - export LM_LICENSE_FILE=29000@ip-172-31-46-244 | ||
- export SNPSLMD_LICENSE_FILE=27020@ip-172-31-46-244.eu-west-1.compute.internal | ||
# Questasim (vsim) environment | ||
# - export QUESTAROOT=/onespin/questasim | ||
# - export LM_LICENSE_FILE=29000@ip-172-31-46-244 | ||
# - export PATH=${QUESTAROOT}/bin:${PATH} | ||
# - export MTI_VCO_MODE=64 | ||
# - wget https://buildbot.embecosm.com/job/corev-gcc-centos7/19/artifact/corev-openhw-gcc-centos7-20230905.tar.gz | ||
Comment on lines
+21
to
+26
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. Maybe remove the commented lines? 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. Yes, the commented lines will be removed before the Draft status of this PR is dropped. These were left in place to show you what I did to get Questasim (vsim) to run. It did not work. Perhaps the value of |
||
- curl -O https://buildbot.embecosm.com/job/corev-gcc-centos7/19/artifact/corev-openhw-gcc-centos7-20230905.tar.gz | ||
- tar xf corev-openhw-gcc-centos7-20230905.tar.gz | ||
- export HERE=`pwd` | ||
- export CV_SW_TOOLCHAIN=$HERE/corev-openhw-gcc-centos7-20230905 | ||
- export CV_SW_PREFIX=riscv32-corev-elf- | ||
- export CV_SW_MARCH=rv32imc_zicsr_zifencei | ||
- corev-openhw-gcc-centos7-20230905/bin/riscv32-corev-elf-gcc --version | ||
# - cd cv32e40p/sim/uvmt | ||
# - make test USE_ISS=0 SIMULATOR=vcs TEST=hello-world | ||
- cd bin | ||
- ./ci_check --batch --iss 0 --simulator vcs --core cv32e40p |
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.
You might want to change that, depending on when to trigger the job. Most l likely on PRs to
dev
I guess?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.
Yes, you are correct. I will be discussing the details of this with @rickoco (to understand our legal constraints) and the Members (to understand their expectations) and will update the trigger accordingly.
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 think it relates to the process which had been setup for cv32e40p: https://github.com/openhwgroup/cv32e40p#contributing