Git-Jenkins using remote server for development.

2014-12-08 Thread Ritesh Patel
Hello All,

We have java GWT project, which was migrated from cvs to git in last week.
We are using shared server to maintain code.
The process is like, developers have eclipse in their local machine, but 
code is in central remote server.
But, now we are facing issue with git, as it is taking long time to clone, 
commit and push branch in git with eclipse.

Can anyone please suggest solution for this?

Thanks,
Ritesh Patel.

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/cf6e0cdf-c975-495a-b06b-c27927867d87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Project structure with git and Jenkins

2014-09-30 Thread Ritesh Patel
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 
implement the code, and to compile they use jenkins, which is on central 
server.

Thanks,
Ritesh Patel.

On Monday, September 29, 2014 10:18:47 PM UTC+7, Mark Waite wrote:

 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, you've now 
 inserted a slowdown (network access) into all the operations performed by 
 developers, all day long.  That seems like a serious penalty for the most 
 active portion of a developer's working day.

 Git users have the notion of a feature branch which allows a developer 
 to submit something to be evaluated by Jenkins, without making that change 
 available on the authoritative branch.  You could investigate a feature 
 branch based workflow, and use Jenkins to automate the merge from feature 
 branches to the authoritative branch.

 Alternately, you could consider using Gerrit, which provides a code read 
 facility and related workflow as a layer over a git repository.

 Mark Waite

 On Sun, Sep 28, 2014 at 10:34 PM, Ritesh Patel rpa...@shipco.com 
 javascript: wrote:

 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 drive, once they save, they can ask Jenkins to 
 compile and deploy automatically.
 But, this should happen without commit to main branch.
 How we can achieve this?

 Thanks in advance.

 Ritesh Patel.

 -- 
 You received this message because you are subscribed to the Google Groups 
 Jenkins Users group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to jenkinsci-use...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




 -- 
 Thanks!
 Mark Waite
  

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.