• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • deploy-plugin
    • None

      We need to deploy 3 wars to 2 servers. The plugin only allows one file to one server. Please extend this.

          [JENKINS-14949] Deploy several wars/ears to several servers

          Related discussion

          [RFC] publishers as a drop-down menu
          https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/UQLvxQclyb4

          once you add a publisher of a certain kind, it gets grayed out and prevents you from adding 2nd (and if you actually click the grayed out item, you jump to the corresponding part of the page.) (this restriction of one instance per one publisher might be something worth removing in the future?)

          OHTAKE Tomohiro added a comment - Related discussion [RFC] publishers as a drop-down menu https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/UQLvxQclyb4 once you add a publisher of a certain kind, it gets grayed out and prevents you from adding 2nd (and if you actually click the grayed out item, you jump to the corresponding part of the page.) (this restriction of one instance per one publisher might be something worth removing in the future?)

          jason james added a comment -

          I would also like to see this feature. Currently it's only useful for a select few of our builds due to the 1 server/container limitation.

          jason james added a comment - I would also like to see this feature. Currently it's only useful for a select few of our builds due to the 1 server/container limitation.

          It would be awesome to see the functionality that the Bamboo Tomcat Deploy plug in has built into this plug in for Jenkins. Though, it's essentially giving the ability to add multiple "deploy ear/war to container" items in one job.

          Jared Griffith added a comment - It would be awesome to see the functionality that the Bamboo Tomcat Deploy plug in has built into this plug in for Jenkins. Though, it's essentially giving the ability to add multiple "deploy ear/war to container" items in one job.

          Jørgen Jervidalo added a comment - - edited

          It would be great if the "<container> URL" field accepted variables. I tried to create a multi-configuration project that would have solved my needs, but if I insert a variable in the URL field, the job fails.
          (Edit: seems like the issues JENKINS-12825 and JENKINS-5790 covers this)

          Jørgen Jervidalo added a comment - - edited It would be great if the "<container> URL" field accepted variables. I tried to create a multi-configuration project that would have solved my needs, but if I insert a variable in the URL field, the job fails. (Edit: seems like the issues JENKINS-12825 and JENKINS-5790 covers this)

          Bob Kubista added a comment -

          Can't you use a separate multi-configurable build job to do this? You could have 1 axis as the wars to be deployed and 1 axis as the servers to be deployed to?!

          Bob Kubista added a comment - Can't you use a separate multi-configurable build job to do this? You could have 1 axis as the wars to be deployed and 1 axis as the servers to be deployed to?!

          bobkubista that is quite the workaround but I use different passwords for each container and I'm not comfortable putting these directly and readable into the job. Also the tomcat url field does not accept parameters.

          Is there a solution in the meantime, or any plans on making a deploy to container step available in Jenkinsfiles?

          Brent Courtois added a comment - bobkubista that is quite the workaround but I use different passwords for each container and I'm not comfortable putting these directly and readable into the job. Also the tomcat url field does not accept parameters. Is there a solution in the meantime, or any plans on making a deploy to container step available in Jenkinsfiles?

          Robin Jansohn added a comment -

          Is this still an issue with the latest version 1.13? As far as I can see most of the fields now support variables.

          Robin Jansohn added a comment - Is this still an issue with the latest version 1.13? As far as I can see most of the fields now support variables.

            Unassigned Unassigned
            cforce cforce
            Votes:
            7 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: