Adventures in tinderbox 2


If you stumbled into this post first you may want to have a look over this previous post as we are building upon steps covered there.

So far we have got our world binaries built and these are the foundation of the environments we setup for testing our port builds. From here we create a tinderbox build. Within tinderbox a build refers to a combination of world binaries (the tinderbox jails we setup before) and a version of the ports files. It is probably a rare case but it would appear that you could setup a build using say netbsd pkgsrc system or similar, the most likely alternative to the official ports system would be an internal development branch of the ports source.

The first step is to setup the ports files to be used. A cvs checkout is shown in the docs and you could adjust the svn usage from yesterday if you have your own local svn repo (official ports are still in cvs at this point). The examples in the docs show a source checkout that is unique to your tinderbox setup. I think using the system installed ports will be enough for what I want and will bypass the confusion of three copies of the ports files. Personally I use portsnap to update my system ports tree and create or update a port there to test and develop it. Then I have a copy within my home folder that is an svn checkout from my redports account that I transfer changes to that I want to keep, and commit as desired from there. While my personal folder is just the ports I make changes to, I don't want a third copy just for test builds, so what I will use here is a user defined update method that will run portsnap anytime I want to update the ports tree. We have two options here, 1. create a portsTree with no update method leaving us to run portsnap manually as desired. 2. create a portsTree with a user update method. The first option is straight forward and acceptable for most but I want to look at option 2 here.

Reading the docs you may jump straight in and use a command like cd /usr/local/tinderbox/scripts ./tc createPortsTree -p FreeBSD -u USER -m /usr/ports and get errors and no ports tree setup. The docs don't help here so I went digging through the scripts and found the answer. When you create a portstree with a user defined update method it looks for the update script when it is first setup. The solution is simple. If we are creating a portstree called FreeBSD then we create a file in tinderbox/portstrees/FreeBSD and call it update.sh and for this example I want it to run portsnap so I use the following contents - #!/bin/sh portsnap fetch update Then run the createPortsTree command with the -u USER option. Simple and a good basis of any custom update you want to setup. You could even use this to run portsnap and then merge files from your personal ports repo automatically. This setup script is run with the command ./tc updatePortsTree

You may also want to share your local distfiles with tinderbox. Pretty easy and the one setup is shared across all portstree configs -

cd /usr/local/tinderbox/scripts ./tc configDistfile -c /usr/ports/distfiles

Now that we have our jails and portsTree setup it is time for the build. Remember a tinderbox build is a combination of a specific jail and portsTree and is straight forward -

cd /usr/local/tinderbox/scripts ./tc createBuild -b 10-CURRENT-clang -j 10-CURRENT -p FreeBSD -d "10-CURRENT building with clang"

The name I used there may raise a few questions but first lets consider what variations of builds we want to use.

The aim of using tinderbox is to test building under a variety of conditions, in this case primarily different system versions. To that end we started by creating 2 jails with different versions of world binaries, you may have extended that number and I encourage you to do so but I use two in these examples. From FreeBSD 9.0 we are moving away from a  dependency on gcc as the main compiler and now include clang within the base system. Being in the early transition of this is a bit awkward as not all ports build with the old gcc v4.2 that is included with base and not all ports build with clang either. Well ports changes need to be tested with each compiler so we may get a full ports build happening on any system install. One option we have is to specify what version of gcc is used to build our port. Easy till we get linking issues with something like boost installed with gcc42 and not linking with a gcc46 built port (that is my early guess and may not be the location of a solution). So anyway I am suggesting that a number of builds are setup to test building with clang as well as gcc. This will only apply to 9.0 and higher, 8.3 has just entered beta1 and doesn't appear to include clang. The other question you may have is that I only put clang in the name, how does it know to build with clang? It doesn't yet - that comes in a minute.

Well using the two jails we built yesterday lets setup the builds -

cd /usr/local/tinderbox/scripts ./tc createBuild -b 10-CURRENT-clang -j 10-CURRENT -p FreeBSD -d "10-CURRENT building with clang" ./tc createBuild -b 10-CURRENT-gcc -j 10-CURRENT -p FreeBSD -d "10-CURRENT building with gcc" ./tc createBuild -b 9-STABLE-clang -j 9-STABLE -p FreeBSD -d "9-STABLE building with clang" ./tc createBuild -b 9-STABLE-gcc -j 9-STABLE -p FreeBSD -d "9-STABLE building with gcc"

Now we have four builds setup to test our ports in. As I suggested before you should also consider having at least an 8-STABLE jail setup and maybe even a 7-STABLE one as well if not more. As clang is not included in 7 or 8 there is no need to setup two builds for each, I would still use gcc in the build name though.

