The legacy code started this work. No reason information available

Question

There is always an additional build with the "promote build plugin" running on jenkins, which I don't know why ...

Here is the whole pipeline:

• dev compiles "feature_branch" on github
• jenkins runs the build on "feature_branch" to run all unit tests.

in assembly:

• If the branch passes the test, it should go to the "code review" (here I use boost_build_plugin, manually advertise after viewing the code),
• I use “Trigger / call builds for other projects” as an action to run the “deploy-job” for the build only if it passes the code check.

during deployment-work:
I see that the new assembly starts and the feature_branch function merges, but there is always another assembly with "no change", "Legacy" started this work. No reason information available "

I was going to try to solve this problem all day, any help?

Answer 1

You probably have a post-commit hook that launches the same job via url or jenkins-cli

Edit after OP comments:

But I’m starting to wonder about the deployment-task, I didn’t configure “Build when the change is transferred to Github”, instead I use “Build when another project is moving forward", so I think that even github hook works, it won’t end with additional assembly?

Well, there is your problem ^^. The Trigger / Call builds engine is completely separate from " Build when another project is moving forward ."

• The first allows you to launch a new assembly from buildstep or a proposal (tied to this special promotion).
• The latter initiates the creation of any promotion of the customized task. This is the inverse of the configuration. Create other projects .

In addition, assembly triggers are not AND'ed, they are OR'ed. Build when a trigger happens. Remove " Build while moving another project " from configuration to git to get rid of extra builds.

Now, if you want to prevent blocking failures from being caused by SCM commit hosts, you need to make sure that the SCM polling is not configured in the job. In addition, different SCM plugins have their own parameters (I know that the SCM SVN plugin allows you to “ignore hooks after commit”, I don’t know about the git SCM plugin)