Introduction
Understanding component interactions
When to use the CloudBees Build Acceleration cluster
Before you install
IntroductionAdditional Linux installation informationInstalling the Cluster Manager on LinuxInstalling Electric Agent/EFS on LinuxInstalling Electric Make on LinuxPath settings
IntroductionAdditional Windows installation informationInstalling the Cluster Manager on WindowsInstalling Electric Agent/EFS on WindowsInstalling Electric Make on Windows
Installing CloudBees Build Acceleration silently
Additional installation options
Installing JDBC drivers for MySQL or Oracle databases
Migrating an eMake-only installation
Installing the backward-compatible eMake package
Uninstalling CloudBees Build Acceleration from Linux
Uninstalling CloudBees Build Acceleration from Windows
Uninstalling CloudBees Build Acceleration silently
Introduction
Configuring CloudBees Build Acceleration on Linux
IntroductionWindows notesRegistry information
IntroductionChanging log locationsDisabling agents by defaultSetting up user authenticationSetting up email notificationAdding custom protocol mismatch error textUsing the database connection monitor
Configuring agent log rotation
Changing the disk cache directory or agent temporary storage location
Default directories
Logging in and enabling licensing
Installing an Apache server certificate
Stopping, starting, or restarting the Cluster Manager service
Configuring CloudBees Build Acceleration to run in Docker containers
IntroductionConfiguring your cloud platform for agent cloud burstingChoosing a machine to run eMakeConfiguring agent cloud bursting resourcesChecking the agent cloud bursting setup
Enabling automatic scaling of the number of agents
Configuring eMake and agents for multiple interface communications
Introduction
IntroductionBreakpointsCluster Manager administration toolsecconfigecagent toolsecinstconfeclockrunagent.local file
IntroductionCleaning up dataDeleting from the builds listManaging the message logSecuring the Cluster Manager databaseConfiguring the databaseBacking up a databaseEnabling LDAPImporting a licenseUsing comments
IntroductionStopping buildsDeleting buildsCreating build classesEditing Build ClassesDeleting build classes
IntroductionSetting the agent allocation policyUnderstanding a cluster sharing policyModifying the number of agents per hostEnabling agentsDisabling agentsTesting agentsDeleting agents
IntroductionCreating resourcesEditing resourcesDeleting resources
IntroductionCreating filtersEditing filtersDeleting filters
IntroductionGenerating reportsAdding custom reports
IntroductionThe home pageBuildsBuild detailsBuild classesBuild class detailsBuild classes - create or edit a build classAgentsAgent detailsResourcesResource detailsResources - create or edit a resourceReportsServer loadRealtime server metricsMessagesMessage policiesCloudCloud credentialsView cloud credentialsCreate or edit cloud credentialsCloud messagesAdministrationFiltersFilters - create or edit a filterPermissionsEdit User PermissionsEnable UserEdit group permissionsEnable groupUsersUsers - create or edit a local userUser passwordGroupsGroups - create or edit a local groupAdd new user to groupUser settings - view or edit user settingsServer settingsLicenses
Error code information
Introduction
Understanding component interactions
Virtualization
Understanding build parts
Setting up CloudBees Build Acceleration
Invoking Electric Make
Setting the Electric Make root directory
Configuring tools
Tools that access or modify the system registry
Configuring environment variables
Setting the Cluster Manager host and port
Setting Electric Make emulation
Electric Make command-line options, environment variables, and configuration file
CloudBees Build Acceleration sample build
Simulating builds
Using build classes
Using priority pools
Using the proxy command
Configuring TLS between eMake and agents
Building multiple targets simultaneously
Using Electric Make variables
Using the ninja build system
Specifying pragmas in an addendum file
Terminating a build
Shutting down cluster hosts during builds
IntroductionUnsupported GNU Make options and featuresUnsupported NMAKE optionsCommands that read from the consoleTransactional command outputStubbed submake outputHidden targetsWildcard sort orderDelayed existence checksMultiple remakes (GNU Make only)NMAKE inline file locations (Windows only)How eMake processes MAKEFLAGS
IntroductionOptimizing Android build performanceDependency optimizationJob cachingJob caching for katiParse avoidanceJavadoc cachingSchedule optimizationRunning a local job on the Make machineSerializing all Make instance jobsManaging temporary files
IntroductionCloudBees Build Acceleration eDependCloudBees Build Acceleration ledger fileManaging the history data fileConflicts and conflict detection
Annotation
IntroductionClearCaseCoverityCygwin (Windows only)EclipseBitBake
Electrify
IntroductionAgent issuesElectric Make debug log levelsUsing the annotation file to troubleshoot builds
Introduction
Installing Insight
Annotation
Starting Insight
Using Insight with BitBake builds
IntroductionAgents and jobsNavigationIntroductionLegendJob summaryZoomReplayMonitor live build
IntroductionBuild propertiesJob details dialogMake details dialogSearching for jobsViewing all jobsUsing the hyperlog
IntroductionGenerating reportsAnnotation differences reportBuild manifest reportBuild metrics reportBuild summary reportCluster sharing reportDerived files analysis reportElectricSimulator reportExport timeline reportFiles modified multiple times reportJob stats reportJob time by type reportJobs by agent reportJobs by file reportLongest jobs reportLongest serial chain reportMakefile manifest reportMetric differences reportMost read files reportRoot conflicts reportSerialization analysis reportSubmake stub reportTerminator lag reportWhy rebuild reportCommand-line enabled reportsCreating custom reports
Understanding build performance
Annolib programmer’s reference

