Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)

[previous subject: Sandbox and logs.fd.io]


Turn out the ability to archive logs from Sandbox

depends on which published macro is used.

I have confirmed (sandbox runs using [1])

that lf-infra-publish macro probably works

for csit (and vpp-csit) jobs.


So I have created [2] to switch the macro.

But I know there were attempts to use this macro

in other jobs, and it did not work. Example: [3].


Do you have any insights on lf-infra-publish usage,

will it work for (at least some) jobs,

or are there still some gotchas?




[1] https://gerrit.fd.io/r/c/ci-management/+/24374

[2] https://gerrit.fd.io/r/c/ci-management/+/24430

[3] https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-18094


From: csit-dev@... <csit-dev@...> On Behalf Of Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) via Lists.Fd.Io
Sent: Friday, January 10, 2020 4:22 PM
To: ci-management-dev@...
Cc: csit-dev@...
Subject: [csit-dev] Sandbox and logs.fd.io


I just realized jobs on Sandbox are now able

to archive their logs, to /vex-yul-rot-jenkins-2/

(-1 is for the primary Jenkins).

Example: [0].


Question: How do the logs survive the weekly cleanup?

I assume there is no (at least not weekly) cleanup on logs.fd.io;

so if somebody creates the same job next week,

the upload either replaces the whole directory,

or perhaps only replaces the conflicting files.

I guess we will see next week, as the listing shows timestamps.




[0] https://logs.fd.io/sandbox/vex-yul-rot-jenkins-2/ci-management-jjb-diff-verify/4/