Related issues: #295, #168, #66
Current artifact processing process goes like this:
- In config preprocessing (before build steps execution) all artifacts, mentioned in all steps, are collected into one big list
1a. All 'report_artifacts' are also collected to a separate list
- All artifacts are checked to be absent before build
- After build steps execution all artifacts from list are collected and reported. This process is completely detached from configuration steps, that initially contained references to artifacts.
How can the situation be improved:
- Collect and report each artifact in the end of corresponding step, only if step was executed?
- Check artifact presence right before step execution?
- Provide mechanism to add more than one artifact (or artifact glob) per step, while maintaining backward compatibility?
What difficulties are expected while implementing following improvements:
- Universum built-in artifacts are not attached to any step, but should be processed anyway
- Some artifacts may be created by previous steps while edited by a step they are announced in
- Trying to report artifacts while executing configuration steps might significantly affect project architecture and exception handling mechanisms
Related issues: #295, #168, #66
Current artifact processing process goes like this:
1a. All 'report_artifacts' are also collected to a separate list
How can the situation be improved:
What difficulties are expected while implementing following improvements: