<p>Travis CI doesn't offer running your own workers, you use their infrastructure unless you mean the on-prem Travis Enterprise. You might be thinking of GitLab CI?</p>

CC BY-SA 3.0
2017-06-21T06:32:14.807Z
what do you mean with GitLab CI? 
Regarding TravisCI, I see all that repos - isn't it completely open source, allowing for deploying own workers as well?
https://github.com/travis-ci
Ta Mu
CC BY-SA 3.0
2017-06-21T12:35:21.717Z
You can deploy your own full copy of Travis-CI but it isn't easy, and you can't use your own workers with the normal travis-ci.org or travis-ci.com.
coderanger
CC BY-SA 3.0
2017-06-21T05:35:31.587Z
2017-06-21T05:35:31.587Z
coderanger
<p>Travis CI is build as a cloud solution focusing upon github repositories.
It is possible to setup a Travis CI in-house as a self-hosted solution, however the open-source project is not build with this in mind and therefore it is likely that you will hit limitations.
This is why Travis CI has an Enterprise solution: <a href="https://enterprise.travis-ci.com/" rel="nofollow noreferrer">https://enterprise.travis-ci.com/</a>.
I think you would be better off looking at similar CI products or buying the enterprise edition of Travis which are focused upon you owning both the master server and the build agents. 
However, it depends on your specific need.</p>

CC BY-SA 3.0
2017-09-15T11:21:51.670Z
2017-09-15T11:21:51.670Z
Steiniche
<p>Is this correct that if I decide to setup an own TravisCI agent, I will be enabled to be independent of the existing distributed Travis computation network?</p>

<continuous-integration><travis-ci>
If I set up a Travis CI agent, will it be independent of Travis's existing infrastructure?
Ta Mu
# If I set up a Travis CI agent, will it be independent of Travis's existing infrastructure?

(Asked by: username_0 on 2017-06-20)

Is this correct that if I decide to setup an own TravisCI agent, I will be enabled to be independent of the existing distributed Travis computation network?

**Tags:** continuous-integration, travis-ci


---

## 2 answers

### Answer by username_1 on 2017-06-21. Score: 1

Travis CI doesn't offer running your own workers, you use their infrastructure unless you mean the on-prem Travis Enterprise. You might be thinking of GitLab CI?

> **Comments:**
> **username_0**: what do you mean with GitLab CI?  Regarding TravisCI, I see all that repos - isn't it completely open source, allowing for deploying own workers as well? https://github.com/travis-ci  
> **username_1**: You can deploy your own full copy of Travis-CI but it isn't easy, and you can't use your own workers with the normal travis-ci.org or travis-ci.com.  

---

### Answer by username_2 on 2017-09-15. Score: 0

Travis CI is build as a cloud solution focusing upon github repositories.
It is possible to setup a Travis CI in-house as a self-hosted solution, however the open-source project is not build with this in mind and therefore it is likely that you will hit limitations.
This is why Travis CI has an Enterprise solution: <https://enterprise.travis-ci.com/>.
I think you would be better off looking at similar CI products or buying the enterprise edition of Travis which are focused upon you owning both the master server and the build agents.
However, it depends on your specific need.


---

