CRX id
acchkklkpbnefohnlbdjnlndnkhpcmfi
acchkklkpbnefohnlbdjnlndnkhpcmfi
Description from extension meta
The ultimate Jenkins Chrome Extension for professionals.
Image from store
Description from store
This is the ultimate Jenkins Chrome Extension for professionals.
If you use Jenkins CI for your automated builds and jobs, then you'll want to use our Chrome Extension.
You'll get alerts (via Chrome) on your desktop whenever a job fails for any reason or if a failing job succeeds. In addition, you'll be able to easily view the state of your jobs without having to browse to your Jenkins dashboard.
FEATURES:
* Receive an alert whenever a Jenkins job succeeds or fails
* Support for multiple jobs across multiple different Jenkins servers
* View failures at a glance in the extension tooltip
* Pop-up shows the state of each job with links to jump to your Jenkins server dashboard or the job page
* Color-shaded Jenkins icon shows you the overall health of your Jenkins' builds
* Plays a 'ta-da' or 'trumpet' sound when your build state changes
INSTALLATION:
1. Install the Chrome Extension
2. Click the Jenkins icon on your Chrome toolbar
3. Click Edit in the pop window to add the URL of your Jenkins server.
Requires Jenkins v1.5X.
Email derekr247 at gmail dot com if you have any questions, comments, and/or feature suggestions.
Contributors:
Aaron Magat
Alexander Schreifels
David Giannini
Derek Rodrigues
Jenkins and the Jenkins icon are copyright ownership of Jenkins CI (http://jenkins-ci.org/). The developers of this extension are not affiliated with Jenkins CI.
Latest reviews
- (2018-09-24) Aravind Sunderrajan: Works seamlessly !!
- (2018-07-11) Jorge M: cant connect to jenkins server
- (2016-02-16) Not working for my Jenkins server. Error 'Sorry, that is not a valid Jenkins server name" is completely useless at debugging whatever is wrong.
- (2015-12-08) John Byrd: Works well; I wish I could customize the sounds though. The klaxon build failure sound is too much.
- (2015-06-03) Christian Lopes: didnt work: couldn't add Jenkins server: I typed servername:port (and Enter) and got the the msg: "Sorry, that is not a valid Jenkins server name".
- (2014-08-11) Aarumuga chamy: this is really great. would it also be possible to add support for https:// ?.
- (2014-07-04) It is not working with current Jenkins(1.570). Where is the Jenkins 1.92 or higher? Lastest version is 1.570.
- (2014-05-06) Oleg Krasnukhin: It is a very nice extension that worked without any problems! Was very surprised how fast it got all information. Would be great to have an option to add specific jobs (when you need to monitor only few jobs, not all of them).
- (2014-04-24) Santhosh Sunderrajan: I like the ta-da sound!!!
Latest issues
- (2017-10-13, v:1.0.3) Michele Ippolito: localhost:8080 is not a valid server
Hi, I wanted to connect this extension to my local Jenkins install. I typed "localhost:8080" as the address and got an error saying it's not a valid server. Michael - (2015-12-16, v:1.0.3) Dennis Cheung: doesn't work with internal jenkins servers
Sorry, that is not a valid Jenkins server name - (2015-03-10, v:1.0.3) Ben Mosior: https support
I would suggest allowing https as well as http. :) - (2015-02-04, v:1.0.3) J: doesn't work with internal jenkins servers
Our jenkins server is internally accessed only and does not have an FQDN -- it's simply a http://servername/ url, and your plugin doesn't allow that. - (2014-11-09, v:1.0.3) Tobias Carlstedt: Can't connect to my local Jenkins server
When trying to connect to my local Jenkins server (which has the address http://jenkins:8080/) I get the error message "Sorry, that is not a valid Jenkins server name". Is it because of the non standard port? Please provide fix if that is the case.