Build for all branches but do not take into account status for all

[Claire Reynaud]

Hello,

We want to trigger a build in Jenkins each time a pull request is created 
on our github repository, and then to have a build success/failure status 
associated directly to the pull request like this: 
https://github.com/blog/1227-commit-status-api .

We set up our job to build for all remote branches, which triggers the 
build correctly when a new remote branch is created/updated.
We call back the github status API and get the status associated to the 
pull request which is pretty cool :).

Problem is we do not want to have these pull request remote branch builds 
to pollute our job history.
Is there a way to work around this issue without duplicating our job (one 
for master only to keep the history clean, and the other one for all the 
pull requests builds)?

Thanks,
Claire

Re: Build for all branches but do not take into account status for all

[Andrew Melo]

On Wed, Oct 10, 2012 at 10:35 AM, Claire Reynaud
claire12.reyn...@gmail.com wrote:
 Hello,

 We want to trigger a build in Jenkins each time a pull request is created on
 our github repository, and then to have a build success/failure status
 associated directly to the pull request like this:
 https://github.com/blog/1227-commit-status-api .

 We set up our job to build for all remote branches, which triggers the build
 correctly when a new remote branch is created/updated.
 We call back the github status API and get the status associated to the pull
 request which is pretty cool :).

 Problem is we do not want to have these pull request remote branch builds to
 pollute our job history.
 Is there a way to work around this issue without duplicating our job (one
 for master only to keep the history clean, and the other one for all the
 pull requests builds)?

I'm also curious about this, but couldn't find any option other than
to duplicate the job.

Thanks,
Andrew


 Thanks,
 Claire



-- 
--
Andrew Melo