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.


10173 comments

pitbull dog food's picture

obviously like your website however you need to take a
look at the spelling on several of your posts.

Several of them are rife with spelling issues and I find it very troublesome to tell the truth
however I'll definitely come back again.

Bitcoin's picture

Hello there! I could have sworn I've been to this blog before but after browsing
through some of the post I realized it's new to me. Anyhow, I'm definitely delighted I
found it and I'll be book-marking and checking back often!

short term rentals miami's picture

This is the right web site for anybody who would like to understand this topic.
You understand a whole lot its almost hard to argue with you (not that
I personally will need to...HaHa). You certainly put a
brand new spin on a topic that's been discussed for a
long time. Excellent stuff, just wonderful!

generic sovaldi cost's picture

I am sure this post has touched all the internet people, its really really
pleasant piece of writing on building up new website.

Brookline Childcare's picture

It's a shame you don't have a donate button! I'd most certainly donate
to this outstanding blog! I suppose for now i'll settle for book-marking and adding your RSS feed to
my Google account. I look forward to new updates and will talk about this blog with my Facebook
group. Talk soon!

temporary protection's picture

Very energetic article, I loved that bit. Will there be a part 2?

plumbers tooting's picture

Every weekend i used to pay a quick visit this web site, for the reason that i want enjoyment, for
the reason that this this site conations in fact fastidious funny data too.

bestwebhostinginc.com's picture

Yesterday, while I was at work, my cousin stole my apple ipad and tested to see if it can survive a forty foot drop, just
so she can be a youtube sensation. My iPad is now destroyed and she has 83
views. I know this is totally off topic but I had to share it with someone!

tamper evident tape's picture

It's really a cool and helpful piece of info. I'm glad that you shared this useful information with us.
Please keep us informed like this. Thanks
for sharing.

tamper proof parcel tape's picture

Amazing! This blog looks just like my old one! It's on a entirely different subject but it has pretty much
the same page layout and design. Superb choice of colors!

interactiveseoagency.org's picture

Wow, that's what I was exploring for, what a data!
existing here at this webpage, thanks admin of this site.

heart specialist Doctor in delhi's picture

Wow! This blog looks exactly like my old one!
It's on a totally different subject but it has pretty much the
same layout and design. Outstanding choice of colors!

top fashion photographers in nyc's picture

Helpful information. Lucky me I discovered your website accidentally, and I'm surprised why this coincidence did
not came about earlier! I bookmarked it.

Togel online's picture

This excellent website really has all the info I needed concerning this subject and didn't know who to ask.

NYC ROLLS ROYCE RENTALS's picture

I like the valuable information you provide in your articles.

I will bookmark your blog and check again here frequently.
I'm quite certain I will learn lots of new stuff right here!
Good luck for the next!

Cedric Moschallski's picture

If you are going for most excellent contents like I do,
only pay a visit this web page every day
since it offers feature contents, thanks

eyebrows threading's picture

Wonderful blog! I found it while searching on Yahoo News.
Do you have any tips on how to get listed in Yahoo News? I've been trying for a while but I never
seem to get there! Cheers

www.3nerd.com's picture

Helpful info. Lucky me I found your website unintentionally, and I'm surprised
why this coincidence did not came about earlier!

I bookmarked it.

Eyebrows shaping's picture

What's up, I would like to subscribe for this webpage to take
most recent updates, therefore where can i do it
please help.

www.con-ciencia.cl's picture

I am genuinely thankful to the owner of this web site who has shared this wonderful article at at this
place.

เล่นไพ่ออนไลน์'s picture

It's not my first time to go to see this site,
i am browsing this site dailly and get pleasant information from here every day.

Engraved mirrors's picture

I am no longer sure the place you're getting your information,
however good topic. I needs to spend a while studying more or
working out more. Thank you for great information I was in search of this information for my mission.

bacnet water meter's picture

This design is steller! You obviously know how to keep a reader amused.
Between your wit and your videos, I was almost moved to start my own blog (well, almost...HaHa!) Fantastic job.

I really loved what you had to say, and more than that, how you presented it.

Too cool!

Car Finance Cairns's picture

I love what you guys are up too. Such clever work and coverage!

Keep up the excellent works guys I've incorporated
you guys to my own blogroll.

Alyce's picture

Its like you read my mind! You appear to know a lot about this,
like you wrote the book in it or something. I think that you
could do with some pics to drive the message home a little
bit, but other than that, this is magnificent blog. A
fantastic read. I'll definitely be back.

