tree: 3d4cac6acebb09ea7f1438361248277c74a868c7 [path history] [tgz]
  1. ci_build.yml
  2. ci_chart_test.yml
  3. ci_check_license.yml
  4. ci_check_pr_title.yml
  5. ci_docker.yml
  6. ci_greeting.yml
  7. ci_labeler.yml
  8. ci_stale.yml
  9. ci_ut.yml
  10. codeql_analysis.yml
  11. README.md
.github/workflows/README.md

GitHub Workflows

This directory contains all InLong CI checks.

  • InLong Build

    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.

  • InLong Unit Test

    Unit testing when pushing changes or opening a pull request.

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

  • InLong Docker Build and Push

    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.

  • InLong Helm Charts Lint and Test

    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.

  • InLong Check License Header

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

  • InLong Pull Request Labeler

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

  • InLong Mark Stale Issues and PRs

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

  • InLong Greeting

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

  • InLong Check Pull Request Title

    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]

Troubleshooting

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

Maintainers