Project

General

Profile

Actions
Copy link

Task #1422

closed

Sun 24 (miranda) re-purpose for developer tasks

Added by Florian Effenberger over 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Florian Effenberger
Category:
-
Target version:
Team - Q2/2016
Start date:
Due date:
% Done:

0%

Tags:
URL:

Description

The existing Sun 24 machine should be re-purposed for certain developer tasks that so far are merely undocumented and on unmaintained machines.
A tool like Jenkins or similar should be used to regularly pull or gather data and mail it around when necessary.

List of things to have there:

  1. Bugzilla statistics
  2. IZBot (#973)
  3. api.libreoffice.org
  4. docs.libreoffice.org
  5. cppcheck
  6. gerrit digest
  7. coverity
  8. lcov.libreoffice.org
  9. regression hotspots list
  10. MABs/high priority digests
  11. regression stats
  12. bibisect stats
  13. EasyHack digests
  14. committer stats
  15. download stats
  16. tinderbox stats
  17. clang warnings and plugins
  18. bazillion other things done manually on releases or elsewhere

Related issues

Related to Infrastructure - Task #973: IZBot migration to server and code publicationClosedChristian Lohmaier

Actions
Blocked by Infrastructure - Task #1421: Sun 24 reinstallationClosedAlexander Werner

Actions
Actions
Copy link
 #1

Updated by Florian Effenberger over 8 years ago

  • Blocked by Task #1421: Sun 24 reinstallation added
Actions
Copy link
 #2

Updated by Florian Effenberger over 8 years ago

  • Related to Task #973: IZBot migration to server and code publication added
Actions
Copy link
 #3

Updated by Florian Effenberger over 8 years ago

Not sure if I poked you via e-mail: Björn, can you add some more thoughts if there are any, to this ticket?

Actions
Copy link
 #4

Updated by Bjoern Michaelsen over 8 years ago

  • Description updated (diff)

Adding things from the mail:
Subject: Odd Sunday night thought - [...]
Date: Tue, 30 Jun 2015 00:16:39 +0200
Message-ID: <20150629221639.GA15123@uzi>

Actions
Copy link
 #5

Updated by Bjoern Michaelsen over 8 years ago

Ideally we should host all those jobs on a infra watched machine, if possible1. It might not be possible to do that for resources intense tasks: lets start with the easy ones. For ressource intense tasks, triggering and monitoring for failure from that host should still be something to aim for.

We should avoid reports like:

It seems this job is not running anymore for some weeks now. Was this intentional ? The host on which the job was scheduled (vm140.documentfoundation.org) appears to be down ?

http://nabble.documentfoundation.org/CppCheck-Report-Update-tp4156085p4159095.html

aka "it stopped weeks ago, we dont know why, we dont even know where it was running" in the future.

Actions
Copy link
 #7

Updated by Florian Effenberger over 8 years ago

  • Target version changed from Q3/2015 to Q1/2016
Actions
Copy link
 #8

Updated by Florian Effenberger over 8 years ago

  • Target version changed from Q1/2016 to Q4/2015
Actions
Copy link
 #9

Updated by Florian Effenberger over 8 years ago

  • Status changed from Feedback to New

I think the Sun24 (#1421) has been setup. Best is to check with Alex, so you can proceed with this ticket

Actions
Copy link
 #10

Updated by Florian Effenberger over 8 years ago

  • Target version changed from Q4/2015 to Q1/2016

Sun24 is setup, this somehow fell through the cracks - we should setup some brainstorming early next year, as Cloph is still unsure what to run on the box

Actions
Copy link
 #11

Updated by Norbert Thiebaud over 8 years ago

Florian Effenberger wrote:

The existing Sun 24 machine should be re-purposed for certain developer tasks that so far are merely undocumented and on unmaintained machines.
A tool like Jenkins or similar should be used to regularly pull or gather data and mail it around when necessary.

List of things to have there:

  1. coverity

That is running on gandalf, by caolan mostly.

  1. lcov.libreoffice.org

That is running on tb31, under jenkins control.

Actions
Copy link
 #12

Updated by Florian Effenberger about 8 years ago

With half of the quarter over, we should at least be clear now what has to run on the machine
Cloph, any status update?
Last time you felt a bit lost on the actual scope, did you manage to clarify that in the meantime?
If not, whom could you poke to move this ticket forward? The box is sitting there mostly unused, and Björn had some great ideas, so I'd love to drive this forward
There might be some overlap with the Dashboard (https://blog.documentfoundation.org/blog/2015/10/01/tender-for-design-and-implementation-of-all-about-libreoffice-community-and-developer-dashboard-201510-01/)

Poke me if you need further feedback - getting an idea and a roadmap to finally start implementing this is key

Actions
Copy link
 #14

Updated by Florian Effenberger about 8 years ago

Talked with Cloph again about this
Several of these items are already at TDF infra, but need to be migrated from gimli/gandalf

AI Cloph:
  1. identify further services that are not yet inside TDF infra -> in Q1
  2. work on the migration from gimli/gandalf together w/ Alex
Actions
Copy link
 #15

Updated by Florian Effenberger about 8 years ago

  • Target version changed from Q1/2016 to Q2/2016
Actions
Copy link
 #16

Updated by Florian Effenberger over 7 years ago

Now does greylog

Actions
Copy link
 #17

Updated by Florian Effenberger over 7 years ago

  • Subject changed from Sun 24 re-purpose for developer tasks to Sun 24 (miranda) re-purpose for developer tasks
Actions
Copy link
 #18

Updated by Florian Effenberger over 7 years ago

  • Assignee changed from Christian Lohmaier to Florian Effenberger
Actions
Copy link
 #19

Updated by Florian Effenberger over 7 years ago

  • Status changed from New to Closed

The Sun24 is in good use now, but the other part of the ticket is not unimportant - moved to #2124

Actions
Copy link

Also available in: Atom PDF