This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • (DEPRECATED) Creating a Pull Request Job in CloudBees

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

DEPRECATED. BUILDS ARE NOW CONFIGURED IN https://builds.apache.org/view/J/view/jclouds/

Overview  

Setting up a Jenkins job in the jclouds DEV@cloud account to trigger on Pull Requests is a three-step process:  

  1. Configure the Jenkins job in DEV@cloud 
  2. Create the Service Hook in GitHub 

  3. Configure the Service Hook via the GitHub API

Prerequisites

DEV@cloud Account

If you don't have a DEV@cloud account with rights to create Jenkins jobs for jclouds, plesae send an email to the dev list requesting access.  

Admin Rights in GitHub

You'll need to be able to administer the GitHub repo for which you're looking to create a pull request job. If you can see the Settings link for the repo, you should be OK.  

Configuring the Jenkins Job

Log in to the jclouds DEV@cloud account and create a new job on the pull requests tab. Your best bet is to clone of the existing pull request jobs and modify the source repository.  

...

  1. The source repository and branch are correct 
  2. Git validated merge support is enabled Git validated merge support option 

  3. Build pull requests to the repository is the only build trigger Build pull requests to the repository trigger  

 

Creating the GitHub Service Hook  

Go to the Settings > Service Hooks menu and create a new WebHook URLs entry pointing at https://jclouds.ci.cloudbees.com/github-pull-request-hook/  

GitHub WebHook URL  

Configuring the Service Hook

Unfortunately, the Service Hook we have just created listens to the wrong repository event (push instead of pull_request) and sends the wrong type of data, and that's not (yet) something we can change via the GitHub site. We'll use the GitHub HTTP API instead.  

...