Re: Error in Javadoc when attempting to publish a new plugin version

[Stéphane BOBIN]

Hi Basil!

Great, thanks, I will try that 

-- Stéphane

Le mar. 5 mars 2024 à 18:09, Basil Crow  a écrit :

> You can reproduce locally by running mvn clean verify -Pjenkins-release
> and on CI by enabling incrementals
> .
> Be sure to use the same version of Java you intend to use when doing the
> release, as different Java versions produce different errors.
>
> --
> 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/CAFwNDjqEWaYB9Kb21Mkzr9VCW9H8v6%2BG%3Dr6_UpuaGg3PyTUTnA%40mail.gmail.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/CAMQQ2s%3Dz9Y2%2B8n7Dh32swKG6vpUQ53ZbCkWeaptJXW4nS1mReg%40mail.gmail.com.

Re: Error in Javadoc when attempting to publish a new plugin version

[Basil Crow]

You can reproduce locally by running mvn clean verify -Pjenkins-release and
on CI by enabling incrementals
. Be
sure to use the same version of Java you intend to use when doing the
release, as different Java versions produce different errors.

-- 
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/CAFwNDjqEWaYB9Kb21Mkzr9VCW9H8v6%2BG%3Dr6_UpuaGg3PyTUTnA%40mail.gmail.com.

Error in Javadoc when attempting to publish a new plugin version

[Stéphane BOBIN]

Hi all!

Sorry, it is probably a newbie question. I was just attempting to publish a 
new version of my plugin (mvn release:prepare release:perform) and I got 
plenty of errors in the Javadoc I recently added in my code. I didn't have 
these errors while building and testing (mvn clean install). 

   - How can I get the errors sooner in my workflow?
   - Can I run "mvn release:prepare" safely to get these errors before 
   without running remote stuff and getting into a wrong state?

Thanks for your help.

Stephane

-- 
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/6478e6ac-8e49-43fd-b12a-dd007dcb4c22n%40googlegroups.com.

Re: Error: Could not find or load main class com.mathworks.polyspace.jenkins.PolyspaceHelpers

[Baptiste Mathus]

o/

Usually the best way to implement something is to look at how other plugins
are doing it. The easiest way to find these existing implems is using
https://www.jenkins.io/doc/developer/extensions/jenkins-core/#toolinstallation

Then, beware to read a few examples of ideally well-known plugins (theory
being that there's greater chance to see idiomatic Jenkins code in a plugin
installed 100k times, than one installed 10 :)).

Cheers

Le dim. 3 mars 2024 à 08:46, Stéphane BOBIN  a
écrit :

> Hi Daniel!
>
> I like the idea. Do you have some more guidance, please? I found this:
> https://javadoc.jenkins.io/hudson/tools/ToolInstallation.html. But it
> does not explain a lot. Can you point me to the doc for the various items
> you suggest? A big thanks for your help!
>
> -- Stéphane BOBIN
>
> Le sam. 2 mars 2024 à 00:40, 'Daniel Beck' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> a écrit :
>
>>
>>
>> On Fri, Mar 1, 2024 at 11:43 PM Stéphane BOBIN <
>> stephane.bobin...@gmail.com> wrote:
>>
>>> - What is the recommended and secure way to have scripts on agents to
>>> call utilities from the plugin?
>>>
>>
>> It's not a common enough use case to have a general recommendation.
>>
>> Some ideas: publish the utilities separately rather than as part of the
>> plugin, integrate them as tools into Jenkins (ToolInstallation /
>> ToolInstaller), implement their functionality as build step(s), provide a
>> build step to copy them to the workspace, or make them available for
>> download from Jenkins like the agent.jar (with some care to not allow
>> downloading anything else).
>>
>> --
>> 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/CAMo7PtJ%2BvW36L2Qhf4gqc2ebO09UQV7WweWByduxgpsXwhT9Pg%40mail.gmail.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/CAMQQ2smfvD2JnTjCFrFWP4sSXgZgf9cOsQ_WPPTQ5S_m-tS3Jw%40mail.gmail.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/CANWgJS6f%2Bye6cet4G2PG%3DH0cyaykJiAcmQzOn-Bi_fD9SzSwMg%40mail.gmail.com.

Re: Error: Could not find or load main class com.mathworks.polyspace.jenkins.PolyspaceHelpers

[Stéphane BOBIN]

Hi Daniel!

I like the idea. Do you have some more guidance, please? I found this:
https://javadoc.jenkins.io/hudson/tools/ToolInstallation.html. But it does
not explain a lot. Can you point me to the doc for the various items you
suggest? A big thanks for your help!

-- Stéphane BOBIN

Le sam. 2 mars 2024 à 00:40, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> a écrit :

>
>
> On Fri, Mar 1, 2024 at 11:43 PM Stéphane BOBIN <
> stephane.bobin...@gmail.com> wrote:
>
>> - What is the recommended and secure way to have scripts on agents to
>> call utilities from the plugin?
>>
>
> It's not a common enough use case to have a general recommendation.
>
> Some ideas: publish the utilities separately rather than as part of the
> plugin, integrate them as tools into Jenkins (ToolInstallation /
> ToolInstaller), implement their functionality as build step(s), provide a
> build step to copy them to the workspace, or make them available for
> download from Jenkins like the agent.jar (with some care to not allow
> downloading anything else).
>
> --
> 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/CAMo7PtJ%2BvW36L2Qhf4gqc2ebO09UQV7WweWByduxgpsXwhT9Pg%40mail.gmail.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/CAMQQ2smfvD2JnTjCFrFWP4sSXgZgf9cOsQ_WPPTQ5S_m-tS3Jw%40mail.gmail.com.

Re: Error: Could not find or load main class com.mathworks.polyspace.jenkins.PolyspaceHelpers

['Daniel Beck' via Jenkins Developers]

On Fri, Mar 1, 2024 at 11:43 PM Stéphane BOBIN 
wrote:

> - What is the recommended and secure way to have scripts on agents to call
> utilities from the plugin?
>

It's not a common enough use case to have a general recommendation.

Some ideas: publish the utilities separately rather than as part of the
plugin, integrate them as tools into Jenkins (ToolInstallation /
ToolInstaller), implement their functionality as build step(s), provide a
build step to copy them to the workspace, or make them available for
download from Jenkins like the agent.jar (with some care to not allow
downloading anything else).

-- 
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/CAMo7PtJ%2BvW36L2Qhf4gqc2ebO09UQV7WweWByduxgpsXwhT9Pg%40mail.gmail.com.

Re: Error: Could not find or load main class com.mathworks.polyspace.jenkins.PolyspaceHelpers

[Stéphane BOBIN]

Hi Basil,

Thanks for your prompt answer and the link. It makes sense and it seems to
explain my problem. However, I couldn't find anything on how to move
forward on this.

Would you please point me to the right direction on:

- What is the recommended and secure way to have scripts on agents to call
utilities from the plugin?

Thanks for your help!

-- Stéphane BOBIN

Le ven. 1 mars 2024 à 19:26, Basil Crow  a écrit :

> This seems to assume the build is running on the built-in node,
> something we no longer recommend:
>
>
> https://www.jenkins.io/doc/book/security/controller-isolation/#not-building-on-the-built-in-node
>
> --
> 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/CAFwNDjpDZynbXQfmPXqTX1sTBrq7Ot2ZhY%2B2c18U6JZMcSSOcg%40mail.gmail.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/CAMQQ2smu_YDrGGPjHrenaao0u-2u%3DJVYJXVqCQfx1wcjgDF-mw%40mail.gmail.com.

Re: Error: Could not find or load main class com.mathworks.polyspace.jenkins.PolyspaceHelpers

[Basil Crow]

This seems to assume the build is running on the built-in node,
something we no longer recommend:

https://www.jenkins.io/doc/book/security/controller-isolation/#not-building-on-the-built-in-node

-- 
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/CAFwNDjpDZynbXQfmPXqTX1sTBrq7Ot2ZhY%2B2c18U6JZMcSSOcg%40mail.gmail.com.

Error: Could not find or load main class com.mathworks.polyspace.jenkins.PolyspaceHelpers

[Stéphane BOBIN]

Hi!

I develop the Mathworks Polyspace plugin: 
https://github.com/jenkinsci/mathworks-polyspace-plugin. 

I have some helpers in my plugin to allow the users to call some utilities 
in the plugin from their script. It was working since the beginning but I 
recently realized it was not anymore. When I call them from a job in 
Jenkins, it fails:
 
java -cp 
/var/lib/jenkins/plugins/mathworks-polyspace/WEB-INF/lib/mathworks-polyspace.jar
 
com.mathworks.polyspace.jenkins.PolyspaceHelpers
Error: Could not find or load main class 
com.mathworks.polyspace.jenkins.PolyspaceHelpers
Caused by: java.lang.ClassNotFoundException: 
com.mathworks.polyspace.jenkins.PolyspaceHelpers
 
When I call them from the server command line, it works:
 
> java -cp 
/var/lib/jenkins/plugins/mathworks-polyspace/WEB-INF/lib/mathworks-polyspace.jar
 
com.mathworks.polyspace.jenkins.PolyspaceHelpers
Usage: ps_helper -report-filter   
[] [ ]+
Usage: ps_helper -report-status  
Usage: ps_helper -report-count-findings 
Usage: ps_helper -print-runid 
Usage: ps_helper -print-projectid 
Usage: ps_helper -print-projecturl  
 
I checked the problem show even with my oldest plugin version which was 
supposed to work from the beginning. Anything has changed on Jenkins’ side 
with newer versions? Is there anything recently that forbids calling 
helpers from a job that way?

Any help understanding what is happening would be welcome!

Stéphane

-- 
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/d1c55a2d-bcc4-47b4-9e22-82d6b08aefbdn%40googlegroups.com.

Re: Banned dependencies error compiling SAML plugin PR

[Basil Crow]

Agreed; this is neither recommended nor supported.

On Mon, Dec 18, 2023 at 1:09 PM James Nord  wrote:
>
> All the supporting code for providing a warning about this has been removed 
> from the update center and Jenkins IIRC.
>
> So you will have no warning when you try and install the plugin - but it will 
> blow up at runtime if you try and use it.
>
> Which is probably not a good idea for a critical plugin like an 
> Authentication or Authorisation based plugin.
>
> /James
> On Wednesday 13 December 2023 at 12:20:09 UTC ullrich...@gmail.com wrote:
>>
>> The correct setting is:
>>
>> 17
>> 17
>>
>>
>> Am 13.12.2023 um 12:55 schrieb 'Jesse Glick' via Jenkins Developers 
>> :
>>
>> On Wed, Dec 13, 2023 at 5:56 AM Ullrich Hafner  wrote:
>>>
>>> I think our tool chain will accept Java 17 dependencies if you explicitly 
>>> declare it as supported by setting the java.version in you pom.
>>
>>
>> If you meant java.level, no, this is gone as of 
>> https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.40
>>
>> --
>> 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/CANfRfr0H-T7OQ8bUcw7KUFkA7bi8YZMXeY-n%2B4O_xkP%2BR5-%3DvA%40mail.gmail.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/a24e7247-9be1-4d4b-91ac-76ef52a21009n%40googlegroups.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/CAFwNDjqWfXKzZvEaCthXQnWJuUPJOiwWV3fX5nCtYELXp6GoXA%40mail.gmail.com.

Re: Banned dependencies error compiling SAML plugin PR

[James Nord]

All the supporting code for providing a warning about this has been removed 
from the update center and Jenkins IIRC.

So you will have no warning when you try and install the plugin - but it 
will blow up at runtime if you try and use it.

Which is probably not a good idea for a critical plugin like an 
Authentication or Authorisation based plugin.

/James
On Wednesday 13 December 2023 at 12:20:09 UTC ullrich...@gmail.com wrote:

> The correct setting is:
>
> 17
> 17
>
>
> Am 13.12.2023 um 12:55 schrieb 'Jesse Glick' via Jenkins Developers <
> jenkin...@googlegroups.com>:
>
> On Wed, Dec 13, 2023 at 5:56 AM Ullrich Hafner  
> wrote:
>
>> I think our tool chain will accept Java 17 dependencies if you explicitly 
>> declare it as supported by setting the java.version in you pom.
>>
>
> If you meant java.level, no, this is gone as of 
> https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.40 
>
> -- 
> 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/CANfRfr0H-T7OQ8bUcw7KUFkA7bi8YZMXeY-n%2B4O_xkP%2BR5-%3DvA%40mail.gmail.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/a24e7247-9be1-4d4b-91ac-76ef52a21009n%40googlegroups.com.

Re: Banned dependencies error compiling SAML plugin PR

[Ullrich Hafner]

The correct setting is:

17
17

> Am 13.12.2023 um 12:55 schrieb 'Jesse Glick' via Jenkins Developers 
> :
> 
> On Wed, Dec 13, 2023 at 5:56 AM Ullrich Hafner  > wrote:
>> I think our tool chain will accept Java 17 dependencies if you explicitly 
>> declare it as supported by setting the java.version in you pom.
> 
> If you meant java.level, no, this is gone as of 
> https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.40
> 
> -- 
> 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/CANfRfr0H-T7OQ8bUcw7KUFkA7bi8YZMXeY-n%2B4O_xkP%2BR5-%3DvA%40mail.gmail.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/2E8001E0-E92B-4FC2-A6BE-023279F600FE%40gmail.com.

Re: Banned dependencies error compiling SAML plugin PR

['Jesse Glick' via Jenkins Developers]

On Wed, Dec 13, 2023 at 5:56 AM Ullrich Hafner 
wrote:

> I think our tool chain will accept Java 17 dependencies if you explicitly
> declare it as supported by setting the java.version in you pom.
>

If you meant java.level, no, this is gone as of
https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.40

-- 
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/CANfRfr0H-T7OQ8bUcw7KUFkA7bi8YZMXeY-n%2B4O_xkP%2BR5-%3DvA%40mail.gmail.com.

Re: Banned dependencies error compiling SAML plugin PR

[Ullrich Hafner]

I think our tool chain will accept Java 17 dependencies if you explicitly 
declare it as supported by setting the java.version in you pom. But this makes 
no sense in your case, as you are just using a wrong dependency.
(I have a plugin distributed that is based on Java 17 as the underlying library 
uses Java 17 as a minimum version.)

> Am 12.12.2023 um 22:08 schrieb Basil Crow :
> 
> As of v6.x, pac4j requires Java 17 or newer. The Jenkins plugin
> development toolchain will not accept Java 17 bytecode as long as
> Jenkins core still supports Java 11. You will need to stay on v5.x of
> pac4j until around fall of next year when Jenkins requires Java 17 or
> newer.
> 
> -- 
> 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/CAFwNDjrCoZb186jw%2BOOXtF2JzBVw7X%2BUZw_LT2D0r7ngYdxeOQ%40mail.gmail.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/A05A5786-F19B-4FD5-AC29-3D63E045CC11%40gmail.com.

Re: Banned dependencies error compiling SAML plugin PR

[Ivan Fernandez Calvo]

I missed the actual error message between too much text

ERROR] Rule 3:
org.codehaus.mojo.extraenforcer.dependencies.EnforceBytecodeVersion

I will bump it to the latest 5.X and wait for Java 17 bytecode



On Tuesday, December 12, 2023 at 10:09:24 PM UTC+1 m...@basilcrow.com wrote:

> As of v6.x, pac4j requires Java 17 or newer. The Jenkins plugin
> development toolchain will not accept Java 17 bytecode as long as
> Jenkins core still supports Java 11. You will need to stay on v5.x of
> pac4j until around fall of next year when Jenkins requires Java 17 or
> newer.
>

-- 
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/9319a3df-2940-4848-bf66-0271a08d867dn%40googlegroups.com.

Re: Banned dependencies error compiling SAML plugin PR

[Basil Crow]

As of v6.x, pac4j requires Java 17 or newer. The Jenkins plugin
development toolchain will not accept Java 17 bytecode as long as
Jenkins core still supports Java 11. You will need to stay on v5.x of
pac4j until around fall of next year when Jenkins requires Java 17 or
newer.

-- 
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/CAFwNDjrCoZb186jw%2BOOXtF2JzBVw7X%2BUZw_LT2D0r7ngYdxeOQ%40mail.gmail.com.

Banned dependencies error compiling SAML plugin PR

[kuisathaverat]

Hi,

I am updating the pac4j library in the SAML plugin, the enforcing
plugin tells me that there are some banned dependencies. I have
checked the banned dependencies at
https://github.com/jenkinsci/pom/blob/master/pom.xml#L683C18-L709 and
none of my dependencies is there (see the dependencies tree at the
end). I dunno if it could be related to the Shibboleth libraries that
are not in the maven repo, a long time ago I requested to mirror the
repo to do the same task
https://github.com/jenkins-infra/helpdesk/issues/2375 Do I have to
request it again? Is it a different thing?

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time:  01:14 min
[INFO] Finished at: 2023-12-12T21:29:27+01:00
[INFO] 
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.4.1:enforce
(display-info) on project saml:
[ERROR] Rule 3:
org.codehaus.mojo.extraenforcer.dependencies.EnforceBytecodeVersion
failed with message:
[ERROR] Found Banned Dependency: org.opensaml:opensaml-messaging-API:jar:5.0.0
[ERROR] Found Banned Dependency: org.pac4j:pac4j-saml:jar:6.0.0
[ERROR] Found Banned Dependency: org.pac4j:pac4j-core:jar:6.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-core-impl:jar:5.0.0
[ERROR] Found Banned Dependency: net.shibboleth:ship-security:jar:9.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-storage-impl:jar:5.0.0
[ERROR] Found Banned Dependency: net.shibboleth:ship-velocity:jar:9.0.0
[ERROR] Found Banned Dependency: org.pac4j:pac4j-javaee:jar:6.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-soap-impl:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-saml-api:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-soap-api:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-profile-API:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-security-impl:jar:5.0.0
[ERROR] Found Banned Dependency: net.shibboleth:shib-networking:jar:9.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-saml-impl:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-xmlsec-api:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-profile-impl:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-core-API:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-security-API:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-storage-api:jar:5.0.0
[ERROR] Found Banned Dependency: net.shibboleth:shib-support:jar:9.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-xmlsec-impl:jar:5.0.0
[ERROR] Found Banned Dependency: org.opensaml:opensaml-messaging-impl:jar:5.0.0
[ERROR] Use 'mvn dependency:tree' to locate the source of the banned
dependencies.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Dec 12, 2023 9:29:27 PM io.opentelemetry.sdk.trace.SdkTracerProvider shutdown
WARNING: Calling shutdown() multiple times.


