-
Notifications
You must be signed in to change notification settings - Fork 151
[SINT-4550] Use CI Identities in Windows CI Jobs #8033
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
bb03329
5a936be
dbe50ef
87ca563
6cccd33
6055f72
3f0c19f
ff11dce
19ddd69
37a05a1
91feb33
a1b6a60
347af18
d0bd32e
7d6fb50
0c2883c
2f7e2a3
3d90ff6
5f71017
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 | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -36,6 +36,10 @@ if "%nuke_args%"=="" ( | |||||||||
| exit /b 1 | ||||||||||
| ) | ||||||||||
|
|
||||||||||
| :: the CI Identities client will write the credentials to the path in the environment variable AWS_SHARED_CREDENTIALS_FILE, | ||||||||||
| :: and if the variable is not set, it will write to %USERPROFILE%\.aws\credentials | ||||||||||
| c:\devtools\ci-identities-gitlab-job-client.exe assume-role | ||||||||||
|
Member
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. Thinking about this more, this could fail, right? What happens if we can't assume the role? Does signing fail? Are we sure that would result in a failure of the build pipeline? Or should we be checking for a non-zero exit code here?
Suggested change
Member
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. If Right now, the CI job would still be able to do its job using these credentials, this is actually what made me lose some time during this PR because Now the reason why we are doing all of this is to remove permissions currently given to the instance profile, so one day the CI job will not be able to do its job if I would suggest that for now we don't fail the job if |
||||||||||
|
|
||||||||||
| dotnet run --project tracer/build/_build/_build.csproj -- %nuke_args% --Artifacts "build-out\%CI_JOB_ID%" | ||||||||||
|
|
||||||||||
| IF %ERRORLEVEL% NEQ 0 EXIT /B %ERRORLEVEL% | ||||||||||
|
|
||||||||||
This file was deleted.
This file was deleted.
This file was deleted.
Uh oh!
There was an error while loading. Please reload this page.