DevOps and performance

CI/CD pipeline setup with GitLab CI or Jenkins

We set up a pipeline that builds, tests and deploys your code on every push, with secrets kept out of the repository and a deploy user that can only touch what it needs.

  • One-time job
  • Scope agreed before work
  • Written handover

Who is this for?

  • You still deploy by copying files over FTP or SSH by hand
  • You want tests to run before code reaches production
  • You need separate staging and production environments

In short

GitLab CE or Jenkins installed, runners or agents registered, build, test and deploy pipelines, protected secrets and a limited deploy user on your server.

Packages: Basic · Standard · Complete. The price is quoted after we review your server or site.

Packages

Each package includes everything in the one before it.

Basic

11 tasks

GitLab CE or Jenkins, a runner or agent, build/test/deploy stages, protected secrets and a limited deploy user with its own SSH key.

Request a quote
Recommended

Standard

22 tasks

Everything in Basic plus staging and production, domain and SSL for the tool, notifications, Docker executor, auto-run on push and tested deploys.

Request a quote

Complete

29 tasks

Everything in Standard plus a separate runner host, Docker image builds, rollback, secret cleanup, docs and a short training.

Request a quote

What is included in each package

TaskBasicStandardComplete
Initial review
Review the repository and current release processIncludedIncludedIncluded
Check server resources for the toolsIncludedIncludedIncluded
Define staging and productionNot includedIncludedIncluded
Tools
Install GitLab CE or JenkinsIncludedIncludedIncluded
Initial usersIncludedIncludedIncluded
Domain and SSL for the toolNot includedIncludedIncluded
Email notificationsNot includedIncludedIncluded
Jenkins plugins your project needsNot includedIncludedIncluded
Runners and agents
Install and register GitLab Runner or a Jenkins agentIncludedIncludedIncluded
Pick an executor such as shell or DockerNot includedIncludedIncluded
Runner on a separate hostNot includedNot includedIncluded
Pipeline
Build and test stagesIncludedIncludedIncluded
Deploy stageIncludedIncludedIncluded
Run the pipeline on a test branchNot includedIncludedIncluded
Run automatically on every pushNot includedIncludedIncluded
Docker image build stageNot includedNot includedIncluded
Rollback to the previous releaseNot includedNot includedIncluded
Secrets
Keys and tokens in protected variablesIncludedIncludedIncluded
Separate variables per environmentNot includedIncludedIncluded
Remove old keys and check the repo has no secretsNot includedNot includedIncluded
Target server
Deploy user with limited rightsIncludedIncludedIncluded
Separate SSH key for deploysIncludedIncludedIncluded
Access only to the paths neededNot includedIncludedIncluded
Test connection and deploy on the targetNot includedIncludedIncluded
Handover
Pipeline filesIncludedIncludedIncluded
Note on adding a project or variableNot includedIncludedIncluded
Documentation of tools and environmentsNot includedNot includedIncluded
Short training on editing the pipelineNot includedNot includedIncluded
Follow-up check of pipeline runsNot includedNot includedIncluded

How it works

  1. Tell us what you needOpen a ticket and describe the job, the server or site, and any deadline.
  2. Scope and quoteWe review it and send the package, the exact scope and the price before starting.
  3. Secure access and backupYou share access through the ticket's private fields. We back up before changing anything.
  4. The workWe do the tasks in the package and test after each step.
  5. HandoverYou get the result, a written record of the changes and answers to your questions.

What we need from you

  • Access to your repository
  • SSH access to the target servers
  • How you build and run the app today

What is not included

  • Writing your application's tests is not included; we wire up the tests you have

Questions people ask

GitLab or Jenkins?

If your code is in GitLab, GitLab CI is the shortest path. Jenkins fits when you use several Git hosts or need its plugins.

Can you use GitHub Actions?

Yes, we can set up a self-hosted runner and deploy workflow for GitHub as well. Ask in a ticket.

Where does the runner run?

On your server or a separate VPS. Keeping it apart from production is safer for busy projects.

Get a quote for ci/cd setup

Open a ticket with a short description of your server or site. We reply with the scope and price.

Request a quote