Hi, I've switched to the CD implemented on JEP-229 for genexus-plugin (https://github.com/jenkinsci/genexus-plugin) and couldn't find a way to publish experimental releases, as I used to do based on what's described at https://www.jenkins.io/doc/developer/publishing/releasing-experimental-updates/
First tried including "-beta" in the changelist property in pom.xml <changelist>999999-beta-7-SNAPSHOT</changelist> The first release was successful ( https://github.com/jenkinsci/genexus-plugin/releases/tag/250.v1b0d8b7f9a4a ) but got published as version 250.v1b0d8b7f9a4a , that is, not including the "-beta" qualifier and thus became available at the standard update center ( https://updates.jenkins.io/update-center.json ) instead of the intended experimental one ( https://updates.jenkins.io/experimental/update-center.json ) Then I tried moving the "-beta" qualifier to the <version> itself (see https://github.com/jenkinsci/genexus-plugin/commit/fbb5777ce84f5c8a4dfe51ddd5dc3166fc85e06e#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8 ) As you can see on the build log at https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Plugins/pipelines/genexus-plugin/branches/master/runs/115/log/?start=0 the -beta qualifier was present when installing the genexus.hpi file: [2021-11-05T22:08:42.395Z] [INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ genexus --- [2021-11-05T22:08:42.395Z] [INFO] Installing C:\Jenkins\workspace\Plugins_genexus-plugin_master\target\genexus.hpi to C:\Jenkins\workspace\Plugins_genexus-plugin_master@tmp\m2repo\org\jenkins-ci\plugins\genexus\251.vfbb5777ce84f-beta\genexus-251.vfbb5777ce84f-beta.hpi [2021-11-05T22:08:42.395Z] [INFO] Installing C:\Jenkins\workspace\Plugins_genexus-plugin_master\target\genexus-251.vfbb5777ce84f-beta.pom to C:\Jenkins\workspace\Plugins_genexus-plugin_master@tmp\m2repo\org\jenkins-ci\plugins\genexus\251.vfbb5777ce84f-beta\genexus-251.vfbb5777ce84f-beta.pom [2021-11-05T22:08:42.395Z] [INFO] Installing C:\Jenkins\workspace\Plugins_genexus-plugin_master\target\genexus.jar to C:\Jenkins\workspace\Plugins_genexus-plugin_master@tmp\m2repo\org\jenkins-ci\plugins\genexus\251.vfbb5777ce84f-beta\genexus-251.vfbb5777ce84f-beta.jar [2021-11-05T22:08:42.395Z] [INFO] Installing C:\Jenkins\workspace\Plugins_genexus-plugin_master\target\genexus-sources.jar to C:\Jenkins\workspace\Plugins_genexus-plugin_master@tmp\m2repo\org\jenkins-ci\plugins\genexus\251.vfbb5777ce84f-beta\genexus-251.vfbb5777ce84f-beta-sources.jar [2021-11-05T22:08:42.395Z] [INFO] Installing C:\Jenkins\workspace\Plugins_genexus-plugin_master\target\genexus-javadoc.jar to C:\Jenkins\workspace\Plugins_genexus-plugin_master@tmp\m2repo\org\jenkins-ci\plugins\genexus\251.vfbb5777ce84f-beta\genexus-251.vfbb5777ce84f-beta-javadoc.jar But then later, when trying to archive it as artifact, it failed to find it because it didn't expect it to contain that "-beta" qualifier: [2021-11-05T22:09:38.560Z] Archiving artifacts [2021-11-05T22:09:39.220Z] java.lang.InterruptedException: no matches found within 10000 [...] [2021-11-05T22:09:39.220Z] No artifacts found that match the file pattern "**/*251.vfbb5777ce84f/*251.vfbb5777ce84f*". Configuration error? Is publising experimental releases supported? I'm not sure I'm doing it the way it's supposed to be done... That "**/*${changelist}/*${changelist}*" pattern does include a trailing wildcard after the filename, so I guess the problem might be fixed adding a wildcard after the folder too (that is, changing the pattern to ""**/*${changelist}*/*${changelist}*"") ? Thanks in advance for any advice, Regards, -- jlr -- 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/faac5382-c55b-46e2-ac88-7c0fa700b22en%40googlegroups.com.
