Jenkins Definintions

For a given Jenkins Multibranch pipeline...

_the_ Bitbucket git repository that _contains_ the Jenkinsfile
_can_ trigger the relevant Jenkins job
_with_ the branch name (i.e. "Omit Branch Name" *not* checked in BitBucket)

_any_ Bitbucket git repository that _does not contain_ the Jenkinsfile
_can only_ trigger the relevant Jenkins job
_without_ the branch name (i.e. "Omit Branch Name" *is* checked in BitBucket)
=============================================================================

There are 2 main categories and some subcategories:

Category A: Job has no test reports configured:

A1: If the last build command executed by Jenkins exits with failure
(that is, non-zero) exit code, the build is considered to be failed.
Permalinks lastBuild, lastUnsuccessfulBuild and lastFailedBuild will
move forward.

A2: If the last build command exits with success (that is, zero) exit
code, the build is successful. Permalinks lastBuild,
lastSuccessfulBuild and lastStableBuild will all move forward.

Category B: Job has one or more test reports configured:

B1: If the last build command executed by Jenkins exits with failure
(that is, non-zero) exit code, the build is considered to be failed.
(Identical to A1). Permalinks lastBuild, lastUnsuccessulBuild and
lastFailedBuild will move forward.

B2: If the last build command exits with success (that is, zero) exit
code but test reports have some failed tests, the build is unstable.
Permalinks lastBuild, lastSuccessfulBuild and lastUnsuccessfulBuild
will move forward.

B3: If the last build command exits with success and all test have
passed, the build is stable. Permalinks lastBuild, lastSuccessfulBuild
and lastStableBuild will move forward.