Stopping, starting, or restarting the Cluster Manager service

2 minute read

To apply any changes that you made in the accelerator.properties file, you must restart the Cluster Manager service. These changes include disabling agents by default, enabling LDAP or Active Directory authentication, setting up email notification, adding custom protocol mismatch error text, reconfiguring the database connection monitor settings , and enabling resource management . You must also restart the service if you use a MySQL or Oracle database and have installed the JDBC driver for that database.

Red Hat Enterprise Linux

  1. Sign in as root.

  2. Stop, start, or restart the service.

    • To stop the service, enter service clustermanager stop.

    • To start the service, enter service clustermanager start.

    • To restart the service, enter service clustermanager restart.

SUSE Linux Enterprise Server

  1. Sign in as root.

  2. Stop, start, or restart the service.

    • To stop the service, enter /etc/init.d/clustermanager stop.

    • To start the service, enter /etc/init.d/clustermanager start.

    • To restart the service, enter /etc/init.d/clustermanager restart.

Ubuntu Linux

  1. Sign in as root.

  2. Stop, start, or restart the service.

    • To stop the service, enter /etc/init.d/clustermanager stop.

    • To start the service, enter /etc/init.d/clustermanager start.

    • To restart the service, enter /etc/init.d/clustermanager restart.

Windows

Using the Windows command line

  1. Sign in as an administrator.

  2. Open a command prompt.

  3. Stop, start, or restart the service.

    • To stop the service, enter net stop "CloudBees Build Acceleration Cluster Manager".

    • To start the service, enter net start "CloudBees Build Acceleration Cluster Manager".

    • To restart the service, enter net stop "CloudBees Build Acceleration Cluster Manager" && net start "CloudBees Build Acceleration Cluster Manager".

Using the Windows Services console

  1. Sign in as an administrator.

  2. Open a command prompt and enter services.msc.

    The Services console appears.

  3. Stop, start, or restart the service.

    • To stop the service, click CloudBees Build Acceleration Cluster Manager and click Stop.

    • To start the service, click CloudBees Build Acceleration Cluster Manager and click Start.

    • To restart the service, click CloudBees Build Acceleration Cluster Manager and click Restart.

  4. Sign in as an administrator.

  5. Stop, start, or restart the service.

    • To stop the service, click Start > Control Panel > Administrative Tools, double-click Services, then click CloudBees Build Acceleration Cluster Manager > Stop.

    • To start the service, click Start > Control Panel > Administrative Tools, double-click Services, then click CloudBees Build Acceleration Cluster Manager > Start.

    • To restart the service, click Start > Control Panel > Administrative Tools, double-click Services, then click CloudBees Build Acceleration Cluster Manager > Restart.

  6. Sign in as an administrator.

  7. Stop, start, or restart the service.

    • To stop the service, click Start > Control Panel > Administrative Tools > Services > CloudBees Build Acceleration Cluster Manager > Stop.

    • To start the service, click Start > Control Panel > Administrative Tools > Services > CloudBees Build Acceleration Cluster Manager > Start.

    • To restart the service, click Start > Control Panel > Administrative Tools > Services > CloudBees Build Acceleration Cluster Manager > Restart.

Installing an Apache server certificate
Configuring CloudBees Build Acceleration to run in Docker containers