Save file after passing a test

[MrCyjaneK]

Currently abstruse work very well for me, but I'm wondering if it is possible to make an option to save job artifacts and download them from the ci? This may be useful when somebody makes a merge request, and I'll not have to build the fork locally to check how the change looks like.

So here is a list of all features that would be cool to have:

• [ ] Storing all the files in simple structure archive directory/user/repo/branch/runid/matrixid (and a special runid called latest should be a symlink to last runid that was green.)
• [ ] Wildcard in list of files to copy, in some cases file name is set dynamically with date/last git commit id.
• [ ] Deleting old builds (keep builds for at least 5 days, and at least 5 latest versions) - and I think that it would be cool to have that feature set in abstruse config, not in abstruse.yml. (If we have 30 builds in 2 days - keep all, if we have 5 very old builds - keep all)
• [ ] An option to keep a build artifact forever would also be cool
• [ ] An option to prune old build from pull requests (timeout + manual)
• [ ] Don't store list of files in database, read it dynamically from the directory
• [ ] Create a global post-archive command that will be run on host machine (also in the config, not in abstruse.yml)

[jkuri]

Hi @MrCyjaneK! we will put this feature on the roadmap along side of caching for the next release.

[slavaGanzin]

Any progress on this?

Found abstruse just today and it awesome. But really confused with no artifacts handling. What’s the point building something if you can’t get results of your build?

Of course, you can always download it somewhere and serve it with nginx autoindex. But it seems so integral to build system itself, feels ridiculous to implement it

[MrCyjaneK]

you can use mountpoints for now