Hello!
I have a plugin - https://github.com/jenkinsci/report-jtreg-plugin/ - where
main branch is aligned with future, prototypeJS-less jenkins, and so it have
another branch, which is compatible with current live jenkinses.
In this setup, I was able to do the only live version of this plugin - 2.1.
IIRC, I had released this one via `mvn release:prepare release:perform`
Recently, we had heavily refactored the plugin, so ti is now multi-module maven plugin, with lib, plugin (with bundled lib), and two standalone services which depends on lib, and - if manually started - can comunicate with plugin. The
release here, of course counts only with the hpi plugin.
Today I wished to release 2.3 but I underestimated it, and (after quite a
struggling), only top level pom.xml got uploaded to artifactory.
However, the commits to master, seems to be (via GHactions autorelease)
correctly propagated to artifactory as incremental per-merge binaries,
including lib, plugin and also both services.
So,encouraged by this, I had manually pushed to not-main branch, and tagged,
and hoped that incremntalify will pick it up and release. Nope.
I guess best would be to setup incrementalify to release only from my non-main
branch (until prototypejs-less jenkins reaches LTS), is ti possible?
If not, any hint on how can I manually release, or jsut upload, binaries from
the branch to artifactory?
Thanx!
J.
--
Jiri Vanek Mgr.
Principal QA Software Engineer
Red Hat Inc.
+420 775 39 01 09
--
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/3527668e-9cf3-4f91-834c-5270b1a6d7ea%40redhat.com.
