[
https://issues.apache.org/jira/browse/LOG4J2-2839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker resolved LOG4J2-2839.
---------------------------------
Resolution: Not A Problem
No longer relevant as we've switched to using GitHub Actions where we've
configured the build not to do this.
> Prevent Jenkins from building tagged release candidats
> ------------------------------------------------------
>
> Key: LOG4J2-2839
> URL: https://issues.apache.org/jira/browse/LOG4J2-2839
> Project: Log4j 2
> Issue Type: Improvement
> Components: Build
> Reporter: Ralph Goers
> Assignee: Matt Sicker
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
