[DISCUSS] Binary diff and hot patch

["Musayev, Ilya" <im...@webmd.net>]

I was wondering if we can use binary diffs to hotpatch ACS.

Currently, the way for me to identify what patch could have caused issue X, would be  - try to find the suspects - it could be several. Revert 1 commit, rebuild and retry, if failed, restore previously reverted commit, revert 2nd commit, rebuild and retry - etc..

As you can see, this is very time consuming and painful, I'm wondering if there is a better way to do this. I came across a project called javaxdelta on sourceforge - curious what your thought on this may be, and if there is a better way to try out patches instead of what I'm doing now.

Thanks
ilya

Re: [DISCUSS] Binary diff and hot patch

[Daan Hoogland <da...@gmail.com>]

Another take is to have a big datastore with all jenkins results and
pick e build from it (containing the patch id in the name) to see if
it is the culprit.

It might be possible, what you are looking for.

On Fri, Aug 9, 2013 at 5:38 PM, Musayev, Ilya <im...@webmd.net> wrote:
> I guess no way to do this :(
>
>> -----Original Message-----
>> From: Musayev, Ilya [mailto:imusayev@webmd.net]
>> Sent: Wednesday, August 07, 2013 5:51 PM
>> To: dev@cloudstack.apache.org
>> Subject: [DISCUSS] Binary diff and hot patch
>>
>> I was wondering if we can use binary diffs to hotpatch ACS.
>>
>> Currently, the way for me to identify what patch could have caused issue X,
>> would be  - try to find the suspects - it could be several. Revert 1 commit,
>> rebuild and retry, if failed, restore previously reverted commit, revert 2nd
>> commit, rebuild and retry - etc..
>>
>> As you can see, this is very time consuming and painful, I'm wondering if
>> there is a better way to do this. I came across a project called javaxdelta on
>> sourceforge - curious what your thought on this may be, and if there is a
>> better way to try out patches instead of what I'm doing now.
>>
>> Thanks
>> ilya
>

RE: [DISCUSS] Binary diff and hot patch

["Musayev, Ilya" <im...@webmd.net>]

I guess no way to do this :(

> -----Original Message-----
> From: Musayev, Ilya [mailto:imusayev@webmd.net]
> Sent: Wednesday, August 07, 2013 5:51 PM
> To: dev@cloudstack.apache.org
> Subject: [DISCUSS] Binary diff and hot patch
> 
> I was wondering if we can use binary diffs to hotpatch ACS.
> 
> Currently, the way for me to identify what patch could have caused issue X,
> would be  - try to find the suspects - it could be several. Revert 1 commit,
> rebuild and retry, if failed, restore previously reverted commit, revert 2nd
> commit, rebuild and retry - etc..
> 
> As you can see, this is very time consuming and painful, I'm wondering if
> there is a better way to do this. I came across a project called javaxdelta on
> sourceforge - curious what your thought on this may be, and if there is a
> better way to try out patches instead of what I'm doing now.
> 
> Thanks
> ilya