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 adds support for running cake.recipe on AzurePipelines with all main features. (another part of #259)
Test run on AzurePipelines you can check here, which is built from custom branch in fork
Changes:
Number
property ofIBuildInfo
interface was changed fromint
tostring
(BuildNumber on AzurePipelines is string)IBuildProvider
interface is extended byUploadArtifact(FilePath file)
methodIBuildProvider
for AzurePipelinesUploadAppVeyorArtifactsTask
renamed toUploadArtifactsTask
("Upload-AppVeyor-Artifacts" -> "Upload-Artifacts")Open questions:
AppVeyor
. I didn't rename it due to backward compatibility. What we need to do it with it, because if I want to run my cake on AzurePipelines with Cake.Recipe I need to callAppVeyour
target, which is a litle bit confusing.