Emilio Reyero

Engineering Manager at CloudBees

Seville, Andalusia, Spain
email-iconphone-icongithub-logolinkedin-logotwitter-logostackoverflow-logofacebook-logo
Join Prog.AI to see contacts
email-iconphone-icongithub-logolinkedin-logotwitter-logostackoverflow-logofacebook-logo
Join Prog.AI to see contacts

Summary

🤩
Rockstar
🎓
Top School
Emilio Reyero is an Engineering Manager based in Seville with 15 years of experience leading teams that build and operate CI/CD platforms, primarily around Jenkins and CloudBees. He combines hands-on back-end development—fixing nuanced Windows command-generation, quoting, and proxy issues in the flagship jenkinsci/jenkins repo—with DevOps and cloud automation work, scripting cluster validation and license-management flows for CloudBees deployments. Progressing from support engineer to manager at CloudBees, he brings deep operational empathy and a track record of turning real-world platform problems into reliable automation. Known for pragmatic improvements that reduce edge-case failures, he blends systems thinking with practical coding and infrastructure-as-code discipline.
code15 years of coding experience
job26 years of employment as a software developer
bookUniversity of Seville
bookHL7 Spain
stackoverflow-logo

Stackoverflow

Stats
1reputation
0reached
0answers
0questions
github-logo-circle

Github Skills (22)

groovy10
bash10
java10
cicd10
javas10
automation10
command-line-utility10
command-line10
command-line-tool10
jenkins10
jenkins-ci10
automations10
scripting9
testing9
continuous-integration9

Programming languages (4)

SmartyJavaGoGroovy

Github contributions (5)

github-logo-circle
cloudbees/jenkins-scripts

Sep 2016 - Jun 2021

Role in this project:
userDevOps Engineer & Cloud Engineer
Contributions:1 review, 37 commits, 46 PRs in 4 years 9 months
Contributions summary:Emilio's commits primarily involve scripts related to managing and deploying Jenkins instances, especially within a CloudBees environment. They made significant changes to scripts for license upgrades, including adjusting the logic for connected masters and handling potential connection issues. Moreover, the user worked on a bash script (`verify-cluster.sh`) designed for validating cluster configurations, indicating a focus on automation and infrastructure as code principles within the context of the Jenkins deployment.
jenkinsci/jenkins

Apr 2020 - Feb 2021

Jenkins automation server
Role in this project:
userBack-end Developer
Contributions:1 review, 4 commits, 5 PRs in 10 months
Contributions summary:Emilio primarily contributed to improving the `ArgumentListBuilder` class, focusing on Windows command generation for the Jenkins automation server. Their work involved fixing issues related to masked parameters, quoting, and handling special characters within the commands. Additionally, the user addressed comments and made minor improvements related to tabulation and error handling. Further, the user fixed proxy settings in the plugins page.
automationjenkinscontinuous-integrationcontinuous-deliverycontinuous-deployment
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.
Request Free Trial