Hey folks, just saw the official announcement come across my feed and my first thought was... well, my second thought was about my `.jx` folder. My *first* thought was "what's everyone's playbook here?" 😅
I've been using Jenkins X for about 18 months, mostly for its baked-in GitOps approach and preview environments. The pipeline definitions living right in the repo was a huge win. But now, the sunsetting news means a migration project just landed in my lap—and probably yours too. I'm already mentally cataloging all the pieces that will need a new home:
* The entire pipeline translation (those `jenkins-x.yml` files aren't going to run themselves elsewhere).
* All the build packs and custom quickstarts we tweaked.
* The secrets management—migrating those securely gives me mild anxiety.
* The ingress and TLS setup for those preview environments.
* The developer experience of creating new services.
I'm naturally leaning towards something like GitHub Actions or GitLab CI, given their deep Git integration, but I'm also eyeing Tekton or even Argo CD for the GitOps piece. The real curiosity for me is how to recreate that "almost magic" feel of Jenkins X's automated CI/CD without building a Frankenstein's monster of scripts.
Has anyone started drafting a migration plan yet? I'd love to compare notes on the actual translation pain. For instance, how are you mapping something like this Jenkins X pipeline stage...
```yaml
pipelineConfig:
pipelines:
pullRequest:
build:
steps:
- command: make test
image: golang:1.19
- command: make build
image: golang:1.19
```
...to another platform's syntax? Are you going for a direct functional translation, or using this as a chance to refactor and improve the workflow?
Also, the *time* factor—how long do we think a full migration for a mid-sized project with, say, 15-20 microservices will *actually* take? A weekend? A month? I'm trying to set realistic expectations for my team.
What's your top contender for the new platform, and what's the biggest hurdle you're anticipating? Let's swap some config snippets and war stories.
editor is my home
Yeah, that "what's the playbook?" feeling hit me too. That `.jx` folder is a weird mix of comfort and dread now, isn't it?
I'm with you on the pipeline translation being the biggest lift. Those `jenkins-x.yml` files have a specific flavor. In my own planning, I've found treating them as a reference spec works better than trying for a direct conversion. We're sketching out the same stages in, say, GitHub Actions workflows or Tekton Pipelines, but accepting that the syntax is a rewrite. It's a chance to clean up some old pipeline cruft, honestly.
For the "almost magic" GitOps and preview environments, my bet is on Argo CD for the GitOps engine, paired with something like Argo Workflows or Tekton for the CI execution. It's more pieces to glue together than Jenkins X gave you out of the box, but you get to own each piece. The preview environment automation is the trickiest part to rebuild, but there are some cool patterns floating around using pull request comment bots to trigger the environment teardown. Have you started prototyping anything yet?
YAML is my love language