At this point you will find a few directories have been created. The first you will probably see is tinderbox/{BUILDNAME} so if your following along you will have four there corresponding to each build you setup. The next ones are inside tinderbox/builds and have the same names as the four we just looked at. The dirs inside builds contain a Makefile with all the package  dependencies and although you may think make.0 and make.1 are makefiles they are in fact logs containing the log of the last compile done, each port compile is run in two phases, and a more than likely empty duds file. The top level dirs are where all the work is done. For each port you make, tinderbox will extract the tarball found in the corresponding jail build and mount the various points needed for portstrees/distfiles/devfs/procfs. From that you can work out that each build starts up in a unique environment (it uses chroot) completely isolated for your test make. Each environment is cleaned up after each test make and the log files will include files left behind if you get your pkg-plist incorrect.

Now to configuring the compiler to use. When you first test making your port and look at a log file you may notice that the timestamp at the start is all wrong. That will be a wrong timezone setting and gets us close to the compiler settings. First lets set the timezone, so edit the file tinderbox/scripts/etc/env/GLOBAL and add the following line (adjusted to match your timezone of course)

export TZ=Australia/Adelaide

You can see that it uses a bash style environment setting. Within the same folder we want to create a config file for each build we setup using the name build.{BUILDNAME} and have it contain the CC options that we wish to use. Before you go thinking about copying all your /etc/make.conf settings consider the purpose of this - testing against a minimum system config to ensure your port is as compatible as possible. Those with a custom edited make.conf need to handle their own port build conflicts with the options they want to use. So here all we want to do is set the compiler to use. To make this easy let's make a script, I will put this inside tinderbox/scripts and lets call it gencompilerenvfiles.sh

#!/bin/sh cd /usr/local/tinderbox/scripts/etc/env for BNAME in `ls ../../../builds | grep clang` do if [ ! -e build.$BNAME ] then cat > build.$BNAME <<CCOPTIONS export CC=clang export CXX=clang++ export CPP=clang-cpp CCOPTIONS fi done for BNAME in `ls ../../../builds | grep gcc` do if [ ! -e build.$BNAME ] then cat > build.$BNAME <<CCOPTIONS export CC=gcc export CXX=g++ export CPP=cpp CCOPTIONS fi done

Pretty straight forward if you know some shell scripting, if it's a bit beyond what you know it simply gets a list of dirs from within builds and outputs three lines to a corresponding config file for each one. The script won't touch files that already exist, so delete them if you want a clean slate or adjust if you want to add to existing files. The first loop uses grep to get clang named builds the second gcc. Is it overkill specifying gcc for the gcc builds - yep - but it keeps things consistent and also gets the CC setting output to the log file to remove any confusion when looking over them later, or more to the point when you get someone else to look over them for some help.

Now your all setup to use tinderbox to test your ports building. While the docs say you can do an adhoc build with just the tinderbuild command I find that not to be the case, the two command you use are

cd /usr/local/tinderbox/scripts ./tc addPort -b 10-CURRENT-clang -d graphics/blender ./tc tinderbuild -nullfs -b 10-CURRENT-clang graphics/blender

The first time you build a port it may take a while - it will build each  dependency needed, basically running make package-recursive for your port. Next time it will just pkg_add each dependancy and build the port you ask it to. The -nullfs option is needed if you setup the nullfs mount for portstree as shown above (or maybe it is for distfiles?). This adds some more dirs for you as well.

tinderbox/packages/{BUILDNAME} will contain all the packages created by that build. You will find a folder for each category containing links to the corresponding package inside the All dir.

tinderbox/logs/{BUILDNAME} will contain log files of each port compiled for that build.

tinderbox/errors/{BUILDNAME} will contain copies of the log files that had errors - this is probably all your really interested in.

That's about all you need to get up and running with tinderbox. I think I will do one more post covering some housekeeping and other notes. To close off I'll show a script I use to automate running any number of ports inside every build you have configured, I save it in tinderbox/scripts and call it testbuilds.sh

#!/bin/sh ## auto build passed ports for every tinderbox build setup ## works on assumption that /usr/ports is used for tinderbox portstree ## to test that the portname is correct cd /usr/local/tinderbox/scripts if [ ! $# -gt 0 ] then echo "Usage: ${0##*/} [category/portname ...]" echo "Multiple ports can be listed - space separated list" exit 1 fi for TESTPORT in "$@" do if [ ! -e "/usr/ports/$TESTPORT" ] then echo "********************" echo " /usr/ports/$TESTPORT doesn't exist" echo "********************" else for BNAME in `ls ../builds` do echo "***** Building $TESTPORT" ./tc addPort -b $BNAME -d ${TESTPORT} ./tc tinderbuild -nullfs -b $BNAME ${TESTPORT} done fi done

