It would be ideal to have the build pull master, fetch the incoming, merge it, 
and build that.  That way you know the result is good.

-----Original Message-----
From: Aki Sukegawa [mailto:[email protected]] 
Sent: Monday, May 02, 2016 10:27 PM
To: [email protected]
Subject: Re: Unstable builds - what's happening?

If we rev-parse on tags/changes/..., we need to map +/refs/pull/*/head to them 
first.
In other words, put the following line before the failing rev-parse, or an 
equivalent plugin setting.
git -c core.askpass=true fetch --tags --progress 
https://github.com/apache/thrift.git +refs/pull/*/head:refs/tags/changes/*
As we're purging workspace every time, it downloads all the past pull requests, 
though.

I noticed that the rebuild does not fetch from pull request at all (it builds 
on master).
I have a feeling that it was working correctly in the past, but I'm not sure.

On Tue, May 3, 2016 at 3:02 AM Jim King <[email protected]> wrote:

> We have 94 (or more) pull requests outstanding and they have all failed.
>
> What’s being done to address it?  I haven’t seen any action taken in 
> many days now.
>
>
>
> Thanks,
>
>
>
> [image: Description: Description: simplivity-lg-xsmall]
>
> James E. King, III
>
> Architect
>
> 8 Technology Drive, 2nd Floor
> Westborough, MA 01581-1756
>
> Ph: 855-SVT-INFO
>
>
>
>
> ------------------------------
> PRIVACY STATEMENT:
> This message is a PRIVATE communication. This message and all 
> attachments are a private communication sent by SimpliVity and are 
> considered to be confidential or protected by privilege. If you are 
> not the intended recipient, you are hereby notified that any 
> disclosure, copying, distribution or use of the information contained 
> in or attached to this message is strictly prohibited. Please notify 
> the sender of the delivery error by replying to this message, and then delete 
> it from your system.
> For more information please visit http://www.simplivity.com
> ------------------------------
>
---------------------------------------------------------------------------------------
PRIVACY STATEMENT:
This message is a PRIVATE communication.  This message and all attachments are 
a private communication sent by SimpliVity and are considered to be 
confidential or protected by privilege. If you are not the intended recipient, 
you are hereby notified that any disclosure, copying, distribution or use of 
the information contained in or attached to this message is strictly 
prohibited.  Please notify the sender of the delivery error by replying to this 
message, and then delete it from your system.
---------------------------------------------------------------------------------------

Reply via email to