|
Has anyone used TeamCity + Vagrant? I basically want TC to 'vagrant up' then run its build agent inside the VM. I could use a different build agent for each build but that immediately puts me into their enterprise pricing tier.
|
#
¿
Oct 20, 2015 21:29
|
|
|
|
| # ¿ Apr 30, 2024 05:41 |
|
|
I'm looking to separate my build server from my deployment. Currently TeamCity builds a feature branch then runs a shell script to start an environment locally (passing in the branch name). Instead I want to push the artifact to a QA server and deal with it there. A web interface to manage those environments would be nice too. What should I be looking for (besides a proper devops engineer)? This is for the development team, not hosting customers. The build artifact is a set of docker images.
|
|
#
¿
Feb 9, 2016 21:53
|
|
|
Mr. Crow posted:Anyone have experience setting up teamcity in a docker container behind a reverse proxy which is also in a container (nginx)? I run teamcity in a docker container. There's nothing to it. Are you having a specific problem? The latest teamcity can store its build configuration in code and version control it. They even have official docker images now. https://www.jetbrains.com/teamcity/whatsnew/
|
|
#
¿
Oct 25, 2016 23:43
|
|
|
Mr. Crow posted:Related but tangential question, can someone explain to me the benefit of a docker data container vs just mounting a volume directly? It seems like an unnecessary layer of indirection, you're replacing being wired to the volume with being wired to the container. I'm missing something. You can share volumes between multiple containers in my experience so...? You're right, there's no reason to use data containers now that named volumes are a thing.
|
|
#
¿
Oct 31, 2016 01:06
|
|
|
Dreadrush posted:Hi I'm very new to the whole Docker thing and am trying to learn more about it. If you're not deploying node, it shouldn't be included in your images. Generate your static files outside docker and build them into the image. code:
|
|
#
¿
Nov 20, 2016 07:47
|
|
|
I've used puppet for a few things and it's always been a disaster. I'll find a package which does exactly what I want, great! Hours later I'm debugging compatibility issues in an package 3 dependencies deep. Oh, there's a PR to fix it. Opened a year ago.
|
|
#
¿
Dec 12, 2017 05:45
|
|
|
|
| # ¿ Apr 30, 2024 05:41 |
|
|
This thing will reverse proxy the docker port https://github.com/jwilder/nginx-proxy Then you can docker run -p 9999 -e VIRTUAL_HOST=${BRANCH_NAME}.yourdomain.com your-image It's a pain in the rear end to debug though when something goes wrong
|
|
#
¿
Feb 16, 2018 18:09
|
|