Re: auto release form branch or manual release of multimodule project

2023-10-27 Thread Jiri Vanek 



Thanx all for help. Resolved.

On 10/27/23 16:44, Jiri Vanek wrote:



On 10/27/23 15:15, Jiri Vanek wrote:

Thht is the trick which did the trick!

Tyvm for providing such direct solution. I would not found those attributes...

The build needed more tweek, but I think I'm nearly done. It now fails in final 
upload:

[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.pom
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.hpi
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.jar
[INFO] [INFO] I/O exception (java.net.SocketException) caught when processing 
request to {s}->https://repo.jenkins-ci.org:443: Connection or outbound has 
closed
[INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-sources.jar
[INFO] [INFO] I/O exception (java.net.SocketException) caught when processing 
request to {s}->https://repo.jenkins-ci.org:443: Connection or outbound has 
closed
[INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-javadoc.jar

Where the reason is wrong base url:
   https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/
whcih should have been
   
https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugins/report-jtreg/

I mean:
  https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg/


This is yet again decalred in parent pom.

Any similar trick to the  one?

TYVMS guys!

   J.


On 10/26/23 17:54, Basil Crow wrote:

On Thu, Oct 26, 2023 at 7:04 AM Jiri Vanek  wrote:


I was fiddling with 
https://github.com/jenkinsci/report-jtreg-plugin/blob/master/pom.xml#L27  (mostly reset to 
jenkinsci but it did not did the job.


Just replace  with .







--
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/969b93c1-96c9-4421-89b2-fd498e548b5c%40redhat.com.

Re: auto release form branch or manual release of multimodule project

2023-10-27 Thread Jiri Vanek 




On 10/27/23 15:15, Jiri Vanek wrote:

Thht is the trick which did the trick!

Tyvm for providing such direct solution. I would not found those attributes...

The build needed more tweek, but I think I'm nearly done. It now fails in final 
upload:

[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.pom
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.hpi
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.jar
[INFO] [INFO] I/O exception (java.net.SocketException) caught when processing 
request to {s}->https://repo.jenkins-ci.org:443: Connection or outbound has 
closed
[INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-sources.jar
[INFO] [INFO] I/O exception (java.net.SocketException) caught when processing 
request to {s}->https://repo.jenkins-ci.org:443: Connection or outbound has 
closed
[INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-javadoc.jar

Where the reason is wrong base url:
   https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/
whcih should have been
   
https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugins/report-jtreg/

I mean:
 https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg/


This is yet again decalred in parent pom.

Any similar trick to the  one?

TYVMS guys!

   J.


On 10/26/23 17:54, Basil Crow wrote:

On Thu, Oct 26, 2023 at 7:04 AM Jiri Vanek  wrote:


I was fiddling with 
https://github.com/jenkinsci/report-jtreg-plugin/blob/master/pom.xml#L27  (mostly reset to 
jenkinsci but it did not did the job.


Just replace  with .





--
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/a49646b6-48da-4926-b411-85e2965e2bd5%40redhat.com.

Re: auto release form branch or manual release of multimodule project

2023-10-27 Thread Jiri Vanek 

On 10/27/23 16:30, Ullrich Hafner wrote:

Our developer documentation is part of the website:
https://github.com/jenkins-infra/jenkins.io/ 



Thank you. Will sum up results of this thread in new file of 
"multimodule-plugin-tips.adoc" in
https://github.com/jenkins-infra/jenkins.io/tree/master/content/doc/developer/plugin-development

J.




Am 27.10.2023 um 16:02 schrieb Jiri Vanek :


That is the trick which did the trick!
Tyvm for providing such direct solution. I would not found those attributes...
The build needed more tweek, but I think I'm nearly done. It now fails in final 
upload:
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.pom
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.hpi
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.jar
[INFO] [INFO] I/O exception (java.net.SocketException) caught when processing 
request to {s}->https://repo.jenkins-ci.org:443: Connection or outbound has 
closed
[INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-sources.jar
[INFO] [INFO] I/O exception (java.net.SocketException) caught when processing 
request to {s}->https://repo.jenkins-ci.org:443: Connection or outbound has 
closed
[INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-javadoc.jar
Where the reason is wrong base url:
  https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/
whcih should have been
  
https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugins/report-jtreg/
This is yet again decalred in parent pom.
Any similar trick to the  one?


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

TYVMS guys!
  J.
On 10/26/23 17:54, Basil Crow wrote:

On Thu, Oct 26, 2023 at 7:04 AM Jiri Vanek  wrote:


I was fiddling with 
https://github.com/jenkinsci/report-jtreg-plugin/blob/master/pom.xml#L27  (mostly reset to 
jenkinsci but it did not did the job.


Just replace  with .



--
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/6c4642c0-7ca6-4bf6-82c4-638719e07ea8%40redhat.com.


--
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/E4EB84EC-CF0E-452F-9D3A-151D8EEB4746%40gmail.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/483e2225-c8db-41e7-ba22-934f04f60cc4%40redhat.com.

Re: auto release form branch or manual release of multimodule project

2023-10-27 Thread Ullrich Hafner 
Our developer documentation is part of the website:
https://github.com/jenkins-infra/jenkins.io/


> Am 27.10.2023 um 16:02 schrieb Jiri Vanek :
> 
>> That is the trick which did the trick!
>> Tyvm for providing such direct solution. I would not found those 
>> attributes...
>> The build needed more tweek, but I think I'm nearly done. It now fails in 
>> final upload:
>> [INFO] [INFO] Uploading to maven.jenkins-ci.org: 
>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.pom
>> [INFO] [INFO] Uploading to maven.jenkins-ci.org: 
>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.hpi
>> [INFO] [INFO] Uploading to maven.jenkins-ci.org: 
>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.jar
>> [INFO] [INFO] I/O exception (java.net.SocketException) caught when 
>> processing request to {s}->https://repo.jenkins-ci.org:443: Connection or 
>> outbound has closed
>> [INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
>> [INFO] [INFO] Uploading to maven.jenkins-ci.org: 
>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-sources.jar
>> [INFO] [INFO] I/O exception (java.net.SocketException) caught when 
>> processing request to {s}->https://repo.jenkins-ci.org:443: Connection or 
>> outbound has closed
>> [INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
>> [INFO] [INFO] Uploading to maven.jenkins-ci.org: 
>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-javadoc.jar
>> Where the reason is wrong base url:
>>   
>> https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/
>> whcih should have been
>>   
>> https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugins/report-jtreg/
>> This is yet again decalred in parent pom.
>> Any similar trick to the  one?
> 
> 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
>> TYVMS guys!
>>   J.
>> On 10/26/23 17:54, Basil Crow wrote:
>>> On Thu, Oct 26, 2023 at 7:04 AM Jiri Vanek  wrote:
 
 I was fiddling with 
 https://github.com/jenkinsci/report-jtreg-plugin/blob/master/pom.xml#L27  
 (mostly reset to jenkinsci but it did not did the 
 job.
>>> 
>>> Just replace  with >> child.scm.connection.inherit.append.path="false"
>>> child.scm.developerConnection.inherit.append.path="false"
>>> child.scm.url.inherit.append.path="false">.
>>> 
> 
> -- 
> 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/6c4642c0-7ca6-4bf6-82c4-638719e07ea8%40redhat.com.

-- 
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/E4EB84EC-CF0E-452F-9D3A-151D8EEB4746%40gmail.com.

Re: auto release form branch or manual release of multimodule project

2023-10-27 Thread Jiri Vanek 

That is the trick which did the trick!

Tyvm for providing such direct solution. I would not found those attributes...

The build needed more tweek, but I think I'm nearly done. It now fails in final 
upload:

[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.pom
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.hpi
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.jar
[INFO] [INFO] I/O exception (java.net.SocketException) caught when processing 
request to {s}->https://repo.jenkins-ci.org:443: Connection or outbound has 
closed
[INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-sources.jar
[INFO] [INFO] I/O exception (java.net.SocketException) caught when processing 
request to {s}->https://repo.jenkins-ci.org:443: Connection or outbound has 
closed
[INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-javadoc.jar

Where the reason is wrong base url:
   https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/
whcih should have been
   
https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugins/report-jtreg/

This is yet again decalred in parent pom.

Any similar trick to the  one?



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

TYVMS guys!

   J.


On 10/26/23 17:54, Basil Crow wrote:

On Thu, Oct 26, 2023 at 7:04 AM Jiri Vanek  wrote:


I was fiddling with 
https://github.com/jenkinsci/report-jtreg-plugin/blob/master/pom.xml#L27  (mostly reset to 
jenkinsci but it did not did the job.


Just replace  with .





--
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/6c4642c0-7ca6-4bf6-82c4-638719e07ea8%40redhat.com.

Re: auto release form branch or manual release of multimodule project

2023-10-27 Thread Jiri Vanek 

Thht is the trick which did the trick!

Tyvm for providing such direct solution. I would not found those attributes...

The build needed more tweek, but I think I'm nearly done. It now fails in final 
upload:

[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.pom
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.hpi
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4.jar
[INFO] [INFO] I/O exception (java.net.SocketException) caught when processing 
request to {s}->https://repo.jenkins-ci.org:443: Connection or outbound has 
closed
[INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-sources.jar
[INFO] [INFO] I/O exception (java.net.SocketException) caught when processing 
request to {s}->https://repo.jenkins-ci.org:443: Connection or outbound has 
closed
[INFO] [INFO] Retrying request to {s}->https://repo.jenkins-ci.org:443
[INFO] [INFO] Uploading to maven.jenkins-ci.org: 
https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/2.4/report-jtreg-plugin-2.4-javadoc.jar

Where the reason is wrong base url:
  https://repo.jenkins-ci.org/releases/io/jenkins/plugins/report-jtreg-plugin/
whcih should have been
  
https://repo.jenkins-ci.org/artifactory/releases/io/jenkins/plugins/report-jtreg/

This is yet again decalred in parent pom.

Any similar trick to the  one?

TYVMS guys!

  J.


On 10/26/23 17:54, Basil Crow wrote:

On Thu, Oct 26, 2023 at 7:04 AM Jiri Vanek  wrote:


I was fiddling with 
https://github.com/jenkinsci/report-jtreg-plugin/blob/master/pom.xml#L27  (mostly reset to 
jenkinsci but it did not did the job.


Just replace  with .



--
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/fd15ad8f-8eaf-4d25-a1e5-8bcf8979e3d1%40redhat.com.

Re: auto release form branch or manual release of multimodule project

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

Just replace  with .

-- 
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/CAFwNDjpysG0nokQ31G5T9joyu9aqGXMpw%2BU60GheWPj%3DYqDPXg%40mail.gmail.com.

Re: auto release form branch or manual release of multimodule project

2023-10-26 Thread Jiri Vanek 

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 
jenkinsci 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 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 
 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-dev+unsubscr...@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 
.


--
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/39cc0589-3ab1-439e-8185-5af02aaeed15%40redhat.com.

Re: auto release form branch or manual release of multimodule project

2023-10-26 Thread 'Daniel Beck' via Jenkins Developers 
On Thu, Oct 26, 2023 at 2:51 PM Jiri Vanek  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?

-- 
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/CAMo7Pt%2BSUkgtZpw_8D7-dFRpqyxO9A%3D17oY94NXt%3DzytjvitxA%40mail.gmail.com.

Re: auto release form branch or manual release of multimodule project

2023-10-26 Thread Jiri Vanek 

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

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.

Re: auto release form branch or manual release of multimodule project

2023-10-26 Thread Ullrich Hafner 
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.

> Am 26.10.2023 um 12:10 schrieb Jiri Vanek :
> 
> 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.

-- 
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/FB5D50EB-F5F1-43F2-8659-6D8DEBC0C466%40gmail.com.

auto release form branch or manual release of multimodule project

2023-10-26 Thread Jiri Vanek 

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.