The build counter in my pipelines does not start at 1.

Last Reviewed:2025-10-06()
1 minute readKnowledge base

Issue

I have created a new Pipeline job that was previously deleted on a controller using CloudBees High Availability (active/active), and the counter is not starting with the number 1.

Environment

Resolution

When you have a Pipeline that already ran at least one build, and you delete the Pipeline, the expected behavior is that if you create another Pipeline with the very same name, the build counter will reset. If you have CloudBees High Availability (active/active) enabled on an affected version, and you create a new Pipeline with the same name as a previously deleted Pipeline, the build counter will reuse the same number as the deleted Pipeline.

This issue will be fixed in a future CloudBees CI release, and this article will be updated with the specific version number with the fix.

Workaround

Restarting your controller will reset those counters for the previously deleted Pipeline.

Tested product/plugin versions

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.