[
https://issues.apache.org/jira/browse/INLONG-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382853#comment-17382853
]
Ji Yuanhao edited comment on INLONG-732 at 7/18/21, 3:25 PM:
-------------------------------------------------------------
Well, I want to do it with GitHub Actions. I found that InLong is using Travis
which is slower than GitHub Actions and has fewer features. What's your option?
----
In addition, I want to implement two workflows based on GitHub Actions.
The first one is for testing, including caching maven packages, building with
Maven, uploading coverage to [Codecov|https://codecov.io/].
There are two questions in this workflow.
1. When to trigger it? Currently it is triggered when a push or pull request
event occurs on the master or INLONG-* branch.
2. Is it possible to delete travis.yml or disable travis? Because it will be
redundant if we use GitHub Actions instead of Travis.
The second one is for labeling PR, which is based on
[labeler|https://github.com/actions/labeler]. It can automatically label new
pull requests based on the paths of files being changed.
We should write a list of labels and minimatch globs in .github/labeler.yml to
match to apply the label. But before that, We need to define the required label
in [labels|https://github.com/apache/incubator-inlong/labels]. The label of PR
can make people clearly know what it does.
Finally, are there other CI/CD workflow needs?
was (Author: shenke):
Well, I want to do it with GitHub Actions. I found that InLong is using Travis
which is slower than GitHub Actions and has fewer features. What's your option?
----
In addition, I want to implemente two workflows based on GitHub Actions.
The first one is for testing, including caching maven packages, building with
Maven, uploading coverage to [Codecov|https://codecov.io/].
There are two questions in this workflow.
1. When to trigger it? Currently it is triggered when a push or pull request
event occurs on the master or INLONG-* branch.
2. Is it possible to delete travis.yml or disable travis? Because it will be
redundant if we use GitHub Actions instead of Travis.
The second one is for labeling PR, which is based on
[labeler|https://github.com/actions/labeler]. It can automatically label new
pull requests based on the paths of files being changed.
We should write a list of labels and minimatch globs in .github/labeler.yml to
match to apply the label. But before that, We need to define the required label
in [labels|https://github.com/apache/incubator-inlong/labels]. The label of PR
can make people clearly know what it does.
Finally, are there other CI/CD workflow needs?
> Optimize the CI/CD workflow for build and integration test
> -----------------------------------------------------------
>
> Key: INLONG-732
> URL: https://issues.apache.org/jira/browse/INLONG-732
> Project: Apache InLong
> Issue Type: Improvement
> Reporter: Charles Zhang
> Assignee: Ji Yuanhao
> Priority: Major
> Fix For: 0.10.0
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
