Skip to content

Commit 2ca1693

Browse files
committed
add more tutorial titles
1 parent c79cf0c commit 2ca1693

File tree

5 files changed

+33
-24
lines changed

5 files changed

+33
-24
lines changed

docs/user/index.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,9 @@ side-bar.
2121
tutorials/05_deploy_example
2222
tutorials/06_ioc_changes
2323
tutorials/07_generic_ioc
24-
tutorials/08_support_module
24+
tutorials/08_debug_generic_ioc
25+
tutorials/09_test_generic_ioc
26+
tutorials/10_support_module
2527

2628
+++
2729

docs/user/tutorials/07_generic_ioc.rst

Lines changed: 1 addition & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -290,34 +290,12 @@ directory:
290290
.. warning::
291291

292292
This will FAIL. There is a deliberate error which we will fix in the next
293-
step.
293+
Tutorial.
294294

295295
You should see this error::
296296

297297
../URLDriver.cpp:22:10: fatal error: Magick++.h: No such file or directory
298298

299-
Investigate the Build Failure
300-
-----------------------------
301-
302-
When a container build fails the container image is created up to the point
303-
where the last successful Dockerfile command was run. This means that we can
304-
investigate the build failure by running a shell in the container. ``ec``
305-
provides us with the following convenience command to do this:
306-
307-
.. code-block:: bash
308-
309-
ec dev debug-last
310-
311-
Now we have a prompt inside the part build container and can retry the failed
312-
command.
313-
314-
.. code-block:: bash
315-
316-
cd /repos/epics/support/adurl
317-
make
318-
319-
You should see the same error again.
320-
321299

322300

323301

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
Debugging Generic IOC Builds
2+
============================
3+
4+
This tutorial is a continuation of `07_generic_ioc`. Here we will look into
5+
debugging failed builds and fix the build failure from the previous tutorial.
6+
7+
Investigate the Build Failure
8+
-----------------------------
9+
10+
When a container build fails the container image is created up to the point
11+
where the last successful Dockerfile command was run. This means that we can
12+
investigate the build failure by running a shell in the container. ``ec``
13+
provides us with the following convenience command to do this:
14+
15+
.. code-block:: bash
16+
17+
ec dev debug-last
18+
19+
Now we have a prompt inside the part-built container and can retry the failed
20+
command.
21+
22+
.. code-block:: bash
23+
24+
cd /repos/epics/support/adurl
25+
make
26+
27+
You should see the same error again.
Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
Testing and Deploying a Generic IOC
2+
===================================
File renamed without changes.

0 commit comments

Comments
 (0)