[JIRA] [core] (JENKINS-20664) radiator-view plugin stop work after upgrade to 1.539
Kamal Mettananda commented on JENKINS-20664 radiator-view plugin stop work after upgrade to 1.539 We do experience the same issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9650) plugin for global build stats just hangs after clicking on create new chart
Kamal Mettananda
commented on JENKINS-9650
plugin for global build stats just hangs after clicking on create new chart
Sure Fred.
prototype.js:1585 is pending for so long.
Following is extracted from HAR--
{
"startedDateTime": "2012-11-30T08:29:45.976Z",
"time": -1,
"request": {
"method": "POST",
"url": "http://jenkins-host/plugin/global-build-stats/createChartMap?buildStatId=ID",
"httpVersion": "HTTP/1.1",
"headers": [
{
"name": "Origin",
"value": "http://jenkins-host"
},
{
"name": "X-Prototype-Version",
"value": "1.7"
},
{
"name": "X-Requested-With",
"value": "XMLHttpRequest"
},
{
"name": "User-Agent",
"value": "Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/11.10 Chromium/18.0.1025.168 Chrome/18.0.1025.168 Safari/535.19"
},
{
"name": "Content-type",
"value": "application/x-www-form-urlencoded; charset=UTF-8"
},
{
"name": "Accept",
"value": "text/_javascript_, text/html, application/xml, text/xml, */*"
},
{
"name": "Referer",
"value": "http://jenkins-host/plugin/global-build-stats/"
}
],
"queryString": [
{
"name": "buildStatId",
"value": "ID"
}
],
"cookies": [],
"headersSize": 552,
"bodySize": 0
},
"response": {
"status": 0,
"statusText": "",
"httpVersion": "HTTP/1.1",
"headers": [],
"cookies": [],
"content": {
"size": 0,
"compression": 0
},
"redirectURL": "",
"headersSize": 13,
"bodySize": 0
},
"cache": {},
"timings": {
"blocked": 0,
"dns": -1,
"connect": -1,
"send": -1,
"wait": -1,
"receive": -1,
"ssl": -1
},
"pageref": "page_1"
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9650) plugin for global build stats just hangs after clicking on create new chart
Kamal Mettananda reopened JENKINS-9650 plugin for global build stats just hangs after clicking on create new chart Plugin is hanging when the charts are being generated. Jenkins version: 1.471 Browser: Firefox Chrome Global build stats plugin version: 1.3 There are two charts; one for monthly and one for weekly stats. I am in doubt whether a separate bug is required, but thought of reporting against this existing one. Change By: Kamal Mettananda (30/Nov/12 6:06 AM) Resolution: CannotReproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13754) Error when compiling a plugin against jenkins version 1.463
Kamal Mettananda commented on JENKINS-13754 Error when compiling a plugin against jenkins version 1.463 Workaround of adding deps to POM resolved the problem. Better if someone could update HPI to include this in the POM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13754) Error when compiling a plugin against jenkins version 1.463
Kamal Mettananda edited a comment on JENKINS-13754 Error when compiling a plugin against jenkins version 1.463 Workaround of adding deps to POM resolved the problem (Maven 2.2.1 Java 6). Better if someone could update HPI to include this in the POM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Łukasz Nowak updated JENKINS-14575 SCM checkout retry count not working Change By: Łukasz Nowak (09/Aug/12 7:33 PM) Component/s: git Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Łukasz Nowak created JENKINS-14575 SCM checkout retry count not working Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin Created: 25/Jul/12 8:08 PM Description: From time to time I reveive error when getting SCM changes from Git repository and the option "SCM checkout retry count" (I have set it to 3) is not working. ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway hudson.plugins.git.GitException: Command "git fetch -t g...@github.com:xxx/xxx +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: ssh_exchange_identification: Connection closed by remote host fatal: The remote end hung up unexpectedly at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:818) at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:780) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:196) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:1026) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:812) at hudson.plugins.git.GitSCM.access$100(GitSCM.java:90) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1096) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1064) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1064) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117) at hudson.model.AbstractProject.checkout(AbstractProject.java:1249) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1488) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) ERROR: Could not fetch from any repository FATAL: Could not fetch from any repository hudson.plugins.git.GitException: Could not fetch from any repository at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1103) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1064) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1064) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117) at hudson.model.AbstractProject.checkout(AbstractProject.java:1249) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1488) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Environment: Jenkins 1.473 on Debian Project: Jenkins Priority: Blocker Reporter: Łukasz Nowak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14524) Slave agent authorization 401
Łukasz Nowak created JENKINS-14524 Slave agent authorization 401 Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 20/Jul/12 11:14 PM Description: I can connect my slave agent using the downloaded jnlp file, but Windows service is not working because of authorization. My configuration looks like this: -Xrs -jar "%BASE%\slave.jar" -auth xxx:xxx -jnlpUrl http://xxx.dyndns.org/computer/windows/slave-agent.jnlp -cp "%BASE%\lib\commons-codec-1.5.jar" -jnlpCredentials xxx:xxx And in logs I see: Failing to obtain http://homersoft-ci.dyndns.org/computer/windows/slave-agent.jnlp java.io.IOException: Failed to load http://xxx.dyndns.org/computer/windows/slave-agent.jnlp: 403 Forbidden at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:230) at hudson.remoting.Launcher.run(Launcher.java:192) at hudson.remoting.Launcher.main(Launcher.java:168) Environment: Debian as Master, Windows 2008 as Slave Project: Jenkins Priority: Critical Reporter: Łukasz Nowak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13982) No user information in build main screen
Łukasz Nowak created JENKINS-13982: -- Summary: No user information in build main screen Key: JENKINS-13982 URL: https://issues.jenkins-ci.org/browse/JENKINS-13982 Project: Jenkins Issue Type: Bug Components: github-oauth Affects Versions: current Reporter: Łukasz Nowak Assignee: Michael O'Cleirigh Attachments: build screen.jpg I turned on GitHub OAuth plugin. The authorization works well, but when I created build there is no information about the user that started it. Also the page users is empty. -- 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
