Jenkins: CentOS 7 slave
Deploy CentOS 7 x86_64 slaves.
Collect the list of packages needed by projects, so that the deployment can be repeated.
#3 Updated by Alex Afanasyev over 4 years ago
Ashlesh, how do you managing images? Just in plain virtualbox?
I have suggestion to invest time into building vagrant images and use puppet as a configuration management. It would still be virtualbox, but this would allow simpler instantiation and management of vms. Moreover, others would be able to easily instantiate VM that is used for testing.
#5 Updated by Alex Afanasyev over 4 years ago
I have limited knowledge about vagrant, as I basically just started learning. Some tutorial is available at https://docs.vagrantup.com/v2/boxes.html.
I can only say that creating "box" in vagrant is straightforward and simple. Most likely, you will be able to reuse the virtualbox image you already created.
Another piece that I briefly mentioned is Puppet. I have not used it at all, but a lot of projects use it for management purposes. So we need to investigate how it can help us.
#12 Updated by Ashlesh Gawande over 4 years ago
- % Done changed from 50 to 100
I am sorry I forgot to update here. I have abandoned the puppet installation. The machines can be logged in at:
- CentOS: port 20024 firstname.lastname@example.org
- FreeBSD: port 20023 email@example.com
- Fedora: port 20021 firstname.lastname@example.org
I have vagrant boxes ready, which can be used to repeat deployment. Where do I upload them to?
#14 Updated by Alex Afanasyev over 4 years ago
CentOS and Fedora required additional tweaking of
/etc/sudoers: default config requires tty to run sudo, which prevents jenkins script to do any meaningful task.
#15 Updated by Alex Afanasyev over 4 years ago
Also failed and also most likely because of limited memory:
#17 Updated by Alex Afanasyev over 4 years ago
Still failing at random places. http://jenkins.named-data.net/job/ndn-cxx/OS=CentOS7/1696/consoleFull
I have no idea what is going on and how to fix that... There is almost 2Gb free space available plus 2Gb of swap (which is not used).
#27 Updated by Davide Pesavento 3 months ago
- Status changed from Feedback to Closed
Davide Pesavento wrote:
Setting status to Feedback due to note-24.
On second thought... both slaves are on maestro (UA) which is also the Jenkins master, so if that machine or site goes offline for any reason, everything else will go down as well. Deploying at different sites won't help in this case. Closing.