[JIRA] (JENKINS-49926) "IllegalArgumentException: Cannot relativize" when using a symlink
Title: Message Title Jesús Lunar Pérez commented on JENKINS-49926 Re: "IllegalArgumentException: Cannot relativize" when using a symlink Great, I didn't know that. We'll try and I'll let you know. Thanks in advance. 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-49898) Cannot relativize 'src/it/projects' relatively to ... when using relative path for Invoker Plugin projectsDirectory
Title: Message Title
benoit guerin commented on JENKINS-49898
Re: Cannot relativize 'src/it/projects' relatively to ... when using relative path for Invoker Plugin projectsDirectory
According to the documentation of the plugin, I would do this (prepending ${basedir} if is not an absolute path). For what I known, this is what Maven internally does. IE considering any relative path as relative from the project root (ie ${basedir}) And sorry but no, I do not have any examples, because I follow Maven conventions, so I use the default value, ${basedir}/src/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-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title Emilio Escobar started work on JENKINS-49931 Change By: Emilio Escobar 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-42567) si viewproject gets stuck (sometimes) while checking out Integrity project
Title: Message Title Alex Ruff reopened an issue Hello PTC ALM Support, in our setup PTC Plugin V2.1 and Jenkins 2.36 we face sporadic hang up of the Jenkins Master when a PTC Project is freshly checked out. Unfortunatelly I dont have any logs of the situation as we have to restart the Jenkins Master Server and after the restart the logs are gone. As soon as we observe this error again (very sporadic) I will post a log of the situation. Best regards Alex Jenkins / JENKINS-42567 si viewproject gets stuck (sometimes) while checking out Integrity project Change By: Alex Ruff Resolution: Won't Fix Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49926) "IllegalArgumentException: Cannot relativize" when using a symlink
Title: Message Title Cyrille Le Clerc commented on JENKINS-49926 Re: "IllegalArgumentException: Cannot relativize" when using a symlink Your welcome Jesús Lunar Pérez! 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-49898) Cannot relativize 'src/it/projects' relatively to ... when using relative path for Invoker Plugin projectsDirectory
Title: Message Title Cyrille Le Clerc commented on JENKINS-49898 Re: Cannot relativize 'src/it/projects' relatively to ... when using relative path for Invoker Plugin projectsDirectory Thanks benoit guerin! 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-46283) pipeline hangs after executing sh step command
Title: Message Title
Steve Boardwell commented on JENKINS-46283
Re: pipeline hangs after executing sh step command
I can confirm this is still happening in Jenkins 2.89.4 with all plugins up to date at the time of writing. In our situation we have one step to start a web server, followed by a step to wait until the web server is ready.
node {
stage('Running Tests') {
setupWebserver()
checkStart('http://webserver:8080')
}
}
def checkStart(String url) {
sh """
...
...curl command in a for loop etc...
...
echo 'Web server up and running!!!'
"""
}
def setupWebserver() {
sh """#!/bin/bash
...
...some pre-steps...
...
webServer/bin/server.sh restart
"""
}
In the logs you can see that the server is started...
18:20:20 Starting jetty using port 8080
18:20:20 Stopping Jetty: OK
18:20:25 Starting Jetty: STARTED Jetty Sat Mar 3 18:20:24 CET 2018 under PID 21653
On the agent, you can see that the process was started successfully and that the web server is available:
# check for PID
jenkins@p-agent:~$ ps aux | grep [2]1653 | awk '{ print $1" "$2 }'
jenkins 21653
# check for url
jenkins@p-agent:~$ curl --write-out '%{http_code}\n' -o /dev/null -qsSL http://localhost:8080
200
Looking for durable tasks, I could not find any processes containing the word 'durable':
jenkins@p-agent:~$ ps auxww | grep [d]urable | awk '{ print $1" "$2 }'
jenkins@p-agent:~$
Question: would it be worth adding a pre-script to our sh scripts to:
print out the current PID of the durable task
print out the current parent directory of the durable task
do a ps aux | grep for the running script
add a trap to print when the script is exiting
which signals should be best handled in this case? EXIT, INT, TERM, HUP?
[JIRA] (JENKINS-49944) support some handling for skipped stages
Title: Message Title Andreas Klemp created an issue Jenkins / JENKINS-49944 support some handling for skipped stages Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2018-03-06 09:01 Environment: Jenkins version 2.89.4 Labels: pipeline skip when Priority: Minor Reporter: Andreas Klemp It would be really nice to support some steps in case a stage is skipped due to the when block. I understand the motivation in JENKINS-47577 not executing some post block for this. However, without some support for this, one cannot send an e-mail when a stage is skipped or inform other tools about this, that monitor pipelines for example. In my case this would render the really nice descriptive pipelines rather useless and I would have to stick to the scripted pipelines which results in a lot more code. Add
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Robin Smith commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries If the pipeline shared libraries are in Bitbucket, it's necessary to use Git to load them. 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
Erez Arbell commented on JENKINS-45982
Re: Calling super to CPS-transformed methods fails with CpsCallableInvocation
I do not understand from the above comment what is the status of this issue. Can you explain? I am also facing the same issue. Here is a simple example:
class A {
def speak(script) {
script.echo "Hello from A"
}
}
class B extends A {
def speak(script) {
script.echo "Hello from B"
super.speak(script)
}
}
node('master') {
def b = new B()
b.speak(this)
}
Output:
[Pipeline] {
[Pipeline] echo
Hello from B
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
hudson.remoting.ProxyException: com.cloudbees.groovy.cps.impl.CpsCallableInvocation
Caused: hudson.remoting.ProxyException: org.codehaus.groovy.runtime.InvokerInvocationException: com.cloudbees.groovy.cps.impl.CpsCallableInvocation
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:100)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)
at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:214)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onSuperCall(GroovyInterceptor.java:49)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onSuperCall(SandboxInterceptor.java:390)
at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:211)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedSuperCall(Checker.java:217)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.superCall(SandboxInvoker.java:25)
at B.speak(WorkflowScript:10)
at WorkflowScript.run(WorkflowScript:16)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:54)
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.GeneratedMethodAccessor71.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.LocalVariableBlock$LocalVariable.get(LocalVariableBlock.java:39)
at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
at com.cloudbees.groovy.cps.impl.LocalVariableBlock.evalLValue(LocalVariableBlock.java:28)
at com.cloudbees.groovy.cps.LValueBlock$BlockImpl.eval(LValueBlock.java:55)
at com.cloudbees.groovy.cps.LValueBlock.eval(LValueBlock.java:16)
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.pl
[JIRA] (JENKINS-45982) Calling super to CPS-transformed methods fails with CpsCallableInvocation
Title: Message Title
Erez Arbell edited a comment on JENKINS-45982
Re: Calling super to CPS-transformed methods fails with CpsCallableInvocation
I do not understand from the above comment what is the status of this issue. Can you explain?I am also facing the same issue. Here is a simple example:{code:java}class A { def speak(script) {script.echo "Hello from A" }}class B extends A { def speak(script) {script.echo "Hello from B"super.speak(script) }}node('master') { def b = new B() b.speak(this)}{code}Output:{code:java}[Pipeline] {[Pipeline] echoHello from B[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinehudson.remoting.ProxyException: com.cloudbees.groovy.cps.impl.CpsCallableInvocationCaused: hudson.remoting.ProxyException: org.codehaus.groovy.runtime.InvokerInvocationException: com.cloudbees.groovy.cps.impl.CpsCallableInvocation at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:100) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:214) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onSuperCall(GroovyInterceptor.java:49) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onSuperCall(SandboxInterceptor.java:390) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:211) at org.kohsuke.groovy.sandbox.impl.Checker.checkedSuperCall(Checker.java:217) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.superCall(SandboxInvoker.java:25) at B.speak(WorkflowScript:10) at WorkflowScript.run(WorkflowScript:16) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:54) 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.GeneratedMethodAccessor71.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.LocalVariableBlock$LocalVariable.get(LocalVariableBlock.java:39) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.LocalVariableBlock.evalLValue(LocalVariableBlock.java:28) at com.cloudbees.groovy.cps.LValueBlock$BlockImpl.eval(LValueBlock.java:55) at com.cloudbees.groovy.cps.LValueBlock.eval(LValueBlock.java:16) 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 org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:32) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:32) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(C
[JIRA] (JENKINS-45982) Calling super to CPS-transformed methods fails with CpsCallableInvocation
Title: Message Title
Erez Arbell edited a comment on JENKINS-45982
Re: Calling super to CPS-transformed methods fails with CpsCallableInvocation
I do not understand from the above comment what is the status of this issue. Can you explain?I am also facing the same issue. Here is a simple example: {code:java}class A { def speak(script) {script.echo "Hello from A" }}class B extends A { def speak(script) {script.echo "Hello from B"super.speak(script) }}node('master') { def b = new B() b.speak(this)}{code}Output: {code:java}[Pipeline] {[Pipeline] echoHello from B[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinehudson.remoting.ProxyException: com.cloudbees.groovy.cps.impl.CpsCallableInvocationCaused: hudson.remoting.ProxyException: org.codehaus.groovy.runtime.InvokerInvocationException: com.cloudbees.groovy.cps.impl.CpsCallableInvocation at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:100) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:214) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onSuperCall(GroovyInterceptor.java:49) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onSuperCall(SandboxInterceptor.java:390) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:211) at org.kohsuke.groovy.sandbox.impl.Checker.checkedSuperCall(Checker.java:217) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.superCall(SandboxInvoker.java:25) at B.speak(WorkflowScript:10) at WorkflowScript.run(WorkflowScript:16) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:54) 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.GeneratedMethodAccessor71.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.LocalVariableBlock$LocalVariable.get(LocalVariableBlock.java:39) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.LocalVariableBlock.evalLValue(LocalVariableBlock.java:28) at com.cloudbees.groovy.cps.LValueBlock$BlockImpl.eval(LValueBlock.java:55) at com.cloudbees.groovy.cps.LValueBlock.eval(LValueBlock.java:16) 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 org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:32) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:32) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNext
[JIRA] (JENKINS-49945) PR matching regex can never match strategies
Title: Message Title
Stephen Connolly created an issue
Jenkins / JENKINS-49945
PR matching regex can never match strategies
Issue Type:
Bug
Assignee:
rsandell
Components:
github-branch-source-plugin
Created:
2018-03-06 09:41
Priority:
Minor
Reporter:
Stephen Connolly
https://github.com/jenkinsci/github-branch-source-plugin/blob/d60cc7617ee9ad56fd3ea3a3c3ad2569dc07c827/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L1163 the regex "^PR-(d+)(.)?$" includes {} in the second matching group which means PR-11-HEAD will never match the strategy of HEAD as the second matching group includes the {}. Just need to do something like "^PR(d+)(:?-(.))?$" (if I can remember my regex for non-matching groups correctly)
Add Comment
[JIRA] (JENKINS-46785) Add a way to disable all reporters (and selectively enable a few)
Title: Message Title olamy commented on JENKINS-46785 Re: Add a way to disable all reporters (and selectively enable a few) Cyrille Le Clerc sorry for the late reply but works fine! 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-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title Emilio Escobar commented on JENKINS-49931 Re: Heap Histogram Collection Destabilizes Masters https://github.com/jenkinsci/support-core-plugin/pull/134 already available for 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-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title Emilio Escobar updated JENKINS-49931 Jenkins / JENKINS-49931 Heap Histogram Collection Destabilizes Masters Change By: Emilio Escobar 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-49946) input step cannot access environment blocks
Title: Message Title
Andreas Klemp created an issue
Jenkins / JENKINS-49946
input step cannot access environment blocks
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-03-06 09:54
Environment:
Jenkins 2.89.4
Labels:
pipeline input environment
Priority:
Minor
Reporter:
Andreas Klemp
The input step in declarative pipeline (JENKINS-48379) cannot access the environment blocks. Thus, dynamic data (e.g. version number) cannot be used in the input dialog. Also defining options in the input and checking the result requires redundant values, because they cannot be reused.
Access to $JOB_NAME and ${env.JOB_NAME} is working.
Access to $myVar is not working. It leads to a "no such property" exception. It doesn't matter if the variable is declared in the global or stage-local environment block.
Access to ${env.myVar} is not working. The value is null. It doesn't matter if the variable is declared in the global or stage-local environment block.
[JIRA] (JENKINS-44568) Gerrit Trigger version 23.2 fails to trigger Jenkins jobs on Jenkins version 2.46.3!!!
Title: Message Title Martin Wiklundh commented on JENKINS-44568 Re: Gerrit Trigger version 23.2 fails to trigger Jenkins jobs on Jenkins version 2.46.3!!! Any progress on this? Any way to test some of the suggested solutions? 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-49947) unclear usage of input step in declarative pipeline
Title: Message Title Andreas Klemp created an issue Jenkins / JENKINS-49947 unclear usage of input step in declarative pipeline Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-03-06 10:08 Environment: Jenkins 2.89.4 Labels: pipeline input when environment Priority: Minor Reporter: Andreas Klemp How is the input step intended to be used in a declarative pipeline using a separate block (JENKINS-48379)? There are several issues with this. The result of the input can only be used in the current stage. Thus, it is not possible to skip multiple stages or use the input value in multiple stages. input and when cannot be combined in all cases. Currently, the result of input can be used in when to skip the stage (cool!). However, if the stage is skipped because of some other criteria, the input is still requested. input cannot be used inside the stage steps as a workaround because the agent would be blocked and it cannot be separated to two steps (approval without agent, handling with agent) because the input result is stage-local. If I missed something and the issues can be solved, it would be nice to know and the documentation should be more clear about this. Currently, it seems impossible to create a declarative pipeline with a manual approval step befo
[JIRA] (JENKINS-47744) xcodebuild export step fails due to empty exportPlist
Title: Message Title Tony Ru edited a comment on JENKINS-47744 Re: xcodebuild export step fails due to empty exportPlist We also have this problem but I found out that in the github repository the exportOptions.plist is already updated with new needed fields ... months ago ... but I wonder why the changes becomes not deployed? Is it possible to build the plugin manually?See this commit:[https://github.com/jenkinsci/xcode-plugin/commit/3937e54f3c0a761528e038668471ef65a545aa99] edit: sorry that was the wrong linkI found the fixed here:[https://github.com/jenkinsci/xcode-plugin/pull/87/commits/09fc94fa0783e6b7f111e3e979fb37ccaefdeeed] still hoping to have it integrated soon 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-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49632 Re: Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts") Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/GeneratedArtifactsPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/PipelineGraphPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtils.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/publishers/GeneratedArtifactsReporterTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtilsTest.java jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/maven-spy-deploy-jar.xml http://jenkins-ci.org/commit/pipeline-maven-plugin/e53f09f5ff94381a21270e9416349f887bcc367a Log: JENKINS-49632 Also record generated attached artifacts Compare: https://github.com/jenkinsci/pipeline-maven-plugin/compare/00a6ba422a68...e53f09f5ff94 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-49913) email-ext: check for attachment size does not consider compression
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49913 Re: email-ext: check for attachment size does not consider compression Code changed in jenkins User: David van Laatum Path: src/main/java/hudson/plugins/emailext/AttachmentUtils.java src/main/java/hudson/plugins/emailext/SizedDataSource.java src/main/java/hudson/plugins/emailext/plugins/ZipDataSource.java src/test/java/hudson/plugins/emailext/AttachmentUtilsTest.java http://jenkins-ci.org/commit/email-ext-plugin/1cde3b10372c11a2b010f25c1d99092d248ed7ae Log: JENKINS-49913 check for attachment size does not consider compression 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-49913) email-ext: check for attachment size does not consider compression
Title: Message Title David van Laatum resolved as Fixed Jenkins / JENKINS-49913 email-ext: check for attachment size does not consider compression Change By: David van Laatum Status: Open 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-49904) workflow-cps groovy engine hijacks closure.rehydrate()
Title: Message Title Gustaf Lundh commented on JENKINS-49904 Re: workflow-cps groovy engine hijacks closure.rehydrate() Jesse Glick: Sorry for pinging you, but we are currently building a groovy framework/backend for pipeline jobs. The framework would allow our end users to setup and manage extremely complex pipelines, consisting of 100's of projects (and allow them to this in an reasonable easy way). Our original vision was very dependent on a working rehydrate() functionality. So before we restart the design work, I would like to know if you think this issue will be fixed within a reasonable timeframe (or if Cloudbees was already aware of the issue). Or perhaps this behaviour is by design? The Groovy and Cps implementation is still a bit too alien to allow me to fix the issue myself within a sensible timeframe. 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-49929) Regression: Log fails to auto update in karaoke mode
Title: Message Title Josh McDonald updated JENKINS-49929 Jenkins / JENKINS-49929 Regression: Log fails to auto update in karaoke mode Change By: Josh McDonald 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-49929) Regression: Log fails to auto update in karaoke mode
Title: Message Title Josh McDonald commented on JENKINS-49929 Re: Regression: Log fails to auto update in karaoke mode PR: https://github.com/jenkinsci/blueocean-plugin/pull/1686 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-46785) Add a way to disable all reporters (and selectively enable a few)
Title: Message Title Cyrille Le Clerc updated JENKINS-46785 Solved in 3.4.0 Jenkins / JENKINS-46785 Add a way to disable all reporters (and selectively enable a few) Change By: Cyrille Le Clerc Status: In Review 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-49702) JTable produces a console warning
Title: Message Title Thorsten Scherler assigned an issue to Thorsten Scherler Jenkins / JENKINS-49702 JTable produces a console warning Change By: Thorsten Scherler Assignee: Thorsten Scherler 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-49702) JTable produces a console warning
Title: Message Title Thorsten Scherler started work on JENKINS-49702 Change By: Thorsten Scherler 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-49702) JTable produces a console warning
Title: Message Title
Thorsten Scherler updated an issue
Jenkins / JENKINS-49702
JTable produces a console warning
Change By:
Thorsten Scherler
https://github.com/jenkinsci/blueocean-plugin/blob/b16ea72cc449c44478e696930c1a078bff727906/jenkins-design-language/src/js/components/jtable/JTable.jsx#L136is causing: {code}Warning: Unknown prop `columns` on tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-propin div (created by JTable)in JTable (created by PlaceholderTable)in div (created by PlaceholderTable)in PlaceholderTable (created by DashboardPlaceholder)in div (created by DashboardPlaceholder)in DashboardPlaceholder (created by CJOCTeams)in article (created by CJOCPage)in main (created by CJOCPage)in div (created by Page)in Page (created by CJOCPage)in CJOCPage (created by CJOCTeams)in CJOCTeams (created by CJOCTeamsWrapper)in div (created by CJOCTeamsWrapper)in CJOCTeamsWrapper (created by Unknown)in Unknown{code} !Screenshot_2018-02-22_20-02-56.png|thumbnail!Testing notes:Needs manual testing on e.g. storybook jtable story and see whether the above error is not present anymore.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49948) vulnerabilities in bo js dependencies
Title: Message Title Thorsten Scherler created an issue Jenkins / JENKINS-49948 vulnerabilities in bo js dependencies Issue Type: Improvement Assignee: Thorsten Scherler Components: blueocean-plugin Created: 2018-03-06 11:26 Priority: Minor Reporter: Thorsten Scherler 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 Gr
[JIRA] (JENKINS-46336) Sidecar docker containers for declarative
Title: Message Title Christopher Orr commented on JENKINS-46336 Re: Sidecar docker containers for declarative Duplicate of JENKINS-41581? 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-49948) vulnerabilities in bo js dependencies
Title: Message Title Thorsten Scherler started work on JENKINS-49948 Change By: Thorsten Scherler 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-49948) vulnerabilities in bo js dependencies
Title: Message Title Thorsten Scherler updated JENKINS-49948 Jenkins / JENKINS-49948 vulnerabilities in bo js dependencies Change By: Thorsten Scherler 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-49702) JTable produces a console warning
Title: Message Title Thorsten Scherler updated JENKINS-49702 Jenkins / JENKINS-49702 JTable produces a console warning Change By: Thorsten Scherler 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-48687) Bitbucket Branch Source Plugin: changes are missing for builds again
Title: Message Title
James Hogarth commented on JENKINS-48687
Re: Bitbucket Branch Source Plugin: changes are missing for builds again
So this bit us on our test instance today, when evaluating some global library changes. A little bit of poking shows it to be a "regression" from this issue: https://issues.jenkins-ci.org/browse/JENKINS-42518 It looks like when there's only a lightweight checkout (to just grab the Jenkinsfile for processing) then currentBuild.changeSets does not get populated. It appears to be sufficient to do an
scm checkout
at any point before poking currentBuild.changeSets (even outside of a stage to make it invisible in the background).
node {
deleteDir()
checkout scm
deleteDir()
}
stage("do stuff") {
echo currentBuild.changeSets
}
Doing something like that, so checking changesets happens after a full checkout, "works" as a workaround at the cost of the weight of the checkout. Presumably the Bitbucket api or something will need to be poked if there's only a lightweight checkout happening as part of BitbucketSCMFile to populate the variable properly when there is no full checkout yet.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-45856) support view Mask filters with wildcards
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-45856 support view Mask filters with wildcards Change By: Karl Wirth Labels: P4_VERIFY 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-45856) support view Mask filters with wildcards
Title: Message Title Karl Wirth commented on JENKINS-45856 Re: support view Mask filters with wildcards Would also be good if we could have nested wildcards. For example: //depot//bin/... 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-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")
Title: Message Title Cyrille Le Clerc commented on JENKINS-49632 Re: Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts") Shipped in 3.4.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-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-49632 Re: Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts") Shipped in 3.4.1 .[~dantran] can you please confirm? 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-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Jenkins / JENKINS-49632 Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts") Change By: Cyrille Le Clerc Status: Open Closed Assignee: Alvaro Lobato Cyrille Le Clerc 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-48737) Provide lightweight checkouts for Bitbucket Pull Requests
Title: Message Title Roman Bolshakov edited a comment on JENKINS-48737 Re: Provide lightweight checkouts for Bitbucket Pull Requests Lightweight checkouts would might help to work-around JENKINS-45997 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 Roman Bolshakov commented on JENKINS-48737 Re: Provide lightweight checkouts for Bitbucket Pull Requests Lightweight checkouts would help to work-around JENKINS-45997 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-49949) Create combined graphs with multiple tests from a group or file
Title: Message Title Tobias Lingemann created an issue Jenkins / JENKINS-49949 Create combined graphs with multiple tests from a group or file Issue Type: Improvement Assignee: Eugene Schava Attachments: Example.jpg Components: perfpublisher-plugin Created: 2018-03-06 12:57 Priority: Minor Reporter: Tobias Lingemann There should be an option to create a singular graph that combines all values from a group or file. For reference take a look at the attached example that is created with the plot plugin. Right now the graphs only contain one test. When looking at how the performance of individual tests has developed over time, this is very cumbersome. It is better to have ten graphs where each graph contains ten tests, than to have 100 graphs where each graph only contains one test. Add Comment
[JIRA] (JENKINS-49950) Specifying Docker registry credentials should not silently fail if using default URL
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-49950 Specifying Docker registry credentials should not silently fail if using default URL Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-03-06 13:11 Priority: Minor Reporter: Christopher Orr In a folder, under Pipeline Model Definition, you can enter the details for accessing a Docker registry. Since I'm using private repositories on Docker Hub, I don't need to change the default Docker Registry URL (the help text says it "May be left blank to use the public DockerHub registry") — I should only need to set the correct Registry Credentials. However, if you only set the Registry Credentials, they are not used during a build — the "https://index.docker.io/v1/" URL has to be explicitly entered in order to apply the credentials using a build. It looks like this is where the logic is: https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/472688704e/pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/agent/impl/AbstractDockerPipelineScript.groovy#L61-L68 Add Comment
[JIRA] (JENKINS-49951) jira-plugin pct issues
Title: Message Title Isa Vilacides updated an issue Jenkins / JENKINS-49951 jira-plugin pct issues Change By: Isa Vilacides Issue Type: Task Bug 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-49951) jira-plugin pct issues
Title: Message Title Isa Vilacides created an issue Jenkins / JENKINS-49951 jira-plugin pct issues Issue Type: Task Assignee: Isa Vilacides Components: jira-plugin Created: 2018-03-06 13:29 Priority: Minor Reporter: Isa Vilacides When running the jira-plugin pct I get the following errors: PCT version = master [INFO] Building Jenkins JIRA plugin 2.4.2 [INFO] [INFO] Downloading: https://nexus-internal.cloudbees.com/content/groups/staged/org/jenkins-ci/plugins/workflow/workflow-step-api/2.14/workflow-step-api-2.14-tests.jar [INFO] Downloading: https://nexus-internal.cloudbees.com/content/groups/staged/org/jenkins-ci/main/jenkins-war/2.89.3-cb-1/jenkins-war-2.89.3-cb-1.executable-war [INFO] Downloaded: https://nexus-internal.cloudbees.com/content/groups/staged/org/jenkins-ci/plugins/workflow/workflow-step-api/2.14/workflow-step-api-2.14-tests.jar (29 KB at 87.1 KB/sec) [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.032 s [INFO] Finished at: 2018-03-02T11:48:23+00:00 [INFO] Final Memory: 35M/803M [INFO] [ERROR] Failed to execute goal on project jira: Could not resolve dependencies for project org.jenkins-ci.plugins:jira:hpi:2.4.2: Could not find artifact org.jenkins-ci.main:jenkins-war:executable-war:2.89.3-cb-1 in cloudbees-internal (https://nexus-internal.cloudbees.com/content/groups/staged/) -> [Help 1] [ERROR]
[JIRA] (JENKINS-49951) jira-plugin pct issues
Title: Message Title Isa Vilacides started work on JENKINS-49951 Change By: Isa Vilacides 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-49951) jira-plugin pct issues
Title: Message Title Isa Vilacides commented on JENKINS-49951 Re: jira-plugin pct issues After changes I have executed all the plugin unit tests and it works well. Then I have executed the tests with the PCT and the tests run now, although they fail. Creating a followup ticket. 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-49951) jira-plugin pct issues
Title: Message Title Isa Vilacides updated JENKINS-49951 Jenkins / JENKINS-49951 jira-plugin pct issues Change By: Isa Vilacides 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-49952) Groovy post-build script in matrix job throws exception
Title: Message Title John David created an issue Jenkins / JENKINS-49952 Groovy post-build script in matrix job throws exception Issue Type: Bug Assignee: Daniel Heid Components: postbuildscript-plugin Created: 2018-03-06 13:37 Environment: Jenkins: 2.89.4 Matrix 1.12 PostBuildScript: 2.5.1 Priority: Major Reporter: John David I added an 'Execute Scripts on Matrix' post build step. This exception also occurs with 'Execute Scripts' post build step. I added a groovy script file with a simple println statement and ran the job. [PostBuildScript] - Problem occurred: java.lang.IllegalStateException: maybe need to rebuild plugin? at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.get(ScriptApproval.java:99) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.configuring(SecureGroovyScript.java:126) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.configuringWithNonKeyItem(SecureGroovyScript.java:150) at org.jenkinsci.plugins.postbuildscript.service.GroovyScriptExecutor.call(GroovyScriptExecutor.java:54) at org.jenkinsci.plugins.postbuildscript.service.GroovyScriptExecutor.call(GroovyScriptExecutor.java:17) at hudson.remoting.UserRequest.perform(UserRequest.java:207) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:358) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to bldsvr03 at hudson
[JIRA] (JENKINS-48030) SAML Azure AD exception
Title: Message Title Jamie commented on JENKINS-48030 Re: SAML Azure AD exception Ivan Fernandez Calvo My configuration also uses a GUID, in the first format style. Not my area but isn't this feature something to do with if you are, say, building a hosted application which allows multiple Azure AD users to utilise 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-42973) User cannot create new Pipeline and locate it in a specific folder
Title: Message Title Matt Aizcorbe commented on JENKINS-42973 Re: User cannot create new Pipeline and locate it in a specific folder I see this issue was closed and while I completely understand the logic behind the decision it creates an issue for those that are using the role-based access strategy. We manage a Jenkins instance that serves many teams and we've created a scheme where we create a folder for each team and then create a role allowing access to that folder. This gives each team their own workspace for managing jobs and credentials. This scheme necessarily means that teams can't create jobs at the root level and thus they can't leverage this VERY useful capability. We are huge advocates for the new pipeline method and want to lower the barrier of entry for those that are used to the point and click capability of freestyle jobs. I haven't figured out another authorization scheme that is manageable given the number of teams we support. I'd welcome any suggestions. 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-48030) SAML Azure AD exception
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-48030 Re: SAML Azure AD exception I do not have all the context but the first is tenant-specific and the second one is tenant-independent, I am not sure if this token can change or not in the first choice. 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-49953) jenkins gives Bad Request page mostly while trying to change configuration of a job
Title: Message Title Ankit Rathore created an issue Jenkins / JENKINS-49953 jenkins gives Bad Request page mostly while trying to change configuration of a job Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-03-06 13:48 Priority: Critical Reporter: Ankit Rathore I have recently upgraded to jenkins 2.89.4 from 2.46.2. Prevoiusly it was running with jdk7 now it is jdk8. Upgrade went well, everything looks working but when I try to change the configuration of any job it gives below error page with HTTP 400 response: Bad Request Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit. Cookie /n Apache/2.2.15 (CentOS) Server at node0.morado.com Port 443 I did delete the cookies and refreshed the page. It get loaded with the desired contents but again within a minute it gives the same HTTP 400 response as above. Does anybody know what is wrong here?
[JIRA] (JENKINS-49953) jenkins gives Bad Request page mostly while trying to change configuration of a job
Title: Message Title
Ankit Rathore updated an issue
Jenkins / JENKINS-49953
jenkins gives Bad Request page mostly while trying to change configuration of a job
Change By:
Ankit Rathore
I have recently upgraded to jenkins 2.89.4 from 2.46.2. Prevoiusly it was running with jdk7 now it is jdk8.Upgrade went well, everything looks working but when I try to change the configuration of any job it gives below error page with HTTP 400 response: {code:java}Bad RequestYour browser sent a request that this server could not understand.Size of a request header field exceeds server limit.Cookie/nApache/2.2.15 (CentOS) Server at node0.morado.com Port 443{code}I did delete the cookies and refreshed the page. It get loaded with the desired contents but again within a minute it gives the same HTTP 400 response as above. I have referred the existing JIRA [JENKINS-25046|https://issues.jenkins-ci.org/browse/JENKINS-25046]. But that solves the issue temporarily. Does anybody know what is wrong here?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49953) jenkins gives Bad Request page mostly while trying to change configuration of a job
Title: Message Title
Ankit Rathore updated an issue
Jenkins / JENKINS-49953
jenkins gives Bad Request page mostly while trying to change configuration of a job
Change By:
Ankit Rathore
I have recently upgraded to jenkins 2.89.4 from 2.46.2. Prevoiusly it was running with jdk7 now it is jdk8.Upgrade went well, everything looks working but when I try to change the configuration of any job it gives below error page with HTTP 400 response: {code:java}Bad RequestYour browser sent a request that this server could not understand.Size of a request header field exceeds server limit.Cookie/nApache/2.2.15 (CentOS) Server at node0.morado.com Port 443{code}I did delete the cookies and refreshed the page. It get loaded with the desired contents but again within a minute it gives the same HTTP 400 response as above. * I have referred the existing JIRA [ JENKINS-25046 |https://issues . jenkins-ci.org/browse/JENKINS-25046]. But that solves the issue temporarily. * Does anybody know what is wrong here?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49840) When Wipe out repository & force clone is selected, single branch checkout does not happen
Title: Message Title Harisha MG closed an issue as Not A Defect Yes, the steps which we followed is the same and the solution provided is working. Thank you for quick resolution Jenkins / JENKINS-49840 When Wipe out repository & force clone is selected, single branch checkout does not happen Change By: Harisha MG Status: Resolved Closed 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-49953) jenkins gives Bad Request page mostly while trying to change configuration of a job
Title: Message Title
Ankit Rathore updated an issue
Jenkins / JENKINS-49953
jenkins gives Bad Request page mostly while trying to change configuration of a job
Change By:
Ankit Rathore
I have recently upgraded to jenkins 2.89.4 from 2.46.2. Prevoiusly it was running with jdk7 now it is jdk8.Upgrade went well, everything looks working but when I try to change the configuration of any job it gives below error page with HTTP 400 response: {code:java}Bad RequestYour browser sent a request that this server could not understand.Size of a request header field exceeds server limit.Cookie/nApache/2.2.15 (CentOS) Server at node0.morado.com Port 443{code}I did delete the cookies and refreshed the page. It get loaded with the desired contents but again within a minute it gives the same HTTP 400 response as above.*I have referred the existing JIRA JENKINS-25046. But that solves the issue temporarily.*Does anybody know what is wrong here? Java Detail:{code:java}openjdk version "1.8.0_141"OpenJDK Runtime Environment (build 1.8.0_141-b16)OpenJDK 64-Bit Server VM (build 25.141-b16, mixed mode) {code}OS : {code:java}CentOS release 6.2 (Final){code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48030) SAML Azure AD exception
Title: Message Title Jamie commented on JENKINS-48030 Re: SAML Azure AD exception Ivan Fernandez Calvo I see. I have made a note of the value for my system and I will check back every few days to see if it has changed. I'll report back in a week or so I guess? 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-49802) Unable to return list of repositories from BitBucket Cloud
Title: Message Title Brandon Ankney closed an issue as Not A Defect There were multiple issues occurring causing this. A very large repository, an underpowered VM and a Bitbucket service outage. I don't think there's anything for the plugin teams to work on and I'm closing this as such. Jenkins / JENKINS-49802 Unable to return list of repositories from BitBucket Cloud Change By: Brandon Ankney 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 I
[JIRA] (JENKINS-49697) Single quote in credentials password causing job crash
Title: Message Title Yahav Itzhak commented on JENKINS-49697 Re: Single quote in credentials password causing job crash Ovidiu-Florin Bogdan, Thanks for reporting this issue. We fixed this issue. You can find a snapshot version in HAP-1039 We would appreciate your feedback for 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-47201) ConcurrentModificationException when serializing MultiSCMRevisionState#revisionStates
Title: Message Title Jesse Glick updated JENKINS-47201 Jenkins / JENKINS-47201 ConcurrentModificationException when serializing MultiSCMRevisionState#revisionStates Change By: Jesse Glick 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-47201) ConcurrentModificationException when serializing MultiSCMRevisionState#revisionStates
Title: Message Title Jesse Glick updated JENKINS-47201 Jenkins / JENKINS-47201 ConcurrentModificationException when serializing MultiSCMRevisionState#revisionStates Change By: Jesse Glick Status: Reopened 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-47201) ConcurrentModificationException when serializing MultiSCMRevisionState#revisionStates
Title: Message Title Jesse Glick assigned an issue to Martin Nowak Jenkins / JENKINS-47201 ConcurrentModificationException when serializing MultiSCMRevisionState#revisionStates Change By: Jesse Glick Assignee: Martin Nowak 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-47201) ConcurrentModificationException when serializing MultiSCMRevisionState#revisionStates
Title: Message Title Jesse Glick started work on JENKINS-47201 Change By: Jesse Glick 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-49697) Single quote in credentials password causing job crash
Title: Message Title Yahav Itzhak edited a comment on JENKINS-49697 Re: Single quote in credentials password causing job crash [~ovidiub13],Thanks for reporting this issue.We fixed this issue. You can find a snapshot version in [HAP-1039|https://www.jfrog.com/jira/browse/HAP-1039] . We would appreciate your feedback for 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-42567) si viewproject gets stuck (sometimes) while checking out Integrity project
Title: Message Title Alex Ruff updated an issue Jenkins / JENKINS-42567 si viewproject gets stuck (sometimes) while checking out Integrity project Change By: Alex Ruff Attachment: PTCLogCheckoutFailedMod.txt 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-49840) When Wipe out repository & force clone is selected, single branch checkout fails (refspec ignored)
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-49840 When Wipe out repository & force clone is selected, single branch checkout fails (refspec ignored) Change By: Mark Waite Summary: When Wipe out repository & force clone is selected, single branch checkout does not happen fails (refspec ignored) 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title rsandell assigned an issue to rsandell Jenkins / JENKINS-48061 git plugin 3.6.4 regression with shared libraries Change By: rsandell Assignee: Stephen Connolly rsandell 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-25519) Rethrown NumberFormatException from exitStatus can cause DurableTaskStep.Execution.check to retry indefinitely
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25519 Re: Rethrown NumberFormatException from exitStatus can cause DurableTaskStep.Execution.check to retry indefinitely Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/durabletask/BourneShellScript.java src/main/java/org/jenkinsci/plugins/durabletask/FileMonitoringTask.java src/main/java/org/jenkinsci/plugins/durabletask/WindowsBatchScript.java http://jenkins-ci.org/commit/durable-task-plugin/21f570e9e6ec92c1b53f3a7e3d872fcd78693ae2 Log: Merge pull request #66 from svanoort/better-fix-to-exitStatus Better fix to JENKINS-25519 – avoid errors when trying to read exitStatus from durable task before finished writing Compare: https://github.com/jenkinsci/durable-task-plugin/compare/5133350aae6f...21f570e9e6ec 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-49927) Add editor ATH coverage for editing an already-existing Jenkinsfile
Title: Message Title Karl Shultz assigned an issue to Karl Shultz Jenkins / JENKINS-49927 Add editor ATH coverage for editing an already-existing Jenkinsfile Change By: Karl Shultz Assignee: Karl Shultz 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-49928) Add editor ATH coverage for changing agent settings in a Jenkinsfile
Title: Message Title Karl Shultz assigned an issue to Karl Shultz Jenkins / JENKINS-49928 Add editor ATH coverage for changing agent settings in a Jenkinsfile Change By: Karl Shultz Assignee: Karl Shultz 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-49954) sh inside container closure waits up to 1 minute
Title: Message Title
benjamin mack created an issue
Jenkins / JENKINS-49954
sh inside container closure waits up to 1 minute
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-03-06 14:55
Priority:
Minor
Reporter:
benjamin mack
Hi, first of all sorry if this an allready known issue or a stupid config by myself. Since i updated from the kubernetes plugin 1.2.1 to 1.3.1 (skipped 1.3) i face the following: doing an sh outside any container closure ( aka jnlp) the sh (simple ls in my example) is excuted instantly. The moment i am inside the container closure it seems to wait about one minute before it executes the sh, for every sh within any container. Switching back to 1.2.1 helped me. using these example calls:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml//with dis example configuration
...
def sdf = new java.text.SimpleDateFormat("MM/dd/ HH:mm:ss")
println "#before# "+sdf.format(new Date())
sh 'ls -lna'
println "#after# "+sdf.format(new Date())
println "#before# "+sdf.format(new Date())
sh 'ls -lna'
println "#after# "+sdf.format(new Date())
container('jnlp')
{
println "#before# "+sdf.format(new Date())
sh 'ls -lna'
println "#after# "+sdf.format(new Date())
println "#before# "+sdf.format(new Date())
sh 'ls -lna'
println "#after# "+sdf.format(new Date())
}
...
[JIRA] (JENKINS-49954) sh inside container closure waits up to 1 minute
Title: Message Title
benjamin mack updated an issue
Jenkins / JENKINS-49954
sh inside container closure waits up to 1 minute
Change By:
benjamin mack
Hi, first of all sorry if this an allready known issue or a stupid config by myself.Since i updated from the kubernetes plugin 1.2.1 to 1.3.1 (skipped 1.3) i face the following: doing an sh outside any container closure ( aka jnlp) the sh (simple ls in my example) is excuted instantly. The moment i am inside the container closure it seems to wait about one minute before it executes the sh, for every sh within any container.Switching back to 1.2.1 helped me. using these example calls:{code java } Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml// with dis this example configuration ... def sdf = new java.text.SimpleDateFormat("MM/dd/ HH:mm:ss") println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) container('jnlp') { println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) } ...{code}I get the follwoing output[Pipeline] echo{color:#14892c}#before# 03/06/2018 14:36:42{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#14892c}#after# 03/06/2018 14:36:44{color}[Pipeline] echo{color:#14892c}#before# 03/06/2018 14:36:44{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#14892c}#after# 03/06/2018 14:36:44{color}[Pipeline] container[Pipeline] \{[Pipeline] echo{color:#ff}#before# 03/06/2018 14:36:44{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#ff}#after# 03/06/2018 14:38:01{color}[Pipeline] echo{color:#ff}#before# 03/06/2018 14:38:01{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 40
[JIRA] (JENKINS-49786) Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up
Title: Message Title Mark Waite resolved as Not A Defect This is behaving as expected. Declarative Pipeline (which is what you are using) begins with an implicit checkout of the repository using the repository definition from the Jenkins job. In your case, the implicit checkout will create a branch named "wrong" in the workspace at the most recent commit on the origin/develop branch. Refer to skipDefaultCheckout in the Declarative Pipeline options if you do not need the default checkout. The default checkout does not seem useful in your example since the checkout in the Jenkinsfile is reusing the workspace directory. Most Declarative Pipeline users use the default checkout to avoid cluttering the Jenkinsfile with a checkout definition. If additional checkout calls are needed, they are typically performed into new subdirectories of the workspace. If you want the branch name in the implicit checkout to match the name provided in "Branches to build", the online help says to either leave the field blank or use the value '**'. Jenkins / JENKINS-49786 Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-49954) sh inside container closure waits up to 1 minute
Title: Message Title
benjamin mack updated an issue
Jenkins / JENKINS-49954
sh inside container closure waits up to 1 minute
Change By:
benjamin mack
Hi, first of all sorry if this an allready known issue or a stupid config by myself.Since i updated from the kubernetes plugin 1.2.1 to 1.3.1 (skipped 1.3) i face the following: doing an sh outside any container closure ( aka jnlp) the sh (simple ls in my example) is excuted instantly. The moment i am inside the container closure it seems to wait about one minute before it executes the sh, for every sh within any container.Switching back to 1.2.1 helped me. using these example calls:{code java }with this example configuration ... def sdf = new java.text.SimpleDateFormat("MM/dd/ HH:mm:ss") println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) container('jnlp') { println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) } ...{code}I get the follwoing output[Pipeline] echo{color:#14892c}#before# 03/06/2018 14:36:42{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#14892c}#after# 03/06/2018 14:36:44{color}[Pipeline] echo{color:#14892c}#before# 03/06/2018 14:36:44{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#14892c}#after# 03/06/2018 14:36:44{color}[Pipeline] container[Pipeline] \{[Pipeline] echo{color:#ff}#before# 03/06/2018 14:36:44{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#ff}#after# 03/06/2018 14:38:01{color}[Pipeline] echo{color:#ff}#before# 03/06/2018 14:38:01{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#ff}#after# 03/06/2018 14:39:18{color}[Pipeline] }[Pipeline] // container
[JIRA] (JENKINS-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49931 Re: Heap Histogram Collection Destabilizes Masters Code changed in jenkins User: Emilio Escobar Path: src/main/java/com/cloudbees/jenkins/support/impl/HeapUsageHistogram.java http://jenkins-ci.org/commit/support-core-plugin/a3ff0c7e985b0ecb9a4460bab94932bc55a17b6a Log: [FIXED JENKINS-49931] DISABLED by default 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-49786) Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-49786 Jenkins uses the same directory for Jenkinsfile pull and project workspace, branches are mixed up 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-49955) Publish always publishing unchanged utf8+w files on Windows slaves.
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-49955 Publish always publishing unchanged utf8+w files on Windows slaves. Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2018-03-06 15:14 Environment: P4-Jenkins 1.8.4 P4D -C1 P4D/LINUX26X86_64/2017.2/1611521 Priority: Major Reporter: Karl Wirth Reproduction steps: (1) Add utf8+w file with BOM on Linux -C1 server. (2) Setup master Jenkins server on Linux (may not be relevant) (3) Set up build slave on WIndows 10. (4) Setup a Freestyle job (for ease; also happens on pipeline) that syncs a workspace containing the utf8+w file and publishes any changed files that is pinned to run on Windows 10 slave. (5) Run the job. Reconcile will always detect the utf8+w file as a file to publish. For example: ... p4 opened -Cjenkins-Windows10-Freestyle_c1-0 //jenkins-Windows10-Freestyle_c1-0/... + ... ... edit //depot/project1/test.ps1 ... submitting files (6) At the command line 'p4 reconcile -a -e -f' does not detect files as changed. For example: C:\Users\karl\AppData\Local\Temp\workspace\Freestyle_c1>p4 -p C1_server:1667 -u super -c jenkins-Windows10-Freestyle_c1-0 reconcile -e -a -f //jenkins-Windows10-Freestyle_c1-0/... //jenkins-Windows10-Freestyle_c1-0/... - no file(s) to reconcile.
[JIRA] (JENKINS-49955) Publish always publishing unchanged utf8+w files on Windows slaves.
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-49955 Publish always publishing unchanged utf8+w files on Windows slaves. Change By: Karl Wirth Labels: P4_VERIFY 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-49943) memory issue (RAM)with jenkins server
Title: Message Title Rob Petti updated an issue Jenkins / JENKINS-49943 memory issue (RAM)with jenkins server Change By: Rob Petti Component/s: core Component/s: perforce-plugin 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-49943) memory issue (RAM)with jenkins server
Title: Message Title Rob Petti assigned an issue to Unassigned Jenkins / JENKINS-49943 memory issue (RAM)with jenkins server Change By: Rob Petti Assignee: Rob Petti 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-49349) git scm plugin attempts to checkout stale SHAs
Title: Message Title Kevin R. commented on JENKINS-49349 Re: git scm plugin attempts to checkout stale SHAs bump 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-49816) swarm node says connected succesffuly, but master has placed it offline
Title: Message Title Alex Gray commented on JENKINS-49816 Re: swarm node says connected succesffuly, but master has placed it offline Unfortunately, those are the only logs. I am spinning up pretty hefty AWS spotinstances (c4.xlarge) when this happens. Out of 1000 spin ups from the same AMI, I get a few of these failures. Most of our "regular" nodes are t2.small and they don't have any issues, but we only spin up a few of those per month, so it's probably not related to any type of load. We also have newrelic metrics and there is no load when this is happening. The workaround is pretty easy: I have a cron that runs every 5 minutes and if the last line in the log is not "INFO: Connected" after a few minutes, I restart the swarm jar and it works. I would rate this ticket as "low priority", since it's easy to detect and easy to workaround. 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-49931) Heap Histogram Collection Destabilizes Masters
Title: Message Title Emilio Escobar commented on JENKINS-49931 Re: Heap Histogram Collection Destabilizes Masters new https://github.com/jenkinsci/support-core-plugin/pull/135 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-49954) sh inside container closure waits up to 1 minute
Title: Message Title benjamin mack commented on JENKINS-49954 Re: sh inside container closure waits up to 1 minute just faced the following: We use 2 jenkins instances (on for testing such as the above) and on for production -> on the test the downgrade to 1.2.1 worked on the prod not. so there must be some diference in configuration. I currently have absolutely no clue where to start looking for the cause 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-49954) sh inside container closure waits up to 1 minute
Title: Message Title benjamin mack edited a comment on JENKINS-49954 Re: sh inside container closure waits up to 1 minute just faced the following:We use 2 jenkins instances ( on one for testing such as the above) and on one for production -> on the test system the downgrade to 1.2.1 worked on the prod not -> same slow incontainer execution^^ .so there must be some diference in configuration.I currently have absolutely no clue where to start looking for the cause :( 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-44715) Pipeline plugin won't get updated PR github title
Title: Message Title Joe Harte commented on JENKINS-44715 Re: Pipeline plugin won't get updated PR github title Stephen Connolly Can you verify if this should be resolved? 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-49850) Run pre-release ATH against Jenkins Essentials bill-of-materials
Title: Message Title Oleg Nenashev commented on JENKINS-49850 Re: Run pre-release ATH against Jenkins Essentials bill-of-materials We are prototyping some bits for that together with Rebecca Ysteboe and Raul Arabaolaza. More news to come soon, maybe it can be reused 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-49797) IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM
Title: Message Title Saad Azam assigned an issue to PTC ALM Jenkins / JENKINS-49797 IllegalArgumentException while using JobDSL for creating pipeline and defining using integritySCM Change By: Saad Azam Assignee: Daniel Spilker PTC ALM 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-47498) Select compatible plugin versions using a BOM
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-47498 Select compatible plugin versions using a BOM Change By: Jesse Glick Labels: essentials 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-48578) Create BOM for components included into the Core
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-48578 Create BOM for components included into the Core Change By: Jesse Glick Labels: essentials 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-45047) Easy way to run integration tests in plugin repositories
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-45047 Easy way to run integration tests in plugin repositories Change By: Jesse Glick Labels: essentials 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-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49651 Extend plugin/update center metadata with known incompatibilities Change By: Jesse Glick Labels: api essentials update-center 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-32468) Pause script on sandbox rejection and give an admin a chance to approve & resume
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-32468 Pause script on sandbox rejection and give an admin a chance to approve & resume Change By: Jesse Glick Assignee: Jesse Glick 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-32468) Pause script on sandbox rejection and give an admin a chance to approve & resume
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32468 Pause script on sandbox rejection and give an admin a chance to approve & resume Change By: Jesse Glick Labels: essentials 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-49890) Allow inline script approvals for admins when looking at Pipeline logs
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-49890 Allow inline script approvals for admins when looking at Pipeline logs Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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-49954) sh inside container closure waits up to 1 minute
Title: Message Title
Carlos Sanchez updated an issue
Jenkins / JENKINS-49954
sh inside container closure waits up to 1 minute
Change By:
Carlos Sanchez
Hi, first of all sorry if this an allready known issue or a stupid config by myself.Since i updated from the kubernetes plugin 1.2.1 to 1.3.1 (skipped 1.3) i face the following: doing an sh outside any container closure ( aka jnlp) the sh (simple ls in my example) is excuted instantly. The moment i am inside the container closure it seems to wait about one minute before it executes the sh, for every sh within any container.Switching back to 1.2.1 helped me. using these example calls:{code}with this example configuration ... def sdf = new java.text.SimpleDateFormat("MM/dd/ HH:mm:ss") println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) container('jnlp') { println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) println "#before# "+sdf.format(new Date()) sh 'ls -lna' println "#after# "+sdf.format(new Date()) } ...{code}I get the follwoing output {code} [Pipeline] echo{color:#14892c}#before# 03/06/2018 14:36:42{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#14892c}#after# 03/06/2018 14:36:44{color}[Pipeline] echo{color:#14892c}#before# 03/06/2018 14:36:44{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#14892c}#after# 03/06/2018 14:36:44{color}[Pipeline] container[Pipeline] \{[Pipeline] echo{color:#ff}#before# 03/06/2018 14:36:44{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#ff}#after# 03/06/2018 14:38:01{color}[Pipeline] echo{color:#ff}#before# 03/06/2018 14:38:01{color}[Pipeline] sh[ces_simple-scheduler_master-UDJYA3VVM57YVGCAAPCPO6GWY2U32LN2MTKQTUHD3EANVLJ5HO4Q] Running shell script+ ls -lnatotal 8drwxr-xr-x 2 1 999 4096 Mar 6 14:36 .drwxr-xr-x 4 1 999 4096 Mar 6 14:36 ..[Pipeline] echo{color:#ff}#after# 03/06/2018 14:39:18{color}[Pipeline] }[Pipeline] // container {code}
[JIRA] (JENKINS-46642) Logs can grow without bound when using ansiColor plugin
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-46642 Logs can grow without bound when using ansiColor plugin Change By: Jesse Glick Component/s: 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.
