diff --git a/docs/404.html b/docs/404.html
index acfe118..3717711 100644
--- a/docs/404.html
+++ b/docs/404.html
@@ -37,83 +37,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="/.">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="/Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="/Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="/Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="/Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
+                <li class="toctree-l1"><a class="reference internal" href="/Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-                <li class="toctree-l2"><a class="" href="/Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="/Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="/Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="/Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="/runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="/Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="/Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
diff --git a/docs/Adding_Custom-build_packages_in_Jenkins/index.html b/docs/Adding_Custom-build_packages_in_Jenkins/index.html
index 6d6b34e..46002a1 100644
--- a/docs/Adding_Custom-build_packages_in_Jenkins/index.html
+++ b/docs/Adding_Custom-build_packages_in_Jenkins/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../img/favicon.ico" />
-    <title>Adding custom-build packages in Jenkins - Cloud-V Docs</title>
+    <title>Adding Custom-build packages in Jenkins - Cloud-V Docs</title>
     <link rel="stylesheet" href="../css/theme.css" />
     <link rel="stylesheet" href="../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Adding custom-build packages in Jenkins";
+        var mkdocs_page_name = "Adding Custom-build packages in Jenkins";
         var mkdocs_page_input_path = "Adding_Custom-build_packages_in_Jenkins.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,89 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Jenkins Docs</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Adding custom-build packages in Jenkins</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#where-to-install-package-for-jenkins-job">Where to install package for Jenkins job</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#adding-the-package-to-jenkins">Adding the package to Jenkins</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -142,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Jenkins Docs &raquo;</li>
-      <li>Adding custom-build packages in Jenkins</li>
+      <li>Adding Custom-build packages in Jenkins</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -172,10 +102,6 @@ <h2 id="adding-the-package-to-jenkins">Adding the package to Jenkins</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Multinode_Pipelines/" class="btn btn-neutral float-left" title="Creating Multinode pipelines"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../jenkins_github_integration/Github_push_webhook/" class="btn btn-neutral float-right" title="Github Push webhook integration">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -197,10 +123,6 @@ <h2 id="adding-the-package-to-jenkins">Adding the package to Jenkins</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Multinode_Pipelines/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../jenkins_github_integration/Github_push_webhook/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Booting_ubuntu22.04_riscv64/index.html b/docs/Booting_ubuntu22.04_riscv64/index.html
index 7bbe254..792ed8f 100644
--- a/docs/Booting_ubuntu22.04_riscv64/index.html
+++ b/docs/Booting_ubuntu22.04_riscv64/index.html
@@ -44,83 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-                <li class="toctree-l2"><a class="" href=".">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
diff --git a/docs/Building_Jenkins_github_repo/index.html b/docs/Building_Jenkins_github_repo/index.html
index fdce147..6bac52f 100644
--- a/docs/Building_Jenkins_github_repo/index.html
+++ b/docs/Building_Jenkins_github_repo/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../img/favicon.ico" />
-    <title>Building Jenkins - Cloud-V Docs</title>
+    <title>Building Github Repository of Jenkins - Cloud-V Docs</title>
     <link rel="stylesheet" href="../css/theme.css" />
     <link rel="stylesheet" href="../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Building Jenkins";
+        var mkdocs_page_name = "Building Github Repository of Jenkins";
         var mkdocs_page_input_path = "Building_Jenkins_github_repo.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,95 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Jenkins Docs</a>
-    <ul class="current">
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Building Jenkins</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#linux-kernel-version-distribution-and-release-at-the-time-of-build-process">Linux kernel version, distribution and release at the time of build process</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#cloning-the-github-repository">Cloning the github repository</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#resolving-the-dependencies">Resolving the dependencies</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#building-jenkins-using-maven-on-linux">Building Jenkins using maven on linux</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#executing-jenkins">Executing Jenkins</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -148,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Jenkins Docs &raquo;</li>
-      <li>Building Jenkins</li>
+      <li>Building Github Repository of Jenkins</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -183,10 +107,6 @@ <h2 id="executing-jenkins">Executing Jenkins</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Tooling/" class="btn btn-neutral float-left" title="Tools available in Cloud-V"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Creating_Jenkins_Node_on_LXC/" class="btn btn-neutral float-right" title="Creating Jenkins Node on LXC">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -208,10 +128,6 @@ <h2 id="executing-jenkins">Executing Jenkins</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Tooling/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Creating_Jenkins_Node_on_LXC/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Building_Linux_Kernel/index.html b/docs/Building_Linux_Kernel/index.html
index 3d9c8a2..2439b55 100644
--- a/docs/Building_Linux_Kernel/index.html
+++ b/docs/Building_Linux_Kernel/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../img/favicon.ico" />
-    <title>Building Linux kernel and booting on QEMU - Cloud-V Docs</title>
+    <title>Building a RISCV Linux kernel and booting it in QEMU inside LXC container - Cloud-V Docs</title>
     <link rel="stylesheet" href="../css/theme.css" />
     <link rel="stylesheet" href="../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Building Linux kernel and booting on QEMU";
+        var mkdocs_page_name = "Building a RISCV Linux kernel and booting it in QEMU inside LXC container";
         var mkdocs_page_input_path = "Building_Linux_Kernel.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,105 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">QEMU and Linux Kernel</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Building Linux kernel and booting on QEMU</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#machines-and-lxc-containers-operating-system-specifications">Machine's and LXC Container's Operating System Specifications</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#pre-requisites">Pre-requisites</a>
-        <ul>
-    <li class="toctree-l4"><a class="reference internal" href="#3-riscv-gnu-toolchain">3. RISCV GNU Toolchain</a>
-    </li>
-    <li class="toctree-l4"><a class="reference internal" href="#4-busybox">4. Busybox</a>
-    </li>
-    <li class="toctree-l4"><a class="reference internal" href="#5-qemu-emulator">5. QEMU Emulator</a>
-    </li>
-        </ul>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#6-linux-kernel">6. Linux Kernel</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#building-linux-kernel-with-riscv64-unknown-linux-gnu-gcc">Building Linux kernel with riscv64-unknown-linux-gnu-gcc</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#booting-into-the-linux-kernel-using-qemu-emulator">Booting into the linux kernel using QEMU emulator</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#reference-links">Reference links</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -158,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>QEMU and Linux Kernel &raquo;</li>
-      <li>Building Linux kernel and booting on QEMU</li>
+      <li>Building a RISCV Linux kernel and booting it in QEMU inside LXC container</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -389,10 +303,6 @@ <h2 id="reference-links">Reference links</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Building_qemu/" class="btn btn-neutral float-left" title="Installing Qemu for RISC-V"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Cross_Compiling/Overview/" class="btn btn-neutral float-right" title="Overview">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -414,10 +324,6 @@ <h2 id="reference-links">Reference links</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Building_qemu/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Cross_Compiling/Overview/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Building_qemu/index.html b/docs/Building_qemu/index.html
index 7bdb8f9..7442174 100644
--- a/docs/Building_qemu/index.html
+++ b/docs/Building_qemu/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../img/favicon.ico" />
-    <title>Installing Qemu for RISC-V - Cloud-V Docs</title>
+    <title>Installing `QEMU` for emulating riscv64 - Cloud-V Docs</title>
     <link rel="stylesheet" href="../css/theme.css" />
     <link rel="stylesheet" href="../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Installing Qemu for RISC-V";
+        var mkdocs_page_name = "Installing `QEMU` for emulating riscv64";
         var mkdocs_page_input_path = "Building_qemu.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,107 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">QEMU and Linux Kernel</a>
-    <ul class="current">
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Installing Qemu for RISC-V</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#installing-pre-requisites">Installing Pre-requisites</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#installing-qemu-system-riscv64">Installing qemu-system-riscv64</a>
-        <ul>
-    <li class="toctree-l4"><a class="reference internal" href="#what-is-qemu-system-riscv64">What is qemu-system-riscv64</a>
-    </li>
-    <li class="toctree-l4"><a class="reference internal" href="#installing-qemu-system-riscv64-on-ubuntu">Installing qemu-system-riscv64 on ubuntu</a>
-    </li>
-    <li class="toctree-l4"><a class="reference internal" href="#testing-qemu-system-riscv64">Testing qemu-system-riscv64</a>
-    </li>
-        </ul>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#installing-qemu-riscv64">Installing qemu-riscv64</a>
-        <ul>
-    <li class="toctree-l4"><a class="reference internal" href="#what-is-qemu-riscv64">What is qemu-riscv64</a>
-    </li>
-    <li class="toctree-l4"><a class="reference internal" href="#installing-qemu-riscv64-on-ubuntu-2204">Installing qemu-riscv64 on ubuntu 22.04</a>
-    </li>
-    <li class="toctree-l4"><a class="reference internal" href="#testing-qemu-riscv64">Testing qemu-riscv64</a>
-    </li>
-        </ul>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -160,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>QEMU and Linux Kernel &raquo;</li>
-      <li>Installing Qemu for RISC-V</li>
+      <li>Installing `QEMU` for emulating riscv64</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -286,10 +198,6 @@ <h3 id="testing-qemu-riscv64">Testing <code>qemu-riscv64</code></h3>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Installing_ssl_certificates_new/" class="btn btn-neutral float-left" title="Letsencrypt configuration with Jenkins"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Building_Linux_Kernel/" class="btn btn-neutral float-right" title="Building Linux kernel and booting on QEMU">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -311,10 +219,6 @@ <h3 id="testing-qemu-riscv64">Testing <code>qemu-riscv64</code></h3>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Installing_ssl_certificates_new/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Building_Linux_Kernel/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Creating_CI_CD_pipeline/index.html b/docs/Creating_CI_CD_pipeline/index.html
index 5d98dd7..15a24b9 100644
--- a/docs/Creating_CI_CD_pipeline/index.html
+++ b/docs/Creating_CI_CD_pipeline/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../img/favicon.ico" />
-    <title>Creating a pipeline project - Cloud-V Docs</title>
+    <title>Creating a CI/CD pipeline in Jenkins - Cloud-V Docs</title>
     <link rel="stylesheet" href="../css/theme.css" />
     <link rel="stylesheet" href="../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Creating a pipeline project";
+        var mkdocs_page_name = "Creating a CI/CD pipeline in Jenkins";
         var mkdocs_page_input_path = "Creating_CI_CD_pipeline.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,89 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Jenkins Docs</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Creating a pipeline project</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#pre-requisistes">Pre Requisistes</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#steps-for-jenkins-pipeline-creation">Steps for Jenkins pipeline creation</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -142,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Jenkins Docs &raquo;</li>
-      <li>Creating a pipeline project</li>
+      <li>Creating a CI/CD pipeline in Jenkins</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -206,10 +136,6 @@ <h2 id="steps-for-jenkins-pipeline-creation">Steps for Jenkins pipeline creation
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Creating_Jenkins_Node_on_LXC/" class="btn btn-neutral float-left" title="Creating Jenkins Node on LXC"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Multinode_Pipelines/" class="btn btn-neutral float-right" title="Creating Multinode pipelines">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -231,10 +157,6 @@ <h2 id="steps-for-jenkins-pipeline-creation">Steps for Jenkins pipeline creation
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Creating_Jenkins_Node_on_LXC/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Multinode_Pipelines/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Creating_Jenkins_Node_on_LXC/index.html b/docs/Creating_Jenkins_Node_on_LXC/index.html
index c4df249..6a7773f 100644
--- a/docs/Creating_Jenkins_Node_on_LXC/index.html
+++ b/docs/Creating_Jenkins_Node_on_LXC/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../img/favicon.ico" />
-    <title>Creating Jenkins Node on LXC - Cloud-V Docs</title>
+    <title>Creating a Jenkins Node on LXC Container - Cloud-V Docs</title>
     <link rel="stylesheet" href="../css/theme.css" />
     <link rel="stylesheet" href="../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Creating Jenkins Node on LXC";
+        var mkdocs_page_name = "Creating a Jenkins Node on LXC Container";
         var mkdocs_page_input_path = "Creating_Jenkins_Node_on_LXC.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,103 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Jenkins Docs</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Creating Jenkins Node on LXC</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#what-is-a-container">What is a container</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#why-do-we-need-a-container-for-jenkins-node">Why do we need a container for Jenkins node</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#what-is-lxc-container">What is LXC Container</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#creating-a-container-with-lxc">Creating a container with LXC</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#pre-requisites">Pre-requisites</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#creating-image">Creating image</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#using-ssh-to-access-container-with-username-and-password">Using SSH to access container with username and password</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#using-ssh-to-access-jenkins-agents-on-the-container">Using SSH to access Jenkins agents on the container</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#reference-links">Reference Links</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -156,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Jenkins Docs &raquo;</li>
-      <li>Creating Jenkins Node on LXC</li>
+      <li>Creating a Jenkins Node on LXC Container</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -289,10 +205,6 @@ <h2 id="reference-links">Reference Links</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Building_Jenkins_github_repo/" class="btn btn-neutral float-left" title="Building Jenkins"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Creating_CI_CD_pipeline/" class="btn btn-neutral float-right" title="Creating a pipeline project">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -314,10 +226,6 @@ <h2 id="reference-links">Reference Links</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Building_Jenkins_github_repo/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Creating_CI_CD_pipeline/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Creating_jenkinsfile/index.html b/docs/Creating_jenkinsfile/index.html
index 8610200..6f0c2cc 100644
--- a/docs/Creating_jenkinsfile/index.html
+++ b/docs/Creating_jenkinsfile/index.html
@@ -44,107 +44,45 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">RISC-V CI User's Guide</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Creating a Jenkinfile</a>
+              </ul>
+              <ul class="current">
+                <li class="toctree-l1 current"><a class="reference internal current" href="./">Creating a Jenkinfile</a>
     <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#what-is-a-jenkinsfile">What is a Jenkinsfile</a>
+    <li class="toctree-l2"><a class="reference internal" href="#what-is-a-jenkinsfile">What is a Jenkinsfile</a>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#jenkins-node">Jenkins Node</a>
+    <li class="toctree-l2"><a class="reference internal" href="#jenkins-node">Jenkins Node</a>
         <ul>
-    <li class="toctree-l4"><a class="reference internal" href="#jenkins-master">Jenkins Master</a>
+    <li class="toctree-l3"><a class="reference internal" href="#jenkins-master">Jenkins Master</a>
     </li>
-    <li class="toctree-l4"><a class="reference internal" href="#jenkins-slave">Jenkins Slave</a>
+    <li class="toctree-l3"><a class="reference internal" href="#jenkins-slave">Jenkins Slave</a>
     </li>
         </ul>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#jenkinsfile-written-in-bash">Jenkinsfile written in Bash</a>
+    <li class="toctree-l2"><a class="reference internal" href="#jenkinsfile-written-in-bash">Jenkinsfile written in Bash</a>
         <ul>
-    <li class="toctree-l4"><a class="reference internal" href="#simple-hello-world-jenkinsfile">Simple Hello World Jenkinsfile</a>
+    <li class="toctree-l3"><a class="reference internal" href="#simple-hello-world-jenkinsfile">Simple Hello World Jenkinsfile</a>
     </li>
-    <li class="toctree-l4"><a class="reference internal" href="#jenkinsfile-for-a-specific-node">Jenkinsfile for a Specific Node</a>
+    <li class="toctree-l3"><a class="reference internal" href="#jenkinsfile-for-a-specific-node">Jenkinsfile for a Specific Node</a>
     </li>
         </ul>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#jenkinsfile-for-cross-platform-compilation-and-execution">Jenkinsfile for Cross-Platform Compilation and Execution</a>
+    <li class="toctree-l2"><a class="reference internal" href="#jenkinsfile-for-cross-platform-compilation-and-execution">Jenkinsfile for Cross-Platform Compilation and Execution</a>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#reference-links">Reference Links</a>
+    <li class="toctree-l2"><a class="reference internal" href="#reference-links">Reference Links</a>
     </li>
     </ul>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -160,8 +98,6 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Cloud-V Users &raquo;</li>
-          <li>RISC-V CI User's Guide &raquo;</li>
       <li>Creating a Jenkinfile</li>
     <li class="wy-breadcrumbs-aside">
     </li>
@@ -278,7 +214,7 @@ <h2 id="reference-links">Reference Links</h2>
             </div>
           </div><footer>
     <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Software_Developer_Guide/" class="btn btn-neutral float-left" title="Guide for Software Developer"><span class="icon icon-circle-arrow-left"></span> Previous</a>
+        <a href="../Software_Developer_Guide/" class="btn btn-neutral float-left" title="Getting Started"><span class="icon icon-circle-arrow-left"></span> Previous</a>
         <a href="../runner_specs/" class="btn btn-neutral float-right" title="Runners' Info">Next <span class="icon icon-circle-arrow-right"></span></a>
     </div>
 
diff --git a/docs/Cross_Compiling/Cross_compiling python3.8.15/index.html b/docs/Cross_Compiling/Cross_compiling python3.8.15/index.html
index 3deb3ed..f230efb 100644
--- a/docs/Cross_Compiling/Cross_compiling python3.8.15/index.html	
+++ b/docs/Cross_Compiling/Cross_compiling python3.8.15/index.html	
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../../img/favicon.ico" />
-    <title>Cross Compiling Python3.8.15 - Cloud-V Docs</title>
+    <title>Cross compiling python3.8.15 for `riscv64` - Cloud-V Docs</title>
     <link rel="stylesheet" href="../../css/theme.css" />
     <link rel="stylesheet" href="../../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Cross Compiling Python3.8.15";
+        var mkdocs_page_name = "Cross compiling python3.8.15 for `riscv64`";
         var mkdocs_page_input_path = "Cross_Compiling/Cross_compiling python3.8.15.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,87 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Cross-Compilation</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Cross Compiling Python3.8.15</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#building-python">Building Python</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -140,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Cross-Compilation &raquo;</li>
-      <li>Cross Compiling Python3.8.15</li>
+      <li>Cross compiling python3.8.15 for `riscv64`</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -169,10 +101,6 @@ <h2 id="building-python">Building Python</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Overview/" class="btn btn-neutral float-left" title="Overview"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Cross_compiling_openssl/" class="btn btn-neutral float-right" title="Cross Compiling Openssl">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -194,10 +122,6 @@ <h2 id="building-python">Building Python</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Overview/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Cross_compiling_openssl/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Cross_Compiling/Cross_compiling_coremark/index.html b/docs/Cross_Compiling/Cross_compiling_coremark/index.html
index 3b9c27f..66e9aec 100644
--- a/docs/Cross_Compiling/Cross_compiling_coremark/index.html
+++ b/docs/Cross_Compiling/Cross_compiling_coremark/index.html
@@ -44,83 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href=".">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
diff --git a/docs/Cross_Compiling/Cross_compiling_dhrystone/index.html b/docs/Cross_Compiling/Cross_compiling_dhrystone/index.html
index 527c282..8f11f83 100644
--- a/docs/Cross_Compiling/Cross_compiling_dhrystone/index.html
+++ b/docs/Cross_Compiling/Cross_compiling_dhrystone/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../../img/favicon.ico" />
-    <title>Cross Compiling Drhystone - Cloud-V Docs</title>
+    <title>Cross-compiling `dhrystone` - Cloud-V Docs</title>
     <link rel="stylesheet" href="../../css/theme.css" />
     <link rel="stylesheet" href="../../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Cross Compiling Drhystone";
+        var mkdocs_page_name = "Cross-compiling `dhrystone`";
         var mkdocs_page_input_path = "Cross_Compiling/Cross_compiling_dhrystone.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,87 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Cross-Compilation</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Cross Compiling Drhystone</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#cross-compiling-for-riscv64-unknown-linux-gnu">Cross-compiling for riscv64-unknown-linux-gnu</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -140,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Cross-Compilation &raquo;</li>
-      <li>Cross Compiling Drhystone</li>
+      <li>Cross-compiling `dhrystone`</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -175,10 +107,6 @@ <h2 id="cross-compiling-for-riscv64-unknown-linux-gnu">Cross-compiling for <code
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Cross_compiling_ruby/" class="btn btn-neutral float-left" title="Cross Compiling Ruby"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Cross_compiling_rust/" class="btn btn-neutral float-right" title="Cross Compiling Rust">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -200,10 +128,6 @@ <h2 id="cross-compiling-for-riscv64-unknown-linux-gnu">Cross-compiling for <code
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Cross_compiling_ruby/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Cross_compiling_rust/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Cross_Compiling/Cross_compiling_go/index.html b/docs/Cross_Compiling/Cross_compiling_go/index.html
index 3010f80..b76a61c 100644
--- a/docs/Cross_Compiling/Cross_compiling_go/index.html
+++ b/docs/Cross_Compiling/Cross_compiling_go/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../../img/favicon.ico" />
-    <title>Cross Compiling go - Cloud-V Docs</title>
+    <title>Cross compiling `Go` - Cloud-V Docs</title>
     <link rel="stylesheet" href="../../css/theme.css" />
     <link rel="stylesheet" href="../../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Cross Compiling go";
+        var mkdocs_page_name = "Cross compiling `Go`";
         var mkdocs_page_input_path = "Cross_Compiling/Cross_compiling_go.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,87 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Cross-Compilation</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Cross Compiling go</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#pre-requisites">Pre Requisites</a>
-    </li>
-    </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -140,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Cross-Compilation &raquo;</li>
-      <li>Cross Compiling go</li>
+      <li>Cross compiling `Go`</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -178,10 +110,6 @@ <h2 id="pre-requisites">Pre Requisites</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Cross_compiling_rust/" class="btn btn-neutral float-left" title="Cross Compiling Rust"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../../Usage_Monitoring/Prometheus_Grafana/" class="btn btn-neutral float-right" title="Setting up Grafana and Prometheus">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -203,10 +131,6 @@ <h2 id="pre-requisites">Pre Requisites</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Cross_compiling_rust/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../../Usage_Monitoring/Prometheus_Grafana/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Cross_Compiling/Cross_compiling_jdk/index.html b/docs/Cross_Compiling/Cross_compiling_jdk/index.html
index 29d7d7d..2f47b82 100644
--- a/docs/Cross_Compiling/Cross_compiling_jdk/index.html
+++ b/docs/Cross_Compiling/Cross_compiling_jdk/index.html
@@ -44,83 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
diff --git a/docs/Cross_Compiling/Cross_compiling_ninja-build/index.html b/docs/Cross_Compiling/Cross_compiling_ninja-build/index.html
index c79801b..24f4253 100644
--- a/docs/Cross_Compiling/Cross_compiling_ninja-build/index.html
+++ b/docs/Cross_Compiling/Cross_compiling_ninja-build/index.html
@@ -44,83 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
diff --git a/docs/Cross_Compiling/Cross_compiling_openssl/index.html b/docs/Cross_Compiling/Cross_compiling_openssl/index.html
index 0347e51..d7569d3 100644
--- a/docs/Cross_Compiling/Cross_compiling_openssl/index.html
+++ b/docs/Cross_Compiling/Cross_compiling_openssl/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../../img/favicon.ico" />
-    <title>Cross Compiling Openssl - Cloud-V Docs</title>
+    <title>Cross-compiling openssl - Cloud-V Docs</title>
     <link rel="stylesheet" href="../../css/theme.css" />
     <link rel="stylesheet" href="../../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Cross Compiling Openssl";
+        var mkdocs_page_name = "Cross-compiling openssl";
         var mkdocs_page_input_path = "Cross_Compiling/Cross_compiling_openssl.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,95 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Cross-Compilation</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Cross Compiling Openssl</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#what-is-openssl">What is openssl</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#building-openssl-v101-for-riscv64-architecture">Building openssl v1.0.1 for riscv64 architecture</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#building-openssl-v111r-for-riscv64-architecture">Building openssl v1.1.1r for riscv64 architecture</a>
-        <ul>
-    <li class="toctree-l4"><a class="reference internal" href="#solving-post-installation-errors">Solving post-installation errors</a>
-    </li>
-        </ul>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -148,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Cross-Compilation &raquo;</li>
-      <li>Cross Compiling Openssl</li>
+      <li>Cross-compiling openssl</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -224,10 +148,6 @@ <h3 id="solving-post-installation-errors">Solving post-installation errors</h3>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Cross_compiling%20python3.8.15/" class="btn btn-neutral float-left" title="Cross Compiling Python3.8.15"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Cross_compiling_ruby/" class="btn btn-neutral float-right" title="Cross Compiling Ruby">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -249,10 +169,6 @@ <h3 id="solving-post-installation-errors">Solving post-installation errors</h3>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Cross_compiling%20python3.8.15/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Cross_compiling_ruby/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Cross_Compiling/Cross_compiling_ruby/index.html b/docs/Cross_Compiling/Cross_compiling_ruby/index.html
index ecf9810..f1499d8 100644
--- a/docs/Cross_Compiling/Cross_compiling_ruby/index.html
+++ b/docs/Cross_Compiling/Cross_compiling_ruby/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../../img/favicon.ico" />
-    <title>Cross Compiling Ruby - Cloud-V Docs</title>
+    <title>Cross Compilation of Ruby - Cloud-V Docs</title>
     <link rel="stylesheet" href="../../css/theme.css" />
     <link rel="stylesheet" href="../../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Cross Compiling Ruby";
+        var mkdocs_page_name = "Cross Compilation of Ruby";
         var mkdocs_page_input_path = "Cross_Compiling/Cross_compiling_ruby.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,99 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Cross-Compilation</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Cross Compiling Ruby</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#system-specifications">System Specifications</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#pre-requisites">Pre-requisites</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#getting-source-code">Getting source code</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#build">Build</a>
-        <ul>
-    <li class="toctree-l4"><a class="reference internal" href="#installing-ruby-for-native-architecture">Installing ruby for native architecture</a>
-    </li>
-    <li class="toctree-l4"><a class="reference internal" href="#cross-compiling-ruby-for-riscv64-unknown-linux-gnu">Cross-Compiling Ruby for riscv64-unknown-linux-gnu</a>
-    </li>
-        </ul>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -152,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Cross-Compilation &raquo;</li>
-      <li>Cross Compiling Ruby</li>
+      <li>Cross Compilation of Ruby</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -240,10 +160,6 @@ <h3 id="cross-compiling-ruby-for-riscv64-unknown-linux-gnu">Cross-Compiling Ruby
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Cross_compiling_openssl/" class="btn btn-neutral float-left" title="Cross Compiling Openssl"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Cross_compiling_dhrystone/" class="btn btn-neutral float-right" title="Cross Compiling Drhystone">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -265,10 +181,6 @@ <h3 id="cross-compiling-ruby-for-riscv64-unknown-linux-gnu">Cross-Compiling Ruby
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Cross_compiling_openssl/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Cross_compiling_dhrystone/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Cross_Compiling/Cross_compiling_rust/index.html b/docs/Cross_Compiling/Cross_compiling_rust/index.html
index ffb3f0a..ba7ec6a 100644
--- a/docs/Cross_Compiling/Cross_compiling_rust/index.html
+++ b/docs/Cross_Compiling/Cross_compiling_rust/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../../img/favicon.ico" />
-    <title>Cross Compiling Rust - Cloud-V Docs</title>
+    <title>Cross-compiling rust - Cloud-V Docs</title>
     <link rel="stylesheet" href="../../css/theme.css" />
     <link rel="stylesheet" href="../../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Cross Compiling Rust";
+        var mkdocs_page_name = "Cross-compiling rust";
         var mkdocs_page_input_path = "Cross_Compiling/Cross_compiling_rust.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,87 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Cross-Compilation</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Cross Compiling Rust</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#getting-source-code">Getting source code</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -140,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Cross-Compilation &raquo;</li>
-      <li>Cross Compiling Rust</li>
+      <li>Cross-compiling rust</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -194,10 +126,6 @@ <h2 id="getting-source-code">Getting source code</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Cross_compiling_dhrystone/" class="btn btn-neutral float-left" title="Cross Compiling Drhystone"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Cross_compiling_go/" class="btn btn-neutral float-right" title="Cross Compiling go">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -219,10 +147,6 @@ <h2 id="getting-source-code">Getting source code</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Cross_compiling_dhrystone/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Cross_compiling_go/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Cross_Compiling/Overview/index.html b/docs/Cross_Compiling/Overview/index.html
index 247ddcf..ad632ed 100644
--- a/docs/Cross_Compiling/Overview/index.html
+++ b/docs/Cross_Compiling/Overview/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../../img/favicon.ico" />
-    <title>Overview - Cloud-V Docs</title>
+    <title>Cross Compilation - Cloud-V Docs</title>
     <link rel="stylesheet" href="../../css/theme.css" />
     <link rel="stylesheet" href="../../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Overview";
+        var mkdocs_page_name = "Cross Compilation";
         var mkdocs_page_input_path = "Cross_Compiling/Overview.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,89 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Cross-Compilation</a>
-    <ul class="current">
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Overview</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#need-of-cross-compilation">Need of Cross Compilation</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#basic-concept">Basic concept</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -142,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Cross-Compilation &raquo;</li>
-      <li>Overview</li>
+      <li>Cross Compilation</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -169,10 +99,6 @@ <h2 id="basic-concept">Basic concept</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../../Building_Linux_Kernel/" class="btn btn-neutral float-left" title="Building Linux kernel and booting on QEMU"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Cross_compiling%20python3.8.15/" class="btn btn-neutral float-right" title="Cross Compiling Python3.8.15">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -194,10 +120,6 @@ <h2 id="basic-concept">Basic concept</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../../Building_Linux_Kernel/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Cross_compiling%20python3.8.15/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Installing_ssl_certificates_new/index.html b/docs/Installing_ssl_certificates_new/index.html
index d19e0c4..664ce2c 100644
--- a/docs/Installing_ssl_certificates_new/index.html
+++ b/docs/Installing_ssl_certificates_new/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../img/favicon.ico" />
-    <title>Letsencrypt configuration with Jenkins - Cloud-V Docs</title>
+    <title>Configure `letsencrypt` with jenkins - Cloud-V Docs</title>
     <link rel="stylesheet" href="../css/theme.css" />
     <link rel="stylesheet" href="../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Letsencrypt configuration with Jenkins";
+        var mkdocs_page_name = "Configure `letsencrypt` with jenkins";
         var mkdocs_page_input_path = "Installing_ssl_certificates_new.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,87 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Jenkins Docs</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Letsencrypt configuration with Jenkins</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#installing-ssl-certificates-with-letsencrypt">Installing SSL certificates with letsencrypt</a>
-    </li>
-    </ul>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -140,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Jenkins Docs &raquo;</li>
-      <li>Letsencrypt configuration with Jenkins</li>
+      <li>Configure `letsencrypt` with jenkins</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -176,10 +108,6 @@ <h2 id="installing-ssl-certificates-with-letsencrypt">Installing SSL certificate
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../jenkins_gitlab_integration/" class="btn btn-neutral float-left" title="GitLab Integration"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Building_qemu/" class="btn btn-neutral float-right" title="Installing Qemu for RISC-V">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -201,10 +129,6 @@ <h2 id="installing-ssl-certificates-with-letsencrypt">Installing SSL certificate
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../jenkins_gitlab_integration/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Building_qemu/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Multinode_Pipelines/index.html b/docs/Multinode_Pipelines/index.html
index 1cb2258..12ce9a0 100644
--- a/docs/Multinode_Pipelines/index.html
+++ b/docs/Multinode_Pipelines/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../img/favicon.ico" />
-    <title>Creating Multinode pipelines - Cloud-V Docs</title>
+    <title>Multinode Pipelines - Cloud-V Docs</title>
     <link rel="stylesheet" href="../css/theme.css" />
     <link rel="stylesheet" href="../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Creating Multinode pipelines";
+        var mkdocs_page_name = "Multinode Pipelines";
         var mkdocs_page_input_path = "Multinode_Pipelines.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,97 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Jenkins Docs</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Creating Multinode pipelines</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#label">Label</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#creating-multinode-pipelines-in-jenkins-native-pipeline-job">Creating multinode pipelines in Jenkins native pipeline job</a>
-        <ul>
-    <li class="toctree-l4"><a class="reference internal" href="#scripted-pipeline">Scripted Pipeline</a>
-    </li>
-    <li class="toctree-l4"><a class="reference internal" href="#declarative-pipeline">Declarative pipeline</a>
-    </li>
-        </ul>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#creating-multinode-pipelines-using-jenkins-freestyle-jobs">Creating multinode pipelines using Jenkins freestyle jobs</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -150,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Jenkins Docs &raquo;</li>
-      <li>Creating Multinode pipelines</li>
+      <li>Multinode Pipelines</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -225,10 +147,6 @@ <h2 id="creating-multinode-pipelines-using-jenkins-freestyle-jobs">Creating mult
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Creating_CI_CD_pipeline/" class="btn btn-neutral float-left" title="Creating a pipeline project"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Adding_Custom-build_packages_in_Jenkins/" class="btn btn-neutral float-right" title="Adding custom-build packages in Jenkins">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -250,10 +168,6 @@ <h2 id="creating-multinode-pipelines-using-jenkins-freestyle-jobs">Creating mult
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Creating_CI_CD_pipeline/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Adding_Custom-build_packages_in_Jenkins/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/Software_Developer_Guide/index.html b/docs/Software_Developer_Guide/index.html
index c542495..1e01335 100644
--- a/docs/Software_Developer_Guide/index.html
+++ b/docs/Software_Developer_Guide/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../img/favicon.ico" />
-    <title>Guide for Software Developer - Cloud-V Docs</title>
+    <title>Getting Started - Cloud-V Docs</title>
     <link rel="stylesheet" href="../css/theme.css" />
     <link rel="stylesheet" href="../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Guide for Software Developer";
+        var mkdocs_page_name = "Getting Started";
         var mkdocs_page_input_path = "Software_Developer_Guide.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,103 +44,41 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">RISC-V CI User's Guide</a>
+                <li class="toctree-l1 current"><a class="reference internal current" href="./">Getting Started</a>
     <ul class="current">
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Guide for Software Developer</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#pre-requisites">Pre-requisites</a>
+    <li class="toctree-l2"><a class="reference internal" href="#pre-requisites">Pre-requisites</a>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#getting-an-account-for-cloud-v">Getting an account for Cloud-V</a>
+    <li class="toctree-l2"><a class="reference internal" href="#getting-an-account-for-cloud-v">Getting an account for Cloud-V</a>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#setting-up-cloud-v-pipeline-inside-github-project-repository">Setting up cloud-v-pipeline inside github project repository</a>
+    <li class="toctree-l2"><a class="reference internal" href="#setting-up-cloud-v-pipeline-inside-github-project-repository">Setting up cloud-v-pipeline inside github project repository</a>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#setting-credentials-for-webhook">Setting credentials for webhook</a>
+    <li class="toctree-l2"><a class="reference internal" href="#setting-credentials-for-webhook">Setting credentials for webhook</a>
         <ul>
-    <li class="toctree-l4"><a class="reference internal" href="#obtaining-github-access-token-for-repository">Obtaining github access token for repository</a>
+    <li class="toctree-l3"><a class="reference internal" href="#obtaining-github-access-token-for-repository">Obtaining github access token for repository</a>
     </li>
-    <li class="toctree-l4"><a class="reference internal" href="#configuring-repository-webhook-optional">Configuring repository webhook (Optional)</a>
+    <li class="toctree-l3"><a class="reference internal" href="#configuring-repository-webhook-optional">Configuring repository webhook (Optional)</a>
     </li>
-    <li class="toctree-l4"><a class="reference internal" href="#configurations-inside-cloud-v">Configurations inside Cloud-V</a>
+    <li class="toctree-l3"><a class="reference internal" href="#configurations-inside-cloud-v">Configurations inside Cloud-V</a>
     </li>
         </ul>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#requirements-for-administrator">Requirements for administrator</a>
+    <li class="toctree-l2"><a class="reference internal" href="#requirements-for-administrator">Requirements for administrator</a>
     </li>
     </ul>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -156,9 +94,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Cloud-V Users &raquo;</li>
-          <li>RISC-V CI User's Guide &raquo;</li>
-      <li>Guide for Software Developer</li>
+      <li>Getting Started</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
diff --git a/docs/Tooling/index.html b/docs/Tooling/index.html
index ab1252e..976b237 100644
--- a/docs/Tooling/index.html
+++ b/docs/Tooling/index.html
@@ -44,95 +44,33 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">RISC-V CI User's Guide</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Tools available in Cloud-V</a>
+              </ul>
+              <ul class="current">
+                <li class="toctree-l1 current"><a class="reference internal current" href="./">Tools available in Cloud-V</a>
     <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#using-environment-modules">Using Environment Modules</a>
+    <li class="toctree-l2"><a class="reference internal" href="#using-environment-modules">Using Environment Modules</a>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#tools-on-x86_runner1-and-qemuusermode_runner1-node">Tools on x86_runner1 and qemuusermode_runner1 node</a>
+    <li class="toctree-l2"><a class="reference internal" href="#tools-on-x86_runner1-and-qemuusermode_runner1-node">Tools on x86_runner1 and qemuusermode_runner1 node</a>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#tools-on-riscv64_runner1-node">Tools on riscv64_runner1 node</a>
+    <li class="toctree-l2"><a class="reference internal" href="#tools-on-riscv64_runner1-node">Tools on riscv64_runner1 node</a>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#tools-on-hifive_unleashed-node">Tools on hifive_unleashed node</a>
+    <li class="toctree-l2"><a class="reference internal" href="#tools-on-hifive_unleashed-node">Tools on hifive_unleashed node</a>
     </li>
-    <li class="toctree-l3"><a class="reference internal" href="#tools-on-starfive_visionfive2-node">Tools on starfive_visionfive2 node</a>
+    <li class="toctree-l2"><a class="reference internal" href="#tools-on-starfive_visionfive2-node">Tools on starfive_visionfive2 node</a>
     </li>
     </ul>
                 </li>
-    </ul>
-                  </li>
-              </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -148,8 +86,6 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Cloud-V Users &raquo;</li>
-          <li>RISC-V CI User's Guide &raquo;</li>
       <li>Tools available in Cloud-V</li>
     <li class="wy-breadcrumbs-aside">
     </li>
@@ -645,7 +581,6 @@ <h2 id="tools-on-starfive_visionfive2-node">Tools on <code>starfive_visionfive2<
           </div><footer>
     <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
         <a href="../runner_specs/" class="btn btn-neutral float-left" title="Runners' Info"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Building_Jenkins_github_repo/" class="btn btn-neutral float-right" title="Building Jenkins">Next <span class="icon icon-circle-arrow-right"></span></a>
     </div>
 
   <hr/>
@@ -671,8 +606,6 @@ <h2 id="tools-on-starfive_visionfive2-node">Tools on <code>starfive_visionfive2<
       <span><a href="../runner_specs/" style="color: #fcfcfc">&laquo; Previous</a></span>
     
     
-      <span><a href="../Building_Jenkins_github_repo/" style="color: #fcfcfc">Next &raquo;</a></span>
-    
   </span>
 </div>
     <script>var base_url = '..';</script>
diff --git a/docs/Usage_Monitoring/Integrating_prometheus_grafana/index.html b/docs/Usage_Monitoring/Integrating_prometheus_grafana/index.html
index 2245b87..b981922 100644
--- a/docs/Usage_Monitoring/Integrating_prometheus_grafana/index.html
+++ b/docs/Usage_Monitoring/Integrating_prometheus_grafana/index.html
@@ -44,91 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Usage monitoring</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Integrating Prometheus with Grafana</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#configuration-in-prometheus">Configuration in Prometheus</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#configuration-in-grafana">Configuration in Grafana</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#creating-a-dashboard-in-grafana">Creating a dashboard in Grafana</a>
-    </li>
-    </ul>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -144,8 +74,6 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Usage monitoring &raquo;</li>
       <li>Integrating Prometheus with Grafana</li>
     <li class="wy-breadcrumbs-aside">
     </li>
@@ -187,9 +115,6 @@ <h2 id="creating-a-dashboard-in-grafana">Creating a dashboard in Grafana</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Prometheus_Grafana/" class="btn btn-neutral float-left" title="Setting up Grafana and Prometheus"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-    </div>
 
   <hr/>
 
@@ -211,8 +136,6 @@ <h2 id="creating-a-dashboard-in-grafana">Creating a dashboard in Grafana</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Prometheus_Grafana/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
     
   </span>
 </div>
diff --git a/docs/Usage_Monitoring/Prometheus_Grafana/index.html b/docs/Usage_Monitoring/Prometheus_Grafana/index.html
index 7086855..4ec11a5 100644
--- a/docs/Usage_Monitoring/Prometheus_Grafana/index.html
+++ b/docs/Usage_Monitoring/Prometheus_Grafana/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../../img/favicon.ico" />
-    <title>Setting up Grafana and Prometheus - Cloud-V Docs</title>
+    <title>Setting up Promtheus and Grafana - Cloud-V Docs</title>
     <link rel="stylesheet" href="../../css/theme.css" />
     <link rel="stylesheet" href="../../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Setting up Grafana and Prometheus";
+        var mkdocs_page_name = "Setting up Promtheus and Grafana";
         var mkdocs_page_input_path = "Usage_Monitoring/Prometheus_Grafana.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,97 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Usage monitoring</a>
-    <ul class="current">
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Setting up Grafana and Prometheus</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#what-are-prometheus-and-grafana">What are Prometheus and Grafana</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#setting-up-node-exporters">Setting up Node Exporters</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#configuring-prometheus">Configuring Prometheus</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#running-prometheus">Running Prometheus</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#running-grafana">Running Grafana</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#reference-links">Reference links</a>
-    </li>
-    </ul>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -150,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Usage monitoring &raquo;</li>
-      <li>Setting up Grafana and Prometheus</li>
+      <li>Setting up Promtheus and Grafana</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -209,10 +131,6 @@ <h2 id="reference-links">Reference links</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../../Cross_Compiling/Cross_compiling_go/" class="btn btn-neutral float-left" title="Cross Compiling go"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Integrating_prometheus_grafana/" class="btn btn-neutral float-right" title="Integrating Prometheus with Grafana">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -234,10 +152,6 @@ <h2 id="reference-links">Reference links</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../../Cross_Compiling/Cross_compiling_go/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Integrating_prometheus_grafana/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/index.html b/docs/index.html
index 7763b36..df28b96 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -46,83 +46,21 @@
     </ul>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
+                <li class="toctree-l1"><a class="reference internal" href="Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -155,7 +93,7 @@ <h1 id="cloud-v-documentation">Cloud-V Documentation</h1>
             </div>
           </div><footer>
     <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="Software_Developer_Guide/" class="btn btn-neutral float-right" title="Guide for Software Developer">Next <span class="icon icon-circle-arrow-right"></span></a>
+        <a href="Software_Developer_Guide/" class="btn btn-neutral float-right" title="Getting Started">Next <span class="icon icon-circle-arrow-right"></span></a>
     </div>
 
   <hr/>
@@ -198,5 +136,5 @@ <h1 id="cloud-v-documentation">Cloud-V Documentation</h1>
 
 <!--
 MkDocs version : 1.4.0
-Build Date UTC : 2023-10-02 08:44:59.158735+00:00
+Build Date UTC : 2023-11-03 06:44:30.107132+00:00
 -->
diff --git a/docs/jenkins_github_integration/Github_PR_webhook_integration/index.html b/docs/jenkins_github_integration/Github_PR_webhook_integration/index.html
index 7f8d066..d284949 100644
--- a/docs/jenkins_github_integration/Github_PR_webhook_integration/index.html
+++ b/docs/jenkins_github_integration/Github_PR_webhook_integration/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../../img/favicon.ico" />
-    <title>Github PR webhook integration - Cloud-V Docs</title>
+    <title>GitHub Pull Request hook integration with Jenkins - Cloud-V Docs</title>
     <link rel="stylesheet" href="../../css/theme.css" />
     <link rel="stylesheet" href="../../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Github PR webhook integration";
+        var mkdocs_page_name = "GitHub Pull Request hook integration with Jenkins";
         var mkdocs_page_input_path = "jenkins_github_integration/Github_PR_webhook_integration.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,99 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Jenkins Docs</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Github PR webhook integration</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#general-guidline">General Guidline</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#github-pull-request-builder-plugin">GitHub Pull Request Builder Plugin</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#specifications-at-the-time-of-documentation">Specifications at the time of documentation</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#pre-requisites">Pre-Requisites</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#setting-up-jenkins-configuration">Setting up Jenkins configuration</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#setting-up-jenkins-job">Setting up Jenkins job</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#verifying-if-the-procedure">Verifying if the procedure</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -152,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Jenkins Docs &raquo;</li>
-      <li>Github PR webhook integration</li>
+      <li>GitHub Pull Request hook integration with Jenkins</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -257,10 +177,6 @@ <h2 id="verifying-if-the-procedure">Verifying if the procedure</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../Github_push_webhook/" class="btn btn-neutral float-left" title="Github Push webhook integration"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../../jenkins_gitlab_integration/" class="btn btn-neutral float-right" title="GitLab Integration">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -282,10 +198,6 @@ <h2 id="verifying-if-the-procedure">Verifying if the procedure</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../Github_push_webhook/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../../jenkins_gitlab_integration/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/jenkins_github_integration/Github_push_webhook/index.html b/docs/jenkins_github_integration/Github_push_webhook/index.html
index ebeb507..6ed0646 100644
--- a/docs/jenkins_github_integration/Github_push_webhook/index.html
+++ b/docs/jenkins_github_integration/Github_push_webhook/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../../img/favicon.ico" />
-    <title>Github Push webhook integration - Cloud-V Docs</title>
+    <title>Github 'Push' webhook integration with Jenkins - Cloud-V Docs</title>
     <link rel="stylesheet" href="../../css/theme.css" />
     <link rel="stylesheet" href="../../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "Github Push webhook integration";
+        var mkdocs_page_name = "Github \u0027Push\u0027 webhook integration with Jenkins";
         var mkdocs_page_input_path = "jenkins_github_integration/Github_push_webhook.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,105 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="../..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Jenkins Docs</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Github Push webhook integration</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#purpose-of-using-github-webhook-integration-with-jenkins">Purpose of using github webhook integration with jenkins</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#jenkins-version-and-operating-system-specifications">Jenkins version and operating system specifications</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#pre-requisites">Pre-requisites</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#setting-up-the-ngrok">Setting up the ngrok</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#setting-up-jenkins-for-github-webhook">Setting up Jenkins for github webhook</a>
-        <ul>
-    <li class="toctree-l4"><a class="reference internal" href="#pre-requisites_1">Pre-requisites</a>
-    </li>
-    <li class="toctree-l4"><a class="reference internal" href="#jenkins-configuration-in-settings">Jenkins Configuration in Settings</a>
-    </li>
-    <li class="toctree-l4"><a class="reference internal" href="#jenkins-job-setup-for-github-webhook">Jenkins job setup for Github Webhook</a>
-    </li>
-        </ul>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#setting-up-github-repository-webhook">Setting up github repository webhook</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -158,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href="../.." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Jenkins Docs &raquo;</li>
-      <li>Github Push webhook integration</li>
+      <li>Github 'Push' webhook integration with Jenkins</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -277,10 +191,6 @@ <h2 id="setting-up-github-repository-webhook">Setting up github repository webho
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../../Adding_Custom-build_packages_in_Jenkins/" class="btn btn-neutral float-left" title="Adding custom-build packages in Jenkins"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Github_PR_webhook_integration/" class="btn btn-neutral float-right" title="Github PR webhook integration">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -302,10 +212,6 @@ <h2 id="setting-up-github-repository-webhook">Setting up github repository webho
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../../Adding_Custom-build_packages_in_Jenkins/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Github_PR_webhook_integration/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/jenkins_gitlab_integration/index.html b/docs/jenkins_gitlab_integration/index.html
index ab146d6..bfab6be 100644
--- a/docs/jenkins_gitlab_integration/index.html
+++ b/docs/jenkins_gitlab_integration/index.html
@@ -5,14 +5,14 @@
     <meta http-equiv="X-UA-Compatible" content="IE=edge" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
       <link rel="shortcut icon" href="../img/favicon.ico" />
-    <title>GitLab Integration - Cloud-V Docs</title>
+    <title>Integrating GitLab with Jenkins - Cloud-V Docs</title>
     <link rel="stylesheet" href="../css/theme.css" />
     <link rel="stylesheet" href="../css/theme_extra.css" />
         <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/highlight.js/10.5.0/styles/github.min.css" />
     
       <script>
         // Current page data
-        var mkdocs_page_name = "GitLab Integration";
+        var mkdocs_page_name = "Integrating GitLab with Jenkins";
         var mkdocs_page_input_path = "jenkins_gitlab_integration.md";
         var mkdocs_page_url = null;
       </script>
@@ -44,93 +44,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">Jenkins Docs</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">GitLab Integration</a>
-    <ul class="current">
-    <li class="toctree-l3"><a class="reference internal" href="#pre-requisites">Pre-requisites</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#configuring-jenkins-system">Configuring Jenkins System</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#configuring-gitlab">Configuring GitLab</a>
-    </li>
-    <li class="toctree-l3"><a class="reference internal" href="#configuring-jenkins-job">Configuring Jenkins Job</a>
-    </li>
-    </ul>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -146,9 +74,7 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Administrators &raquo;</li>
-          <li>Jenkins Docs &raquo;</li>
-      <li>GitLab Integration</li>
+      <li>Integrating GitLab with Jenkins</li>
     <li class="wy-breadcrumbs-aside">
     </li>
   </ul>
@@ -217,10 +143,6 @@ <h2 id="configuring-jenkins-job">Configuring Jenkins Job</h2>
               
             </div>
           </div><footer>
-    <div class="rst-footer-buttons" role="navigation" aria-label="Footer Navigation">
-        <a href="../jenkins_github_integration/Github_PR_webhook_integration/" class="btn btn-neutral float-left" title="Github PR webhook integration"><span class="icon icon-circle-arrow-left"></span> Previous</a>
-        <a href="../Installing_ssl_certificates_new/" class="btn btn-neutral float-right" title="Letsencrypt configuration with Jenkins">Next <span class="icon icon-circle-arrow-right"></span></a>
-    </div>
 
   <hr/>
 
@@ -242,10 +164,6 @@ <h2 id="configuring-jenkins-job">Configuring Jenkins Job</h2>
   <span class="rst-current-version" data-toggle="rst-current-version">
     
     
-      <span><a href="../jenkins_github_integration/Github_PR_webhook_integration/" style="color: #fcfcfc">&laquo; Previous</a></span>
-    
-    
-      <span><a href="../Installing_ssl_certificates_new/" style="color: #fcfcfc">Next &raquo;</a></span>
     
   </span>
 </div>
diff --git a/docs/runner_specs/index.html b/docs/runner_specs/index.html
index 52994dd..0833957 100644
--- a/docs/runner_specs/index.html
+++ b/docs/runner_specs/index.html
@@ -44,85 +44,23 @@
                 <li class="toctree-l1"><a class="reference internal" href="..">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
-              <ul class="current">
-                  <li class="toctree-l1 current"><a class="reference internal current" href="#">RISC-V CI User's Guide</a>
-    <ul class="current">
-                <li class="toctree-l2"><a class="reference internal" href="../Software_Developer_Guide/">Guide for Software Developer</a>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="../Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-                <li class="toctree-l2 current"><a class="reference internal current" href="./">Runners' Info</a>
+              </ul>
+              <ul class="current">
+                <li class="toctree-l1 current"><a class="reference internal current" href="./">Runners' Info</a>
     <ul class="current">
     </ul>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
+                <li class="toctree-l1"><a class="reference internal" href="../Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="../Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="../Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
@@ -138,8 +76,6 @@
         <div class="rst-content"><div role="navigation" aria-label="breadcrumbs navigation">
   <ul class="wy-breadcrumbs">
     <li><a href=".." class="icon icon-home" alt="Docs"></a> &raquo;</li>
-          <li>For Cloud-V Users &raquo;</li>
-          <li>RISC-V CI User's Guide &raquo;</li>
       <li>Runners' Info</li>
     <li class="wy-breadcrumbs-aside">
     </li>
diff --git a/docs/search.html b/docs/search.html
index 346c135..41f960d 100644
--- a/docs/search.html
+++ b/docs/search.html
@@ -37,83 +37,21 @@
                 <li class="toctree-l1"><a class="reference internal" href="./.">Home</a>
                 </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Cloud-V Users</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">RISC-V CI User's Guide</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="./Software_Developer_Guide/">Guide for Software Developer</a>
+                <li class="toctree-l1"><a class="reference internal" href="./Software_Developer_Guide/">Getting Started</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Creating_jenkinsfile/">Creating a Jenkinfile</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./runner_specs/">Runners' Info</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Tooling/">Tools available in Cloud-V</a>
-                </li>
-    </ul>
-                  </li>
               </ul>
-              <p class="caption"><span class="caption-text">For Administrators</span></p>
               <ul>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Jenkins Docs</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="./Building_Jenkins_github_repo/">Building Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Creating_Jenkins_Node_on_LXC/">Creating Jenkins Node on LXC</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Creating_CI_CD_pipeline/">Creating a pipeline project</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Multinode_Pipelines/">Creating Multinode pipelines</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Adding_Custom-build_packages_in_Jenkins/">Adding custom-build packages in Jenkins</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./jenkins_github_integration/Github_push_webhook/">Github Push webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./jenkins_github_integration/Github_PR_webhook_integration/">Github PR webhook integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./jenkins_gitlab_integration/">GitLab Integration</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Installing_ssl_certificates_new/">Letsencrypt configuration with Jenkins</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">QEMU and Linux Kernel</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="./Building_qemu/">Installing Qemu for RISC-V</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Building_Linux_Kernel/">Building Linux kernel and booting on QEMU</a>
+                <li class="toctree-l1"><a class="reference internal" href="./Creating_jenkinsfile/">Creating a Jenkinfile</a>
                 </li>
-                <li class="toctree-l2"><a class="" href="./Booting_ubuntu22.04_riscv64">Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Cross-Compilation</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="./Cross_Compiling/Overview/">Overview</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Cross_Compiling/Cross_compiling%20python3.8.15/">Cross Compiling Python3.8.15</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Cross_Compiling/Cross_compiling_openssl/">Cross Compiling Openssl</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Cross_Compiling/Cross_compiling_ruby/">Cross Compiling Ruby</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Cross_Compiling/Cross_compiling_dhrystone/">Cross Compiling Drhystone</a>
-                </li>
-                <li class="toctree-l2"><a class="" href="./Cross_Compiling/Cross_compiling_coremark">Cross Compiling Coremark</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Cross_Compiling/Cross_compiling_rust/">Cross Compiling Rust</a>
-                </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Cross_Compiling/Cross_compiling_go/">Cross Compiling go</a>
-                </li>
-    </ul>
-                  </li>
-                  <li class="toctree-l1"><a class="reference internal" href="#">Usage monitoring</a>
-    <ul>
-                <li class="toctree-l2"><a class="reference internal" href="./Usage_Monitoring/Prometheus_Grafana/">Setting up Grafana and Prometheus</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="./runner_specs/">Runners' Info</a>
                 </li>
-                <li class="toctree-l2"><a class="reference internal" href="./Usage_Monitoring/Integrating_prometheus_grafana/">Integrating Prometheus with Grafana</a>
+              </ul>
+              <ul>
+                <li class="toctree-l1"><a class="reference internal" href="./Tooling/">Tools available in Cloud-V</a>
                 </li>
-    </ul>
-                  </li>
               </ul>
       </div>
     </div>
diff --git a/docs/search/search_index.json b/docs/search/search_index.json
index bf72aa9..0484875 100644
--- a/docs/search/search_index.json
+++ b/docs/search/search_index.json
@@ -1 +1 @@
-{"config":{"indexing":"full","lang":["en"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"Cloud-V Documentation On this site, you will find all the documentation regarding Jenkins, LXC containers and QEMU configured to use with Cloud-V CI infrastructure Documentation slides: link Youtube Channel: youtube.com/@Cloud-V","title":"Home"},{"location":"#cloud-v-documentation","text":"On this site, you will find all the documentation regarding Jenkins, LXC containers and QEMU configured to use with Cloud-V CI infrastructure Documentation slides: link Youtube Channel: youtube.com/@Cloud-V","title":"Cloud-V Documentation"},{"location":"Adding_Custom-build_packages_in_Jenkins/","text":"Adding Custom-build packages in Jenkins __NOTE: For this documentation, Ubuntu 22.04 and Jenkins version 2.371 is used. While working open-source, many times one may need to build the package from source code. While working on the local machine, the built package may be accessible by adding it to the $PATH environment variable. But while working with Jenkins, This may not work. Where to install package for Jenkins job In Jenkins job, the package is installed on the node (or agent) on which the specific job is being used and NOT on the node where the jenkins controller node is installed. For example if the Jenkins controller node is on computer1 and slave node on which the job is destined to run is on computer2 then computer2 should have all the packages used by the job and not the computer1 . Adding the package to Jenkins Considering there is a node with name Runner1 in jenkins on which the job is destined to run and that job uses a toolchain riscv64-unknown-elf-gcc to run properly and that toolchain is present in directory /home/runner1/path_to_install/bin , then the following procedure is used to add the toolchain in Jenkins. Go to Dashboard > Manage Jenkins > Nodes > Runner1 . Scroll down and check Environment variables . Under section List of variables add: Name as PATH Value as $PATH:/home/runner1/path_to_install/bin . Click on Save . After this, the package should be available to be used.","title":"Adding custom-build packages in Jenkins"},{"location":"Adding_Custom-build_packages_in_Jenkins/#adding-custom-build-packages-in-jenkins","text":"__NOTE: For this documentation, Ubuntu 22.04 and Jenkins version 2.371 is used. While working open-source, many times one may need to build the package from source code. While working on the local machine, the built package may be accessible by adding it to the $PATH environment variable. But while working with Jenkins, This may not work.","title":"Adding Custom-build packages in Jenkins"},{"location":"Adding_Custom-build_packages_in_Jenkins/#where-to-install-package-for-jenkins-job","text":"In Jenkins job, the package is installed on the node (or agent) on which the specific job is being used and NOT on the node where the jenkins controller node is installed. For example if the Jenkins controller node is on computer1 and slave node on which the job is destined to run is on computer2 then computer2 should have all the packages used by the job and not the computer1 .","title":"Where to install package for Jenkins job"},{"location":"Adding_Custom-build_packages_in_Jenkins/#adding-the-package-to-jenkins","text":"Considering there is a node with name Runner1 in jenkins on which the job is destined to run and that job uses a toolchain riscv64-unknown-elf-gcc to run properly and that toolchain is present in directory /home/runner1/path_to_install/bin , then the following procedure is used to add the toolchain in Jenkins. Go to Dashboard > Manage Jenkins > Nodes > Runner1 . Scroll down and check Environment variables . Under section List of variables add: Name as PATH Value as $PATH:/home/runner1/path_to_install/bin . Click on Save . After this, the package should be available to be used.","title":"Adding the package to Jenkins"},{"location":"Booting_ubuntu22.04_riscv64/","text":"Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64 Pre-requisites Following are the pre-requisites which are needed to be installed before booting ubuntu 22.04 for RISC-V on qemu . Note: Make sure RISC-V GNU Toolchain is installed before proceeding U-boot Qemu version 7.0 or greater with networking Ubuntu 22.04 pre-built image for RISC-V 1. Installing U-boot Note: If you plan on installing U-boot from apt or some system repository, install the one which comes with ubuntu 22.04. Older will not work with this process. Also, be sure to checkout a latest Stable version instead of development version. Get source code of u-boot and checkout stable version using commands below. git clone https://github.com/qemu/u-boot.git cd u-boot git checkout v2022.10 Generate configurations for supervisor mode with following command. make qemu-riscv64_smode_defconfig CROSS_COMPILE=riscv64-unknown-linux-gnu- Execute following command to start build process. make CROSS_COMPILE=riscv64-unknown-linux-gnu- This should install u-boot.bin in the source directory. This file will be used later so its path must be kept remember. Here it will be refered to as $UBOOTPATH . 2. Installing Qemu Qemu version 7.0 or greater should be installed with networking for ubuntu 22.04 to work. See Installing Qemu for RISC-V for instructions on installing qemu-system-riscv64 . 3. Getting Ubuntu 22.04 pre-build image for RISC-V Ubuntu 22.04 image can be downloaded from https://ubuntu.com/download/risc-v . Booting Ubuntu 22.04 Image on qemu In the directory where ubuntu 22.04 image is present, execute following command to boot into ubuntu 22.04 with qemu-system-riscv64 . If you need more space, you can use following command. qemu-img resize -f raw ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img +5G This will increase storage size of the image by 5GB. qemu-system-riscv64 \\ -machine virt -nographic -m 2048 -smp 4 \\ -kernel $UBOOTPATH/u-boot.bin \\ -device virtio-net-device,netdev=eth0 -netdev user,id=eth0,hostfwd=::<host_port>-:<VM_port> \\ -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio Here -m is the memory in Megabytes and -smp is number of cores. -nographic means qemu will use same terminal instance instead of opening a new window of its own (which is beneficial while running servers without gui). Whereas hostfwd=::<host_port>-:<VM_port> will forward traffic going to port <host_port> to port VM_port . Due to this port <host_port> will be used to access ssh on qemu machine. This should boot ubuntu 22.04. But it will take a while on first start. On start, credentials will be as follows. Username: ubuntu Password: ubuntu After entering credentials, terminal will prompt for change of password after which ubuntu will be ready to use.","title":"Booting RISC-V Ubuntu 22.04 on `qemu-system-riscv64`"},{"location":"Booting_ubuntu22.04_riscv64/#booting-risc-v-ubuntu-2204-on-qemu-system-riscv64","text":"","title":"Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64"},{"location":"Booting_ubuntu22.04_riscv64/#pre-requisites","text":"Following are the pre-requisites which are needed to be installed before booting ubuntu 22.04 for RISC-V on qemu . Note: Make sure RISC-V GNU Toolchain is installed before proceeding U-boot Qemu version 7.0 or greater with networking Ubuntu 22.04 pre-built image for RISC-V","title":"Pre-requisites"},{"location":"Booting_ubuntu22.04_riscv64/#1-installing-u-boot","text":"Note: If you plan on installing U-boot from apt or some system repository, install the one which comes with ubuntu 22.04. Older will not work with this process. Also, be sure to checkout a latest Stable version instead of development version. Get source code of u-boot and checkout stable version using commands below. git clone https://github.com/qemu/u-boot.git cd u-boot git checkout v2022.10 Generate configurations for supervisor mode with following command. make qemu-riscv64_smode_defconfig CROSS_COMPILE=riscv64-unknown-linux-gnu- Execute following command to start build process. make CROSS_COMPILE=riscv64-unknown-linux-gnu- This should install u-boot.bin in the source directory. This file will be used later so its path must be kept remember. Here it will be refered to as $UBOOTPATH .","title":"1. Installing U-boot"},{"location":"Booting_ubuntu22.04_riscv64/#2-installing-qemu","text":"Qemu version 7.0 or greater should be installed with networking for ubuntu 22.04 to work. See Installing Qemu for RISC-V for instructions on installing qemu-system-riscv64 .","title":"2. Installing Qemu"},{"location":"Booting_ubuntu22.04_riscv64/#3-getting-ubuntu-2204-pre-build-image-for-risc-v","text":"Ubuntu 22.04 image can be downloaded from https://ubuntu.com/download/risc-v .","title":"3. Getting Ubuntu 22.04 pre-build image for RISC-V"},{"location":"Booting_ubuntu22.04_riscv64/#booting-ubuntu-2204-image-on-qemu","text":"In the directory where ubuntu 22.04 image is present, execute following command to boot into ubuntu 22.04 with qemu-system-riscv64 . If you need more space, you can use following command. qemu-img resize -f raw ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img +5G This will increase storage size of the image by 5GB. qemu-system-riscv64 \\ -machine virt -nographic -m 2048 -smp 4 \\ -kernel $UBOOTPATH/u-boot.bin \\ -device virtio-net-device,netdev=eth0 -netdev user,id=eth0,hostfwd=::<host_port>-:<VM_port> \\ -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio Here -m is the memory in Megabytes and -smp is number of cores. -nographic means qemu will use same terminal instance instead of opening a new window of its own (which is beneficial while running servers without gui). Whereas hostfwd=::<host_port>-:<VM_port> will forward traffic going to port <host_port> to port VM_port . Due to this port <host_port> will be used to access ssh on qemu machine. This should boot ubuntu 22.04. But it will take a while on first start. On start, credentials will be as follows. Username: ubuntu Password: ubuntu After entering credentials, terminal will prompt for change of password after which ubuntu will be ready to use.","title":"Booting Ubuntu 22.04 Image on qemu"},{"location":"Building_Jenkins_github_repo/","text":"Building Github Repository of Jenkins Linux kernel version, distribution and release at the time of build process Linux Kernel : 5.15.0-46-generic (can be checked using uname -r in ubuntu) Distribution : Ubuntu Release : focal (20.04); also works without issue on ubuntu 22.04 (release can be checked using lsb_release -a in ubuntu) Cloning the github repository First clone the repository using the command below (here it is assumed to be cloned at user's home directory: ~/) git clone https://github.com/jenkinsci/jenkins.git Resolving the dependencies After cloning the repository at ~/, the file CONTRIBUTING.md should be available in ~/jenkins/. This file contains all the information to resolve the dependencies and building the repository. Some notable dependencies are Java Development Kit (JDK), Apache Maven (latest version will be preferable) and git. Running Following command will resolve the mentioned dependencies. sudo apt update && sudo apt install default-jdk default-jre maven git -y Building Jenkins using maven on linux For having the jenkins build up as fast as possible, following command can be used in ~/jenkins/. mvn -am -pl war,bom -Pquick-build clean install Executing Jenkins After the above commands successfully completes execution, jenkins.war should be present in ~/jenkins/war/target and can be executed to run at port 8080 on localhost using following command. java -jar ~/jenkins/war/target/jenkins.war --httpPort=8080 #Considering jenkins repo is cloned at ~/ After this process jenkins UI can be accessed using http://localhost:8080 in a browser and a password will be shown on terminal to login to jenkins first time After this, Jenkins UI will go through a very simple post installation process which one can configure according to his needs.","title":"Building Jenkins"},{"location":"Building_Jenkins_github_repo/#building-github-repository-of-jenkins","text":"","title":"Building Github Repository of Jenkins"},{"location":"Building_Jenkins_github_repo/#linux-kernel-version-distribution-and-release-at-the-time-of-build-process","text":"Linux Kernel : 5.15.0-46-generic (can be checked using uname -r in ubuntu) Distribution : Ubuntu Release : focal (20.04); also works without issue on ubuntu 22.04 (release can be checked using lsb_release -a in ubuntu)","title":"Linux kernel version, distribution and release at the time of build process"},{"location":"Building_Jenkins_github_repo/#cloning-the-github-repository","text":"First clone the repository using the command below (here it is assumed to be cloned at user's home directory: ~/) git clone https://github.com/jenkinsci/jenkins.git","title":"Cloning the github repository"},{"location":"Building_Jenkins_github_repo/#resolving-the-dependencies","text":"After cloning the repository at ~/, the file CONTRIBUTING.md should be available in ~/jenkins/. This file contains all the information to resolve the dependencies and building the repository. Some notable dependencies are Java Development Kit (JDK), Apache Maven (latest version will be preferable) and git. Running Following command will resolve the mentioned dependencies. sudo apt update && sudo apt install default-jdk default-jre maven git -y","title":"Resolving the dependencies"},{"location":"Building_Jenkins_github_repo/#building-jenkins-using-maven-on-linux","text":"For having the jenkins build up as fast as possible, following command can be used in ~/jenkins/. mvn -am -pl war,bom -Pquick-build clean install","title":"Building Jenkins using maven on linux"},{"location":"Building_Jenkins_github_repo/#executing-jenkins","text":"After the above commands successfully completes execution, jenkins.war should be present in ~/jenkins/war/target and can be executed to run at port 8080 on localhost using following command. java -jar ~/jenkins/war/target/jenkins.war --httpPort=8080 #Considering jenkins repo is cloned at ~/ After this process jenkins UI can be accessed using http://localhost:8080 in a browser and a password will be shown on terminal to login to jenkins first time After this, Jenkins UI will go through a very simple post installation process which one can configure according to his needs.","title":"Executing Jenkins"},{"location":"Building_Linux_Kernel/","text":"Building a RISCV Linux kernel and booting it in QEMU inside LXC container This documentation covers how to build a linux kernel with RISCV linux toolchain inside an un-privileged LXC container and then boot it on qemu. Doing this process on privileged lxc container makes life easier, but privileged containers always have security loop holes. For instance, their root id is mapped to root id of host machine. On the other hand un-privileged containers are the safest (see link ). Machine's and LXC Container's Operating System Specifications At the time of creating this documentation, following is the specification of host machine and operating system. Host Machine: Ubuntu focal (20.04) 64-bit. LXC Container: Ubuntu jammy (22.04) 64-bit. LXC Container is unprivileged with non-sudo user. NOTE: Throughout this documentation, name of the lxc container will be qemu_container or qemucontainer with non-sudo user as qemu-user which is running on ubuntu 22.04 and host machine x86. Do not confuse the name with assumption that it is booting on qemu emulator. It is just a naming convention. Pre-requisites Following programs may also have their own pre-requisites. Git: For cloning repositories of following programs. Install it with [sudo] apt install git . TMUX: For convenience of multiple terminals. Install it using [sudo] apt install tmux RISCV GNU toolchain built as linux: For compiling the linux kernel. Busybox: For Generating the binaries for linux kernel boot. QEMU Emulator: For booting the linux kernel Linux Kernel (latest version which is used at point of writing this documentation is 6.0.0 ) The working directory inside lxc container for all of this documentation will be ~/riscv-linux or /home/qemu-user/riscv-linux . NOTE: Busybox will not be built inside the lxc container rather it will be built in (any) host linux machine with sudo privileges. 3. RISCV GNU Toolchain Log in the lxc container to the non-sudo user (here SSH is used to log in). Install the prerequisites for building RISCV GNU TOOLCHAIN inside lxc container with root user using command below. apt-get install autoconf automake autotools-dev curl python3 libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev libexpat-dev libncurses-dev Clone the GNU toolchain using the command below. git clone https://github.com/riscv-collab/riscv-gnu-toolchain.git Create a directory in which the RISCV GNU toolchain is desired to be installed (here it will be /home/qemu-user/riscv-linux/riscv-gnu-installed ) Execute following command inside cloned repository with --prefix as the absolute directory path to where the RISCV toolchain is to be installed ./configure --prefix=/home/qemu-user/riscv-linux/riscv-gnu-installed Execute following inside cloned repository (execution of this command will take a while to complete) make linux -j$(nproc) # 'nproc' is the command used to determine the number of processors in machine so that 'make' can use parallelism. After the execution of command is complete, add bin directory created inside the riscv installation directory to the $PATH and add the expression to .bashrc . According to this documentation, following expression will be added to .bashrc . PATH=\"/home/qemu-user/riscv-linux/riscv-gnu-installed/bin:$PATH\" Check if the toolchain is installed by executing following commands. exec $SHELL riscv64-unknown-linux-gnu-gcc Expected Output: fatal error: no input files compilation terminated. Now RISCV linux toolchain is ready ! 4. Busybox Busybox is the package for creating linux binutils and set of directories for linux to boot into. Busybox will be installed in host machine instead of lxc container. The reason for this is linux kernel requires block oriented device and character oriented device for it to boot. Those devices can be created using mknod command which can only be created inside a host machine with sudo privileges. Busybox will be used in creating initial ram disk file (in gz format) which is used to boot kernel. It does not matter at which operating system or on which machine this file is created. But the machine on which it is compiled, must also have RISCV GNU toolchain installed above. Clone Busybox using the command below. git clone https://git.busybox.net/busybox Navigate to cloned directory. cd busybox Before building busybox, we need to produce a configuration (.config file) for busybox. It is better to apply default configurations and then change only those which are desired. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- defconfig After the command is executed, a .config file will be present in the busybox cloned directory. Now, an additional option is to be enabled which enables busybox to build the libraries in the executable instead of separate shared libraries. For this purpose, execute the following command to access the configuration menu. Then go to Settings menu by pressing enter and from there, enable [ ] Build static binary (no shared libs) by pressing space. After the option is enabled, exit by pressing esc twice two times and press yes to the prompt about file saving. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- menuconfig Now that configuration is complete, build busybox by executing following command. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) Execute following command which will produce all the basic linux utilities in _install directory in busybox repo directory. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) install Navigate to _install directory and create dev directory. cd _install mkdir dev Now, a linux console and a ram devices are to be created inside dev directory. A fact to understand here is that, every device is a file in linux but they are special kind of files. A detail of these devices can be found here . In this documentation mknod command is used to create these devices. sudo mknod dev/console c 5 1 sudo mknod dev/ram b 1 0 After executing above commands, following files with names ram and console will be created as shown in the image below. Now an init file is needed because linux kernel does not boot itself, it rather searches for init file in the directories (read linux kernel messages during build procedure). init file contains commands to mount some directories during boot (more information can be found here ). In busybox/_install , create a file with following contents (be sure to make it executable with chmod +x init ). vim init #!/bin/sh echo \"### INIT SCRIPT ###\" mkdir /proc /sys /tmp mount -t proc none /proc #For processes mount -t sysfs none /sys #For all the devices on the machine mount -t tmpfs none /tmp #For virtual memory echo -e \"\\nThis boot took $(cut -d' ' -f1 /proc/uptime) seconds\\n\" exec /bin/sh Now that all the files are ready for linux to boot into, pack them in cpio format and then to gz format. It is because cpio format is in \"Early userspace support\" in linux kernel (see link ) whereas gz format is needed because it is one of the formats needed by qemu emulator. Following command produces a qemu-compatible initramfs file for linux kernel to boot in. find -print0 | cpio -0oH newc | gzip -9 > ../initramfs.cpio.gz Command Details: find -print0 separates the file names with null character cpio -0oH newc produces an archive file in newc format gzip -9 creates a gz format zip file. -9 represents the best compression level at the slowest speed ../initramfs.cpio.gz represents the output file which is created in parent directory to present working directory. At this point, our work with busybox is done. Copy the produced file into the lxc container (use scp command if it is on ssh). 5. QEMU Emulator Install the pre-requisites of qemu emulator on lxc container with root user with following command (see link ). apt-get install git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build Clone the QEMU Emulator repository using the command below with root user: git clone https://github.com/qemu/qemu.git Build QEMU for RISCV with root user using commands below (see link ). ./configure --target-list=riscv64-softmmu make -j$(nproc) For system-wide installation of QEMU Emulator, run following command with root user. make -j$(nproc) install After execution of this command, work with QEMU Emulator is done and its commands can be accessed anywhere. 6. Linux Kernel Clone the linux kernel from Linus Torvalds' repository using the command below. git clone https://github.com/torvalds/linux.git Navigate to cloned repository. cd linux Building Linux kernel with riscv64-unknown-linux-gnu-gcc Before building linux kernel with RISCV toolchain a configuration file (.config) must be produced in its directory. First, produce a file with default configurations, then change configurations according to needs. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- defconfig make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- menuconfig Above command will open configuration menu. Enter General setup , scroll down and enable Initial RAM filesystem and RAM disk (initramfs/initrd) support using Space key. Then enter () Initramfs source file(s) and here put the absolute path to initramfs.cpio.gz file which was just created using busybox. For this documentation, it is /home/qemu-user/riscv-linux/initramfs.cpio.gz . Double-press esc and save the file. Now linux kernel is ready to be compiled with riscv64-linux-gnu-gcc toolchain. So execute the command below. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) If the above command successfully executed without any errors, there must be Kernel: arch/riscv/boot/Image.gz is ready printed on terminal. On newer linux kernels, it might be scrolled up a little, use Ctrl-shift-f to find it. Booting into the linux kernel using QEMU emulator Now that everything is ready, execute the following command in linux/arch/riscv/boot/ directory to boot linux on sifive's unleashed . qemu-system-riscv64 -kernel Image -machine sifive_u -nographic Command Details qemu-system-riscv64 is the qemu built for riscv64 -kernel takes the image produced by linux kernel compilation and is present in linux/arch/riscv/boot/ directory. -machine takes one of the machine names as arguments available in qemu-system-riscv64 . Available machines can be listed on terminal using command qemu-system-riscv64 -machine help . -nographic restricts the use of GUI (which is a better option considering lxc container does not support gtk initialization). If everything goes on right, the kernel will boot successfully as shown in the picture below. Reference links https://risc-v-getting-started-guide.readthedocs.io/en/latest/linux-qemu.html https://hackernoon.com/how-to-set-up-the-environment-for-riscv-64-linux-kernel-development-in-ubuntu-2004-si5p35kv","title":"Building Linux kernel and booting on QEMU"},{"location":"Building_Linux_Kernel/#building-a-riscv-linux-kernel-and-booting-it-in-qemu-inside-lxc-container","text":"This documentation covers how to build a linux kernel with RISCV linux toolchain inside an un-privileged LXC container and then boot it on qemu. Doing this process on privileged lxc container makes life easier, but privileged containers always have security loop holes. For instance, their root id is mapped to root id of host machine. On the other hand un-privileged containers are the safest (see link ).","title":"Building a RISCV Linux kernel and booting it in QEMU inside LXC container"},{"location":"Building_Linux_Kernel/#machines-and-lxc-containers-operating-system-specifications","text":"At the time of creating this documentation, following is the specification of host machine and operating system. Host Machine: Ubuntu focal (20.04) 64-bit. LXC Container: Ubuntu jammy (22.04) 64-bit. LXC Container is unprivileged with non-sudo user. NOTE: Throughout this documentation, name of the lxc container will be qemu_container or qemucontainer with non-sudo user as qemu-user which is running on ubuntu 22.04 and host machine x86. Do not confuse the name with assumption that it is booting on qemu emulator. It is just a naming convention.","title":"Machine's and LXC Container's Operating System Specifications"},{"location":"Building_Linux_Kernel/#pre-requisites","text":"Following programs may also have their own pre-requisites. Git: For cloning repositories of following programs. Install it with [sudo] apt install git . TMUX: For convenience of multiple terminals. Install it using [sudo] apt install tmux RISCV GNU toolchain built as linux: For compiling the linux kernel. Busybox: For Generating the binaries for linux kernel boot. QEMU Emulator: For booting the linux kernel Linux Kernel (latest version which is used at point of writing this documentation is 6.0.0 ) The working directory inside lxc container for all of this documentation will be ~/riscv-linux or /home/qemu-user/riscv-linux . NOTE: Busybox will not be built inside the lxc container rather it will be built in (any) host linux machine with sudo privileges.","title":"Pre-requisites"},{"location":"Building_Linux_Kernel/#3-riscv-gnu-toolchain","text":"Log in the lxc container to the non-sudo user (here SSH is used to log in). Install the prerequisites for building RISCV GNU TOOLCHAIN inside lxc container with root user using command below. apt-get install autoconf automake autotools-dev curl python3 libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev libexpat-dev libncurses-dev Clone the GNU toolchain using the command below. git clone https://github.com/riscv-collab/riscv-gnu-toolchain.git Create a directory in which the RISCV GNU toolchain is desired to be installed (here it will be /home/qemu-user/riscv-linux/riscv-gnu-installed ) Execute following command inside cloned repository with --prefix as the absolute directory path to where the RISCV toolchain is to be installed ./configure --prefix=/home/qemu-user/riscv-linux/riscv-gnu-installed Execute following inside cloned repository (execution of this command will take a while to complete) make linux -j$(nproc) # 'nproc' is the command used to determine the number of processors in machine so that 'make' can use parallelism. After the execution of command is complete, add bin directory created inside the riscv installation directory to the $PATH and add the expression to .bashrc . According to this documentation, following expression will be added to .bashrc . PATH=\"/home/qemu-user/riscv-linux/riscv-gnu-installed/bin:$PATH\" Check if the toolchain is installed by executing following commands. exec $SHELL riscv64-unknown-linux-gnu-gcc Expected Output: fatal error: no input files compilation terminated. Now RISCV linux toolchain is ready !","title":"3. RISCV GNU Toolchain"},{"location":"Building_Linux_Kernel/#4-busybox","text":"Busybox is the package for creating linux binutils and set of directories for linux to boot into. Busybox will be installed in host machine instead of lxc container. The reason for this is linux kernel requires block oriented device and character oriented device for it to boot. Those devices can be created using mknod command which can only be created inside a host machine with sudo privileges. Busybox will be used in creating initial ram disk file (in gz format) which is used to boot kernel. It does not matter at which operating system or on which machine this file is created. But the machine on which it is compiled, must also have RISCV GNU toolchain installed above. Clone Busybox using the command below. git clone https://git.busybox.net/busybox Navigate to cloned directory. cd busybox Before building busybox, we need to produce a configuration (.config file) for busybox. It is better to apply default configurations and then change only those which are desired. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- defconfig After the command is executed, a .config file will be present in the busybox cloned directory. Now, an additional option is to be enabled which enables busybox to build the libraries in the executable instead of separate shared libraries. For this purpose, execute the following command to access the configuration menu. Then go to Settings menu by pressing enter and from there, enable [ ] Build static binary (no shared libs) by pressing space. After the option is enabled, exit by pressing esc twice two times and press yes to the prompt about file saving. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- menuconfig Now that configuration is complete, build busybox by executing following command. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) Execute following command which will produce all the basic linux utilities in _install directory in busybox repo directory. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) install Navigate to _install directory and create dev directory. cd _install mkdir dev Now, a linux console and a ram devices are to be created inside dev directory. A fact to understand here is that, every device is a file in linux but they are special kind of files. A detail of these devices can be found here . In this documentation mknod command is used to create these devices. sudo mknod dev/console c 5 1 sudo mknod dev/ram b 1 0 After executing above commands, following files with names ram and console will be created as shown in the image below. Now an init file is needed because linux kernel does not boot itself, it rather searches for init file in the directories (read linux kernel messages during build procedure). init file contains commands to mount some directories during boot (more information can be found here ). In busybox/_install , create a file with following contents (be sure to make it executable with chmod +x init ). vim init #!/bin/sh echo \"### INIT SCRIPT ###\" mkdir /proc /sys /tmp mount -t proc none /proc #For processes mount -t sysfs none /sys #For all the devices on the machine mount -t tmpfs none /tmp #For virtual memory echo -e \"\\nThis boot took $(cut -d' ' -f1 /proc/uptime) seconds\\n\" exec /bin/sh Now that all the files are ready for linux to boot into, pack them in cpio format and then to gz format. It is because cpio format is in \"Early userspace support\" in linux kernel (see link ) whereas gz format is needed because it is one of the formats needed by qemu emulator. Following command produces a qemu-compatible initramfs file for linux kernel to boot in. find -print0 | cpio -0oH newc | gzip -9 > ../initramfs.cpio.gz Command Details: find -print0 separates the file names with null character cpio -0oH newc produces an archive file in newc format gzip -9 creates a gz format zip file. -9 represents the best compression level at the slowest speed ../initramfs.cpio.gz represents the output file which is created in parent directory to present working directory. At this point, our work with busybox is done. Copy the produced file into the lxc container (use scp command if it is on ssh).","title":"4. Busybox"},{"location":"Building_Linux_Kernel/#5-qemu-emulator","text":"Install the pre-requisites of qemu emulator on lxc container with root user with following command (see link ). apt-get install git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build Clone the QEMU Emulator repository using the command below with root user: git clone https://github.com/qemu/qemu.git Build QEMU for RISCV with root user using commands below (see link ). ./configure --target-list=riscv64-softmmu make -j$(nproc) For system-wide installation of QEMU Emulator, run following command with root user. make -j$(nproc) install After execution of this command, work with QEMU Emulator is done and its commands can be accessed anywhere.","title":"5. QEMU Emulator"},{"location":"Building_Linux_Kernel/#6-linux-kernel","text":"Clone the linux kernel from Linus Torvalds' repository using the command below. git clone https://github.com/torvalds/linux.git Navigate to cloned repository. cd linux","title":"6. Linux Kernel"},{"location":"Building_Linux_Kernel/#building-linux-kernel-with-riscv64-unknown-linux-gnu-gcc","text":"Before building linux kernel with RISCV toolchain a configuration file (.config) must be produced in its directory. First, produce a file with default configurations, then change configurations according to needs. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- defconfig make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- menuconfig Above command will open configuration menu. Enter General setup , scroll down and enable Initial RAM filesystem and RAM disk (initramfs/initrd) support using Space key. Then enter () Initramfs source file(s) and here put the absolute path to initramfs.cpio.gz file which was just created using busybox. For this documentation, it is /home/qemu-user/riscv-linux/initramfs.cpio.gz . Double-press esc and save the file. Now linux kernel is ready to be compiled with riscv64-linux-gnu-gcc toolchain. So execute the command below. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) If the above command successfully executed without any errors, there must be Kernel: arch/riscv/boot/Image.gz is ready printed on terminal. On newer linux kernels, it might be scrolled up a little, use Ctrl-shift-f to find it.","title":"Building Linux kernel with riscv64-unknown-linux-gnu-gcc"},{"location":"Building_Linux_Kernel/#booting-into-the-linux-kernel-using-qemu-emulator","text":"Now that everything is ready, execute the following command in linux/arch/riscv/boot/ directory to boot linux on sifive's unleashed . qemu-system-riscv64 -kernel Image -machine sifive_u -nographic Command Details qemu-system-riscv64 is the qemu built for riscv64 -kernel takes the image produced by linux kernel compilation and is present in linux/arch/riscv/boot/ directory. -machine takes one of the machine names as arguments available in qemu-system-riscv64 . Available machines can be listed on terminal using command qemu-system-riscv64 -machine help . -nographic restricts the use of GUI (which is a better option considering lxc container does not support gtk initialization). If everything goes on right, the kernel will boot successfully as shown in the picture below.","title":"Booting into the linux kernel using QEMU emulator"},{"location":"Building_Linux_Kernel/#reference-links","text":"https://risc-v-getting-started-guide.readthedocs.io/en/latest/linux-qemu.html https://hackernoon.com/how-to-set-up-the-environment-for-riscv-64-linux-kernel-development-in-ubuntu-2004-si5p35kv","title":"Reference links"},{"location":"Building_qemu/","text":"Installing QEMU for emulating riscv64 QEMU is an open-source emulator. It can be used to emulate different architectures on a single machine. In RISC-V CI there are various programs which run on RISC-V architecture. But instead of porting them to a dedicated board of riscv architecture, they can be run readily on qemu emulator. Here two types of QEMU emulators will be used for RISC-V applications: qemu-system-riscv64: It can be used to load a complete linux operating system image. qemu-riscv64: It can be used to execute program's binary directly without need of a complete operating system. Installing Pre-requisites Execute the following command to install the pre-requisites for installing qemu on ubuntu 22.04 (jammy) sudo apt-get install meson git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build qemu-slirp is important for enabling user-level networking with qemu-system-riscv64 qemu-system-riscv64 while loading image of server installation of ubuntu. So it needs to be installed first. Get the source code of qemu-slirp using following command: git clone https://github.com/openSUSE/qemu-slirp.git Then Execute following commands to install slirp in meson, which can later be used by qemu during build. meson build ninja -C build install Note: Make sure you have riscv64-unknown-linux-gnu toolchain installed for compiling program and executing them on qemu later. There are some optional dependencies which one can download, but they are actually not needed for installing qemu and make it work. Installing qemu-system-riscv64 What is qemu-system-riscv64 qemu-system-riscv64 is qemu executable program. It can load a complete linux distribution. It cannot take program's executable binary as argument and run it without a dedicated linux distribution. Installing qemu-system-riscv64 on ubuntu Get source code of qemu from github using the command below git clone https://github.com/qemu/qemu.git Configure qemu for riscv64-softmmu with following command (replace $PREFIX with valid location of installation). ./configure --prefix=$PREFIX --target-list=riscv64-linux-user,riscv64-softmmu --enable-slirp Execute following command to start the build. make Execute following command to install the binaries at $PREFIX location. make install Note: After the installation with slirp following error can be encountered on some systems . qemu-system-riscv64: symbol lookup error: qemu-system-riscv64: undefined symbol: slirp_new, version SLIRP_4.0 Solution: This can be solved by executing following command in source directory of qemu (which is cloned from github). [sudo] ldconfig Testing qemu-system-riscv64 qemu-system-riscv64 can only be tested by booting a linux operating system. See Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64 . Installing qemu-riscv64 What is qemu-riscv64 qemu-riscv64 is qemu executable program. But instead of porting a complete operating system (like qemu-system-riscv64 ), it can readily execute binaries. Throughout cross-compiling section, qemu-riscv64 will be used with linux-user and executable of every program can be tested on qemu (e.g. python, ruby etc.). Installing qemu-riscv64 on ubuntu 22.04 Get source code of qemu using the command below git clone https://github.com/qemu/qemu.git Use following command in the root directory of repository to configure qemu for riscv64-linux-user ./configure --target-list=riscv64-linux-user --prefix=$PREFIX # Replace $PREFIX with a valid location to install at Note: If this is not your architecture/platform, you can see a list of available platform/architecture by executing following command. ./configure --help Use the following command to start the build process make -j$(nproc) After the builld is complete without any error, use the following command to install binaries at $PREFIX location make install Add the $PREFIX/bin to $PATH variable so that it may be recognized as a command. Using this method causes the qemu-riscv64 to have an issue with sysroot. It starts searching for libraries in the root folder of the machine which is based on x86_64-linux-gnu . A simple workaround is to give path of the sysroot/ folder where riscv64-unknown-linux-gnu toolchain is installed. Here that directory will be denoted as $RISCV_SYSROOT Testing qemu-riscv64 Create a C file in your favorite editor or by using the commands below: echo \"#include<stdio.h>\" > helloworld.c echo \"int main(){\" >> helloworld.c echo \"printf(\"Hello World !\");\" >> helloworld.c echo '}' >> helloworld.c Execute following command to compile C program with riscv gnu toolchain riscv64-unknown-linux-gnu-gcc helloworld.c -o helloworld Execute following command to execute the compiled binary on qemu-riscv64 qemu-riscv64 -L $RISCV_SYSROOT ./helloworld If everything went right, following output will be shown. Hello World !","title":"Installing Qemu for RISC-V"},{"location":"Building_qemu/#installing-qemu-for-emulating-riscv64","text":"QEMU is an open-source emulator. It can be used to emulate different architectures on a single machine. In RISC-V CI there are various programs which run on RISC-V architecture. But instead of porting them to a dedicated board of riscv architecture, they can be run readily on qemu emulator. Here two types of QEMU emulators will be used for RISC-V applications: qemu-system-riscv64: It can be used to load a complete linux operating system image. qemu-riscv64: It can be used to execute program's binary directly without need of a complete operating system.","title":"Installing QEMU for emulating riscv64"},{"location":"Building_qemu/#installing-pre-requisites","text":"Execute the following command to install the pre-requisites for installing qemu on ubuntu 22.04 (jammy) sudo apt-get install meson git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build qemu-slirp is important for enabling user-level networking with qemu-system-riscv64 qemu-system-riscv64 while loading image of server installation of ubuntu. So it needs to be installed first. Get the source code of qemu-slirp using following command: git clone https://github.com/openSUSE/qemu-slirp.git Then Execute following commands to install slirp in meson, which can later be used by qemu during build. meson build ninja -C build install Note: Make sure you have riscv64-unknown-linux-gnu toolchain installed for compiling program and executing them on qemu later. There are some optional dependencies which one can download, but they are actually not needed for installing qemu and make it work.","title":"Installing Pre-requisites"},{"location":"Building_qemu/#installing-qemu-system-riscv64","text":"","title":"Installing qemu-system-riscv64"},{"location":"Building_qemu/#what-is-qemu-system-riscv64","text":"qemu-system-riscv64 is qemu executable program. It can load a complete linux distribution. It cannot take program's executable binary as argument and run it without a dedicated linux distribution.","title":"What is qemu-system-riscv64"},{"location":"Building_qemu/#installing-qemu-system-riscv64-on-ubuntu","text":"Get source code of qemu from github using the command below git clone https://github.com/qemu/qemu.git Configure qemu for riscv64-softmmu with following command (replace $PREFIX with valid location of installation). ./configure --prefix=$PREFIX --target-list=riscv64-linux-user,riscv64-softmmu --enable-slirp Execute following command to start the build. make Execute following command to install the binaries at $PREFIX location. make install Note: After the installation with slirp following error can be encountered on some systems . qemu-system-riscv64: symbol lookup error: qemu-system-riscv64: undefined symbol: slirp_new, version SLIRP_4.0 Solution: This can be solved by executing following command in source directory of qemu (which is cloned from github). [sudo] ldconfig","title":"Installing qemu-system-riscv64 on ubuntu"},{"location":"Building_qemu/#testing-qemu-system-riscv64","text":"qemu-system-riscv64 can only be tested by booting a linux operating system. See Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64 .","title":"Testing qemu-system-riscv64"},{"location":"Building_qemu/#installing-qemu-riscv64","text":"","title":"Installing qemu-riscv64"},{"location":"Building_qemu/#what-is-qemu-riscv64","text":"qemu-riscv64 is qemu executable program. But instead of porting a complete operating system (like qemu-system-riscv64 ), it can readily execute binaries. Throughout cross-compiling section, qemu-riscv64 will be used with linux-user and executable of every program can be tested on qemu (e.g. python, ruby etc.).","title":"What is qemu-riscv64"},{"location":"Building_qemu/#installing-qemu-riscv64-on-ubuntu-2204","text":"Get source code of qemu using the command below git clone https://github.com/qemu/qemu.git Use following command in the root directory of repository to configure qemu for riscv64-linux-user ./configure --target-list=riscv64-linux-user --prefix=$PREFIX # Replace $PREFIX with a valid location to install at Note: If this is not your architecture/platform, you can see a list of available platform/architecture by executing following command. ./configure --help Use the following command to start the build process make -j$(nproc) After the builld is complete without any error, use the following command to install binaries at $PREFIX location make install Add the $PREFIX/bin to $PATH variable so that it may be recognized as a command. Using this method causes the qemu-riscv64 to have an issue with sysroot. It starts searching for libraries in the root folder of the machine which is based on x86_64-linux-gnu . A simple workaround is to give path of the sysroot/ folder where riscv64-unknown-linux-gnu toolchain is installed. Here that directory will be denoted as $RISCV_SYSROOT","title":"Installing qemu-riscv64 on ubuntu 22.04"},{"location":"Building_qemu/#testing-qemu-riscv64","text":"Create a C file in your favorite editor or by using the commands below: echo \"#include<stdio.h>\" > helloworld.c echo \"int main(){\" >> helloworld.c echo \"printf(\"Hello World !\");\" >> helloworld.c echo '}' >> helloworld.c Execute following command to compile C program with riscv gnu toolchain riscv64-unknown-linux-gnu-gcc helloworld.c -o helloworld Execute following command to execute the compiled binary on qemu-riscv64 qemu-riscv64 -L $RISCV_SYSROOT ./helloworld If everything went right, following output will be shown. Hello World !","title":"Testing qemu-riscv64"},{"location":"Creating_CI_CD_pipeline/","text":"Creating a CI/CD pipeline in Jenkins Pre Requisistes For sake of this documentation, jenkins built-in sample script is used to create and execute a cd/cd pipeline in jenkins. In the built-in script maven is used as M3, so one must install Maven plugin inside jenkins and name it M3 . Usually maven is already present inside jenkins and can be configured from Global Configuration Tools . Following steps demonstrate configuring Maven plugin. Go to Jenkins Dashboard and click on Manage Jenkins In Manage Jenkins , under System Configuration section, click on Global Tool Configuration . In Global Tool Configuration , scroll down to Maven section and click on the respective option under the Maven Section (should be Maven installations\u2026 or Add Maven ). Under Maven installations , enter M3 in \u201cname\u201d text box, check Install Automatically and select Version greater than 3, then click Apply and Save . This should install Maven version 3 and configure as M3 . Steps for Jenkins pipeline creation After installing Jenkins and having all the suggested plugins installed, go to Jenkins dashboard and click on Create Job . On the next page, give your pipeline a name, select Pipeline and click OK . A Configuration page for the pipeline will appear. Select Build Triggers options and General options according to need and scroll down to the Pipeline section. Definition section contains configuration for stages and steps of the pipeline. Under Definition section, you can either choose Pipeline script and try writing your own script or try some sample pipeline (like Hello World , Github+Maven etc) or you could select Pipeline script from SCM and give a github repository containing configurations of Pipeline. Press Save and Apply . This should take you to the Pipeline and you can build the pipeline and if no unresolved dependencies are present, the pipeline should build without any error.","title":"Creating a pipeline project"},{"location":"Creating_CI_CD_pipeline/#creating-a-cicd-pipeline-in-jenkins","text":"","title":"Creating a CI/CD pipeline in Jenkins"},{"location":"Creating_CI_CD_pipeline/#pre-requisistes","text":"For sake of this documentation, jenkins built-in sample script is used to create and execute a cd/cd pipeline in jenkins. In the built-in script maven is used as M3, so one must install Maven plugin inside jenkins and name it M3 . Usually maven is already present inside jenkins and can be configured from Global Configuration Tools . Following steps demonstrate configuring Maven plugin. Go to Jenkins Dashboard and click on Manage Jenkins In Manage Jenkins , under System Configuration section, click on Global Tool Configuration . In Global Tool Configuration , scroll down to Maven section and click on the respective option under the Maven Section (should be Maven installations\u2026 or Add Maven ). Under Maven installations , enter M3 in \u201cname\u201d text box, check Install Automatically and select Version greater than 3, then click Apply and Save . This should install Maven version 3 and configure as M3 .","title":"Pre Requisistes"},{"location":"Creating_CI_CD_pipeline/#steps-for-jenkins-pipeline-creation","text":"After installing Jenkins and having all the suggested plugins installed, go to Jenkins dashboard and click on Create Job . On the next page, give your pipeline a name, select Pipeline and click OK . A Configuration page for the pipeline will appear. Select Build Triggers options and General options according to need and scroll down to the Pipeline section. Definition section contains configuration for stages and steps of the pipeline. Under Definition section, you can either choose Pipeline script and try writing your own script or try some sample pipeline (like Hello World , Github+Maven etc) or you could select Pipeline script from SCM and give a github repository containing configurations of Pipeline. Press Save and Apply . This should take you to the Pipeline and you can build the pipeline and if no unresolved dependencies are present, the pipeline should build without any error.","title":"Steps for Jenkins pipeline creation"},{"location":"Creating_Jenkins_Node_on_LXC/","text":"Creating a Jenkins Node on LXC Container What is a container A container is a virtualization method for isolating the applications (or even operating systems) from each other. Why do we need a container for Jenkins node In Jenkins, node is a location where our jobs run. One user can use one node for all of his processes and multiple users may also use one node for all of their processes. In Jenkins freestyle project, we can use bash shell or windows command shell due to which there is a possibility to navigate anywhere in the server machine. This possibility can lead to various security and integrity issues for server administrators and also for other users using that webserver. So one must isolate each node and allocate each node to each user separately. What is LXC Container LXC stands for Linux Containers. LXC is a package for linux operating systems and provides linux users with containers which may contain a whole linux operating system while also being lightweight than a virtual machine. More information regarding LXC can be found at https://linuxcontainers.org/lxc/introduction/ On ubuntu 20.04 one can install LXC using command [sudo] apt-get install lxc Creating a container with LXC NOTE: Throughout this document, the name of the container will be my-container and the name of the user will be user1 . So wherever my-container is written, one may change the name to whatever one wants to give it. Pre-requisites Before proceeding, it is important to mention that at the point of writing this document following are the specifications for linux kernel and distribution: Linux Kernel : 5.15.0-46-generic (can be checked on ubuntu by command uname -r ) Distribution : Ubuntu focal (20.04) (can be checked on ubuntu by command lsb_release -a ) By default linux users are not allowed to create any network device on the machine. For doing that, one must add uid and gid in the /etc/lxc/lxc-usernet . The uid and gid of the user you want to use can be found in the files /etc/uid and /etc/gid respectively. After getting the gid and uid of the user you want to allow for creating the network devices, one must go to /etc/lxc/lxc-usernet and add the uid and gid in the following format: <username> veth lxcbr0 10 e.g. jenkins veth lxcbr0 10 In above example jenkins is the username, veth is the command used for creating the bridges between virtual network devices and physical network devices (you will be able to see that ethernet device in our container will be lxcbr0 ) and lxbr0 is the network device we want to create. \u201810\u2019 represents the number of devices we want to create using our specified user. According lxc documentation, in ubuntu 20.04 an additional command is required before creating lxc container: export DOWNLOAD_KEYSERVER=\"hkp://keyserver.ubuntu.com\" Creating image After this, one can create container using following command systemd-run --unit=my-unit --user --scope -p \"Delegate=yes\" -- lxc-create -t download -n my-container This runs lxc container with unit name my-unit , container name my-container and delegates a control group (also known as the cgroup ) which is needed for resource allocation for processes in container. This will output the list of available linux distributions in which one may want to run the container and will prompt for Distribution as shown in the following image. After selecting the suitable distribution, release and architecture (which is also mentioned in the table), the container may be created as shown in the image below: Next thing is to start a container which will change its state from STOPPED to RUNNING using the following command. lxc-start -n my-container Above command will have no output if it succeeds. The state of the container can be checked using the following command. lxc-info -n my-container After starting the container, its state will be set as running and is just like turning a linux machine ON. From this point onwards, if one wants to use the machine in the terminal then use the following command and this will switch the terminal to the root of the container. lxc-attach my-container Now the container is ready to be used and is completely isolated from the host machine. Using SSH to access container with username and password The above mentioned method can be used to attach the host machine terminal to the container and this can be used to access the container. But if one wants to access the machine remotely then one possible and well-known method will be to configure and use SSH on the container. As it is an out of the box linux distro and only the root user is present, so first create another user using the following command and then manage its permissions for /home folder . #Considering you remain the root user for execution of all the following #commands useradd user1 cd /home mkdir user1 #Creating home directory for user1 chown user1:user1 user1 #Giving ownership of home directory to new user #For adding the same shell and bashrc configurations for new user, use #following #command, otherwise the shell will be very basic for new user and will be #very inconvenient to use. usermod -s /bin/bash user1 For the sake of simplicity of this document the name used for the new user is user1 here. (You may want to set the password for user1 by executing the passwd command in root.) At this point user1 is not in sudoers. For adding it to the sudoers, it must be added in the sudo group which can be done by using the following command. usermod -a -G sudo user1 Now switch to the user1 using the following command. su - user Now install openssh-server for configuring the ssh on user1. sudo apt install openssh-server After that one must find the ip of the container we are using, for this either run following command while in container with user1, sudo apt-install net-tools #Because ifconfig is part of net-tools which are by default not installed on new #container Ifconfig -a OR open a new terminal in the host machine and execute the following command. lxc-info my-container -iH So, the ip of the container is 10.0.3.127 . The command for establishing an ssh connection to a remote machine is mentioned below and it will ask for the password of the remote machine which is actually the container in our case. ssh user1@10.0.3.127 After entering the password, terminal will switch to the container\u2019s user1 as can be seen in the following image. Using SSH to access Jenkins agents on the container First install some initial dependencies (git, jdk, jre) on the containers for running agents on the container. sudo apt update sudo apt install default-jdk default-jre git maven Now login to jenkins with administrator privileges and create a node in it from Dashboard > Manage Jenkins > Nodes and press + New Node . Enter a name for the node and select the desirable node type. For this documentation, the node will be a permanent type and the name will be temp_node . After this click on Create which will display the configuration page of the node. Write the description of the node as desired. Number of executors means number of threads running at a time (it will be better to set it to the number of processors present on the machine which is running this node). Remote root directory will be the directory where the jobs will run by default on the node. In our case this will be a specified directory inside the container. Labels indicate that this node will run only when a job with specified labels is run, otherwise this node will not be used (also depends on the usage method in the next option). If the purpose is to use the node by default for every job, then leave it empty. Select a desired usage option. In launch methods, select \u201cLaunch agents via SSH\u201d In \u201cHost\u201d enter the ip address of the container which is 10.0.3.127 in our case. In \u201cCredentials\u201d, click Add and this will open another sub dialog for entering credentials information. Select the kind as \u201cUsername wih password\u201d. Leave other options as is and write the username and password of the container user, in our case the username will be user1 and password will be the password which was set for user1. \u201cID\u201d and \u201cDescription\u201d are optional. Click on \u201cAdd\u201d. Now as the credentials are added, click on the dropdown menu and select the username you just added. In our case it is user1 as the username added was user1. After this rest of the options need not to be changed if this node is going to be a default node. Click on \u201cSave\u201d. After complete setup, the configuration for this node will look something like this. If no issue is encountered during this whole setup, jenkins will take us to the log and after sometime (when the ssh connection is established) we can see \u201cAgent successfully connected and online\u201d at the bottom of the log as can be seen in the screenshot below. After this point, node will be able to run jobs from the container directory. Reference Links Documentation for LXC containers can be found at: https://linuxcontainers.org Details regarding Jenkins ssh agents can be found at: https://acloudguru.com/blog/engineering/adding-a-jenkins-agent-node","title":"Creating Jenkins Node on LXC"},{"location":"Creating_Jenkins_Node_on_LXC/#creating-a-jenkins-node-on-lxc-container","text":"","title":"Creating a Jenkins Node on LXC Container"},{"location":"Creating_Jenkins_Node_on_LXC/#what-is-a-container","text":"A container is a virtualization method for isolating the applications (or even operating systems) from each other.","title":"What is a container"},{"location":"Creating_Jenkins_Node_on_LXC/#why-do-we-need-a-container-for-jenkins-node","text":"In Jenkins, node is a location where our jobs run. One user can use one node for all of his processes and multiple users may also use one node for all of their processes. In Jenkins freestyle project, we can use bash shell or windows command shell due to which there is a possibility to navigate anywhere in the server machine. This possibility can lead to various security and integrity issues for server administrators and also for other users using that webserver. So one must isolate each node and allocate each node to each user separately.","title":"Why do we need a container for Jenkins node"},{"location":"Creating_Jenkins_Node_on_LXC/#what-is-lxc-container","text":"LXC stands for Linux Containers. LXC is a package for linux operating systems and provides linux users with containers which may contain a whole linux operating system while also being lightweight than a virtual machine. More information regarding LXC can be found at https://linuxcontainers.org/lxc/introduction/ On ubuntu 20.04 one can install LXC using command [sudo] apt-get install lxc","title":"What is LXC Container"},{"location":"Creating_Jenkins_Node_on_LXC/#creating-a-container-with-lxc","text":"NOTE: Throughout this document, the name of the container will be my-container and the name of the user will be user1 . So wherever my-container is written, one may change the name to whatever one wants to give it.","title":"Creating a container with LXC"},{"location":"Creating_Jenkins_Node_on_LXC/#pre-requisites","text":"Before proceeding, it is important to mention that at the point of writing this document following are the specifications for linux kernel and distribution: Linux Kernel : 5.15.0-46-generic (can be checked on ubuntu by command uname -r ) Distribution : Ubuntu focal (20.04) (can be checked on ubuntu by command lsb_release -a ) By default linux users are not allowed to create any network device on the machine. For doing that, one must add uid and gid in the /etc/lxc/lxc-usernet . The uid and gid of the user you want to use can be found in the files /etc/uid and /etc/gid respectively. After getting the gid and uid of the user you want to allow for creating the network devices, one must go to /etc/lxc/lxc-usernet and add the uid and gid in the following format: <username> veth lxcbr0 10 e.g. jenkins veth lxcbr0 10 In above example jenkins is the username, veth is the command used for creating the bridges between virtual network devices and physical network devices (you will be able to see that ethernet device in our container will be lxcbr0 ) and lxbr0 is the network device we want to create. \u201810\u2019 represents the number of devices we want to create using our specified user. According lxc documentation, in ubuntu 20.04 an additional command is required before creating lxc container: export DOWNLOAD_KEYSERVER=\"hkp://keyserver.ubuntu.com\"","title":"Pre-requisites"},{"location":"Creating_Jenkins_Node_on_LXC/#creating-image","text":"After this, one can create container using following command systemd-run --unit=my-unit --user --scope -p \"Delegate=yes\" -- lxc-create -t download -n my-container This runs lxc container with unit name my-unit , container name my-container and delegates a control group (also known as the cgroup ) which is needed for resource allocation for processes in container. This will output the list of available linux distributions in which one may want to run the container and will prompt for Distribution as shown in the following image. After selecting the suitable distribution, release and architecture (which is also mentioned in the table), the container may be created as shown in the image below: Next thing is to start a container which will change its state from STOPPED to RUNNING using the following command. lxc-start -n my-container Above command will have no output if it succeeds. The state of the container can be checked using the following command. lxc-info -n my-container After starting the container, its state will be set as running and is just like turning a linux machine ON. From this point onwards, if one wants to use the machine in the terminal then use the following command and this will switch the terminal to the root of the container. lxc-attach my-container Now the container is ready to be used and is completely isolated from the host machine.","title":"Creating image"},{"location":"Creating_Jenkins_Node_on_LXC/#using-ssh-to-access-container-with-username-and-password","text":"The above mentioned method can be used to attach the host machine terminal to the container and this can be used to access the container. But if one wants to access the machine remotely then one possible and well-known method will be to configure and use SSH on the container. As it is an out of the box linux distro and only the root user is present, so first create another user using the following command and then manage its permissions for /home folder . #Considering you remain the root user for execution of all the following #commands useradd user1 cd /home mkdir user1 #Creating home directory for user1 chown user1:user1 user1 #Giving ownership of home directory to new user #For adding the same shell and bashrc configurations for new user, use #following #command, otherwise the shell will be very basic for new user and will be #very inconvenient to use. usermod -s /bin/bash user1 For the sake of simplicity of this document the name used for the new user is user1 here. (You may want to set the password for user1 by executing the passwd command in root.) At this point user1 is not in sudoers. For adding it to the sudoers, it must be added in the sudo group which can be done by using the following command. usermod -a -G sudo user1 Now switch to the user1 using the following command. su - user Now install openssh-server for configuring the ssh on user1. sudo apt install openssh-server After that one must find the ip of the container we are using, for this either run following command while in container with user1, sudo apt-install net-tools #Because ifconfig is part of net-tools which are by default not installed on new #container Ifconfig -a OR open a new terminal in the host machine and execute the following command. lxc-info my-container -iH So, the ip of the container is 10.0.3.127 . The command for establishing an ssh connection to a remote machine is mentioned below and it will ask for the password of the remote machine which is actually the container in our case. ssh user1@10.0.3.127 After entering the password, terminal will switch to the container\u2019s user1 as can be seen in the following image.","title":"Using SSH to access container with username and password"},{"location":"Creating_Jenkins_Node_on_LXC/#using-ssh-to-access-jenkins-agents-on-the-container","text":"First install some initial dependencies (git, jdk, jre) on the containers for running agents on the container. sudo apt update sudo apt install default-jdk default-jre git maven Now login to jenkins with administrator privileges and create a node in it from Dashboard > Manage Jenkins > Nodes and press + New Node . Enter a name for the node and select the desirable node type. For this documentation, the node will be a permanent type and the name will be temp_node . After this click on Create which will display the configuration page of the node. Write the description of the node as desired. Number of executors means number of threads running at a time (it will be better to set it to the number of processors present on the machine which is running this node). Remote root directory will be the directory where the jobs will run by default on the node. In our case this will be a specified directory inside the container. Labels indicate that this node will run only when a job with specified labels is run, otherwise this node will not be used (also depends on the usage method in the next option). If the purpose is to use the node by default for every job, then leave it empty. Select a desired usage option. In launch methods, select \u201cLaunch agents via SSH\u201d In \u201cHost\u201d enter the ip address of the container which is 10.0.3.127 in our case. In \u201cCredentials\u201d, click Add and this will open another sub dialog for entering credentials information. Select the kind as \u201cUsername wih password\u201d. Leave other options as is and write the username and password of the container user, in our case the username will be user1 and password will be the password which was set for user1. \u201cID\u201d and \u201cDescription\u201d are optional. Click on \u201cAdd\u201d. Now as the credentials are added, click on the dropdown menu and select the username you just added. In our case it is user1 as the username added was user1. After this rest of the options need not to be changed if this node is going to be a default node. Click on \u201cSave\u201d. After complete setup, the configuration for this node will look something like this. If no issue is encountered during this whole setup, jenkins will take us to the log and after sometime (when the ssh connection is established) we can see \u201cAgent successfully connected and online\u201d at the bottom of the log as can be seen in the screenshot below. After this point, node will be able to run jobs from the container directory.","title":"Using SSH to access Jenkins agents on the container"},{"location":"Creating_Jenkins_Node_on_LXC/#reference-links","text":"Documentation for LXC containers can be found at: https://linuxcontainers.org Details regarding Jenkins ssh agents can be found at: https://acloudguru.com/blog/engineering/adding-a-jenkins-agent-node","title":"Reference Links"},{"location":"Creating_jenkinsfile/","text":"Creating a Jenkinsfile What is a Jenkinsfile A Jenkinsfile is a Continuous Integration (CI) pipeline script which is written Java. It describes various stages (and possibly steps) which are executed in the defined pattern. These stages can be written in bash or they can be written in Java itself. Mainly Jenkinsfiles are of two types: Scripted: Only contains stages Declarative: Contains stages as well as steps This documentation will cover how to create a jenkinsfile in bash script and run it on various compute instances (which are known as Nodes in jenkins). Jenkins Node In jenkins, node represents a compute instance. In simple words, it is the platform on which our job build is going to run. Jenkins Master There is a jenkins Master node which is actually the compute instance on which Jenkins is installed. It is the node which schedules builds on runners. For security reason, no job is allowed to run on this node. Jenkins Slave Jenkins slave nodes are the compute instances on which our job builds run safely. They may be attached with jenkins master via hardware or they may be connected through remote SSH connection. Jenkinsfile written in Bash Simple Hello World Jenkinsfile In Cloud-V, all the platforms are running Linux operating system, so the jenkinsfile should be written in bash. Following script is an example of how can we run a bash script in scripted pipeline Jenkinsfile. node{ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } } The keyword sh is used to specify a shell script As there is nothing mentioned with node , so the script will run job build on any available compute instance. Jenkinsfile for a Specific Node In previous script, the jenkinsfile would run on any compute instances which are available. But in case if someone wants to run a job build on specific node, then a compute instance name must be specified with keyword node . The following script is an example of running above Hello World program on node named hifive_unleashed . node('hifive_unleashed'){ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } } Jenkinsfile for Cross-Platform Compilation and Execution Cloud-V supports cross-compilation and execution on emulated RISC-V compute instances. Following tools help in cross compilation and cross-platfrom execution: RISC-V GNU Toolchain QEMU user mode QEMU System (with Linux installed) An example pipeline script is given below in scripted pipeline. node('x86_runner2'){ checkout scm //Getting content of this repo stage('*** Compilation Phase ***') { // for display purposes //Compiling helloworld.c using bash commands sh '''#!/bin/bash gcc -g ./helloworld.c -o helloworld.out riscv64-unknown-linux-gnu-gcc ./helloworld.c -o helloworld_riscv_compiled.out //Cross compiling for RISC-V ''' } stage (' *** Running Binaries ***'){ sh '''#!/bin/bash ./helloworld.out qemu-riscv64 -L $RISCV_SYSROOT helloworld_riscv_compiled.out //Running executable on RISC-V emulated platform ''' } } The equivalent declarative pipeline is as follows: pipeline { agent {label \"x86_runner2\"} stages { stage('Clone Repository') { steps('delegate'){ checkout scm //Clones the repository on the local machine } } stage ('Compilation Phase'){ steps{ sh '''#!/bin/bash gcc -g ./helloworld.c -o helloworld.out ''' sh '''#!/bin/bash riscv64-unknown-linux-gnu-gcc ./helloworld.c -o helloworld_riscv_compiled.out ''' } } stage ('Running Binaries'){ steps { sh ''' #!/bin/bash ./helloworld.out ''' sh'''#!/bin/bash qemu-riscv64 -L $RISCV_SYSROOT helloworld_riscv_compiled.out ''' } } } } Reference Links https://www.jenkins.io/doc/book/pipeline/syntax/","title":"Creating a Jenkinfile"},{"location":"Creating_jenkinsfile/#creating-a-jenkinsfile","text":"","title":"Creating a Jenkinsfile"},{"location":"Creating_jenkinsfile/#what-is-a-jenkinsfile","text":"A Jenkinsfile is a Continuous Integration (CI) pipeline script which is written Java. It describes various stages (and possibly steps) which are executed in the defined pattern. These stages can be written in bash or they can be written in Java itself. Mainly Jenkinsfiles are of two types: Scripted: Only contains stages Declarative: Contains stages as well as steps This documentation will cover how to create a jenkinsfile in bash script and run it on various compute instances (which are known as Nodes in jenkins).","title":"What is a Jenkinsfile"},{"location":"Creating_jenkinsfile/#jenkins-node","text":"In jenkins, node represents a compute instance. In simple words, it is the platform on which our job build is going to run.","title":"Jenkins Node"},{"location":"Creating_jenkinsfile/#jenkins-master","text":"There is a jenkins Master node which is actually the compute instance on which Jenkins is installed. It is the node which schedules builds on runners. For security reason, no job is allowed to run on this node.","title":"Jenkins Master"},{"location":"Creating_jenkinsfile/#jenkins-slave","text":"Jenkins slave nodes are the compute instances on which our job builds run safely. They may be attached with jenkins master via hardware or they may be connected through remote SSH connection.","title":"Jenkins Slave"},{"location":"Creating_jenkinsfile/#jenkinsfile-written-in-bash","text":"","title":"Jenkinsfile written in Bash"},{"location":"Creating_jenkinsfile/#simple-hello-world-jenkinsfile","text":"In Cloud-V, all the platforms are running Linux operating system, so the jenkinsfile should be written in bash. Following script is an example of how can we run a bash script in scripted pipeline Jenkinsfile. node{ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } } The keyword sh is used to specify a shell script As there is nothing mentioned with node , so the script will run job build on any available compute instance.","title":"Simple Hello World Jenkinsfile"},{"location":"Creating_jenkinsfile/#jenkinsfile-for-a-specific-node","text":"In previous script, the jenkinsfile would run on any compute instances which are available. But in case if someone wants to run a job build on specific node, then a compute instance name must be specified with keyword node . The following script is an example of running above Hello World program on node named hifive_unleashed . node('hifive_unleashed'){ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } }","title":"Jenkinsfile for a Specific Node"},{"location":"Creating_jenkinsfile/#jenkinsfile-for-cross-platform-compilation-and-execution","text":"Cloud-V supports cross-compilation and execution on emulated RISC-V compute instances. Following tools help in cross compilation and cross-platfrom execution: RISC-V GNU Toolchain QEMU user mode QEMU System (with Linux installed) An example pipeline script is given below in scripted pipeline. node('x86_runner2'){ checkout scm //Getting content of this repo stage('*** Compilation Phase ***') { // for display purposes //Compiling helloworld.c using bash commands sh '''#!/bin/bash gcc -g ./helloworld.c -o helloworld.out riscv64-unknown-linux-gnu-gcc ./helloworld.c -o helloworld_riscv_compiled.out //Cross compiling for RISC-V ''' } stage (' *** Running Binaries ***'){ sh '''#!/bin/bash ./helloworld.out qemu-riscv64 -L $RISCV_SYSROOT helloworld_riscv_compiled.out //Running executable on RISC-V emulated platform ''' } } The equivalent declarative pipeline is as follows: pipeline { agent {label \"x86_runner2\"} stages { stage('Clone Repository') { steps('delegate'){ checkout scm //Clones the repository on the local machine } } stage ('Compilation Phase'){ steps{ sh '''#!/bin/bash gcc -g ./helloworld.c -o helloworld.out ''' sh '''#!/bin/bash riscv64-unknown-linux-gnu-gcc ./helloworld.c -o helloworld_riscv_compiled.out ''' } } stage ('Running Binaries'){ steps { sh ''' #!/bin/bash ./helloworld.out ''' sh'''#!/bin/bash qemu-riscv64 -L $RISCV_SYSROOT helloworld_riscv_compiled.out ''' } } } }","title":"Jenkinsfile for Cross-Platform Compilation and Execution"},{"location":"Creating_jenkinsfile/#reference-links","text":"https://www.jenkins.io/doc/book/pipeline/syntax/","title":"Reference Links"},{"location":"Installing_ssl_certificates_new/","text":"Configure letsencrypt with jenkins SSL certificates allow a website to run on HTTPS protocol which makes sure that data transfer between user and server cannot be intercepted between them. When using HTTPS protocol the data transfer is encrypted between user and server being used. NOTE: Keep the fact in mind that letsencrypt does not generate certificates for bare IP. It needs a domain name. Installing SSL certificates with letsencrypt In unix, letsencrypt package is called certbot . This can be installed using following command: sudo apt install certbot Here standalone mode will be used for generating certificates which authenticates the machine's ownership by hosting a temporary server on port 80. This is because ports less than 1024 are privileged and require root/sudo access. So make sure that port 80 is open in firewall and there is no application already running on it. Also if this process is being done on container, make sure port 80 is forwarded properly. One can also use webroot mode to generate certificates. See this link for more information. Use following command to generate certificate files and keys in /etc/letsencrypt/live/your.domain.name/ certbot certonly --standalone -d your.domain.name This will produce cert.pem , fullchain.pem and privkey.pem . Copy these files to location where .war of jenkins is located. Make sure to change the permission from root to jenkins' user. After that, use following command to convert certificate files to pkcs12 format. openssl pkcs12 -inkey privkey.pem -in fullchain.pem -export -out keys.pkcs12 keytool -importkeystore -srckeystore keys.pkcs12 -srcstoretype pkcs12 -destkeystore keystore This will ask for a password. Here it will be denoted as <password> . Use following command to start jenkins server with generated SSL certificates. java -jar jenkins.war --httpPort=-1 --httpsPort=<your_port> --httpsKeyStore=keystore --httpsKeyStorePassword=<password> After this, go to browser and type your.domain.name:<your_port> to start jenkins with https protocol.","title":"Letsencrypt configuration with Jenkins"},{"location":"Installing_ssl_certificates_new/#configure-letsencrypt-with-jenkins","text":"SSL certificates allow a website to run on HTTPS protocol which makes sure that data transfer between user and server cannot be intercepted between them. When using HTTPS protocol the data transfer is encrypted between user and server being used. NOTE: Keep the fact in mind that letsencrypt does not generate certificates for bare IP. It needs a domain name.","title":"Configure letsencrypt with jenkins"},{"location":"Installing_ssl_certificates_new/#installing-ssl-certificates-with-letsencrypt","text":"In unix, letsencrypt package is called certbot . This can be installed using following command: sudo apt install certbot Here standalone mode will be used for generating certificates which authenticates the machine's ownership by hosting a temporary server on port 80. This is because ports less than 1024 are privileged and require root/sudo access. So make sure that port 80 is open in firewall and there is no application already running on it. Also if this process is being done on container, make sure port 80 is forwarded properly. One can also use webroot mode to generate certificates. See this link for more information. Use following command to generate certificate files and keys in /etc/letsencrypt/live/your.domain.name/ certbot certonly --standalone -d your.domain.name This will produce cert.pem , fullchain.pem and privkey.pem . Copy these files to location where .war of jenkins is located. Make sure to change the permission from root to jenkins' user. After that, use following command to convert certificate files to pkcs12 format. openssl pkcs12 -inkey privkey.pem -in fullchain.pem -export -out keys.pkcs12 keytool -importkeystore -srckeystore keys.pkcs12 -srcstoretype pkcs12 -destkeystore keystore This will ask for a password. Here it will be denoted as <password> . Use following command to start jenkins server with generated SSL certificates. java -jar jenkins.war --httpPort=-1 --httpsPort=<your_port> --httpsKeyStore=keystore --httpsKeyStorePassword=<password> After this, go to browser and type your.domain.name:<your_port> to start jenkins with https protocol.","title":"Installing SSL certificates with letsencrypt"},{"location":"Multinode_Pipelines/","text":"Multinode Pipelines One can create multinode pipelines in jenkins freestyle pipeline job as well as in jenkins native pipeline job. In such a pipeline, different stages of the pipeline can run on separate nodes. The jenkins native pipeline job can have two types. Scripted Pipeline Declarative pipeline For the sake of this documentation, two nodes are used: container-node and container-node2 Label In jenkins, label specifies where the job or a stage of the job can run. In jenkins, a label can be explicitly added in the node's configuration so that each time that label is mentioned in a jenkins job, that specific node is used for building the job, or the name of the node can also be used as label in case if no label is added in the node. Creating multinode pipelines in Jenkins native pipeline job Scripted Pipeline For creating a multinode pipeline with jenkins native scripted pipeline job, jenkinsfile can be tweaked. The keyword node can be used to specify the node in which the stages are going to run and this keyword can also be used in between stages. Following screenshot indicates a code in which first stage runs on node named container-node . While the second node runs on node named container-node2 . node ('container-node') { stage ('*** Creating a directory in container-node ***'){ sh '''#!/bin/bash mkdir newdir_container-node-$RANDOM ''' } stage ('*** Creating a directory in container-node2'){ node ('container-node2'){ sh'''#!/bin/bash mkdir newdir_container-node2-$RANDOM ''' } } } Declarative pipeline For a declarative pipeline the keyword label can be used in the agent block. This can either be done at the start of the pipeline after the keyword pipeline or it can be used inside the stages. The following code builds two stages each of which is built in separate node. The keyword none with agent means that the agent is not specified globally for each stage and it should be specified inside each stage. pipeline { agent none // Means no agent specified. This means each node will specify its own agent stages { stage('container-node') { agent{ label \"container-node\" //Selecting container-node for this stage } steps { sh '''#!/bin/bash echo 'Hello container-node' mkdir \"newdir-container-node-$RANDOM\" ''' } } stage('container-node2'){ agent{ label \"container-node2\" //Selecting container-node2 for this stage } steps{ sh'''#!/bin/bash echo ''Hello container-node2 mkdir \"newdir-container-node2-$RANDOM\" ''' } } } } Creating multinode pipelines using Jenkins freestyle jobs Jenkins freestyle jobs can be combined together by mentioning post-build jobs in the freestyle job settings. Freestyle jobs are customizable and offer more options than jenkins native pipeline jobs. Each job represents a stage and each stage has separate settings. One can use jenkins freestyle jobs to run on a separate node by selecting the option Restrict where this project can be run in the General section of the job's configuration. In the Label Expression , the node's name can be mentioned in which to run the job. The following image shows the option from job's configuration. This can be done in all the job's configuration for the specified node.","title":"Creating Multinode pipelines"},{"location":"Multinode_Pipelines/#multinode-pipelines","text":"One can create multinode pipelines in jenkins freestyle pipeline job as well as in jenkins native pipeline job. In such a pipeline, different stages of the pipeline can run on separate nodes. The jenkins native pipeline job can have two types. Scripted Pipeline Declarative pipeline For the sake of this documentation, two nodes are used: container-node and container-node2","title":"Multinode Pipelines"},{"location":"Multinode_Pipelines/#label","text":"In jenkins, label specifies where the job or a stage of the job can run. In jenkins, a label can be explicitly added in the node's configuration so that each time that label is mentioned in a jenkins job, that specific node is used for building the job, or the name of the node can also be used as label in case if no label is added in the node.","title":"Label"},{"location":"Multinode_Pipelines/#creating-multinode-pipelines-in-jenkins-native-pipeline-job","text":"","title":"Creating multinode pipelines in Jenkins native pipeline job"},{"location":"Multinode_Pipelines/#scripted-pipeline","text":"For creating a multinode pipeline with jenkins native scripted pipeline job, jenkinsfile can be tweaked. The keyword node can be used to specify the node in which the stages are going to run and this keyword can also be used in between stages. Following screenshot indicates a code in which first stage runs on node named container-node . While the second node runs on node named container-node2 . node ('container-node') { stage ('*** Creating a directory in container-node ***'){ sh '''#!/bin/bash mkdir newdir_container-node-$RANDOM ''' } stage ('*** Creating a directory in container-node2'){ node ('container-node2'){ sh'''#!/bin/bash mkdir newdir_container-node2-$RANDOM ''' } } }","title":"Scripted Pipeline"},{"location":"Multinode_Pipelines/#declarative-pipeline","text":"For a declarative pipeline the keyword label can be used in the agent block. This can either be done at the start of the pipeline after the keyword pipeline or it can be used inside the stages. The following code builds two stages each of which is built in separate node. The keyword none with agent means that the agent is not specified globally for each stage and it should be specified inside each stage. pipeline { agent none // Means no agent specified. This means each node will specify its own agent stages { stage('container-node') { agent{ label \"container-node\" //Selecting container-node for this stage } steps { sh '''#!/bin/bash echo 'Hello container-node' mkdir \"newdir-container-node-$RANDOM\" ''' } } stage('container-node2'){ agent{ label \"container-node2\" //Selecting container-node2 for this stage } steps{ sh'''#!/bin/bash echo ''Hello container-node2 mkdir \"newdir-container-node2-$RANDOM\" ''' } } } }","title":"Declarative pipeline"},{"location":"Multinode_Pipelines/#creating-multinode-pipelines-using-jenkins-freestyle-jobs","text":"Jenkins freestyle jobs can be combined together by mentioning post-build jobs in the freestyle job settings. Freestyle jobs are customizable and offer more options than jenkins native pipeline jobs. Each job represents a stage and each stage has separate settings. One can use jenkins freestyle jobs to run on a separate node by selecting the option Restrict where this project can be run in the General section of the job's configuration. In the Label Expression , the node's name can be mentioned in which to run the job. The following image shows the option from job's configuration. This can be done in all the job's configuration for the specified node.","title":"Creating multinode pipelines using Jenkins freestyle jobs"},{"location":"Software_Developer_Guide/","text":"Software Developer Guide for RISC-V CI A software developer is the end-user who will develop or build his/her projects on RISC-V CI infrastructure. This guide will cover all the things a software developer needs to create a project based on Cloud-V Continuous Integration (CI). Pre-requisites GitHub account. GitHub project repository with owner rights. Getting an account for Cloud-V Fill out this google form with all the required information for getting an account on Cloud-V. After this we will get back to you with login credentials. Setting up cloud-v-pipeline inside github project repository Cloud-V will need a cloud-v-pipeline written with jenkinsfile pipeline syntax to start execution of tests/checks (see link ). This pipeline will contain all the stages (and may be steps) of a CI/CD pipeline. This pipeline can be scripted pipeline which will only have stages or it can also be declarative pipeline which may also have steps inside stages. A simple scripted Helloworld pipeline in linux is as follows: node{ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } } Upon execution of such a pipeline, the console output can be viewed as follows. Note: This cloud-v-pipeline should remain same in all the branches and pull requests. Setting credentials for webhook Cloud-V supports webhooks which can trigger the job from external sources such as GitHub. They work in a way such that, if a specified branch is committed or if a pull request is created, the specified job build starts running depending upon the trigger event which is set in build's configuration in Cloud-V. This process requires access token of the repository CREATED BY OWNER OF REPOSITORY on which the webhook is to be set. These credentials can be safely added to Cloud-V without anyone (even administrator) seeing the passwords as follows. Obtaining github access token for repository Navigate to the dashboard of your github account and click on the your github profile picture on the top-right corner on dashboard. Then click on the \"Settings\" from the list. From the left option bar in Settings scroll down and click on \"Developer settings\". Once there, click on \"Personal access tokens\", then click on \"Fine-grained tokens\" from the dropdown list and after that click on \"Generate new token\". This will open the page for setting up new access token. Follow following steps for creating a token: Give your token a meaningful name under \"Token name\" Set expiration date in \"Expiration\" depending upon how long you would like your repository to be integrated with Cloud-V (think of a meaningful upper bound) The \"Resource owner\" should be the owner of the repository who can access all kinds of settings of the repository Under \"Repository access\", check \"Only select repositories\" and then select the repository for which you would like to create the token Under \"Permissions\" section, expand \"Repository Permissions\" and give the following two permissions: \"Read and write\" access to \"Commit statuses\" (Because after the CI has run, Cloud-V will be able to set the status of the commit accordingly) \"Read and write\" access to \"Webhooks\" (Read permission for the webhook is required for reading the incoming pull request. Write permission is required if you want Cloud-V to set the webhook for you instead of you going through the repository settings and setting it up) IMPORTANT NOTE: If you have decided to create a webhook yourself or have already created one, then Cloud-V will not be able to manage the settings for you, proceed to following section Configuring repository webhook (Optional) You can skip this step if you have given webhook read and write permission in your repository token settings in above step and havent configured any webhook yourself In GitHub, Go to repository settings which you want to integrate for Cloud-V. Go to Webhooks Click on Add webhook Add Payload URL as https://cloud-v.co:8443/ghprbhook/ Select content type as application/x-www-form-urlencoded Check Enable SSL verification In the section Which events would you like to trigger this webhook? check Let me select individual events and check Pul requests as individual events and dont check any other permission. Webhook settings will look something like this: Configurations inside Cloud-V Note: Currently users are not able to see or modify pipeline build configuration inside Jenkins, that is currently managed by administrator. Users are requested to inform administrator about how they want their pipeline configured. We will provide you with Cloud-V credentials on the provided email. Login with provided credentials. Click on the Credentials in the left menu. This will take you to the credentials page. Scroll down to the Stores scoped to Jenkins and click on the System as shown in the image. Click on Global credentials (unrestricted) . Click on Add Credentials . This will take you to the New Credentials page. Select Kind as Secret text . Select Scope as Global (Jenkins, nodes, items, all child items etc) . Enter Secret as GitHub personal authentication token (PAT) which can be acquired from Github account settings. Enter a unique ID . Description can be left empty. But it is recommended to give a suitable but careful description by which administrator will be able to identify and use these credentials to set up github webhook. Select Create . This process will look something like this. Now credentials will be available in the credentials list and will be shown to you as well as administrator as shown in the image below. This will create an option in configurations for using these credentials in github webhook without changing or viewing them. Note the credentials ID (as shown in the image below) and email it to the same administrator email on which you received the credentials. It is important that administrator knows the credentials ID because he will use it in the job build configurations. Note: Please make sure to inform the administrator via email that you have added the credentials in jenkins. Also, send administrator the ID of credentials via email. Requirements for administrator After the above setup is complete from software developer's side, developer will need to provide the administrator with following information. Dependencies for running the project which can be packages which are needed to install in the RISC-V CI environment by administrator. Events for triggering the job build. URL of GitHub repository. Path and name of Jenkinsfile on the provided GitHub repository. Any additional information which should be given for successful execution of job builds.","title":"Guide for Software Developer"},{"location":"Software_Developer_Guide/#software-developer-guide-for-risc-v-ci","text":"A software developer is the end-user who will develop or build his/her projects on RISC-V CI infrastructure. This guide will cover all the things a software developer needs to create a project based on Cloud-V Continuous Integration (CI).","title":"Software Developer Guide for RISC-V CI"},{"location":"Software_Developer_Guide/#pre-requisites","text":"GitHub account. GitHub project repository with owner rights.","title":"Pre-requisites"},{"location":"Software_Developer_Guide/#getting-an-account-for-cloud-v","text":"Fill out this google form with all the required information for getting an account on Cloud-V. After this we will get back to you with login credentials.","title":"Getting an account for Cloud-V"},{"location":"Software_Developer_Guide/#setting-up-cloud-v-pipeline-inside-github-project-repository","text":"Cloud-V will need a cloud-v-pipeline written with jenkinsfile pipeline syntax to start execution of tests/checks (see link ). This pipeline will contain all the stages (and may be steps) of a CI/CD pipeline. This pipeline can be scripted pipeline which will only have stages or it can also be declarative pipeline which may also have steps inside stages. A simple scripted Helloworld pipeline in linux is as follows: node{ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } } Upon execution of such a pipeline, the console output can be viewed as follows. Note: This cloud-v-pipeline should remain same in all the branches and pull requests.","title":"Setting up cloud-v-pipeline inside github project repository"},{"location":"Software_Developer_Guide/#setting-credentials-for-webhook","text":"Cloud-V supports webhooks which can trigger the job from external sources such as GitHub. They work in a way such that, if a specified branch is committed or if a pull request is created, the specified job build starts running depending upon the trigger event which is set in build's configuration in Cloud-V. This process requires access token of the repository CREATED BY OWNER OF REPOSITORY on which the webhook is to be set. These credentials can be safely added to Cloud-V without anyone (even administrator) seeing the passwords as follows.","title":"Setting credentials for webhook"},{"location":"Software_Developer_Guide/#obtaining-github-access-token-for-repository","text":"Navigate to the dashboard of your github account and click on the your github profile picture on the top-right corner on dashboard. Then click on the \"Settings\" from the list. From the left option bar in Settings scroll down and click on \"Developer settings\". Once there, click on \"Personal access tokens\", then click on \"Fine-grained tokens\" from the dropdown list and after that click on \"Generate new token\". This will open the page for setting up new access token. Follow following steps for creating a token: Give your token a meaningful name under \"Token name\" Set expiration date in \"Expiration\" depending upon how long you would like your repository to be integrated with Cloud-V (think of a meaningful upper bound) The \"Resource owner\" should be the owner of the repository who can access all kinds of settings of the repository Under \"Repository access\", check \"Only select repositories\" and then select the repository for which you would like to create the token Under \"Permissions\" section, expand \"Repository Permissions\" and give the following two permissions: \"Read and write\" access to \"Commit statuses\" (Because after the CI has run, Cloud-V will be able to set the status of the commit accordingly) \"Read and write\" access to \"Webhooks\" (Read permission for the webhook is required for reading the incoming pull request. Write permission is required if you want Cloud-V to set the webhook for you instead of you going through the repository settings and setting it up) IMPORTANT NOTE: If you have decided to create a webhook yourself or have already created one, then Cloud-V will not be able to manage the settings for you, proceed to following section","title":"Obtaining github access token for repository"},{"location":"Software_Developer_Guide/#configuring-repository-webhook-optional","text":"You can skip this step if you have given webhook read and write permission in your repository token settings in above step and havent configured any webhook yourself In GitHub, Go to repository settings which you want to integrate for Cloud-V. Go to Webhooks Click on Add webhook Add Payload URL as https://cloud-v.co:8443/ghprbhook/ Select content type as application/x-www-form-urlencoded Check Enable SSL verification In the section Which events would you like to trigger this webhook? check Let me select individual events and check Pul requests as individual events and dont check any other permission. Webhook settings will look something like this:","title":"Configuring repository webhook (Optional)"},{"location":"Software_Developer_Guide/#configurations-inside-cloud-v","text":"Note: Currently users are not able to see or modify pipeline build configuration inside Jenkins, that is currently managed by administrator. Users are requested to inform administrator about how they want their pipeline configured. We will provide you with Cloud-V credentials on the provided email. Login with provided credentials. Click on the Credentials in the left menu. This will take you to the credentials page. Scroll down to the Stores scoped to Jenkins and click on the System as shown in the image. Click on Global credentials (unrestricted) . Click on Add Credentials . This will take you to the New Credentials page. Select Kind as Secret text . Select Scope as Global (Jenkins, nodes, items, all child items etc) . Enter Secret as GitHub personal authentication token (PAT) which can be acquired from Github account settings. Enter a unique ID . Description can be left empty. But it is recommended to give a suitable but careful description by which administrator will be able to identify and use these credentials to set up github webhook. Select Create . This process will look something like this. Now credentials will be available in the credentials list and will be shown to you as well as administrator as shown in the image below. This will create an option in configurations for using these credentials in github webhook without changing or viewing them. Note the credentials ID (as shown in the image below) and email it to the same administrator email on which you received the credentials. It is important that administrator knows the credentials ID because he will use it in the job build configurations. Note: Please make sure to inform the administrator via email that you have added the credentials in jenkins. Also, send administrator the ID of credentials via email.","title":"Configurations inside Cloud-V"},{"location":"Software_Developer_Guide/#requirements-for-administrator","text":"After the above setup is complete from software developer's side, developer will need to provide the administrator with following information. Dependencies for running the project which can be packages which are needed to install in the RISC-V CI environment by administrator. Events for triggering the job build. URL of GitHub repository. Path and name of Jenkinsfile on the provided GitHub repository. Any additional information which should be given for successful execution of job builds.","title":"Requirements for administrator"},{"location":"Tooling/","text":"Tools on Cloud-V Using Environment Modules Users can use environment modules to load different versions of same program. For using environment modules the pattern is as follows: module load <PACKAGENAME/VERSION> For example if you want to load python version 3.9.2 compiled for x86, you will need to use following command: module load python/3.9.2 For packages compiled for RISC-V architecture host, you will need to append _riscv to package name. For example, for python 3.8.15 compiled for RISC-V, following command will be used. module load python_riscv/3.8.15 Following are the tools and libraries available in Cloud-V. Tools on x86_runner1 and qemuusermode_runner1 node Tools which are mentioned for x86 architecture are able to run on x86_runner2 . Tools which are mentioned for RISC-V architecture are able to run on qemuusermode_runner1 . The packages which are supported for QEMU User mode can be used by normal commands once they are loaded. Here PACKAGE_NAME is the package which you want to run on QEMU user mode. Operating System: Debian 11 (bullseye) QEMU User Mode Version: 7.1.0 Tool Versions Installed from Host Architecture Environment Modules Support RISC-V GNU Linux Toolchain 12.2.0 source x86 N/A Git 2.3.0.2 source x86 N/A OpenJDK 19.0.1 apt x86 N/A GCC 10.4.0, 12.2.0 apt x86 Yes Python3 3.8.15, 3.9.2 source x86 Yes Python3 3.8.15 source RISC-V Yes zlib 1.2.13 source RISC-V N/A OpenSSL 1.1.1r source RISC-V Yes Ruby (without IRB) 3.2.0dev source RISC-V Yes Go 1.18.8 apt x86 N/A rustc 1.65.0 source RISC-V,x86 N/A Flex 2.6.4 apt x86 N/A Flex 2.6.4 source RISC-V yes Ninja 1.10.1-1 apt x86 N/A Ninja 1.12.0.git source RISC-V Yes Bison 3.7.5 apt x86 N/A Bison 3.8.2, 2.3 source RISC-V Yes clang 16.0.0 source RISC-V Yes autoconf 2.69 apt x86 N/A gperf 2.2.4 apt x86 N/A spike 1.1.1-dev source x86 Yes Verilator 4.038 apt x86 N/A riscv-pk 1.0.0-91-g573c858 source RISC-V Yes Sail (riscv_sim_RV64, riscv_sim_RV32) 0.5 source x86 Yes cmake 3.18.4 apt x86 N/A make 4.3 apt x86 N/A Tools on riscv64_runner1 node This is compute instance with 64-bit RISC-V Linux and it has all the packages ONLY for RISC-V architecture Operating System: Ubuntu 22.04.1 (jammy) QEMU Linux Version: 7.1.90 Tool Version Installed from Git 2.34.1 apt OpenJDK 19.0.1 apt GCC 11.3.0 apt Python3 3.10.6 apt zlib 1.2.11 apt OpenSSL 3.0.2 apt Ruby 3.0.2p107 apt Go 1.18.8 apt rustc 1.61.0 apt Flex 2.6.4 apt Ninja 1.10.1 apt Bison 3.8.2 apt autoconf 2.71 apt gperf 3.1 apt make 4.3 apt cmake 3.22.1 apt Tools on hifive_unleashed node This compute instance is Sifive's HiFive Unleased board and it has available packages ONLY for RISC-V architecture. Operating System: Fedora 32 (Rawhide) Tool Version Installed from Git 2.23.0 dnf OpenJDK 11 dnf GCC 9.2.1 dnf Python3 3.8.1 dnf OpenSSL 1.1.1d dnf Ruby 2.5.1p57 dnf Go 1.12.2 dnf rustc 1.66.0 dnf Flex 2.6.4 dnf Ninja 1.9.0 dnf Bison 3.4.1 dnf autoconf 2.69 dnf make 4.2.1 dnf cmake 3.14.5 dnf Tools on starfive_visionfive2 node This compute instance is Starfive's VisionFive 2 board and it has available packages ONLY for RISC-V architecture. Operating System: Debian Unstable (Bookworm) Tool Version Installed from Git 2.36.1 apt OpenJDK 17.0.3 apt GCC 11.3.0 apt Python3 3.8.1 apt OpenSSL 1.1.1f apt Ruby 3.0.4p208 apt Go 1.18.3 apt rustc 1.59.0 apt Flex 2.6.4 apt Ninja 1.11.0 apt Bison 3.8.2 apt autoconf 2.71 apt gperf 3.1 apt cmake 3.23.2 apt make 4.3 apt","title":"Tools available in Cloud-V"},{"location":"Tooling/#tools-on-cloud-v","text":"","title":"Tools on Cloud-V"},{"location":"Tooling/#using-environment-modules","text":"Users can use environment modules to load different versions of same program. For using environment modules the pattern is as follows: module load <PACKAGENAME/VERSION> For example if you want to load python version 3.9.2 compiled for x86, you will need to use following command: module load python/3.9.2 For packages compiled for RISC-V architecture host, you will need to append _riscv to package name. For example, for python 3.8.15 compiled for RISC-V, following command will be used. module load python_riscv/3.8.15 Following are the tools and libraries available in Cloud-V.","title":"Using Environment Modules"},{"location":"Tooling/#tools-on-x86_runner1-and-qemuusermode_runner1-node","text":"Tools which are mentioned for x86 architecture are able to run on x86_runner2 . Tools which are mentioned for RISC-V architecture are able to run on qemuusermode_runner1 . The packages which are supported for QEMU User mode can be used by normal commands once they are loaded. Here PACKAGE_NAME is the package which you want to run on QEMU user mode. Operating System: Debian 11 (bullseye) QEMU User Mode Version: 7.1.0 Tool Versions Installed from Host Architecture Environment Modules Support RISC-V GNU Linux Toolchain 12.2.0 source x86 N/A Git 2.3.0.2 source x86 N/A OpenJDK 19.0.1 apt x86 N/A GCC 10.4.0, 12.2.0 apt x86 Yes Python3 3.8.15, 3.9.2 source x86 Yes Python3 3.8.15 source RISC-V Yes zlib 1.2.13 source RISC-V N/A OpenSSL 1.1.1r source RISC-V Yes Ruby (without IRB) 3.2.0dev source RISC-V Yes Go 1.18.8 apt x86 N/A rustc 1.65.0 source RISC-V,x86 N/A Flex 2.6.4 apt x86 N/A Flex 2.6.4 source RISC-V yes Ninja 1.10.1-1 apt x86 N/A Ninja 1.12.0.git source RISC-V Yes Bison 3.7.5 apt x86 N/A Bison 3.8.2, 2.3 source RISC-V Yes clang 16.0.0 source RISC-V Yes autoconf 2.69 apt x86 N/A gperf 2.2.4 apt x86 N/A spike 1.1.1-dev source x86 Yes Verilator 4.038 apt x86 N/A riscv-pk 1.0.0-91-g573c858 source RISC-V Yes Sail (riscv_sim_RV64, riscv_sim_RV32) 0.5 source x86 Yes cmake 3.18.4 apt x86 N/A make 4.3 apt x86 N/A","title":"Tools on x86_runner1 and qemuusermode_runner1 node"},{"location":"Tooling/#tools-on-riscv64_runner1-node","text":"This is compute instance with 64-bit RISC-V Linux and it has all the packages ONLY for RISC-V architecture Operating System: Ubuntu 22.04.1 (jammy) QEMU Linux Version: 7.1.90 Tool Version Installed from Git 2.34.1 apt OpenJDK 19.0.1 apt GCC 11.3.0 apt Python3 3.10.6 apt zlib 1.2.11 apt OpenSSL 3.0.2 apt Ruby 3.0.2p107 apt Go 1.18.8 apt rustc 1.61.0 apt Flex 2.6.4 apt Ninja 1.10.1 apt Bison 3.8.2 apt autoconf 2.71 apt gperf 3.1 apt make 4.3 apt cmake 3.22.1 apt","title":"Tools on riscv64_runner1 node"},{"location":"Tooling/#tools-on-hifive_unleashed-node","text":"This compute instance is Sifive's HiFive Unleased board and it has available packages ONLY for RISC-V architecture. Operating System: Fedora 32 (Rawhide) Tool Version Installed from Git 2.23.0 dnf OpenJDK 11 dnf GCC 9.2.1 dnf Python3 3.8.1 dnf OpenSSL 1.1.1d dnf Ruby 2.5.1p57 dnf Go 1.12.2 dnf rustc 1.66.0 dnf Flex 2.6.4 dnf Ninja 1.9.0 dnf Bison 3.4.1 dnf autoconf 2.69 dnf make 4.2.1 dnf cmake 3.14.5 dnf","title":"Tools on hifive_unleashed node"},{"location":"Tooling/#tools-on-starfive_visionfive2-node","text":"This compute instance is Starfive's VisionFive 2 board and it has available packages ONLY for RISC-V architecture. Operating System: Debian Unstable (Bookworm) Tool Version Installed from Git 2.36.1 apt OpenJDK 17.0.3 apt GCC 11.3.0 apt Python3 3.8.1 apt OpenSSL 1.1.1f apt Ruby 3.0.4p208 apt Go 1.18.3 apt rustc 1.59.0 apt Flex 2.6.4 apt Ninja 1.11.0 apt Bison 3.8.2 apt autoconf 2.71 apt gperf 3.1 apt cmake 3.23.2 apt make 4.3 apt","title":"Tools on starfive_visionfive2 node"},{"location":"jenkins_gitlab_integration/","text":"Integrating GitLab with Jenkins This documentation will cover how to create an integration between jenkins and GitLab. This will allow users to trigger jenkins job when a merge request or a push is detected in GitLab. Pre-requisites GitLab plugin Git plugin GitLab repository with owner's credentials Configuring Jenkins System First jenkins needs to be configured. Go to Dashboard > Manage Jenkins > Configure System Scroll down to Gitlab section Check Enable authentication for '/project' end-point Enter a Connection name . Enter Gitlab host URL as https://gitlab.com/ . In case there is a different domain name, then enter there instead of above url. In Credentials , click on Add then click on Jenkins . In Kind , select GitLab API token . In API token , enter the gitlab personal access token (this will be obtained below while configuring GitLab). Click on Advanced . Click on Test Connection . If everything goes right, it should print success . Configuring GitLab Click on profile avatar in the top right. Click on Edit profile . Click on Access Tokens . Create a new personal access token and copy it (this is the GitLab API token used in above section Configuring Jenkins System ). Go to repository settings. On left-side pane, select Webhooks . Enter GitLab webhook URL (this is explained below in next section). Enter Secret Token (this is explained in the below section). Check desirable trigger options. Click Add webhook . Configuring Jenkins Job Create a jenkins job. On job configuration page, scroll down to Source Code Management . Select Git . In Credentials , add the owner credentials of GitLab repository. This will be Username and Password . Select the appropriate branch (generally it is main ). Scroll down to Build Triggers . Check Build when a change is pushed to GitLab . There will also be a GitLab webhook URL . This is needed in GitLab. This URL will be called as Webhook URL . Click on Advanced in the same option, then scroll down and generate a secret token. This token is also needed. This token will be called as Secret Token . Scroll down to Post-build Actions and select Publish build status to GitLab . Click on Apply and Save . Now whenever there will be a push (or whatever build trigger option is set in jenkins and gitlab webhook), specified jenkins job will be triggered.","title":"GitLab Integration"},{"location":"jenkins_gitlab_integration/#integrating-gitlab-with-jenkins","text":"This documentation will cover how to create an integration between jenkins and GitLab. This will allow users to trigger jenkins job when a merge request or a push is detected in GitLab.","title":"Integrating GitLab with Jenkins"},{"location":"jenkins_gitlab_integration/#pre-requisites","text":"GitLab plugin Git plugin GitLab repository with owner's credentials","title":"Pre-requisites"},{"location":"jenkins_gitlab_integration/#configuring-jenkins-system","text":"First jenkins needs to be configured. Go to Dashboard > Manage Jenkins > Configure System Scroll down to Gitlab section Check Enable authentication for '/project' end-point Enter a Connection name . Enter Gitlab host URL as https://gitlab.com/ . In case there is a different domain name, then enter there instead of above url. In Credentials , click on Add then click on Jenkins . In Kind , select GitLab API token . In API token , enter the gitlab personal access token (this will be obtained below while configuring GitLab). Click on Advanced . Click on Test Connection . If everything goes right, it should print success .","title":"Configuring Jenkins System"},{"location":"jenkins_gitlab_integration/#configuring-gitlab","text":"Click on profile avatar in the top right. Click on Edit profile . Click on Access Tokens . Create a new personal access token and copy it (this is the GitLab API token used in above section Configuring Jenkins System ). Go to repository settings. On left-side pane, select Webhooks . Enter GitLab webhook URL (this is explained below in next section). Enter Secret Token (this is explained in the below section). Check desirable trigger options. Click Add webhook .","title":"Configuring GitLab"},{"location":"jenkins_gitlab_integration/#configuring-jenkins-job","text":"Create a jenkins job. On job configuration page, scroll down to Source Code Management . Select Git . In Credentials , add the owner credentials of GitLab repository. This will be Username and Password . Select the appropriate branch (generally it is main ). Scroll down to Build Triggers . Check Build when a change is pushed to GitLab . There will also be a GitLab webhook URL . This is needed in GitLab. This URL will be called as Webhook URL . Click on Advanced in the same option, then scroll down and generate a secret token. This token is also needed. This token will be called as Secret Token . Scroll down to Post-build Actions and select Publish build status to GitLab . Click on Apply and Save . Now whenever there will be a push (or whatever build trigger option is set in jenkins and gitlab webhook), specified jenkins job will be triggered.","title":"Configuring Jenkins Job"},{"location":"runner_specs/","text":"Specifications of compute instances in Cloud-V This document contains the specifications of the compute instances available for users to run builds in Cloud-V. The term \"Compute Instance\", can also be safely interchanged with the terms \"Build Executor\" and \"Runner\". Name String Architecture Cores Memory Compute Instance Type x86_runner1 (or) qemuusermode_runner1 x86_64 4 8GiB Hardware with application-level emulator x86_runner2 x86_64 1 512MiB Hardware dell5559 x86_64 4 8GiB Hardware rasp4-1 aarch64 4 4GiB Hardware riscv64_runner1 riscv64 2 2GiB QEMU System emulator sf1-1 riscv64 2 8GiB Hardware sf1-2 riscv64 2 8GiB Hardware sf1-3 riscv64 2 8GiB Hardware sf2-1 riscv64 4 8GiB Hardware sf2-2 riscv64 4 8GiB Hardware sf2-3 riscv64 4 8GiB Hardware sf2-4 riscv64 4 8GiB Hardware sf2-5 riscv64 4 8GiB Hardware unleashed1-1 riscv64 4 8GiB Hardware unleashed1-2 riscv64 4 8GiB Hardware Note: The qemuusermode_runner1 and x86_runner1 are one and the same runner. The purpose of creating two separate executors for same hardware is that x86_runner1 is supposed to be specifically for x86 architecture whereas qemuusermode_runner1 is specifically for the users who want to cross compile source code for riscv64 architecture and then use qemu-usermode to execute them. Nevertheless, the tooling available for x86_runner1 can also be used for qemuusermode_runner1","title":"Runners' Info"},{"location":"runner_specs/#specifications-of-compute-instances-in-cloud-v","text":"This document contains the specifications of the compute instances available for users to run builds in Cloud-V. The term \"Compute Instance\", can also be safely interchanged with the terms \"Build Executor\" and \"Runner\". Name String Architecture Cores Memory Compute Instance Type x86_runner1 (or) qemuusermode_runner1 x86_64 4 8GiB Hardware with application-level emulator x86_runner2 x86_64 1 512MiB Hardware dell5559 x86_64 4 8GiB Hardware rasp4-1 aarch64 4 4GiB Hardware riscv64_runner1 riscv64 2 2GiB QEMU System emulator sf1-1 riscv64 2 8GiB Hardware sf1-2 riscv64 2 8GiB Hardware sf1-3 riscv64 2 8GiB Hardware sf2-1 riscv64 4 8GiB Hardware sf2-2 riscv64 4 8GiB Hardware sf2-3 riscv64 4 8GiB Hardware sf2-4 riscv64 4 8GiB Hardware sf2-5 riscv64 4 8GiB Hardware unleashed1-1 riscv64 4 8GiB Hardware unleashed1-2 riscv64 4 8GiB Hardware Note: The qemuusermode_runner1 and x86_runner1 are one and the same runner. The purpose of creating two separate executors for same hardware is that x86_runner1 is supposed to be specifically for x86 architecture whereas qemuusermode_runner1 is specifically for the users who want to cross compile source code for riscv64 architecture and then use qemu-usermode to execute them. Nevertheless, the tooling available for x86_runner1 can also be used for qemuusermode_runner1","title":"Specifications of compute instances in Cloud-V"},{"location":"Cross_Compiling/Cross_compiling%20python3.8.15/","text":"Cross compiling python3.8.15 for riscv64 This document will include how to build python3.8.15 for riscv64 architecture while using build machine as x86_64. Building Python Get the python source code of python 3.8.15 in form of tarball from this link. Once a tarball is obtained, extract it and use following command in its root folder to configure it. # Here $PREFIX is the directory where the binaries are desired to be installed. ./configure --host=riscv64-unknown-linux-gnu --build=x86_64-linux-gnu --prefix=\"$PREFIX\" --disable-ipv6 ac_cv_file__dev_ptmx=no ac_cv_file__dev_ptc=no After the above command is executed, use following command to start the build. make -j$(nproc) Now to install binaries on the location where PREFIX, use following command. make install This will install binaries for python3.8.15 in the $PREFIX directory and it can be checked using qemu-riscv64 .","title":"Cross Compiling Python3.8.15"},{"location":"Cross_Compiling/Cross_compiling%20python3.8.15/#cross-compiling-python3815-for-riscv64","text":"This document will include how to build python3.8.15 for riscv64 architecture while using build machine as x86_64.","title":"Cross compiling python3.8.15 for riscv64"},{"location":"Cross_Compiling/Cross_compiling%20python3.8.15/#building-python","text":"Get the python source code of python 3.8.15 in form of tarball from this link. Once a tarball is obtained, extract it and use following command in its root folder to configure it. # Here $PREFIX is the directory where the binaries are desired to be installed. ./configure --host=riscv64-unknown-linux-gnu --build=x86_64-linux-gnu --prefix=\"$PREFIX\" --disable-ipv6 ac_cv_file__dev_ptmx=no ac_cv_file__dev_ptc=no After the above command is executed, use following command to start the build. make -j$(nproc) Now to install binaries on the location where PREFIX, use following command. make install This will install binaries for python3.8.15 in the $PREFIX directory and it can be checked using qemu-riscv64 .","title":"Building Python"},{"location":"Cross_Compiling/Cross_compiling_coremark/","text":"Cross-compiling Coremark Coremark is another benchmarking tool. Here coremark will be cross-compiled for riscv64-unknown-linux-gnu and will be run on qemu-riscv64 . The github source code commit at the time of build is eefc986ebd3452d6adde22eafaff3e5c859f29e4 and branch is main . Getting the source code Execute the following command to get the source code of coremark. git clone https://github.com/eembc/coremark.git Tweaking source files for riscv64-unknown-linux-gnu At the time of this documentation, linux is being used for this test. First of all core_portme.mak will be changed. Navigate to linux/ directory in source repository. Open core_portme.mak . Here a single line will be used to include core_portme.mak from posix directory. So, navigate to posix/ directory in source folder Open core_portme.mak in posix/ directory and do the following changes to variables here. Change CC?=cc to CC=riscv64-unknown-linux-gnu-gcc . Scroll down and change EXE=.exe to EXE= (it should be blank). Scroll down and change LD=gcc to LD=riscv64-unknown-linux-gnu-ld . As we are using qemu-riscv64 , so change RUN= to RUN=qemu-riscv64 -L \"$$RISCV_SYSROOT\" Save changes and exit this file. Now open core_portme.h and change #define USE_CLOCK 0 to #define USE_CLOCK 1 and save. Navigate to source directory of repository and execute following command make PORT_DIR=linux/ If everything went right, the output result will be stored in run1.log and run2.log and will be of the form as shown below. 2K validation run parameters for coremark. CoreMark Size : 666 Total ticks : 12368459 Total time (secs): 12.368459 Iterations/Sec : 8893.589735 Iterations : 110000 Compiler version : GCC12.2.0 Compiler flags : -O2 -DPERFORMANCE_RUN=1 -lrt Memory location : Please put data memory location here (e.g. code in flash, data on heap etc) seedcrc : 0x18f2 [0]crclist : 0xe3c1 [0]crcmatrix : 0x0747 [0]crcstate : 0x8d84 [0]crcfinal : 0x0956 Correct operation validated. See README.md for run and reporting rules.","title":"Cross-compiling Coremark"},{"location":"Cross_Compiling/Cross_compiling_coremark/#cross-compiling-coremark","text":"Coremark is another benchmarking tool. Here coremark will be cross-compiled for riscv64-unknown-linux-gnu and will be run on qemu-riscv64 . The github source code commit at the time of build is eefc986ebd3452d6adde22eafaff3e5c859f29e4 and branch is main .","title":"Cross-compiling Coremark"},{"location":"Cross_Compiling/Cross_compiling_coremark/#getting-the-source-code","text":"Execute the following command to get the source code of coremark. git clone https://github.com/eembc/coremark.git","title":"Getting the source code"},{"location":"Cross_Compiling/Cross_compiling_coremark/#tweaking-source-files-for-riscv64-unknown-linux-gnu","text":"At the time of this documentation, linux is being used for this test. First of all core_portme.mak will be changed. Navigate to linux/ directory in source repository. Open core_portme.mak . Here a single line will be used to include core_portme.mak from posix directory. So, navigate to posix/ directory in source folder Open core_portme.mak in posix/ directory and do the following changes to variables here. Change CC?=cc to CC=riscv64-unknown-linux-gnu-gcc . Scroll down and change EXE=.exe to EXE= (it should be blank). Scroll down and change LD=gcc to LD=riscv64-unknown-linux-gnu-ld . As we are using qemu-riscv64 , so change RUN= to RUN=qemu-riscv64 -L \"$$RISCV_SYSROOT\" Save changes and exit this file. Now open core_portme.h and change #define USE_CLOCK 0 to #define USE_CLOCK 1 and save. Navigate to source directory of repository and execute following command make PORT_DIR=linux/ If everything went right, the output result will be stored in run1.log and run2.log and will be of the form as shown below. 2K validation run parameters for coremark. CoreMark Size : 666 Total ticks : 12368459 Total time (secs): 12.368459 Iterations/Sec : 8893.589735 Iterations : 110000 Compiler version : GCC12.2.0 Compiler flags : -O2 -DPERFORMANCE_RUN=1 -lrt Memory location : Please put data memory location here (e.g. code in flash, data on heap etc) seedcrc : 0x18f2 [0]crclist : 0xe3c1 [0]crcmatrix : 0x0747 [0]crcstate : 0x8d84 [0]crcfinal : 0x0956 Correct operation validated. See README.md for run and reporting rules.","title":"Tweaking source files for riscv64-unknown-linux-gnu"},{"location":"Cross_Compiling/Cross_compiling_dhrystone/","text":"Cross-compiling dhrystone Dhrystone is a benchmarking tool. Here dhrystone will be compiled from source and run on qemu-riscv64 . Dhrystone is comparable to VAX 11/780 in a way that VAX 11/780 achieves 1757 dhrystones per second which is also referred to as 1 MIPS of VAX11/780. So number of dhrystones per seconds are obtained and then divided by 1757 to get MIPS. See this link for more details. Cross-compiling for riscv64-unknown-linux-gnu Get the source code of dhrystone using the command below git clone https://github.com/sifive/benchmark-dhrystone.git Navigate to root directory of repository and compile program with riscv64-unknown-linux-gnu-gcc instead of native gcc cd benchmark-dhrystone make CC=riscv64-unknown-linux-gnu-gcc Execute following command to execute dhrystone binary qemu-riscv64 -L $RISCV_SYSROOT ./dhrystone Note: You may want to tweak Makefile and dhry_1.c a little bit to get the correct results.","title":"Cross Compiling Drhystone"},{"location":"Cross_Compiling/Cross_compiling_dhrystone/#cross-compiling-dhrystone","text":"Dhrystone is a benchmarking tool. Here dhrystone will be compiled from source and run on qemu-riscv64 . Dhrystone is comparable to VAX 11/780 in a way that VAX 11/780 achieves 1757 dhrystones per second which is also referred to as 1 MIPS of VAX11/780. So number of dhrystones per seconds are obtained and then divided by 1757 to get MIPS. See this link for more details.","title":"Cross-compiling dhrystone"},{"location":"Cross_Compiling/Cross_compiling_dhrystone/#cross-compiling-for-riscv64-unknown-linux-gnu","text":"Get the source code of dhrystone using the command below git clone https://github.com/sifive/benchmark-dhrystone.git Navigate to root directory of repository and compile program with riscv64-unknown-linux-gnu-gcc instead of native gcc cd benchmark-dhrystone make CC=riscv64-unknown-linux-gnu-gcc Execute following command to execute dhrystone binary qemu-riscv64 -L $RISCV_SYSROOT ./dhrystone Note: You may want to tweak Makefile and dhry_1.c a little bit to get the correct results.","title":"Cross-compiling for riscv64-unknown-linux-gnu"},{"location":"Cross_Compiling/Cross_compiling_go/","text":"Cross compiling Go Go currenlty has support for riscv64 architecture. This document will cover how to compile go on x86 for riscv64 architecture. Note: Right now, go can be cross-compiled on x86 but it cannot be executed on x86 with qemu-riscv64 because it needs to execute goroot/pkg/tool/compile and qemu-riscv64 can only execute one binary at a time. Pre Requisites On ubuntu, following pre-requisites should be installed. Snap qemu-riscv64 (linux-user) Go source code is written in go. That means a go toolchain is needed to compile the source code (see link ). As this document cross-compiles the code, first of all install a go language on build machine. Use following command on ubuntu to install a go language compiler. sudo snap install go --classic After this, get the source code of go from following command. git clone https://go.googlesource.com/go goroot Now set the environment variable as follows. export GOROOT_BOOTSTRAP=/snap export GOARCH=riscv64 export GOOS=linux Navigate to goroot/src and execute following command. ./all.bash After this, an executable file will be located in folder goroot/bin/linux_riscv64 .","title":"Cross Compiling go"},{"location":"Cross_Compiling/Cross_compiling_go/#cross-compiling-go","text":"Go currenlty has support for riscv64 architecture. This document will cover how to compile go on x86 for riscv64 architecture. Note: Right now, go can be cross-compiled on x86 but it cannot be executed on x86 with qemu-riscv64 because it needs to execute goroot/pkg/tool/compile and qemu-riscv64 can only execute one binary at a time.","title":"Cross compiling Go"},{"location":"Cross_Compiling/Cross_compiling_go/#pre-requisites","text":"On ubuntu, following pre-requisites should be installed. Snap qemu-riscv64 (linux-user) Go source code is written in go. That means a go toolchain is needed to compile the source code (see link ). As this document cross-compiles the code, first of all install a go language on build machine. Use following command on ubuntu to install a go language compiler. sudo snap install go --classic After this, get the source code of go from following command. git clone https://go.googlesource.com/go goroot Now set the environment variable as follows. export GOROOT_BOOTSTRAP=/snap export GOARCH=riscv64 export GOOS=linux Navigate to goroot/src and execute following command. ./all.bash After this, an executable file will be located in folder goroot/bin/linux_riscv64 .","title":"Pre Requisites"},{"location":"Cross_Compiling/Cross_compiling_jdk/","text":"Cross-compiling JDK for riscv64-unknown-linux-gnu JDK is abbreviation of 'Java Development Kit'. It is used for compiling and executing java-based programs and applications. All the information regarding building jdk and relevant dependencies are given at https://github.com/openjdk/jdk/blob/master/doc/building.md Make sure to have riscv64-unknown-linux-gnu toolchain installed on machine. Getting source code The source code of jdk can be obtained using command below git clone https://github.com/openjdk/jdk.git Building the source code for First of all configure the source code using the command below bash configure --host=riscv64-unknown-linux-gnu --build=x86_64-linux-gnu --target=riscv64-unknown-linux-gnu --prefix=/home/ali/custom_installed/RISCV/jdk/967a28c3d85fdde6d5eb48aa0edd8f7597772469 --with-cups=/home/ali/custom_installed/cups --with-fontconfig=/home/ali/custom_installed/fontconfig/e291fda7d42e5d64379555097a066d9c2c4efce3 --x-includes=/usr/include --x-lib=/usr/lib","title":"Cross-compiling JDK for `riscv64-unknown-linux-gnu`"},{"location":"Cross_Compiling/Cross_compiling_jdk/#cross-compiling-jdk-for-riscv64-unknown-linux-gnu","text":"JDK is abbreviation of 'Java Development Kit'. It is used for compiling and executing java-based programs and applications. All the information regarding building jdk and relevant dependencies are given at https://github.com/openjdk/jdk/blob/master/doc/building.md Make sure to have riscv64-unknown-linux-gnu toolchain installed on machine.","title":"Cross-compiling JDK for riscv64-unknown-linux-gnu"},{"location":"Cross_Compiling/Cross_compiling_jdk/#getting-source-code","text":"The source code of jdk can be obtained using command below git clone https://github.com/openjdk/jdk.git","title":"Getting source code"},{"location":"Cross_Compiling/Cross_compiling_jdk/#building-the-source-code-for","text":"First of all configure the source code using the command below bash configure --host=riscv64-unknown-linux-gnu --build=x86_64-linux-gnu --target=riscv64-unknown-linux-gnu --prefix=/home/ali/custom_installed/RISCV/jdk/967a28c3d85fdde6d5eb48aa0edd8f7597772469 --with-cups=/home/ali/custom_installed/cups --with-fontconfig=/home/ali/custom_installed/fontconfig/e291fda7d42e5d64379555097a066d9c2c4efce3 --x-includes=/usr/include --x-lib=/usr/lib","title":"Building the source code for"},{"location":"Cross_Compiling/Cross_compiling_ninja-build/","text":"Cross-compiling ninja-build for RISC-V Ninja is a small build system with a focus on speed. It differs from other build systems in two major respects: it is designed to have its input files generated by a higher-level build system, and it is designed to run builds as fast as possible. This document will cover how to compile ninja to work on 64-bit RISC-V architecture. Getting source code Use following command to get source code of ninja-build and navigate to source directory. git clone git://github.com/ninja-build/ninja.git cd ninja git checkout release Create following cmake file inside the root directory of ninja-build repository. # the name of the target operating system set(CMAKE_SYSTEM_NAME Linux) # which compilers to use for C and C++ set(CMAKE_C_COMPILER riscv64-unknown-linux-gnu-gcc) set(CMAKE_CXX_COMPILER riscv64-unknown-linux-gnu-g++) # where is the target environment located set(CMAKE_FIND_ROOT_PATH /softwares/RISCV/riscv64-unknown-linux-gnu/50c1b734e889e5cbb88bcc7f14975ea9a1d0b936/sysroot ) # adjust the default behavior of the FIND_XXX() commands: # search programs in the host environment set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER) # search headers and libraries in the target environment set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY) set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)","title":"Cross-compiling ninja-build for RISC-V"},{"location":"Cross_Compiling/Cross_compiling_ninja-build/#cross-compiling-ninja-build-for-risc-v","text":"Ninja is a small build system with a focus on speed. It differs from other build systems in two major respects: it is designed to have its input files generated by a higher-level build system, and it is designed to run builds as fast as possible. This document will cover how to compile ninja to work on 64-bit RISC-V architecture.","title":"Cross-compiling ninja-build for RISC-V"},{"location":"Cross_Compiling/Cross_compiling_ninja-build/#getting-source-code","text":"Use following command to get source code of ninja-build and navigate to source directory. git clone git://github.com/ninja-build/ninja.git cd ninja git checkout release Create following cmake file inside the root directory of ninja-build repository. # the name of the target operating system set(CMAKE_SYSTEM_NAME Linux) # which compilers to use for C and C++ set(CMAKE_C_COMPILER riscv64-unknown-linux-gnu-gcc) set(CMAKE_CXX_COMPILER riscv64-unknown-linux-gnu-g++) # where is the target environment located set(CMAKE_FIND_ROOT_PATH /softwares/RISCV/riscv64-unknown-linux-gnu/50c1b734e889e5cbb88bcc7f14975ea9a1d0b936/sysroot ) # adjust the default behavior of the FIND_XXX() commands: # search programs in the host environment set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER) # search headers and libraries in the target environment set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY) set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)","title":"Getting source code"},{"location":"Cross_Compiling/Cross_compiling_openssl/","text":"Cross-compiling openssl What is openssl Openssl is a software library which is used inside many high level languages (e.g. Python, Ruby etc.) and also in linux itself. It is used for security and other cryptography applications. Building openssl v1.0.1 for riscv64 architecture Following are the steps used to build openssl for riscv64 architecture. Get the source code of openssl and navigate inside the cloned repository using the commands below git clone https://github.com/openssl/openssl.git cd openssl Configure openssl for building. In openssl there are some os/compiler choices which one can use to build for his architecture. But in our case there is no support for building with riscv64. As it is written in C language, so it can be compiled whether or not the support is given. Use the following command to generate a Makefile for linux-generic64 ./Configure linux-generic64 --prefix=$PREFIX # Prefix is the directory where you want binaries to be installed at the end After the above command is successfully completed, run the following command to build openssl using riscv64-unknown-linux-gnu-gcc compiler instead of native gcc compiler. make -j$(nproc) CC=riscv64-unknown-linux-gnu-gcc Install the binaries in the specified --prefix using the command below make -j$(nproc) install CC=riscv64-unknown-linux-gnu-gcc The installed binary can be tested on qemu-riscv64 using the command below: qemu-riscv64 -L $RISCV_SYSROOT ./openssl Here $RISCV_SYSROOT is the sysroot/ folder located inside the riscv gnu toolchain installed directory. The above mentioned command will start the openssl console if everything went right. Note: Do not change the directory of openssl or rename it, as it some files inside it are inferred with absolute paths, changing the directory or renaming it will cause other packages to not configure openssl for them when cross-compiling. Building openssl v1.1.1r for riscv64 architecture In openssl v1.1.1r, there is a support for linux64-riscv64 . Following is the procedure for cross-compilation. Checkout the v1.1.1r of openssl by executing following command in the repository directory. git checkout OpenSSL_1_1_1r Execute following command to configure for riscv64 architecture and generate a Makefile . ./Configure linux64-riscv64 --prefix=$PREFIX # Replace $PREFIX with where you want to install binaries Execute following command to cross-compile for riscv64-unknown-linux-gnu . make CROSS_COMPILE=riscv64-unknown-linux-gnu- Then install binaries at $PREFIX with following command. make install Solving post-installation errors On some operating systems, the installed binaries may not run properly and will give following error. ./openssl: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory This means that shared libraries cannot be found in the path where the system is looking for them. This can be solved by setting LD_LIBRARY_PATH variable as follows. export LD_LIBRARY_PATH=$PREFIX/lib:$LD_LIBRARY_PATH It will be a good practice to include the above in the bashrc for debian users.","title":"Cross Compiling Openssl"},{"location":"Cross_Compiling/Cross_compiling_openssl/#cross-compiling-openssl","text":"","title":"Cross-compiling openssl"},{"location":"Cross_Compiling/Cross_compiling_openssl/#what-is-openssl","text":"Openssl is a software library which is used inside many high level languages (e.g. Python, Ruby etc.) and also in linux itself. It is used for security and other cryptography applications.","title":"What is openssl"},{"location":"Cross_Compiling/Cross_compiling_openssl/#building-openssl-v101-for-riscv64-architecture","text":"Following are the steps used to build openssl for riscv64 architecture. Get the source code of openssl and navigate inside the cloned repository using the commands below git clone https://github.com/openssl/openssl.git cd openssl Configure openssl for building. In openssl there are some os/compiler choices which one can use to build for his architecture. But in our case there is no support for building with riscv64. As it is written in C language, so it can be compiled whether or not the support is given. Use the following command to generate a Makefile for linux-generic64 ./Configure linux-generic64 --prefix=$PREFIX # Prefix is the directory where you want binaries to be installed at the end After the above command is successfully completed, run the following command to build openssl using riscv64-unknown-linux-gnu-gcc compiler instead of native gcc compiler. make -j$(nproc) CC=riscv64-unknown-linux-gnu-gcc Install the binaries in the specified --prefix using the command below make -j$(nproc) install CC=riscv64-unknown-linux-gnu-gcc The installed binary can be tested on qemu-riscv64 using the command below: qemu-riscv64 -L $RISCV_SYSROOT ./openssl Here $RISCV_SYSROOT is the sysroot/ folder located inside the riscv gnu toolchain installed directory. The above mentioned command will start the openssl console if everything went right. Note: Do not change the directory of openssl or rename it, as it some files inside it are inferred with absolute paths, changing the directory or renaming it will cause other packages to not configure openssl for them when cross-compiling.","title":"Building openssl v1.0.1 for riscv64 architecture"},{"location":"Cross_Compiling/Cross_compiling_openssl/#building-openssl-v111r-for-riscv64-architecture","text":"In openssl v1.1.1r, there is a support for linux64-riscv64 . Following is the procedure for cross-compilation. Checkout the v1.1.1r of openssl by executing following command in the repository directory. git checkout OpenSSL_1_1_1r Execute following command to configure for riscv64 architecture and generate a Makefile . ./Configure linux64-riscv64 --prefix=$PREFIX # Replace $PREFIX with where you want to install binaries Execute following command to cross-compile for riscv64-unknown-linux-gnu . make CROSS_COMPILE=riscv64-unknown-linux-gnu- Then install binaries at $PREFIX with following command. make install","title":"Building openssl v1.1.1r for riscv64 architecture"},{"location":"Cross_Compiling/Cross_compiling_openssl/#solving-post-installation-errors","text":"On some operating systems, the installed binaries may not run properly and will give following error. ./openssl: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory This means that shared libraries cannot be found in the path where the system is looking for them. This can be solved by setting LD_LIBRARY_PATH variable as follows. export LD_LIBRARY_PATH=$PREFIX/lib:$LD_LIBRARY_PATH It will be a good practice to include the above in the bashrc for debian users.","title":"Solving post-installation errors"},{"location":"Cross_Compiling/Cross_compiling_ruby/","text":"Cross Compilation of Ruby System Specifications Build Architecture: x86_64-linux-gnu Host Architecture: riscv64-unknown-linux-gnu Operating System for Installation Procedure: Ubuntu 20.04 Pre-requisites Pre-requisites for installing ruby from source can be installed using the following command sudo apt-get -y install libc6-dev libssl-dev libmysql++-dev libsqlite3-dev make build-essential libssl-dev libreadline6-dev zlib1g-dev libyaml-dev Other than this, ruby itself is needed for building ruby from source. sudo apt install ruby There is another thing which needs to be taken care of before building ruby from source. If ruby is installed on system itself using apt , then cross compiling ruby will end up in an error as shown in the image below. This error is seen in ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu] . To tackle this issue, one workaround is to install build ruby for native system, then delete ruby which was installed through apt . This procedure will be added in the Build section. Getting source code Source code of ruby can be obtained from github repository using the command below: git clone https://github.com/ruby/ruby.git Build Installing ruby for native architecture Before cross-compiling, one must install ruby from source on the native machine which will solve the error described in Pre-requisites section above. ( THIS STEP IS STRONGLY RECOMMENDED ! )In the source directory, create a folder with any name in which Makefile will be generated otherwise there will be a lot of files made in the source directory (possibly create copy of repo directory). In the source directory of ruby run following command to generate configure file. ./autogen.sh After this, run the following configure command to generate Makefile . ../configure --prefix=$PREFIX #$PREFIX is where you want to install binary files at the end, so replace it. After the above command is completed, run following command to start the build make -j$(nproc) #-j$(nproc) uses parallelism for make After the above command is complete, run following command to install the binaries on the specified path mentioned in --prefix above make install Now ruby should be available in the $PREFIX path (also in the .bashrc ). Add $PREFIX path to $PATH variable and uninstall the the ruby installed using apt otherwise, the source will keep using that one for building and the error will persist. sudo apt purge ruby Cross-Compiling Ruby for riscv64-unknown-linux-gnu After the ruby installed using apt is uninstalled from the system, clean the working directory with following command. make clean After cleaning the working directory, generate the Makefile again for cross-compiling ruby for riscv64-unknown-linux-gnu target and host using the command below ../../configure --prefix=$PREFIX --build=x86_64-linux-gnu --host=riscv64-unknown-linux-gnu --target=riscv64-unknown-linux-gnu After the above command is successful, start build with following command make -j(nproc) Install the binaries in path mentioned with --prefix above with following command make install After this process, ruby will be installed inside $PREFIX/ directory. Note: Currently, this process (as checked on version 3.1.2) installs ruby without extensions shown in the following image","title":"Cross Compiling Ruby"},{"location":"Cross_Compiling/Cross_compiling_ruby/#cross-compilation-of-ruby","text":"","title":"Cross Compilation of Ruby"},{"location":"Cross_Compiling/Cross_compiling_ruby/#system-specifications","text":"Build Architecture: x86_64-linux-gnu Host Architecture: riscv64-unknown-linux-gnu Operating System for Installation Procedure: Ubuntu 20.04","title":"System Specifications"},{"location":"Cross_Compiling/Cross_compiling_ruby/#pre-requisites","text":"Pre-requisites for installing ruby from source can be installed using the following command sudo apt-get -y install libc6-dev libssl-dev libmysql++-dev libsqlite3-dev make build-essential libssl-dev libreadline6-dev zlib1g-dev libyaml-dev Other than this, ruby itself is needed for building ruby from source. sudo apt install ruby There is another thing which needs to be taken care of before building ruby from source. If ruby is installed on system itself using apt , then cross compiling ruby will end up in an error as shown in the image below. This error is seen in ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu] . To tackle this issue, one workaround is to install build ruby for native system, then delete ruby which was installed through apt . This procedure will be added in the Build section.","title":"Pre-requisites"},{"location":"Cross_Compiling/Cross_compiling_ruby/#getting-source-code","text":"Source code of ruby can be obtained from github repository using the command below: git clone https://github.com/ruby/ruby.git","title":"Getting source code"},{"location":"Cross_Compiling/Cross_compiling_ruby/#build","text":"","title":"Build"},{"location":"Cross_Compiling/Cross_compiling_ruby/#installing-ruby-for-native-architecture","text":"Before cross-compiling, one must install ruby from source on the native machine which will solve the error described in Pre-requisites section above. ( THIS STEP IS STRONGLY RECOMMENDED ! )In the source directory, create a folder with any name in which Makefile will be generated otherwise there will be a lot of files made in the source directory (possibly create copy of repo directory). In the source directory of ruby run following command to generate configure file. ./autogen.sh After this, run the following configure command to generate Makefile . ../configure --prefix=$PREFIX #$PREFIX is where you want to install binary files at the end, so replace it. After the above command is completed, run following command to start the build make -j$(nproc) #-j$(nproc) uses parallelism for make After the above command is complete, run following command to install the binaries on the specified path mentioned in --prefix above make install Now ruby should be available in the $PREFIX path (also in the .bashrc ). Add $PREFIX path to $PATH variable and uninstall the the ruby installed using apt otherwise, the source will keep using that one for building and the error will persist. sudo apt purge ruby","title":"Installing ruby for native architecture"},{"location":"Cross_Compiling/Cross_compiling_ruby/#cross-compiling-ruby-for-riscv64-unknown-linux-gnu","text":"After the ruby installed using apt is uninstalled from the system, clean the working directory with following command. make clean After cleaning the working directory, generate the Makefile again for cross-compiling ruby for riscv64-unknown-linux-gnu target and host using the command below ../../configure --prefix=$PREFIX --build=x86_64-linux-gnu --host=riscv64-unknown-linux-gnu --target=riscv64-unknown-linux-gnu After the above command is successful, start build with following command make -j(nproc) Install the binaries in path mentioned with --prefix above with following command make install After this process, ruby will be installed inside $PREFIX/ directory. Note: Currently, this process (as checked on version 3.1.2) installs ruby without extensions shown in the following image","title":"Cross-Compiling Ruby for riscv64-unknown-linux-gnu"},{"location":"Cross_Compiling/Cross_compiling_rust/","text":"Cross-compiling rust Rust is a programming language just like C but it focuses on safety of programs. This document describes how one can build rust for x86_64 and then add support to compile code for riscv64 architecture. The executable for RISC-V architecture will be able to run on qemu-riscv64 . Note: Make sure riscv64-unknown-linux-gnu toolchain is installed on the machine. Getting source code Here the code will be taken from rustup GitHub repository. This is because instead of installing cargo , rustup and rustc , just compiling rustup will compile them along with itself. Get the source code using the command below: git clone https://github.com/rust-lang/rustup.git Before starting installation process, if you want to install rust in a specific location, then set CARGO_HOME and RUSTUP_HOME variable in the directory where you want to install rustup. After that, considering you are in the repository directory, start the installation process using the command below: sh rustup-init.sh -y After execution above command, follow the prompts as desired and complete the installation process. Now add riscv64 library support in rust using the command below: rustup target add riscv64gc-unknown-linux-gnu Once this is complete, go to the desired location where a new project is to be created and use following command to create a project's directory structure. cargo new project_name # Use a meaningful project name A directory with name project_name will be created as soon as the above command is executed successfully. This project will contain a main.rs which initially contains a Hello World program. Navigate to the project_name directory and create a folder with name .cargo , this will include a config.toml file inside it, which will tell it cargo during build that what is the target for which the compilation is to be done. The contents of the project_name/.cargo/config.toml will be as follows: [build] target = \"riscv64gc-unknown-linux-gnu\" [target.riscv64gc-unknown-linux-gnu] linker = \"riscv64-unknown-linux-gnu-gcc\" Now the project will be ready to build. Get back to the project_name/ directory and use following command to build the main.rs file: cargo build The output of the above command should as follows: Compiling myproject v0.1.0 (project_name) Finished dev [unoptimized + debuginfo] target(s) in 0.27s After the above command, the executable with the name project_name will be available at following location: project_name/target/riscv64gc-unknown-linux-gnu/debug Now the produced executable can be executed using qemu usermode. Use the following command to execute binary: qemu-riscv64 -L $RISCV_SYSROOT ./project_name","title":"Cross Compiling Rust"},{"location":"Cross_Compiling/Cross_compiling_rust/#cross-compiling-rust","text":"Rust is a programming language just like C but it focuses on safety of programs. This document describes how one can build rust for x86_64 and then add support to compile code for riscv64 architecture. The executable for RISC-V architecture will be able to run on qemu-riscv64 . Note: Make sure riscv64-unknown-linux-gnu toolchain is installed on the machine.","title":"Cross-compiling rust"},{"location":"Cross_Compiling/Cross_compiling_rust/#getting-source-code","text":"Here the code will be taken from rustup GitHub repository. This is because instead of installing cargo , rustup and rustc , just compiling rustup will compile them along with itself. Get the source code using the command below: git clone https://github.com/rust-lang/rustup.git Before starting installation process, if you want to install rust in a specific location, then set CARGO_HOME and RUSTUP_HOME variable in the directory where you want to install rustup. After that, considering you are in the repository directory, start the installation process using the command below: sh rustup-init.sh -y After execution above command, follow the prompts as desired and complete the installation process. Now add riscv64 library support in rust using the command below: rustup target add riscv64gc-unknown-linux-gnu Once this is complete, go to the desired location where a new project is to be created and use following command to create a project's directory structure. cargo new project_name # Use a meaningful project name A directory with name project_name will be created as soon as the above command is executed successfully. This project will contain a main.rs which initially contains a Hello World program. Navigate to the project_name directory and create a folder with name .cargo , this will include a config.toml file inside it, which will tell it cargo during build that what is the target for which the compilation is to be done. The contents of the project_name/.cargo/config.toml will be as follows: [build] target = \"riscv64gc-unknown-linux-gnu\" [target.riscv64gc-unknown-linux-gnu] linker = \"riscv64-unknown-linux-gnu-gcc\" Now the project will be ready to build. Get back to the project_name/ directory and use following command to build the main.rs file: cargo build The output of the above command should as follows: Compiling myproject v0.1.0 (project_name) Finished dev [unoptimized + debuginfo] target(s) in 0.27s After the above command, the executable with the name project_name will be available at following location: project_name/target/riscv64gc-unknown-linux-gnu/debug Now the produced executable can be executed using qemu usermode. Use the following command to execute binary: qemu-riscv64 -L $RISCV_SYSROOT ./project_name","title":"Getting source code"},{"location":"Cross_Compiling/Overview/","text":"Cross Compilation Need of Cross Compilation Lets say you have a computer A having processor with architecture a and another computer B having processor with architecture b . Assume computer A has all the necessary tools and softwares whereas computer B does not have any software, tools, compilers and also the dependencies needed to install these tools and softwares. In this scenario, you cannot download the software setups (say tarballs) directly on computer B and have them installed/compiled because they will not be able to get compiled by computer B and will be completely useless. Basic concept The basic workflow in such a condition will be as follows: Install a compiler on computer A such that it runs on computer A and compiles code for architecture a . Using the above installed compiler, install a compiler on computer A such that it runs on computer A but compiles code for architecture b . Such a compiler is called cross compiler. One example of such a cross-compiler is RISC-V GNU TOOLCHAIN . Using the above compiled cross compiler, compile all the programs and also the compiler itself for architecture b . Port all the compiled binaries to the computer B . Such a process is beneficial if you have created a custom architecture and there is no support available for it. Throughout this documentation, the cross compiler used will be RISCV GNU Toolchain mentioned with riscv64-unknown-linux-gcc running on x86_64 and compiling code for riscv64 architecture whereas the native compiler will be gcc running on x86_64 and compiling code for x86_64 unless otherwise specified.","title":"Overview"},{"location":"Cross_Compiling/Overview/#cross-compilation","text":"","title":"Cross Compilation"},{"location":"Cross_Compiling/Overview/#need-of-cross-compilation","text":"Lets say you have a computer A having processor with architecture a and another computer B having processor with architecture b . Assume computer A has all the necessary tools and softwares whereas computer B does not have any software, tools, compilers and also the dependencies needed to install these tools and softwares. In this scenario, you cannot download the software setups (say tarballs) directly on computer B and have them installed/compiled because they will not be able to get compiled by computer B and will be completely useless.","title":"Need of Cross Compilation"},{"location":"Cross_Compiling/Overview/#basic-concept","text":"The basic workflow in such a condition will be as follows: Install a compiler on computer A such that it runs on computer A and compiles code for architecture a . Using the above installed compiler, install a compiler on computer A such that it runs on computer A but compiles code for architecture b . Such a compiler is called cross compiler. One example of such a cross-compiler is RISC-V GNU TOOLCHAIN . Using the above compiled cross compiler, compile all the programs and also the compiler itself for architecture b . Port all the compiled binaries to the computer B . Such a process is beneficial if you have created a custom architecture and there is no support available for it. Throughout this documentation, the cross compiler used will be RISCV GNU Toolchain mentioned with riscv64-unknown-linux-gcc running on x86_64 and compiling code for riscv64 architecture whereas the native compiler will be gcc running on x86_64 and compiling code for x86_64 unless otherwise specified.","title":"Basic concept"},{"location":"Usage_Monitoring/Integrating_prometheus_grafana/","text":"Integrating Prometheus with Grafana Before starting to integrate Prometheus with Grafana make sure they are set up properly. See this document for setting up Prometheus and Grafana as standalone tools. Configuration in Prometheus Make sure all the node_exporter are running properly and the compute instances are discoverable by prometheus. Use following command for checking if the instances are accessible: telnet COMPUTE_INSTANCE_IP COMPUTE_INSTANCE_PORT If you get following response, then it means there is something wrong with firewall of compute instances as they are not accessible. Name or service not known Configuration in Grafana Enter the grafana IP in browser and login with credentials. Use following steps to integrate Grafana with Prometheus and creating dashbaords in Grafana Go to Grafana settings Go to Data sources tab Click on Add data source In HTTP section, add IP of machine on which Prometheus is running along with the port on which Prometheus is hosted (it is recommended to host Prometheus on the machine where Grafana is hosted, in that case, Prometheus will be accessed using LAN IP). In Type and version section, select Prometheus from drop down menu and choose a version of Prometheus in the next field. Click on Save and test If everything goes right, then it will say Data source is working . Creating a dashboard in Grafana For creating a dashboard, click on Dashboards Click on New and then New Dashboard Then add a panel inside the dashbaord If you know the mathemtical expressions (which are easier and more verbose) then select Code while creating the panels instead of Builder . Note: Be sure to save the dashbaord because otherwise, it will not make changes on its own and dashboard will be lost.","title":"Integrating Prometheus with Grafana"},{"location":"Usage_Monitoring/Integrating_prometheus_grafana/#integrating-prometheus-with-grafana","text":"Before starting to integrate Prometheus with Grafana make sure they are set up properly. See this document for setting up Prometheus and Grafana as standalone tools.","title":"Integrating Prometheus with Grafana"},{"location":"Usage_Monitoring/Integrating_prometheus_grafana/#configuration-in-prometheus","text":"Make sure all the node_exporter are running properly and the compute instances are discoverable by prometheus. Use following command for checking if the instances are accessible: telnet COMPUTE_INSTANCE_IP COMPUTE_INSTANCE_PORT If you get following response, then it means there is something wrong with firewall of compute instances as they are not accessible. Name or service not known","title":"Configuration in Prometheus"},{"location":"Usage_Monitoring/Integrating_prometheus_grafana/#configuration-in-grafana","text":"Enter the grafana IP in browser and login with credentials. Use following steps to integrate Grafana with Prometheus and creating dashbaords in Grafana Go to Grafana settings Go to Data sources tab Click on Add data source In HTTP section, add IP of machine on which Prometheus is running along with the port on which Prometheus is hosted (it is recommended to host Prometheus on the machine where Grafana is hosted, in that case, Prometheus will be accessed using LAN IP). In Type and version section, select Prometheus from drop down menu and choose a version of Prometheus in the next field. Click on Save and test If everything goes right, then it will say Data source is working .","title":"Configuration in Grafana"},{"location":"Usage_Monitoring/Integrating_prometheus_grafana/#creating-a-dashboard-in-grafana","text":"For creating a dashboard, click on Dashboards Click on New and then New Dashboard Then add a panel inside the dashbaord If you know the mathemtical expressions (which are easier and more verbose) then select Code while creating the panels instead of Builder . Note: Be sure to save the dashbaord because otherwise, it will not make changes on its own and dashboard will be lost.","title":"Creating a dashboard in Grafana"},{"location":"Usage_Monitoring/Prometheus_Grafana/","text":"Setting up Promtheus and Grafana What are Prometheus and Grafana Prometheus is a tool for monitoring usage of memory, CPU etc. It takes queries as mathematical expressions (like SQL) and returns the interactive graphical usage stats. It collects data using node_exporter , which is used to get raw data from the compute instances Grafana is used for creating dashboards in which there can be different panels containing the graphical statistics from Prometheus. Grafana dashboards are more interactive and user-friendly than Prometheus. Setting up Node Exporters Node exporters are needed for prometheus to get data from the compute instances. Download pre-compiled tarball of node_exporters from this link and place the tarballs on compute instances. Once node_exporter tarball is downloaded, extract it using following command: tar -xvf node_exporter-x.x.x.linux-amd64.tar.gz Run node_exporter on compute instances using command below (which will run node_exporter on port 9100 by default): ./node_exporter Follow this procedure on every compute instance which is desired to be monitored using Prometheus. Note: Make sure that compute instances can be accessed in the machine in which prometheus is installed. Configuring Prometheus Use this link to get pre-compiled tarball of Prometheus. Once Prometheus is downloaded, extract it using following command: tar -xvf prometheus-x.xx.x.linux-amd.tar.gz Now either configure prometheus.yml file or create another yml file which will include the addresses of node_exporters. Following is an example template for yml file: global: scrape_interval: 15s scrape_configs: - job_name: node static_configs: - targets: ['node_exporter_ip1:node_exporter_port1'] - targets: ['node_exporter_ip2:node_exporter_port2'] Running Prometheus Once prometheus is configured properly, use following command to run prometheus. ./prometheus Note: By default Prometheus looks for prometheus.yml , if you want to use some other file for configuration, you will need to specify explicitly with --config.file option. Running Grafana Once Prometheus is up and running, Grafana can be used to create dashboards with graphical interface in various panels inside dashboards. Use this to get pre-compiled tarball of Grafana After Grafana is ready to be run, use following command to run Grafana: ./grafana-server #By default it will run on port 3000 The default username and password of Grafana will be admin . Once Grafana is installed, a dashboard can be created to with multiple panels which will show data from Prometheus. Reference links https://grafana.com/docs/grafana/latest/getting-started/get-started-grafana-prometheus/","title":"Setting up Grafana and Prometheus"},{"location":"Usage_Monitoring/Prometheus_Grafana/#setting-up-promtheus-and-grafana","text":"","title":"Setting up Promtheus and Grafana"},{"location":"Usage_Monitoring/Prometheus_Grafana/#what-are-prometheus-and-grafana","text":"Prometheus is a tool for monitoring usage of memory, CPU etc. It takes queries as mathematical expressions (like SQL) and returns the interactive graphical usage stats. It collects data using node_exporter , which is used to get raw data from the compute instances Grafana is used for creating dashboards in which there can be different panels containing the graphical statistics from Prometheus. Grafana dashboards are more interactive and user-friendly than Prometheus.","title":"What are Prometheus and Grafana"},{"location":"Usage_Monitoring/Prometheus_Grafana/#setting-up-node-exporters","text":"Node exporters are needed for prometheus to get data from the compute instances. Download pre-compiled tarball of node_exporters from this link and place the tarballs on compute instances. Once node_exporter tarball is downloaded, extract it using following command: tar -xvf node_exporter-x.x.x.linux-amd64.tar.gz Run node_exporter on compute instances using command below (which will run node_exporter on port 9100 by default): ./node_exporter Follow this procedure on every compute instance which is desired to be monitored using Prometheus. Note: Make sure that compute instances can be accessed in the machine in which prometheus is installed.","title":"Setting up Node Exporters"},{"location":"Usage_Monitoring/Prometheus_Grafana/#configuring-prometheus","text":"Use this link to get pre-compiled tarball of Prometheus. Once Prometheus is downloaded, extract it using following command: tar -xvf prometheus-x.xx.x.linux-amd.tar.gz Now either configure prometheus.yml file or create another yml file which will include the addresses of node_exporters. Following is an example template for yml file: global: scrape_interval: 15s scrape_configs: - job_name: node static_configs: - targets: ['node_exporter_ip1:node_exporter_port1'] - targets: ['node_exporter_ip2:node_exporter_port2']","title":"Configuring Prometheus"},{"location":"Usage_Monitoring/Prometheus_Grafana/#running-prometheus","text":"Once prometheus is configured properly, use following command to run prometheus. ./prometheus Note: By default Prometheus looks for prometheus.yml , if you want to use some other file for configuration, you will need to specify explicitly with --config.file option.","title":"Running Prometheus"},{"location":"Usage_Monitoring/Prometheus_Grafana/#running-grafana","text":"Once Prometheus is up and running, Grafana can be used to create dashboards with graphical interface in various panels inside dashboards. Use this to get pre-compiled tarball of Grafana After Grafana is ready to be run, use following command to run Grafana: ./grafana-server #By default it will run on port 3000 The default username and password of Grafana will be admin . Once Grafana is installed, a dashboard can be created to with multiple panels which will show data from Prometheus.","title":"Running Grafana"},{"location":"Usage_Monitoring/Prometheus_Grafana/#reference-links","text":"https://grafana.com/docs/grafana/latest/getting-started/get-started-grafana-prometheus/","title":"Reference links"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/","text":"GitHub Pull Request hook integration with Jenkins Reference Link: https://plugins.jenkins.io/ghprb/ General Guidline If facing an issue, it is better to launch the Jenkins from running the .war file (which is obtained by building the Jenkins github repository) in terminal (which is mostly bash in case of linux) and observing the terminal's output. For example if a webhook is not created, the GUI may not show anything but the terminal will most probably print a message showing the reason for this behavior. GitHub Pull Request Builder Plugin In version control, it is better to check the changes and run tests before the changes are merged into main branch. Sometimes those changes can be enormous to check. So it becomes difficult for requested reviewer of the pull request to check all the changes and run tests on them manually. For that purpose, it is better to automate the process so that whenever a pull request is generated, all the tests are triggered and based on the results, the reviewer decides whether or not to merge the branch with main. This can be achieved using Jenkins' Github Pull Request Builder plugin. Specifications at the time of documentation Operating System: Linux Distribution: Ubuntu Release: Focal (also known as 20.04) Jenkins version: 2.371 (can be seen in config.xml) Github Webhook Builder version: 1.42.2 Pre-Requisites Jenkins. Git Plugin GitHub Plugin Github Pull Request Builder Plugin Github account and repository with permission to generate a pull request to merge the branch. Setting up Jenkins configuration Install the above mentioned plugins from Dashboard > Manage Jenkins > Manage Plugins > Available Plugins . Go to Dashboard > Manage Jenkins > Configure System . Scroll down to Github Pull Request Builder . Leave GitHub Server API URL and Jenkins URL override as it is. In Credentials , click on add and select Jenkins from drop down. Select Kind as Secret text . In Secret , add GitHub Personal authentication token which can be acquired from GitHub account settings. Add some safe description to remind what these credentials are about otherwise jenkins use a lot of credentials and it gets difficult to keep account of them. Leave ID empty. Click on Add . Now select the added credentials from the drop down menu of Credentials . Click on Test Credentials... . Check Test basic connection to GitHub . Click on Connect to API . This will show the message Connected to <API_URL> as <Name_of_GitHub_user> . Other settings can be left empty. Click on save. Setting up Jenkins job In this documentation, Pipeline job will be used, but any job is expected to work fine with these settings. For this documentation it is considered that the jenkinsfile for building the pipeline is present in the repository which is to be built. Go to Dashboard and click New Item . Enter a Job name (here it will be github_PR_webhook ). Click OK . It will navigate to the job's configuration page. Add a Description of choice. Scroll down and check GitHub project . Add the URL of GitHub repository. Here the URL of the repository should be added without .git extention. This is important that the person who is creating pull request should be either in admin list or whitelist because otherwise, the webhook will not be created. Scroll down to Build Triggers section. Check GitHub Pull Request Builder . This will open further configurations for this option. Leave GitHub API credentials . Add a GitHub admin's username in the Admin list . This is important becaue otherwise, the checks will not run on generating a pull request. Check Use github hooks for build triggering . Click on Advanced and in Whitelist Target Branches add the branch name for which, when a pull request is generated, the job is supposed to be trigger (here it is main ). Scroll down to Pipeline section. In Definition , select Pipeline script from SCM . Select SCM as Git from drop down. Enter the Repository URL from GitHub. Enter Credentials with access to this repository (This is optional if the repository is public). Under Advanced , enter Refspec as +refs/pull/*:refs/remotes/origin/pr/* [^note]. If the tests are to be run on actual commit in the pull request then, under Branches to build section, in Branch Specifier , enter ${ghprbActualCommit} [^note]. Leave other settings as it is. In Script Path , add the path and name of the jenkinsfile which is present in GitHub repository. Uncheck Lightweight checkout [^note1] Click Apply and then Save . After saving the job, a webhook should be created automatically in GitHub if the credentials provided in the settings are correct. Verifying if the procedure In the GitHub repository, add another branch aside from main . For this, expand main and click on View all branches . Click on New Branch , and insert a name. After a new branch is created, select new branch instead of main in repository page. Add some changings to either of the file (even adding a space is enough). Commit Changes. Create a Pull request. Now after checking the merge conflicts, the checks will run their results will be shown with pull request (as can be seen in the image below). NOTE: The Jenkinfile will run present in the pull request and not in the main branch. Clicking on the Details navigates the user to the Jenkins Job result page where the console output and each stage can be seen. [^note]: This point is taken from the jenkins GitHub Pull Request Builder plugin documentation at https://plugins.jenkins.io/ghprb/ [^note1]: This is an issue mentioned in the documentation of Github Pull Request Builder plugin at https://plugins.jenkins.io/ghprb/ .","title":"Github PR webhook integration"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#github-pull-request-hook-integration-with-jenkins","text":"Reference Link: https://plugins.jenkins.io/ghprb/","title":"GitHub Pull Request hook integration with Jenkins"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#general-guidline","text":"If facing an issue, it is better to launch the Jenkins from running the .war file (which is obtained by building the Jenkins github repository) in terminal (which is mostly bash in case of linux) and observing the terminal's output. For example if a webhook is not created, the GUI may not show anything but the terminal will most probably print a message showing the reason for this behavior.","title":"General Guidline"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#github-pull-request-builder-plugin","text":"In version control, it is better to check the changes and run tests before the changes are merged into main branch. Sometimes those changes can be enormous to check. So it becomes difficult for requested reviewer of the pull request to check all the changes and run tests on them manually. For that purpose, it is better to automate the process so that whenever a pull request is generated, all the tests are triggered and based on the results, the reviewer decides whether or not to merge the branch with main. This can be achieved using Jenkins' Github Pull Request Builder plugin.","title":"GitHub Pull Request Builder Plugin"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#specifications-at-the-time-of-documentation","text":"Operating System: Linux Distribution: Ubuntu Release: Focal (also known as 20.04) Jenkins version: 2.371 (can be seen in config.xml) Github Webhook Builder version: 1.42.2","title":"Specifications at the time of documentation"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#pre-requisites","text":"Jenkins. Git Plugin GitHub Plugin Github Pull Request Builder Plugin Github account and repository with permission to generate a pull request to merge the branch.","title":"Pre-Requisites"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#setting-up-jenkins-configuration","text":"Install the above mentioned plugins from Dashboard > Manage Jenkins > Manage Plugins > Available Plugins . Go to Dashboard > Manage Jenkins > Configure System . Scroll down to Github Pull Request Builder . Leave GitHub Server API URL and Jenkins URL override as it is. In Credentials , click on add and select Jenkins from drop down. Select Kind as Secret text . In Secret , add GitHub Personal authentication token which can be acquired from GitHub account settings. Add some safe description to remind what these credentials are about otherwise jenkins use a lot of credentials and it gets difficult to keep account of them. Leave ID empty. Click on Add . Now select the added credentials from the drop down menu of Credentials . Click on Test Credentials... . Check Test basic connection to GitHub . Click on Connect to API . This will show the message Connected to <API_URL> as <Name_of_GitHub_user> . Other settings can be left empty. Click on save.","title":"Setting up Jenkins configuration"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#setting-up-jenkins-job","text":"In this documentation, Pipeline job will be used, but any job is expected to work fine with these settings. For this documentation it is considered that the jenkinsfile for building the pipeline is present in the repository which is to be built. Go to Dashboard and click New Item . Enter a Job name (here it will be github_PR_webhook ). Click OK . It will navigate to the job's configuration page. Add a Description of choice. Scroll down and check GitHub project . Add the URL of GitHub repository. Here the URL of the repository should be added without .git extention. This is important that the person who is creating pull request should be either in admin list or whitelist because otherwise, the webhook will not be created. Scroll down to Build Triggers section. Check GitHub Pull Request Builder . This will open further configurations for this option. Leave GitHub API credentials . Add a GitHub admin's username in the Admin list . This is important becaue otherwise, the checks will not run on generating a pull request. Check Use github hooks for build triggering . Click on Advanced and in Whitelist Target Branches add the branch name for which, when a pull request is generated, the job is supposed to be trigger (here it is main ). Scroll down to Pipeline section. In Definition , select Pipeline script from SCM . Select SCM as Git from drop down. Enter the Repository URL from GitHub. Enter Credentials with access to this repository (This is optional if the repository is public). Under Advanced , enter Refspec as +refs/pull/*:refs/remotes/origin/pr/* [^note]. If the tests are to be run on actual commit in the pull request then, under Branches to build section, in Branch Specifier , enter ${ghprbActualCommit} [^note]. Leave other settings as it is. In Script Path , add the path and name of the jenkinsfile which is present in GitHub repository. Uncheck Lightweight checkout [^note1] Click Apply and then Save . After saving the job, a webhook should be created automatically in GitHub if the credentials provided in the settings are correct.","title":"Setting up Jenkins job"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#verifying-if-the-procedure","text":"In the GitHub repository, add another branch aside from main . For this, expand main and click on View all branches . Click on New Branch , and insert a name. After a new branch is created, select new branch instead of main in repository page. Add some changings to either of the file (even adding a space is enough). Commit Changes. Create a Pull request. Now after checking the merge conflicts, the checks will run their results will be shown with pull request (as can be seen in the image below). NOTE: The Jenkinfile will run present in the pull request and not in the main branch. Clicking on the Details navigates the user to the Jenkins Job result page where the console output and each stage can be seen. [^note]: This point is taken from the jenkins GitHub Pull Request Builder plugin documentation at https://plugins.jenkins.io/ghprb/ [^note1]: This is an issue mentioned in the documentation of Github Pull Request Builder plugin at https://plugins.jenkins.io/ghprb/ .","title":"Verifying if the procedure"},{"location":"jenkins_github_integration/Github_push_webhook/","text":"Github 'Push' webhook integration with Jenkins Purpose of using github webhook integration with jenkins Most of the time, after a push on the upstream repository, one may want to check the result of all the checks on the repository defined by CI/CD pipeline. This tells whether there is some issue with push and whether or not the defined checks/tests have passed. This can be achieved using github push webhook integration with jenkins. Jenkins version and operating system specifications The version of Jenkins and operating system specifications at the time of writing this documentation are mentioned below: Jenkins version: 2.370 Operating System: Linux Distribution: Ubuntu Release: Focal (also called 20.04) Pre-requisites Jenkins ngrok (only if a public IP is not available) Setting up the ngrok The localhost cannot be used for github webhook integration as it cannot be detected by online webservers. For this reason, a public ip must be used. For the sake of this documentation, ngrok is being used, which maps localhost to some public ip which can then be accessed publicly on the internet. Following steps can be used for setting up ngrok on ubuntu: Install ngrok. sudo apt install ngrok For using html content, a sign up is required on ngrok. So sign up on ngrok. Execute the following command to run ngrok which will provide a public ip mapped to localhost. ngrok http <port number> This will setup ngrok and provide a public ip for working online. Setting up Jenkins for github webhook Pre-requisites Following plugins should be installed in jenkins: Git Plugin GitHub API Plugin GitHub Plugin Jenkins Configuration in Settings Go to Manage Jenkins > Configure System and scroll down to GitHub section. Click on Add GitHub Server Add a name for the Github server. Leave API URL as is. In Credentials, click on Add . Jenkins will appear in drop down, click on it. Select Kind as Secret text Scroll down to the Secret and here, put down the github personal authentication token (PAT) which can be acquired from github account. Other options can be left unattended. Click on Add . Now the credentials should be added. In the Credentials drop down, select Secret text . Check Manage hooks . Now the connection can be established and can be checked by clicking the Test Connection . Click Save . Jenkins job setup for Github Webhook Create a new jenkins freestyle job and proceed with following settings on the configurations along with desired settings. Check GitHub project in General section and provide GitHub repository URL. In Source Code Management section, select Git . Give Repository URL In Credentials (if the credentials are not created already), click on Add , click on Jenkins from the drop down. Select Kind as Username with password . In Username , enter github username. In Password , enter github personal authentication token (PAT) which can be acquired from github account. Other fields can be left unattended. Click on Add From Credentials drop down, select your added credentials. In Branches to build section, in Branch Specifier field, enter the name of branch of github repository which needs to be built. In Build Triggers section, check GitHub hook trigger for GITScm polling . (Following step is for checking the commit status according to the Jenkins job status, means if Jenkins job fails, commit status is also Failure ) Scroll down to the bottom and Add post-build action . From drop down, select Set GitHub commit status . Leave other settings as is and click on Advanced . Check Handle errors Under drop down Result on failure , select FAILURE Click on Apply and Save By this point, Jenkins is setup for github webhooks. Setting up github repository webhook For the sake of this documentation, I have created a simple repository called jenkins_hello_world_integrated . Go to GitHub repository's settings In Webhooks section, click on Add webhook In Webhooks settings: Add Payload URL as the URL of jenkins and append /github-webhook/ at the end of it. Select Content type application/jason . It is recommended to add Secret which can be generated by jenkins API Token by going to account configuration. It is recommended to Enable SSL verification . Select the events which should trigger the build in jenkins. Check Active . Click on Add Webhook . After this point each time the github repository is commited with a change, jenkins job will start the build and will also denote on the repository if the build has passed or failed (as can be seen in the below screenshot).","title":"Github Push webhook integration"},{"location":"jenkins_github_integration/Github_push_webhook/#github-push-webhook-integration-with-jenkins","text":"","title":"Github 'Push' webhook integration with Jenkins"},{"location":"jenkins_github_integration/Github_push_webhook/#purpose-of-using-github-webhook-integration-with-jenkins","text":"Most of the time, after a push on the upstream repository, one may want to check the result of all the checks on the repository defined by CI/CD pipeline. This tells whether there is some issue with push and whether or not the defined checks/tests have passed. This can be achieved using github push webhook integration with jenkins.","title":"Purpose of using github webhook integration with jenkins"},{"location":"jenkins_github_integration/Github_push_webhook/#jenkins-version-and-operating-system-specifications","text":"The version of Jenkins and operating system specifications at the time of writing this documentation are mentioned below: Jenkins version: 2.370 Operating System: Linux Distribution: Ubuntu Release: Focal (also called 20.04)","title":"Jenkins version and operating system specifications"},{"location":"jenkins_github_integration/Github_push_webhook/#pre-requisites","text":"Jenkins ngrok (only if a public IP is not available)","title":"Pre-requisites"},{"location":"jenkins_github_integration/Github_push_webhook/#setting-up-the-ngrok","text":"The localhost cannot be used for github webhook integration as it cannot be detected by online webservers. For this reason, a public ip must be used. For the sake of this documentation, ngrok is being used, which maps localhost to some public ip which can then be accessed publicly on the internet. Following steps can be used for setting up ngrok on ubuntu: Install ngrok. sudo apt install ngrok For using html content, a sign up is required on ngrok. So sign up on ngrok. Execute the following command to run ngrok which will provide a public ip mapped to localhost. ngrok http <port number> This will setup ngrok and provide a public ip for working online.","title":"Setting up the ngrok"},{"location":"jenkins_github_integration/Github_push_webhook/#setting-up-jenkins-for-github-webhook","text":"","title":"Setting up Jenkins for github webhook"},{"location":"jenkins_github_integration/Github_push_webhook/#pre-requisites_1","text":"Following plugins should be installed in jenkins: Git Plugin GitHub API Plugin GitHub Plugin","title":"Pre-requisites"},{"location":"jenkins_github_integration/Github_push_webhook/#jenkins-configuration-in-settings","text":"Go to Manage Jenkins > Configure System and scroll down to GitHub section. Click on Add GitHub Server Add a name for the Github server. Leave API URL as is. In Credentials, click on Add . Jenkins will appear in drop down, click on it. Select Kind as Secret text Scroll down to the Secret and here, put down the github personal authentication token (PAT) which can be acquired from github account. Other options can be left unattended. Click on Add . Now the credentials should be added. In the Credentials drop down, select Secret text . Check Manage hooks . Now the connection can be established and can be checked by clicking the Test Connection . Click Save .","title":"Jenkins Configuration in Settings"},{"location":"jenkins_github_integration/Github_push_webhook/#jenkins-job-setup-for-github-webhook","text":"Create a new jenkins freestyle job and proceed with following settings on the configurations along with desired settings. Check GitHub project in General section and provide GitHub repository URL. In Source Code Management section, select Git . Give Repository URL In Credentials (if the credentials are not created already), click on Add , click on Jenkins from the drop down. Select Kind as Username with password . In Username , enter github username. In Password , enter github personal authentication token (PAT) which can be acquired from github account. Other fields can be left unattended. Click on Add From Credentials drop down, select your added credentials. In Branches to build section, in Branch Specifier field, enter the name of branch of github repository which needs to be built. In Build Triggers section, check GitHub hook trigger for GITScm polling . (Following step is for checking the commit status according to the Jenkins job status, means if Jenkins job fails, commit status is also Failure ) Scroll down to the bottom and Add post-build action . From drop down, select Set GitHub commit status . Leave other settings as is and click on Advanced . Check Handle errors Under drop down Result on failure , select FAILURE Click on Apply and Save By this point, Jenkins is setup for github webhooks.","title":"Jenkins job setup for Github Webhook"},{"location":"jenkins_github_integration/Github_push_webhook/#setting-up-github-repository-webhook","text":"For the sake of this documentation, I have created a simple repository called jenkins_hello_world_integrated . Go to GitHub repository's settings In Webhooks section, click on Add webhook In Webhooks settings: Add Payload URL as the URL of jenkins and append /github-webhook/ at the end of it. Select Content type application/jason . It is recommended to add Secret which can be generated by jenkins API Token by going to account configuration. It is recommended to Enable SSL verification . Select the events which should trigger the build in jenkins. Check Active . Click on Add Webhook . After this point each time the github repository is commited with a change, jenkins job will start the build and will also denote on the repository if the build has passed or failed (as can be seen in the below screenshot).","title":"Setting up github repository webhook"}]}
\ No newline at end of file
+{"config":{"indexing":"full","lang":["en"],"min_search_length":3,"prebuild_index":false,"separator":"[\\s\\-]+"},"docs":[{"location":"","text":"Cloud-V Documentation On this site, you will find all the documentation regarding Jenkins, LXC containers and QEMU configured to use with Cloud-V CI infrastructure Documentation slides: link Youtube Channel: youtube.com/@Cloud-V","title":"Home"},{"location":"#cloud-v-documentation","text":"On this site, you will find all the documentation regarding Jenkins, LXC containers and QEMU configured to use with Cloud-V CI infrastructure Documentation slides: link Youtube Channel: youtube.com/@Cloud-V","title":"Cloud-V Documentation"},{"location":"Adding_Custom-build_packages_in_Jenkins/","text":"Adding Custom-build packages in Jenkins __NOTE: For this documentation, Ubuntu 22.04 and Jenkins version 2.371 is used. While working open-source, many times one may need to build the package from source code. While working on the local machine, the built package may be accessible by adding it to the $PATH environment variable. But while working with Jenkins, This may not work. Where to install package for Jenkins job In Jenkins job, the package is installed on the node (or agent) on which the specific job is being used and NOT on the node where the jenkins controller node is installed. For example if the Jenkins controller node is on computer1 and slave node on which the job is destined to run is on computer2 then computer2 should have all the packages used by the job and not the computer1 . Adding the package to Jenkins Considering there is a node with name Runner1 in jenkins on which the job is destined to run and that job uses a toolchain riscv64-unknown-elf-gcc to run properly and that toolchain is present in directory /home/runner1/path_to_install/bin , then the following procedure is used to add the toolchain in Jenkins. Go to Dashboard > Manage Jenkins > Nodes > Runner1 . Scroll down and check Environment variables . Under section List of variables add: Name as PATH Value as $PATH:/home/runner1/path_to_install/bin . Click on Save . After this, the package should be available to be used.","title":"Adding Custom-build packages in Jenkins"},{"location":"Adding_Custom-build_packages_in_Jenkins/#adding-custom-build-packages-in-jenkins","text":"__NOTE: For this documentation, Ubuntu 22.04 and Jenkins version 2.371 is used. While working open-source, many times one may need to build the package from source code. While working on the local machine, the built package may be accessible by adding it to the $PATH environment variable. But while working with Jenkins, This may not work.","title":"Adding Custom-build packages in Jenkins"},{"location":"Adding_Custom-build_packages_in_Jenkins/#where-to-install-package-for-jenkins-job","text":"In Jenkins job, the package is installed on the node (or agent) on which the specific job is being used and NOT on the node where the jenkins controller node is installed. For example if the Jenkins controller node is on computer1 and slave node on which the job is destined to run is on computer2 then computer2 should have all the packages used by the job and not the computer1 .","title":"Where to install package for Jenkins job"},{"location":"Adding_Custom-build_packages_in_Jenkins/#adding-the-package-to-jenkins","text":"Considering there is a node with name Runner1 in jenkins on which the job is destined to run and that job uses a toolchain riscv64-unknown-elf-gcc to run properly and that toolchain is present in directory /home/runner1/path_to_install/bin , then the following procedure is used to add the toolchain in Jenkins. Go to Dashboard > Manage Jenkins > Nodes > Runner1 . Scroll down and check Environment variables . Under section List of variables add: Name as PATH Value as $PATH:/home/runner1/path_to_install/bin . Click on Save . After this, the package should be available to be used.","title":"Adding the package to Jenkins"},{"location":"Booting_ubuntu22.04_riscv64/","text":"Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64 Pre-requisites Following are the pre-requisites which are needed to be installed before booting ubuntu 22.04 for RISC-V on qemu . Note: Make sure RISC-V GNU Toolchain is installed before proceeding U-boot Qemu version 7.0 or greater with networking Ubuntu 22.04 pre-built image for RISC-V 1. Installing U-boot Note: If you plan on installing U-boot from apt or some system repository, install the one which comes with ubuntu 22.04. Older will not work with this process. Also, be sure to checkout a latest Stable version instead of development version. Get source code of u-boot and checkout stable version using commands below. git clone https://github.com/qemu/u-boot.git cd u-boot git checkout v2022.10 Generate configurations for supervisor mode with following command. make qemu-riscv64_smode_defconfig CROSS_COMPILE=riscv64-unknown-linux-gnu- Execute following command to start build process. make CROSS_COMPILE=riscv64-unknown-linux-gnu- This should install u-boot.bin in the source directory. This file will be used later so its path must be kept remember. Here it will be refered to as $UBOOTPATH . 2. Installing Qemu Qemu version 7.0 or greater should be installed with networking for ubuntu 22.04 to work. See Installing Qemu for RISC-V for instructions on installing qemu-system-riscv64 . 3. Getting Ubuntu 22.04 pre-build image for RISC-V Ubuntu 22.04 image can be downloaded from https://ubuntu.com/download/risc-v . Booting Ubuntu 22.04 Image on qemu In the directory where ubuntu 22.04 image is present, execute following command to boot into ubuntu 22.04 with qemu-system-riscv64 . If you need more space, you can use following command. qemu-img resize -f raw ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img +5G This will increase storage size of the image by 5GB. qemu-system-riscv64 \\ -machine virt -nographic -m 2048 -smp 4 \\ -kernel $UBOOTPATH/u-boot.bin \\ -device virtio-net-device,netdev=eth0 -netdev user,id=eth0,hostfwd=::<host_port>-:<VM_port> \\ -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio Here -m is the memory in Megabytes and -smp is number of cores. -nographic means qemu will use same terminal instance instead of opening a new window of its own (which is beneficial while running servers without gui). Whereas hostfwd=::<host_port>-:<VM_port> will forward traffic going to port <host_port> to port VM_port . Due to this port <host_port> will be used to access ssh on qemu machine. This should boot ubuntu 22.04. But it will take a while on first start. On start, credentials will be as follows. Username: ubuntu Password: ubuntu After entering credentials, terminal will prompt for change of password after which ubuntu will be ready to use.","title":"Booting RISC-V Ubuntu 22.04 on `qemu-system-riscv64`"},{"location":"Booting_ubuntu22.04_riscv64/#booting-risc-v-ubuntu-2204-on-qemu-system-riscv64","text":"","title":"Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64"},{"location":"Booting_ubuntu22.04_riscv64/#pre-requisites","text":"Following are the pre-requisites which are needed to be installed before booting ubuntu 22.04 for RISC-V on qemu . Note: Make sure RISC-V GNU Toolchain is installed before proceeding U-boot Qemu version 7.0 or greater with networking Ubuntu 22.04 pre-built image for RISC-V","title":"Pre-requisites"},{"location":"Booting_ubuntu22.04_riscv64/#1-installing-u-boot","text":"Note: If you plan on installing U-boot from apt or some system repository, install the one which comes with ubuntu 22.04. Older will not work with this process. Also, be sure to checkout a latest Stable version instead of development version. Get source code of u-boot and checkout stable version using commands below. git clone https://github.com/qemu/u-boot.git cd u-boot git checkout v2022.10 Generate configurations for supervisor mode with following command. make qemu-riscv64_smode_defconfig CROSS_COMPILE=riscv64-unknown-linux-gnu- Execute following command to start build process. make CROSS_COMPILE=riscv64-unknown-linux-gnu- This should install u-boot.bin in the source directory. This file will be used later so its path must be kept remember. Here it will be refered to as $UBOOTPATH .","title":"1. Installing U-boot"},{"location":"Booting_ubuntu22.04_riscv64/#2-installing-qemu","text":"Qemu version 7.0 or greater should be installed with networking for ubuntu 22.04 to work. See Installing Qemu for RISC-V for instructions on installing qemu-system-riscv64 .","title":"2. Installing Qemu"},{"location":"Booting_ubuntu22.04_riscv64/#3-getting-ubuntu-2204-pre-build-image-for-risc-v","text":"Ubuntu 22.04 image can be downloaded from https://ubuntu.com/download/risc-v .","title":"3. Getting Ubuntu 22.04 pre-build image for RISC-V"},{"location":"Booting_ubuntu22.04_riscv64/#booting-ubuntu-2204-image-on-qemu","text":"In the directory where ubuntu 22.04 image is present, execute following command to boot into ubuntu 22.04 with qemu-system-riscv64 . If you need more space, you can use following command. qemu-img resize -f raw ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img +5G This will increase storage size of the image by 5GB. qemu-system-riscv64 \\ -machine virt -nographic -m 2048 -smp 4 \\ -kernel $UBOOTPATH/u-boot.bin \\ -device virtio-net-device,netdev=eth0 -netdev user,id=eth0,hostfwd=::<host_port>-:<VM_port> \\ -drive file=ubuntu-22.04.1-preinstalled-server-riscv64+unmatched.img,format=raw,if=virtio Here -m is the memory in Megabytes and -smp is number of cores. -nographic means qemu will use same terminal instance instead of opening a new window of its own (which is beneficial while running servers without gui). Whereas hostfwd=::<host_port>-:<VM_port> will forward traffic going to port <host_port> to port VM_port . Due to this port <host_port> will be used to access ssh on qemu machine. This should boot ubuntu 22.04. But it will take a while on first start. On start, credentials will be as follows. Username: ubuntu Password: ubuntu After entering credentials, terminal will prompt for change of password after which ubuntu will be ready to use.","title":"Booting Ubuntu 22.04 Image on qemu"},{"location":"Building_Jenkins_github_repo/","text":"Building Github Repository of Jenkins Linux kernel version, distribution and release at the time of build process Linux Kernel : 5.15.0-46-generic (can be checked using uname -r in ubuntu) Distribution : Ubuntu Release : focal (20.04); also works without issue on ubuntu 22.04 (release can be checked using lsb_release -a in ubuntu) Cloning the github repository First clone the repository using the command below (here it is assumed to be cloned at user's home directory: ~/) git clone https://github.com/jenkinsci/jenkins.git Resolving the dependencies After cloning the repository at ~/, the file CONTRIBUTING.md should be available in ~/jenkins/. This file contains all the information to resolve the dependencies and building the repository. Some notable dependencies are Java Development Kit (JDK), Apache Maven (latest version will be preferable) and git. Running Following command will resolve the mentioned dependencies. sudo apt update && sudo apt install default-jdk default-jre maven git -y Building Jenkins using maven on linux For having the jenkins build up as fast as possible, following command can be used in ~/jenkins/. mvn -am -pl war,bom -Pquick-build clean install Executing Jenkins After the above commands successfully completes execution, jenkins.war should be present in ~/jenkins/war/target and can be executed to run at port 8080 on localhost using following command. java -jar ~/jenkins/war/target/jenkins.war --httpPort=8080 #Considering jenkins repo is cloned at ~/ After this process jenkins UI can be accessed using http://localhost:8080 in a browser and a password will be shown on terminal to login to jenkins first time After this, Jenkins UI will go through a very simple post installation process which one can configure according to his needs.","title":"Building Github Repository of Jenkins"},{"location":"Building_Jenkins_github_repo/#building-github-repository-of-jenkins","text":"","title":"Building Github Repository of Jenkins"},{"location":"Building_Jenkins_github_repo/#linux-kernel-version-distribution-and-release-at-the-time-of-build-process","text":"Linux Kernel : 5.15.0-46-generic (can be checked using uname -r in ubuntu) Distribution : Ubuntu Release : focal (20.04); also works without issue on ubuntu 22.04 (release can be checked using lsb_release -a in ubuntu)","title":"Linux kernel version, distribution and release at the time of build process"},{"location":"Building_Jenkins_github_repo/#cloning-the-github-repository","text":"First clone the repository using the command below (here it is assumed to be cloned at user's home directory: ~/) git clone https://github.com/jenkinsci/jenkins.git","title":"Cloning the github repository"},{"location":"Building_Jenkins_github_repo/#resolving-the-dependencies","text":"After cloning the repository at ~/, the file CONTRIBUTING.md should be available in ~/jenkins/. This file contains all the information to resolve the dependencies and building the repository. Some notable dependencies are Java Development Kit (JDK), Apache Maven (latest version will be preferable) and git. Running Following command will resolve the mentioned dependencies. sudo apt update && sudo apt install default-jdk default-jre maven git -y","title":"Resolving the dependencies"},{"location":"Building_Jenkins_github_repo/#building-jenkins-using-maven-on-linux","text":"For having the jenkins build up as fast as possible, following command can be used in ~/jenkins/. mvn -am -pl war,bom -Pquick-build clean install","title":"Building Jenkins using maven on linux"},{"location":"Building_Jenkins_github_repo/#executing-jenkins","text":"After the above commands successfully completes execution, jenkins.war should be present in ~/jenkins/war/target and can be executed to run at port 8080 on localhost using following command. java -jar ~/jenkins/war/target/jenkins.war --httpPort=8080 #Considering jenkins repo is cloned at ~/ After this process jenkins UI can be accessed using http://localhost:8080 in a browser and a password will be shown on terminal to login to jenkins first time After this, Jenkins UI will go through a very simple post installation process which one can configure according to his needs.","title":"Executing Jenkins"},{"location":"Building_Linux_Kernel/","text":"Building a RISCV Linux kernel and booting it in QEMU inside LXC container This documentation covers how to build a linux kernel with RISCV linux toolchain inside an un-privileged LXC container and then boot it on qemu. Doing this process on privileged lxc container makes life easier, but privileged containers always have security loop holes. For instance, their root id is mapped to root id of host machine. On the other hand un-privileged containers are the safest (see link ). Machine's and LXC Container's Operating System Specifications At the time of creating this documentation, following is the specification of host machine and operating system. Host Machine: Ubuntu focal (20.04) 64-bit. LXC Container: Ubuntu jammy (22.04) 64-bit. LXC Container is unprivileged with non-sudo user. NOTE: Throughout this documentation, name of the lxc container will be qemu_container or qemucontainer with non-sudo user as qemu-user which is running on ubuntu 22.04 and host machine x86. Do not confuse the name with assumption that it is booting on qemu emulator. It is just a naming convention. Pre-requisites Following programs may also have their own pre-requisites. Git: For cloning repositories of following programs. Install it with [sudo] apt install git . TMUX: For convenience of multiple terminals. Install it using [sudo] apt install tmux RISCV GNU toolchain built as linux: For compiling the linux kernel. Busybox: For Generating the binaries for linux kernel boot. QEMU Emulator: For booting the linux kernel Linux Kernel (latest version which is used at point of writing this documentation is 6.0.0 ) The working directory inside lxc container for all of this documentation will be ~/riscv-linux or /home/qemu-user/riscv-linux . NOTE: Busybox will not be built inside the lxc container rather it will be built in (any) host linux machine with sudo privileges. 3. RISCV GNU Toolchain Log in the lxc container to the non-sudo user (here SSH is used to log in). Install the prerequisites for building RISCV GNU TOOLCHAIN inside lxc container with root user using command below. apt-get install autoconf automake autotools-dev curl python3 libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev libexpat-dev libncurses-dev Clone the GNU toolchain using the command below. git clone https://github.com/riscv-collab/riscv-gnu-toolchain.git Create a directory in which the RISCV GNU toolchain is desired to be installed (here it will be /home/qemu-user/riscv-linux/riscv-gnu-installed ) Execute following command inside cloned repository with --prefix as the absolute directory path to where the RISCV toolchain is to be installed ./configure --prefix=/home/qemu-user/riscv-linux/riscv-gnu-installed Execute following inside cloned repository (execution of this command will take a while to complete) make linux -j$(nproc) # 'nproc' is the command used to determine the number of processors in machine so that 'make' can use parallelism. After the execution of command is complete, add bin directory created inside the riscv installation directory to the $PATH and add the expression to .bashrc . According to this documentation, following expression will be added to .bashrc . PATH=\"/home/qemu-user/riscv-linux/riscv-gnu-installed/bin:$PATH\" Check if the toolchain is installed by executing following commands. exec $SHELL riscv64-unknown-linux-gnu-gcc Expected Output: fatal error: no input files compilation terminated. Now RISCV linux toolchain is ready ! 4. Busybox Busybox is the package for creating linux binutils and set of directories for linux to boot into. Busybox will be installed in host machine instead of lxc container. The reason for this is linux kernel requires block oriented device and character oriented device for it to boot. Those devices can be created using mknod command which can only be created inside a host machine with sudo privileges. Busybox will be used in creating initial ram disk file (in gz format) which is used to boot kernel. It does not matter at which operating system or on which machine this file is created. But the machine on which it is compiled, must also have RISCV GNU toolchain installed above. Clone Busybox using the command below. git clone https://git.busybox.net/busybox Navigate to cloned directory. cd busybox Before building busybox, we need to produce a configuration (.config file) for busybox. It is better to apply default configurations and then change only those which are desired. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- defconfig After the command is executed, a .config file will be present in the busybox cloned directory. Now, an additional option is to be enabled which enables busybox to build the libraries in the executable instead of separate shared libraries. For this purpose, execute the following command to access the configuration menu. Then go to Settings menu by pressing enter and from there, enable [ ] Build static binary (no shared libs) by pressing space. After the option is enabled, exit by pressing esc twice two times and press yes to the prompt about file saving. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- menuconfig Now that configuration is complete, build busybox by executing following command. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) Execute following command which will produce all the basic linux utilities in _install directory in busybox repo directory. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) install Navigate to _install directory and create dev directory. cd _install mkdir dev Now, a linux console and a ram devices are to be created inside dev directory. A fact to understand here is that, every device is a file in linux but they are special kind of files. A detail of these devices can be found here . In this documentation mknod command is used to create these devices. sudo mknod dev/console c 5 1 sudo mknod dev/ram b 1 0 After executing above commands, following files with names ram and console will be created as shown in the image below. Now an init file is needed because linux kernel does not boot itself, it rather searches for init file in the directories (read linux kernel messages during build procedure). init file contains commands to mount some directories during boot (more information can be found here ). In busybox/_install , create a file with following contents (be sure to make it executable with chmod +x init ). vim init #!/bin/sh echo \"### INIT SCRIPT ###\" mkdir /proc /sys /tmp mount -t proc none /proc #For processes mount -t sysfs none /sys #For all the devices on the machine mount -t tmpfs none /tmp #For virtual memory echo -e \"\\nThis boot took $(cut -d' ' -f1 /proc/uptime) seconds\\n\" exec /bin/sh Now that all the files are ready for linux to boot into, pack them in cpio format and then to gz format. It is because cpio format is in \"Early userspace support\" in linux kernel (see link ) whereas gz format is needed because it is one of the formats needed by qemu emulator. Following command produces a qemu-compatible initramfs file for linux kernel to boot in. find -print0 | cpio -0oH newc | gzip -9 > ../initramfs.cpio.gz Command Details: find -print0 separates the file names with null character cpio -0oH newc produces an archive file in newc format gzip -9 creates a gz format zip file. -9 represents the best compression level at the slowest speed ../initramfs.cpio.gz represents the output file which is created in parent directory to present working directory. At this point, our work with busybox is done. Copy the produced file into the lxc container (use scp command if it is on ssh). 5. QEMU Emulator Install the pre-requisites of qemu emulator on lxc container with root user with following command (see link ). apt-get install git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build Clone the QEMU Emulator repository using the command below with root user: git clone https://github.com/qemu/qemu.git Build QEMU for RISCV with root user using commands below (see link ). ./configure --target-list=riscv64-softmmu make -j$(nproc) For system-wide installation of QEMU Emulator, run following command with root user. make -j$(nproc) install After execution of this command, work with QEMU Emulator is done and its commands can be accessed anywhere. 6. Linux Kernel Clone the linux kernel from Linus Torvalds' repository using the command below. git clone https://github.com/torvalds/linux.git Navigate to cloned repository. cd linux Building Linux kernel with riscv64-unknown-linux-gnu-gcc Before building linux kernel with RISCV toolchain a configuration file (.config) must be produced in its directory. First, produce a file with default configurations, then change configurations according to needs. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- defconfig make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- menuconfig Above command will open configuration menu. Enter General setup , scroll down and enable Initial RAM filesystem and RAM disk (initramfs/initrd) support using Space key. Then enter () Initramfs source file(s) and here put the absolute path to initramfs.cpio.gz file which was just created using busybox. For this documentation, it is /home/qemu-user/riscv-linux/initramfs.cpio.gz . Double-press esc and save the file. Now linux kernel is ready to be compiled with riscv64-linux-gnu-gcc toolchain. So execute the command below. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) If the above command successfully executed without any errors, there must be Kernel: arch/riscv/boot/Image.gz is ready printed on terminal. On newer linux kernels, it might be scrolled up a little, use Ctrl-shift-f to find it. Booting into the linux kernel using QEMU emulator Now that everything is ready, execute the following command in linux/arch/riscv/boot/ directory to boot linux on sifive's unleashed . qemu-system-riscv64 -kernel Image -machine sifive_u -nographic Command Details qemu-system-riscv64 is the qemu built for riscv64 -kernel takes the image produced by linux kernel compilation and is present in linux/arch/riscv/boot/ directory. -machine takes one of the machine names as arguments available in qemu-system-riscv64 . Available machines can be listed on terminal using command qemu-system-riscv64 -machine help . -nographic restricts the use of GUI (which is a better option considering lxc container does not support gtk initialization). If everything goes on right, the kernel will boot successfully as shown in the picture below. Reference links https://risc-v-getting-started-guide.readthedocs.io/en/latest/linux-qemu.html https://hackernoon.com/how-to-set-up-the-environment-for-riscv-64-linux-kernel-development-in-ubuntu-2004-si5p35kv","title":"Building a RISCV Linux kernel and booting it in QEMU inside LXC container"},{"location":"Building_Linux_Kernel/#building-a-riscv-linux-kernel-and-booting-it-in-qemu-inside-lxc-container","text":"This documentation covers how to build a linux kernel with RISCV linux toolchain inside an un-privileged LXC container and then boot it on qemu. Doing this process on privileged lxc container makes life easier, but privileged containers always have security loop holes. For instance, their root id is mapped to root id of host machine. On the other hand un-privileged containers are the safest (see link ).","title":"Building a RISCV Linux kernel and booting it in QEMU inside LXC container"},{"location":"Building_Linux_Kernel/#machines-and-lxc-containers-operating-system-specifications","text":"At the time of creating this documentation, following is the specification of host machine and operating system. Host Machine: Ubuntu focal (20.04) 64-bit. LXC Container: Ubuntu jammy (22.04) 64-bit. LXC Container is unprivileged with non-sudo user. NOTE: Throughout this documentation, name of the lxc container will be qemu_container or qemucontainer with non-sudo user as qemu-user which is running on ubuntu 22.04 and host machine x86. Do not confuse the name with assumption that it is booting on qemu emulator. It is just a naming convention.","title":"Machine's and LXC Container's Operating System Specifications"},{"location":"Building_Linux_Kernel/#pre-requisites","text":"Following programs may also have their own pre-requisites. Git: For cloning repositories of following programs. Install it with [sudo] apt install git . TMUX: For convenience of multiple terminals. Install it using [sudo] apt install tmux RISCV GNU toolchain built as linux: For compiling the linux kernel. Busybox: For Generating the binaries for linux kernel boot. QEMU Emulator: For booting the linux kernel Linux Kernel (latest version which is used at point of writing this documentation is 6.0.0 ) The working directory inside lxc container for all of this documentation will be ~/riscv-linux or /home/qemu-user/riscv-linux . NOTE: Busybox will not be built inside the lxc container rather it will be built in (any) host linux machine with sudo privileges.","title":"Pre-requisites"},{"location":"Building_Linux_Kernel/#3-riscv-gnu-toolchain","text":"Log in the lxc container to the non-sudo user (here SSH is used to log in). Install the prerequisites for building RISCV GNU TOOLCHAIN inside lxc container with root user using command below. apt-get install autoconf automake autotools-dev curl python3 libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev libexpat-dev libncurses-dev Clone the GNU toolchain using the command below. git clone https://github.com/riscv-collab/riscv-gnu-toolchain.git Create a directory in which the RISCV GNU toolchain is desired to be installed (here it will be /home/qemu-user/riscv-linux/riscv-gnu-installed ) Execute following command inside cloned repository with --prefix as the absolute directory path to where the RISCV toolchain is to be installed ./configure --prefix=/home/qemu-user/riscv-linux/riscv-gnu-installed Execute following inside cloned repository (execution of this command will take a while to complete) make linux -j$(nproc) # 'nproc' is the command used to determine the number of processors in machine so that 'make' can use parallelism. After the execution of command is complete, add bin directory created inside the riscv installation directory to the $PATH and add the expression to .bashrc . According to this documentation, following expression will be added to .bashrc . PATH=\"/home/qemu-user/riscv-linux/riscv-gnu-installed/bin:$PATH\" Check if the toolchain is installed by executing following commands. exec $SHELL riscv64-unknown-linux-gnu-gcc Expected Output: fatal error: no input files compilation terminated. Now RISCV linux toolchain is ready !","title":"3. RISCV GNU Toolchain"},{"location":"Building_Linux_Kernel/#4-busybox","text":"Busybox is the package for creating linux binutils and set of directories for linux to boot into. Busybox will be installed in host machine instead of lxc container. The reason for this is linux kernel requires block oriented device and character oriented device for it to boot. Those devices can be created using mknod command which can only be created inside a host machine with sudo privileges. Busybox will be used in creating initial ram disk file (in gz format) which is used to boot kernel. It does not matter at which operating system or on which machine this file is created. But the machine on which it is compiled, must also have RISCV GNU toolchain installed above. Clone Busybox using the command below. git clone https://git.busybox.net/busybox Navigate to cloned directory. cd busybox Before building busybox, we need to produce a configuration (.config file) for busybox. It is better to apply default configurations and then change only those which are desired. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- defconfig After the command is executed, a .config file will be present in the busybox cloned directory. Now, an additional option is to be enabled which enables busybox to build the libraries in the executable instead of separate shared libraries. For this purpose, execute the following command to access the configuration menu. Then go to Settings menu by pressing enter and from there, enable [ ] Build static binary (no shared libs) by pressing space. After the option is enabled, exit by pressing esc twice two times and press yes to the prompt about file saving. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- menuconfig Now that configuration is complete, build busybox by executing following command. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) Execute following command which will produce all the basic linux utilities in _install directory in busybox repo directory. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) install Navigate to _install directory and create dev directory. cd _install mkdir dev Now, a linux console and a ram devices are to be created inside dev directory. A fact to understand here is that, every device is a file in linux but they are special kind of files. A detail of these devices can be found here . In this documentation mknod command is used to create these devices. sudo mknod dev/console c 5 1 sudo mknod dev/ram b 1 0 After executing above commands, following files with names ram and console will be created as shown in the image below. Now an init file is needed because linux kernel does not boot itself, it rather searches for init file in the directories (read linux kernel messages during build procedure). init file contains commands to mount some directories during boot (more information can be found here ). In busybox/_install , create a file with following contents (be sure to make it executable with chmod +x init ). vim init #!/bin/sh echo \"### INIT SCRIPT ###\" mkdir /proc /sys /tmp mount -t proc none /proc #For processes mount -t sysfs none /sys #For all the devices on the machine mount -t tmpfs none /tmp #For virtual memory echo -e \"\\nThis boot took $(cut -d' ' -f1 /proc/uptime) seconds\\n\" exec /bin/sh Now that all the files are ready for linux to boot into, pack them in cpio format and then to gz format. It is because cpio format is in \"Early userspace support\" in linux kernel (see link ) whereas gz format is needed because it is one of the formats needed by qemu emulator. Following command produces a qemu-compatible initramfs file for linux kernel to boot in. find -print0 | cpio -0oH newc | gzip -9 > ../initramfs.cpio.gz Command Details: find -print0 separates the file names with null character cpio -0oH newc produces an archive file in newc format gzip -9 creates a gz format zip file. -9 represents the best compression level at the slowest speed ../initramfs.cpio.gz represents the output file which is created in parent directory to present working directory. At this point, our work with busybox is done. Copy the produced file into the lxc container (use scp command if it is on ssh).","title":"4. Busybox"},{"location":"Building_Linux_Kernel/#5-qemu-emulator","text":"Install the pre-requisites of qemu emulator on lxc container with root user with following command (see link ). apt-get install git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build Clone the QEMU Emulator repository using the command below with root user: git clone https://github.com/qemu/qemu.git Build QEMU for RISCV with root user using commands below (see link ). ./configure --target-list=riscv64-softmmu make -j$(nproc) For system-wide installation of QEMU Emulator, run following command with root user. make -j$(nproc) install After execution of this command, work with QEMU Emulator is done and its commands can be accessed anywhere.","title":"5. QEMU Emulator"},{"location":"Building_Linux_Kernel/#6-linux-kernel","text":"Clone the linux kernel from Linus Torvalds' repository using the command below. git clone https://github.com/torvalds/linux.git Navigate to cloned repository. cd linux","title":"6. Linux Kernel"},{"location":"Building_Linux_Kernel/#building-linux-kernel-with-riscv64-unknown-linux-gnu-gcc","text":"Before building linux kernel with RISCV toolchain a configuration file (.config) must be produced in its directory. First, produce a file with default configurations, then change configurations according to needs. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- defconfig make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- menuconfig Above command will open configuration menu. Enter General setup , scroll down and enable Initial RAM filesystem and RAM disk (initramfs/initrd) support using Space key. Then enter () Initramfs source file(s) and here put the absolute path to initramfs.cpio.gz file which was just created using busybox. For this documentation, it is /home/qemu-user/riscv-linux/initramfs.cpio.gz . Double-press esc and save the file. Now linux kernel is ready to be compiled with riscv64-linux-gnu-gcc toolchain. So execute the command below. make ARCH=riscv CROSS_COMPILE=riscv64-unknown-linux-gnu- -j$(nproc) If the above command successfully executed without any errors, there must be Kernel: arch/riscv/boot/Image.gz is ready printed on terminal. On newer linux kernels, it might be scrolled up a little, use Ctrl-shift-f to find it.","title":"Building Linux kernel with riscv64-unknown-linux-gnu-gcc"},{"location":"Building_Linux_Kernel/#booting-into-the-linux-kernel-using-qemu-emulator","text":"Now that everything is ready, execute the following command in linux/arch/riscv/boot/ directory to boot linux on sifive's unleashed . qemu-system-riscv64 -kernel Image -machine sifive_u -nographic Command Details qemu-system-riscv64 is the qemu built for riscv64 -kernel takes the image produced by linux kernel compilation and is present in linux/arch/riscv/boot/ directory. -machine takes one of the machine names as arguments available in qemu-system-riscv64 . Available machines can be listed on terminal using command qemu-system-riscv64 -machine help . -nographic restricts the use of GUI (which is a better option considering lxc container does not support gtk initialization). If everything goes on right, the kernel will boot successfully as shown in the picture below.","title":"Booting into the linux kernel using QEMU emulator"},{"location":"Building_Linux_Kernel/#reference-links","text":"https://risc-v-getting-started-guide.readthedocs.io/en/latest/linux-qemu.html https://hackernoon.com/how-to-set-up-the-environment-for-riscv-64-linux-kernel-development-in-ubuntu-2004-si5p35kv","title":"Reference links"},{"location":"Building_qemu/","text":"Installing QEMU for emulating riscv64 QEMU is an open-source emulator. It can be used to emulate different architectures on a single machine. In RISC-V CI there are various programs which run on RISC-V architecture. But instead of porting them to a dedicated board of riscv architecture, they can be run readily on qemu emulator. Here two types of QEMU emulators will be used for RISC-V applications: qemu-system-riscv64: It can be used to load a complete linux operating system image. qemu-riscv64: It can be used to execute program's binary directly without need of a complete operating system. Installing Pre-requisites Execute the following command to install the pre-requisites for installing qemu on ubuntu 22.04 (jammy) sudo apt-get install meson git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build qemu-slirp is important for enabling user-level networking with qemu-system-riscv64 qemu-system-riscv64 while loading image of server installation of ubuntu. So it needs to be installed first. Get the source code of qemu-slirp using following command: git clone https://github.com/openSUSE/qemu-slirp.git Then Execute following commands to install slirp in meson, which can later be used by qemu during build. meson build ninja -C build install Note: Make sure you have riscv64-unknown-linux-gnu toolchain installed for compiling program and executing them on qemu later. There are some optional dependencies which one can download, but they are actually not needed for installing qemu and make it work. Installing qemu-system-riscv64 What is qemu-system-riscv64 qemu-system-riscv64 is qemu executable program. It can load a complete linux distribution. It cannot take program's executable binary as argument and run it without a dedicated linux distribution. Installing qemu-system-riscv64 on ubuntu Get source code of qemu from github using the command below git clone https://github.com/qemu/qemu.git Configure qemu for riscv64-softmmu with following command (replace $PREFIX with valid location of installation). ./configure --prefix=$PREFIX --target-list=riscv64-linux-user,riscv64-softmmu --enable-slirp Execute following command to start the build. make Execute following command to install the binaries at $PREFIX location. make install Note: After the installation with slirp following error can be encountered on some systems . qemu-system-riscv64: symbol lookup error: qemu-system-riscv64: undefined symbol: slirp_new, version SLIRP_4.0 Solution: This can be solved by executing following command in source directory of qemu (which is cloned from github). [sudo] ldconfig Testing qemu-system-riscv64 qemu-system-riscv64 can only be tested by booting a linux operating system. See Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64 . Installing qemu-riscv64 What is qemu-riscv64 qemu-riscv64 is qemu executable program. But instead of porting a complete operating system (like qemu-system-riscv64 ), it can readily execute binaries. Throughout cross-compiling section, qemu-riscv64 will be used with linux-user and executable of every program can be tested on qemu (e.g. python, ruby etc.). Installing qemu-riscv64 on ubuntu 22.04 Get source code of qemu using the command below git clone https://github.com/qemu/qemu.git Use following command in the root directory of repository to configure qemu for riscv64-linux-user ./configure --target-list=riscv64-linux-user --prefix=$PREFIX # Replace $PREFIX with a valid location to install at Note: If this is not your architecture/platform, you can see a list of available platform/architecture by executing following command. ./configure --help Use the following command to start the build process make -j$(nproc) After the builld is complete without any error, use the following command to install binaries at $PREFIX location make install Add the $PREFIX/bin to $PATH variable so that it may be recognized as a command. Using this method causes the qemu-riscv64 to have an issue with sysroot. It starts searching for libraries in the root folder of the machine which is based on x86_64-linux-gnu . A simple workaround is to give path of the sysroot/ folder where riscv64-unknown-linux-gnu toolchain is installed. Here that directory will be denoted as $RISCV_SYSROOT Testing qemu-riscv64 Create a C file in your favorite editor or by using the commands below: echo \"#include<stdio.h>\" > helloworld.c echo \"int main(){\" >> helloworld.c echo \"printf(\"Hello World !\");\" >> helloworld.c echo '}' >> helloworld.c Execute following command to compile C program with riscv gnu toolchain riscv64-unknown-linux-gnu-gcc helloworld.c -o helloworld Execute following command to execute the compiled binary on qemu-riscv64 qemu-riscv64 -L $RISCV_SYSROOT ./helloworld If everything went right, following output will be shown. Hello World !","title":"Installing `QEMU` for emulating riscv64"},{"location":"Building_qemu/#installing-qemu-for-emulating-riscv64","text":"QEMU is an open-source emulator. It can be used to emulate different architectures on a single machine. In RISC-V CI there are various programs which run on RISC-V architecture. But instead of porting them to a dedicated board of riscv architecture, they can be run readily on qemu emulator. Here two types of QEMU emulators will be used for RISC-V applications: qemu-system-riscv64: It can be used to load a complete linux operating system image. qemu-riscv64: It can be used to execute program's binary directly without need of a complete operating system.","title":"Installing QEMU for emulating riscv64"},{"location":"Building_qemu/#installing-pre-requisites","text":"Execute the following command to install the pre-requisites for installing qemu on ubuntu 22.04 (jammy) sudo apt-get install meson git libglib2.0-dev libfdt-dev libpixman-1-dev zlib1g-dev ninja-build qemu-slirp is important for enabling user-level networking with qemu-system-riscv64 qemu-system-riscv64 while loading image of server installation of ubuntu. So it needs to be installed first. Get the source code of qemu-slirp using following command: git clone https://github.com/openSUSE/qemu-slirp.git Then Execute following commands to install slirp in meson, which can later be used by qemu during build. meson build ninja -C build install Note: Make sure you have riscv64-unknown-linux-gnu toolchain installed for compiling program and executing them on qemu later. There are some optional dependencies which one can download, but they are actually not needed for installing qemu and make it work.","title":"Installing Pre-requisites"},{"location":"Building_qemu/#installing-qemu-system-riscv64","text":"","title":"Installing qemu-system-riscv64"},{"location":"Building_qemu/#what-is-qemu-system-riscv64","text":"qemu-system-riscv64 is qemu executable program. It can load a complete linux distribution. It cannot take program's executable binary as argument and run it without a dedicated linux distribution.","title":"What is qemu-system-riscv64"},{"location":"Building_qemu/#installing-qemu-system-riscv64-on-ubuntu","text":"Get source code of qemu from github using the command below git clone https://github.com/qemu/qemu.git Configure qemu for riscv64-softmmu with following command (replace $PREFIX with valid location of installation). ./configure --prefix=$PREFIX --target-list=riscv64-linux-user,riscv64-softmmu --enable-slirp Execute following command to start the build. make Execute following command to install the binaries at $PREFIX location. make install Note: After the installation with slirp following error can be encountered on some systems . qemu-system-riscv64: symbol lookup error: qemu-system-riscv64: undefined symbol: slirp_new, version SLIRP_4.0 Solution: This can be solved by executing following command in source directory of qemu (which is cloned from github). [sudo] ldconfig","title":"Installing qemu-system-riscv64 on ubuntu"},{"location":"Building_qemu/#testing-qemu-system-riscv64","text":"qemu-system-riscv64 can only be tested by booting a linux operating system. See Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64 .","title":"Testing qemu-system-riscv64"},{"location":"Building_qemu/#installing-qemu-riscv64","text":"","title":"Installing qemu-riscv64"},{"location":"Building_qemu/#what-is-qemu-riscv64","text":"qemu-riscv64 is qemu executable program. But instead of porting a complete operating system (like qemu-system-riscv64 ), it can readily execute binaries. Throughout cross-compiling section, qemu-riscv64 will be used with linux-user and executable of every program can be tested on qemu (e.g. python, ruby etc.).","title":"What is qemu-riscv64"},{"location":"Building_qemu/#installing-qemu-riscv64-on-ubuntu-2204","text":"Get source code of qemu using the command below git clone https://github.com/qemu/qemu.git Use following command in the root directory of repository to configure qemu for riscv64-linux-user ./configure --target-list=riscv64-linux-user --prefix=$PREFIX # Replace $PREFIX with a valid location to install at Note: If this is not your architecture/platform, you can see a list of available platform/architecture by executing following command. ./configure --help Use the following command to start the build process make -j$(nproc) After the builld is complete without any error, use the following command to install binaries at $PREFIX location make install Add the $PREFIX/bin to $PATH variable so that it may be recognized as a command. Using this method causes the qemu-riscv64 to have an issue with sysroot. It starts searching for libraries in the root folder of the machine which is based on x86_64-linux-gnu . A simple workaround is to give path of the sysroot/ folder where riscv64-unknown-linux-gnu toolchain is installed. Here that directory will be denoted as $RISCV_SYSROOT","title":"Installing qemu-riscv64 on ubuntu 22.04"},{"location":"Building_qemu/#testing-qemu-riscv64","text":"Create a C file in your favorite editor or by using the commands below: echo \"#include<stdio.h>\" > helloworld.c echo \"int main(){\" >> helloworld.c echo \"printf(\"Hello World !\");\" >> helloworld.c echo '}' >> helloworld.c Execute following command to compile C program with riscv gnu toolchain riscv64-unknown-linux-gnu-gcc helloworld.c -o helloworld Execute following command to execute the compiled binary on qemu-riscv64 qemu-riscv64 -L $RISCV_SYSROOT ./helloworld If everything went right, following output will be shown. Hello World !","title":"Testing qemu-riscv64"},{"location":"Creating_CI_CD_pipeline/","text":"Creating a CI/CD pipeline in Jenkins Pre Requisistes For sake of this documentation, jenkins built-in sample script is used to create and execute a cd/cd pipeline in jenkins. In the built-in script maven is used as M3, so one must install Maven plugin inside jenkins and name it M3 . Usually maven is already present inside jenkins and can be configured from Global Configuration Tools . Following steps demonstrate configuring Maven plugin. Go to Jenkins Dashboard and click on Manage Jenkins In Manage Jenkins , under System Configuration section, click on Global Tool Configuration . In Global Tool Configuration , scroll down to Maven section and click on the respective option under the Maven Section (should be Maven installations\u2026 or Add Maven ). Under Maven installations , enter M3 in \u201cname\u201d text box, check Install Automatically and select Version greater than 3, then click Apply and Save . This should install Maven version 3 and configure as M3 . Steps for Jenkins pipeline creation After installing Jenkins and having all the suggested plugins installed, go to Jenkins dashboard and click on Create Job . On the next page, give your pipeline a name, select Pipeline and click OK . A Configuration page for the pipeline will appear. Select Build Triggers options and General options according to need and scroll down to the Pipeline section. Definition section contains configuration for stages and steps of the pipeline. Under Definition section, you can either choose Pipeline script and try writing your own script or try some sample pipeline (like Hello World , Github+Maven etc) or you could select Pipeline script from SCM and give a github repository containing configurations of Pipeline. Press Save and Apply . This should take you to the Pipeline and you can build the pipeline and if no unresolved dependencies are present, the pipeline should build without any error.","title":"Creating a CI/CD pipeline in Jenkins"},{"location":"Creating_CI_CD_pipeline/#creating-a-cicd-pipeline-in-jenkins","text":"","title":"Creating a CI/CD pipeline in Jenkins"},{"location":"Creating_CI_CD_pipeline/#pre-requisistes","text":"For sake of this documentation, jenkins built-in sample script is used to create and execute a cd/cd pipeline in jenkins. In the built-in script maven is used as M3, so one must install Maven plugin inside jenkins and name it M3 . Usually maven is already present inside jenkins and can be configured from Global Configuration Tools . Following steps demonstrate configuring Maven plugin. Go to Jenkins Dashboard and click on Manage Jenkins In Manage Jenkins , under System Configuration section, click on Global Tool Configuration . In Global Tool Configuration , scroll down to Maven section and click on the respective option under the Maven Section (should be Maven installations\u2026 or Add Maven ). Under Maven installations , enter M3 in \u201cname\u201d text box, check Install Automatically and select Version greater than 3, then click Apply and Save . This should install Maven version 3 and configure as M3 .","title":"Pre Requisistes"},{"location":"Creating_CI_CD_pipeline/#steps-for-jenkins-pipeline-creation","text":"After installing Jenkins and having all the suggested plugins installed, go to Jenkins dashboard and click on Create Job . On the next page, give your pipeline a name, select Pipeline and click OK . A Configuration page for the pipeline will appear. Select Build Triggers options and General options according to need and scroll down to the Pipeline section. Definition section contains configuration for stages and steps of the pipeline. Under Definition section, you can either choose Pipeline script and try writing your own script or try some sample pipeline (like Hello World , Github+Maven etc) or you could select Pipeline script from SCM and give a github repository containing configurations of Pipeline. Press Save and Apply . This should take you to the Pipeline and you can build the pipeline and if no unresolved dependencies are present, the pipeline should build without any error.","title":"Steps for Jenkins pipeline creation"},{"location":"Creating_Jenkins_Node_on_LXC/","text":"Creating a Jenkins Node on LXC Container What is a container A container is a virtualization method for isolating the applications (or even operating systems) from each other. Why do we need a container for Jenkins node In Jenkins, node is a location where our jobs run. One user can use one node for all of his processes and multiple users may also use one node for all of their processes. In Jenkins freestyle project, we can use bash shell or windows command shell due to which there is a possibility to navigate anywhere in the server machine. This possibility can lead to various security and integrity issues for server administrators and also for other users using that webserver. So one must isolate each node and allocate each node to each user separately. What is LXC Container LXC stands for Linux Containers. LXC is a package for linux operating systems and provides linux users with containers which may contain a whole linux operating system while also being lightweight than a virtual machine. More information regarding LXC can be found at https://linuxcontainers.org/lxc/introduction/ On ubuntu 20.04 one can install LXC using command [sudo] apt-get install lxc Creating a container with LXC NOTE: Throughout this document, the name of the container will be my-container and the name of the user will be user1 . So wherever my-container is written, one may change the name to whatever one wants to give it. Pre-requisites Before proceeding, it is important to mention that at the point of writing this document following are the specifications for linux kernel and distribution: Linux Kernel : 5.15.0-46-generic (can be checked on ubuntu by command uname -r ) Distribution : Ubuntu focal (20.04) (can be checked on ubuntu by command lsb_release -a ) By default linux users are not allowed to create any network device on the machine. For doing that, one must add uid and gid in the /etc/lxc/lxc-usernet . The uid and gid of the user you want to use can be found in the files /etc/uid and /etc/gid respectively. After getting the gid and uid of the user you want to allow for creating the network devices, one must go to /etc/lxc/lxc-usernet and add the uid and gid in the following format: <username> veth lxcbr0 10 e.g. jenkins veth lxcbr0 10 In above example jenkins is the username, veth is the command used for creating the bridges between virtual network devices and physical network devices (you will be able to see that ethernet device in our container will be lxcbr0 ) and lxbr0 is the network device we want to create. \u201810\u2019 represents the number of devices we want to create using our specified user. According lxc documentation, in ubuntu 20.04 an additional command is required before creating lxc container: export DOWNLOAD_KEYSERVER=\"hkp://keyserver.ubuntu.com\" Creating image After this, one can create container using following command systemd-run --unit=my-unit --user --scope -p \"Delegate=yes\" -- lxc-create -t download -n my-container This runs lxc container with unit name my-unit , container name my-container and delegates a control group (also known as the cgroup ) which is needed for resource allocation for processes in container. This will output the list of available linux distributions in which one may want to run the container and will prompt for Distribution as shown in the following image. After selecting the suitable distribution, release and architecture (which is also mentioned in the table), the container may be created as shown in the image below: Next thing is to start a container which will change its state from STOPPED to RUNNING using the following command. lxc-start -n my-container Above command will have no output if it succeeds. The state of the container can be checked using the following command. lxc-info -n my-container After starting the container, its state will be set as running and is just like turning a linux machine ON. From this point onwards, if one wants to use the machine in the terminal then use the following command and this will switch the terminal to the root of the container. lxc-attach my-container Now the container is ready to be used and is completely isolated from the host machine. Using SSH to access container with username and password The above mentioned method can be used to attach the host machine terminal to the container and this can be used to access the container. But if one wants to access the machine remotely then one possible and well-known method will be to configure and use SSH on the container. As it is an out of the box linux distro and only the root user is present, so first create another user using the following command and then manage its permissions for /home folder . #Considering you remain the root user for execution of all the following #commands useradd user1 cd /home mkdir user1 #Creating home directory for user1 chown user1:user1 user1 #Giving ownership of home directory to new user #For adding the same shell and bashrc configurations for new user, use #following #command, otherwise the shell will be very basic for new user and will be #very inconvenient to use. usermod -s /bin/bash user1 For the sake of simplicity of this document the name used for the new user is user1 here. (You may want to set the password for user1 by executing the passwd command in root.) At this point user1 is not in sudoers. For adding it to the sudoers, it must be added in the sudo group which can be done by using the following command. usermod -a -G sudo user1 Now switch to the user1 using the following command. su - user Now install openssh-server for configuring the ssh on user1. sudo apt install openssh-server After that one must find the ip of the container we are using, for this either run following command while in container with user1, sudo apt-install net-tools #Because ifconfig is part of net-tools which are by default not installed on new #container Ifconfig -a OR open a new terminal in the host machine and execute the following command. lxc-info my-container -iH So, the ip of the container is 10.0.3.127 . The command for establishing an ssh connection to a remote machine is mentioned below and it will ask for the password of the remote machine which is actually the container in our case. ssh user1@10.0.3.127 After entering the password, terminal will switch to the container\u2019s user1 as can be seen in the following image. Using SSH to access Jenkins agents on the container First install some initial dependencies (git, jdk, jre) on the containers for running agents on the container. sudo apt update sudo apt install default-jdk default-jre git maven Now login to jenkins with administrator privileges and create a node in it from Dashboard > Manage Jenkins > Nodes and press + New Node . Enter a name for the node and select the desirable node type. For this documentation, the node will be a permanent type and the name will be temp_node . After this click on Create which will display the configuration page of the node. Write the description of the node as desired. Number of executors means number of threads running at a time (it will be better to set it to the number of processors present on the machine which is running this node). Remote root directory will be the directory where the jobs will run by default on the node. In our case this will be a specified directory inside the container. Labels indicate that this node will run only when a job with specified labels is run, otherwise this node will not be used (also depends on the usage method in the next option). If the purpose is to use the node by default for every job, then leave it empty. Select a desired usage option. In launch methods, select \u201cLaunch agents via SSH\u201d In \u201cHost\u201d enter the ip address of the container which is 10.0.3.127 in our case. In \u201cCredentials\u201d, click Add and this will open another sub dialog for entering credentials information. Select the kind as \u201cUsername wih password\u201d. Leave other options as is and write the username and password of the container user, in our case the username will be user1 and password will be the password which was set for user1. \u201cID\u201d and \u201cDescription\u201d are optional. Click on \u201cAdd\u201d. Now as the credentials are added, click on the dropdown menu and select the username you just added. In our case it is user1 as the username added was user1. After this rest of the options need not to be changed if this node is going to be a default node. Click on \u201cSave\u201d. After complete setup, the configuration for this node will look something like this. If no issue is encountered during this whole setup, jenkins will take us to the log and after sometime (when the ssh connection is established) we can see \u201cAgent successfully connected and online\u201d at the bottom of the log as can be seen in the screenshot below. After this point, node will be able to run jobs from the container directory. Reference Links Documentation for LXC containers can be found at: https://linuxcontainers.org Details regarding Jenkins ssh agents can be found at: https://acloudguru.com/blog/engineering/adding-a-jenkins-agent-node","title":"Creating a Jenkins Node on LXC Container"},{"location":"Creating_Jenkins_Node_on_LXC/#creating-a-jenkins-node-on-lxc-container","text":"","title":"Creating a Jenkins Node on LXC Container"},{"location":"Creating_Jenkins_Node_on_LXC/#what-is-a-container","text":"A container is a virtualization method for isolating the applications (or even operating systems) from each other.","title":"What is a container"},{"location":"Creating_Jenkins_Node_on_LXC/#why-do-we-need-a-container-for-jenkins-node","text":"In Jenkins, node is a location where our jobs run. One user can use one node for all of his processes and multiple users may also use one node for all of their processes. In Jenkins freestyle project, we can use bash shell or windows command shell due to which there is a possibility to navigate anywhere in the server machine. This possibility can lead to various security and integrity issues for server administrators and also for other users using that webserver. So one must isolate each node and allocate each node to each user separately.","title":"Why do we need a container for Jenkins node"},{"location":"Creating_Jenkins_Node_on_LXC/#what-is-lxc-container","text":"LXC stands for Linux Containers. LXC is a package for linux operating systems and provides linux users with containers which may contain a whole linux operating system while also being lightweight than a virtual machine. More information regarding LXC can be found at https://linuxcontainers.org/lxc/introduction/ On ubuntu 20.04 one can install LXC using command [sudo] apt-get install lxc","title":"What is LXC Container"},{"location":"Creating_Jenkins_Node_on_LXC/#creating-a-container-with-lxc","text":"NOTE: Throughout this document, the name of the container will be my-container and the name of the user will be user1 . So wherever my-container is written, one may change the name to whatever one wants to give it.","title":"Creating a container with LXC"},{"location":"Creating_Jenkins_Node_on_LXC/#pre-requisites","text":"Before proceeding, it is important to mention that at the point of writing this document following are the specifications for linux kernel and distribution: Linux Kernel : 5.15.0-46-generic (can be checked on ubuntu by command uname -r ) Distribution : Ubuntu focal (20.04) (can be checked on ubuntu by command lsb_release -a ) By default linux users are not allowed to create any network device on the machine. For doing that, one must add uid and gid in the /etc/lxc/lxc-usernet . The uid and gid of the user you want to use can be found in the files /etc/uid and /etc/gid respectively. After getting the gid and uid of the user you want to allow for creating the network devices, one must go to /etc/lxc/lxc-usernet and add the uid and gid in the following format: <username> veth lxcbr0 10 e.g. jenkins veth lxcbr0 10 In above example jenkins is the username, veth is the command used for creating the bridges between virtual network devices and physical network devices (you will be able to see that ethernet device in our container will be lxcbr0 ) and lxbr0 is the network device we want to create. \u201810\u2019 represents the number of devices we want to create using our specified user. According lxc documentation, in ubuntu 20.04 an additional command is required before creating lxc container: export DOWNLOAD_KEYSERVER=\"hkp://keyserver.ubuntu.com\"","title":"Pre-requisites"},{"location":"Creating_Jenkins_Node_on_LXC/#creating-image","text":"After this, one can create container using following command systemd-run --unit=my-unit --user --scope -p \"Delegate=yes\" -- lxc-create -t download -n my-container This runs lxc container with unit name my-unit , container name my-container and delegates a control group (also known as the cgroup ) which is needed for resource allocation for processes in container. This will output the list of available linux distributions in which one may want to run the container and will prompt for Distribution as shown in the following image. After selecting the suitable distribution, release and architecture (which is also mentioned in the table), the container may be created as shown in the image below: Next thing is to start a container which will change its state from STOPPED to RUNNING using the following command. lxc-start -n my-container Above command will have no output if it succeeds. The state of the container can be checked using the following command. lxc-info -n my-container After starting the container, its state will be set as running and is just like turning a linux machine ON. From this point onwards, if one wants to use the machine in the terminal then use the following command and this will switch the terminal to the root of the container. lxc-attach my-container Now the container is ready to be used and is completely isolated from the host machine.","title":"Creating image"},{"location":"Creating_Jenkins_Node_on_LXC/#using-ssh-to-access-container-with-username-and-password","text":"The above mentioned method can be used to attach the host machine terminal to the container and this can be used to access the container. But if one wants to access the machine remotely then one possible and well-known method will be to configure and use SSH on the container. As it is an out of the box linux distro and only the root user is present, so first create another user using the following command and then manage its permissions for /home folder . #Considering you remain the root user for execution of all the following #commands useradd user1 cd /home mkdir user1 #Creating home directory for user1 chown user1:user1 user1 #Giving ownership of home directory to new user #For adding the same shell and bashrc configurations for new user, use #following #command, otherwise the shell will be very basic for new user and will be #very inconvenient to use. usermod -s /bin/bash user1 For the sake of simplicity of this document the name used for the new user is user1 here. (You may want to set the password for user1 by executing the passwd command in root.) At this point user1 is not in sudoers. For adding it to the sudoers, it must be added in the sudo group which can be done by using the following command. usermod -a -G sudo user1 Now switch to the user1 using the following command. su - user Now install openssh-server for configuring the ssh on user1. sudo apt install openssh-server After that one must find the ip of the container we are using, for this either run following command while in container with user1, sudo apt-install net-tools #Because ifconfig is part of net-tools which are by default not installed on new #container Ifconfig -a OR open a new terminal in the host machine and execute the following command. lxc-info my-container -iH So, the ip of the container is 10.0.3.127 . The command for establishing an ssh connection to a remote machine is mentioned below and it will ask for the password of the remote machine which is actually the container in our case. ssh user1@10.0.3.127 After entering the password, terminal will switch to the container\u2019s user1 as can be seen in the following image.","title":"Using SSH to access container with username and password"},{"location":"Creating_Jenkins_Node_on_LXC/#using-ssh-to-access-jenkins-agents-on-the-container","text":"First install some initial dependencies (git, jdk, jre) on the containers for running agents on the container. sudo apt update sudo apt install default-jdk default-jre git maven Now login to jenkins with administrator privileges and create a node in it from Dashboard > Manage Jenkins > Nodes and press + New Node . Enter a name for the node and select the desirable node type. For this documentation, the node will be a permanent type and the name will be temp_node . After this click on Create which will display the configuration page of the node. Write the description of the node as desired. Number of executors means number of threads running at a time (it will be better to set it to the number of processors present on the machine which is running this node). Remote root directory will be the directory where the jobs will run by default on the node. In our case this will be a specified directory inside the container. Labels indicate that this node will run only when a job with specified labels is run, otherwise this node will not be used (also depends on the usage method in the next option). If the purpose is to use the node by default for every job, then leave it empty. Select a desired usage option. In launch methods, select \u201cLaunch agents via SSH\u201d In \u201cHost\u201d enter the ip address of the container which is 10.0.3.127 in our case. In \u201cCredentials\u201d, click Add and this will open another sub dialog for entering credentials information. Select the kind as \u201cUsername wih password\u201d. Leave other options as is and write the username and password of the container user, in our case the username will be user1 and password will be the password which was set for user1. \u201cID\u201d and \u201cDescription\u201d are optional. Click on \u201cAdd\u201d. Now as the credentials are added, click on the dropdown menu and select the username you just added. In our case it is user1 as the username added was user1. After this rest of the options need not to be changed if this node is going to be a default node. Click on \u201cSave\u201d. After complete setup, the configuration for this node will look something like this. If no issue is encountered during this whole setup, jenkins will take us to the log and after sometime (when the ssh connection is established) we can see \u201cAgent successfully connected and online\u201d at the bottom of the log as can be seen in the screenshot below. After this point, node will be able to run jobs from the container directory.","title":"Using SSH to access Jenkins agents on the container"},{"location":"Creating_Jenkins_Node_on_LXC/#reference-links","text":"Documentation for LXC containers can be found at: https://linuxcontainers.org Details regarding Jenkins ssh agents can be found at: https://acloudguru.com/blog/engineering/adding-a-jenkins-agent-node","title":"Reference Links"},{"location":"Creating_jenkinsfile/","text":"Creating a Jenkinsfile What is a Jenkinsfile A Jenkinsfile is a Continuous Integration (CI) pipeline script which is written Java. It describes various stages (and possibly steps) which are executed in the defined pattern. These stages can be written in bash or they can be written in Java itself. Mainly Jenkinsfiles are of two types: Scripted: Only contains stages Declarative: Contains stages as well as steps This documentation will cover how to create a jenkinsfile in bash script and run it on various compute instances (which are known as Nodes in jenkins). Jenkins Node In jenkins, node represents a compute instance. In simple words, it is the platform on which our job build is going to run. Jenkins Master There is a jenkins Master node which is actually the compute instance on which Jenkins is installed. It is the node which schedules builds on runners. For security reason, no job is allowed to run on this node. Jenkins Slave Jenkins slave nodes are the compute instances on which our job builds run safely. They may be attached with jenkins master via hardware or they may be connected through remote SSH connection. Jenkinsfile written in Bash Simple Hello World Jenkinsfile In Cloud-V, all the platforms are running Linux operating system, so the jenkinsfile should be written in bash. Following script is an example of how can we run a bash script in scripted pipeline Jenkinsfile. node{ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } } The keyword sh is used to specify a shell script As there is nothing mentioned with node , so the script will run job build on any available compute instance. Jenkinsfile for a Specific Node In previous script, the jenkinsfile would run on any compute instances which are available. But in case if someone wants to run a job build on specific node, then a compute instance name must be specified with keyword node . The following script is an example of running above Hello World program on node named hifive_unleashed . node('hifive_unleashed'){ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } } Jenkinsfile for Cross-Platform Compilation and Execution Cloud-V supports cross-compilation and execution on emulated RISC-V compute instances. Following tools help in cross compilation and cross-platfrom execution: RISC-V GNU Toolchain QEMU user mode QEMU System (with Linux installed) An example pipeline script is given below in scripted pipeline. node('x86_runner2'){ checkout scm //Getting content of this repo stage('*** Compilation Phase ***') { // for display purposes //Compiling helloworld.c using bash commands sh '''#!/bin/bash gcc -g ./helloworld.c -o helloworld.out riscv64-unknown-linux-gnu-gcc ./helloworld.c -o helloworld_riscv_compiled.out //Cross compiling for RISC-V ''' } stage (' *** Running Binaries ***'){ sh '''#!/bin/bash ./helloworld.out qemu-riscv64 -L $RISCV_SYSROOT helloworld_riscv_compiled.out //Running executable on RISC-V emulated platform ''' } } The equivalent declarative pipeline is as follows: pipeline { agent {label \"x86_runner2\"} stages { stage('Clone Repository') { steps('delegate'){ checkout scm //Clones the repository on the local machine } } stage ('Compilation Phase'){ steps{ sh '''#!/bin/bash gcc -g ./helloworld.c -o helloworld.out ''' sh '''#!/bin/bash riscv64-unknown-linux-gnu-gcc ./helloworld.c -o helloworld_riscv_compiled.out ''' } } stage ('Running Binaries'){ steps { sh ''' #!/bin/bash ./helloworld.out ''' sh'''#!/bin/bash qemu-riscv64 -L $RISCV_SYSROOT helloworld_riscv_compiled.out ''' } } } } Reference Links https://www.jenkins.io/doc/book/pipeline/syntax/","title":"Creating a Jenkinfile"},{"location":"Creating_jenkinsfile/#creating-a-jenkinsfile","text":"","title":"Creating a Jenkinsfile"},{"location":"Creating_jenkinsfile/#what-is-a-jenkinsfile","text":"A Jenkinsfile is a Continuous Integration (CI) pipeline script which is written Java. It describes various stages (and possibly steps) which are executed in the defined pattern. These stages can be written in bash or they can be written in Java itself. Mainly Jenkinsfiles are of two types: Scripted: Only contains stages Declarative: Contains stages as well as steps This documentation will cover how to create a jenkinsfile in bash script and run it on various compute instances (which are known as Nodes in jenkins).","title":"What is a Jenkinsfile"},{"location":"Creating_jenkinsfile/#jenkins-node","text":"In jenkins, node represents a compute instance. In simple words, it is the platform on which our job build is going to run.","title":"Jenkins Node"},{"location":"Creating_jenkinsfile/#jenkins-master","text":"There is a jenkins Master node which is actually the compute instance on which Jenkins is installed. It is the node which schedules builds on runners. For security reason, no job is allowed to run on this node.","title":"Jenkins Master"},{"location":"Creating_jenkinsfile/#jenkins-slave","text":"Jenkins slave nodes are the compute instances on which our job builds run safely. They may be attached with jenkins master via hardware or they may be connected through remote SSH connection.","title":"Jenkins Slave"},{"location":"Creating_jenkinsfile/#jenkinsfile-written-in-bash","text":"","title":"Jenkinsfile written in Bash"},{"location":"Creating_jenkinsfile/#simple-hello-world-jenkinsfile","text":"In Cloud-V, all the platforms are running Linux operating system, so the jenkinsfile should be written in bash. Following script is an example of how can we run a bash script in scripted pipeline Jenkinsfile. node{ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } } The keyword sh is used to specify a shell script As there is nothing mentioned with node , so the script will run job build on any available compute instance.","title":"Simple Hello World Jenkinsfile"},{"location":"Creating_jenkinsfile/#jenkinsfile-for-a-specific-node","text":"In previous script, the jenkinsfile would run on any compute instances which are available. But in case if someone wants to run a job build on specific node, then a compute instance name must be specified with keyword node . The following script is an example of running above Hello World program on node named hifive_unleashed . node('hifive_unleashed'){ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } }","title":"Jenkinsfile for a Specific Node"},{"location":"Creating_jenkinsfile/#jenkinsfile-for-cross-platform-compilation-and-execution","text":"Cloud-V supports cross-compilation and execution on emulated RISC-V compute instances. Following tools help in cross compilation and cross-platfrom execution: RISC-V GNU Toolchain QEMU user mode QEMU System (with Linux installed) An example pipeline script is given below in scripted pipeline. node('x86_runner2'){ checkout scm //Getting content of this repo stage('*** Compilation Phase ***') { // for display purposes //Compiling helloworld.c using bash commands sh '''#!/bin/bash gcc -g ./helloworld.c -o helloworld.out riscv64-unknown-linux-gnu-gcc ./helloworld.c -o helloworld_riscv_compiled.out //Cross compiling for RISC-V ''' } stage (' *** Running Binaries ***'){ sh '''#!/bin/bash ./helloworld.out qemu-riscv64 -L $RISCV_SYSROOT helloworld_riscv_compiled.out //Running executable on RISC-V emulated platform ''' } } The equivalent declarative pipeline is as follows: pipeline { agent {label \"x86_runner2\"} stages { stage('Clone Repository') { steps('delegate'){ checkout scm //Clones the repository on the local machine } } stage ('Compilation Phase'){ steps{ sh '''#!/bin/bash gcc -g ./helloworld.c -o helloworld.out ''' sh '''#!/bin/bash riscv64-unknown-linux-gnu-gcc ./helloworld.c -o helloworld_riscv_compiled.out ''' } } stage ('Running Binaries'){ steps { sh ''' #!/bin/bash ./helloworld.out ''' sh'''#!/bin/bash qemu-riscv64 -L $RISCV_SYSROOT helloworld_riscv_compiled.out ''' } } } }","title":"Jenkinsfile for Cross-Platform Compilation and Execution"},{"location":"Creating_jenkinsfile/#reference-links","text":"https://www.jenkins.io/doc/book/pipeline/syntax/","title":"Reference Links"},{"location":"Installing_ssl_certificates_new/","text":"Configure letsencrypt with jenkins SSL certificates allow a website to run on HTTPS protocol which makes sure that data transfer between user and server cannot be intercepted between them. When using HTTPS protocol the data transfer is encrypted between user and server being used. NOTE: Keep the fact in mind that letsencrypt does not generate certificates for bare IP. It needs a domain name. Installing SSL certificates with letsencrypt In unix, letsencrypt package is called certbot . This can be installed using following command: sudo apt install certbot Here standalone mode will be used for generating certificates which authenticates the machine's ownership by hosting a temporary server on port 80. This is because ports less than 1024 are privileged and require root/sudo access. So make sure that port 80 is open in firewall and there is no application already running on it. Also if this process is being done on container, make sure port 80 is forwarded properly. One can also use webroot mode to generate certificates. See this link for more information. Use following command to generate certificate files and keys in /etc/letsencrypt/live/your.domain.name/ certbot certonly --standalone -d your.domain.name This will produce cert.pem , fullchain.pem and privkey.pem . Copy these files to location where .war of jenkins is located. Make sure to change the permission from root to jenkins' user. After that, use following command to convert certificate files to pkcs12 format. openssl pkcs12 -inkey privkey.pem -in fullchain.pem -export -out keys.pkcs12 keytool -importkeystore -srckeystore keys.pkcs12 -srcstoretype pkcs12 -destkeystore keystore This will ask for a password. Here it will be denoted as <password> . Use following command to start jenkins server with generated SSL certificates. java -jar jenkins.war --httpPort=-1 --httpsPort=<your_port> --httpsKeyStore=keystore --httpsKeyStorePassword=<password> After this, go to browser and type your.domain.name:<your_port> to start jenkins with https protocol.","title":"Configure `letsencrypt` with jenkins"},{"location":"Installing_ssl_certificates_new/#configure-letsencrypt-with-jenkins","text":"SSL certificates allow a website to run on HTTPS protocol which makes sure that data transfer between user and server cannot be intercepted between them. When using HTTPS protocol the data transfer is encrypted between user and server being used. NOTE: Keep the fact in mind that letsencrypt does not generate certificates for bare IP. It needs a domain name.","title":"Configure letsencrypt with jenkins"},{"location":"Installing_ssl_certificates_new/#installing-ssl-certificates-with-letsencrypt","text":"In unix, letsencrypt package is called certbot . This can be installed using following command: sudo apt install certbot Here standalone mode will be used for generating certificates which authenticates the machine's ownership by hosting a temporary server on port 80. This is because ports less than 1024 are privileged and require root/sudo access. So make sure that port 80 is open in firewall and there is no application already running on it. Also if this process is being done on container, make sure port 80 is forwarded properly. One can also use webroot mode to generate certificates. See this link for more information. Use following command to generate certificate files and keys in /etc/letsencrypt/live/your.domain.name/ certbot certonly --standalone -d your.domain.name This will produce cert.pem , fullchain.pem and privkey.pem . Copy these files to location where .war of jenkins is located. Make sure to change the permission from root to jenkins' user. After that, use following command to convert certificate files to pkcs12 format. openssl pkcs12 -inkey privkey.pem -in fullchain.pem -export -out keys.pkcs12 keytool -importkeystore -srckeystore keys.pkcs12 -srcstoretype pkcs12 -destkeystore keystore This will ask for a password. Here it will be denoted as <password> . Use following command to start jenkins server with generated SSL certificates. java -jar jenkins.war --httpPort=-1 --httpsPort=<your_port> --httpsKeyStore=keystore --httpsKeyStorePassword=<password> After this, go to browser and type your.domain.name:<your_port> to start jenkins with https protocol.","title":"Installing SSL certificates with letsencrypt"},{"location":"Multinode_Pipelines/","text":"Multinode Pipelines One can create multinode pipelines in jenkins freestyle pipeline job as well as in jenkins native pipeline job. In such a pipeline, different stages of the pipeline can run on separate nodes. The jenkins native pipeline job can have two types. Scripted Pipeline Declarative pipeline For the sake of this documentation, two nodes are used: container-node and container-node2 Label In jenkins, label specifies where the job or a stage of the job can run. In jenkins, a label can be explicitly added in the node's configuration so that each time that label is mentioned in a jenkins job, that specific node is used for building the job, or the name of the node can also be used as label in case if no label is added in the node. Creating multinode pipelines in Jenkins native pipeline job Scripted Pipeline For creating a multinode pipeline with jenkins native scripted pipeline job, jenkinsfile can be tweaked. The keyword node can be used to specify the node in which the stages are going to run and this keyword can also be used in between stages. Following screenshot indicates a code in which first stage runs on node named container-node . While the second node runs on node named container-node2 . node ('container-node') { stage ('*** Creating a directory in container-node ***'){ sh '''#!/bin/bash mkdir newdir_container-node-$RANDOM ''' } stage ('*** Creating a directory in container-node2'){ node ('container-node2'){ sh'''#!/bin/bash mkdir newdir_container-node2-$RANDOM ''' } } } Declarative pipeline For a declarative pipeline the keyword label can be used in the agent block. This can either be done at the start of the pipeline after the keyword pipeline or it can be used inside the stages. The following code builds two stages each of which is built in separate node. The keyword none with agent means that the agent is not specified globally for each stage and it should be specified inside each stage. pipeline { agent none // Means no agent specified. This means each node will specify its own agent stages { stage('container-node') { agent{ label \"container-node\" //Selecting container-node for this stage } steps { sh '''#!/bin/bash echo 'Hello container-node' mkdir \"newdir-container-node-$RANDOM\" ''' } } stage('container-node2'){ agent{ label \"container-node2\" //Selecting container-node2 for this stage } steps{ sh'''#!/bin/bash echo ''Hello container-node2 mkdir \"newdir-container-node2-$RANDOM\" ''' } } } } Creating multinode pipelines using Jenkins freestyle jobs Jenkins freestyle jobs can be combined together by mentioning post-build jobs in the freestyle job settings. Freestyle jobs are customizable and offer more options than jenkins native pipeline jobs. Each job represents a stage and each stage has separate settings. One can use jenkins freestyle jobs to run on a separate node by selecting the option Restrict where this project can be run in the General section of the job's configuration. In the Label Expression , the node's name can be mentioned in which to run the job. The following image shows the option from job's configuration. This can be done in all the job's configuration for the specified node.","title":"Multinode Pipelines"},{"location":"Multinode_Pipelines/#multinode-pipelines","text":"One can create multinode pipelines in jenkins freestyle pipeline job as well as in jenkins native pipeline job. In such a pipeline, different stages of the pipeline can run on separate nodes. The jenkins native pipeline job can have two types. Scripted Pipeline Declarative pipeline For the sake of this documentation, two nodes are used: container-node and container-node2","title":"Multinode Pipelines"},{"location":"Multinode_Pipelines/#label","text":"In jenkins, label specifies where the job or a stage of the job can run. In jenkins, a label can be explicitly added in the node's configuration so that each time that label is mentioned in a jenkins job, that specific node is used for building the job, or the name of the node can also be used as label in case if no label is added in the node.","title":"Label"},{"location":"Multinode_Pipelines/#creating-multinode-pipelines-in-jenkins-native-pipeline-job","text":"","title":"Creating multinode pipelines in Jenkins native pipeline job"},{"location":"Multinode_Pipelines/#scripted-pipeline","text":"For creating a multinode pipeline with jenkins native scripted pipeline job, jenkinsfile can be tweaked. The keyword node can be used to specify the node in which the stages are going to run and this keyword can also be used in between stages. Following screenshot indicates a code in which first stage runs on node named container-node . While the second node runs on node named container-node2 . node ('container-node') { stage ('*** Creating a directory in container-node ***'){ sh '''#!/bin/bash mkdir newdir_container-node-$RANDOM ''' } stage ('*** Creating a directory in container-node2'){ node ('container-node2'){ sh'''#!/bin/bash mkdir newdir_container-node2-$RANDOM ''' } } }","title":"Scripted Pipeline"},{"location":"Multinode_Pipelines/#declarative-pipeline","text":"For a declarative pipeline the keyword label can be used in the agent block. This can either be done at the start of the pipeline after the keyword pipeline or it can be used inside the stages. The following code builds two stages each of which is built in separate node. The keyword none with agent means that the agent is not specified globally for each stage and it should be specified inside each stage. pipeline { agent none // Means no agent specified. This means each node will specify its own agent stages { stage('container-node') { agent{ label \"container-node\" //Selecting container-node for this stage } steps { sh '''#!/bin/bash echo 'Hello container-node' mkdir \"newdir-container-node-$RANDOM\" ''' } } stage('container-node2'){ agent{ label \"container-node2\" //Selecting container-node2 for this stage } steps{ sh'''#!/bin/bash echo ''Hello container-node2 mkdir \"newdir-container-node2-$RANDOM\" ''' } } } }","title":"Declarative pipeline"},{"location":"Multinode_Pipelines/#creating-multinode-pipelines-using-jenkins-freestyle-jobs","text":"Jenkins freestyle jobs can be combined together by mentioning post-build jobs in the freestyle job settings. Freestyle jobs are customizable and offer more options than jenkins native pipeline jobs. Each job represents a stage and each stage has separate settings. One can use jenkins freestyle jobs to run on a separate node by selecting the option Restrict where this project can be run in the General section of the job's configuration. In the Label Expression , the node's name can be mentioned in which to run the job. The following image shows the option from job's configuration. This can be done in all the job's configuration for the specified node.","title":"Creating multinode pipelines using Jenkins freestyle jobs"},{"location":"Software_Developer_Guide/","text":"Software Developer Guide for RISC-V CI A software developer is the end-user who will develop or build his/her projects on RISC-V CI infrastructure. This guide will cover all the things a software developer needs to create a project based on Cloud-V Continuous Integration (CI). Pre-requisites GitHub account. GitHub project repository with owner rights. Getting an account for Cloud-V Fill out this google form with all the required information for getting an account on Cloud-V. After this we will get back to you with login credentials. Setting up cloud-v-pipeline inside github project repository Cloud-V will need a cloud-v-pipeline written with jenkinsfile pipeline syntax to start execution of tests/checks (see link ). This pipeline will contain all the stages (and may be steps) of a CI/CD pipeline. This pipeline can be scripted pipeline which will only have stages or it can also be declarative pipeline which may also have steps inside stages. A simple scripted Helloworld pipeline in linux is as follows: node{ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } } Upon execution of such a pipeline, the console output can be viewed as follows. Note: This cloud-v-pipeline should remain same in all the branches and pull requests. Setting credentials for webhook Cloud-V supports webhooks which can trigger the job from external sources such as GitHub. They work in a way such that, if a specified branch is committed or if a pull request is created, the specified job build starts running depending upon the trigger event which is set in build's configuration in Cloud-V. This process requires access token of the repository CREATED BY OWNER OF REPOSITORY on which the webhook is to be set. These credentials can be safely added to Cloud-V without anyone (even administrator) seeing the passwords as follows. Obtaining github access token for repository Navigate to the dashboard of your github account and click on the your github profile picture on the top-right corner on dashboard. Then click on the \"Settings\" from the list. From the left option bar in Settings scroll down and click on \"Developer settings\". Once there, click on \"Personal access tokens\", then click on \"Fine-grained tokens\" from the dropdown list and after that click on \"Generate new token\". This will open the page for setting up new access token. Follow following steps for creating a token: Give your token a meaningful name under \"Token name\" Set expiration date in \"Expiration\" depending upon how long you would like your repository to be integrated with Cloud-V (think of a meaningful upper bound) The \"Resource owner\" should be the owner of the repository who can access all kinds of settings of the repository Under \"Repository access\", check \"Only select repositories\" and then select the repository for which you would like to create the token Under \"Permissions\" section, expand \"Repository Permissions\" and give the following two permissions: \"Read and write\" access to \"Commit statuses\" (Because after the CI has run, Cloud-V will be able to set the status of the commit accordingly) \"Read and write\" access to \"Webhooks\" (Read permission for the webhook is required for reading the incoming pull request. Write permission is required if you want Cloud-V to set the webhook for you instead of you going through the repository settings and setting it up) IMPORTANT NOTE: If you have decided to create a webhook yourself or have already created one, then Cloud-V will not be able to manage the settings for you, proceed to following section Configuring repository webhook (Optional) You can skip this step if you have given webhook read and write permission in your repository token settings in above step and havent configured any webhook yourself In GitHub, Go to repository settings which you want to integrate for Cloud-V. Go to Webhooks Click on Add webhook Add Payload URL as https://cloud-v.co:8443/ghprbhook/ Select content type as application/x-www-form-urlencoded Check Enable SSL verification In the section Which events would you like to trigger this webhook? check Let me select individual events and check Pul requests as individual events and dont check any other permission. Webhook settings will look something like this: Configurations inside Cloud-V Note: Currently users are not able to see or modify pipeline build configuration inside Jenkins, that is currently managed by administrator. Users are requested to inform administrator about how they want their pipeline configured. We will provide you with Cloud-V credentials on the provided email. Login with provided credentials. Click on the Credentials in the left menu. This will take you to the credentials page. Scroll down to the Stores scoped to Jenkins and click on the System as shown in the image. Click on Global credentials (unrestricted) . Click on Add Credentials . This will take you to the New Credentials page. Select Kind as Secret text . Select Scope as Global (Jenkins, nodes, items, all child items etc) . Enter Secret as GitHub personal authentication token (PAT) which can be acquired from Github account settings. Enter a unique ID . Description can be left empty. But it is recommended to give a suitable but careful description by which administrator will be able to identify and use these credentials to set up github webhook. Select Create . This process will look something like this. Now credentials will be available in the credentials list and will be shown to you as well as administrator as shown in the image below. This will create an option in configurations for using these credentials in github webhook without changing or viewing them. Note the credentials ID (as shown in the image below) and email it to the same administrator email on which you received the credentials. It is important that administrator knows the credentials ID because he will use it in the job build configurations. Note: Please make sure to inform the administrator via email that you have added the credentials in jenkins. Also, send administrator the ID of credentials via email. Requirements for administrator After the above setup is complete from software developer's side, developer will need to provide the administrator with following information. Dependencies for running the project which can be packages which are needed to install in the RISC-V CI environment by administrator. Events for triggering the job build. URL of GitHub repository. Path and name of Jenkinsfile on the provided GitHub repository. Any additional information which should be given for successful execution of job builds.","title":"Getting Started"},{"location":"Software_Developer_Guide/#software-developer-guide-for-risc-v-ci","text":"A software developer is the end-user who will develop or build his/her projects on RISC-V CI infrastructure. This guide will cover all the things a software developer needs to create a project based on Cloud-V Continuous Integration (CI).","title":"Software Developer Guide for RISC-V CI"},{"location":"Software_Developer_Guide/#pre-requisites","text":"GitHub account. GitHub project repository with owner rights.","title":"Pre-requisites"},{"location":"Software_Developer_Guide/#getting-an-account-for-cloud-v","text":"Fill out this google form with all the required information for getting an account on Cloud-V. After this we will get back to you with login credentials.","title":"Getting an account for Cloud-V"},{"location":"Software_Developer_Guide/#setting-up-cloud-v-pipeline-inside-github-project-repository","text":"Cloud-V will need a cloud-v-pipeline written with jenkinsfile pipeline syntax to start execution of tests/checks (see link ). This pipeline will contain all the stages (and may be steps) of a CI/CD pipeline. This pipeline can be scripted pipeline which will only have stages or it can also be declarative pipeline which may also have steps inside stages. A simple scripted Helloworld pipeline in linux is as follows: node{ stage('*** Phase 1 ***') { //Using bash commands sh '''#!/bin/bash echo \"Hello World !\\n\" ''' } } Upon execution of such a pipeline, the console output can be viewed as follows. Note: This cloud-v-pipeline should remain same in all the branches and pull requests.","title":"Setting up cloud-v-pipeline inside github project repository"},{"location":"Software_Developer_Guide/#setting-credentials-for-webhook","text":"Cloud-V supports webhooks which can trigger the job from external sources such as GitHub. They work in a way such that, if a specified branch is committed or if a pull request is created, the specified job build starts running depending upon the trigger event which is set in build's configuration in Cloud-V. This process requires access token of the repository CREATED BY OWNER OF REPOSITORY on which the webhook is to be set. These credentials can be safely added to Cloud-V without anyone (even administrator) seeing the passwords as follows.","title":"Setting credentials for webhook"},{"location":"Software_Developer_Guide/#obtaining-github-access-token-for-repository","text":"Navigate to the dashboard of your github account and click on the your github profile picture on the top-right corner on dashboard. Then click on the \"Settings\" from the list. From the left option bar in Settings scroll down and click on \"Developer settings\". Once there, click on \"Personal access tokens\", then click on \"Fine-grained tokens\" from the dropdown list and after that click on \"Generate new token\". This will open the page for setting up new access token. Follow following steps for creating a token: Give your token a meaningful name under \"Token name\" Set expiration date in \"Expiration\" depending upon how long you would like your repository to be integrated with Cloud-V (think of a meaningful upper bound) The \"Resource owner\" should be the owner of the repository who can access all kinds of settings of the repository Under \"Repository access\", check \"Only select repositories\" and then select the repository for which you would like to create the token Under \"Permissions\" section, expand \"Repository Permissions\" and give the following two permissions: \"Read and write\" access to \"Commit statuses\" (Because after the CI has run, Cloud-V will be able to set the status of the commit accordingly) \"Read and write\" access to \"Webhooks\" (Read permission for the webhook is required for reading the incoming pull request. Write permission is required if you want Cloud-V to set the webhook for you instead of you going through the repository settings and setting it up) IMPORTANT NOTE: If you have decided to create a webhook yourself or have already created one, then Cloud-V will not be able to manage the settings for you, proceed to following section","title":"Obtaining github access token for repository"},{"location":"Software_Developer_Guide/#configuring-repository-webhook-optional","text":"You can skip this step if you have given webhook read and write permission in your repository token settings in above step and havent configured any webhook yourself In GitHub, Go to repository settings which you want to integrate for Cloud-V. Go to Webhooks Click on Add webhook Add Payload URL as https://cloud-v.co:8443/ghprbhook/ Select content type as application/x-www-form-urlencoded Check Enable SSL verification In the section Which events would you like to trigger this webhook? check Let me select individual events and check Pul requests as individual events and dont check any other permission. Webhook settings will look something like this:","title":"Configuring repository webhook (Optional)"},{"location":"Software_Developer_Guide/#configurations-inside-cloud-v","text":"Note: Currently users are not able to see or modify pipeline build configuration inside Jenkins, that is currently managed by administrator. Users are requested to inform administrator about how they want their pipeline configured. We will provide you with Cloud-V credentials on the provided email. Login with provided credentials. Click on the Credentials in the left menu. This will take you to the credentials page. Scroll down to the Stores scoped to Jenkins and click on the System as shown in the image. Click on Global credentials (unrestricted) . Click on Add Credentials . This will take you to the New Credentials page. Select Kind as Secret text . Select Scope as Global (Jenkins, nodes, items, all child items etc) . Enter Secret as GitHub personal authentication token (PAT) which can be acquired from Github account settings. Enter a unique ID . Description can be left empty. But it is recommended to give a suitable but careful description by which administrator will be able to identify and use these credentials to set up github webhook. Select Create . This process will look something like this. Now credentials will be available in the credentials list and will be shown to you as well as administrator as shown in the image below. This will create an option in configurations for using these credentials in github webhook without changing or viewing them. Note the credentials ID (as shown in the image below) and email it to the same administrator email on which you received the credentials. It is important that administrator knows the credentials ID because he will use it in the job build configurations. Note: Please make sure to inform the administrator via email that you have added the credentials in jenkins. Also, send administrator the ID of credentials via email.","title":"Configurations inside Cloud-V"},{"location":"Software_Developer_Guide/#requirements-for-administrator","text":"After the above setup is complete from software developer's side, developer will need to provide the administrator with following information. Dependencies for running the project which can be packages which are needed to install in the RISC-V CI environment by administrator. Events for triggering the job build. URL of GitHub repository. Path and name of Jenkinsfile on the provided GitHub repository. Any additional information which should be given for successful execution of job builds.","title":"Requirements for administrator"},{"location":"Tooling/","text":"Tools on Cloud-V Using Environment Modules Users can use environment modules to load different versions of same program. For using environment modules the pattern is as follows: module load <PACKAGENAME/VERSION> For example if you want to load python version 3.9.2 compiled for x86, you will need to use following command: module load python/3.9.2 For packages compiled for RISC-V architecture host, you will need to append _riscv to package name. For example, for python 3.8.15 compiled for RISC-V, following command will be used. module load python_riscv/3.8.15 Following are the tools and libraries available in Cloud-V. Tools on x86_runner1 and qemuusermode_runner1 node Tools which are mentioned for x86 architecture are able to run on x86_runner2 . Tools which are mentioned for RISC-V architecture are able to run on qemuusermode_runner1 . The packages which are supported for QEMU User mode can be used by normal commands once they are loaded. Here PACKAGE_NAME is the package which you want to run on QEMU user mode. Operating System: Debian 11 (bullseye) QEMU User Mode Version: 7.1.0 Tool Versions Installed from Host Architecture Environment Modules Support RISC-V GNU Linux Toolchain 12.2.0 source x86 N/A Git 2.3.0.2 source x86 N/A OpenJDK 19.0.1 apt x86 N/A GCC 10.4.0, 12.2.0 apt x86 Yes Python3 3.8.15, 3.9.2 source x86 Yes Python3 3.8.15 source RISC-V Yes zlib 1.2.13 source RISC-V N/A OpenSSL 1.1.1r source RISC-V Yes Ruby (without IRB) 3.2.0dev source RISC-V Yes Go 1.18.8 apt x86 N/A rustc 1.65.0 source RISC-V,x86 N/A Flex 2.6.4 apt x86 N/A Flex 2.6.4 source RISC-V yes Ninja 1.10.1-1 apt x86 N/A Ninja 1.12.0.git source RISC-V Yes Bison 3.7.5 apt x86 N/A Bison 3.8.2, 2.3 source RISC-V Yes clang 16.0.0 source RISC-V Yes autoconf 2.69 apt x86 N/A gperf 2.2.4 apt x86 N/A spike 1.1.1-dev source x86 Yes Verilator 4.038 apt x86 N/A riscv-pk 1.0.0-91-g573c858 source RISC-V Yes Sail (riscv_sim_RV64, riscv_sim_RV32) 0.5 source x86 Yes cmake 3.18.4 apt x86 N/A make 4.3 apt x86 N/A Tools on riscv64_runner1 node This is compute instance with 64-bit RISC-V Linux and it has all the packages ONLY for RISC-V architecture Operating System: Ubuntu 22.04.1 (jammy) QEMU Linux Version: 7.1.90 Tool Version Installed from Git 2.34.1 apt OpenJDK 19.0.1 apt GCC 11.3.0 apt Python3 3.10.6 apt zlib 1.2.11 apt OpenSSL 3.0.2 apt Ruby 3.0.2p107 apt Go 1.18.8 apt rustc 1.61.0 apt Flex 2.6.4 apt Ninja 1.10.1 apt Bison 3.8.2 apt autoconf 2.71 apt gperf 3.1 apt make 4.3 apt cmake 3.22.1 apt Tools on hifive_unleashed node This compute instance is Sifive's HiFive Unleased board and it has available packages ONLY for RISC-V architecture. Operating System: Fedora 32 (Rawhide) Tool Version Installed from Git 2.23.0 dnf OpenJDK 11 dnf GCC 9.2.1 dnf Python3 3.8.1 dnf OpenSSL 1.1.1d dnf Ruby 2.5.1p57 dnf Go 1.12.2 dnf rustc 1.66.0 dnf Flex 2.6.4 dnf Ninja 1.9.0 dnf Bison 3.4.1 dnf autoconf 2.69 dnf make 4.2.1 dnf cmake 3.14.5 dnf Tools on starfive_visionfive2 node This compute instance is Starfive's VisionFive 2 board and it has available packages ONLY for RISC-V architecture. Operating System: Debian Unstable (Bookworm) Tool Version Installed from Git 2.36.1 apt OpenJDK 17.0.3 apt GCC 11.3.0 apt Python3 3.8.1 apt OpenSSL 1.1.1f apt Ruby 3.0.4p208 apt Go 1.18.3 apt rustc 1.59.0 apt Flex 2.6.4 apt Ninja 1.11.0 apt Bison 3.8.2 apt autoconf 2.71 apt gperf 3.1 apt cmake 3.23.2 apt make 4.3 apt","title":"Tools available in Cloud-V"},{"location":"Tooling/#tools-on-cloud-v","text":"","title":"Tools on Cloud-V"},{"location":"Tooling/#using-environment-modules","text":"Users can use environment modules to load different versions of same program. For using environment modules the pattern is as follows: module load <PACKAGENAME/VERSION> For example if you want to load python version 3.9.2 compiled for x86, you will need to use following command: module load python/3.9.2 For packages compiled for RISC-V architecture host, you will need to append _riscv to package name. For example, for python 3.8.15 compiled for RISC-V, following command will be used. module load python_riscv/3.8.15 Following are the tools and libraries available in Cloud-V.","title":"Using Environment Modules"},{"location":"Tooling/#tools-on-x86_runner1-and-qemuusermode_runner1-node","text":"Tools which are mentioned for x86 architecture are able to run on x86_runner2 . Tools which are mentioned for RISC-V architecture are able to run on qemuusermode_runner1 . The packages which are supported for QEMU User mode can be used by normal commands once they are loaded. Here PACKAGE_NAME is the package which you want to run on QEMU user mode. Operating System: Debian 11 (bullseye) QEMU User Mode Version: 7.1.0 Tool Versions Installed from Host Architecture Environment Modules Support RISC-V GNU Linux Toolchain 12.2.0 source x86 N/A Git 2.3.0.2 source x86 N/A OpenJDK 19.0.1 apt x86 N/A GCC 10.4.0, 12.2.0 apt x86 Yes Python3 3.8.15, 3.9.2 source x86 Yes Python3 3.8.15 source RISC-V Yes zlib 1.2.13 source RISC-V N/A OpenSSL 1.1.1r source RISC-V Yes Ruby (without IRB) 3.2.0dev source RISC-V Yes Go 1.18.8 apt x86 N/A rustc 1.65.0 source RISC-V,x86 N/A Flex 2.6.4 apt x86 N/A Flex 2.6.4 source RISC-V yes Ninja 1.10.1-1 apt x86 N/A Ninja 1.12.0.git source RISC-V Yes Bison 3.7.5 apt x86 N/A Bison 3.8.2, 2.3 source RISC-V Yes clang 16.0.0 source RISC-V Yes autoconf 2.69 apt x86 N/A gperf 2.2.4 apt x86 N/A spike 1.1.1-dev source x86 Yes Verilator 4.038 apt x86 N/A riscv-pk 1.0.0-91-g573c858 source RISC-V Yes Sail (riscv_sim_RV64, riscv_sim_RV32) 0.5 source x86 Yes cmake 3.18.4 apt x86 N/A make 4.3 apt x86 N/A","title":"Tools on x86_runner1 and qemuusermode_runner1 node"},{"location":"Tooling/#tools-on-riscv64_runner1-node","text":"This is compute instance with 64-bit RISC-V Linux and it has all the packages ONLY for RISC-V architecture Operating System: Ubuntu 22.04.1 (jammy) QEMU Linux Version: 7.1.90 Tool Version Installed from Git 2.34.1 apt OpenJDK 19.0.1 apt GCC 11.3.0 apt Python3 3.10.6 apt zlib 1.2.11 apt OpenSSL 3.0.2 apt Ruby 3.0.2p107 apt Go 1.18.8 apt rustc 1.61.0 apt Flex 2.6.4 apt Ninja 1.10.1 apt Bison 3.8.2 apt autoconf 2.71 apt gperf 3.1 apt make 4.3 apt cmake 3.22.1 apt","title":"Tools on riscv64_runner1 node"},{"location":"Tooling/#tools-on-hifive_unleashed-node","text":"This compute instance is Sifive's HiFive Unleased board and it has available packages ONLY for RISC-V architecture. Operating System: Fedora 32 (Rawhide) Tool Version Installed from Git 2.23.0 dnf OpenJDK 11 dnf GCC 9.2.1 dnf Python3 3.8.1 dnf OpenSSL 1.1.1d dnf Ruby 2.5.1p57 dnf Go 1.12.2 dnf rustc 1.66.0 dnf Flex 2.6.4 dnf Ninja 1.9.0 dnf Bison 3.4.1 dnf autoconf 2.69 dnf make 4.2.1 dnf cmake 3.14.5 dnf","title":"Tools on hifive_unleashed node"},{"location":"Tooling/#tools-on-starfive_visionfive2-node","text":"This compute instance is Starfive's VisionFive 2 board and it has available packages ONLY for RISC-V architecture. Operating System: Debian Unstable (Bookworm) Tool Version Installed from Git 2.36.1 apt OpenJDK 17.0.3 apt GCC 11.3.0 apt Python3 3.8.1 apt OpenSSL 1.1.1f apt Ruby 3.0.4p208 apt Go 1.18.3 apt rustc 1.59.0 apt Flex 2.6.4 apt Ninja 1.11.0 apt Bison 3.8.2 apt autoconf 2.71 apt gperf 3.1 apt cmake 3.23.2 apt make 4.3 apt","title":"Tools on starfive_visionfive2 node"},{"location":"jenkins_gitlab_integration/","text":"Integrating GitLab with Jenkins This documentation will cover how to create an integration between jenkins and GitLab. This will allow users to trigger jenkins job when a merge request or a push is detected in GitLab. Pre-requisites GitLab plugin Git plugin GitLab repository with owner's credentials Configuring Jenkins System First jenkins needs to be configured. Go to Dashboard > Manage Jenkins > Configure System Scroll down to Gitlab section Check Enable authentication for '/project' end-point Enter a Connection name . Enter Gitlab host URL as https://gitlab.com/ . In case there is a different domain name, then enter there instead of above url. In Credentials , click on Add then click on Jenkins . In Kind , select GitLab API token . In API token , enter the gitlab personal access token (this will be obtained below while configuring GitLab). Click on Advanced . Click on Test Connection . If everything goes right, it should print success . Configuring GitLab Click on profile avatar in the top right. Click on Edit profile . Click on Access Tokens . Create a new personal access token and copy it (this is the GitLab API token used in above section Configuring Jenkins System ). Go to repository settings. On left-side pane, select Webhooks . Enter GitLab webhook URL (this is explained below in next section). Enter Secret Token (this is explained in the below section). Check desirable trigger options. Click Add webhook . Configuring Jenkins Job Create a jenkins job. On job configuration page, scroll down to Source Code Management . Select Git . In Credentials , add the owner credentials of GitLab repository. This will be Username and Password . Select the appropriate branch (generally it is main ). Scroll down to Build Triggers . Check Build when a change is pushed to GitLab . There will also be a GitLab webhook URL . This is needed in GitLab. This URL will be called as Webhook URL . Click on Advanced in the same option, then scroll down and generate a secret token. This token is also needed. This token will be called as Secret Token . Scroll down to Post-build Actions and select Publish build status to GitLab . Click on Apply and Save . Now whenever there will be a push (or whatever build trigger option is set in jenkins and gitlab webhook), specified jenkins job will be triggered.","title":"Integrating GitLab with Jenkins"},{"location":"jenkins_gitlab_integration/#integrating-gitlab-with-jenkins","text":"This documentation will cover how to create an integration between jenkins and GitLab. This will allow users to trigger jenkins job when a merge request or a push is detected in GitLab.","title":"Integrating GitLab with Jenkins"},{"location":"jenkins_gitlab_integration/#pre-requisites","text":"GitLab plugin Git plugin GitLab repository with owner's credentials","title":"Pre-requisites"},{"location":"jenkins_gitlab_integration/#configuring-jenkins-system","text":"First jenkins needs to be configured. Go to Dashboard > Manage Jenkins > Configure System Scroll down to Gitlab section Check Enable authentication for '/project' end-point Enter a Connection name . Enter Gitlab host URL as https://gitlab.com/ . In case there is a different domain name, then enter there instead of above url. In Credentials , click on Add then click on Jenkins . In Kind , select GitLab API token . In API token , enter the gitlab personal access token (this will be obtained below while configuring GitLab). Click on Advanced . Click on Test Connection . If everything goes right, it should print success .","title":"Configuring Jenkins System"},{"location":"jenkins_gitlab_integration/#configuring-gitlab","text":"Click on profile avatar in the top right. Click on Edit profile . Click on Access Tokens . Create a new personal access token and copy it (this is the GitLab API token used in above section Configuring Jenkins System ). Go to repository settings. On left-side pane, select Webhooks . Enter GitLab webhook URL (this is explained below in next section). Enter Secret Token (this is explained in the below section). Check desirable trigger options. Click Add webhook .","title":"Configuring GitLab"},{"location":"jenkins_gitlab_integration/#configuring-jenkins-job","text":"Create a jenkins job. On job configuration page, scroll down to Source Code Management . Select Git . In Credentials , add the owner credentials of GitLab repository. This will be Username and Password . Select the appropriate branch (generally it is main ). Scroll down to Build Triggers . Check Build when a change is pushed to GitLab . There will also be a GitLab webhook URL . This is needed in GitLab. This URL will be called as Webhook URL . Click on Advanced in the same option, then scroll down and generate a secret token. This token is also needed. This token will be called as Secret Token . Scroll down to Post-build Actions and select Publish build status to GitLab . Click on Apply and Save . Now whenever there will be a push (or whatever build trigger option is set in jenkins and gitlab webhook), specified jenkins job will be triggered.","title":"Configuring Jenkins Job"},{"location":"runner_specs/","text":"Specifications of compute instances in Cloud-V This document contains the specifications of the compute instances available for users to run builds in Cloud-V. The term \"Compute Instance\", can also be safely interchanged with the terms \"Build Executor\" and \"Runner\". Name String Architecture Cores Memory Compute Instance Type x86_runner1 (or) qemuusermode_runner1 x86_64 4 8GiB Hardware with application-level emulator x86_runner2 x86_64 1 512MiB Hardware dell5559 x86_64 4 8GiB Hardware rasp4-1 aarch64 4 4GiB Hardware riscv64_runner1 riscv64 2 2GiB QEMU System emulator sf1-1 riscv64 2 8GiB Hardware sf1-2 riscv64 2 8GiB Hardware sf1-3 riscv64 2 8GiB Hardware sf2-1 riscv64 4 8GiB Hardware sf2-2 riscv64 4 8GiB Hardware sf2-3 riscv64 4 8GiB Hardware sf2-4 riscv64 4 8GiB Hardware sf2-5 riscv64 4 8GiB Hardware unleashed1-1 riscv64 4 8GiB Hardware unleashed1-2 riscv64 4 8GiB Hardware Note: The qemuusermode_runner1 and x86_runner1 are one and the same runner. The purpose of creating two separate executors for same hardware is that x86_runner1 is supposed to be specifically for x86 architecture whereas qemuusermode_runner1 is specifically for the users who want to cross compile source code for riscv64 architecture and then use qemu-usermode to execute them. Nevertheless, the tooling available for x86_runner1 can also be used for qemuusermode_runner1","title":"Runners' Info"},{"location":"runner_specs/#specifications-of-compute-instances-in-cloud-v","text":"This document contains the specifications of the compute instances available for users to run builds in Cloud-V. The term \"Compute Instance\", can also be safely interchanged with the terms \"Build Executor\" and \"Runner\". Name String Architecture Cores Memory Compute Instance Type x86_runner1 (or) qemuusermode_runner1 x86_64 4 8GiB Hardware with application-level emulator x86_runner2 x86_64 1 512MiB Hardware dell5559 x86_64 4 8GiB Hardware rasp4-1 aarch64 4 4GiB Hardware riscv64_runner1 riscv64 2 2GiB QEMU System emulator sf1-1 riscv64 2 8GiB Hardware sf1-2 riscv64 2 8GiB Hardware sf1-3 riscv64 2 8GiB Hardware sf2-1 riscv64 4 8GiB Hardware sf2-2 riscv64 4 8GiB Hardware sf2-3 riscv64 4 8GiB Hardware sf2-4 riscv64 4 8GiB Hardware sf2-5 riscv64 4 8GiB Hardware unleashed1-1 riscv64 4 8GiB Hardware unleashed1-2 riscv64 4 8GiB Hardware Note: The qemuusermode_runner1 and x86_runner1 are one and the same runner. The purpose of creating two separate executors for same hardware is that x86_runner1 is supposed to be specifically for x86 architecture whereas qemuusermode_runner1 is specifically for the users who want to cross compile source code for riscv64 architecture and then use qemu-usermode to execute them. Nevertheless, the tooling available for x86_runner1 can also be used for qemuusermode_runner1","title":"Specifications of compute instances in Cloud-V"},{"location":"Cross_Compiling/Cross_compiling%20python3.8.15/","text":"Cross compiling python3.8.15 for riscv64 This document will include how to build python3.8.15 for riscv64 architecture while using build machine as x86_64. Building Python Get the python source code of python 3.8.15 in form of tarball from this link. Once a tarball is obtained, extract it and use following command in its root folder to configure it. # Here $PREFIX is the directory where the binaries are desired to be installed. ./configure --host=riscv64-unknown-linux-gnu --build=x86_64-linux-gnu --prefix=\"$PREFIX\" --disable-ipv6 ac_cv_file__dev_ptmx=no ac_cv_file__dev_ptc=no After the above command is executed, use following command to start the build. make -j$(nproc) Now to install binaries on the location where PREFIX, use following command. make install This will install binaries for python3.8.15 in the $PREFIX directory and it can be checked using qemu-riscv64 .","title":"Cross compiling python3.8.15 for `riscv64`"},{"location":"Cross_Compiling/Cross_compiling%20python3.8.15/#cross-compiling-python3815-for-riscv64","text":"This document will include how to build python3.8.15 for riscv64 architecture while using build machine as x86_64.","title":"Cross compiling python3.8.15 for riscv64"},{"location":"Cross_Compiling/Cross_compiling%20python3.8.15/#building-python","text":"Get the python source code of python 3.8.15 in form of tarball from this link. Once a tarball is obtained, extract it and use following command in its root folder to configure it. # Here $PREFIX is the directory where the binaries are desired to be installed. ./configure --host=riscv64-unknown-linux-gnu --build=x86_64-linux-gnu --prefix=\"$PREFIX\" --disable-ipv6 ac_cv_file__dev_ptmx=no ac_cv_file__dev_ptc=no After the above command is executed, use following command to start the build. make -j$(nproc) Now to install binaries on the location where PREFIX, use following command. make install This will install binaries for python3.8.15 in the $PREFIX directory and it can be checked using qemu-riscv64 .","title":"Building Python"},{"location":"Cross_Compiling/Cross_compiling_coremark/","text":"Cross-compiling Coremark Coremark is another benchmarking tool. Here coremark will be cross-compiled for riscv64-unknown-linux-gnu and will be run on qemu-riscv64 . The github source code commit at the time of build is eefc986ebd3452d6adde22eafaff3e5c859f29e4 and branch is main . Getting the source code Execute the following command to get the source code of coremark. git clone https://github.com/eembc/coremark.git Tweaking source files for riscv64-unknown-linux-gnu At the time of this documentation, linux is being used for this test. First of all core_portme.mak will be changed. Navigate to linux/ directory in source repository. Open core_portme.mak . Here a single line will be used to include core_portme.mak from posix directory. So, navigate to posix/ directory in source folder Open core_portme.mak in posix/ directory and do the following changes to variables here. Change CC?=cc to CC=riscv64-unknown-linux-gnu-gcc . Scroll down and change EXE=.exe to EXE= (it should be blank). Scroll down and change LD=gcc to LD=riscv64-unknown-linux-gnu-ld . As we are using qemu-riscv64 , so change RUN= to RUN=qemu-riscv64 -L \"$$RISCV_SYSROOT\" Save changes and exit this file. Now open core_portme.h and change #define USE_CLOCK 0 to #define USE_CLOCK 1 and save. Navigate to source directory of repository and execute following command make PORT_DIR=linux/ If everything went right, the output result will be stored in run1.log and run2.log and will be of the form as shown below. 2K validation run parameters for coremark. CoreMark Size : 666 Total ticks : 12368459 Total time (secs): 12.368459 Iterations/Sec : 8893.589735 Iterations : 110000 Compiler version : GCC12.2.0 Compiler flags : -O2 -DPERFORMANCE_RUN=1 -lrt Memory location : Please put data memory location here (e.g. code in flash, data on heap etc) seedcrc : 0x18f2 [0]crclist : 0xe3c1 [0]crcmatrix : 0x0747 [0]crcstate : 0x8d84 [0]crcfinal : 0x0956 Correct operation validated. See README.md for run and reporting rules.","title":"Cross-compiling Coremark"},{"location":"Cross_Compiling/Cross_compiling_coremark/#cross-compiling-coremark","text":"Coremark is another benchmarking tool. Here coremark will be cross-compiled for riscv64-unknown-linux-gnu and will be run on qemu-riscv64 . The github source code commit at the time of build is eefc986ebd3452d6adde22eafaff3e5c859f29e4 and branch is main .","title":"Cross-compiling Coremark"},{"location":"Cross_Compiling/Cross_compiling_coremark/#getting-the-source-code","text":"Execute the following command to get the source code of coremark. git clone https://github.com/eembc/coremark.git","title":"Getting the source code"},{"location":"Cross_Compiling/Cross_compiling_coremark/#tweaking-source-files-for-riscv64-unknown-linux-gnu","text":"At the time of this documentation, linux is being used for this test. First of all core_portme.mak will be changed. Navigate to linux/ directory in source repository. Open core_portme.mak . Here a single line will be used to include core_portme.mak from posix directory. So, navigate to posix/ directory in source folder Open core_portme.mak in posix/ directory and do the following changes to variables here. Change CC?=cc to CC=riscv64-unknown-linux-gnu-gcc . Scroll down and change EXE=.exe to EXE= (it should be blank). Scroll down and change LD=gcc to LD=riscv64-unknown-linux-gnu-ld . As we are using qemu-riscv64 , so change RUN= to RUN=qemu-riscv64 -L \"$$RISCV_SYSROOT\" Save changes and exit this file. Now open core_portme.h and change #define USE_CLOCK 0 to #define USE_CLOCK 1 and save. Navigate to source directory of repository and execute following command make PORT_DIR=linux/ If everything went right, the output result will be stored in run1.log and run2.log and will be of the form as shown below. 2K validation run parameters for coremark. CoreMark Size : 666 Total ticks : 12368459 Total time (secs): 12.368459 Iterations/Sec : 8893.589735 Iterations : 110000 Compiler version : GCC12.2.0 Compiler flags : -O2 -DPERFORMANCE_RUN=1 -lrt Memory location : Please put data memory location here (e.g. code in flash, data on heap etc) seedcrc : 0x18f2 [0]crclist : 0xe3c1 [0]crcmatrix : 0x0747 [0]crcstate : 0x8d84 [0]crcfinal : 0x0956 Correct operation validated. See README.md for run and reporting rules.","title":"Tweaking source files for riscv64-unknown-linux-gnu"},{"location":"Cross_Compiling/Cross_compiling_dhrystone/","text":"Cross-compiling dhrystone Dhrystone is a benchmarking tool. Here dhrystone will be compiled from source and run on qemu-riscv64 . Dhrystone is comparable to VAX 11/780 in a way that VAX 11/780 achieves 1757 dhrystones per second which is also referred to as 1 MIPS of VAX11/780. So number of dhrystones per seconds are obtained and then divided by 1757 to get MIPS. See this link for more details. Cross-compiling for riscv64-unknown-linux-gnu Get the source code of dhrystone using the command below git clone https://github.com/sifive/benchmark-dhrystone.git Navigate to root directory of repository and compile program with riscv64-unknown-linux-gnu-gcc instead of native gcc cd benchmark-dhrystone make CC=riscv64-unknown-linux-gnu-gcc Execute following command to execute dhrystone binary qemu-riscv64 -L $RISCV_SYSROOT ./dhrystone Note: You may want to tweak Makefile and dhry_1.c a little bit to get the correct results.","title":"Cross-compiling `dhrystone`"},{"location":"Cross_Compiling/Cross_compiling_dhrystone/#cross-compiling-dhrystone","text":"Dhrystone is a benchmarking tool. Here dhrystone will be compiled from source and run on qemu-riscv64 . Dhrystone is comparable to VAX 11/780 in a way that VAX 11/780 achieves 1757 dhrystones per second which is also referred to as 1 MIPS of VAX11/780. So number of dhrystones per seconds are obtained and then divided by 1757 to get MIPS. See this link for more details.","title":"Cross-compiling dhrystone"},{"location":"Cross_Compiling/Cross_compiling_dhrystone/#cross-compiling-for-riscv64-unknown-linux-gnu","text":"Get the source code of dhrystone using the command below git clone https://github.com/sifive/benchmark-dhrystone.git Navigate to root directory of repository and compile program with riscv64-unknown-linux-gnu-gcc instead of native gcc cd benchmark-dhrystone make CC=riscv64-unknown-linux-gnu-gcc Execute following command to execute dhrystone binary qemu-riscv64 -L $RISCV_SYSROOT ./dhrystone Note: You may want to tweak Makefile and dhry_1.c a little bit to get the correct results.","title":"Cross-compiling for riscv64-unknown-linux-gnu"},{"location":"Cross_Compiling/Cross_compiling_go/","text":"Cross compiling Go Go currenlty has support for riscv64 architecture. This document will cover how to compile go on x86 for riscv64 architecture. Note: Right now, go can be cross-compiled on x86 but it cannot be executed on x86 with qemu-riscv64 because it needs to execute goroot/pkg/tool/compile and qemu-riscv64 can only execute one binary at a time. Pre Requisites On ubuntu, following pre-requisites should be installed. Snap qemu-riscv64 (linux-user) Go source code is written in go. That means a go toolchain is needed to compile the source code (see link ). As this document cross-compiles the code, first of all install a go language on build machine. Use following command on ubuntu to install a go language compiler. sudo snap install go --classic After this, get the source code of go from following command. git clone https://go.googlesource.com/go goroot Now set the environment variable as follows. export GOROOT_BOOTSTRAP=/snap export GOARCH=riscv64 export GOOS=linux Navigate to goroot/src and execute following command. ./all.bash After this, an executable file will be located in folder goroot/bin/linux_riscv64 .","title":"Cross compiling `Go`"},{"location":"Cross_Compiling/Cross_compiling_go/#cross-compiling-go","text":"Go currenlty has support for riscv64 architecture. This document will cover how to compile go on x86 for riscv64 architecture. Note: Right now, go can be cross-compiled on x86 but it cannot be executed on x86 with qemu-riscv64 because it needs to execute goroot/pkg/tool/compile and qemu-riscv64 can only execute one binary at a time.","title":"Cross compiling Go"},{"location":"Cross_Compiling/Cross_compiling_go/#pre-requisites","text":"On ubuntu, following pre-requisites should be installed. Snap qemu-riscv64 (linux-user) Go source code is written in go. That means a go toolchain is needed to compile the source code (see link ). As this document cross-compiles the code, first of all install a go language on build machine. Use following command on ubuntu to install a go language compiler. sudo snap install go --classic After this, get the source code of go from following command. git clone https://go.googlesource.com/go goroot Now set the environment variable as follows. export GOROOT_BOOTSTRAP=/snap export GOARCH=riscv64 export GOOS=linux Navigate to goroot/src and execute following command. ./all.bash After this, an executable file will be located in folder goroot/bin/linux_riscv64 .","title":"Pre Requisites"},{"location":"Cross_Compiling/Cross_compiling_jdk/","text":"Cross-compiling JDK for riscv64-unknown-linux-gnu JDK is abbreviation of 'Java Development Kit'. It is used for compiling and executing java-based programs and applications. All the information regarding building jdk and relevant dependencies are given at https://github.com/openjdk/jdk/blob/master/doc/building.md Make sure to have riscv64-unknown-linux-gnu toolchain installed on machine. Getting source code The source code of jdk can be obtained using command below git clone https://github.com/openjdk/jdk.git Building the source code for First of all configure the source code using the command below bash configure --host=riscv64-unknown-linux-gnu --build=x86_64-linux-gnu --target=riscv64-unknown-linux-gnu --prefix=/home/ali/custom_installed/RISCV/jdk/967a28c3d85fdde6d5eb48aa0edd8f7597772469 --with-cups=/home/ali/custom_installed/cups --with-fontconfig=/home/ali/custom_installed/fontconfig/e291fda7d42e5d64379555097a066d9c2c4efce3 --x-includes=/usr/include --x-lib=/usr/lib","title":"Cross-compiling JDK for `riscv64-unknown-linux-gnu`"},{"location":"Cross_Compiling/Cross_compiling_jdk/#cross-compiling-jdk-for-riscv64-unknown-linux-gnu","text":"JDK is abbreviation of 'Java Development Kit'. It is used for compiling and executing java-based programs and applications. All the information regarding building jdk and relevant dependencies are given at https://github.com/openjdk/jdk/blob/master/doc/building.md Make sure to have riscv64-unknown-linux-gnu toolchain installed on machine.","title":"Cross-compiling JDK for riscv64-unknown-linux-gnu"},{"location":"Cross_Compiling/Cross_compiling_jdk/#getting-source-code","text":"The source code of jdk can be obtained using command below git clone https://github.com/openjdk/jdk.git","title":"Getting source code"},{"location":"Cross_Compiling/Cross_compiling_jdk/#building-the-source-code-for","text":"First of all configure the source code using the command below bash configure --host=riscv64-unknown-linux-gnu --build=x86_64-linux-gnu --target=riscv64-unknown-linux-gnu --prefix=/home/ali/custom_installed/RISCV/jdk/967a28c3d85fdde6d5eb48aa0edd8f7597772469 --with-cups=/home/ali/custom_installed/cups --with-fontconfig=/home/ali/custom_installed/fontconfig/e291fda7d42e5d64379555097a066d9c2c4efce3 --x-includes=/usr/include --x-lib=/usr/lib","title":"Building the source code for"},{"location":"Cross_Compiling/Cross_compiling_ninja-build/","text":"Cross-compiling ninja-build for RISC-V Ninja is a small build system with a focus on speed. It differs from other build systems in two major respects: it is designed to have its input files generated by a higher-level build system, and it is designed to run builds as fast as possible. This document will cover how to compile ninja to work on 64-bit RISC-V architecture. Getting source code Use following command to get source code of ninja-build and navigate to source directory. git clone git://github.com/ninja-build/ninja.git cd ninja git checkout release Create following cmake file inside the root directory of ninja-build repository. # the name of the target operating system set(CMAKE_SYSTEM_NAME Linux) # which compilers to use for C and C++ set(CMAKE_C_COMPILER riscv64-unknown-linux-gnu-gcc) set(CMAKE_CXX_COMPILER riscv64-unknown-linux-gnu-g++) # where is the target environment located set(CMAKE_FIND_ROOT_PATH /softwares/RISCV/riscv64-unknown-linux-gnu/50c1b734e889e5cbb88bcc7f14975ea9a1d0b936/sysroot ) # adjust the default behavior of the FIND_XXX() commands: # search programs in the host environment set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER) # search headers and libraries in the target environment set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY) set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)","title":"Cross-compiling ninja-build for RISC-V"},{"location":"Cross_Compiling/Cross_compiling_ninja-build/#cross-compiling-ninja-build-for-risc-v","text":"Ninja is a small build system with a focus on speed. It differs from other build systems in two major respects: it is designed to have its input files generated by a higher-level build system, and it is designed to run builds as fast as possible. This document will cover how to compile ninja to work on 64-bit RISC-V architecture.","title":"Cross-compiling ninja-build for RISC-V"},{"location":"Cross_Compiling/Cross_compiling_ninja-build/#getting-source-code","text":"Use following command to get source code of ninja-build and navigate to source directory. git clone git://github.com/ninja-build/ninja.git cd ninja git checkout release Create following cmake file inside the root directory of ninja-build repository. # the name of the target operating system set(CMAKE_SYSTEM_NAME Linux) # which compilers to use for C and C++ set(CMAKE_C_COMPILER riscv64-unknown-linux-gnu-gcc) set(CMAKE_CXX_COMPILER riscv64-unknown-linux-gnu-g++) # where is the target environment located set(CMAKE_FIND_ROOT_PATH /softwares/RISCV/riscv64-unknown-linux-gnu/50c1b734e889e5cbb88bcc7f14975ea9a1d0b936/sysroot ) # adjust the default behavior of the FIND_XXX() commands: # search programs in the host environment set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER) # search headers and libraries in the target environment set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY) set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)","title":"Getting source code"},{"location":"Cross_Compiling/Cross_compiling_openssl/","text":"Cross-compiling openssl What is openssl Openssl is a software library which is used inside many high level languages (e.g. Python, Ruby etc.) and also in linux itself. It is used for security and other cryptography applications. Building openssl v1.0.1 for riscv64 architecture Following are the steps used to build openssl for riscv64 architecture. Get the source code of openssl and navigate inside the cloned repository using the commands below git clone https://github.com/openssl/openssl.git cd openssl Configure openssl for building. In openssl there are some os/compiler choices which one can use to build for his architecture. But in our case there is no support for building with riscv64. As it is written in C language, so it can be compiled whether or not the support is given. Use the following command to generate a Makefile for linux-generic64 ./Configure linux-generic64 --prefix=$PREFIX # Prefix is the directory where you want binaries to be installed at the end After the above command is successfully completed, run the following command to build openssl using riscv64-unknown-linux-gnu-gcc compiler instead of native gcc compiler. make -j$(nproc) CC=riscv64-unknown-linux-gnu-gcc Install the binaries in the specified --prefix using the command below make -j$(nproc) install CC=riscv64-unknown-linux-gnu-gcc The installed binary can be tested on qemu-riscv64 using the command below: qemu-riscv64 -L $RISCV_SYSROOT ./openssl Here $RISCV_SYSROOT is the sysroot/ folder located inside the riscv gnu toolchain installed directory. The above mentioned command will start the openssl console if everything went right. Note: Do not change the directory of openssl or rename it, as it some files inside it are inferred with absolute paths, changing the directory or renaming it will cause other packages to not configure openssl for them when cross-compiling. Building openssl v1.1.1r for riscv64 architecture In openssl v1.1.1r, there is a support for linux64-riscv64 . Following is the procedure for cross-compilation. Checkout the v1.1.1r of openssl by executing following command in the repository directory. git checkout OpenSSL_1_1_1r Execute following command to configure for riscv64 architecture and generate a Makefile . ./Configure linux64-riscv64 --prefix=$PREFIX # Replace $PREFIX with where you want to install binaries Execute following command to cross-compile for riscv64-unknown-linux-gnu . make CROSS_COMPILE=riscv64-unknown-linux-gnu- Then install binaries at $PREFIX with following command. make install Solving post-installation errors On some operating systems, the installed binaries may not run properly and will give following error. ./openssl: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory This means that shared libraries cannot be found in the path where the system is looking for them. This can be solved by setting LD_LIBRARY_PATH variable as follows. export LD_LIBRARY_PATH=$PREFIX/lib:$LD_LIBRARY_PATH It will be a good practice to include the above in the bashrc for debian users.","title":"Cross-compiling openssl"},{"location":"Cross_Compiling/Cross_compiling_openssl/#cross-compiling-openssl","text":"","title":"Cross-compiling openssl"},{"location":"Cross_Compiling/Cross_compiling_openssl/#what-is-openssl","text":"Openssl is a software library which is used inside many high level languages (e.g. Python, Ruby etc.) and also in linux itself. It is used for security and other cryptography applications.","title":"What is openssl"},{"location":"Cross_Compiling/Cross_compiling_openssl/#building-openssl-v101-for-riscv64-architecture","text":"Following are the steps used to build openssl for riscv64 architecture. Get the source code of openssl and navigate inside the cloned repository using the commands below git clone https://github.com/openssl/openssl.git cd openssl Configure openssl for building. In openssl there are some os/compiler choices which one can use to build for his architecture. But in our case there is no support for building with riscv64. As it is written in C language, so it can be compiled whether or not the support is given. Use the following command to generate a Makefile for linux-generic64 ./Configure linux-generic64 --prefix=$PREFIX # Prefix is the directory where you want binaries to be installed at the end After the above command is successfully completed, run the following command to build openssl using riscv64-unknown-linux-gnu-gcc compiler instead of native gcc compiler. make -j$(nproc) CC=riscv64-unknown-linux-gnu-gcc Install the binaries in the specified --prefix using the command below make -j$(nproc) install CC=riscv64-unknown-linux-gnu-gcc The installed binary can be tested on qemu-riscv64 using the command below: qemu-riscv64 -L $RISCV_SYSROOT ./openssl Here $RISCV_SYSROOT is the sysroot/ folder located inside the riscv gnu toolchain installed directory. The above mentioned command will start the openssl console if everything went right. Note: Do not change the directory of openssl or rename it, as it some files inside it are inferred with absolute paths, changing the directory or renaming it will cause other packages to not configure openssl for them when cross-compiling.","title":"Building openssl v1.0.1 for riscv64 architecture"},{"location":"Cross_Compiling/Cross_compiling_openssl/#building-openssl-v111r-for-riscv64-architecture","text":"In openssl v1.1.1r, there is a support for linux64-riscv64 . Following is the procedure for cross-compilation. Checkout the v1.1.1r of openssl by executing following command in the repository directory. git checkout OpenSSL_1_1_1r Execute following command to configure for riscv64 architecture and generate a Makefile . ./Configure linux64-riscv64 --prefix=$PREFIX # Replace $PREFIX with where you want to install binaries Execute following command to cross-compile for riscv64-unknown-linux-gnu . make CROSS_COMPILE=riscv64-unknown-linux-gnu- Then install binaries at $PREFIX with following command. make install","title":"Building openssl v1.1.1r for riscv64 architecture"},{"location":"Cross_Compiling/Cross_compiling_openssl/#solving-post-installation-errors","text":"On some operating systems, the installed binaries may not run properly and will give following error. ./openssl: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory This means that shared libraries cannot be found in the path where the system is looking for them. This can be solved by setting LD_LIBRARY_PATH variable as follows. export LD_LIBRARY_PATH=$PREFIX/lib:$LD_LIBRARY_PATH It will be a good practice to include the above in the bashrc for debian users.","title":"Solving post-installation errors"},{"location":"Cross_Compiling/Cross_compiling_ruby/","text":"Cross Compilation of Ruby System Specifications Build Architecture: x86_64-linux-gnu Host Architecture: riscv64-unknown-linux-gnu Operating System for Installation Procedure: Ubuntu 20.04 Pre-requisites Pre-requisites for installing ruby from source can be installed using the following command sudo apt-get -y install libc6-dev libssl-dev libmysql++-dev libsqlite3-dev make build-essential libssl-dev libreadline6-dev zlib1g-dev libyaml-dev Other than this, ruby itself is needed for building ruby from source. sudo apt install ruby There is another thing which needs to be taken care of before building ruby from source. If ruby is installed on system itself using apt , then cross compiling ruby will end up in an error as shown in the image below. This error is seen in ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu] . To tackle this issue, one workaround is to install build ruby for native system, then delete ruby which was installed through apt . This procedure will be added in the Build section. Getting source code Source code of ruby can be obtained from github repository using the command below: git clone https://github.com/ruby/ruby.git Build Installing ruby for native architecture Before cross-compiling, one must install ruby from source on the native machine which will solve the error described in Pre-requisites section above. ( THIS STEP IS STRONGLY RECOMMENDED ! )In the source directory, create a folder with any name in which Makefile will be generated otherwise there will be a lot of files made in the source directory (possibly create copy of repo directory). In the source directory of ruby run following command to generate configure file. ./autogen.sh After this, run the following configure command to generate Makefile . ../configure --prefix=$PREFIX #$PREFIX is where you want to install binary files at the end, so replace it. After the above command is completed, run following command to start the build make -j$(nproc) #-j$(nproc) uses parallelism for make After the above command is complete, run following command to install the binaries on the specified path mentioned in --prefix above make install Now ruby should be available in the $PREFIX path (also in the .bashrc ). Add $PREFIX path to $PATH variable and uninstall the the ruby installed using apt otherwise, the source will keep using that one for building and the error will persist. sudo apt purge ruby Cross-Compiling Ruby for riscv64-unknown-linux-gnu After the ruby installed using apt is uninstalled from the system, clean the working directory with following command. make clean After cleaning the working directory, generate the Makefile again for cross-compiling ruby for riscv64-unknown-linux-gnu target and host using the command below ../../configure --prefix=$PREFIX --build=x86_64-linux-gnu --host=riscv64-unknown-linux-gnu --target=riscv64-unknown-linux-gnu After the above command is successful, start build with following command make -j(nproc) Install the binaries in path mentioned with --prefix above with following command make install After this process, ruby will be installed inside $PREFIX/ directory. Note: Currently, this process (as checked on version 3.1.2) installs ruby without extensions shown in the following image","title":"Cross Compilation of Ruby"},{"location":"Cross_Compiling/Cross_compiling_ruby/#cross-compilation-of-ruby","text":"","title":"Cross Compilation of Ruby"},{"location":"Cross_Compiling/Cross_compiling_ruby/#system-specifications","text":"Build Architecture: x86_64-linux-gnu Host Architecture: riscv64-unknown-linux-gnu Operating System for Installation Procedure: Ubuntu 20.04","title":"System Specifications"},{"location":"Cross_Compiling/Cross_compiling_ruby/#pre-requisites","text":"Pre-requisites for installing ruby from source can be installed using the following command sudo apt-get -y install libc6-dev libssl-dev libmysql++-dev libsqlite3-dev make build-essential libssl-dev libreadline6-dev zlib1g-dev libyaml-dev Other than this, ruby itself is needed for building ruby from source. sudo apt install ruby There is another thing which needs to be taken care of before building ruby from source. If ruby is installed on system itself using apt , then cross compiling ruby will end up in an error as shown in the image below. This error is seen in ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu] . To tackle this issue, one workaround is to install build ruby for native system, then delete ruby which was installed through apt . This procedure will be added in the Build section.","title":"Pre-requisites"},{"location":"Cross_Compiling/Cross_compiling_ruby/#getting-source-code","text":"Source code of ruby can be obtained from github repository using the command below: git clone https://github.com/ruby/ruby.git","title":"Getting source code"},{"location":"Cross_Compiling/Cross_compiling_ruby/#build","text":"","title":"Build"},{"location":"Cross_Compiling/Cross_compiling_ruby/#installing-ruby-for-native-architecture","text":"Before cross-compiling, one must install ruby from source on the native machine which will solve the error described in Pre-requisites section above. ( THIS STEP IS STRONGLY RECOMMENDED ! )In the source directory, create a folder with any name in which Makefile will be generated otherwise there will be a lot of files made in the source directory (possibly create copy of repo directory). In the source directory of ruby run following command to generate configure file. ./autogen.sh After this, run the following configure command to generate Makefile . ../configure --prefix=$PREFIX #$PREFIX is where you want to install binary files at the end, so replace it. After the above command is completed, run following command to start the build make -j$(nproc) #-j$(nproc) uses parallelism for make After the above command is complete, run following command to install the binaries on the specified path mentioned in --prefix above make install Now ruby should be available in the $PREFIX path (also in the .bashrc ). Add $PREFIX path to $PATH variable and uninstall the the ruby installed using apt otherwise, the source will keep using that one for building and the error will persist. sudo apt purge ruby","title":"Installing ruby for native architecture"},{"location":"Cross_Compiling/Cross_compiling_ruby/#cross-compiling-ruby-for-riscv64-unknown-linux-gnu","text":"After the ruby installed using apt is uninstalled from the system, clean the working directory with following command. make clean After cleaning the working directory, generate the Makefile again for cross-compiling ruby for riscv64-unknown-linux-gnu target and host using the command below ../../configure --prefix=$PREFIX --build=x86_64-linux-gnu --host=riscv64-unknown-linux-gnu --target=riscv64-unknown-linux-gnu After the above command is successful, start build with following command make -j(nproc) Install the binaries in path mentioned with --prefix above with following command make install After this process, ruby will be installed inside $PREFIX/ directory. Note: Currently, this process (as checked on version 3.1.2) installs ruby without extensions shown in the following image","title":"Cross-Compiling Ruby for riscv64-unknown-linux-gnu"},{"location":"Cross_Compiling/Cross_compiling_rust/","text":"Cross-compiling rust Rust is a programming language just like C but it focuses on safety of programs. This document describes how one can build rust for x86_64 and then add support to compile code for riscv64 architecture. The executable for RISC-V architecture will be able to run on qemu-riscv64 . Note: Make sure riscv64-unknown-linux-gnu toolchain is installed on the machine. Getting source code Here the code will be taken from rustup GitHub repository. This is because instead of installing cargo , rustup and rustc , just compiling rustup will compile them along with itself. Get the source code using the command below: git clone https://github.com/rust-lang/rustup.git Before starting installation process, if you want to install rust in a specific location, then set CARGO_HOME and RUSTUP_HOME variable in the directory where you want to install rustup. After that, considering you are in the repository directory, start the installation process using the command below: sh rustup-init.sh -y After execution above command, follow the prompts as desired and complete the installation process. Now add riscv64 library support in rust using the command below: rustup target add riscv64gc-unknown-linux-gnu Once this is complete, go to the desired location where a new project is to be created and use following command to create a project's directory structure. cargo new project_name # Use a meaningful project name A directory with name project_name will be created as soon as the above command is executed successfully. This project will contain a main.rs which initially contains a Hello World program. Navigate to the project_name directory and create a folder with name .cargo , this will include a config.toml file inside it, which will tell it cargo during build that what is the target for which the compilation is to be done. The contents of the project_name/.cargo/config.toml will be as follows: [build] target = \"riscv64gc-unknown-linux-gnu\" [target.riscv64gc-unknown-linux-gnu] linker = \"riscv64-unknown-linux-gnu-gcc\" Now the project will be ready to build. Get back to the project_name/ directory and use following command to build the main.rs file: cargo build The output of the above command should as follows: Compiling myproject v0.1.0 (project_name) Finished dev [unoptimized + debuginfo] target(s) in 0.27s After the above command, the executable with the name project_name will be available at following location: project_name/target/riscv64gc-unknown-linux-gnu/debug Now the produced executable can be executed using qemu usermode. Use the following command to execute binary: qemu-riscv64 -L $RISCV_SYSROOT ./project_name","title":"Cross-compiling rust"},{"location":"Cross_Compiling/Cross_compiling_rust/#cross-compiling-rust","text":"Rust is a programming language just like C but it focuses on safety of programs. This document describes how one can build rust for x86_64 and then add support to compile code for riscv64 architecture. The executable for RISC-V architecture will be able to run on qemu-riscv64 . Note: Make sure riscv64-unknown-linux-gnu toolchain is installed on the machine.","title":"Cross-compiling rust"},{"location":"Cross_Compiling/Cross_compiling_rust/#getting-source-code","text":"Here the code will be taken from rustup GitHub repository. This is because instead of installing cargo , rustup and rustc , just compiling rustup will compile them along with itself. Get the source code using the command below: git clone https://github.com/rust-lang/rustup.git Before starting installation process, if you want to install rust in a specific location, then set CARGO_HOME and RUSTUP_HOME variable in the directory where you want to install rustup. After that, considering you are in the repository directory, start the installation process using the command below: sh rustup-init.sh -y After execution above command, follow the prompts as desired and complete the installation process. Now add riscv64 library support in rust using the command below: rustup target add riscv64gc-unknown-linux-gnu Once this is complete, go to the desired location where a new project is to be created and use following command to create a project's directory structure. cargo new project_name # Use a meaningful project name A directory with name project_name will be created as soon as the above command is executed successfully. This project will contain a main.rs which initially contains a Hello World program. Navigate to the project_name directory and create a folder with name .cargo , this will include a config.toml file inside it, which will tell it cargo during build that what is the target for which the compilation is to be done. The contents of the project_name/.cargo/config.toml will be as follows: [build] target = \"riscv64gc-unknown-linux-gnu\" [target.riscv64gc-unknown-linux-gnu] linker = \"riscv64-unknown-linux-gnu-gcc\" Now the project will be ready to build. Get back to the project_name/ directory and use following command to build the main.rs file: cargo build The output of the above command should as follows: Compiling myproject v0.1.0 (project_name) Finished dev [unoptimized + debuginfo] target(s) in 0.27s After the above command, the executable with the name project_name will be available at following location: project_name/target/riscv64gc-unknown-linux-gnu/debug Now the produced executable can be executed using qemu usermode. Use the following command to execute binary: qemu-riscv64 -L $RISCV_SYSROOT ./project_name","title":"Getting source code"},{"location":"Cross_Compiling/Overview/","text":"Cross Compilation Need of Cross Compilation Lets say you have a computer A having processor with architecture a and another computer B having processor with architecture b . Assume computer A has all the necessary tools and softwares whereas computer B does not have any software, tools, compilers and also the dependencies needed to install these tools and softwares. In this scenario, you cannot download the software setups (say tarballs) directly on computer B and have them installed/compiled because they will not be able to get compiled by computer B and will be completely useless. Basic concept The basic workflow in such a condition will be as follows: Install a compiler on computer A such that it runs on computer A and compiles code for architecture a . Using the above installed compiler, install a compiler on computer A such that it runs on computer A but compiles code for architecture b . Such a compiler is called cross compiler. One example of such a cross-compiler is RISC-V GNU TOOLCHAIN . Using the above compiled cross compiler, compile all the programs and also the compiler itself for architecture b . Port all the compiled binaries to the computer B . Such a process is beneficial if you have created a custom architecture and there is no support available for it. Throughout this documentation, the cross compiler used will be RISCV GNU Toolchain mentioned with riscv64-unknown-linux-gcc running on x86_64 and compiling code for riscv64 architecture whereas the native compiler will be gcc running on x86_64 and compiling code for x86_64 unless otherwise specified.","title":"Cross Compilation"},{"location":"Cross_Compiling/Overview/#cross-compilation","text":"","title":"Cross Compilation"},{"location":"Cross_Compiling/Overview/#need-of-cross-compilation","text":"Lets say you have a computer A having processor with architecture a and another computer B having processor with architecture b . Assume computer A has all the necessary tools and softwares whereas computer B does not have any software, tools, compilers and also the dependencies needed to install these tools and softwares. In this scenario, you cannot download the software setups (say tarballs) directly on computer B and have them installed/compiled because they will not be able to get compiled by computer B and will be completely useless.","title":"Need of Cross Compilation"},{"location":"Cross_Compiling/Overview/#basic-concept","text":"The basic workflow in such a condition will be as follows: Install a compiler on computer A such that it runs on computer A and compiles code for architecture a . Using the above installed compiler, install a compiler on computer A such that it runs on computer A but compiles code for architecture b . Such a compiler is called cross compiler. One example of such a cross-compiler is RISC-V GNU TOOLCHAIN . Using the above compiled cross compiler, compile all the programs and also the compiler itself for architecture b . Port all the compiled binaries to the computer B . Such a process is beneficial if you have created a custom architecture and there is no support available for it. Throughout this documentation, the cross compiler used will be RISCV GNU Toolchain mentioned with riscv64-unknown-linux-gcc running on x86_64 and compiling code for riscv64 architecture whereas the native compiler will be gcc running on x86_64 and compiling code for x86_64 unless otherwise specified.","title":"Basic concept"},{"location":"Usage_Monitoring/Integrating_prometheus_grafana/","text":"Integrating Prometheus with Grafana Before starting to integrate Prometheus with Grafana make sure they are set up properly. See this document for setting up Prometheus and Grafana as standalone tools. Configuration in Prometheus Make sure all the node_exporter are running properly and the compute instances are discoverable by prometheus. Use following command for checking if the instances are accessible: telnet COMPUTE_INSTANCE_IP COMPUTE_INSTANCE_PORT If you get following response, then it means there is something wrong with firewall of compute instances as they are not accessible. Name or service not known Configuration in Grafana Enter the grafana IP in browser and login with credentials. Use following steps to integrate Grafana with Prometheus and creating dashbaords in Grafana Go to Grafana settings Go to Data sources tab Click on Add data source In HTTP section, add IP of machine on which Prometheus is running along with the port on which Prometheus is hosted (it is recommended to host Prometheus on the machine where Grafana is hosted, in that case, Prometheus will be accessed using LAN IP). In Type and version section, select Prometheus from drop down menu and choose a version of Prometheus in the next field. Click on Save and test If everything goes right, then it will say Data source is working . Creating a dashboard in Grafana For creating a dashboard, click on Dashboards Click on New and then New Dashboard Then add a panel inside the dashbaord If you know the mathemtical expressions (which are easier and more verbose) then select Code while creating the panels instead of Builder . Note: Be sure to save the dashbaord because otherwise, it will not make changes on its own and dashboard will be lost.","title":"Integrating Prometheus with Grafana"},{"location":"Usage_Monitoring/Integrating_prometheus_grafana/#integrating-prometheus-with-grafana","text":"Before starting to integrate Prometheus with Grafana make sure they are set up properly. See this document for setting up Prometheus and Grafana as standalone tools.","title":"Integrating Prometheus with Grafana"},{"location":"Usage_Monitoring/Integrating_prometheus_grafana/#configuration-in-prometheus","text":"Make sure all the node_exporter are running properly and the compute instances are discoverable by prometheus. Use following command for checking if the instances are accessible: telnet COMPUTE_INSTANCE_IP COMPUTE_INSTANCE_PORT If you get following response, then it means there is something wrong with firewall of compute instances as they are not accessible. Name or service not known","title":"Configuration in Prometheus"},{"location":"Usage_Monitoring/Integrating_prometheus_grafana/#configuration-in-grafana","text":"Enter the grafana IP in browser and login with credentials. Use following steps to integrate Grafana with Prometheus and creating dashbaords in Grafana Go to Grafana settings Go to Data sources tab Click on Add data source In HTTP section, add IP of machine on which Prometheus is running along with the port on which Prometheus is hosted (it is recommended to host Prometheus on the machine where Grafana is hosted, in that case, Prometheus will be accessed using LAN IP). In Type and version section, select Prometheus from drop down menu and choose a version of Prometheus in the next field. Click on Save and test If everything goes right, then it will say Data source is working .","title":"Configuration in Grafana"},{"location":"Usage_Monitoring/Integrating_prometheus_grafana/#creating-a-dashboard-in-grafana","text":"For creating a dashboard, click on Dashboards Click on New and then New Dashboard Then add a panel inside the dashbaord If you know the mathemtical expressions (which are easier and more verbose) then select Code while creating the panels instead of Builder . Note: Be sure to save the dashbaord because otherwise, it will not make changes on its own and dashboard will be lost.","title":"Creating a dashboard in Grafana"},{"location":"Usage_Monitoring/Prometheus_Grafana/","text":"Setting up Promtheus and Grafana What are Prometheus and Grafana Prometheus is a tool for monitoring usage of memory, CPU etc. It takes queries as mathematical expressions (like SQL) and returns the interactive graphical usage stats. It collects data using node_exporter , which is used to get raw data from the compute instances Grafana is used for creating dashboards in which there can be different panels containing the graphical statistics from Prometheus. Grafana dashboards are more interactive and user-friendly than Prometheus. Setting up Node Exporters Node exporters are needed for prometheus to get data from the compute instances. Download pre-compiled tarball of node_exporters from this link and place the tarballs on compute instances. Once node_exporter tarball is downloaded, extract it using following command: tar -xvf node_exporter-x.x.x.linux-amd64.tar.gz Run node_exporter on compute instances using command below (which will run node_exporter on port 9100 by default): ./node_exporter Follow this procedure on every compute instance which is desired to be monitored using Prometheus. Note: Make sure that compute instances can be accessed in the machine in which prometheus is installed. Configuring Prometheus Use this link to get pre-compiled tarball of Prometheus. Once Prometheus is downloaded, extract it using following command: tar -xvf prometheus-x.xx.x.linux-amd.tar.gz Now either configure prometheus.yml file or create another yml file which will include the addresses of node_exporters. Following is an example template for yml file: global: scrape_interval: 15s scrape_configs: - job_name: node static_configs: - targets: ['node_exporter_ip1:node_exporter_port1'] - targets: ['node_exporter_ip2:node_exporter_port2'] Running Prometheus Once prometheus is configured properly, use following command to run prometheus. ./prometheus Note: By default Prometheus looks for prometheus.yml , if you want to use some other file for configuration, you will need to specify explicitly with --config.file option. Running Grafana Once Prometheus is up and running, Grafana can be used to create dashboards with graphical interface in various panels inside dashboards. Use this to get pre-compiled tarball of Grafana After Grafana is ready to be run, use following command to run Grafana: ./grafana-server #By default it will run on port 3000 The default username and password of Grafana will be admin . Once Grafana is installed, a dashboard can be created to with multiple panels which will show data from Prometheus. Reference links https://grafana.com/docs/grafana/latest/getting-started/get-started-grafana-prometheus/","title":"Setting up Promtheus and Grafana"},{"location":"Usage_Monitoring/Prometheus_Grafana/#setting-up-promtheus-and-grafana","text":"","title":"Setting up Promtheus and Grafana"},{"location":"Usage_Monitoring/Prometheus_Grafana/#what-are-prometheus-and-grafana","text":"Prometheus is a tool for monitoring usage of memory, CPU etc. It takes queries as mathematical expressions (like SQL) and returns the interactive graphical usage stats. It collects data using node_exporter , which is used to get raw data from the compute instances Grafana is used for creating dashboards in which there can be different panels containing the graphical statistics from Prometheus. Grafana dashboards are more interactive and user-friendly than Prometheus.","title":"What are Prometheus and Grafana"},{"location":"Usage_Monitoring/Prometheus_Grafana/#setting-up-node-exporters","text":"Node exporters are needed for prometheus to get data from the compute instances. Download pre-compiled tarball of node_exporters from this link and place the tarballs on compute instances. Once node_exporter tarball is downloaded, extract it using following command: tar -xvf node_exporter-x.x.x.linux-amd64.tar.gz Run node_exporter on compute instances using command below (which will run node_exporter on port 9100 by default): ./node_exporter Follow this procedure on every compute instance which is desired to be monitored using Prometheus. Note: Make sure that compute instances can be accessed in the machine in which prometheus is installed.","title":"Setting up Node Exporters"},{"location":"Usage_Monitoring/Prometheus_Grafana/#configuring-prometheus","text":"Use this link to get pre-compiled tarball of Prometheus. Once Prometheus is downloaded, extract it using following command: tar -xvf prometheus-x.xx.x.linux-amd.tar.gz Now either configure prometheus.yml file or create another yml file which will include the addresses of node_exporters. Following is an example template for yml file: global: scrape_interval: 15s scrape_configs: - job_name: node static_configs: - targets: ['node_exporter_ip1:node_exporter_port1'] - targets: ['node_exporter_ip2:node_exporter_port2']","title":"Configuring Prometheus"},{"location":"Usage_Monitoring/Prometheus_Grafana/#running-prometheus","text":"Once prometheus is configured properly, use following command to run prometheus. ./prometheus Note: By default Prometheus looks for prometheus.yml , if you want to use some other file for configuration, you will need to specify explicitly with --config.file option.","title":"Running Prometheus"},{"location":"Usage_Monitoring/Prometheus_Grafana/#running-grafana","text":"Once Prometheus is up and running, Grafana can be used to create dashboards with graphical interface in various panels inside dashboards. Use this to get pre-compiled tarball of Grafana After Grafana is ready to be run, use following command to run Grafana: ./grafana-server #By default it will run on port 3000 The default username and password of Grafana will be admin . Once Grafana is installed, a dashboard can be created to with multiple panels which will show data from Prometheus.","title":"Running Grafana"},{"location":"Usage_Monitoring/Prometheus_Grafana/#reference-links","text":"https://grafana.com/docs/grafana/latest/getting-started/get-started-grafana-prometheus/","title":"Reference links"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/","text":"GitHub Pull Request hook integration with Jenkins Reference Link: https://plugins.jenkins.io/ghprb/ General Guidline If facing an issue, it is better to launch the Jenkins from running the .war file (which is obtained by building the Jenkins github repository) in terminal (which is mostly bash in case of linux) and observing the terminal's output. For example if a webhook is not created, the GUI may not show anything but the terminal will most probably print a message showing the reason for this behavior. GitHub Pull Request Builder Plugin In version control, it is better to check the changes and run tests before the changes are merged into main branch. Sometimes those changes can be enormous to check. So it becomes difficult for requested reviewer of the pull request to check all the changes and run tests on them manually. For that purpose, it is better to automate the process so that whenever a pull request is generated, all the tests are triggered and based on the results, the reviewer decides whether or not to merge the branch with main. This can be achieved using Jenkins' Github Pull Request Builder plugin. Specifications at the time of documentation Operating System: Linux Distribution: Ubuntu Release: Focal (also known as 20.04) Jenkins version: 2.371 (can be seen in config.xml) Github Webhook Builder version: 1.42.2 Pre-Requisites Jenkins. Git Plugin GitHub Plugin Github Pull Request Builder Plugin Github account and repository with permission to generate a pull request to merge the branch. Setting up Jenkins configuration Install the above mentioned plugins from Dashboard > Manage Jenkins > Manage Plugins > Available Plugins . Go to Dashboard > Manage Jenkins > Configure System . Scroll down to Github Pull Request Builder . Leave GitHub Server API URL and Jenkins URL override as it is. In Credentials , click on add and select Jenkins from drop down. Select Kind as Secret text . In Secret , add GitHub Personal authentication token which can be acquired from GitHub account settings. Add some safe description to remind what these credentials are about otherwise jenkins use a lot of credentials and it gets difficult to keep account of them. Leave ID empty. Click on Add . Now select the added credentials from the drop down menu of Credentials . Click on Test Credentials... . Check Test basic connection to GitHub . Click on Connect to API . This will show the message Connected to <API_URL> as <Name_of_GitHub_user> . Other settings can be left empty. Click on save. Setting up Jenkins job In this documentation, Pipeline job will be used, but any job is expected to work fine with these settings. For this documentation it is considered that the jenkinsfile for building the pipeline is present in the repository which is to be built. Go to Dashboard and click New Item . Enter a Job name (here it will be github_PR_webhook ). Click OK . It will navigate to the job's configuration page. Add a Description of choice. Scroll down and check GitHub project . Add the URL of GitHub repository. Here the URL of the repository should be added without .git extention. This is important that the person who is creating pull request should be either in admin list or whitelist because otherwise, the webhook will not be created. Scroll down to Build Triggers section. Check GitHub Pull Request Builder . This will open further configurations for this option. Leave GitHub API credentials . Add a GitHub admin's username in the Admin list . This is important becaue otherwise, the checks will not run on generating a pull request. Check Use github hooks for build triggering . Click on Advanced and in Whitelist Target Branches add the branch name for which, when a pull request is generated, the job is supposed to be trigger (here it is main ). Scroll down to Pipeline section. In Definition , select Pipeline script from SCM . Select SCM as Git from drop down. Enter the Repository URL from GitHub. Enter Credentials with access to this repository (This is optional if the repository is public). Under Advanced , enter Refspec as +refs/pull/*:refs/remotes/origin/pr/* [^note]. If the tests are to be run on actual commit in the pull request then, under Branches to build section, in Branch Specifier , enter ${ghprbActualCommit} [^note]. Leave other settings as it is. In Script Path , add the path and name of the jenkinsfile which is present in GitHub repository. Uncheck Lightweight checkout [^note1] Click Apply and then Save . After saving the job, a webhook should be created automatically in GitHub if the credentials provided in the settings are correct. Verifying if the procedure In the GitHub repository, add another branch aside from main . For this, expand main and click on View all branches . Click on New Branch , and insert a name. After a new branch is created, select new branch instead of main in repository page. Add some changings to either of the file (even adding a space is enough). Commit Changes. Create a Pull request. Now after checking the merge conflicts, the checks will run their results will be shown with pull request (as can be seen in the image below). NOTE: The Jenkinfile will run present in the pull request and not in the main branch. Clicking on the Details navigates the user to the Jenkins Job result page where the console output and each stage can be seen. [^note]: This point is taken from the jenkins GitHub Pull Request Builder plugin documentation at https://plugins.jenkins.io/ghprb/ [^note1]: This is an issue mentioned in the documentation of Github Pull Request Builder plugin at https://plugins.jenkins.io/ghprb/ .","title":"GitHub Pull Request hook integration with Jenkins"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#github-pull-request-hook-integration-with-jenkins","text":"Reference Link: https://plugins.jenkins.io/ghprb/","title":"GitHub Pull Request hook integration with Jenkins"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#general-guidline","text":"If facing an issue, it is better to launch the Jenkins from running the .war file (which is obtained by building the Jenkins github repository) in terminal (which is mostly bash in case of linux) and observing the terminal's output. For example if a webhook is not created, the GUI may not show anything but the terminal will most probably print a message showing the reason for this behavior.","title":"General Guidline"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#github-pull-request-builder-plugin","text":"In version control, it is better to check the changes and run tests before the changes are merged into main branch. Sometimes those changes can be enormous to check. So it becomes difficult for requested reviewer of the pull request to check all the changes and run tests on them manually. For that purpose, it is better to automate the process so that whenever a pull request is generated, all the tests are triggered and based on the results, the reviewer decides whether or not to merge the branch with main. This can be achieved using Jenkins' Github Pull Request Builder plugin.","title":"GitHub Pull Request Builder Plugin"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#specifications-at-the-time-of-documentation","text":"Operating System: Linux Distribution: Ubuntu Release: Focal (also known as 20.04) Jenkins version: 2.371 (can be seen in config.xml) Github Webhook Builder version: 1.42.2","title":"Specifications at the time of documentation"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#pre-requisites","text":"Jenkins. Git Plugin GitHub Plugin Github Pull Request Builder Plugin Github account and repository with permission to generate a pull request to merge the branch.","title":"Pre-Requisites"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#setting-up-jenkins-configuration","text":"Install the above mentioned plugins from Dashboard > Manage Jenkins > Manage Plugins > Available Plugins . Go to Dashboard > Manage Jenkins > Configure System . Scroll down to Github Pull Request Builder . Leave GitHub Server API URL and Jenkins URL override as it is. In Credentials , click on add and select Jenkins from drop down. Select Kind as Secret text . In Secret , add GitHub Personal authentication token which can be acquired from GitHub account settings. Add some safe description to remind what these credentials are about otherwise jenkins use a lot of credentials and it gets difficult to keep account of them. Leave ID empty. Click on Add . Now select the added credentials from the drop down menu of Credentials . Click on Test Credentials... . Check Test basic connection to GitHub . Click on Connect to API . This will show the message Connected to <API_URL> as <Name_of_GitHub_user> . Other settings can be left empty. Click on save.","title":"Setting up Jenkins configuration"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#setting-up-jenkins-job","text":"In this documentation, Pipeline job will be used, but any job is expected to work fine with these settings. For this documentation it is considered that the jenkinsfile for building the pipeline is present in the repository which is to be built. Go to Dashboard and click New Item . Enter a Job name (here it will be github_PR_webhook ). Click OK . It will navigate to the job's configuration page. Add a Description of choice. Scroll down and check GitHub project . Add the URL of GitHub repository. Here the URL of the repository should be added without .git extention. This is important that the person who is creating pull request should be either in admin list or whitelist because otherwise, the webhook will not be created. Scroll down to Build Triggers section. Check GitHub Pull Request Builder . This will open further configurations for this option. Leave GitHub API credentials . Add a GitHub admin's username in the Admin list . This is important becaue otherwise, the checks will not run on generating a pull request. Check Use github hooks for build triggering . Click on Advanced and in Whitelist Target Branches add the branch name for which, when a pull request is generated, the job is supposed to be trigger (here it is main ). Scroll down to Pipeline section. In Definition , select Pipeline script from SCM . Select SCM as Git from drop down. Enter the Repository URL from GitHub. Enter Credentials with access to this repository (This is optional if the repository is public). Under Advanced , enter Refspec as +refs/pull/*:refs/remotes/origin/pr/* [^note]. If the tests are to be run on actual commit in the pull request then, under Branches to build section, in Branch Specifier , enter ${ghprbActualCommit} [^note]. Leave other settings as it is. In Script Path , add the path and name of the jenkinsfile which is present in GitHub repository. Uncheck Lightweight checkout [^note1] Click Apply and then Save . After saving the job, a webhook should be created automatically in GitHub if the credentials provided in the settings are correct.","title":"Setting up Jenkins job"},{"location":"jenkins_github_integration/Github_PR_webhook_integration/#verifying-if-the-procedure","text":"In the GitHub repository, add another branch aside from main . For this, expand main and click on View all branches . Click on New Branch , and insert a name. After a new branch is created, select new branch instead of main in repository page. Add some changings to either of the file (even adding a space is enough). Commit Changes. Create a Pull request. Now after checking the merge conflicts, the checks will run their results will be shown with pull request (as can be seen in the image below). NOTE: The Jenkinfile will run present in the pull request and not in the main branch. Clicking on the Details navigates the user to the Jenkins Job result page where the console output and each stage can be seen. [^note]: This point is taken from the jenkins GitHub Pull Request Builder plugin documentation at https://plugins.jenkins.io/ghprb/ [^note1]: This is an issue mentioned in the documentation of Github Pull Request Builder plugin at https://plugins.jenkins.io/ghprb/ .","title":"Verifying if the procedure"},{"location":"jenkins_github_integration/Github_push_webhook/","text":"Github 'Push' webhook integration with Jenkins Purpose of using github webhook integration with jenkins Most of the time, after a push on the upstream repository, one may want to check the result of all the checks on the repository defined by CI/CD pipeline. This tells whether there is some issue with push and whether or not the defined checks/tests have passed. This can be achieved using github push webhook integration with jenkins. Jenkins version and operating system specifications The version of Jenkins and operating system specifications at the time of writing this documentation are mentioned below: Jenkins version: 2.370 Operating System: Linux Distribution: Ubuntu Release: Focal (also called 20.04) Pre-requisites Jenkins ngrok (only if a public IP is not available) Setting up the ngrok The localhost cannot be used for github webhook integration as it cannot be detected by online webservers. For this reason, a public ip must be used. For the sake of this documentation, ngrok is being used, which maps localhost to some public ip which can then be accessed publicly on the internet. Following steps can be used for setting up ngrok on ubuntu: Install ngrok. sudo apt install ngrok For using html content, a sign up is required on ngrok. So sign up on ngrok. Execute the following command to run ngrok which will provide a public ip mapped to localhost. ngrok http <port number> This will setup ngrok and provide a public ip for working online. Setting up Jenkins for github webhook Pre-requisites Following plugins should be installed in jenkins: Git Plugin GitHub API Plugin GitHub Plugin Jenkins Configuration in Settings Go to Manage Jenkins > Configure System and scroll down to GitHub section. Click on Add GitHub Server Add a name for the Github server. Leave API URL as is. In Credentials, click on Add . Jenkins will appear in drop down, click on it. Select Kind as Secret text Scroll down to the Secret and here, put down the github personal authentication token (PAT) which can be acquired from github account. Other options can be left unattended. Click on Add . Now the credentials should be added. In the Credentials drop down, select Secret text . Check Manage hooks . Now the connection can be established and can be checked by clicking the Test Connection . Click Save . Jenkins job setup for Github Webhook Create a new jenkins freestyle job and proceed with following settings on the configurations along with desired settings. Check GitHub project in General section and provide GitHub repository URL. In Source Code Management section, select Git . Give Repository URL In Credentials (if the credentials are not created already), click on Add , click on Jenkins from the drop down. Select Kind as Username with password . In Username , enter github username. In Password , enter github personal authentication token (PAT) which can be acquired from github account. Other fields can be left unattended. Click on Add From Credentials drop down, select your added credentials. In Branches to build section, in Branch Specifier field, enter the name of branch of github repository which needs to be built. In Build Triggers section, check GitHub hook trigger for GITScm polling . (Following step is for checking the commit status according to the Jenkins job status, means if Jenkins job fails, commit status is also Failure ) Scroll down to the bottom and Add post-build action . From drop down, select Set GitHub commit status . Leave other settings as is and click on Advanced . Check Handle errors Under drop down Result on failure , select FAILURE Click on Apply and Save By this point, Jenkins is setup for github webhooks. Setting up github repository webhook For the sake of this documentation, I have created a simple repository called jenkins_hello_world_integrated . Go to GitHub repository's settings In Webhooks section, click on Add webhook In Webhooks settings: Add Payload URL as the URL of jenkins and append /github-webhook/ at the end of it. Select Content type application/jason . It is recommended to add Secret which can be generated by jenkins API Token by going to account configuration. It is recommended to Enable SSL verification . Select the events which should trigger the build in jenkins. Check Active . Click on Add Webhook . After this point each time the github repository is commited with a change, jenkins job will start the build and will also denote on the repository if the build has passed or failed (as can be seen in the below screenshot).","title":"Github 'Push' webhook integration with Jenkins"},{"location":"jenkins_github_integration/Github_push_webhook/#github-push-webhook-integration-with-jenkins","text":"","title":"Github 'Push' webhook integration with Jenkins"},{"location":"jenkins_github_integration/Github_push_webhook/#purpose-of-using-github-webhook-integration-with-jenkins","text":"Most of the time, after a push on the upstream repository, one may want to check the result of all the checks on the repository defined by CI/CD pipeline. This tells whether there is some issue with push and whether or not the defined checks/tests have passed. This can be achieved using github push webhook integration with jenkins.","title":"Purpose of using github webhook integration with jenkins"},{"location":"jenkins_github_integration/Github_push_webhook/#jenkins-version-and-operating-system-specifications","text":"The version of Jenkins and operating system specifications at the time of writing this documentation are mentioned below: Jenkins version: 2.370 Operating System: Linux Distribution: Ubuntu Release: Focal (also called 20.04)","title":"Jenkins version and operating system specifications"},{"location":"jenkins_github_integration/Github_push_webhook/#pre-requisites","text":"Jenkins ngrok (only if a public IP is not available)","title":"Pre-requisites"},{"location":"jenkins_github_integration/Github_push_webhook/#setting-up-the-ngrok","text":"The localhost cannot be used for github webhook integration as it cannot be detected by online webservers. For this reason, a public ip must be used. For the sake of this documentation, ngrok is being used, which maps localhost to some public ip which can then be accessed publicly on the internet. Following steps can be used for setting up ngrok on ubuntu: Install ngrok. sudo apt install ngrok For using html content, a sign up is required on ngrok. So sign up on ngrok. Execute the following command to run ngrok which will provide a public ip mapped to localhost. ngrok http <port number> This will setup ngrok and provide a public ip for working online.","title":"Setting up the ngrok"},{"location":"jenkins_github_integration/Github_push_webhook/#setting-up-jenkins-for-github-webhook","text":"","title":"Setting up Jenkins for github webhook"},{"location":"jenkins_github_integration/Github_push_webhook/#pre-requisites_1","text":"Following plugins should be installed in jenkins: Git Plugin GitHub API Plugin GitHub Plugin","title":"Pre-requisites"},{"location":"jenkins_github_integration/Github_push_webhook/#jenkins-configuration-in-settings","text":"Go to Manage Jenkins > Configure System and scroll down to GitHub section. Click on Add GitHub Server Add a name for the Github server. Leave API URL as is. In Credentials, click on Add . Jenkins will appear in drop down, click on it. Select Kind as Secret text Scroll down to the Secret and here, put down the github personal authentication token (PAT) which can be acquired from github account. Other options can be left unattended. Click on Add . Now the credentials should be added. In the Credentials drop down, select Secret text . Check Manage hooks . Now the connection can be established and can be checked by clicking the Test Connection . Click Save .","title":"Jenkins Configuration in Settings"},{"location":"jenkins_github_integration/Github_push_webhook/#jenkins-job-setup-for-github-webhook","text":"Create a new jenkins freestyle job and proceed with following settings on the configurations along with desired settings. Check GitHub project in General section and provide GitHub repository URL. In Source Code Management section, select Git . Give Repository URL In Credentials (if the credentials are not created already), click on Add , click on Jenkins from the drop down. Select Kind as Username with password . In Username , enter github username. In Password , enter github personal authentication token (PAT) which can be acquired from github account. Other fields can be left unattended. Click on Add From Credentials drop down, select your added credentials. In Branches to build section, in Branch Specifier field, enter the name of branch of github repository which needs to be built. In Build Triggers section, check GitHub hook trigger for GITScm polling . (Following step is for checking the commit status according to the Jenkins job status, means if Jenkins job fails, commit status is also Failure ) Scroll down to the bottom and Add post-build action . From drop down, select Set GitHub commit status . Leave other settings as is and click on Advanced . Check Handle errors Under drop down Result on failure , select FAILURE Click on Apply and Save By this point, Jenkins is setup for github webhooks.","title":"Jenkins job setup for Github Webhook"},{"location":"jenkins_github_integration/Github_push_webhook/#setting-up-github-repository-webhook","text":"For the sake of this documentation, I have created a simple repository called jenkins_hello_world_integrated . Go to GitHub repository's settings In Webhooks section, click on Add webhook In Webhooks settings: Add Payload URL as the URL of jenkins and append /github-webhook/ at the end of it. Select Content type application/jason . It is recommended to add Secret which can be generated by jenkins API Token by going to account configuration. It is recommended to Enable SSL verification . Select the events which should trigger the build in jenkins. Check Active . Click on Add Webhook . After this point each time the github repository is commited with a change, jenkins job will start the build and will also denote on the repository if the build has passed or failed (as can be seen in the below screenshot).","title":"Setting up github repository webhook"}]}
\ No newline at end of file
diff --git a/docs/sitemap.xml b/docs/sitemap.xml
index 8d0abf5..7c45ef9 100644
--- a/docs/sitemap.xml
+++ b/docs/sitemap.xml
@@ -2,147 +2,147 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2023-10-02</lastmod>
+         <lastmod>2023-11-03</lastmod>
          <changefreq>daily</changefreq>
     </url>
 </urlset>
\ No newline at end of file
diff --git a/docs/sitemap.xml.gz b/docs/sitemap.xml.gz
index 6427a6d..ebfa957 100644
Binary files a/docs/sitemap.xml.gz and b/docs/sitemap.xml.gz differ
diff --git a/mkdocs_src/mkdocs.yml b/mkdocs_src/mkdocs.yml
index 19ae473..f9b1d37 100755
--- a/mkdocs_src/mkdocs.yml
+++ b/mkdocs_src/mkdocs.yml
@@ -1,38 +1,36 @@
 site_name: Cloud-V Docs
 nav:
-- Home: index.md
-- For Cloud-V Users:
-    - RISC-V CI User's Guide:
-        - Guide for Software Developer: Software_Developer_Guide.md
-        - Creating a Jenkinfile: Creating_jenkinsfile.md
-        - Runners' Info: runner_specs.md
-        - Tools available in Cloud-V: Tooling.md
-- For Administrators:
-    - Jenkins Docs:
-        - Building Jenkins: Building_Jenkins_github_repo.md
-        - Creating Jenkins Node on LXC: Creating_Jenkins_Node_on_LXC.md
-        - Creating a pipeline project: Creating_CI_CD_pipeline.md
-        - Creating Multinode pipelines: Multinode_Pipelines.md
-        - Adding custom-build packages in Jenkins: Adding_Custom-build_packages_in_Jenkins.md
-        - Github Push webhook integration: jenkins_github_integration/Github_push_webhook.md
-        - Github PR webhook integration: jenkins_github_integration/Github_PR_webhook_integration.md
-        - GitLab Integration: jenkins_gitlab_integration.md
-        - Letsencrypt configuration with Jenkins: Installing_ssl_certificates_new.md
-    - QEMU and Linux Kernel:
-        - Installing Qemu for RISC-V: Building_qemu.md
-        - Building Linux kernel and booting on QEMU: Building_Linux_Kernel.md
-        - Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64: Booting_ubuntu22.04_riscv64
-    - Cross-Compilation:
-        - Overview: Cross_Compiling/Overview.md
-        - Cross Compiling Python3.8.15: Cross_Compiling/Cross_compiling python3.8.15.md
-        - Cross Compiling Openssl: Cross_Compiling/Cross_compiling_openssl.md
-        - Cross Compiling Ruby: Cross_Compiling/Cross_compiling_ruby.md
-        - Cross Compiling Drhystone: Cross_Compiling/Cross_compiling_dhrystone.md
-        - Cross Compiling Coremark: Cross_Compiling/Cross_compiling_coremark
-        - Cross Compiling Rust: Cross_Compiling/Cross_compiling_rust.md
-        - Cross Compiling go: Cross_Compiling/Cross_compiling_go.md
+  - Home: index.md
+  - Getting Started: Software_Developer_Guide.md
+  - Creating a Jenkinfile: Creating_jenkinsfile.md
+  - Runners' Info: runner_specs.md
+  - Tools available in Cloud-V: Tooling.md
+# - For Administrators:
+#     - Jenkins Docs:
+#         - Building Jenkins: Building_Jenkins_github_repo.md
+#         - Creating Jenkins Node on LXC: Creating_Jenkins_Node_on_LXC.md
+#         - Creating a pipeline project: Creating_CI_CD_pipeline.md
+#         - Creating Multinode pipelines: Multinode_Pipelines.md
+#         - Adding custom-build packages in Jenkins: Adding_Custom-build_packages_in_Jenkins.md
+#         - Github Push webhook integration: jenkins_github_integration/Github_push_webhook.md
+#         - Github PR webhook integration: jenkins_github_integration/Github_PR_webhook_integration.md
+#         - GitLab Integration: jenkins_gitlab_integration.md
+#         - Letsencrypt configuration with Jenkins: Installing_ssl_certificates_new.md
+#     - QEMU and Linux Kernel:
+#         - Installing Qemu for RISC-V: Building_qemu.md
+#         - Building Linux kernel and booting on QEMU: Building_Linux_Kernel.md
+#         - Booting RISC-V Ubuntu 22.04 on qemu-system-riscv64: Booting_ubuntu22.04_riscv64
+#     - Cross-Compilation:
+#         - Overview: Cross_Compiling/Overview.md
+#         - Cross Compiling Python3.8.15: Cross_Compiling/Cross_compiling python3.8.15.md
+#         - Cross Compiling Openssl: Cross_Compiling/Cross_compiling_openssl.md
+#         - Cross Compiling Ruby: Cross_Compiling/Cross_compiling_ruby.md
+#         - Cross Compiling Drhystone: Cross_Compiling/Cross_compiling_dhrystone.md
+#         - Cross Compiling Coremark: Cross_Compiling/Cross_compiling_coremark
+#         - Cross Compiling Rust: Cross_Compiling/Cross_compiling_rust.md
+#         - Cross Compiling go: Cross_Compiling/Cross_compiling_go.md
 
-    - Usage monitoring:
-        - Setting up Grafana and Prometheus: Usage_Monitoring/Prometheus_Grafana.md
-        - Integrating Prometheus with Grafana: Usage_Monitoring/Integrating_prometheus_grafana.md
+#     - Usage monitoring:
+#         - Setting up Grafana and Prometheus: Usage_Monitoring/Prometheus_Grafana.md
+#         - Integrating Prometheus with Grafana: Usage_Monitoring/Integrating_prometheus_grafana.md
 theme: readthedocs