Skip to content

Conversation

@Chisanan232
Copy link
Owner

Pre-Checking

‼️Please must read this section and check by yourself.
⚠️Do NOT modify this section if it doesn't have any necessary reason.

Please verify the PR header should be satisfied below format:

[commit topic] (commit scope) <commit summary>
  • commit topic: The major topic of your modify. It could have multiple topics, e.g., [Breaking Change + Test].
  • commit scope: The scope in project of modify. It could have multiple scopes, e.g., (config + test).
  • commit summary: Summary of the commits. It should be clear that the target, the KEY POINT why you modify it or what you resolve, etc.

Please refer to GCR (Git Commit Rules) to get more detail about it.


Target

  • Integrate the feature about organizing and generating testing coverage reports into a reusable workflow. So workflow could be more shorter and clear (organize_and_generate_test_cov_reports.yaml).
  • Add new feature about set up and run a sample HTTP server for testing if it needs in some testing scenario. (run_test_items_via_pytest.yaml)
  • Add new feature about automation of building git tag and GitHub release.
  • Fix uploading feature cannot work issue. (upload_test_cov_report.yaml)
  • Integrate all the uploading test coverage report features into a reusable workflow. (upload_test_cov_report.yaml)
  • Update document README.
  • Move the PR template to .github directory (for working finely).

Modify Code Scope

  • All settings in .github directory.

    • GitHub Action settings all in .github/workflows.
    • Template of PR content setting in .github.

Effecting Scope

  • The all automations after developers pushes their commits to GitHub platform.

Description

  • GitHub Action CI:

    • Integrate one of CI processes about organizing and generating testing report into ONYL ONE reusable workflow organize_and_generate_testing_coverage_reports.yaml. It's detail work flow:

      download all testing reports -> combine some reports with specific condition (test type) into one report -> show the report -> convert the report as XML format file -> upload the report in GitHub Action temp space

    • Add new feature to set up and run HTTP server for testing in run_test_items_via_pytest.yaml. It's would run this process with Python library flask and gunicorn.

    • About modify uploading feature workflow upload_test_cov_report.yaml

      • Fix issue about uploading test coverage report to some platform doesn't work at all.
      • Integrate the uploading test coverage report feature into a workflow.
    • About building git tag or creating GitHub release feature workflow build_git-tag_and_create_github-release.yaml

  • Template of PR content:

    • Modify the template file path to implement PR template feature (not sure work finely).
  • Update the document content of README.

Chisanan232 and others added 30 commits August 23, 2022 07:13
…pe to get the final testing code coverage report.
…usable workflow config. It's has 3 major changes:

1. Add parameters about docker operators at job 'run_integration-test'.

2. Modify the reusable workflow at job 'organize_all-test_codecov_and_generate_report'.

3. Add new input parameter 'test_type' at job 'codecov_finish'.
…sample HTTP server and its related configurations.
…on is too latest to it does not support in Python 3.6.
…ation, and add description for new input parameters.
…tegration-test' and add new option 'test_type' at job 'codacy_finish'.
…er one organizing and generate testing coverage report workflow.
🎉🎊🍾 [New Feature + Breaking Change + Refactor] (config + docs) Add new feature, integrate organizing reports features and update document.
Chisanan232 and others added 29 commits August 31, 2022 10:09
…f output and paramize the shell script arguments.
… shell script path and modify the use shell script checks the getting output.
🎉🎊🍾 [New Feature + Breaking Change + Refactor] (config + docs) Add new feature, integrate organizing reports features and update document.
@Chisanan232 Chisanan232 merged commit 8ce418d into master Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants