azure-pipelines-agent: Does not work with 2015 QU1 (works with RTM and QU2)
Hello! I’d like thank you for what you are doing.
I installed CMake, registered the agent created build definition, and queued a build
It seams the agent did not tried to get sources and gave the log on the web: What is missing? Could you please give me a hint?
******************************************************************************
Starting: Build
******************************************************************************
API resource location 60aac929-f0cd-4bc8-9ce4-6b30e8f1b1bd is not registered on https://tfs.company.com/tfs/COLLECTION/.
******************************************************************************
Finishing: Build
******************************************************************************
On the VM log looks like that:
2016-05-06 17:02:17Z: Listening for Jobs
2016-05-06 17:02:39Z: Running job: Build
2016-05-06 17:02:46Z: Job Build completed with result: Failed
Worker_* log looks like that:
[2016-05-06 17:02:44Z INFO TaskManager] Ensuring task exists: ID '7d831c3c-3c68-459a-a5c9-bde6e659596c', version '1.0.9', name 'CMake', directory '/home/buildvm/agent/_work/_tasks/CMake_7d831c3c-3c68-459a-a5c9-bde6e659596c/1.0.9'.
[2016-05-06 17:02:44Z INFO TaskManager] Getting task.
[2016-05-06 17:02:44Z ERR JobRunner] Caught exception from TaskManager: Microsoft.VisualStudio.Services.WebApi.VssResourceNotFoundException: API resource location 60aac929-f0cd-4bc8-9ce4-6b30e8f1b1bd is not registered on https://tfs.company.com/tfs/COLLECTION/.
at Microsoft.VisualStudio.Services.WebApi.VssHttpClientBase.
..
STACK TRACE
..
[2016-05-06 17:02:44Z INFO JobRunner] Shutting down the job server queue.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 48 (12 by maintainers)
Re-released the 2.102.0 binaries with the fixes. Please redownload
https://github.com/Microsoft/vsts-agent/releases/tag/v2.102.0
This one will in a preview version soon ( not current preview). But it will only be against next version of TFS onprem since it needed server side changes as well.
No. It looks like you’re going against on-prem server? That’s not supported yet in the preview. There’s on going work to make that possible.
We should try and head this off. Even if we have to make an extra call during config to ensure it’s at the right level.url.
@rusergeev did you register your agent against an collection url instead of account url? make sure the server url you use for configuration does not have /defaultcollection at the end.