Deployment support for Grunt

[m]

I think it would be useful to be able to run Grunt from deployment tasks. Although I don't personally work with it so much (yet), I've been introduced to many projects where it's used for so many scripting tasks.

Although most of the other tasks here don't seem (to me, at least) to have much use in deployment mode, Grunt certainly does.

I'd be happy to do this myself when I find a few cycles, but maybe someone will beat me to it (or point out why it might not be such a good idea)

[Jason Berry]

From what I understand this would actually be fairly trivial to do, it would only require the task to implement com.atlassian.bamboo.task.CommonTaskType instead of com.atlassian.bamboo.task.TaskType.

[m]

Essentially, yes.

There's a tiny gotcha if, for some reason, we need to get some config out of the build plan.

See https://bitbucket.org/issacg/bamboo-amazon-s3/commits/bca0761a26315b2d30263e4bdc7865615afe06a4 for a diff that covers both points.

[m]

Oh, and I was thinking last night that the node.js script task and npm task might also benefit by being deployment tasks. For node script, you just never know, and it's a script language. For npm, npm publish is an excellent use-case...

[Marcin Oles]

I've slightly altered Grunt, Node and npm tasks (according to Jason's suggestion), so now they can be used in deployment projects as well.

@issacg Unfortunately I don't have access to the repository you posted the link to.