# Continuous Deployment Security

**URL:** <https://discuss.circleci.com/t/continuous-deployment-security/17550>\
**Category:** Build Environment\
**Created:** [October 19, 2017, 4:31pm UTC](https://discuss.circleci.com/t/continuous-deployment-security/17550 "2017-10-19T16:31:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![joaomneto](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/joaomneto/32/16966_2.png) [@joaomneto](https://discuss.circleci.com/u/joaomneto)\
**Post date:** [October 19, 2017, 4:31pm UTC](https://discuss.circleci.com/t/continuous-deployment-security/17550/1 "2017-10-19T16:31:48Z")

</div>

Hi there,

I have a project in Github for an Android app where I’m currently using circleCi.

I was configuring a workflow to perform the deployment to Google Play Store using a gradle task however I running in cricles trying to prevent other developers from triggering the deployment.

I have a protected branch where I intend to push the code version I want to deploy. So no one can force push to it and my workflow configuration states the task only runs for.this branch. However what’s preventing another developer to change config.yml and allowing the deployment job to run on all branches including his.

Am I missing something? Is there anyway to restrict job execution outside the config.yml.

I’m using v2.0 btw.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/circleci/original/3X/5/1/511608acda8e85906e15909b57bd0a46c1dbe291.png) [@system](https://discuss.circleci.com/u/system)\
**Post date:** [June 18, 2018, 11:40am UTC](https://discuss.circleci.com/t/continuous-deployment-security/17550/2 "2018-06-18T11:40:00Z")

</div>