Hi, some exemple with git.

The base structure is

force-dev-tool remote add NAME_REMOTE "login_XXX" "passwordtoken" --default
git diff HEAD~1 HEAD --no-renames | force-dev-tool changeset create feature-merge -f
force-dev-tool deploy -c -t -d config/deployments/feature-merge NAME_REMOTE


In the pipeline you can create manual steps

1 - Does nothing
2 - Deploy to Staging ( Or any Sandbox )
3 - After deploy Staging, the button has enable to click and deploy to another org.

image: node:7.5.0
pipelines:
branches:
develop:
- step:
name: Deploy to UAT
deployment: test
script:
- echo Deploy to UAT
- git diff HEAD~1 HEAD --no-renames --name-only
- step:
caches:
- node-global
name: Deploy to staging
deployment: staging
trigger: manual
script:
- npm install --global force-dev-tool
- force-dev-tool remote add staging $STAGING_USERNAME $STAGING_PASSWORD
- echo Deploy to staging
- git diff HEAD~1 HEAD --no-renames | force-dev-tool changeset create feature-merge -f
- force-dev-tool deploy -d config/deployments/feature-merge staging
- step:
caches:
- node-global
name: Deploy to PRODUCTION
deployment: production
trigger: manual
script:
- npm install --global force-dev-tool
- force-dev-tool remote add production $PRODUCTION_USERNAME $PRODUCTION_PASSWORD https://login.salesforce.com
- echo Deploy to production
- git diff HEAD~1 HEAD --no-renames | force-dev-tool changeset create feature-merge -f
- force-dev-tool deploy -c -t -d config/deployments/feature-merge production
definitions:
caches:
node-global: /usr/local/lib/node_modules