Thanks, Owen! I fixed the error.
I am continuing with the integration, and will let you know if I encounter any issues. Cheers. On Wednesday, April 29, 2015 at 7:32:23 PM UTC-4, Owen Windsor wrote: > > Hi - Check out this jenkins module in the first instance; > > https://wiki.jenkins-ci.org/display/JENKINS/Gitlab+Hook+Plugin > > We use this in conjunction with a web hook in each project to spawn builds > on our jenkins host for each commit to each branch. > > Our Gitlab and Jenkins boxes are very separate, so there is no need to > co-locate the applications. > > Regarding your first issue with Jenkins failing to clone the repository, > make sure that you have some credentials configured in the Jenkins > credentials config - we use a deployment key that is applied the the > appropriate project in Gitlab that we load the key within jenkins and apply > that to each of the build profiles. This then lets jenkins clone the > repository for build. > > There are other options for the authentication, but this one is the most > flexible if you are using slaves for the build. > > Hope that helps some and happy to answer more questions if you have them. > > Cheers, > Owen > > On Wed, Apr 29, 2015 at 12:24 AM, OG <ogfu...@gmail.com <javascript:>> > wrote: > >> Nope.....not yet......I wish !!! *I STILL NEED HELP >> BADLY !!!* >> >> I ran the git commands (git init, etc) for Creating The Repository in the >> GitLab VM, which is in a separate VM from the Jenkins VM. >> >> Our current setup is this: We have GitLab, Jenkins, and Nexus all >> running on their INDIVIDUAL and SEPARATE servers (VM's). >> >> For the integration of ALL 3 (GitLab, Jenkins, & Nexus) to work >> flawlessly, should they ALL be installed on ONE server or VM? >> >> Thanks. >> >> >> >> >> >> >> >> On Tuesday, April 28, 2015 at 12:12:48 AM UTC-4, Karen Carias wrote: >>> >>> No problem. I hope you solved it. :) >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "GitLab" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to gitlabhq+u...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/gitlabhq/01251e07-63ef-4ee5-b6a4-98f17a002980%40googlegroups.com >> >> <https://groups.google.com/d/msgid/gitlabhq/01251e07-63ef-4ee5-b6a4-98f17a002980%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/3bb3a1d0-229c-4c0f-822b-42f5d95ac080%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
