On Wed, Nov 10, 2021 at 7:26 PM José Lamas Ríos <j...@genexus.com> wrote:

> GitHub does allow marking releases as in draft state and also, as a
> separate concept, optionally marking them as 'pre-release'
>

You are right, pre-release status is what I was thinking of, not draft. I
have not used this feature before but I presume you can retroactively
remove that status by editing a release. Thus `jenkins-maven-cd-action`
should have an option to mark the new release as pre-release (while still
taking it out of draft status as today); and the UC generator should
automatically limit a plugin version to the experimental UC when it can
find an associated GH release and that release is marked as pre-release.
The latter enhancement would also be a much friendlier way for users of
`maven-release-plugin` to temporarily hold back wide distribution of a new
version, without needing to run MRP all over again with a new version
number.

In my previous experiment I had tried adding "-beta" to the <version> in
> the pom file…
>

It might be possible to make something like that work in the current scheme
but it would certainly be a workaround. The intention of JEP-229 is that
you should simply be able to merge PRs to functional code and have the
resulting binaries be available, without ever touching the Maven `version`
field after initial setup.

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr34Q1KcHWYVzaC_SdJqBxg-fYoXP3AwrooB_2YQzSGttg%40mail.gmail.com.

Reply via email to