This section provides pointers to several tutorials targetted at a specific topic. Following a general overview, the tutorials are grouped into usage roles, which match the authorisation and authentication model of ETICS.

ETICS Overview

1. Brief overview of the ETICS tool kit
   1. The different components in the ETICS service (TutorialSystemOverview)
   2. Highlights
      1. Build system (TutorialBuildSystemOverview)
      2. Test system (TutorialTestSystemOverview)
      3. User roles (TutorialRoles)
      4. Glossary (TutorialGlossary)
2. ETICS web application quick overview (WebAppHowTo)
3. ETICS client quick overview (ClientHowTo)

Pre-requisite

1. User certificates. Users should have the valid certificate in order to perfom any write operation using the etics service. To facilitate the tasks we provide you with the already operating certificates. Of course you can use your private certificates affiliated with any of the Certification Authority recohnised by EUGridpma (additional role assignment will be necessary in this case).

Roles

Developer Role

1. Checking out code
   1. How to check out code and dependencies (TutorialCheckoutBasic)
   2. Advanced checkout options (TutorialCheckoutAdvanced)
   3. Advantages/differences over using CVS clients (TutorialCheckoutCvsSemantic)
2. Building and packaging the component
   1. Locally on developers machine
      1. Basic building (TutorialLocalBuildBasic)
      2. Advanced options, including platform substitution and packaging (TutorialLocalBuildAdvanced)
   2. Using the remote build system (on demand build)
      1. Building on a remote machine (TutorialRemoteBuilds)
      2. Building on multiple platforms (TutorialMultiPlatformBuilds)
      3. Artefacts repository (TutorialArtefactsRepository)
3. Packaging
   1. Default packaging overview (TutorialPackagerBasic)
   2. Advanced packaging options (TutorialPackagerAdvanced)
   3. Using a custom spec file (TutorialPackagerCustomScripts)
4. Advanced metadata editing
   1. working with branches and different versions
5. Checking in and tagging code
   1. How to tag, check in code and commit using ETICS clients tools (TutorialTagAndCheckin)
   2. Advantages/differences over using CVS clients (TutorialCheckinCvsSemantic)
6. Registring artefacts (i.e. build products) (TutorialArtefactRegistration)
7. Editing and creating configurations (project, subsystems and components) with basic meta data (name, dependency)
   1. Using the client tools (TutorialEditingConfigurationClient)
   2. Using the web interface (TutorialEditingConfigurationWebApp)
   3. Defining build-time and runtime dependencies

Integrator Role

1. Using metadata to create meta rpms (TutorialConfigurationMetaRpmsCreation)
2. How to group configurations together into a subsystem/project configurations
   1. Basic configuration management (TutorialConfigurationManagementBasic)
   2. Advanced configuration management (TutorialConfigurationManagementAdvanced)
3. Metadata management and links between CVS tags, ETICS configuration names and package versions
   1. Highlight rule creation for traceability and show how this is enforcible in ETICS (TutorialConfigurationTagging)
4. Case studies on how ETICS can help managing distribution repositories (TutorialCaseStudies)
5. Conflict analysis between configurations, using metadata (TutorialConfigurationConflicAnalysis)

Module Administrator

1. Editing and creating modules (subsystems and components) with basic meta data
   1. Using the client tools (TutorialEditingModuleClient)
   2. Using the web interface (TutorialEditingModuleWebApp)

Release Manager Role

1. Going from development -> Alpha -> Beta -> Release Candidate -> Release (TutorialReleaseManagement)
2. Listing artefacts for a given configuration (TutorialListingArtefacts)

Specific Use Cases

This section illustrates how can the previous generic roles can be reused to perform specific tasks.

Porting Use Case

1. How to try a full build on a local machine (TutorialLocalBuildBasic + TutorialLocalBuildAdvanced)
2. How to fix porting problems when they arise (Good question )
3. How to link a remote machine to the central build system (used for continuous, nightly and on-demand builds) (TutorialNmiAddingWorkerNode + TutorialSettingUpWebAndBuildReactors)

Hackers Use Case

1. Show the different ways to download the source and build a patched package
   1. Using source tarballs
   2. Using source packages eg source rpms
   3. Using the checked out source against checked out binaries (--frombinary)
   4. Building everything from source (--fromsource)
   5. How Etics can deal with patches

Domesday Use Case

1. What to do in case of service interruption (ETICS central service availability)
   1. How do we continue to work while there is downtime on the ETICS service?
   2. How and when we should go behind ETICS and what are the implications?

Developers' Use Cases

1. The current set of developers' use cases being discussed is available at DevelopersUseCases

ETICS Service Administrator

In this section, you will learn about setting-up your own ETICS Service

1. Installing and setting-up ETICS Web Service
2. Installing and setting-up ETICS Web Application
3. Installing and setting-up ETICS NMI and Condor
4. Installing and setting-up ETICS Build and Web Reactors for continuous and nightly build (TutorialSettingUpWebAndBuildReactors)
5. Installing and setting-up ETICS MySql Database
6. Adding remote node to ETICS Service pool (TutorialNmiAddingWorkerNode)

-- LaurenceField - 05 Jul 2006

-- MebSter - 24 Jul 2006