makyo
/
zk_html
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

update from sparkleup

This commit is contained in:
Madison Scott-Clary 2022-06-28 19:20:24 -07:00
parent e52e49f565
commit 55dd935530
2 changed files with 40 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
work/gitea-4.html Normal file
View File

@ -0,0 +1,39 @@
<!doctype html>
<html>
<head>
<title>Zk | gitea-4</title>
<link rel="stylesheet" type="text/css" href="/style.css" />
<meta name="viewport" content="width=device-width" />
<meta charset="utf-8" />
</head>
<body>
<main>
<header>
<h1>Zk | gitea-4</h1>
</header>
<article class="content">
<h1 id="how-to-set-up-cicd-with-drone-ci-and-gitea">How To Set Up CI/CD with Drone CI and Gitea</h1>
<p>In the process of developing and releasing software, one of the most useful tools at a developer&rsquo;s disposal is a solution that performs <strong>continuous integration</strong> and <strong>continuous deployment</strong>, or <strong>CI/CD</strong>.</p>
<p>Continuous integration (CI) refers to the practice of multiple developers merging their changes to a codebase back into the main branch often, perhaps daily or even more frequently, relying on smaller chunks of work that are more easily reviewed to and tested during the process of development. In order to ensure that these changes don&rsquo;t leave the main branch in a broken state, a tool that helps with continuous integration will often include functionality that runs test suites within the software package. When a developer proposes a merge of their work back into the main branch, the tests will run automatically and report back whether or not they pass, which may mean that the code is not ready to land.</p>
<p>Continuous deployment or continuous delibery (CD) refers to the idea that changes to code &mdash; whether they&rsquo;re security patches, bug fixes, or new features &mdash; be released quickly and seamlessly to the end users of the application. In the case of applications that the user runs, this will mean a frequent release schedule, offering incremental improvements to the software they are using. In the case of a service such as a website, this will mean frequent deployments of the new features in the code to the site so that the user&rsquo;s experience is continuously improving.</p>
<p>There are several tools that can help with CI/CD. These run as their own web services, which work with many source code management (SCM) systems to perform these tasks automatically. <a href="https://drone.io">Drone</a> is one such solution, that provides a way of executing <strong>pipelines</strong> &mdash; sets of steps that the service will run through such as building the software and running tests &mdash; that are described in the code itself. Drone is a flexible CI/CD tool that can perform this on many different types of <strong>runners</strong>, containers or machines where the project can be repeatably built.</p>
<p>This tutorial aims to show how Drone can integrate with the source code management tool Gitea in order to offer fully self-hosted solutions for SCM and CI/CD. You will be installing Drone, connecting it with Gitea, and creating a test project to see how the two services work together.</p>
<h3 id="prerequisites">Prerequisites</h3>
<h2 id="step-1-installing-drone">Step 1 — Installing Drone</h2>
<h2 id="step-2-connecting-drone-and-gitea">Step 2 — Connecting Drone and Gitea</h2>
<h2 id="step-3-setting-up-a-project-for-cicd">Step 3 — Setting Up a Project for CI/CD</h2>
<h2 id="conclusion">Conclusion</h2>
</article>
<footer>
<p>Page generated on 2022-06-28</p>
</footer>
</main>
<script type="text/javascript">
document.querySelectorAll('.tag').forEach(tag => {
let text = tag.innerText;
tag.innerText = '';
tag.innerHTML = `<a href="/tags.html#${text}">${text}</a>`;
});
</script>
</body>
</html>

1
work/index.html
View File

@ -24,6 +24,7 @@
<ul>
<li><a href="gitea-2.html">Gitea 2</a></li>
<li><a href="gitea-3.html">Gitea 3</a></li>
<li><a href="gitea-4.html">Gitea 4</a></li>
</ul>
</article>
<footer>