So to make use of the script

cd /usr/local/tinderbox/scripts ./testbuilds.sh graphics/blender graphics/luxrender ports-mgmt/tinderbox

and it will go through and compile each port with every tinderbox build you have setup.


9553 comments

Waist trainer in deutschland's picture

Thanks , I have recently been searching for information approximately this
topic for a long time and yours is the best I have came upon till now.

However, what about the bottom line? Are you sure about the
source?

yalla-shoot's picture

Very nice blog post. I definitely love this website.
Thanks!

Green Matcha Powder's picture

Wow, wonderful weblog structure! How long have you been running a blog for?
you make running a blog look easy. The entire
glance of your site is excellent, as neatly as the
content material!

Holiday lets Cheshire's picture

You really make it seem so easy with your presentation but I find
this topic to be actually something which I think I would never understand.
It seems too complicated and very broad for me.
I am looking forward for your next post, I will try to get the hang
of it!

Sofia's picture

Fantastic website. Lots of useful information here. I am sending it to some friends
ans additionally sharing in delicious. And naturally, thank you
on your sweat!

smartwatch's picture

You actually make it seem so easy with your presentation but I find this topic to be actually something that I
think I would never understand. It seems too complicated
and extremely broad for me. I'm looking forward for your next post,
I'll try to get the hang of it!

pinboard's picture

It's great that you are getting thoughts from this
piece of writing as well as from our argument made at this
place.

Movers Del Mar's picture

Admiring the commitment you put into your blog and in depth information you offer.
It's awesome to come across a blog every once in a while that isn't the same old rehashed material.

Great read! I've bookmarked your site and I'm including your RSS feeds
to my Google account.

Hemp oil's picture

Simply desire to say your article is as astounding.
The clarity in your post is simply cool and i can assume you are an expert on this subject.
Fine with your permission allow me to grab your RSS feed to keep updated with forthcoming post.
Thanks a million and please continue the gratifying work.

CBD olie's picture

Keep on writing, great job!

Boswelia's picture

I constantly spent my half an hour to read this web site's articles daily along with a mug
of coffee.

Executive forum's picture

Keep on working, great job!

Local Internet Marketing For Small Business's picture

Remarkable! Its truly awesome article, I have got much clear idea concerning from this piece
of writing.

Laser hair growth's picture

I believe this is one of the so much vital information for
me. And i'm glad reading your article. However wanna commentary on some common issues, The website taste is ideal,
the articles is actually excellent : D. Excellent process,
cheers

used scooter's picture

Have you ever thought about adding a little bit more than just your articles?
I mean, what you say is fundamental and all. However just imagine if you added
some great pictures or video clips to give your
posts more, "pop"! Your content is excellent but with pics and video clips, this blog could certainly be one of the
best in its field. Excellent blog!

Formation thérapie manuelle's picture

Vous pouvez aussi vous en servir un peu comme d'un tracker, en prenant
des notes sur les adversaires.

eiendomsmegler's picture

Hi Dear, are you genuinely visiting this web page regularly,
if so afterward you will without doubt take pleasant knowledge.

sprint chat's picture

Very nice write-up. I certainly love this site. Keep writing!

tamper evident tape's picture

Thanks on your marvelous posting! I truly enjoyed reading it, you happen to be a great author.
I will be sure to bookmark your blog and may come back in the future.
I want to encourage you to ultimately continue your great work, have a nice morning!

floor protection's picture

Hello, just wanted to say, I liked this blog post.
It was helpful. Keep on posting!

write my essay now's picture

hi!,I love your writing so so much! share we keep up a correspondence more approximately
your article on AOL? I require a specialist in this house
to unravel my problem. Maybe that is you! Looking ahead to see you.

Prediksi Togel Hongkong Pools Malam Ini's picture

I just couldn't depart your website prior to suggesting that I actually
enjoyed the standard information an individual provide in your guests?

Is gonna be back steadily to inspect new posts

tissue paper's picture

You can definitely see your skills in the article
you write. The arena hopes for more passionate writers such as
you who aren't afraid to mention how they believe.
At all times follow your heart.

social media business marketing's picture

Aw, this was an extremely good post. Taking the time and actual effort to generate a superb article... but what can I
say... I procrastinate a whole lot and don't manage to
get anything done.

secondary glazing's picture

Keep on working, great job!

carpet protection's picture

