Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-58741

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

    XMLWordPrintable

Details

    Description

      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 and it is hard to configure the target server every time. 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.

      Attachments

        Activity

          19shank91 Shashank Goel created issue -
          19shank91 Shashank Goel made changes -
          Field Original Value New Value
          Issue Type Bug [ 1 ] Improvement [ 4 ]
          19shank91 Shashank Goel made changes -
          Description 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.
          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 and it is hard to configure the target server every time. 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.
          19shank91 Shashank Goel made changes -
          Priority Minor [ 4 ] Critical [ 2 ]
          19shank91 Shashank Goel made changes -
          Priority Critical [ 2 ] Minor [ 4 ]
          jimsp Jim Spriggs added a comment -

          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.

           

           

          jimsp Jim Spriggs added a comment - 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.    

          For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues

          Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/87
          And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-58741%22

          (Note: this is an automated bulk comment)

          gmcdonald Gavin McDonald added a comment - For your information, all publish-over-ssh component type JENKINS issues related to the Publish Over SSH plugin have been transferred to Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues Here is the direct link to this issue in Github: https://github.com/jenkinsci/publish-over-ssh-plugin/issues/87 And here is the link to a search for related issues: https://github.com/jenkinsci/publish-over-ssh-plugin/issues?q=%22JENKINS-58741%22 (Note: this is an automated bulk comment)

          Closing ticket, please use the corresponding Github Issue as linked above.

          gmcdonald Gavin McDonald added a comment - Closing ticket, please use the corresponding Github Issue as linked above.
          gmcdonald Gavin McDonald made changes -
          Resolution Incomplete [ 4 ]
          Status Open [ 1 ] Closed [ 6 ]

          People

            Unassigned Unassigned
            19shank91 Shashank Goel
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: