Fresh Varnish packages for Debian/Ubuntu and Redhat systems

We use continuous integration when developing Varnish Cache. This means that we run our internal test suite (varnishtest) on all commits, so we catch our mistakes earlier.

This pipeline of build jobs sometimes end up with binary packages of Varnish, which may be useful to people when they know they exist. They may not be the easiest to find, which this blog post tries to remedy.

Development wise, Varnish Cache is developed with GIT with a master branch for development and a set of production branches, currently 3.0 and 4.0.

Unreleased packages for Varnish master can be found here: https://jenkins.varnish-software.com/view/varnish-master/

Unreleased packages of Varnish 4.0 can be found here: https://jenkins.varnish-software.com/view/varnish-4.0/

(There is also a set of 3.0 jobs, but you should really go for 4.0 these days.)

The latest commits in each of the production branches may contain fixes we’ve added after the last production release, but haven’t cut a formal release for yet. (For example there are some gzip fixes in the 3.0 branch awaiting a 3.0.6 release, which I really should get out soon.)

Some jobs in the job listing just check that Varnish builds, without creating any output (or artifacts as Jenkins calls it.) This applies for any jobs with “-build-” in the name, for example varnish-4.0-build-el7-x86_64 and varnish-4.0-build-freebsd10-amd64.

The Debian and Ubuntu packages are all built from one job currently, called varnish-VERSION-deb-debian-wheezy-amd64. Press “Expand all” under artifacts to get the full list.

Redhat/RHEL packages are built in the different el5/el6/el7 jobs.

The unreleased packages built for 3.0 and 4.0 are safe. This is the process used to build the officially released packages, just a step earlier in the process. The varnish-master packages are of course failing from time to time, but that is to be expected.

The version numbers in the packages produced may be a bit strange, but that is what you get with unreleased software builds.

I’m happy to improve this process and system if it can help you run never versions of Varnish, comments (either here or on IRC) are appreciated.

This entry was posted in stuff, varnish and tagged , , . Bookmark the permalink.

6 Responses to Fresh Varnish packages for Debian/Ubuntu and Redhat systems

  1. Is there is a way to get vmods builds from repositories somewhere ? I think at least very popular ones (like cookies and header) would be helpful for most users.

    Another question is. Is it safe to have Varnish installed from official repos (RHEL in my case), while I compile vmods manually using Varnish src of the installed revision. Or should I install Varnish also from src for this?

    Also, maybe make a shortcut for fetching Varnish revision sha (`varnishd -sha`) :)

    • Hi Anton.

      I don’t think anyone else is packaging vmods these days. I expect that to change after 4.0.2 which relaxes the hard gitref ABI check.
      For Varnish 3.0 you should definitively use a built source tree of the same version/gitref when building vmods. The gitref is available in ‘varnishd -V’, you just need to cut/awk it a bit.

      Best of luck :-)

      • Interesting. How I can get vmods for Varnish 4.0.1 without compiling them? Is there RHEL repo for them ?

      • There isn’t currently, but I expect that to change the next couple of months.

        Both the Fedora and Debian packagers were at the last developer meeting, and they are positive to building vmod packages in the downstream distributions.

  2. Great.

    Btw, are there plans to update Varnish book for version 4 ? It is not a lot of information about version 4 online, yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s