[JIRA] (JENKINS-62195) ec2-1.50.2 doesn't work with SSH <7.5
Title: Message Title Ryan Campbell commented on JENKINS-62195 Re: ec2-1.50.2 doesn't work with SSH <7.5 Noting in case it isn't clear, that a valid workaround is to update the ssh client to a more recent version which supports these more secure options. 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.206127.1588831961000.23633.1588944960262%40Atlassian.JIRA.
[JIRA] (JENKINS-53158) Pipelines leak OneOffExecutors when triggered on a temporary offline master
Title: Message Title Ryan Campbell commented on JENKINS-53158 Re: Pipelines leak OneOffExecutors when triggered on a temporary offline master Seems like behavior similar to JENKINS-57304 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.193168.1534849944000.2237.1578172200180%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Ryan Campbell updated an issue Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Ryan Campbell Component/s: cloudbees-jenkins-advisor-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202395.1570521598000.8881.1571243880401%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Ryan Campbell commented on JENKINS-59707 Re: Give more details in the connection success panel Really nice diagnostics – great work! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202408.1570569525000.8879.1571243340124%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Ryan Campbell commented on JENKINS-59707 Re: Give more details in the connection success panel I don't think we want to expose the # of probes or Advisor version. I think we just want to say something like "Connection successful" for the Server: I really like showing the previous upload vs. next. Where is that data coming from? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202408.1570569525000.7250.1571076720640%40Atlassian.JIRA.
[JIRA] (JENKINS-59644) Upgrade Jenkins core pre-requisite to 2.138.4
Title: Message Title Ryan Campbell commented on JENKINS-59644 Re: Upgrade Jenkins core pre-requisite to 2.138.4 1 Agree, we only support 2.138 now anyway. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202334.1570111402000.596.1570111920125%40Atlassian.JIRA.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Ryan Campbell updated an issue Jenkins / JENKINS-57154 Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Change By: Ryan Campbell Summary: HTTP ERROR 403 Regression in github-oauth-plugin 0.32 breaks /configureSecurity page 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.198903.1556022985000.21241.1559673420882%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56825) Don't redact URL in support-core anonymization
Title: Message Title Ryan Campbell commented on JENKINS-56825 Re: Don't redact URL in support-core anonymization Not clear what to do here. I can see how the URL may contain proprietary information, such as the name of a secret project. 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.198481.1554062136000.20654.1559649480209%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55815) Allow API access with Google Login Plugin
Title: Message Title Ryan Campbell closed an issue as Won't Do Please reopen with details on why the Jenkins API key is insufficient Jenkins / JENKINS-55815 Allow API access with Google Login Plugin Change By: Ryan Campbell Status: Open Closed Resolution: Won't Do 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-55815) Allow API access with Google Login Plugin
Title: Message Title Ryan Campbell commented on JENKINS-55815 Re: Allow API access with Google Login Plugin This is already possible by setting an API key for your user. https://support.cloudbees.com/hc/en-us/articles/115003090592-How-to-re-generate-my-Jenkins-user-token There isn't a way to authenticate with your Google password via API that I'm aware of anyway. But the above should work fine. 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-54770) A new client object is created each time the plugin needs to connection to K8s
Title: Message Title Ryan Campbell commented on JENKINS-54770 Re: A new client object is created each time the plugin needs to connection to K8s This was fixed in 1.13.6 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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Ryan Campbell assigned an issue to Alex Taylor Jenkins / JENKINS-53146 TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step Change By: Ryan Campbell Assignee: Oleg Nenashev Alex Taylor 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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title
Ryan Campbell commented on JENKINS-53146
Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
In, JENKINS-19892, Oleg says:
Plugin exports ${toolName_HOME} or ${TOOLNAME_HOME} according to options. In the current state, shese variables are being exported to build steps based on remote launchers (execute shells, etc.). Steps like envInject or parameterizedTrigger (which don't invoke external process) have access to toolVersion only. I hope to fix this issue at some point; as a workaround you can write variable to file and then inject it to the environment using EnvInject build step.
So I think this is exactly the issue – perhaps this bug report is a dupe of JENKINS-19892
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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Ryan Campbell edited a comment on JENKINS-53146 Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step The problem may actually be in the Custom Build Tools plugin. The [CustomToolInstallWrapper#setup(AbstractBuild,Launcher,BuildListener)|https://github.com/jenkinsci/custom-tools-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/customtools/CustomToolInstallWrapper.java#L116] returns a hudson.model.Environment, but it seems like these enviroment variables are not reflected in the EnvVars returned by build.getEnvironment(listener).So the CustomToolInstallWrapper is perhaps only affecting processes which are launched and not actually exposing environment variables to other evaluations like this one.In this case, it seems like the fix is for Custom tools plugin to extend the hudson.model.EnvironmentContributor to fix this problem. 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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Ryan Campbell commented on JENKINS-53146 Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step The problem may actually be in the Custom Build Tools plugin. The CustomToolInstallWrapper#setup(AbstractBuild,Launcher,BuildListener) returns a hudson.model.Environment, but it seems like these enviroment variables are not reflected in the EnvVars returned by build.getEnvironment(listener). So the CustomToolInstallWrapper is perhaps only affecting processes which are launched and not actually exposing environment variables to other evaluations like this one. 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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title
Ryan Campbell edited a comment on JENKINS-53146
Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Perhaps the evaluation is incorrectly done in [FileSystemScriptSource::getSecureGroovyScript(FilePath,AbstractBuild,TaskListener|https://github.com/jenkinsci/groovy-plugin/blob/master/src/main/java/hudson/plugins/groovy/FileSystemScriptSource.java#L30]):{code}public SecureGroovyScript getSecureGroovyScript(FilePath projectWorkspace, AbstractBuild build, TaskListener listener) throws IOException, InterruptedException {EnvVars env = build.getEnvironment(listener);String expandedScriptFile = env.expand(this.scriptFile);String text = new FilePath(projectWorkspace, expandedScriptFile).readToString();return new SecureGroovyScript(text, true, null).configuring(ApprovalContext.create()/* unused but just in case: */.withItem(build.getParent()));}{code} After debugging this, we see that "env" does not contain an environment variable for the custom tool.
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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title
Ryan Campbell edited a comment on JENKINS-53146
Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Perhaps the evaluation is incorrectly done in [FileSystemScriptSource::getSecureGroovyScript(FilePath,AbstractBuild,TaskListener|https://github.com/jenkinsci/groovy-plugin/blob/master/src/main/java/hudson/plugins/groovy/FileSystemScriptSource.java#L30] ) :{code}public SecureGroovyScript getSecureGroovyScript(FilePath projectWorkspace, AbstractBuild build, TaskListener listener) throws IOException, InterruptedException {EnvVars env = build.getEnvironment(listener);String expandedScriptFile = env.expand(this.scriptFile);String text = new FilePath(projectWorkspace, expandedScriptFile).readToString();return new SecureGroovyScript(text, true, null).configuring(ApprovalContext.create()/* unused but just in case: */.withItem(build.getParent()));}{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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title
Ryan Campbell commented on JENKINS-53146
Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Perhaps the evaluation is incorrectly done in FileSystemScriptSource::getSecureGroovyScript(FilePath,AbstractBuild,TaskListener:
public SecureGroovyScript getSecureGroovyScript(FilePath projectWorkspace, AbstractBuild build, TaskListener listener) throws IOException, InterruptedException {
EnvVars env = build.getEnvironment(listener);
String expandedScriptFile = env.expand(this.scriptFile);
String text = new FilePath(projectWorkspace, expandedScriptFile).readToString();
return new SecureGroovyScript(text, true, null).configuring(ApprovalContext.create()/* unused but just in case: */.withItem(build.getParent()));
}
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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Ryan Campbell commented on JENKINS-53146 Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step Noting that variables contributed by envInject ARE properly expanded by the System Groovy Step. 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-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title
Ryan Campbell updated an issue
Jenkins / JENKINS-53146
TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Change By:
Ryan Campbell
h2. Summary Attempting to use the TOOLNAME_HOME variable within an Execute system Groovy script build step causes error due to no variable expansion.java.io.FileNotFoundException: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory)h2. Steps to reproduce # Install custom build tool plugin and system groovy script plugin # Create a custom build tool called "TestTool" which downloads a file from some URL # Create a freestyle job # In the freestyle job, select "Install custom tools" and a Tool which has a Tool Selection of "TestTool". Be sure to select the the "Convert #ToolName_HOME variables to the upper-case" !Meet_-_System_Groovy_Problem_from_ZD_64348.png! # In the build steps section of the freestyle job, add a step to "Execute System Groovy script" with the "Groovy Script File" option selected and the path to the groovy script file should be "TESTTOOL_HOME" !FreeEnvVar_Config__Jenkins_.png|width=864,height=303! # Save the jobh2. Expect behaviorWhen you run the job, the TESTTOOL_HOME variable is correctly explanded before the System Groovy Step evalutes the file locationh2. Actual behaviorWhen you run the job, the TESTTOOL_HOME variable is not corretly expanded by the System Groovy Step, resulting in an error like this:{code:java}FATAL: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory)java.io.FileNotFoundException: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory)at java.io.FileInputStream.open0(Native Method)at java.io.FileInputStream.open(FileInputStream.java:195)at java.io.FileInputStream.(FileInputStream.java:138)at hudson.FilePath.read(FilePath.java:1754)at hudson.FilePath.readToString(FilePath.java:1855)at hudson.plugins.groovy.FileSystemScriptSource.getSecureGroovyScript(FileSystemScriptSource.java:31)at hudson.plugins.groovy.SystemGroovy.run(SystemGroovy.java:95)at hudson.plugins.groovy.SystemGroovy.perform(SystemGroovy.java:59)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)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:534)at hudson.model.Run.execute(Run.java:1728)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:407){code}
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title
Ryan Campbell updated an issue
Jenkins / JENKINS-53146
TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Change By:
Ryan Campbell
Attempting to use the TOOLNAME_HOME variable within an Execute system Groovy script build step causes error due to no variable expansion.java.io.FileNotFoundException: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory)h2. Steps to reproduce # Install custom build tool plugin and system groovy script plugin # Create a custom build tool called "TestTool" which downloads a file from some URL # Create a freestyle job # In the freestyle job, select "Install custom tools" and a Tool which has a Tool Selection of "TestTool". Be sure to select the the "Convert #ToolName_HOME variables to the upper-case" !Meet_-_System_Groovy_Problem_from_ZD_64348.png! # In the build steps section of the freestyle job, add a step to "Execute System Groovy script" with the "Groovy Script File" option selected and the path to the groovy script file should be "TESTTOOL_HOME" !FreeEnvVar_Config__Jenkins_.png |width=864,height=303 !# Save the jobh2. Expect behaviorWhen you run the job, the TESTTOOL_HOME variable is correctly explanded before the System Groovy Step evalutes the file location h2. Actual behavior When you run the job, the TESTTOOL_HOME variable is not corretly expanded by the System Groovy Step, resulting in an error like this: {code :java }FATAL: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory)java.io.FileNotFoundException: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory)at java.io.FileInputStream.open0(Native Method)at java.io.FileInputStream.open(FileInputStream.java:195)at java.io.FileInputStream.(FileInputStream.java:138)at hudson.FilePath.read(FilePath.java:1754)at hudson.FilePath.readToString(FilePath.java:1855)at hudson.plugins.groovy.FileSystemScriptSource.getSecureGroovyScript(FileSystemScriptSource.java:31)at hudson.plugins.groovy.SystemGroovy.run(SystemGroovy.java:95)at hudson.plugins.groovy.SystemGroovy.perform(SystemGroovy.java:59)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)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:534)at hudson.model.Run.execute(Run.java:1728)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:407){code}
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title
Ryan Campbell updated an issue
Jenkins / JENKINS-53146
TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Change By:
Ryan Campbell
Attempting to use the TOOLNAME_HOME variable within an Execute system Groovy script build step causes error due to no variable expansion.java.io.FileNotFoundException: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory)h2. Steps to reproduce # Install custom build tool plugin and system groovy script plugin # Create a custom build tool called "TestTool" which downloads a file from some URL # Create a freestyle job # In the freestyle job, select "Install custom tools" and a Tool which has a Tool Selection of "TestTool". Be sure to select the the "Convert #ToolName_HOME variables to the upper-case" !Meet_-_System_Groovy_Problem_from_ZD_64348.png! # In the build steps section of the freestyle job, add a step to "Execute System Groovy script" with the "Groovy Script File" option selected and the path to the groovy script file should be "TESTTOOL_HOME" !FreeEnvVar_Config__Jenkins_.png!# Save the jobh2. Expect behaviorWhen you run the job, the TESTTOOL_HOME variable is correctly explanded before the System Groovy Step evalutes the file locationh2. Actual behavior When you run the job, the TESTTOOL_HOME variable is not corretly expanded by the System Groovy Step, resulting in an error like this:{code}FATAL: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory)java.io.FileNotFoundException: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory)at java.io.FileInputStream.open0(Native Method)at java.io.FileInputStream.open(FileInputStream.java:195)at java.io.FileInputStream.(FileInputStream.java:138)at hudson.FilePath.read(FilePath.java:1754)at hudson.FilePath.readToString(FilePath.java:1855)at hudson.plugins.groovy.FileSystemScriptSource.getSecureGroovyScript(FileSystemScriptSource.java:31)at hudson.plugins.groovy.SystemGroovy.run(SystemGroovy.java:95)at hudson.plugins.groovy.SystemGroovy.perform(SystemGroovy.java:59)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)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:534)at hudson.model.Run.execute(Run.java:1728)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:98)at hudson.model.Executor.run(Executor.java:407){code}
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title
Ryan Campbell updated an issue
Jenkins / JENKINS-53146
TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Change By:
Ryan Campbell
Attempting to use the TOOLNAME_HOME variable within an Execute system Groovy script build step causes error due to no variable expansion.java.io.FileNotFoundException: /jenkins-home/workspace/FreeEnvVar/${TESTTOOL_HOME}/script.groovy (No such file or directory) h2. Steps to reproduce # Install custom build tool plugin and system groovy script plugin # Create a custom build tool called "TestTool" which downloads a file from some URL # Create a freestyle job # In the freestyle job, select "Install custom tools" and a Tool which has a Tool Selection of "TestTool". Be sure to select the the "Convert #ToolName_HOME variables to the upper-case" !Meet_-_System_Groovy_Problem_from_ZD_64348.png! # In the build steps section of the freestyle job, add a step to "Execute System Groovy script" with the "Groovy Script File" option selected and the path to the groovy script file should be "TESTTOOL_HOME"
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
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Ryan Campbell updated an issue Jenkins / JENKINS-53146 TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step Change By: Ryan Campbell Attachment: Meet_-_System_Groovy_Problem_from_ZD_64348.png 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-35124) Allow limiting by domain without google apps
Title: Message Title Ryan Campbell closed an issue as Fixed Please just open a new issue rather than reopening one which has been completed for ages. Jenkins / JENKINS-35124 Allow limiting by domain without google apps Change By: Ryan Campbell Status: Reopened Closed Resolution: Fixed 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-51005) Unrecognized SSL message after logging in through Google OAuth
Title: Message Title Ryan Campbell resolved as Not A Defect Looks like an environmental issue, closing with correct resolution. Jenkins / JENKINS-51005 Unrecognized SSL message after logging in through Google OAuth Change By: Ryan Campbell Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-51005) Unrecognized SSL message after logging in through Google OAuth
Title: Message Title Ryan Campbell reopened an issue Jenkins / JENKINS-51005 Unrecognized SSL message after logging in through Google OAuth Change By: Ryan Campbell Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10160) When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast.
Title: Message Title Ryan Campbell commented on JENKINS-10160 Re: When the network is broken,then jenkins will query dns info in loop.The log file will grow up very fast. Patrick Rose, which pull request? I don't see it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50154) Webhook delivery failed as X-Hub-Signature did not match calculated
Title: Message Title Ryan Campbell commented on JENKINS-50154 Re: Webhook delivery failed as X-Hub-Signature did not match calculated Dave, do you have any log messages with the category org.jenkinsci.plugins.github.webhook? 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-49968) Core 2.110 is unable to select a branch source via the server dropdown
Title: Message Title Ryan Campbell edited a comment on JENKINS-49968 Re: Core 2.110 is unable to select a branch source via the server dropdown [~drulli] It seems like your upgrade of Prototype 1.7.3 broke Jenkins validation logic. [~danielbeck] Perhaps we should just roll this back? 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-49968) Core 2.110 is unable to select a branch source via the server dropdown
Title: Message Title Ryan Campbell commented on JENKINS-49968 Re: Core 2.110 is unable to select a branch source via the server dropdown Ulli Hafner It seems like your upgrade of Prototype 1.7.3 broke Jenkins validation logic. 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-48480) Getting deprecated protocols warning on first startup
Title: Message Title Ryan Campbell updated JENKINS-48480 jenkins-2.96 Jenkins / JENKINS-48480 Getting deprecated protocols warning on first startup Change By: Ryan Campbell Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
