In .travis.yml file. no matter how many os environments you configure, they all execute same commands, for example "mvn clean test".
Can we configure a special os to only run 'mvn rat:check' command while other os run 'mvn clean test'? On 3/3/2019 21:50，Xiangdong Huang<[email protected]> wrote： Hi, I am not sure whether travis can provide a separated pipeline to run user-specified command. What do you mean about `user-specified command`? Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 徐毅 <[email protected]> 于2019年3月3日周日 下午8:13写道： Hi When someone creates a pull request from forked repo, jenkins won't trigger to run tests. So we use travis-ci to trigger tests on different os. I am not sure whether travis can provide a separated pipeline to run user-specified command. Thanks XuYi On 3/3/2019 19:46，Julian Feinauer<[email protected]> wrote： Hi, this behavior sounds strange. But I think this pipeline should be build into the Jenkins build, or? It should be pretty easy to force one build step to a specific os. Perhaps we should open a Jira for that issue to finally track down the real source of the problem. Julian Von meinem Mobiltelefon gesendet -------- Ursprüngliche Nachricht -------- Betreff: Problems about rat plugin and apache header check Von: 徐毅 An: [email protected] Cc: Hi, Now we use rat plugin to check apache header, it seems that our project can pass rat check on linux but failed on windows. If someone creates a pull request from his forked repo, we use travis-ci to run tests on different os without checking apache header. If we add apache header check in travis file(see [1]), it fails on some os. Can we add a new pipeline which is only used to check apache header on linux? I found that there many free continuous integration service at [2]. Shall we choose one of them? [1] https://github.com/apache/incubator-iotdb/pull/84 [2] https://github.com/marketplace/category/continuous-integration Thanks XuYi
