Introduction — Shubham: a first Jenkins UI regression task

Hi everyone, I’m Shubham Padkonde (GitHub: Shubham-Padkonde). I work mainly with Python and JavaScript, and my recent contributions include regression fixes in Music Blocks: fix: prevent overflow when accumulating MusicXML ties by Shubham-Padkonde · Pull Request #9850 · sugarlabs/musicblocks · GitHub. I’m starting to learn Jenkins while preparing for GSoC 2027.

I read the core development guide, including the separate frontend build and the need to exercise changed UI behavior. I also looked at #27597, the undefined button label when reopening a new API token. That already has PR #27598, so I won’t duplicate its fix.

Would a bounded browser regression task be useful for a first contribution—such as checking repeated open/close behavior and button labels on an existing change, or a current unowned UI bug? Could a maintainer delegate one specific scope to me? I haven’t built Jenkins or run these checks yet, and Java/Maven is new territory for me, so I’d start with the documented setup and a clear reproduction before making changes.

Existing fix: Fix button label when reopening a newly created API token by ollehu · Pull Request #27598 · jenkinsci/jenkins · GitHub