# Skip deploy for a specific job

**URL:** <https://travis-ci.community/t/skip-deploy-for-a-specific-job/9042>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** travis-yml, build-matrix, build-phases\
**Created:** [June 17, 2020, 6:48pm UTC](https://travis-ci.community/t/skip-deploy-for-a-specific-job/9042 "2020-06-17T18:48:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![thegecko](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/thegecko/32/4696_2.png) [@thegecko](https://travis-ci.community/u/thegecko)\
**Post date:** [June 17, 2020, 6:48pm UTC](https://travis-ci.community/t/skip-deploy-for-a-specific-job/9042/1 "2020-06-17T18:48:55Z")

</div>

Hi,

I’m trying to skip the deploy step for a specific build job (along with other steps), but instead of skipping, the config is expanded to try and deploy using a provider called ‘skip’.

build with the issue here:

[https://travis-ci.org/github/theia-ide/theia-apps/builds/699401823/config](https://travis-ci.org/github/theia-ide/theia-apps/builds/699401823/config)

config:

```auto
      install: skip
      script: <the script to run>
      before_deploy: skip
      deploy: skip

```

expanded config:

```auto
        "install": [
          "skip"
        ],
        "script": [
          <script to be run>
        ],
        "before_deploy": [
          "skip"
        ],
        "deploy": [
          {
            "provider": "skip"
          }
        ]

```

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [June 19, 2020, 1:03am UTC](https://travis-ci.community/t/skip-deploy-for-a-specific-job/9042/3 "2020-06-19T01:03:43Z")

</div>

> [@Deploy to GitHub multiple files from multiple Travis jobs on different conditions](https://travis-ci.community/t/deploy-to-github-multiple-files-from-multiple-travis-jobs-on-different-conditions/5091/2):
>
> A deploy: clause is a part of a job description. So if you need to deploy at multiple moments, you’ll need to make sure that all relevant jobs have a deploy: clause with an appropriate content, this way or another. The ways are: A deploy: at global level will be inherited by all jobs. A deploy: at matrix: include: level will be private for the job The clause cannot be inherited in parts – a job-level clause fully overrides a global one. So you either make a global deploy: clause with a st…

---

<div class="post-metadata">

**Author:** ![thegecko](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/thegecko/32/4696_2.png) [@thegecko](https://travis-ci.community/u/thegecko)\
**Post date:** [June 19, 2020, 8:21am UTC](https://travis-ci.community/t/skip-deploy-for-a-specific-job/9042/4 "2020-06-19T08:21:27Z")

</div>

That’s… confusing

So to confirm, it’s not possible to skip the deploy step in included jobs and this is working as intended?

---

<div class="post-metadata">

**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\
**Post date:** [June 19, 2020, 6:16pm UTC](https://travis-ci.community/t/skip-deploy-for-a-specific-job/9042/5 "2020-06-19T18:16:33Z")

</div>

It is possible

- with a condition on the global deploy clause that would be true for all jobs except this one
- by overriding the inherited `deploy:` clause with a DIY no-op deploy clause like

```auto
provider: script
script: true

```

- It would probably also work if you put an empty `deploy:` clause into the job (checking at [https://config.travis-ci.com/explore](https://config.travis-ci.com/explore) shows that it should)

```auto
deploy:

```