our organization uses travis-ci within github basic sanity checking when change committed. there way prevent full travis build/run when changes specific files or file types made?
as simplest example: if makes change readme.md file , wants commit directly master, don't need ci run before allowing this.
you might instruct team add [skip ci] commit messages, e.g.
git commit -m "updated readme [skip ci]".
this means github commit (after pushed) not trigger travis-ci run.
the alternative accept commit triggers travis-ci run, condition checks inside .travis.yml (or scripts executed it) exclude processing of unit-tests, etc. in other words: there ci run, heavy script stuff skipped.
Comments
Post a Comment