Psake 2.01 and hierarchical build scripts?

6 views
Skip to first unread message

Patrick van der Velde

unread,
Oct 15, 2009, 5:20:11 PM10/15/09
to psak...@googlegroups.com
Hi Guys

I just saw the notice that 2.01 has been released and so I wanted to
try it on our build process but unfortunately it fails :( From the
looks of it this is due to the fact that we're running a set of
hierarchical build scripts. i.e:
- build.ps1
- product1.ps1
- product2.ps1

where build.ps1 calls the product build scripts in order. The error I get is:

product2.ps1:Exception calling "Pop" with "0"
argument(s): "Stack empty"

I'm pretty sure this is due to the fact the stack gets killed as soon
as the second build script exits but there should have been some more
elements on that stack. From what I can see this is due to the fact
that psake uses some script-level global variables which get clobbered
if you run psake multiple times from inside a psake task call.

I just wanted to let you guys know about this problem in case nobody
else runs into it :)

Thanks heaps for the new version, it looks like psake is going to be
an awesome build runner :)

Regards

Patrick

Jorge Matos

unread,
Oct 16, 2009, 2:39:48 AM10/16/09
to psak...@googlegroups.com
Patrick,

Feel free to submit an svn patch if you'd like to a shot at fixing it, or if
anyone else in the dev group would like to tackle it by all means feel free
to submit an svn patch as well. Remind me in a week or so if the issue
hasn't been fixed and I'll see what I can do.

--------------------------------------------------
From: "Patrick van der Velde" <petrikva...@gmail.com>
Sent: Thursday, October 15, 2009 4:20 PM
To: <psak...@googlegroups.com>
Subject: Psake 2.01 and hierarchical build scripts?

Patrick van der Velde

unread,
Oct 16, 2009, 6:12:02 AM10/16/09
to psak...@googlegroups.com
Hi Jorge

I've got a modified psake version based on the previous v2 that was in
your branch on google code. Unfortunately the new v2 code has changed
so much that it didn't look like it would be an easy merge so I'd have
to rewrite the code again. At the moment I'm way to busy to have
another crack at updating the new code. Also I'm pretty sure there is
a better way of solving the problem than the solution I had but my
powershell skills aren't very good.

I can send you my version which might be helpful.

Regards

Patrick
Reply all
Reply to author
Forward
0 new messages