Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR setup nightly build, what we have:
Directory.Build.props
withNerdbank.GitVersioning
ref for git versioning and setup ofPackageOutputPath
coverlet.collector.csproj
to use custom nuspec so we can also cleanupbuild.proj
eng/nightly.ps1
I know that we could use AZP to do all works(build artifacts and release)...but for now I prefer use what we have on master...and in future step by step we'll refactor build with @AArnott advices, pinned sdk for generic build and test with multi SDK locally testable.Script accept 2 params
-apiKey xxx and -source https://...
I tested all workflow on https://nugetservercoverlet.azurewebsites.net/ and it works well.@tonerdo you must setup variable with myget credentials like
Here you can see tests log https://marcorossignoli.visualstudio.com/githubazp/_build/results?buildId=765
YAML ignore errors, because if we don't have new commit on master
donet nuget push
fails for "package already present".global.json
fist step of @AArnott advice, this update does not conflicts with Make build more coherent with same "dotnet sdk" on all CI machine. #396 because there we useDOTNET_MULTILEVEL_LOOKUP=0
BTW after this merge we'll have to override
build.proj
with new one, but I look forward to fix that@toni after merge you need to create a new "Scheduled" pipeline(
![image](https://user-images.githubusercontent.com/7894084/58383271-f616e280-7fd4-11e9-8f63-8cad5a22e657.png)
eng/azure-pipelines-nightly.yml
) by hand likeScheduled trigger is not yet supported with YAML https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops&tabs=yaml#scheduled-triggers
To local test
Format will be
coverlet.collector.1.0.0-g2478511111.nupkg
where2478511111
is the first n part of last commit. Using scripts https://github.com/AArnott/Nerdbank.GitVersioning/tree/master/src/Nerdbank.GitVersioning.Tasks/tools we can translate version to commit.cc: @vagisha-nidhi
PS. A mega-huge thank's to @AArnott and @onovotny for the tool and help with setup, very appreciated!