Ask Your Question
1

How to configure buildfarm after setting up jenkins ?

asked 2018-05-17 16:21:13 -0500

venkisagunner gravatar image

updated 2018-05-18 09:54:52 -0500

This is a continuation of the question that I asked here previously. Step 1 was to basically make jenkins run on master. I was able to achieve that. Now the next step I believe is to configure jobs for the packages that I have built. I understood that I have to edit the configuration files here in this repository but for some reasons the documentation is not so clear on what are the files that should be edited.

So here it goes. This is what I have done so far. I went into this repository and forked the ros_buildfarm_config repo to my account according to the instructions here.

  1. As I earlier mentioned, let us assume that I'm using kinetic distribution and in the Disable notification of maintainers/committers section, I was asked to set false to all committers which by default was already set to false in all the files. When I say all files, I changed or verified whether they are false in index.yaml, doc-build.yaml, doc-released-build.yaml, release-armhf-build.yaml, release-build.yaml, source-build.yaml inside kinetic folder.
  2. Next up was to update administrator notification. I changed the email on all files as said in the previous point. I want to know whether whatever I did in these two points are correct. If yes, I request you to update the documentation, its totally out of sync and not intuitive.
  3. I figured out that the jenkins_url takes the ip address of the master machine and the repo_hostname.example.com simply gets replaced by the repository ip address on all the yaml files mentioned earlier. Is that right ? Also I want to know whether the PGP key used here is the same as the ones used in the buildfarm_deployment_config ?
  4. After that I understood that inorder to run jobs on my custom ros package(s) in the buildfarm, I was given two options. One to perform full fork and the another one being add-on fork. As I understood that clearly, I decided to go with option 2 which is Add-on fork so that I don't have to worry about other ROS packages from build.ros.org . Interesting thing here is that I saw that we have to add a tag to custom distribution files. I understand that we have to add those but to what files is not so clear. Also mentioning custom distribution file is not very clear to me.
  5. Is there a better way (may be a structural way) to actually tell me, what I should be doing in Import ROS packages which are not built by the custom build farm ? Like could you be more specific on where should I place the import_distro.yaml file ? May be an example would be great. And also I have no idea how to invoke import_upstream job. Could you please be clear here ?
edit retag flag offensive close merge delete

Comments

I agree with you that the documentation is not great, but this (as an example):

And also I have no idea how to invoke import_upstream job

is basic Jenkins background knowledge. Not saying it can't be made clearer, but it would be good if you get some experience with Jenkins. It'll make your ..

gvdhoorn gravatar imagegvdhoorn ( 2018-05-18 01:19:47 -0500 )edit

.. life a lot easier, and will also turn some of these things -- that now look like magic / are completely opaque -- into understandable bits of information.

gvdhoorn gravatar imagegvdhoorn ( 2018-05-18 01:20:24 -0500 )edit

Is there any material that you can point to that might help me ? Thank you !

venkisagunner gravatar imagevenkisagunner ( 2018-05-18 08:48:23 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2018-05-18 12:28:31 -0500

tfoote gravatar image

The goal of our documentation is to show how to use Jenkins, but not to teach how to use Jenkins. There are lots of good free standing Jenkins tutorials from Jenkins experts, going through some of the top hits here will be the best way to learn about Jenkins.

For most of your questions you need to be much more concrete about what you're doing for us to be able to help you. For example I can't tell you if what you did was correct if you don't show what you did.

For your specific question:

Is there a better way (may be a structural way) to actually tell me, what I should be doing in Import ROS packages which are not built by the custom build farm ? Like could you be more specific on where should I place the import_distro.yaml file ? May be an example would be great. And also I have no idea how to invoke import_upstream job. Could you please be clear here ?

As stated in the documentation you can place the file anywhere on that machine. Then to run it you click the "Build with Parameters" button for the import_upstream job. And on the configuration page you should enter the path to the file from above in the config_file parameter field, and then click "Build". How would you want that to be better or "structurally" different?

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

3 followers

Stats

Asked: 2018-05-17 16:21:13 -0500

Seen: 266 times

Last updated: May 18 '18