Sandbox and logs.fd.io


Andrew Grimberg
 

On 2020-01-10 07:21, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at
Cisco) via Lists.Fd.Io wrote:
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?
Looks like an oversight on our part. We'll get the nexus side cron job
in place!

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.
Yes, new file would trump old file, but we shouldn't have them surviving
the clean-up time, so we'll get it fixed.

[0]
https://logs.fd.io/sandbox/vex-yul-rot-jenkins-2/ci-management-jjb-diff-verify/4/
--
Andrew J Grimberg
Manager Release Engineering
The Linux Foundation


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

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.

 

Vratko.

 

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