Two-and-a-half months after Git 2.0, a new version of Git has been released. Though a minor update, the list of new features and improvements is large.
Heroku is trying to make it easier to turn source code into a running application. The Heroku Button – a simple bit of HTML or Markdown that triggers a deployment from a public GitHub repository to Heroku’s public cloud – sets up Heroku as an attractive destination for quickly previewing, hosting, and extending open source web applications.
Google recently took the wraps off Kubernetes, an open source orchestration tool for managing Docker containers at scale. Late last week, Microsoft, IBM, RedHat, Docker, Mesosphere, CoreOS, and SaltStack all jumped on board and pledged to actively contribute to this project.
Git 2.0 is finally released, almost a month after the first release candidate was available. This comes with performance improvements such as introduction of bit-map indexes, as well as sensible defaults, especially helping first-time users.
Using the Deployment Notification plugin for Jenkins developed by CloudBees and either the additional Chef Software plugin or Puppet Labs plugin, engineers can now trace every file installed by Chef or Puppet within Jenkins CI.
The official RTM release of Visual Studio 2013 Update 2 has been made, and unlike the first update it brings with it a host of new features that should interest if not outright benefit nearly all users. Improved areas include better Git tooling support, web development, and profiling.
GitHub has open sourced their Atom IDE including the Atom Shell framework, Atom Core, and the Atom Package Manager (apm).
The database source control and deployment system DBmaestro now offers SQL Server support. This tool, which is also available for Oracle, is designed to be used in environments where multiple instances of a database exist in development, QA, and staging branches that need to be kept in sync with source code changes.
Today, Greg Stein, founder of the Apache Subversion project, raised a request to migrate the Subversion codebase to Git. More controversial than the decision itself was the way that the decision was made, by the PMC on the private mailing list. Read on to find out what happened and what the current state is.
Facebook has posted on how they've sped up Mercurial to be five times faster than Git in certain operations. Read on to find out what they have changed, and why it makes such a difference for their setup.
Mitchell Hashimoto, creator of Vagrant, gave a talk last month at Velocity Conf London about his vision for a “FutureOps” with immutable infrastructures and built-in failure recovery.
Versioning of services is something which has been a cornerstone problem of SOA. There are many examples over the years of experiences gained and shared, but little in the way of concretely comparing and contrasting different approaches. Jean-Jacques Dubray has written about the experiences of his team in this area and some equations they have developed to try to illustrate the differences.
On each day of the 3-day conference at the inviting environs offered at the Hyatt there was a jam-packed schedule of speakers, exhibits and activities that made for some difficult decisions as to which tracks and what happening to attend.
Yesterday, a developer on the Jenkins project accidentally triggered a force push on the GitHub repositories that store the Git repositories for the Jenkins codebase, wiping out several months of commits. InfoQ looks at what happened and what needs to prevent this re-occuring in the future.