| *** krotscheck has joined #storyboard | 03:30 | |
| *** krotscheck_dcm has quit IRC | 03:32 | |
| *** yarkot_ has joined #storyboard | 03:51 | |
| *** yarkot_ has quit IRC | 03:53 | |
| *** mrmartin has joined #storyboard | 07:16 | |
| *** mrmartin has quit IRC | 07:32 | |
| *** jtomasek has joined #storyboard | 07:40 | |
| *** fay has joined #storyboard | 07:48 | |
| *** fay is now known as faybrocklebank | 07:48 | |
| *** mrmartin has joined #storyboard | 09:18 | |
| Zara | morning, storyboard! | 09:30 |
|---|---|---|
| Zara | I've pinged anteaya in #infra so we can talk about integrating storyboard with gerrit, though she's on holiday from tomorrow 'til the 11th. So once she's about, I'm going to make the most of that time; there might be a delay for me replying to other things | 09:34 |
| *** mrmartin has quit IRC | 09:36 | |
| *** alexismonville has joined #storyboard | 09:59 | |
| Zara | I'm also too tired to concentrate today, so sorry about that. :/ | 10:31 |
| openstackgerrit | Beth Elwell proposed openstack-infra/storyboard-webclient: Added comments to dashboard.html https://review.openstack.org/299856 | 11:03 |
| betherly | Zara: pushed one tiny change to dashboard.html re comments | 11:04 |
| betherly | decided to change my development approach to storyboard and so trying to access code changes between mac and ubuntu vm | 11:05 |
| betherly | this could be fun | 11:05 |
| betherly | also, Zara totally know that feeling | 11:05 |
| Zara | oooh | 11:06 |
| Zara | I'll take a look, thanks! :D | 11:08 |
| Zara | ah, nice, never been sure of commenting conventions for html | 11:08 |
| betherly | Zara: its just easier to look at when im editing so thought would push up that as a start | 11:19 |
| *** mrmartin has joined #storyboard | 11:34 | |
| Zara | :) | 11:36 |
| Zara | hm http://doc.gitlab.com/ce/system_hooks/system_hooks.html | 11:43 |
| Zara | that... seems very basic. there's nothing about task status? | 11:44 |
| Zara | ah, http://doc.gitlab.com/ce/integration/external-issue-tracker.html | 11:46 |
| pedroalvarez | Zara: so, the way it's implemented for jira, is something that is already integrated in gitlab, not something running externally | 11:53 |
| Zara | at a glance there, they make a jira user that's 'gitlab', and then give it permissions to change things in a project in jira. then they have a gitlab project and they add a service for that, like http://doc.gitlab.com/ce/project_services/services_templates.html , with the relevant auth | 12:12 |
| Zara | and then maybe things are automatic? | 12:12 |
| Zara | so the issue there seems to be that it doesn't track very much. http://doc.gitlab.com/ce/project_services/jira.html#configuring-jira | 12:14 |
| Zara | so imo the suggested gitlab integration path is a really bad fit for any external issue tracker, as it pushes its own model of issues onto the external issue tracker | 12:21 |
| Zara | which kinda negates a bunch of the benefits of using an external issue tracker | 12:21 |
| Zara | the examples lets you say, in gitlab, 'I'm talking about this issue in my issue tracker' | 12:23 |
| Zara | and they let you say, in your issue tracker, 'this issue is now closed' when it closes in gitlab | 12:24 |
| Zara | and that's it | 12:24 |
| Zara | there's no integration with build status, review status, etc | 12:24 |
| persia | "review status" is a tricky thing in a pull-request model | 12:24 |
| Zara | yeah. and the first example is something you can do manually anyway with minimal effort. | 12:25 |
| persia | I'm not sure what "build status" means: do you mean some CI integration? | 12:25 |
| Zara | yeah | 12:25 |
| persia | Given the Storyboard model, I don't think there's any meaningful difference between "A change is available for consideration" and "a change is available for consideration and some automation ran some tests and delivered an opinion" | 12:29 |
| persia | Unless I misunderstand, the only bits you need to capture are 1) was a change proposed that relates to a task? and 2) Was such a proposed change merged? | 12:30 |
| persia | Each of these ought be a safe boolean (or, better, a positive signal on occurance and inactivity on non-occurance) | 12:31 |
| Zara | so the gitlab model doesn't include tasks aiui. it talks about everything in terms of issues, which would map to storeis. | 12:37 |
| persia | Forcing one task per story? | 12:39 |
| Zara | well, it assumes you have a project containing issues. | 12:39 |
| persia | So no cross-project issues? | 12:39 |
| Zara | so you either map that in terms of project= story, issue=task; or project=project issue=task; or project=project, issue=story | 12:40 |
| Zara | so it seems like the best fit conceptually is the last one, but stories are only tied to projects via tasks. | 12:41 |
| Zara | and there's nothing to represent that | 12:42 |
| Zara | idk I'm very tired today, which doesn't help | 12:42 |
| Zara | all you'll get from the last one is 'story created, story changed', aiui | 12:42 |
| Zara | (I'm still looking at the example fields here: http://doc.gitlab.com/ce/project_services/jira.html#configuring-jira) | 12:43 |
| Zara | I'm not yet sure how much is mandated by gitlab and how much is just that service | 12:45 |
| persia | JIRA has it's own model, etc. | 12:47 |
| persia | Would it be possible to have a mapping as "project=project" and "issue=task"? | 12:47 |
| persia | This means gitlab can't operate on stories, but perhaps that is fine. | 12:47 |
| * persia may be entirely misunderstanding the problem | 12:49 | |
| Zara | so the issue there is that a task isn't a bug report, and people want this as a proof-of-concept of gitlab integrating with a bugtracker | 12:52 |
| Zara | a story can be used as a bug report. | 12:52 |
| persia | Oh my. I didn't understand the problem. Good luck with that. Advanced semiotics may be required. | 12:54 |
| Zara | yeah, roughly my view is that we could get something working, I think it would be worthless both as a proof of concept and as a thing in itself. | 13:16 |
| Zara | urghhh, sorry I'm so tired today. can't concentrate at all. | 14:12 |
| Zara | huh... the column for 'stories created by me' is going off the page on my test instance. when did that happen. | 14:17 |
| Zara | ohhh, nvm | 14:17 |
| Zara | it's because I have a story in there with a massive title | 14:18 |
| Zara | that's a bug, but not one users will encounter a lot | 14:18 |
| Zara | pedroalvarez: btw, meant to ask a while back; you mentioned wanting a gerritbot for baserock; is there a reason baserock were unable to set up their own instance of gerritbot? just a lack of time? (I'm referring to this thing, http://docs.openstack.org/infra/system-config/irc.html#gerritbot , so that's totally separate to the stuff about updating storyboard based on gerrit etc ) | 14:27 |
| Zara | just remembered it since I'm on the bots page now | 14:27 |
| pedroalvarez | well, I tried to install it and run it, but it didn't work | 14:28 |
| pedroalvarez | no error, no output, just not working :/ | 14:28 |
| pedroalvarez | and tried to debug it a bit, but it uses pyton-daemon making it difficult to debug.. | 14:29 |
| pedroalvarez | s/pyton/python | 14:29 |
| Zara | ah, I see there's separate config stuff and puppet stuff? | 14:30 |
| Zara | https://git.openstack.org/cgit/openstack-infra/puppet-gerritbot/tree/ and https://git.openstack.org/cgit/openstack-infra/project-config/tree/gerritbot/channels.yaml | 14:30 |
| Zara | I don't know how generalisable any of that is... | 14:30 |
| pedroalvarez | one to install gerritbot, another one to configure it, as in storyboard too | 14:31 |
| Zara | yeah, idk how much would need to be changed there for baserock :/ | 14:31 |
| pedroalvarez | yeah, I had a look at those first, I think I wasn't missing anything. I was expecting it to be a day-work | 14:31 |
| pedroalvarez | but no logging output from gerrit bot made it impossible for me to debug :.( | 14:32 |
| Zara | I wonder if the author(s) could shed some light on that at some point; I feel like they must have some way of debugging it. | 14:33 |
| Zara | anyway, I'm not looking at that... I'm looking at this! https://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/update_bug.py | 14:35 |
| Zara | straight away, I see from launchpadlib import launchpad | 14:35 |
| Zara | from launchpadlib import uris | 14:35 |
| Zara | so am wondering, is python-storyboardclient the equivalent of launchpadlib there? | 14:35 |
| * anteaya witnesses Zara waffling | 14:38 | |
| Zara | hi! :D | 14:38 |
| anteaya | hi | 14:38 |
| Zara | relevant waffling only starts at 15:35 | 14:39 |
| anteaya | I'll be in and out do to mopping | 14:39 |
| Zara | :( | 14:39 |
| anteaya | thanks :) | 14:39 |
| anteaya | yeah fact of life, water 'tis wet | 14:39 |
| Zara | I hope that's the last of it, at least :( | 14:39 |
| anteaya | nope | 14:39 |
| Zara | D: | 14:39 |
| anteaya | yeah, so you were waffling? | 14:39 |
| Zara | yes! | 14:39 |
| Zara | 15:35 < Zara> anyway, I'm not looking at that... I'm looking at this! | 14:40 |
| Zara | https://git.openstack.org/cgit/openstack-infra/jeepyb/tree/jeepyb/cmd/update_bug.py | 14:40 |
| Zara | 15:35 < Zara> straight away, I see from launchpadlib import launchpad | 14:40 |
| Zara | 15:35 < Zara> from launchpadlib import uris | 14:40 |
| Zara | was as far as I had gotten | 14:40 |
| Zara | 15:35 < Zara> so am wondering, is python-storyboardclient the equivalent of launchpadlib there? | 14:40 |
| anteaya | yup, saw that in backscroll | 14:40 |
| anteaya | I can witness, I don't know the answers | 14:40 |
| anteaya | but you do ask good questions | 14:40 |
| Zara | \o/ | 14:40 |
| Zara | I suppose my next question should be: who wrote that update_bug.py (and the things around it)? | 14:41 |
| anteaya | I think you found the right file | 14:41 |
| Zara | my other question was 'why did zaro want to deprecate jeepyb, and why didn't that happen?' | 14:41 |
| anteaya | there is the log for that file: https://git.openstack.org/cgit/openstack-infra/jeepyb/log/jeepyb/cmd/update_bug.py | 14:41 |
| Zara | aha, thank you | 14:42 |
| anteaya | welcome | 14:42 |
| anteaya | what leads you to the conclusion zaro wanted to deprecate jeepyb? | 14:42 |
| anteaya | I'm not saying your wrong, I'm saying this is news to me | 14:43 |
| anteaya | have to go mop, will read when I return | 14:43 |
| anteaya | hold my cat? | 14:43 |
| Zara | zaro's comments here: https://storyboard.openstack.org/#!/story/2000012 | 14:43 |
| Zara | I assume that's a canadian idiom? | 14:44 |
| Zara | and interesting; https://git.openstack.org/cgit/openstack-infra/jeepyb/commit/jeepyb/cmd/update_bug.py?id=959a8a52e47a32f36de68a5aba5a1c00471815d5 suggests some work was done to plan around storyboard | 14:45 |
| persia | launchpadlib is like, and entirely unlike storyboard-client. Like in the sense of being a python library for local representation of a service API. Unlike in the sense of being differently organised and covering a different scope. | 14:47 |
| Zara | I'm only interested here in if I can import it in a similar way to use here, or if there's something else I should be importing instead | 14:48 |
| Zara | to use the python client, a script has to be written that imports it and initialises it with data from a specific storyboard instance, so I assume that that would have to be in a different config files somewhere, if that's the right approach | 14:49 |
| persia | That sounds roughly right. | 14:50 |
| *** mrmartin has quit IRC | 15:09 | |
| anteaya | Zara: okay I don't know as anyone else know khai felt this way | 15:16 |
| anteaya | Zara: if you want to follow up with zaro that would be my suggestion | 15:16 |
| anteaya | the gerrit upstream patch he linked to has merged | 15:16 |
| Zara | yeah, as I understand it it was able to update comments, and then the second half still needed doing (update task status). pedroalvarez investigated how well the tool worked atm, so... hi pedro! am I right in thinking the patch works and gerrit is capable of updating sb comments, but nothing else? or have I imagined that? | 15:18 |
| Zara | I think the blocker on this end for extending that plugin is that we don't really know java or the ecosystem around gerrit in any depth. | 15:20 |
| pedroalvarez | I take we are talking about the its-storyboard plugin here right? I never tested it, but looked through the code and it looked like it should work | 15:20 |
| pedroalvarez | just to post some comments | 15:20 |
| Zara | ohhh, I thought you tested it! | 15:20 |
| Zara | xD | 15:20 |
| Zara | yes, that's the one | 15:21 |
| anteaya | i also don't know java | 15:23 |
| pedroalvarez | well, tested that it builds, and given that they all use its-base code, I assumed that it works | 15:23 |
| anteaya | i think is time you got to know zaro if you don't already | 15:23 |
| Zara | we chatted a bit at summit, only a little since | 15:24 |
| Zara | every couple of months he gets a ping about that plugin, haha | 15:24 |
| anteaya | well I think it is time you launched yourself into the -infra channel in search of him and have a good chat about current status | 15:25 |
| anteaya | he usually is online in about 30 minutes to 90 minutes from now | 15:25 |
| Zara | pedroalvarez: I go by 'if I haven't personally tested it, it's broken', but I'm a pessimist. :P | 15:25 |
| anteaya | a realist | 15:25 |
| anteaya | <-- vacuuming water | 15:25 |
| pedroalvarez | Zara: yeah, in this case I think it's possible to assume that it's not really broken | 15:25 |
| Zara | anteaya: okay, will do, though I'm not sure I have anything new to add from last time. He said he wasn't motivated to continue it, and the first bit was merged. well, I guess I can check the original motivation for wanting to deprecrate jeepyb. | 15:27 |
| Zara | and if that still applies | 15:27 |
| Zara | pedroalvarez: okay, what's blocking integrating the work so far on storyboard.baserock.org? just a lack of time? | 15:28 |
| Zara | (that's fine, btw, I'm just trying to work out how much there's left to implement) | 15:29 |
| Zara | (so knowing whether it's a case of 'nobody has time to set this up' or 'there's not yet something that's ready to set up' is useful to me) | 15:30 |
| pedroalvarez | Zara: to integrate it so that it does what it does? or also to make it do what we want it to do? | 15:30 |
| Zara | so that it does what it does | 15:30 |
| Zara | I'd imagine 'java, nooooooo' + no time is the blocker for making it do what we want it to do. | 15:30 |
| pedroalvarez | nah, java is not a blocker for me | 15:31 |
| pedroalvarez | :) | 15:31 |
| Zara | oh, okay, good to know | 15:31 |
| Zara | total blocker for me, lol | 15:31 |
| pedroalvarez | so right we need: | 15:31 |
| pedroalvarez | 1) way to create automation users in storyboard. | 15:32 |
| pedroalvarez | 2) Convince -infra of including the its-plugin in Openstack's gerrit | 15:33 |
| pedroalvarez | s/its-plugin/its-storyboard plugin/ | 15:33 |
| pedroalvarez | and of course, test first that it works :) | 15:34 |
| pedroalvarez | I think that will be it | 15:34 |
| anteaya | well if zaro isn't motivated to continue, having him add a comment to the story saying so is helpful | 15:34 |
| anteaya | then if you go a different direction you have evidence that this is the only direciton left open to you | 15:35 |
| pedroalvarez | anteaya: how likely is that #infra adds this plugin to Openstack's gerrit? | 15:37 |
| pedroalvarez | (once we prove it's useful, of course) | 15:38 |
| pedroalvarez | I was kind of expecting that waiting for infra to take a decision to include it or not may take a while.. | 15:40 |
| anteaya | well infra won't make a decision until a plugin exists and is tested | 15:41 |
| anteaya | once it exists and is tested and someone can share the testing data then we can have a conversation | 15:41 |
| anteaya | infra is supportive of storyboard succeeding as an application | 15:42 |
| anteaya | and having the ability to tie into gerrit is useful for storyboard's users | 15:42 |
| anteaya | however | 15:42 |
| anteaya | until we have data from tests that have run | 15:42 |
| anteaya | any conversation it academic really | 15:42 |
| anteaya | as we can't make a plan for implimenting it | 15:43 |
| anteaya | pedroalvarez: does that make sense? | 15:43 |
| pedroalvarez | it does | 15:43 |
| Zara | so it seems like the first step for any approach, gerrit plugin or not, is to have a way to create a storyboard user whose activities are automated, as pedro brought up for 1) | 15:45 |
| anteaya | wonderful | 15:45 |
| Zara | so I guess now I'm wondering, how far does storyboard allow that currently? what, if anything, is missing for that? | 15:46 |
| anteaya | automation users, do you mean a bot? | 15:46 |
| pedroalvarez | so, this plugin, or whatever that is going to modify storyboard (adding comments, or changing task statuts) needs some credentials, right? | 15:46 |
| anteaya | if you use the rest api | 15:47 |
| pedroalvarez | hmm... | 15:47 |
| Zara | yeah. so far, python-storyboardclient allows you to submit some, haven't tested that yet (only done GETs) | 15:47 |
| anteaya | it needs an account on gerrit yes, so it can create itself an http password | 15:47 |
| Zara | so on the storyboard side, you could write a script that imports python-storyboardclient, feeds it some agreed upon credentials, and then does whatever based on the info it gets from gerrit (how it gets it, I don't know. how exactly it's written, I don't know) | 15:48 |
| pedroalvarez | Zara: exacatly, using gerrit stream-events would be an option | 15:49 |
| pedroalvarez | of a python library for it if there is already on | 15:50 |
| pedroalvarez | e | 15:50 |
| pedroalvarez | s/of/or/ | 15:50 |
| Zara | that's where I know absolutely nothing about gerrit stream events | 15:51 |
| Zara | I assume they get interacted with somehow by jeepyb things | 15:53 |
| anteaya | run the following command | 15:53 |
| anteaya | ssh -p 29418 -l anteaya review.openstack.org gerrit stream-events | 15:53 |
| anteaya | replace my username with yours | 15:53 |
| anteaya | the output is stream events | 15:54 |
| anteaya | there will be a lot | 15:54 |
| Zara | I see 'em | 15:54 |
| pedroalvarez | wow! didn't expect everyone to be allowed to see openstack stream-events! | 15:54 |
| anteaya | yes | 15:58 |
| anteaya | we can close it or open it | 15:58 |
| anteaya | rather than closing and having folks ask permission we just opened it | 15:58 |
| anteaya | it has its drawback | 15:59 |
| anteaya | s | 15:59 |
| anteaya | so read this: http://docs.openstack.org/infra/system-config/third_party.html | 15:59 |
| anteaya | and I'm going to suggest the name Storyboard Bot as a gerrit account name | 15:59 |
| pedroalvarez | :) | 16:00 |
| anteaya | I think the docs I just linked will support me in that suggestion | 16:00 |
| anteaya | but do read them in case I am mis remembering | 16:00 |
| anteaya | <-- water | 16:00 |
| pedroalvarez | I think that a separate service is better than using its-storyboard | 16:00 |
| * Zara reads | 16:08 | |
| *** jtomasek has quit IRC | 16:16 | |
| Zara | okay, so from that, I'm wondering... do we give it a normal reviewer account, or set it up as a third party system? it seems like the latter is designed for different sorts of things to what we want to do (afaict we only want to consume gerrit events, not cause any) | 16:20 |
| pedroalvarez | yup, we don't need to send reviews to gerrit, just consume the stream | 16:23 |
| Zara | yeah, I believe those docs are based around something sending reviews to gerrit, so I'm not sure how applicable they should be. | 16:32 |
| Zara | whatever kind of account it is, I'm fine with Storyboard Bot as an account name, anyway | 16:41 |
| Zara | (add cases or dashes or underscores as necessary) | 16:41 |
| anteaya | a bot account | 16:55 |
| anteaya | in that doc it should use the word bot somewhere | 16:55 |
| anteaya | This value should be CI for most CI systems but can be Bot if you are not performing continuous integration. | 16:55 |
| anteaya | item 2 http://docs.openstack.org/infra/system-config/third_party.html#creating-a-service-account | 16:55 |
| anteaya | so an automation, non human not performing continuous integration | 16:56 |
| anteaya | bot | 16:56 |
| Zara | ah, thanks, sorry, I missed 'This new CI service account needs to use a different email address than any existing accounts you have, because Gerrit assumes email addresses are unique across all accounts.' at first | 17:00 |
| Zara | so step 2) suggests a naming scheme | 17:02 |
| Zara | but that's also very centered around CI systems | 17:02 |
| Zara | ah, there's a mention of bots toward the end | 17:03 |
| Zara | so 'Codethink StoryBoard Bot' seems to be the required name | 17:03 |
| *** b3rnard0 is now known as b3rnard0_away | 17:03 | |
| Zara | but that's getting ahead; seems first step is to make a launchpad acct for it | 17:07 |
| Zara | it needs a different email address; not sure what that should be | 17:07 |
| persia | Probably makes sense to have it aligned with other mail from storyboard. | 17:26 |
| persia | So it can be handled by the storyboard mailserver. | 17:26 |
| persia | I don't remember the details of what was decided for mail, but perhaps something like gerritbot@storyboard.openstack.org? | 17:26 |
| persia | (would be a different address for a different storyboard deployment) | 17:26 |
| anteaya | Zara: zaro is in infra now | 17:32 |
| anteaya | I don't know what the best email is to use with launchpad | 17:33 |
| anteaya | Codethink StoryBoard Bot is fine | 17:34 |
| anteaya | I also think you could do StoryBoard Bot, let's ask in infra | 17:34 |
| anteaya | I'm of the opinion you announce what you want to do and give folks the opportunity to object | 17:36 |
| anteaya | if noone objects, you go ahead | 17:36 |
| *** zara_the_lemur__ has joined #storyboard | 17:43 | |
| persia | +1 on effective strategies to get things done | 17:43 |
| zara_the_lemur__ | I think it was storyboard@storyboard.openstack.org | 17:43 |
| zara_the_lemur__ | and it's one of those things that needs fixing at some point... :D | 17:44 |
| zara_the_lemur__ | for me, the main thing is that we have some kind of access to the account | 17:44 |
| zara_the_lemur__ | if we're going to set it up, verify it etc | 17:45 |
| persia | I'd recommend using different email addresses for different purposes. I thought storyboard@storyboard.openstack.org was the address used to send notices. | 17:46 |
| *** b3rnard0_away is now known as b3rnard0 | 17:47 | |
| zara_the_lemur__ | I think we ended up using that one because it was recognised | 17:48 |
| persia | recognised? | 17:49 |
| -openstackstatus- NOTICE: Job failures for missing traceroute packages are in the process of being fixed now, ETA 30 minutes to effectiveness for new jobs | 17:49 | |
| zara_the_lemur__ | (yeah, it's that.) yeah, exim didn't like no-reply@storyboard.openstack.org because it wasn't a thing | 17:50 |
| zara_the_lemur__ | I think it was exim, anyway. something in the mail world | 17:50 |
| * zara_the_lemur__ knows all the correct terminology | 17:51 | |
| persia | Oh right. Yeah You'd need to create another user on the machine or an alias to use another address. | 17:51 |
| persia | My fear is that using the same address, if there were interesting notices, they might be all mixed up. | 17:51 |
| persia | I may worry too much about these sorts of things. | 17:51 |
| *** mrmartin has joined #storyboard | 17:51 | |
| zara_the_lemur__ | oh, I missed some backscroll | 17:52 |
| zara_the_lemur__ | all anteaya's comments only just came up for me in the logs | 17:52 |
| zara_the_lemur__ | is anyone free to ask? it's actually nearly my 7pm and I'm about to make tea and vanish for the night, unless it can't keep for tomorrow | 17:53 |
| persia | 18:00 UTC is 11:00 PDT, so an excellent time to catch folk before lunch in that timezone. | 17:54 |
| zara_the_lemur__ | :< | 17:54 |
| zara_the_lemur__ | I meant if anyone here was free to ask on my behalf, wahhhhhhhhhhhhhhhhh (not that there's any reason why anyone else should) | 17:55 |
| zara_the_lemur__ | infra suggest using https://launchpad.net/~hudson-openstack | 18:16 |
| zara_the_lemur__ | so I think that's the account we'd want to use | 18:19 |
| anteaya | zara_the_lemur__: I asked about the name | 18:19 |
| zara_the_lemur__ | oh? | 18:20 |
| anteaya | yes fungi said he was fine with StoryBoard Bot | 18:20 |
| anteaya | noone else responded | 18:20 |
| zara_the_lemur__ | \o/ I must have missed that, sorry | 18:20 |
| zara_the_lemur__ | I looked at logs | 18:20 |
| zara_the_lemur__ | didn't see it, probably same way I missed some backscroll in here | 18:21 |
| anteaya | http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-03-31.log.html#t2016-03-31T17:36:39 | 18:21 |
| anteaya | I didn't realize you were changing your nice | 18:21 |
| anteaya | nick | 18:21 |
| anteaya | I highlighted Zara | 18:21 |
| zara_the_lemur__ | ah, yeah, sorry my eyes are just bad, it was in my tab all along... | 18:22 |
| zara_the_lemur__ | I changed nicks because I went home in the middle and started using the web irc portal instead | 18:22 |
| anteaya | ah | 18:22 |
| zara_the_lemur__ | so I also have no access to any messages sent to Zara | 18:22 |
| zara_the_lemur__ | or any channels she's in \o/ | 18:22 |
| anteaya | right | 18:22 |
| anteaya | yup | 18:23 |
| anteaya | the web client doesn't know about such things | 18:23 |
| zara_the_lemur__ | :) anyway, it seems like we can use hudson's credentials in a smallish python script that imports the python storyboardclient, and that script will be Storyboard Bot | 18:24 |
| zara_the_lemur__ | sure there's loads of interaction with gerrit stream events to be done soooooooomehow | 18:25 |
| zara_the_lemur__ | but.... seems straightforward so far... that can't be right :) | 18:25 |
| anteaya | yay | 18:25 |
| anteaya | shhhhhhh | 18:25 |
| anteaya | take what you are given | 18:26 |
| anteaya | and don't make a fuss | 18:26 |
| zara_the_lemur__ | hehehe | 18:26 |
| anteaya | :) | 18:26 |
| zara_the_lemur__ | :) nah, I love that openstack have so much infra set up; thank you all | 18:26 |
| *** mrmartin has quit IRC | 18:27 | |
| *** zara_the_lemur__ has quit IRC | 18:40 | |
| *** zara_the_lemur__ has joined #storyboard | 19:00 | |
| zara_the_lemur__ | I just got an email notification about a story that had a tag! I'm so happy | 19:00 |
| pleia2 | :D | 19:00 |
| zara_the_lemur__ | it was your story, yay! :D | 19:01 |
| pleia2 | I'm excited, added an agenda item to infra meeting on tuesday about starting to use them | 19:01 |
| zara_the_lemur__ | \o/ I'm just relieved the email template told me the correct author! | 19:02 |
| pleia2 | lol | 19:02 |
| zara_the_lemur__ | I hope we don't find any strange bugs with them as time goes on... tags have done some interesting things in the past, round these parts. | 19:02 |
| zara_the_lemur__ | but the only way we'll find anything is if people use it, so | 19:02 |
| pleia2 | exactly | 19:02 |
| pleia2 | woo dogfooding | 19:02 |
| zara_the_lemur__ | :) | 19:02 |
| *** openstackgerrit has quit IRC | 19:03 | |
| zara_the_lemur__ | 'night, all, again. | 19:04 |
| pleia2 | ooh yay, I got email too | 19:04 |
| *** zara_the_lemur__ has quit IRC | 19:04 | |
| *** openstackgerrit has joined #storyboard | 19:04 | |
| *** b3rnard0 is now known as b3rnard0_away | 19:07 | |
| *** mrmartin has joined #storyboard | 19:45 | |
| *** mrmartin has quit IRC | 19:47 | |
| -openstackstatus- NOTICE: Any jobs which erroneously failed on missing traceroute packages should be safe to recheck now | 19:55 | |
| *** mrmartin has joined #storyboard | 20:02 | |
| *** b3rnard0_away is now known as b3rnard0 | 20:52 | |
| *** mrmartin has quit IRC | 21:18 | |
| *** b3rnard0 is now known as b3rnard0_away | 21:47 | |
| *** b3rnard0_away is now known as b3rnard0 | 23:03 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!