format(): sprintf semantics in CFEngine
by Ted Zlatanov - May 16, 2013
If you are a programmer, you probably know and maybe even love the sprintf family of functions.
I wrote an implementation called format()...
Behind the scenes: How do we test CFEngine
by Carlos Duclos - May 16, 2013
Over the last year we have changed the way we test our software from a manual process to a highly automated process. This new system is capable of taking a change from our source code repository and follow it all the way up to where we update our internal staging servers, thus giving us incredibly valuable information while keeping manual intervention to a minimum.
New Output Format
by Sigurd Teigen - May 13, 2013
Last week, we revamped the way CFEngine formats output. You can continue to use the old output format by specifying the option --legacy-output (-l), but this is considered deprecated and may be removed in a future version.
IT-Organizations Face Disruption - Automation to the Rescue
by Thomas Ryd - May 09, 2013
IT-organizations around the world face constant pressure to do more, do it faster and with fewer resources. They are seen as cost centers and as such benchmarked against the performance of nimbler competitors and the public cloud providers.
IT-organizations feel that pressure from multiple sources at the same time. The CFO compares his internal IT-budgets with the costs of public cloud offerings and demands comparable savings. The lines of business know they can get the latest applications and platforms within minutes in the public cloud and complain about the slowness of their internal IT department. And the end-users expect continuous availability of all IT-services. Add Moore's law to describe the growth in scale and complexity of the IT infrastructure, and it becomes understandable why CIOs have the shortest tenure of all C-level executives.
Syntax warnings
by Sigurd Teigen - April 26, 2013
Over the past month we have removed a bit of functionality for CFEngine. These were features that were useful (cf-report) and good ideas (knowledge management), but the implementation was either in an unfinished state or the design had unclear semantics (outputs promise type).