MuseLab’s Post

People ask me how to solve the problem of merge conflicts and back promotion hell in Salesforce DevOps. These are not the real problems. Both these are symptoms of a single problem, 2 sides of the same coin: Working in orgs that are not integrated and high fidelity. If we can ensure that each individual sandbox automatically has the latest changes made by the dev team every day, then we don't need to back promote. The more in sync our orgs are, the less likely are merge conflicts to occur. Work on getting your orgs to be integrated daily, and you'll see these symptoms go away.

Salesforce DevOps experts, I have a question for you! When you work with developer sandboxes and a git repo, do you activate source tracking? Which problems or limitations do you encounter when working with this approach? Thanks!

Successful DevOps begins with teamwork, not tooling. I explore this is my new book, Salesforce DevOps for Architects, out TOMORROW. https://packt.link/a7TEV

Remember, the solution should be better than the problem. I've been talking to lots of customers over the past several months that have invested in GIT based Salesforce DevOps tools. They cant keep their environmental in sync. They can't do roll backs. They have to learn a CI/CD tool and learn GIT. When the tool doesn't work it's "a GIT problem, not ours". If you're feeling the pain, there is a better way. Flosum can help.

Transitioning your source code from GitHub to Git within Salesforce represents a big step forward in streamlining your workflows and enhancing collaboration. With the help of a platform like Opsera, migrating to Git within the Salesforce ecosystem simplifies your DevOps processes and provides comprehensive visibility into your operations. To hear more on this topic, watch our latest DevOps Huddle on the “Top Salesforce DevOps Challenges and How to Solve Them.” Link to watch: https://hubs.la/Q02w_JR_0 #Salesforce #SalesforceDevOps #DevOps #SoftwareDelivery #Technology #DeveloperProductivity #Security #Quality #GitHub #Git #Opsera

Join us next Wednesday, September 13th, at Dreamforce for a fast paced story on DevOps Center for Salesforce Developers, packed with 15 tips on the role and knowledge stack of Devs, how to get started successfully and improve your day-to-say DevOps Center workflow and some hidden gems that you probably didn't know yet. Number 14 is hot off the press! Bookmark now 📱 in the Salesforce Events app or 🌐 on the web in your Dreamforce Agenda Builder. Link in the comments!

We need a "model Salesforce devops lab". Imagine if we could reproduce an org set up with enterprise-style development, layers of Apex with varying test styles and frameworks, deep customization, partial adoption of source control, and maybe a couple of gnarly integrations. Practitioners and learners could experiment, build, vet, and publish devops strategies using a common base and solving problems that nearly all orgs share, at least in part.

DevOps is increasingly becoming the de facto approach to Salesforce development across the ecosystem. We take a look at some of the key challenges facing Salesforce teams looking to adopt DevOps, and how you can avoid these common pitfalls 👉 https://grst.co/3ZwKtuz

Whether you want to propel your product release cycles, improve your service quality or increase your product/service speed, Salesforce DevOps can help you deliver more value to your #business. Check out this comprehensive list of popular tools to supercharge your Salesforce DevOps project for grand success. From automation to seamless integration, these tools can elevate your Salesforce development game. Dive in for insights and take your DevOps strategy to the next level! #Salesforce #DevOps #ToolsForSuccess #Solunus 

New version of the Salesforce DevOps Manifesto! 📜 Our collective experience of deploying Salesforce applications has led us to embrace the following principles: ✔️ Prefer development environments that are ephemeral, integrated, and production-like over stale, shared, and out-of-sync sandboxes ✔️ Think of modular architectures instead of monoliths and happy soups ✔️ Automate everything that can be automated instead of using deployment checklists ✔️ Think of sandboxes as test environments; avoid coupling them to Git branches ✔️ Think of artifacts, deployment candidates, and versions, not org-based comparisons and deployments. Together, we embrace these principles to enhance agility, collaboration, and the efficiency of Salesforce DevOps practices. 📜 I came up with this new version after reflecting on the first one I came up with a few weeks ago, which was later refined by Ramzi Akremi in his article "A proposal for a Salesforce DevOps Manifesto" (a great read!). The idea is this one is more inclusive and focuses on the principles behind the principles :) and not the how-to. This way, these can be interpreted and not dictated. You can read more about my rationale here: https://lnkd.in/gkuQbxYJ What do you think?