Better TeamCity integration?

[Borek Bernard]

Is it correct that currently, in order for these instructions to work:
https://github.com/psake/psake/wiki/How-can-I-integrate-psake-with-Team-City%3F,
one must include psake.ps1 and psake.psm1 in the source control
repository? I tried not to but unsurprisingly, the build failed with
the "term '.\psake.ps1' is not recognized" error.

I am new to both PowerShell and psake so I may be doing something
wrong but if it is true that psake.ps1 and psm1 need to be included in
the repository, it doesn't feel quite right to me (I also don't
include msbuild.exe in order to build my solution etc. - hope you get
the point).

So the question is, isn't there a specialized TeamCity plugin that
would run PowerShell with psake preconfigured?

Thanks,
Borek

[James Kovacs]

You need to include psake in your repository. This is fairly typical of 3rd-party build systems (e.g. not MSBuild), including NAnt and others. The major advantage is that different projects can use different versions of the build tool without collision. You can upgrade to a new version or include fixes to the build system (e.g. psake) without worrying that you'll break another unrelated project. If you're worried about the size, psake.psm1 is 679 lines of Powershell including comments, documentation, and whitespace. All of psake is roughly 616kB of highly compressible text. So it's not going to bloat your repository.

HTH,
James
--
James Kovacs, B.Sc., M.Sc.
http://jameskovacs.com
jko...@post.harvard.edu
@jameskovacs (Twitter)
403-397-3177 (mobile)
jameskovacs (Skype)

--
You received this message because you are subscribed to the Google Groups "psake-users" group.
To post to this group, send email to psake...@googlegroups.com.
To unsubscribe from this group, send email to psake-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/psake-users?hl=en.

[Borek Bernard]

Thanks. I've asked also because I have had hard times integrating
psake with TeamCity so at that time I would appreciate a runner that
would "just work" (the problem was that psake was not reporting
failures to TeamCity and the build always appeared as green). But we
now have a fixed version of psake in our repository so we ended up
using what you suggested :)

Thanks,
Borek

On 9 ún, 20:07, James Kovacs <jkov...@post.harvard.edu> wrote:
> You need to include psake in your repository. This is fairly typical of
> 3rd-party build systems (e.g. not MSBuild), including NAnt and others. The
> major advantage is that different projects can use different versions of
> the build tool without collision. You can upgrade to a new version or
> include fixes to the build system (e.g. psake) without worrying that you'll
> break another unrelated project. If you're worried about the size,
> psake.psm1 is 679 lines of Powershell including comments, documentation,
> and whitespace. All of psake is roughly 616kB of highly compressible text.
> So it's not going to bloat your repository.
>
> HTH,
> James
> --
> James Kovacs, B.Sc., M.Sc.http://jameskovacs.com

> jkov...@post.harvard.edu

> @jameskovacs (Twitter)
> 403-397-3177 (mobile)
> jameskovacs (Skype)
>
>
>
>
>
>
>
> On Sat, Feb 4, 2012 at 7:29 PM, Borek Bernard <bor...@gmail.com> wrote:
> > Is it correct that currently, in order for these instructions to work:
>

> >https://github.com/psake/psake/wiki/How-can-I-integrate-psake-with-Te...
> > ,