Ansible Role: serdigital64.devops.dops_jenkins¶

Purpose¶

Manage Jenkins server

Supported features in the current version:

• Deploy application. Packages are defined in the variable dops_jenkins_profiles.
• Control application subsystem services. Services are defined in the variable dops_jenkins_subsystems.
• Configure application. Options are defined in the end-state: dops_jenkins_server_options
• Resolve dependencies
  • Install OpenJDK
  • Install daemonize tool
• Add OS level firewall rules

The dops_jenkins Ansible-Role is part of the A:Platform64 project and is available in the devops Ansible-Collection.

Usage¶

The following example is an Ansible Playbook that includes all the supported features:

use this link if viewing the doc on github

---
- name: "DevOps / Jenkins / Usage example"
  hosts: "localhost"
  gather_facts: true

  tasks:
    - name: "Example: Install Jenkins, configure service, start server"
      vars:
        dops_jenkins:
          resolve_prereq: true
          deploy: true
          setup: true
          control: true
        dops_jenkins_subsystem:
          enabled: true
          status: "started"
        dops_jenkins_server_options:
          port: "8080"
          listen_address: ""
        dops_jenkins_firewall:
          zone: "public"
      ansible.builtin.include_role:
        name: "serdigital64.devops.dops_jenkins"
...

The playbook can be run by executing:

# Set ANSIBLE_COLLECTIONS_PATHS to the default install location. Change as needed.
ANSIBLE_COLLECTIONS_PATHS="${HOME}/.ansible/collections"
ansible-playbook "${ANSIBLE_COLLECTIONS_PATHS}/ansible_collections/serdigital64/devops/playbooks/dops_jenkins.yml"

Role Parameters¶

Actions¶

• Use action-parameters to control what tasks are enabled for the role to execute.
• Parameters should be declared as task level vars as they are intented to be dynamic.

dops_jenkins:
  resolve_prereq:
  deploy:
  setup:
  control:

End State¶

• Use end-state parameters to define the target state after role execution.
• Parameters should be declared in host_vars or group_vars as they are intended to be permanent.

dops_jenkins_application:
  name:
  type:
  version:
  installed:
dops_jenkins_subsystem:
  enabled:
  status:
dops_jenkins_server_options:
  port:
  listen_address:
dops_jenkins_firewall:
  zone:

Deployment¶

OS Compatibility¶

The operating system compatibility list is defined in the variable: dops_jenkins_platforms

Dependencies¶

• Ansible Collections:
  • serdigital64.backup
    • bkp_archive
  • serdigital64.system
    • sys_package
    • sys_repository
  • serdigital64.development
    • dev_java
• OS:
  • SystemD
  • Daemonize
• Packages:
  • OpenJDK11

Prerequisites¶

The Ansible engine must be already installed and configured for privileged access and remote execution.

In addition the following prerequisites can be automatically solved when running the playbook by setting the role action: resolve_prereq: true

• Package manager for the target application is installed and enabled.

Installation Procedure¶

Manually install Ansible Collections from the Ansible Galaxy repository:

ansible-galaxy collection install --upgrade serdigital64.devops

Automatic installation is also available by deploying A:Platform64

Contributing¶

Help on implementing new features and maintaining the code base is welcomed.

Please see the guidelines for further details.

Author¶

• SerDigital64

License¶

Apache-2.0