Regenerate docs
This commit is contained in:
		
							parent
							
								
									8375f480d6
								
							
						
					
					
						commit
						a8f7338273
					
				|  | @ -474,7 +474,7 @@ | |||
| 
 | ||||
| <p>Prepare your Kubernetes cluster and set up your <code>kubectl</code> access.</p> | ||||
| 
 | ||||
| <p>Once you have running Kubernetes cluster you can focus on installing <strong>Jenkins Operator</strong> according to the <a href="/docs/installation/">Installation</a> guide.</p> | ||||
| <p>Once you have a running Kubernetes cluster you can focus on installing <strong>Jenkins Operator</strong> according to the <a href="/docs/installation/">Installation</a> guide.</p> | ||||
| 
 | ||||
|         <div class="section-index"> | ||||
|      | ||||
|  |  | |||
|  | @ -634,7 +634,7 @@ for backup and restore are required, e.g.:</p> | |||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>echo<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#4e9a06">"Running backup #${backup_number}"</span><span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>BACKUP_TMP_DIR=$(mktemp<span style="color:#f8f8f8;text-decoration:underline"> </span>-d)<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>tar<span style="color:#f8f8f8;text-decoration:underline"> </span>-C<span style="color:#f8f8f8;text-decoration:underline"> </span>${JENKINS_HOME}<span style="color:#f8f8f8;text-decoration:underline"> </span>-czf<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#4e9a06">"${BACKUP_TMP_DIR}/${backup_number}.tar.gz"</span><span style="color:#f8f8f8;text-decoration:underline"> </span>--exclude<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs/<span style="color:#8f5902;font-style:italic">*/config.xml</span><span style="color:#f8f8f8;text-decoration:underline"> </span>--exclude<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs/<span style="color:#8f5902;font-style:italic">*/workspace*</span><span style="color:#f8f8f8;text-decoration:underline"> </span>-c<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#8f5902;font-style:italic">&&</span><span style="color:#f8f8f8;text-decoration:underline"> </span>\<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>tar<span style="color:#f8f8f8;text-decoration:underline"> </span>-C<span style="color:#f8f8f8;text-decoration:underline"> </span>${JENKINS_HOME}<span style="color:#f8f8f8;text-decoration:underline"> </span>-czf<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#4e9a06">"${BACKUP_TMP_DIR}/${backup_number}.tar.gz"</span><span style="color:#f8f8f8;text-decoration:underline"> </span>--exclude<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs/<span style="color:#8f5902;font-style:italic">*/workspace*</span><span style="color:#f8f8f8;text-decoration:underline"> </span>-c<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#8f5902;font-style:italic">&&</span><span style="color:#f8f8f8;text-decoration:underline"> </span>\<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>aws<span style="color:#f8f8f8;text-decoration:underline"> </span>s3<span style="color:#f8f8f8;text-decoration:underline"> </span>cp<span style="color:#f8f8f8;text-decoration:underline"> </span>${BACKUP_TMP_DIR}/${backup_number}.tar.gz<span style="color:#f8f8f8;text-decoration:underline"> </span>s3<span style="color:#000;font-weight:bold">:</span>//${BACKUP_BUCKET}/${BACKUP_PATH}/${backup_number}.tar.gz<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>echo<span style="color:#f8f8f8;text-decoration:underline"> </span>Done<span style="color:#f8f8f8;text-decoration:underline"> | ||||
|  |  | |||
|  | @ -809,7 +809,7 @@ for backup and restore are required, e.g.:</p> | |||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>echo<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#4e9a06">&#34;Running backup #${backup_number}&#34;</span><span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>BACKUP_TMP_DIR=$(mktemp<span style="color:#f8f8f8;text-decoration:underline"> </span>-d)<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>tar<span style="color:#f8f8f8;text-decoration:underline"> </span>-C<span style="color:#f8f8f8;text-decoration:underline"> </span>${JENKINS_HOME}<span style="color:#f8f8f8;text-decoration:underline"> </span>-czf<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#4e9a06">&#34;${BACKUP_TMP_DIR}/${backup_number}.tar.gz&#34;</span><span style="color:#f8f8f8;text-decoration:underline"> </span>--exclude<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs/<span style="color:#8f5902;font-style:italic">*/config.xml</span><span style="color:#f8f8f8;text-decoration:underline"> </span>--exclude<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs/<span style="color:#8f5902;font-style:italic">*/workspace*</span><span style="color:#f8f8f8;text-decoration:underline"> </span>-c<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#8f5902;font-style:italic">&amp;&amp;</span><span style="color:#f8f8f8;text-decoration:underline"> </span>\<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>tar<span style="color:#f8f8f8;text-decoration:underline"> </span>-C<span style="color:#f8f8f8;text-decoration:underline"> </span>${JENKINS_HOME}<span style="color:#f8f8f8;text-decoration:underline"> </span>-czf<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#4e9a06">&#34;${BACKUP_TMP_DIR}/${backup_number}.tar.gz&#34;</span><span style="color:#f8f8f8;text-decoration:underline"> </span>--exclude<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs/<span style="color:#8f5902;font-style:italic">*/workspace*</span><span style="color:#f8f8f8;text-decoration:underline"> </span>-c<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#8f5902;font-style:italic">&amp;&amp;</span><span style="color:#f8f8f8;text-decoration:underline"> </span>\<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>aws<span style="color:#f8f8f8;text-decoration:underline"> </span>s3<span style="color:#f8f8f8;text-decoration:underline"> </span>cp<span style="color:#f8f8f8;text-decoration:underline"> </span>${BACKUP_TMP_DIR}/${backup_number}.tar.gz<span style="color:#f8f8f8;text-decoration:underline"> </span>s3<span style="color:#000;font-weight:bold">:</span>//${BACKUP_BUCKET}/${BACKUP_PATH}/${backup_number}.tar.gz<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>echo<span style="color:#f8f8f8;text-decoration:underline"> </span>Done<span style="color:#f8f8f8;text-decoration:underline"> | ||||
|  | @ -871,7 +871,7 @@ the number of backups under control, e.g. Cloud Formation fragment:</p> | |||
| <p>In <code>v0.1.x</code> <strong>Jenkins Operator</strong> user configuration application was implemented using <strong>Jenkins</strong> jobs | ||||
| and this mechanism was replaced since <code>v0.2.0</code> with Groovy scripts implementing the same functionality.</p> | ||||
| 
 | ||||
