Permalink
Commits on Jan 30, 2013
  1. Try load psake-config.ps1 from module directory

    when there if no psake-config.ps1 in configdir. If you want to put your
    default modules next to your psake distribution, you need a way to
    change the default configuration from you psake folder instead from the
    folder where the build script is.
    committed Jan 30, 2013
  2. Ensure TabExpansion function exists before rename.

    Prevents an error in environment where there is no initial TabExpansion function defined.
    ArturDorochowicz committed with Jan 11, 2013
  3. Fixed spec writing_psake_variables_should_pass.ps1 failure. The spec …

    …was checking .framework -eq '3.5' when this was never explicitly set. it seems like this spec was making incorrect assumptions about the framework it would be executed under.
    jeffreyabecker committed with Sep 29, 2012
  4. fixed bug in write-coloredoutput. under alternative hosts that dont s…

    …upport coloring it wasnt checking for color support and crashing
    jeffreyabecker committed with Sep 29, 2012
  5. turkish i problem fix

    yadazula committed with Jul 8, 2012
  6. Added config option to import modules into global scope. Disabled nam…

    …e checking for modules
    kblooie committed with Jun 16, 2012
  7. Fixed package script to exclude nuget directory and nuget.ext. Bumped…

    … package version to 4.2.0.1
    damianh committed with Jun 13, 2012
  8. Bumped version to 4.2

    damianh committed with Jun 10, 2012
  9. Replaced NuGetPackageBuilder.cmd with a powershell equivalent (it's a…

    … powershell lib after all)
    damianh committed with Jun 10, 2012
  10. Added NuGet.exe so NuGetPackageBuilder.cmd will run without nuget hav…

    …ing to be on the path.
    damianh committed with Jun 10, 2012
  11. wrapping the chocolateyInstall in a try catch and changing the path t…

    …o chocolatey install to use the environment variable ($env:ChocolateyInstall)
    ferventcoder committed with Jun 6, 2012
  12. The exit code from PowerShell was not being used as the exit code fro…

    …m the CMD script. This update fixes that so that the CMD script will exit with the same code that the PowerShell script exited with.
    jpoehls committed with May 25, 2012
  13. Replaced existing ResolveError with a modified variant that includes …

    …a short view, so that exceptions can be represented as one-liners for build output parsing purposes (it special cases Sql Exceptions as well to dig into the real errors)
    
    Relies on new SelectObjectWithDefault function that can safely read properties off of objects w/out adding to the $Error collection (oddly, I've found this necessary when using WinRM, so I left that code in)
    
    For instance, a short representation of an Error looks like this:
    Error:  At C:\source\project\build\modules\Sql.psm1:175 char:36 +   [Void]$database.ExecuteNonQuery <<<< ($commands) [<<==>>] Exception: Exception calling "ExecuteNonQuery" with "1" argument(s): "ExecuteNonQuery failed for Database 'a73fa37f891e46bbab9e2b23b8f87c56'. " --> ExecuteNonQuery failed for Database 'a73fa37f891e46bbab9e2b23b8f87c56'.  --> An exception occurred while executing a Transact-SQL statement or batch. --> Foreign key 'fk_file_cabinet_num' references invalid column 'file_cabinet_num' in referencing table 'file_cabinet_files'.Could not create constraint. See previous errors. --> (Line [4] Proc
    edure [] Class [16]  Number [1769] State [1] )
    
    This is much more actionable / easier to read than 50 lines of output from an Exception with 4 InnerExceptions
    Iristyle committed with May 17, 2012
  14. Minor tweaks to error output to make it consistent with what a build …

    …server like Jenkins might expect based on similarity to MSBuild output -- this is part one of the modification
    
    Part two will involve incorporating a friendlier single line error message
    
    psake#32
    Iristyle committed with May 17, 2012
  15. Internal function names have been changed from Verb-Noun to VerbNoun …

    …(without dash) in an effort to reduce potential for external collisions. Since external modules may be loaded with Verb-Noun naming after these internal functions are brought into scope, common functions like Resolve-Error are prone to get wiped out.. and to further lead to difficult to diagnose build problems.
    
    See discussion psake#33
    Iristyle committed with May 17, 2012
  16. Added test for issue with running a module function that depends on a…

    … function from another module
    kblooie committed with Apr 24, 2012
  17. Fixed formatting in .nuspec

    JamesKovacs committed with Mar 21, 2012
  18. Switched to semantic versioning

    JamesKovacs committed with Mar 21, 2012
  19. Defaulted psake to .NET 4.0

    JamesKovacs committed with Mar 21, 2012
  20. Adds support to defining an alias to a task.

    Example:
      task Task_With_Descriptive_Name -alias twdn {}
    
    By doing that I can now call .\psake.ps1 twdn and have the
    Task_With_Descriptive_Name executed
    pedroreys committed with Feb 10, 2012
Commits on Mar 19, 2012
  1. fixing case where framework is set using 3 digits (3.0/4.0). The bit …

    …substring is empty, not null. This will fix all specs.
    idavis committed Mar 19, 2012
Commits on Nov 5, 2011
  1. Added -help switch to psake.ps1 instead of psake-help.ps1 script

    Simplificated psake.cmd because of that (also removed some ifs that detected if help should be displayed, because they for example make it impossible to call task with name "help")
    whut committed Nov 5, 2011
  2. Warning (yellow colored output) when task failed with -ContinueOnError

    Also some small stuff, unified error messages, comment formating, etc
    whut committed Nov 5, 2011
  3. Task duration shows duration of task, not of task and it's dependencies

    Also added default duration of TimeSpan.Zero (to show in summary 00:00:00 instead of 0)
    And added argument to Write-TaskSummary, to make it more readable where $stopwatch variable inside that function came from, and use of where-object instead of its alias ?, to also make it more readable
    whut committed Nov 5, 2011
Commits on Nov 4, 2011
  1. Use of Cyan foreground color, instead of Blue to make it more visible…

    … on darker consoles
    
    Cyan is also commonly recommended, for example in http://blogs.msdn.com/b/abhinaba/archive/2006/01/05/509581.aspx
    whut committed Nov 4, 2011