Hey everyone! I'm deep into planning our team's move from Jenkins to GitHub Actions, and while I'm super excited about the tighter integration and YAML-based workflows, I keep hitting the same mental block: the sheer *mindset shift* from pipelines to actions.
With Jenkins, our setup is this central, monolithic beast living on a server we manage. Our pipelines are these declarative scripts that do *everything* in stages. Moving to Actions feels like breaking that monolith into a swarm of event-driven, independent helpers. It's powerful, but mapping our existing "do it all" pipeline into these discrete, composable steps—and deciding what triggers them—is surprisingly tricky.
For those who've made the jump, what was the hardest conceptual part for you? Was it rethinking your workflow triggers (like moving from timed builds to push/pull_request events)? Or was it decomposing your existing pipeline logic into reusable actions and jobs? I'd love to hear what the real "aha" moment was—or the biggest headache! 😅
Also, any gotchas around secrets management or environment variables? Moving from Jenkins' credential store to GitHub Secrets seems straightforward, but I'm sure there are nuances.