Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

    •  
      request #9679 No iFrame with Hudson
    Infos
    #9679
    Kelly Ferrone (kferrone)
    2016-12-06 21:44
    2016-11-25 23:32
    9961
    Details
    No iFrame with Hudson

    So I have been fighting with Hudson now for a while. Now I finally got Hudson all up and running and all of a sudden Tuleaps "Continuous Integration" section on the builds shows an empty iFrame and it links to something like this "http://localhost:8089/hudson/job/my-project-build/" which does not resolve to anything because it's localhost. 

    I was unable to find any errors anywhere. Earlier the iFrames and everything with Hudson worked fine, then right after I got Hudson to finally clone a GIT repo from Tuleap they disappeared and now point to localhost. I also restarted the server in the mean time, could something not have turned on correctly? 

    Other steps I took include adding my CI server to known hosts by using SSH and is asks to add to known_hosts file. 

    Anyone know how to get the iFrame to come back?

    Any advice on how I can debug the iFrames?

    Continuous Integration
    9.1
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    New
    Empty
    Attachments
    Empty
    References
    Referencing request #9679

    Follow-ups

    User avatar

    I'll check this out. I have my server admin on it. Hope it works. What's weird is it worked totally fine before. All of a sudden this started happening. 

    User avatar
    The empty iframe is a security protection used by browsers to prevent clickjacking. You may try to configure your jenkins webserver to provide the X-Frame-Options HTTP header, as stated in https://tools.ietf.org/html/rfc7034, so that it permits the display of its content in an iframe.
    User avatar
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes