1
0
Форкнуть 0
Перейти к файлу
Wade Wegner ab3ba91e19
Update README.md
2019-05-02 08:03:51 -07:00
bin Updates to post-setup.sh 2018-02-13 06:13:22 -08:00
config Added sfdx project to repo 2018-02-09 16:50:46 -08:00
force-app Update DemoControllerTests.cls 2018-02-09 19:44:06 -08:00
.forceignore Added sfdx project to repo 2018-02-09 16:50:46 -08:00
.gitignore Minor updates 2018-02-12 05:00:14 -08:00
.salesforcedx.yml Default to not showing org url 2018-02-13 13:48:41 -08:00
LICENSE Initial commit 2018-02-09 13:49:46 -08:00
README.md Update README.md 2019-05-02 08:03:51 -07:00
app.json Updating test-setup call 2018-02-13 13:51:43 -08:00
setup.sh Merge branch 'master' of github.com:wadewegner/salesforce-dx-pipeline-sample 2018-02-13 05:13:31 -08:00
sfdx-project.json Added sfdx project to repo 2018-02-09 16:50:46 -08:00

README.md

salesforce-dx-pipeline-sample

This repository has not received regular updates. Please use to https://github.com/heroku/salesforce-buildpack instead.

Using this sample app and the resources in this repo, you can setup a Heroku Pipeline to drive CI / CD for Salesforce DX. This sample uses the salesforce-dx-buildpack and the salesforce-cli-buildpack.

image

To use Heroku Pipelines with any Salesforce DX project, you only need to do two things:

  1. Create a app.json file.

  2. Create a .salesforcedx.yml file.

That's it. Along with the setup.sh script you find in this repo, the buildpacks do the rest.

Setup

  1. Install the Heroku CLI.

  2. Install the Salesforce CLI.

  3. Log into the four orgs you'll use with the Salesforce CLI and give them aliases:

    • Dev Hub (e.g.. "HubOrg"): this will create scratch orgs for your Review Apps
    • Development Org (e.g. "DevOrg"): this is the first environment you'll update using a metadata deploy
    • Staging Org (e.g. "TestOrg"): this is the first environment from which you'll promote your code via release phase
    • Prod Org : "ProdOrg": this is your production org

    Note: you could cheat and, simply for demo purposes, use the same org for the DevOrg, TestOrg, and ProdOrg.

  4. Ensure you see all four orgs when you run sfdx force:org:list.

  5. Fork this repository.

  6. Clone the repository locally.

  7. Update the values in setup.sh accordingly (e.g. HEROKU_TEAM_NAME, DEV_HUB_USERNAME, DEV_USERNAME, STAGING_USERNAME, and PROD_USERNAME).

  8. Run ./setup.sh.

Unfortunately there's a bug in heroku pipelines:setup that prevents us from fully setting up the pipeline. To manually finish the setup, perform the following steps:

  1. Open your pipeline: heroku pipelines:open <YOURPIPELINENAME>

  2. Click Settings.

  3. Search for "salesforce-dx-pipeline-sample" and click Connect.

  4. Clic Pipelines.

  5. Click Enable Review Apps.... Check both boxes and click Enable.

  6. Under development, click the expansion button and then click Configure automatic deploys... Then click Enable Automatic Deploys.

Now you're all set.

Usage

To demo, simply submit a pull request. It's easiest to do through the Github UI. Simply edit a page, then instead of committing directly to the branch, create a pull request. Once created, the review app is ready to go. When the pull request is accepted, the review app is deleted and the application is deployed to your staging org.

If you want to work against the latest buildpacks, update the version # (or remove entirely).

Clean up

At any time you can run ./destroy.sh to delete your pipeline and apps.