ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
pending--There are no nodes with the label 'building_repository'
This was the result of a misconfigured repo/common.yaml (one of the ssh keys wasn't consistent with the master/common.yaml jenkins::private_ssh_key).
Upon trying to run reconfigure.bash repo a couple of times it looked like the change wasn't working. I ended up doing this on the repo machine:
rm -rf /var/log/puppet.log # Just to get a clean log, not necessary
sudo deluser jenkins-slave
sudo rm -rf /home/jenkins-slave
./reconfigure.bash repo
And now I have a 'building_repository' on my master. I also reran reconfigure on the master and slave several times, so I'm not 100% sure cleaning out jenkins-slave on the repo was the entire solution.
2 | No.2 Revision |
pending--There are no nodes with the label 'building_repository'
This was the result of a misconfigured repo/common.yaml (one of the ssh keys wasn't consistent with the master/common.yaml jenkins::private_ssh_key).
Upon trying to run reconfigure.bash repo a couple of times it looked like the change wasn't working. I ended up doing this on the repo machine:
rm -rf /var/log/puppet.log # Just to get a clean log, not necessary
sudo deluser jenkins-slave
sudo rm -rf /home/jenkins-slave
./reconfigure.bash repo
And now I have a 'building_repository' on my master. I also reran reconfigure on the master and slave several times, so I'm not 100% sure cleaning out jenkins-slave on the repo was the entire solution.
3 | No.3 Revision |
pending--There are no nodes with the label 'building_repository'
This was the result of a misconfigured repo/common.yaml (one of the ssh keys wasn't consistent with the master/common.yaml jenkins::private_ssh_key).
Upon trying to run reconfigure.bash repo a couple of times it looked like the change wasn't working. I ended up doing this on the repo machine:
rm -rf /var/log/puppet.log # Just to get a clean log, not necessary
sudo deluser jenkins-slave
sudo rm -rf /home/jenkins-slave
./reconfigure.bash repo
And now I have a 'building_repository' build executor on my master. master jenkins server. I also reran reconfigure on the master and slave several times, so I'm not 100% sure cleaning out jenkins-slave on the repo was the entire solution.
4 | No.4 Revision |
pending--There are no nodes with the label 'building_repository'
This was the result of a misconfigured repo/common.yaml (one of the ssh keys wasn't consistent with the master/common.yaml jenkins::private_ssh_key).
Upon trying to run reconfigure.bash repo a couple of times it looked like the change wasn't working. I ended up doing this on the repo machine:
rm -rf /var/log/puppet.log # Just to get a clean log, not necessary
sudo deluser jenkins-slave
sudo rm -rf /home/jenkins-slave
sudo ./install_prerequisites.bash
sudo ./reconfigure.bash repo
And now I have a 'building_repository' build executor on my master jenkins server. I also reran reconfigure on the master and slave several times, so I'm not 100% sure cleaning out jenkins-slave on the repo was the entire solution.
5 | No.5 Revision |
pending--There are no nodes with the label 'building_repository'
This was the result of a misconfigured repo/common.yaml (one of the ssh keys wasn't consistent with the master/common.yaml jenkins::private_ssh_key).
Upon trying to run reconfigure.bash repo a couple of times it looked like the change wasn't working. I ended up doing this on the repo machine:
rm -rf /var/log/puppet.log # Just to get a clean log, not necessary
sudo deluser jenkins-slave
sudo rm -rf /home/jenkins-slave
sudo ./install_prerequisites.bash
sudo ./reconfigure.bash repo
And now I have a 'building_repository' build executor on my master jenkins server. I also reran reconfigure on the master and slave several times, so I'm not 100% sure cleaning out jenkins-slave on the repo was the entire solution.
6 | No.6 Revision |
pending--There are no nodes with the label 'building_repository'
This was the result of a misconfigured repo/common.yaml (one of the ssh keys wasn't consistent with the master/common.yaml jenkins::private_ssh_key).
Upon trying to run reconfigure.bash repo a couple of times it looked like the change wasn't working. I ended up doing this on the repo machine:
rm -rf /var/log/puppet.log # Just to get a clean log, not necessary
sudo deluser jenkins-slave
sudo rm -rf /home/jenkins-slave
sudo su
./install_prerequisites.bash
sudo ./reconfigure.bash repo
And now I have a 'building_repository' build executor on my master jenkins server. I also reran reconfigure on the master and slave several times, so I'm not 100% sure cleaning out jenkins-slave on the repo was the entire solution.
7 | No.7 Revision |
pending--There are no nodes with the label 'building_repository'
This was the result of a misconfigured repo/common.yaml (one of the ssh keys wasn't consistent with the master/common.yaml jenkins::private_ssh_key).
Upon trying to run reconfigure.bash repo a couple of times it looked like the change wasn't working. I ended up doing this on the repo machine:
rm -rf /var/log/puppet.log # Just to get a clean log, not necessary
sudo deluser jenkins-slave
sudo rm -rf /home/jenkins-slave
sudo su
./install_prerequisites.bash
./reconfigure.bash repo
And now I have a 'building_repository' build executor on my master jenkins server. I also reran reconfigure on the master and slave several times, so I'm not 100% sure cleaning out jenkins-slave on the repo was the entire solution.
I encountered some issues where simply deleting jenkins-slave did not do enough- trying to run reconfigure did not recreate the jenkins-slave home directory. I ended up reinstalling ubuntu 14.04 server on the same repo vm instance and starting from scratch (and cloned the vm prior to making changes to save a little time if this step needed again).