|
Command |
Description |
|---|---|
|
date |
Show the current date and time |
|
cal |
Show the month calendar # cal à Shows current month of the calendar # cal nav 1979 à Shows particular month & year of the calendar |
|
uptime |
Show current uptime (System up and running) |
|
whoami |
Who you are logged in as |
|
finger |
Display information about the user |
|
users/id |
Shows user information |
|
man |
Shows manual of a command Ex: man cat |
|
username |
Shows your username |
|
who/w |
Display who is online in a server |
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