Skip to main content

Passwordless Privileges to Jenkins as sudo user

Giving Jenkins sudo privileges to write in Ubuntu involves adding the Jenkins user to the sudo group. Here's how you can do it using the usermod command:

Open a terminal on your Ubuntu machine.

  • Add the Jenkins user to the sudo group:

            sudo usermod -aG sudo jenkins

Explanation of the command:

  • sudo: Run the command with superuser privileges.
  • usermod: Modify user account properties.
  • -aG sudo: Add the user to the "sudo" group.
  • jenkins: The username of the Jenkins user.

You might also need to grant passwordless sudo access to the Jenkins user. To do this, edit the sudoers file:

            sudo visudo

  • Add the following line to the file, replacing "jenkins" with the actual username if it's different:

            jenkins ALL=(ALL) NOPASSWD:ALL

  • This line allows the Jenkins user to execute all commands with sudo privileges without being prompted for a password.
  • Save and exit the editor. In most terminal editors, you can press Ctrl + X, then Y, and finally Enter to save the changes.

Now the Jenkins user should have sudo privileges and be able to execute commands requiring elevated permissions. Keep in mind that granting passwordless sudo access should be done with caution and only for trusted users, as it could potentially introduce security risks.

Comments

Popular posts from this blog

Example of Maven project that interacts with a MySQL database and includes testing

Example Maven project that interacts with a MySQL database and includes testing To install Java, MySQL, Maven, and write a Java program to fetch table data, execute, and create a JAR file using Maven on Ubuntu, you can follow these steps: Step 1: Install Java You can install Java using the following commands: sudo apt update sudo apt install default-jre sudo apt install default-jdk Verify the installation by running: java -version Step 2: Install MySQL You can install MySQL using the following commands: sudo apt update sudo apt install mysql-server During the installation, you'll be prompted to set a root password for MySQL or you can set password at latter stage using following steps.  sudo mysql ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'password'; exit Step 3: Install Maven You can install Maven using the following commands: sudo apt update sudo apt install maven Verify the installation by running: mvn -version Step 4: Create

Maven Create and Build Artifacts

In Maven, you can create and build artifacts using the package phase of the build lifecycle. The package phase is responsible for taking the compiled code and other project resources and packaging them into a distributable format, such as a JAR (Java Archive), WAR (Web Application Archive), or other custom formats. Here are the steps to create and build artifacts using Maven: Configure the Build Output: In your project's pom.xml file, you need to configure the output of the build. This includes specifying the type of artifact you want to create (e.g., JAR, WAR) and any additional resources to include. You do this in the <build> section of your pom.xml: <build>     <finalName>my-artifact</finalName> <!-- Name of the artifact without the extension -->     <plugins>         <!-- Plugin configurations for creating the artifact -->         <!-- For example, maven-jar-plugin or maven-war-plugin -->     </plugins> </build> Depend

Maven Repositories (local, central, global)

Maven relies on repositories to manage dependencies, plugins, and other artifacts required for a project. There are typically three types of repositories in Maven: local, central, and remote/global repositories. Local Repository: Location: The local repository is located on your local development machine. By default, it's in the .m2 directory within your user home directory (e.g., C:\Users\<username>\.m2\repository on Windows or /Users/<username>/.m2/repository on macOS and Linux). Purpose: The local repository is used to store artifacts (JARs, POMs, and other files) that your machine has downloaded or built during previous Maven builds. These artifacts are specific to your local development environment. Benefits: Using a local repository improves build performance since it caches dependencies locally, reducing the need to download them repeatedly. It also ensures reproducibility by maintaining a local copy of dependencies. Central Repository: Location: The central repo