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.

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

Update build pipeline badge #5351

Closed
danieljurek opened this issue Sep 11, 2019 · 3 comments
Closed

Update build pipeline badge #5351

danieljurek opened this issue Sep 11, 2019 · 3 comments
Labels
EngSys This issue is impacting the engineering system.

Comments

@danieljurek
Copy link
Member

Need to update the URL so this points to a more recent source of status data:

image.png

@danieljurek danieljurek added the EngSys This issue is impacting the engineering system. label Sep 11, 2019
@kurtzeborn
Copy link
Member

What does it point to now?

@danieljurek
Copy link
Member Author

Today it points to https://dev.azure.com/azure-sdk/public/_build?definitionId=17

With unified pipelines (where we don't have a single client build) it might make sense to use multiple badges

Service Status
App Config Build Status
Batch Build Status

Since the pipeline is internal, however, the results will only be viewable to those with permissions. Clicking on the badge today will take an unauthenticated user to an authentication experience.

@JimSuplizio
Copy link
Member

@danieljurek @kurtzeborn @weshaggard @joshfree
I'm closing this out, there's really nothing to do here. Wes replace this pipeline badge with packages back as part of PR 6672 which links to the latest releases page. NET, JS and pyton have had similar changes but the only language with a pipelines badge is Python which is core only and not representative.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
EngSys This issue is impacting the engineering system.
Projects
None yet
Development

No branches or pull requests

3 participants