Allow anyone, or restricted users to add slaves and have them auto-tested to ensure they are setup correctly.

What that will entail is having a patch that will force a return of every error code, exact ones like "Failed to checkout CVS...". Once a server is confirmed then an admin can activate it.

This will greatly enhance the process of adding slaves. Possibly later mechanism for removing slaves once people no longer won't there boxed used for testing. Maybe a "Manage slaves" page for slave owners.

CommentFileSizeAuthor
#4 pifr_auto_test.patch4.42 KBboombatower

Comments

boombatower’s picture

Title: Public slave queue and auto test slave » Public client queue and auto test client
Version: 6.x-1.x-dev » 6.x-2.x-dev
boombatower’s picture

Assigned: Unassigned » boombatower

Public client queue has been implemented.

boombatower’s picture

Status: Active » Postponed
StatusFileSize
new4.42 KB

Initial stab at auto test code, postponing until #360909: Keep track of project nid so that commit log and cvs can be checked for individual projects is complete.

Include #346025: Check version number of client before allowing it to run tests in tests.

Also should provide a mechanism to force all clients to be tested upon update of PIFR code and/or manual reset.

boombatower’s picture

Project client check:

  • Hit project server xmlrpc.php. (system.getCapabilities)
  • Parse commit information.
  • ...
boombatower’s picture

Status: Postponed » Active

Back to working on auto confirmation (testing) of clients.

boombatower’s picture

Status: Active » Fixed

Completed code required to initiate client test.

Result code will be in separate push.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.