The system is not designed to support marking releases as beta. I am not sure such a requirement is even conceptually compatible with the style of automatic deployment. If such a requirement is common, I think it would need to be done differently, as a true promotion: the same version number and binary artifact would initially be published to the experimental update center and then subsequently marked somehow as eligible for the main update center.
Consider skipping the experimental update center and gating new features behind a flag that users can opt into. If only a select few users actually run the experimental releases to begin with, they can also obtain them from the incrementals repository—you can turn off automatic releasing of the default branch and trigger releases only with the manual workflow, while every successful trunk build will be deployed to the incrementals repository where it can be downloaded on demand for beta testing. -- 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/CANfRfr304LiQ3Ten_cDaqt5DAJ-4qO-Gj%2B-V3z2YfzcJCZ%2BcCQ%40mail.gmail.com.
