Set up CI with Azure Pipelines #14
Merged
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
Move pipeline definition to ci subfolder
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.
Adds Azure DevOps Build pipeline definition to a new
cisubfolder.In order to properly forward linting warnings and errors produced by ESLint, the
cisubfolder contains theci-lint.ps1PowerShell script that is executed by the build agent. Theci-lint.ps1script parses the JSON output from ESLint and formats proper##vso[task.logissue]messages that Azure understands. See couven92/dust-webapp -- Build 35 (2019-01-17-rev15) for an example how linting errors are displayed. I added a task that downloads theLoggingCommandFunctions.ps1file from the offical Microsoft Azure Pipelines Task SDK repository for that purpose.The CI build produces the a build artifact which can be downloaded once the build succeeds. It contains the output produced from running the
npm run buildscript.@Pwntus I'll help you set up the build pipeline on your Azure DevOps account, since it's your repo, you should also own the Build Pipeline. Note: The build pipeline depends on a secure file
.env.localthat must be added to the Azure DevOps Build Library.