[ 
https://issues.jenkins-ci.org/browse/JENKINS-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163204#comment-163204
 ] 

Kohsuke Kawaguchi commented on JENKINS-9142:
--------------------------------------------

In 1.467 I put the probe code that provides optional logging.

To enable this optional logging, first execute the following code in Groovy 
console. This enables this debug logging feature:

{noformat}org.kohsuke.stapler.bind.BoundObjectTable.DEBUG_LOGGING=true;{noformat}

Then, from type {{http://localhost:8080/$stapler/bound/table/enableLogging}} in 
the address bar. If this page reports back that the logging is enabled, your 
HTTP session and object binding activity is now logged to the server console.

You can then visit the configuration page, etc.

When you notice that that "add build step" (or some other similar activities 
that loads additional HTTP fragments) aren't working, check the developer tool 
to look up the GUID of the bound object that's causing the issue. Then search 
that GUID in the server log to see if {{BoundObjectTable}} reports anything 
about that GUID.

Thank you for your cooperation in the data gathering process. Your input would 
help us understand the root cause better.
                
> "Add Build Step" button broken in job configure page
> ----------------------------------------------------
>
>                 Key: JENKINS-9142
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-9142
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: CentOS linux x86_64 firefox 3.6.15
>            Reporter: Andrew Helfer
>            Priority: Blocker
>
> after upggrading from Hudson 1.395 to Jenkins 1.403 and installing the 
> msbuild and VCviewer plugins, the add build step button no longer works.  
> Doesn't add a shell window to the web UI, no matter what I do.
> Last known successful action was to delete a step, first unsuccessful action 
> was to add an msbuild step.
> there are no Java console errors or warnings, and nothing in the logs to 
> suggest anything wrong.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to