[Feedback Tracking] 🚀 GA - New Deployments dashboard view is now generally available! #62676
-
Select Topic AreaProduct Feedback Body📣 On April 25, 2024, we shipped the new dashboard view UI experience for Deployments to general availability! 🚀 Along this ship, the Deployments dashboard now includes the following enhancements:
Quick links: Please leave your feedback as a comment! 💬 Previous Beta Announcement 📣📣 On August 3, 2023, we shipped a new dashboard view UI experience for Deployments. This is a stepping stone on our roadmap toward a renewed focus on Continuous Delivery. 🚀 For now, users may choose to opt-out of the new experience using GitHub's feature preview settings. If you do opt-out, we would love to hear why. 👂🏻 You can learn more about this change in our changelog post. Quick links: |
Beta Was this translation helpful? Give feedback.
Replies: 122 comments 149 replies
-
What would be extremely helpful is if this was available across the org, like the security stuff, and filterable by repo topics and by environments (e.g. "show me all repos that have one of the topics [back_end, integration_layer] and show the following environments if they exist [stage, production]" This way you could easily build views that show you what's deployed across your org. Ideally, the environments would be columns. e.g.
or put a badge there? would make it more reusable... |
Beta Was this translation helpful? Give feedback.
-
The overview already shows if its main branch, but it would be very helpfull if it could also show the release name if theres a release tag associated with the deployment. |
Beta Was this translation helpful? Give feedback.
-
Some feedback from my team's testing of the new UI:
|
Beta Was this translation helpful? Give feedback.
-
It's a nice, iterative improvement over the previous iteration. My primary feedback would be to support monorepos in a more official capacity. At the moment, with our internal deployment tool that uses GitHub Deployments under the hood, we split environments into two components: a project and an environment name. E.g That said, official support for multiple "projects" in a repository would be helpful both to avoid such fragile features on top of this, as well as allowing the environments list on the left to filter by projects. |
Beta Was this translation helpful? Give feedback.
-
Thank you so much for this feature! It couldn't have come at a better time. My only two items of feedback:
|
Beta Was this translation helpful? Give feedback.
-
It would be nice to have the ability to remove all/selected deployments (with artifacts) to clean up storage. |
Beta Was this translation helpful? Give feedback.
-
Would love to be able to add filtering to this so we only see the ones we care about. our repo is a monorepo with many apps and packages. so our deployment environment names look like:
so:
if we could add in the repo settings something like:
and then have those groups reflected as separate groups in the ui.. 🎉 |
Beta Was this translation helpful? Give feedback.
-
We use many parallel steps (as reusable workflows) to deploy multiple applications to multiple regions. All of these workflows declare the use of a single environment ( The dashboard counting each one as a completely independent dashboard is useless information and means seeing actual atomic deployment is impossible. I've run the overall workflow 15 times, but this dashboard tells me we have performed 533 deployments: |
Beta Was this translation helpful? Give feedback.
-
This is a massive improvement and looking forward to more iteration. Desperately needs capability to filter by team/name/etc. We have (currently) 400+ environments in a single monorepo setup (all active), without filters its difficult for any team to be able to find a single view of their last deployed state). |
Beta Was this translation helpful? Give feedback.
This comment has been hidden.
This comment has been hidden.
-
Cool feature and excited to see how the tooling is improving. I would love to have some ability to delete these deployments as I've had to run about 40+ experiments to get things working, and now that it's finally green, I want to hide the earlier messes. |
Beta Was this translation helpful? Give feedback.
-
Please add a feature to delete deployments, I ran a couple of test runs to getting this stuff to work. |
Beta Was this translation helpful? Give feedback.
-
I opted out personally. We have many many deploys and it was too hard to see which was the latest deploy to each server. That's all I wanted. Additionally, the list of deployments isn't a complete list -> is that because deployments that are down / expired aren't listed? If so, it would be nice to be able to see that. It would also be nice to be able to sort the currently active deployments by server name & by deployment time. |
Beta Was this translation helpful? Give feedback.
-
tldr; Use the compare tool with environments This is a great feature. My team recently migrated from Bitbucket cloud, and in the process created a monorepo with many individual service deployments. We have created an environment for each $service - $env. We previously used long lived branches for each service, but with everything in a monorepo we decided to migrate to an image promotion strategy. Only main is long lived at this point. Overall this has been a really good change, but culturally the team is use to being able to see the PR from main -> prod for each service. If we could use the compare tool to compare environments, I think that would provide a quick sanity check that everything your about to promote to production was tested in dev. If the compare tool had a tab/selection for environments (most recent deploy, the one with the green checkmark) that would be amazing. The monorepo concept makes environments a little messy. In our case we are mangling services with ENV, and others in this thread are adding even more levels to the mangling. So a sort of double enhancement would be to add a "service" concept that can link to "env", and then the compare tool could just take a service and assume your going to compare prod to most recent non-prod for that service? |
Beta Was this translation helpful? Give feedback.
-
We deploy our services to multiple regions, and those deployments are independent from each other. Are there any plans to introduce another top level attribute that would allow us to identify deployments? Currently I have to follow a naming convention for the environments e.g. Thanks! |
Beta Was this translation helpful? Give feedback.
-
We have multiple deployment jobs using same environment. Some are in the same workflow, some in separate workflow. My biggest itch is that we see several identical rows (or just slightly different) in the deployment list, as one row corresponds to one job, but info shown (commit message, actor, trigger) is mostly the same for all jobs, especially ones from same workflow. Would be nice if we could get some control over that - showing a job display name instead of commit message, for example, would let us put info we need there to disambiguate between the rows. |
Beta Was this translation helpful? Give feedback.
-
I'd like to show a URL to the deployed app for any viewer of the repo. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
I'm seeing a bug on the new deployments screen that is not present on the old version. An unrelated PR opened against a fork (not against my source repo) is showing up as the reference PR for every deployment: https://github.com/johnbillion/query-monitor/deployments/QueryMonitor.com Note the |
Beta Was this translation helpful? Give feedback.
-
@johnbillion No. The problem is on the left side! Archived repo is just an example and works fine, but left side with deleted branch - not. All pages options are gone and it's really bug. I recreated the whole repo to fix it. And you can reproduce this. Ok, if this bug not related to Deployments, where can I put this feedback? Because Pages functionality (pages, pages deployment workflow) completely breaks after this manipulations. |
Beta Was this translation helpful? Give feedback.
-
I made a mistake, and now i have the unwanted |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Thanks! |
Beta Was this translation helpful? Give feedback.
-
Hey GitHub, Playing with the Deployment API, I noticed two things (probably already on the map but can't find a ref here):
e.g:
Screen.Recording.2023-09-14.at.12.31.00.movNB: The first 404 is CTRL + R |
Beta Was this translation helpful? Give feedback.
-
Loved it! |
Beta Was this translation helpful? Give feedback.
-
Bug / errors by downloading files/songs in large sizes more than 130 MB cause to break |
Beta Was this translation helpful? Give feedback.
-
I will need to opt out of this as it gives misleading information about my project. Firstly there seems to be some confusion over deployments vs publishing. I'd argue that publishing to a repository is not a deployment, as deployments to an environment have very different semantics to publishing. For one thing, publishing an artefact does not typically remove the previously published artefact. Eg: if you publish a docker image, and then publish another then BOTH remain published at the same time, the first is not implicitly deleted. There seems to be an assumption that because my workflow has used an environment, the workflow must be a deployment. This is not true. Deployments ought to be explicitly declared by the workflow. Currently publishing to PyPi requires setting up an environment. As above, I don't believe "deployments" is a good model for representing publishing to PyPi. Through the UI
|
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
I like it, but can I use it for GitHub Pages? Or does it have any errors? |
Beta Was this translation helpful? Give feedback.
📣 On April 25, 2024, we shipped the new dashboard view UI experience for Deployments to general availability! 🚀
Along this ship, the Deployments dashboard now includes the following enhancements:
OR
behavior.