-
Notifications
You must be signed in to change notification settings - Fork 12
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
Start improving local deployments #136
base: master
Are you sure you want to change the base?
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,4 @@ | ||
## Development information | ||
|
||
You can build locally the extension by using ./dotnet/build-packages-local.sh | ||
It will both build the application and upload to a dev nuget feed that you can use on your app. This feed can be used by setting the variable `SCM_SITEEXTENSIONS_FEED_URL` to `https://pkgs.dev.azure.com/datadoghq/dd-trace-dotnet/_packaging/Public_Feed/nuget/v2` in your app. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
INSTALL_SHA="38787d2e9cadd408f541675e95fab7b9a687d559" | ||
PACKAGE_BUILD_VERSION="0.2.659679454" | ||
|
||
# Handle later the possibility to use a local commit | ||
./dotnet/build-packages-dev.sh $PACKAGE_BUILD_VERSION $INSTALL_SHA | ||
# SET AZDO_PAT in external env variable as it's a secret | ||
./dotnet/upload-dev-nuget.sh $PACKAGE_BUILD_VERSION $AZDO_PAT |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
dev_version="$1" | ||
AZDO_PAT=$2 | ||
|
||
dotnet nuget add source https://pkgs.dev.azure.com/datadoghq/dd-trace-dotnet/_packaging/Public_Feed/nuget/v3/index.json --name Public_Feed --username any_string --password $AZDO_PAT --store-password-in-clear-text | ||
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'm wary of using this ever since I've been burnt in the past as artifiacts go in, are never removed, use up your allowance, and kill all CI... so on your head be-it 😛 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. 🤔 , Thanks for raising this, I didn't see this as a potential issue. 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 may just be scare-mongering, it's just something I avoid in personal projects now 🙂 Oh wait... maybe that was GitHub... pfft, I forget 😂 |
||
dotnet nuget push package/DevelopmentVerification.DdDotNet.Apm.$dev_version.nupkg --source Public_Feed --api-key any_string |
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 get how the SHA is set for the GitHub Action, but is this also supposed to work right with a local dev build or is that out of scope?
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.
That's out of scope. As said in the description, 2 things are not yet handled: use a local tracer, and modify where the files are modified to avoid having to revert modified files (as the build process do a lot of sed to change the version)