Jenkins builds somewhat on a solo mission
Jenkins has a way to set up a job for two different builds, which can be triggers for different reasons.
As an example
(1) Create descriptors first and only run manually.
(2) The second build starts automatically every time a commit occurs.
I know that I can split this into two different posts, each with only inline and triggers, but I don't want to.
source to share
Do the compilations have something in common? If they are using the same build process, but the release requires additional pre / post-build steps, then Disabling the plugin is exactly what you need.
It allows you to define additional pre / post-build steps that are only performed when you manually start a release build.
However, this is contrary to the concept of CI. In CI, your finally released build would be promoted from the regular CI auto build.
source to share