Jump to content

Recommended Posts

Hi all,

 

I've created a workflow for interacting with a Jenkins CI instance. Currently it only supports fetching the status of the builds but I'm planning on expanding this to getting the health of the builds, starting builds and some other neat features.

 

You can download it from here, or you can check out the GitHub repository here.

 

When you've installed it in Alfred, be sure to set the correct URL to your Jenkins CI instance via:

Alfred > Preferences > Workflows > Jenkins > Script Filter

And then entering the correct URL in the "Script" box.

 

Be sure to let me know (either here or on GitHub) if you run into any issues, or if you have any ideas!

 

 

alfred-jenkins-workflow-screenshot.png

* project names and statuses added for illustrative purposes

Edited by RevellNL

Share this post


Link to post

Updated, as shown in the screenshot in first post, the result now shows the health and status for the build, as well as some extra information in the subtext.

 

Be sure to update!

Share this post


Link to post

Fantastic idea, unfortunately doesn't work for me. My guess would be it's because our Jenkins instance requires login with Google credentials. 

Share this post


Link to post

Fantastic idea, unfortunately doesn't work for me. My guess would be it's because our Jenkins instance requires login with Google credentials. 

 

Hmm, I wonder if that would be solveable using HTTP BASIC authentication. I don't really have an instance to test this on though =(

 

I've added an issue for it in the GitHub repository, you can keep track of the progress there, as well as elaborate on the issue if needed. https://github.com/jeroenseegers/alfred-jenkins-workflow/issues/3

Edited by RevellNL

Share this post


Link to post

Fantastic idea, unfortunately doesn't work for me. My guess would be it's because our Jenkins instance requires login with Google credentials. 

 

 

Hmm, I wonder if that would be solveable using HTTP BASIC authentication. I don't really have an instance to test this on though =(

 

I've added an issue for it in the GitHub repository, you can keep track of the progress there, as well as elaborate on the issue if needed. https://github.com/jeroenseegers/alfred-jenkins-workflow/issues/3

 

Ours also requires and Basic seemed to do the trick for me.

 

Just set your url to http://USERNAME:PASSWORD@jenkins.url/

 

EDIT:

 

Just realized you were using google creds.  Might be able to still get by with this. Or maybe a one time use password if you are using two factor.

Edited by wmbest2

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×