double sided tape's picture

Incredible points. Solid arguments. Keep up the great effort.

website design's picture

This is the right web site for anybody who wants to find out about this topic.

You realize so much its almost tough to argue with you (not that
I actually will need to...HaHa). You certainly put a fresh spin on a subject that has been discussed for ages.
Great stuff, just excellent!

individual eyelashes's picture

Have you ever thought about including a little bit more than just your articles?
I mean, what you say is fundamental and all.

But just imagine if you added some great graphics or videos
to give your posts more, "pop"! Your content is excellent but with images and videos, this blog could undeniably be one of the most beneficial in its niche.
Very good blog!

cancun airport shuttle's picture

Thanks for the good writeup. It if truth be told was once a amusement account it.
Glance complicated to more added agreeable from you! By the way, how can we communicate?

knee pads for baby crawling's picture

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

VideoMix apk's picture

After looking into a few of the blog articles on your web page, I honestly like your way of writing a blog.
I saved it to my bookmark site list and will be checking back
in the near future. Please visit my web site too and let me know your
opinion.

BOLIGALARM's picture

Greate article. Keep writing such kind of information on your
site. Im really impressed by it.
Hello there, You have performed a fantastic job.
I will definitely digg it and in my view suggest to my friends.
I am sure they'll be benefited from this web site.

hair growth products for men's picture

What's up friends, nice article and fastidious urging commented at this place, I am in fact enjoying by these.

dieseluhrenhe.soup.io's picture

I think the admin of this website is really working hard for his web page, as here every information is
quality based information.

WordPress Plugin Development's picture

I do trust all the ideas you have offered on your post. They are very convincing and will certainly work.
Nonetheless, the posts are too brief for novices. May you please prolong them a little from subsequent time?
Thanks for the post.

Positive jameda Bewertungen kaufen's picture

I every time spent my half an hour to read this web site's posts everyday along with a
cup of coffee.

Michaela's picture

Just desire to say your article is as astounding.
The clearness for your submit is just cool and that i could think you're an expert on this subject.

Well together with your permission let me to grab your RSS feed
to keep updated with approaching post. Thanks 1,000,000 and please keep up the rewarding
work.

situs Poker's picture

I simply could not depart your web site before suggesting that I extremely
loved the usual information an individual provide on your visitors?

Is gonna be again incessantly in order to check out
new posts

film's picture

Hello! I just wanted to ask if you ever have any problems with hackers?
My last blog (wordpress) was hacked and I ended up losing many months of hard work due
to no back up. Do you have any methods to stop hackers?

Vip clubbing bangkok's picture

continuously i used to read smaller articles that as well clear their motive, and that is also happening with this post which I am reading at this
place.

fingerboard skateboard's picture

That is very fascinating, You are an excessively professional blogger.
I have joined your feed and look forward to in quest of more of your great post.
Additionally, I've shared your site in my social networks

condo rental in hallandale beach's picture

Touche. Solid arguments. Keep up the great effort.

custom made reef's picture

Yes! Finally someone writes about Aqua Medic.

bralette's picture

I have read so many articles on the topic of the blogger lovers
however this paragraph is really a nice article, keep it up.

florida campsites's picture

Very good blog post. I certainly love this website. Keep it
up!

tips's picture

I'm impressed, I have to admit. Rarely do I come across a blog that's equally educative and amusing,
and without a doubt, you've hit the nail on the head. The problem is something which
not enough folks are speaking intelligently about. I am very happy that I found this in my
hunt for something concerning this.

Earring repair london's picture

My family every time say that I am wasting my time
here at web, except I know I am getting know-how all the time by reading such fastidious posts.

research report writing's picture

Hi Dear, are you genuinely visiting this web site daily, if so afterward you will definitely obtain good
know-how.

Magnetic letters's picture

It's the best time to make a few plans for the long run and it is time to be happy.
I have learn this publish and if I may I want to recommend you few interesting
issues or tips. Perhaps you could write subsequent articles relating to this article.
I want to learn more issues approximately it!

Double sided magnets's picture

Heya! I understand this is kind of off-topic however I had to
ask. Does managing a well-established website
like yours require a large amount of work? I am brand new to blogging but I do write
in my diary daily. I'd like to start a blog so I will be able to share my own experience
and views online. Please let me know if you have any kind of recommendations or tips for new aspiring blog
owners. Thankyou!

Pages

Add new comment