Commit 63d0becb authored by Dimitrios Giannopoulos's avatar Dimitrios Giannopoulos
Browse files

Deployed a3035106 to develop in public with MkDocs 1.6.0 and mike 2.1.2

parent beb80f11
Loading
Loading
Loading
Loading
+1 −1

File changed.

Preview size limit exceeded, changes collapsed.

+14 −12
Original line number Diff line number Diff line
@@ -2738,20 +2738,22 @@ spec:
<p>See the following image: </p>
<p><img alt="img06.png" src="../img06.png" /></p>
<ol>
<li>Drag-Drop the _CR_SPEC characteristic of jenkinsrfs from the Service&gt;Text blocks</li>
<li>Drag-Drop Text&gt;Formatted text block</li>
<li>Drag-Drop Text&gt;Multi-line text input block</li>
<li>Copy paste the YAML text</li>
<li>Change the spec: destination:namespace to the value %s</li>
<li>Drag-Drop Lists&gt;Create list with block delete 2 items (click the gear icon). Connect it to formatted text block</li>
<li>Drag-Drop Context&gt;Current Service Order block and select the id. Connect it to the List</li>
<li>Drag-Drop the _CR_SPEC block (Set characteristic value) of jenkinsrfs from the Service &gt; Text blocks</li>
<li>Drag-Drop the Text &gt; Formatted text block and attach it after the block from the previous step</li>
<li>Drag-Drop the Text &gt; Multi-line text input block and attach it at the Input(String) connector of the block from the previous text </li>
<li>Copy paste the previously provided YAML text</li>
<li>Change the spec:destination:namespace property to the value %s</li>
<li>Drag-Drop the Lists &gt; Create list block, delete the 2 extra items (click the gear icon). Attach it at the Variables(Array) connector of the formatted text block from the previous step.</li>
<li>Drag-Drop the Service &gt; Context &gt; Current Service Order block and select the ID from the drop-down menu. Attach it to the List block of the previous step.</li>
<li>Save the PRE_PROVISION Rule</li>
</ol>
<h1 id="expose-the-service-to-your-users">Expose the service to your users</h1>
<p>Expose then as CustomerFacingServiceSpecification by using the previous RFSS as Service Specification Relationship 
1. Create a Jenkins service and mark as Bundle and save it 
2. Go to Service Specification Relationships and assign Jenkinsrfs
3. Add also a Logo if you wish</p>
<p>Expose then as CustomerFacingServiceSpecification by using the previous RFSS as Service Specification Relationship </p>
<ol>
<li>Create a Jenkins service and mark as Bundle and save it </li>
<li>Go to Service Specification Relationships and assign Jenkinsrfs</li>
<li>Add also a Logo if you wish</li>
</ol>
<p><img alt="img03.png" src="../img03.png" /></p>
<p><img alt="img04.png" src="../img04.png" /></p>
<p>Expose it now to a Category and a Catalog to be available for ordering.</p>
@@ -2769,7 +2771,7 @@ spec:
<p><img alt="img09.png" src="../img09.png" /></p>
<p>Use them to login in your Jenkins.</p>
<blockquote>
<p>Exposing Jenkins to you external is a matter of cluster configuration and request (nodeport, load balancing, etc)! This is not a topic for this example</p>
<p>Exposing Jenkins externally is a matter of cluster configuration and request (nodeport, load balancing, etc), thus is not a topic for this example</p>
</blockquote>