Fixing CI failures for AzureFunctionOnKubernetesV0 and PublishPipelineMetadataV0 tasks #12042
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
…eMetadataV0 tasks
ajinkya599
force-pushed
the
users/aj/azFuncK8s-Publishmetadata-ci-failures
branch
from
08e4e5f to
9664163
Compare
thesattiraju
approved these changes
Dec 27, 2019
ajinkya599
added a commit
that referenced
this pull request
Jan 13, 2020
…eMetadataV0 tasks (#12042)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Explicitly specifying @types/node version in package.json. It seems that a higher version dependency is causing the build failures.