Team Chat Logs

December 11, 2009

2009 11
Mo Tu We Th Fr Sa Su
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      
<< <   > >>

[00:30:49.751810]<cogocogo>osimons: It's regular basic auth (ref. last days problems with bitten-slave and http auth)
[01:59:19.963633]<osimons>cogocogo: and are both slave and master running same version?
[01:59:43.003096]<cogocogo>osimons: Yes. I installed them both yesterday.
[02:00:12.151181]<osimons>turn on verbose logging on slave (-v) - anything useful?
[02:00:58.587035]<cogocogo>I'll try
[02:06:34.926112]<cogocogo>osimons: My bad! I had setup a <Location ... /builds> and the bitten slave first uses /login (which the user it's using wasn't allowed to)
[02:09:12.580412]<osimons>goodie
[02:09:59.913357]<cogocogo>It's only /login and /builds it needs access to then?
[02:46:54.318416]<cogocogo>osimons: What would you say would be the best way for me to have a working copy of bitten installad while implementing new recipe commands? I have installed bitten using easy_install <svn url>
[02:47:30.874297]<osimons>cogocogo: only /login and /builds, yes
[02:49:01.111997]<osimons>cogocogo: are you adding new features? if so install bitten using python setup.py develop - that runs it off your working copy instead of pushing eggs into site-packages
[02:49:16.477620]<cogocogo>Ah, ok
[02:49:22.697061]<cogocogo>I'm adding new features yes.
[02:49:30.092390]<cogocogo>Adding some php commands.
[02:49:52.625564]<osimons>(need to run 'develop' every time you change metadata though - to have it refresh its knowledge of entry_points and such)
[02:50:05.279244]<osimons>cool
[02:50:10.434697]<osimons>patches welcome :-)
[02:50:20.143472]<cogocogo>They will come when I'm done. :)
[02:51:05.956700]<osimons>- also welcome is verification of php commands that actually work.... don't use any of it myself, so hard to know if things actually are ok.
[02:51:44.355993]<cogocogo>I will use phpunit and the coverage commands so I can at least verify that they work for me, and of not, make them work. I'll add 3-4 new commands.
[02:54:59.855350]<osimons>nice. much welcome. you have of course looked at open tickets already - are some php stuff and patches in there...
[02:55:25.438524]<cogocogo>Yup, I've looked at them. I can add some new tickets with the stuff I'm doing as well
[04:14:31.978935]<cogocogo>osimons: So I simply change the .py files that I've extracted and run setup.py develop to use the changes?
[04:15:00.690213]<osimons>cogocogo: for changed files, all that should be needed is server restart
[04:15:38.379642]<osimons>- however, to find new tools you need entry in setup.py with tool reference. that metadata change needs to be rebuilt (which setup.py call does)
[04:16:04.614372]<cogocogo>osimons: I'm running the slave on a different server, so I'm only changing the phptools.py file
[04:16:07.770981]<cogocogo>ok
[04:16:34.986122]<osimons>still - it looks in metadata to find what file and method to call when it sees the command in the recipe
[04:17:38.114269]<cogocogo>Yup, I'm looking at it now.
[11:11:26.417025]<cogocogo>Is the xmlio utility documented somewhere?
[11:14:16.333303]<cogocogo>Looking at the source now. I think that'll do
[11:34:22.570719]<cogocogo>I'm a bit confused as to how this whole thing works. I've been using cruisecontrol for a while and can't really get how bitten flows. The bitten-slave (that I have installed on a different machine than the one hosting the trac instance) is the one that parses xml files and generate results that it posts to the master?
[11:34:46.146131]<cogocogo>The build recipe's ... are they to live on the master, or where the slave is run?
[11:37:20.253393]<cogocogo>I also see there is a Manage Build Configurations page in my trac instance that I can add stuff ... am I to specify recipe's here and have the slave fetch them when connecting?
[11:41:34.505791]<cogocogo>I've read through the white paper and understand the flow of things a bit more.
[11:42:06.839134]<cogocogo>But I'm a bit confused about the "Add Configuration" part in the admin area of the trac.
[12:29:46.629337]<cogocogo>I seem to be getting somewhere now. :) But, when my bitten-slave has finished I'm getting:
[12:30:07.368438]<cogocogo>[DEBUG ] Sending POST request to '<url>'
[12:30:08.114821]<cogocogo>[DEBUG ] Server returned error 405: Method Not Allowed (Method GET not allowed)
[12:30:11.112191]<cogocogo>[DEBUG ] Removing build directory /tmp/bittenMJSamN/build_build_1
[12:30:13.516341]<cogocogo>[ERROR ] HTTP Error 405: Method Not Allowed
[12:30:24.104355]<cogocogo>And the build is listed as "in progress" over at the Trac.