infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Thistlethwaite (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-14492) It would be a great asset to see jenkins build results on github pull requests
Date Mon, 18 Jun 2018 17:04:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-14492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Thistlethwaite updated INFRA-14492:
-----------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

Adding to [~cml]'s comment, this can be achieved by using GitBox. I suggest you put in a request
to move the repo. 

> It would be a great asset to see jenkins build results on github pull requests
> ------------------------------------------------------------------------------
>
>                 Key: INFRA-14492
>                 URL: https://issues.apache.org/jira/browse/INFRA-14492
>             Project: Infrastructure
>          Issue Type: Improvement
>          Components: Git, Github
>            Reporter: Dominik Psenner
>            Priority: Minor
>              Labels: #bugbash-jun2018
>
> Currently I have set up a jenkins job named logging-log4net that uses my credentials
to fetch branches and pull requests from the github mirror logging-log4net. It then automatically
builds a pull request and it would be great to see build outcomes on that pull request.
> Notice that the job already would like to update some status on github but it seems to
fail with the following message:
> Could not update commit status, please check if your scan credentials belong to a member
of the organization or a collaborator of the repository and repo:status scope is selected
> I've set up a personal access token and granted the personal access token repo:status
scope. Further I am member of the apache organization on github so this error message seems
odd to me.
> This directly relates also to how jenkins jobs that fetch data from github need to be
configured. It is discouraged to use anonymous but from what I've observed across other jenkins
jobs most people simply use anonymous for authentication. The drawback is that fetching updates
takes ages because of github rate limiting taking place. It would be a lot easier if there
was a global credential ready for use in jenkins pipelines that has the necessary scopes set
up right.
> Last but not least, here's an example of an integration between github and travis that
gives great feedback to whoever opens a pull request:
> https://github.com/nant/nant/pull/169
> It would be great to have this or something comparable also for the ASF integration with
github.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message