Greetings from Colorado! I'm bored at work so I decided to check
out your blog on my iphone during lunch break. I really like the knowledge you present here and can't wait to take a
look when I get home. I'm shocked at how fast your blog
loaded on my phone .. I'm not even using WIFI, just
3G .. Anyhow, awesome blog!

flame retardant floor protection's picture

Hello, this weekend is good for me, because this point in time i am reading this enormous informative piece of
writing here at my home.

top 40 charts's picture

Hey there just wanted to give you a quick heads up.
The text in your article seem to be running off the screen in Opera.

I'm not sure if this is a formatting issue or something to do with browser compatibility but
I figured I'd post to let you know. The style and design look great though!
Hope you get the issue fixed soon. Many thanks

flame retardant floor protection's picture

I don't even know how I ended up here, but I thought this post was great.
I do not know who you are but definitely you are going to a
famous blogger if you are not already ;) Cheers!

gearboxes's picture

Ahaa, its good dialogue on the topic of this paragraph here at
this blog, I have read all that, so at this time me also
commenting here.

temporary site protection's picture

For the reason that the admin of this web site
is working, no question very shortly it will be famous, due to its quality
contents.

hook and loop fastener's picture

whoah this blog is great i like reading your posts.
Keep up the great work! You already know, many people
are hunting round for this information, you can help them greatly.

Video production for small businesses's picture

My partner and I stumbled over here different web page and thought I might as well check things out.
I like what I see so i am just following you. Look forward to
looking at your web page again.

facilities services's picture

These are in fact great ideas in on the topic of blogging.
You have touched some nice things here. Any way keep up wrinting.

minneapolis corporate event photographer's picture

Saved as a favorite, I like your blog!

carpet protector's picture

Pretty! This was a really wonderful post. Thank you for
providing this info.

dungeons and dragons monsters's picture

I just couldn't go away your website before suggesting that I
actually loved the usual information an individual supply on your visitors?

Is gonna be again continuously in order to inspect new posts

http://alanmillerantiquesconsultant.com's picture

We stumbled over here different web page and thought I
should check things out. I like what I see so now i'm following you.

Look forward to checking out your web page yet again.

tamper safe tape's picture

Hey There. I found your blog using msn. That is a really neatly written article.

I will be sure to bookmark it and return to learn extra of your helpful info.
Thank you for the post. I'll certainly comeback.

Fitness &amp; Equipment store's picture

Hey there! Someone in my Myspace group shared this site with us so
I came to take a look. I'm definitely loving the information. I'm bookmarking and will be tweeting this to my followers!
Terrific blog and superb style and design.

Beastiary's picture

Excellent blog here! Additionally your site quite a bit up fast!
What web host are you using? Can I get your associate hyperlink for your host?
I desire my web site loaded up as quickly as yours lol

best travel cards's picture

That is really attention-grabbing, You're an excessively professional blogger.
I have joined your rss feed and look ahead to looking for extra of your wonderful post.
Also, I have shared your website in my social networks

diy secondary glazing's picture

Hi there! I just wanted to ask if you ever
have any trouble with hackers? My last blog (wordpress) was hacked and I ended up losing a few months of hard work due to no back up.
Do you have any solutions to protect against hackers?

women&#039;s clothing's picture

I was curious if you ever considered changing the structure of your
site? Its very well written; I love what youve
got to say. But maybe you could a little more in the way
of content so people could connect with it better. Youve
got an awful lot of text for only having 1 or two images.
Maybe you could space it out better?

Minneapolis corporate event photography's picture

I like what you guys are up too. This kind of clever work and reporting!
Keep up the good works guys I've included you guys to my own blogroll.

diy secondary glazing's picture

I'm not sure why but this weblog is loading incredibly slow
for me. Is anyone else having this problem or is it a issue
on my end? I'll check back later on and see if the problem still exists.

Pasta's picture

Hi my family member! I wish to say that this post is awesome, nice written and
come with approximately all vital infos. I'd like to see more posts like this
.

bandar livecasino's picture

Fine way of explaining, and good piece of writing to take facts about my presentation topic, which i am going to deliver in school.

Shylesh Sriranjan's picture

Hello, i feel that i noticed you visited my site thus i got here to go back the want?.I'm trying to
to find things to improve my web site!I assume its ok
to use some of your concepts!!

world explorer's picture

I do not know whether it's just me or if everyone else experiencing issues
with your website. It appears as though some
of the text on your posts are running off the screen. Can someone else please provide feedback and let me know
if this is happening to them too? This could be a
issue with my web browser because I've had this happen before.
Thank you

Pages

Add new comment