1. psake
build with < <>
21 June 2012

2. Agenda
Quick recap of the landscape & problem domain
Brief tour of psake
Discussion

3. Build is not
ctrl + shift + b
That is compiling. Good for
Local testing
One man projects
Demos

4. Build is
Separate process
Documented
Exactly repeatable
Has different goals to compiling
Can be made up of more than 1 solution.
Can have non-code artifacts

5. Build evolution
Continuous
Deployment
Continuous
Integration
Value
Build
Compiling
Complexity

6. Introducing psake
sake – as in the drink, not as in make, rake, bake

7. I can’t pronounce: those
Sake – Japanese drink
Make (C++)
Bake (Boo)
Rake (Ruby)
P?
POWERSHELL
psake = a Powershell powered build system

8. .NET has
MSBuild
From Microsoft
Aligned to VS & TFS releases
Love you some xml
Backwards & Forwards compat is hard
NAnt
Based off Ant
Better XML, but still XML
Has it’s own set of compat issues because it is not aligned
psake is directly built to address those issues

9. Silly demo time

10. What about TFS & Jenkins
TFS & Jenkins are build servers
TFS knows MSBuild & can build/extend it for your
needed
Not trivial if you do not want msbuild
Jenkins knows everyone, thanks to plugins
Hudson even knows psake
They do more than build – they report & manage
output

11. Can it do CI or Deployments?
Yeah – sure it can
Anything you can do in PowerShell it can do

12. Questions?