Monday 15 August 2011

Test result trend not appearing in Jenkins for NUnit plugin?

This was driving me crazy for a week. Some jobs were showing the trends graph, others were not.

Eventually, i solved the problem; your job's name must begin with a lower case if you there are any other upper case characters in the first word. Confused? Here's an example;

OvernightBuild_Test (graph will not appear)


overnightBuild_Test (graph will appear)


Overnight_Build_Test (graph will appear)

If you rename, it will appear (including all previous builds)


10 comments:

  1. Wow, way to go! I had something similar where I had spaces in my project name. After sticking a z in front of the name the graph appeared. Perhaps spaces are removed from the project name at some point.

    ReplyDelete
  2. Wow, most obscure bug ever. I don't even want to know how you figured this out. This did the trick for a particular job that was not showing the trend for me.

    Weird thing is, we do have some jobs with multiple caps in one word, where the test result trend did show up...

    ReplyDelete
  3. Actually, I now realise that my post isn't quite true; the rule is if your trend doesn't exist, rename the job with the opposite case at the beginning. It works for some reason!

    I have two jobs spelt exactly the same apart from one character half way through, and one of jobs has to have the case changed, the other doesn't.

    I have no idea what is going on!

    ReplyDelete
  4. hey the issue is that it re-appears when you re-save the job, a rename isnt required just a re-save. It is very irritating has any resolution been found?

    ReplyDelete
  5. I din't find that worked, it was only renaming which solved it for me.

    actually, what completely solved is that I create a service to generate graphs for me! I just used Jenkins to schedule and run.

    ReplyDelete
  6. For me, adding a space to the project name, clicking on save and answering the next question "Are you sure about renaming [projectname] to [projectname ]?" did the job and I didn't need to really rename it. Really a _very_ obscure bug...

    ReplyDelete
    Replies
    1. This comment has been removed by the author.

      Delete
  7. I no longer use Jenkins in my job, so fortunately no longer have thsi issue!

    ReplyDelete
  8. I no longer use Jenkins in my job, so fortunately no longer have thsi issue!

    ReplyDelete
  9. Jenkins also fails to render the graph if the job or view name has a space in it. E.g. if you job is called 'My Job' and so the URL has a %20 in it, Jenkins 1.509.1 LTS won't render the graph.

    ReplyDelete