4paradigm / 4paradigm/OpenMLDB
Automatic packaging openmldb-import after tag creation
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
### Expected Behavior
Automatic packaging `openmldb-import` after creating a release tag.
### Possible Solution
Adding packaging code into [`steps/package_openmldb.sh`](https://github.com/4paradigm/OpenMLDB/blob/main/steps/package_openmldb.sh)
### Reference
- `openmldb-import` [module](https://github.com/4paradigm/OpenMLDB/tree/main/java/openmldb-import)
- CICD and auto-release [code](https://github.com/4paradigm/OpenMLDB/blob/main/.github/workflows/cicd.yaml)
Contributor guide
Research direction
Examine the existing packaging script at steps/package_openmldb.sh and the openmldb-import module in java/openmldb-import. Understand the CI/CD workflow in .github/workflows/cicd.yaml to see where the packaging step is triggered. The goal is to modify the script to include the Java module in the release artifacts, then test the packaging locally or in a CI run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, shell
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 40/100