-
Notifications
You must be signed in to change notification settings - Fork 228
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
[ci] Add codebuild #2229
[ci] Add codebuild #2229
Conversation
0837f5a
to
157df56
Compare
Signed-off-by: Florian Zaruba <[email protected]>
157df56
to
23c3476
Compare
build: | ||
commands: | ||
- chown -R florian:florian . | ||
- su florian -c "source /synopsys/scripts/env.sh; echo $PATH" |
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.
Why doesn't this command require the runner to provide the password for user florian
? (When I type su mike -c "source...
I am prompted for my passwd.)
build: | ||
commands: | ||
- chown -R florian:florian . | ||
- su florian -c "source /synopsys/scripts/env.sh; echo $PATH" |
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.
Looking at log AWS logs I see this:
[Container] 2023/10/10 20:38:27 Running command su florian -c "source /synopsys/scripts/env.sh; echo $PATH"
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/codebuild/user/bin
It seems that "sourcing" the script does not propagate the env vars to the invoking shell. How about this:
commands:
- chown -R florian:florian .
- export VCS_HOME=/synopsys/vcs/S-2021.09-SP1
- export PATH=$VCS_HOME/bin:$PATH
- vcs -id
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.
If it works, please change whatever works! This PR is entirely yours now :-)
No description provided.