Publish rockspec automatically #102
Conversation
printercu force-pushed the publish_rockspec branch from d630e87 to 455e4f6 Compare 
Totktonada left a comment
Totktonada left a comment There was a problem hiding this comment.
Reducing of duplication in .travis.yml is great, thanks!
I'm tentative about splitting jobs to testing and deploy stages, because stages are run sequentially: this will increase overall time of the pipeline. However queue tests are quite small and it does not matter much. So, I'm okay if there are no other way to reduce text duplication here.
Let's add 'travis-ci:' prefix to the commit message: it is useful when looking over commits to filter out ones that do not change code or tests.
Will you add a commit re publishing rockspec to our repository? Now the PR is named 'Publish rockspec automatically', while it contains just .travis.yml rewriting.
printercu force-pushed the publish_rockspec branch from 455e4f6 to 533f924 Compare 
| I've split deployment from tests because deployment includes building packages with packpack. This takes quite long. Now it runs tests for 3 Tarantool versions in I've also added commit for publishing rockspecs. |
| I wrote it in assumption that we run tests in packpack jobs itself, but now I see that it is so only in Debian / Ubuntu jobs, while test are not run in CentOS / Fedora jobs. Okay for splitting stages so. |
Totktonada left a comment
Totktonada left a comment There was a problem hiding this comment.
LGTM.
Let's add 'travis-ci' prefixes for commit messages.
If possible, please, set a jobs name for rockspec upload jobs for Travis-CI web UI.
printercu force-pushed the publish_rockspec branch from 533f924 to ab45a10 Compare 
No description provided.