02:44
<sr>
bdot, I think heroku is having some issue with pgsql
02:44
<sr>
I belive their working on it
02:53
<sr>
heroku needs a status blog
02:57
<nakajima>
sr: are you having troubles?
02:58
<nakajima>
bea: Thanks
02:58
<nakajima>
I've seen that actually
02:58
<nakajima>
why tell me?
02:58
<sr>
nakajima, no but some of their users are
02:59
<sr>
apparently do_pgsql isn't installed at the system level anymore
02:59
<nakajima>
I just checked my apps, they seem to be ok
02:59
<nakajima>
friggin do
02:59
<sr>
and it isn't possible to compile it
02:59
<sr>
nakajima, I've told her to tell you
02:59
<nakajima>
well yea, I've seen that
03:00
<nakajima>
but it's still activerecord, if that's what you're talking abot
03:00
<sr>
yeah... saw it afterwards
03:02
<nakajima>
did you see github.com/nakajima/gemifest?
03:03
<sr>
yeah, looking at it
03:03
<nakajima>
I'm almost positive I didn't get it right, but it works for what I need right now
03:03
<sr>
I've done it with a bunch of bash aliases
03:04
<sr>
gem list | ruby -e'ARGF.each{|l|next if l=~/LOCAL/ || l=="
03:04
<sr>
";puts l.gsub(/\(.*?\)/, "") }' > gems-list
03:04
<nakajima>
yea, I played with that
03:04
<nakajima>
but the versioning stuff, I just wanted to see if I could do it better than geminstaller
03:04
<sr>
geminstaller... I still don't get it
03:04
<nakajima>
which was sort of the bane of my existence at pivotal
03:05
<nakajima>
I'm at a point where I don't really get the point of YAML anymore
03:05
<sr>
yeah. also, why not just use a gemspec?
03:06
<nakajima>
though I suppose it's nice to have a separation of concerns between application dependencies and library dependencies
03:07
<nakajima>
I think heroku nailed it
03:07
<nakajima>
so I just made a library to make it happen locally
03:08
<sr>
yeah, .gems is just simple
03:09
<nakajima>
I like that
03:09
<nakajima>
I wish rubygems was a viable library. I don't really feel comfortable using any part of rubygems though, since all the useful classes are "private"
03:13
<sr>
huum yeah, weird
03:13
<sr>
and yeah, I tried to use rubyems as a library too; miserabely failed
03:14
<sr>
hopefully the ruby communauty will figure a replacement some day :)
03:15
<nakajima>
about the queued stuff, explain your intent. I'm not quite grasping it (though that
03:15
<nakajima>
s probably because it's 5am here and I've been out out at the blues club)
03:16
<sr>
blues club in NY... must be awesome
03:16
<sr>
basically you give the queue a proc to push a buildable into a queue
03:16
<nakajima>
as opposed to as it comes in?
03:17
<nakajima>
to prevent concurrent builds?
03:17
<sr>
nope, so that you can have a bunch of builders that grab a buildable out of the queue and build it
03:18
<nakajima>
my concern these days is keeping one build at a time, because the server doesn't have much power, and the codebase/test-suite is atrocious. I've seen the server crash because of too many post-commit hook pings
03:18
<nakajima>
but that's just my problem
03:18
<nakajima>
I like the idea
03:19
<sr>
did you try devver?
03:19
<nakajima>
btw, where do you live, where you're awake at this ridiculous hour for me?
03:19
<sr>
brussels, belgium (11:19 am)
03:19
<halorgium>
nakajima, you are crazy
03:19
<nakajima>
halorgium: crazy like a fox
03:19
<nakajima>
I work at 1
03:19
<halorgium>
well, yes
03:20
<halorgium>
but still crazy
03:20
<nakajima>
so if I go to sleep at 6, I can still get *just* enough sleep
03:20
<nakajima>
of course I don't
03:20
<nakajima>
I create zany libraries on the github for my own amusement
03:20
<sr>
well, mine too :)
03:20
<nakajima>
I created one because I used to have a crush on a girl and so I named it after her
03:21
<nakajima>
I recently got past the crush, so I renamed it
03:21
<halorgium>
BALEEETED
03:21
<nakajima>
key-valerie => key-val
03:21
<nakajima>
changed the gemspec and everything
03:21
<halorgium>
nakajima: got a versioned history of love life? :P
03:21
<sr>
nakajima, that new name sucks :P
03:21
<nakajima>
here and there. If you ever visit bleecker st in nyc, you'll probably see it
03:22
<sr>
key-valerie was much more amusing
03:22
<nakajima>
that it was
03:22
<nakajima>
but much weirder once I decided friend > fling
03:22
<nakajima>
some guys write songs about girls, I write code
03:22
<nakajima>
it's much more romantic
03:23
<sr>
I've got to get some school work done
03:23
<sr>
good night/day
03:23
<nakajima>
sr: good day/night
09:20
esquivalient joined
09:47
<qrush>
take a look at your server logs
09:47
<qrush>
thin or apache's, whatever you're using to run integrity
09:47
<kobani>
that's from the logs
09:47
<kobani>
that's integrity's own log (integrity/log.log)
09:52
<kobani>
qrush: that'd do it:
09:52
<kobani>
sh: git: command not found
09:52
<kobani>
Git not in apache's path
09:52
<qrush>
What system are you deploying it on?
09:56
<kobani>
its Apache2 under CentOS
09:56
<kobani>
the Apache user doesn't have a login shell, therefore, doens't have git in its path
09:56
<kobani>
erm, and there's nothing in the config to specify which git to use :\
09:56
<kobani>
(centos 5.2)
09:56
<qrush>
I had a really rough time getting integrity to work with passenger and centos
09:57
<qrush>
I ended up doing exporting path in the build script
09:57
<kobani>
that would work, would it ?
09:57
<qrush>
and appending /usr/local/bin
09:57
<kobani>
in the make script ?
09:57
<kobani>
nice one, thanks - lemme try that
09:59
<kobani>
damn, `git not found` appears in the apache error log before it even tries to run my build scrip :\
09:59
<qrush>
i think i threw in a link for git in somewhere.
09:59
<qrush>
it was just ugly.
10:00
<qrush>
deploying on ubuntu is WAAAAY easier
10:00
<kobani>
yeah, I don't doubt it
10:00
<kobani>
might fork this, and make the path to git optional
10:00
<kobani>
would you consider a patch for that ?
10:00
<qrush>
I'm sure they would. ;)
10:00
<kobani>
ohh yeah, you don't have the keys :)
10:09
<kobani>
yaya, I got an error :)
11:01
esquivalient joined
12:16
<qrush>
How can i get to the build location from a Project instance?
12:18
<sr>
qrush, some method on ProjectBuilder iirc
12:51
<lypanov>
which gem should i be using if i need passenger?
12:51
<lypanov>
i can't figure out how to get email + passenger + integrity (not foka) working
13:13
<lypanov>
foca: guess you're foca, so. odd question. which gem: foca-integrity or integrity?. notification plugins don't seem to love me
13:14
<lypanov>
foca: thought so as your md says such. thx!
13:14
<foca>
some notifiers will force install foca-integrity
13:14
<lypanov>
shall start forking random projects then
13:14
<foca>
so if you see that, uninstall it
13:14
<lypanov>
ah, they Just Work after install?
13:14
<lypanov>
i got really random sinatra exceptions after installing one of the plugins
13:14
<lypanov>
they don't seem to be very well tested
13:15
<sr>
lypanov, which notifier?
13:15
<lypanov>
neither the twitter nor email plugins directly linked to worked out of the box
13:15
<lypanov>
mainly for the above dependency reason though
13:16
<lypanov>
i might have had messed up gems so take the above with a pinch of salt
13:16
<lypanov>
(was my first day of experiencing passenger)
13:16
<lypanov>
maybe the integrity page could better link to one of the working twitter forks
13:17
<lypanov>
(which still fires exceptions sometimes... but at least it doesn't fail everytime)
13:17
<lypanov>
(be9-integrity-twitter to be exact)
13:17
<sr>
integrity-email does work (just make sure you install it from rubyforge)
13:17
<sr>
do not about twitter
13:18
<lypanov>
ah! i used foca-integrity-email. didn't notice a rubyforce one. silly me
13:18
<sr>
where did you read you have to install foca-integrity-email?
13:19
<lypanov>
not sure. just checked the main integrityapp.com and it doesn't link to it
13:20
<* lypanov>
tests the above "sudo gem install integrity-email"
13:21
<sr>
make sure you uninstall any foca- gem. they'll get loaded before rubyforge gem
13:22
<lypanov>
i think issue was that i tried that trick for twitter but it still didn't work. so didn't realize it would
13:22
<lypanov>
thx for the clarification!
13:23
<sr>
foca, that article isn't interesant at all, as far as I can tell :P
13:24
<foca>
yeah, dunno, too many people sent it to me
13:24
<foca>
so maybe I missed something :p
13:57
michaelglass joined
13:57
<michaelglass>
hiya
13:57
<michaelglass>
is it generally adviseable not to use mysql as of right now
13:58
<michaelglass>
and, if that's the case, can someone explain this error message when using sqlite (3.5.9): unable to open database file Query: INSERT INTO "integrity_projects" ("command", "name", "uri", "branch", "updated_at", "created_at", "permalink", "public", "building") VALUES ('rake', 'Consumption Log', 'git@localhost:consumption_log', 'master', '2009-05-20T19:52:54+00:00', '2009-05-20T19:52:54+00:00', 'consumption-log', 't',
14:00
invalidusrname joined
14:02
<invalidusrname>
anyone in here using integrity with heroku? I'm running into this gem problem with do_postgres
14:15
<foca>
invalidusrname: you could also ask in #datamapper, dkubb usually likes to help people out :)
14:16
<invalidusrname>
will do, thanks
14:36
michaelglass joined
14:49
<mileszs>
invalidusrname: when are you getting this error?
14:49
<invalidusrname>
milezs: when I load up integrity
14:52
<mileszs>
This is going to sound like an asshole question: You followed the directions on integrityapp.com?
14:54
<invalidusrname>
yep
14:56
<mileszs>
Weird. I don't know off the top of my head, but I'll play with it and see what I can figure out.
14:58
<leehambley>
hey all, is the config variable available to the SCM module ?
14:58
<invalidusrname>
cool, thanks for looking into it. I'll try the heroku steps again, just to be sure
15:00
<leehambley>
hey sr, sorry to bug you personally, but I know you know the code best of anyone
15:00
<leehambley>
I need to send you guys a patch
15:01
<leehambley>
(right after I write it ;)
15:06
<jnicklas>
I'm trying to install integrity on Heroku (using the bundled config), but I'm getting "no such file to load -- do_postgres". I tried adding do_postgres to the .gems file but it didn't help. Any ideas?
15:06
<mileszs>
As a quick note, thrown into the ether: I'm on a fresh system without the integrity gem (and its dependencies installed). After installing the integrity gem, integrity install throws a "no such file to load -- builder" error.
15:06
<mileszs>
I never know whether I should add these little thigns to Lighthouse.
15:06
<mileszs>
jnicklas: So is invalidusrname. I'm trying to figure it out. I'll let you know if I find anything interesting.
15:07
<jnicklas>
mileszs: thanks :)
15:16
<mileszs>
Well, heroku claims that do_postgres is installed by default. I have no idea why this error is occurring.
15:21
blakemizerany joined
15:21
<nubee>
Greetings. I need some startup help. I have a local git repository on a project, integrity setup and asking for first project, cap deploy working for my deployment server. What should be my deploy script for integrity? ... "cucumber features; cap deploy" ?
15:27
<jnicklas>
mileszs: very odd :S
15:29
<mileszs>
nubee: You don't need to deploy to integrity. You need to tell Integrity where your repository is, via the web interface.
15:29
<mileszs>
Unless I'm completely missing the goal.
15:32
<nubee_>
mileszs. my "cap deploy" is deploying to a separate QA server, not to integrity or my local repo
15:33
<foca>
nubee_: probably you want "cucumber features && cap deploy"
15:33
<foca>
so it only deploys after successfully running the features
15:35
<nubee___>
apologies mileszs. internet was disconnected. My setup is... repo on local machine. QA server on slicehost, integrity on local machine. I want to commit my code on local machine and watch it pass test and get deployed to my slicehost qa server. CI works that way , right?
15:35
<foca>
nubee nubee_ nubee__ nubee___: are you a self-replicating robot that will conquer the world?
15:36
<foca>
yeah, it's a good process
15:37
<foca>
nubee___ what you want is probably "cucumber features && cap deploy"
15:37
<foca>
so deploys are only run after successful builds
15:37
<nubee___>
foca. I dunno. internet connection was disrupted and the alias was created on auto connect again. I am using a GUI app on mac os x called colloquy. Apologies for inconvenience caused.
15:37
<foca>
hahaha, no worries
15:37
<foca>
that way you don't make your QA people work on versions you *know* are broken somehow
15:37
<foca>
I gotta run, be back in a few hours
15:39
<nubee___>
So, do I have any suggestions? anyone please?
15:39
<nubee___>
"get" any suggestion, not "have". :) typo there. Not very good English knowledge.
15:44
<nubee___>
ok, bye. I will see what I can do. Thanks everyone.
17:52
<rtomayko>
sr: ping
18:05
<rtomayko>
^ do_postgres issue research
19:13
<halorgium>
rtomayko: does the .gems support in heroku get used in the gems which are required?
19:13
<halorgium>
or is that separate?
19:14
<rtomayko>
halorgium: can you rephrase the question?
19:14
<halorgium>
sure :P
19:14
<rtomayko>
I can't quite parse that. kinda sleepy :)
19:15
<halorgium>
i can't parse it myself now ;P
19:15
<halorgium>
heroku uses .gems for allowing others to specify gems to install
19:15
<halorgium>
does that feil get used for activating gems for the app?
19:15
<halorgium>
file...
19:16
<halorgium>
bah, 80% loss :(
19:18
<rtomayko>
halorgium: I think I understand.
19:18
<rtomayko>
no, we don't try to require those gems or anything
19:19
<rtomayko>
it's used purely to create a gem repo directory and placed on the GEM_PATH
19:19
<rtomayko>
heroku doesn't inject any code at runtime
19:19
<halorgium>
ok, i've been wanting to get to a point where a project has a "project spec" which describes what deps there are
19:19
<halorgium>
for install, and activation
19:20
<rtomayko>
halorgium: sure, makes sense.
19:20
<halorgium>
there is a big mismatch between that .gems file and the .rb files otherwise
19:20
<rtomayko>
gemspec kinda does that today. *if* you're loaded as a gem.
19:20
<halorgium>
yes, indeed
19:21
<halorgium>
i was thinking that it would be an ancestor of Specification
19:21
<halorgium>
(in the end)
19:21
<rtomayko>
the .gems file is a list of gems to install. how you use them is a totally separate issue today.
19:21
<halorgium>
yes, exactly
19:21
<rtomayko>
halorgium: ahh.
19:24
<rtomayko>
halorgium: peek a boo!
21:52
<foca>
I need some brainstorming: what's the best way to allow plugin developers to extend projects/commits/builds? as far as interface goes it's easy -- just generate html and we can plug it in at certain places, but if you wanted to add a "dependencies" column to your projects table?
21:55
<foca>
probably some sort of schemaless database would be nice
21:55
<foca>
buuuuut that's a huge dependency if it's just meant for plugins
21:56
<foca>
file database? $integrity_root/db/projects/$plugin_name/$project_id
21:57
<foca>
(plus, very slow, probably
21:58
<foca>
just a `text` field for "metadata" where you can save stuff and get it serialized into a hash
21:59
<foca>
not indexable/sortable on the db
21:59
<foca>
but so far I'm inclining for that
21:59
<foca>
if anyone else has suggestions, please ping me :)
21:59
<* halorgium>
lols :P
21:59
<halorgium>
just for you foca :)
21:59
<* foca>
slaps halorgium with a smelly trout
22:00
<halorgium>
are you going with sequel for the rewrite?
22:00
<halorgium>
does it have a Object colum?
22:00
<foca>
I'm trying that, see how it goes
22:01
<foca>
not that I know
22:03
<foca>
OpenStruct.new(JSON.parse(@values["metadata"]))
22:04
<foca>
or just JSON serialization/deserialization and get a hash, if you need better accessor methods, write them in your extension :)
22:09
<foca>
I already have three plugins I want to write, which more or less are guiding me in what stuff should be available to plugins =)
22:10
<foca>
integrity-github: link relevant stuff to the appropriate place in github if the repo is in gh (commit, project, etc, maybe even display the project's description or whatever)
22:10
<foca>
integrity-dependencies: allow defining dependencies for a project so after X builds successfully it triggers builds for W, Y, and Z
22:10
<foca>
errr s/three/two
22:31
<halorgium>
foca: one thing i would say is that having a compartmentalized app would be nice
22:31
<halorgium>
then i could put the API stuff behind a key and the rest behind HTTP auth
23:29
<foca>
halorgium: how do you mean? like multiple rack apps each mounted on top of each other?
23:30
<foca>
or am I missing the point entirely?
23:31
<halorgium>
foca: yes, with a toplevel one for normal use cases
23:31
<foca>
well that's sort of what we're doing with bobette
23:32
<halorgium>
right, i don't know that it needs to be that generic really
23:32
<foca>
extracting the part that handles pushes and triggers builds out
23:32
<foca>
what other part do you think makes sense to split?
23:32
<halorgium>
administration
23:33
<halorgium>
i've been making simple DSLs for configuring the rack app which is spat out at the end
23:33
<halorgium>
so you can inject middleware into certain sets of routes
23:48
<foca>
I'm still looking for good ideas on how to handle per-project auth
23:48
<foca>
so you can have different clients look at different projects
23:48
<halorgium>
yer, i haven't thought about to handle it via rack
23:49
<halorgium>
i think it shouldn't be in the app
23:49
<foca>
you could probably just run a different "integrity frontend" app for each client
23:49
<foca>
kind of bothersome for your team though
23:50
<foca>
since you now have N different places to look for status
23:51
<foca>
so probably just need to build some sort of ACL
23:51
<halorgium>
yes, i was thinking it should be exposed down into a middleware for the authorization
23:52
<foca>
hm, how would the middleware know which projects belong to whom?
23:52
<halorgium>
it wouldn't
23:53
<halorgium>
but your app would tell it
23:53
<foca>
on the way back?
23:53
<halorgium>
either by doing a pre-request into another app API
23:54
<halorgium>
which would be more efficient
23:54
<halorgium>
or on the way back, but don't think that would work
23:54
<foca>
nah, for destructive actions it wouldn't for sure :p
23:54
<foca>
[401, {}, "oh, shit, dude, he wasn't allowed to do that"]
23:55
<halorgium>
[-100, {}, "rewind time, kthx"]