How to Setup JFrog Artifactory using Docker-Compose | Install Artifactory using Docker Compose | Install Artifactory using Docker Compose on Ubuntu 18.0.4

How to setup Artifactory using Docker compose?

Artifactory is open source, binary repository manager. Artifactory is the single solution for managing all the artifacts, binaries, files and containers throughout your software supply chain. 

Some of the key features of Artifactory:

• Supports 27 different package types including helm charts, docker images regardless of tech stack.
• A single source of truth for all your binaries
• Integration with all CICD tools
• role based authorization with teams to manage artifacts 
• you can create local, remote and virtual repositories

What is Docker Compose?

Compose is a tool for defining and running multi-container Docker applications. With Compose, you use a YAML file to configure your application’s services. Then, with a single command, you create and start all the services from your configuration. Since Docker Compose lets you configure related containers in a single YAML file, you get the same Infrastructure-as-Code abilities as Kubernetes. But they come in a simpler system that’s more suited to smaller applications that don’t need Kubernetes’ resiliency and scaling.

 

The purpose of docker-compose is to function as docker cli but to issue multiple commands much more quickly. To make use of docker-compose, you need to encode the commands you were running before into a docker-compose.yml file

 

Run docker-compose up and Compose starts and runs your entire app.

Watch the Steps in YouTube channel: 

Pre-requisites:

• Ubuntu EC2 up and running with at least t2.medium (4GB RAM), 2GB will not work
  
• Port 8081, 8082 is opened in security firewall rule
• instance should have docker-compose installed

Change Host Name to Artifactory
sudo hostnamectl set-hostname Artifactory

Perform System update

sudo apt update

Install Docker-Compose

sudo apt install docker-compose -y

Create docker-compose.yml

this yml has all the configuration for installing Artifactory on Ubuntu EC2.

sudo vi docker-compose.yml 

(Copy the below code high-lighted in yellow color)

version: "3.3"

services:

  artifactory-service:

    image: docker.bintray.io/jfrog/artifactory-oss:7.49.6

    container_name: artifactory

    restart: always

    networks:

      - ci_net

    ports:

      - 8081:8081

      - 8082:8082

    volumes:

      - artifactory:/var/opt/jfrog/artifactory

volumes:

  artifactory:

networks:

  ci_net:

Save the file by entering :wq!

Now execute the compose file using Docker compose command to start Artifactory Container

sudo docker-compose up -d 

-d means detached mode

Make sure Artifactory is up and running

sudo docker-compose logs --follow

Once you see the message, that's it. Artifactory is been setup successfully. Now press Control C and enter to come out of the above screen.

Check Artifactory is up and running by typing below command:

curl localhost:8081

This confirms that Artifactory is up and running locally.

How to access Artifactory in the browser?

Now access Artifactory UI by going to browser and enter public dns name with port 8081

http://change to_artifactory_publicdns_name:8081

How to integrate Artifactory with Jenkins?

https://www.coachdevops.com/2023/01/how-to-integrate-artifactory-with.html

How to stop Artifactory container

sudo docker-compose down

How to Setup Self Hosted Linux Agent in Azure DevOps | How to configure Self Hosted Agent for Azure Pipelines | Create Build Agent in Azure Cloud

Let us learn how to create and configure a Self-Hosted Agent in Azure DevOps (ADO).

What is an Agent?

An agent is computing infrastructure with installed agent software that runs one job at a time.

To build your code or deploy your software using Azure Pipelines, you need at least one agent. As you add more code and people, you'll eventually need more.

When your pipeline runs, the system begins one or more jobs. 

In Azure pipelines, there are two types of build agents:

1. Microsoft-hosted agents - This is a service totally managed by Microsoft and it's cleared on every execution of the pipeline (on each pipeline execution, you have a fresh new environment).
2. Self-hosted agents - This is a service that you can to set up and manage by yourself. This can be a custom virtual machine on Azure or a custom on-premise machine inside your infrastructure. In a self-hosted agent, you can install all the software you need for your builds, and this is persisted on every pipeline execution. A self-hosted agent can be on Windows, Linux, macOS, or in a Docker container.

