[JIRA] (JENKINS-48428) Groovy Plugin should share the codebase with Groovy Postbuild Plugin
Title: Message Title
akostadinov edited a comment on JENKINS-48428
Re: Groovy Plugin should share the codebase with Groovy Postbuild Plugin
I think it is related to using spaces in job name. This is using groovy file:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/update.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1319) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1272) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) 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 hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.54.6.1/172.54.6.1:60644 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1060) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$ProcStarter.join(Launcher.java:466) at hudson.plugins.groovy.Groovy.perform(Groovy.java:106) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: 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) ... 15 moreBuild step 'Execute Groovy script' marked build as failure{code}This is using script:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/hudson6527770564855321328.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at
[JIRA] (JENKINS-48428) Groovy Plugin should share the codebase with Groovy Postbuild Plugin
Title: Message Title
akostadinov edited a comment on JENKINS-48428
Re: Groovy Plugin should share the codebase with Groovy Postbuild Plugin
I think it is related to using spaces in job name. This is using groovy file:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/update.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1319) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1272) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) 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 hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.54.6.1/172.54.6.1:60644 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1060) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$ProcStarter.join(Launcher.java:466) at hudson.plugins.groovy.Groovy.perform(Groovy.java:106) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: 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) ... 15 moreBuild step 'Execute Groovy script' marked build as failure{code}This is using script:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/hudson6527770564855321328.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at
[JIRA] (JENKINS-48428) Groovy Plugin should share the codebase with Groovy Postbuild Plugin
Title: Message Title akostadinov commented on JENKINS-48428 Re: Groovy Plugin should share the codebase with Groovy Postbuild Plugin I think it is related to using spaces in job name. This is using groovy file: [Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/update.groovy" FATAL: command execution failed java.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1319) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1272) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) 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 hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.54.6.1/172.54.6.1:60644 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1060) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$ProcStarter.join(Launcher.java:466) at hudson.plugins.groovy.Groovy.perform(Groovy.java:106) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: 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) ... 15 more Build step 'Execute Groovy script' marked build as failure This is using script: [Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops
[JIRA] (JENKINS-54678) Compression trick not supported by JEP-210
Title: Message Title akostadinov commented on JENKINS-54678 Re: Compression trick not supported by JEP-210 Yeah, I can confirm that keeping the file name `log` even though it is compressed, keeps things working. Can't it just create a symlink log -> log.gz ? Jesse Glick, any plan to fix it? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195469.1542393908000.11723.1586958301070%40Atlassian.JIRA.
[JIRA] (JENKINS-61902) Slave roles not respected with Authorize Project plugin
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-61902 Slave roles not respected with Authorize Project plugin Change By: akostadinov Attachment: manage_roles.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205774.1586890711000.11165.1586890860375%40Atlassian.JIRA.
[JIRA] (JENKINS-61902) Slave roles not respected with Authorize Project plugin
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-61902 Slave roles not respected with Authorize Project plugin Change By: akostadinov Attachment: manage_roles.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205774.1586890711000.11162.1586890802432%40Atlassian.JIRA.
[JIRA] (JENKINS-61902) Slave roles not respected with Authorize Project plugin
Title: Message Title akostadinov created an issue Jenkins / JENKINS-61902 Slave roles not respected with Authorize Project plugin Issue Type: Bug Assignee: ikedam Attachments: assign_roles.png, manage_roles.png Components: authorize-project-plugin Created: 2020-04-14 18:58 Priority: Critical Reporter: akostadinov Using Authorize Project plugin I have setting we have "Project Default build Authorization" set to "Run as User who Triggered Build". Then I have project roles letting particular users to run specific jobs. To allow said people to also build on the nodes I assign to them Slave role (see assign_roles.png). That Slave role is allowed to build on ".*" nodes (see manage_roles.png). But still when project is triggered from such a user, in the queue a message can be seen: > 'myusername' lacks permission to run on 'my-node-name-1' My workaround is to allow global Agent/Build permission to everybody but this is not ideal. Jenkins 2.190.3 Authorize Project 1.3.0 Role-based Authorization Strategy 2.13 Add Comment
[JIRA] (JENKINS-59979) Script Security: JCasC ScriptApproval does not apply until Jenkins reboot
Title: Message Title akostadinov commented on JENKINS-59979 Re: Script Security: JCasC ScriptApproval does not apply until Jenkins reboot For me it worked properly on Jenkins 2.190, casc plugin 1.36 and Script Security plugin 1.68. security: scriptApproval: approvedSignatures: - method java.net.URI getHost Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202784.1572381545000.9445.1586685600278%40Atlassian.JIRA.
[JIRA] (JENKINS-60849) pipeline build step, wait until build is scheduled
Title: Message Title akostadinov created an issue Jenkins / JENKINS-60849 pipeline build step, wait until build is scheduled Issue Type: New Feature Assignee: Unassigned Components: pipeline-build-step-plugin Created: 2020-01-23 21:27 Labels: pipeline Priority: Major Reporter: akostadinov I need to easily navigate between upstream and downstream builds. Presently it is easy to navigate from downstream to upstream build because downstream build has upstream build as a cause. But navigating from upstream to downstream build is complicated when `wait: false` is used in the build step. When `wait` it is set to false, a build is triggered. But there is no way for the pipeline to know which build that was. When `wait` is false, the returned value is `org.codehaus.groovy.runtime.NullObject`. What will be useful is to have a parameter where build is triggered, then step waits until it has an id and returns only then. Or is there any other easy way to figure out triggered builds? Add Comment
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title akostadinov commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once Suraj Sharma, and if you have a multiline string that function works in a surprising way. It needs to be done on the lower level by the plugin to be reliable. I actually wonder if we can have a console wrapper that will capture whatever output produced inside. Like AnsiColor Plugin. It will not be able to differentiate stdin from stderr though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183003.149756330.16582.1559221921649%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job
Title: Message Title akostadinov commented on JENKINS-57642 Re: Wrong parameter type and squashing its content when trigger a job I'd like to add that this is a huge problem for the job rebuild plugin. Because it seems to respect the type given by the jms-messaging-plugin instead of config.xml. This removes new lines from text parameter so job can't be effectively rebuilt. P.S. maybe second part of description needs to be changed because removing of new lines happens with String rather than Text param. Or possibly I misread it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199573.1558615641000.10145.1558622820164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53288) Signature verification failed in update site 'default' (again)
Title: Message Title akostadinov closed an issue as Duplicate Jenkins / JENKINS-53288 Signature verification failed in update site 'default' (again) Change By: akostadinov Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53288) Signature verification failed in update site 'default' (again)
Title: Message Title akostadinov commented on JENKINS-53288 Re: Signature verification failed in update site 'default' (again) Ok, issue was INFRA-1659, in Fedora 28 there is an additional file `/etc/crypto-policies/back-ends/java.config` that overrides settings in `java.security` and it has `RSA keySize < 2048`. Setting this to `1024` resolved the issue. But it sounds like update center certificate is now time to be updated to 4096 bits. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53288) Signature verification failed in update site 'default' (again)
Title: Message Title
akostadinov updated an issue
Jenkins / JENKINS-53288
Signature verification failed in update site 'default' (again)
Change By:
akostadinov
I have applied proposed fix from JENKINS-31089 and this is my line in `/usr/lib/jvm/java-openjdk/jre/lib/security/java.security`:{code}jdk.certpath.disabledAlgorithms=MD2, MD5, SHA1 jdkCA & usage TLSServer, \RSA keySize < 512, DSA keySize < 1024, EC keySize < 224{code}But still I'm seeing this in Jenkins 2.121.3 log:{code}Aug 28, 2018 3:20:15 PM hudson.model.UpdateSite updateDataSEVERE: ERROR: Signature verification failed in update site default (show details)java.security.cert.CertPathValidatorException: Algorithm constraints check failed on keysize limits. RSA 1024bit key used with certificate: CN=Community Update Center, O=Jenkins Project, ST=California, C=US. at sun.security.util.DisabledAlgorithmConstraints$KeySizeConstraint.permits(DisabledAlgorithmConstraints.java:817){code}Java:{code}$ java -versionopenjdk version "1.8.0_181"OpenJDK Runtime Environment (build 1.8.0_181-b13)OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode){code} Attached `java.security` from Fedora 28, I can't spot any place where RSA 1024 is blocked.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-53288) Signature verification failed in update site 'default' (again)
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-53288 Signature verification failed in update site 'default' (again) Change By: akostadinov Attachment: java.security Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53288) Signature verification failed in update site 'default' (again)
Title: Message Title
akostadinov updated an issue
Jenkins / JENKINS-53288
Signature verification failed in update site 'default' (again)
Change By:
akostadinov
I have applied proposed fix from JENKINS-31089 and this is my line in `/usr/lib/jvm/java-openjdk/jre/lib/security/java.security`:{code}jdk.certpath.disabledAlgorithms=MD2, MD5, SHA1 jdkCA & usage TLSServer, \RSA keySize < 512, DSA keySize < 1024, EC keySize < 224{code}But still I'm seeing this in Jenkins 2.121.3 log:{code}Aug 28, 2018 3:20:15 PM hudson.model.UpdateSite updateDataSEVERE: ERROR: Signature verification failed in update site default (show details)java.security.cert.CertPathValidatorException: Algorithm constraints check failed on keysize limits. RSA 1024bit key used with certificate: CN=Community Update Center, O=Jenkins Project, ST=California, C=US. at sun.security.util.DisabledAlgorithmConstraints$KeySizeConstraint.permits(DisabledAlgorithmConstraints.java:817){code} Java:{code}$ java -versionopenjdk version "1.8.0_181"OpenJDK Runtime Environment (build 1.8.0_181-b13)OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode){java}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-53288) Signature verification failed in update site 'default' (again)
Title: Message Title
akostadinov updated an issue
Jenkins / JENKINS-53288
Signature verification failed in update site 'default' (again)
Change By:
akostadinov
I have applied proposed fix from JENKINS-31089 and this is my line in `/usr/lib/jvm/java-openjdk/jre/lib/security/java.security`:{code}jdk.certpath.disabledAlgorithms=MD2, MD5, SHA1 jdkCA & usage TLSServer, \RSA keySize < 512, DSA keySize < 1024, EC keySize < 224{code}But still I'm seeing this in Jenkins 2.121.3 log:{code}Aug 28, 2018 3:20:15 PM hudson.model.UpdateSite updateDataSEVERE: ERROR: Signature verification failed in update site default (show details)java.security.cert.CertPathValidatorException: Algorithm constraints check failed on keysize limits. RSA 1024bit key used with certificate: CN=Community Update Center, O=Jenkins Project, ST=California, C=US. at sun.security.util.DisabledAlgorithmConstraints$KeySizeConstraint.permits(DisabledAlgorithmConstraints.java:817){code}Java:{code}$ java -versionopenjdk version "1.8.0_181"OpenJDK Runtime Environment (build 1.8.0_181-b13)OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode){ java code }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-31089) Signature verification failed in update site 'default'
Title: Message Title akostadinov commented on JENKINS-31089 Re: Signature verification failed in update site 'default' Filed JENKINS-53288 for signature verification check I see with 2.121.3 and a clean install (after applying the RSA 512 fix). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53288) Signature verification failed in update site 'default' (again)
Title: Message Title akostadinov created an issue Jenkins / JENKINS-53288 Signature verification failed in update site 'default' (again) Issue Type: Bug Assignee: Unassigned Components: update-sites-manager-plugin Created: 2018-08-28 12:26 Priority: Critical Reporter: akostadinov I have applied proposed fix from JENKINS-31089 and this is my line in `/usr/lib/jvm/java-openjdk/jre/lib/security/java.security`: jdk.certpath.disabledAlgorithms=MD2, MD5, SHA1 jdkCA & usage TLSServer, \ RSA keySize < 512, DSA keySize < 1024, EC keySize < 224 But still I'm seeing this in Jenkins 2.121.3 log: Aug 28, 2018 3:20:15 PM hudson.model.UpdateSite updateData SEVERE: ERROR: Signature verification failed in update site default '#' class='showDetails'>(show details)'display:none'>java.security.cert.CertPathValidatorException: Algorithm constraints check failed on keysize limits. RSA 1024bit key used with certificate: CN=Community Update Center, O=Jenkins Project, ST=California, C=US. at sun.security.util.DisabledAlgorithmConstraints$KeySizeConstraint.permits(DisabledAlgorithmConstraints.java:817)
[JIRA] (JENKINS-50902) shell pipeline step cannot use relative path to shell
Title: Message Title akostadinov created an issue Jenkins / JENKINS-50902 shell pipeline step cannot use relative path to shell Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2018-04-19 16:53 Priority: Major Reporter: akostadinov There is some difference between free-style project shell build step and the pipeline `sh` step. If I set in jenkins global configuration `bash` as the "Shell Executable", then free-style project works and calls `bash` from the PATH on the slave. The pipeline `sh` step fails like this though: [pipeline-test-job] Running shell script sh: /home/jenkins/workspace/pipeline-test-akostadi@tmp/durable-2ff6e6ae/script.sh: bash: bad interpreter: No such file or directory [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code 126 Finished: FAILURE The use case is that some systems like MacOS ship with an old bash version under /bin/sh. And we want to not be limited in shell scripts by that version. Since proper bash should be installed in other locations on such slaves, we need to run `bash` from PATH. But also can't hardcode `bash` absolute path because it is still `/bin/bash` on normal linux slaves. I'm reading through ShellStep.java and BourneShellScript.java. It looks like it launches `sh -c cmd` but I don't see how the global setting is applied, even less I understand why it fails. At the same time free-style projects work fine with this setting on all slaves. I think this difference between free-style and pipeline might be related to JENKINS-44341 also. Any clue what exactly might be the difference and how it could be fixed?
[JIRA] (JENKINS-50228) commits count refreshing many times
Title: Message Title akostadinov created an issue Jenkins / JENKINS-50228 commits count refreshing many times Issue Type: Bug Assignee: Paul Horvath Attachments: strange_updates.png Components: pipeline-aggregator-view-plugin Created: 2018-03-16 20:44 Priority: Minor Reporter: akostadinov Hi, when a build is in progress and I stay at "stage view" watching progress of the pipeline, I see that the commit count for the archived builds is constantly refreshing. Each time progress moves for the running pipeline, all archived builds do refresh their commit counts. Sounds like a great idea to remove this. Attaching a screenshot from Firefox 58. Add Comment
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title akostadinov commented on JENKINS-36568 Re: workflow script node step cannot trigger build on specific node Jesse Glick, have a job with label parameter build manually => the default value of parameter is respected build from a pipeline (without specifying this parameter) => job is built on a random node (i.e. the default value of the label parameter is not respected) And in the latter case, when you go to the executed build parameters, you see the label parameter with the default values. They just didn't take effect. But probably this is a separate issue so I will file one. 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-36568) workflow script node step cannot trigger build on specific node
Title: Message Title akostadinov reopened an issue Jesse Glick, we're hitting the same issue. I find it reasonable to require usage of the NodeLabel plugin. But our job does have a Label parameter with a default _expression_ in it. When triggered from pipeline, build executes on a random slave marked as "utilize as much as possible" instead of using the default value from the job label parameter. I think that the default label parameter should be respected. It is IMO unnecessary complication if pipeline has to hardcode this parameter for every external job called. Jenkins / JENKINS-36568 workflow script node step cannot trigger build on specific node Change By: akostadinov Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43003) label parameter does not enforse execution on the labels
Title: Message Title akostadinov resolved as Duplicate Seems like we're hitting JENKINS-36568 Jenkins / JENKINS-43003 label parameter does not enforse execution on the labels Change By: akostadinov 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
[JIRA] (JENKINS-43003) label parameter does not enforse execution on the labels
Title: Message Title akostadinov created an issue Jenkins / JENKINS-43003 label parameter does not enforse execution on the labels Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 2017/Mar/21 10:18 PM Priority: Critical Reporter: akostadinov When there are slaves configured to be "utilized as much as possible", then the label _expression_ can be disregarded and job built on one of these slaves. Node and Label parameter plugin - 1.7.2 Jenkins - 1.609.3 Add Comment
[JIRA] (JENKINS-17116) gracefull job termination
Title: Message Title akostadinov edited a comment on JENKINS-17116 Re: gracefull job termination [~kashierez], it is possible to:1. remove the jenkins cookie environment variable2. run your program in background (output still can go to stdout)3. launch another background process to check original process PID, such that when it is gone, it would kill the other child gracefully4. in main process, wait for the other two to complete (make sure second monitor process would exit if the first background process exits)5. take care to report proper termination status of the programNot very nice probably but you can script it to run arbitrary shell commands in this way. Also might not be worth the effort. It didn't for me. Forgot to mention: this would only work on UNIX derivatives IIRC. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-17116) gracefull job termination
Title: Message Title akostadinov commented on JENKINS-17116 Re: gracefull job termination Erez Kashi, it is possible to: 1. remove the jenkins cookie environment variable 2. run your program in background (output still can go to stdout) 3. launch another background process to check original process PID, such that when it is gone, it would kill the other child gracefully 4. in main process, wait for the other two to complete (make sure second monitor process would exit if the first background process exits) 5. take care to report proper termination status of the program Not very nice probably but you can script it to run arbitrary shell commands in this way. Also might not be worth the effort. It didn't for me. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-30500) jclouds docker support
Title: Message Title akostadinov commented on JENKINS-30500 Re: jclouds docker support You can run anything inside container. I've done sshd specifically. But eventually ended up using the kubernetes plugin to launch slaves off OpenShift cluster. Much nicer in my experience. It uses JNLP. Here's base image that would work on Kubernetes or OpenSHift. That's completely off topic though except for providing some proof that containers are suitable for running slaves. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-24805) Mask credentials in Build Log
Title: Message Title akostadinov commented on JENKINS-24805 Re: Mask credentials in Build Log Thanks a lot for implementing this! Which version of plug-in would have these changes? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22363) Upgrade of copy-project-link from v1.1 to v1.2 fails
Title: Message Title akostadinov reopened an issue Jenkins / JENKINS-22363 Upgrade of copy-project-link from v1.1 to v1.2 fails Change By: akostadinov Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-22363) Upgrade of copy-project-link from v1.1 to v1.2 fails
Title: Message Title akostadinov commented on JENKINS-22363 Re: Upgrade of copy-project-link from v1.1 to v1.2 fails After last week plug-in upgrade, some people started to hit such issues. Installing the Folders plugin resolved the issue. I think some plugin(s) was changed to require it but proper dependencies have not been set. Any idea how to find this out? Can we somehow check which plugins refer to `com/cloudbees/hudson/plugins/folder/AbstractFolder` and add the plugin as a dependency? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38829) "Kubernetes server certificate key" not working
Title: Message Title
akostadinov edited a comment on JENKINS-38829
Re: "Kubernetes server certificate key" not working
Hello again. Looking at your test cases I understood and tested what the issue is. The certificate you test with is actually a PEM encoded cert but then base64 encoded. I think that it makes more sense to ask from user simply a PEM cert and base64 encode it upon passing to the kubernetes API. Also your new help text also indicates normal PEM encoding is needed while I could make it work only after additionally base64 encoding it.i.e. I'd expect that I need to put this in the field this:{CODE}-BEGIN CERTIFICATE-MIIC6jCCAdKgAwIBAgIBATANBgkqhkiG9w0BAQsFADAmMSQwIgYDVQQDDBtvcGVuc2hpZnQtc2lnbmVyQDE0NzU4NzkyMDYwHhcNMTYxMDA3MjIyNjQ2WhcNMjExMDA2MjIyNjQ3WjAmMSQwIgYDVQQDDBtvcGVuc2hpZnQtc2lnbmVyQDE0NzU4NzkyMDYwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC8e9H5mVf6T0VYzG3cUkXkUSArFStbZs1XQ0mOqM25DK/wPJ464NHcYBRlgnONqdvlwu/sMHTw9cIelWi9peAgK5EcoDrp5spXwY/NSjmBtEV2+w+3FvvjZQhGhde79vafTiRAfCBJVvhZC6DwGzH6c7axTNjF82WjQ1G5lv4pXpanj4zKpX4DCchuE1zet2UmDkDtl1vcho/eiTc737BgrXOCau3LbTtFlw2Cg1gzk5YlWTzB1DaprP/55+Ks6dUKKX7WsSALErv6Sj0RW1//CQ6OqtACznyYjXRHH9zLBys7YV27gfvyqujdV8Obk66sI+kT9Pf8jW02GVUt//9RAgMBAAGjIzAhMA4GA1UdDwEB/wQEAwICpDAPBgNVHRMBAf8EBTADAQH/MA0GCSqGSIb3DQEBCwUAA4IBAQC7OhnypzgmpBN62GgDbFZTsFSmvxJHNjKeZfDJr1i/r2oZa/0SZ5Q2N7B5wJegA6mcjYD0p7i9++mRL5niwX2yIWSpMMcB1plDXMwraZyn0VqYuXlOYYEQNsOOXcmGnIkRxMwEnqDVS6WSMDh0kRcLrWjockpErGlwSr60WLLUf2rDrW3MNI6cMMY//XQyHjGl0s7YWj1hjprsQWUGcCz7GGBxYYGbE4KGUWSx2gnCloxwC7ZOtxzSdKyNiY+uI9qxWiIxtezilH7CHlr3z/nWR+IKr+MB2ZGFbsZ//igS1nnokPW40Ipo23cchopITlDVVusdlHVUELTeNn9Svvzk-END CERTIFICATE-{CODE}But I had to put this instead:{ CODE code }LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUM2akNDQWRLZ0F3SUJBZ0lCQVRBTkJna3Foa2lHOXcwQkFRc0ZBREFtTVNRd0lnWURWUVFEREJ0dmNHVnUKYzJocFpuUXRjMmxuYm1WeVFERTBOelU0TnpreU1EWXdIaGNOTVRZeE1EQTNNakl5TmpRMldoY05NakV4TURBMgpNakl5TmpRM1dqQW1NU1F3SWdZRFZRUUREQnR2Y0dWdWMyaHBablF0YzJsbmJtVnlRREUwTnpVNE56a3lNRFl3CmdnRWlNQTBHQ1NxR1NJYjNEUUVCQVFVQUE0SUJEd0F3Z2dFS0FvSUJBUUM4ZTlINW1WZjZUMFZZekczY1VrWGsKVVNBckZTdGJaczFYUTBtT3FNMjVESy93UEo0NjROSGNZQlJsZ25PTnFkdmx3dS9zTUhUdzljSWVsV2k5cGVBZwpLNUVjb0RycDVzcFh3WS9OU2ptQnRFVjIrdyszRnZ2alpRaEdoZGU3OXZhZlRpUkFmQ0JKVnZoWkM2RHdHekg2CmM3YXhUTmpGODJXalExRzVsdjRwWHBhbmo0ektwWDREQ2NodUUxemV0MlVtRGtEdGwxdmNoby9laVRjNzM3QmcKclhPQ2F1M0xiVHRGbHcyQ2cxZ3prNVlsV1R6QjFEYXByUC81NStLczZkVUtLWDdXc1NBTEVydjZTajBSVzEvLwpDUTZPcXRBQ3pueVlqWFJISDl6TEJ5czdZVjI3Z2Z2eXF1amRWOE9iazY2c0kra1Q5UGY4alcwMkdWVXQvLzlSCkFnTUJBQUdqSXpBaE1BNEdBMVVkRHdFQi93UUVBd0lDcERBUEJnTlZIUk1CQWY4RUJUQURBUUgvTUEwR0NTcUcKU0liM0RRRUJDd1VBQTRJQkFRQzdPaG55cHpnbXBCTjYyR2dEYkZaVHNGU212eEpITmpLZVpmREpyMWkvcjJvWgphLzBTWjVRMk43QjV3SmVnQTZtY2pZRDBwN2k5KyttUkw1bml3WDJ5SVdTcE1NY0IxcGxEWE13cmFaeW4wVnFZCnVYbE9ZWUVRTnNPT1hjbUduSWtSeE13RW5xRFZTNldTTURoMGtSY0xyV2pvY2twRXJHbHdTcjYwV0xMVWYyckQKclczTU5JNmNNTVkvL1hReUhqR2wwczdZV2oxaGpwcnNRV1VHY0N6N0dHQnhZWUdiRTRLR1VXU3gyZ25DbG94dwpDN1pPdHh6U2RLeU5pWSt1STlxeFdpSXh0ZXppbEg3Q0hscjN6L25XUitJS3IrTUIyWkdGYnNaLy9pZ1Mxbm5vCmtQVzQwSXBvMjNjY2hvcElUbERWVnVzZGxIVlVFTFRlTm45U3Z2emsKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo={code}
[JIRA] (JENKINS-38829) "Kubernetes server certificate key" not working
Title: Message Title akostadinov commented on JENKINS-38829 Re: "Kubernetes server certificate key" not working Hello again. Looking at your test cases I understood and tested what the issue is. The certificate you test with is actually a PEM encoded cert but then base64 encoded. I think that it makes more sense to ask from user simply a PEM cert and base64 encode it upon passing to the kubernetes API. Also your new help text also indicates normal PEM encoding is needed while I could make it work only after additionally base64 encoding it. i.e. I'd expect that I need to put this in the field this: -BEGIN CERTIFICATE- MIIC6jCCAdKgAwIBAgIBATANBgkqhkiG9w0BAQsFADAmMSQwIgYDVQQDDBtvcGVu c2hpZnQtc2lnbmVyQDE0NzU4NzkyMDYwHhcNMTYxMDA3MjIyNjQ2WhcNMjExMDA2 MjIyNjQ3WjAmMSQwIgYDVQQDDBtvcGVuc2hpZnQtc2lnbmVyQDE0NzU4NzkyMDYw ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC8e9H5mVf6T0VYzG3cUkXk USArFStbZs1XQ0mOqM25DK/wPJ464NHcYBRlgnONqdvlwu/sMHTw9cIelWi9peAg K5EcoDrp5spXwY/NSjmBtEV2+w+3FvvjZQhGhde79vafTiRAfCBJVvhZC6DwGzH6 c7axTNjF82WjQ1G5lv4pXpanj4zKpX4DCchuE1zet2UmDkDtl1vcho/eiTc737Bg rXOCau3LbTtFlw2Cg1gzk5YlWTzB1DaprP/55+Ks6dUKKX7WsSALErv6Sj0RW1// CQ6OqtACznyYjXRHH9zLBys7YV27gfvyqujdV8Obk66sI+kT9Pf8jW02GVUt//9R AgMBAAGjIzAhMA4GA1UdDwEB/wQEAwICpDAPBgNVHRMBAf8EBTADAQH/MA0GCSqG SIb3DQEBCwUAA4IBAQC7OhnypzgmpBN62GgDbFZTsFSmvxJHNjKeZfDJr1i/r2oZ a/0SZ5Q2N7B5wJegA6mcjYD0p7i9++mRL5niwX2yIWSpMMcB1plDXMwraZyn0VqY uXlOYYEQNsOOXcmGnIkRxMwEnqDVS6WSMDh0kRcLrWjockpErGlwSr60WLLUf2rD rW3MNI6cMMY//XQyHjGl0s7YWj1hjprsQWUGcCz7GGBxYYGbE4KGUWSx2gnCloxw C7ZOtxzSdKyNiY+uI9qxWiIxtezilH7CHlr3z/nWR+IKr+MB2ZGFbsZ//igS1nno kPW40Ipo23cchopITlDVVusdlHVUELTeNn9Svvzk -END CERTIFICATE- But I had to put this instead:
[JIRA] (JENKINS-38933) allow mounting secrets to pod
Title: Message Title akostadinov commented on JENKINS-38933 Re: allow mounting secrets to pod My bad, I didn't notice the "secret volume" type under "volumes" when I looked for the option. I'll try it out. Thank you! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38933) allow mounting secrets to pod
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-38933 allow mounting secrets to pod Change By: akostadinov Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38933) allow mounting secrets to pod
Title: Message Title akostadinov created an issue Jenkins / JENKINS-38933 allow mounting secrets to pod Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Oct/12 4:52 PM Priority: Major Reporter: akostadinov When launching slaves especially if master lives outside target environment, there is often a need to provide slaves with additional information like CAs, passwords, etc. Would be very useful to allow mounting secrets to pods launched by the kubernetes slaves plugin. Add Comment
[JIRA] (JENKINS-38829) "Kubernetes server certificate key" not working
Title: Message Title akostadinov created an issue Jenkins / JENKINS-38829 "Kubernetes server certificate key" not working Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Oct/07 8:18 PM Priority: Critical Reporter: akostadinov In JENKINS-29213 a parameter has been added "Kubernetes server certificate key". It has no help but looking at the relevant commit I see it should read PEM formatted server certificate. This doesn't appear to work for me. Jenkins server doesn't use a self-signed certificate, it uses a corporate internal CA thus I put into the field the server certificate and it's CAs. This doesn't work. I tried changing order of certificates to no avail. I think help needs to be added about format and order of certificates so that they can work. Full backtrace: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1884) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:276) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:270) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1341) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:153) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:868) at sun.security.ssl.Handshaker.process_record(Handshaker.java:804) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1016) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1312) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1339)
[JIRA] (JENKINS-38626) allow conditional custom tools installation
Title: Message Title akostadinov created an issue Jenkins / JENKINS-38626 allow conditional custom tools installation Issue Type: New Feature Assignee: Oleg Nenashev Components: customtools-plugin Created: 2016/Sep/30 1:03 PM Priority: Major Reporter: akostadinov Hello, it will be very useful to make custom tools installation plug-in allow conditional installation of tools based on job parameters. e.g. I have a job that can run against Firefox and Chrome. I want chrome installed only if current build parameters suggest that chrome will be used. This is especially useful when slaves are provisioned just for a single build, e.g. docker/kubernetes. Without such option, the tool will always take time and bandwidth to install regardless current build parameter selection. Add Comment
[JIRA] [core] (JENKINS-17116) gracefull job termination
Title: Message Title
akostadinov commented on JENKINS-17116
Re: gracefull job termination
I am wondering, because universal solution might not be that easy, would it be possible to have a hook {{ gracefulShutdown }} where one can have a custom implementation before the regular {{ kill -9 }} kicks in?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov commented on JENKINS-33468 Re: CLONE - Sandbox cannot handle methods Groovy provides additionally My immediate issue is resolved by upgrading to email-ext-plugin from master (1.42.SNAPSHOT) where support for script sandboxing is dropped. But I guess it's still good to have this issue fixed in the sandbox plug-in. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov edited a comment on JENKINS-33468 Re: CLONE - Sandbox cannot handle methods Groovy provides additionally Issue seems same as JENKINS-25119 just something missed.Update: Just see I'm not using latest plug-in. Update center lags behind. Trying latest one now. update 2: same with 1.17 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-33468 CLONE - Sandbox cannot handle methods Groovy provides additionally Change By: akostadinov Environment: RHEL x86_64, Jenkins 1.642.2, Email Extension Plugin 2.38.2, script-security 1. 15 17 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov edited a comment on JENKINS-33468 Re: CLONE - Sandbox cannot handle methods Groovy provides additionally Issue seems same as JENKINS-25119 just something missed. Update: Just see I'm not using latest plug-in. Update center lags behind. Trying latest one now. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-33468 CLONE - Sandbox cannot handle methods Groovy provides additionally Change By: akostadinov Environment: Windows 8 64bit RHEL x86_64 , Jenkins 1. 509 642 . 4 2 , groovy-postbuild Email Extension Plugin 2. 0 38.2 , script-security 1. 6 15 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title
akostadinov updated an issue
Jenkins / JENKINS-33468
CLONE - Sandbox cannot handle methods Groovy provides additionally
Change By:
akostadinov
Running Basically creating a following pre-send script for editable email plug-in results in the exception below. Here's the part of the script blowing: {code :java } "30".toInteger def artifactNamed ( build, name ) { return build.artifacts.find { it.fileName == name } ; } {code} Results following error Console log :{ noformat code:java } Setting up sandbox for pre-send scriptgroovy.lang.MissingPropertyException: No such property: it for class: Script1 at org. jenkinsci codehaus . plugins groovy . scriptsecurity runtime . ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:454) at org.kohsuke.groovy. sandbox. RejectedAccessException impl.Checker$4.call(Checker.java : unclassified method 243) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onGetProperty(GroovyInterceptor. java :52) at org . kohsuke.groovy.sandbox.GroovyValueFilter.onGetProperty(GroovyValueFilter.java:73) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:221) at org.kohsuke.groovy.sandbox.impl.Checker$checkedGetProperty.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:177) at Script1$_artifactNamed_closure1.doCall(Script1.groovy:2) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java. lang. String toInteger reflect.Method.invoke(Method.java:606) at org. jenkinsci codehaus . plugins groovy . scriptsecurity reflection . CachedMethod.invoke(CachedMethod.java:90) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233) at org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:903) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:39) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.BooleanReturningMethodInvoker.invoke(BooleanReturningMethodInvoker.java:49) at org.codehaus.groovy.runtime.callsite.BooleanClosureWrapper.call(BooleanClosureWrapper.java:52) at org.codehaus.groovy.runtime.DefaultGroovyMethods.find(DefaultGroovyMethods.java:2695) at org.codehaus.groovy.runtime.dgm$261.invoke(Unknown Source) at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoMetaMethodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:271) at
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov commented on JENKINS-33468 Re: CLONE - Sandbox cannot handle methods Groovy provides additionally Issue seems same as JENKINS-25119 just something missed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [script-security-plugin] (JENKINS-33468) CLONE - Sandbox cannot handle methods Groovy provides additionally
Title: Message Title akostadinov created an issue Jenkins / JENKINS-33468 CLONE - Sandbox cannot handle methods Groovy provides additionally Issue Type: Bug Assignee: Jesse Glick Components: script-security-plugin Created: 10/Mar/16 9:37 PM Environment: Windows 8 64bit, Jenkins 1.509.4, groovy-postbuild 2.0, script-security 1.6 Priority: Major Reporter: akostadinov Running a following script "30".toInteger(); Results following error: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.String toInteger at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:63) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:111) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:108) at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall.callStatic(Unknown Source) at
[JIRA] [mask-passwords-plugin] (JENKINS-31985) mask passwords from Credentials Binding Plugin
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-31985 mask passwords from Credentials Binding Plugin Change By: akostadinov Comment: [~jglick], which issue did you consider to be the duplicate? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mask-passwords-plugin] (JENKINS-31985) mask passwords from Credentials Binding Plugin
Title: Message Title akostadinov commented on JENKINS-31985 Re: mask passwords from Credentials Binding Plugin Jesse Glick, which issue did you consider to be the duplicate? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mask-passwords-plugin] (JENKINS-31985) mask passwords from Credentials Binding Plugin
Title: Message Title akostadinov commented on JENKINS-31985 Re: mask passwords from Credentials Binding Plugin JENKINS-24805 is about same thing but in the Credentials Binding Plugin component. I'm not sure where the solution should live but I think it needs to be implemented in the mask plug-in. So creating an issue in this component. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mask-passwords-plugin] (JENKINS-31985) mask passwords from Credentials Binding Plugin
Title: Message Title akostadinov created an issue Jenkins / JENKINS-31985 mask passwords from Credentials Binding Plugin Issue Type: Improvement Assignee: Oleg Nenashev Components: mask-passwords-plugin Created: 09/Dec/15 5:02 PM Priority: Major Reporter: akostadinov Would really help if passwords from Credentials Binding Plugin are also masked. It's the best approach so far to include credentials in builds as credentials plugin is the unified way to store credentials in jenkins. Add Comment
[JIRA] [git-plugin] (JENKINS-31267) cannot push non-HEAD to remote repo
Title: Message Title akostadinov created an issue Jenkins / JENKINS-31267 cannot push non-HEAD to remote repo Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 29/Oct/15 4:44 PM Environment: 1.609.3 Priority: Minor Reporter: akostadinov Git publisher plug-in can push current HEAD to remote repo but does not allow arbitrary branch specifier. What I'm doing is performing repo mirror periodically, e.g. git push mirror origin/master:master git push mirror origin/another_branch:another_branch I have a workaround to use ssh agent environemnt plug-in + shell commands but would be nice if option to specify custom source branch is possible. P.S. I see that mirroring can be done but only for a single branch per job definition. So if you have multiple branches to mirror it means extrapolating job number and making job management harder.
[JIRA] [multi-slave-config-plugin] (JENKINS-31224) allow replacing ${NUM} with the number of the slave
Title: Message Title
akostadinov created an issue
Jenkins / JENKINS-31224
allow replacing ${NUM} with the number of the slave
Issue Type:
New Feature
Assignee:
rsandell
Components:
multi-slave-config-plugin
Created:
28/Oct/15 12:24 PM
Priority:
Major
Reporter:
akostadinov
It would be very helpful if one can put $ {NUM} in multi-slave configuration and have that replaced with the slave numeber beeing added/configured. For example configure 10 slaves on one machine like:
Workspace: /home/slave${NUM}
Add Comment
[JIRA] [core] (JENKINS-23722) Anonymous treated like "Everybody" no as just Anonymous
Title: Message Title akostadinov commented on JENKINS-23722 Re: Anonymous treated like "Everybody" no as just Anonymous I see no point in removing permissions granted to Anonymous. If Anonymous has more permissions, then a user can just skip auth and have them. So what's the benefit authenticated user having less permissions than Anonymous? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov commented on JENKINS-30719
Re: cannot specify ${something} string in parameters
Excuse me for stupid explanation. Here's the hypothetical scenario: 1. you have a parameter `VERSION` in the job config 2. you want to also configure in a parameter that will have as a value literal `something_$ {VERSION}_something` How is it possible to prevent the `${VERSION}
` string in the second parameter to be expanded? I don't currently have that exact use case. But I thought it is possible to escape the `$` character such that variables are not expanded.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov edited a comment on JENKINS-30719
Re: cannot specify ${something} string in parameters
Excuse me for stupid explanation. Here's the hypothetical scenario:1. you have a parameter `VERSION` in the job config2. you want to also configure in a parameter that will have as a value literal {noformat} `something_${VERSION}_something` {noformat} How is it possible to prevent the string in the second parameter to be expanded? I don't currently have that exact use case. But I thought it is possible to escape the `$` character such that variables are not expanded.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov edited a comment on JENKINS-30719
Re: cannot specify ${something} string in parameters
Excuse me for stupid explanation. Here's the hypothetical scenario:1. you have a parameter `VERSION` in the job config2. you want to also configure in a parameter that will have as a value literal `something_${VERSION}_something`How is it possible to prevent the {code}${VERSION}{code} string in the second parameter to be expanded? I don't currently have that exact use case. But I thought it is possible to escape the `$` character such that variables are not expanded.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov edited a comment on JENKINS-30719
Re: cannot specify ${something} string in parameters
Excuse me for stupid explanation. Here's the hypothetical scenario:1. you have a parameter `VERSION` in the job config2. you want to also configure in a parameter that will have as a value literal `something_${VERSION}_something`How is it possible to prevent the{code :java }${VERSION}{code}string in the second parameter to be expanded? I don't currently have that exact use case. But I thought it is possible to escape the `$` character such that variables are not expanded.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov edited a comment on JENKINS-30719
Re: cannot specify ${something} string in parameters
Excuse me for stupid explanation. Here's the hypothetical scenario:1. you have a parameter `VERSION` in the job config2. you want to also configure in a parameter that will have as a value literal `something_${VERSION}_something`How is it possible to prevent the ` {code:java} ${VERSION} ` {code} string in the second parameter to be expanded? I don't currently have that exact use case. But I thought it is possible to escape the `$` character such that variables are not expanded.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov commented on JENKINS-30719
Re: cannot specify ${something} string in parameters
You're freakin' right!
So is there a way to escape parameters that may or may not exist in configuration? I remember in the past there was some code handling `\` escape when doing param expansion. For my current usage it is not an issue but I wonder if there is a way to escape parameter expansion when literal value is needed.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov updated an issue
Jenkins / JENKINS-30719
cannot specify ${something} string in parameters
Change By:
akostadinov
Not sure I've got correct component. Anyway, when I try to put a parameter value of containing literal `${something}` then exception is thrown. If I escape it like `\${something}`, then it works but value is passed down with the `\` character instead of having it removed. So AFAIU there is no way to pass down literal `${}` as a parameter with jenkins.Here's an exception: {code} javax.servlet.ServletException: java.lang.IllegalArgumentException: Illegal choice for parameter IMAGE_PRE: registry.access.redhat.com/openshift3/ose-${component}:${version} {code:java} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at com.sonymobile.jenkins.plugins.kerberossso.KerberosSSOFilter.doFilter(KerberosSSOFilter.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:85) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [core] (JENKINS-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov created an issue
Jenkins / JENKINS-30719
cannot specify ${something} string in parameters
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
30/Sep/15 1:19 PM
Priority:
Major
Reporter:
akostadinov
Not sure I've got correct component. Anyway, when I try to put a parameter value of containing literal `$ {something}` then exception is thrown. If I escape it like `\${something}
`, then it works but value is passed down with the `\` character instead of having it removed. So AFAIU there is no way to pass down literal `${}` as a parameter with jenkins.
Here's an exception: javax.servlet.ServletException: java.lang.IllegalArgumentException: Illegal choice for parameter IMAGE_PRE: registry.access.redhat.com/openshift3/ose-$ {component}:${version}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at
[JIRA] [docker-plugin] (JENKINS-30422) docker pull image: Unrecognized field "stream"
Title: Message Title akostadinov commented on JENKINS-30422 Re: docker pull image: Unrecognized field "stream" With the versions I describe in issue description I see the errors in jenkins system log (Jenkins -> Manage -> System log). The errors appear when a container is to be started (e.g. a job is scheduled that needs an executor). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rebuild-plugin] (JENKINS-30532) rebuild shuld not store last used password non-stored
Title: Message Title akostadinov created an issue Jenkins / JENKINS-30532 rebuild shuld not store last used password non-stored Issue Type: Bug Assignee: ragesh_nair Components: rebuild-plugin Created: 17/Sep/15 10:41 PM Priority: Critical Reporter: akostadinov It's very bad that non-stored password parameters are stored for future rebuild. That's not what user expect - i.e. non-stored password should not be stored anywhere no matter what. This is to have some basic password security. Add Comment
[JIRA] [jclouds-plugin] (JENKINS-30500) jclouds docker support
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-30500 jclouds docker support Change By: akostadinov Labels: docker jclouds Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jclouds-plugin] (JENKINS-30500) jclouds docker support
Title: Message Title akostadinov created an issue Jenkins / JENKINS-30500 jclouds docker support Issue Type: New Feature Assignee: abayer Attachments: jclouds_docker.png Components: jclouds-plugin Created: 16/Sep/15 8:07 PM Labels: jclouds Priority: Minor Reporter: akostadinov Hello, tried to setup jclouds plugin to launch docker slaves. I had to build it from master as it includes latest jclouds. Basically I had to add the `docker` artifact and I've got ability to select docker type slaves. But I'm hitting an issue that docker connection cannot be established. Cannot connect to specified cloud, please check the identity and credentials: Guice creation errors: 1) Error in custom provider, java.lang.RuntimeException: java.io.FileNotFoundException: ddd (No such file or directory) while locating org.jclouds.http.okhttp.config.OkHttpCommandExecutorServiceModule$OkHttpClientProvider at
[JIRA] [docker-plugin] (JENKINS-30422) docker pull image: Unrecognized field "stream"
Title: Message Title akostadinov created an issue Jenkins / JENKINS-30422 docker pull image: Unrecognized field "stream" Issue Type: Bug Assignee: Kanstantsin Shautsou Components: docker-plugin Created: 11/Sep/15 8:35 PM Environment: linux, fedora 22, jenkins 1.609.3, remote docker host docker 1.8.1.fc22, and docker plug-in 0.13.0 Labels: docker Priority: Critical Reporter: akostadinov Trying docker plugin with docker 1.8.1.fc22 and docker plug-in 0.13.0 and jenkins LTS 1.609.3 You'll see error below. One more strange thing I see is that in jenkins system configuration I see "Credentials" under docker cloud. But I can select no creadentials. It gives only "none" as an option. Under image template I see credentials and I can select them so perhaps it is ok. The error jenkins system log is: Sep 11, 2015 4:10:33 PM INFO
[JIRA] [ldap-plugin] (JENKINS-29162) Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ...
Title: Message Title akostadinov commented on JENKINS-29162 Re: Jenkins internal user in order to be able to log-in under an authentication failure with LDAP AD, ... I'd advocate for support of non-LDAP users. Sometimes one needs a machine account to just access jenkins. Setting up an LDAP account might be an issue with IT. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-27062) email-ext-plugin: configurable attachment mime type
akostadinov edited a comment on JENKINS-27062 email-ext-plugin: configurable attachment mime type I found out what's the issue. The local jvm does not have default mime.types defined. When I ln -s /etc/mime.types ~/.mime.types Without this all files were translated to application/octet-stream. The jvm finds the file and uses it to correctly map files to mime types. I filed a bug with the OS. If you believed there is no room for improvement for the plug-in, you can close the issue. Regards and thank you for looking into this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-27062) email-ext-plugin: configurable attachment mime type
akostadinov commented on JENKINS-27062 email-ext-plugin: configurable attachment mime type I found out what's the issue. The local jvm does not have default mime.types defined. When I ln -s /etc/mime.types ~/.mime.types Without this all files were translated to application/octet-stream. The jvm finds the file and uses it to correctly map files to mime types. I filed a bug with the OS. If you believed there is no room for improvement for the plug-in, you can close the issue. Regards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-27062) email-ext-plugin: configurable attachment mime type
akostadinov
commented on JENKINS-27062
email-ext-plugin: configurable attachment mime type
ok, used a very simple groovy script:
import javax.activation.MimetypesFileTypeMap;
println MimetypesFileTypeMap.getDefaultFileTypeMap().getContentType("filename")
And it appears local java version returns `application/octet-stream` while newer openjdk returns `text/html`.
Do you think anything can be done on the plugin side or is my only option to get back to java vendor/change java version used? Any other workarounds you may know? Using a pre-send script to change mime-type?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [email-ext-plugin] (JENKINS-27062) email-ext-plugin: configurable attachment mime type
akostadinov commented on JENKINS-27062 email-ext-plugin: configurable attachment mime type I tried attaching a proper HTML. Firefox shows it as standard compliance mode. Still attached as and application/octet-stream. Let me try to craft a reproducer. I'll need a little time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-27062) email-ext-plugin: configurable attachment mime type
akostadinov updated JENKINS-27062 email-ext-plugin: configurable attachment mime type The attached empty body HTML is also attached as `application/octet-stream`. We're running latest stable jenkins release `1.580.3`. Latest email-ext-plugin. Openjdk 1.6 running on linux. JDK is not updated very recently though. Change By: akostadinov (23/Feb/15 7:12 AM) Attachment: TCMS_backup.fake.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-27062) email-ext-plugin: configurable attachment mime type
akostadinov created JENKINS-27062 email-ext-plugin: configurable attachment mime type Issue Type: New Feature Assignee: Alex Earl Components: email-ext-plugin Created: 21/Feb/15 4:58 PM Description: Hello, using email-ext-plugin and hit a problem. I want to attach an html report to the message but it is attached as Content-Type: application/octet-stream; name=report.html As a result mailers like thunderbird display garbled content (or not at all). I think it would be very useful to have ability to specify content type of attached files (e.g. text/html). Project: Jenkins Priority: Minor Reporter: akostadinov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-27062) email-ext-plugin: configurable attachment mime type
akostadinov edited a comment on JENKINS-27062 email-ext-plugin: configurable attachment mime type Good points. I looked again and it appears my htmls were not generated with proper HTML header and footer. Let me try again with proper HTML and I'll report back. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [email-ext-plugin] (JENKINS-27062) email-ext-plugin: configurable attachment mime type
akostadinov commented on JENKINS-27062 email-ext-plugin: configurable attachment mime type Good points. I looked again and it looks my htmls were not generated with proper HTML header and footer. Let me try again with proper HTML and I'll report back. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-13432) ec2 plugin - support for the new amazon instance types - especially medium
akostadinov created JENKINS-13432: - Summary: ec2 plugin - support for the new amazon instance types - especially medium Key: JENKINS-13432 URL: https://issues.jenkins-ci.org/browse/JENKINS-13432 Project: Jenkins Issue Type: Improvement Components: ec2 Affects Versions: current Reporter: akostadinov Assignee: Kohsuke Kawaguchi ec2 plugin - support for the new amazon instance types - especially medium It's hard to test 32bit AMIs that demand more memory than 1.7G -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
