Could I disable production deployment on demand before comitting

Question

I am searchin for a Solution to say in The commit: deploy on staging and production or deploy just staging.

What i‘ve done so far: Setting up pipeline with two  steps. One step for staging on for production.

Deployment working fine for now.

But now i want to deploy only on staging eccept i write something in the commit to say: on production too!

albertaugustin · Answer

Hi Nathan, thanks for answering.

If there's no switch between example: staging and production. How do i divide these both servers, base on the same GIT-Repo?

Here is my example:

image: samueldebruyn/debian-git

pipelines:
default:
- step:
caches:
- node
deployment: staging
script:
- apt-get update
- apt-get -qq install git-ftp
- git ftp push --user $FTP_USERNAME --passwd $FTP_PASSWORD ftp://staging.ja.do/
- step:
caches:
- node
deployment: production
script:
- apt-get update
- apt-get -qq install git-ftp
- git ftp push --user $FTP_USERNAMEPROD --passwd $FTP_PASSWORDPROD ftp://production.ja.do/

Thanks in advance, Albert

lassian · Answer

Hi Albert,

Could you provide an example of your yaml configuration.

If the second step, that deploys to production, is it a manual step?

If so there is currently no feature in pipelines to automatically kick off this manual step triggered conditionally based on the contents of a commit.

Kind Regards,
Nathan