#368 task artifacts are mixed up with taskotron logs
Closed: Fixed 6 years ago Opened 7 years ago by kparal.

If you look into some artifact directory, [[ https://taskotron-dev.fedoraproject.org/artifacts/all/558374a4-dd7a-11e6-8458-525400cb0b45/ | like this one ]], you see this:

[DIR] task_output/  
    [   ] taskotron.log.gz
    [   ] taskotron-stdio.log.gz
    [   ] taskotron-overlord.log.gz
    [   ] docker-1.12.6-5.git037a2f5.fc25.log.gz 

But I would expect it to look like this:

[   ] taskotron.log.gz
[   ] taskotron-stdio.log.gz
[   ] taskotron-overlord.log.gz
[DIR] task_output/
    [   ] docker-1.12.6-5.git037a2f5.fc25.log.gz

I think our internal artifacts (taskotron log files, but we might want to add new ones in the future, like #882) should be separated from task artifacts, so that we/they don't unintentionally overwrite their/our files.

This will probably need some adjustment in buildbot steps, and most probably even some support in libtaskotron (because currently we support just a single artifactsdir that is shared for all purposes).


I'm afraid I don't have time for this now. Also if we switch from buildbot to jenkins, this might work a bit differently.

This is now resolved. Artifacts are stored per STI spec, and taskotron specific files are in taskotron subdirs.

Metadata Update from @kparal:
- Issue close_status updated to: Fixed

6 years ago

Login to comment on this ticket.

Metadata