[JIRA] (JENKINS-61481) No signature of method: groovy.util.Node.div() when use sandbox
Title: Message Title
Jose Luis Rivero created an issue
Jenkins / JENKINS-61481
No signature of method: groovy.util.Node.div() when use sandbox
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2020-03-14 20:38
Environment:
Jenkins version 2.204.4 Job-dsl version 1.77
Priority:
Minor
Reporter:
Jose Luis Rivero
When running the following example using the sandbox option:
job('test')
{
scm {
hg("http://test_repo") {
configure { node ->
node / browser(class: 'hudson.plugins.mercurial.browser.BitBucket') / "url" << "test"
}
}
}
}
I get the following error:
ERROR: (script, line 6) No signature of method: groovy.util.Node.div() is applicable for argument types: (groovy.util.Node) values: [browser[attributes={class=hudson.plugins.mercurial.browser.BitBucket}; value=[]]]
Possible solutions: is(java.lang.Object), wait(), find(), dump(), any(), wait(long)
The problem is gone when the sandbox is disabled or the piece of code works fine when run in http://job-dsl.herokuapp.com/.
[JIRA] (JENKINS-42823) False positive with msbuild parser
Title: Message Title
Jose Luis Rivero updated an issue
Jenkins / JENKINS-42823
False positive with msbuild parser
Change By:
Jose Luis Rivero
Hello:I've found a false positive using the Msbuild Warning parser when the output of the Jenkins job display the following string:{code:none}3: Known information: {code}Note that there must be a final space at the end: '3: Known information: ' (without single quotes) . If you remove the final space the warning is gone. A minimal test case was implemented here: http://build.osrfoundation.org/job/_test_bug_msbuild_ignition_transport/29It generates the following backtrace:{code:java}01 Copying the source file '3' from the workspace to the build folder '33.tmp' on the Jenkins master failed.02 Seems that the path is relative, however an absolute path is required when copying the sources.03 Is the file '3' contained more than once in your workspace?04 Is the file '3' a valid filename?05 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]/3'06 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace/3'07 java.io.IOException: Failed to copy 3 to /var/lib/jenkins/jobs/_test_bug_msbuild_ignition_transport/builds/29/workspace-files/33.tmp08 at hudson.FilePath.copyTo(FilePath.java:1984)09 at hudson.plugins.analysis.util.Files.copyFilesWithAnnotationsToBuildFolder(Files.java:80)10 at hudson.plugins.analysis.core.HealthAwareRecorder.copyFilesWithAnnotationsToBuildFolder(HealthAwareRecorder.java:348)11 at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:89)12 at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:295)13 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78)14 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)15 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)16 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)17 at hudson.model.Build$BuildExecution.post2(Build.java:185)18 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)19 at hudson.model.Run.execute(Run.java:1753)20 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)21 at hudson.model.ResourceController.execute(ResourceController.java:98)22 at hudson.model.Executor.run(Executor.java:404)23 Caused by: java.io.IOException: remote file operation failed: 3 at hudson.remoting.Channel@7a5c4d93:Channel to /70.35.50.58: java.io.FileNotFoundException: 3 (No such file or directory)24 at hudson.FilePath.act(FilePath.java:992)25 at hudson.FilePath.act(FilePath.java:974)26 at hudson.FilePath.copyTo(FilePath.java:2005)27 at hudson.FilePath.copyTo(FilePath.java:1981)28 ... 14 more29 Caused by: java.io.FileNotFoundException: 3 (No such file or directory)30 at java.io.FileInputStream.open(Native Method){code}Thanks.
[JIRA] (JENKINS-42823) False positive with msbuild parser
Title: Message Title Jose Luis Rivero created an issue Jenkins / JENKINS-42823 False positive with msbuild parser Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2017/Mar/15 11:10 PM Environment: Jenkins version 2.32.2 warning-plugins version: 4.60 Priority: Minor Reporter: Jose Luis Rivero Hello: I've found a false positive using the Msbuild Warning parser when the output of the Jenkins job display the following string: 3: Known information: Note that there must a final space at the end: '3: Known information: ' . If you remove the final space the warning is gone. A minimal test case was implemented here: http://build.osrfoundation.org/job/_test_bug_msbuild_ignition_transport/29 It generates the following backtrace: 01 Copying the source file '3' from the workspace to the build folder '33.tmp' on the Jenkins master failed. 02 Seems that the path is relative, however an absolute path is required when copying the sources. 03 Is the file '3' contained more than once in your workspace? 04 Is the file '3' a valid filename? 05 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]/3' 06 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace/3' 07
[JIRA] [script-security-plugin] (JENKINS-35352) unclassified new org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified field org.jenkinsci.plugins.workflow.support.steps.b
Title: Message Title Jose Luis Rivero created an issue Jenkins / JENKINS-35352 unclassified new org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified field org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper Issue Type: Bug Assignee: Jesse Glick Components: script-security-plugin Created: 2016/Jun/03 11:08 PM Labels: workflow Priority: Minor Reporter: Jose Luis Rivero I'm not sure if this can be consider a bug but all the information I found using the exception name refers to classes not supported in the sandbox that should be so this case could be the another case. I did not find a way to allow this org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified field org.jenkinsci.plugins.workflow.support.steps.build.RunWrapper result at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.unclassifiedField(SandboxInterceptor.java:367) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onSetProperty(SandboxInterceptor.java:217) at org.kohsuke.groovy.sandbox.impl.Checker$5.call(Checker.java:297) at org.kohsuke.groovy.sandbox.impl.Checker.checkedSetProperty(Checker.java:294) at
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32548) Support for mercurial repositories
Title: Message Title
Jose Luis Rivero edited a comment on JENKINS-32548
Re: Support for mercurial repositories
Build the current master branch of the repo and [ tested in Jenkins 1.625.3 ](http://build.osrfoundation.org/view/All/job/sdformat-ci-pr_any-trusty-amd64_test_status/25/console) , fails with this backtrace:{code:java}Bitbucket notify on start failed: nulljava.lang.NullPointerException at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.createBuildStatusResourceFromBuild(BitbucketBuildStatusNotifier.java:169) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.prebuild(BitbucketBuildStatusNotifier.java:78) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:835) at hudson.model.Build$BuildExecution.doRun(Build.java:144) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32548) Support for mercurial repositories
Title: Message Title
Jose Luis Rivero edited a comment on JENKINS-32548
Re: Support for mercurial repositories
Build the current master branch of the repo and [tested in Jenkins 1.625.3 ]( | http://build.osrfoundation.org/view/All/job/sdformat-ci-pr_any-trusty-amd64_test_status/25/console ) ] , fails with this backtrace:{code:java}Bitbucket notify on start failed: nulljava.lang.NullPointerException at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.createBuildStatusResourceFromBuild(BitbucketBuildStatusNotifier.java:169) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.prebuild(BitbucketBuildStatusNotifier.java:78) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:835) at hudson.model.Build$BuildExecution.doRun(Build.java:144) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-build-status-notifier-plugin] (JENKINS-32548) Support for mercurial repositories
Title: Message Title Jose Luis Rivero commented on JENKINS-32548 Re: Support for mercurial repositories Build the current master branch of the repo and tested in Jenkins 1.625.3, fails with this backtrace: Bitbucket notify on start failed: null java.lang.NullPointerException at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.createBuildStatusResourceFromBuild(BitbucketBuildStatusNotifier.java:169) at org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier.prebuild(BitbucketBuildStatusNotifier.java:78) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:835) at hudson.model.Build$BuildExecution.doRun(Build.java:144) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ansicolor-plugin] (JENKINS-29090) Too many span labels for the same line
Title: Message Title Jose Luis Rivero created an issue Jenkins / JENKINS-29090 Too many span labels for the same line Issue Type: Improvement Assignee: Unassigned Components: ansicolor-plugin Created: 25/Jun/15 10:59 PM Environment: Ansi Color Plugin version 0.4.1 Labels: performance Priority: Minor Reporter: Jose Luis Rivero The Plugin seems to generate a span html tag for several parts of the same line, having all the line the same colour. While this is not a problem on small builds, in large projects the console output can increase considerably (up to 100Mb in ours) and the response time to check the whole log is also affected notably. An example can be checked at: http://build.osrfoundation.org/job/gazebo-default-devel-trusty-amd64-gpu-nvidia/lastSuccessfulBuild/consoleFull For example (all the line is in red):
