[Builder] Issue with CI/CD auto releases per PR Policy

KasunG Gajasinghe kasung at wso2.com
Thu Jan 25 03:27:40 PST 2018


On Wed, Jan 24, 2018 at 8:28 AM, Rasika Perera <rasikap at wso2.com> wrote:

> Hi Team,
>
> Currently, as i understood we are triggering auto release per PR merge.
> Due to recent recommendations we approve the PRs and wait for Travis build
> to complete before merging PRs. Since this process consumes some
> considerable time; there will be *several* PRs to be merged at a given time
> of a day.
>
> When we merge these multiple PRs at once; we noticed that multiple
> releases occurs on the respective repos without any usable commits in
> between.
>

This statement is not correct. :) Even though you are seeing this behavior
in the master branch, you can only find the actual commit lists of a given
release via that release tag's commits:

For ex:
https://github.com/wso2/carbon-device-mgt/commits/v3.0.208
[image: Inline image 1]

https://github.com/wso2/carbon-device-mgt/commits/v3.0.209
[image: Inline image 2]

As you see, v3.0.208 was released with PR #1163, the next immediate version
was released with PR #1164.

There is no engineering team wide agreement to wait for Travis CI's input.
I think this is a product team-level decision. Other option to Travis CI is
to build locally and verify. Both options will consume similar amount of
time IMO.

For instance please refer recent releases 3.0.208 and 3.0.209(same for
> 3.0.204 and 3.0.205) in carbon-device-mgt repo in [1].
>
> [image: Inline image 1]
>
> To avoid unnecessary release triggers; can we have a *window time* for
> triggering release process? If such window is already implemented what is
> the current value for it?
>
> [1] https://github.com/wso2/carbon-device-mgt/commits/master
>> --
> With Regards,
>
> *Rasika Perera*
> Senior Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> <http://wso2.com/signature>
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 

*Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
phone: +1 650-745-4499, 77 678 0813
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://wso2.org/pipermail/builder/attachments/20180125/58d0fa3f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2018-01-24 at 8.16.31 AM.png
Type: image/png
Size: 542972 bytes
Desc: not available
URL: <http://wso2.org/pipermail/builder/attachments/20180125/58d0fa3f/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 149742 bytes
Desc: not available
URL: <http://wso2.org/pipermail/builder/attachments/20180125/58d0fa3f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 66126 bytes
Desc: not available
URL: <http://wso2.org/pipermail/builder/attachments/20180125/58d0fa3f/attachment-0005.png>


More information about the Builder mailing list