> ## Documentation Index
> Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Demo Create Organization Folder Project
> This tutorial explains how to create an Organization Folder project in Jenkins using Gitea-hosted repositories.
In this step-by-step tutorial, you'll learn how to use Jenkins' Organization Folder project type with Gitea-hosted repositories. You'll:
1. Migrate a GitHub repository to Gitea
2. Install and configure the Gitea plugin in Jenkins
3. Create and configure an Organization Folder
4. Observe automatic multibranch pipeline creation and webhook-triggered builds
***
## 1. Migrate the Solar System Repository to Gitea
First, copy the clone URL of the Solar System repository from GitHub:
Sign in to your Gitea instance:
Go to your organization (e.g., `dasher-org`) and click **+ → New Migration**:
Paste the GitHub URL, set the owner to `dasher-org`, and name the repo **solar-system**:
Once migration completes, verify the new repository by visiting its Gitea page:
***
## 2. Why Use an Organization Folder?
Manually creating a separate Pipeline job for each repository or branch can quickly become a maintenance headache. With the Organization Folder, Jenkins automatically scans your SCM, creates or removes jobs based on your configuration, and keeps everything in sync.
| Aspect | Manual Pipelines | Organization Folder |
| ----------------- | --------------------------- | ------------------------- |
| Setup per repo | Manual each time | Single configuration |
| Branch management | Manual updates | Automatic discovery |
| Scalability | Limited by manual processes | Scales with your codebase |
Organization Folders streamline multibranch pipeline management and support GitHub, Bitbucket, Gitea, and more.
For further details, see the [Jenkins documentation](https://www.jenkins.io/doc/):
***
## 3. Create an Organization Folder in Jenkins
1. From the Jenkins dashboard, click **New Item**.
2. Enter **GitHub Organization** (or any descriptive name).
3. Select **Organization Folder** and click **OK**:
***
## 4. Install and Configure the Gitea Plugin
### Install the Plugin
1. Navigate to **Manage Jenkins → Manage Plugins**.
2. In the **Available** tab, search for **Gitea plugin**.
3. Select and install it, checking **Restart Jenkins when installation is complete and no jobs are running**:
Wait for the installation to finish:
After Jenkins restarts, verify the plugin is listed under **Installed**:
### Configure Gitea Server
1. Go to **Manage Jenkins → Configure System**.
2. Scroll to **Gitea Servers** and click **Add Gitea Server**.
3. Enter:
* **Name**: Gitea server
* **API URL**: `https:///api/v1`
4. Check **Manage hooks** to enable automatic webhook creation.
5. Next to **Credentials**, click **Add**, select **Username with password**, and enter your Gitea credentials (scope: Global):
6. Click **Apply** and **Save**:
***
## 5. Configure the Organization Folder
1. Open the **GitHub Organization** item and click **Configure**.
2. Under **Repository Sources**, click **Add Source → GitHub Organization**.
3. Select:
* **GitHub Server**: your configured server
* **Credentials**: the admin credential you added
* **Owner**: `dasher-org`
4. Leave discovery and project recognizer settings at default (looks for `Jenkinsfile`):
5. Click **Save**. Jenkins begins scanning the organization immediately.
***
## 6. Organization Scan and Job Creation
During the scan, Jenkins inspects each repository and its branches for a `Jenkinsfile`. Only those that match will have jobs created or updated.
Example scan output:
```text theme={null}
Checking repository parameterized-pipeline-job-init
Proposing parameterized-pipeline-job-init
Looking up repository dasher-org/parameterized-pipeline-job-init
Checking branches...
Checking branch main
'Jenkinsfile' found
Met criteria
1 branches were processed (query completed)
Checking repository solar-system
Proposing solar-system
Looking up repository dasher-org/solar-system
Checking branches...
Checking branch main
'Jenkinsfile' not found
Does not meet criteria
1 branches were processed
Checking pull requests...
0 pull requests were processed
3 repositories were processed
[Mon Sep 23 07:23:10 UTC 2024] Finished organization scan. Scan took 1.8 sec
Finished: SUCCESS
```
In this example:
* `parameterized-pipeline-job-init` → multibranch pipeline created
* `solar-system` → skipped (no `Jenkinsfile`)
***
## 7. Inspecting Branch Pipelines
Click the **parameterized-pipeline-job-init** item to view branch-level pipelines:
Repository details such as files and commit history are pulled from Gitea:
***
## 8. Webhook Configuration and Automatic Triggers
By enabling **Manage hooks**, Jenkins automatically adds webhooks to each repository. These webhooks trigger builds on push, branch/tag creation, and pull request events.
For example, edit the `README` in the `main` branch:
```bash theme={null}
git checkout main
# edit README.md
git add README.md
git commit -m "Edited README"
git push origin main
```
The webhook notifies Jenkins, triggering a new build:
Ensure your Gitea API token has permissions to create webhooks and read repositories.
***
## Conclusion
After adding a `Jenkinsfile` to the `solar-system` repository, Jenkins picks it up in the next scan and automatically creates a pipeline:
***
## Links and References
* [Jenkins Documentation](https://www.jenkins.io/doc/)
* [Gitea Documentation](https://docs.gitea.io/)
* [Gitea Plugin for Jenkins](https://plugins.jenkins.io/gitea/)