This repository has been archived by the owner on Feb 10, 2021. It is now read-only.
Feat azpipelines #190
Merged
Feat azpipelines #190
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tomation engine be az pipelines
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Incorporated a number of minor changes that allow for Azure Pipelines builds.
Where jenkins builds output properties to context.properties file and read the file regularly, Pipelines allows you to echo comments in such a way as to set a variable that is available in subsequent build steps. Because they aren't immediately available, we also export the variable to be available within the same step.
There is also currently an issue in Jekyll (jekyll/jekyll#7591) when run from Azure Pipelines that prevents the cache dir from creating (subsequently failing the build). I have implemented a minor change here to the creation of the "indir" temp directory to also create the child".jekyll-cache" at the same time, with the intention of reverting this once the issue has been deployed to jekyll proper (looks like its the next release).