I propose that after the test is done all the non-tracked files (the output of `git ls-files -o`) are rsync'd from the runner to GitLab CI coordinator and can be browsed with a link called 'Build artifacts' on every job page.
No code should be added to the runner, the coordinator should just add this to the build script if someone enables the 'Store build artifacts' for a job.
4 comments
[ 0.27 ms ] story [ 21.2 ms ] threadI wonder what why of uploading people want to use. Have a special directory that gets uploaded at the end of the tests?
I don't understand what you mean with test integration. GitLab CI already allows for testing and deploy jobs.
I propose that after the test is done all the non-tracked files (the output of `git ls-files -o`) are rsync'd from the runner to GitLab CI coordinator and can be browsed with a link called 'Build artifacts' on every job page.
No code should be added to the runner, the coordinator should just add this to the build script if someone enables the 'Store build artifacts' for a job.
Please let me know what you think.