Is it cool to use internal grunt tasks?

[neall]

I'm making a deploy grunt task. I made a task called scp_files to do the actual deploy, and right now my deploy task is defined like this:

grunt.registerTask('deploy', ['dist', 'scp_files']);

The dist task seems to be doing the same thing that running lineman build would do, which is nice.

On my CI machine I want to run the tests and then automatically deploy to my beta server if the tests pass.

Is there a task I can run that runs the headless tests? Should I even be relying on these tasks that Lineman defines for its own use? I would like to define a task something like this:

grunt.registerTask('ci_deploy', ['dist', '??????', 'scp_files']);

If using the internally-defined grunt tasks isn't kosher, I can always go back to running build, spec-ci, grunt deploy sequentially in a shell script.

[davemo]

you should be able to drop spec-ci into your workflow:

grunt.registerTask('ci_deploy', ['dist', 'spec-ci', 'scp_files']);

[davemo]

As for whether it's kosher, we don't have any predetermined methods of consuming the internal tasks that lineman uses; given they are exposed and part of the grunt config object I think it's entirely appropriate to use them in your own task definitions :)

[neall]

Thanks. I also threw 'clean' and 'common' on before 'dist' after looking at what lineman build does.