search

backstage / community-plugins

Community plugins for Backstage
Apache License 2.0
114 stars 91 forks source link

🔌 Plugin: @backstage/plugin-azure-devops - Releases Component #217

Open aj-dev-smith opened 1 year ago

aj-dev-smith commented 1 year ago

🔖 Summary

Currently the plugin has a few different cards, including pipelines.

At my org we use pipelines for builds and the Releases tab for actual deployments.

At the moment there is no component for Releases. It would be great to have a component similar to EntityAzurePipelinesContent, but with content around releases pipelines instead. There are APIs available from Azure that can fetch the data needed for this component easily.

🌐 Project website (if applicable)

No response

✌️ Context

No response

👀 Have you spent some time to check if this plugin request has been raised before?

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

No, I don't have time to work on this right now

awanlin commented 1 year ago

Hi @aj-dev-smith, this is a great suggestion and maybe someone from the community will do just that.

Just wanted to share some background: When I initially started on the Azure DevOps plugin I had looked into building a Releases table component. What I found was that this was really hard to build in a generic way that could be used by other Organizations. Releases can be very flexible so they will look different from Company to Company.

Also, Releases are being replaced by Multi-Stage YAML Pipelines. Now, I have not seen MS say explicitly say they are dead but they generally never do till years later. I have not seen any new features added to Releases in any updates or new versions. Because of this I feel like the effort is somewhat wasted and it would be nicer to see better support for Multi-Stage Pipelines in the Backstage Azure DevOps plugin.

antoniobergas commented 1 year ago

Hi! I totally agree with @awanlin. Last year I was in a meeting with an engineer from Microsoft that works with Azure DevOps, he pointed that internally everyone was migrating to yaml.

Also you can find this in the latest version of Azure DevOps Services image