In the latest beta (1.0.0.1647) the PowerShell task lets you run PS scripts and pass arguments into the scripts, which lovely stuff.
The scripts are external to Continua and it would be very useful to also be able to embed the script into Continua and for it to be run by Continua.
Further to this, we should be able to use Continua variables inside the scripts that are replaced by Continua before the script is run.
We did consider this, in fact in early pre-beta builds thats how the powershell action was implemented. The reason we changed it is because we are trying to avoid windows dependencies in the agents, as we hope to have agents running on other platforms using mono at some point. We will revisit this in the future as it should now be possible to have agents with different sets of actions due to other architecture changes since we made that change.
I’ve been thinking about this a slightly different way. In my repositories, I’ve added a {myrepo}\ci\ folder to include all the finalbuilder components etc. However for upgrading web sites, I have a couple of powershell scripts that automate IIS tasks to configure a maintenance site during upgrades, so Joe Public doesn’t have a bad user experience. I figured I would be able to use Continua and powershell using that approach. Just my two cents.
@Vincent: Okay, that sounds good. It would be nice to have the scripts in the CI. What about automatic injection of parameters into the scripts?
@ Jamie: yes, that’s probably what I’m going to be doing too.