Inspiration
While developing a BDD automation framework for a client, I got annoyed that each team member must pull down the project and execute via command line. CLI is not friendly to most testers, and good luck getting Devs to keep another terminal open for acceptance tests! I wanted a way to tie the Issue to a Jenkins build so I could integrate Selenium automation within the JIRA platform. The solution? Execute, a button to run Jenkins Jobs.
What it does
Runs Jenkins jobs.
How I built it
I created a JIRA plugin to communicate with the Jenkins Remote access API.
Challenges I ran into
TBD
Accomplishments that I'm proud of
TBD
What I learned
TBD
What's next for Execute
Execute will probably languish in solitude on GitHub until I stop caring about it. :D
Log in or sign up for Devpost to join the conversation.