[JIRA] (JENKINS-53100) SSH2 Easy uses the local directory to derive the default local filename
Title: Message Title John Czukkermann created an issue Jenkins / JENKINS-53100 SSH2 Easy uses the local directory to derive the default local filename Issue Type: Bug Assignee: Jerry Cai Attachments: image-2018-08-17-11-18-01-939.png Components: ssh2easy-plugin Created: 2018-08-17 15:19 Environment: Jenkins 2.121.3, SSH2 Easy Plugin 1.4 Priority: Major Reporter: John Czukkermann When the local filename is left empty, the local file is saved as /tmp/tmp. The plugin should use the filename of the remote file as the default fileName (just like sftp would do). In this case, I expected /tmp/zosmf-jars.zip. Add Comment
[JIRA] (JENKINS-53099) SSH2 Easy does not support build parameters for filenames and paths
Title: Message Title John Czukkermann created an issue Jenkins / JENKINS-53099 SSH2 Easy does not support build parameters for filenames and paths Issue Type: Bug Assignee: Jerry Cai Attachments: image-2018-08-17-10-59-21-284.png Components: ssh2easy-plugin Created: 2018-08-17 14:59 Environment: Jenkins 2.121.3, SSH2 Easy Plugin 1.4 Priority: Major Reporter: John Czukkermann The plugin does not support the use of build parameters being used in the build step. Add Comment
[JIRA] (JENKINS-52942) Load Options load directory doesn't substitute a parameter
Title: Message Title John Czukkermann commented on JENKINS-52942 Re: Load Options load directory doesn't substitute a parameter Related to this, possibly a separate issue, the Poll SCM support does not substitute the build parameter for the workspace/stream name either. This issue is a big problem for me because my team develops in multiple streams. I don't want to create/maintain different Jenkins jobs for each such stream. I want one job that does the thing I need it to do using the stream/workspace I specify in the build parameter. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52942) Load Options load directory doesn't substitute a parameter
Title: Message Title John Czukkermann updated an issue Jenkins / JENKINS-52942 Load Options load directory doesn't substitute a parameter Change By: John Czukkermann Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52942) Load Options load directory doesn't substitute a parameter
Title: Message Title
John Czukkermann created an issue
Jenkins / JENKINS-52942
Load Options load directory doesn't substitute a parameter
Issue Type:
Improvement
Assignee:
Unassigned
Attachments:
image-2018-08-08-14-37-37-895.png
Components:
teamconcert-plugin
Created:
2018-08-08 18:37
Environment:
Running on RHEL 7. Jenkins 2.121.2. Team Concert Plugin 1.2.0.5
Priority:
Major
Reporter:
John Czukkermann
The issue is with the Load Directory entry in the Load Options section of the SCM tab for the parameterized job I have defined. The job has a parameter named rtc-workspace. I want to specify ${rtc-workspace} as the load directory and have the actual directory be the substituted value for the parameter. The plugin is not performing this substitution.
Add Comment
