auto release form branch or manual release of multimodule project

Jiri Vanek

unread,

Oct 26, 2023, 6:10:45 AM10/26/23

to jenkin...@googlegroups.com, Patrik Cerbak

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

Ullrich Hafner

unread,

Oct 26, 2023, 8:03:32 AM10/26/23

to JenkinsCI Developers

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.

> --
> 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-de...@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

unread,

Oct 26, 2023, 8:51:28 AM10/26/23

to jenkin...@googlegroups.com, Ullrich Hafner

> 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.

Daniel Beck

unread,

Oct 26, 2023, 9:06:13 AM10/26/23

to jenkin...@googlegroups.com

On Thu, Oct 26, 2023 at 2:51 PM Jiri Vanek <jva...@redhat.com> wrote:

[ERROR] jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin is not a valid repository name

Looks like the attributes in https://github.com/jenkinsci/archetypes/blob/8203c822c89145f74d077c4895fd691c7d61c893/empty-plugin/src/main/resources/archetype-resources/pom.xml#L24 could fix this?

Jiri Vanek

unread,

Oct 26, 2023, 10:04:07 AM10/26/23

to jenkin...@googlegroups.com

Right.

I think I'm lacking imagination how to use them then.
I was fiddling with https://github.com/jenkinsci/report-jtreg-plugin/blob/master/pom.xml#L27 (mostly reset to <gitHubRepo>jenkinsci</gitHubRepo> but it did not did the job.
If you have a stronger kick to me, please share!

TYVM!
J.

On 10/26/23 15:05, 'Daniel Beck' via Jenkins Developers wrote:

>
>
> On Thu, Oct 26, 2023 at 2:51 PM Jiri Vanek <jva...@redhat.com <mailto:jva...@redhat.com>> wrote:
>
> [ERROR] jenkinsci/report-jtreg-plugin-plugin.git/report-jtreg-plugin is not a valid repository name
>
>
> Looks like the attributes in https://github.com/jenkinsci/archetypes/blob/8203c822c89145f74d077c4895fd691c7d61c893/empty-plugin/src/main/resources/archetype-resources/pom.xml#L24
> <https://github.com/jenkinsci/archetypes/blob/8203c822c89145f74d077c4895fd691c7d61c893/empty-plugin/src/main/resources/archetype-resources/pom.xml#L24> could fix this?
>

> --
> 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-de...@googlegroups.com <mailto:jenkinsci-de...@googlegroups.com>.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BSUkgtZpw_8D7-dFRpqyxO9A%3D17oY94NXt%3DzytjvitxA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BSUkgtZpw_8D7-dFRpqyxO9A%3D17oY94NXt%3DzytjvitxA%40mail.gmail.com?utm_medium=email&utm_source=footer>.

Basil Crow

unread,

Oct 26, 2023, 11:55:10 AM10/26/23

to jenkin...@googlegroups.com

On Thu, Oct 26, 2023 at 7:04 AM Jiri Vanek <jva...@redhat.com> wrote:
>
> I was fiddling with https://github.com/jenkinsci/report-jtreg-plugin/blob/master/pom.xml#L27 (mostly reset to <gitHubRepo>jenkinsci</gitHubRepo> but it did not did the job.

Just replace <scm> with <scm
child.scm.connection.inherit.append.path="false"
child.scm.developerConnection.inherit.append.path="false"
child.scm.url.inherit.append.path="false">.

Jiri Vanek

unread,

Oct 27, 2023, 9:15:41 AM10/27/23

to jenkin...@googlegroups.com, Basil Crow

Jiri Vanek

unread,

Oct 27, 2023, 10:03:04 AM10/27/23

to jenkin...@googlegroups.com, Basil Crow

> That is the trick which did the trick!

Also, is there some wikipage I can update for this? Alhough multimodule plugins are not common, they do exists, and it is quite hard to walk through

Ullrich Hafner

unread,

Oct 27, 2023, 10:30:36 AM10/27/23

to JenkinsCI Developers

Our developer documentation is part of the website:

https://github.com/jenkins-infra/jenkins.io/

--
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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6c4642c0-7ca6-4bf6-82c4-638719e07ea8%40redhat.com.