We would like to have a directory named Samba created on https://artifacts.ci.centos.org to upload job results periodically.
Metadata Update from @arrfab: - Issue tagged with: centos-ci-infra, feature-request, need-more-info
artifacts.ci.centos.org is tied to ci.centos.org , which was considered legacy and also supposed to disappear. It wouldn't make sense to add new tenants there if it goes away soon, and we should internally review if ci tenants should push the artifacts they want to keep on their own storage space somewhere, or if we can provide a S3 bucket with a policy that would clean on regular basis.
To be discussed/reviewed
Discussed on IRC and to unblock for now (while we should have another solution further down the road), I created a samba user and samba rsync target/module on artifacts.ci.centos.org (internal to CI vlan) and you can use your duffy-api-key as password for that rsync user/module.
samba
Let us know if that works and unblocks you for now
Metadata Update from @arrfab: - Issue assigned to arrfab
To chime in - we (systemd) would also welcome a replacement to artifacts.c.c.org (if/when it goes away), as currently we use it as a cache for a couple of libvirt images.
I managed to move another job, which used the artifacts storage (a simple Copr repo mirror via reposync), directly into Jenkins by (ab)using job artifacts, and then sharing the "last successful build" artifact URL with other jobs. It works but it's just... ugly.
Discussed on IRC and to unblock for now (while we should have another solution further down the road), I created a samba user and samba rsync target/module on artifacts.ci.centos.org (internal to CI vlan) and you can use your duffy-api-key as password for that rsync user/module. Let us know if that works and unblocks you for now
Yes. I can confirm that rsync is successful with user/module samba using duffy-api-key.
Note: As mentioned in wiki, first 13 characters of duffi-api-key was not accepted as rsync password.
yeah, problem is that even head of that wiki page says "This page is not maintained" and clearly showing CentOS 5 and 6 testing in CI :-) Also, no new tenants were manually added (there is not even a process for it) either. Let's close this ticket as "it works for you" but let's create a new one to come with a new solution for artifacts, instead of the legacy and manual process
Metadata Update from @arrfab: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.