mordred | done | 00:01 |
---|---|---|
mordred | krotscheck: http://status.openstack.org/reviews/ | 00:03 |
mordred | krotscheck: that's 'reviewday' - which creates lists of reviews people should look at based on the combo of bug importance and some other stuff | 00:03 |
krotscheck | That list is generated once a day though, right? | 00:05 |
krotscheck | clark mentioned that it's a static page. | 00:05 |
pleia2 | krotscheck: every 15 minutes | 00:07 |
pleia2 | err, 30 :) | 00:08 |
mordred | yeah. cron job | 00:08 |
krotscheck | Is the API stable enough to query that ad-hoc? | 00:09 |
krotscheck | Or is that going to crash gerritt? | 00:09 |
mordred | you are not likely to crash gerrit - but we're not running a version with a rest api yet | 00:13 |
krotscheck | Cool. Does the API support CORS, or do we have to proxy the API requests? | 00:14 |
krotscheck | Actually, how about we just answer that when we upgrade. | 00:15 |
krotscheck | Ok, I think I finally have all the silly pieces in place for storyboard-webclient. | 01:21 |
krotscheck | Hrm. Build failed on gate-config-layout :/ | 01:58 |
*** krotscheck has quit IRC | 02:02 | |
*** drdee has joined #storyboard | 10:43 | |
*** drdee has quit IRC | 11:45 | |
* ttx wonders if we shouldn't provide IRC-Proxy-aaS | 12:23 | |
ttx | hard to have a discussion on IRC with someone that is too far away TZ-wise and not using proxy | 12:24 |
*** ruhe has joined #storyboard | 15:12 | |
mordred | ttx: ++ | 15:41 |
*** drdee has joined #storyboard | 16:12 | |
*** ruhe has quit IRC | 16:35 | |
*** krotscheck has joined #storyboard | 17:34 | |
krotscheck | mordred: Thanks for that patch this morning. I'll ping clark about having jenkins pick up the cobertura and junit output | 17:39 |
*** ruhe has joined #storyboard | 17:39 | |
*** drdee has quit IRC | 17:47 | |
*** ruhe is now known as _ruhe | 17:57 | |
*** _ruhe is now known as ruhe | 18:13 | |
*** ruhe is now known as _ruhe | 18:28 | |
*** _ruhe is now known as ruhe | 18:33 | |
*** drdee has joined #storyboard | 18:49 | |
ruhe | krotscheck: re https://review.openstack.org/#/c/64761 | 19:09 |
ruhe | ./bin/bootstrap.sh expects some packages to be pre-installed | 19:10 |
ruhe | do you expect jenkins slave nodes to have these packages installed? | 19:10 |
krotscheck | ruhe: That was my assumption. Incorrect assumption? | 19:12 |
ruhe | i'd clarify that with infra folks (if you didn't do so before) | 19:13 |
krotscheck | Just did. Thanks for pointing that out. | 19:16 |
krotscheck | Done :) | 19:17 |
ruhe | thank you | 19:17 |
ruhe | i've just launched ./bin/build.sh and got these errors: | 19:27 |
ruhe | ERROR [launcher]: Cannot start Firefox | 19:28 |
ruhe | ERROR [launcher]: Cannot start PhantomJS | 19:28 |
krotscheck | Huhn. | 19:30 |
krotscheck | What're your system specs? | 19:30 |
ruhe | it's ubuntu 12.04 cloud image | 19:31 |
ruhe | i'm trying to replicate the same environment where unit-tests for this project will run | 19:31 |
krotscheck | Odd. So, PhantomJS should have been packaged into .local | 19:31 |
krotscheck | And clark assured me that firefox was installed. Let me set up a VM and mirror what you're doing... | 19:33 |
ruhe | i have phantomjs in ./node_modules/karma-phantomjs-launcher/node_modules/phantomjs/bin/phantomjs | 19:33 |
krotscheck | Ok, so something else is borked. | 19:34 |
krotscheck | You can run the karma tests directly via ./node_modules/.bin/karma ./karma-unit.conf.js | 19:34 |
krotscheck | It'll take me a bit to set up a jenkins slave. | 19:34 |
ruhe | yeah, firefox should be installed. it's my fault | 19:35 |
krotscheck | (Well, I should have probably done this testing anyway, so I'm just going to do this slave thingie for future use...) | 19:36 |
krotscheck | Thanks for sanity checking my work btw. | 19:36 |
ruhe | that's a good way to learn how things work :) | 19:36 |
krotscheck | ...but after lunch. I'm off to go ring shopping with the soon-to-be-missus :) | 19:39 |
ruhe | wow, good luck :) | 19:40 |
krotscheck | And I'm back! | 21:11 |
ruhe | krotscheck: i'm still waiting on clean repo setup. i want to install exactly the same software and then run UT for your PoC project | 21:13 |
ruhe | *clean repro setup | 21:13 |
*** krotscheck_ has joined #storyboard | 21:14 | |
ruhe | i didn't expect slave nodes to have so many packages installed. there are 4 different jdk's installed | 21:14 |
*** krotscheck_ has quit IRC | 21:14 | |
krotscheck | Right - I've just gotten a cloud image instance up and running, now I'm going to figure out how to setup config and get the puppet script to run. | 21:15 |
ruhe | you can clone from git://git.openstack.org/openstack-infra/config | 21:16 |
ruhe | and... | 21:16 |
ruhe | run prepare_node_bare.sh from ./modules/openstack_project/files/nodepool/scripts/ | 21:16 |
krotscheck | ...install_jenkins_slave is not the right one? | 21:18 |
ruhe | yeah. it seems to do the same thing | 21:19 |
* krotscheck is hurrying up and waiting for the script to finish | 21:22 | |
krotscheck | Invalid database user fail | 21:27 |
ruhe | postgres user? | 21:28 |
krotscheck | No, it's trying to load the default mysql account_security.pp | 21:32 |
krotscheck | Going to ping clark | 21:33 |
ruhe | krotscheck: i didn't have such errors | 21:45 |
ruhe | and after installation completed i've cloned storyboard-webclient, ran ./bin/bootstrap.sh and ./bin/build.sh | 21:46 |
ruhe | and the result is "Done, without errors." :) | 21:46 |
krotscheck | Oh. | 21:48 |
krotscheck | Well then. | 21:48 |
krotscheck | Can you do me a favor and take a peek inside of /cover and /reports? | 21:48 |
krotscheck | (Actually, that's fucking fantastic, because it means we've got selenium, unit, and integration tests running) | 21:49 |
krotscheck | (headlessly. It's a magical snowflake) | 21:49 |
*** drdee has quit IRC | 21:50 | |
krotscheck | ruhe: Where did you spin up the instance? I'm juggling cloud images via virtualbox. | 21:51 |
krotscheck | (And not having much luck) | 21:51 |
ruhe | i have actual OpenStack installation | 21:51 |
ruhe | both /cover and /reports have reports generated | 21:52 |
ruhe | so, everything seems to work correctly | 21:52 |
krotscheck | Cool. Now I need to figure out how to get storyboard.openstack.org set up. | 21:54 |
ruhe | krotscheck: s.o.o should run storyboard REST service and statically serve storyboard-webclient/dist ? | 22:02 |
krotscheck | ruhe: For now, yeah, that's the assumption. | 22:09 |
krotscheck | There's actually three pieces there. | 22:09 |
krotscheck | One, which is a non-storyboard-specific wgsi module that listens to crawler requests and hands back crawlable HTML. | 22:09 |
krotscheck | Two, the static storyboard client. | 22:09 |
krotscheck | Three. The actual API | 22:09 |
*** SergeyLukjanov has joined #storyboard | 22:10 | |
krotscheck | Khai just pointed me at the various project manifest files. Seems like I need to learn puppet. | 22:10 |
krotscheck | Yet another new skill needed for new job. Wooooo! | 22:10 |
ruhe | i'd be happy to help with that | 22:12 |
krotscheck | Sure! As long as you mansplain it to me as we go :) | 22:12 |
krotscheck | So, first thing I've got is manifest/site.pp with a new domain entry | 22:13 |
krotscheck | Actually, should I wrap this into my original patch, or create a new one with a dependency? | 22:14 |
ruhe | I'd create a separate patch | 22:15 |
krotscheck | Got it. | 22:16 |
krotscheck | ruhe: Looking at static.pp, it seems like the convention for hosted static files is "/src/static/subdomain", is that right? | 22:27 |
krotscheck | I'm pondering the options for getting the build-generated artifacts onto the server. We could build it from scratch, or wrap a tarball... | 22:27 |
krotscheck | The latter being more of a maven-esque way of handling it. | 22:28 |
krotscheck | While the former seems to be more package-maintainer friendly (ensuring that the software can be built on the hosting platform) | 22:28 |
krotscheck | From my conversations with jeblair methinks the latter approach is more openstacky | 22:28 |
ruhe | yeah, i like tarball option. since we intend to build on ubuntu-12.04 we might run production on ubuntu-12.04 too | 22:29 |
krotscheck | Oh? | 22:29 |
krotscheck | Huhn. Allrightey, tarball option it is. | 22:29 |
krotscheck | So how about I switch back to the build patch and make the build give me a tarball first. | 22:29 |
ruhe | you alread have tarball-site: tarballs.openstack.org in projects.yaml, but i'm not sure if it's enough | 22:31 |
krotscheck | I don't think so, that's just a configuration flag | 22:33 |
krotscheck | s/flag/parameter/ | 22:33 |
krotscheck | I think i have to invoke something like the tarball macro, but it's python specific. | 22:33 |
krotscheck | While I like the idea of adding a ./bin/package.sh script, I feel that the actual choice of what gets tarballed should be in the builder config. | 22:35 |
ruhe | so, the way other projects get tarballs from master branch is they use template '{name}-branch-tarball' (see python-jobs.yaml) | 22:42 |
ruhe | with a small modification in the build script you'll get desired result | 22:43 |
krotscheck | Is that what all the 'post/pre-release/release' sections are all about? | 22:51 |
ruhe | yes. but as you already said this macros is currently python-job specific | 22:52 |
krotscheck | Is there a place where the various zuul states are listed? I'm not finding the difference between check, gate, post, pre-release, and release. | 23:03 |
ruhe | this page should help http://ci.openstack.org/zuul/zuul.html#configuration | 23:04 |
ruhe | krotscheck: something like http://paste.openstack.org/show/60006/ should get the job done | 23:17 |
krotscheck | ruhe: Awesome, thanks. | 23:19 |
krotscheck | Almost exactly what I had, but I got hung up setting up the pipeline triggers. | 23:19 |
ruhe | it seems i forgot the most important step - to build static files :) | 23:19 |
krotscheck | Right. Exactly :) | 23:21 |
krotscheck | So, in the layout- the various jobs are run in order? | 23:21 |
krotscheck | Are they scrubbed out between every step? | 23:21 |
krotscheck | (so, if I do this http://paste.openstack.org/show/60010/) | 23:22 |
krotscheck | Will the /dist/ directory be there, or do I have to rebuild? | 23:22 |
ruhe | i'm not 100% sure, but i think that you need to rebuild in each job | 23:23 |
ruhe | so, you'll need to build in storyboard-webclient-branch-tarball | 23:24 |
krotscheck | That makes sense. | 23:24 |
ruhe | that's what they do in python jobs '{name}-branch-tarball'. it has builders: [tarball, shell]. | 23:25 |
*** SergeyLukjanov has quit IRC | 23:26 | |
ruhe | krotscheck: what would you say if i start working on puppet modules for storyboard.openstack.org while you're dealing with getting webclient built and published? | 23:34 |
krotscheck | ruhe: Go for it | 23:34 |
krotscheck | You're probably going to be faster at this. | 23:34 |
krotscheck | Also, I have a wedding website that I need to continually hit refresh on until the mysql server connects. | 23:35 |
ruhe | ok :) | 23:35 |
ruhe | you should automate wedding website thing | 23:35 |
*** ruhe is now known as _ruhe | 23:44 | |
krotscheck | Ok, so that's the changes I made. | 23:52 |
krotscheck | I think that wraps it up for the storyboard project mode. | 23:52 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!