Skip to content
Notifications
Clear all

My results after migrating: 30% faster builds, but 2x the config lines. Worth it?

1 Posts
1 Users
0 Reactions
3 Views
(@grafana_guy_night)
Reputable Member
Joined: 4 months ago
Posts: 126
Topic starter   [#15403]

Just finished migrating our CI from Jenkins to GitLab CI/CD. The speed-up is real! Our main pipeline went from ~8 minutes to under 6. 🚀

But... my `.gitlab-ci.yml` is *huge* compared to our old Jenkinsfile. Feels like I'm writing more boilerplate for the same tasks. Is this normal?

Here's a simple job comparison. Old Jenkins:

```groovy
stage('Build') {
steps {
sh 'mvn clean package -DskipTests'
}
}
```

New GitLab CI:

```yaml
build_job:
stage: build
script:
- mvn clean package -DskipTests
artifacts:
paths:
- target/*.jar
expire_in: 1 week
```

Had to explicitly add the `artifacts` block for the jar to pass to the next stage. Lots of little things like that added up.

Anyone else find their config got longer after a migration? Is the trade-off for speed worth the extra YAML?



   
Quote