Carignani at 08:08, 2 July 2020

2020-07-02T08:08:13Z

← Older revision		Revision as of 10:08, 2 July 2020
Line 1:		Line 1:
			== Want to run the CI directly in Gitlab? ==
			The shared runner in Gitlab needs to be allowed by a Forge Admin. Contact '''cti_support''' at '''etsi''' dot '''org''' for more information.

	== Build scripts ==		== Build scripts ==

Carignani: Created page with "== Build scripts == The default build command for Jenkins on Forge is as follows: #!/bin/bash bash .jenkins.sh This means that Jenkins will look for a file cal..."

2018-08-06T16:26:09Z

Created page with "== Build scripts == The default build command for Jenkins on Forge is as follows: #!/bin/bash bash .jenkins.sh This means that Jenkins will look for a file cal..."

New page

== Build scripts ==

The default build command for Jenkins on Forge is as follows:

#!/bin/bash

bash .jenkins.sh

This means that Jenkins will look for a file called <code>.jenkins.sh</code> (note the dot at the beginning!) and will exectude the shell commands inside.

=== Guidelines for writing your build script ===

* Jenkins uses the '''returned exit code''' of the script to determine the outcome of the build:
** Exit status 0: successful build
** Exit status 1: build failed

=== Basic build script example ===

A very basic example for a script, assuming you need to run the <code>compile</code> command on a text file and check that an HTML file has been created

#!/bin/bash

compile myfile.txt
if [ -f myfile.html ] ; then
exit 0
else
exit 1

Get started with Jenkins - Revision history

Carignani at 08:08, 2 July 2020

Carignani: Created page with "== Build scripts == The default build command for Jenkins on Forge is as follows: #!/bin/bash bash .jenkins.sh This means that Jenkins will look for a file cal..."