<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 10, 2017 at 2:28 PM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">>><br>
>> Oh, but it does.. you can configure publishers ans webhooks in the<br>
>> .travis.yml file. I commonly build a project, create a docker image<br>
>> using the built bits and deploy to my VPS (using a branch name check).<br>
>><br>
><br>
> What travis does not have is build chains in the sense of multiple jobs by<br>
> different yaml files, but as Martin says the rest is there. What they have<br>
> is different steps inside one yaml file (setup, pre_script, post_script,<br>
> deployment, ...)<br>
> which can be triggered according to branches and tags.<br>
><br>
> In Kubevirt we also use a .travis.yaml which does testing and releasing<br>
> based on tags and branches [1].<br>
><br>
> Note that for more finetuned controls, they also provide a lot of<br>
> environment variables which you can reference (e.g. branch, tag, ...)<br>
><br>
<br>
</span>Lets not run this into an off-topic 'travis vs. foo' discussion. This<br>
is not going anywhere.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>Not trying to make any point, except from providing insight how travis is doing it. Since it might be useful.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
--<br>
Barak Korren<br>
<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
RHCE, RHCi, RHV-DevOps Team<br>
<a href="https://ifireball.wordpress.com/" rel="noreferrer" target="_blank">https://ifireball.wordpress.<wbr>com/</a><br>
</div></div></blockquote></div><br></div></div>