[JIRA] [tfs-plugin] (JENKINS-33545) The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0.

[davy.courvoisier@gmail.com (JIRA)]

Davy Courvoisier created an issue

Jenkins / JENKINS-33545 The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0. Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 15/Mar/16 11:30 AM Environment: TFS Plugin: V 4.1.0 Jenkins: 1.642.1 and 1.609.3 Priority: Blocker Reporter: Davy Courvoisier Upgrading TFS Plugin from version 4.0.0 to 4.1.0 make system unusable. Tried creating a new job from scratch and same error occurs. Workaround is to revert to V4.0.0. This is reproduced on 2 different instances. The following error occurs when the TFS plugin tries to connect to TFS(poll, checkout): FATAL: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302 com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302 at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:105) at com.microsoft.tfs.core.exceptions.mappers.RegistrationExceptionMapper.map(RegistrationExceptionMapper.java:23) at com.microsoft.tfs.core.clients.registration.RegistrationData.newFromServer(RegistrationData.java:70) at com.microsoft.tfs.core.clients.registration.RegistrationClient.getRegistrationData(RegistrationClient.java:645) at com.microsoft.tfs.core.clients.registration.RegistrationClient.getRegistrationEntry(RegistrationClient.java:188) at com.microsoft.tfs.core.clients.registration.RegistrationClient.getRegistrationEntry(RegistrationClient.java:167) at com.microsoft.tfs.core.clients.webservices.IdentityManagementService.<init>(IdentityManagementService.java:65) at hudson.plugins.tfs.model.Server.createIdentityManagementService(Server.java:213) at hudson.plugins.tfs.model.Project.getOrCreateUserLookup(Project.java:112) at hudson.plugins.tfs.model.Project.getVCCHistory(Project.java:82) at hudson.plugins.tfs.model.Project.getLatestUncloakedChangeset(Project.java:179) at hudson.plugins.tfs.TeamFoundationServerScm.compareRemoteRevisionWith(TeamFoundationServerScm.java:555) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1450) at hudson.model.AbstractProject.poll(AbstractProject.java:1353) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:510) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:539) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: com.microsoft.tfs.core.ws.runtime.exceptions.EndpointNotFoundException: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302 at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineHeadersForFederatedAuthURL(SOAPService.java:1198) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:716) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:475) at ms.tfs.services.registration._03._RegistrationSoap12Service.getRegistrationEntries(_RegistrationSoap12Service.java:105) at com.microsoft.tfs.core.clients.registration.RegistrationData.newFromServer(RegistrationData.java:65) ... 20 more Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[davy.courvoisier@gmail.com (JIRA)]

Davy Courvoisier updated an issue

Jenkins / JENKINS-33545 The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0.

Change By: Davy Courvoisier

Upgrading TFS Plugin from version 4.0.0 to 4.1.0 make system unusable.

Tried creating a new job from scratch and same error occurs. Workaround is to revert to V4.0.0. This is reproduced on 2 different  linux jenkins  instances. V 4.1.0 does not have the issue on a Windows installation.

[davy.courvoisier@gmail.com (JIRA)]

Davy Courvoisier updated an issue

Jenkins / JENKINS-33545 The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0. Change By: Davy Courvoisier

Upgrading TFS Plugin from version 4.0.0 to 4.1.0 make system unusable.

Tried creating a new job from scratch and same error occurs. Workaround is to revert to V4.0.0. This is reproduced on 2 different linux jenkins instances , with Windows clients . V 4.1.0 does not have the issue on a  newly installed  Windows installation  jenkins 1 . 642.2.

[Matthew.D.Sweeney@wellsfargo.com (JIRA)]

Matthew Sweeney commented on JENKINS-33545

Re: The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0. Same problem directly after upgrading to 4.1, downgrading to 4.0 is the current solution.

Add Comment

[mattias.vannergard@gmail.com (JIRA)]

Mattias Vannergård commented on JENKINS-33545

Re: The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0.

I see the same problem installing 5.3.1 on a fresh Jenkins 2.32.1 LTS. I manually installed 4.0.0, but still the same errors.

Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[Matthew.D.Sweeney@wellsfargo.com (JIRA)]

Matthew Sweeney commented on JENKINS-33545

Re: The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0.

Hi Mattias, I believe we resolved this issue by making sure the system proxy settings were correct - in our case after upgrading to the latest version of the plugin it was using the default Java system proxy whereas in the past it was not. If I remember correctly you need to modify this in the config file or via the service startup options.

Add Comment

[mattias.vannergard@gmail.com (JIRA)]

Mattias Vannergård commented on JENKINS-33545

Re: The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0.

It is probably the same here, because the server was moved, and connected to us via a LAN2LAN-connection, which will need a proxy setup we didn't use before. I think this issue should be Closed, and marked as Not A Bug, because it is not a problem with Jenkins.

Add Comment