hi
DOT503_Assessment_2_SourceCode_Report_Module 8 Page 3 of 9 Task Summary In most Continuous Integration and Continuous Delivery (CI/CD) pipelines, the first three stages are Source control, Unit testing and Build automation. In this assessment you will: a) Implement the Source control stage b) Implement the Unit testing stage c) Implement the Build automation stage that performs the task of cleaning, compiling, testing and creating deployable package/executable d) Write a 1000-words report explaining the concept of Infrastructure as Code (IaC) and how it relates to DevOps practices. Please refer to the Task Instructions for details on how to complete this task. Task Instructions Although implementation of Source control stage is independent of the choice of programming language, the implementation of Unit testing and Build automation relies on the specific ASSESSMENT 2 BRIEF Subject Code and Title DOT503 - DevOps Tools Assessment Continuous integration and testing pipeline Individual/Group Individual Length Report 1000 words (+/- 10%) and Source code Learning Outcomes The Subject Learning Outcomes demonstrated by successful completion of the task below include: a) Analyse and integrate goals, terminologies, and the continuous development pipeline in a collaborative environment. b) Evaluate and critique design practices using skillsets, knowledge, and established competencies in DevOps. c) Implement best practices of Continuous Testing and Continuous Integration. Submission Due by 11:55pm AEST Sunday end of Module 8. Weighting 40% Total Marks 100 marks DOT503_Assessment_2_SourceCode_Report_Module 8 Page 4 of 9 programming language. Thus, you are first required to choose your favourite programming language along with a suitable unit testing framework and build automation tool. With your choice of programming language, unit testing framework, and build automation tool implement the followings. a) Implement Source control using Git and GitHub 1. Create a free GitHub account if you do not have one. 2. Create a simplistic application in your favourite programming language and push into GitHub. 3. Create three branches from your repository named ‘feature-x’, ‘feature-y’, and ‘feature- z’. 4. From each branch modify one of the source files so that they would lead to merge conflicts. 5. Commit your changes in each branch and push each of the branches into GitHub. 6. In GitHub, create a pull request to merge ‘feature-x’ branch into the master branch and approve the pull request. 7. From Git CLI, merge the updated master branch with ‘feature-y’ branch. Resolve the conflict and push it into GitHub. 8. In GitHub, create a pull request to merge ‘feature-z’ branch into the master branch. Resolve the conflict and complete the merge. 9. Commit your changes and push the master branch into GitHub. b) Implement Unit testing 1. Create a branch named ‘unit-test’ and checkout the newly created branch. 2. In your chosen Unit testing framework, write five test cases for your applications such that three test cases pass and two test cases fail. Modify your applications if required. 3. Add unit test files to your repository, commit the change and push the branch into GitHub. 4. In GitHub, create a pull request to merge ‘unit-test’ branch with the master branch and complete the merge. c) Implement Build automation 1. In your chosen build automation tools create a script to compile and test your application as well as making a deployable package or executable for your application. 2. Create a ‘Readme.txt’ file with instructions on how to run the build script. 3. Add the build script and the Readme.txt file to your master branch. Commit the changes and push the changes into GitHub. d) Write a report on Infrastructure as Code (IaC) 1. The report shall contain the link to your GitHub repository. 2. Explain the concept of Infrastructure as Code (IaC) and its benefits in the context of DevOps. DOT503_Assessment_2_SourceCode_Report_Module 8 Page 5 of 9 Referencing It is essential that you use appropriate APA style for citing and referencing research. Please see more information on referencing here http://library.laureate.net.au/research_skills/referencing Submission Instructions • Submit this task via the Assessment link in the main navigation menu in DOT503 – DevOps Tools. • The Learning Facilitator will provide feedback via the Grade Centre in the LMS portal. Feedback can be viewed in My Grades. Academic Integrity Declaration I declare that except where I have referenced, the work I am submitting for this assessment task is my own work. I have read and am aware of Torrens University Australia Academic Integrity Policy and Procedure viewable online at http://www.torrens.edu.au/policies-and-forms I am aware that I need to keep a copy of all submitted material and their drafts, and I will do so accordingly. http://library.laureate.net.au/research_skills/referencing http://www.torrens.edu.au/policies-and-forms DOT503_Assessment_2_SourceCode_Report_Module 8 Page 6 of 9 Assessment Rubric Assessment Attributes Fail (Yet to achieve minimum standard) 0-49% Pass (Functional) 50-64% Credit (Proficient) 65-74% Distinction (Advanced) 75-84% High Distinction (Exceptional) 85-100% Knowledge and understanding of Git and GitHub source control tools 30% Demonstrated partial or unsatisfactory knowledge and understanding of Git and GitHub. Performs less than 50% of the given tasks stated below. The tasks completed are of unsatisfactory quality. 1. All the three feature branches exist in GitHub 2. Each of the three feature branches shows at least one commit made to it 3. Branch ‘feature-x’ merged to master using a pull request in GitHub 4. Branch ‘feature-y’ merged with master from CLI, resolving the merge conflict 5. Branch ‘feature-z’ merged with the Demonstrated functional knowledge and understanding of Git and GitHub. Performs more than 50% of the given tasks stated below. The task completed are of satisfactory quality. 1. All the three feature branches exist in GitHub 2. Each of the three feature branches shows at least one commit made to it 3. Branch ‘feature-x’ merged to master using a pull request in GitHub 4. Branch ‘feature-y’ merged with master from CLI, resolving the merge conflict 5. Branch ‘feature-z’ merged with the master branch from GitHub, resolving the merge conflict Demonstrated good knowledge and understanding of Git and GitHub. Performs more than 65% of the given tasks stated below. The tasks completed are of good quality. 1. All the three feature branches exist in GitHub 2. Each of the three feature branches shows at least one commit made to it 3. Branch ‘feature-x’ merged to master using a pull request in GitHub 4. Branch ‘feature-y’ merged with master from CLI, resolving the merge conflict 5. Branch ‘feature-z’ merged with the master branch from Demonstrated advanced knowledge and understanding of Git and GitHub. Performs more than 75% of the given tasks stated below. The task completed are of very high quality. 1. All the three feature branches exist in GitHub 2. Each of the three feature branches shows at least one commit made to it 3. Branch ‘feature-x’ merged to master using a pull request in GitHub 4. Branch ‘feature-y’ merged with master from CLI, resolving the merge conflict 5. Branch ‘feature-z’ merged with the master branch from Demonstrated exceptional knowledge and understanding of Git and GitHub. Performs more than 85% of the given tasks stated below. The tasks completed are of exceptional quality. 1. All the three feature branches exist in GitHub 2. Each of the three feature branches shows at least one commit made to it 3. Branch ‘feature-x’ merged to master using a pull request in GitHub 4. Branch ‘feature-y’ merged with master from CLI, resolving the merge conflict 5. Branch ‘feature-z’ merged with the DOT503_Assessment_2_SourceCode_Report_Module 8 Page 7 of 9 master branch from GitHub, resolving the merge conflict 6. The commit messages are clear and appropriate 6. The commit messages are clear and appropriate GitHub, resolving the merge conflict 6. The commit messages are clear and appropriate GitHub, resolving the merge conflict 6. The commit messages are clear and appropriate master branch from GitHub, resolving the merge conflict 6. The commit messages are clear and appropriate Knowledge and understanding of Unit testing and unit testing tools 25% Demonstrated partial or unsatisfactory knowledge and understanding of Unit testing and unit testing tools. Performs less than 50% of the given tasks stated below. The tasks completed are of unsatisfactory quality. 1. The branch ‘unit-test’ exist in GitHub 2. The branch ‘unit-test’ contains source files for unit testings 3. There are five test cases - Three cases pass and two test cases fail 4. The commit messages are clear and appropriate 5. The branch ‘unit-test’ is merged with the master branch Demonstrated satisfactory knowledge and understanding of Unit testing and unit testing tools. Performs more than 50% of the given tasks stated below. The task completed are of satisfactory quality. 1. The branch ‘unit-test’ exist in GitHub 2. The branch ‘unit-test’ contains source files for unit testings 3. There are five test cases - Three cases pass and two test cases fail 4. The