Automation Scripts (Assignment #1 - GroupB)

📋 Project Overview

This repository contains automation scripts developed as part of the Cloud & DevOps Infrastructure Migration Project. Each team member will contribute a production-ready Bash script that solves a real-world DevOps/IT challenge. The project simulates a real-world DevOps environment by using GitHub, Jira, and Confluence for collaboration, code reviews, and documentation.

🎯 Objectives

• Learn and apply Linux administration & Bash scripting
• Practice Git/GitHub workflows (branching, PRs, reviews)
• Manage work using Jira Agile boards
• Maintain clear documentation on GitHub and Confluence
• Collaborate effectively as a DevOps team

📁 Repository Structure

team4techsolutions-automationscript/
├── members/
│   └── member-name/
│       └── script.sh
├── docs/
└── README.md

• members/ – each team member creates their own folder and places their script inside
• docs/ – documentation, diagrams, and supporting files
• README.md – this file

⚙️ Getting Started

1. Clone the Repository

git clone <repo-url>
cd team4techsolutions-automationscript

2. Create Your Folder

Inside the members/ directory, create a folder with your name:

mkdir members/<your-name>

Add a placeholder script:

echo "#!/bin/bash" > members/<your-name>/script.sh

3. Push Changes via Feature Branch

git checkout -b feature/<your-name>-setup
git add .
git commit -m "Added folder and placeholder script for <your-name>"
git push origin feature/<your-name>-setup

Then open a Pull Request (PR) in GitHub → request peer review → merge to main.

✅ Contribution Guidelines

• Branch Naming: feature/<short-description>
• No direct commits to main. All changes must go through a PR.
• Each PR must have at least 1 peer review before merging.
• Scripts must include:
  • Input parameters
  • Error handling & logging
  • Clear comments & documentation
  • Idempotency where possible

📖 Documentation

• GitHub: Project overview, setup instructions, script documentation
• Confluence: Project scope, timeline, architecture diagrams, team processes, lessons learned

👥 Team Members

• Emmanuel Ngufor (Team Lead)
• [Member 2 Name]
• [Member 3 Name]
• [Member 4 Name]

🏆 Grading Criteria

• Creativity & Impact (20%) – Does the script solve a real-world problem?
• Technical Quality (30%) – Code clarity, error handling, Bash best practices
• Collaboration (30%) – Jira usage, PR reviews, fair contribution
• Documentation (20%) – Clear and professional GitHub/Confluence docs

🚀 Expected Outcomes

• Real-world DevOps experience
• Production-ready Bash automation scripts
• Git, Jira, Confluence proficiency
• Strong team collaboration

📝 Member Script Documentation Template

Each member must create a personal readme file and describe the purpose and working details once their script is ready.