kiegroup / kiegroup/github-action-build-chain
Implement on success/failure archiving
- Dominant language
- TypeScript
- Stars
- 94
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
For each `path` in `archive-artifacts` in the definition file, the build-chain-config reader produces an object `{path: path_to_file, on: success/failure`
We have to implement this `on` functionality. So if a job is successful then upload the artifact only if `on` is `success` otherwise if the job failed then only upload the artifact only if `on` is `failure`
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the build-chain-config reader and the artifact upload handling for archive-artifacts in the definition file. Trace how each {path, on} object is processed for successful and failed jobs. Done means artifacts are uploaded only when on matches the job outcome, with tests covering both outcomes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100