How to Deploy Changes Using Salesforce DevOps Center [DevOps Center Series]
Vložit
- čas přidán 5. 09. 2024
- Welcome to the third and final video in our DevOps Center series! This one's a full tutorial, so get ready.
In this video, we'll break down how to to begin using Salesforce DevOps Center to deploy changes, as explained by Jereriah Manning, the Director of Solution Engineering at Prodly.
Check out the other two videos in the series in this playlist: tinyurl.com/5n...
Follow us on our socials! 📱
LinkedIn: / salesforce-ben
Facebook: / salesforceben
Twitter: / salesforceben
And don't forget to subscribe!
#salesforce #salesforceadmin #salesforcedeveloper #technology #salary #salaryincrease #salesforceforbeginners #devops #devopstutorial #devopstraining
Thank you for the demo, much easier to follow than the Salesforce documentation
Glad to hear you found it helpful Abulfazal!
Great video. Not sure if this can handle those Vlocity (Industry Cloud) artifacts, which my company is now using Copado because it can handle Vlocity but have limitations too.
If this tool can handle Vlocity metadata, it would be a perfect fit.
How can we perform back promotion?
Question, at the uat bundling stage, if you havs say 4 user stories to promote do you have to bundle all 4 or can you take just 1 up to the next org be it a pre prod or prod?
Hey! Yes, you can promote just one rather than all 4 as long as there are no dependencies between them (i.e. user story 1 needs a feature in user story 3 to function)
Thank you Ben for this amazing explanation
Glad to help!
Hi,
I am trying to connect a SF developer training org to the DevOps Center and I am able to connect the org to the pipeline. It keeps telling me -> Please check your username and password. If you still can't log in, contact your Salesforce administrator. NOTE: When I connect it as a production org it will connect. You guys know why?
Does the DevOps center currently only work with GitHub or any another repository like Azure DevOps could work?
Hi there, according to Salesforce: 'DevOps Center requires that you use it with a cloud-based, GitHub-hosted, github.com account. You can create a new (free) account or use an existing account. We aren’t supporting any kind of on-premise, enterprise, locally hosted GitHub, or any other Git-based or other source control provider system in this release.'
This is really clear and helpful introduction. I think we could use a follow up which talks about practical methods to resolve conflicts.
Does anyone know of good resources where this may exist?
Why not call this what it really is, instead of making it sound like it is made by Salesforce? This is the 'Prodly DevOps Center' for Salesforce, not 'Salesforce DevOps Center'.