| <p>As a result the <strong>Jenkins</strong> configuration jobs (&ldquo;Configure Seed Jobs&rdquo;, &ldquo;jenkins-operator-base-configuration&rdquo;, &ldquo;jenkins-operator-user-configuration&rdquo;) are no longer visible in <strong>Jenkins</strong> UI.</p> | ||||
| <p>As a result, the <strong>Jenkins</strong> configuration jobs (&ldquo;Configure Seed Jobs&rdquo;, &ldquo;jenkins-operator-base-configuration&rdquo;, &ldquo;jenkins-operator-user-configuration&rdquo;) are no longer visible in <strong>Jenkins</strong> UI.</p> | ||||
| 
 | ||||
| <p>In <code>v0.1.x</code> you can see if any of the configuration jobs failed or succeded in the <strong>Jenkins</strong> UI (job build logs). | ||||
| Instead, you can make sure the operator is running correctly by inspecting its logs, e.g.:</p> | ||||
|  |  | |||
|  | @ -520,7 +520,7 @@ | |||
| <p>In <code>v0.1.x</code> <strong>Jenkins Operator</strong> user configuration application was implemented using <strong>Jenkins</strong> jobs | ||||
| and this mechanism was replaced since <code>v0.2.0</code> with Groovy scripts implementing the same functionality.</p> | ||||
| 
 | ||||
| <p>As a result the <strong>Jenkins</strong> configuration jobs (“Configure Seed Jobs”, “jenkins-operator-base-configuration”, “jenkins-operator-user-configuration”) are no longer visible in <strong>Jenkins</strong> UI.</p> | ||||
| <p>As a result, the <strong>Jenkins</strong> configuration jobs (“Configure Seed Jobs”, “jenkins-operator-base-configuration”, “jenkins-operator-user-configuration”) are no longer visible in <strong>Jenkins</strong> UI.</p> | ||||
| 
 | ||||
| <p>In <code>v0.1.x</code> you can see if any of the configuration jobs failed or succeded in the <strong>Jenkins</strong> UI (job build logs). | ||||
| Instead, you can make sure the operator is running correctly by inspecting its logs, e.g.:</p> | ||||
|  |  | |||
|  | @ -35,7 +35,7 @@ | |||
| 
 | ||||
