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

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

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

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

Error in Javadoc when attempting to publish a new plugin version

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

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

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

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

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

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

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

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

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

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

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"

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

. 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

Re: Banned dependencies error compiling SAML plugin PR

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 -

Re: Banned dependencies error compiling SAML plugin PR

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

Re: Banned dependencies error compiling SAML plugin PR

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

Re: Banned dependencies error compiling SAML plugin PR

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

Re: Banned dependencies error compiling SAML plugin PR

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

Re: Banned dependencies error compiling SAML plugin PR

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 v

Re: Banned dependencies error compiling SAML plugin PR

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

Banned dependencies error compiling SAML plugin PR

] [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

Re: Error while setting up Jenkins core

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

Re: Error while setting up Jenkins core

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

Re: Error while setting up Jenkins core

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

Re: Error while setting up Jenkins core

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 inst

Re: Error while setting up Jenkins core

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

Error while setting up Jenkins core

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 o

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

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

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

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

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

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

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

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

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

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

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

t; > *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

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

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?

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

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, sen

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

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

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

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

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

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

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

ty, > > 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: dup

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

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

Re: error occuring during mvn release

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

Re: Error publishing plugin

t;> 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

Re: Error publishing plugin

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

Re: Error publishing plugin

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

Error publishing plugin

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 in

Re: Certificate expiry error on get.jenkins.io

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

Re: Certificate expiry error on get.jenkins.io

://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... >&g

Re: Certificate expiry error on get.jenkins.io

gt; > 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.4

Certificate expiry error on get.jenkins.io

.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

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

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

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

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

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

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

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

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 plugi

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

"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

javadoc-plugin error since plugin-pom 4.19 ?

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

Re: Error handling in Groovy initialization scripts vs JCasC

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

Re: Error handling in Groovy initialization scripts vs JCasC

On Thu, Jun 24, 2021 at 9:07 AM Tim Jacomb wrote: > > There are some flags you can use to tune this behaviour: >

Re: Error handling in Groovy initialization scripts vs JCasC

insci/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 poli

Re: Error handling in Groovy initialization scripts vs JCasC

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

Re: Error handling in Groovy initialization scripts vs JCasC

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 pr

Re: Error handling in Groovy initialization scripts vs JCasC

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

Re: Error handling in Groovy initialization scripts vs JCasC

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

Error handling in Groovy initialization scripts vs JCasC

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

Re: Jenkins parsing error on Nexus 3 Response

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

Re: Jenkins parsing error on Nexus 3 Response

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

Jenkins parsing error on Nexus 3 Response

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

Re: Error: This repository is over its data quota

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

Re: Error: This repository is over its data quota

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

Error: This repository is over its data quota

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 re

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

ent 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

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

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

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

vin, 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

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

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

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

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

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

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

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

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

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

im > > 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* >> >

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

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 fol

certificate error on lts 2.235.2 (centos/red hat)

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 4048

Re: Build Error

*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

Build Error

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

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

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

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

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

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

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

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

3.56 >> >> >> >> >> >> And >> >> >> 1.8 >> 8 >> 2.121.1 >> >> >> >> >> I get >> >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-compi

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

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

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

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

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

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

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

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

Re: Jenkins Plugin Error

ke 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? > > Gavi

Re: Jenkins Plugin Error

() 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 f

Jenkins Plugin Error

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")

Re: 502 proxy error on ci.jenkins.io

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

Re: 502 proxy error on ci.jenkins.io

;> > --- >> > -> 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 50

Re: 502 proxy error on ci.jenkins.io

age, 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, >

Re: 502 proxy error on ci.jenkins.io

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

Re: 502 proxy error on ci.jenkins.io

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

502 proxy error on ci.jenkins.io

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 fro

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

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

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

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

Re: ERROR: Permission to jenkinsci/openshift-client-plugin.git denied 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: > >&g

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

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

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

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

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

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

  1   2   3   4   5   >