Challenge Overview
Welcome to the TOSCA Architecture | CI/CD pipeline Challenge. In this challenge, we are looking for you to create an Architectural document for the requirements listed below. No codes are required in this challenge.
Let us know any question you have!
Architectural requirements
Prepare a CI/CD documentation for the architectural design above. Feel free to update the architectural design if required.
0 Environments
- The yellow section is the TC environment.
- The section enclosed below TC environment is Wipro's environment.
- The green section is also a separate environment.
- The Purple box is a separate environment represents the client section.
1 Workflow
- The project is divided into 2 parts. Some part is with TC & some part is with Wipro.
- There will need to be a code push from TC to Wipro, these will two different environments/code repository.
- The CI/CD for all the environments should be in Jenkins. For TC CI/CD can be via git-lab-ci.yaml
- From these two code Repos (TC & Wipro), the code is pushed into the Clients Code Repo.
- From the client's repo, the code is going to be pushed into the Staging & Production environments.
The CI/CD pipeline should perform the following actions:
1.1 Test
- Test the application by calling the gradle test task that will run a unit test of the angular app
- Run the lint on the application source code.
- Run the integration test of angular app.
- Should perform screen test via Selenium.
- We do not have to get into the depts of these, we need a high-level architecture for now.
1.2 Build
- Build the application by calling gradle build.
- The build should only be created if all the test in section 1.1 Test passes.
1.3 Deploy
- Deploy the generated build to weblogic by calling the gradle goal that will do the deployment.
We need an Architecture document along with the architectural design for this CI/CD workflow. You can reuse the give arch. design in your submission.
Final Submission Guidelines
Submit a word document in OR.
- The word doc should contain Architectural Design & Architectural Descriptions.
Licenses & attribution
- Third-party assets used to build your item must be properly licensed or free for commercial use. MIT, some modified BSD, Apache 2 licenses are ok. If a library is not commercial friendly you will need to get our approval first.
- Sufficient information regarding third-party assets must be present in your documentation. This includes the author, license info and a direct link to the asset online.
FAQs
After submission as a submitter what should be my next step?
Once the challenge submission phase is over the assigned reviewers are going to review all the submissions based on the challenge scorecard. They are expected to raise all issues found in the submissions they are reviewing. After the completion of the review phase the Appeal phase status. In this phase, the submitters should go to the Online Review page, select the project & have a look at the issues raised by the reviewers. If you disagree with the reviewer on any issue/comment, raise an appeal by clicking the 'Appeal' button associated with the section and entering the appeal comment.
When & where I can see the challenge results?
After the Appeal response phase is over the results are displayed on the challenge specification page as well as on the online reivew page.