Making sure that stage/production deploy behaves like dev does by adding rules... - #1p88d4x

Making sure that stage/production deploy behaves like dev does by adding rules to check for WEB_PROJECT/ANDROID_PROJECT/IOS_PROJECT variables.

CMT would have to set WEB_PROJECT=true for backend apps and either ANDROID_PROJECT=true or IOS_PROJECT=true for fe mobile apps.

Tested:

• https://gitlab.builder.ai/devsecops/gavinvdm/gvdm-app/-/pipelines/4227239
• https://gitlab.builder.ai/devsecops/gavinvdm/gvdm-app-fe/-/pipelines/4227139

Notes about testing:

For app:

• Commit to master will trigger deploy to dev jobs.
• Master will be auto tagged for commits but not deployed anywhere.
• Pushing new tags ( without -o ci.skip ) will trigger deployments to uat/stage/prod.

For app web:

• Commit to master will trigger deploy to dev jobs.
• Master will be auto tagged for commits but not deployed anywhere.
• Pushing new tags ( without -o ci.skip ) will trigger deployments to uat/stage/prod.
• This should work where WEB_PROJECT == true

For app mobiles:

• Changes to master with upload the app but not deploy because ANDROID_DEPLOY_TO_GOOGLE_PLAY_STORE or IOS_DEPLOY_TO_APPLE_APP_STORE is not set to true.
• Manual tags will only be relevant to source control (no ci jobs)
• Deployment jobs for app or app web do not run in these pipelines.