Skip to main content

#Github0 discutindo

Salesforce Code Analyzer v5.0.0 is Now Generally Available (GA) 

 

Code Analyzer

 is completely free and helps developers scan and fix problematic code, acting as a unified layer on top of a range of open-source code scanning engines. It's now available across all key DX experiences: CLI, IDE, GitHub Actions and DevOps Testing!  

 

v5 now comes with:

  • 2 new engines: Flow Scanner and Regular Expressions
  • AI-powered quick fixes by Agentforce for Developers 
  • A single command to execute Code Analyzer
  • A brand new, highly polished HTML report
  • A completely new YAML configuration file
  • New integrations with DevOps Testing, GitHub Actions

Our VS Code extension v1.6.0 is also available with quick fix functionality that calls through to our Agenforce for Developers LLM.  

 

See our updated documentation here.

 

#Agentforce #Code Analyzer #Devops #Salesforce CLI #Github

0/9000

Hi everybody, I have an issue, when I am trying to access to repository SFRA GitHub, the login fail, I have been trying to use the Single-On and typical login, but both show a wrong message. 

I have the two authentication in GitHub correctly but I don’t know what can I do to follow with my learning, I am block.

Obviously, I have been using the Commerce Cloud Trailhead Developer Credentials. Please help me.

 

Hi everybody, I have an issue, when I am trying to access to repository SFRA GitHub, the login fail, I have been trying to use the Single-On and typical login, but both show a wrong message.

 

#B2C Commerce #SFRA #Github

0/9000

Hi, I'm getting some deployment errors which I am fixing in GitHub. I'm committing those changes but they don't seem to be syncing back to DevOps Center, so I'm getting the same errors when I try and depoly again.

 

Our environment strategy is as follows:

DEV > QA > SIT > UAT > PROD

 

When I make fixes in GitHub if a deployment to QA from DEV fails, the sync seems to kick in fine and the deployment subsequently works. However, in this case I'm trying to fix a Work Item I am trying to deploy from SIT to UAT.

 

Why would the changes not be syncing back to DevOps Center in this case?

 

#Github

2 respostas
  1. 5 de dez. de 2023, 16:14

    @Alex Twomey-McLeod sad to hear that. I was assessing this product a couple of months ago and my finding were that it's not a mature at all. We've decided to use Gtihub and self crafted scripts(mainly JS/TS/bash) - it give us a lot of flexibility and the sense of control over the process. 

     

    I strongly recommend to consider to use native Jira integration or switch to Gihub issues as a main source of incident management. It will simplify your process and bring scalability in the future - adding quality gates for code or metadata will be as easy as plug and play

0/9000

I’m excited to announce the launch of SaltoLeap for Salesforce, a learning platform full of 100% free courses (taught by yours truly!) designed to increase your #Salesforce #DevOps knowledge and take you further in your career. 🔥

 

If you’ve enjoyed my DevOps content, these are the same but 10x better. We’ll walk through the fundamentals of #CI/CD in Salesforce and get into the nitty-gritty with #SFDX commands, #GitHub Actions configurations, and #VSCode techniques.

 

By the time you finish the courses, you’ll be surprised at how much knowledge you will have gained.

 

Plus, if you’ll be at Dreamforce, be sure to take the special 5-min DevOps course I put together (hosted on SaltoLeap) and then stop by our booth! Just show us your shared completion certificate on social media, and you’ll get an adorable Knuckles plush toy 🤩

 

Sign up below to get free access to all of SaltoLeap!

 

https://s-leap.salto.io/

I’m excited to announce the launch of SaltoLeap for Salesforce, a learning platform full of 100% free courses (taught by yours truly!) designed to increase your knowledge and take you further in your

1 comentário
0/9000
5 respostas
  1. 10 de jul. de 2023, 20:58
    Give the system permissions on profile level manage addresses
0/9000

I am trying to run robot tests in github action with persistent org. I have done all the setup as mentioned in cumulusci documentation. But I am still getting below error 

Error: ('Could not deserialize key data. The data may be in an incorrect format,it may be encrypted with an unsupported algorithm, or it may be an unsupported key type (e.g. EC curves with explicit parameters).', [_OpenSSLErrorWithText(code=75497580, lib=9, reason=108, 

reason_text=b'error:0480006C:PEM routines::no start line')])"

 

GITHUB:

Environment Varialbles:

 CUMULUSCI_KEYCHAIN_CLASS: cumulusci.core.keychain.EnvironmentProjectKeychain

 CUMULUSCI_ORG_auto_admin: ${{ secrets.AUTO_ADMIN_EMAIL }}

 CUMULUSCI_ORG_lead_agent: ${{ secrets.LEAD_AGENT_EMAIL }}

 SFDX_CLIENT_ID: ${{ secrets.CLIENT_ID }}

 SFDX_HUB_KEY: ${{ secrets.SERVER_KEY }}

 