| <meta itemprop="datePublished" content="2019-08-05T00:00:00+00:00" /> | ||||
| <meta itemprop="dateModified" content="2019-08-05T00:00:00+00:00" /> | ||||
| <meta itemprop="wordCount" content="242"> | ||||
| <meta itemprop="wordCount" content="244"> | ||||
| 
 | ||||
| 
 | ||||
| 
 | ||||
|  | @ -489,12 +489,12 @@ | |||
| 	<div class="lead">How to customize Jenkins</div> | ||||
| 	 | ||||
| 
 | ||||
| <p>Jenkins can be customized using by groovy scripts or the Jenkins Configuration as Code Plugin. All custom configuration is stored in | ||||
| <p>Jenkins can be customized by using groovy scripts or the Jenkins Configuration as a Code Plugin. All custom configuration is stored in | ||||
| the <strong>jenkins-operator-user-configuration-<cr_name></strong> ConfigMap, which is automatically created by the <strong>Jenkins Operator</strong>.</p> | ||||
| 
 | ||||
| <p>The <strong>Jenkins Operator</strong> creates a <strong>jenkins-operator-user-configuration-<cr_name></strong> secret where the user can store sensitive | ||||
| information used for custom configuration. If you have an entry in the secret named <code>PASSWORD</code> then you can use it in the | ||||
| Jenkins Configuration as Code Plugin as <code>adminAddress: "${PASSWORD}"</code>.</p> | ||||
| Jenkins Configuration as a Code Plugin as <code>adminAddress: "${PASSWORD}"</code>.</p> | ||||
| 
 | ||||
| <pre><code>kubectl get secret jenkins-operator-user-configuration-<cr_name> -o yaml | ||||
| 
 | ||||
|  |  | |||
|  | @ -366,12 +366,12 @@ The <code>/sbin/tini -s -- /usr/local/bin/jenkins.sh</code> command | |||
|          | ||||
|          | ||||
| 
 | ||||
| <p>Jenkins can be customized using by groovy scripts or the Jenkins Configuration as Code Plugin. All custom configuration is stored in | ||||
| <p>Jenkins can be customized by using groovy scripts or the Jenkins Configuration as a Code Plugin. All custom configuration is stored in | ||||
| the <strong>jenkins-operator-user-configuration-<cr_name></strong> ConfigMap, which is automatically created by the <strong>Jenkins Operator</strong>.</p> | ||||
| 
 | ||||
| <p>The <strong>Jenkins Operator</strong> creates a <strong>jenkins-operator-user-configuration-<cr_name></strong> secret where the user can store sensitive | ||||
| information used for custom configuration. If you have an entry in the secret named <code>PASSWORD</code> then you can use it in the | ||||
| Jenkins Configuration as Code Plugin as <code>adminAddress: &quot;${PASSWORD}&quot;</code>.</p> | ||||
| Jenkins Configuration as a Code Plugin as <code>adminAddress: &quot;${PASSWORD}&quot;</code>.</p> | ||||
| 
 | ||||
| <pre><code>kubectl get secret jenkins-operator-user-configuration-&lt;cr_name&gt; -o yaml | ||||
| 
 | ||||
|  |  | |||
|  | @ -79,7 +79,7 @@ | |||
|          | ||||
|         <p><strong>Jenkins Operator</strong> is fully compatible with <strong><code>jenkins:lts</code></strong> Docker image and does not introduce any hidden changes to the upstream Jenkins.</p> | ||||
| 
 | ||||
| <p>If needed, the Docker image can easily be changed in custom resource manifest as long as it supports standard Jenkins file system structure.</p> | ||||
| <p>If needed, the Docker image can be easily changed in custom resource manifest as long as it supports standard Jenkins file system structure.</p> | ||||
| 
 | ||||
|       </description> | ||||
|     </item> | ||||
|  |  | |||
|  | @ -477,7 +477,7 @@ | |||
| 	<div class="lead">Jenkins default image details</div> | ||||
| 	<p><strong>Jenkins Operator</strong> is fully compatible with <strong><code>jenkins:lts</code></strong> Docker image and does not introduce any hidden changes to the upstream Jenkins.</p> | ||||
| 
 | ||||
| <p>If needed, the Docker image can easily be changed in custom resource manifest as long as it supports standard Jenkins file system structure.</p> | ||||
| <p>If needed, the Docker image can be easily changed in custom resource manifest as long as it supports standard Jenkins file system structure.</p> | ||||
| 
 | ||||
