- In Linux, the top level directory represented by “/”. It is also known as ROOT directory or Parent directory. (The root account is like a system administrator account. It provides you full control of the system. You can create and maintain user accounts, assign different permission for each account, etc.)
- The home directory for root user is “/root”. It is also known as Super user. It provides working environment for root user.
- The home directory for all other users is “/home”. It provides working environment for all other users.
- The default software’s are installed in “/usr” (Unix Sharable Resources directory)
- The commands used by all users are stored in “/bin” whereas the commands used by Super user stored in “/sbin” directory.
- The variables data like mails, log files stored in “/var” directory
- The /tmp directory is a temporary landing place for files. All users can access this directory.
Complete CI/CD Pipeline Using GitHub, Jenkins, Maven, SonarQube, Nexus, and Docker A well-designed CI/CD pipeline plays a critical role in modern DevOps practices by automating software delivery, improving code quality, and reducing deployment risks. In this article, I will explain how I build an automated CI/CD pipeline using GitHub, Jenkins, Maven, SonarQube, Nexus Repository, Docker, and Docker Hub. Source Code Management with GitHub The CI/CD workflow begins with storing the application source code in GitHub. Developers regularly push code changes or create pull requests to collaborate on features and bug fixes. Whenever new code is pushed to the repository, GitHub triggers Jenkins automatically through a webhook. This integration helps start the CI/CD pipeline without manual intervention. Code Checkout Stage in Jenkins The first stage of the pipeline is the checkout process. Jenkins connects to the GitHub repository and pulls the latest version of the source code. ...
Comments
Post a Comment