[LOG4J2-2839] Prevent Jenkins from building tagged release candidats

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Component/s: Build
• Assignee: Matt Sicker
• Reporter: Ralph Goers
• Created: 10/May/20 19:42
• Updated: 01/Dec/23 23:14
• Resolved: 01/Dec/23 23:14

Description

When running a release of Log4j the poms are all changed to reflect the new release version and then a tag for the released version is created. Then the poms are updated again to reflect the new snapshot version. When the initial pom changes are completed Jenkins will kick off a build with the release version number and try to deploy it. This will fail.

There is no reason to perform this build as this is exactly what the release build is doing.

All non-SNAPSHOT builds should be ignored by the default Jenkins build.