Connect many Jenkins servers with different branches of the same github repo

I want to set up a staging server where each developer will have his own docker container running the app and Jenkins .

I want each one to be able to connect his github branch with his jenkins server with the github plugin for jenkins and create the automated build pipeline. But every branch will be in the same corporate private repository.

  • Django in docker. Can't see logs
  • Docker tutum/wordpress container issues with apache2 and supervisor
  • Is it possible to allow the containers running on the same image to share their filesystem?
  • Spring boot app runs fine standalone, errs in docker
  • Open file inside docker container has been shut down
  • SkyDNS does not work with Kubernetes 1.1.2
  • Push code from IDE -> Code goes on Github -> Github pushes to jenkins(in container) -> jenkins builds new code(in container) -> tester connects to container and browses the app branch

    I have made 2 containers each with a jenkins server. One is connected with master branch and the other with branch1 of the same repo. But each repo allows only one implementation of the github plugin for jenkins.
    Setting one new repo for every branch seems kind of silly and wasteful.

    Best case scenario would be to connect many jenkins servers with the same repo but on different ports by specifying different branches.

    Is something like this possible?

  • Docker fig multiple server deployment
  • Docker mount from host to remote
  • What is the relationship between a docker image ID and the IDs in the manifests?
  • docker set iptables options in docker-compose.yml
  • Installing packages into ubuntu14.04 docker container
  • How do I use the git commit id as a docker image tag in maven?
  • One Solution collect form web for “Connect many Jenkins servers with different branches of the same github repo”

    If those docker container can mount the same data container with the git repo in it, that means they can checkout different branches per repo.

    For that, they need a recent git (2.5+) and to use the new git worktree add command.
    Then those containers would work in a worktree set to a different branch per container, but all pointing to the same repo.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.