The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
One of the bloom tutorials described the process to enable pull request jobs for your repo: http://wiki.ros.org/buildfarm/Pull%20request%20testing
I assume you are missing the 1.1 Prerequisite a step. You need to give the GitHub user used by Jenkins access to setup web hooks to notify Jenkins about pull requests and changes to them.
| | 2 | No.2 Revision |
One of the bloom tutorials described describes the process to enable pull request jobs for your repo: http://wiki.ros.org/buildfarm/Pull%20request%20testing
I assume you are missing the 1.1 Prerequisite a step. You need to give the GitHub user used by Jenkins access to setup web hooks to notify Jenkins about pull requests and changes to them.
| | 3 | No.3 Revision |
One of the bloom tutorials describes the process to enable pull request jobs for your repo: http://wiki.ros.org/buildfarm/Pull%20request%20testing
I assume you are missing the 1.1 Prerequisite a step. You need to give the GitHub user used by Jenkins access to setup web hooks to notify Jenkins about pull requests and changes to them.
Update: I have updated the wiki page with a reference to the Jenkins plugin and repeating the requirements documented there.
Jenkins uses the Pull Request Builder plugin to setup the webhooks which trigger Jenkins for new or updated pull requests and report back the status. Therefore the GitHub org unit where the repository is located must grant push, pull and administrative rights to the user ros-pull-request-builder. (You can setup the webhook manually to avoid the need for administrative rights. Then the Jenkins user only needs push and pull access.)
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
