On Mon, Jan 25, 2016 at 4:32 PM, Michael Katkin <[email protected]> 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. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1OBynY%2B2z0tTarJ0AJKpCXnvvawXHdWGW%3DS%3DLkE6-A2A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
