Return-Path: X-Original-To: apmail-groovy-dev-archive@minotaur.apache.org Delivered-To: apmail-groovy-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 196EC18CFB for ; Thu, 22 Oct 2015 05:24:21 +0000 (UTC) Received: (qmail 45738 invoked by uid 500); 22 Oct 2015 05:24:21 -0000 Delivered-To: apmail-groovy-dev-archive@groovy.apache.org Received: (qmail 45686 invoked by uid 500); 22 Oct 2015 05:24:21 -0000 Mailing-List: contact dev-help@groovy.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@groovy.incubator.apache.org Delivered-To: mailing list dev@groovy.incubator.apache.org Received: (qmail 45675 invoked by uid 99); 22 Oct 2015 05:24:20 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Oct 2015 05:24:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 49262C0B1C for ; Thu, 22 Oct 2015 05:24:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=asert_com_au.20150623.gappssmtp.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id f5TVrByUjX_o for ; Thu, 22 Oct 2015 05:24:06 +0000 (UTC) Received: from mail-yk0-f179.google.com (mail-yk0-f179.google.com [209.85.160.179]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 9222E20751 for ; Thu, 22 Oct 2015 05:24:05 +0000 (UTC) Received: by ykba4 with SMTP id a4so66274323ykb.3 for ; Wed, 21 Oct 2015 22:23:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=asert_com_au.20150623.gappssmtp.com; s=20150623; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=BwqwwS3pb9JG1zx/f2/ylcTMBKW1Hw+zDQOQaJIfrC8=; b=NZBGo9KakXRqN5xxrN/9b/CRSJXczc6S96EPOog77CtdPePJqYF0LAPwd52xtzOBps 8aNEvnVH3Y2pumVbiicrafzBuheJrhyeof4YwK76RyBI2UVNZ5M+7nO/RM4sj9s+1ljx rGJC0ORfkv3QZF7t27fSqEXp23c17x+8MyYYT3cMi01pfxKP99EQimLfQclvSjuvBmSe yr7F1FIzxb+AJ++3YETT68H8khRe2akTJghthgEOBhhdS1h5YhKawq65FOq1+A2l/Ome 6xYSqPVGQVMDSFONcezLn1/aYelv/wIwmkEM4iw4nkDRDARGpEkOGrHSSK8aPS4Lt/nq zRUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=BwqwwS3pb9JG1zx/f2/ylcTMBKW1Hw+zDQOQaJIfrC8=; b=N0x4pZO9vrnQTfLiyOjBHdMXpIh8nIz3svQW9uO2vlNeb3iNspXT+idjnSsU4HpYqD Z4pXvQdoA+i4AsD8vhj4D1CZJJ7UOqw/lzN7WNTXi0pCHn02btLWYsk+HsEATUJjAkNg xNUQxuJuC5QRqwAMcP8RK2NvxUJ0+hufkitEAiu899Y+ojSUmEYZ302FiOGOZIn9eWFW 1p9hZOfKdR32r8qts3QDkzzigt498GIogUF7mldMcNUUDsmCZh0/h6tw0M6mQl0I12tN YEj93ZyMJni4Bh9/jusPPWgqmdYXTlqZ0FYk7VW4oQo1y8OEfsxFz/UAfWAtzfZzC5iw inBw== X-Gm-Message-State: ALoCoQkZqbM7sjkHRDCDAqcHYcSmLNZkl2rbHy8QpqEYbwfsHwC+6dUaPP771SFxjS0ecpS/8woc MIME-Version: 1.0 X-Received: by 10.13.245.68 with SMTP id e65mr9706320ywf.264.1445491438280; Wed, 21 Oct 2015 22:23:58 -0700 (PDT) Received: by 10.129.92.198 with HTTP; Wed, 21 Oct 2015 22:23:58 -0700 (PDT) X-Originating-IP: [101.183.18.104] Reply-To: paulk@asert.com.au In-Reply-To: References: <55F537DE.1000704@gmx.net> <562536CC.20508@gmx.net> <56253B23.2050501@gmx.net> <56253DF0.5050206@gmx.net> <56266FD1.3040802@gmx.net> <5627E322.4020601@gmx.net> Date: Thu, 22 Oct 2015 15:23:58 +1000 Message-ID: Subject: Re: [mentors] access to https://builds.apache.org groovy jobs From: Paul King To: dev@groovy.incubator.apache.org Content-Type: text/plain; charset=UTF-8 Also, is the freebsd agent meant to have access to github? I get this error: FATAL: Failed to fetch from git://github.com/apache/incubator-groovy.git hudson.plugins.git.GitException: Failed to fetch from git://github.com/apache/incubator-groovy.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:647) ... Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress git://github.com/apache/incubator-groovy.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: unable to connect to github.com: github.com[0: 192.30.252.130]: errno=Operation not permitted at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1435) ... Using the freebsd agent isn't critical for the build in any way - but we like to support as many platforms as we can, so I thought it might be nice to have a build that checked that platform. Cheers, Paul. On Thu, Oct 22, 2015 at 5:35 AM, Andrew Bayer wrote: > Yeah, I need to turn it on. I'll do that tomorrow. > > > On Wednesday, October 21, 2015, Pascal Schumacher > wrote: >> >> Thanks! :) >> >> The first question: >> >> Could it be that the Github hook for pull request is not enabled by >> default? I tried to set up this job: >> https://builds.apache.org/view/Groovy/job/Groovy%20Github%20PRs/ by >> following the instructions at: >> https://blogs.apache.org/infra/entry/github_pull_request_builds_now >> >> I also compared the job configuration with >> https://builds.apache.org/view/All/job/kafka-trunk-git-pr-jdk7/ where the >> integration is working. >> >> Maybe I did something wrong? >> >> The second question: Is it possible to check the apache git repo without >> polling? >> >> Am 21.10.2015 um 10:14 schrieb Andrew Bayer: >> >> Done! >> >> On Tue, Oct 20, 2015 at 6:46 PM, Pascal Schumacher >> wrote: >>> >>> Hello mentors, >>> >>> could you please grant me (id: pascalschumacher) access to the groovy >>> jobs on https://builds.apache.org groovy ? >>> >>> Thanks, >>> Pascal >>> >>> Am 20.10.2015 um 02:37 schrieb Paul King: >>>> >>>> I have set up some builds on Jenkins including PR builds but as you >>>> noted earlier, the builds were failing. I didn't have time to >>>> investigate further. >>>> >>>> On Tue, Oct 20, 2015 at 5:01 AM, Andrew Bayer >>>> wrote: >>>>> >>>>> If you need anything installed or configured, just let me know and I >>>>> can >>>>> make it so. >>>>> >>>>> On Oct 19, 2015 21:01, "Pascal Schumacher" >>>>> wrote: >>>>>> >>>>>> I could not figure out if builds.apache.org has the jenkins gradle >>>>>> plugin? >>>>>> >>>>>> Also there are already some groovy jobs >>>>>> https://builds.apache.org/view/Groovy/ but it looks like every build >>>>>> failed. >>>>>> >>>>>> Am 19.10.2015 um 20:54 schrieb Andrew Bayer: >>>>>> >>>>>> Yup, Jenkins can happily do what we need. >>>>>> >>>>>> On Oct 19, 2015 20:49, "Pascal Schumacher" >>>>>> wrote: >>>>>>> >>>>>>> Thanks for the info. I did not know that. >>>>>>> >>>>>>> I would also be fine with creating a jenkins job on builds.apache.org >>>>>>> (I >>>>>>> use jenkins at work). If my understanding of the information on >>>>>>> https://wiki.apache.org/general/Jenkins is correct, that would also >>>>>>> allow us >>>>>>> to test on Windows. >>>>>>> >>>>>>> I'm fine with either solution. The important thing is that pull >>>>>>> request >>>>>>> are automatically updated with test result. Having to update pull >>>>>>> request by >>>>>>> hand and then having contributors think that they can not access the >>>>>>> ci-server because it requires a login with "guest" and a blank >>>>>>> password is >>>>>>> far from optional. >>>>>>> >>>>>>> Am 19.10.2015 um 20:34 schrieb Andrew Bayer: >>>>>>> >>>>>>> Fwiw, we can build and update pull requests on builds.apache.org as >>>>>>> well. >>>>>>> >>>>>>> On Oct 19, 2015 20:30, "Pascal Schumacher" >>>>>>> wrote: >>>>>>>> >>>>>>>> Hello everybody, >>>>>>>> >>>>>>>> according to the web TeamCity requires write access to the repo to >>>>>>>> update pull requests with test results. As this is not possible to >>>>>>>> with the >>>>>>>> Apache Github mirror, I suggest we use Travis CI to test pull >>>>>>>> request. >>>>>>>> >>>>>>>> Apache has a subscription for Travis CI >>>>>>>> >>>>>>>> https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci and >>>>>>>> according to >>>>>>>> >>>>>>>> http://de.slideshare.net/jukka/apache-development-with-github-and-travis-ci >>>>>>>> we only need to create a infrastructure ticket to enable the Travis >>>>>>>> Webhook >>>>>>>> for the mirror. >>>>>>>> >>>>>>>> If there are no objections I will add a ".travis.yml" file and >>>>>>>> create >>>>>>>> the infrastructure ticket. >>>>>>>> >>>>>>>> -Pascal >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Am 13.09.2015 um 10:46 schrieb Pascal Schumacher: >>>>>>>>> >>>>>>>>> Hello everybody, >>>>>>>>> >>>>>>>>> before moving to Apache TeamCity updated the pull request after >>>>>>>>> running >>>>>>>>> the tests, e.g.: >>>>>>>>> >>>>>>>>> https://github.com/groovy/groovy-core/pull/648 >>>>>>>>> >>>>>>>>> Is this no possible with the Apache Github clone? >>>>>>>>> >>>>>>>>> If it's not possible with TeamCity maybe we should add Travis to >>>>>>>>> test >>>>>>>>> pull request (as Thibault suggested in >>>>>>>>> https://github.com/apache/incubator-groovy/pull/112), because >>>>>>>>> Travis it's >>>>>>>>> possible, e.g.: >>>>>>>>> >>>>>>>>> https://github.com/apache/commons-lang/pull/107 >>>>>>>>> >>>>>>>>> -Pascal >>>>>>>>> >>> >> >> >