Note that will require creating a Traceability Matrix so you know what tests to create and where to put them.
This assignment builds on the design of Assignment 1:
Builds directly on Assignment 1's foundation
Assignment 2 is a simulation of the practices performe DevOps Engineers at work running the Product Build. Here we emphasize hands-on DevOps engineering practices
Incorporates both technical skills and process management
Provides clear grading criteria
Aligns with course learning outcomes
Part of doing this assignment will be teams’ running Agile practices in class to resolve issues on the product openned by the Instructor who will play the roles of Business Analyst, Product manager and IT architect. This encourages continuous engagement through daily/weekly tasks
# CSD-4503 DevOps: Tools and Practices
Assignment 2: DevOps Pipeline Implementation and Operation
Value: 20% of final grade**
Due Date: November 11
### Overview
In this assignment, you will expand upon your Assignment 1 TypeScript application by implementing and operating a complete CI/CD pipeline process using GitHub.
You will role-play as DevOps engineers responsible for maintaining code quality, processing daily Git Issues, and ensuring smooth pipeline operation.
### Prerequisites
- Completed Assignment 1 TypeScript application
- GitHub repository with initial codebase
- Basic understanding of Git Issues and Actions
### Learning Objectives
1. Implement and maintain a CI/CD pipeline using GitHub Actions
2. Process and resolve Git Issues effectively
3. Use traceability matrix as a product roadmap to asses how to best implement code changes and testing in response to Defects and New Product Feature Requests.
5. Deploy applications using Docker containers. We will see how to set up GIT ACTIONS to containerize into a Kubernetics Container your updated code base and ftp that Container to where ever it needs to go.
- Lessons learned
- Recommendations for improvement
Deliverables
1. GitHub repository containing:
- Complete CI/CD pipeline configuration
- Jest test suite
- Docker configuration
- Technical documentation: Latex with Overleaf.com
2. Documentation package including:
- Process documentation: Instruction manual for a new Devops Engineer
- Updated traceability matrix and all other UP Artifacts
- Issue management logs
- Code review records
3. Final report (2000 words maximum)
### Grading Rubric
Your Documentation report will be presented in Latex.
Submission Guidelines
1. Ensure your GitHub repository is up-to-date
2. Submit documentation package via Moodle
3. Submit final report as PDF via Moodle
4. Include repository URL in submission
### Academic Integrity
- All work must be original
- Cite any external resources used
- Collaboration is encouraged for learning but submit individual work
- Follow Lambton College academic integrity policies
### Support Resources
- Course lecture materials
- DevOps documentation
- GitHub Actions documentation
- Jest documentation
- Docker documentation
### Tips for Success
1. Start early - pipeline setup takes time
2. Test thoroughly before submission
3. Document continuously
4. Participate actively in code reviews
5. Maintain regular issue processing schedule
To Do Work:
Start experimenting with GIT ISSUES and GIT Actions
Assignment 4: Workbook on pointing PowerBI at the GIT ISSUES Journal
Workbook on using Jest Testing Framework with TypeScript
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (