[JIRA] (JENKINS-50369) Missing git environment variable
Title: Message Title Mark Waite commented on JENKINS-50369 Re: Missing git environment variable Please provide more details so that others can duplicate the bug. I attempted to duplicate the bug with the following steps: Create a freestyle job that uses a git repository and reports the environment variables after checkout Run that freestyle job Confirm the environment variables are reported More details are in the commit message for the job that performs that check. I see the environment variables output for my job as: GIT_AUTHOR_EMAIL=mwa...@mark-pc2.markwaite.net GIT_AUTHOR_NAME=Jenkins Docker User GIT_BRANCH=origin/master GIT_COMMIT=42fbc34cc227fd1514710d54e790cb6489c20282 GIT_COMMITTER_EMAIL=mwa...@mark-pc2.markwaite.net GIT_COMMITTER_NAME=Jenkins Docker User GIT_PREVIOUS_COMMIT=42fbc34cc227fd1514710d54e790cb6489c20282 GIT_URL=https://github.com/jenkinsci/git-client-plugin Please provide more details to duplicate the problem you're seeing. I don't know how the job looks after DSL generates a freestyle job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50369) Missing git environment variable
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-50369 Missing git environment variable Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50383) iOS fastline build failed
Title: Message Title gang li created an issue Jenkins / JENKINS-50383 iOS fastline build failed Issue Type: Bug Assignee: Oleg Nenashev Attachments: HTHang-HTHang.log Components: _unsorted Created: 2018-03-24 03:49 Environment: Jenkins 2.107.1, macOS High Sierra Labels: build plugin Priority: Minor Reporter: gang li The following build commands failed: CompileC /Users/Shared/Jenkins/Library/Developer/Xcode/DerivedData/HTHang-gsetiuztxebqzyfhsteqemagehuo/Build/Intermediates.noindex/ArchiveIntermediates/HTHang/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/AliyunOSSiOS.build/Objects-normal/armv7/OSSHttpResponseParser.o AliyunOSSiOS/AliyunOSSSDK/OSSHttpResponseParser.m normal armv7 objective-c com.apple.compilers.llvm.clang.1_0.compiler (1 failure)
[JIRA] (JENKINS-50382) build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project
Title: Message Title Kyle L commented on JENKINS-50382 Re: build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project Gavin Mogan Thanks. I did both for good measure. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50382) build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project
Title: Message Title Gavin Mogan commented on JENKINS-50382 Re: build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project Hi Kyle L, I reassigned the ticket to the current developer. You'll probably get faster response to talk to support though. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50382) build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project
Title: Message Title Gavin Mogan assigned an issue to Yeh Fang Jenkins / JENKINS-50382 build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project Change By: Gavin Mogan Assignee: Gavin Mogan Yeh Fang Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50382) build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project
Title: Message Title Kyle L created an issue Jenkins / JENKINS-50382 build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project Issue Type: Bug Assignee: Gavin Mogan Attachments: jenkins.log Components: sauce-ondemand-plugin Created: 2018-03-24 03:30 Environment: Jenkins ver. 2.107.1 sauce-ondemand-plugin 1.172 Labels: dataloss Priority: Major Reporter: Kyle L I've attached the Jenkins log file. This error occurs for any job that is a multi-configuration project that uses the "Sauce Labs WebDriver tests" axis for the configuration matrix. The build.xml file for the axis configurations will save, but the build.xml file for the base job will not causing the builds to fail to stick around in the build history. Note: I reproduced this on a clean Jenkins instance where it was the minimal plugins past install and only the job used to reproduce this. This has also been happening on our main Jenkins instance stemming since at least Jenkins 2.60 that I can remember. Our main instance is currently running 2.110 and it's still happening. This has been around for multiple sauce ondemand plugin releases too.
[JIRA] (JENKINS-50381) ECS plugin fails to use label expression
Title: Message Title Dmytro Kryvenko created an issue Jenkins / JENKINS-50381 ECS plugin fails to use label _expression_ Issue Type: Bug Assignee: Jan Roehrich Components: amazon-ecs-plugin Created: 2018-03-24 02:39 Environment: Tested on 2.107.1 and 2.89.2. Priority: Blocker Reporter: Dmytro Kryvenko When I have multiple images defined in the same cluster I want to differentiate them by labels, like 'aws&' or 'aws&'. Unfortunately it seems this plugin fails to handle plugin expressions, see the error stack trace below: Mar 23, 2018 10:03:28 PM WARNING hudson.slaves.NodeProvisioner$2 run Unexpected exception encountered while provisioning agent ECS Slave aws linux foo bar java.lang.ClassCastException: hudson.model.labels.LabelExpression$And cannot be cast to hudson.model.labels.LabelAtom at jenkins.model.Jenkins.getLabelAtom(Jenkins.java:1978) at hudson.model.Label.parse(Label.java:592) at hudson.model.Node.getAssignedLabels(Node.java:300) at hudson.model.Slave.(Slave.java:196) at hudson.slaves.AbstractCloudSlave.(AbstractCloudSlave.java:51) at com.cloudbees.jenkins.plugins.amazonecs.ECSSlave.(ECSSlave.java:95) at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:243) at com.cloudbees.jenkins.plugins.amazonecs.ECSCloud$ProvisioningCallback.call(ECSCloud.java:221) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at
[JIRA] (JENKINS-50347) Design and create instance registration process
Title: Message Title R. Tyler Croy started work on JENKINS-50347 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-36459) Inconsistency in Parameterized Remote Trigger Plugin options via UI & DSL API
Title: Message Title Greg Ferrell commented on JENKINS-36459 Re: Inconsistency in Parameterized Remote Trigger Plugin options via UI & DSL API Hi, 2018 and this is still a major issue. There is literally no way to enable this checkbox except manually. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-48525) Perforce plugin doesn't sync
Title: Message Title Maciej Piechotka edited a comment on JENKINS-48525 Re: Perforce plugin doesn't sync * I started reproducing it with non-parallel sync * How is this 'Not a defect'? I'm assuming it was closed by accident as no comment was made and reopen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-48525) Perforce plugin doesn't sync
Title: Message Title Maciej Piechotka reopened an issue Jenkins / JENKINS-48525 Perforce plugin doesn't sync Change By: Maciej Piechotka Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-48525) Perforce plugin doesn't sync
Title: Message Title Maciej Piechotka commented on JENKINS-48525 Re: Perforce plugin doesn't sync I started reproducing it with non-parallel sync How is this 'Not a defect'? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47932) VSTest Runner plugin is not shown in manage jenkins nor jenkins job configure
Title: Message Title Matt Sheppard commented on JENKINS-47932 Re: VSTest Runner plugin is not shown in manage jenkins nor jenkins job configure Any word on this? Every time we run plugin updates inevitably someone forgets that this has been broken for months and ends up breaking all of our pipelines all over again we're going to have to migrate from this plugin soon in order to avoid logistical nightmares... version 1.0.4 = "All good" version 1.0.5 = "headache" Exact same symptoms as previous commentors... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50223) Pipeline Jenkins master ran out of Java Metaspace
Title: Message Title
Mike Kozell commented on JENKINS-50223
Re: Pipeline Jenkins master ran out of Java Metaspace
We are able to reproduce the memory leak with two examples that is not specific to our code. In both examples and our potential workaround, the Jenkins jobs were all successful and the output in the console log was the same. The classes remained in the GC.class_stats query when using the examples and didn't when using the work around. Abstract Animal class Concrete Lion class extends Animal Example 1 We create a custom pipeline step and pass in an instantiated extended abstract object. The issue occurs when we use "runIdentify(AbstractObject)"
runZoo.groovy
def call() {
node {
def myLion = new Lion()
myLion.noise = "Roar"
myLion.sound(steps,myLion.noise)
runIdentify(myLion)
}
runIdentify.groovy
def call(Animal animal) {
if (animal.noise.toLowerCase().contains('roar')) {
println('This must be a Lion')
} else {
println('NOT a Lion')
}
}
Example 2 We instantiate an extended abstract object and pass it into a constructor object. The issue occurs when use "new Identity(AbstractObject)" to create the new object.
runZoo.groovy
def call() {
node {
def myLion = new Lion()
myLion.noise = "Roar"
myLion.sound(steps,myLion.noise)
new Identity(steps,myLion)
}
}
Identity.groovy
class Identity implements Serializable {
Identity(DSL steps, Animal animal) {
if (animal.noise.toLowerCase().contains('roar')) {
steps.echo('This must be a Lion')
} else {
steps.echo('NOT a Lion')
}
}
}
Work Around We were able to work around the issue by adding a new method to the abstract or concrete class.
runZoo.groovy
def call() {
node {
def myLion = new Lion()
myLion.noise = "Roar"
myLion.sound(steps,myLion.noise)
myLion.identifyAnimal(steps)
}
}
def
[JIRA] (JENKINS-50291) Customize where AsyncPeriodicWork are logged
Title: Message Title Baptiste Mathus updated JENKINS-50291 Jenkins / JENKINS-50291 Customize where AsyncPeriodicWork are logged Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-44981) Developer can see node steps within the step listing
Title: Message Title Damien Jiang commented on JENKINS-44981 Re: Developer can see node steps within the step listing Hi, I noticed this has been in progress for many months; is there a projected release date for i t? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-44981) Developer can see node steps within the step listing
Title: Message Title Damien Jiang edited a comment on JENKINS-44981 Re: Developer can see node steps within the step listing Hi, I noticed this has been in progress for many months; is there a projected release date for i t it ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50380) pipeline using shared library failed after upgrading Jenkins to 2.89.4.2
Title: Message Title Ronnie Zhou updated an issue Jenkins / JENKINS-50380 pipeline using shared library failed after upgrading Jenkins to 2.89.4.2 Change By: Ronnie Zhou Environment: Jenkins 2.89.4.2Script Security 1. 29 39 Pipeline 2.5 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50380) pipeline using shared library failed after upgrading Jenkins to 2.89.4.2
Title: Message Title
Ronnie Zhou updated an issue
Jenkins / JENKINS-50380
pipeline using shared library failed after upgrading Jenkins to 2.89.4.2
Change By:
Ronnie Zhou
Summary:
pipeline using shared library fail failed after upgrading Jenkins to 2.89 .4.2
Pipeline job fails after upgrading Jenkins from 2.32.1.1 to 2.89.4.2. The following error is returned although Script approval list is empty and the following error is returned :{code:java}org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified new common.EnvsToBuild common.Env at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onNewInstance(SandboxInterceptor.java:144) at org.kohsuke.groovy.sandbox.impl.Checker$14.call(Checker.java:580) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCast(Checker.java:585) at org.kohsuke.groovy.sandbox.impl.Checker$checkedCast.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:188) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onStaticCall(GroovyInterceptor.java:35) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:158) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:186) at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:190) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:97) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript:5) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor224.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at
[JIRA] (JENKINS-50380) pipeline using shared library fail upgrading Jenkins to 2.89
Title: Message Title
Ronnie Zhou updated an issue
Jenkins / JENKINS-50380
pipeline using shared library fail upgrading Jenkins to 2.89
Change By:
Ronnie Zhou
Pipeline job fails after upgrading Jenkins from 2.32.1.1 to 2.89.4.2. Script approval list is empty and the following error is returned: {code:java} org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified new common.EnvsToBuild common.Env at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onNewInstance(SandboxInterceptor.java:144) at org.kohsuke.groovy.sandbox.impl.Checker$14.call(Checker.java:580) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCast(Checker.java:585) at org.kohsuke.groovy.sandbox.impl.Checker$checkedCast.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:188) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onStaticCall(GroovyInterceptor.java:35) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:158) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:186) at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:190) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:97) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript:5) at ___cps __cps . transform___ transform__ (Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor224.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:19) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:35) at
[JIRA] (JENKINS-50380) pipeline using shared library fail upgrading Jenkins to 2.89
Title: Message Title Ronnie Zhou created an issue Jenkins / JENKINS-50380 pipeline using shared library fail upgrading Jenkins to 2.89 Issue Type: Bug Assignee: Andrew Bayer Components: pipeline Created: 2018-03-23 21:03 Environment: Jenkins 2.89.4.2 Script Security 1.29 Pipeline 2.5 Labels: pipeline Priority: Minor Reporter: Ronnie Zhou Pipeline job fails after upgrading Jenkins from 2.32.1.1 to 2.89.4.2. Script approval list is empty and the following error is returned: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified new common.EnvsToBuild common.Env at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onNewInstance(SandboxInterceptor.java:144) at org.kohsuke.groovy.sandbox.impl.Checker$14.call(Checker.java:580) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCast(Checker.java:585) at org.kohsuke.groovy.sandbox.impl.Checker$checkedCast.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:188) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onStaticCall(GroovyInterceptor.java:35) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:158) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:186) at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:190) at
[JIRA] (JENKINS-50379) Jenkins kills long running sh script with no output
Title: Message Title Evan Ward created an issue Jenkins / JENKINS-50379 Jenkins kills long running sh script with no output Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2018-03-23 19:53 Environment: Jenkins ver. 2.107.1 on CentOS 7 Priority: Minor Reporter: Evan Ward I have a Jenkins pipeline that runs a shell script that takes about 5 minutes and generates no output. The job fails and I'm seeing the following in the output: wrapper script does not seem to be touching the log file in /home/jenkins/workspace/job_Pipeline@2@tmp/durable-595950a5 (--JENKINS-48300--: if on a laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=300) script returned exit code -1 Based on JENKINS-48300 it seems that Jenkins is intentionally killing my script while it is still running. IMHO it is a bug for Jenkins to assume that a shell script will generate output every n seconds for any finite n. As a workaround I've set -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL to one hour. But what happens when I have a script that takes an hour and one minute!?
[JIRA] (JENKINS-50378) Nodejs plugin should allow passing the architecture on windows
Title: Message Title Atishay Jain created an issue Jenkins / JENKINS-50378 Nodejs plugin should allow passing the architecture on windows Issue Type: Bug Assignee: Nikolas Falco Components: nodejs-plugin Created: 2018-03-23 19:24 Priority: Minor Reporter: Atishay Jain There should be a way to specify that we want to use 32-bit version of node.js on 64-bit version of windows. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48737) Provide lightweight checkouts for Bitbucket Pull Requests
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-48737 Re: Provide lightweight checkouts for Bitbucket Pull Requests Hi, we are also having this issue with our Bitbucket server.I created an easy fix for this issue:https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/117 Also think that this is related to https://issues.jenkins-ci.org/browse/JENKINS-47617 since if the branch name would be the source branch and not something like PR- it would work without this fix. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-25816) Race condition in Proc.join during Channel.syncIO exchange
Title: Message Title Venkata Vineel Yalamarthi commented on JENKINS-25816 Re: Race condition in Proc.join during Channel.syncIO exchange Oleg Nenashev You mind helping me reproduce and understand the issue. I 'm just getting started to work on the project. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-25816) Race condition in Proc.join during Channel.syncIO exchange
Title: Message Title Venkata Vineel Yalamarthi started work on JENKINS-25816 Change By: Venkata Vineel Yalamarthi Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-48737) Provide lightweight checkouts for Bitbucket Pull Requests
Title: Message Title Benjamin Fuchs edited a comment on JENKINS-48737 Re: Provide lightweight checkouts for Bitbucket Pull Requests Hi, we are also having this issue with our Bitbucket server.I created a an easy fix for this issue:https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/117 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-48737) Provide lightweight checkouts for Bitbucket Pull Requests
Title: Message Title Benjamin Fuchs commented on JENKINS-48737 Re: Provide lightweight checkouts for Bitbucket Pull Requests Hi, we are also having this issue with our Bitbucket server. I created a easy fix for this issue: https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/117 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-25816) Race condition in Proc.join during Channel.syncIO exchange
Title: Message Title Venkata Vineel Yalamarthi assigned an issue to Venkata Vineel Yalamarthi Jenkins / JENKINS-25816 Race condition in Proc.join during Channel.syncIO exchange Change By: Venkata Vineel Yalamarthi Assignee: Venkata Vineel Yalamarthi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50377) Error when using axis as token
Title: Message Title
Jarrett B updated an issue
Jenkins / JENKINS-50377
Error when using axis as token
Change By:
Jarrett B
In Jenkins version 1.651.1 it is possible in a [matrix job|[https://wiki.jenkins.io/display/JENKINS/Matrix+Project+Plugin]] to use a [conditional-buildstep|[https://wiki.jenkins.io/display/JENKINS/Conditional+BuildStep+Plugin]] to run a build step to trigger/call builds on other projects and to have as part of the condition the name of an axis (using [token expansion|[https://wiki.jenkins.io/display/JENKINS/Token+Macro+Plugin]]). Doing this in our setup causes the following exception: {code}Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'PLATFORM' in '$\{PLATFORM}'], action = "" the build] {code}For example, having an axis named PLATFORM with string values NX3 and LX3 use to be able to be used in a conditional build step comparing two strings where string 1 is $\{PLATFORM} and string 2 is hard coded to NX3 or LX3 which would build jobs in the matrices differently:!configuration_matrix_axis.PNG!!build_job_condition.PNG!In addition, adding the same functionality using a dynamic axis would be even better.Our setup: * Jenkins version 2.107.1 * Matrix plugin version 1.11 or 1.12 * Token macro plugin v2.3 * Conditional BuildStep 1.3.6 * Dynamic axis v1.0.3Other setup: * Jenkins version 1.651.1 * Will get info on the other versions if it matters when I canIt's a nice feature to have the axis as a token to build the same job differently. Perhpas similar to the email-ext problem JENKINS-14382?
Add Comment
[JIRA] (JENKINS-50377) Error when using axis as token
Title: Message Title
Jarrett B updated an issue
Jenkins / JENKINS-50377
Error when using axis as token
Change By:
Jarrett B
In Jenkins version 1.651.1 it is possible in a [matrix job|[https://wiki.jenkins.io/display/JENKINS/Matrix+Project+Plugin]] to use a [conditional-buildstep|[https://wiki.jenkins.io/display/JENKINS/Conditional+BuildStep+Plugin]] to run a build step to trigger/call builds on other projects and to have as part of the condition the name of an axis (using [token expansion|[https://wiki.jenkins.io/display/JENKINS/Token+Macro+Plugin]]). Doing this in our setup causes the following exception: Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro ' jobs_to_run PLATFORM ' in '$ jobs_to_run \{PLATFORM} '], action = "" the build] For example, having an axis named PLATFORM with string values NX3 and LX3 use to be able to be used in a conditional build step comparing two strings where string 1 is $\{PLATFORM} and string 2 is hard coded to NX3 or LX3 which would build jobs in the matrices differently:!configuration_matrix_axis.PNG!!build_job_condition.PNG!In addition, adding the same functionality using a dynamic axis would be even better.Our setup: * Jenkins version 2.107.1 * Matrix plugin version 1.11 or 1.12 * Token macro plugin v2.3 * Conditional BuildStep 1.3.6 * Dynamic axis v1.0.3Other setup: * Jenkins version 1.651.1 * Will get info on the other versions if it matters when I canIt's a nice feature to have the axis as a token to build the same job differently. Perhpas similar to the email-ext problem [ JENKINS-14382 |https://issues.jenkins-ci.org/browse/JENKINS-14382] ?
Add Comment
[JIRA] (JENKINS-50377) Error when using axis as token
Title: Message Title
Jarrett B created an issue
Jenkins / JENKINS-50377
Error when using axis as token
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Attachments:
build_job_condition.PNG, configuration_matrix_axis.PNG
Components:
conditional-buildstep-plugin, dynamic-axis-plugin, matrix-project-plugin, token-macro-plugin
Created:
2018-03-23 18:55
Priority:
Major
Reporter:
Jarrett B
In Jenkins version 1.651.1 it is possible in a [matrix job|https://wiki.jenkins.io/display/JENKINS/Matrix+Project+Plugin] to use a [conditional-buildstep|https://wiki.jenkins.io/display/JENKINS/Conditional+BuildStep+Plugin] to run a build step to trigger/call builds on other projects and to have as part of the condition the name of an axis (using [token expansion|https://wiki.jenkins.io/display/JENKINS/Token+Macro+Plugin]). Doing this in our setup causes the following exception: Exception caught evaluating condition: [org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'jobs_to_run' in '$jobs_to_run'], action = "" class="error">[Fail the build] For example, having an axis named PLATFORM with string values NX3 and LX3 use to be able to be used in a conditional build step comparing two strings where string 1 is ${PLATFORM} and string 2 is hard coded to NX3 or LX3 which would build jobs in the matrices differently: In addition, adding the same functionality using a dynamic axis would be even better. Our setup:
Jenkins version 2.107.1
Matrix plugin version 1.11 or 1.12
Token macro plugin v2.3
[JIRA] (JENKINS-50376) New Item sidebar link is not working
Title: Message Title E Varona created an issue Jenkins / JENKINS-50376 New Item sidebar link is not working Issue Type: Bug Assignee: Unassigned Attachments: jenkinsNoNewItem.png Components: core Created: 2018-03-23 18:36 Environment: Jenkins ver. 2.110 running on AWS Linux 3.14.48-33.39.amzn1.x86_64. Issue tested with Chrome v65.0, Firefox 59.0.1 (64-bit) and Safari 11.0.3 Labels: jenkins link new-item Priority: Minor Reporter: E Varona We recently noticed that on any page view, the sidebar link for "New Item" is not available. The icon is there but the link is unavailable. Manually going to a view's /newJob link works as does selecting New Item from the Jenkins chevron in the upper left. The only change we've made recently is to switch from using Crowd to SAML for authentication. The auth matrix is identical to what was previously configured and no other privileges seem to be effected.
[JIRA] (JENKINS-45982) Calling super to CPS-transformed methods fails with CpsCallableInvocation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-45982 Re: Calling super to CPS-transformed methods fails with CpsCallableInvocation Code changed in jenkins User: Andrew Bayer Path: pom.xml src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java http://jenkins-ci.org/commit/workflow-cps-plugin/7ac0d46ce3ef04525a74570962328a12adea9add Log: Merge pull request #212 from abayer/jenkins-45982 JENKINS-45982 Fix calling CPS-transformed super methods. Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/a63e6848d642...7ac0d46ce3ef Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-45982) Calling super to CPS-transformed methods fails with CpsCallableInvocation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-45982 Re: Calling super to CPS-transformed methods fails with CpsCallableInvocation Code changed in jenkins User: Andrew Bayer Path: pom.xml src/test/java/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition2Test.java http://jenkins-ci.org/commit/workflow-cps-plugin/672122274d4eab2217ae4d5460c984f953905d63 Log: JENKINS-45982 Fix calling CPS-transformed super methods. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-33708) Invocation of 'sh' on Windows should provide a more helpful error
Title: Message Title
Nick Jones edited a comment on JENKINS-33708
Re: Invocation of 'sh' on Windows should provide a more helpful error
With Git for Windows 2.16.2, I was able to add C:\Program Files\Git\usr\bin to the PATH (rather than C:\Program Files\Git\bin) and consequently my ` {{ sh ` }} commands work in both FreeStyle and Pipeline builds. No ` {{ mklink ` }} was necessary.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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] (JENKINS-33708) Invocation of 'sh' on Windows should provide a more helpful error
Title: Message Title Nick Jones commented on JENKINS-33708 Re: Invocation of 'sh' on Windows should provide a more helpful error With Git for Windows 2.16.2, I was able to add C:\Program Files\Git\usr\bin to the PATH (rather than C:\Program Files\Git\bin) and consequently my `sh` commands work in both FreeStyle and Pipeline builds. No `mklink` was necessary. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49366) Nested podTemplate stopped working in 1.1.4
Title: Message Title Steven Goodstein updated JENKINS-49366 Jenkins / JENKINS-49366 Nested podTemplate stopped working in 1.1.4 Change By: Steven Goodstein Status: Closed In Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49366) Nested podTemplate stopped working in 1.1.4
Title: Message Title Steven Goodstein commented on JENKINS-49366 Re: Nested podTemplate stopped working in 1.1.4 I have been using nested pod templates this way for some time. I have a shared library with "templates" that I can mix and match and build off of in a DRY fashion. Updating my kubernetes plugin past 1.1.3 breaks this functionality for me as well. As Yngvar stated this is still in the readme as well. I'm confused by the resolution "This is not a defect". Is this just a feature that is being removed? Is there an architectural change that prevents this from being possible? Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-41791) Pipeline waiting for user input does not survive Jenkins restart
Title: Message Title Junpeng Luo commented on JENKINS-41791 Re: Pipeline waiting for user input does not survive Jenkins restart Same behavior as described. Can't reproduce that in local Jenkins but for us it happened every time after each restarts recently in our PROD Jenkins. With following logs for builds can't click input step. Mar 23, 2018 12:22:37 PM org.jenkinsci.plugins.workflow.support.steps.input.InputAction loadExecutions WARNING: no flow execution found for my-job #79 Jenkins version 2.73.2 Pipeline input step plugin version 2.8 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-30909) queue.xml only gets persisted on successful shutdown
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30909 Re: queue.xml only gets persisted on successful shutdown Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/model/Queue.java test/pom.xml test/src/test/java/hudson/model/QueueRestartTest.java test/src/test/java/hudson/model/QueueTest.java test/src/test/resources/hudson/model/QueueTest/load_queue_xml/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/a/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/b/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/c/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/d/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/e/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/f/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/g/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/h/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/i/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/j/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/jobs/k/config.xml test/src/test/resources/hudson/model/QueueTest/load_queue_xml/queue.xml http://jenkins-ci.org/commit/jenkins/8c975f11c5a366b1693ed2be04e184a714cf2f84 Log: [FIX JENKINS-30909] Make sure queue is persisted reliably (#3244) [FIX JENKINS-30909] Make sure queue is persisted reliably Fix tests on Windows Ensure Saver is thread-safe (cherry picked from commit 72a7529a119b2be6b3ff93d63688ee6973404236) Add Comment
[JIRA] (JENKINS-49634) Wrong escaping of quotes in the Setup Wizard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49634 Re: Wrong escaping of quotes in the Setup Wizard Code changed in jenkins User: Oleg Nenashev Path: core/src/main/resources/jenkins/install/pluginSetupWizard.properties core/src/main/resources/jenkins/install/pluginSetupWizard_it.properties http://jenkins-ci.org/commit/jenkins/96c52d901bda669eea6eff7c4f57e7032be1e4d5 Log: Merge pull request #3303 from recena/JENKINS-49634 JENKINS-49634 Wrong escaping of quotes in the Setup Wizard (cherry picked from commit dcb1bcd540ae2b5612f31335ba2bd80a65203303) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49498) Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49498 Re: Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard Code changed in jenkins User: Oleg Nenashev Path: core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/config_nl.properties http://jenkins-ci.org/commit/jenkins/d09fc3a5521ad3fba446e36002ef4fc58d5f9bf9 Log: Merge pull request #3286 from vStone/feature/JENKINS-49496-dutch-translation-security-fix JENKINS-49498: Fix poorly translated sign-up string (dutch) (cherry picked from commit 59bfe03ebe70eafaeb057aa0a0c0184e2097a8c9) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-34712) "master is offline" preventing Pipeline from executing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34712 Re: "master is offline" preventing Pipeline from executing Code changed in jenkins User: Oleg Nenashev Path: core/src/main/resources/lib/hudson/executors.jelly http://jenkins-ci.org/commit/jenkins/20d44c5aa750f6fece96f83f0f7ed519e9df2e54 Log: Merge pull request #3294 from dwnusbaum/JENKINS-34712 JENKINS-34712 Always show the master node when it is offline (cherry picked from commit b67a30f8daff936c91fd54b90bef6c366707a8f1) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49565) Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49565 Re: Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core Code changed in jenkins User: Oleg Nenashev Path: cli/pom.xml http://jenkins-ci.org/commit/jenkins/db034758e09a4a7cab98e65ec1084be0e1205e70 Log: JENKINS-49565 - Update Jenkins CLI to Mina SSHD Core 1.7.0 (cherry picked from commit 36f7fc0d925338a2642553ec7e7a0eda938fb3f6) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50375) Can't copy/paste stage logs because the selections get deselected after mouse button is released
Title: Message Title
Karl Shultz created an issue
Jenkins / JENKINS-50375
Can't copy/paste stage logs because the selections get deselected after mouse button is released
Issue Type:
Bug
Assignee:
Sam Van Oort
Attachments:
image-2018-03-23-13-01-40-311.png, image-2018-03-23-13-02-52-197.png
Components:
pipeline-stage-view-plugin
Created:
2018-03-23 17:09
Environment:
Jenkins: Core 2.11 Pipeline: Stage View 2.9 Client: Fedora Workstation 27 Chrome 65.0.3325.181 Firefox 59.0.1
Priority:
Minor
Reporter:
Karl Shultz
Summary: When viewing the logs for an individual stage in stage view (by clicking on that stage and selecting "Logs"), the user is not able to copy content from those logs into their clipboard, because the highlighted area gets deselected as soon as they release the mouse button. Steps to recreate: 1. Create a very simple pipeline. Mine looks like:
node {
currentDirectory = pwd()
stage ("thing") {
sh "echo HERE IT IS ${currentDirectory}"
echo "PWD is ${currentDirectory}"
}
}
2. Run the pipeline. 3. Click in the green "stage' area of any existing run, and click Logs:4. Pick an entry in the popover. 5. Click and hold the left mouse button to select some text. That behaves normally. 6. But the moment you release
[JIRA] (JENKINS-38998) Cannot trigger pipeline job
Title: Message Title Tiejun Sha commented on JENKINS-38998 Re: Cannot trigger pipeline job pipeline can be triggered, but seems it will run sequentially with the other sub-jobs in a multi-job how can we make sure it can run parallel with the other sub-jobs? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50291) Customize where AsyncPeriodicWork are logged
Title: Message Title Baptiste Mathus started work on JENKINS-50291 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-21942) Unreliable defaulting of Jenkins.workspaceDir
Title: Message Title Baptiste Mathus commented on JENKINS-21942 Re: Unreliable defaulting of Jenkins.workspaceDir Jesse Glick I couldn't reproduce either with 2.112, or a local build for https://github.com/jenkinsci/jenkins/pull/3364 I can confirm the config.xml gets created without any user interaction during Jenkins startup in any case now, even . Do we want to close this, do you still think it makes sense to do additional things here, like the admin monitor you're talking about? If so, care to clarify what you mean that monitor would do? Unassigning myself, and removing from Essentials milestone 1 for now at least as AFAIU there's nothing to fix here. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-21942) Unreliable defaulting of Jenkins.workspaceDir
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-21942 Unreliable defaulting of Jenkins.workspaceDir Change By: Baptiste Mathus Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-21942) Unreliable defaulting of Jenkins.workspaceDir
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-21942 Unreliable defaulting of Jenkins.workspaceDir Change By: Baptiste Mathus Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-21942) Unreliable defaulting of Jenkins.workspaceDir
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-21942 Unreliable defaulting of Jenkins.workspaceDir Change By: Baptiste Mathus Labels: essentials upgrade workspace Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-41519) Post stages should have well defined order
Title: Message Title Jeff G commented on JENKINS-41519 Re: Post stages should have well defined order +1 for this. Just got bit because you can't use archiveArtifacts in a post:success if you use cleanWs in post:always because post:always will clean up the artifacts you want to archive. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-38825) MultiJob does not build Pipeline jobs
Title: Message Title Tiejun Sha commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs +1 , we are eager to get this fix as well Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50364) Attachment URI incorrect when file name contains a space
Title: Message Title Stefan Drissen commented on JENKINS-50364 Re: Attachment URI incorrect when file name contains a space It seems like this was broken recently in JENKINS-37026 - for which the pull request was created a "long" time ago in 2016 - but which has only been included in the latest 1.5 version of the plug-in which was release 29 days ago. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50291) Customize where AsyncPeriodicWork are logged
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-50291 Customize where AsyncPeriodicWork are logged Change By: Baptiste Mathus Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-21942) Unreliable defaulting of Jenkins.workspaceDir
Title: Message Title Baptiste Mathus started work on JENKINS-21942 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50320) Adjust JEP 301 once snapshotting data JEP is accepted
Title: Message Title Baptiste Mathus updated JENKINS-50320 Jenkins / JENKINS-50320 Adjust JEP 301 once snapshotting data JEP is accepted Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50374) Multibranch job is permanently disabled if Jenkinsfile is deleted then re-added back to a branch
Title: Message Title Edgar Pedron created an issue Jenkins / JENKINS-50374 Multibranch job is permanently disabled if Jenkinsfile is deleted then re-added back to a branch Issue Type: Bug Assignee: Denis Saponenko Components: pipeline-multibranch-defaults-plugin Created: 2018-03-23 16:24 Environment: Jenkins ver 2.60.3 (unknown) null - Version Active Directory plugin - 1.33 Ant Plugin - 1.2 anything-goes-formatter - 1.0 Apache HttpComponents Client 4.x API Plugin - 4.5.3-2.0 Async Http Client - 1.7.24.1 Audit Trail - 1.7 Authentication Tokens API Plugin - 1.3 Backup plugin - 1.6.1 bouncycastle API Plugin - 2.16.1 Branch API Plugin - 2.0.10 Build Blocker Plugin - 1.7.3 Build Keeper Plugin - 1.3 Build Pipeline Plugin - 1.5.3.1 Hudson build timeout plugin - 1.6 buildgraph-view - 1.8 Checkmarx Plugin - 8.42.0 Checkstyle Plug-in - 3.43 chromedriver - 1.2 Hudson ClearCase Plug-in - 1.3.3 Hudson ClearCase UCM Baseline Plug-in - 1.7.1 Clone Workspace SCM Plug-in - 0.3 Cobertura Plugin - 1.9.6 Code-Share - 1.4.0-RC-15 Conditional BuildStep - 1.3.6 Config File Provider Plugin - 2.9.2 Copy Artifact Plugin - 1.38.1 Credentials Binding Plugin - 1.14 Credentials Plugin - 2.1.16 Custom View Tabs Plugin - 1.3 CVS Plug-in - 2.11 Dashboard View - 2.9.10 Dependency Graph Viewer Plugin - 0.11 Hudson description setter plugin - 1.6 disk-usage plugin - 0.25 Display URL API - 2.0 Docker Commons Plugin - 1.7 Docker Pipeline - 1.12 DocLinks plugin - 0.6 Durable Task Plugin - 1.14 Edgewall Trac Plugin - 1.13 Email Extension Plugin - 2.41 Emma plugin - 1.29 Environment Injector Plugin - 1.90 Hudson Extended Read Permission Plugin - 1.0 External Monitor Job Type Plugin - 1.4 Favorite - 2.3.0 FindBugs Plug-in - 4.69 Folders Plugin - 6.0.4 Git plugin - 3.7.0 Git client plugin - 2.7.0 GIT server Plugin - 1.7 GitLab Plugin - 1.5.1 Green Balls - 1.14 Groovy - 2.0 Groovy Postbuild - 2.3 HTML Publisher plugin - 1.11 HTTP Request Plugin - 1.8.22 Hudson WebSVN2 plugin - 0.9 Icon Shim Plugin - 2.0.3 Jackson 2 API Plugin - 2.7.3 JaCoCo plugin - 1.0.19 Javadoc Plugin - 1.4 _javascript_ GUI Lib: ACE Editor bundle plugin - 1.1 _javascript_ GUI Lib: Handlebars bundle plugin - 1.1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin - 1.2.1 _javascript_ GUI Lib: Moment.js bundle plugin - 1.1.1 jmdc-jenkins-plugin - 1.1 Job Configuration History Plugin - 2.15 Job Import Plugin - 1.7 jQuery plugin - 1.12.4-0 jQuery UI plugin - 1.0.2 JSch dependency plugin - 0.1.54.1 JUnit Plugin - 1.20 LDAP Plugin - 1.16 LDAP Email Plugin - 0.8 M2 Extra Steps Plugin
[JIRA] (JENKINS-50373) Design and implement the evergreen-client metrics system
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50373 Design and implement the evergreen-client metrics system Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-03-23 16:23 Priority: Minor Reporter: R. Tyler Croy Related to JENKINS-49852 I need to write down my thoughts in a JEP and design the basics for the metrics system for evergreen-client. My first thought is to have evergreen-client just act as a local statsd collector for Jenkins, and send those bits along to datadog on some period. Add Comment
[JIRA] (JENKINS-49852) Collect Pipeline usage telemetry
Title: Message Title R. Tyler Croy commented on JENKINS-49852 Re: Collect Pipeline usage telemetry Some meeting notes can be found here from a discussion with the Pipeline developers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Jesse Glick commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Oleg Nenashev actually the fix was in 1.14-beta-1: original commit Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50320) Adjust JEP 301 once snapshotting data JEP is accepted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50320 Re: Adjust JEP 301 once snapshotting data JEP is accepted Code changed in jenkins User: R. Tyler Croy Path: jep/301/README.adoc http://jenkins-ci.org/commit/jep/861b42b140544d5dae27a756a1726747c4a8bd54 Log: Merge pull request #72 from batmat/JENKINS-50320-align-jep-301-with-jep-302 JENKINS-50320 EVERGREEN_HOME is where things are, not just JENKINS_HOME Compare: https://github.com/jenkinsci/jep/compare/0a879260118b...861b42b14054 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50320) Adjust JEP 301 once snapshotting data JEP is accepted
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50320 Re: Adjust JEP 301 once snapshotting data JEP is accepted Code changed in jenkins User: Baptiste Mathus Path: jep/301/README.adoc http://jenkins-ci.org/commit/jep/2825fbddb447f36c56290fbfb46d2a06c7ad91be Log: JENKINS-50320 EVERGREEN_HOME is where things are, not just JENKINS_HOME Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50320) Adjust JEP 301 once snapshotting data JEP is accepted
Title: Message Title Baptiste Mathus updated JENKINS-50320 Jenkins / JENKINS-50320 Adjust JEP 301 once snapshotting data JEP is accepted Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50249) disable "build by token" by default using a system property in Jenkins
Title: Message Title James Nord assigned an issue to Unassigned Jenkins / JENKINS-50249 disable "build by token" by default using a system property in Jenkins Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50249) disable "build by token" by default using a system property in Jenkins
Title: Message Title James Nord stopped work on JENKINS-50249 Change By: James Nord Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50372) Error when deleting multibranch job
Title: Message Title Edgar Pedron updated an issue Jenkins / JENKINS-50372 Error when deleting multibranch job Change By: Edgar Pedron Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50372) Error when deleting multibranch job
Title: Message Title Edgar Pedron created an issue Jenkins / JENKINS-50372 Error when deleting multibranch job Issue Type: Bug Assignee: Denis Saponenko Components: pipeline-multibranch-defaults-plugin Created: 2018-03-23 16:08 Environment: Jenkins ver 2.60.3 null - Version Active Directory plugin - 1.33 Ant Plugin - 1.2 anything-goes-formatter - 1.0 Apache HttpComponents Client 4.x API Plugin - 4.5.3-2.0 Async Http Client - 1.7.24.1 Audit Trail - 1.7 Authentication Tokens API Plugin - 1.3 Backup plugin - 1.6.1 bouncycastle API Plugin - 2.16.1 Branch API Plugin - 2.0.10 Build Blocker Plugin - 1.7.3 Build Keeper Plugin - 1.3 Build Pipeline Plugin - 1.5.3.1 Hudson build timeout plugin - 1.6 buildgraph-view - 1.8 Checkmarx Plugin - 8.42.0 Checkstyle Plug-in - 3.43 chromedriver - 1.2 Hudson ClearCase Plug-in - 1.3.3 Hudson ClearCase UCM Baseline Plug-in - 1.7.1 Clone Workspace SCM Plug-in - 0.3 Cobertura Plugin - 1.9.6 Code-Share - 1.4.0-RC-15 Conditional BuildStep - 1.3.6 Config File Provider Plugin - 2.9.2 Copy Artifact Plugin - 1.38.1 Credentials Binding Plugin - 1.14 Credentials Plugin - 2.1.16 Custom View Tabs Plugin - 1.3 CVS Plug-in - 2.11 Dashboard View - 2.9.10 Dependency Graph Viewer Plugin - 0.11 Hudson description setter plugin - 1.6 disk-usage plugin - 0.25 Display URL API - 2.0 Docker Commons Plugin - 1.7 Docker Pipeline - 1.12 DocLinks plugin - 0.6 Durable Task Plugin - 1.14 Edgewall Trac Plugin - 1.13 Email Extension Plugin - 2.41 Emma plugin - 1.29 Environment Injector Plugin - 1.90 Hudson Extended Read Permission Plugin - 1.0 External Monitor Job Type Plugin - 1.4 Favorite - 2.3.0 FindBugs Plug-in - 4.69 Folders Plugin - 6.0.4 Git plugin - 3.7.0 Git client plugin - 2.7.0 GIT server Plugin - 1.7 GitLab Plugin - 1.5.1 Green Balls - 1.14 Groovy - 2.0 Groovy Postbuild - 2.3 HTML Publisher plugin - 1.11 HTTP Request Plugin - 1.8.22 Hudson WebSVN2 plugin - 0.9 Icon Shim Plugin - 2.0.3 Jackson 2 API Plugin - 2.7.3 JaCoCo plugin - 1.0.19 Javadoc Plugin - 1.4 _javascript_ GUI Lib: ACE Editor bundle plugin - 1.1 _javascript_ GUI Lib: Handlebars bundle plugin - 1.1.1 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin - 1.2.1 _javascript_ GUI Lib: Moment.js bundle plugin - 1.1.1 jmdc-jenkins-plugin - 1.1 Job Configuration History Plugin - 2.15 Job Import Plugin - 1.7 jQuery plugin - 1.12.4-0 jQuery UI plugin - 1.0.2 JSch dependency plugin - 0.1.54.1 JUnit Plugin - 1.20 LDAP Plugin - 1.16 LDAP Email Plugin - 0.8 M2 Extra Steps Plugin - 1.1.4 Mailer Plugin - 1.20 MapDB API Plugin - 1.0.1.0 Mask
[JIRA] (JENKINS-50249) disable "build by token" by default using a system property in Jenkins
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-50249 disable "build by token" by default using a system property in Jenkins I think BuildAuthorizationToken itself could be split out into the build-token-root plugin, with a PluginServletFilter for URL compatibility. Change By: Jesse Glick Labels: split-plugins-from-core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-49374) 'Could not find dependency command-launcher of [package]' for every installed plugin when trying to run the jenkins check for updates
Title: Message Title Nathan Hodson commented on JENKINS-49374 Re: 'Could not find dependency command-launcher of [package]' for every installed plugin when trying to run the jenkins check for updates I was able to resolve this issue by changing the update site to https://updates.jenkins.io/current/update-center.json. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Oleg Nenashev commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Sam Van Oort Yes, the PR will do its job Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Sam Van Oort commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache PR that should sort this out incidentally while fixing another bug IIUC Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50164) 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running
Title: Message Title Baptiste Mathus updated JENKINS-50164 Jenkins / JENKINS-50164 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Sam Van Oort commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Oleg Nenashev The field gets renamed in https://github.com/jenkinsci/workflow-job-plugin/pull/91 as part of fixing JENKINS-38383 – would that sort them out? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47611) RejectedAccessException: Scripts not permitted to use method org.apache.maven.model.Model getVersion
Title: Message Title Oleg Nenashev commented on JENKINS-47611 Re: RejectedAccessException: Scripts not permitted to use method org.apache.maven.model.Model getVersion It is not a JEP-200 issue, just something about Script Security Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47611) RejectedAccessException: Scripts not permitted to use method org.apache.maven.model.Model getVersion
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47611 RejectedAccessException: Scripts not permitted to use method org.apache.maven.model.Model getVersion Change By: Oleg Nenashev Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-47611) RejectedAccessException: Scripts not permitted to use method org.apache.maven.model.Model getVersion
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-47611 RejectedAccessException: Scripts not permitted to use method org.apache.maven.model.Model getVersion Change By: Oleg Nenashev Labels: JEP-200 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-33668) vSphere Plugin crashes with "org.apache.commons.beanutils.ConversionException: No value specified for 'Class'" with Jenkins ver. 1.653
Title: Message Title pjdarton closed an issue as Fixed Looks like this was fixed a while ago. See https://issues.jenkins-ci.org/browse/JENKINS-33668?focusedCommentId=251838=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-251838 Jenkins / JENKINS-33668 vSphere Plugin crashes with "org.apache.commons.beanutils.ConversionException: No value specified for 'Class'" with Jenkins ver. 1.653 Change By: pjdarton Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to
[JIRA] (JENKINS-25291) Allow selection of cloud to be parameterized/text entry
Title: Message Title pjdarton closed an issue as Done I'm not sure when it was done, but this functionality has been present for a while now - you can have a vsphere cloud parameter on a parameterized build. Jenkins / JENKINS-25291 Allow selection of cloud to be parameterized/text entry Change By: pjdarton Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-42215) vSphere-cloud-plugin add feature to Delete/Rename Template
Title: Message Title pjdarton closed an issue as Won't Do No response to earlier question. Suspect this has been a non-issue for some time. Jenkins / JENKINS-42215 vSphere-cloud-plugin add feature to Delete/Rename Template Change By: pjdarton Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-40336) invalid login for second template in one vsphere cloud
Title: Message Title pjdarton commented on JENKINS-40336 Re: invalid login for second template in one vsphere cloud Downgrading to "minor" as this is only a cosmetic bug (it doesn't affect actual plugin operation, it just looks bad on the GUI). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-40336) invalid login for second template in one vsphere cloud
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-40336 invalid login for second template in one vsphere cloud Change By: pjdarton Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-31468) Allow the usage of parameters in Reconfigure VM
Title: Message Title pjdarton closed an issue as Done No response to earlier question. Suspect this has been a non-issue for some time. Jenkins / JENKINS-31468 Allow the usage of parameters in Reconfigure VM Change By: pjdarton Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-29479) Unable to connect to vCloud
Title: Message Title pjdarton closed an issue as Cannot Reproduce No response to earlier question. Suspect this has been a non-issue for some time. Jenkins / JENKINS-29479 Unable to connect to vCloud Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-50371) JIRA PIPELINE jiraSearch() finds max 50 items
Title: Message Title Julian Fuchs created an issue Jenkins / JENKINS-50371 JIRA PIPELINE jiraSearch() finds max 50 items Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2018-03-23 15:17 Priority: Major Reporter: Julian Fuchs When I perform a query with the jiraSearch() in the Jenkins pipeline it only finds 50 items. I would have expected that it finds all items on the JIRA server that are matching the query. The SearchIssuesStep class calling the method getIssuesFromJqlSearch() of the JiraSession class in line 91. The result of the method is in line 135 and is: return service.getIssuesFromJqlSearch(jqlSearch, 50); Other parts of the JiraSession class are using the max integer value, like line 230. List issues = service.getIssuesFromJqlSearch(query, Integer.MAX_VALUE);
[JIRA] (JENKINS-28627) Jenkins Vsphere-cloud-plugin
Title: Message Title pjdarton closed an issue as Done No response to earlier question. Jenkins / JENKINS-28627 Jenkins Vsphere-cloud-plugin Change By: pjdarton Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-28345) Linked Clone breaks Deploy step
Title: Message Title pjdarton closed an issue as Fixed Suspect this has been a non-issue for some time now. Jenkins / JENKINS-28345 Linked Clone breaks Deploy step Change By: pjdarton Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-26543) VM abruptly gets restarted through Jenkins.
Title: Message Title pjdarton closed an issue as Not A Defect No response to earlier prompt. Jenkins / JENKINS-26543 VM abruptly gets restarted through Jenkins. Change By: pjdarton Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-24758) Build crashes (network timout) with vSphere slaves
Title: Message Title pjdarton closed an issue as Cannot Reproduce No response to earlier question. Suspect this has been a non-issue for some time. Jenkins / JENKINS-24758 Build crashes (network timout) with vSphere slaves Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-42144) Publish HP test result Failed with java.lang.NumberFormatException
Title: Message Title Weston Dyer commented on JENKINS-42144 Re: Publish HP test result Failed with java.lang.NumberFormatException Hi Yafim Kazak, I've tried the patch above, but I am still getting a similar issue. Is there any resolution? Anything that I need to check? Test PASSED Test result: Passed 22/03/2018 16:14:15 Test complete: C:\LR\Scenario1.lrs --- Cleaning up the environment... Run status: Job succeeded, total tests: 1, succeeded: 1, failures: 0, errors: 0 Passed : C:\LR\Scenario1.lrs Recording test results Report archiving mode is set to: PUBLISH_HTML_REPORT Zipping report folder: C:\myJenkins\workspace\PerformanceTest\0451c9 Parsing test run dataset for perfomrance report ERROR: Build step failed with exception java.lang.NumberFormatException: For input string: "0.2" at java.lang.NumberFormatException.forInputString(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) at java.lang.Integer.parseInt(Unknown Source) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-19987) Automatically determine VM IP address for SSH login
Title: Message Title pjdarton closed an issue as Done No response to earlier question. Suspect this has been a non-issue for years. Jenkins / JENKINS-19987 Automatically determine VM IP address for SSH login Change By: pjdarton Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-28536) Deploy VM from Template no longer working
Title: Message Title pjdarton closed an issue as Cannot Reproduce Closing: No response to previous question. Feel free to re-open if there's new evidence. Jenkins / JENKINS-28536 Deploy VM from Template no longer working Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-12163) Cleaning VM before start next job in queue.
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-12163 Cleaning VM before start next job in queue. Change By: pjdarton Assignee: Jason Swager Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-41483) com.vmware.vim25.NoPermission exception connecting to vsphere 6.0 server
Title: Message Title pjdarton closed an issue as Cannot Reproduce No response from original poster. Feel free to re-open if there's new evidence. Jenkins / JENKINS-41483 com.vmware.vim25.NoPermission exception connecting to vsphere 6.0 server Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-36085) vSphere 2.13 causes error while restarting VM
Title: Message Title pjdarton closed an issue as Cannot Reproduce No response from original poster. Feel free to re-open if there's new evidence. Jenkins / JENKINS-36085 vSphere 2.13 causes error while restarting VM Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-48341) Wrong link changeset to tfs/vsts
Title: Message Title Kellie Jos commented on JENKINS-48341 Re: Wrong link changeset to tfs/vsts Hector Scesa We've just released the newest version of the plugin, 5.133.0, which contains this fix. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50348) Why does "Pipeline: Groovy" require "Support Core"?
Title: Message Title Christian Höltje commented on JENKINS-50348 Re: Why does "Pipeline: Groovy" require "Support Core"? Jesse Glick Is there any reason you set Support Core as required (instead of optional) in JENKINS-31840 or was it an accident? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-43946) vSphere cloud plugin takes too long to notice needed capacity
Title: Message Title pjdarton closed an issue as Cannot Reproduce Believed to be a core Jenkins issue; no response from original poster. Feel free to re-open if there's new evidence. Jenkins / JENKINS-43946 vSphere cloud plugin takes too long to notice needed capacity Change By: pjdarton Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
