Skip to main content

jenkins master ip address changed and slaves node disconnected

Please refer to the below:

In your jenkins Dashboard go to Manage Jenkins > Configure System

Under Jenkins Location set the Jenkins URL to the new IP address of your server computer

Save changes

On jenkins dashboard under Build Executor Status click on your slave node

Click launch button to download new slave agent with updated IP and save it in desired location. web start slave launch. On the picture, below the sentence "Run from slave command line" you should see a command that includes the new IP address

Launch the slave agent and it should now connect to the new IP address successfully!

Hope this helps anyone else! 

use the below command to connect to master and run it on agent:

java -jar agent.jar -jnlpUrl http://65.0.89.147:8080/computer/new%20node/jenkins-agent.jnlp -secret ec3d573f1cc65cc77c00474aedb3891a5ba8b9d3e235c32acdfaf4cb6a518a84 -workDir ""

the above command runs in the foreground and when ctrl+c, connection will be lost between slave and master. To run it in the backgroup, use & at the end of the url.

java -jar agent.jar -jnlpUrl http://65.0.89.147:8080/computer/new%20node/jenkins-agent.jnlp -secret ec3d573f1cc65cc77c00474aedb3891a5ba8b9d3e235c32acdfaf4cb6a518a84 -workDir "" & 

Install required software of slave node as well under same location as root

/opt/


Comments

Post a Comment

Popular posts from this blog

Jenkins for salesforce on RHEL OS or CentOS and configuring jenkins slave

To find the version  cat /etc/os-release sudo su - yum install jyava-11-openjdk-devel curl --silent --location http://pkg.jenkins-ci.org/redhat-stable/jenkins.repo | sudo tee /etc/yum.repos.d/jenkins.repo sudo rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io.key sudo yum install jenkins -y sudo systemctl enable jenkins sudo systemctl start jenkins systemctl status jenkins sudo firewall-cmd --permanent --zone=public --add-port=8080/tcp sudo firewall-cmd --reload =================================================== Create a another instance for slave connect the vm using pem file and  cd ~/.ssh ssh-keygen -t rsa -C "The access key for Jenkins slaves" cat id_rsa.pub > ~/.ssh/authorized_keys cat id_rsa Add the SSH Private Key to Jenkins Credentials Go to jenkins dashboard –> credentials –> Global credentials –> add credentials Create a Slave in jenkins CONFIGURE AGENT -> LAUNCH METHOD -> Manually trusted key verification strategy - > SAVE. If Manua...
Post a Comment
Read more

Reducing Manual Tasks in Salesforce DevOps

  🚩Focus: Automating the Deletion of Old Flow Versions ❓One of the most frequently asked questions I get as a DevOps Consultant is: “How can we reduce manual tasks during deployments?” A common manual task is deleting outdated Flow versions in Salesforce. Here’s why automating this step is valuable: 🚨 Why Automate This? Deleting old Flow versions is a best practice that helps in several ways: Improves overall performance Reduces clutter in the environment Makes the system easier to manage, especially during continuous development and iteration How to Automate Flow Deletion Deleting old Flow versions is fairly simple in itself, but doing it manually across multiple orgs during forward or backward promotions can become a tedious and error-prone process. 🚩Here are a few ways to automate it: 1. Using Salesforce Inspector Reloaded or Other Tools Supporting Tooling API You can run a query to fetch obsolete Flow versions and delete them using tools that support the Tooling API. 2. Usin...
Post a Comment
Read more