[jira] [Updated] (KAFKA-2320) Configure GitHub pull request build in Jenkins

2015-07-16 Thread Ismael Juma (JIRA)

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

Ismael Juma updated KAFKA-2320:
---
Assignee: Jun Rao

 Configure GitHub pull request build in Jenkins
 --

 Key: KAFKA-2320
 URL: https://issues.apache.org/jira/browse/KAFKA-2320
 Project: Kafka
  Issue Type: Task
Reporter: Ismael Juma
Assignee: Jun Rao

 The details are available in the following Apache Infra post:
 https://blogs.apache.org/infra/entry/github_pull_request_builds_now
 I paste the instructions here as well for convenience:
 {quote}
 Here’s what you need to do to set it up:
 * Create a new job, probably copied from an existing job.
 * Make sure you’re not doing any “mvn deploy” or equivalent in the new job - 
 this job shouldn’t be deploying any artifacts to Nexus, etc.
 * Check the Enable Git validated merge support” box - you can leave the 
 first few fields set to their default, since we’re not actually pushing 
 anything. This is just required to get the pull request builder to register 
 correctly.
 * Set the “GitHub project” field to the HTTP URL for your repository - 
 i.e.,http://github.com/apache/kafka/- make sure it ends with that trailing 
 slash and doesn’t include .git, etc.
 * In the Git SCM section of the job configuration, set the repository URL to 
 point to the GitHub git:// URL for your repository - i.e., 
 git://github.com/apache/kafka.git.
 * You should be able to leave the “Branches to build” field as is - this 
 won’t be relevant anyway.
 * Click the “Add” button in “Additional Behaviors” and choose Strategy for 
 choosing what to build”. Make sure the choosing strategy is set to “Build 
 commits submitted for validated merge”.
 * Uncheck any existing build triggers - this shouldn’t be running on a 
 schedule, polling, running when SNAPSHOT dependencies are built, etc.
 * Check the “Build pull requests to the repository” option in the build 
 triggers.
 * Optionally change anything else in the job that you’d like to be different 
 for a pull request build than for a normal build - i.e., any downstream build 
 triggers should probably be removed,  you may want to change email 
 recipients, etc.
 * Save, and you’re done!
 {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (KAFKA-2320) Configure GitHub pull request build in Jenkins

2015-07-14 Thread Ismael Juma (JIRA)

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

Ismael Juma updated KAFKA-2320:
---
Description: 
The details are available in the following Apache Infra post:
https://blogs.apache.org/infra/entry/github_pull_request_builds_now

I paste the instructions here as well for convenience:

{quote}
Here’s what you need to do to set it up:
* Create a new job, probably copied from an existing job.
* Make sure you’re not doing any “mvn deploy” or equivalent in the new job - 
this job shouldn’t be deploying any artifacts to Nexus, etc.
* Check the Enable Git validated merge support” box - you can leave the first 
few fields set to their default, since we’re not actually pushing anything. 
This is just required to get the pull request builder to register correctly.
* Set the “GitHub project” field to the HTTP URL for your repository - 
i.e.,http://github.com/apache/kafka/- make sure it ends with that trailing 
slash and doesn’t include .git, etc.
* In the Git SCM section of the job configuration, set the repository URL to 
point to the GitHub git:// URL for your repository - i.e., 
git://github.com/apache/kafka.git.
* You should be able to leave the “Branches to build” field as is - this won’t 
be relevant anyway.
* Click the “Add” button in “Additional Behaviors” and choose Strategy for 
choosing what to build”. Make sure the choosing strategy is set to “Build 
commits submitted for validated merge”.
* Uncheck any existing build triggers - this shouldn’t be running on a 
schedule, polling, running when SNAPSHOT dependencies are built, etc.
* Check the “Build pull requests to the repository” option in the build 
triggers.
* Optionally change anything else in the job that you’d like to be different 
for a pull request build than for a normal build - i.e., any downstream build 
triggers should probably be removed,  you may want to change email recipients, 
etc.
* Save, and you’re done!
{quote}

  was:
The details are available in the following Apache Infra post:
https://blogs.apache.org/infra/entry/github_pull_request_builds_now

I paste the instructions here as well for convenience:

{quote}
Here’s what you need to do to set it up:
* Create a new job, probably copied from an existing job.
* Make sure you’re not doing any “mvn deploy” or equivalent in the new job - 
this job shouldn’t be deploying any artifacts to Nexus, etc.
* Check the Enable Git validated merge support” box - you can leave the first 
few fields set to their default, since we’re not actually pushing anything. 
This is just required to get the pull request builder to register correctly.
* Set the “GitHub project” field to the HTTP URL for your repository - 
i.e.,http://github.com/apache/incubator-brooklyn/- make sure it ends with 
that trailing slash and doesn’t include .git, etc.
* In the Git SCM section of the job configuration, set the repository URL to 
point to the GitHub git:// URL for your repository - i.e., 
git://github.com/apache/kafka.git.
* You should be able to leave the “Branches to build” field as is - this won’t 
be relevant anyway.
* Click the “Add” button in “Additional Behaviors” and choose Strategy for 
choosing what to build”. Make sure the choosing strategy is set to “Build 
commits submitted for validated merge”.
* Uncheck any existing build triggers - this shouldn’t be running on a 
schedule, polling, running when SNAPSHOT dependencies are built, etc.
* Check the “Build pull requests to the repository” option in the build 
triggers.
* Optionally change anything else in the job that you’d like to be different 
for a pull request build than for a normal build - i.e., any downstream build 
triggers should probably be removed,  you may want to change email recipients, 
etc.
* Save, and you’re done!
{quote}


 Configure GitHub pull request build in Jenkins
 --

 Key: KAFKA-2320
 URL: https://issues.apache.org/jira/browse/KAFKA-2320
 Project: Kafka
  Issue Type: Task
Reporter: Ismael Juma

 The details are available in the following Apache Infra post:
 https://blogs.apache.org/infra/entry/github_pull_request_builds_now
 I paste the instructions here as well for convenience:
 {quote}
 Here’s what you need to do to set it up:
 * Create a new job, probably copied from an existing job.
 * Make sure you’re not doing any “mvn deploy” or equivalent in the new job - 
 this job shouldn’t be deploying any artifacts to Nexus, etc.
 * Check the Enable Git validated merge support” box - you can leave the 
 first few fields set to their default, since we’re not actually pushing 
 anything. This is just required to get the pull request builder to register 
 correctly.
 * Set the “GitHub project” field to the HTTP URL for your repository - 
 i.e.,http://github.com/apache/kafka/- make sure it ends with that trailing 
 slash and