<p>Since on-premise TFS and the newly renamed Azure DevOps Server 2019 still have the concept of collections, which is the highest level of separation of data you can have (separate physical databases), you'd need to treat a code repo in Collection 1 as an external repository rather than try to discover it as a known internal repository.</p>

<p>You can do this in the Build pipeline of a build in Collection 2 by selecting External Git (if your repo is Git, TFVC is not supported), then clicking <code>Add Connection</code> and entering the Git repository URL and login credentials like in the screenshot below.  Once connected, your pipeline, if it produces artifacts, will store them in Collection 2, which can be used for a Release pipeline.</p>

<p><a href="https://i.sstatic.net/BO5c3.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/BO5c3.png" alt="enter image description here"></a></p>

CC BY-SA 4.0
2019-04-10T01:21:44.870Z
2019-04-10T01:21:44.870Z
Sumo
<p>In Azure DevOps there is no Collection - there is a project and there are organizations which hold zero or more projects. There is also a distinction between the code repositories and the builds and between the builds and the release mechanism. </p>

<p>Within a build pipeline it is entirely possible to reference a different projects repository to pull into the build and that repository could be in GitHub, Gitlab, or another VSTS organization, and within a release it is entirely possible to include build artifacts from multiple build pipelines.</p>

<p>TFS on-premises depends highly on how up-to-date it has been kept. The most recent versions are feature equal or close to it with Azure DevOps and the above should be true. Milage may vary in older versions. </p>

<p>It isn't clear here in your question though what you are trying to achieve or what you've tried so far.</p>

CC BY-SA 4.0
2019-01-12T23:47:45.893Z
2019-01-12T23:47:45.893Z
Absurdly
<p>I have code repo held in Collection 1 and, using this code repo, I am trying to create a Build artifact and Release definition in a different Collection 2.</p>

<p>Is this even possible? </p>

<continuous-integration><azure-devops><cicd><azure-pipelines><tfs>
In Azure Devops and TFS, is it possible to create a build artifact and release definition in a different collection than the original code repository?
nuprap
# In Azure Devops and TFS, is it possible to create a build artifact and release definition in a different collection than the original code repository?

(Asked by: username_0 on 2019-01-10)

I have code repo held in Collection 1 and, using this code repo, I am trying to create a Build artifact and Release definition in a different Collection 2.

Is this even possible?

**Tags:** continuous-integration, azure-devops, cicd, azure-pipelines, tfs


---

## 2 answers

### Answer by username_1 on 2019-04-10. Score: 1 | Accepted answer

Since on-premise TFS and the newly renamed Azure DevOps Server 2019 still have the concept of collections, which is the highest level of separation of data you can have (separate physical databases), you'd need to treat a code repo in Collection 1 as an external repository rather than try to discover it as a known internal repository.

You can do this in the Build pipeline of a build in Collection 2 by selecting External Git (if your repo is Git, TFVC is not supported), then clicking `Add Connection` and entering the Git repository URL and login credentials like in the screenshot below. Once connected, your pipeline, if it produces artifacts, will store them in Collection 2, which can be used for a Release pipeline.

[![enter image description here](https://i.sstatic.net/BO5c3.png)](https://i.sstatic.net/BO5c3.png)


---

### Answer by username_2 on 2019-01-12. Score: 0

In Azure DevOps there is no Collection - there is a project and there are organizations which hold zero or more projects. There is also a distinction between the code repositories and the builds and between the builds and the release mechanism.

Within a build pipeline it is entirely possible to reference a different projects repository to pull into the build and that repository could be in GitHub, Gitlab, or another VSTS organization, and within a release it is entirely possible to include build artifacts from multiple build pipelines.

TFS on-premises depends highly on how up-to-date it has been kept. The most recent versions are feature equal or close to it with Azure DevOps and the above should be true. Milage may vary in older versions.

It isn't clear here in your question though what you are trying to achieve or what you've tried so far.


---

