## TL;DR

Second, from a multibranch project, you can use the environment variable BRANCH_NAME to make logic conditional on the current branch. Update: stage 'test-downstream' node { def job = build job: 'some-downtream-job-name' } Still, when executed I get an error No parameterized job named

## Steps

1. First of all, it is a waste of an executor slot to wrap the build step in node . Your upstream executor will just be sitting idle for no reason. Second, from a multibranch project, you can use the environment variable BRANCH_NAME to make logic conditional on the current branch. Third, the job parameter takes an absolute or relative job name. If you give a name without any path qualification, that would refer to another job in the same folder, which in the case of a multibranch project would mean another branch of the same repository. Thus what you meant to write is probably if (env.BRANCH_NAME == 'master') { build '../other-repo/master' }

## When to use

You are seeing this: First of all, it is a waste of an executor slot to wrap the build step in node. Use this skill when you run into "How can I trigger another job from a jenkins pipeline (jenkinsfile) with GitHub Org Plugin?".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.