* Run the link verification step even previous step failed.
* Make the tab right
* Address comments
* Run default condition if no RunOnFailure set.
* Changed back to simple condition
Co-authored-by: Sima Zhu <sizhu@microsoft.com>
* Disable dependency on azure-core until azure-core releases to vcpkg.
* Remove release artifact creation script and pipeline step
* Copy items from root cmake generate outputs (no need to do individual project preparation)
* Space
* Add VcpkgPortName (package port names may change in the future to include non v1 version numbers like azure-template-cpp-v2)
* Destination should be artifact name, not vcpkg port name
* Disable PR steps
* SHA512 1 -> SHA512 %SHA512%
* New release procedure
* Unblock publishing process
* Increment azure-template version
* Update branch strategy, uncomment final release of template
* Increment version to test release
* Fix remote branch checkout logic
* Increment version
* Exit successfully
* Increment version
* Increment Version
* Version Increment
* Add a difference in the output file to validate multiple runs against a target PR branch
* Enable existing PR branches in create-pull-request.yml
* Increment version
* Fix archetype-cpp-release.yml syntax
* Skip checkout instead
* Increment version
* Fix automated version incrementing
* Increment version
* Update CHANGELOG.md
* Update CHANGELOG.md date
* Revert CONTROL file
* Remove Build-Depends
* Increment version
* Output commands
* Check out branch in either branch scenario
* Increment version
* Fetch the .tar.gz file using convention, the REST API does not give the location of the .tar.gz
* Increment Version
* ToLower
* Increment
* Increment version
* Version updater should not append a new line to the end of the file contents (existing new line at the end of the file will remain, if present)
* Add azure-template2 to validate base case of shipping different packages instead of file replacement validation from previous runs
* Remove extra backtick
* Add template2 to root CMakeLists.txt
* Review feedback: Support main scenario with packages coming from different location (no new file conflicts)
* Remove file blocking link check step. This is ok because the whole azure-template2 folder will be removed after this verification is complete
* Version increment
* Make template2 install in different locations
* Increment version
* Remove azure-template2 that was used for validating publishing multiple packages
* Remove template2 from ci.yml
* Use "SHA512 1" syntax as proposed by vcpkg documentation and regex replacement
* Review feedback
* Increment version
* Quotes
* Review feedback and re-add New-ReleaseAsset.ps1
* Make the user agent configurable.
* Address comments
* Default to current Chrome version
* Revert the yaml file changes
Co-authored-by: Sima Zhu <sizhu@microsoft.com>
* Update latest folder with one index.html includes the redirect links
* Update the redirect links and remove everything in latest
* Address feedback
* Have the entire copy for latest GA.
Co-authored-by: Sima Zhu <sizhu@microsoft.com>
- Add set of helpers to work with devops work items
- Add script to create devops release package items
- Update SemVer to support version type
Co-authored-by: Wes Haggard <Wes.Haggard@microsoft.com>
* Support alpha and azure pipeline build version formats for SemVer parsing and sorting
* Minor build number fixes
* Support zero-padding of build versions more generically in SemVer script
* Fix pre-release label conditional for HasValidPrereleaseLabel in semver script
* Set default convention for build number separator in semver script
Co-authored-by: Ben Broderick Phillips <bebroder@microsoft.com>
* reformatted parameter arguments to both update-docs scripts. added parameter requirements and renamed CIRepository to DocRepoLocation which is a lot clearer. Added additional CIConfig parameter to update-docs-metadata to support specific write locations per moniker.
Co-authored-by: scbedd <45376673+scbedd@users.noreply.github.com>
* Fixed the docindex.yml and rename the files
* Reset the mutated changes
* Force checkout as the changes have already copied out
* Minor changes for parameters
* Update Generate-DocIndex.ps1
* Update Generate-DocIndex.ps1
* Update Generate-DocIndex.ps1
* Added function to common
* Update Generate-DocIndex.ps1
Co-authored-by: Sima Zhu <sizhu@microsoft.com>
Co-authored-by: Sima Zhu <48036328+sima-zhu@users.noreply.github.com>
* Move entire docgeneration into common tools
* Move docindex to common
* Added the package replacement logic
* Fixed on parameters
* Fixed param
* Change function to dash
* Added regex on function
* Added display name.
* Update eng/common/docgeneration/Generate-DocIndex.ps1
Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>
* Deal with js
* Add no new line args
* revert some test changes
* Need to default to the double quotes for JS regex
* Update Generate-DocIndex.ps1
* Added the appTitle
* type
Co-authored-by: Sima Zhu <sizhu@microsoft.com>
Co-authored-by: Sima Zhu <48036328+sima-zhu@users.noreply.github.com>
Co-authored-by: Wes Haggard <weshaggard@users.noreply.github.com>
Root Cause:
Storage project generates coverage files in a different location (sdk/*/*cov_xml.xml) from where Core and Template (sdk/*/*/*cov_xml.xml). Basically one level up.
When I added the coverage for Storage, I didn’t know we were also running live tests for Core and Template pipelines. It failed on them because the xml files were not found.
In the PR, I add a new parameter to pipelines to change the default path, and also I am disabling LiveTests from Core and Template, since it only runs the same thing that we run on CI pipelines (We can enable it if we ever have some live tests)
fix: #1001
