Difference between revisions of "Using Hudson/Using other shells (for ex. Python)"

Revision as of 17:18, 5 December 2012

This article is a stub. It will be expanded as content is migrated from the Hudson-CIWeb site.

On Windows using cmd.exe can be a burden. Fortunately Hudson allows the use of other shells.

A different shell can be used for each "Execute shell" build step of a job - even on Windows.

Note the inline help for the "Execute shell" build step type.

Examples of "Execute shell" build steps for Windows using Python as the shell:

#!python.exe
print 1

#!C:\Python25\python.exe
print 1

Note that you can also pass parameters to the shell, like:

#!python.exe -u
#From "python -h": -u     : unbuffered binary stdout and stderr (also PYTHONUNBUFFERED=x)
print 1

@@ Line 1: / Line 1: @@
 This article is a stub. It will be expanded as content is migrated from the [http://wiki.hudson-ci.org/display/HUDSON/Use+Hudson|Use Hudson-CI]Web site.
+<br>
+On Windows using cmd.exe can be a burden. Fortunately Hudson allows the use of other shells.
+A different shell can be used for each "Execute shell" build step of a job - even on Windows.
+Note the inline help for the "Execute shell" build step type.
+Examples of "Execute shell" build steps for Windows using Python as the shell:
+<pre>#!python.exe
+print 1</pre><pre>#!C:\Python25\python.exe
+print 1</pre>
+Note that you can also pass parameters to the shell, like:
+<pre>#!python.exe -u
+#From "python -h": -u     : unbuffered binary stdout and stderr (also PYTHONUNBUFFERED=x)
+print 1</pre>
+<br><br>