Pre-requisites:

• Microsoft account setup
• Azure account and subscription setup
• Create a VM(Ubuntu 18.0.4) in Azure Cloud
• Create Personal Access Token in Azure DevOps

Watch Steps in YouTube channel:

How to configure Self-hosted build agent?

1. Go to Azure DevOps dashboard - https://dev.azure.com/

2. Select your project dashboard

3. Go to your project settings

4. Click on Agent pools

Create a new Agent pool name

Enter name as Ubuntu18-VM-Pool or any name

Make sure you select Grant access permission to all pipelines

click on Ubuntu18-VM-Pool, Agents, New agent

Click on Linux

Note down the steps to configure Linux build agent.

Login to your Azure VM now.

Step #1 - Create the Agent

mkdir myagent && cd myagent

Step #2 - Download the agent

wget https://vstsagentpackage.azureedge.net/agent/2.214.1/vsts-agent-linux-x64-2.214.1.tar.gz

Step #3 - Configure the Agent

tar zxvf vsts-agent-linux-x64-2.214.1.tar.gz

List the files in the directory after extracting.

ls -al

Step #4:

Run the below command:

./config.sh

Accept the Team Explorer Everywhere license agreement now?

Type Y and enter

Step #5:

Enter server URL >
https://dev.azure.com/{yourorganization}

Step #6:

Enter authentication type (press enter for PAT) > PAT

Step #7:

Enter personal access token, generated from this step

Step #8:

Enter Agent pool

Give some name

Step #9:

Enter Agent name --> myBuildAgent_1

Step #10:

Enter work folder > enter

that's it agent is successfully configured.

Configure the Agent to run as a Service

sudo ./svc.sh install &

Execute now to run as a service

./runsvc.sh &

Check the status of build Agent

Click on Ubuntu-18-VM pool name

Click on Agents

This confirms that Build agent is successfully configured in Azure DevOps and is available to run builds.

Steps for removing Agent from the agent pool

Remove the service first

sudo ./svc.sh uninstall

./config.sh remove

To Perform Java related builds on this Agent, make sure you install Java and Maven on this VM.

Install Java 11

sudo apt-get install default-jdk -y

Maven Installation
Maven is a popular build tool used for building Java applications. Please click here to learn more about Maven. You can install Maven by executing below command:

sudo apt update && sudo apt install maven -y

Check if Maven got installed

mvn --version

How to run Ansible playbook from Jenkins pipeline job | Automate EC2 provisioning in AWS using Jenkins and Ansible Playbook | Create new EC2 instance in AWS cloud using Ansible Playbook and Jenkins Pipeline

We will learn how to create new EC2 instance using Ansible playbook and automate using Jenkins Pipeline. 

Watch Steps in YouTube Channel:

Pre-requisites:

• Ansible is installed and Boto is also installed on Jenkins instance
• Ansible plug-in is installed in Jenkins. 
• Make sure you create an IAM role with AmazonEC2FullAccess policy and attach the role to Jenkins EC2 instance.
• Playbook for creating new EC2 instance needs to be created but you can refer my GitHub Repo

Steps:

Create Ansible playbook for provisioning EC2 instance

(Sample playbook is available in my GitHub Repo, you can use that as a reference)

Create Jenkins Pipeline 

pipeline {

    agent any

    stages {

        

        stage ("checkout") {

            steps {

                        checkout([$class: 'GitSCM', branches: [[name: '*/master']], extensions: [],                                                     userRemoteConfigs: [[url: 'https://github.com/akannan1087/myAnsibleInfraRepo']]])         

            }

        }

        stage('execute') {

            steps {

                //to suppress warnings when you execute playbook    

                sh "pip install --upgrade requests==2.20.1"

                // execute ansible playbook

                ansiblePlaybook playbook: 'create-EC2.yml'

            }

        }

    }

}

Execute Pipeline

Pipeline Console output