Difference: JenkinsHowto (1 vs. 6)

Revision 62013-11-21 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="Documentation"

How to add new JENKINS slave nodes (clients)

Line: 46 to 46
  and
Changed:
<
<
boost boost-devel createrepo
>
>
boost boost-devel createrepo maven (for java pacakges)
  \ No newline at end of file

Revision 52013-06-27 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="Documentation"
Changed:
<
<

How to add new JENKINS slave nodes (clients)

>
>

How to add new JENKINS slave nodes (clients)

 

Revision 42013-06-27 - CristinaAiftimiei

Line: 1 to 1
 
META TOPICPARENT name="Documentation"
Deleted:
<
<
 

How to add new JENKINS slave nodes (clients)

Added:
>
>
 

Set up the jenkins user on the client node

  • Create the user jenkins on the node

Passwordless ssh from jenkins server configuration

Line: 44 to 44
 
cmake bash bzip2 coreutils cpio diffutils fedora-release findutils gawk gcc gcc-c++ grep gzip info make patch redhat-rpm-config rpm-build sed shadow-utils tar unzip util-linux which xz
Changed:
<
<

-- FabioCapannini - 2013-05-08

>
>
and
boost boost-devel createrepo

Revision 32013-06-21 - FabioCapannini

Line: 1 to 1
 
META TOPICPARENT name="Documentation"
Line: 25 to 25
 
  • The user which performs ssh (jenkins) is already specified. If the node is created from scratch this is another option to be specified.

In order to trigger a build on the already created node, specify the corresponding label in the build options.

Changed:
<
<
>
>

Enable package deployment to nexus

In order to publish artifacts in nexus, it is necessary to define a file on each build node under the jenkins user home directory. The file is ~jenkins/.m2/settings.xml and the content should be the following:
<settings>
  <servers>
    <server>
      <id>sonatype-nexus-staging</id>
      <username>jenkins</username>
      <password>***</password>
    </server>
  </servers>
</settings>
The id is the one that must be specified in the pom.xml section for the deployment.

Install build packages

These packages are considered the minimum build environment. Install them on the slave node.
cmake bash bzip2 coreutils cpio diffutils fedora-release findutils gawk gcc gcc-c++ grep gzip info make patch redhat-rpm-config rpm-build sed shadow-utils tar unzip util-linux which xz
 

-- FabioCapannini - 2013-05-08 \ No newline at end of file

Revision 22013-05-10 - FabioCapannini

Line: 1 to 1
 
META TOPICPARENT name="Documentation"
Line: 7 to 7
 

Set up the jenkins user on the client node

  • Create the user jenkins on the node

Passwordless ssh from jenkins server configuration

Changed:
<
<
  • If not already done, on the jenkins server enter ssh-keygen -t rsa without specifying a password
>
>
  • If not already done, on the jenkins server enter ssh-keygen -t rsa without specifying a password as user jenkins
 

Passwordless ssh from jenkins client configuration

  • mkdir /home/jenkins/.ssh
  • chmod 700 /home/jenkins/.ssh/

Revision 12013-05-08 - FabioCapannini

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="Documentation"

How to add new JENKINS slave nodes (clients)

Set up the jenkins user on the client node

  • Create the user jenkins on the node

Passwordless ssh from jenkins server configuration

  • If not already done, on the jenkins server enter ssh-keygen -t rsa without specifying a password

Passwordless ssh from jenkins client configuration

  • mkdir /home/jenkins/.ssh
  • chmod 700 /home/jenkins/.ssh/
  • vim .ssh/authorized_keys (<< copy here the content of cat .ssh/id_rsa.pub run on jenkins server home)
  • chmod 640 .ssh/authorized_keys
  • service sshd restart (as root)

Create the node in Jenkins

  • Point your browser to the jenkins instance: http://ci-01.cnaf.infn.it:8080/
  • Log in as admin and go to Configura Jenkins -> Gestisci nodi
  • Go to New Node
  • Insert node name and select the Copy existing node radio button. Specify the node to be copied eg. ci-02
  • Modify the following fields according to your desiderata: Name, Description, Labels (important for triggering builds on this node), Host
  • Click on the Save button
  • The user which performs ssh (jenkins) is already specified. If the node is created from scratch this is another option to be specified.

In order to trigger a build on the already created node, specify the corresponding label in the build options.

-- FabioCapannini - 2013-05-08

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback