buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ilya Pyatigorskiy <ata...@gmail.com>
Subject Re: How do you handle buildr release + CI?
Date Tue, 08 Mar 2011 17:39:25 GMT
Right, manual build release sounds reasonable!

Thanks,
Ilya.

On Tue, Mar 8, 2011 at 8:37 PM, Antoine Toulme <antoine@lunar-ocean.com>wrote:

> A release is usually manual. Maybe having a CI build that does buildr
> deploy would do the job ?
>
> If your CI server is jenkins, I think you can specify which paths should be
> ignored when polling for changes. (see in the advanced options, excluded
> regions and excluded users).
>
> Antoine
>
>
> On Tue, Mar 8, 2011 at 04:01, Ilya Pyatigorskiy <atamur@gmail.com> wrote:
>
>> Hi,
>>
>> I've bumped into a strange problem: I was trying to setup my CI server to
>> automatically test and release my app on all commits, but then it went
>> into
>> an infinite loop, because buildr during the release process was creating
>> new
>> commits!
>>
>> How do people handle such situations? I was forced to make the release
>> process manual, which for me means that I'll have to click a "release"
>> link
>> in my CI by hand whenever I want to upgrade my UAT.
>>
>> Ilya.
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message