This directory contains all InLong CI checks.

• 

  Build InLong when pushing changes or opening a pull request.

  If it passes, you can download the InLong binary package from the workflow run's URL.

• 

  Unit testing when pushing changes or opening a pull request.

  If it fails, you can check out reports form the workflow run's URL.

• 

  Build Docker images when pushing changes or opening a pull request.

  Only when pushing changes to the apache/inlong repository will the Docker images are pushed to Docker Hub.

• 

  Lint and test the InLong Helm Chart when pushing changes or opening a pull request.

  In this workflow, firstly, install Helm using the azure/setup-helm action, then install chart-testing using the helm/chart-testing-action and install Kind using the helm/kind-action, finally, use the chart-testing tool to lint and install the InLong Helm Chart. And here is the chart-testing configuration and here is the kind configuration.

  NOTE: If the charts have not changed, they will not be linted, validated, installed and tested.

• 

  Check licence header when pushing changes or opening a pull request using the apache/skywalking-eyes action. And here is the configuration.

• 

  label new pull requests based on the paths of files being changed using the actions/labeler action. And here is the labeler configuration

• 

  Mark issues and pull requests that have not had recent interaction using the actions/stale action.

• 

  Interact with newcomers using the actions/first-interaction action.

• 

  Check pull request title.

  Title Example: [INLONG-XYZ][Component] Title of the pull request

  • XYZ should be replaced by the actual GitHub Issue number, e.g. [INLONG-123]

  • Component should be replaced by the InLong component name, e.g. [INLONG-123][Manager]

If you have any questions, welcome to contact the maintainers. And feel free to make a pull request!

• dockerzhang
• shink