Environment manual hob

We try to split the deployments between developers and tester.

The pattern will be at high level as followed:

After a pull to Gitlib a automatic deployment will occur in the Dev environment.
One ore more manual jobs will be available to be start the deployment to the Test environment.

The security we arrange by the environment setup. For some reason we can’t see the “Test deployment” job when checking the Test environment. We have tried the prepare option as well but still is it not be showed on the Test environment.

The question is how can this be solved? So the idea is: Automatic deployment job in Dev (which is working fine at the moment) and a manual deployment in Test but visible by the environment functionality.

Hi @mboer

Can you post your .gitlab-ci.yml file?

Hello snim2,

Hereby:

So the idea is that jobs in stage tst_deploy will be visible when you click on environment TST. From there the stage should be started manually.

includes

include:

  • local: ‘/common/yml/ibis_pipeline_common.yml’

config specific templates

.deploy_config_template:
script:
- bash pipeline_files/config/scripts/deploy_config.sh

start of pipeline

stages:

  • setup_pipeline
  • unit_test
  • publish_artifacts
  • dev
  • tst_deploy

######################## PUBLISH ########################

setup_pipeline:
extends: .setup_pipeline_template

unit_test:
extends: .unit_test_template
script:
- bash pipeline_files/config/scripts/maven_build.sh
- bash pipeline_files/config/scripts/unit_test.sh

publish_artifacts:
extends: .publish_artifacts_template
script:
- bash pipeline_files/config/scripts/maven_build.sh

########################## DEV ##########################

dev_deploy_config:
extends: .deploy_config_template
stage: dev
rules:
- !reference [.deploy_rules_dev,rules]
environment:
name: “DEV”
deployment_tier: development

dev_health_check_config:
extends: .health_check_template
stage: dev
needs: [“setup_pipeline”, “dev_deploy_config”]
rules:
- !reference [.hc_rules_dev,rules]
variables:
HC_SCOPE: “CONFIG”
environment:
name: “DEV”
deployment_tier: development
action: prepare

dev_health_check_ibis:
extends: .health_check_template
stage: dev
needs: [“setup_pipeline”, “dev_deploy_config”]
rules:
- !reference [.hc_rules_dev,rules]
variables:
HC_SCOPE: “IBIS”
environment:
name: “DEV”
deployment_tier: development
action: prepare
allow_failure: true

########################## TST ##########################

tst_deploy_config:
extends: .deploy_config_template
stage: tst_deploy
rules:
- !reference [.deploy_rules_tst,rules]
environment:
name: “TST”
deployment_tier: testing

tst_health_check_config:
extends: .health_check_template
stage: tst_deploy
needs: [“setup_pipeline”, “tst_deploy_config”]
rules:
- !reference [.hc_rules_tst,rules]
variables:
HC_SCOPE: “CONFIG”
environment:
name: “TST”
deployment_tier: testing
action: prepare

tst_health_check_ibis:
extends: .health_check_template
stage: tst_deploy
needs: [“setup_pipeline”, “tst_deploy_config”]
rules:
- !reference [.hc_rules_tst,rules]
variables:
HC_SCOPE: “IBIS”
environment:
name: “TST”
deployment_tier: testing
action: prepare

tst_soapui_test:
extends: .soapui_test_template
stage: tst_deploy
needs: [“setup_pipeline”, “tst_deploy_config”,“tst_health_check_config”,“tst_health_check_ibis”]
variables:
environment:
name: “TST”
deployment_tier: testing
action: prepare

tst_jmeter_test:
extends: .jmeter_test_template
stage: tst_deploy
needs: [“setup_pipeline”, “tst_deploy_config”,“tst_health_check_config”,“tst_health_check_ibis”,“tst_soapui_test”]
environment:
name: “TST”
deployment_tier: staging
action: prepare

Regards,
Maurice