Re: Automating installer creation

Hi.

On 6/30/11 9:57 AM, Eric Steele wrote:
> Wyn's given me a private Jenkins instance that I intend to use for automating a good chunk of the release process. The Foundation has picked up a MSDN license so we'll be able to get Windows VMs running as well.
>
> I'd like to start some discussion about automating the building of installers. Since I know very little about how you go about generating those, I'll have to defer completely to you on this. What does the process look like? How much can be automated? What needs to be done by hand?

I'm not sure who "you" is in this case… SteveM and Sidnei? :-) But since 
you sent this to the list I'll chime in with the following:

* +1 for automation, especially as it leads to standardization (We've 
got some subtle differences between the various installers that should 
be eliminated IHMO)

* I'm interested in helping, and possibly even available for some values 
of interested and available.

Unfortunately, I know about as much as you do. Maybe documenting is the 
first step (I know SteveM keeps all his UI stuff in svn, but that is 
probably only part of the story.)


Alex



>
> Eric
>
>
>
> ------------------------------------------------------------------------------
> All of the data generated in your IT infrastructure is seriously valuable.
> Why? It contains a definitive record of application performance, security
> threats, fraudulent activity, and more. Splunk takes this data and makes
> sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-d2d-c2


-- 
Alex Clark · http://aclark.net


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2