[JIRA] (JENKINS-58741) Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin

[goel.shashank91@gmail.com (JIRA)]

Shashank Goel created an issue

Jenkins / JENKINS-58741 Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin Issue Type: Bug Assignee: Unassigned Components: publish-over-ssh-plugin Created: 2019-07-31 14:44 Environment: Jenkins 2.138.1 Publish over SSH 1.20.1 Labels: publish-over-ssh Priority: Minor Reporter: Shashank Goel I've more than a dozen environment with similar build configuration and artifacts to be uploaded from the Jenkins server. I pull up the code from SVN and then modifies it according to the target Environment (taking target Environment Name as parameters from User) and then modifies that environment-specific details in the artifacts and then upload it to the target server using Publish over SSH plugin. Now, this was okay until I had 6 Environment but the servers are increasing day-by-day for me and it is hard to configure the target server every time. ANd I have 12 such build jobs. It would be helpful if I could configure Environment Variables in the Server Name and then the plugin could actually search for the server in the list of configured servers. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[goel.shashank91@gmail.com (JIRA)]

Shashank Goel updated an issue

Jenkins / JENKINS-58741

Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin

Change By: Shashank Goel Issue Type: Bug Improvement

Add Comment

[goel.shashank91@gmail.com (JIRA)]

Shashank Goel updated an issue

Jenkins / JENKINS-58741 Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin Change By: Shashank Goel

I've more than a dozen environment with similar build configuration and artifacts to be uploaded from the Jenkins server. I pull up the code from SVN and then modifies it according to the target Environment (taking target Environment Name as parameters from User) and then modifies that environment-specific details in the artifacts and then upload it to the target server using Publish over SSH plugin. Now, this was okay until I had 6 Environment but the servers are increasing day-by-day for me and it is hard to configure the target server every time. ANd Moreover, I have 12 such build jobs.

It would be helpful if I could configure Environment Variables in the Server Name and then the plugin could actually search for the server in the list of configured servers.

Add Comment

[goel.shashank91@gmail.com (JIRA)]

Shashank Goel updated an issue

Jenkins / JENKINS-58741 Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin

Change By: Shashank Goel Priority: Minor Critical

Add Comment

[goel.shashank91@gmail.com (JIRA)]

Shashank Goel updated an issue

Jenkins / JENKINS-58741 Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin

Change By: Shashank Goel Priority: Critical Minor

Add Comment

[j.spriggs@raylase.de (JIRA)]

Jim Spriggs commented on JENKINS-58741

Re: Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin Vote++ This would be a big help for me when deploying to multiple embedded systems (I'm testing with hardware in the loop). Currently I'm using (and maintaining) one traditional freestyle job for each system . Parameterized Publishing as it stands is of no real benefit since I would still have to add a complete server-block for each system.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)