root
/
public
mirror of https://github.com/01-edu/public.git
14
27
Fork 0
Code Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
5831 Commits
41 Branches
11 Tags
349 MiB
 
 
 
 
 
 
Tree: 51a5af45f7
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '51a5af45f7'
${ noResults }
public/subjects/java/projects/sharpen-it
zanninso b631b2c4e0
docs: adding subject,audit and the env files (#2394) 		10 months ago
..
audit docs: adding subject,audit and the env files (#2394) 10 months ago
README.md docs: adding subject,audit and the env files (#2394) 10 months ago
env.zip docs: adding subject,audit and the env files (#2394) 10 months ago

README.md

Sharpen-It

Objectives

In this project, your task is to finalize the provided environment for your project, applying coding best practices to enhance clarity and cleanliness.

Instructions

You have to download this Environment, then you will find two folders, one for Jenkins and another for SonarQube. Your goal is to finish the given infrastructure and make the environment functional and compliant with the below requirements.

Jenkins

  • Build and run the Jenkins Docker image.

  • Install missing plugins.

  • Set up credentials to access your repository.

  • Fix the provided pipeline to build and test the back-end and front-end

  • Complete and rectify the configuration for deployment.

  • Finalize the configuration for the rollback strategy.

  • Configure your repository to trigger the CI/CD pipeline for every approved pull request (PR).

  • Configure Jenkins to automatically merge a new PR if the build is successful during deployment.

💡 Feel free to use GitHub or GitLab for environment configuration.

SonarQube

  • Run the provided Docker Compose for SonarQube.

  • Complete the configuration to integrate SonarQube with your repository.

  • Ensure SonarQube runs regularly for continuous monitoring of code quality and security.

  • Implement a code review and approval process to prevent Jenkins CI/CD pipeline execution in case of reported issues.

💡 Use the provided sonar.properties file or configure SonarQube through the web interface.

Testing

Your CI/CD setup will be assessed based on:

  • Successful and automated fetching of the latest code changes.

  • Effective implementation of automated tests and proper responses to their outcomes.

  • Sound deployment strategies, ensuring smooth transitions of new versions into live environments.

  • Immediacy and accuracy of build and deployment.

Resources