Design Patterns for Salesforce Git Branching Strategies

Поделиться
HTML-код
  • Опубликовано: 27 ноя 2024

Комментарии • 13

  • @manugne
    @manugne 9 месяцев назад +2

    Well done Pablo...I liked idea of single branch master and feature branch with tags..In Salesforce multi org using branches per sandbox is very tough to manage especially in case of bugs found in one org and one need to backpromote in all other Salesforce orgs.

  • @riesenrum
    @riesenrum 9 месяцев назад +1

    Very clear and informative, thank you Pablo! I genuinely enjoyed this session and learned a lot.

    • @9gager87
      @9gager87 9 месяцев назад +1

      Thanks 😊🙏

    • @apexhours
      @apexhours  8 месяцев назад +1

      Glad you like it

  • @SalesforceUSA
    @SalesforceUSA 9 месяцев назад +2

    We need this. This is a very good video. I recommend it. It is very helpful. Thanks.............

  • @andrea004
    @andrea004 9 месяцев назад +1

    Wow! Thank you so much for this Pablo. DevOps is a super complicated part of the Salesforce world and you explained so simply, it was brilliant! I've working on DevOps processes that have been based on many of the strategies shown here for years and I found it very helpful and enlightning. Kudos to you! I will suscribe to your blog and hopefully to future trainings as well

    • @9gager87
      @9gager87 9 месяцев назад

      Glad you liked it!

  • @jefersonspencer
    @jefersonspencer 9 месяцев назад +1

    Well done Pablo, really useful.
    It is great to see more people challenging branches = sandboxes idea, we should decouple that and reuse the lessons we learned in other engineering fields.

  • @SFLightningForce
    @SFLightningForce 9 месяцев назад +2

    Nice insight at Salesforce deployment (CI/CD), thanks

  • @kennethsoerensen81
    @kennethsoerensen81 2 месяца назад +1

    This is so outdated! You should not run org based delopment that forces you to use git as any tooling for organing your sandboxes and environments. The only correct way going forward is package based devlopment and trunck based git strategy. Even larger monorepos containg multiple packages is fine. The problem is that all these companies that try to get you pay for their toolings don't want you to go package based as it ruins the market for them. I'm a Tech Lead and the Team Leader for our Platform Team in one of the larges SF customer in Norway with more than 12000 users and the wholw Norwegian populain as our community users. We have 5 product team delivering and deploying new featers multiple times daily to our production with no problems.