Skip to content

[INFO] What should we set in copado in order to run? #209

@DannyCastroVentura

Description

@DannyCastroVentura

Pipeline

  • Details:

    Name Value
    Active
    Main Branch master
    Commit Job Template MC Commit Action
    Promotion Job Template MC Promote Action
    Deployment Job Template MC Deploy Action
  • Pipeline Connections:

    • Add all the environments needed to this pipeline
  • System Variables:

    Api Name Value
    mc_devtools_version #mcdo (if assume branch of mcdev's git repo shall be loaded)
    ^ <number_version> (if install via npm at specified version)
    mc_credentials JSON with credentials

Environments:

  • Details:

    Name Value
    Platform Marketing Cloud
    Type Sandbox (if DEV or Production)
    ^ Production/Developer (if QA)
  • Environment Variables:

    • Add here if we want anything to change when changing from one environment to another
  • System Properties:

    Api Name Value
    credential_name name of the credential for this environement
    mid MID of the BU

Credentials:

Bind credentials to the environments.

Flow:

  1. In the User Story you want to work on, click on Commit Changes;
  2. If you need to have the most current values in the table click on Refresh;
  3. Choose the data you want to send to the other BU by checking them and then click on the Commit Changes button;
  4. If commit is succeeded, you can go to the Pipelines tab;
  5. Choose the pipeline you were working on;
  6. Then on the the field located in Details > Information > Manage Releases, click on its link;
  7. Then click on the arrow → with a number on top;
  8. Choose the User Story you would want to deploy (you will only see your user story in here if the user story checkbox field ready to promote is ✓)´;
  9. And click on Create Promotion;
  10. After click on Merge and Deploy and wait for the result;

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions