Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make CI logs public #5781

Closed
aahmed-se opened this issue Mar 22, 2019 · 2 comments
Closed

Make CI logs public #5781

aahmed-se opened this issue Mar 22, 2019 · 2 comments
Assignees
@Rastaban
Labels
category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed

Comments

@aahmed-se
Copy link

I can't access the ci env via my credentials , read only access should not need any authentication.
@LilyWangL LilyWangL added the category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed label Mar 27, 2019
@JackBoosY
Copy link
Contributor

Related: #6618.

@Rastaban
Copy link
Contributor

Rastaban commented Jun 1, 2019

The pipelines are being moved to a public location so they can be accessed anonymously https://dev.azure.com/vcpkg/public

@Rastaban Rastaban closed this as completed Jun 1, 2019
azure-sdk added a commit to azure-sdk/vcpkg that referenced this issue Aug 6, 2024
@azure-sdk
[azure-data-tables-cpp] Update to 1.0.0-beta.4
4de7108 
## 1.0.0-beta.4 (2024-08-06)

### Bugs Fixed

- [[microsoft#5781]](Azure/azure-sdk-for-cpp#5781) Fixed exception when deserializing numeric values from JSON. (A community contribution, courtesy of _[0xar1](https://github.com/0xar1)_)

### Acknowledgments

Thank you to our developer community members who helped to make Azure Data Tables better with their contributions to this release:

- arwell _([GitHub](https://github.com/0xar1))_
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Rastaban Rastaban

Labels
category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Rastaban @aahmed-se @JackBoosY @LilyWangL