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

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) on project openshift-client: Unable to commit files [ERROR] Provider message: [ERROR] The git-push command failed. [ERROR] Command output: [ERROR] ERROR: Permission to jenkinsci/openshift

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

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

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

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

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

lp fix it. Thanks in advance. >> >> On Wednesday, July 17, 2019 at 12:26:46 AM UTC+5:30, Jesse Glick wrote: >>> >>> On Tue, Jul 16, 2019 at 2:47 PM Parichay Barpanda >>> wrote: >>> > Invalid archive retrieved from Jenkins, perhaps the plugin is not

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

;> properly incrementalized? >> >> Well Tyler added this particular error message, perhaps related to >> INFRA-2125: >> >> >> https://github.com/jenkins-infra/community-functions/commit/d4bf3d3c68961b6a778325397336bdb7d99fe4a4 >> >> Since I lack access to

Re: JNLP : Error: Invalid or corrupt jarfile agent.jar

Also make sure to launch with at least Java 8, preferably the exact version of Java running 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

Re: JNLP : Error: Invalid or corrupt jarfile agent.jar

Maybe a virus scanner is damaging the file during download? On Wed, Jul 17, 2019, 3:29 AM Mathieu Delrocq wrote: > Hello, > > My problem is when try to launch the command "java -jar agent.jar ... " to > connect my Jenkins agent via JNLP, I got the error "Error: I

JNLP : Error: Invalid or corrupt jarfile agent.jar

Hello, My problem is when try to launch the command "java -jar agent.jar ... " to connect my Jenkins agent via JNLP, I got the error "Error: Invalid or corrupt jarfile agent.jar". I download agent.jar with a command "curl". My Jenkins is launched with the war

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

:47 PM Parichay Barpanda > > wrote: > > Invalid archive retrieved from Jenkins, perhaps the plugin is not > properly incrementalized? > > Well Tyler added this particular error message, perhaps related to > INFRA-2125: > > > https://github.com/j

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

On Tue, Jul 16, 2019 at 2:47 PM Parichay Barpanda wrote: > Invalid archive retrieved from Jenkins, perhaps the plugin is not properly > incrementalized? Well Tyler added this particular error message, perhaps related to INFRA-2125: https://github.com/jenkins-infra/community-functions/

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

p directory to .gitignore to test the build. Now I >>>> tried to remove classes that might have affected the images such as >>>> GitLabAvatarCache (didn't work), refixed svgs and the pngs (didn't work). >>>> The current work can be found in this commit - >>>> https://github

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

gt;> The current work can be found in this commit - >>> https://github.com/jenkinsci/gitlab-branch-source-plugin/commit/57c5f1705a78a5a3c6012ebfc0ded91a4c93dcab >>> . >>> >>> I am unable to understand the issue, if it was bug in the code it would >>> have also

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

gt; The current work can be found in this commit - >> https://github.com/jenkinsci/gitlab-branch-source-plugin/commit/57c5f1705a78a5a3c6012ebfc0ded91a4c93dcab >> . >> >> I am unable to understand the issue, if it was bug in the code it would >> have also returned error ab

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

