I haven't rewritten uscan in ruby, and they are all still separate
knife plugins, but I updated the easybake ingredients with some
common external dependencies for chef/devops work. Next is to put
together a devops-workstation cookbook that supports OSX, Windows, and
Ubuntu hosts with 'Vagrant+Windows+Ubuntu' and ability to build
baseboxes based on pulling these files from the file_cache_path. If we
run chef-solo from a USB stick, it could feasibly not require a
network connection. If we booted the USB stick as an automated OS
installer (that included a chef-solo run at the end), it would deploy
an devops workstation on hardware with all of the below:
Any blobs people use that I might be missing here?
Ubuntu desktop ISO 12.04.2 for ubuntu desktop 12.04.2
Ubuntu server ISO 12.04.2 for ubuntu server 12.04.2
Windows GRMSXEVAL_EN_DVD ISO 7601 for windows Windows GRMSXEVAL_EN_DVD
ISO 2008r2
VirtualBox Extension Pack 4.2.8
VirtualBox Guest Additions ISO 4.2.8
VirtualBox 4.2.8 for el 6
VirtualBox 4.2.8 for mac_os_x 10.7, 10.8
VirtualBox 4.2.8 for windows 2008r2, 2012, 7, 8
VirtualBox 4.2.8 for ubuntu 12.04
VirtualBox 4.2.8 for ubuntu 12.10
Chef Omnibus Client 11.4.0-18-gdf096fa-1 for debian 6
Chef Omnibus Client 11.4.0-18-gdf096fa-1 for el 5; for sles 11.2
Chef Omnibus Client 11.4.0-18-gdf096fa-1 for el 6; for suse 12.1
Chef Omnibus Client 11.4.0-18-gdf096fa-1 for mac_os_x 10.6
Chef Omnibus Client 11.4.0-18-gdf096fa-1 for mac_os_x 10.7
Chef Omnibus Client 11.4.0-18-gdf096fa-1 for ubuntu 10.04, 10.10
Chef Omnibus Client 11.4.0-18-gdf096fa-1 for ubuntu 11.04, 11.10, 12.04, 12.10
Chef Omnibus Client 11.4.0-18-gdf096fa-1 for windows 2008, 2003r2, 2008r2, 2012
Chef Server 11.0.6 for el 5
Chef Server 11.0.6 for el 6
Chef Server 11.0.6 for ubuntu 10.04, 10.10
Chef Server 11.0.6 for ubuntu 11.04, 11.10
Chef Server 11.0.6 for ubuntu 12.10, 12.04
Vagrant v1.0.6 for mac_os_x 10.7, 10.8
Vagrant v1.0.6 for windows 2008r2, 2012, 7, 8
Vagrant v1.0.6 for i686 ubuntu 10.04, 10.10, 11.04, 11.10, 12.04,
12.10; for i686 debian 6
Vagrant v1.0.6 for i686 el 5, 6; for i686 sles 11.2, 12.2
Vagrant v1.0.6 for ubuntu 10.04, 10.10, 11.04, 11.10, 12.04, 12.10; for debian 6
Vagrant v1.0.6 for el 5, 6; for sles 11.2, 12.2
Emacs 24.2 for i386 windows 2008r2, 2012, 7, 8
Emacs 24.2 for osx 10.6, 10.7, 10.8
GVim 7.3.46 for i386 windows 2008r2, 2012, 7, 8
Sublime Text 2.0.1 for osx 10.6, 10.7, 10.8
Sublime Text 2.0.1 for windows 2008r2, 2012, 7, 8
Sublime Text 2.0.1 for debian 6; for el 5, 6; for sles 11.2, 12.1; for
ubuntu 10.04, 10.10, 11.04, 11.10, 12.04, 12.10
Sublime Text 2.0.1 for i386 windows 2008r2, 2012, 7, 8
Sublime Text 2.0.1 for i386 debian 6; for i386 el 5, 6; for i386 sles
11.2, 12.1; for i386 ubuntu 10.04, 10.10, 11.04, 11.10, 12.04, 12.10
Git 1.8.1.2 for windows 2008r2, 2012, 7, 8
Git 1.8.1.2 for osx 10.6, 10.7, 10.8
On Thu, Mar 7, 2013 at 9:17 AM, Chris McClimans chef@hippiehacker.org wrote:
This pattern of enumerating through and downloading versions of
software has been solved before in debian.
Which results in automated monitoring of new releases of upstream
software, which is used to notify and eventually build debian packages
around them.
If we could do something similar with easybake ingredients and put it
into a continuous delivery pipeline, we could have tested/vetted
combinations of ingredients.
ingredients.easybake.cd
Looks like uscan is written in perl:
http://anonscm.debian.org/gitweb/?p=devscripts/devscripts.git;a=blob;f=scripts/uscan.pl;h=8723fb45dfd25df36ebc2aa06fd045df8ee75416;hb=HEAD
My next target is Virtualbox, which has a debian/watch file in the
debian sources and I'm digging the automated approach they took to
checking for new upstream releases.