| 	 | ||||
| 	 | ||||
|  |  | |||
|  | @ -954,12 +954,12 @@ spec: | |||
|          | ||||
|          | ||||
| 
 | ||||
| <p>Jenkins can be customized using by groovy scripts or the Jenkins Configuration as Code Plugin. All custom configuration is stored in | ||||
| <p>Jenkins can be customized by using groovy scripts or the Jenkins Configuration as a Code Plugin. All custom configuration is stored in | ||||
| the <strong>jenkins-operator-user-configuration-<cr_name></strong> ConfigMap, which is automatically created by the <strong>Jenkins Operator</strong>.</p> | ||||
| 
 | ||||
| <p>The <strong>Jenkins Operator</strong> creates a <strong>jenkins-operator-user-configuration-<cr_name></strong> secret where the user can store sensitive | ||||
| information used for custom configuration. If you have an entry in the secret named <code>PASSWORD</code> then you can use it in the | ||||
| Jenkins Configuration as Code Plugin as <code>adminAddress: &quot;${PASSWORD}&quot;</code>.</p> | ||||
| Jenkins Configuration as a Code Plugin as <code>adminAddress: &quot;${PASSWORD}&quot;</code>.</p> | ||||
| 
 | ||||
| <pre><code>kubectl get secret jenkins-operator-user-configuration-&lt;cr_name&gt; -o yaml | ||||
| 
 | ||||
|  | @ -1411,7 +1411,7 @@ for backup and restore are required, e.g.:</p> | |||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>echo<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#4e9a06">&#34;Running backup #${backup_number}&#34;</span><span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>BACKUP_TMP_DIR=$(mktemp<span style="color:#f8f8f8;text-decoration:underline"> </span>-d)<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>tar<span style="color:#f8f8f8;text-decoration:underline"> </span>-C<span style="color:#f8f8f8;text-decoration:underline"> </span>${JENKINS_HOME}<span style="color:#f8f8f8;text-decoration:underline"> </span>-czf<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#4e9a06">&#34;${BACKUP_TMP_DIR}/${backup_number}.tar.gz&#34;</span><span style="color:#f8f8f8;text-decoration:underline"> </span>--exclude<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs/<span style="color:#8f5902;font-style:italic">*/config.xml</span><span style="color:#f8f8f8;text-decoration:underline"> </span>--exclude<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs/<span style="color:#8f5902;font-style:italic">*/workspace*</span><span style="color:#f8f8f8;text-decoration:underline"> </span>-c<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#8f5902;font-style:italic">&amp;&amp;</span><span style="color:#f8f8f8;text-decoration:underline"> </span>\<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>tar<span style="color:#f8f8f8;text-decoration:underline"> </span>-C<span style="color:#f8f8f8;text-decoration:underline"> </span>${JENKINS_HOME}<span style="color:#f8f8f8;text-decoration:underline"> </span>-czf<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#4e9a06">&#34;${BACKUP_TMP_DIR}/${backup_number}.tar.gz&#34;</span><span style="color:#f8f8f8;text-decoration:underline"> </span>--exclude<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs/<span style="color:#8f5902;font-style:italic">*/workspace*</span><span style="color:#f8f8f8;text-decoration:underline"> </span>-c<span style="color:#f8f8f8;text-decoration:underline"> </span>jobs<span style="color:#f8f8f8;text-decoration:underline"> </span><span style="color:#8f5902;font-style:italic">&amp;&amp;</span><span style="color:#f8f8f8;text-decoration:underline"> </span>\<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>aws<span style="color:#f8f8f8;text-decoration:underline"> </span>s3<span style="color:#f8f8f8;text-decoration:underline"> </span>cp<span style="color:#f8f8f8;text-decoration:underline"> </span>${BACKUP_TMP_DIR}/${backup_number}.tar.gz<span style="color:#f8f8f8;text-decoration:underline"> </span>s3<span style="color:#000;font-weight:bold">:</span>//${BACKUP_BUCKET}/${BACKUP_PATH}/${backup_number}.tar.gz<span style="color:#f8f8f8;text-decoration:underline"> | ||||
| </span><span style="color:#f8f8f8;text-decoration:underline">    </span>echo<span style="color:#f8f8f8;text-decoration:underline"> </span>Done<span style="color:#f8f8f8;text-decoration:underline"> | ||||
|  | @ -1460,7 +1460,7 @@ the number of backups under control, e.g. Cloud Formation fragment:</p> | |||
|          | ||||
|         <p><strong>Jenkins Operator</strong> is fully compatible with <strong><code>jenkins:lts</code></strong> Docker image and does not introduce any hidden changes to the upstream Jenkins.</p> | ||||
| 
 | ||||
