search

forcedotcom / devops-center-roadmap

22 stars 1 forks source link

Option to keep Branches when Promoting #113

Open fmannreply opened 1 year ago

fmannreply commented 1 year ago

Currently branches are always deleted when promoting work items, it be nice to have the option to toggle that off.

Example: image

GilsonCanario commented 9 months ago

Hi @fmannreply - Thank you for your feature request. Could you share more information of your specific use case and why keeping branches is beneficial for you?

fmannreply commented 9 months ago

Hi @GilsonCanario , there would be two main benefits to me:

The first use case would be do setup extensions on top of DevOps Center. We currently only use the DevOps Center for Personal Admins Devs->INT, UAT & Prod are only connected via a custom Github pipeline (reevaluating this with every new update :) ). If the branch tag would still be there, I could write a GitHub Action allowing Admins to deploy their work items to QA and Prod.

The second but minor use case would be quicker internal reviews. I like doing internal reviews via VS Code. Currently, I have to:

If I'd still have the branch, I could just switch branches via VS Code.

To me, this would improve working with the DevOps Center.

GilsonCanario commented 9 months ago

Hi @fmannreply - Thank you for your reply. Could you share a little bit of information as to why your UAT & Prod are only connected via custom Github pipeline and not directly in DevOps Center? by doing this, your Admins can deploy their work items to QA and Prod from within DevOps Center. Also, you get the benefit and shifting left and review PR early in the process, before promoting to INT.

fmannreply commented 9 months ago

Thank you @GilsonCanario for your response and question. I am working with a great admin but also a great dev team and they prefer their tools for PersonalDev to INT deployment. We also use our custom SF cli pipeline for most deployments because it allows use to have more control over Fastlane, hotfix, QA and Prod deployments. We have the control over the deployment tool, can add custom hooks (e.g. one customer has an old QA instance which we can not refresh and need to transform some components before deployment), integrate PMD, follow our GitFlow model, and interact with it via Cli or our regular DevTools like VS Code.

When testing the DevOps center I observed that INT->QA deployment sometimes (probably when selecting some wrong buttons) trigger an unwanted bundle deployment and together with the forementioned arguments, we don't use it for QA & Prod deployments.

We very successfully use DevOps center for Admins. It's really been the final topping on the cake and gives admins a very intuitive way to be integrated into the whole cicd pipeline. But currently they can not do Fastlane deployments (Dev->INT->QA).

Regarding the feature request, this would enable us to add a custom pipeline for our Admins to perform Fastlane deployments (Dev->INT->QA). This could serve as a temporary solution until features like #38, #77, #118, and #16 address our gaps and we extend the usage of the DevOps center.