Showing posts with label Minick. Show all posts
Showing posts with label Minick. Show all posts

Tuesday, November 16, 2010

Subject: Configuration Management the build system's job? - by: Eric Minick

tekkie wrote:
What do you say? Is Software Configuration Management the build system's job? Or is it a shared responsibility between the SCM/VC system and the build system?
I don't really agree with anybody on this thread...

The problem is probably in the question, and more precisely in the 'is' predicate.

SCM is about management, and shouldn't make sense unless it would be itself manageable. Thus it has to take responsibility for its presentation of reality: it cannot accept arguments of authority. Thus nothing is unless we want it and know why.

The special kind of sophisticated SCM I'd wish to achieve/evolve (trying to avoid the word 'build'), based on concepts taken from clearmake, would reverse the terms of the assertion: SCM is a by-product of Build Management.

I have already attempted to develop this idea, e.g. in: DO Management, or in: DO as CI, but here is a new bit of argument: identification makes only sense for stable artifacts. Unless the SCM/build tool provides a way to promote, save, and share derived objects, the only stable artifacts are (hand-produced, and thus slowly changing) 'sources'. But as soon as the life-time of DOs gets extended, it becomes possible to base the whole identification on them, and this makes much more sense than the traditional state-of-things.
This is because DOs have more intrinsic value, because they have a structure (based on dependency graphs), and because they may typically be run (they don't need to be painstakingly interpreted).

Marc


View the original article here

Monday, November 8, 2010

Subject: Configuration Management the build system's job? - by: Eric Minick

It can be a blend.

You mention that determining which components (and versions of those components) should be used is the job of people. That should be true, until the people decide that there are obvious rules like "Use the latest version of the logging library approved by the security team" or "Latest build of that other related project".

Once there are rules, the mundane work of actually looking up the correct version and provisioning it into the build workspace can, and should, be handled by the build system. All mundane, repetitive, rule based work should be pushed to automation if possible to free up smart, creative, and less consistent people to work on interesting things - like defining the darn rules in the first place.

I suspect the SVN folks are used to working in a straight forward environment where clear rules made it easy to offload the work to automation. If the rules aren't defineable in your environment, the first question to ask is "why?". Is it because it's hard to formally track what's approved / released / built from various teams? You can fix that. It's possible that things are genuinely hard and human intervention is required. That tends to slow things down and I try to drive it out of the process where possible.

Keep in mind that there is a difference between a build tool like Make and Ant which are compile / package tools and larger build management frameworks which handle component provisioning, etc.


View the original article here

Monday, November 1, 2010

Evolution of Continuous Integration - by: Eric Minick

Agile in the development team is more or less reality. It seems like everyone is either Agile or planning to move to it (if only in name). But as Jeffery pointed out, faster releases from Dev places more strain on test and ops. That's where the big changes are going to be happening.
Even as that goes on, it will put pressure on other groups. I'm hearing, "How come the app teams are able to build and release so quickly while our business intelligence reports take a long time to migrate?" In response to the need for faster BI migrations, we're starting to add support for applying DevOps to BI tooling in AnthillPro. At the same time, the BI tool vendors are clearly feeling some pressure and adding more automation friendly APIs.
In short: Agile isn't just for application developers anymore.
The cloud is interesting. I think it's mostly finding a role right now around test. How do I let my developers spin up private sand-boxes to test the software? If I have a new code line, how do I spin up the 10 VMs required to really put it through it's functional tests in 15 minutes rather than 15 days?
View the original article here