groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pascal Schumacher <pascalschumac...@gmx.net>
Subject Re: [mentors] access to https://builds.apache.org groovy jobs
Date Thu, 22 Oct 2015 16:24:23 GMT
Thanks! :)

Integration is working: https://github.com/apache/incubator-groovy/pull/156

Am 22.10.2015 um 15:31 schrieb Andrew Bayer:
> Hook is live.
>
> Honestly, I don't know the last time anyone tried to use the freebsd 
> slave - wouldn't shock me at all that it doesn't know how to talk to 
> the internet. =)
>
> A.
>
> On Thu, Oct 22, 2015 at 7:23 AM, Paul King <paulk@asert.com.au 
> <mailto:paulk@asert.com.au>> wrote:
>
>     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
>     <http://github.com/apache/incubator-groovy.git>
>     hudson.plugins.git.GitException: Failed to fetch from
>     git://github.com/apache/incubator-groovy.git
>     <http://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
>     <http://github.com/apache/incubator-groovy.git>
>     +refs/heads/*:refs/remotes/origin/*" returned status code 128:
>     stdout:
>     stderr: fatal: unable to connect to github.com <http://github.com>:
>     github.com <http://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
>     <andrew.bayer@gmail.com <mailto:andrew.bayer@gmail.com>> wrote:
>     > Yeah, I need to turn it on. I'll do that tomorrow.
>     >
>     >
>     > On Wednesday, October 21, 2015, Pascal Schumacher
>     <pascalschumacher@gmx.net <mailto:pascalschumacher@gmx.net>>
>     > 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
>     >> <pascalschumacher@gmx.net <mailto:pascalschumacher@gmx.net>>
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
>     <andrew.bayer@gmail.com <mailto:andrew.bayer@gmail.com>>
>     >>>> 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"
>     <pascalschumacher@gmx.net <mailto:pascalschumacher@gmx.net>>
>     >>>>> wrote:
>     >>>>>>
>     >>>>>> I could not figure out if builds.apache.org
>     <http://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"
>     <pascalschumacher@gmx.net <mailto:pascalschumacher@gmx.net>>
>     >>>>>> wrote:
>     >>>>>>>
>     >>>>>>> Thanks for the info. I did not know that.
>     >>>>>>>
>     >>>>>>> I would also be fine with creating a jenkins job on
>     builds.apache.org <http://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 <http://builds.apache.org> as
>     >>>>>>> well.
>     >>>>>>>
>     >>>>>>> On Oct 19, 2015 20:30, "Pascal Schumacher"
>     <pascalschumacher@gmx.net <mailto:pascalschumacher@gmx.net>>
>     >>>>>>> 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
>     >>>>>>>>>
>     >>>
>     >>
>     >>
>     >
>
>


Mime
View raw message