http://wiki.apache.org/couchdb/CI
On Jun 7, 2013, at 11:43 , Noah Slater <[email protected]> wrote: > Ooh, ooh. I just found a link to Jan's Jenkins. Not sure if I am allowed to > share though, so won't link for now. > > Note sure how to read the dashboard. Looks like most of the build nodes are > offline though. > > > On 7 June 2013 10:39, Noah Slater <[email protected]> wrote: > >> Hi, >> >> At the moment, Jan has a Jenkins setup running on one of his machines. >> >> Just searched my mail, Trello, etc for a link to Jan's Jenkins setup, but >> I can't find it. Could someone remind me? (Sorry!) >> >> I'd like to build Jenkins into the release procedure. I see this as a two >> step integration process. >> >> First, we can: >> >> 1. Add a note to check the build status of Jenkins before doing the >> release >> >> Then, after a bit of time, I'd like to: >> >> 2. Grab the release artefacts directly from Jenkins for signing >> >> If we could get to (2), doing a release would be trivial. >> >> So, I have a few questions: >> >> a. What's the status of our current Jenkins setup? Is it ready for (1)? >> >> b. How long before we can get to (2)? >> >> c. What's blocking the move to the ASF-run Jenkins? >> >> For (c), I recently found out that we have some OS X Jenkins nodes >> available to us at the ASF. We can also spin up any flavour of Linux that >> we feel like. So it seems like there should be no blockers here except time. >> >> This would be an *excellent* project for someone who's interested in >> improving our QA. And would be massively valuable to the project. (Though, >> maybe I am a bit biased here as one of the primary "customers" of the >> project. Hehe.) >> >> Thanks! >> >> >> On 7 June 2013 10:30, Noah Slater <[email protected]> wrote: >> >>> Awesome! Thanks Jan & Joan! >>> >>> Okay, next step for me is figuring out how to check the build before a >>> release is done. >>> >>> Is that Jenkins setup still working? Lemme see if I can figure that out. >>> >>> >>> On 5 June 2013 21:20, Jan Lehnardt <[email protected]> wrote: >>> >>>> >>>> On Jun 5, 2013, at 22:18 , Wendall Cada <[email protected]> wrote: >>>> >>>>> Awesome, thanks Jan. Simple fix. >>>> >>>> FWIW, the correct fix is to create a fixture specifically for this test >>>> and use that than a random file from the source tree that we don’t have >>>> any awareness of that it is used in a test case. >>>> >>>> Should be easy if anyone wants to send that in :) >>>> >>>> Best >>>> Jan >>>> -- >>>> >>>> >>>> >>>> >>>>> >>>>> Wendall >>>>> >>>>> On 06/05/2013 01:06 PM, Jan Lehnardt wrote: >>>>>> Fixed. >>>>>> >>>>>> 257fc5c..86d756a 1.3.x -> 1.3.x >>>>>> df23be9..e78ce41 master -> master >>>>>> >>>>>> This was a fun one. Thanks Wohali for helping to track this one down! >>>>>> >>>>>> Jan >>>>>> -- >>>>>> >>>>>> On Jun 4, 2013, at 13:53 , Noah Slater <[email protected]> wrote: >>>>>> >>>>>>> Wendall, any update on this? I'd rather rip the test out that wait >>>> any >>>>>>> longer, I think. >>>>>>> >>>>>>> (We're a week behind schedule at this point. Not sure how to handle >>>> this >>>>>>> sort of thing in the general case. Perhaps after X many days, we say >>>> we >>>>>>> missed the window, and just wait for the next one. Which is now >>>> three weeks >>>>>>> away!) >>>>>>> >>>>>>> >>>>>>> On 31 May 2013 16:38, Noah Slater <[email protected]> wrote: >>>>>>> >>>>>>>> Woop woop! Thanks Wendall. :D >>>>>>>> >>>>>>>> >>>>>>>> On 31 May 2013 16:34, Dirkjan Ochtman <[email protected]> wrote: >>>>>>>> >>>>>>>>> On Fri, May 31, 2013 at 5:24 PM, Wendall Cada <[email protected] >>>>> >>>>>>>>> wrote: >>>>>>>>>> I'm limited on time today, but I'll spend some time testing and >>>> evaluate >>>>>>>>>> over the weekend. Do we have a ticket for this? >>>>>>>>> Awesome! COUCHDB-1711. >>>>>>>>> >>>>>>>>> BTW: I'll be mostly AFK for the next week. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> >>>>>>>>> Dirkjan >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> NS >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> NS >>>>> >>>> >>>> >>> >>> >>> -- >>> NS >>> >> >> >> >> -- >> NS >> > > > > -- > NS
