-
Notifications
You must be signed in to change notification settings - Fork 38
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
Add Build Image for dotnetcore3.1 #25
Conversation
b9476a7
to
8b32a16
Compare
I noticed now that other pull requests go against the
If I should rebase and point this elsewhere, please do let me know. |
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.
Thanks for submitting this PR!
If I should rebase and point this elsewhere, please do let me know.
We're indeed developing against develop
, sorry for the confusion! I've updated the docs.
2fddba4
to
495a501
Compare
495a501
to
f4ee642
Compare
Ecch, I'm not super adroit at rebasing across fork and branch, but I believe that's done it. Thanks so much! |
...and Get `make pr` to Work
- Suppress First-Time Run Messages - Redirect Nuget Warmup Output - Justify Nuget Warmup Procedure
Somehow, I failed to notice that the very next line was also setting environment variables.
...Which Is Compatible with aws-lambda-builders (a.k.a. `sam build`)
304cd44
to
42a3811
Compare
Co-authored-by: Chris Rehn <[email protected]>
The image is now available as |
...and Get
make pr
to WorkIssue #, if available: #13
Description of changes:
Adds a
dotnetcore3.1
build image in the style of the other build images – pulling its base from Public ECR as Python 3.9 does. The pre-invocation ofdotnet
is from LambCI, and attributed appropriately.Notes:
make pr
working correctly. I tried to keep the changes for that to a minimum.pytest
wants the unit tests to be run in random order. I don't know enough about it to know whether that plugin is loaded for everyone or just for me, so I did not add it.AWS_EXECUTION_ENV=AWS_Lambda_dotnetcore3.1
for the build image, but that should be set in the emulation image, or whatever it is that's used forsam local invoke
.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.