Changes in handling logs from (centos) regressions and smoke

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello folks,

We're making some changes in how we handle logs from Centos regression and smoke tests. Instead of having them available via HTTP access to the node itself, it will be available via the Jenkins job as artifacts.

For example:
Smoke job: https://build.gluster.org/job/smoke/38523/console
Logs: https://build.gluster.org/job/smoke/38523/artifact/ (link available from the main page)

We clear out regression logs every 30 days, so if you can see a regression on build.gluster.org, logs for that should be available. This reduces the need for space or HTTP access on our nodes and for separate deletion process.

We also archive builds and cores. This is still available the old-fashioned way, however, I intend to change that in the next few weeks to centralize it to a file server.

--
nigelb
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux