Question 1

High Level Architecture Design - Servana Platforms

Accepted Answer

The following is a simplified architectural diagram of the Servana platform. The diagram highlights the Managed Service

Platform and how it integrates with the supporting services like the Managed Jenkins Build Service. The diagram is illustrative with elements like security groups and subnets omitted as they vary on a service level.

Components like the load balancer are shared and the VPC egress gateway. Where we have positioned the S3 buckets in the Managed Jenkins Build Service VPCs it is because access to the bucket is controlled by a role within the Managed Build Service account that would enable connectivity from the Jenkins Controller to the build infrastructure and storage buckets.

Jenkins Controllers

We offer three Jenkins Controller configurations in small, medium and large. The Jenkins controller runs on dedicated hosts with storage provided by EBS. Storage is encrypted with a KMS key and we use a dedicated KMS key for each customer. Storage including backups and artifacts are encrypted with the dedicated KMS keys.

Jenkins Agents

When a customer requests the Managed Jenkins Build Service we provide a single tenant environment with access to either a Kubernetes Build Service or standard EC2 Build Service. All build agents are ephemeral.

![](https://storage.crisp.chat/users/helpdesk/website/-/2/3/c/d/23cd236aaf7d6a00/dd069e2d-04

Question 2

Jenkins Shared Library Tutorial

Accepted Answer

Jenkins Shared Library Tutorial

Learn to build reusable, testable pipeline code that follows the DRY principle A comprehensive, production-ready guide to Jenkins Shared Libraries with working examples, tests, and Job DSL integration.

📚 Documentation

Getting Started ← Start here

Advanced Guide - Testing, Job DSL, advanced patterns

Reference - Complete examples, API, troubleshooting

Demo Repository - Working, runnable code

Getting Started

What is Jenkins Shared Library?

When we say "CI/CD as code," it should embrace modularity and reusability, following the DRY principle (Don't Repeat Yourself). Jenkins Shared Library makes this possible.

The Problem

Imagine 10 Java microservices, each with its own pipeline. The Maven build step is duplicated across all 10. When you add a service, you copy-paste the pipeline. Need to change Maven parameters? Update all 10+ pipelines manually. This is:

❌ Time-consuming
❌ Error-prone
❌ Not scalable The Solution: Write the Maven build once, reference it everywhere: ``` // Before: Duplicated in every pipeline stage('Build') { sh 'mvn clean package -DskipT

Question 3

Jenkins Shared Library Tutorial - Advanced Guide

Accepted Answer

Jenkins Shared Library - Advanced Guide

Prerequisites: Complete the main tutorial first to understand the basics. This guide covers advanced topics for mastering Jenkins Shared Libraries.

Team-Based Architecture

[](https://github.com/Servana/jenkins-shared-library-tutorial/blob/mai

Question 4

User Federation with Active Directory / LDAP

Accepted Answer

Click on ‘User Federation’ on the left pane to navigate to the user federation window. Select ‘LDAP’ from the drop-down selector to navigate further.

In the ‘Add user storage provider’ window, there is a lot to fill up. Let go through them one by one.

Select ‘Active Directory’ as the vendor to fill the fields ‘Username LDAP attribute’, ‘RDN LDAP attribute’, ‘UUID LDAP attribute’ and ‘User Object classes’ automatically.
As the connection url, use ‘ldap://’ or ‘ldaps://’ followed by domain name. Click on ‘test connection’ to see if the LDAP connection works.
Type ‘dsquery user -name ’ followed by the administrator’s name to get the ‘Bind DN’ and ‘Users DN’. Use the administrator password as the ‘Bind Credentials’ and click ‘Test Authentication’ to check whether it is correct.

Bind DN in below example is “CN=Administrator,CN=Users,DC=dhruv,DC=demo"
Users DN in below example is “CN=Users,DC=dhruv,DC=demo”

Enter if any custom user LDAP filter is required.
Periodic full and changed user sync of LDAP users to Keyclock can be enabled from sync settings.
Click on save and execute to sync users button.

![](https://storage.crisp.chat/u

Question 5

Create a Service Account to access Jenkins with cli

Accepted Answer

Step 1: Create a service user account in the StackTrack Identity Service admin console.
Step 2: Log in to Jenkins with the service account and create an API Token.
Step 3: Create a role in Jenkins for the service account with the least privileges principle. Manage Jenkins -> Manage Roles.
Step 4: Assign the new role created in Step 3 to the service account via the assign role menu in Jenkins. Assign Role Link.
Step 5: Execute the Jenkins cli with the API Token and service user login information.

A link has been kindly shared of a resource that wraps the Jenkins CLI in a shell script. Here is a link to a gist which makes this process easier.

```

!/bin/bash

Jenkins-cli wrapper see. https://www.jenkins.io/doc/book/managing/cli/

#

.installation:

curl -o ~/bin/jcli-wrapper

chmod +x ~/bin/jcli-wrapper

#

.usage:

jcli-wrapper Jenins-URL file-with-credentilas

#

.example:

jcli-wrapper https://jenkins.example.com $(realpath ~/.rcjenkins/jenkins) list-jobs

#

.tip:

you can create own wrapper with pre-defined values like:

#file: ~/bin/jcli

#!/bin/bash

jcli-wrapper https://jenkins.example.com $(realpath ~/.rcjenkins/jenkins) $@

#

.note:

content of ~/.rcjenkins/jenkins is:

{username}:{token|password}

user:123456

jenkinshost=$1 shift 1 passwdfile=$1 shift 1

if [ ! -f ~/bin/jenkins-cli.jar ] then mkdir -p ~/bin curl -o ~/bin/jenkins-cli.jar $

Question 6

Platform, Tools and Environment Documentation

Accepted Answer

This page contains code, instructions on how to access features on the build agents. If you have any questions please get support.

Generated At: 2025-10-31T13:26:48.862144 Agent Version: 1.0.0 Generation Method: automated Workflow ID: ami-workflow-41df886c

Platforms

windows_amd64

AMI ID: ami-068b7a66128a5d38e
Base OS: windows
Architecture: amd64
Description: Windows 64-bit platform
Tool Count: 22

ubuntu_amd64

AMI ID: ami-003624985569a39e8
Base OS: ubuntu
Architecture: amd64
Description: Ubuntu 64-bit platform
Tool Count: 34

ubuntu_arm64

AMI ID: ami-00838562fab8becbc
Base OS: ubuntu
Architecture: arm64
Description: Ubuntu ARM 64-bit platform
Tool Count: 21

AMI IDs by Region

windows_amd64

eu-central-1: ami-068b7a66128a5d38e
eu-west-1: ami-0dd9d4ff342336cbf
eu-west-2: ami-015e7586e5e568498
us-east-2: ami-0fdc3db03521b2b94

ubuntu_amd64

eu-central-1: ami-003624985569a39e8
eu-west-1: ami-0cd9764e5e7ab881e
eu-west-2: ami-0865e9b14b9e95505
us-east-2: ami-041e921724a912c9f

ubuntu_arm64

eu-central-1: ami-00838562fab8becbc
eu-west-1: ami-052940a3864feedeb
eu-west-2: ami-07824fea5fb42fe65
us-east-2: ami-038b322b9de6be65c

Tool Tables

Version Control

Tools for version control management

| Name | Ver

Featured Articles

Browse All Categories