infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Won Wook SONG (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-16171) Nemo: Jenkins - Credentials for GitHub commit status + Hooks for GHPRB
Date Mon, 12 Mar 2018 09:15:00 GMT
Won Wook SONG created INFRA-16171:
-------------------------------------

             Summary: Nemo: Jenkins - Credentials for GitHub commit status + Hooks for GHPRB
                 Key: INFRA-16171
                 URL: https://issues.apache.org/jira/browse/INFRA-16171
             Project: Infrastructure
          Issue Type: Bug
          Components: Buildbot, Github, Jenkins
            Reporter: Won Wook SONG


We've been trying to integrate Jenkins CI to our Github repository (https://github.com/apache/incubator-nemo),
but it seems like we need some help throughout the process. As it can be seen in https://builds.apache.org/job/Nemo/
, we have set up two jenkins jobs: one to verify the master branch periodically and one to
listen to hooks and build pull requests. 

1. The problem on both jobs is that although we have tried using the `Authorization` plugin
for authorization, the build fails continuously (as shown in the master job) as it fails to
find the credentials required to update its commit status. We have tried the same configuration
on our private jenkins server on a forked repo, but it works well, so it doesn't seem like
a problem on the configurations.

2. In order for the Jenkins server to listen to pull requests and commits, we should set up
a webhook on the Github side to post its activities to the Jenkins server to trigger builds.
Notice that we would also like to use the `!rebuild` trigger phase, so it would be mandatory
to send the 'commenting on PRs' activities with the webhook as well. 

Could you kindly provide help on these issues?



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

Mime
View raw message