Preventing auto-deploy of builds to DEV

Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

• When a new pull request merges to the develop branch, it auto-builds and deploys to the "dev" environment. How can this be prevented?

Environment

• Liferay Cloud
• Liferay PaaS

Resolution

• Per this article on Continuous Integration, we see that the behavior is the default and expected. This means that whatever is pushed to the "develop" git branch, is deployed into the project's "dev" environment.
  
  Here are the associated configurations:
  

  "LCP_CI_DEPLOY_BRANCH": "develop"
  "LCP_CI_DEPLOY_TARGET": "dev"

   
  FYI: Work is ongoing to make improvements to the above-linked article, to better clarify this functionality and its usage. This can be followed on LRDOCS-8350.
   
  Workaround
  To prevent the automatic deployment of builds to "dev", in the CI service LCP.json we need to add a configuration pointing the BRANCH variable to a non-existing branch. 
  
  For example:
  

  "LCP_CI_DEPLOY_BRANCH": "xxxxxx"

  (Note: "LCP_CI_DEPLOY_TARGET": "dev" is not required)
  
  

Additional Information

• If the above suggestion still does not prevent the behavior, please try updating the CI service version to the latest one.