> On 10/26/23 14:03, Ullrich Hafner wrote:
I think the incremental tools do not work with multi-module projects. I always 
cd to my plugin folder and start mvn release from there.

Hello! Thanx a lot! that would work, and also it is what I tried. There must be 
some misconfiguration, or I had missed anything, because  when running
 $ cd report-jtreg-plugin  # top level project as cloned form 
https://github.com/jenkinsci/report-jtreg-plugin/
 $ mvn clean install       # all passes
 $ cd report-jtreg-plugin  # the submodule with plugin
 $ mvn release:prepare
... dies :
[INFO] Executing: /bin/sh -c cd 
'/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin' && 'git' 'commit' 
'--verbose' '-F' '/tmp/maven-scm-1232529661.commit'
[INFO] Working directory: 
/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin
[INFO] Executing: /bin/sh -c cd 
'/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin' && 'git' 
'symbolic-ref' 'HEAD'
[INFO] Working directory: 
/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin
[INFO] Executing: /bin/sh -c cd '/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin' && 'git' 'push' 'g...@github.com:jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin' 'refs/heads/chartjs-1-rebasedToRefactored:refs/heads/chartjs-1-rebasedToRefactored'
[INFO] Working directory: 
/home/jvanek/git/report-jtreg-plugin/report-jtreg-plugin
...
[ERROR] The git-push command failed.
[ERROR] Command output:
[ERROR] fatal: remote error:
[ERROR]  jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin is not a 
valid repository name
[ERROR] Visit https://support.github.com/ for help
[ERROR]


Where indeed, the 
g...@github.com:jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin is 
nonsese (should be jsut 
g...@github.com:jenkinsci/report-jtreg-plugin-plugin.git)

TYVM!

 J.



Am 26.10.2023 um 12:10 schrieb Jiri Vanek <jva...@redhat.com>:

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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3527668e-9cf3-4f91-834c-5270b1a6d7ea%40redhat.com.


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/872d6b3b-2399-4c08-813b-9dfd2ac3c9a6%40redhat.com.

Reply via email to