It does sound like a use case for my employer's (CloudBees) proprietary
validated merge plugin... I'm sure you can figure out how to find out more
about it without me venturing any further into "pimp our own wares"
territory
On 1 October 2014 03:31, Mark Waite wrote:
> Given that condition (deve
Given that condition (developer computers are too slow for reasonable
compilation), I don't have any suggestion that I would consider very
helpful.
You could try having them commit to git on their local computer using
feature branches, then push the feature branch to a central repository for
compi
Thank you Mark.
Actually, we are facing compilation time issue on local servers as we are
using GWT.
To solve it, we set a central server with very good configuration.
So, developers can use that server for compilation.
Now, the idea is that developers have code on some shared drive, they
imple
Can you explain further what you hope to gain by using a shared drive for
development?
Git works best with local drives. It is a fast version control system in
large measure because the vast majority of its operations work on the local
file system. If you make git operate on a shared file system
Hi All,
Right now, in our project, developers develop code on shared drive, compile
on common server, but deploy on local PC.
But, we want continuous integration in future with git and Jenkins.
Our main requirement is that developers should not have anything on their
PC, they develop on shared