| <p>If needed, the Docker image can easily be changed in custom resource manifest as long as it supports standard Jenkins file system structure.</p> | ||||
| <p>If needed, the Docker image can be easily changed in custom resource manifest as long as it supports standard Jenkins file system structure.</p> | ||||
| 
 | ||||
|       </description> | ||||
|     </item> | ||||
|  | @ -1489,7 +1489,7 @@ the number of backups under control, e.g. Cloud Formation fragment:</p> | |||
| <p>In <code>v0.1.x</code> <strong>Jenkins Operator</strong> user configuration application was implemented using <strong>Jenkins</strong> jobs | ||||
| and this mechanism was replaced since <code>v0.2.0</code> with Groovy scripts implementing the same functionality.</p> | ||||
| 
 | ||||
| <p>As a result the <strong>Jenkins</strong> configuration jobs (&ldquo;Configure Seed Jobs&rdquo;, &ldquo;jenkins-operator-base-configuration&rdquo;, &ldquo;jenkins-operator-user-configuration&rdquo;) are no longer visible in <strong>Jenkins</strong> UI.</p> | ||||
| <p>As a result, the <strong>Jenkins</strong> configuration jobs (&ldquo;Configure Seed Jobs&rdquo;, &ldquo;jenkins-operator-base-configuration&rdquo;, &ldquo;jenkins-operator-user-configuration&rdquo;) are no longer visible in <strong>Jenkins</strong> UI.</p> | ||||
| 
 | ||||
| <p>In <code>v0.1.x</code> you can see if any of the configuration jobs failed or succeded in the <strong>Jenkins</strong> UI (job build logs). | ||||
| Instead, you can make sure the operator is running correctly by inspecting its logs, e.g.:</p> | ||||
|  |  | |||
|  | @ -496,7 +496,7 @@ because <strong>Jenkins Operator</strong> calls Jenkins API.</p> | |||
| <li>basic settings - use <code>Mode.EXCLUSIVE</code> - Jobs must specify that they want to run on master node</li> | ||||
| <li>enable CSRF - Cross Site Request Forgery Protection is enabled</li> | ||||
| <li>disable usage stats - Jenkins usage stats submitting is disabled</li> | ||||
| <li>enable master access control - Slave To Master Access Control is enabled</li> | ||||
| <li>enable master access control - Slave to Master Access Control is enabled</li> | ||||
| <li>disable old JNLP protocols - <code>JNLP3-connect</code>, <code>JNLP2-connect</code> and <code>JNLP-connect</code> are disabled</li> | ||||
| <li>disable CLI - CLI access of <code>/cli</code> URL is disabled</li> | ||||
| <li>configure kubernetes-plugin - secure configuration for Kubernetes plugin</li> | ||||
|  |  | |||
|  | @ -225,12 +225,15 @@ | |||
| 
 | ||||
| <div class="col-lg-4 mb-5 mb-lg-0 text-center "> | ||||
|   <div class="mb-4 h1"> | ||||
|     <i class="fas fa-bug"></i> | ||||
|     <i class="fab fa-slack"></i> | ||||
|   </div> | ||||
|   <h4 class="h3">Bugs</h4> | ||||
|   <p class="mb-0"><p>Help us work on the software by reporting or fixing bugs. Make the Jenkins Operator better.</p> | ||||
|   <h4 class="h3">Join #jenkins-operator on Slack!</h4> | ||||
|   <p class="mb-0"><p>Ask questions, receive help and talk with other users about operator on dedicated Slack channel.</p> | ||||
| 
 | ||||
| <p><a href="https://forms.gle/X3X8qA1XMirdBuEH7">Invite form</a> | ||||
| <a href="https://virtuslab-oss.slack.com">Go to Slack</a></p> | ||||
| </p> | ||||
|   <p><a href="https://github.com/jenkinsci/kubernetes-operator/issues">Read more …</a></p> | ||||
|    | ||||
| </div> | ||||
| 
 | ||||
| 		</div> | ||||
|  |  | |||
		Loading…
	
		Reference in New Issue