-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
CloudBees (based on Jenkins LTS 2.204.1-cb-2)
TFS plugin version 5.157.1
Our DevOps team recently ran maintenance on our jenkins master and I am no longer able to run our pipelines. These connections were working consistently prior to the maintenance and now it consistently not working. Please advise, this is stopping all jenkins pipelines from running. Below is the console output:
Lightweight checkout support not available, falling back to full checkout.
Checking out hudson.plugins.tfs.TeamFoundationServerScm into /var/lib/jenkins/workspace/FXL/7.5 DevTest@script to read Jenkins_DevTest.groovy
Querying for remote changeset at '$/TwoFour Version 7.5' as of 'D2020-03-10T16:30:44Z'...
ERROR: Checkout failed
com.microsoft.tfs.core.ws.runtime.exceptions.EndpointNotFoundException: The SOAP endpoint
http://<server>:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx
could not be contacted. HTTP status: 503
at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineHeadersForErrorMessage(SOAPService.java:1101)
at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:660)
at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444)
at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.queryHistory(_RepositorySoap12Service.java:1503)
at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.queryHistory(WebServiceLayer.java:1573)
Caused: com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint
http:// <server> :8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx
could not be contacted. HTTP status: 503
at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92)
at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:43)
at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.queryHistory(WebServiceLayer.java:1589)
at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayerLocalWorkspaces.queryHistory(WebServiceLayerLocalWorkspaces.java:1254)
at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.queryHistory(VersionControlClient.java:4264)
at hudson.plugins.tfs.model.MockableVersionControlClient.queryHistory(MockableVersionControlClient.java:255)
at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:66)
at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:34)
at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
at hudson.plugins.tfs.model.Server.execute(Server.java:233)
Caused: java.lang.RuntimeException
at hudson.plugins.tfs.model.Server.execute(Server.java:237)
at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:280)
at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:276)
at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:292)
at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:394)
at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:343)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:155)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:69)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:299)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:427)
ERROR: Maximum checkout retry attempts reached, aborting
Finished: FAILURE
[JENKINS-61420] The SOAP endpoint could not be contacted. HTTP status: 503
Description |
Original:
Our DevOps team recently ran maintenance on our jenkins master and I am no longer able to run our pipelines. These connections were working consistently prior to the maintenance and now it consistently not working. Please advise, this is stopping all jenkins pipelines from running. Below is the console output: Lightweight checkout support not available, falling back to full checkout. Checking out hudson.plugins.tfs.TeamFoundationServerScm into /var/lib/jenkins/workspace/FXL/7.5 DevTest@script to read Jenkins_DevTest.groovy Querying for remote changeset at '$/TwoFour Version 7.5' as of 'D2020-03-10T16:30:44Z'... ERROR: Checkout failed com.microsoft.tfs.core.ws.runtime.exceptions.EndpointNotFoundException: The SOAP endpoint [http://<server>:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx|http://teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx] could not be contacted. HTTP status: 503 at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineHeadersForErrorMessage(SOAPService.java:1101) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:660) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.queryHistory(_RepositorySoap12Service.java:1503) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.queryHistory(WebServiceLayer.java:1573) Caused: com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint [http://teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx] could not be contacted. HTTP status: 503 at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:43) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.queryHistory(WebServiceLayer.java:1589) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayerLocalWorkspaces.queryHistory(WebServiceLayerLocalWorkspaces.java:1254) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.queryHistory(VersionControlClient.java:4264) at hudson.plugins.tfs.model.MockableVersionControlClient.queryHistory(MockableVersionControlClient.java:255) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:66) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:34) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:233) Caused: java.lang.RuntimeException at hudson.plugins.tfs.model.Server.execute(Server.java:237) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:280) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:276) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:292) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:394) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:343) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:155) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:69) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:299) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427) ERROR: Maximum checkout retry attempts reached, aborting Finished: FAILURE |
New:
Our DevOps team recently ran maintenance on our jenkins master and I am no longer able to run our pipelines. These connections were working consistently prior to the maintenance and now it consistently not working. Please advise, this is stopping all jenkins pipelines from running. Below is the console output: Lightweight checkout support not available, falling back to full checkout. Checking out hudson.plugins.tfs.TeamFoundationServerScm into /var/lib/jenkins/workspace/FXL/7.5 DevTest@script to read Jenkins_DevTest.groovy Querying for remote changeset at '$/TwoFour Version 7.5' as of 'D2020-03-10T16:30:44Z'... ERROR: Checkout failed com.microsoft.tfs.core.ws.runtime.exceptions.EndpointNotFoundException: The SOAP endpoint [http://<server>:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx|http://teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx] could not be contacted. HTTP status: 503 at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineHeadersForErrorMessage(SOAPService.java:1101) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:660) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.queryHistory(_RepositorySoap12Service.java:1503) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.queryHistory(WebServiceLayer.java:1573) Caused: com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint [http://|http://teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx] [<server>|http://teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx] [:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx|http://teamfoundation:8080/tfs/TwoFour/VersionControl/v1.0/repository.asmx] could not be contacted. HTTP status: 503 at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:43) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.queryHistory(WebServiceLayer.java:1589) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayerLocalWorkspaces.queryHistory(WebServiceLayerLocalWorkspaces.java:1254) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.queryHistory(VersionControlClient.java:4264) at hudson.plugins.tfs.model.MockableVersionControlClient.queryHistory(MockableVersionControlClient.java:255) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:66) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:34) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:233) Caused: java.lang.RuntimeException at hudson.plugins.tfs.model.Server.execute(Server.java:237) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:280) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:276) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:292) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:394) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:343) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:155) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:69) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:299) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427) ERROR: Maximum checkout retry attempts reached, aborting Finished: FAILURE |
Environment |
New:
CloudBees (based on Jenkins LTS 2.204.1-cb-2) TFS plugin version 5.157.1 |
Assignee | Original: redsolo [ redsolo ] |
Assignee | New: chulkwon [ chulkwon_shin ] |
Assignee | Original: chulkwon [ chulkwon_shin ] | New: redsolo [ redsolo ] |
Comment | [ SPAM ] |
Comment |
[ I’m sorry to hear that you are having trouble with running your Jenkins pipelines after the maintenance. It seems that the error you are getting is related to the Team Foundation Server (TFS) plugin for Jenkins, which allows you to integrate Jenkins with TFS or Azure DevOps. The error indicates that the Jenkins server cannot connect to the TFS repository using the SOAP endpoint.
There are a few possible causes and solutions for this error, such as: The TFS server is down or unreachable. You can check the status of the TFS server by accessing it from a browser or using a tool like ping or curl. If the server is not responding, you may need to contact your TFS administrator or DevOps team to fix the issue. The Jenkins server is behind a proxy or firewall that blocks the connection to the TFS server. You can check the proxy settings of your Jenkins server by going to Manage Jenkins > Manage Plugins > Advanced. You may need to add the TFS server URL to the list of non-proxy hosts or configure the proxy credentials. The TFS plugin for Jenkins is outdated or incompatible with the TFS server version. You can check the version of the TFS plugin by going to Manage Jenkins > Manage Plugins > Installed. You may need to update the plugin to the latest version or install a compatible version. The TFS credentials for Jenkins are incorrect or expired. You can check the credentials by going to Manage Jenkins > Credentials. You may need to update or create new credentials for the TFS server. I hope this helps you to troubleshoot and resolve the error. {color:#c1c7d0}[https://www.doglikesbest.com/]{color} ] |
Comment |
[ I never face this failure. So lucky
----------------- [https://smashkartsio.com|https://smashkartsio.com/] ] |
redsolo is no longer maintaining plugin; unassigned issues