Dependency tree

❯ mvn dependency:tree

[INFO] Scanning for projects...

[INFO]

[INFO] < org.jenkins-ci.plugins:saml >-

[INFO] Building SAML Plugin 4.99-SNAPSHOT

[INFO] [ hpi ]-

[INFO]

[INFO] --- maven-dependency-plugin:3.6.1:tree (default-cli) @ saml ---

[INFO] org.jenkins-ci.plugins:saml:hpi:4.99-SNAPSHOT

[INFO] +- 
io.jenkins.plugins:commons-lang3-api:jar:3.13.0-62.v7d18e55f51e2:compile

[INFO] |  \- org.apache.commons:commons-lang3:jar:3.13.0:compile

[INFO] +- 
io.jenkins.plugins:apache-httpcomponents-client-5-api:jar:5.2.3-1.0:compile

[INFO] |  +- org.apache.httpcomponents.core5:httpcore5:jar:5.2.4:compile

[INFO] |  +- org.apache.httpcomponents.core5:httpcore5-h2:jar:5.2.4:compile

[INFO] |  +- 
org.apache.httpcomponents.core5:httpcore5-reactive:jar:5.2.4:compile

[INFO] |  |  \- org.reactive streams:reactive-streams:jar:1.0.4:compile

[INFO] |  +- org.apache.httpcomponents.client5:httpclient5:jar:5.2.3:compile

[INFO] |  +- 
org.apache.httpcomponents.client5:httpclient5-cache:jar:5.2.3:compile

[INFO] |  \- 
org.apache.httpcomponents.client5:httpclient5-fluent:jar:5.2.3:compile

[INFO] +- io.jenkins.plugins:jaxb:jar:2.3.9-1:compile

[INFO] |  +- com.sun.xml.bind:jaxb-impl:jar:2.3.9:compile

[INFO] |  +- io.jenkins.plugins:javax-activation-api:jar:1.2.0-6:compile

[INFO] |  |  \- com.sun.activation:javax.activation:jar:1.2.0:compile

[INFO] |  \- javax.xml.bind:jaxb-api:jar:2.3.1:compi

Re: Error while setting up Jenkins core

[Nagarjun Repala]

Thank you Alex

On Mon, Jan 23, 2023 at 8:54 PM Alex Earl  wrote:

> PowerShell considers it an expression, that is why you have to quote it.
> You can see more information here:
> https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_parsing?view=powershell-7.3
>
> On Mon, Jan 23, 2023 at 2:05 AM  wrote:
>
>> IIRC powershell messes with parameter names with dots, try
>> "-Dspotbugs.skip" *with* quotes.
>>
>> BR
>>
>> On 23 January 2023 05:02:56 CET, Nagarjun Repala 
>> wrote:
>>>
>>> Hi team,
>>>
>>> I'm facing issues while running(build) " mvn -am -pl war,bom -DskipTests
>>> -Dspotbugs.skip clean install " with an error message. Please check the
>>> below screenshot for reference[image: Screenshot 2023-01-23 092823.png]
>>>
>>> I'm using Intellij IDE
>>>
>>> Please help I'm a beginner to open source and thanks in advance.
>>>
>>> --
>> 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/AA91D211-F520-4D60-9779-3973ACAA06D0%40chsc.de
>> <https://groups.google.com/d/msgid/jenkinsci-dev/AA91D211-F520-4D60-9779-3973ACAA06D0%40chsc.de?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> Website: http://earl-of-code.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/CAOabPaxJPHDLbDySovq_c0OVCwNfGZhkqnDyfjBYg_Pp4rCDMQ%40mail.gmail.com.

Re: Error while setting up Jenkins core

[Alex Earl]

PowerShell considers it an expression, that is why you have to quote it.
You can see more information here:
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_parsing?view=powershell-7.3

On Mon, Jan 23, 2023 at 2:05 AM  wrote:

> IIRC powershell messes with parameter names with dots, try
> "-Dspotbugs.skip" *with* quotes.
>
> BR
>
> On 23 January 2023 05:02:56 CET, Nagarjun Repala 
> wrote:
>>
>> Hi team,
>>
>> I'm facing issues while running(build) " mvn -am -pl war,bom -DskipTests
>> -Dspotbugs.skip clean install " with an error message. Please check the
>> below screenshot for reference[image: Screenshot 2023-01-23 092823.png]
>>
>> I'm using Intellij IDE
>>
>> Please help I'm a beginner to open source and thanks in advance.
>>
>> --
> 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/AA91D211-F520-4D60-9779-3973ACAA06D0%40chsc.de
> <https://groups.google.com/d/msgid/jenkinsci-dev/AA91D211-F520-4D60-9779-3973ACAA06D0%40chsc.de?utm_medium=email_source=footer>
> .
>


-- 
Website: http://earl-of-code.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/CAPiUgVeJWMnEvSRg44eXRW9R%3DmK72SiVON8Yd6w_scthJHfU5A%40mail.gmail.com.

Re: Error while setting up Jenkins core

[Nagarjun Repala]

@Ice and @Opay thank you for responding. It is working after adding quotes 
around it thank you.

On Monday, January 23, 2023 at 2:35:16 PM UTC+5:30 opay...@chsc.de wrote:

> IIRC powershell messes with parameter names with dots, try 
> "-Dspotbugs.skip" *with* quotes.
>
> BR
>
>
> On 23 January 2023 05:02:56 CET, Nagarjun Repala  
> wrote:
>>
>> Hi team,
>>
>> I'm facing issues while running(build) " mvn -am -pl war,bom -DskipTests 
>> -Dspotbugs.skip clean install " with an error message. Please check the 
>> below screenshot for reference[image: Screenshot 2023-01-23 092823.png]
>>
>> I'm using Intellij IDE
>>
>> Please help I'm a beginner to open source and thanks in advance.
>>
>>

-- 
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/c48122e4-8950-4439-b081-c40de554979an%40googlegroups.com.

Re: Error while setting up Jenkins core

[opayq-gg]

IIRC powershell messes with parameter names with dots, try "-Dspotbugs.skip" 
*with* quotes.

BR

On 23 January 2023 05:02:56 CET, Nagarjun Repala  wrote:
>Hi team,
>
>I'm facing issues while running(build) " mvn -am -pl war,bom -DskipTests 
>-Dspotbugs.skip clean install " with an error message. Please check the 
>below screenshot for reference[image: Screenshot 2023-01-23 092823.png]
>
>I'm using Intellij IDE
>
>Please help I'm a beginner to open source and thanks in advance.
>
>-- 
>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/01351728-9dd7-4ba2-a5da-a3a14a92bbe5n%40googlegroups.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/AA91D211-F520-4D60-9779-3973ACAA06D0%40chsc.de.

Re: Error while setting up Jenkins core

['Björn Pedersen' via Jenkins Developers]

rnaga...@gmail.com schrieb am Montag, 23. Januar 2023 um 05:14:13 UTC+1:
Hi team,

I'm facing issues while running(build) " mvn -am -pl war,bom -DskipTests 
-Dspotbugs.skip clean install " with an error message. Please check the 
below screenshot for reference[image: Screenshot 2023-01-23 092823.png]

Looks like a whitespace problem (a space before .skip is too much)

In future, please copy/paste both command line and output instead of taking 
screenshots.



 
I'm using Intellij IDE

Please help I'm a beginner to open source and thanks in advance.

-- 
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/8fcc810c-5899-44c8-ad6d-6fab56e88d5fn%40googlegroups.com.

Error while setting up Jenkins core

[Nagarjun Repala]

Hi team,

I'm facing issues while running(build) " mvn -am -pl war,bom -DskipTests 
-Dspotbugs.skip clean install " with an error message. Please check the 
below screenshot for reference[image: Screenshot 2023-01-23 092823.png]

I'm using Intellij IDE

Please help I'm a beginner to open source and thanks in advance.

-- 
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/01351728-9dd7-4ba2-a5da-a3a14a92bbe5n%40googlegroups.com.

