* Upload logs on cmake generate/build failure
* Copy relevant files to staging location, clean up after publishing
* Update cspell words
* Test: break cmake generate in a way that'll produce SOME log files.
* Revert "Test: break cmake generate in a way that'll produce SOME log files."
This reverts commit d5a300587b3359ed3f2bf7be5abea40868f958a7.
* Show failure logs instead of uploading artifacts. Only show log files for vcpkg at this time
* Reapply "Test: break cmake generate in a way that'll produce SOME log files."
This reverts commit 582629ad587f3c9b652ac1f8a7eda5e12d46843a.
* Revert "Reapply "Test: break cmake generate in a way that'll produce SOME log files.""
This reverts commit 7a35250c7e598fc6e1c060f896cbc952704e40bf.
* Another type of test
* Revert inadvertent whitespace changes
* Revert "Another type of test"
This reverts commit e38013f95b152e4e2a3b9d27ccf1eb9b63fa1817.
* More logging
* First cut at snippet generation - markdown files only for now.
* Removed trailing blank lines in updated file
* Use snippet generator for keyvault snippets
* lll
* sss
* oipio
* vcvc
* enable test proxy start at test suite start for KV and storage , example created for attestation, we cannot find the base definitions for the test suites,
* Contrib
* clangs
* clangs
* test logs
* pipeline
* more clangs
* pipeline
* clang
* try try again
* try try again
* try again
* try again
* again
* update paths , moved to macro , call macro in target code
* core
* capitalization
* Added ability to switch to OpenSSL 1.1.1n
* Fixed OpenSSL compilation challenges - the CRL stuff works now
* Added instructions on using OpenSSL 1.1.1 to README
* Added vcpkg args to handle openssl variants
* Pulled WebSocket fixes into main except for WebSockets functionality
Co-authored-by: Rick Winter <rick.winter@microsoft.com>
Co-authored-by: Daniel Jurek <djurek@microsoft.com>
Co-authored-by: George Arama <50641385+gearama@users.noreply.github.com>
Co-authored-by: Ahson Khan <ahson_ahmedk@yahoo.com>
Co-authored-by: Ben Broderick Phillips <bebroder@microsoft.com>
Co-authored-by: Anton Kolesnyk <antkmsft@users.noreply.github.com>
* Expiration time, eliminate AzureRm warning, condition on Set-VcpkgWriteModeCache
* Attempt uninstalling AzureRM and installing Az.Storage
* Import PSModule-Helpers.ps1
* Unsintall-AzureRm if the function exists
* Get-Command
* Uninstall-Module Azure.Storage
* Log
* quotes
* Get-Command some more
* Format list
* Alias fun
* Naming
* show PSModulePath
* Attempt to handle module double backslash
* do not observe
* do not observe for real
* Spelling
* Empty commit to re-trigger CI with a full matrix
* Script that automates updating vcpkg betas
* Wire up to pipeline
* Spelling, commentary
* Clone into repo name
* Remove-Item requires the path to exist, even if -Force is specified
* Bootstrap vcpkg
* Arguments to Test-ShouldReleaseToVcpkg.ps1
* More commit
* Escape quotes
* Quote git commit
* Set strict mode
* Use tags
* Actually tag
* Run git commands
* Invoke-Expression
* Onboard releasing package to vcpkg before attempting to isntall from overaly
* temporarily disable matrix generation (30s tasks sometimes runs for 20+ minutes)
* Test-ShouldReleaseToVcpkg.ps1
* Test-Path
* Test vcpkg build, also ensure we push
* Just the tags... low probabiltiy of success given that '--' if frequently treated as a separator
* Add ability to skip link verification for tighter inner loop
* Push tag separately
* Unnecessary condition and conjunction
* Base repo owner: Azure
* Specify remote name
* Tighten inner loop
* git remote -v
* workingDirectory
* Go back to two tags and a regular push
* Saving some progress
* Use original push method
* BaseRepoOwner
* Cleanup, put changes in the default branch (vcpkg does not look at refs outside of the default branch)
* Use default branch
* Revert changes used to tighten up devops inner loop
* Revert an unrelated change
* Revert unrelated changes
* Revert unrelated changes
* Add spelling
* Script that automates updating vcpkg betas
* Wire up to pipeline
* Spelling, commentary
* Clone into repo name
* Remove-Item requires the path to exist, even if -Force is specified
* Bootstrap vcpkg
* Arguments to Test-ShouldReleaseToVcpkg.ps1
* More commit
* Escape quotes
* Quote git commit
* Set strict mode
* Use tags
* Actually tag
* Run git commands
* Invoke-Expression
* Onboard releasing package to vcpkg before attempting to isntall from overaly
* temporarily disable matrix generation (30s tasks sometimes runs for 20+ minutes)
* Test-ShouldReleaseToVcpkg.ps1
* Test-Path
* Test vcpkg build, also ensure we push
* Just the tags... low probability of success given that '--' if frequently treated as a separator
* Add ability to skip link verification for tighter inner loop
* Push tag separately
* Unnecessary condition and conjunction
* Base repo owner: Azure
* Specify remote name
* Tighten inner loop
* git remote -v
* workingDirectory
* Go back to two tags and a regular push
* Saving some progress
* Use original push method
* BaseRepoOwner
* Cleanup, put changes in the default branch (vcpkg does not look at refs outside of the default branch)
* Use default branch
* binary cache and manifest
* update packages
* udpate
* add cache to private pipeline
* next try
* aver
* other
* again
* aver quick
* more
* this way
* again
* one more
* print
* test
* use depend
* more deps
* dep
* Apply suggestions from code review
Co-authored-by: Daniel Jurek <djurek@microsoft.com>
* updated to use group variable
* update identity
* end line
* Update vcpkg.json
* Apply suggestions from code review
* cspell
* remove comment
* updates
* make cache mode depend on SAS env var
* map env var only for internal pipelines
* other approach
* what about this
* and this
* try
* amd
* another
* extra step
* typo
* override for internal
* use default succeded
* azure core update manifest
* a
* run cmake-generate nightly as well
* check for SAS
* check cache
* no secret
* fix is secret
* pass explicit
* use secret all the time
* char
* One more
* export
* echos
* last
* array
* remove question
* ok
* weird
* use account key
* substring
* VCPKG_BINARY_SOURCES
* Add module installation
* task:
* Correct pathing for module
* update source gen
* format
* update spelling
* IsWindoows
* Use pwsh
* Cannot clobber with PSModule-Helpers. Attempt plain install
* Attempt plain install
* Revert unnecessary change to Update-DocsMsToc.ps1
* template ready
* curl is required on Windows as well for some CI gates
* attestation
* fix format
Co-authored-by: Daniel Jurek <djurek@microsoft.com>
* Output binary sizes (Get-BinarySizes.ps1 works for linux environment)
* Add better support for Windows binary output
* Update matrix to properly build Debug and Release on Windows
* Add TEAMPROJECTID to spell check
* Add extra labels
* Ensure BuildArgs doesn't get duplicated
* Log additional metrics
* Add openssl to Win32Api_curl
* SourceBranchName -> SourceBranch
* Fix matrix entries
* Document included
* Review feedback for Get-BinarySizes.ps1
* Infer many metrics from the environment
* Add issecret to cspell.json
* Extra equal signs
* Correct directory depth for $BuildDirectory
* Correct casing for mac VM image
* Put dependency versions
* Update version
* Core does not have any 1.1 functionality
* Core 1.1
* 1.1.0
Co-authored-by: Anton Kolesnyk <antkmsft@users.noreply.github.com>
* vcpkg.json -- update all links to point to "main" .. This is hardcoded and will go out in future releases.
* ci.yml -- add `- main` to trigger criteria near `- master` ... This adds forward compatilbitiy when we rename the branch in the repo
* archetype-cpp-release.yml use a script which evaluates a repo's default branch and sets that in a global variable, then use that variable instead. When vcpkg updates their branch the publishing scripts will work transparently.
* Collect-Changelogs.ps1 -- Add default hardcoded branch name for use with future releases. This can be optionally overridden with a parameter when invoking the script.
* eng/pipelines/client.yml -- Delete this file. It is no longer in use.
Part of https://github.com/Azure/azure-sdk-for-cpp/issues/1277, checking what types of warnings the CI emits.
Verified all SDK product `.cpp`, `.hpp`, `.txt`, and `.md` files, primarily focused on azure-core. They are all clean now. There are some exceptions that needs to be added for keyvault and storage, but they are false positives, so not a concern.
> `cspell lint --config .vscode/cspell.json *.hpp */**/*.hpp`
CSpell: Files checked: 188, Issues found: 0 in 0 files
> `cspell lint --config .vscode/cspell.json *.cpp */**/*.cpp`
CSpell: Files checked: 186, Issues found: 88 in 15 files (keyvault and storage false positives, or tests)
> `cspell lint --config .vscode/cspell.json *.md */**/*.md`
CSpell: Files checked: 45, Issues found: 5 in 2 files (eng/common)
> `cspell lint --config .vscode/cspell.json *.txt */**/*.txt`
CSpell: Files checked: 44, Issues found: 0 in 0 files
> `cspell lint --config .vscode/cspell.json *.* */**/*`
CSpell: Files checked: 646, Issues found: 328 in 69 files (most of these are in eng\docs\api\assets\style.css or eng/common)
Deprioritize and ignored the errors from the test files (including test resource json files), and `eng/common` since those need to be centrally fixed.
* Use linux for vcpkg release
* Force lf line endings
* Set config correctly
* Better core.eol syntax and sequencing
* Try using linux host which uses LF by default
* Revert "Try using linux host which uses LF by default"
This reverts commit 160eb22b647e851a50f9d1e7b157a1e385fe946f.
* Use vcpkg.exe to format the manifest
* Spell correctly
* Move format-manfiest
* Update vcpkg ports to use a manifest json file instead of a CONTROL file.
* Update vcpkg ports to use a manifest json file instead of a CONTROL file
for remaining packages.
* Add the new vcpkg manifet json files and also update the template
package.
* Update paths in the cmake and eng scripts to find the right file now
that CONTROL is gone.
