git - Legacy code started this job. No cause information is available -

Promoting Jenkins on "promoting the plugin" always creates an extra, which I do not know ... ... <

< p>

On the build-job:

• If he passes the branch exam, he should go to "code review" (see I encourage promotion after code, use promotion_build_plugin here),
• I pass a review of the code, That's when I wanted to trigger a "deployed-job" Uses "Triggers / Calls on Other Projects" for

  Posted in Jobs:
  I can see that a new build has been started and merged this feature_branch It's done, but there is always another build with "there is no change"; Legacy code

  "text">

  You may have a post-cut hook that is triggering the same work via URL or Jenkins-CLI

  Edit after OP comments:

  But I started to wonder at the deployment-job, I did not have a "builder made any changes when Github was pushed", instead, I use "build" "I think that the Geethbal hook has also started, will not it end with an extra creation?"

  Okay, Your problem is ^^

  • The " trigger / call build " mechanism completely promotes another project from " Build"
    • Create a new build with a buildstep or a promotion (associated with that specific publicity). Trigger.
    • A build will be triggered on any promotions of a configured job that is "Building Other Projects" "Post-Build Configuration Is inversion.

      In addition, build triggers are not AND'ed , they are or when it or that or is triggered, then remove the " build build " from the configuration to snooze the extra build.

      Now, if you want to stop triggering by SCM committed hook, you need to ensure that SCM voting is not configured on the job. Alternatively, various SCM plugins have their own options (I know that the SVN SCM plugin "allows to ignore post-commit hooks"; do not know about git SCM plugins)