On Sunday, November 7, 2021 at 8:07:46 PM UTC-3 Jesse Glick wrote:
> 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. > Regarding 'conceptually compatible' I'm not sure whether you refer to automatic deployment in general or to the way it's implemented in this case, using incremental versions in particular. > If such a requirement is common, > Personally I find it practical to have a separate release channel for beta releases and its corresponding discovery and update simplicity for end users: just change the URL to be able to see possible updates and apply them through the UI), but not sure if it may be considered as common. The update channels currently list 1874 plugins and comparing the experimental at https://updates.jenkins.io/experimental/update-center.json with the standard at https://updates.jenkins.io/current/update-center.json there are right now differences for around 30 plugins. > 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. > FWICS, the update center currently checks the version to exclude artifacts containing "alpha" or "beta" from the regular update center: https://github.com/jenkins-infra/update-center2/blob/1690b80d6a92489c1be9ba51105c47ba4f3e5d9d/src/main/java/io/jenkins/update_center/MavenArtifact.java#L88 It also checks for "SNAPSHOT" and "JENKINS" to ignore those: https://github.com/jenkins-infra/update-center2/blob/e72cebfa594356c94f0c40d310c956058439e576/src/main/java/io/jenkins/update_center/BaseMavenRepository.java#L56 But if keep adding qualifiers to versions is a problem, then yes, it would require moving those marks (and the update center code) somewhere else. > > Consider skipping the experimental update center and gating new features > behind a flag that users can opt into. > Yes, feature flags may help on some particular scenarios but not for many beta processes. > 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. > Agree, that would be a work-around, but it does penalize both the CD experience for the developer and the discover and update experience for beta testers. -- 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/e270f5ea-d286-45d9-9833-1b3ade248e48n%40googlegroups.com.
