[00:00:08] <Mick99> how will it go away?
[00:00:47] <jenkinsci_builds> Starting build 630 for job jenkins_main_trunk (previous build: SUCCESS)
[00:15:25] *** esteele has quit IRC
[00:19:24] *** magnayn has joined #jenkins
[00:19:24] *** ChanServ sets mode: +v magnayn
[00:26:08] <gmcdonald> http://maven.glassfish.org/content/groups/public/com/sun/xml/txw2/txw2/20070624/txw2-20070624.pom is there
[00:34:01] *** fcamblor has quit IRC
[00:34:22] <jenkinsci_builds> Project jenkins_main_trunk build #630: SUCCESS in 33 min: http://ci.jenkins-ci.org/job/jenkins_main_trunk/630/
[00:34:23] <jenkinsci_builds> Seiji Sogabe: Updated Japanese localization.
[00:34:23] <jenkinsci_builds> Starting build 631 for job jenkins_main_trunk (previous build: SUCCESS)
[00:53:07] *** vivek_ has joined #jenkins
[00:53:57] *** esteele has joined #jenkins
[00:58:35] *** Lewisham has quit IRC
[01:00:19] <kohsuke> Mick99: yes, mwalling's comment was for you
[01:00:19] *** elpargo_ has joined #jenkins
[01:00:39] <kohsuke> The server that we download dependencies from apparently was down temporarily
[01:00:58] <kohsuke> it's now up and running, so if you retry now it should work
[01:02:19] *** elpargo has quit IRC
[01:02:19] *** elpargo_ is now known as elpargo
[01:03:44] <Mick99> @kohsuke ok thanks kohsuke
[01:06:55] <jenkinsci_builds> Project jenkins_main_trunk build #631: SUCCESS in 32 min: http://ci.jenkins-ci.org/job/jenkins_main_trunk/631/
[01:06:56] <jenkinsci_builds> Olivier Lamy: upgrade bundled ssh-slaves to 0.15
[01:07:11] <Mick99> @kohsuke once i generate the git.hpi, can i remove the expanded directory under JENKINS_HOME/plugins and replace the existing git.hpi with the new git.api and restart jenkins?
[01:07:29] <Mick99> or do i need to rename the file to git.hpi.pinned and restart jenkins
[01:11:06] <kohsuke> Mick99: deleting expanded directory is optional
[01:11:14] <kohsuke> Jenkins is smart enough to know that you put a new hpi
[01:11:27] <Mick99> @kohsuke..sweet, almost there...
[01:11:35] <kohsuke> once it restarts, go to the plugin manager to make sure your private build is recognized
[01:11:41] <kohsuke> it'll show you the version number that includes your name
[01:12:10] <kohsuke> jenkins-admin: create reverse-proxy-auth-plugin on github for kohsuke
[01:12:29] <jenkins-admin> New github repository created at https://github.com/jenkinsci/reverse-proxy-auth-plugin
[01:12:37] <Mick99> @kohsuke it's a great learnin from you today, will be able to make Jenkins much more powerful now wid custom changes to plugins :)
[01:13:11] <kohsuke> And please submit the pull requests when you make changes that are useful to others
[01:15:04] 
[01:15:18] <_Aeris_> specific dependencies?
[01:27:50] <Mick99> @kohsuke build success, got the new git.hpi, tryin it now
[01:28:11] *** jamesd__ has joined #jenkins
[01:28:39] *** jamesd__ has quit IRC
[01:31:03] *** jamesd_laptop has quit IRC
[01:31:34] *** jamesd2 has joined #jenkins
[01:36:17] *** magnayn has quit IRC
[03:05:30] *** smolyn has joined #jenkins
[03:14:29] *** Mick99 has quit IRC
[03:15:12] *** Haloperidol has quit IRC
[03:15:34] *** Haloperidol has joined #jenkins
[03:17:31] *** Lewisham has joined #jenkins
[03:17:31] *** ChanServ sets mode: +v Lewisham
[03:20:04] *** Mick99 has joined #jenkins
[03:20:36] <Mick99> @kohsuke @_Aeries_@ +other: great news, that fix actually worked and it's able to clone the repo :)
[03:46:16] *** esteele has quit IRC
[03:53:24] <prusswan> that's great, I expect to benefit from a more verbose output from git clone failures
[04:04:43] *** Mick99 has quit IRC
[04:22:50] *** vivek_ has quit IRC
[04:27:25] *** smolyn has quit IRC
[04:28:23] *** smolyn has joined #jenkins
[04:36:04] *** Mick99 has joined #jenkins
[04:37:41] <Mick99> don't want to bug more, but i tried two repo's and i can see they were able to clone but both of them failed with this error FATAL Invalid id: trace: built-in: git 'rev-list' ' 009d9xx0000099s'
[04:38:38] <Mick99> Java.lang.IllegalArgumentException: Invalid id: trace built-in: git 'rev_list' '009dxxxx00000099s'
[04:39:10] <Mick99> at org.spearce.jgit.lib.ObjectId.fromString(ObjectId.java: 230)
[04:39:15] <Mick99> any clues folks?
[05:10:57] *** echelog-1 has joined #jenkins
[05:13:30] *** cogocogo has quit IRC
[05:14:32] *** Mick99 has joined #jenkins
[05:14:51] <Mick99> FATAL: Invalid id: setup: git_dir: .git
[05:15:16] <Mick99> i am getting that error, any ideas anyone?
[05:28:29] *** wilmoore has joined #jenkins
[05:37:58] *** Mick99 has quit IRC
[05:50:34] *** joewilliams is now known as joewilliams_away
[06:10:13] *** cristhiank has quit IRC
[06:11:39] *** jamesd2 has quit IRC
[06:12:04] *** jamesd2 has joined #jenkins
[06:19:05] *** peeps[work] has joined #jenkins
[06:22:00] *** peepsalot has quit IRC
[06:29:19] *** peeps has joined #jenkins
[06:32:59] *** peeps[work] has quit IRC
[06:37:48] *** zaphX has joined #jenkins
[06:45:36] *** Lewisham has joined #jenkins
[06:45:36] *** ChanServ sets mode: +v Lewisham
[06:49:20] *** sshaw has joined #jenkins
[06:50:31] *** rcampbell_ has quit IRC
[06:54:37] *** zaphX has quit IRC
[07:05:48] *** smolyn has quit IRC
[07:07:16] *** wilmoore has quit IRC
[07:16:21] *** wilmoore has joined #jenkins
[07:43:59] *** elpargo_ has joined #jenkins
[07:46:22] *** elpargo has quit IRC
[07:48:28] *** elpargo_ has quit IRC
[07:54:08] *** vivek_ has joined #jenkins
[07:54:09] *** rakslice has quit IRC
[08:02:38] *** elpargo has joined #jenkins
[08:18:02] *** ExtraSpice has joined #jenkins
[08:19:38] *** elpargo_ has joined #jenkins
[08:20:31] *** elpargo has quit IRC
[08:20:31] *** elpargo_ is now known as elpargo
[08:25:53] *** vivek_ has quit IRC
[08:28:05] *** sshaw has quit IRC
[08:30:46] *** vivek_ has joined #jenkins
[08:30:58] *** vivek_ has joined #jenkins
[08:39:02] *** imeikas has quit IRC
[08:39:25] *** imeikas has joined #jenkins
[08:51:37] *** _marc` has quit IRC
[08:52:26] *** awb has quit IRC
[08:56:18] *** magnayn has joined #jenkins
[08:56:18] *** ChanServ sets mode: +v magnayn
[08:59:40] *** awb has joined #jenkins
[09:01:37] *** elpargo has quit IRC
[09:04:30] *** awb has quit IRC
[09:08:38] *** elpargo has joined #jenkins
[09:10:02] *** Lewisham has quit IRC
[09:12:30] *** Stubbs has quit IRC
[09:45:38] *** olamy has quit IRC
[09:46:12] *** magnayn has quit IRC
[10:01:02] *** akostadinov has joined #jenkins
[10:08:48] *** LiohAu has joined #jenkins
[10:11:19] *** redsolo has quit IRC
[10:12:07] *** akostadinov has quit IRC
[10:12:44] *** akostadinov has joined #jenkins
[10:14:03] *** akostadinov has quit IRC
[10:14:28] *** vivek_ has quit IRC
[10:14:41] *** akostadinov has joined #jenkins
[10:15:04] *** akostadinov has quit IRC
[10:15:04] *** andreasmandel has joined #jenkins
[10:15:39] *** akostadinov has joined #jenkins
[10:22:04] *** akostadinov has quit IRC
[10:22:40] *** akostadinov has joined #jenkins
[10:25:42] *** akostadinov has quit IRC
[10:26:20] *** akostadinov has joined #jenkins
[10:27:26] *** akostadinov has quit IRC
[10:28:01] *** akostadinov has joined #jenkins
[10:32:17] *** awb has joined #jenkins
[10:32:34] *** akostadinov has quit IRC
[10:33:07] *** akostadinov has joined #jenkins
[10:35:13] *** akostadinov has quit IRC
[10:35:48] *** akostadinov has joined #jenkins
[10:37:30] *** Sebast1an has joined #jenkins
[10:37:42] *** Sebast1an is now known as Sebastian
[10:42:02] *** akostadinov has quit IRC
[11:12:49] *** awb has quit IRC
[11:13:48] *** magnayn has joined #jenkins
[11:13:48] *** ChanServ sets mode: +v magnayn
[11:27:38] *** cogocogo has joined #jenkins
[11:31:12] *** Stubbs has joined #jenkins
[11:48:46] *** protocol7 has joined #jenkins
[11:50:40] *** protocol7 has joined #jenkins
[11:51:40] *** protocol7_ has joined #jenkins
[11:51:40] *** protocol7 has quit IRC
[11:51:42] *** protocol7_ is now known as protocol7
[11:59:31] *** nd___ has quit IRC
[12:02:52] *** akostadinov has joined #jenkins
[12:03:53] *** nd__ has joined #jenkins
[12:14:08] *** magnayn has quit IRC
[12:18:46] *** Stubbs has quit IRC
[12:25:29] *** protocol7 has quit IRC
[12:29:34] *** LiohAu has quit IRC
[12:41:25] *** kutzi has joined #jenkins
[12:41:25] *** ChanServ sets mode: +v kutzi
[12:45:10] *** magnayn has joined #jenkins
[12:45:10] *** ChanServ sets mode: +v magnayn
[12:55:23] *** LiohAu has joined #jenkins
[13:08:47] *** Haloperidol has joined #jenkins
[13:11:37] *** _Aeris_ has quit IRC
[13:12:39] *** _aeris_ has joined #jenkins
[13:16:04] *** _aeris_ has quit IRC
[13:18:08] *** _aeris_ has joined #jenkins
[13:20:14] *** Dummy has joined #jenkins
[13:21:41] *** protocol7 has joined #jenkins
[13:29:04] *** protocol7 has quit IRC
[13:30:37] *** aeris- has joined #jenkins
[13:30:39] *** _aeris_ has quit IRC
[13:40:06] *** Sebastian has quit IRC
[13:42:39] *** protocol7 has joined #jenkins
[13:49:25] *** akostadinov has quit IRC
[14:02:14] *** protocol7 has quit IRC
[14:12:23] *** protocol7 has joined #jenkins
[14:16:00] *** callum1 has joined #jenkins
[14:16:36] <callum1> Hi all can anyone help me with a maven classpath issue in Jenkins?
[14:20:38] <FauxFaux> Not if you don't ask.
[14:22:15] <callum1> I have referenced some project jars in eclipse this runs my tests fine. When running in jenkins im not sure how to add this classpath dependancy and as a result the tests fail
[14:22:24] <callum1> how can I add this in maven?
[14:22:35] <callum1> or jenkins i should say
[14:28:18] *** protocol7 has quit IRC
[14:32:32] <sietse> You should add them as dependencies to your maven pom
[14:33:30] <sietse> Just fix it locally (till mvn clean install runs succesfull)
[14:33:39] <sietse> Then add a job to Jenkins
[14:43:24] <callum1> your right ill remove the local jars and add them as maven dependencies
[14:43:26] <callum1> thanks
[14:44:48] <sietse> It is good practice to have a environment independent configuration
[14:44:55] <sietse> that's where maven shines
[14:46:24] <aeris-> or gradle =)
[15:03:26] *** akostadinov has joined #jenkins
[15:13:30] *** callum1 has left #jenkins
[15:15:45] <jenkinsci_builds> Starting build 632 for job jenkins_main_trunk (previous build: SUCCESS)
[15:48:14] <jenkinsci_builds> Project jenkins_main_trunk build #632: SUCCESS in 32 min: http://ci.jenkins-ci.org/job/jenkins_main_trunk/632/
[15:48:14] <jenkinsci_builds> Starting build 633 for job jenkins_main_trunk (previous build: SUCCESS)
[16:05:56] *** andreasmandel1 has joined #jenkins
[16:07:10] *** andreasmandel has quit IRC
[16:10:44] *** Kw4h has joined #jenkins
[16:11:46] *** andreasmandel has joined #jenkins
[16:14:43] *** andreasmandel1 has quit IRC
[16:14:51] *** _marc` has joined #jenkins
[16:21:21] <jenkinsci_builds> Project jenkins_main_trunk build #633: SUCCESS in 33 min: http://ci.jenkins-ci.org/job/jenkins_main_trunk/633/
[16:21:22] <jenkinsci_builds> wyukawa: fix help link to fingerprint document
[16:31:28] *** Mick99 has joined #jenkins
[16:43:05] *** jamesd2 has quit IRC
[16:43:33] *** jamesd2 has joined #jenkins
[17:30:41] *** vivek_ has joined #jenkins
[17:36:50] *** jenkinsci_builds has quit IRC
[17:38:15] *** jenkinsci_builds has joined #jenkins
[17:38:22] *** wilmoore has quit IRC
[17:42:35] *** wilmoore has joined #jenkins
[17:44:17] *** Mick99_ has joined #jenkins
[17:47:18] <Mick99_> @aeris + others: guys, any idea what could be causing this error: java.lang.IllegalArgumentException: Invalid id: setup: git_dir: .git
[17:47:35] <aeris-> hum
[17:47:37] <Mick99_> Full log trace here - http://pastebin.com/Qp6qLuYa
[17:48:02] <aeris-> windows hates file name with . at the first letter
[17:49:13] <Mick99_> but in that case all git installations will fail as they have a .git directory
[17:50:57] <aeris-> perhaps
[17:51:24] <aeris-> but try to create .git file directly from
[17:51:33] <aeris-> from windows
[17:51:39] <aeris-> it fails
[17:52:05] 
[17:52:42] <Mick99_> yes i know that, but in this case do you think it could be a permission issue?
[17:53:04] <aeris-> permission or fs problem
[17:53:39] <Mick99_> any workarounds apart from movin to a diff O.S ?
[17:54:16] *** kutzi has quit IRC
[17:54:50] *** kutzi has joined #jenkins
[17:54:50] *** ChanServ sets mode: +v kutzi
[17:55:50] <aeris-> hum
[17:55:55] <aeris-> strange
[17:56:22] <aeris-> see here
[17:56:29] <aeris-> http://egit.eclipse.org/w/?p=jgit.git;a=blob;f=org.eclipse.jgit/src/org/eclipse/jgit/lib/ObjectId.java;h=4d6dab4bb60f71479711938a2f4917a237a707e3;hb=HEAD
[17:56:32] <aeris-> line 230
[17:57:11] 
[17:57:29] <aeris-> it must be a commit ref i think?
[17:58:11] *** rcampbell_ has joined #jenkins
[17:58:20] <Mick99_> i don't pass anything, i think it gets passed internally, by default git_dir is set to .git
[17:58:41] <Mick99_> i tried to set the GIT_DIR as an env. variable with complete absolute path to the .git directory but it still failed
[17:59:02] <aeris-> yes but this function expect commit id?
[18:00:27] <Mick99_> are u saying its an issue on the dev. side who committed to the repo ?
[18:02:37] <prusswan> .git is not the issue here, because I never ran into this problem myself
[18:03:24] <aeris-> Mick99_ > no
[18:03:47] <Mick99_> there was a very similar issue reported in jenkins here and its marked as fixed - http://issues.hudson-ci.org/browse/HUDSON-7207
[18:03:47] <aeris-> perhaps --progress add some stuff on output
[18:03:59] <jenkins-admin> JENKINS-7207:Hudson fails to run a merge commit (Closed) http://jenkins-ci.org/issue/7207
[18:04:01] <aeris-> and then git parser is broker
[18:04:02] <Mick99_> so not sure why the fix is not in the current build of jenkins
[18:06:09] <aeris-> what is your git plugin version?
[18:06:36] <Mick99_> i downloaded the latest one ( i expect 1.1.6) and then patched it with --progress
[18:07:21] <Mick99_> so now the git plugin is able to clone the repo but then fails with that error, future builds fail wid tht error as well
[18:08:45] <Mick99_> so now the plugin version shows up as : 1.1.7-SNAPSHOT(private -03/26/2011 08:25-mick)
[18:09:21] *** jamesd2 has quit IRC
[18:09:23] <prusswan> im curious about something
[18:09:35] <Mick99_> @prusswan wat?
[18:09:56] <aeris-> Mick99_ > where is the sources from your build?
[18:09:58] <prusswan> when you encountered these errors, have you tried other git repos or do they only happen to the one you are using?
[18:10:49] <Mick99_> aeris- I downloaded it from the location @kohsuke told i.e https://github.com/jenkinsci/git-plugin
[18:10:58] *** jamesd2 has joined #jenkins
[18:12:24] <Mick99_> prusswan Yes, I tried on another repo but that has it's own merge issues but i know for sure this one worked fine using the manual methods i did before (manually clone using tortoise git and then future builds from jenkins as jenkins was just choking while creating clone)
[18:14:28] <prusswan> oh ok so your original problem was only with the clone, the rest of the job worked fine, and the problems you encounter now are with the plugin that you built to resolve the clone issue
[18:15:50] <Mick99_> yes you can say that but it could be that by adding '--progress' we just solved one part and might be it needs one more fix
[18:17:18] <Mick99_> i just did a 'git checkout 'exact_same_revision_thats_choking> in command line and it went through fine
[18:17:34] <Mick99_> it showed me  setup: git_dir: .git
[18:17:52] <Mick99_> setup: worktresss: /path/to/worktreee
[18:18:22] <Mick99_> and then completed successfully, so seems like it comes down to wireshark again :(
[18:19:02] *** javabot has quit IRC
[18:19:12] <prusswan> can you upload the plugin which you built somewhere?
[18:19:14] <aeris-> Mick99_ > i don't see kohsuke commit in that source tree
[18:19:29] *** javabot has joined #jenkins
[18:19:48] <Mick99_> kohsuke did not committed it, i made the change, built it locally and then deployed it locally
[18:20:23] <aeris-> can you send me the patch?
[18:20:41] <Mick99_> yes, do you guys know any gud file uploadin site?
[18:21:29] <aeris-> pastebin
[18:21:51] <aeris-> send just the diff
[18:22:35] *** Kw4h has quit IRC
[18:22:47] *** elpargo_ has joined #jenkins
[18:24:45] *** elpargo has quit IRC
[18:24:45] *** elpargo_ is now known as elpargo
[18:29:29] *** sshaw has joined #jenkins
[18:33:05] *** Kw4h has joined #jenkins
[18:34:48] *** Mick99_ has quit IRC
[18:50:30] *** rcampbell__ has joined #jenkins
[18:50:30] *** rcampbell_ has quit IRC
[18:50:50] *** rcampbell__ has quit IRC
[18:51:18] *** recampbell has joined #jenkins
[18:56:57] *** Stubbs has joined #jenkins
[18:58:24] *** mick99_ has joined #jenkins
[18:59:35] <mick99_> aeris- prusswan one other thing i am noticed in wireshark logs is there's a no-progress parameter here as well, so could it be the same issue like y'day where we need a pass a --progress parameter for checkout/fetch commands as well?
[19:00:36] <aeris-> mick99_ > after clone, no network access is done
[19:00:44] <aeris-> all data is local
[19:00:49] <aeris-> so?
[19:01:11] <mick99_> yah but i mean i am runnin new builds now, so probably i expect a checkout is being done at this stage
[19:02:21] <aeris-> perhaps
[19:05:36] *** jamesd2 has quit IRC
[19:06:09] *** jamesd2 has joined #jenkins
[19:06:11] *** kutzi has quit IRC
[19:07:55] *** drulli has joined #jenkins
[19:07:55] *** ChanServ sets mode: +v drulli
[19:10:14] *** jamesd_laptop has joined #jenkins
[19:10:36] *** jamesd2 has quit IRC
[19:12:11] *** choas has joined #jenkins
[19:19:54] *** smolyn has joined #jenkins
[19:26:19] *** MMX2 has joined #jenkins
[19:27:09] <mick99_> aeris- any idea how to print out  from gitapi.java?
[19:27:35] <mick99_> i would like to print out this line: while ((line = rdr.readLine()) != null) {
[19:28:15] *** joewilliams_away is now known as joewilliams
[19:28:15] <MMX2> Hi, I was wondering if it would be possible for jenkins to know what dependencies a project has if it only contains out of modules (sub projects)
[19:28:34] <aeris-> mick99_ > what is the need?
[19:29:28] <mick99_> GITAPI.java line 850 reads the line from buffered reader and sends it to org.spearce.jgit.lib.ObjectId.fromString(ObjectId.java:230)
[19:29:44] <mick99_> org.spearce.jgit.lib.ObjectId.fromString(ObjectId.java:230) fails if the arg passed is not 40 digits in length
[19:29:44] 
[19:29:48] <MMX2> I splitted our huge project into it's main modules but since there are no direct dependencies but only modules within the child modules of the moaster pom, jenkins dose not recognies any snapshot changes
[19:30:05] <mick99_> so trying to see what is being passed to org.spearce.jgit.lib.ObjectId.fromString(ObjectId.java:230)
[19:30:40] <MMX2> i know aeris- but for some reason the projects do not get triggered
[19:31:15] <aeris-> this project depends of an other?
[19:31:23] <MMX2> even Dependency Graph dose not show any tree but only a list of modules
[19:31:50] <MMX2> the sub modules of the projects do depend on each other
[19:32:30] <aeris-> the build is not trigger in which case?
[19:32:32] <aeris-> in
[19:32:42] <aeris-> in case of commit?
[19:32:57] <MMX2> i am not quite sure how deep the dependencies are nested since i only do take care of jenkins but not the software itself.
[19:33:43] <aeris-> MMX2 > on jenkins, you have one job per module?
[19:33:50] <aeris-> or only the parent?
[19:34:08] <MMX2> this has not been tested in case of a commit. but i expected when i build the parent pom which is a dependency of all sub modules that all projects would be scheduled to be build
[19:34:27] <aeris-> no
[19:34:46] <aeris-> not if you don't configure each project
[19:34:48] <MMX2> the whole project only uses snapshot dependencies
[19:35:21] *** fcamblor has joined #jenkins
[19:35:25] <aeris-> if you have one job per module, you MUST configure build chain manually
[19:35:26] *** ChanServ sets mode: +v fcamblor
[19:35:44] <MMX2> okay
[19:36:25] <aeris-> i don't think jenkins cross-analyse pom to do it automatically
[19:36:46] <MMX2> hm, but wouldn't it be possible for jenkins to create a dependency tree of each module (project) so that it knows all dependencies and can trigger a build on that list?
[19:37:05] <MMX2> i thought jenkins would trigger on fingerprint
[19:37:11] <aeris-> all is possible =)
[19:37:18] *** Lewisham has joined #jenkins
[19:37:18] *** ChanServ sets mode: +v Lewisham
[19:37:38] <aeris-> it's just time and motivation problem =)
[19:37:58] <aeris-> MMX2 > in
[19:37:59] *** jasonb has quit IRC
[19:38:14] <mick99_> aeris- @kohsuke prusswan wohooooooooooooooooo.....worked finally!!! 2 days of effort paid off...
[19:38:15] <MMX2> yeah i know that everything is possible, it's just a matter of time and effort to get it implemented :) but the question is if such a behavior already exists or is easily achivable
[19:38:15] <aeris-> in common case, dependencies are not jobed
[19:38:49] <aeris-> MMX2 > not at this time i think
[19:38:54] <mick99_> @kohsuke just discovered another issue with the git-plugin which we shud fix asap
[19:39:44] <MMX2> right now we have a build duration of 2.5 hrs :S
[19:40:04] 
[19:40:14] <mick99_> yes..that's the issue
[19:40:59] <mick99_> aeris- @kohsuke the problem was GIT_TRACE was enabled and the git-plugin uses buffered reader to read the lines and pass them to jgit which is where it was choking
[19:41:41] <mick99_> after decompiling the jgit code and going through all the methods, i knew GIT_TRACE was choking it down, so i turned off GIT_TRACE and bang, it worked !!!
[19:42:10] <mick99_> but i think this shud be fixed in the git-plugin, they shud handle the arguments in a better way then blindly passing them to jgit
[19:42:39] <aeris-> where is the code with GIT_TRACE ?
[19:42:45] <aeris-> on jgit?
[19:43:22] <mick99_> no GIT_TRACE was enabled on client side (my side), people enable it to debug GIT calls, but then whenever a user will enable it
[19:43:40] <mick99_> he will not know that unknowingly it will break down his jenkins build
[19:44:00] <aeris->  debug GIT calls? Oo
[19:44:09] <aeris-> what the target? Oo
[19:44:45] <mick99_> after enabling GIT_TRACE only, i was able to figure out that --no-progress was being passed
[19:45:13] *** akostadinov has quit IRC
[19:45:28] <mick99_> GIT_TRACE: If this variable is set to "1", "2" or "true" (comparison is case insensitive), git will print trace: messages on stderr telling about alias expansion, built-in command execution and external command execution. If this variable is set to an integer value greater than 1 and lower than 10 (strictly) then git will interpret this value as an open file descriptor and will try to write the trace messages into this file descript
[19:46:19] <mick99_> (starting with a / character), git will interpret this as a file path and will try to write the trace messages into it.
[19:47:19] <aeris-> yes but why trace is enable on your pc?
[19:48:27] <mick99_> i enabled it last week to debug what was going on, at that point i didn't knew the clone was choking because of --progress
[19:49:12] <mick99_> but users can always enable that option as GIT allows that option, so Jenkins shud be smart enough to not be confused with that and shud still parse arguments correctly i think...
[19:49:59] <mick99_> so when we fixed clone, it still didn't worked as GIT_TRACE was still enabled in the background, turned it off and bang, it worked....
[19:50:19] <mick99_> i am so happy and so thankful to you, @kohsuke pruswaan selkins and all other guys here :)
[19:50:33] *** jasonb has joined #jenkins
[19:51:34] <mick99_> @kohsuke can i commit the --progress back to the git-plugin source, so that future version includes the fix?
[19:52:52] *** sgronblo has left #jenkins
[19:53:33] *** jasonb has quit IRC
[19:59:27] *** jasonb has joined #jenkins
[20:01:40] *** drulli has quit IRC
[20:11:59] <mick99_> i have added my comment to: http://issues.jenkins-ci.org/browse/JENKINS-9168?focusedCommentId=147246#comment-147246
[20:12:01] <jenkins-admin> JENKINS-9168:"git clone" should add --progress (Open) http://jenkins-ci.org/issue/9168
[20:14:50] *** drulli has joined #jenkins
[20:14:51] *** ChanServ sets mode: +v drulli
[20:25:49] *** elpargo_ has joined #jenkins
[20:26:50] *** elpargo has quit IRC
[20:26:50] *** elpargo_ is now known as elpargo
[20:35:28] *** Kw4h has quit IRC
[20:44:35] *** Dummy has quit IRC
[20:58:10] *** Mick99 has quit IRC
[21:11:39] *** vjuranek has joined #jenkins
[21:18:41] *** mick99_ has quit IRC
[21:25:00] *** jasonb has quit IRC
[21:29:59] *** joewilliams is now known as joewilliams_away
[21:31:08] *** LiohAu has quit IRC
[21:48:42] *** jieryn-w has joined #jenkins
[21:48:42] *** ChanServ sets mode: +v jieryn-w
[22:03:06] *** drulli has quit IRC
[22:04:07] *** kisielk has quit IRC
[22:18:18] *** kutzi has joined #jenkins
[22:18:19] *** ChanServ sets mode: +v kutzi
[22:32:52] *** smolyn has quit IRC
[22:42:39] <MMX2> Maven: If you have a subModule B which is defined in Module A. Is subModule B then a dependency of Module A?
[22:43:53] <aeris-> no
[22:44:35] <MMX2> hm, still trying to think how to solve my issue
[22:44:41] <aeris-> and if this is the case, it leads to infinite loop
[22:45:16] <kutzi> not necessarily, a submodule needs not have to have the aggregator POM as parent
[22:45:21] <aeris-> because B need A pom
[22:45:48] <aeris-> if this is the parent yes
[22:46:06] <kutzi> that's a common misconcepted. There's a difference between aggregation (modules) and parent-relationship
[22:46:10] <aeris-> but this is the most common case i think, no?
[22:46:15] <kutzi> yes
[22:46:20] <kutzi> it's the common case
[22:46:31] *** recampbell has quit IRC
[22:47:27] <MMX2> well, i am still seeking for a solution, maybe i can provide a module count of the project
[22:47:43] <kutzi> what's your problem?
[22:48:02] <MMX2> creating each module as project within jenkins would be a maintenance desaster
[22:48:55] <MMX2> I have a project that takes 2.5 hrs to build
[22:49:10] <kutzi> ouch
[22:49:18] <MMX2> it consists of a master pom vile which contains only modules
[22:49:42] <MMX2> so i created a project for each module
[22:50:09] <MMX2> but each new project has even more sub modules, not sure how deep they nest
[22:51:21] <kutzi> and the problem is that you don't want to manually create a job for each module?
[22:51:25] <MMX2> the issue is that if i build project A which is a dependency of module E within project B, B is not getting triggered
[22:52:01] <kutzi> but E is triggered?
[22:52:14] <MMX2> no B is not triggered
[22:52:40] <MMX2> as far as i understood Jenkins only knows about direct Project dependencies
[22:53:04] <kutzi> no, it knows about module dependencies, too, if you use the Maven2/3 project type
[22:53:19] <MMX2> but not about dependencies nested within modules and sub modules
[22:53:44] <MMX2> we use Maven 3 to build our project
[22:54:15] <kutzi> if E is a module in the B multi-module build and A is a dependency of E, and A is build then B will be build afterwards
[22:54:43] <MMX2> well okay sorry we have to alter A
[22:56:01] <MMX2> lets say module F within project A is a dependency of module E within project B
[22:56:05] <MMX2> i hope you can follow
[22:56:11] <kutzi> yes
[22:56:23] <MMX2> if i now bild project A, B is not getting triggered
[22:56:41] <kutzi> it should be. That's how the maven project type in Jenkins works
[22:56:54] <MMX2> i know, but it dosen't
[22:57:06] <kutzi> is 'build when snapshot dependency is build' enabled?
[22:57:14] <MMX2> i need to take a break, but ill be back in 5-10 minutes
[22:57:23] <MMX2> yes on all of the projects
[22:57:36] <kutzi> have you checked that the versions match?
[23:06:15] <MMX2> okay i am back
[23:06:16] <MMX2> sorry
[23:06:57] <MMX2> i am pretty sure they do but i just remembered that there was a bug with blocking upstream and downstream projects
[23:07:37] <kutzi> then I don't know what could be the problem.
[23:07:53] <MMX2> what made me believe that jenkins ins not handling the projects "properly" is that the dependency graph only shows a list of projects but no tree at all
[23:07:56] <kutzi> Is A listed as an upstream job in B and vice versa?
[23:08:03] <MMX2> nope
[23:08:34] <kutzi> and they are Maven2/3 projects not Freestyle projects?
[23:08:53] <MMX2> yes maven projects no freestyle
[23:09:48] <kutzi> maybe there's a bug in the Jenkins version you're using, but I haven't heard of anything like that, yet
[23:10:00] <MMX2> I'd love to show you the server but its behind a firewall
[23:10:10] <kutzi> basically, this works since a very long time
[23:10:47] <MMX2> thats what i read about: http://issues.jenkins-ci.org/browse/JENKINS-8929
[23:10:49] <jenkins-admin> JENKINS-8929:Deadlock when upstream and downstream jobs are blocked on each other (In Progress) http://jenkins-ci.org/issue/8929
[23:11:38] <kutzi> that's a completely different problem, isn't it?
[23:12:07] <MMX2> hm but thats not the case for me
[23:12:25] <MMX2> yeah the jobs don't get scheduled
[23:12:28] <kutzi> You should open a JIRA issue against the maven2 plugin and ideally attach your job configuration and the POMs of F and E
[23:12:45] <MMX2> and the graph also shows no tree
[23:14:55] <aeris-> kutzi > jenkins doesn't link maven project each other automatically, right?
[23:15:45] <kutzi> no, it should link them automatically
[23:16:07] <aeris-> ok
[23:16:33] <aeris-> so MMX2 problem is a new feature and not a bug i think
[23:16:33] <kutzi> One thing, though: you have to trigger the jobs once manually (or via SCM trigger), so that Jenkins can parse the POMs and detect the dependencies
[23:16:43] <kutzi> ?
[23:17:03] <MMX2> yeah i did that
[23:17:09] <MMX2> i build them once
[23:17:28] <kutzi> aeris- I didn't get your last commet
[23:17:30] <MMX2> and then build the parent which is included in many poms as parent
[23:17:43] <aeris-> MMX2 > do you add dependencies MANUALLY to your jobs?
[23:18:24] <MMX2> hm i am not sure what you mean with manually - (I am not a java developer :/ )
[23:19:27] <MMX2> i just take care of jenkins
[23:19:31] <aeris-> do you think that just adding B job which rely on a A job from a maven point of view add B job to A children from jenkins point of view?
[23:19:35] <MMX2> and the debian system running it
[23:19:52] *** joshc has left #jenkins
[23:20:08] <aeris-> i think this is the step you miss
[23:20:38] <aeris-> you must declare B job as A dependances in jenkins
[23:20:41] <aeris-> manually
[23:20:50] <aeris-> not just create B job
[23:20:58] <kutzi> MMX2 you should contact the java developers in your organisation - maybe they can help you figure it out
[23:21:25] <kutzi> aeris-: no he doesn't need to do that
[23:21:33] <aeris-> hu?
[23:21:34] <MMX2> the project consists of 494 modules
[23:22:02] <MMX2> at least thats what' $ find . -type f -name 'pom.xml' | xargs grep '\<module\>' | wc -l' told me
[23:22:08] <kutzi> if they have dependencies defined in Maven POMs, Jenkins can figure out the job dependencies by itself
[23:22:12] <aeris-> jenkins has no way to see the A job results are used by B jobs
[23:22:46] <aeris-> kutzi > in a same job yes
[23:22:47] <MMX2> aeris-: no i don't think that is that's the case
[23:23:02] <aeris-> but cross jobs?
[23:23:07] <kutzi> no, also across jobs
[23:23:12] <aeris-> Oo
[23:23:25] <MMX2> hm maybe i just didn't test properly
[23:23:29] <kutzi> that's what the maven job type is all about
[23:23:52] <aeris-> it's very dangerous i think
[23:24:06] <kutzi> what is dangerous?
[23:24:12] <aeris-> if i create branch job for example
[23:24:37] <kutzi> yes?
[23:24:52] <aeris-> i don't want a build of B' or B" trigger the build of A project
[23:25:18] <kutzi> if you create a branch, you MUST change the POM versions on the branch!
[23:25:43] <aeris-> hum?
[23:25:48] <kutzi> they are different version of the artifact, you must track this in the version
[23:26:10] <aeris-> i'm not agree
[23:26:27] <aeris-> merge could be a real pain in this case
[23:26:44] <kutzi> what when you deploy the artifact to a repository. How would you differ them not if not by version?
[23:27:04] <aeris-> branch are not deployed
[23:27:13] <kutzi> why not?
[23:27:36] <aeris-> branch is to test some potentially bro
[23:27:38] <aeris-> bre
[23:27:41] <aeris-> ><
[23:27:47] <kutzi> ? :)
[23:27:52] <aeris-> broken features
[23:28:24] <aeris-> devs must try the result with others dependencies
[23:28:32] <kutzi> yes and the artifacts created from the branch builds are deployed to the repo, so they can be tested on a test server
[23:28:37] <aeris-> but other depends use real version
[23:28:45] <aeris-> not branched ones
[23:28:45] <kutzi> that's at least how it works in my organization
[23:29:21] <aeris-> if i have a A project depends on B project
[23:29:47] <aeris-> if dev want to try a b branch, A pom doesn't change
[23:30:07] <aeris-> and continue to rely on B version, not B-branch
[23:30:20] <kutzi> well that depends on how you use it in your organisation, but clearly an artifact of a module on a branch is different from the artifact on trunk and therefore should have a different version
[23:30:41] <aeris-> in scm theory yes
[23:30:49] <kutzi> and in practice
[23:31:05] <aeris-> but with maven in the loop this is too complicated
[23:31:32] <kutzi> if you don't like that behaviour in jenkins, you should use the freestyle job or disable 'trigger when SNAPSHOT ..'
[23:31:42] <aeris-> if i want to try a feature, i don't want to changes all dependants
[23:32:04] <MMX2> okay i just build a project where i know that it has sub modules that are are dependencies for a lot of sub modules in other projects, the other projects didn't get scheduled
[23:32:26] <kutzi> well, Maven definitely doesn't make it easier, but the principle problem is the same no matter which build tool you use
[23:32:42] <aeris-> kutzi > yes
[23:33:06] <aeris-> but in your case, you must branch all yours projects
[23:33:19] <aeris-> and not only the target artifact
[23:33:31] <aeris-> and good luck for merge?
[23:33:39] <kutzi> yes, it does really hurt, but that's what what we make for all dependend projects
[23:33:54] <aeris-> ok
[23:34:13] <kutzi> we're aiming to use more fixed version, so that the pain gets less
[23:34:25] <aeris-> it's an acceptable point of view for me
[23:34:37] <aeris-> but not my way of work
[23:34:43] 
[23:34:57] <MMX2> yeah okay thanks
[23:35:24] <MMX2> i'd love to provide more info but i am not sure what could help
[23:35:36] *** Haloperidol has quit IRC
[23:35:49] <kutzi> as I said: jobs configuration and POMs of E and F
[23:36:05] <kutzi> and talk to your Java developers
[23:36:17] <MMX2> okay i'll ask tomorrow if i can publish them, but i guess i can't
[23:36:22] <aeris-> MMX2 > post output of dependency:tree
[23:36:32] <aeris-> and your job configuration
[23:36:33] <kutzi> good idea
[23:37:16] <MMX2> I guess we have to try to create a test case
[23:39:09] <MMX2> thanks for you help guys
[23:39:12] <MMX2> cya
[23:47:36] *** kutzi has quit IRC
[23:52:22] *** MMX2 has quit IRC





top