search

netmelody / ci-eye

An infrastructure agnostic CI build radiator
http://netmelody.org/ci-eye/
Apache License 2.0
43 stars 26 forks source link

Mark as 'Under Investigation' seems not to work. #11

Closed lemval closed 12 years ago

lemval commented 12 years ago

I first had some thoughts about difference between a build failure or a test failure (as Jenkins/Hudson supports). It is tempting to ask for to differentiate between those states using a different color. However, I must state that all red is pretty good: failed tests is no more and no less a broken build.

Under Investigation is a usefull addition though to differentiate. Letting others know someone is working on the build to make it run again.

Fixed might not be so usefull, since it is fixed no sooner the build is no longer broken.

However, both options do not work. I can manually (and locally) change the class type to 'UNDER_INVESTIGATION' to show a job orange (this won't get overwritten in a refresh, it seems) and I can see the post with the note to the server. However using the menu does not change the appearance anywhere.

Using FF11 on WinXP.

Thanks.

scarytom commented 12 years ago

Strongly agree with your first point -- and hence by design CI-Eye treats all breaks as RED regardless of cause.

There is a really simple reason why the "Mark as..." options do not work for you, and this is my fault. CI-Eye deliberately avoids maintaining state, and relies as far as possible on the underlying CI server (Jenkins in this case) to do this. When marking a build, CI-Eye tries to add a comment to the build on the CI server, but if you have user accounts and passwords on your Jenkins instance then it will fail. You can prove that marking builds would work by manually adding a comment to a failed build in Jenkins -- it should then (after a few seconds) appear orange on CI-Eye instead of red.

Now for the bit that is my fault: At present there is no way to specify a user/password for CI-Eye to use to log into your Jenkins instance and add comments. This has been number 1 on my TODO list for some time. Currently CI-Eye assumes a username of "ci" and a blank password. In the short term, if you want to get marking builds working, I suggest you add such a user to you Jenkins instance. In the long term, I intend to allow a user/password to be specified in the views.txt

scarytom commented 12 years ago

The latest release of CI-Eye (v0.4.0) allows authenticated access to the underlying CI servers, and hence should fix this issue. See documentation on the Wiki for how to configure.

I'm closing this issue for now, but feel free to comment if you are still having problems.