ITK/Release 4/Testing On Demand/Tutorial: Difference between revisions
(36 intermediate revisions by 4 users not shown) | |||
Line 3: | Line 3: | ||
= Overview = | = Overview = | ||
There are two steps for setting up an on-demand CDash test. If you want make your computer available to the InsightToolkit project for testing, just complete step 1. Step 2 is only available to CDash administrators. | |||
# [[#How to Setup a Client| Configure your client]] | |||
# [[#How to Schedule a Testing Task | Tell the CDash server to use your client]] | |||
= How to Setup a Client = | = How to Setup a Client = | ||
A cdash@home client | A cdash@home client is a computer that is donating time to CDash. It makes itself available to run testing tasks, such as builds for the [[ITK/Gerrit| the Gerrit review system]], that may be requested by CDash. | ||
== XML Description == | == XML Description == | ||
Place an XML description of your client machine, whose name is perhaps awesomebox, in an XML file, e.g. ''awesomebox.cdash.xml''. | |||
<?xml version="1.0" encoding="UTF-8"?> | |||
<cdash> | |||
<system> | |||
<platform>Linux</platform> | |||
<version>Ubuntu</version> | |||
<bits>64</bits> | |||
<basedirectory>/home/ibanez/Dashboards/cdashclient_workspace/</basedirectory> | |||
</system> | |||
<compiler> | |||
<name>gcc</name> | |||
<version>4.4.3</version> | |||
<generator>Unix Makefiles</generator> | |||
</compiler> | |||
<cmake> | |||
<version>2.8</version> | |||
<path>/home/ibanez/local/bin/cmake</path> | |||
</cmake> | |||
<program> | |||
<name>git</name> | |||
<version>1.7.0.4</version> | |||
<path>/usr/bin/git</path> | |||
</program> | |||
</cdash> | <allowedproject>Insight</allowedproject> | ||
</cdash> | |||
Valid values for the ''cdash/system/platform'' element and the ''cdash/system/version'' element can be observed here: | |||
[https://www.kitware.com/svn/CDash/trunk/models/clientos.php Client OS description] | |||
== CTest script == | == CTest script == | ||
A CTest script to advertise your availability to the CDash server. Pit this in a file such as ''awesomebox.ctest''. | |||
# These variables define the system and should be set | |||
# In the future CTest might be able to determine this automatically | |||
set(CDASH_SITENAME "awesomebox") | |||
set(CDASH_SYSTEMNAME "Ubuntu-64bits") | |||
get_filename_component(_thisdir "${CMAKE_CURRENT_LIST_FILE}" PATH) | |||
set(CDASH_SITE_CONFIG_FILE "${_thisdir}/awesomebox.cdash.xml") | |||
set(CDASH_TEMP_DIRECTORY "${_thisdir}/workspace/tmp") | |||
set(CTEST_EXECUTABLE "/usr/bin/ctest") | |||
set(CTEST_DROP_SITE "open.cdash.org") | |||
set(CTEST_DROP_URL "/submit.php") | |||
set(CDASH_LOOP_DURATION 64800) # Available for 18 hours / day | |||
# Now include the common setup for cdash | |||
include(cdash_client_common.ctest) | |||
== Common Script == | |||
And finally, you need to put in the same directory the common script: | |||
* [https://www.kitware.com/svn/CDash/trunk/scripts/cdash_client_common.ctest cdash_client_common.ctest] | |||
that is included at the bottom of the client script. | |||
== Run It == | == Run It == | ||
Line 46: | Line 74: | ||
you run the ctest script the usual way with CTest | you run the ctest script the usual way with CTest | ||
ctest -S | ctest -S awesomebox.ctest -V | ||
The system will reply with a message similar to | The system will reply with a message similar to | ||
Line 54: | Line 82: | ||
Submit files (using http) | Submit files (using http) | ||
Using HTTP submit method | Using HTTP submit method | ||
Drop site:http:// | Drop site:http://open.cdash.org/submit.php?sitename=awesomebox&systemname=Ubuntu-64bits&submitinfo=1 | ||
Uploaded: /home/ibanez/Dashboards/cdashclient/cdash-home/ | Uploaded: /home/ibanez/Dashboards/cdashclient/cdash-home/awesomebox.cdash.xml | ||
Submission successful | Submission successful | ||
SiteId=13 | SiteId=13 | ||
Line 64: | Line 92: | ||
The client will ping the server every 30 seconds (this value may change in the future) to check if the server has any new tasks for the client. | The client will ping the server every 30 seconds (this value may change in the future) to check if the server has any new tasks for the client. | ||
= How to Schedule Testing Task = | = How to Schedule a Testing Task = | ||
In order to schedule a testing task in CDash you should execute the following steps: | In order to schedule a testing task in CDash you should execute the following steps: | ||
== Login into CDash == | |||
Go to the CDash page of your administrator account | |||
* http://open.cdash.org/user.php | |||
== Select the Scheduling Icon == | |||
* Click on the icon of a Floppy disk with a Gear on top | * Click on the icon of a Floppy disk with a Gear on top | ||
** Marked as "Schedule Build" | ** Marked as "Schedule Build" | ||
Line 77: | Line 108: | ||
[[File:ITK-testing-on-demand.png|400px]] | [[File:ITK-testing-on-demand.png|400px]] | ||
* This will show the available | * This will show the available machines and their platform features. | ||
** http:// | * The "Schedule Build" icon is available only to CDash users whose project role is "project administrator." | ||
* If you still don't see it as Project Administrator, make sure the [http://public.kitware.com/Wiki/CDash:Build_Management $CDASH_MANAGE_CLIENTS variable is '1'] in your cdash/config.php. | |||
Line 88: | Line 120: | ||
[[File:ITK-testsing-on-demand-03.png|400px]] | [[File:ITK-testsing-on-demand-03.png|400px]] | ||
== Select a Client == | |||
Select a client or clients by clicking on the | |||
* Architecture list | |||
* Compiler list | |||
and finally going to the bottom of the interface and clicking on the "Schedule" button. |
Latest revision as of 04:43, 31 August 2014
Overview
There are two steps for setting up an on-demand CDash test. If you want make your computer available to the InsightToolkit project for testing, just complete step 1. Step 2 is only available to CDash administrators.
How to Setup a Client
A cdash@home client is a computer that is donating time to CDash. It makes itself available to run testing tasks, such as builds for the the Gerrit review system, that may be requested by CDash.
XML Description
Place an XML description of your client machine, whose name is perhaps awesomebox, in an XML file, e.g. awesomebox.cdash.xml.
<?xml version="1.0" encoding="UTF-8"?> <cdash> <system> <platform>Linux</platform> <version>Ubuntu</version> <bits>64</bits> <basedirectory>/home/ibanez/Dashboards/cdashclient_workspace/</basedirectory> </system> <compiler> <name>gcc</name> <version>4.4.3</version> <generator>Unix Makefiles</generator> </compiler> <cmake> <version>2.8</version> <path>/home/ibanez/local/bin/cmake</path> </cmake> <program> <name>git</name> <version>1.7.0.4</version> <path>/usr/bin/git</path> </program> <allowedproject>Insight</allowedproject> </cdash>
Valid values for the cdash/system/platform element and the cdash/system/version element can be observed here: Client OS description
CTest script
A CTest script to advertise your availability to the CDash server. Pit this in a file such as awesomebox.ctest.
# These variables define the system and should be set # In the future CTest might be able to determine this automatically set(CDASH_SITENAME "awesomebox") set(CDASH_SYSTEMNAME "Ubuntu-64bits") get_filename_component(_thisdir "${CMAKE_CURRENT_LIST_FILE}" PATH) set(CDASH_SITE_CONFIG_FILE "${_thisdir}/awesomebox.cdash.xml") set(CDASH_TEMP_DIRECTORY "${_thisdir}/workspace/tmp") set(CTEST_EXECUTABLE "/usr/bin/ctest") set(CTEST_DROP_SITE "open.cdash.org") set(CTEST_DROP_URL "/submit.php") set(CDASH_LOOP_DURATION 64800) # Available for 18 hours / day # Now include the common setup for cdash include(cdash_client_common.ctest)
Common Script
And finally, you need to put in the same directory the common script:
that is included at the bottom of the client script.
Run It
you run the ctest script the usual way with CTest
ctest -S awesomebox.ctest -V
The system will reply with a message similar to
Cannot create directory /Testing/Temporary Cannot create log file: LastSubmit.log Submit files (using http) Using HTTP submit method Drop site:http://open.cdash.org/submit.php?sitename=awesomebox&systemname=Ubuntu-64bits&submitinfo=1 Uploaded: /home/ibanez/Dashboards/cdashclient/cdash-home/awesomebox.cdash.xml Submission successful SiteId=13 2: Nothing to do... 22: Nothing to do... ...
The client will ping the server every 30 seconds (this value may change in the future) to check if the server has any new tasks for the client.
How to Schedule a Testing Task
In order to schedule a testing task in CDash you should execute the following steps:
Login into CDash
Go to the CDash page of your administrator account
Select the Scheduling Icon
- Click on the icon of a Floppy disk with a Gear on top
- Marked as "Schedule Build"
- This will show the available machines and their platform features.
- The "Schedule Build" icon is available only to CDash users whose project role is "project administrator."
- If you still don't see it as Project Administrator, make sure the $CDASH_MANAGE_CLIENTS variable is '1' in your cdash/config.php.
The top of the web interface looks like:
and the bottom of the same page looks like:
Select a Client
Select a client or clients by clicking on the
- Architecture list
- Compiler list
and finally going to the bottom of the interface and clicking on the "Schedule" button.