github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #562] Fix Build status badges #440

New issue

Closed

opened 2026-05-05 06:23:19 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 06:23:19 -06:00

Owner

Originally created by @icornett on GitHub (Feb 12, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/562

@nelsonjchen
I deleted the form because this is an Azure DevOps issue. The reason that your build status badges aren't working is probably due to the fact that you're running all builds in a single pipeline. If you split the pipelines by build type, your status badges will likely be fixed. It is interesting that they're not showing failed instead of never built, though.

Originally created by @icornett on GitHub (Feb 12, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/562 @nelsonjchen I deleted the form because this is an Azure DevOps issue. The reason that your build status badges aren't working is probably due to the fact that you're running all builds in a single pipeline. If you split the pipelines by build type, your status badges will likely be fixed. It is interesting that they're not showing failed instead of never built, though.

gitea-mirror closed this issue

2026-05-05 06:23:20 -06:00

gitea-mirror commented

2026-05-05 06:23:23 -06:00

Author

Owner

@nelsonjchen commented on GitHub (Feb 13, 2020):

Oh, I didn't add those badges to the readme.

https://github.com/debauchee/barrier/blame/170a27173759d15d6dce0acc62e2b40176b71448/README.md

6dc59d14a3

I haven't been involved with the project for some time. That said, it would be nice if the fix for this was also bundled in with moving the CI to GitHub Actions proper which wasn't available when I was fooling around with the project's CI.

@nelsonjchen commented on GitHub (Feb 13, 2020): Oh, I didn't add those badges to the readme. https://github.com/debauchee/barrier/blame/170a27173759d15d6dce0acc62e2b40176b71448/README.md https://github.com/debauchee/barrier/commit/6dc59d14a33a2564520bd8f95f742a934728a414 I haven't been involved with the project for some time. That said, it would be nice if the fix for this was also bundled in with moving the CI to GitHub Actions proper which wasn't available when I was fooling around with the project's CI.

gitea-mirror commented

2026-05-05 06:23:25 -06:00

Author

Owner

@digitaldelirium commented on GitHub (Feb 13, 2020):

Azure DevOps does this for free anyway since it's open source. I guess you could move it to GitHub Actions too.

I can take this on, I literally just got my Azure DevOps cert after filing this. Would you be able to provide permissions for me to be a contributor in Azure DevOps?

@digitaldelirium commented on GitHub (Feb 13, 2020): Azure DevOps does this for free anyway since it's open source. I guess you could move it to GitHub Actions too. I can take this on, I literally just got my Azure DevOps cert after filing this. Would you be able to provide permissions for me to be a contributor in Azure DevOps?

gitea-mirror commented

2026-05-05 06:23:27 -06:00

Author

Owner

@nelsonjchen commented on GitHub (Feb 13, 2020):

@digitaldelirium I don't have access to it so I couldn't give you access to this project's on there if I wanted to. Maybe the other maintainers here might be game, I don't know. That said, the pipeline definitions are mostly in the Azure Pipelines YML. So if you want to contribute to the Azure Devops CI implementation, I suggest you fork this repo, and then make a Azure DevOps project in either your personal org tied to your fork, refactor/test the pipeline to be pipelines and send a PR in with the updated azure-pipelines.yml.

That said, Azure Devops is indeed free but it is unfortunately an annoying non-integrated separate system if we're only talking about using it for CI. Look at all that setup for CI of a forked GitHub repository you have to do above! If this were GitHub Actions, you could press "Fork" and start hacking on the workflows immediately and then be able to send a PR in. GitHub Actions is a fork of the Pipelines functionality in Azure DevOps so much of the existing functionality/worker environment is available along with many GitHub flavored extras. Maybe that might be worthy of another issue.

@nelsonjchen commented on GitHub (Feb 13, 2020): @digitaldelirium I don't have access to it so I couldn't give you access to this project's on there if I wanted to. Maybe the other maintainers here might be game, I don't know. That said, the pipeline definitions are mostly in the Azure Pipelines YML. So if you want to contribute to the Azure Devops CI implementation, I suggest you fork this repo, and then make a Azure DevOps project in either your personal org tied to your fork, refactor/test the pipeline to be pipelines and send a PR in with the updated `azure-pipelines.yml`. That said, Azure Devops is indeed free but it is unfortunately an annoying non-integrated separate system if we're only talking about using it for CI. Look at all that setup for CI of a forked GitHub repository you have to do above! If this were GitHub Actions, you could press "Fork" and start hacking on the workflows immediately and then be able to send a PR in. GitHub Actions is a fork of the Pipelines functionality in Azure DevOps so much of the existing functionality/worker environment is available along with many GitHub flavored extras. Maybe that might be worthy of another issue.

gitea-mirror commented

2026-05-05 06:23:29 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 29, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 29, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:23:33 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

Build status badges have worked for quite some time so far. Therefore I'm closing this issue. It seems that I may be missing some context about the issue, so feel free to reopen.

@p12tic commented on GitHub (Jan 10, 2021): Build status badges have worked for quite some time so far. Therefore I'm closing this issue. It seems that I may be missing some context about the issue, so feel free to reopen.

No labels

Rows
Columns