You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: doc/jobs/ci_jobs.rst
+17-17
Original file line number
Diff line number
Diff line change
@@ -44,8 +44,6 @@ It generates three Dockerfiles: one to perform the *create-workspace* task to
44
44
populate the workspace and enumerate prerequisites, one to perform the
45
45
*build-and-install* task, and one to perform the *build-and-test* task.
46
46
47
-
A typical job runs 4 Dockerfiles in all.
48
-
49
47
Create workspace
50
48
^^^^^^^^^^^^^^^^
51
49
@@ -56,7 +54,7 @@ The task performs the following steps:
56
54
57
55
* Prepare the package sources
58
56
59
-
* Fetches the `.repos` file(s)
57
+
* Fetches the ``.repos`` file(s)
60
58
* Fetches the source repositories containing the package(s) to be built
61
59
* If necessary, switches the branch in those repositories
62
60
@@ -86,11 +84,11 @@ Known limitations
86
84
^^^^^^^^^^^^^^^^^
87
85
88
86
System dependency enumeration happens for all ROS packages that are part of the
89
-
non-underlay workspace. This means that any non-ROS packages present in that
90
-
workspace may need their dependencies explicitly called out for inclusion in
91
-
the foundation package list, and also means that a missing dependency may be
92
-
occluded by another package in the workspace correctly declaring the same
93
-
dependency.
87
+
non-underlay workspace.
88
+
This means that any non-ROS packages present in that workspace may need their
89
+
dependencies explicitly called out for inclusion in the foundation package list,
90
+
and also means that a missing dependency may be occluded by another package in
91
+
the workspace correctly declaring the same dependency.
94
92
95
93
Run the *CI* job locally
96
94
------------------------
@@ -111,10 +109,10 @@ from ROS *Crystal* for Ubuntu *Bionic* *amd64*:
111
109
Return code
112
110
-----------
113
111
114
-
The return code of the generated script will be zero if it successfully performed
115
-
the build and ran the test even if some tests failed. By setting the environment
116
-
variable `ABORT_ON_TEST_FAILURE=1` the return code will also be non-zero in case
117
-
of failed tests.
112
+
The return code of the generated script will be zero if it successfully
113
+
performed the build and ran the test even if some tests failed.
114
+
By setting the environment variable ``ABORT_ON_TEST_FAILURE=1`` the return code
115
+
will also be non-zero in case of failed tests.
118
116
119
117
Instead of invoking the generated script it can also be *sourced*:
120
118
@@ -127,12 +125,13 @@ The return code of the invocation of ``catkin_tests_results`` /
127
125
``test_result_RC``.
128
126
129
127
Run the *CI* job on Travis
130
-
-----------------------------
128
+
--------------------------
131
129
132
130
Since it is easy to run a *CI* job locally it can also be run on Travis to
133
-
either test every commit or pull request. The setup and invocation is the same
134
-
as locally. The following .travis.yml template is a good starting point and is
135
-
ready to be use:
131
+
either test every commit or pull request.
132
+
The setup and invocation is the same as locally.
133
+
The following .travis.yml template is a good starting point and is ready to be
134
+
used:
136
135
137
136
.. code:: yaml
138
137
@@ -179,7 +178,8 @@ ready to be use:
179
178
notifications:
180
179
email: false
181
180
182
-
An example can be found in the `.travis.yml <https://github.com/ros-infrastructure/ros_buildfarm/blob/master/.travis.yml>`_ file of the *ros_buildfarm* repository.
181
+
An example can be found in the `.travis.yml <https://github.com/ros-infrastructure/ros_buildfarm/blob/master/.travis.yml>`_
0 commit comments