Cumulusci Commands:

cci task run robot --org auto_admin

 

CLIENT_ID = consumer key of connected app

SERVER_KEY= contents of server.key file

Please refer attached attached screenshot for error message 

#Trailhead Challenges #Trailhead #Certifications #Salesforce Developer #TrailblazerCommunity #Automation #Github #CumulusCI

Unable to run robot tasks in Github actions with CumulusCI

3 respostas
  1. 16 de jun. de 2023, 08:51

    Hi ,

     

    Change:

    request.setEndpoint('https://ap5.salesforce.com/services/oauth2/token');

    to either Login or test depending on if in production or sandbox

    request.setEndpoint('https://[login | test].salesforce.com/services/oauth2/token');

    You also need to put the parameters in the body or as URL params and not header

    request.setBody(

    'grant_type=password' +

    '&client_id=xxxx' +

    '&client_secret=xx' +

    '&username=xx' +

    '&password=xx'

    );

     https://salesforce.stackexchange.com/questions/172980/errorunsupported-grant-type-error-descriptiongrant-type-not-supported

0/9000

Resources from the Salesforce Developers Ask Me Anything on The Future of Heroku

 

We hope you were able to join us for the fantastic #SFDevsAMA on Wednesday 29th March featuring @Julián Duque and @Andrew Fawcett. They loved answering your questions about The Future of #Heroku

 

If you missed it, don't worry - we recorded the session and our experts have provided some great resources that our experts for you to continue your learning! 

*To see roadmaps for other Salesforce products take a look at the Salesforce Architects Roadmap Explorer, or the Salesforce IdeaExchange.

 

Still have questions? Post them in this thread for our experts!

 

#Ask An Expert #Heroku Enterprise #Heroku Platform #Heroku Architecture 

2 comentários
0/9000

I m getting error invalid fullname, must end in a custom suffix ( for ex. __c ) when deploying changes via Github (2 custom fields on , one on lead another on the Opportunity )to another sandbox.

Also verified the field names and api names too , it showing correct. Can anyone help me on this. 

  

#SalesforceDXCLI #SalesforceDeployment #Github #Salesforce

invalid fullname, must end in a custom suffix ( for ex. __c )

4 respostas
  1. 24 de jan. de 2022, 09:44

    This error is a result of In-App Guidance not being enabled in the target org. Either remove the metadata (e.g. force-app/main/default/objects/PromptAction), or enable In-App Guidance.

0/9000

I am attempting to install a managed package in a scratch org with install_managed. I get the below errors:

admin@admins-MacBook-Pro core-app % cci task run install_managed --org scratchorg

[12/17/21 11:50:14] Resolution strategy latest_release failed for dependency https://github.com/ClarityCX1/core-app.

Resolution strategy unmanaged failed for dependency https://github.com/ClarityCX1/core-app.

Error: Unable to resolve dependency https://github.com/ClarityCX1/core-app

What am I missing here? Do I need to configure something on cci or on github?

#CumulusCI #Github

9 respostas
  1. 29 de dez. de 2021, 16:25

    CumulusCI dependency resolution expects that you use CumulusCI flows for creating releases, which includes generating a GitHub tag with a very specific format (as well as some metadata included in the tag annotations). 

     

    If you choose not to use CumulusCI flows to run your releases, or manually run the `github_release` task after you execute a release and provide all the relevant details in options (see `cci task info github_release`), CumulusCI has no way to resolve your package releases.

0/9000

I'm trying to release a beta and it's failing in the github_release task,

 

https://gist.github.com/icrm-af/e3a0b25ccb21b4ad5a03611a031d5301

 

I'm connected to three GitHub accounts using SSH, each one identified with a unique name, so when I clone the repo is something like: git@icrm:ImagineCRM-org/Repo.git.

 

The repo is hosted in an Org account and is private, to which my main profile has full access.

I had removed and connected the GitHub service multiple times using my main profile.

I created the same repo in my main profile and made it public.

 

Always failing in the same error.

9 comentários
  1. 16 de jun. de 2021, 13:35
    @Adrian Flores We'll adjust how we are getting the repo owner so that it can handle your ssh aliases: https://github.com/SFDO-Tooling/CumulusCI/pull/2684

    For configuring multiple github services, you can already do this as long as you only need to use one github account per CumulusCI project. First, connect the service with `cci service connect github <name>` and give it a name that helps you remember which account it is. Then, set it as the default github service for the current project by running `cci service default github <name> --project`. (Project defaults take precedence over global defaults.)

    If you have a situation where you have a project with a dependency on a repository that is only accessible using a different account, we don't support that yet.

0/9000