Job execution will attempt to use a stale build number under certain conditions

[Michael Katkin]

Hey guys,

There's some interesting behavior I noticed after installing the latest job-history plugin (2.12) on our Jenkins server (1.607). Whenever the job configuration is changed, and the next execution is triggered by a timer, the build will fail because it attempts to reuse an old build number.

Some googling around lead me to the Jira about how reloading the configuration from disk can cause this. In our case, this is not what's happening. We don't trigger reloading either manually or though a job (if that's possible). 

I'd be happy to look for patterns; however, as our servers run behind several flavors of cooperate firewall, I cannot transmit raw files. In fact I have to copy all the information directly to my non-work related email.

I greatly appreciate your time in looking into this and making Jenkins better

Cheers,

Michael Katkin

[Jesse Glick]

On Mon, Jan 25, 2016 at 4:32 PM, Michael Katkin
<katkin....@gmail.com> wrote:
> There's some interesting behavior I noticed after installing the latest
> job-history plugin (2.12)

`jobConfigHistory` you mean?

> on our Jenkins server (1.607). Whenever the job
> configuration is changed, and the next execution is triggered by a timer,
> the build will fail because it attempts to reuse an old build number.

No clue offhand how that could be, but if it is indeed reproducible,
file a bug for it, I suppose starting in that plugin until it is shown
to be a core bug.