#Continuous Deployment0 diskutieren mit

Starting in 30 Minutes: #AskMeAnything with the Salesforce Developer Advocates!

Our experts today are Kevin Poorman and Philippe Ozil, and they'll be answering all your questions on CI/CD and DevOps.   

To participate:

1. Ask your question here ⬇️ using the #SFDevsAMA tag. 
2. Join us for the broadcast to see your question answered! 

See you soon!

#CICD #Devops #SFDX CLI #Salesforce CLI #Continuous Integration #Continuous Delivery #Continuous Deployment #TrailblazerCommunity

TOMORROW January 26th: ASK ME ANYTHING with the Salesforce Developer Advocates!

Join Salesforce Developer Advocates Kevin Poorman and Philippe Ozil here for our monthly feature, Ask Me Anything! This 1-hour session is your chance to get the answers you need to succeed. Bring your questions! 

• Date: January 26th, 2022
• Time: 9am PT / 5pm GMT / 6pm CET / 9:30pm IST 
• Theme: CI/CD and DevOps
• Location: Right here, on our Salesforce Developers Trailblazer Community page!

Click here to add it to your Google Calendar.  This event will feature a live session from our YouTube channel and the developer advocates will answer questions that you post here using the official #SFDevsAMA tag. The live stream link will be shared on this page just before the event goes live.

#CICD #Devops #SFDX CLI #Salesforce CLI #Continuous Delivery #Continuous Integration #Continuous Deployment 

Hi

I invested a lot of time, trying to generate a valid 2GP package and install it to a newly created Scratch Org without any success.

Do you have some tips which flows i should use?

I tried release_2gp_beta but i get always an error when i install the package in a Scratch Org created over CumulusCI (with cci org scratch dev dev-test and then cci flow run dependencies --org dev-test to install npsp). First i had issues with a ConnectedApp then i had a general error message like in the attachment.

Have i missed something?

And one more thing i don't understand: when i have a release-tag in github-repo, the release_2gp_beta fails with the error:

Response content: [{'message': 'Can’t create the package version. The ancestor package version specified in the sfdx-project.json file hasn’t been promoted and released. Release the ancestor package version before specifying it as the ancestor in a new package or patch version.', 'errorCode': 'INVALID_INPUT', 'fields': []}]

Run this command for more information about debugging errors: cci error --help

Do you have some informations about this error?

Hello all,

what are your best practice recommendations for #Continuous Deployment with #ExperienceBundles enabled? The experience bundle tree with all the details like views shows up in the dev tools but in our deployment tool Copado I only get the experience bundle as a whole. Is this a limit of the tool or the API?

Deploying the whole community each time in one piece although only a specific page update is needed seems like a high risk for a larger community. I have hoped that the switch to ExperienceBundles would give admins the chance to deploy on a more granular level like one single page including translations and component settings.

Thanks

Tobias

#deployment

Hello! We recently switched over from metadata format to source format in our source control (Github), and created new CI/CD pipelines in Azure to handle source format builds and releases. Since we made that change though, I've been finding that every Continuous Deployment release to our sandbox orgs is creating a new version of our flows and processes, even though those flows were not actually changed/updated in the release.

Since we have multiple builds a day being released, flow versions are rapidly proliferating and we have started hitting the "too many flow versions" error on our releases due to hitting 50 versions on certain flows.

Previously, our flows did not have an "API Version for Running", but all of the new versions that are automatically created show an API Version for Running of 49.0. I am not sure why they are getting added as 49.0 instead of our current org API version 51.0. I have read this stackexchange thread on the topic, which suggests that perhaps adding the current API version of the target environment to the flow-meta.xml file would resolve the issue, but I am wondering if there is a different solution that wouldn't require us to always use the latest api version for all of flows.