Skip to main content
Grupo

DevOps

This Group is for those who are Developers and System Administrators within Operations, interested in incorporating Big Data to further drive the value of CRM and capture valuable business insights. Also, Apex, VF, Mobile, Analytics API discussions is promoted here as well.

I am setting up a pipeline in AzureDevOps (first time) and keep getting this error: error:1E08010C:DECODER routines::unsupported. 

Here is my YAML , can anyone take a look and tell me what I might be missing? 

 

trigger:  branches:    include:      - mainpool:  vmImage: 'ubuntu-latest'variables:  - group: SalesforceSecrets  - name: SFDX_CLI_VERSION    value: lateststages:  - stage: DeployToProduction    jobs:      - job: Deploy        steps:          - checkout: self          - task: NodeTool@0            inputs:              versionSpec: '18.x'            displayName: 'Install Node.js'          - script: |              npm install --global sfdx-cli            displayName: 'Install Salesforce CLI'          - script: |              echo "$SFDX_HUB_KEY" > server.key              sfdx force:auth:jwt:grant \                --clientid "$(SFDX_CLIENT_ID)" \                --jwtkeyfile server.key \                --username "gabriel.swenson@amtrustgroup.com" \                --setdefaultusername \                --instanceurl https://login.salesforce.com            displayName: 'Authenticate to Production'            env:              SFDX_CLIENT_ID: $(SFDX_CLIENT_ID)              SFDX_HUB_KEY: $(SFDX_HUB_KEY)          - script: |              sfdx force:source:deploy -p force-app -u "$(gabriel.swenson@amtrustgroup.com)" --testlevel RunLocalTests --wait 30            displayName: 'Deploy to Production'
1 resposta
  1. 3 de jul. de 2025, 19:14

    Hi @Gabe Swenson

     

     

    The DECODER routines::unsupported error occurs because your JWT key’s PEM formatting was lost when you echoed the secret.  

    To solve the issue use something like echo -e "$SFDX_HUB_KEY" > server.key so the key file retains proper line breaks before running sfdx force:auth:jwt:grant 

    Please refer to this documentation:

    https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_jwt_flow.htm

0/9000

When I'm trying to deploy active flows via GitLab pipeline as a Salesforce Integration License user, I'm getting "You can't activate this flow because it always runs in system context. Your salesforce admin can help with that." error. Can you someone provide your suggestions on resolving this permission related issue. Which permission should be provided to this user to mitigate this issue?

2 respostas
  1. 15 de dez. de 2024, 09:52

    Thanks @Eric Burté for the suggestion. I try to avoid creating duplicate posts in future. I would be happy if you could provide a solution to my issue.

     

    Regards,

    Arun

0/9000

BUILD FAILED

/home/circleci/project/build.xml:74: Failed to submit request to https://xyz.my.salesforce.com/services/Soap/m/46.0/00D7F000007DLHm for user **********************.

Error: Failed to send request to https://xyz.my.salesforce.com/services/Soap/m/46.0/00D7F000007DLHm

 

I have created 4 branches to push to production but only one fails, rest 3 have gone through. I comapared the config.yml file, seems same for all the 4 branches, need help on this.

0/9000

I would like to know Best DevOps Tools for Really big teams where we have around 80-100 Developers working on different projects, its a single org instance. We have biweekly releases to production. In the past we used few DevOps tools but they really didn't went well. So I would like to hear from other group members what tools are working for your teams.

 

cc @DevOps Admin 

Thanks & Regards

Srini 

4 respostas
  1. 28 de set. de 2024, 02:11

    Hi @Srinivasa Yeduru,

    Handling DevOps and releases for large enterprises can indeed be challenging. Here’s my take based on my experience managing release and DevOps operations for a project with weekly releases for over three years. We release every Thursday for our Indian client, amounting to about 3-4 releases per month and 10-12 releases per quarter.

    1. Main Tool - Jenkins: We use Jenkins for configuring jobs and pipelines, utilizing Groovy scripts. Our Jenkins server is hosted on AWS, which provides reliability.
    2. Integrations: Set up integrations with your ALM tool (we use JIRA) and SCM (currently on GitHub; we previously used Bitbucket and GitLab). Configure other integrations as needed.
    3. Continuous Integration: We implement CI up to the point where developers have access. Beyond that, code deployments are done selectively. Hint: Use webhooks.
    4. Continuous Delivery: Managing CD with a large team (35+ developers) is tough, especially if initial project implementations didn’t account for it. Issues can snowball, making it hard to proceed without impacting business continuity. For example, our Senior Tech Lead and Architect, with over 20 years of experience, couldn’t refresh the lower pre-production org from production without downtime, even when offered a month. Be very careful if you plan to implement CD in the future.
    5. Best Practices: Follow them diligently, or you’ll face a heavy workload in the future. Enterprise-grade projects with over 30 developers are no joke.
    6. The Dream - Seamless CI/CD: I’m still dreaming of achieving this.

    If this helps, please consider marking it as the best answer.

    Thanks!!!

0/9000

Try exporting --metadata CustomField:Account.AccountSource, and I noticed all the picklist values are empty.

<?xml version="1.0" encoding="UTF-8"?>

<CustomField xmlns="http://soap.sforce.com/2006/04/metadata">

<fullName>AccountSource</fullName>

<trackFeedHistory>true</trackFeedHistory>

<trackHistory>false</trackHistory>

<type>Picklist</type>

</CustomField>

It and all other picklist fields used to include their picklist values.  Is there a setting or a new metadata type I need to export to see these?  I do NOT want to move them manually.

 

This particular standard field has multiple picklist values.  Where'd they go?

 

Update

I'm starting to worry picklist values have moved to the PicklistValueInfo object.  Is there a new tool to use to migrate these to sandboxes?  Dataloader seems impractical and specific picklists for specific custom fields may be migrated before other values.

 

What is the new process supposed to be?  There's gotta be an article floating around somewhere...

3 respostas
  1. 22 de nov. de 2023, 15:35

    @Tom Gagne Standard picklists are usually stored in StandardValueSet as in my previous LeadSource example. Custom picklists are a part of a field meta.

0/9000

Hi ,

Is there any devops tool for salesforce where we can track and manage  the changes using Git without using Github.

Thanks.

2 respostas
  1. 9 de out. de 2023, 09:40

    What Lukasz said, just keep in mind if you're using a private Git server and a publicly hosted DevOps platform how will you securely expose that repository? A VPN Tunnel is one option, but a secure cloud-hosted Git is worth considering for less risk, which is why Github etc is so popular.

0/9000
1 comentário
0/9000
0/9000
1 resposta
  1. 19 de mai. de 2023, 14:14

    Pls mark this as "BEST ANSWER" IF THIS HELPS @Ajay Budarapu

     

    In Azure DevOps, you can find older User Stories related to a specific feature by following these steps:

    1. Go to the Azure DevOps project where the User Stories are stored.
    2. Navigate to the Boards or Work Items section.
    3. Use the search functionality and enter relevant keywords related to the feature or User Stories you're looking for.
    4. Apply filters if necessary to narrow down the search results by work item type, state, or other relevant criteria.
    5. Review the search results to find the User Stories that are associated with the feature you're interested in.

    Note: The exact steps may vary slightly depending on the version of Azure DevOps you are using and the customization done within your project.

0/9000
3 respostas
0/9000