Jira Introduction, Installation, Configuration, and DevOps Automation Practices

Jira is introduced as a tool for planning and tracking software development, allowing users to create projects, plan sprints, and assign tasks across teams.

The installation section covers downloading the Data Center version, selecting the deployment environment, and running the installer on a Linux server. Example commands include copying the installer via scp atlassian-jira-software-8.20.1-x64.bin [email protected]:/opt/ , adding execution permission with chmod +x atlassian-jira-software-8.20.1-x64.bin , and launching the installer ./atlassian-jira-software-8.20.1-x64.bin . The installer prompts for custom installation paths, data directories, and port configuration (e.g., HTTP port 8801, RMI port 8802) and offers to install Jira as a service.

After installation, the guide shows how to access Jira via http://serverip:8801 and obtain a license key for activation.

Jira usage practices include creating a project (linked to a GitLab group), adding modules (each corresponding to a GitLab project), configuring webhooks, managing requirements and tasks, and publishing releases that map to GitLab branches.

The automation practice demonstrates defining a workflow and integrating tools. It explains creating a Jenkins job with a webhook that receives Jira events, parsing the webhook payload, and using Groovy scripts to create GitLab branches via the GitLab API. Sample pipeline code is provided, such as:

pipeline {
    agent { label "build" }
    stages {
        stage("Process") {
            steps {
                script {
                    // process webhook data and create branches
                }
            }
        }
    }
}

Additional helper functions for creating branches, retrieving project IDs, and making HTTP requests to GitLab are also included.

The validation steps verify that creating a module and issue in Jira triggers the Jenkins pipeline, resulting in new branches appearing in GitLab.