, refixed svgs and the pngs (didn't work). >> The current work can be found in this commit - >> https://github.com/jenkinsci/gitlab-branch-source-plugin/commit/57c5f1705a78a5a3c6012ebfc0ded91a4c93dcab >> . >> >> I am unable to understand the issue, if it was bug in

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

gt; The current work can be found in this commit - > https://github.com/jenkinsci/gitlab-branch-source-plugin/commit/57c5f1705a78a5a3c6012ebfc0ded91a4c93dcab > . > > I am unable to understand the issue, if it was bug in the code it would > have also returned error about the w

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

/jenkinsci/gitlab-branch-source-plugin/commit/57c5f1705a78a5a3c6012ebfc0ded91a4c93dcab . I am unable to understand the issue, if it was bug in the code it would have also returned error about the webapp images but it also returns errors with the docs images. On Tuesday, July 16, 2019 at 12:32:01 AM

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

On Sun, Jul 14, 2019 at 11:53 AM Parichay Barpanda wrote: > We can also avoid the error by adding `-Dignore.dirt` flag to Maven config as > was suggested by Marky Jackson. No, fix your build process. https://github.com/jenkinsci/gitlab-branch-source-plugin/compare/master...jenkinsci:d

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

Thank Abyudaya. I think maybe the error is caused to some misconfiguration of incrementals. I am also getting an error message in the deploy stage [2019-07-14T15:58:59.299Z] Invalid archive retrieved from Jenkins, perhaps the plugin is not properly incrementalized? Still I haven't been able

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

t was merged the pipeline still failed with the >>> same results. >>> >>> Based on the logs: >>> >>> [2019-07-14T04:05:22.417Z] [ERROR] Make sure git status -s is empty >>> before using -Dset.changelist: [docs/img/gitlab-credentials.png, doc

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

That or figure out if the git status -s is in fact empty On Sunday, July 14, 2019 at 8:53:37 AM UTC-7, Parichay Barpanda wrote: > > We can also avoid the error by adding `-Dignore.dirt` flag to Maven config > as was suggested by Marky Jackson. > > On Sun 14 Jul, 2019, 21:06 Pa

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

We can also avoid the error by adding `-Dignore.dirt` flag to Maven config as was suggested by Marky Jackson. On Sun 14 Jul, 2019, 21:06 Parichay Barpanda, wrote: > I don't think in our code we are optimisation the docs images or making > changes to the docs images. I was thinking the

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

ed with the >> same results. >> >> Based on the logs: >> >> [2019-07-14T04:05:22.417Z] [ERROR] Make sure git status -s is empty >> before using -Dset.changelist: [docs/img/gitlab-credentials.png, docs/img >> /gitlab-section.png, docs/img/gitlab-server.

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

< parichay.barpa...@gmail.com> wrote: > Thanks Mark and Batmat. I am not sure if it was due to #1218 not being > merged. Because soon as it was merged the pipeline still failed with the > same results. > > Based on the logs: > > [2019-07-14T04:05:22.417Z] [ERROR] Make sure git status

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

Thanks Mark and Batmat. I am not sure if it was due to #1218 not being merged. Because soon as it was merged the pipeline still failed with the same results. Based on the logs: [2019-07-14T04:05:22.417Z] [ERROR] Make sure git status -s is empty before using -Dset.changelist: [docs/img/gitlab

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

Also possibly related to the fact https://github.com/jenkins-infra/repository-permissions-updater/pull/1218 was not merged, yet. (Now done). The github field there is used in Incrementals IIRC. Le dim. 14 juil. 2019 à 13:31, Mark Waite a écrit : > That particular error case (` Make sure `

Re: Incrementals error in Jenkins CI for GitLab Branch Source Plugin

That particular error case (` Make sure `git status -s` is empty before using -Dset.changelis `) likely means that some portion of the build is modifying one or more files in the source code during the build process. I believe the incrementals build process wants the output of `git status -s

Incrementals error in Jenkins CI for GitLab Branch Source Plugin

Hi all, GitLab Branch Source Plugin was recently hosted on `jenkinsci` org. But the build is failing on Jenkins CI. I am unable to figure out the error. Can someone help me figure this out? The build information can be found here - https://ci.jenkins.io/blue/organizations/jenkins/Plugins

Re: Facing Error in loading Build Action page

On Thu, May 30, 2019 at 7:52 AM selva vignesh wrote: > No page found 'sidepanel.jelly' for class > io.jenkins.plugins.sample.BuildAction Exception. > > What is `it` in this case? What type does the `getBuild()` method return? Not sure where you are copying this example from exactly,

Re: Facing Error in loading Build Action page

ix this issue >> >> Same Code working for Project Action >> >> *index.jelly* >> >> >> >> >> >> ${it.displayName} >> Build #${it.buildNumber}'s Output: ${it.message} >> Build Start Time : ${it.StartTime} >>

Re: Facing Error in loading Build Action page

roject Action > > *index.jelly* > > > > > > ${it.displayName} > Build #${it.buildNumber}'s Output: ${it.message} > Build Start Time : ${it.StartTime} > > >

Facing Error in loading Build Action page

} ${action} Facing Error in loading page -- 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

Facing Error in loading page

Hi team, I have configured one Build action and later time added one more Build action class and made a old class as pojo class. Now, i am facing * No page found 'sidepanel.jelly' for class io.jenkins.plugins.sample.BuildAction* *Exception*. Even i have configured correctly can anyone let me know

Re: Plugin PR Build failing with out of space error during version control step

Thanks for the quick response! Good to know. On Friday, March 15, 2019 at 2:27:39 PM UTC-7, Baptiste Mathus wrote: > > This isn't your plug-in. > This is an infra issue. > > Seen this morning once, finally not so temporary. > Also seen just a few seconds ago in >

Re: Plugin PR Build failing with out of space error during version control step

This isn't your plug-in. This is an infra issue. Seen this morning once, finally not so temporary. Also seen just a few seconds ago in https://github.com/jenkins-infra/repository-permissions-updater/pull/1060 Adding the infrastructure ml in cc because cannot easily reach IRC from the phone.

Plugin PR Build failing with out of space error during version control step

Here is the most recent iteration of the build that I'm talking about. It fails pretty much instantly. https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgoogle-kubernetes-engine-plugin/detail/PR-36/2/pipeline Hadn't encountered this issue so far on our recent builds. The next two PRs

Re: Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install node and yarn) on project jenkins-war: Could not download Node.js: Got error code 405 from the s

On Mon, Oct 8, 2018 at 5:02 PM Philipp Kunz wrote: > how this is supposed to be working? The build should be downloading something from https://repo.jenkins-ci.org/nodejs-dist/v6.10.2/ to your local Maven repository. According to your logs [DEBUG] (f) nodeDownloadRoot =

Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.4:install-node-and-yarn (install node and yarn) on project jenkins-war: Could not download Node.js: Got error code 405 from the serve

-[INFO] BUILD FAILURE[INFO] - ---[INFO] Total time: 02:58 min[INFO] Finished at: 2018-10-08T18:55:55+02:00[INFO] ----[ERROR] Failed to execute goal com.github.ei

Re: unit test error: java.lang.IllegalAccessError: tried to access method

60) > > Most likely you are using mismatched plugin versions, typically > visible (when using reasonably recent versions of Jenkins) by some > earlier warnings about some plugins being unloadable for dependency > reasons. If your parent POM is set to a reasonably recent version, you >

Re: unit test error: java.lang.IllegalAccessError: tried to access method

some plugins being unloadable for dependency reasons. If your parent POM is set to a reasonably recent version, you should get a more straightforward build error much earlier, in the `validate` phase. -- You received this message because you are subscribed to the Google Groups "Je

unit test error: java.lang.IllegalAccessError: tried to access method

When I run the JUnit test, got an errors, like this: Running in Durability level: MAX_SURVIVABILITY [Pipeline] End of Pipeline java.lang.IllegalAccessError: tried to access method

Re: Error

Hello, Answered there, let's keep the discussion where the issue happens generally. Cheers Le jeu. 17 mai 2018 à 09:13, Rahul Pure <rahulp2...@gmail.com> a écrit : > Hi > > getting this error while apply for pull request to publish the plugin > > > [-pe

Error

Hi getting this error while apply for pull request to publish the plugin [-permissions-updater_PR-700-LYD3MWGHXRV7JB35ISKXIBYKVCKRHAVJ2HUMAAWJKR3IAK6UPXWQ] Running shell script + /home/jenkins/tools/hudson.model.JDK/jdk8/bin/java -DdryRun=true -DdefinitionsDir=/home/jenkins/workspace

Re: [Essentials] (client) Error Telemetry logging: JEP in early draft review

Quick heads-up everyone. So since last email, the proposal got accepted as JEP-304. After a discussion yesterday with Tyler, we discussed a small adjustment to make JSON parsing and evolution more straightforward, making the `exception` field an object instead of a string as it was currently.

Re: [Essentials] Error Telemetry Server API JEP Draft

After defining how we would do the client side of error telemetry logging > > in JEP-304 <https://github.com/jenkinsci/jep/tree/master/jep/304>, I > just > > published a draft of the corresponding server side for review: > > > > https://github.com/batmat/jep/tree

Re: [Essentials] Error Telemetry Server API JEP Draft

(replies inline) On Tue, 08 May 2018, Baptiste Mathus wrote: > Hello everyone, > > After defining how we would do the client side of error telemetry logging > in JEP-304 <https://github.com/jenkinsci/jep/tree/master/jep/304>, I just > published a draft of the corr

[Essentials] Error Telemetry Server API JEP Draft

Hello everyone, After defining how we would do the client side of error telemetry logging in JEP-304 <https://github.com/jenkinsci/jep/tree/master/jep/304>, I just published a draft of the corresponding server side for review: https://github.com/batmat/jep/tree/JENKINS-51140/ C

Re: [Newbie] Declarative Pipeline agent/docker directive causing script.sh not found error

Build') { > steps { > sh 'mvn -B clean verify' > } > } > } > } > > > Error: > > Started by user Calvin > Running in Durability level: MAX_SURVIVABILITY > [Pipeline] node > Running on slave_0 in /ho

[Newbie] Declarative Pipeline agent/docker directive causing script.sh not found error

New Item > Pipeline > Pipeline script pipeline { agent { docker 'maven:3-alpine' } stages { stage('Example Build') { steps { sh 'mvn -B clean verify' } } } } Error: Started by user Calvin Running in Durability

Re: [Essentials] (client) Error Telemetry logging: JEP in early draft review

Seems reasonable. The implementation separates JSON records with a newline. This is not apparent from the JEP; it would be nice to mention it, so that readers do not wonder whether you are using some kind of streaming JSON parser (which is unnecessary when each line is a well-formed JSON

[Essentials] (client) Error Telemetry logging: JEP in early draft review

Hello everyone, So as a followup on the recent discussions around telemetry logging for Essentials, I've drafted a JEP on this matter I would love to get feedback on: https://github.com/batmat/jep/tree/JENKINS-49805/jep/ Thanks! -- Baptiste -- You received this message because you are

Re: [Essentials] Error Telemetry logging: how to do it (was: Re: Thoughts on sending error telemetry for Jenkins Essentials)

So, to clarify: *I would like to keep this thread dedicated to the pros and cons to either write a `jenkins-module` as advised by Jesse, or a Jenkins plugin to host the classes that this will require*, whatever the implementation paths we choose. For instance, I think I'll also need to write a

Re: [Essentials] Error Telemetry logging: how to do it (was: Re: Thoughts on sending error telemetry for Jenkins Essentials)

2018-04-02 15:27 GMT+02:00 Jesse Glick : > On Fri, Mar 30, 2018 at 11:15 AM, Baptiste Mathus wrote: > > SocketHandler is unusable for real life IMO: any loss of connection will > not be reconnected. > > So we need to develop something that *will* reconnect

[Essentials] Error Telemetry logging: how to do it (was: Re: Thoughts on sending error telemetry for Jenkins Essentials)

Hello, (Changing the subject also because I don't think it's strictly necessary for people to read the previous thread to be able to provide help/feedback here). I've started working on https://issues.jenkins-ci.org/browse/JENKINS-49805, and the tests I've done so far led me to see two possible

Re: Thoughts on sending error telemetry for Jenkins Essentials

I just wanted to make sure I shared an update on this thread. I have filed the following ticket (https://issues.jenkins-ci.org/browse/JENKINS-49805) to capture some of the prototyping work necessary here. I expect we'll have a draft JEP coming up after the prototyping work is done. Thanks for

Re: Thoughts on sending error telemetry for Jenkins Essentials

(replies inline) On Wed, 21 Feb 2018, Robert Sandell wrote: > Or if you've ever seen one of these panels at the checkout counter in a > store somewhere > > http://customerstrategy.net/customer-experience-improvement-systems-part-1/ Heh, I've seen those outside bathrooms, which I find kind of

Re: Thoughts on sending error telemetry for Jenkins Essentials

Or if you've ever seen one of these panels at the checkout counter in a store somewhere http://customerstrategy.net/customer-experience-improvement-systems-part-1/ 2018-02-21 17:14 GMT+01:00 Robert Sandell : > How do you feel about Jenkins today?  > > :) > > 2018-02-21

Re: Thoughts on sending error telemetry for Jenkins Essentials

How do you feel about Jenkins today?  :) 2018-02-21 16:58 GMT+01:00 Jesse Glick : > On Wed, Feb 21, 2018 at 9:44 AM, R. Tyler Croy > wrote: > >> How about also a less automated /form/ in the Jenkins UI itself, to be > used by > >> human in case

Re: Thoughts on sending error telemetry for Jenkins Essentials

(replies inline) On Sat, 17 Feb 2018, Baptiste Mathus wrote: > Le 16 févr. 2018 15:51, "R. Tyler Croy" <[1]ty...@monkeypox.org> a écrit : > > > One of the necessary details, in my opinion, to make Jenkins Essentials > [0] > successful is provid

Re: Thoughts on sending error telemetry for Jenkins Essentials

Le 16 févr. 2018 15:51, "R. Tyler Croy" <ty...@monkeypox.org> a écrit : One of the necessary details, in my opinion, to make Jenkins Essentials [0] successful is providing near-real-time error telemetry. Coupled with the "Evergreen" distribution system [1], er

Re: Thoughts on sending error telemetry for Jenkins Essentials

(replies inline) On Fri, 16 Feb 2018, Jesse Glick wrote: > On Fri, Feb 16, 2018 at 9:51 AM, R. Tyler Croy <ty...@monkeypox.org> wrote: > > I currently define "error telemetry" to include: > > > > * Uncaught exceptions which cause the Evil Jenkins

Re: Thoughts on sending error telemetry for Jenkins Essentials

On Fri, Feb 16, 2018 at 9:51 AM, R. Tyler Croy <ty...@monkeypox.org> wrote: > I currently define "error telemetry" to include: > > * Uncaught exceptions which cause the Evil Jenkins 500 page > * Logged ERROR messages, with or without exceptions Absolutely.

Re: Thoughts on sending error telemetry for Jenkins Essentials

it in JDK_HOME/jre/lib/logging.properties in the container. That way you can get the error logs all the way from jetty startup to the end. /B 2018-02-16 15:51 GMT+01:00 R. Tyler Croy <ty...@monkeypox.org>: > > One of the necessary details, in my opinion, to make Jenkins Essentials [0]

Thoughts on sending error telemetry for Jenkins Essentials

One of the necessary details, in my opinion, to make Jenkins Essentials [0] successful is providing near-real-time error telemetry. Coupled with the "Evergreen" distribution system [1], error telemetry "post-deploy" will be absolutely crucial to determine whether or not we

error on gstring during execution of jenkins script with shared library

Hi all, I have a shared library that extends the pipeline. Inside of my class I have a variable that is a Gstring. If I call a method after this variable, the Jenkinsfile produces an error when running class SlackNotifierImpl implements SlackNotifier, Serializable { final def

Re: Access denied error on repo.jenkins-ci.org attempting to publish a plugin.

> On 25. Jan 2018, at 13:13, dave.dresser.c...@gmail.com wrote: > > Yes, we have access and thanks! I reset the email address to that one. Request a password reset to get the current one, and configure Maven to use those Artifactory credentials. Upload should then work. -- You received this

Re: Access denied error on repo.jenkins-ci.org attempting to publish a plugin.

Yes, we have access and thanks! On Wednesday, January 24, 2018 at 5:57:35 PM UTC-5, Daniel Beck wrote: > > > > On 24. Jan 2018, at 20:33, dave.dre...@gmail.com wrote: > > > > Thanks for you help. We are still confused here. Somehow we have two > ID's cpwr_jenkins and cpwr_jenkins_plugin.

Re: Access denied error on repo.jenkins-ci.org attempting to publish a plugin.

> On 24. Jan 2018, at 20:33, dave.dresser.c...@gmail.com wrote: > > Thanks for you help. We are still confused here. Somehow we have two ID's > cpwr_jenkins and cpwr_jenkins_plugin. I'm not completely clear on the > history due to changing personnel. Let's start with the id cpwr_jenkins.

Re: Access denied error on repo.jenkins-ci.org attempting to publish a plugin.

'cpwr_jenkins' is allowed to upload this artifact per > https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-compuware-common-configuration.yml > > > > We have searched this mailing list for this error and through google and > there seem t

Re: Access denied error on repo.jenkins-ci.org attempting to publish a plugin.

' is allowed to upload this artifact per https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-compuware-common-configuration.yml > We have searched this mailing list for this error and through google and > there seem to be many different root causes for

Access denied error on repo.jenkins-ci.org attempting to publish a plugin.

We are having troubling publishing a new version of one of our plugins. Another person on my team who was able to publish a change in early January cannot publish and I also tried to publish and get the same error: [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ compuware

Re: Calling a DSL extension resulting in error

> On 5. Jan 2018, at 22:01, Rijo Simon <r...@rijosimon.com> wrote: > > On adding node block I get the error: java.lang.NoSuchMethodError: No such > DSL method 'node' found among steps Per https://jenkins.io/doc/pipeline/steps/ the 'node' step is provided by the 'Pipeline: N

Re: Calling a DSL extension resulting in error

This is my pipeline script: node{ step ([$class: 'GoBuildSandboxBuilder', product: 'gobuild_tiny_target', branch: 'main', changeset: 'False']) } On Friday, January 5, 2018 at 1:01:16 PM UTC-8, Rijo Simon wrote: > > On adding node block I get the error: java.lang.NoSuchMetho

Re: Calling a DSL extension resulting in error

On adding node block I get the error: java.lang.NoSuchMethodError: No such DSL method 'node' found among steps On Friday, January 5, 2018 at 12:37:30 PM UTC-8, Jesse Glick wrote: > > On Fri, Jan 5, 2018 at 3:30 PM, Rijo Simon <ri...@rijosimon.com

Re: Calling a DSL extension resulting in error

On Fri, Jan 5, 2018 at 3:30 PM, Rijo Simon wrote: > org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: > Required context class hudson.FilePath is missing `step` may only be called inside `node`. -- You received this message because you are subscribed to

Re: Calling a DSL extension resulting in error

After install workflow-basic-steps, I get the following stacktrace: [Pipeline] stage[Pipeline] { (gobuild-stage)[Pipeline] stepRequired context class hudson.FilePath is missing[Pipeline] }[Pipeline] // stage[Pipeline] End of

Re: Calling a DSL extension resulting in error

On Fri, Jan 5, 2018 at 2:36 PM, Rijo Simon wrote: > java.lang.NoSuchMethodError: No such DSL method 'step' found among steps Install the `workflow-basic-steps` plugin. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.

Re: Calling a DSL extension resulting in error

', where: 'anywhere', when: 'anytime']) This returned "java.lang.NoSuchMethodError: No such DSL method 'step' found among steps" error. Then I edited my script to look like this: stage{ steps ([$class: 'ForgetBuilder', what: 'everything', where: 'anywhere', when: 'anytime']) } Whic

Re: Calling a DSL extension resulting in error

> On 3. Jan 2018, at 22:37, Rijo Simon wrote: > > so that this BuildStep plugin can be called from a pipeline script. Please > guide me on how to achieve this. https://jenkins.io/doc/developer/plugin-development/pipeline-integration/ should have everything you need. --

Re: Calling a DSL extension resulting in error

ok so I think I was wrong in using gobuild method within the groovy file, but I still think this issue is relevant to Jenkins developer group. This plugin I am developing basically calls and maintains some command line instructions that is implemented as a class that extends to Builder and

Re: Calling a DSL extension resulting in error

On Wed, Jan 3, 2018 at 1:12 PM, Rijo Simon wrote: >gobuild product: "${gobuild_params.product ?: 'copytest64'}", branch: > "${gobuild_params.branch ?: 'stage'}", changeset: > "${gobuild_params.changeset ?: 'latest'}", buildType: > "${gobuild_params.buildType ?: 'beta'}"

Re: Calling a DSL extension resulting in error

On Wed, Jan 3, 2018 at 1:10 PM, Rijo Simon wrote: > What is the reason you advice to not to package DSLs in plugins? Because you can already share libraries across instances, much more easily, and without drawbacks such as forcing a single version of the library upon every

Re: Calling a DSL extension resulting in error

k Making it a >> plugin). >> >> I would strongly advise you not to use the builder pattern >> (`Closure.DELEGATE_FIRST` etc.) shown in that blog post and the source >> of the error you saw. Use plain function arguments or a `Map`-valued >> parameter. >&

Re: Calling a DSL extension resulting in error

/dsl-plugins/ (Check Making it a > plugin). > > I would strongly advise you not to use the builder pattern > (`Closure.DELEGATE_FIRST` etc.) shown in that blog post and the source > of the error you saw. Use plain function arguments or a `Map`-valued > parameter. > > I would

Re: Calling a DSL extension resulting in error

lder pattern (`Closure.DELEGATE_FIRST` etc.) shown in that blog post and the source of the error you saw. Use plain function arguments or a `Map`-valued parameter. I would also advise you not to package DSLs in plugins. You can use @Library('github.com/myacct/myrepo') _ to distribute a library directly—i

Re: Calling a DSL extension resulting in error

The "I have a created a DSL plugin" at the start of the mail is the hint I am looking at... now it may be a script approval issue, but that may actually instead point to a question as to how to annotate a newly developed extension to mark the script safe methods... or it may be plain script

Re: Calling a DSL extension resulting in error

Sorry if I misunderstood this question, but I though that particular stacktrace was related to the usage of the script approval process. Cheers -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop

Re: Calling a DSL extension resulting in error

On Wed 3 Jan 2018 at 08:24, Victor Martinez wrote: > Please ask to the jenkinsci-users mailing list: > https://jenkins.io/mailing-lists/ > The poster is *clearly* asking a question about plugin development. This is the correct list for that. The users list is

Re: Calling a DSL extension resulting in error

Please ask to the jenkinsci-users mailing list: https://jenkins.io/mailing-lists/ -- 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

Calling a DSL extension resulting in error

I have a created a DSL plugin as documented at the end of this link: https://jenkins.io/blog/2016/04/21/dsl-plugins/ (Check Making it a plugin). I however get the following error when I call the DSL command: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts

Re: No Class found error while running Test Case for Jenkins plugin

Is there a need to explicitly specify the Jenkins Test Harness version in your pom.xml? I'd guess there is a version mismatch in the build due to that. So I would recommend to start from removing "2.27 " and re-running the build. вторник, 19 декабря 2017 г., 21:22:23 UTC+1 пользователь chirag

No Class found error while running Test Case for Jenkins plugin

Hi, I am developing test cases for one of my plugin. Below is snipped code of test case: > > JenkinsRule.WebClient webClient=rule.createWebClient(); >FreeStyleProject p = (FreeStyleProject) rule.jenkins.getItem( > "WebApp"); > > HtmlPage page=

Re: Unable to upload snapshot of teamconcert-plugin 401 Unauthorized error

It appeared to be an intermittent issue. I was able to upload a snapshot after a few hours. Thanks. On Tuesday, November 21, 2017 at 8:06:09 PM UTC+5:30, Daniel Beck wrote: > > > > On 21. Nov 2017, at 15:27, Lakshmi Narasimhan Vaikuntam < > vaikuntam@gmail.com > wrote: > > > > Any reasons

Re: Unable to upload snapshot of teamconcert-plugin 401 Unauthorized error

Hi Daniel Thanks. It appeared to an intermittent issue. I tried after a few hours and was able to upload a snapshot. On Tuesday, November 21, 2017 at 8:06:09 PM UTC+5:30, Daniel Beck wrote: > > > > On 21. Nov 2017, at 15:27, Lakshmi Narasimhan Vaikuntam < > vaikuntam@gmail.com > wrote: > >

Re: Unable to upload snapshot of teamconcert-plugin 401 Unauthorized error

> On 21. Nov 2017, at 15:27, Lakshmi Narasimhan Vaikuntam > wrote: > > Any reasons for this to happen? Please see https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues -- You received this message because you are

Unable to upload snapshot of teamconcert-plugin 401 Unauthorized error

I am trying to create a snapshot from the latest commit to teamconcert-plugin (https://github.com/jenkinsci/teamconcert-plugin). I get the following exception. Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Return code is: 401, ReasonPhrase: Unauthorized. I am able

Unable to upload snapshot of teamconcert-plugin 401 Unauthorized error

I am trying to create a snapshot from the latest commit to teamconcert-plugin (https://github.com/jenkinsci/teamconcert-plugin). I get the following exception. Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Return code is: 401, ReasonPhrase: Unauthorized. Any

Re: Debugging HtmlUnit: FailingHttpStatusCodeException 500 Server Error

est In my case I haven't mocked out getDescriptor(), so it returns nullptr and the server dies with NullPointerException Thanks for getting me on track again! On Thursday, September 28, 2017 at 5:11:36 AM UTC-4, Robert Sandell wrote: > > A 500 server error is an indication that an exce

Re: Debugging HtmlUnit: FailingHttpStatusCodeException 500 Server Error

A 500 server error is an indication that an exception was thrown in the backend when the http request was made. You should see another stacktrace in the log just before the FailingHttpstatusCodeException. /B 2017-09-27 22:53 GMT+02:00 'Alexandra Goultiaeva' via Jenkins Developers < jenkinsci-

Debugging HtmlUnit: FailingHttpStatusCodeException 500 Server Error

e-storage-plugin/tree/brokenUnitTest>. I've added the roundtrip test ClassicUploadStepTest <https://github.com/agoulti/google-storage-plugin/blob/brokenUnitTest/src/test/java/com/google/jenkins/plugins/storage/ClassicUploadStepTest.java> When I run the test, I get t

Re: Error in Eclipse Compiling

; > Mark, Thank you for your time and your help. > > > > Mark D > > > > *From:* jenkin...@googlegroups.com [mailto: > jenkin...@googlegroups.com ] *On Behalf Of *Mark Waite > *Sent:* Friday, September 22, 2017 12:47 PM > *To:* jenkin...@googlegrou

<    1   2   3   4   5   >