Amazon changed the install in Linux 2. One no-longer using 'yum' See: https://aws.amazon.com/amazon-linux-2/release-notes/
sudo amazon-linux-extras install docker
sudo service docker start
sudo usermod -a -G docker ec2-user| 1. What Is a Plugin in Jenkins? | |
| A Jenkins plugin is a self-contained Java archive (.hpi or .jpi file) that extends Jenkins' core functionality. Plugins allow Jenkins to integrate with tools like Git, Docker, Maven, Slack, and even custom steps in your pipeline. | |
| They’re the backbone of Jenkins’ flexibility — you can add build triggers, post-build actions, UI elements, pipeline steps, and more. | |
| 2. Where Are Plugins Stored? | |
| Jenkins stores plugins in the following location on the controller (master) node: | |
| $JENKINS_HOME/plugins/ | |
| Each plugin is stored as a .jpi or .hpi file. |
| 1. Jenkins Plugin Manager CLI | |
| The Jenkins Plugin Manager CLI (jenkins-plugin-manager) is officially recommended, modern, and robust: | |
| - Better dependency resolution. | |
| - Officially supported by Jenkins. | |
| - YAML-based plugin configuration. | |
| 2. Step-by-step Automation Guide: |
| #!/usr/bin/env bash | |
| FILENAME=${1} | |
| # expected to be defined in the environment | |
| # - AZURE_STORAGE_ACCOUNT | |
| # - AZURE_CONTAINER_NAME | |
| # - AZURE_ACCESS_KEY | |
| # inspired by |
| # Working with a [System.IO.FileInfo] Object | |
| ## Get file object into variable | |
| PS C:\DATA> $file = Get-ChildItem C:\DATA\test.xls | |
| ## Full path name | |
| PS C:\DATA> $file.FullName | |
| C:\DATA\test.xls | |
| ## Filename including extension | |
| PS C:\DATA> $file.Name |
Amazon changed the install in Linux 2. One no-longer using 'yum' See: https://aws.amazon.com/amazon-linux-2/release-notes/
sudo amazon-linux-extras install docker
sudo service docker start
sudo usermod -a -G docker ec2-user| #!/usr/bin/env bash | |
| ### | |
| # The script uses CFN to provision a Target Group in the app-dev ALB, and creates | |
| # an instance behind that target group, after which it attaches two host-header | |
| # based rules to the HTTP/HTTPS listeners which target the newly created target group. | |
| # After the stack is up, it installs the relevant Strigo app, ssc and job-worker builds | |
| # on it for the relevant branch. | |
| # | |
| # NOTE: AWS_DEFAULT_REGION, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY must be set prior to running this. |
| #!/usr/bin/env bash | |
| URL="http://localhost:15672/cli/rabbitmqadmin" | |
| VHOST="<>" | |
| USER="<>" | |
| PWD="<>" | |
| QUEUE="<>" | |
| FAILED_QUEUE="<>" |
So HAProxy is primalery a load balancer an proxy for TCP and HTTP. But it may act as a traffic regulator. It may also be used as a protection against DDoS and service abuse, by maintening a wide variety of statistics (IP, URL, cookie) and when abuse is happening, action as denying, redirecting to other backend may undertaken ([haproxy ddos config], [haproxy ddos])