tencent cloud

How do I access a local Jenkins instance in a custom build node?

Step 1: Access Jenkins

1. First, you must set your device as a custom build node access point.
2. To avoid exposing ports, Jenkins instances started by CODING-CI custom nodes only listen to the local loopback address (127.0.0.1) by default. The default listener port is 15740. In this case, you can only access Jenkins from the build node machine through localhost or 127.0.0.1. The specific access address is <http: localhost:15740="">.
3. If you cannot access Jenkins, run the command cat ~/.coding/cci-agent.yml to see the port (publicPort).
4. If you want to access Jenkins from outside the build node, run the up command to launch the program and add the --jserver 0.0.0.0 parameter. At the same time, you can use --jport to specify the listening port. Assuming the build node IP address is NODE_IP and the listening port is PORT, the access address will be <http: node_ip:port="">.

Step 2: Jenkins login token

Enter the Jenkins access address in your browser to view the login page.

Here, we assume the Jenkins username and password are coding and 11bf48c0403ec88231b530b5f98a113cad. You can run the ./cci-agent up -h command.

How do I install plugins in custom build nodes?

Custom build nodes that use the open-source software Jenkins as their build engines can use the over 1,000 plugins Jenkins provides for build, deployment, and automated operations. By default, CODING CI custom build nodes only have the most common Jenkins plugins. You can manually install other plugins as needed.

1. First, sign in to Jenkins.
2. After you sign in to Jenkins, you will see the Jenkins management interface. Go to Manage Jenkins > Manage Plugins.
3. In the menu on the left, click Manage Jenkins.
   
4. On the page, select Manage Plugins.
   
5. Open the Plugin Manager page.
   
6. On the Plugin Manager page, find the Available tab, select the plugins to install, and click Download now and install after restart at the bottom. On the Update Center page that pops up, select Restart Jenkins when installation is complete. Wait for Jenkins to install the plugins and automatically restart. You can now use the plugins.
   

How do quotas work for custom build nodes?

• Access custom nodes are not limited by CODING team quotas.
• Custom build nodes are not counted towards the team's weekly build quota.
• Custom build nodes are not limited by the team's parallel operation quota.
• Custom build nodes are not limited by timeout quotas.

How do caches work for custom build nodes?

A build plan configured with a custom build node pool will use the build node's own cache.

For a build plan executed by custom build nodes, each execution creates an independent WorkSpace, which is cleared after the build is completed. Files produced outside of the workspace during the build process are retained (such as files in the global cache for maven, npm, and other artifact repositories).

How do I re-register cci-agent?

Under normal conditions, if you repeatedly register cci-agent on a machine, you will be prompted that the node is already registered, and you must delete the registered node before registering it again.

This is because you must provide a config directory (default: ~/.config) and a port number (default: 15740) when registering a node. To re-register a node, manually specify a non-conflicting config directory and port number.

Before performing this operation, you must have already applied for a project token password with permissions for the build node by going to Project Settings > Developer Options > Project Token.

In the following example, we use ~/.coding2 and port 15741 to re-register a node.

./cci-agent init --config ~/.coding2 --pt 

./cci-agent up --config ~/.coding2 --jport 15741

Custom node exceptions

Custom node operating system: CentOS Minimal Install

If your custom node Jenkins fails to start and the warning below is shown, it may be because the node's operating system is CentOS (Minimal Install), and the Jenkins webpage relies on some graphical components.

To solve this problem, run the following command:

yum install fontconfig

Abnormal status handling

In actual production, unstable factors such as the client's network environment or a missing configuration environment can affect access to custom build nodes. The list below provides the methods used to handle abnormal statuses.

Deleted build node pool

"In Use" build node deleted

"In Use" build node is offline

Note：

The build node may be offline due to the unstable network of the client.

After going offline, the client (build node) will attempt to reconnect. The server will retry the operation after the client reconnects.

• If the operation times out (after three minutes), the build node is judged to be offline and the build task is marked as failed.
• Upon successful reconnection, the client will continue to report build content.

  Location	Build Record Error Prompt	Handling Method
  Build tasks in queue	-	Unaffected, the build tasks in the queue have not been assigned specific build nodes and will remain in the queue until a valid build node is found.
  Initializing, preparing build, building	Build node xxx offline	Build tasks in these statuses will fail immediately.

Configured build pool has no accessible nodes

Build plan authorization canceled