sfdo-tooling/cumulusci-test

Dummy project used to test CumulusCI - CumulusCI will run this project through the whole CI flow to verify everything works

CumulusCI-Test

Dummy project used to test CumulusCI - CumulusCI will run this project through the whole CI flow to verify everything works.

cumulusci-test's Issues

Add instances of namespace token in unpackaged/post

To catch build failures like this one:
https://mrbelvedereci.herokuapp.com/builds/10649

Should include %%%NAMESPACE%%%, ___NAMESPACE___, %%%NAMESPACED_ORG%%%, and ___NAMESPACED_ORG___

Error "Chatter.settings Not available for deploy for this API version" when creating scratch org

Getting error when working through the tutorial at the step to create a scratch org:
https://cumulusci.readthedocs.io/en/latest/tutorial.html#using-salesforce-dx-scratch-orgs

Error  shape/settings/Chatter.settings              settings/Chatter.settings              Not available for deploy for this API version
Error  shape/settings/LightningExperience.settings  settings/LightningExperience.settings  Not available for deploy for this API version

ERROR running force:org:create:  Failed to deploy settings to scratch org.

I just installed cci 3.10. on mac.

When I try the sfdx command I get the same error.

I edited orgs/dev.json to remove:

  "settings": {
    "chatterSettings": {
      "enableChatter": true
    },
    "lightningExperienceSettings": {
      "enableS1DesktopEnabled": true
    }
  }

And now it works fine. Seems to be some issue with the settings?

Test issue

Question: How to use / For what to use Parallelism in CircleCI

I have successfully set everything up to use SalesforceDX Beta, CircleCI and the CircleCI GitHub Trigger that initiates builds in multiple containers.

What I am missing is how to use this feature correctly/efficiently. 3 containers, creating 3 scratch orgs doing all the same thing. I need some inspiration, push into the right direction where to investigate further.

(Ive put this question here rather with CumulusCI since I know Salesforce.org has since moved to MrBelvedereCI.)

Test issue

Not really a problem, just used for testing.

Create one instance of each metadata type for testing purposes

To verify they can all be properly deployed and undeployed.

Types to include:

• Business class - DONE
• Controller class - DONE
• Test class - DONE
• Visualforce page - DONE
• Visualforce component - DONE
• Custom object - DONE
• Layout - DONE
• Trigger - DONE
• App - DONE
• Custom tab - DONE
• Object-specific action - DONE
• Weblink (custom button) - DONE
• Home page component - DONE
• Home page layout - DONE

Add some non-ascii characters to test for unicode issues

Test issue

Is "descriptions" a typo?

CumulusCI-Test/cumulusci.yml

Line 337 in bad6b89

descriptions: A preflight flow that passes.

Test issue from Contributor Tool

External Contribution Issue created by @jlantz

Just a test issue, please ignore