чт, 16 мая 2019 г. в 12:42, Willy Tarreau <w...@1wt.eu>: > Hi Ilya, > > On Thu, May 16, 2019 at 01:12:40AM +0500, ???? ??????? wrote: > > in order to enable builds, the following steps must be taken > > > > 1) must be enabled (using owner account) on > > https://github.com/marketplace/cirrus-ci , also "haproxy/haproxy" repo > > should be enabled there > > 2) build configuration is taken from .cirrus.yml (attached as patch to > > previous email) > > So I did this, stupidly repeating the steps you explained above and > committing your file, but I have absolutely no idea what I did and > still couldn't figure on their cirrus-ci.org and .com sites where the > build statuses are supposed to be reported. I wanted to at least add > this in the commit message but couldn't. Quite frankly, I really hate > doing stuff that I don't understand with little more info than "please > just click the green buttons there and don't worry it will not hurt, > only red ones do". > > It would be nice next time to give a bit more information. Maybe for > you this cirrus stuff is legacy, but I never heard about it before, am > not used at all to this type of tools, and don't even know why this one > and not another one. And can't we use just one instead of fragmenting > the build results between multiple sites ? These are typically the > element that should be provided upfront when requesting such features, > so that I don't have to spend time asking or blindly trusting that this > will not break our process. > > If in the mean time you know how to verify that it was properly enabled > and builds there, and share with us the link to consult the status, it > would be nice. >
I understand what you mean, actually I've no idea yet how to document it properly. while travis-ci provides very good url naming, i.e. https://travis-ci.com/haproxy/haproxy there's no such way within cirrus-ci I'll try to find out :) > > Thanks, > Willy >
