Continuous Integration using GIT / BitBucket on a GIT controlled Intranet

I had just implemented GIT Version Control for a Team of three people. We are managing to pull/push/fetch etc to our bitBucket repository. My only concern is how I should push live after we make an update to the repository.

On another server, I wrote a shell script to clone the repo into a directory so I would be able to test, but on the live server I cannot do the same since on some occasions I just have to push one file only.

  • Possible to know if member has cloned source code from git repository?
  • Jenkins - Get code from BitBucket with SSH
  • BitBucket Git Error: did not send all necessary objects
  • Configuration of 2 Bitbucket accounts on one laptop: cannot clone code
  • Smartgit Integrate Develop not available - Bitbucket # commits behind | # commits ahead
  • Git pull on remote host with Fabric
  • Please note that our live server is inside a network and not accessible over the internet (thus I cannot use BitBucket’s push service)

    Really looking forward for your suggestions as I’m currently really stumbled :S

    Thanks in advanced!

  • branch diverged after rebase from another upstream
  • Git renaming file. History is available on cmd-line, but not in github interface?
  • .gitignore /folder vs folder/
  • gerrit admin does not have “Access Database” capability
  • How to resolve Git error: “fatal: BUG: get_tempfile_fd() called for inactive object”
  • Gitignore - Ignore only images & ignore everything except .. in single command
  • One Solution collect form web for “Continuous Integration using GIT / BitBucket on a GIT controlled Intranet”

    The only advise I can give is to make sure that the local repository (which concentrates changes from the developers) is up to date and in shape before pushing.

    Locally you can define your workflow. Perhaps the master repo, into which only official commits are taken, branches for each developer’s work once it passes local tests, and each one does as they please on their machines. Or something fancier. There are suggestions on workflows, ranging from almost centralized to completely distributed, check them out. If you adopt one way of working, git won’t stand in your way if you decide later to change it.

    Git Baby is a git and github fan, let's start git clone.