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

Allow authentication in swarm plugin

    XMLWordPrintable

Details

    Description

      The swarm plugin doesn't support authentication yet. This means that it won't work with a locked-down Hudson. It would be nice if the appropriate options could be added to the swarm jar file.

      Attachments

        Activity

          closing

          mindjiver Peter Jönsson added a comment - closing
          brunken brunken added a comment -

          Added -username and -password parameters
          Changed -master url , now it requires the complete url path, like http://server:8080/hudson to solve some url problems.

          brunken brunken added a comment - Added -username and -password parameters Changed -master url , now it requires the complete url path, like http://server:8080/hudson to solve some url problems.

          Code changed in hudson
          User: : brunken
          Path:
          trunk/hudson/plugins/swarm/client/pom.xml
          http://jenkins-ci.org/commit/35601
          Log:
          Added commons-httpclient for JIRA ISSUE #JENKINS-5504

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : brunken Path: trunk/hudson/plugins/swarm/client/pom.xml http://jenkins-ci.org/commit/35601 Log: Added commons-httpclient for JIRA ISSUE # JENKINS-5504

          Code changed in hudson
          User: : brunken
          Path:
          trunk/hudson/plugins/swarm/client/src/main/java/hudson/plugins/swarm/Client.java
          http://jenkins-ci.org/commit/35600
          Log:
          JIRA ISSUE #JENKINS-5504
          Added -username and -password, changed -master parameter to accept the complete hudson url.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : brunken Path: trunk/hudson/plugins/swarm/client/src/main/java/hudson/plugins/swarm/Client.java http://jenkins-ci.org/commit/35600 Log: JIRA ISSUE # JENKINS-5504 Added -username and -password, changed -master parameter to accept the complete hudson url.
          brunken brunken added a comment - - edited

          I solved this issue by adding some additional command line parameters to the plugin and i also changed the post method settings, now it authenticate on hudson. It worked fine on our Corporate Hudson, wich is locked tight with LDAP.
          Also, I changed the -master method, instead just a server name, I changed to work with the complete Hudson Path with port, like http://server:8080/hudson because it was not working on Tomcat or Winston.

          brunken brunken added a comment - - edited I solved this issue by adding some additional command line parameters to the plugin and i also changed the post method settings, now it authenticate on hudson. It worked fine on our Corporate Hudson, wich is locked tight with LDAP. Also, I changed the -master method, instead just a server name, I changed to work with the complete Hudson Path with port, like http://server:8080/hudson because it was not working on Tomcat or Winston.

          People

            mindjiver Peter Jönsson
            larsko larsko
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: