PHPackages                             xtraorange/jenkinize\_laravel - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. xtraorange/jenkinize\_laravel

ActiveLibrary

xtraorange/jenkinize\_laravel
=============================

Create an CI/CD pipeline in any Laravel project with fewer steps.

v0.1.4(2y ago)016Dockerfile

Since Jul 1Pushed 2y ago1 watchersCompare

[ Source](https://github.com/xtraorange/JenkinizeLaravel)[ Packagist](https://packagist.org/packages/xtraorange/jenkinize_laravel)[ RSS](/packages/xtraorange-jenkinize-laravel/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependenciesVersions (6)Used By (0)

Jenkinize Laravel
=================

[](#jenkinize-laravel)

Jenkinize Laravel is a utility to facilitate the configuration of your Laravel environment and setup your deployment pipeline with Jenkins. It enables you to establish your development, staging, and production environments with just a few simple steps.

Getting Started
---------------

[](#getting-started)

Follow these instructions to integrate "Jenkinize Laravel" into your existing or new Laravel project.

### Prerequisites

[](#prerequisites)

Before you begin, make sure you have:

- [Docker](https://www.docker.com/) installed.
- [Jenkins](https://www.jenkins.io/) installed.
- A [Laravel](https://laravel.com/) project set up.
- A [GitHub](https://github.com/) account.

### Pre-setup Steps

[](#pre-setup-steps)

1. Create MySQL volumes (`project_name_env_mysql`).
2. Create environment networks (`project_name_env_network`).
3. Set up the MySQL stack using the `mysql_portainer_custom_template.txt` provided in the repository.
4. Verify the configuration in your `Jenkinsfile`.
5. Push your code to the repository and let Jenkins handle the rest.

### Installation

[](#installation)

To install "Jenkinize Laravel", follow these steps:

1. Navigate to your Laravel project directory.
2. Require "Jenkinize Laravel" into your project using Composer:

    `composer require xtraorange/jenkinize-laravel`
3. In Jenkins, create a new multi-branch pipeline.
4. Choose GitHub as the branch source and provide your GitHub credentials.
5. Add your repository URL and validate it.
6. Set "Discover branches" to "All Branches".

Next, you need to publish all the assets that you want to use. You can either publish all assets by running: `php artisan vendor:publish`

Or publish specific assets by specifying their tags: `php artisan vendor:publish --tag=jenkinsfile``php artisan vendor:publish --tag=jenkinize-config``php artisan vendor:publish --tag=docker``php artisan vendor:publish --tag=docker-jenkins`

### Usage

[](#usage)

Once "Jenkinize Laravel" is installed, you can set up your environments and deployment pipeline:

1. Create a definition for each of your environments in the `jenkinize.config` file.
2. For each environment, create a corresponding `.env.[environment name]` file. Avoid storing sensitive information in this file.
3. For each environment, create a corresponding secret in Jenkins for sensitive environment variable values.

(Provide more detailed instructions here)

Contributing
------------

[](#contributing)

If you'd like to contribute, please fork the repository and use a feature branch. Pull requests are warmly welcome.

License
-------

[](#license)

This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details.

### TODO

[](#todo)

- Explore Docker registry options in Jenkins.
- Specify Jenkins Docker deployment details.
- Implement automatic deployment of an appropriate database image (perhaps create a dedicated directory for Docker files?).
- Refine stage setups.
- Write setup instructions for Jenkins and other prerequisite components.

###  Health Score

19

—

LowBetter than 10% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity38

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~4 days

Total

5

Last Release

1032d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/c648298885c5f578b1daea9973867438ec43decbe6a1898812955777dfef584f?d=identicon)[xtraorange](/maintainers/xtraorange)

---

Top Contributors

[![xtraorange](https://avatars.githubusercontent.com/u/1166896?v=4)](https://github.com/xtraorange "xtraorange (11 commits)")

### Embed Badge

![Health badge](/badges/xtraorange-jenkinize-laravel/health.svg)

```
[![Health](https://phpackages.com/badges/xtraorange-jenkinize-laravel/health.svg)](https://phpackages.com/packages/xtraorange-jenkinize-laravel)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)