[JIRA] (JENKINS-50358) While downgrading Jenkins version 2.112 to 2.101 getting eror
Title: Message Title Priyanga G created an issue Jenkins / JENKINS-50358 While downgrading Jenkins version 2.112 to 2.101 getting eror Issue Type: Bug Assignee: Oleg Nenashev Attachments: Error.txt Components: core Created: 2018-03-23 05:47 Environment: Jenkins-2.101 OS:windows 7 web browser:chrome Priority: Major Reporter: Priyanga G Downgraded Jenkins version 2.112 to 2.101 through Jenkins (localhost:8080). After successful installed (Jenkins.war) Error page is showing Add Comment
[JIRA] (JENKINS-40152) Unable to provide credentials for scm sync configuration plguin in Jenkins 2.19
Title: Message Title sachin das edited a comment on JENKINS-40152 Re: Unable to provide credentials for scm sync configuration plguin in Jenkins 2.19 Craig Rodrigues Can this issue be fixed ? ,i'm facing this issue on Jenkins Version=2.105 please re-assign to the right person if you are not the one who has to resolve this n number of customers are facing the problem when they think about the jenkins backupmechanism. 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-40152) Unable to provide credentials for scm sync configuration plguin in Jenkins 2.19
Title: Message Title sachin das commented on JENKINS-40152 Re: Unable to provide credentials for scm sync configuration plguin in Jenkins 2.19 Can this issue be fixed ? ,i'm facing this issue on Jenkins Version=2.105 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-47415) DockerClient.version doesn't use build environment
Title: Message Title
Paul Eipper edited a comment on JENKINS-47415
Re: DockerClient.version doesn't use build environment
I have the same issue by just building an image and trying to get the reference to it:{code:title=Jenkinsfile}node(docker) {stage('Build image') {builtImage = docker.build("corp/api:1.0", ".")}}{code}The stack trace generated is:{code}(...)Successfully built 9a71968963a9Successfully tagged corp/api:1.0[Pipeline] dockerFingerprintFrom[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to zerg at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693) at hudson.remoting.UserResponse.retrieve(UserRequest.java:310) at hudson.remoting.Channel.call(Channel.java:908) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1053) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:296) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:277) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:274) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspect(DockerClient.java:198) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:218) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:129) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)Caused: java.io.IOException: Cannot run program "docker": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:249) at hudson.Proc$LocalProc.(Proc.java:218) at hudson.Launcher$LocalLauncher.launch(Launcher.java:930) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1299) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1260) 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:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}The environment is running with master macOS machine and a slave macOS machine.Only the slave has docker installed.The install location on the slave for the docker binary is in ` {{ /usr/local/bin ` }} , which is not by default in PATH.It is set as an extended extra variable on the executor configuration by setting an environment variable named ` {{
[JIRA] (JENKINS-47415) DockerClient.version doesn't use build environment
Title: Message Title
Paul Eipper commented on JENKINS-47415
Re: DockerClient.version doesn't use build environment
I have the same issue by just building an image and trying to get the reference to it:
Jenkinsfile
node(docker) {
stage('Build image') {
builtImage = docker.build("corp/api:1.0", ".")
}
}
The stack trace generated is:
(...)
Successfully built 9a71968963a9
Successfully tagged corp/api:1.0
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to zerg
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:310)
at hudson.remoting.Channel.call(Channel.java:908)
at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1053)
at hudson.Launcher$ProcStarter.start(Launcher.java:450)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:296)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:277)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:274)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspect(DockerClient.java:198)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:218)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:129)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
at hudson.security.ACL.impersonate(ACL.java:260)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Caused: java.io.IOException: Cannot run program "docker": error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at hudson.Proc$LocalProc.(Proc.java:249)
at hudson.Proc$LocalProc.(Proc.java:218)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:930)
at hudson.Launcher$ProcStarter.start(Launcher.java:450)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1299)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1260)
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
[JIRA] (JENKINS-47415) DockerClient.version doesn't use build environment
Title: Message Title
Paul Eipper edited a comment on JENKINS-47415
Re: DockerClient.version doesn't use build environment
I have the same issue by just building an image and trying to get the reference to it:{code:title=Jenkinsfile}node(docker) {stage('Build image') {builtImage = docker.build("corp/api:1.0", ".")}}{code}The stack trace generated is:{code}(...)Successfully built 9a71968963a9Successfully tagged corp/api:1.0[Pipeline] dockerFingerprintFrom[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to zerg at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693) at hudson.remoting.UserResponse.retrieve(UserRequest.java:310) at hudson.remoting.Channel.call(Channel.java:908) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1053) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:296) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:277) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:274) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspect(DockerClient.java:198) at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:218) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:129) at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)Caused: java.io.IOException: Cannot run program "docker": error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:249) at hudson.Proc$LocalProc.(Proc.java:218) at hudson.Launcher$LocalLauncher.launch(Launcher.java:930) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1299) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1260) 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:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}The environment is running with master macOS machine and a slave macOS , only machine.Only the slave has docker installed. The install location on the slave for the docker binary is in `/usr/local/bin`, which is not by default in PATH , but .It is set as an extended variable on the executor configuration by setting an environment variable named
[JIRA] (JENKINS-47415) DockerClient.version doesn't use build environment
Title: Message Title
Paul Eipper commented on JENKINS-47415
Re: DockerClient.version doesn't use build environment
I have the same issue by just building an image and trying to get the reference to it:
Jenkinsfile
node(docker) {
stage('Build image') {
builtImage = docker.build("corp/api:1.0", ".")
}
}
The stack trace generated is:
(...)
Successfully built 9a71968963a9
Successfully tagged corp/api:1.0
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to zerg
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:310)
at hudson.remoting.Channel.call(Channel.java:908)
at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1053)
at hudson.Launcher$ProcStarter.start(Launcher.java:450)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:296)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:277)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.launch(DockerClient.java:274)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspect(DockerClient.java:198)
at org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:218)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:129)
at org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
at hudson.security.ACL.impersonate(ACL.java:260)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Caused: java.io.IOException: Cannot run program "docker": error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at hudson.Proc$LocalProc.(Proc.java:249)
at hudson.Proc$LocalProc.(Proc.java:218)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:930)
at hudson.Launcher$ProcStarter.start(Launcher.java:450)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1299)
at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1260)
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
[JIRA] (JENKINS-50357) Garbled in picture
Title: Message Title jianheng liu created an issue Jenkins / JENKINS-50357 Garbled in picture Issue Type: Bug Assignee: Ognjen Bubalo Attachments: image-2018-03-23-11-59-56-287.png Components: jacoco-plugin Created: 2018-03-23 04:00 Priority: Major Reporter: jianheng liu Add Comment This
[JIRA] (JENKINS-45764) Add upload and download attachment steps
Title: Message Title Naresh Rayapati closed an issue as Fixed Jenkins / JENKINS-45764 Add upload and download attachment steps Change By: Naresh Rayapati 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-45764) Add upload and download attachment steps
Title: Message Title Naresh Rayapati commented on JENKINS-45764 Re: Add upload and download attachment steps Released with 1.4.0, the plugin should be available soon for installation on 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-49314) Allow configurable readTimeout for jira-steps-plugin
Title: Message Title Naresh Rayapati commented on JENKINS-49314 Re: Allow configurable readTimeout for jira-steps-plugin Released with 1.4.0, the plugin should be available soon for installation on 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-49314) Allow configurable readTimeout for jira-steps-plugin
Title: Message Title Naresh Rayapati closed an issue as Fixed Jenkins / JENKINS-49314 Allow configurable readTimeout for jira-steps-plugin Change By: Naresh Rayapati 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-50194) Build userId missing for a job being built by other Jobs
Title: Message Title Naresh Rayapati closed an issue as Fixed Jenkins / JENKINS-50194 Build userId missing for a job being built by other Jobs Change By: Naresh Rayapati 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-50194) Build userId missing for a job being built by other Jobs
Title: Message Title Naresh Rayapati commented on JENKINS-50194 Re: Build userId missing for a job being built by other Jobs Released with 1.4.0, the plugin should be available soon for installation on 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-50356) Update hugo theme to latest
Title: Message Title Naresh Rayapati updated JENKINS-50356 Jenkins / JENKINS-50356 Update hugo theme to latest Change By: Naresh Rayapati 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-50356) Update hugo theme to latest
Title: Message Title Naresh Rayapati commented on JENKINS-50356 Re: Update hugo theme to latest Updated and new site at https://jenkinsci.github.io/jira-steps-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-50356) Update hugo theme to latest
Title: Message Title Naresh Rayapati closed an issue as Fixed Jenkins / JENKINS-50356 Update hugo theme to latest Change By: Naresh Rayapati 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-50356) Update hugo theme to latest
Title: Message Title Naresh Rayapati updated JENKINS-50356 Jenkins / JENKINS-50356 Update hugo theme to latest Change By: Naresh Rayapati Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24141) SCM with non-AbstractProject, revisited
Title: Message Title David van Laatum closed an issue as Fixed Jenkins / JENKINS-24141 SCM with non-AbstractProject, revisited Change By: David van Laatum 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-49733) The email-ext-plugin Pipeline integration is not very ergonomic
Title: Message Title David van Laatum closed an issue as Fixed Jenkins / JENKINS-49733 The email-ext-plugin Pipeline integration is not very ergonomic Change By: David van Laatum 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-49913) email-ext: check for attachment size does not consider compression
Title: Message Title David van Laatum closed an issue as Fixed Jenkins / JENKINS-49913 email-ext: check for attachment size does not consider compression Change By: David van Laatum 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-48345) Cloud statistics is still counting the hours even after terminated the Azure VM agents
Title: Message Title Chenyang Liu commented on JENKINS-48345 Re: Cloud statistics is still counting the hours even after terminated the Azure VM agents Did you ever use "Shutdown Only" strategy? We found a bug when using "Shutdown Only" VMs, so that it will lead to a lot of never end cloud statistics events. We will fix it in the next version release. 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-36089) Pipeline support for Promoted Builds Plugin
Title: Message Title Pingru Cheng commented on JENKINS-36089 Re: Pipeline support for Promoted Builds Plugin Recently we are trying Jenkins 2.X with declarative pipeline. If Promotions plug-in can support it, that would be great! 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-50356) Update hugo theme to latest
Title: Message Title Naresh Rayapati started work on JENKINS-50356 Change By: Naresh Rayapati 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-50356) Update hugo theme to latest
Title: Message Title Naresh Rayapati created an issue Jenkins / JENKINS-50356 Update hugo theme to latest Issue Type: New Feature Assignee: Naresh Rayapati Components: jira-steps-plugin Created: 2018-03-23 02:20 Priority: Minor Reporter: Naresh Rayapati Seems like there are few exiting update make site awesome. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-5336) Users are automatically created when going thru HUDSON_URL/user/[anything]
Title: Message Title Amin Moralic commented on JENKINS-5336 Re: Users are automatically created when going thru HUDSON_URL/user/[anything] I still have this issue somehow, i try with latest LTS and weekly release and still can create user any suggestions how to check what is 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
Georg Henzler edited a comment on JENKINS-39203
Re: All stages show up as UNSTABLE when only one stage should
bq. This build status issue is causing a very large amount of frustration and wastes a lot of developer time trying to dig through logs to deduce failure statuses[~leedega] we have had the same issue. Today we work extensively with [Slack notifications|https://wiki.jenkins.io/display/JENKINS/Slack+Plugin] that contain links to [html reports|https://wiki.jenkins.io/display/JENKINS/HTML+Publisher+Plugin] (this is more important than just showing the correctly coloured box anyway, because even with that the developer would still have to check the log file for the actual root cause). In general I think it is great to have a per-pipeline-run build status - this probably shouldn't even be refactored: There are quite some use cases that need that: Notifications to source control if a feature branch can be merged, notifications about "back to normal", just showing a color in the build list in the left panel. That said I think it would be great to have additionally a per stage status, but not only for success/unstable/failed but with a much richer data model - it could e.g. be a list of info, warn and error messages that can be reduced to info/warn/error counts and even more reduced to success/unstable/failed per stage. If that was implemented as stage.info(...), stage.warn(...), stage.error(...) it could under the hood automatically set the per-pipeline-run build status. Plugins could without hassle one by one switch to the new way of setting the build status (while the old way stays intact).All that being said, if for a certain use case it is really important to only "change the color of one box", there is currently one way to achieve it:{code}stage('Stage 1') { echo "green" }try { stage('Stage 2') { throw new IllegalStateException("a failed stage") }} catch(err) { echo "made the stage only red" }stage('Stage 3') { echo "green" }try { stage('Stage 4') { throw new IllegalStateException("a failed stage") }} catch(err) { echo "made the stage only red" }stage('Stage 5') { echo "green" }{code}Will get you !overall-success-but-some-stages-marked-as-red.png|thumbnail![~svanoort] As people's grief lies mostly in the UI presentation as it seems (and not in the underlying data model), maybe it could be a very simple change in the pipeline core plugin to show yellow for a a predefined exception?
Add Comment
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
Georg Henzler edited a comment on JENKINS-39203
Re: All stages show up as UNSTABLE when only one stage should
> bq. This build status issue is causing a very large amount of frustration and wastes a lot of developer time trying to dig through logs to deduce failure statuses[~leedega] we have had the same issue. Today we work extensively with [Slack notifications|https://wiki.jenkins.io/display/JENKINS/Slack+Plugin] that contain links to [html reports|https://wiki.jenkins.io/display/JENKINS/HTML+Publisher+Plugin] (this is more important than just showing the correctly coloured box anyway, because even with that the developer would still have to check the log file for the actual root cause). In general I think it is great to have a per-pipeline-run build status - this probably shouldn't even be refactored: There are quite some use cases that need that: Notifications to source control if a feature branch can be merged, notifications about "back to normal", just showing a color in the build list in the left panel. That said I think it would be great to have additionally a per stage status, but not only for success/unstable/failed but with a much richer data model - it could e.g. be a list of info, warn and error messages that can be reduced to info/warn/error counts and even more reduced to success/unstable/failed per stage. If that was implemented as stage.info(...), stage.warn(...), stage.error(...) it could under the hood automatically set the per-pipeline-run build status. Plugins could without hassle one by one switch to the new way of setting the build status (while the old way stays intact).All that being said, if for a certain use case it is really important to only "change the color of one box", there is currently one way to achieve it:{code}stage('Stage 1') { echo "green" }try { stage('Stage 2') { throw new IllegalStateException("a failed stage") }} catch(err) { echo "made the stage only red" }stage('Stage 3') { echo "green" }try { stage('Stage 4') { throw new IllegalStateException("a failed stage") }} catch(err) { echo "made the stage only red" }stage('Stage 5') { echo "green" }{code}Will get you !overall-success-but-some-stages-marked-as-red.png|thumbnail![~svanoort] As people's grief lies mostly in the UI presentation as it seems (and not in the underlying data model), maybe it could be a very simple change in the pipeline core plugin to show yellow for a a predefined exception?
Add Comment
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
Georg Henzler commented on JENKINS-39203
Re: All stages show up as UNSTABLE when only one stage should
> This build status issue is causing a very large amount of frustration and wastes a lot of developer time trying to dig through logs to deduce failure statuses Kevin Phillips we have had the same issue. Today we work extensively with Slack notifications that contain links to html reports (this is more important than just showing the correctly coloured box anyway, because even with that the developer would still have to check the log file for the actual root cause). In general I think it is great to have a per-pipeline-run build status - this probably shouldn't even be refactored: There are quite some use cases that need that: Notifications to source control if a feature branch can be merged, notifications about "back to normal", just showing a color in the build list in the left panel. That said I think it would be great to have additionally a per stage status, but not only for success/unstable/failed but with a much richer data model - it could e.g. be a list of info, warn and error messages that can be reduced to info/warn/error counts and even more reduced to success/unstable/failed per stage. If that was implemented as stage.info(...), stage.warn(...), stage.error(...) it could under the hood automatically set the per-pipeline-run build status. Plugins could without hassle one by one switch to the new way of setting the build status (while the old way stays intact). All that being said, if for a certain use case it is really important to only "change the color of one box", there is currently one way to achieve it:
stage('Stage 1') { echo "green" }
try {
stage('Stage 2') { throw new IllegalStateException("a failed stage") }
} catch(err) { echo "made the stage only red" }
stage('Stage 3') { echo "green" }
try {
stage('Stage 4') { throw new IllegalStateException("a failed stage") }
} catch(err) { echo "made the stage only red" }
stage('Stage 5') { echo "green" }
Will get you Sam Van Oort As people's grief lies mostly in the UI presentation as it seems (and not in the underlying data model), maybe it could be a very simple change in the pipeline core plugin to show yellow for a a predefined exception?
Add Comment
[JIRA] (JENKINS-45486) Blue Ocean karaoke mode with an input step fails to continue updating
Title: Message Title Nicolae Pascu assigned an issue to Nicolae Pascu Jenkins / JENKINS-45486 Blue Ocean karaoke mode with an input step fails to continue updating Change By: Nicolae Pascu Assignee: Nicolae Pascu 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-45486) Blue Ocean karaoke mode with an input step fails to continue updating
Title: Message Title Nicolae Pascu updated an issue Jenkins / JENKINS-45486 Blue Ocean karaoke mode with an input step fails to continue updating Change By: Nicolae Pascu Sprint: Blue Ocean 1.5 - Candidates beta 3 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-45251) User Input text doesn't be formatted in Blue Ocean
Title: Message Title Nicolae Pascu assigned an issue to Nicolae Pascu Jenkins / JENKINS-45251 User Input text doesn't be formatted in Blue Ocean Change By: Nicolae Pascu Assignee: James Dumay Nicolae Pascu 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-43016) BlueOcean editor: does not allow empty string for label on agent or node
Title: Message Title Nicolae Pascu assigned an issue to Nicolae Pascu Jenkins / JENKINS-43016 BlueOcean editor: does not allow empty string for label on agent or node Change By: Nicolae Pascu Assignee: Nicolae Pascu 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-43016) BlueOcean editor: does not allow empty string for label on agent or node
Title: Message Title Nicolae Pascu updated an issue Jenkins / JENKINS-43016 BlueOcean editor: does not allow empty string for label on agent or node Change By: Nicolae Pascu Sprint: Blue Ocean 1.5 - Candidates beta 3 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Georg Henzler updated an issue Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Georg Henzler Attachment: overall-success-but-some-stages-marked-as-red.png 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-45251) User Input text doesn't be formatted in Blue Ocean
Title: Message Title Nicolae Pascu updated an issue Jenkins / JENKINS-45251 User Input text doesn't be formatted in Blue Ocean Change By: Nicolae Pascu Sprint: Blue Ocean 1.5 - Candidates beta 3 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-50355) @QueryParameter in form validation is not filled for dropdownDescriptorSelector
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-50355
@QueryParameter in form validation is not filled for dropdownDescriptorSelector
Change By:
Ulli Hafner
I’m trying to use form validation on a dropdownDescriptorSelector, however here the validation method parameters (annotated with @QueryParameter) are not found and set to null (or 0). (If used standalone the validation works).Is there anything different with a dropdownDescriptorSelector? Or is this caused since the jelly views are in different plugins that use different class loaders?The relevant main jelly part:{code} descriptors="${descriptor.availableTools}"/>{code}(whole file: [ScanForIssuesStep/config.jelly|https://github.com/jenkinsci/analysis-core-plugin/blob/3.0/src/main/resources/io/jenkins/plugins/analysis/core/steps/ScanForIssuesStep/config.jelly])The relevant jelly part of the referenced Describable:{code}description="${%Minimum number of duplicated lines for high priority warnings.}"field="highThreshold"> {code}(whole file: [DuplicateCodeScanner/config.jelly|https://github.com/jenkinsci/warnings-plugin/blob/3.0/src/main/resources/io/jenkins/plugins/analysis/warnings/DuplicateCodeScanner/config.jelly])My validation method:{code}public FormValidation doCheckHighThreshold(@QueryParameter final int highThreshold, @QueryParameter final int normalThreshold) { return VALIDATION.validateHigh(highThreshold, normalThreshold);}{code}(whole file: [DuplicateCodeScanner.java|https://github.com/jenkinsci/warnings-plugin/blob/3.0/src/main/java/io/jenkins/plugins/analysis/warnings/DuplicateCodeScanner.java] Both parameters are always set to zero when setting a breakpoint here.
Add Comment
[JIRA] (JENKINS-50355) @QueryParameter in form validation is not filled for dropdownDescriptorSelector
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-50355
@QueryParameter in form validation is not filled for dropdownDescriptorSelector
Change By:
Ulli Hafner
I’m trying to use form validation on a dropdownDescriptorSelector, however here the validation method parameters (annotated with @QueryParameter) are not found and set to null (or 0). (If used standalone the validation works).Is there anything different with a dropdownDescriptorSelector? Or is this caused since the jelly views are in different plugins that use different class loaders?The relevant main jelly part:{code} descriptors="${descriptor.availableTools}"/>{code}(whole file: [ScanForIssuesStep/config.jelly|https://github.com/jenkinsci/analysis-core-plugin/blob/3.0/src/main/resources/io/jenkins/plugins/analysis/core/steps/ScanForIssuesStep/config.jelly])The relevant jelly part of the referenced Describable:{code}description="${%Minimum number of duplicated lines for high priority warnings.}"field="highThreshold"> {code}(whole file: [DuplicateCodeScanner/config.jelly|https://github.com/jenkinsci/warnings-plugin/blob/3.0/src/main/resources/io/jenkins/plugins/analysis/warnings/DuplicateCodeScanner/config.jelly])My validation method:{code}public FormValidation doCheckHighThreshold(@QueryParameter final int highThreshold, @QueryParameter final int normalThreshold) { return VALIDATION.validateHigh(highThreshold, normalThreshold);}{code}(whole file: [DuplicateCodeScanner.java|https://github.com/jenkinsci/warnings-plugin/blob/3.0/src/main/java/io/jenkins/plugins/analysis/warnings/DuplicateCodeScanner.java] ) Both parameters are always set to zero when setting a breakpoint here.
Add Comment
[JIRA] (JENKINS-50355) @QueryParameter in form validation is not filled for dropdownDescriptorSelector
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-50355
@QueryParameter in form validation is not filled for dropdownDescriptorSelector
Change By:
Ulli Hafner
I ’m trying to use form validation on a dropdownDescriptorSelector, however here the validation method parameters (annotated with @QueryParameter) are not found and set to null (or 0). (If used standalone the validation works).Is there anything different with a dropdownDescriptorSelector? Or is this caused since the jelly views are in different plugins that use different class loaders? The relevant main jelly part:{code} descriptors="${descriptor.availableTools}"/>{code}(whole file: [ScanForIssuesStep/config.jelly|https://github.com/jenkinsci/analysis-core-plugin/blob/3.0/src/main/resources/io/jenkins/plugins/analysis/core/steps/ScanForIssuesStep/config.jelly])The relevant jelly part of the referenced Describable:{code}description="${%Minimum number of duplicated lines for high priority warnings.}"field="highThreshold"> {code}(whole file: [DuplicateCodeScanner/config.jelly|https://github.com/jenkinsci/warnings-plugin/blob/3.0/src/main/resources/io/jenkins/plugins/analysis/warnings/DuplicateCodeScanner/config.jelly])My validation method:{code}public FormValidation doCheckHighThreshold(@QueryParameter final int highThreshold, @QueryParameter final int normalThreshold) { return VALIDATION.validateHigh(highThreshold, normalThreshold);}{code}(whole file: [DuplicateCodeScanner.java|https://github.com/jenkinsci/warnings-plugin/blob/3.0/src/main/java/io/jenkins/plugins/analysis/warnings/DuplicateCodeScanner.java]Both parameters are always set to zero when setting a breakpoint here.
Add Comment
[JIRA] (JENKINS-50355) @QueryParameter in form validation is not filled for dropdownDescriptorSelector
Title: Message Title
Ulli Hafner created an issue
Jenkins / JENKINS-50355
@QueryParameter in form validation is not filled for dropdownDescriptorSelector
Issue Type:
Improvement
Assignee:
Unassigned
Attachments:
Bildschirmfoto 2018-03-22 um 23.50.22.png
Components:
core
Created:
2018-03-22 23:01
Priority:
Minor
Reporter:
Ulli Hafner
’m trying to use form validation on a dropdownDescriptorSelector, however here the validation method parameters (annotated with @QueryParameter) are not found and set to null (or 0). (If used standalone the validation works). Is there anything different with a dropdownDescriptorSelector? The relevant main jelly part:
"${description.tool}">
"tool" title="${%title.tool}"
descriptors="${descriptor.availableTools}"/>
(whole file: ScanForIssuesStep/config.jelly) The relevant jelly part of the referenced Describable:
"${%High priority threshold}"
description="${%Minimum number of duplicated lines for high priority warnings.}"
field="highThreshold">
default="50"/>
(whole file: DuplicateCodeScanner/config.jelly) My validation method:
[JIRA] (JENKINS-50264) Refusing to marshal com.amazonaws.services.codebuild.model.BuildPhase for security reasons : AWS CodeBuild
Title: Message Title Oleg Nenashev updated JENKINS-50264 The fix has been released in version 0.20 Jenkins / JENKINS-50264 Refusing to marshal com.amazonaws.services.codebuild.model.BuildPhase for security reasons : AWS CodeBuild Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Oleg Nenashev commented on JENKINS-50350 Re: JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Likely it happens for historical builds. Jesse Glick fixed persistency of the field in Pipeline: Job 2.0 (Feb 2016): https://github.com/jenkinsci/workflow-job-plugin/commit/6cdf41664d24e10c2f97d80f444571057fa2aa46 Would it possible to confirm it? You could just open build.xml for the failing builds and check the version of the plugin for which the Run object has been saved. 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-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Oleg Nenashev updated JENKINS-50339 Jenkins / JENKINS-50339 log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update Change By: Oleg Nenashev 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-50339) log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update
Title: Message Title Oleg Nenashev commented on JENKINS-50339 Re: log-entry: 'svnkit-1.9.1.jar might be dangerous' after LTS update I have created https://github.com/jenkinsci/subversion-plugin/pull/211 which *should* fix the error. 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-50354) Mockito Test for StaticAnalysisToolSuite
Title: Message Title Ulli Hafner closed an issue as Duplicate Jenkins / JENKINS-50354 Mockito Test for StaticAnalysisToolSuite Change By: Ulli Hafner Status: Open Closed 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-50354) Mockito Test for StaticAnalysisToolSuite
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-50354 Mockito Test for StaticAnalysisToolSuite Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2018-03-22 22:31 Priority: Minor Reporter: Ulli Hafner 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
[JIRA] (JENKINS-50067) Mockito: Improve Coverage Quality Gate
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50067 Mockito: Improve Coverage Quality Gate Change By: Ulli Hafner Summary: Mockito: Improve Coverage Quality Gate 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-50067) Improve Coverage Quality Gate
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50067 Improve Coverage Quality Gate Change By: Ulli Hafner Labels: Mockito 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-50067) Improve Coverage Quality Gate
Title: Message Title Ulli Hafner commented on JENKINS-50067 Re: Improve Coverage Quality Gate Methode getEvaluations 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-50075) Unit Test for IssuesFilter
Title: Message Title Ulli Hafner started work on JENKINS-50075 Change By: Ulli Hafner 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-50076) Unit Test for PropertyStatistics
Title: Message Title Ulli Hafner started work on JENKINS-50076 Change By: Ulli Hafner 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-50082) Unit Test of LocalizedPriority and EnvironmentResolver
Title: Message Title Ulli Hafner started work on JENKINS-50082 Change By: Ulli Hafner 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-50071) Unit Test for remaining *SeriesBuilder
Title: Message Title Ulli Hafner started work on JENKINS-50071 Change By: Ulli Hafner 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-50069) Unit Test for IssuesRecorder.Descriptor
Title: Message Title Ulli Hafner started work on JENKINS-50069 Change By: Ulli Hafner 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-50074) Mockito Test for ByIdResultSelector
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50074 Mockito Test for ByIdResultSelector Change By: Ulli Hafner Summary: Unit Mockito Test for ByIdResultSelector 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-50079) Mockito Test for DetailFactory
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50079 Mockito Test for DetailFactory Change By: Ulli Hafner Summary: Unit Mockito Test for DetailFactory 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-50353) Mockito Test for StaticAnalysisToolSuite
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50353 Mockito Test for StaticAnalysisToolSuite Change By: Ulli Hafner Summary: Unt Mockito Test for StaticAnalysisToolSuite 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-50078) Mockito - Improve Coverage Summary
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50078 Mockito - Improve Coverage Summary Change By: Ulli Hafner Labels: Mockito 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-50073) Mockito Test for StablePluginReference
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50073 Mockito Test for StablePluginReference Change By: Ulli Hafner Summary: Unit Mockito Test for StablePluginReference 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-50078) Mockito - Improve Coverage Summary
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50078 Mockito - Improve Coverage Summary Change By: Ulli Hafner Summary: Mockito - Improve Coverage Summary 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-50072) Mockito Test for PreviousRunReference
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50072 Mockito Test for PreviousRunReference Change By: Ulli Hafner Summary: Unit Mockito Test for PreviousRunReference 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-50353) Unt Test for StaticAnalysisToolSuite
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-50353 Unt Test for StaticAnalysisToolSuite Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2018-03-22 22:04 Labels: Mockito Priority: Minor Reporter: Ulli Hafner Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50352) gerit-plugin is not yet published as a plugin
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-50352 gerit-plugin is not yet published as a plugin Issue Type: Task Assignee: lucamilanesio Components: gerrit-plugin Created: 2018-03-22 21:47 Priority: Critical Reporter: Sorin Sbarnea It seems that gerit-plugin is not published as a plugin, so the only way to install it is for the user to compile it locally and upload the gerrit-plugin.hpi to the jenkins server. Even if the plugin is not considered stable, it should be published to Jenkins update sites and marked as experimental. PS. I tried to add support for gerrit-plugin inside jenkins-job-builder but my CR was blocked by this bug. Add Comment
[JIRA] (JENKINS-50351) Provide Hook for Orphaned Item Strategy
Title: Message Title Jacob Tomaw created an issue Jenkins / JENKINS-50351 Provide Hook for Orphaned Item Strategy Issue Type: Improvement Assignee: Devin Nusbaum Components: cloudbees-folder-plugin Created: 2018-03-22 21:24 Priority: Minor Reporter: Jacob Tomaw My team is using Jenkins to manage out Continuous Delivery pipelines. This means infrastructure is created and maintained through the life of a service in different environments. It would be useful if upon a job becoming an orphan we could execute something that destroys the infrastructure. Add Comment
[JIRA] (JENKINS-48656) Mercurial triggers broken by duplicate checkout in Multibranch pipeline
Title: Message Title Leon Blakey commented on JENKINS-48656 Re: Mercurial triggers broken by duplicate checkout in Multibranch pipeline If anyone still wants webhook triggers, you can host this script and point Bitbucket to it jenkinsWebHook.php 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-48656) Mercurial triggers broken by duplicate checkout in Multibranch pipeline
Title: Message Title Leon Blakey updated an issue Jenkins / JENKINS-48656 Mercurial triggers broken by duplicate checkout in Multibranch pipeline Change By: Leon Blakey Attachment: jenkinsWebHook.php Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Marian Klymov created an issue Jenkins / JENKINS-50350 JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Issue Type: Bug Assignee: Unassigned Components: workflow-job-plugin Created: 2018-03-22 20:26 Environment: Jenkins 2.107.1 Pipeline: Job 2.17 Labels: JEP-200 log pipeline Priority: Minor Reporter: Marian Klymov I'm getting lots of "Unreadable data" from different pipelines after upgrade to 2.107.1. ConversionException: Refusing to unmarshal logPrefixCache for security reasons; see https://jenkins.io/redirect/class-filter/ Debugging information class : com.google.common.cache.LocalCache$LocalLoadingCache required-type : com.google.common.cache.LocalCache$LocalLoadingCache converter-type : hudson.util.XStream2$BlacklistedTypesConverter path : /flow-build/logPrefixCache line number : 214 --- line numbers: 134, 214, 222, 238, 313, 391 etc. On first look log seems to be normal for mentioned build numbers. Is this something that I need to be worried about?
[JIRA] (JENKINS-49488) promotion conditions to support OR condition
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49488 promotion conditions to support OR condition Change By: Rick Liu Summary: Document that all promotion conditions have to be met to start the promotion support OR condition 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-47884) "Pipeline Aggregator" name is confusing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-47884 Re: "Pipeline Aggregator" name is confusing Code changed in jenkins User: Paul Path: pom.xml http://jenkins-ci.org/commit/pipeline-aggregator-view-plugin/bd43df66328dc6c9e9d2f4c31b0811945525d111 Log: Merge pull request #3 from oleg-nenashev/JENKINS-47884 JENKINS-47884 - Add "View" to the plugin's name Compare: https://github.com/jenkinsci/pipeline-aggregator-view-plugin/compare/9594a943f3fb...bd43df66328d 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-47884) "Pipeline Aggregator" name is confusing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-47884 Re: "Pipeline Aggregator" name is confusing Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/pipeline-aggregator-view-plugin/52a75c2c7ab2b473e47d7ad960f87734205a42c2 Log: JENKINS-47884 - Add "View" to the plugin's name 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-49809) Create the Evergreen Status service data model
Title: Message Title R. Tyler Croy stopped work on JENKINS-49809 Change By: R. Tyler Croy Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50164) 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running
Title: Message Title Baptiste Mathus updated JENKINS-50164 Jenkins / JENKINS-50164 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50349) NPE during dynamic install
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50349 Re: NPE during dynamic install Code changed in jenkins User: Stephen Connolly Path: CHANGES.md src/main/java/org/jenkinsci/plugin/gitea/GiteaSCMNavigator.java http://jenkins-ci.org/commit/gitea-plugin/b07f40075de874efcbe8aac066b59fa4741d6ae8 Log: [FIXED JENKINS-50349] Another NPE during dynamic installation of the 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-50349) NPE during dynamic install
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-50349 NPE during dynamic install Change By: SCM/JIRA link daemon 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-50348) Why does "Pipeline: Groovy" require "Support Core"?
Title: Message Title Christian Höltje commented on JENKINS-50348 Re: Why does "Pipeline: Groovy" require "Support Core"? It looks like it was added for the issue JENKINS-31840. I'm not sure why it is required and not optional, though. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50348) Why does "Pipeline: Groovy" require "Support Core"?
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-50348 Why does "Pipeline: Groovy" require "Support Core"? Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-03-22 19:54 Environment: Pipeline:Groovy version 2.45 Priority: Minor Reporter: Christian Höltje Why does the "Pipeline: Groovy" plugin (part of workflow-cps) require the "Support Core" plugin? Usually "Support Core" is optional. I ask because "Support Core" can kill performance on a system if the system is very busy and generates a lot of logging information. Add Comment
[JIRA] (JENKINS-50349) NPE during dynamic install
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-50349 NPE during dynamic install Issue Type: Bug Assignee: Stephen Connolly Components: gitea-plugin Created: 2018-03-22 19:54 Priority: Minor Reporter: Stephen Connolly java.lang.AssertionError at org.jenkinsci.plugin.gitea.GiteaSCMNavigator$DescriptorImpl.getTraitsDefaults(GiteaSCMNavigator.java:436) at org.jenkinsci.plugin.gitea.GiteaSCMNavigator$DescriptorImpl.newInstance(GiteaSCMNavigator.java:393) at jenkins.branch.CustomOrganizationFolderDescriptor.doAddSpecificDescriptors(CustomOrganizationFolderDescriptor.java:181) at jenkins.branch.CustomOrganizationFolderDescriptor.access$100(CustomOrganizationFolderDescriptor.java:54) at jenkins.branch.CustomOrganizationFolderDescriptor$ListenerImpl.onChange(CustomOrganizationFolderDescriptor.java:157) at hudson.ExtensionList.fireOnChangeListeners(ExtensionList.java:345) at hudson.ExtensionList.refresh(ExtensionList.java:338) at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2648) at hudson.PluginManager.dynamicLoad(PluginManager.java:879) at hudson.PluginManager.dynamicLoad(PluginManager.java:822) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1889) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1651) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:112) at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-49762) withMaven fails to detect maven executable in kubernetes container
Title: Message Title Carlos Sanchez commented on JENKINS-49762 Re: withMaven fails to detect maven executable in kubernetes container No, there's none that I could figure out, although there's a PR that works around it https://github.com/jenkinsci/kubernetes-plugin/pull/242 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-49762) withMaven fails to detect maven executable in kubernetes container
Title: Message Title Giuseppe Iannello commented on JENKINS-49762 Re: withMaven fails to detect maven executable in kubernetes container I would like you to reconsider this issue. Using docker containers for builds helps with reproducibility and composability: it's trivial to replace a container with a different one and immediately check if there's any impact on the build process. This partially overlaps with one of the goals of the jenkins-maven plugin, but it's not enough to justify stopping using withMaven in a build: all the benefits coming from the publishers and artifacts fingerprinting are lost. Now, if you still insist to combine the two, you are possibly affected by the fact that the `container` block only supports sh based steps. All other steps will just ignore the `container` and execute inside the jnlp container. There's no actual reason not to "insist", as this seems to me the normal use case for a composable, docker-based build process: each container hosts a specific tool, everything runs in the same workspace. Your suggested distinct approaches have some fundamental flaws: plain agent pod: it ships with a JVM, and no maven. Switching to a different JVM is cumbersome, might break the jnlp slave itself, goes against the basic principles of containerization. skipping withMaven: losing all the benefits of the maven plugin Combining the two is the most logical option: sh steps will run in the maven container - and there's no problem with that, as even within a withMaven block, sh 'mvn ...' is the way to invoke the wrapper maven, and whatever cannot run in the maven container can run in the JNLP slave container, with the same workspace as the maven one. Carlos Sanchez isn't there a different way to return the exit code without having to inject a string into stdout? Add Comment
[JIRA] (JENKINS-48828) Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2
Title: Message Title Jarrod Johnson commented on JENKINS-48828 Re: Bitbucket Team/Folder project: View Configuration pages shows Access Denied, Jenkins throws hudson.security.AccessDeniedException2 Same issue here. Even if we explicitly grant the user the job/configure permission they are still unable to make changes on the repository configuration page. This is wildly annoying as our current configuration requires us to poll for new branches that are created and the default polling period is one day. Is there a version of the plugin this works with that we can roll back to or is it due to updates in newer versions of jenkins? We are running: Jenkins 2.89.4 Bitbucket Plugin 1.1.7 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-50075) Unit Test for IssuesFilter
Title: Message Title Frank Christian Geyer assigned an issue to Frank Christian Geyer Jenkins / JENKINS-50075 Unit Test for IssuesFilter Change By: Frank Christian Geyer Assignee: Deniz Mardin Frank Christian Geyer 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-50075) Unit Test for IssuesFilter
Title: Message Title Deniz Mardin assigned an issue to Deniz Mardin Jenkins / JENKINS-50075 Unit Test for IssuesFilter Change By: Deniz Mardin Assignee: Frank Christian Geyer Deniz Mardin 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-45480) GIT Build with Parameters is not listing branches
Title: Message Title Boguslaw Klimas commented on JENKINS-45480 Re: GIT Build with Parameters is not listing branches Maybe I didn't express myself precisely, I meant it: I understand that each of these jobs (SCM) works fetch/clone correctly on the master node? (the plugin does not need to build a project) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49023) Cannot upload file using cifs-plugin
Title: Message Title Geoff Butler commented on JENKINS-49023 Re: Cannot upload file using cifs-plugin Here are my global, project and plugin configs. Cleansed of course. If you need any more info please let me know 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-49023) Cannot upload file using cifs-plugin
Title: Message Title Geoff Butler updated an issue Jenkins / JENKINS-49023 Cannot upload file using cifs-plugin Change By: Geoff Butler Attachment: global config.xml Attachment: jenkins.plugins.publish_over_cifs.CifsPublisherPlugin.xml Attachment: project config.xml 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-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49406 Re: Prototype the Evergreen snapshotting data safety system Code changed in jenkins User: R. Tyler Croy Path: jep/302/README.adoc jep/README.adoc http://jenkins-ci.org/commit/jep/949cbdb6bb2823a0a780e1005cf86a9b815f48b6 Log: Merge pull request #67 from batmat/JENKINS-49406-JEP-submission JENKINS-49406 Evergreen snapshotting data safety system JEP Compare: https://github.com/jenkinsci/jep/compare/b5b57a9f1c93...949cbdb6bb28 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-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49406 Re: Prototype the Evergreen snapshotting data safety system Code changed in jenkins User: Baptiste Mathus Path: jep//README.adoc http://jenkins-ci.org/commit/jep/6773edbc06488de4c2fa7371f54c79df38672861 Log: JENKINS-49406 Evergreen snapshotting data safety system JEP 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-45251) User Input text doesn't be formatted in Blue Ocean
Title: Message Title Aaron Curley commented on JENKINS-45251 Re: User Input text doesn't be formatted in Blue Ocean Definitely a desired item from my team's perspective as well. Certainly not a blocker though. Thanks for all that you folks do! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49380) Git plugin builds although ls-remote reports no heads
Title: Message Title Christopher Timm closed an issue as Won't Do For my personal use I have applied the suggested solution and it is working, but I understand, that including it in master introduces possible silent failures, that should not be ignored. I will close it as won't fix. Jenkins / JENKINS-49380 Git plugin builds although ls-remote reports no heads Change By: Christopher Timm Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest
Title: Message Title Ken Lamb commented on JENKINS-50327 Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest Here is one of the pipeline commands that reproduces the issue: checkout changelog: true, poll: true, scm: [ $class: 'SubversionSCM', additionalCredentials: [], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[credentialsId: SVN_CREDENTIALS, depthOption: 'empty', ignoreExternalsOption: true, local: '.', remote: "http://code-repository.net/branches/trunk"]], quietOperation: true, workspaceUpdater: [$class: 'UpdateUpdater'] ] 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-50075) Unit Test for IssuesFilter
Title: Message Title Frank Christian Geyer assigned an issue to Frank Christian Geyer Jenkins / JENKINS-50075 Unit Test for IssuesFilter Change By: Frank Christian Geyer Assignee: Ulli Hafner Frank Christian Geyer 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-50347) Design and create instance registration process
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50347 Design and create instance registration process Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-03-22 17:47 Priority: Minor Reporter: R. Tyler Croy Discussed this a bit with Michael Neale via Google Hangouts yesterday, but an instance will need to initiate a registration process with the Evergreen hosted services layer to create a cryptographic key for use with future requests. Basically we need to ensure that the information we're receiving from the instance over time can be trusted to come from that instance. Add Comment
[JIRA] (JENKINS-50347) Design and create instance registration process
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-50347 Design and create instance registration process Change By: R. Tyler Croy Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50296) ThreadPools for remoting should run as SYSTEM user
Title: Message Title Jesse Glick assigned an issue to Steve Arch Jenkins / JENKINS-50296 ThreadPools for remoting should run as SYSTEM user Change By: Jesse Glick Assignee: Steve Arch 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-49804) Multibranch Helix Branches: support exclusionary mapping?
Title: Message Title W Basu assigned an issue to Karl Wirth Would you look into it please Jenkins / JENKINS-49804 Multibranch Helix Branches: support exclusionary mapping? Change By: W Basu Assignee: Karl Wirth 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-50327) Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest
Title: Message Title Ken Lamb commented on JENKINS-50327 Re: Update to 2.10.4 causes NullPointerException in HTTPDigestAuthentication.createDigest For what it is worth, I tried updating the plugin again after updating to Jenkins 2.107.1, but I got the same error. So, I rolled back again. 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-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Andrew Lamonica commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Baptiste Mathus, I'm not sure you are helping the XML1.1-argument when you remind people that XML 1.1 was published in 2004. Any software standard that is not well-supported after more than a decade is not likely to suddenly gain widespread acceptance. But, as I mentioned before, it looks like Jenkins isn't really doing XML 1.1, anyway. The code is just emitting the header, then doing business-as-usual for the body. That's weird, but not a deal breaker. No one is going to switch away from a great technology like Jenkins just because they have to do a little text-replacing when using one of the APIs. I'm not sure what mailing list you think I should join. But, I can give a quick explanation of what we are using the XML for. My company tracks changes to configurations of most of our off-the-shelf and open-source software (as well as some hardware) in something we call the "recovery system". This recovery system is a little like an automated backup, except that it can be used to easily view changes made to confirmations. The system is often the first place people go where there is a mysterious service disruption since it aggregates all changes together into a single timeline. The code our "recovery system" uses to extract Jenkins' would be more-or-less agnostic to XML-type (since it largely doesn't care about the format of the configuration it is backing up) except that it gets a lists of things to track by inspecting the output of other XML APIs. (such as jankins.hostname/api/xml). At time of writing this, I'm not 100% sure which API calls were failing to parse, since the person on my team who fixed this did so in a very-general way and it's unlikely all of them failed (given my example doesn't have a header at all). But, maybe I can provide more details after locating the mailing-list. Cheers. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50344) Failed to start Jenkins INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50344 Failed to start Jenkins INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet Change By: Oleg Nenashev Component/s: _unsorted Component/s: winstone-jetty 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-50344) Failed to start Jenkins INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
Title: Message Title Oleg Nenashev commented on JENKINS-50344 Re: Failed to start Jenkins INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet "ava.net.BindException: Address already in use: bind". There is another service running on the same port Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21942) Unreliable defaulting of Jenkins.workspaceDir
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-21942 Unreliable defaulting of Jenkins.workspaceDir Change By: Baptiste Mathus Labels: essentials upgrade workspace Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