Re: Error injecting: public org.apache.maven.repository.internal.DefaultVersionResolver org.apache.maven.repository.internal.DefaultVersionResolver.setRepositoryEventDispatcher(org.eclipse.aether.impl

['Daniel Beck' via Jenkins Developers]

On Thu, Sep 1, 2022 at 1:37 PM Mehul Parmar 
wrote:

> ### Jenkins and plugins versions report
>
> 
>   Environment
>
>   
>   ```text
>   Paste the output here
>   ```
>
> 
>

The instructions Basil provided in
https://github.com/jenkinsci/jenkins-test-harness/issues/480#issuecomment-1226073300
should indicate that what you posted there (and copied here) isn't good
enough.

Please provide the additional information requested in his comment.

-- 
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/CAMo7PtKNZxweJFMnVm%2B%2BJAVPgsAZr_pp_UsqVwWapt_PZibKQg%40mail.gmail.com.

Error injecting: public org.apache.maven.repository.internal.DefaultVersionResolver org.apache.maven.repository.internal.DefaultVersionResolver.setRepositoryEventDispatcher(org.eclipse.aether.impl.Rep

[Mehul Parmar]

### Jenkins and plugins versions report


  Environment

  
  ```text
  Paste the output here
  ```




### What Operating System are you using (both controller, and any agents 
involved in the problem)?

macos

### Reproduction steps

Running a JUnit test like this

```java
@Test
public void mavenJob1() throws Exception {
MavenModuleSet project = j.createProject(MavenModuleSet.class, 
"maven");
Maven.MavenInstallation mavenInstallation = new 
Maven.MavenInstallation("test",
"/usr/local/apache-maven-3.8" + ".5");

project.getDescriptor().getMavenDescriptor().setInstallations(mavenInstallation);
project.setMaven("test");
//project.setScm(new SingleFileSCM("pom.xml", 
readResourceAsString("pom.xml")));
Path resourceDirectory = Paths.get("src", "test", "resources");
String absolutePath = resourceDirectory.toFile().getAbsolutePath();
project.setCustomWorkspace(absolutePath.concat("/testNgFiles"));
List actions = getDefaultActions();
j.assertBuildStatus(Result.SUCCESS, project.scheduleBuild2(0, 
actions.toArray(new Action[0])));
}
   ```

### Expected Results

I should get the build output of Jenkins job

### Actual Results

```
[Executor #0 for master : executing maven #1] WARN Sisu - Error injecting: 
org.apache.maven.artifact.resolver.DefaultArtifactResolver
com.google.inject.ProvisionException: Unable to provision, see the 
following errors:

1) Error injecting: public 
org.apache.maven.repository.internal.DefaultVersionResolver 
org.apache.maven.repository.internal.DefaultVersionResolver.setRepositoryEventDispatcher(org.eclipse.aether.impl.RepositoryEventDispatcher)
  at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] (via 
modules: org.eclipse.sisu.wire.WireModule -> 
org.eclipse.sisu.plexus.PlexusBindingModule)
  while locating org.apache.maven.repository.internal.DefaultVersionResolver
  while locating java.lang.Object annotated with *
  at org.eclipse.sisu.wire.LocatorWiring
  while locating org.eclipse.aether.impl.VersionResolver
for the 1st parameter of 
org.eclipse.aether.internal.impl.DefaultRepositorySystem.(DefaultRepositorySystem.java:131)
  while locating org.eclipse.aether.internal.impl.DefaultRepositorySystem
  while locating java.lang.Object annotated with *
  while locating org.apache.maven.artifact.resolver.DefaultArtifactResolver

1 error
at 
com.google.inject.internal.InternalProvisionException.toProvisionException(InternalProvisionException.java:226)
at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1053)
at 
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1086)
at 
org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
at 
com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:85)
at 
com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:57)
at 
com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:66)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:112)
at 
com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:127)
at 
com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:66)
at 
com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:61)
at 
com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
at 
com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at 
com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:148)
at 
com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1050)
at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81)
at 
org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51)
at 
org.eclipse.sisu.plexus.PlexusRequirements$RequirementProvider.get(PlexusRequirements.java:250)
at 
org.eclipse.sisu.plexus.ProvidedPropertyBinding.injectProperty(ProvidedPropertyBinding.java:48)
at 
org.eclipse.sisu.bean.BeanInjector.injectMembers(BeanInjector.java:52)
at 
com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:160)
at 
com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:124)
at 
com.google.inject.internal.ConstructorInjector.access$000(Const

Error injecting: public org.apache.maven.repository.internal.DefaultVersionResolver org.apache.maven.repository.internal.DefaultVersionResolver.setRepositoryEventDispatcher(org.eclipse.aether.impl.Rep

[Mehul Parmar]

Hello,
Can someone help with me issue 
- https://github.com/jenkinsci/jenkins-test-harness/issues/480



Regards
Mehul Kumar Parmar

-- 
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/c6a45452-b337-4087-a863-a44199c952cen%40googlegroups.com.

Re: ERROR: No test report files were found. Configuration error?

[Mark Waite]

On Friday, May 20, 2022 at 7:56:22 AM UTC-6 Priya wrote:

> The build is success too
>
>
Create a test.  Many of the integrated development environments offer 
automated tools that will generate "starter" test classes.  Use that 
facility to create one or more tests.

You may also need to check the configuration of your pom.xml file.  I 
thought that Jenkins plugins automatically had a test "injected" into their 
build process by the Jenkins plugin build process.

Mark Waite
 

>

-- 
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/cfcce2d0-b82e-4b17-9a8f-c4c2a61e957en%40googlegroups.com.

Re: ERROR: No test report files were found. Configuration error?

[priya jagyasi]

The build is success too

On Friday, May 20, 2022 at 7:25:48 PM UTC+5:30 priya jagyasi wrote:

> I don't have any tests in my plugin. 
>
> On Friday, May 20, 2022 at 7:21:37 PM UTC+5:30 jxpe...@godaddy.com wrote:
>
>> I believe I’ve seen that when the build failed and tests weren’t even ran
>>
>>  
>>
>> *From: * on behalf of priya jagyasi <
>> jagyasi...@gmail.com>
>> *Reply-To: *"jenkin...@googlegroups.com" 
>> *Date: *Friday, May 20, 2022 at 6:17 AM
>> *To: *Jenkins Developers 
>> *Subject: *ERROR: No test report files were found. Configuration error?
>>
>>  
>>
>> You don't often get email from jagyasi...@gmail.com. Learn why this is 
>> important <https://aka.ms/LearnAboutSenderIdentification>
>>
>> Caution: This email is from an external sender. Please do not click 
>> links or open attachments unless you recognize the sender and know the 
>> content is safe. Forward suspicious emails to isitbad@.
>>
>>  
>>
>> Hi, 
>>
>>  
>>
>> I am getting this error on jenkins build for my plugin. What does this 
>> error mean? 
>>
>>  
>>
>> Regards,
>>
>> Priya
>>
>> -- 
>> 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/384cd5db-b27d-4290-981c-8cabad9dcf3bn%40googlegroups.com
>>  
>> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fjenkinsci-dev%2F384cd5db-b27d-4290-981c-8cabad9dcf3bn%2540googlegroups.com%3Futm_medium%3Demail%26utm_source%3Dfooter=05%7C01%7Cjxpearce%40godaddy.com%7C2246f0ad56794731553208da3a62da62%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637886494365290342%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=LN5g%2BWNtFXVURZtnfiHUFk%2FyrhtrmoWhSe96RgCWcYA%3D=0>
>> .
>>
>

-- 
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/4fc7826f-baa5-477d-bbcf-d8c8d63bed5dn%40googlegroups.com.

Re: ERROR: No test report files were found. Configuration error?

[priya jagyasi]

I don't have any tests in my plugin. 

On Friday, May 20, 2022 at 7:21:37 PM UTC+5:30 jxpe...@godaddy.com wrote:

> I believe I’ve seen that when the build failed and tests weren’t even ran
>
>  
>
> *From: * on behalf of priya jagyasi <
> jagyasi...@gmail.com>
> *Reply-To: *"jenkin...@googlegroups.com" 
> *Date: *Friday, May 20, 2022 at 6:17 AM
> *To: *Jenkins Developers 
> *Subject: *ERROR: No test report files were found. Configuration error?
>
>  
>
> You don't often get email from jagyasi...@gmail.com. Learn why this is 
> important <https://aka.ms/LearnAboutSenderIdentification>
>
> Caution: This email is from an external sender. Please do not click links 
> or open attachments unless you recognize the sender and know the content is 
> safe. Forward suspicious emails to isitbad@.
>
>  
>
> Hi, 
>
>  
>
> I am getting this error on jenkins build for my plugin. What does this 
> error mean? 
>
>  
>
> Regards,
>
> Priya
>
> -- 
> 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/384cd5db-b27d-4290-981c-8cabad9dcf3bn%40googlegroups.com
>  
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fjenkinsci-dev%2F384cd5db-b27d-4290-981c-8cabad9dcf3bn%2540googlegroups.com%3Futm_medium%3Demail%26utm_source%3Dfooter=05%7C01%7Cjxpearce%40godaddy.com%7C2246f0ad56794731553208da3a62da62%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637886494365290342%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=LN5g%2BWNtFXVURZtnfiHUFk%2FyrhtrmoWhSe96RgCWcYA%3D=0>
> .
>

-- 
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/98c47d88-3ba2-4e86-adde-b2ea95fb9086n%40googlegroups.com.

Re: ERROR: No test report files were found. Configuration error?

['Jeff Pearce' via Jenkins Developers]

I believe I’ve seen that when the build failed and tests weren’t even ran

From:  on behalf of priya jagyasi 

Reply-To: "jenkinsci-dev@googlegroups.com" 
Date: Friday, May 20, 2022 at 6:17 AM
To: Jenkins Developers 
Subject: ERROR: No test report files were found. Configuration error?

You don't often get email from jagyasi.priy...@gmail.com. Learn why this is 
important<https://aka.ms/LearnAboutSenderIdentification>
Caution: This email is from an external sender. Please do not click links or 
open attachments unless you recognize the sender and know the content is safe. 
Forward suspicious emails to isitbad@.


Hi,

I am getting this error on jenkins build for my plugin. What does this error 
mean?

Regards,
Priya
--
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<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/384cd5db-b27d-4290-981c-8cabad9dcf3bn%40googlegroups.com<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fjenkinsci-dev%2F384cd5db-b27d-4290-981c-8cabad9dcf3bn%2540googlegroups.com%3Futm_medium%3Demail%26utm_source%3Dfooter=05%7C01%7Cjxpearce%40godaddy.com%7C2246f0ad56794731553208da3a62da62%7Cd5f1622b14a345a6b069003f8dc4851f%7C0%7C0%7C637886494365290342%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=LN5g%2BWNtFXVURZtnfiHUFk%2FyrhtrmoWhSe96RgCWcYA%3D=0>.

-- 
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/54810C58-F5E0-43C2-AD40-363CBA88AE24%40godaddy.com.

ERROR: No test report files were found. Configuration error?

[priya jagyasi]

Hi,

I am getting this error on jenkins build for my plugin. What does this 
error mean? 

Regards,
Priya

-- 
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/384cd5db-b27d-4290-981c-8cabad9dcf3bn%40googlegroups.com.

An error occurred (AccessDeniedException) when calling the UpdateFunctionCode operation: User:

[chinnu]

Hi 
I am getting the below error while deploying code to the aws lambda from 
jenkins pipeline  through aws lambda updatefunctioncode command

*An error occurred (AccessDeniedException) when calling the 
UpdateFunctionCode operation: User:*
*arn:aws:sts:::assumed-role/jxxx/i-049e95c3d70187410 
is not authorized to perform: lambda:UpdateFunctionCode on resource: 
arn:aws:lambda:us-east-1:118:function:demo because no 
identity-based policy allows the lambda:UpdateFunctionCode action*

I dont have access to update the permissions and policies in the aws 
suggest me any 
that should be running from my pipeline and need to do jenkins

-- 
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/8acff98e-ef34-4c2c-96c2-0f2e056e6bb8n%40googlegroups.com.

Re: Jenkins build failure: "...project cli: Error creating shaded jar: duplicate entry: META-INF/services/io.jenkins.cli.shaded.jakarta.websocket.ContainerProvider"

['Cyrille Le Clerc' via Jenkins Developers]

Thanks, using Maven 3.8.4 fixed my problem. I created the issue JENKINS-68302 
Building Jenkins with Maven 3.8.5 fails on maven-shade-plugin:shade 
 and submitted the pull 
request JENKINS-68302 Use mvnw to specify Maven v3.8.4 as v3.8.5 fails #6491 
.


On Friday, April 15, 2022 at 9:37:05 PM UTC+2 Jesse Glick wrote:

> On Fri, Apr 15, 2022 at 12:08 PM 'Cyrille Le Clerc' via Jenkins Developers 
>  wrote:
>
>> Is it a known build problem?
>>
>
> Other than Maven 3.8.5 being broken as Mark mentioned, there are not in 
> general known build problems. Someone would fix the problem right away, if 
> it even somehow got merged to trunk despite CI checks.
>
> I would suggest starting with `mvn clean`. If that still fails, try a 
> build of a fresh checkout inside a Docker container.
>

-- 
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/541293cd-db95-4f45-b413-eeb2ac715769n%40googlegroups.com.

Re: Jenkins build failure: "...project cli: Error creating shaded jar: duplicate entry: META-INF/services/io.jenkins.cli.shaded.jakarta.websocket.ContainerProvider"

['Jesse Glick' via Jenkins Developers]

On Fri, Apr 15, 2022 at 12:08 PM 'Cyrille Le Clerc' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Is it a known build problem?
>

Other than Maven 3.8.5 being broken as Mark mentioned, there are not in
general known build problems. Someone would fix the problem right away, if
it even somehow got merged to trunk despite CI checks.

I would suggest starting with `mvn clean`. If that still fails, try a build
of a fresh checkout inside a Docker container.

-- 
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/CANfRfr3DGfFqG2yykcusa4WtS%2BU0RQhj1kTaEv8ygu59TCPhJw%40mail.gmail.com.

Re: Jenkins build failure: "...project cli: Error creating shaded jar: duplicate entry: META-INF/services/io.jenkins.cli.shaded.jakarta.websocket.ContainerProvider"

[Mark Waite]

We had known problems with Maven 3.8.5 on ci.jenkins.io and had to roll
back to 3.8.4.  Currently building with Java 11.0.14.1 and maven 3.8.4.

On Fri, Apr 15, 2022 at 10:08 AM 'Cyrille Le Clerc' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Dear Jenkins Dev community,
>
> I fail to build Jenkins on my Mac amd64 12.3.1 with Maven 3.8.5 and JDK
> 11.0.11.
>
> The message is:
> Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.3.0:shade (default) on
> project cli: Error creating shaded jar: duplicate entry:
> META-INF/services/io.jenkins.cli.shaded.jakarta.websocket.ContainerProvider
>
> The detailed build logs are here:
> https://gist.github.com/cyrille-leclerc/1b1177f47984e90872a70763d4012d93
>
> Is it a known build problem?
> Thanks in advance,
>
> Cyrille
>
> --
> 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/6c473a86-2096-4b74-8c7c-16de18a5e008n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/6c473a86-2096-4b74-8c7c-16de18a5e008n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAO49JtFuXJdzEsfSvSLUp0ZN5p-Q8EY684HDd7jsn%3DZAUaGsyg%40mail.gmail.com.

Jenkins build failure: "...project cli: Error creating shaded jar: duplicate entry: META-INF/services/io.jenkins.cli.shaded.jakarta.websocket.ContainerProvider"

['Cyrille Le Clerc' via Jenkins Developers]

Dear Jenkins Dev community,

I fail to build Jenkins on my Mac amd64 12.3.1 with Maven 3.8.5 and JDK 
11.0.11.

The message is:
Failed to execute goal 
org.apache.maven.plugins:maven-shade-plugin:3.3.0:shade (default) on 
project cli: Error creating shaded jar: duplicate entry: 
META-INF/services/io.jenkins.cli.shaded.jakarta.websocket.ContainerProvider

The detailed build logs are here:
https://gist.github.com/cyrille-leclerc/1b1177f47984e90872a70763d4012d93

Is it a known build problem?
Thanks in advance,

Cyrille

-- 
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/6c473a86-2096-4b74-8c7c-16de18a5e008n%40googlegroups.com.

Re: error occuring during mvn release

['Daniel Beck' via Jenkins Developers]

On Thu, Mar 24, 2022 at 1:26 PM 'Mohammad Uddin' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hi All,
>
> I am getting this error "The initial value of this parameter is ignored,
> and the parameter is overwritten here. This often indicates a mistaken
> belief that the write to the parameter will be conveyed back to the caller.
> "
>

It looks like you're trying to set field values, but since there is a
parameter with the same name you would need to put "this.fieldName".

That said: Do not attempt to set field values in form validation. That is
guaranteed to be wrong.

-- 
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/CAMo7PtLd6-Cy%3DQw_Q84EiJ8RJe216nVzOO%3DL%2B9nALwN77eOPxA%40mail.gmail.com.

Re: Error publishing plugin

[Alberto Bec]

Thanks, the "Include administrators" option was set on the rule. Didn't 
know that was a thing

On Friday, January 21, 2022 at 12:54:56 PM UTC-5 ga...@gavinmogan.com wrote:

> So that's usually branch protection settings in GitHub. I've personally 
> never found a way to support mvn release and have branch protection enabled.
>
> You could disable the no pushes while you do the release.
>
> I bet there's also a way to tell mvn to use a branch 
>
> On Fri., Jan. 21, 2022, 7:45 a.m. Alberto Bec,  wrote:
>
>> Forgot to include screenshot
>>
>> On Friday, January 21, 2022 at 10:43:59 AM UTC-5 Alberto Bec wrote:
>>
>>> I'm trying to publish our plugin using the manual method 
>>> <https://www.jenkins.io/doc/developer/publishing/releasing-manually/> but 
>>> getting the error "remote: error: GH006: Protected branch update failed for 
>>> refs/heads/master."
>>>
>>> Do I need to do this in a branch then merge that into master? Or am I 
>>> missing a permission?
>>>
>> -- 
>> 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/bae55f98-1324-44f5-9d94-a3bbe034220cn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/bae55f98-1324-44f5-9d94-a3bbe034220cn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/240d9a8a-b742-43e8-a9ac-dad03a9415fan%40googlegroups.com.

Re: Error publishing plugin

['Gavin Mogan' via Jenkins Developers]

So that's usually branch protection settings in GitHub. I've personally
never found a way to support mvn release and have branch protection enabled.

You could disable the no pushes while you do the release.

I bet there's also a way to tell mvn to use a branch

On Fri., Jan. 21, 2022, 7:45 a.m. Alberto Bec,  wrote:

> Forgot to include screenshot
>
> On Friday, January 21, 2022 at 10:43:59 AM UTC-5 Alberto Bec wrote:
>
>> I'm trying to publish our plugin using the manual method
>> <https://www.jenkins.io/doc/developer/publishing/releasing-manually/> but
>> getting the error "remote: error: GH006: Protected branch update failed for
>> refs/heads/master."
>>
>> Do I need to do this in a branch then merge that into master? Or am I
>> missing a permission?
>>
> --
> 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/bae55f98-1324-44f5-9d94-a3bbe034220cn%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/bae55f98-1324-44f5-9d94-a3bbe034220cn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAG%3D_DutMr4R1rthU0bXWMrjy9dmmQrrkf9AfXfP1qDKKZqS6OA%40mail.gmail.com.

Re: Error publishing plugin

[Alberto Bec]

Forgot to include screenshot

On Friday, January 21, 2022 at 10:43:59 AM UTC-5 Alberto Bec wrote:

> I'm trying to publish our plugin using the manual method 
> <https://www.jenkins.io/doc/developer/publishing/releasing-manually/> but 
> getting the error "remote: error: GH006: Protected branch update failed for 
> refs/heads/master."
>
> Do I need to do this in a branch then merge that into master? Or am I 
> missing a permission?
>

-- 
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/bae55f98-1324-44f5-9d94-a3bbe034220cn%40googlegroups.com.

Error publishing plugin

[Alberto Bec]

I'm trying to publish our plugin using the manual method 
<https://www.jenkins.io/doc/developer/publishing/releasing-manually/> but 
getting the error "remote: error: GH006: Protected branch update failed for 
refs/heads/master."

Do I need to do this in a branch then merge that into master? Or am I 
missing a permission?

-- 
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/aa11d549-ed21-4ab2-9ec6-265a8903a9f7n%40googlegroups.com.

Re: Certificate expiry error on get.jenkins.io

[Mark Waite]

On Wednesday, December 8, 2021 at 10:16:28 AM UTC-7 Tony Noble wrote:

> Thanks - it looks like we might have something caching old certificates 
> then.  Apologies for the false alarm...
>
>>
>>
We've seen reports that older Java versions and older operating system 
versions may not support Server Name Indication (SNI) from TLS.

We've also seen reports that older Java versions and older operating system 
versions may not support the ISRG X1 root certificate from Let's Encrypt 
(see their blog post 
). 

The solution in both cases was to update the Java version and the operating 
system packages (like ca-certificates) to recent versions.

You may want to check that your operating system patches are current and 
that your Java version is current.

Mark Waite

-- 
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/f809b05c-1ffc-4e8b-9390-de32d9eb0588n%40googlegroups.com.

Re: Certificate expiry error on get.jenkins.io

[Tony Noble]

Thanks - it looks like we might have something caching old certificates
then.  Apologies for the false alarm...


On Wed, Dec 8, 2021 at 5:11 PM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Maybe someone restarted the service already. As far as I can tell is valid
> - https://www.sslshopper.com/ssl-checker.html#hostname=get.jenkins.io
>
> On Wed, Dec 8, 2021 at 9:03 AM Tony Noble  wrote:
>
>> Looks like the previous certificate expiry issues are still in place on
>> the above host:
>>
>> tmp>wget https://get.jenkins.io/war-stable/2.303.3/jenkins.war
>>
>> --2021-12-08 17:02:03--
>> https://get.jenkins.io/war-stable/2.303.3/jenkins.war
>> Resolving get.jenkins.io (get.jenkins.io)... 52.167.253.43
>> Connecting to get.jenkins.io (get.jenkins.io)|52.167.253.43|:443...
>> connected.
>> ERROR: cannot verify get.jenkins.io's certificate, issued by
>> ‘/C=US/O=Let's Encrypt/CN=R3’:
>>   Issued certificate has expired.
>> To connect to get.jenkins.io insecurely, use `--no-check-certificate'.
>> /tmp>
>>
>> Is there anyone with access to take a look?
>>
>> --
>> 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/CAEWqh9HEpsGSvpDCStdcCrmWBD0tjfyO%3Da27SpdrQojk%3DRY%3DeA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAEWqh9HEpsGSvpDCStdcCrmWBD0tjfyO%3Da27SpdrQojk%3DRY%3DeA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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/CAG%3D_DusX9ZzHyvpAb%3D0MFNYjXov3cE9gseDHgY%2Bv1fXAn9JnnA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusX9ZzHyvpAb%3D0MFNYjXov3cE9gseDHgY%2Bv1fXAn9JnnA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAEWqh9GCEBxjD5A7ACWvn7iVau6qtaLLTi7McdcONfYibiMVfw%40mail.gmail.com.

Re: Certificate expiry error on get.jenkins.io

['Gavin Mogan' via Jenkins Developers]

Maybe someone restarted the service already. As far as I can tell is valid
- https://www.sslshopper.com/ssl-checker.html#hostname=get.jenkins.io

On Wed, Dec 8, 2021 at 9:03 AM Tony Noble  wrote:

> Looks like the previous certificate expiry issues are still in place on
> the above host:
>
> tmp>wget https://get.jenkins.io/war-stable/2.303.3/jenkins.war
>
> --2021-12-08 17:02:03--
> https://get.jenkins.io/war-stable/2.303.3/jenkins.war
> Resolving get.jenkins.io (get.jenkins.io)... 52.167.253.43
> Connecting to get.jenkins.io (get.jenkins.io)|52.167.253.43|:443...
> connected.
> ERROR: cannot verify get.jenkins.io's certificate, issued by
> ‘/C=US/O=Let's Encrypt/CN=R3’:
>   Issued certificate has expired.
> To connect to get.jenkins.io insecurely, use `--no-check-certificate'.
> /tmp>
>
> Is there anyone with access to take a look?
>
> --
> 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/CAEWqh9HEpsGSvpDCStdcCrmWBD0tjfyO%3Da27SpdrQojk%3DRY%3DeA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAEWqh9HEpsGSvpDCStdcCrmWBD0tjfyO%3Da27SpdrQojk%3DRY%3DeA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAG%3D_DusX9ZzHyvpAb%3D0MFNYjXov3cE9gseDHgY%2Bv1fXAn9JnnA%40mail.gmail.com.

Certificate expiry error on get.jenkins.io

[Tony Noble]

Looks like the previous certificate expiry issues are still in place on the
above host:

tmp>wget https://get.jenkins.io/war-stable/2.303.3/jenkins.war

--2021-12-08 17:02:03--
https://get.jenkins.io/war-stable/2.303.3/jenkins.war
Resolving get.jenkins.io (get.jenkins.io)... 52.167.253.43
Connecting to get.jenkins.io (get.jenkins.io)|52.167.253.43|:443...
connected.
ERROR: cannot verify get.jenkins.io's certificate, issued by ‘/C=US/O=Let's
Encrypt/CN=R3’:
  Issued certificate has expired.
To connect to get.jenkins.io insecurely, use `--no-check-certificate'.
/tmp>

Is there anyone with access to take a look?

-- 
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/CAEWqh9HEpsGSvpDCStdcCrmWBD0tjfyO%3Da27SpdrQojk%3DRY%3DeA%40mail.gmail.com.

Re: javadoc-plugin error since plugin-pom 4.19 ?

[Jesse Glick]

https://github.com/jenkins-infra/javadoc/pull/30 ought to prevent a
recurrence.

-- 
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/CANfRfr2T%2BBE9Z88RnHPFOb2%2BwJ1-Fu%3DLeP%2BK2shk48uCBf8Syw%40mail.gmail.com.

Re: javadoc-plugin error since plugin-pom 4.19 ?

[Mark Waite]

Thanks Daniel!

When it is resolved, we can 
close https://issues.jenkins.io/browse/WEBSITE-779 that reports the issue 
in the issue tracker.

On Monday, July 5, 2021 at 11:52:55 PM UTC-6 db...@cloudbees.com wrote:

>
>
> On Mon, Jul 5, 2021 at 8:16 PM Mark Waite  wrote:
>
>>
>> Will need some further research to understand why that Javadoc page is 
>> not being generated for Jenkins core.
>>
>
> Looks like it's a side effect of the 2.300 release not being in the usual 
> repo (see my thread from last week). If so, it should resolve itself later 
> today with the release of 2.301.
>

-- 
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/e472e672-0431-48d8-9b39-4febbe838870n%40googlegroups.com.

Re: javadoc-plugin error since plugin-pom 4.19 ?

[Daniel Beck]

On Mon, Jul 5, 2021 at 8:16 PM Mark Waite  wrote:

>
> Will need some further research to understand why that Javadoc page is not
> being generated for Jenkins core.
>

Looks like it's a side effect of the 2.300 release not being in the usual
repo (see my thread from last week). If so, it should resolve itself later
today with the release of 2.301.

-- 
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/CAMo7PtJ-aS-i3a4dx-ShRABF8zrR3tBcMuuODasAoSeeSmj%3DCg%40mail.gmail.com.

Re: javadoc-plugin error since plugin-pom 4.19 ?

[Mark Waite]

If you need to release in a hurry, you could generate the javadoc without 
the reference to https://javadoc.jenkins.io/ by adding the following into 
the builds section of your pom file:



maven-javadoc-plugin
3.3.0

8
false






On Monday, July 5, 2021 at 12:16:17 PM UTC-6 Mark Waite wrote:

> There appears to be a problem in the Javadoc generation process for 
> Jenkins core.  When I open https://javadoc.jenkins-ci.org/ , it shows 3 
> links (as expected).  When I click the "plugins" link and the "components" 
> link, it opens a page listing those items.  When I click the "Jenkins core" 
> link, it reports "404 - not found".
>
> Will need some further research to understand why that Javadoc page is not 
> being generated for Jenkins core.
>
> On Mon, Jul 5, 2021 at 9:34 AM Goyot, Martin  
> wrote:
>
>> Hi there,
>>
>> We repeatedly run into an error trying to `maven release:prepare 
>> release:perform` our plugin. It would appear that the javadoc plugin was 
>> updated by plugin-pom 4.19 but maybe this is just a misguided guess. 
>> Someone with the same kind of error ?
>>
>> here is the trace:
>>
>> [WARNING] 
>> '/home/mgoyot/Cube/tuleap-api-plugin/target/checkout/target/tuleap-api.hpi' 
>> not allowed on the path, only outputDirectories and jars are accepted 
>> [INFO] No previous run data found, generating javadoc. [INFO] 1 error 
>> [INFO] 
>>  
>> [INFO] BUILD FAILURE [INFO] 
>> ---- 
>> [INFO] Total time: 27.899 s [INFO] Finished at: 2021-07-05T15:53:30+02:00 
>> [INFO] 
>> ---- 
>> [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-javadoc-plugin:3.3.0:jar (attach-javadocs) 
>> on project tuleap-api: MavenReportException: Error while generating 
>> Javadoc: [ERROR] Exit code: 1 - javadoc: error - Error fetching URL: 
>> https://javadoc.jenkins.io/ [ERROR] [ERROR] Command line was: 
>> /usr/lib/jvm/java-11-openjdk-11.0.11.0.9-4.fc34.x86_64/bin/javadoc @options 
>> @packages [ERROR] [ERROR] Refer to the generated Javadoc files in 
>> '/home/mgoyot/Cube/tuleap-api-plugin/target/checkout/target/apidocs' dir. 
>> [ERROR] [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of 
>> the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the 
>> -X switch to enable full debug logging. [ERROR] [ERROR] For more 
>> information about the errors and possible solutions, please read the 
>> following articles: [ERROR] [Help 1] 
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException 
>> [INFO] 
>> ---- 
>> [INFO] BUILD FAILURE [INFO] 
>>  
>> [INFO] Total time: 01:55 min [INFO] Finished at: 2021-07-05T15:53:30+02:00 
>> [INFO] 
>> ---- 
>> [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) 
>> on project tuleap-api: Maven execution failed, exit code: '1' -> [Help 1] 
>> [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven 
>> with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full 
>> debug logging. [ERROR] [ERROR] For more information about the errors and 
>> possible solutions, please read the following articles: [ERROR] [Help 1] 
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>>
>> -- 
>> 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/CA%2Bb6JB_AQoQYSUmEyGcp2y9u%3DgoaKC8A3TqZJJxrONs1OkZqmA%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2Bb6JB_AQoQYSUmEyGcp2y9u%3DgoaKC8A3TqZJJxrONs1OkZqmA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/5e3fbc49-01ab-4cee-b40f-176cf32b5872n%40googlegroups.com.

Re: javadoc-plugin error since plugin-pom 4.19 ?

[Mark Waite]

There appears to be a problem in the Javadoc generation process for Jenkins
core.  When I open https://javadoc.jenkins-ci.org/ , it shows 3 links (as
expected).  When I click the "plugins" link and the "components" link, it
opens a page listing those items.  When I click the "Jenkins core" link, it
reports "404 - not found".

Will need some further research to understand why that Javadoc page is not
being generated for Jenkins core.

On Mon, Jul 5, 2021 at 9:34 AM Goyot, Martin 
wrote:

> Hi there,
>
> We repeatedly run into an error trying to `maven release:prepare
> release:perform` our plugin. It would appear that the javadoc plugin was
> updated by plugin-pom 4.19 but maybe this is just a misguided guess.
> Someone with the same kind of error ?
>
> here is the trace:
>
> [WARNING]
> '/home/mgoyot/Cube/tuleap-api-plugin/target/checkout/target/tuleap-api.hpi'
> not allowed on the path, only outputDirectories and jars are accepted
> [INFO] No previous run data found, generating javadoc. [INFO] 1 error
> [INFO]
> 
> [INFO] BUILD FAILURE [INFO]
> 
> [INFO] Total time: 27.899 s [INFO] Finished at: 2021-07-05T15:53:30+02:00
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.3.0:jar (attach-javadocs)
> on project tuleap-api: MavenReportException: Error while generating
> Javadoc: [ERROR] Exit code: 1 - javadoc: error - Error fetching URL:
> https://javadoc.jenkins.io/ [ERROR] [ERROR] Command line was:
> /usr/lib/jvm/java-11-openjdk-11.0.11.0.9-4.fc34.x86_64/bin/javadoc @options
> @packages [ERROR] [ERROR] Refer to the generated Javadoc files in
> '/home/mgoyot/Cube/tuleap-api-plugin/target/checkout/target/apidocs' dir.
> [ERROR] [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of
> the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the
> -X switch to enable full debug logging. [ERROR] [ERROR] For more
> information about the errors and possible solutions, please read the
> following articles: [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [INFO]
> 
> [INFO] BUILD FAILURE [INFO]
> 
> [INFO] Total time: 01:55 min [INFO] Finished at: 2021-07-05T15:53:30+02:00
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli)
> on project tuleap-api: Maven execution failed, exit code: '1' -> [Help 1]
> [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven
> with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full
> debug logging. [ERROR] [ERROR] For more information about the errors and
> possible solutions, please read the following articles: [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
> --
> 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/CA%2Bb6JB_AQoQYSUmEyGcp2y9u%3DgoaKC8A3TqZJJxrONs1OkZqmA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2Bb6JB_AQoQYSUmEyGcp2y9u%3DgoaKC8A3TqZJJxrONs1OkZqmA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAO49JtG-ZGmf3Q7z6ixYef8xqwW%3DRzWhX%3D7G8c0m9iJ37M%2BWLA%40mail.gmail.com.

javadoc-plugin error since plugin-pom 4.19 ?

[Goyot, Martin]

Hi there,

We repeatedly run into an error trying to `maven release:prepare
release:perform` our plugin. It would appear that the javadoc plugin was
updated by plugin-pom 4.19 but maybe this is just a misguided guess.
Someone with the same kind of error ?

here is the trace:

[WARNING]
'/home/mgoyot/Cube/tuleap-api-plugin/target/checkout/target/tuleap-api.hpi'
not allowed on the path, only outputDirectories and jars are accepted
[INFO] No previous run data found, generating javadoc. [INFO] 1 error
[INFO]

[INFO] BUILD FAILURE [INFO]

[INFO] Total time: 27.899 s [INFO] Finished at: 2021-07-05T15:53:30+02:00
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.3.0:jar (attach-javadocs)
on project tuleap-api: MavenReportException: Error while generating
Javadoc: [ERROR] Exit code: 1 - javadoc: error - Error fetching URL:
https://javadoc.jenkins.io/ [ERROR] [ERROR] Command line was:
/usr/lib/jvm/java-11-openjdk-11.0.11.0.9-4.fc34.x86_64/bin/javadoc @options
@packages [ERROR] [ERROR] Refer to the generated Javadoc files in
'/home/mgoyot/Cube/tuleap-api-plugin/target/checkout/target/apidocs' dir.
[ERROR] [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of
the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the
-X switch to enable full debug logging. [ERROR] [ERROR] For more
information about the errors and possible solutions, please read the
following articles: [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[INFO]

[INFO] BUILD FAILURE [INFO]

[INFO] Total time: 01:55 min [INFO] Finished at: 2021-07-05T15:53:30+02:00
[INFO]
----
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli)
on project tuleap-api: Maven execution failed, exit code: '1' -> [Help 1]
[ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven
with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full
debug logging. [ERROR] [ERROR] For more information about the errors and
possible solutions, please read the following articles: [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

-- 
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/CA%2Bb6JB_AQoQYSUmEyGcp2y9u%3DgoaKC8A3TqZJJxrONs1OkZqmA%40mail.gmail.com.

Re: Error handling in Groovy initialization scripts vs JCasC

[Jesse Glick]

On Thu, Jun 24, 2021 at 5:18 AM Ullrich Hafner 
wrote:

> I often have this problem that my working JCasC configuration suddenly
> breaks after an upgrade of JCasC (or another plugin) and Jenkins just not
> starts up. And then you need to dig into log files to see what happens. It
> would be much better if those errors would be reported in the UI
>

Maybe it depends on how you are using JCasC. If you treat your JCasC YAML
plus a pinned set of versions of Jenkins core and plugins as an atomic
configuration set describing your whole system, with a PR-type workflow,
then failing fast is a feature not a bug: if either a change to YAML *or* a
change to some component version causes a failure, then you can clearly see
that this is a bad PR and it should not be merged until the issue is
resolved.

-- 
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/CANfRfr0JbtH9JPz-sq8Enpd-kxXZbEoGQpHzf5giMX4%3D3%2B8TGw%40mail.gmail.com.

Re: Error handling in Groovy initialization scripts vs JCasC

[Basil Crow]

On Thu, Jun 24, 2021 at 9:07 AM Tim Jacomb  wrote:
>
> There are some flags you can use to tune this behaviour:
> https://github.com/jenkinsci/configuration-as-code-plugin/blob/a6983ff60e0cf198ce02d7992bcba927197174db/test-harness/src/test/resources/io/jenkins/plugins/casc/validSelfConfig.yml#L1-L5

Those flags don't work in all cases. Try the following JCasC YAML file
when Theme Manager is installed but Dark Theme is not installed:

configuration-as-code:
 version: 1
 deprecated: warn
 restricted: warn
 unknown: warn

unclassified:
 themeManager:
   disableUserThemes: false
   theme: "darkSystem"

Jenkins will not start up.

Now try starting Jenkins with a
io.jenkins.plugins.thememanager.ThemeManagerPageDecorator.xml file
that references
io.jenkins.plugins.darktheme.DarkThemeSystemManagerFactory when Theme
Manager is installed but Dark Theme is not installed. Jenkins does
start up. (No warning is displayed and the default theme is used.)

I think the ideal behavior in both cases would be for Jenkins to start
up and display an administrative monitor warning that invalid
configuration was not applied. (Obviously, this would not apply to
security-related configuration per Antonio's point.)

> I think the consensus has been it's 'good enough', there's plenty of room for 
> improvement, but in general it works 'just fine' for most use-cases

I don't disagree. Yet I also recall listening to an interview with
Kohsuke where he explicitly talked about wanting to build a tool that
was not only good enough but also a pleasure to use. That seems like
an example worth following.

-- 
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/CAFwNDjqSK-xxwCgTeOCKrviU2JSnce9OkXURcgtvURzMFf3Rag%40mail.gmail.com.

Re: Error handling in Groovy initialization scripts vs JCasC

['Gavin Mogan' via Jenkins Developers]

I've had times when those groovy scripts "silently" fail on startup, and
while isn't a big deal when I'm just restarting an existing instance, it
does suck when I'm spinning up a new instance and suddely I don't have
security setup.

I used to pair my jcasc config with my jenkins docker image, so I could
roll back when things fail to start (I hit a helm bug and had to split them
up again). I like the idea in that case of not being able to spin up a
broken install. But I also understand that lots of people just tweak
existing installs, and probably want warnings without fatals for parsing.
So I really like that override behavior. I don't think the default should
be warn though since it could potentially lead to insecure setups.

On Thu, Jun 24, 2021 at 9:08 AM Tim Jacomb  wrote:

> There are some flags you can use to tune this behaviour:
>
> https://github.com/jenkinsci/configuration-as-code-plugin/blob/a6983ff60e0cf198ce02d7992bcba927197174db/test-harness/src/test/resources/io/jenkins/plugins/casc/validSelfConfig.yml#L1-L5
>
> The default is to show an error page with what failed.
>
> > I concur. My initial impression is that JCasC lacks polish, and I was
> > surprised to see it promoted so heavily when issues like this remain.
>
> I think the consensus has been it's 'good enough', there's plenty of room
> for improvement, but in general it works 'just fine' for most use-cases
>
>
>
> On Thu, 24 Jun 2021 at 16:54, Basil Crow  wrote:
>
>> On Thu, Jun 24, 2021 at 2:18 AM Ullrich Hafner 
>> wrote:
>> > This is a very bad user experience (actually I don’t know of any other
>> application that does not start because of a configuration error).
>>
>> I concur. My initial impression is that JCasC lacks polish, and I was
>> surprised to see it promoted so heavily when issues like this remain.
>>
>> > This is also the approach that we are using if a plugin changes
>> serialization (or if a plugin cannot be started because of missing
>> dependencies): in this case Jenkins still continues to work and the
>> problems are highlighted in the UI.
>>
>> Core isn't entirely consistent in this regard, either. Yes
>> OldDataMonitor and PluginWrapperAdministrativeMonitor exist. But I
>> just tried corrupting core's config.xml file and Jenkins wouldn't
>> start at all. But when I corrupted Email Extension's
>> hudson.plugins.emailext.ExtendedEmailPublisher.xml, Jenkins started
>> but with the default values for Email Extension and no administrative
>> monitor in the UI. The latter clearly could use some improvement, but
>> I'm not sure about the former. It seems that we want _some_
>> configuration loading errors to be fatal. But which ones, exactly? In
>> the JCasC issue on GitHub, Antonio raised the valid point that errors
>> in loading security-related configuration should be fatal (for obvious
>> reasons).
>>
>> --
>> 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/CAFwNDjrLf3jJ-dTk%2BOX1E4b2%3DvB2rsWDFgMX0%2BzKNHMbcgRcJA%40mail.gmail.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/CAH-3BidoM3VfGS%2B4hiMs5dncaVywyrVm7OMt%3DZN6Yj%2BCTDwCyA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidoM3VfGS%2B4hiMs5dncaVywyrVm7OMt%3DZN6Yj%2BCTDwCyA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAG%3D_Duvc4Ai%3D6PXbkTXgOkH4K%2BOU7FbLT5ZE7UR9Y%3Dzymxp%2Byw%40mail.gmail.com.

Re: Error handling in Groovy initialization scripts vs JCasC

[Tim Jacomb]

There are some flags you can use to tune this behaviour:
https://github.com/jenkinsci/configuration-as-code-plugin/blob/a6983ff60e0cf198ce02d7992bcba927197174db/test-harness/src/test/resources/io/jenkins/plugins/casc/validSelfConfig.yml#L1-L5

The default is to show an error page with what failed.

> I concur. My initial impression is that JCasC lacks polish, and I was
> surprised to see it promoted so heavily when issues like this remain.

I think the consensus has been it's 'good enough', there's plenty of room
for improvement, but in general it works 'just fine' for most use-cases



On Thu, 24 Jun 2021 at 16:54, Basil Crow  wrote:

> On Thu, Jun 24, 2021 at 2:18 AM Ullrich Hafner 
> wrote:
> > This is a very bad user experience (actually I don’t know of any other
> application that does not start because of a configuration error).
>
> I concur. My initial impression is that JCasC lacks polish, and I was
> surprised to see it promoted so heavily when issues like this remain.
>
> > This is also the approach that we are using if a plugin changes
> serialization (or if a plugin cannot be started because of missing
> dependencies): in this case Jenkins still continues to work and the
> problems are highlighted in the UI.
>
> Core isn't entirely consistent in this regard, either. Yes
> OldDataMonitor and PluginWrapperAdministrativeMonitor exist. But I
> just tried corrupting core's config.xml file and Jenkins wouldn't
> start at all. But when I corrupted Email Extension's
> hudson.plugins.emailext.ExtendedEmailPublisher.xml, Jenkins started
> but with the default values for Email Extension and no administrative
> monitor in the UI. The latter clearly could use some improvement, but
> I'm not sure about the former. It seems that we want _some_
> configuration loading errors to be fatal. But which ones, exactly? In
> the JCasC issue on GitHub, Antonio raised the valid point that errors
> in loading security-related configuration should be fatal (for obvious
> reasons).
>
> --
> 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/CAFwNDjrLf3jJ-dTk%2BOX1E4b2%3DvB2rsWDFgMX0%2BzKNHMbcgRcJA%40mail.gmail.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/CAH-3BidoM3VfGS%2B4hiMs5dncaVywyrVm7OMt%3DZN6Yj%2BCTDwCyA%40mail.gmail.com.

Re: Error handling in Groovy initialization scripts vs JCasC

[Basil Crow]

On Thu, Jun 24, 2021 at 2:18 AM Ullrich Hafner  wrote:
> This is a very bad user experience (actually I don’t know of any other 
> application that does not start because of a configuration error).

I concur. My initial impression is that JCasC lacks polish, and I was
surprised to see it promoted so heavily when issues like this remain.

> This is also the approach that we are using if a plugin changes serialization 
> (or if a plugin cannot be started because of missing dependencies): in this 
> case Jenkins still continues to work and the problems are highlighted in the 
> UI.

Core isn't entirely consistent in this regard, either. Yes
OldDataMonitor and PluginWrapperAdministrativeMonitor exist. But I
just tried corrupting core's config.xml file and Jenkins wouldn't
start at all. But when I corrupted Email Extension's
hudson.plugins.emailext.ExtendedEmailPublisher.xml, Jenkins started
but with the default values for Email Extension and no administrative
monitor in the UI. The latter clearly could use some improvement, but
I'm not sure about the former. It seems that we want _some_
configuration loading errors to be fatal. But which ones, exactly? In
the JCasC issue on GitHub, Antonio raised the valid point that errors
in loading security-related configuration should be fatal (for obvious
reasons).

-- 
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/CAFwNDjrLf3jJ-dTk%2BOX1E4b2%3DvB2rsWDFgMX0%2BzKNHMbcgRcJA%40mail.gmail.com.

Re: Error handling in Groovy initialization scripts vs JCasC

[Antonio Muñiz]

Cf. https://github.com/jenkinsci/configuration-as-code-plugin/issues/912

On Thu, 24 Jun 2021 at 11:18, Ullrich Hafner 
wrote:

>
>
> > Am 24.06.2021 um 00:54 schrieb Basil Crow :
> >
> > After all these years, we finally migrated from Groovy initialization
> > scripts to JCasC on our Jenkins controllers.
> >
> > While any configuration error is a problem, I noticed that the way
> > these errors are reported differs from one mechanism to the next. With
> > Groovy initialization scripts, errors in one initialization script are
> > logged but this does not prevent subsequent initialization scripts
> > from running and startup from completing. In contrast, an error in a
> > JCasC configuation file causes subsequent changes not to be applied
> > and halts Jenkins startup.
> >
> > Do others view this lack of consistency as a problem? If so, would we
> > want to resolve the inconsistency by making JCasC more lenient or by
> > making Groovy initialization scripts more draconian? I could see
> > arguments both ways: making things more draconian is likely to break
> > things for someone out there, while making things more lenient is
> > likely to hide legitimate errors and decrease operability. I could
> > also see an argument for maintaining the status quo if people are
> > happy with it. If there is a consensus about this I could look into
> > implementing the change.
>
>
> From a user experience view I think that the error handling of JCasC
> currently should be changed (and improved). I’m not using Groovy scripts so
> I don’t care about consistency in that context. But I think that no
> application should totally break because of a misconfigured configuration
> value. This is a very bad user experience (actually I don’t know of any
> other application that does not start because of a configuration error). I
> often have this problem that my working JCasC configuration suddenly breaks
> after an upgrade of JCasC (or another plugin) and Jenkins just not starts
> up. And then you need to dig into log files to see what happens. It would
> be much better if those errors would be reported in the UI and the rest of
> the configuration will be applied (and the broken configuration will be
> initialized with default values). This is also the approach that we are
> using if a plugin changes serialization (or if a plugin cannot be started
> because of missing dependencies): in this case Jenkins still continues to
> work and the problems are highlighted in the UI. The broken components are
> just disabled or default values are used.
>
> --
> 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/CCA1297B-34F4-4D7E-93C1-65D70AA7B7A2%40gmail.com
> .
>


-- 
Antonio Muñiz
Human, Engineer
CloudBees, Inc.

-- 
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/CAJc7kzTfr7QumVupqzzbZG23E0X_FWq5aqNozGKaHSu96jHOYw%40mail.gmail.com.

Re: Error handling in Groovy initialization scripts vs JCasC

[Ullrich Hafner]

> Am 24.06.2021 um 00:54 schrieb Basil Crow :
> 
> After all these years, we finally migrated from Groovy initialization
> scripts to JCasC on our Jenkins controllers.
> 
> While any configuration error is a problem, I noticed that the way
> these errors are reported differs from one mechanism to the next. With
> Groovy initialization scripts, errors in one initialization script are
> logged but this does not prevent subsequent initialization scripts
> from running and startup from completing. In contrast, an error in a
> JCasC configuation file causes subsequent changes not to be applied
> and halts Jenkins startup.
> 
> Do others view this lack of consistency as a problem? If so, would we
> want to resolve the inconsistency by making JCasC more lenient or by
> making Groovy initialization scripts more draconian? I could see
> arguments both ways: making things more draconian is likely to break
> things for someone out there, while making things more lenient is
> likely to hide legitimate errors and decrease operability. I could
> also see an argument for maintaining the status quo if people are
> happy with it. If there is a consensus about this I could look into
> implementing the change.


>From a user experience view I think that the error handling of JCasC currently 
>should be changed (and improved). I’m not using Groovy scripts so I don’t care 
>about consistency in that context. But I think that no application should 
>totally break because of a misconfigured configuration value. This is a very 
>bad user experience (actually I don’t know of any other application that does 
>not start because of a configuration error). I often have this problem that my 
>working JCasC configuration suddenly breaks after an upgrade of JCasC (or 
>another plugin) and Jenkins just not starts up. And then you need to dig into 
>log files to see what happens. It would be much better if those errors would 
>be reported in the UI and the rest of the configuration will be applied (and 
>the broken configuration will be initialized with default values). This is 
>also the approach that we are using if a plugin changes serialization (or if a 
>plugin cannot be started because of missing dependencies): in this case 
>Jenkins still continues to work and the problems are highlighted in the UI. 
>The broken components are just disabled or default values are used. 

-- 
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/CCA1297B-34F4-4D7E-93C1-65D70AA7B7A2%40gmail.com.

Error handling in Groovy initialization scripts vs JCasC

[Basil Crow]

After all these years, we finally migrated from Groovy initialization
scripts to JCasC on our Jenkins controllers.

While any configuration error is a problem, I noticed that the way
these errors are reported differs from one mechanism to the next. With
Groovy initialization scripts, errors in one initialization script are
logged but this does not prevent subsequent initialization scripts
from running and startup from completing. In contrast, an error in a
JCasC configuation file causes subsequent changes not to be applied
and halts Jenkins startup.

Do others view this lack of consistency as a problem? If so, would we
want to resolve the inconsistency by making JCasC more lenient or by
making Groovy initialization scripts more draconian? I could see
arguments both ways: making things more draconian is likely to break
things for someone out there, while making things more lenient is
likely to hide legitimate errors and decrease operability. I could
also see an argument for maintaining the status quo if people are
happy with it. If there is a consensus about this I could look into
implementing the change.

-- 
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/CAFwNDjqih7TVJi8rvkcPbXgn-jzrdRTo%2B8EBuv8y_jQoZJipOA%40mail.gmail.com.

Re: Jenkins parsing error on Nexus 3 Response

['Alain Lavoie' via Jenkins Developers]

Will contact them. Thanks

On Monday, January 11, 2021 at 8:20:50 AM UTC-5 Oleg Nenashev wrote:

> Hello,
>
> Note that the plugin in concern is "maven_artifact_choicelistprovider", 
> not extended choice on its own.
> The plugin is hosted ere: 
> https://github.com/jenkinsci/maven-artifact-choicelistprovider-plugin
> It has enabled GitHub issues, and I assume this is the best way to raise 
> these concerns.
>
> Best regards,
> Oleg
>
> On Monday, January 11, 2021 at 2:19:07 PM UTC+1 ala...@cloudops.com wrote:
>
>> Hi,
>>
>> We recently updated our nexus repository and we are having issues with 
>> the Extended Choice Parameter.
>> We were using it to fetch npm artifact versions and now it is not working.
>>
>> I checked the logs and it is failing because of a mapping error. It seems 
>> that nexus added some information in their asset to add the npm component.
>>
>> , {
>> "id" : "",
>> "repository" : "npm-public",
>> "format" : "npm",
>> "group" : "cloudops",
>> "name" : "cloudmc-ui",
>> "version" : "21.1.0-SNAPSHOT",
>> "assets" : [ {
>>   "downloadUrl" : "",
>>   "path" : "@cloudops/cloudmc-ui/-/cloudmc-ui-21.1.0-SNAPSHOT.tgz",
>>   "id" : "",
>>   "repository" : "npm-public",
>>   "format" : "npm",
>>   "checksum" : {
>> "sha1" : ""
>>   },
>>   "contentType" : "application/x-tgz",
>>   "lastModified" : "2020-06-09T16:00:56.682+00:00",
>>   "npm" : {
>> "name" : "@cloudops/cloudmc-ui",
>> "version" : "21.1.0-SNAPSHOT"
>>   }
>> } ]
>> ...
>>
>> From the logs we have the following error in jenkins.
>>
>> 2021-01-08 21:01:09.267+ [id=52087] WARNING 
>> o.j.p.m.n.Nexus3RestApiSearchService#callService: failed to map
>> com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: 
>> Unrecognized field "npm" (class 
>> org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Item), not 
>> marked as ignorable (9 known properties: "checksum", "path", "downloadUrl", 
>> "repository", "id", "lastModified", "contentType", "format", "maven2"])
>>  at [Source: (String)"{
>>   "items" : [ {
>> "downloadUrl" : "...",
>> "path" : "@cloudops/cloudmc-ui/-/cloudmc-ui-11.0.0.tgz",
>> "id" : "",
>> "repository" : "npm-internal",
>> "format" : "npm",
>> "checksum" : {
>>   "sha1" : ""
>> },
>> "contentType" : "application/x-tgz",
>> "lastModified" : "2018-10-18T20:18:39.900"[truncated 29334 chars]; 
>> line: 13, column: 14] (through reference chain: 
>> org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Nexus3RestResponse["items"]->java.lang.Object[][0]->org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Item["npm"])
>> at 
>> com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:61)
>> at 
>> com.fasterxml.jackson.databind.DeserializationContext.handleUnknownProperty(DeserializationContext.java:823)
>> at 
>> com.fasterxml.jackson.databind.deser.std.StdDeserializer.handleUnknownProperty(StdDeserializer.java:1153)
>> at 
>> com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownProperty(BeanDeserializerBase.java:1589)
>> at 
>> com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownVanilla(BeanDeserializerBase.java:1567)
>> at 
>> com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:294)
>> at 
>> com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
>> at 
>> com.fasterxml.jackson.databind.deser.std.ObjectArrayDeserializer.deserialize(ObjectArrayDeserializer.java:195)
>> at 
>> com.fasterxml.jackson.databind.deser.std.ObjectArrayDeserializer.deserialize(ObjectAr

Re: Jenkins parsing error on Nexus 3 Response

[Oleg Nenashev]

Hello,

Note that the plugin in concern is "maven_artifact_choicelistprovider", not 
extended choice on its own.
The plugin is hosted 
ere: https://github.com/jenkinsci/maven-artifact-choicelistprovider-plugin
It has enabled GitHub issues, and I assume this is the best way to raise 
these concerns.

Best regards,
Oleg

On Monday, January 11, 2021 at 2:19:07 PM UTC+1 ala...@cloudops.com wrote:

> Hi,
>
> We recently updated our nexus repository and we are having issues with the 
> Extended Choice Parameter.
> We were using it to fetch npm artifact versions and now it is not working.
>
> I checked the logs and it is failing because of a mapping error. It seems 
> that nexus added some information in their asset to add the npm component.
>
> , {
> "id" : "",
> "repository" : "npm-public",
> "format" : "npm",
> "group" : "cloudops",
> "name" : "cloudmc-ui",
> "version" : "21.1.0-SNAPSHOT",
> "assets" : [ {
>   "downloadUrl" : "",
>   "path" : "@cloudops/cloudmc-ui/-/cloudmc-ui-21.1.0-SNAPSHOT.tgz",
>   "id" : "",
>   "repository" : "npm-public",
>   "format" : "npm",
>   "checksum" : {
> "sha1" : ""
>   },
>   "contentType" : "application/x-tgz",
>   "lastModified" : "2020-06-09T16:00:56.682+00:00",
>   "npm" : {
> "name" : "@cloudops/cloudmc-ui",
> "version" : "21.1.0-SNAPSHOT"
>   }
> } ]
> ...
>
> From the logs we have the following error in jenkins.
>
> 2021-01-08 21:01:09.267+ [id=52087] WARNING 
> o.j.p.m.n.Nexus3RestApiSearchService#callService: failed to map
> com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: 
> Unrecognized field "npm" (class 
> org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Item), not 
> marked as ignorable (9 known properties: "checksum", "path", "downloadUrl", 
> "repository", "id", "lastModified", "contentType", "format", "maven2"])
>  at [Source: (String)"{
>   "items" : [ {
> "downloadUrl" : "...",
> "path" : "@cloudops/cloudmc-ui/-/cloudmc-ui-11.0.0.tgz",
> "id" : "",
> "repository" : "npm-internal",
> "format" : "npm",
> "checksum" : {
>   "sha1" : ""
> },
> "contentType" : "application/x-tgz",
> "lastModified" : "2018-10-18T20:18:39.900"[truncated 29334 chars]; 
> line: 13, column: 14] (through reference chain: 
> org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Nexus3RestResponse["items"]->java.lang.Object[][0]->org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Item["npm"])
> at 
> com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:61)
> at 
> com.fasterxml.jackson.databind.DeserializationContext.handleUnknownProperty(DeserializationContext.java:823)
> at 
> com.fasterxml.jackson.databind.deser.std.StdDeserializer.handleUnknownProperty(StdDeserializer.java:1153)
> at 
> com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownProperty(BeanDeserializerBase.java:1589)
> at 
> com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownVanilla(BeanDeserializerBase.java:1567)
> at 
> com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:294)
> at 
> com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
> at 
> com.fasterxml.jackson.databind.deser.std.ObjectArrayDeserializer.deserialize(ObjectArrayDeserializer.java:195)
> at 
> com.fasterxml.jackson.databind.deser.std.ObjectArrayDeserializer.deserialize(ObjectArrayDeserializer.java:21)
> at 
> com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
> at 
> com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:288)
> at 
> com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
> at 
> com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4013)
> at 
> com.fasterxml.jackson.databind

Jenkins parsing error on Nexus 3 Response

['Alain Lavoie' via Jenkins Developers]

Hi,

We recently updated our nexus repository and we are having issues with the 
Extended Choice Parameter.
We were using it to fetch npm artifact versions and now it is not working.

I checked the logs and it is failing because of a mapping error. It seems 
that nexus added some information in their asset to add the npm component.

, {
"id" : "",
"repository" : "npm-public",
"format" : "npm",
"group" : "cloudops",
"name" : "cloudmc-ui",
"version" : "21.1.0-SNAPSHOT",
"assets" : [ {
  "downloadUrl" : "",
  "path" : "@cloudops/cloudmc-ui/-/cloudmc-ui-21.1.0-SNAPSHOT.tgz",
  "id" : "",
  "repository" : "npm-public",
  "format" : "npm",
  "checksum" : {
"sha1" : ""
  },
  "contentType" : "application/x-tgz",
  "lastModified" : "2020-06-09T16:00:56.682+00:00",
  "npm" : {
"name" : "@cloudops/cloudmc-ui",
"version" : "21.1.0-SNAPSHOT"
  }
} ]
...

>From the logs we have the following error in jenkins.

2021-01-08 21:01:09.267+ [id=52087] WARNING 
o.j.p.m.n.Nexus3RestApiSearchService#callService: failed to map
com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: 
Unrecognized field "npm" (class 
org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Item), not 
marked as ignorable (9 known properties: "checksum", "path", "downloadUrl", 
"repository", "id", "lastModified", "contentType", "format", "maven2"])
 at [Source: (String)"{
  "items" : [ {
"downloadUrl" : "...",
"path" : "@cloudops/cloudmc-ui/-/cloudmc-ui-11.0.0.tgz",
"id" : "",
"repository" : "npm-internal",
"format" : "npm",
"checksum" : {
  "sha1" : ""
},
"contentType" : "application/x-tgz",
"lastModified" : "2018-10-18T20:18:39.900"[truncated 29334 chars]; 
line: 13, column: 14] (through reference chain: 
org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Nexus3RestResponse["items"]->java.lang.Object[][0]->org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Item["npm"])
at 
com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:61)
at 
com.fasterxml.jackson.databind.DeserializationContext.handleUnknownProperty(DeserializationContext.java:823)
at 
com.fasterxml.jackson.databind.deser.std.StdDeserializer.handleUnknownProperty(StdDeserializer.java:1153)
at 
com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownProperty(BeanDeserializerBase.java:1589)
at 
com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownVanilla(BeanDeserializerBase.java:1567)
at 
com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:294)
at 
com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
at 
com.fasterxml.jackson.databind.deser.std.ObjectArrayDeserializer.deserialize(ObjectArrayDeserializer.java:195)
at 
com.fasterxml.jackson.databind.deser.std.ObjectArrayDeserializer.deserialize(ObjectArrayDeserializer.java:21)
at 
com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
at 
com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:288)
at 
com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:151)
at 
com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4013)
at 
com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3004)
at 
org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Nexus3RestApiSearchService.callService(Nexus3RestApiSearchService.java:54)
at 
org.jenkinsci.plugins.maven_artifact_choicelistprovider.AbstractRESTfulVersionReader.retrieveVersions(AbstractRESTfulVersionReader.java:70)
at 
org.jenkinsci.plugins.maven_artifact_choicelistprovider.AbstractMavenArtifactChoiceListProvider.readURL(AbstractMavenArtifactChoiceListProvider.java:116)
at 
org.jenkinsci.plugins.maven_artifact_choicelistprovider.nexus3.Nexus3ChoiceListProvider$Nexus3DescriptorImpl.wrapTestConnection(Nexus3ChoiceListProvider.java:98)
at 
org.jenkinsci.plugins.maven_artifact_choicelistprovider.AbstractMavenArtifactDescriptorImpl.performTest(AbstractMavenArtifactDescriptorImpl.java:59)
at 
org.jenkinsci.plug

Re: Error: This repository is over its data quota

['Ciprian Burca' via Jenkins Developers]

Duh 臘‍♂️. 

Thanks :)

On Thursday, November 26, 2020 at 4:58:05 PM UTC+2 db...@cloudbees.com 
wrote:

> On Thu, Nov 26, 2020 at 3:51 PM 'Ciprian Burca' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>>
>> How can I fix this?
>>
>
> Don't use Git LFS.
>

-- 
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/94fc8ce7-3f0d-4465-8180-404ca3701509n%40googlegroups.com.

Re: Error: This repository is over its data quota

[Daniel Beck]

On Thu, Nov 26, 2020 at 3:51 PM 'Ciprian Burca' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
> How can I fix this?
>

Don't use Git LFS.

-- 
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/CAMo7PtJp0YN7yrx2Q1Wi5CQrw2YVLxM0vV5uRbzZVn39VWj0eg%40mail.gmail.com.

Error: This repository is over its data quota

['Ciprian Burca' via Jenkins Developers]

Hello everybody,

I tried to move our plugin documentation to GitHub as described here 
<https://www.jenkins.io/doc/developer/publishing/documentation/>. The 
content included two images of   57kB and 38 kB. When I try to push to 
remote I get the following error:

*batch response: This repository is over its data quota. Account 
responsible for LFS bandwidth should purchase more data packs to restore 
access. error: failed to push some refs to *

How can I fix this? 

Thanks

-- 
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/e91f7113-d022-41cc-a40d-de2e349c80b0n%40googlegroups.com.

Re: PR build crashed with error message "The channel is closing down or has closed down"

[Mark Waite]

Thanks for the suggestion.  One of the ways that we reduced the impact of
the disconnects was by clicking the "Relaunch agent" button every few
minutes for agents that are disconnected.  We implemented that after
observing that many times the agent will reconnect when the relaunch agent
button is clicked by an administrator.  We can certainly double check that
there is no async reboot of the agent, but I don't expect there to be one.

On Sat, Aug 8, 2020 at 5:28 AM Steve Carter  wrote:

> I've experienced this error in my corporate network where the agent was
> just so busy with the Jenkins job that it didn't respond to monitoring and
> monitoring rebooted the machine. I don't know aws, but if it's easy to
> check it could be worth ruling out
>
> --
> 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/d2abc458-42a7-4e76-b919-04222bf49cc8o%40googlegroups.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/CAO49JtE7roqJehXGjpABjV7HEssFsSe6SPzh0WHmSsWv6GUN3w%40mail.gmail.com.

Re: PR build crashed with error message "The channel is closing down or has closed down"

[Steve Carter]

I've experienced this error in my corporate network where the agent was just so 
busy with the Jenkins job that it didn't respond to monitoring and monitoring 
rebooted the machine. I don't know aws, but if it's easy to check it could be 
worth ruling out

-- 
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/d2abc458-42a7-4e76-b919-04222bf49cc8o%40googlegroups.com.

Re: PR build crashed with error message "The channel is closing down or has closed down"

[Mark Waite]

Unfortunately, there is not much that you can do to diagnose the issue.
There is some issue that causes the agents on AWS EC2 to be disconnected
from the master on Azure.  We don't know if the issue is in the EC2 plugin,
the communications between the Azure Jenkins master and AWS EC2 agent, the
remoting code that carries the data, or something completely outside those
items.

I've started a new copy of the job in hopes the connection between agent
and master will last long enough to complete the job.

Mark Waite

On Fri, Aug 7, 2020 at 3:22 PM Mads Mohr Christensen 
wrote:

> Thanks Gavin, great tip!
>
> Unfortunately it failed again with the same error message:
>
> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadoptopenjdk-plugin/detail/PR-12/2/pipeline/68
>
> At time of writing this mail the job is still running but it will most
> likely timeout in an hour.
>
> I can't remember seeing this error before and I really don't know how to
> deal with it. Does anyone have a tip on how I can debug this?
>
> On Fri, Aug 7, 2020 at 7:36 PM 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> Easiest way as a non admin:
>>
>> Close the PR, wait a couple seconds, and reopen it.
>>
>> On Fri, Aug 7, 2020 at 10:28 AM Mads Mohr Christensen 
>> wrote:
>>
>>> I've opened a PR which just includes a better error message.
>>> The build completed very fast for Linux JDK 8+11 but for Windows it
>>> looks like the build has crashed.
>>>
>>> Error message:
>>> Cannot contact EC2 (aws) - Windows 2019 (i-003aa1d3772d37d10):
>>> hudson.remoting.ChannelClosedException: Channel
>>> "hudson.remoting.Channel@2f7406ec:EC2 (aws) - Windows 2019
>>> (i-003aa1d3772d37d10)": Remote call on EC2 (aws) - Windows 2019
>>> (i-003aa1d3772d37d10) failed. The channel is closing down or has closed down
>>>
>>>
>>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadoptopenjdk-plugin/detail/PR-12/1/pipeline/24/
>>>
>>> Is there a way to cancel a running job and to start it again?
>>>
>>> --
>>> 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/CALWGXhdA_t4SeTbXWW-8YaoyhZofHj_qsCnJwuyQJwP1AG5rZw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALWGXhdA_t4SeTbXWW-8YaoyhZofHj_qsCnJwuyQJwP1AG5rZw%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
>> 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/CAG%3D_Duv%3DNYLpkfU9Nw5b%2BV6TfbbDWkCOmxtHZqJmU1KUBZXoiA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duv%3DNYLpkfU9Nw5b%2BV6TfbbDWkCOmxtHZqJmU1KUBZXoiA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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/CALWGXhfqWQO_wg-6sh8DJhsJBXPJ5biwiScdrEcZNH%3DOBqkRTA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CALWGXhfqWQO_wg-6sh8DJhsJBXPJ5biwiScdrEcZNH%3DOBqkRTA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAO49JtHs9JmP1EgUJfrGdf4Z1g11-pmQkhLpWcboe0T6PxUEgA%40mail.gmail.com.

Re: PR build crashed with error message "The channel is closing down or has closed down"

[Mads Mohr Christensen]

Thanks Gavin, great tip!

Unfortunately it failed again with the same error message:
https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadoptopenjdk-plugin/detail/PR-12/2/pipeline/68

At time of writing this mail the job is still running but it will most
likely timeout in an hour.

I can't remember seeing this error before and I really don't know how to
deal with it. Does anyone have a tip on how I can debug this?

On Fri, Aug 7, 2020 at 7:36 PM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Easiest way as a non admin:
>
> Close the PR, wait a couple seconds, and reopen it.
>
> On Fri, Aug 7, 2020 at 10:28 AM Mads Mohr Christensen 
> wrote:
>
>> I've opened a PR which just includes a better error message.
>> The build completed very fast for Linux JDK 8+11 but for Windows it looks
>> like the build has crashed.
>>
>> Error message:
>> Cannot contact EC2 (aws) - Windows 2019 (i-003aa1d3772d37d10):
>> hudson.remoting.ChannelClosedException: Channel
>> "hudson.remoting.Channel@2f7406ec:EC2 (aws) - Windows 2019
>> (i-003aa1d3772d37d10)": Remote call on EC2 (aws) - Windows 2019
>> (i-003aa1d3772d37d10) failed. The channel is closing down or has closed down
>>
>>
>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadoptopenjdk-plugin/detail/PR-12/1/pipeline/24/
>>
>> Is there a way to cancel a running job and to start it again?
>>
>> --
>> 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/CALWGXhdA_t4SeTbXWW-8YaoyhZofHj_qsCnJwuyQJwP1AG5rZw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALWGXhdA_t4SeTbXWW-8YaoyhZofHj_qsCnJwuyQJwP1AG5rZw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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/CAG%3D_Duv%3DNYLpkfU9Nw5b%2BV6TfbbDWkCOmxtHZqJmU1KUBZXoiA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duv%3DNYLpkfU9Nw5b%2BV6TfbbDWkCOmxtHZqJmU1KUBZXoiA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CALWGXhfqWQO_wg-6sh8DJhsJBXPJ5biwiScdrEcZNH%3DOBqkRTA%40mail.gmail.com.

Re: PR build crashed with error message "The channel is closing down or has closed down"

['Gavin Mogan' via Jenkins Developers]

Easiest way as a non admin:

Close the PR, wait a couple seconds, and reopen it.

On Fri, Aug 7, 2020 at 10:28 AM Mads Mohr Christensen 
wrote:

> I've opened a PR which just includes a better error message.
> The build completed very fast for Linux JDK 8+11 but for Windows it looks
> like the build has crashed.
>
> Error message:
> Cannot contact EC2 (aws) - Windows 2019 (i-003aa1d3772d37d10):
> hudson.remoting.ChannelClosedException: Channel
> "hudson.remoting.Channel@2f7406ec:EC2 (aws) - Windows 2019
> (i-003aa1d3772d37d10)": Remote call on EC2 (aws) - Windows 2019
> (i-003aa1d3772d37d10) failed. The channel is closing down or has closed down
>
>
> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadoptopenjdk-plugin/detail/PR-12/1/pipeline/24/
>
> Is there a way to cancel a running job and to start it again?
>
> --
> 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/CALWGXhdA_t4SeTbXWW-8YaoyhZofHj_qsCnJwuyQJwP1AG5rZw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CALWGXhdA_t4SeTbXWW-8YaoyhZofHj_qsCnJwuyQJwP1AG5rZw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAG%3D_Duv%3DNYLpkfU9Nw5b%2BV6TfbbDWkCOmxtHZqJmU1KUBZXoiA%40mail.gmail.com.

PR build crashed with error message "The channel is closing down or has closed down"

[Mads Mohr Christensen]

I've opened a PR which just includes a better error message.
The build completed very fast for Linux JDK 8+11 but for Windows it looks
like the build has crashed.

Error message:
Cannot contact EC2 (aws) - Windows 2019 (i-003aa1d3772d37d10):
hudson.remoting.ChannelClosedException: Channel
"hudson.remoting.Channel@2f7406ec:EC2 (aws) - Windows 2019
(i-003aa1d3772d37d10)": Remote call on EC2 (aws) - Windows 2019
(i-003aa1d3772d37d10) failed. The channel is closing down or has closed down

https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fadoptopenjdk-plugin/detail/PR-12/1/pipeline/24/

Is there a way to cancel a running job and to start it again?

-- 
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/CALWGXhdA_t4SeTbXWW-8YaoyhZofHj_qsCnJwuyQJwP1AG5rZw%40mail.gmail.com.

Re: [jenkins-infra] Re: certificate error on lts 2.235.2 (centos/red hat)

[Oleg Nenashev]

Thanks all for the quick fix!

On Sun, Jul 19, 2020, 13:00 Tim Jacomb  wrote:

> The cert issue is fixed, thanks Olivier for doing it
>
> Cheers
> Tim
>
> On Sun, 19 Jul 2020 at 09:13, Tim Jacomb  wrote:
>
>> Yes it appears to have expired
>>
>>  curl -kv https://pkg.origin.jenkins.io/
>>
>> * Server certificate:
>> *  subject: CN=pkg.jenkins.io
>> *  start date: Apr 19 13:34:08 2020 GMT
>> *  expire date: Jul 18 13:34:08 2020 GMT
>> *  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
>> *  SSL certificate verify result: certificate has expired (10)
>>
>> Likely needs someone with pkg.jenkins.io access to restart nginx
>>
>> Thanks
>> Tim
>>
>> On Sun, 19 Jul 2020 at 08:50, Amit Dar  wrote:
>>
>>> While trying to download <https://pkg.jenkins.io/redhat-stable/> the
>>> 2.235.2 version of jenkins, I received the following error:
>>>
>>>
>>>
>>> *Error 503 certificate has expired*
>>>
>>> certificate has expired
>>>
>>> *Guru Mediation:*
>>>
>>> Details: cache-hhn4070-HHN 1595144217 4048092794
>>> --
>>>
>>> Varnish cache server
>>>
>>>
>>>
>>> This happened on several devices, which means it is a server problem.
>>>
>>>
>>>
>>> Am I doing something wrong?
>>>
>>> --
>>> 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/8bcec729-7af1-4519-83ce-df5989174e25o%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/8bcec729-7af1-4519-83ce-df5989174e25o%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Infrastructure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkins-infra+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/jenkins-infra/CAH-3BifGHoB%2BZ3a3TmmrrRqP3YbmyP-q_rQOmj0BPmCu5JHFEg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkins-infra/CAH-3BifGHoB%2BZ3a3TmmrrRqP3YbmyP-q_rQOmj0BPmCu5JHFEg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPfivLBcQcb_bP18mPh5qCEk8MLTjOgYPU-aP_URsreB_owkyA%40mail.gmail.com.

Re: certificate error on lts 2.235.2 (centos/red hat)

[Tim Jacomb]

The cert issue is fixed, thanks Olivier for doing it

Cheers
Tim

On Sun, 19 Jul 2020 at 09:13, Tim Jacomb  wrote:

> Yes it appears to have expired
>
>  curl -kv https://pkg.origin.jenkins.io/
>
> * Server certificate:
> *  subject: CN=pkg.jenkins.io
> *  start date: Apr 19 13:34:08 2020 GMT
> *  expire date: Jul 18 13:34:08 2020 GMT
> *  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
> *  SSL certificate verify result: certificate has expired (10)
>
> Likely needs someone with pkg.jenkins.io access to restart nginx
>
> Thanks
> Tim
>
> On Sun, 19 Jul 2020 at 08:50, Amit Dar  wrote:
>
>> While trying to download <https://pkg.jenkins.io/redhat-stable/> the
>> 2.235.2 version of jenkins, I received the following error:
>>
>>
>>
>> *Error 503 certificate has expired*
>>
>> certificate has expired
>>
>> *Guru Mediation:*
>>
>> Details: cache-hhn4070-HHN 1595144217 4048092794
>> --
>>
>> Varnish cache server
>>
>>
>>
>> This happened on several devices, which means it is a server problem.
>>
>>
>>
>> Am I doing something wrong?
>>
>> --
>> 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/8bcec729-7af1-4519-83ce-df5989174e25o%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/8bcec729-7af1-4519-83ce-df5989174e25o%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/CAH-3BifGHoB%2BZ3a3TmmrrRqP3YbmyP-q_rQOmj0BPmCu5JHFEg%40mail.gmail.com.

Re: certificate error on lts 2.235.2 (centos/red hat)

[Tim Jacomb]

Yes it appears to have expired

 curl -kv https://pkg.origin.jenkins.io/

* Server certificate:
*  subject: CN=pkg.jenkins.io
*  start date: Apr 19 13:34:08 2020 GMT
*  expire date: Jul 18 13:34:08 2020 GMT
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify result: certificate has expired (10)

Likely needs someone with pkg.jenkins.io access to restart nginx

Thanks
Tim

On Sun, 19 Jul 2020 at 08:50, Amit Dar  wrote:

> While trying to download <https://pkg.jenkins.io/redhat-stable/> the
> 2.235.2 version of jenkins, I received the following error:
>
>
>
> *Error 503 certificate has expired*
>
> certificate has expired
>
> *Guru Mediation:*
>
> Details: cache-hhn4070-HHN 1595144217 4048092794
> --
>
> Varnish cache server
>
>
>
> This happened on several devices, which means it is a server problem.
>
>
>
> Am I doing something wrong?
>
> --
> 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/8bcec729-7af1-4519-83ce-df5989174e25o%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/8bcec729-7af1-4519-83ce-df5989174e25o%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAH-3BicK_sHBPOg8WqKWuTjA8Hx9WORRNCaZs2z%3DFLf26441xw%40mail.gmail.com.

certificate error on lts 2.235.2 (centos/red hat)

[Amit Dar]

While trying to download <https://pkg.jenkins.io/redhat-stable/> the 
2.235.2 version of jenkins, I received the following error:

 

*Error 503 certificate has expired*

certificate has expired

*Guru Mediation:*

Details: cache-hhn4070-HHN 1595144217 4048092794
--

Varnish cache server

 

This happened on several devices, which means it is a server problem.

 

Am I doing something wrong?

-- 
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/8bcec729-7af1-4519-83ce-df5989174e25o%40googlegroups.com.

Re: Build Error

['Gavin Mogan' via Jenkins Developers]

*There's a very clear error message, which is preventing maven from
running tests, which means no xml files for the junit plugin to parse
which is the error message you saw*


*You need to fix the errors*


*21:32:07*  [WARNING] Rule 4:
org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed with
message:*21:32:07*  Failed while enforcing RequireUpperBoundDeps. The
error(s) are [*21:32:07*  Require upper bound dependencies error for
commons-codec:commons-codec:1.9 paths to dependency are:*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.apache.httpcomponents:httpclient:4.5.2*21:32:07*
+-commons-codec:commons-codec:1.9*21:32:07*  and*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.jenkins-ci.main:jenkins-core:2.222.3*21:32:07*
+-commons-codec:commons-codec:1.12*21:32:07*  and*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.jenkins-ci.main:jenkins-core:2.222.3*21:32:07*
+-commons-httpclient:commons-httpclient:3.1-jenkins-1*21:32:07*
+-commons-codec:commons-codec:1.8*21:32:07*  and*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.jenkins-ci.main:jenkins-core:2.222.3*21:32:07*
+-org.acegisecurity:acegi-security:1.0.7*21:32:07*
+-commons-codec:commons-codec:1.3*21:32:07*  and*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.jenkins-ci.main:jenkins-core:2.222.3*21:32:07*
+-org.kohsuke.stapler:stapler-jrebel:1.258*21:32:07*
+-org.kohsuke.stapler:stapler:1.258*21:32:07*
+-commons-codec:commons-codec:1.9*21:32:07*  , *21:32:07*  Require
upper bound dependencies error for org.slf4j:jcl-over-slf4j:1.7.25
paths to dependency are:*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.slf4j:jcl-over-slf4j:1.7.25*21:32:07*  and*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.jenkins-ci.main:jenkins-core:2.222.3*21:32:07*
+-org.slf4j:jcl-over-slf4j:1.7.26*21:32:07*  , *21:32:07*  Require
upper bound dependencies error for org.slf4j:log4j-over-slf4j:1.7.25
paths to dependency are:*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.slf4j:log4j-over-slf4j:1.7.25*21:32:07*  and*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.jenkins-ci.main:jenkins-core:2.222.3*21:32:07*
+-org.slf4j:log4j-over-slf4j:1.7.26*21:32:07*  , *21:32:07*  Require
upper bound dependencies error for org.slf4j:slf4j-jdk14:1.7.25 paths
to dependency are:*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.slf4j:slf4j-jdk14:1.7.25*21:32:07*  and*21:32:07*
+-io.jenkins.plugins:zohosprints:1.1.2-SNAPSHOT*21:32:07*
+-org.jenkins-ci.main:jenkins-war:2.222.3*21:32:07*
+-org.slf4j:slf4j-jdk14:1.7.26*21:32:07*  ]*21:32:07*  [INFO]
*21:32:07*
 [INFO] BUILD FAILURE*21:32:07*  [INFO]
*21:32:07*
 [INFO] Total time:  01:57 min*21:32:07*  [INFO] Finished at:
2020-05-11T04:32:06Z*21:32:07*  [INFO]
*21:32:07*
 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M2:enforce
(display-info) on project zohosprints: Some Enforcer rules have
failed. Look above for specific messages explaining why the rule
failed. -> [Help 1]


On Sun, May 10, 2020 at 9:42 PM selva vignesh 
wrote:

> Hi,
> Build is getting failed for *zohosprints *plugin. There is no issues in
> code base.
> I'm getting below error,
>
>> *10:03:06*  ERROR: No test report files were found. Configuration 
>> error?*10:03:06*  Finished: FAILURE
>>
>>
> Build Console Log :
> https://ci.jenkins.io/job/Plugins/job/zohosprints-plugin/job/master/64/console
> Kindly check and know is anything need to be done in my side.
>
> Thanks in advance
>
> --
> 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/0397ad94-aa95-4366-9e35-3d7a39a3be75%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/0397ad94-aa95-4366-9e35-3d7a39a3be75%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAG%3D_Dut_7pGcHODBWhSGPUGY2Hsa7%2BJQeAcVNgroZ2-99V40qA%40mail.gmail.com.

Build Error

[selva vignesh]

Hi,
Build is getting failed for *zohosprints *plugin. There is no issues in 
code base.
I'm getting below error,

> *10:03:06*  ERROR: No test report files were found. Configuration 
> error?*10:03:06*  Finished: FAILURE
>
>
Build Console Log : 
https://ci.jenkins.io/job/Plugins/job/zohosprints-plugin/job/master/64/console
Kindly check and know is anything need to be done in my side.

Thanks in advance 

-- 
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/0397ad94-aa95-4366-9e35-3d7a39a3be75%40googlegroups.com.

Re: I'm working on a new plugin and when I try to run it I get the following error

[Mark Waite]

Adopt OpenJDK is widely used in the Jenkins project.  You're also welcome
to use other OpenJDK implementations.  Licensing restrictions on recent
Oracle JDK 8 versions have made it very rarely used in the Jenkins project.

On Mon, Feb 24, 2020 at 11:38 AM Daniel Anechitoaie 
wrote:

> Will do. Is OpenJDK ok? Or i need Oracle JDK?
>
> On Monday, February 24, 2020 at 8:35:39 PM UTC+2, Jesse Glick wrote:
>>
>> On Mon, Feb 24, 2020 at 12:05 PM Daniel Anechitoaie
>>  wrote:
>> > I'm compiling on OpenJDK 11.
>>
>> Best to use JDK 8 for all purposes related to Jenkins.
>>
> --
> 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/b925de42-af7a-4047-92bb-01b39b69d6a6%40googlegroups.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/CAO49JtHt-ooDrX5E0HaETr-_9pj%3Dqha%2BEbWzA%2Ba2AiMC9saD_g%40mail.gmail.com.

Re: I'm working on a new plugin and when I try to run it I get the following error

[Daniel Anechitoaie]

Will do. Is OpenJDK ok? Or i need Oracle JDK?

On Monday, February 24, 2020 at 8:35:39 PM UTC+2, Jesse Glick wrote:
>
> On Mon, Feb 24, 2020 at 12:05 PM Daniel Anechitoaie 
> > wrote: 
> > I'm compiling on OpenJDK 11. 
>
> Best to use JDK 8 for all purposes related to Jenkins. 
>

-- 
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/b925de42-af7a-4047-92bb-01b39b69d6a6%40googlegroups.com.

Re: I'm working on a new plugin and when I try to run it I get the following error

[Jesse Glick]

On Mon, Feb 24, 2020 at 12:05 PM Daniel Anechitoaie
 wrote:
> I'm compiling on OpenJDK 11.

Best to use JDK 8 for all purposes related to Jenkins.

-- 
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/CANfRfr2LUp1V42HZEXzjhz2o3fULmFHU%3D0A95R9PGq29%3D4u5CA%40mail.gmail.com.

Re: I'm working on a new plugin and when I try to run it I get the following error

[Daniel Anechitoaie]

Yes, that was it. I'm compiling on OpenJDK 11.
Using 2.164.1 works now even with parent 
POM 3.56

Thank you.


On Monday, February 24, 2020 at 6:30:39 PM UTC+2, Mark Waite wrote:
>
>
>
> On Mon, Feb 24, 2020 at 9:19 AM Daniel Anechitoaie  > wrote:
>
>> Hmm, yeah, I had a small brainfart. For some reason I was thinking in 
>> decimal and was seeing 3.6 as 3.60 which in my mind was more recent than 
>> 3.56 (which is the latest 3.x version)/
>>
>> So now with 
>>
>> 
>> org.jenkins-ci.plugins
>> plugin
>> 3.56
>> 
>> 
>>
>>
>>
>> And 
>>
>> 
>> 1.8
>> 8
>> 2.121.1
>> 
>>
>>
>>
>> I get
>>
>> [ERROR] Failed to execute goal 
>> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile 
>> (default-compile) on project my-plugin: Compilation failure
>> [ERROR] java.nio.file.NoSuchFileException: 
>> /Users/daniels/Work/my-plugin/target/classes/META-INF/annotations/hudson.Extension
>>
>> Should I just go to latest Jenkins and the 4.0 beta parent pom?
>>
>>
> I receive that message when I'm compiling with Java 11 but using a Jenkins 
> version before 2.164.  The first Jenkins LTS to support Java 11 compilation 
> is Jenkins 2.164 (as far as I know)  I've learned to type:
>
> $ mvn clean -Djenkins.version=2.164.3 verify
>
> Eventually, I will update the plugins where I use that technique so that 
> they require Jenkins 2.164 or newer as their minimum version.  Jenkins 
> 2.164 is over a year old.  
>

-- 
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/723e6cd0-0774-4903-8f3f-f33d1e00567f%40googlegroups.com.

Re: I'm working on a new plugin and when I try to run it I get the following error

[Mark Waite]

On Mon, Feb 24, 2020 at 9:19 AM Daniel Anechitoaie 
wrote:

> Hmm, yeah, I had a small brainfart. For some reason I was thinking in
> decimal and was seeing 3.6 as 3.60 which in my mind was more recent than
> 3.56 (which is the latest 3.x version)/
>
> So now with
>
> 
> org.jenkins-ci.plugins
> plugin
> 3.56
> 
> 
>
>
>
> And
>
> 
> 1.8
> 8
> 2.121.1
> 
>
>
>
> I get
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile
> (default-compile) on project my-plugin: Compilation failure
> [ERROR] java.nio.file.NoSuchFileException:
> /Users/daniels/Work/my-plugin/target/classes/META-INF/annotations/hudson.Extension
>
> Should I just go to latest Jenkins and the 4.0 beta parent pom?
>
>
I receive that message when I'm compiling with Java 11 but using a Jenkins
version before 2.164.  The first Jenkins LTS to support Java 11 compilation
is Jenkins 2.164 (as far as I know)  I've learned to type:

$ mvn clean -Djenkins.version=2.164.3 verify

Eventually, I will update the plugins where I use that technique so that
they require Jenkins 2.164 or newer as their minimum version.  Jenkins
2.164 is over a year old.

-- 
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/CAO49JtFcGD4ByCPZKQ0Zb6pWGirs5utgsHyoUZ5W8zWQOPtzWw%40mail.gmail.com.

Re: I'm working on a new plugin and when I try to run it I get the following error

[Daniel Anechitoaie]

Hmm, yeah, I had a small brainfart. For some reason I was thinking in 
decimal and was seeing 3.6 as 3.60 which in my mind was more recent than 
3.56 (which is the latest 3.x version)/

So now with 


org.jenkins-ci.plugins
plugin
3.56





And 


1.8
8
2.121.1




I get

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile 
(default-compile) on project my-plugin: Compilation failure
[ERROR] java.nio.file.NoSuchFileException: 
/Users/daniels/Work/my-plugin/target/classes/META-INF/annotations/hudson.Extension

Should I just go to latest Jenkins and the 4.0 beta parent pom?

On Monday, February 24, 2020 at 5:58:39 PM UTC+2, Jesse Glick wrote:
>
> On Mon, Feb 24, 2020 at 10:29 AM Daniel Anechitoaie 
> > wrote: 
> >  
> > org.jenkins-ci.plugins 
> > plugin 
> > 3.6 
>
> This is very old. Try using the latest 3.x, and for the newer LTS line 
> you may need to use a 4.0 beta. 
>

-- 
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/89819385-f68d-485b-9c11-30acad69c7ca%40googlegroups.com.

Re: I'm working on a new plugin and when I try to run it I get the following error

[Jesse Glick]

On Mon, Feb 24, 2020 at 10:29 AM Daniel Anechitoaie
 wrote:
> 
> org.jenkins-ci.plugins
> plugin
> 3.6

This is very old. Try using the latest 3.x, and for the newer LTS line
you may need to use a 4.0 beta.

-- 
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/CANfRfr0VF6ebag2%2BVJKAmaYXcGvsjg%3DmLRQ4yFEExXkCkhU5Rw%40mail.gmail.com.

I'm working on a new plugin and when I try to run it I get the following error

[Daniel Anechitoaie]

Hi,

I just started working on a new plugin and when I run mvn hpi:run I get the 
following error:

Failed while enforcing RequireUpperBoundDeps. The error(s) are [
Require upper bound dependencies error for org.slf4j:jcl-over-slf4j:1.7.25 
paths to dependency are:
+-io.jenkins.plugins:my-plugin:1.0.0
  +-org.slf4j:jcl-over-slf4j:1.7.25
and
+-io.jenkins.plugins:my-plugin:1.0.0
  +-org.jenkins-ci.main:jenkins-core:2.204.2
+-org.slf4j:jcl-over-slf4j:1.7.26
,
Require upper bound dependencies error for 
org.slf4j:log4j-over-slf4j:1.7.25 paths to dependency are:
+-io.jenkins.plugins:my-plugin:1.0.0
  +-org.slf4j:log4j-over-slf4j:1.7.25
and
+-io.jenkins.plugins:my-plugin:1.0.0
  +-org.jenkins-ci.main:jenkins-core:2.204.2
+-org.slf4j:log4j-over-slf4j:1.7.26
,
Require upper bound dependencies error for org.slf4j:slf4j-jdk14:1.7.25 
paths to dependency are:
+-io.jenkins.plugins:my-plugin:1.0.0
  +-org.slf4j:slf4j-jdk14:1.7.25
and
+-io.jenkins.plugins:my-plugin:1.0.0
  +-org.jenkins-ci.main:jenkins-war:2.204.2
+-org.slf4j:slf4j-jdk14:1.7.26
]

Any idea what's going on and what I can do to fix this? 
I don't have any direct dependencies to org.slf4j

Here's my POM as well:

---


http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;>

4.0.0


org.jenkins-ci.plugins
plugin
3.6



io.jenkins.plugins
my-plugin
1.0.0
hpi

My Plugin




1.8
8
2.204.2





org.apache.maven.plugins
maven-compiler-plugin

${jdk.version}
${jdk.version}
true



org.jenkins-ci.tools
maven-hpi-plugin

true







repo.jenkins-ci.org
https://repo.jenkins-ci.org/public/





repo.jenkins-ci.org
https://repo.jenkins-ci.org/public/






org.jenkins-ci.plugins
structs
1.17




org.apache.commons
commons-lang3
3.9




org.apache.commons
commons-text
1.8




commons-io
commons-io
2.6




org.codehaus.plexus
plexus-utils
3.3.0



org.jsoup
jsoup
1.12.2




-- 
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/00ff633f-fe59-4861-a7fc-80b07ea0d8c0%40googlegroups.com.

Re: Jenkins Plugin Error

[Matt Sicker]

I think you need to add an index.jelly file for that URL. If you
already have one, can you paste its contents?

On Mon, Dec 23, 2019 at 4:11 PM 'Gavin Mogan' via Jenkins Developers
 wrote:
>
> You havn't really given us very much to work with. At least seeing the code 
> we could make a shot at this.
>
> Did you confirm your run has the action (look at the xml file)
> What url did you try to hit? Looks like /job/testProject/4/greeting but want 
> to confirm
>
> Did you define getUrlName() to something like the tutorials/error message 
> suggested?
>
> Gavin
>
>
> On Mon, Dec 23, 2019 at 5:24 AM wla  wrote:
>>
>> Hello,
>>
>> if i follow this tut :
>> https://jenkins.io/doc/developer/tutorial/extend/
>> i get the following error
>> Stapler processed this HTTP request as follows, but couldn't find the 
>> resource to consume the request
>>
>> -> evaluate( 
>> :hudson.model.Hudson,"/job/testProject/4/greeting")
>> -> 
>> evaluate(((StaplerProxy)).getTarget(),"/job/testProject/4/greeting")
>> -> evaluate(.getJob("testProject"),"/4/greeting")
>> -> evaluate( 
>> :hudson.model.FreeStyleProject,"/4/greeting")
>> -> 
>> evaluate(((StaplerProxy)).getTarget(),"/4/greeting")
>> -> 
>> evaluate(.getDynamic("4",...),"/greeting")
>> -> evaluate( :hudson.model.FreeStyleBuild,"/greeting")
>> -> evaluate(((StaplerProxy)).getTarget(),"/greeting")
>> -> evaluate(.getDynamic("greeting",...),"")
>> -> evaluate( 
>> :io.jenkins.plugins.sample.HelloWorldAction,"")
>> -> No matching rule was found on 
>>  for ""
>>
>>  has the following URL 
>> mappings, in the order of preference:
>>
>> If path ends without '/' insert it
>> TOKEN.groovy for url=/TOKEN
>> VIEW.jelly for url=/VIEW
>> BLOCKED: java.lang.String 
>> io.jenkins.plugins.sample.HelloWorldAction.getDisplayName() for 
>> url=/displayName/...
>> BLOCKED: java.lang.String 
>> io.jenkins.plugins.sample.HelloWorldAction.getIconFileName() for 
>> url=/iconFileName/...
>> BLOCKED: java.lang.String 
>> io.jenkins.plugins.sample.HelloWorldAction.getUrlName() for url=/urlName/...
>> BLOCKED: java.lang.Class java.lang.Object.getClass() for url=/class/...
>> BLOCKED: java.lang.String 
>> io.jenkins.plugins.sample.HelloWorldAction.getName() for url=/name/...
>>
>> have someon a similar issue ?
>> Or better a solution?
>>
>> --
>> 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/41d6fcd1-7721-4191-b6a0-2e825fd575ee%40googlegroups.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/CAG%3D_Dut6cb9_SWnAmuw0yAhLh%2BXjxc4s7merm2d7DVz5KxMVhA%40mail.gmail.com.



-- 
Matt Sicker
Senior Software Engineer, CloudBees

-- 
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/CAEot4ozagS1CPnZFkJbcVqi51iwF7E7w5sH%2BSVS_8pJq3RxS6g%40mail.gmail.com.

Re: Jenkins Plugin Error

['Gavin Mogan' via Jenkins Developers]

You havn't really given us very much to work with. At least seeing the code
we could make a shot at this.

Did you confirm your run has the action (look at the xml file)
What url did you try to hit? Looks like /job/testProject/4/greeting but
want to confirm

Did you define getUrlName() to something like the tutorials/error message
suggested?

Gavin


On Mon, Dec 23, 2019 at 5:24 AM wla  wrote:

> Hello,
>
> if i follow this tut :
> https://jenkins.io/doc/developer/tutorial/extend/
> i get the following error
> Stapler processed this HTTP request as follows, but couldn't find the
> resource to consume the request
>
> -> evaluate(
> :hudson.model.Hudson,"/job/testProject/4/greeting")
> -> evaluate(((StaplerProxy) >).getTarget(),"/job/testProject/4/greeting")
> -> evaluate(.getJob("testProject"),"/4/greeting")
> -> evaluate(
> :hudson.model.FreeStyleProject,"/4/greeting")
> -> evaluate(((StaplerProxy) [testProject]>).getTarget(),"/4/greeting")
> -> evaluate( [testProject]>.getDynamic("4",...),"/greeting")
> -> evaluate( :hudson.model.FreeStyleBuild,"/greeting")
> -> evaluate(((StaplerProxy)).getTarget(),"/greeting")
> -> evaluate(.getDynamic("greeting",...),"")
> -> evaluate(
> :io.jenkins.plugins.sample.HelloWorldAction,"")
> -> No matching rule was found on
>  for ""
>
>  has the following URL
> mappings, in the order of preference:
>
> If path ends without '/' insert it
> TOKEN.groovy for url=/TOKEN
> VIEW.jelly for url=/VIEW
> BLOCKED: java.lang.String
> io.jenkins.plugins.sample.HelloWorldAction.getDisplayName() for
> url=/displayName/...
> BLOCKED: java.lang.String
> io.jenkins.plugins.sample.HelloWorldAction.getIconFileName() for
> url=/iconFileName/...
> BLOCKED: java.lang.String
> io.jenkins.plugins.sample.HelloWorldAction.getUrlName() for url=/urlName/...
> BLOCKED: java.lang.Class java.lang.Object.getClass() for url=/class/...
> BLOCKED: java.lang.String
> io.jenkins.plugins.sample.HelloWorldAction.getName() for url=/name/...
>
> have someon a similar issue ?
> Or better a solution?
>
> --
> 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/41d6fcd1-7721-4191-b6a0-2e825fd575ee%40googlegroups.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/CAG%3D_Dut6cb9_SWnAmuw0yAhLh%2BXjxc4s7merm2d7DVz5KxMVhA%40mail.gmail.com.

Jenkins Plugin Error

[wla]

Hello,

if i follow this tut : 
https://jenkins.io/doc/developer/tutorial/extend/
i get the following error 
Stapler processed this HTTP request as follows, but couldn't find the resource 
to consume the request

-> evaluate( 
:hudson.model.Hudson,"/job/testProject/4/greeting")
-> 
evaluate(((StaplerProxy)).getTarget(),"/job/testProject/4/greeting")
-> evaluate(.getJob("testProject"),"/4/greeting")
-> evaluate( 
:hudson.model.FreeStyleProject,"/4/greeting")
-> 
evaluate(((StaplerProxy)).getTarget(),"/4/greeting")
-> 
evaluate(.getDynamic("4",...),"/greeting")
-> evaluate( :hudson.model.FreeStyleBuild,"/greeting")
-> evaluate(((StaplerProxy)).getTarget(),"/greeting")
-> evaluate(.getDynamic("greeting",...),"")
-> evaluate( 
:io.jenkins.plugins.sample.HelloWorldAction,"")
-> No matching rule was found on 
 for ""

 has the following URL mappings, 
in the order of preference:

If path ends without '/' insert it
TOKEN.groovy for url=/TOKEN
VIEW.jelly for url=/VIEW
BLOCKED: java.lang.String 
io.jenkins.plugins.sample.HelloWorldAction.getDisplayName() for 
url=/displayName/...
BLOCKED: java.lang.String 
io.jenkins.plugins.sample.HelloWorldAction.getIconFileName() for 
url=/iconFileName/...
BLOCKED: java.lang.String 
io.jenkins.plugins.sample.HelloWorldAction.getUrlName() for url=/urlName/...
BLOCKED: java.lang.Class java.lang.Object.getClass() for url=/class/...
BLOCKED: java.lang.String 
io.jenkins.plugins.sample.HelloWorldAction.getName() for url=/name/... 

have someon a similar issue ?
Or better a solution?

-- 
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/41d6fcd1-7721-4191-b6a0-2e825fd575ee%40googlegroups.com.

Re: 502 proxy error on ci.jenkins.io

[Jesse Glick]

On Thu, Oct 24, 2019 at 9:14 AM Chris Kilding
 wrote:
> is the master being overwhelmed by either the sheer number of steps as they 
> enter the job queue, or the parallelism of those steps when they execute

Quite possibly. The server sets a cap on the number of active elastic
agents, which is fine, but pushing up against that limit seems to
actually cause things to explode, rather than tasks simply waiting
politely in the queue. No one with sufficient access has (to my
knowledge) yet tried to track down whether the problem is in Jenkins
core, Pipeline, the Azure agent plugin we use, or something else.

https://github.com/jenkinsci/bom/blob/f384f08edeb3da9a2ba2c5b83be3fee4b5e0c628/Jenkinsfile#L40-L43

-- 
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/CANfRfr2_9kw15pWuyzA-591MZrsNR3S_OgpGZB0dpvtRMuPsvg%40mail.gmail.com.

Re: 502 proxy error on ci.jenkins.io

[Chris Kilding]

It happened again this morning.

The recent 502 errors seemed to coincide with builds of certain Jenkins Core 
components, which have a large number of (parallel) steps.

Just an initial idea - is the master being overwhelmed by either the sheer 
number of steps as they enter the job queue, or the parallelism of those steps 
when they execute (they seem to take over almost every executor)?

Chris

On Thu, 3 Oct 2019, at 8:37 PM, Tim Jacomb wrote:
> Seems to be happening again now
> https://p.datadoghq.com/sb/0Igb9a-dca9738dbb5048025c005182a8f240c0
> 
> On Wed, 2 Oct 2019 at 15:14, Paul Allen  wrote:
>> Thanks - It seems to be working now.
>> 
>>  > On 2 Oct 2019, at 10:24, Olblak  wrote:
>>  >
>>  > As you can see on this status page, there is definitely something wrong, 
>> I start looking at it
>>  >
>>  > ---
>>  > -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
>>  > ---
>>  >
>>  >
>>  >
>>  >
>>  > On Wed, Oct 2, 2019, at 10:37 AM, pallen wrote:
>>  >> Hi Guys,
>>  >>
>>  >> I'm getting a 502 proxy error on ci.jenkins.io? Is it just me or is 
>> there an outage?
>>  >>
>>  >> Kind regards,
>>  >> Paul
>>  >>
>>  >>
>>  >> --
>>  >> 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 
>> <mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>.
>>  >> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/fdc23c1f-ecf0-47bc-b4d8-d3bf126b2170%40googlegroups.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 
>> <mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>.
>>  > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/bd355020-3a8e-45ec-a2cc-4eb0f87e68c8%40www.fastmail.com.
>> 
>>  This e-mail may contain information that is privileged or confidential. If 
>> you are not the intended recipient, please delete the e-mail and any 
>> attachments and notify us immediately.
>> 
>>  Perforce Software UK Ltd is registered in England and Wales as company no.
>>  3816019 at the following address: West Forest Gate,
>>  Wellington Road, Wokingham,
>>  RG40 2AT, UK
>> 
>>  -- 
>>  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 
>> <mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>.
>>  To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/5475CAA0-A0A1-4619-9983-3F49D763D1B0%40perforce.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/CAH-3Bier9Qgwc6qsDvV_q0yqg_bmzUMi5YoLsbadLaRATeOQBA%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bier9Qgwc6qsDvV_q0yqg_bmzUMi5YoLsbadLaRATeOQBA%40mail.gmail.com?utm_medium=email_source=footer>.

-- 
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/a125c2f9-a61a-4cb3-9d12-44de3fe4726c%40www.fastmail.com.

Re: 502 proxy error on ci.jenkins.io

[Tim Jacomb]

Seems to be happening again now
https://p.datadoghq.com/sb/0Igb9a-dca9738dbb5048025c005182a8f240c0

On Wed, 2 Oct 2019 at 15:14, Paul Allen  wrote:

> Thanks - It seems to be working now.
>
> > On 2 Oct 2019, at 10:24, Olblak  wrote:
> >
> > As you can see on this status page, there is definitely something wrong,
> I start looking at it
> >
> > ---
> > -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> > ---
> >
> >
> >
> >
> > On Wed, Oct 2, 2019, at 10:37 AM, pallen wrote:
> >> Hi Guys,
> >>
> >> I'm getting a 502 proxy error on ci.jenkins.io?  Is it just me or is
> there an outage?
> >>
> >> Kind regards,
> >> Paul
> >>
> >>
> >> --
> >> 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/fdc23c1f-ecf0-47bc-b4d8-d3bf126b2170%40googlegroups.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/bd355020-3a8e-45ec-a2cc-4eb0f87e68c8%40www.fastmail.com
> .
>
> This e-mail may contain information that is privileged or confidential. If
> you are not the intended recipient, please delete the e-mail and any
> attachments and notify us immediately.
>
> Perforce Software UK Ltd is registered in England and Wales as company no.
> 3816019 at the following address: West Forest Gate,
> Wellington Road, Wokingham,
> RG40 2AT, UK
>
> --
> 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/5475CAA0-A0A1-4619-9983-3F49D763D1B0%40perforce.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/CAH-3Bier9Qgwc6qsDvV_q0yqg_bmzUMi5YoLsbadLaRATeOQBA%40mail.gmail.com.

Re: 502 proxy error on ci.jenkins.io

[Paul Allen]

Thanks - It seems to be working now.

> On 2 Oct 2019, at 10:24, Olblak  wrote:
>
> As you can see on this status page, there is definitely something wrong, I 
> start looking at it
>
> ---
> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
>
>
>
> On Wed, Oct 2, 2019, at 10:37 AM, pallen wrote:
>> Hi Guys,
>>
>> I'm getting a 502 proxy error on ci.jenkins.io?  Is it just me or is there 
>> an outage?
>>
>> Kind regards,
>> Paul
>>
>>
>> --
>> 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/fdc23c1f-ecf0-47bc-b4d8-d3bf126b2170%40googlegroups.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/bd355020-3a8e-45ec-a2cc-4eb0f87e68c8%40www.fastmail.com.

This e-mail may contain information that is privileged or confidential. If you 
are not the intended recipient, please delete the e-mail and any attachments 
and notify us immediately.

Perforce Software UK Ltd is registered in England and Wales as company no.
3816019 at the following address: West Forest Gate,
Wellington Road, Wokingham,
RG40 2AT, UK

-- 
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/5475CAA0-A0A1-4619-9983-3F49D763D1B0%40perforce.com.

Re: 502 proxy error on ci.jenkins.io

[Olblak]

As you can see on this status page 
<https://p.datadoghq.com/sb/0Igb9a-dca9738dbb5048025c005182a8f240c0>, there is 
definitely something wrong, I start looking at it

---
-> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---




On Wed, Oct 2, 2019, at 10:37 AM, pallen wrote:
> Hi Guys,
> 
> I'm getting a 502 proxy error on ci.jenkins.io? Is it just me or is there an 
> outage?
> 
> Kind regards,
> Paul
> 

> --
>  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/fdc23c1f-ecf0-47bc-b4d8-d3bf126b2170%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/fdc23c1f-ecf0-47bc-b4d8-d3bf126b2170%40googlegroups.com?utm_medium=email_source=footer>.

-- 
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/bd355020-3a8e-45ec-a2cc-4eb0f87e68c8%40www.fastmail.com.

502 proxy error on ci.jenkins.io

[pallen]

Hi Guys,

I'm getting a 502 proxy error on ci.jenkins.io?  Is it just me or is there 
an outage?

Kind regards,
Paul

-- 
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/fdc23c1f-ecf0-47bc-b4d8-d3bf126b2170%40googlegroups.com.

Re: ERROR: Permission to jenkinsci/openshift-client-plugin.git denied

[Oleg Nenashev]

See https://groups.google.com/forum/#!topic/jenkinsci-dev/2kWOhATbNJM

On Saturday, August 10, 2019 at 2:38:55 AM UTC+2, Akram Ben Aissi wrote:
>
> looks like an admin of the project had to invite me to collaboration.
> we were missing this for this project.
> Thank you
>
> On Fri, 9 Aug 2019 at 20:58, Slide > 
> wrote:
>
>> Can you give more details on what error you are seeing?
>>
>> On Fri, Aug 9, 2019 at 11:57 AM Akram Ben Aissi > > wrote:
>>
>>> Hi admins,
>>>
>>>
>>> I am trying to cut a release for the openshift-client-plugin and got a 
>>> permission denied for my user despite it is listed in:
>>>
>>> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-openshift-client.yml
>>>
>>> can someone help?
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/b8044a33-505d-4738-b629-a243c9e7860a%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/b8044a33-505d-4738-b629-a243c9e7860a%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> -- 
>> Website: http://earl-of-code.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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcoGgzUAK%2BC%3DvayWziY25c4EKYY%3DOPAhRPMXRcNjQY0bw%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcoGgzUAK%2BC%3DvayWziY25c4EKYY%3DOPAhRPMXRcNjQY0bw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
>
> AKRAM BEN AISSI
>
> PRINCIPAL SOFTWARE ENGINEER
>
>  <https://red.ht/sig>
>
> M: +33.6.31.57.08.60   T: @akrambenaissi 
> <http://twitter.com/akrambenaissi>
>
> E: aben...@redhat.com #: Akram  
>
>
>

-- 
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/d59b0cb3-5aa9-4361-ae3a-975c514c0ab3%40googlegroups.com.

Re: ERROR: Permission to jenkinsci/openshift-client-plugin.git denied to

[Daniel Beck]

> On 9. Aug 2019, at 20:57, Akram Ben Aissi  wrote:
> 
> despite my user is listed here:
> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-openshift-client.yml
> 
> 
> Am I missing something?
> 

https://github.com/jenkins-infra/repository-permissions-updater#about

-- 
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/98899E63-B93E-457C-AB70-7706B25516D3%40beckweb.net.

Re: ERROR: Permission to jenkinsci/openshift-client-plugin.git denied to

[Oleg Nenashev]

Hi,

GitHub is managed by chatops or by plugin maintiners who can add more 
contributors to the plugin developer teams.
Taking the approvals for 
https://github.com/jenkins-infra/repository-permissions-updater/commit/ce27600d5d839d4df866bc6ff92f815c5f9b6055#diff-074094ab111c0b5f7f586e7b4d66f7de
 , 
I have granted access to you and Vibhav Bobade.
I have not touched other plugins from the commit so far.

Best regards,
Oleg


On Saturday, August 10, 2019 at 4:57:04 AM UTC+2, Gavin Mogan wrote:
>
> Sounds like you figured it out, but that file controls who can publish 
> releases to the nexus repository. 
>
> I think your error message is access to GitHub, which is managed elsewhere.
>
> Publishers need GitHub, but committers don't need publishing access.
>
> Gavin
>
> On Fri., Aug. 9, 2019, 5:38 p.m. Akram Ben Aissi,  > wrote:
>
>> Hi all,
>>
>> I am trying to cut a release for the openshift-client-plugin and got the 
>> following error:
>>  ERROR: Permission to jenkinsci/openshift-client-plugin.git denied to 
>> akram
>>
>> despite my user is listed here:
>>
>> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-openshift-client.yml
>>
>>
>> Am I missing something?
>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/2549c745-906f-491e-9033-bb1656623dce%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/2549c745-906f-491e-9033-bb1656623dce%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/a780e908-1aee-49cb-a364-9a417a599e89%40googlegroups.com.

Re: ERROR: Permission to jenkinsci/openshift-client-plugin.git denied to

[Gavin]

Sounds like you figured it out, but that file controls who can publish
releases to the nexus repository.

I think your error message is access to GitHub, which is managed elsewhere.

Publishers need GitHub, but committers don't need publishing access.

Gavin

On Fri., Aug. 9, 2019, 5:38 p.m. Akram Ben Aissi, 
wrote:

> Hi all,
>
> I am trying to cut a release for the openshift-client-plugin and got the
> following error:
>  ERROR: Permission to jenkinsci/openshift-client-plugin.git denied to akram
>
> despite my user is listed here:
>
> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-openshift-client.yml
>
>
> Am I missing something?
>
> --
> 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/2549c745-906f-491e-9033-bb1656623dce%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/2549c745-906f-491e-9033-bb1656623dce%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAG%3D_DuuoGDEUx%3D-e4Ec8Z-SdOp7BMQVFsWKUKX9MbSMkQD2p0A%40mail.gmail.com.

Re: ERROR: Permission to jenkinsci/openshift-client-plugin.git denied

[Akram Ben Aissi]

looks like an admin of the project had to invite me to collaboration.
we were missing this for this project.
Thank you

On Fri, 9 Aug 2019 at 20:58, Slide  wrote:

> Can you give more details on what error you are seeing?
>
> On Fri, Aug 9, 2019 at 11:57 AM Akram Ben Aissi 
> wrote:
>
>> Hi admins,
>>
>>
>> I am trying to cut a release for the openshift-client-plugin and got a
>> permission denied for my user despite it is listed in:
>>
>> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-openshift-client.yml
>>
>> can someone help?
>>
>> --
>> 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/b8044a33-505d-4738-b629-a243c9e7860a%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/b8044a33-505d-4738-b629-a243c9e7860a%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> Website: http://earl-of-code.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/CAPiUgVcoGgzUAK%2BC%3DvayWziY25c4EKYY%3DOPAhRPMXRcNjQY0bw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcoGgzUAK%2BC%3DvayWziY25c4EKYY%3DOPAhRPMXRcNjQY0bw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 

AKRAM BEN AISSI

PRINCIPAL SOFTWARE ENGINEER

 <https://red.ht/sig>

M: +33.6.31.57.08.60T: @akrambenaissi
<http://twitter.com/akrambenaissi>

E: abena...@redhat.com#: Akram

-- 
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/CAFkVfmMF7Qz9oD59ZWnf2e%3Dbx8wkBS6CENxuUG0yMKQpYrXbvg%40mail.gmail.com.

ERROR: Permission to jenkinsci/openshift-client-plugin.git denied to

[Akram Ben Aissi]

Hi all,

I am trying to cut a release for the openshift-client-plugin and got the 
following error:
 ERROR: Permission to jenkinsci/openshift-client-plugin.git denied to akram

despite my user is listed here:
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-openshift-client.yml


Am I missing something?

-- 
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/2549c745-906f-491e-9033-bb1656623dce%40googlegroups.com.