Re: [ovirt-devel] Toward self-configuring CI, or how can we stop writing YAML

>> >> Oh, but it does.. you can configure publishers ans webhooks in the >> .travis.yml file. I commonly build a project, create a docker image >> using the built bits and deploy to my VPS (using a branch name check). >> > > What travis does not have is build chains in the sense of multiple jobs by > different yaml files, but as Martin says the rest is there. What they have > is different steps inside one yaml file (setup, pre_script, post_script, > deployment, ...) > which can be triggered according to branches and tags. > > In Kubevirt we also use a .travis.yaml which does testing and releasing > based on tags and branches [1]. > > Note that for more finetuned controls, they also provide a lot of > environment variables which you can reference (e.g. branch, tag, ...) > Lets not run this into an off-topic 'travis vs. foo' discussion. This is not going anywhere. -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/