Failed build logs in the UI?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Failed build logs in the UI?

Eric Crahen-3
I've been using Hudson 1.68, and I have a situation where the svn command failed because of a trust issue. I was checking source out of a svn server over https, and the server has a misconfigured certifiact (the hostname used in the self-signed cert was wrong).

I have a failure in the Hudson console, but no link to a log to see what went wrong. If I look in the HUDSON_HOME, I can dig up the error:
(builds/2007-01-08_11-17-49
/log)

[workspace] $ svn co --non-interactive <a href="https://server/svn/project/trunk" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://server/svn/project/trunk
svn: PROPFIND request failed on '/svn/project/trunk'
svn: PROPFIND of '/svn/project/trunk': Server certificate verification failed: certificate issued for a different hostname, issuer is not trusted ( <a href="https://server/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">https://server)
ERROR: Subversion failed. exit code=1

It would be nice if this was accessible through the console. The console link for the last failure goes to a page where the little notepad icon says not yet determined.

Do you think it is possible to add a link to that log file I found?


--

- Eric
Reply | Threaded
Open this post in threaded view
|

Re: Failed build logs in the UI?

Kohsuke Kawaguchi-2
Eric Crahen wrote:

> I've been using Hudson 1.68, and I have a situation where the svn command
> failed because of a trust issue. I was checking source out of a svn server
> over https, and the server has a misconfigured certifiact (the hostname used
> in the self-signed cert was wrong).
>
> I have a failure in the Hudson console, but no link to a log to see what
> went wrong. If I look in the HUDSON_HOME, I can dig up the error:
> (builds/2007-01-08_11-17-49/log)
>
> [workspace] $ svn co --non-interactive https://server/svn/project/trunk
> svn: PROPFIND request failed on '/svn/project/trunk'
> svn: PROPFIND of '/svn/project/trunk': Server certificate verification
> failed: certificate issued for a different hostname, issuer is not trusted (
> https://server)
> ERROR: Subversion failed. exit code=1
>
> It would be nice if this was accessible through the console. The console
> link for the last failure goes to a page where the little notepad icon says
> not yet determined.
Note that the log file is accessible from the web UI under "console output".

As for displaying "failed to determine" (with a link to log) instead of
"not yet determined". I think it makes sense. Please file an RFE.


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Failed build logs in the UI?

Eric Crahen-3
Great. Thanks alot.

On 1/8/07, Kohsuke Kawaguchi <[hidden email]> wrote:
Eric Crahen wrote:

> I've been using Hudson 1.68, and I have a situation where the svn command
> failed because of a trust issue. I was checking source out of a svn server
> over https, and the server has a misconfigured certifiact (the hostname used
> in the self-signed cert was wrong).
>
> I have a failure in the Hudson console, but no link to a log to see what
> went wrong. If I look in the HUDSON_HOME, I can dig up the error:
> (builds/2007-01-08_11-17-49/log)
>
> [workspace] $ svn co --non-interactive https://server/svn/project/trunk
> svn: PROPFIND request failed on '/svn/project/trunk'
> svn: PROPFIND of '/svn/project/trunk': Server certificate verification
> failed: certificate issued for a different hostname, issuer is not trusted (
> https://server)
> ERROR: Subversion failed. exit code=1
>
> It would be nice if this was accessible through the console. The console
> link for the last failure goes to a page where the little notepad icon says
> not yet determined.

Note that the log file is accessible from the web UI under "console output".

As for displaying "failed to determine" (with a link to log) instead of
"not yet determined". I think it makes sense. Please file an RFE.


--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]





--

- Eric