How do I specify job dependency running in another workflow? #26632

rn4n · 2019-10-06T06:04:09Z

rn4n
Oct 6, 2019

I’ve this workflow:

name: Testing on: [push, pull_request] jobs: testing: runs-on: ubuntu-latest steps: - uses: actions/checkout@v1 - name: Setup Environment (Using NodeJS 12.x) uses: actions/setup-node@v1 with: node-version: 12.x - name: install dependencies run: npm install - name: Run unit tests and collect coverage run: npm run test:unit

Now, I would like to create another workflow (deploy.yml) to deploy my application on Netlify.

How can specify that this deploy depends of the successfully run of “testing” job ?

“testing” and “deploy” are in different workflows files.

name: Deploy
on:
  push:
    branches:
      - master
jobs:
deploy:
# ... ??? ...

Thanks.

Answered by brpaz

Oct 6, 2019

You cant.

What you can do is to use the same workflow file and then use conditions to trigger or not a specific job.

If you want to run a job only when there is a push to master branch you can do it like this:

jobs:
   deploy:
       if: github.event_name == 'push' && github.ref == 'refs/heads/master'

Another option for deployments is to create a tag when you are ready to deploy and then having a seperate workflow that is listening to the push tag event and trigger your deploy.

View full answer

brpaz · 2019-10-06T17:46:13Z

brpaz
Oct 6, 2019

You cant.

What you can do is to use the same workflow file and then use conditions to trigger or not a specific job.

If you want to run a job only when there is a push to master branch you can do it like this:

jobs:
   deploy:
       if: github.event_name == 'push' && github.ref == 'refs/heads/master'

Another option for deployments is to create a tag when you are ready to deploy and then having a seperate workflow that is listening to the push tag event and trigger your deploy.

2 replies

neopunisher Aug 9, 2022

I think you can do it now with workflow run https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#workflow_run described here https://stackoverflow.com/questions/58457140/dependencies-between-workflows-on-github-actions

daveisfera Feb 3, 2023

To anyone looking to use this, it only runs on the default branch and not the branch that actually triggered the workflow that this one depends on ( see notes about this here )

justfathi · 2019-10-17T23:13:43Z

justfathi
Oct 17, 2019

Will this be a feature that will be added in the future?

0 replies

mingrammer · 2020-01-03T09:30:57Z

mingrammer
Jan 3, 2020

I think it should be supported!

0 replies

DannyBen · 2020-02-04T18:44:21Z

DannyBen
Feb 4, 2020

I would love to have such a feature. Perhaps it is simple (for GitHub) to implement, by adding another “on” event trigger?

on:
  workflow_complete:
workflow: Test
    types: [success]
jobs:

...

or

on:
  workflow_success:
    workflow: Test

Seems like a must have for “test then deploy” flow, where it makes sense to separate the two workflows instead of toying around with conditions and have everything as one pile of YAML mess.

0 replies

moltar · 2020-02-18T05:10:38Z

moltar
Feb 18, 2020

This solution would cause a problem if you are using matrix. It will run for every matrix item basically.

This really needs to be solved. I can’t believe this doesn’t work!

It’s a pretty common requirement.

I need to run tests in a matrix.

2. I also want to deploy only on master, but only if all tests pass.

Right now this is basically impossible.

0 replies

lulubobst · 2020-03-20T19:13:50Z

lulubobst
Mar 20, 2020

When will this be supported?

0 replies

shinny-hongyan · 2020-04-21T08:35:29Z

shinny-hongyan
Apr 21, 2020

I have try this code,

on:
  workflow_success:
    workflow: Test

but it does not work , and show me

`workflow_success` is not a valid event name

0 replies

slinkydeveloper · 2020-04-23T20:44:55Z

slinkydeveloper
Apr 23, 2020

Same here, I’m facing the same problem. On every master push I need to test different JDK versions and then I publish a package snapshot, but i don’t know how to solve it.

0 replies

jeffmaher · 2020-07-05T19:12:29Z

jeffmaher
Jul 5, 2020

Instead of creating a new workflow, you might just create a dependent job. See the documentation for jobs.<job_id>.needs.

0 replies

AlexMcConnell · 2020-07-14T13:08:02Z

AlexMcConnell
Jul 14, 2020

Yes, you can put it all into different jobs in one workflow, but breaking up your large files into logically separated smaller files is a pretty universal programming best practice, and that’s extra true when you have a lot of different things branching off from one spot (like your tests passing or whatever). If they want to define a workflow as all of those branches together, that’s fine, but that means we need to be able to split out jobs into different files. Otherwise, we’re forced to either write code in some scripting language that builds into the yaml code for our workflow or create some sort of funky trigger event, both of which are incredibly hacky.

0 replies

asarkar · 2020-07-25T08:18:10Z

asarkar
Jul 25, 2020

This is possible using the GitHub Workflow runs API. Assuming Testing workflow fails if the testing step fails, in the Deploy workflow, you get the conclusion of the latest Testing workflow run using some cURL and jq foo, and then exit if the output is not success. See this project, where publish depends on ci.

0 replies

NasAmin · 2020-10-02T11:33:15Z

NasAmin
Oct 2, 2020

I am also interested in this as well. Workflow depencencies is a must to allow engineers breakdown their pipelines logically in separate files instead of having to maintain huge files.
I thought I didn’t like GitLab’s approach but they are miles ahead!

0 replies

edudepetris · 2020-10-09T06:07:12Z

edudepetris
Oct 9, 2020

could be possible with workflow_run…

Ref.: Events that trigger workflows - GitHub Docs

<a href="https://github.community/t/workflow-run-completed-event-triggered-by-failed-workflow/128001">Workflow_run completed event triggered by failed workflow</a> <a class="badge-wrapper  bullet" href="/c/code-to-cloud/github-actions/41"><span class="badge-category-parent-bg" style="background-color: #6a737d;"></span><span class="badge-category-bg" style="background-color: #2188ff;"></span><span style="" data-drop-close="true" class="badge-category clear-badge" title="Discussion and questions about GitHub Actions—automation for all of your development workflows, now with world-class CI/CD.">GitHub Actions</span></a>

I have a workflow triggered as follows: name: Production deploy on: workflow_run: workflows: ["Stage deploy"] types: - completed
I expect that after the stage deploy (which also runs API tests) completes successfully, then the production deploy would start. However, I just watched a failed stage deploy (which skipped its API tests due to the failed deploy) also trigger a production deploy. Is there a different “types” value for workflow_run that causes it not to fire if the wor…

0 replies

mobeigi · 2020-12-20T05:47:05Z

mobeigi
Dec 20, 2020

Surprised this isn’t supported. It would be nice to have multiple workflows nicely separated (one for builds, one for tests, one for deployments) and have some depend on others. It’s possible now using all jobs in a single workflow but its a little messier imo.

0 replies

jakoch · 2021-03-21T13:51:54Z

jakoch
Mar 21, 2021

Hmmm… so.
You go from “build” workflow to “API” to “status var” to “check, if you can publish” to “publish”.
This is a really clever workaround for a missing feature!

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitHub Community

How do I specify job dependency running in another workflow? #26632

{{title}}

Replies: 15 comments 2 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

How do I specify job dependency running in another workflow? #26632

Replies: 15 comments · 2 replies

Replies: 15 comments 2 replies