[JIRA] [github-oauth] (JENKINS-24866) github-oauth does not work behind proxies nor authentication proxies
OHTAKE Tomohiro commented on JENKINS-24866 github-oauth does not work behind proxies nor authentication proxies I have create a pull request. https://github.com/jenkinsci/github-oauth-plugin/pull/30 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/d/optout.
[JIRA] [github-oauth] (JENKINS-24866) github-oauth does not work behind proxies nor authentication proxies
OHTAKE Tomohiro updated JENKINS-24866 github-oauth does not work behind proxies nor authentication proxies Change By: OHTAKE Tomohiro (25/Sep/14 1:03 PM) Description: github-oauth merged [jenkinsci/github-oauth-plugin#15|https://github.com/jenkinsci/github-oauth-plugin/pull/15] and now uses jenkins proxy configuration [jenkinsci/github-oauth-plugin@09dc928f24a633cd5dc41033be3196e6eb47b325|https://github.com/jenkinsci/github-oauth-plugin/commit/09dc928f24a633cd5dc41033be3196e6eb47b325].But proxy support is incomplete.# It does not work behind non-authentication proxies, because github-api does not support proxies in some cases. ([kohsuke/github-api#109|https://github.com/kohsuke/github-api/issues/109] and [kohsuke/github-api#124|https://github.com/kohsuke/github-api/pull/124])# It does not respect Jenkins' noProxyHost.# It does not support authentication proxies. 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/d/optout.
[JIRA] [github-oauth] (JENKINS-24866) github-oauth does not work behind proxies nor authentication proxies
OHTAKE Tomohiro started work on JENKINS-24866 github-oauth does not work behind proxies nor authentication proxies Change By: OHTAKE Tomohiro (25/Sep/14 1:02 PM) Status: Open In Progress 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/d/optout.
[JIRA] [github-oauth] (JENKINS-24866) github-oauth does not work behind proxies nor authentication proxies
OHTAKE Tomohiro created JENKINS-24866 github-oauth does not work behind proxies nor authentication proxies Issue Type: Bug Assignee: OHTAKE Tomohiro Components: github-oauth Created: 25/Sep/14 1:01 PM Description: github-oauth merged jenkinsci/github-oauth-plugin#15 and now uses jenkins proxy configuration jenkinsci/github-oauth-plugin@09dc928f24a633cd5dc41033be3196e6eb47b325. But proxy support is incomplete. It does not work behind non-authentication proxies, because github-api does not support proxies in some cases. (kohsuke/github-api#109 and kohsuke/github-api#124) It does not support authentication proxies. Environment: github-oauth-0.19 Jenkins 1.581 OpenJDK 7u65-2.5.2-3~14.04 Ubuntu 14.04.1 LTS x86_64 Project: Jenkins Priority: Minor Reporter: OHTAKE Tomohiro 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/d/optout.
[JIRA] [ghprb] (JENKINS-24592) ghprb does not support proxies
OHTAKE Tomohiro updated JENKINS-24592 ghprb does not support proxies Change By: OHTAKE Tomohiro (17/Sep/14 7:30 AM) Environment: ghprb 1. 15 16 - 1 0 Jenkins 1. 578 580 OpenJDK 7u65-2.5. 1 2 - 4ubuntu1 3 ~ 0. 14.04 .2 Ubuntu 14.04.1 LTS x86_64 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/d/optout.
[JIRA] [git-client] (JENKINS-24112) git-client does not support authentication proxy
OHTAKE Tomohiro closed JENKINS-24112 as Fixed git-client does not support authentication proxy Change By: OHTAKE Tomohiro (17/Sep/14 7:23 AM) Status: Resolved Closed 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/d/optout.
[JIRA] [ghprb] (JENKINS-24592) ghprb does not support proxies
OHTAKE Tomohiro started work on JENKINS-24592 ghprb does not support proxies Change By: OHTAKE Tomohiro (05/Sep/14 3:00 AM) Status: Open In Progress 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/d/optout.
[JIRA] [ghprb] (JENKINS-24592) ghprb does not support proxies
OHTAKE Tomohiro commented on JENKINS-24592 ghprb does not support proxies I have create a pull request https://github.com/jenkinsci/ghprb-plugin/pull/49 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/d/optout.
[JIRA] [ghprb] (JENKINS-24592) ghprb does not support proxies
OHTAKE Tomohiro created JENKINS-24592 ghprb does not support proxies Issue Type: Bug Assignee: OHTAKE Tomohiro Components: ghprb Created: 05/Sep/14 2:56 AM Description: GitHub Pull Request Builder plugin does not work behind HTTP proxies. Sep 03, 2014 2:09:00 PM org.jenkinsci.plugins.ghprb.GhprbGitHub connect SEVERE: Can't connect to https://api.github.com using oauth Sep 03, 2014 2:09:00 PM org.jenkinsci.plugins.ghprb.GhprbRepository initGhRepository SEVERE: Error while accessing rate limit API java.net.UnknownHostException: api.github.com at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618) at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:160) at sun.net.NetworkClient.doConnect(NetworkClient.java:180) at sun.net.www.http.HttpClient.openServer(HttpClient.java:432) at sun.net.www.http.HttpClient.openServer(HttpClient.java:527) at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:275) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:932) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1300) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at org.kohsuke.github.Requester.parse(Requester.java:383) at org.kohsuke.github.Requester._to(Requester.java:185) at org.kohsuke.github.Requester.to(Requester.java:160) at org.kohsuke.github.GitHub.getMyself(GitHub.java:265) at org.kohsuke.github.GitHub.(GitHub.java:134) at org.kohsuke.github.GitHub.connectUsingOAuth(GitHub.java:191) at org.jenkinsci.plugins.ghprb.GhprbGitHub.connect(GhprbGitHub.java:22) at org.jenkinsci.plugins.ghprb.GhprbGitHub.get(GhprbGitHub.java:38) at org.jenkinsci.plugins.ghprb.GhprbRepository.initGhRepository(GhprbRepository.java:49) at org.jenkinsci.plugins.ghprb.GhprbRepository.check(GhprbRepository.java:72) at org.jenkinsci.plugins.ghprb.Ghprb.run(Ghprb.java:97) at org.jenkinsci.plugins.ghprb.GhprbTrigger.run(GhprbTrigger.java:140) at hudson.triggers.Trigger.checkTriggers(Trigger.java:266) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:214) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Environment: ghprb 1.15-1 Jenkins 1.578 OpenJDK 7u65-2.5.1-4ubuntu1~0.14.04.2 Ubuntu 14.04.1 LTS x86_64 Project: Jenkins Priority: Major Reporter: OHTAKE Tomohiro
[JIRA] [memegen] (JENKINS-15041) Proxy support
OHTAKE Tomohiro resolved JENKINS-15041 as Fixed Proxy support The issue has been resolved in source code. https://github.com/jenkinsci/memegen-plugin/commit/ccf7a8516d8b1ca258467398c5ac805c72728171 But it is not released yet. Change By: OHTAKE Tomohiro (05/Sep/14 2:49 AM) Status: Open Resolved Resolution: Fixed 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/d/optout.
[JIRA] [git-client] (JENKINS-24112) git-client does not support authentication proxy
OHTAKE Tomohiro commented on JENKINS-24112 git-client does not support authentication proxy I have created a pull request. https://github.com/jenkinsci/git-client-plugin/pull/141 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/d/optout.
[JIRA] [git-client] (JENKINS-24112) git-client does not support authentication proxy
OHTAKE Tomohiro started work on JENKINS-24112 git-client does not support authentication proxy Change By: OHTAKE Tomohiro (05/Aug/14 9:55 AM) Status: Open In Progress 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/d/optout.
[JIRA] [git-client] (JENKINS-24112) git-client does not support authentication proxy
OHTAKE Tomohiro created JENKINS-24112 git-client does not support authentication proxy Issue Type: Bug Assignee: OHTAKE Tomohiro Components: git-client Created: 05/Aug/14 9:28 AM Description: When Jenkins is behind an authentication proxy, git-client cannot checkout git repository. Cloning the remote Git repository Cloning repository https://example.com/example.git > git init /var/lib/jenkins/jobs/test/workspace # timeout=10 Fetching upstream changes from https://example.com/example.git > git --version # timeout=10 using .gitcredentials to set credentials > git config --local credential.helper store --file=/tmp/git3935065820026506239.credentials # timeout=10 Setting http proxy: http://example.local:8080/ > git fetch --tags --progress https://example.com/example.git +refs/heads/*:refs/remotes/origin/* > git config --local --remove-section credential # timeout=10 ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress https://example.com/example.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: unable to access 'https://example.com/example.git': Received HTTP code 407 from proxy after CONNECT at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1407) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1195) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:87) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:266) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:422) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:848) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:881) at hudson.model.AbstractProject.checkout(AbstractProject.java:1254) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:624) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530) at hudson.model.Run.execute(Run.java:1732) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) ERROR: null Finished: FAILURE Environment: Jenkins 1.574 Git client plugin 1.10.1 Git plugin 2.2.4 Ubuntu 13.10 x64 OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1~0.13.10.1) Project: Jenkins Priority: Major Reporter: OHTAKE Tomohiro 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/d/optout.
[JIRA] [ec2] (JENKINS-18855) EC2 plugin does not work behind proxy server
OHTAKE Tomohiro commented on JENKINS-18855 EC2 plugin does not work behind proxy server I have created a pull request. https://github.com/jenkinsci/ec2-plugin/pull/90 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/d/optout.
[JIRA] [ec2] (JENKINS-18855) EC2 plugin does not work behind proxy server
OHTAKE Tomohiro updated JENKINS-18855 EC2 plugin does not work behind proxy server Change By: OHTAKE Tomohiro (14/May/14 8:18 AM) Assignee: Francis Upton OHTAKE Tomohiro 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/d/optout.
[JIRA] [git] (JENKINS-21057) Cannot checkout git repository with submodules: "FATAL: No remotes found!"
OHTAKE Tomohiro updated JENKINS-21057 Cannot checkout git repository with submodules: "FATAL: No remotes found!" Change By: OHTAKE Tomohiro (18/Dec/13 11:49 PM) Component/s: git-client 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] [git] (JENKINS-21057) Cannot checkout git repository with submodules: "FATAL: No remotes found!"
OHTAKE Tomohiro created JENKINS-21057 Cannot checkout git repository with submodules: "FATAL: No remotes found!" Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 18/Dec/13 7:49 AM Description: Steps to reproduce Create a free-style project. Set "Git Repository URL". The repository specified should use submodules. In "Additional Behaviours", add "Advanced sub-modules behaviours" and check "Recursively update submodules". Build it. Expected result Workspace should have git working tree and submodules. Actual console log Cloning the remote Git repository Cloning repository git://***/*.git Fetching upstream changes from git://***/*.git Fetching upstream changes from git://***/*.git Checking out Revision 0123456789abcdef0123456789abcdef01234567 (origin/master) FATAL: No remotes found! hudson.plugins.git.GitException: No remotes found! at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getDefaultRemote(CliGitAPIImpl.java:702) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.setupSubmoduleUrls(CliGitAPIImpl.java:863) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:69) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:882) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) 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:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Actual .git/config [core] repositoryformatversion = 0 filemode = false logallrefupdates = true There is no [remote "origin"] nor [submodule "submodule-name"] sections. Workaround One of the followings: Downgrade git plugin to 1.5 Do not check "Recursively update submodules" Do not checkout git repository with submodules Environment: Master: Jenkins 1.544, Git Plugin 2.0, Ubuntu 13.10 64bit, OpenJDK 1.7.0_25-b30 Slave: CentOS 6.5 64bit, OpenJDK 1.7.0_45, Git 1.7.1 Project: Jenkins Priority: Major Reporter: OHTAKE Tomohiro 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-15328) Build name in promotion log is broken
OHTAKE Tomohiro resolved JENKINS-15328 as Fixed Build name in promotion log is broken Change By: OHTAKE Tomohiro (27/Sep/12 7:01 AM) Status: In Progress Resolved Resolution: Fixed 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-15328) Build name in promotion log is broken
OHTAKE Tomohiro started work on JENKINS-15328 Build name in promotion log is broken Change By: OHTAKE Tomohiro (27/Sep/12 6:05 AM) Status: Open In Progress 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-15328) Build name in promotion log is broken
OHTAKE Tomohiro created JENKINS-15328 Build name in promotion log is broken Issue Type: Bug Assignee: OHTAKE Tomohiro Attachments: Untitled.png Components: promoted-builds Created: 27/Sep/12 6:04 AM Description: Promoted builds 2.7 does not show build name correctly. See the attached image. Workarounds Downgrade to 2.6.2 Append "console" to URL Environment: Promoted builds 2.7 Project: Jenkins Priority: Minor Reporter: OHTAKE Tomohiro 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-15106) Configue Screen Fails to Load/Render(?) correctly on IE 8, Win 7
OHTAKE Tomohiro resolved JENKINS-15106 as Duplicate Configue Screen Fails to Load/Render(?) correctly on IE 8, Win 7 Change By: OHTAKE Tomohiro (21/Sep/12 12:01 AM) Status: Open Resolved Resolution: Duplicate 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-15027) Cron expression 'H H * * *' does not work as advertised
OHTAKE Tomohiro commented on JENKINS-15027 Cron _expression_ 'H H * * *' does not work as advertised JAVA_ARGS "-Dhudson.scheduler.BaseParser.hash=true" is required to enabled 'H' token. It seems that there is no description about that. 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-9175) Changing capitalization of promotion deletes promotion
OHTAKE Tomohiro resolved JENKINS-9175 as Fixed Changing capitalization of promotion deletes promotion Thank you for testing. We can close the issue. Change By: OHTAKE Tomohiro (17/Aug/12 1:51 PM) Status: Open Resolved Resolution: Fixed 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-7894) BuildWithParameters - parameter values disappear if user is not logged in
OHTAKE Tomohiro updated JENKINS-7894 BuildWithParameters - parameter values disappear if user is not logged in Change By: OHTAKE Tomohiro (17/Aug/12 7:52 AM) Assignee: huybrechts OHTAKE Tomohiro Component/s: core Component/s: parameterized-trigger 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-9175) Changing capitalization of promotion deletes promotion
OHTAKE Tomohiro commented on JENKINS-9175 Changing capitalization of promotion deletes promotion I could not reproduce non-ascii chars issue. Is it still reproducible? Windows 7 32bit Enterprise, Java SE 1.6.0_33-b03 Promoted-builds 2.6.2, Jenkins 1.448 (minimum core for 2.6.2) 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-9175) Changing capitalization of promotion deletes promotion
OHTAKE Tomohiro commented on JENKINS-9175 Changing capitalization of promotion deletes promotion The capitalization issue has been resolved in 2.1. https://github.com/jenkinsci/promoted-builds-plugin/commit/af6c70c8268d8762ca4058ac1f84513662202bfc 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-14521) Configuration Slicing should temporarily disable the Auto Refresh plugin
OHTAKE Tomohiro commented on JENKINS-14521 Configuration Slicing should temporarily disable the Auto Refresh plugin Yes, it can be controlled by the 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-14756) Fatal error on JSON parsing
OHTAKE Tomohiro resolved JENKINS-14756 as Duplicate Fatal error on JSON parsing Change By: OHTAKE Tomohiro (17/Aug/12 12:29 AM) Status: Open Resolved Resolution: Duplicate 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-13975) Promoted-builds not following jenkins access control policies
OHTAKE Tomohiro commented on JENKINS-13975 Promoted-builds not following jenkins access control policies How about this one? "#Job.Build,user1" allows user1 and any user with Job.Build permission to approve. It enables us to do what this issue says. We have to decide which charactor is the best to denote permission later. 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-10309) Some environment variables are not resolved in command line
OHTAKE Tomohiro
commented on JENKINS-10309
Some environment variables are not resolved in command line
If you use multiple Subversion repositories, you can use ${SVN_REVISION_1} and ${SVN_REVISION_2}.
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-13975) Promoted-builds not following jenkins access control policies
OHTAKE Tomohiro commented on JENKINS-13975 Promoted-builds not following jenkins access control policies Currently "Promote" permission is not defined. "Job.Build" or "Job.Configure" would be candidates if we do not define "Promote". In either case, I agree that using "Matrix-based security" or "Project-based Matrix Authorization Strategy" is a good idea. But we have to consider that a job might contain multiple promotion processes and that users want to set different approvers on them. Also we have to consider that no one has "Job.Build" permission, and that what users can do is only to approve. In that case, using matrix-based secuity will force users to change their configurations if they update the plugin. To avoid breaking changes, I prefer '!' notation. 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-13975) Promoted-builds not following jenkins access control policies
OHTAKE Tomohiro commented on JENKINS-13975 Promoted-builds not following jenkins access control policies Since there are a lot of AuthorizationStrategy'ies in Jenkins, it's not a good idea to distinguish FullControlOnceLoggedInAuthorizationStrategy. What do you think '!' notation. For instance, "!anonymous" allows non-anonymous users to approve, and "group1,!user1" allows members in group1 except user1 to approve. Implementation would be https://github.com/jenkinsci/promoted-builds-plugin/compare/jenkinsci:1653a48...ohtake:9c9ab04 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-14560) Job names are only static string fields instead of auto-complete fields
OHTAKE Tomohiro assigned JENKINS-14560 to OHTAKE Tomohiro Job names are only static string fields instead of auto-complete fields Change By: OHTAKE Tomohiro (16/Aug/12 8:33 AM) Assignee: OHTAKE Tomohiro 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-14451) Parsing junitResult.xml takes long time in some case
OHTAKE Tomohiro assigned JENKINS-14451 to OHTAKE Tomohiro Parsing junitResult.xml takes long time in some case Change By: OHTAKE Tomohiro (30/Jul/12 6:57 AM) Assignee: OHTAKE Tomohiro 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-14521) Configuration Slicing should temporarily disable the Auto Refresh plugin
OHTAKE Tomohiro commented on JENKINS-14521 Configuration Slicing should temporarily disable the Auto Refresh plugin I guess he would like configurationslicing to add norefresh="true" attribute to . If my guess is right, I would like too. 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-14499) Jenkins failed to load matrix project
OHTAKE Tomohiro resolved JENKINS-14499 as Duplicate Jenkins failed to load matrix project Change By: OHTAKE Tomohiro (20/Jul/12 5:47 AM) Status: Open Resolved Resolution: Duplicate 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-14451) Parsing junitResult.xml takes long time in some case
OHTAKE Tomohiro created JENKINS-14451 Parsing junitResult.xml takes long time in some case Issue Type: Bug Assignee: Unassigned Attachments: jenkins-ui_changes_dev.7z Components: junit Created: 17/Jul/12 2:29 AM Description: Steps to reproduce: Install Jenkins. No additional plugin are required. Extract jenkins-ui_changes_dev.7z into $JENKINS_HOME/jobs Fetching http://localhost:8080/job/jenkins-ui_changes_dev/$NNN/testReport/ takes less than 1 seccond, where $NNN is not 87 and 83 Fetching http://localhost:8080/job/jenkins-ui_changes_dev/$NNN/testReport/ took around 10 seconds, where $NNN is 87 and 83 Size of junitResult.xml is about 2 MB. I am not sure why it takes long in some cases. Environment: Jenkins 1.474 on Ubuntu 12.04 64bit and OpenJDK 1.6.0_24 Jenkins 1.474 on Windows 7 32bit and Oracle Java SE 1.6.0_33-b03 No additional plugins Project: Jenkins Priority: Minor Reporter: OHTAKE Tomohiro 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-11494) "Changes" for maven modules show unexpected numbers
OHTAKE Tomohiro resolved JENKINS-11494 as Duplicate "Changes" for maven modules show unexpected numbers Change By: OHTAKE Tomohiro (11/Jul/12 12:04 AM) Status: Open Resolved Resolution: Duplicate 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-14369) Protoype.selector undefined when using javascript proxy
OHTAKE Tomohiro resolved JENKINS-14369 as Fixed Protoype.selector undefined when using _javascript_ proxy Change By: OHTAKE Tomohiro (11/Jul/12 12:06 AM) Status: Open Resolved Resolution: Fixed 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-14309) HTML injection in username
OHTAKE Tomohiro assigned JENKINS-14309 to OHTAKE Tomohiro HTML injection in username Change By: OHTAKE Tomohiro (10/Jul/12 6:01 AM) Assignee: redsolo OHTAKE Tomohiro 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-14359) Cannot able to start
OHTAKE Tomohiro resolved JENKINS-14359 as Duplicate Cannot able to start Change By: OHTAKE Tomohiro (10/Jul/12 5:05 AM) Status: Open Resolved Resolution: Duplicate 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-14361) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
OHTAKE Tomohiro resolved JENKINS-14361 as Duplicate 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Change By: OHTAKE Tomohiro (10/Jul/12 5:04 AM) Status: Open Resolved Resolution: Duplicate 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-14369) Protoype.selector undefined when using javascript proxy
OHTAKE Tomohiro commented on JENKINS-14369 Protoype.selector undefined when using _javascript_ proxy The same issue had occured in managed-scripts-plugin. You have to include if you want to use outside . See also https://github.com/jenkinsci/managed-scripts-plugin/commit/858cba776127970e80f2aa73939dee33533afa69 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-14348) Multi-configuration projects don't load properly in 1.473
OHTAKE Tomohiro resolved JENKINS-14348 as Duplicate Multi-configuration projects don't load properly in 1.473 Change By: OHTAKE Tomohiro (07/Jul/12 9:27 AM) Status: Open Resolved Resolution: Duplicate 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-10395) Promote Builds + Trigger parameterized build = java.lang.NullPointerException
OHTAKE Tomohiro resolved JENKINS-10395 as Duplicate Promote Builds + Trigger parameterized build = java.lang.NullPointerException Change By: OHTAKE Tomohiro (05/Jul/12 11:59 AM) Status: Open Resolved Resolution: Duplicate 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-14286) Promoted Build Plugin stacktraces on manual approve
OHTAKE Tomohiro resolved JENKINS-14286 as Duplicate Promoted Build Plugin stacktraces on manual approve Change By: OHTAKE Tomohiro (05/Jul/12 11:52 AM) Status: Open Resolved Resolution: Duplicate 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-14145) Promoted Builds + Parameterized Trigger fails to pass Git revision
OHTAKE Tomohiro
resolved JENKINS-14145 as Fixed
Promoted Builds + Parameterized Trigger fails to pass Git revision
Pull requst 11 has been merged and released in 2.5.
You can pass GIT_COMMIT as following:
Predefined parameter
GIT_COMMIT=${PROMOTED_GIT_COMMIT}
Change By:
OHTAKE Tomohiro
(05/Jul/12 11:51 AM)
Status:
Open
Resolved
Resolution:
Fixed
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-3910) Provide a page that shows the list of promoted builds
OHTAKE Tomohiro commented on JENKINS-3910 Provide a page that shows the list of promoted builds JENKINS-10448 added a capability to list 10 latest promotions. Does it suit them? 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-13472) java.lang.IllegalArgumentException: Can't parse
OHTAKE Tomohiro resolved JENKINS-13472 as Fixed java.lang.IllegalArgumentException: Can't parse Fix for JENKINS-13631 will resolve the issue too. If not, please reopen. Change By: OHTAKE Tomohiro (05/Jul/12 7:57 AM) Status: Open Resolved Assignee: OHTAKE Tomohiro Resolution: Fixed 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-13631) Can't manually promote build with approval parameter
OHTAKE Tomohiro assigned JENKINS-13631 to OHTAKE Tomohiro Can't manually promote build with approval parameter Change By: OHTAKE Tomohiro (05/Jul/12 7:32 AM) Assignee: OHTAKE Tomohiro 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-6104) Provide a better RSS feed for hudson and plugin releases
OHTAKE Tomohiro commented on JENKINS-6104 Provide a better RSS feed for hudson and plugin releases "jenkins-ci.org" now provides an rss at http://jenkins-ci.org/releases.rss 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-14180) Command is not done in Execution shell in Windows 7 64 bit
OHTAKE Tomohiro resolved JENKINS-14180 as Not A Defect Command is not done in Execution shell in Windows 7 64 bit Change By: OHTAKE Tomohiro (05/Jul/12 5:45 AM) Status: Open Resolved Resolution: Not A Defect 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-14226) Restrict where this project can be run, does not work anymore
OHTAKE Tomohiro resolved JENKINS-14226 as Duplicate Restrict where this project can be run, does not work anymore Change By: OHTAKE Tomohiro (02/Jul/12 5:05 AM) Status: Open Resolved Resolution: Duplicate 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-14197) Plugin is preventing setting "Restrict where this project can be run"
OHTAKE Tomohiro commented on JENKINS-14197 Plugin is preventing setting "Restrict where this project can be run" Promoted Builds 2.6.1 has been released. It will be available in several hours. Sorry for inconvenience. 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-14223) accessing Jenkins through https produces browser warning about mixed https/http content
OHTAKE Tomohiro
commented on JENKINS-14223
accessing Jenkins through https produces browser warning about mixed https/http content
If you change Jenkins URL to https scheme, the argument of loadScript will change.
https://github.com/jenkinsci/jenkins/blob/d7bd7f59ee7924c8c8e811a7882a2e77d550bb45/core/src/main/resources/hudson/model/UsageStatistics/footer.jelly#L37
loadScript("${app.isRootUrlSecure()?'https':'http'}://usage.jenkins-ci.org/usage-stats.js?${it.statData}");
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-14095) RedHat RPM has different checksum than repository metadata
OHTAKE Tomohiro resolved JENKINS-14095 as Fixed RedHat RPM has different checksum than repository metadata Fixed in 1.470 http://jenkins-ci.org/changelog What's new in 1.470 (2012/06/13) Problem in syncing mirrors with native packages. Re-releasing the same bits as 1.469 as 1.470. Change By: OHTAKE Tomohiro (27/Jun/12 8:21 AM) Status: Open Resolved Resolution: Fixed 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-14082) Can't start Jenkins on Upgrade to 1.469 LDAP-related stack trace output.
OHTAKE Tomohiro resolved JENKINS-14082 as Duplicate Can't start Jenkins on Upgrade to 1.469 LDAP-related stack trace output. Change By: OHTAKE Tomohiro (27/Jun/12 8:16 AM) Status: Open Resolved Resolution: Duplicate 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-14197) Plugin is preventing setting "Restrict where this project can be run"
OHTAKE Tomohiro assigned JENKINS-14197 to OHTAKE Tomohiro Plugin is preventing setting "Restrict where this project can be run" Change By: OHTAKE Tomohiro (27/Jun/12 7:03 AM) Assignee: OHTAKE Tomohiro 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-13532) Changing analysis-core's tab makes breadcrumbs bar move down
OHTAKE Tomohiro commented on JENKINS-13532 Changing analysis-core's tab makes breadcrumbs bar move down I have tested YUI 2.9 with Jenkins core 1.409 and found no problems. There is no need to update core version. Since tree-view.js is bundled with core, using loads proper version of tree-view.js for Jenkins core. Though utilities.js is not bundled with core, it seems that utilities.js 2.9 is compatible with YUI 2.5.2. I will close https://github.com/jenkinsci/analysis-pom-plugin/pull/1, and will update https://github.com/jenkinsci/analysis-core-plugin/pull/7. 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-13532) Changing analysis-core's tab makes breadcrumbs bar move down
OHTAKE Tomohiro commented on JENKINS-13532 Changing analysis-core's tab makes breadcrumbs bar move down Jenkins core uses YUI 2.9 since 1.433. Updating core to 1.433 and updating YUI utilities.js in analysis-core works for me. As 1.447.x LTS has been released, we could update core to 1.433. I'll raise two pull requests. Could you review them? 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-13532) Changing analysis-core's tab makes breadcrumbs bar move down
OHTAKE Tomohiro reopened JENKINS-13532 Changing analysis-core's tab makes breadcrumbs bar move down I'm terribly sorry to push a topic branch to jenkinsci repository. Change By: OHTAKE Tomohiro (13/Jun/12 10:38 AM) Resolution: Fixed 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-14035) Responsive design
OHTAKE Tomohiro created JENKINS-14035:
-
Summary: Responsive design
Key: JENKINS-14035
URL: https://issues.jenkins-ci.org/browse/JENKINS-14035
Project: Jenkins
Issue Type: New Feature
Components: ui-changes
Reporter: OHTAKE Tomohiro
Assignee: OHTAKE Tomohiro
Make Web UI responsive for better experience with smartphones.
{noformat:title=Desktops (current design)}
+---+
|Top Bar|
+---+
|Breadcrumbs|
+-+-+
|side-| main-panel |
|panel| |
| | |
+-+-+
|Footer |
+---+
{noformat}
{noformat:title=Smartphones}
+---+
|Top bar|
+---+
|Breadcrumbs|
+---+
|side-panel |
|(togglable)|
+---+
|main-panel |
| |
| |
+---+
|Footer |
+---+
{noformat}
--
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
[JIRA] (JENKINS-13934) Make it possible to delete all except latest 'n' archived artifacts
[ https://issues.jenkins-ci.org/browse/JENKINS-13934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13934. --- Resolution: Not A Defect > Make it possible to delete all except latest 'n' archived artifacts > --- > > Key: JENKINS-13934 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13934 > Project: Jenkins > Issue Type: Improvement > Components: postbuild-task >Affects Versions: current > Environment: Sun/Solaris 9 ; Java 1.6.0_10; Jenkins ver. 1.466 >Reporter: Paul Croome >Assignee: OHTAKE Tomohiro >Priority: Minor > Attachments: Max_number_of_builds_to_keep_with_artifacts.png > > > In the job configuration page, under Post-build Actions > Archive the > Artifacts > Advanced > it's possible to select the checkbox "Discard all but the last > successful/stable artifact to save disk space". > It would be useful if I could choose "Discard all but the last 'n' > successful/stable artifacts to save disk space". > (By comparison: The option "Discard Old Builds" allows me to specify "Max # > of builds to keep". A similar feature for archived artifacts would be nice.) -- 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
[JIRA] (JENKINS-13977) Broken breadcrumb link drops me on contextMenu
[
https://issues.jenkins-ci.org/browse/JENKINS-13977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163392#comment-163392
]
OHTAKE Tomohiro commented on JENKINS-13977:
---
The issue has been resolved in Jenkins 1.456.
See
[5301b262327e685251e786ea0176a11b4bd994a4|https://github.com/jenkinsci/jenkins/commit/5301b262327e685251e786ea0176a11b4bd994a4].
> Broken breadcrumb link drops me on contextMenu
> --
>
> Key: JENKINS-13977
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13977
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Reporter: R. Tyler Croy
>Priority: Minor
>
> On a console page such as {{https://ci.lan/job/jobname/1472/console}} if I go
> to the "#1472" breadcrumb and click on "Previous Build" or "Next Build" then
> I land on {{https://ci.lan/job/jobname/1471/contextMenu}}
--
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
[JIRA] (JENKINS-13934) Make it possible to delete all except latest 'n' archived artifacts
[ https://issues.jenkins-ci.org/browse/JENKINS-13934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro updated JENKINS-13934: -- Attachment: Max_number_of_builds_to_keep_with_artifacts.png > Make it possible to delete all except latest 'n' archived artifacts > --- > > Key: JENKINS-13934 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13934 > Project: Jenkins > Issue Type: Improvement > Components: postbuild-task >Affects Versions: current > Environment: Sun/Solaris 9 ; Java 1.6.0_10; Jenkins ver. 1.466 >Reporter: Paul Croome >Assignee: OHTAKE Tomohiro >Priority: Minor > Attachments: Max_number_of_builds_to_keep_with_artifacts.png > > > In the job configuration page, under Post-build Actions > Archive the > Artifacts > Advanced > it's possible to select the checkbox "Discard all but the last > successful/stable artifact to save disk space". > It would be useful if I could choose "Discard all but the last 'n' > successful/stable artifacts to save disk space". > (By comparison: The option "Discard Old Builds" allows me to specify "Max # > of builds to keep". A similar feature for archived artifacts would be nice.) -- 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
[JIRA] (JENKINS-13934) Make it possible to delete all except latest 'n' archived artifacts
[ https://issues.jenkins-ci.org/browse/JENKINS-13934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163340#comment-163340 ] OHTAKE Tomohiro commented on JENKINS-13934: --- (1) and (2) can be specified independently. See screenshot attached. > Make it possible to delete all except latest 'n' archived artifacts > --- > > Key: JENKINS-13934 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13934 > Project: Jenkins > Issue Type: Improvement > Components: postbuild-task >Affects Versions: current > Environment: Sun/Solaris 9 ; Java 1.6.0_10; Jenkins ver. 1.466 >Reporter: Paul Croome >Assignee: OHTAKE Tomohiro >Priority: Minor > Attachments: Max_number_of_builds_to_keep_with_artifacts.png > > > In the job configuration page, under Post-build Actions > Archive the > Artifacts > Advanced > it's possible to select the checkbox "Discard all but the last > successful/stable artifact to save disk space". > It would be useful if I could choose "Discard all but the last 'n' > successful/stable artifacts to save disk space". > (By comparison: The option "Discard Old Builds" allows me to specify "Max # > of builds to keep". A similar feature for archived artifacts would be nice.) -- 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
[JIRA] (JENKINS-13878) [Max # of builds to keep] can't be configured as global variable
[ https://issues.jenkins-ci.org/browse/JENKINS-13878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163310#comment-163310 ] OHTAKE Tomohiro commented on JENKINS-13878: --- I believe you would like [Configuration Slicing Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Configuration+Slicing+Plugin]. > [Max # of builds to keep] can't be configured as global variable > > > Key: JENKINS-13878 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13878 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current > Environment: Java version: 1.6.0_27, vendor: Sun Microsystems Inc. > Java home: d:\fspldev\java\jdk1.6.0_27-i586 > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows xp", version: "5.1", arch: "x86", family: "windows" > Jenkins ver. 1.465 >Reporter: Neven Radovanovic > > It would be very helpful to configure [Max # of builds to keep] as a [Global > property] that can be applied to several jobs at once for easy maintenance. > -- 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
[JIRA] (JENKINS-13934) Make it possible to delete all except latest 'n' archived artifacts
[ https://issues.jenkins-ci.org/browse/JENKINS-13934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163309#comment-163309 ] OHTAKE Tomohiro commented on JENKINS-13934: --- You can find "Max # of builds to keep with artifacts" inside the advanced block of "Discard Old Builds". > Make it possible to delete all except latest 'n' archived artifacts > --- > > Key: JENKINS-13934 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13934 > Project: Jenkins > Issue Type: Improvement > Components: postbuild-task >Affects Versions: current > Environment: Sun/Solaris 9 ; Java 1.6.0_10; Jenkins ver. 1.466 >Reporter: Paul Croome >Priority: Minor > > In the job configuration page, under Post-build Actions > Archive the > Artifacts > Advanced > it's possible to select the checkbox "Discard all but the last > successful/stable artifact to save disk space". > It would be useful if I could choose "Discard all but the last 'n' > successful/stable artifacts to save disk space". > (By comparison: The option "Discard Old Builds" allows me to specify "Max # > of builds to keep". A similar feature for archived artifacts would be nice.) -- 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
[JIRA] (JENKINS-13532) Changing analysis-core's tab makes breadcrumbs bar move down
[
https://issues.jenkins-ci.org/browse/JENKINS-13532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
OHTAKE Tomohiro reopened JENKINS-13532:
---
Breadcrumbs bar sticks to the top, but dropdown menu on it won't work.
Jenkins 1.463, Task Scanner 4.29
{code:title=IE 9}
SCRIPT438: Object doesn't support property or method '_canPosition'
dom-min.js, line 7 character 4051
{code}
{code:title=Chrome 18}
Uncaught TypeError: Object # has no method '_canPosition'
e.Dom.getRegion.W dom-min.js:7
YAHOO.util.Dom.batchutilities.js:10
e.Dom.getRegion dom-min.js:7
showMenubreadcrumbs.js:79
handleHover breadcrumbs.js:100
jenkinsRules.#breadcrumbs LIbreadcrumbs.js:119
responder prototype.js:5662
{code}
> Changing analysis-core's tab makes breadcrumbs bar move down
>
>
> Key: JENKINS-13532
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13532
> Project: Jenkins
> Issue Type: Bug
> Components: analysis-core
> Environment: Jenkins 1.460, Task Scanner 4.27
>Reporter: OHTAKE Tomohiro
>Assignee: Ulli Hafner
>Priority: Minor
> Attachments: Untitled.png
>
>
> See an attached image. If you change tabs, breadcrumbs bar moves down.
> The cause is that changing tabs invokes Behaviour.apply(document) in
> main/resources/hudson/plugins/analysis/views/TabDetail/index.jelly(8).
--
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
[JIRA] (JENKINS-13722) vSphere plugin causing non-vSphere jobs to fail
[
https://issues.jenkins-ci.org/browse/JENKINS-13722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162670#comment-162670
]
OHTAKE Tomohiro commented on JENKINS-13722:
---
Reproduced and roled back to 0.5.
I got 2 different stacktraces.
One is same as the description and another is:
{code}
FATAL: null
java.lang.NullPointerException
at hudson.matrix.MatrixBuild$RunnerImpl.doRun(MatrixBuild.java:285)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480)
at hudson.model.Run.run(Run.java:1434)
at hudson.matrix.MatrixBuild.run(MatrixBuild.java:248)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
{code}
> vSphere plugin causing non-vSphere jobs to fail
> ---
>
> Key: JENKINS-13722
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13722
> Project: Jenkins
> Issue Type: Bug
> Components: vsphere-cloud
>Reporter: Christian Höltje
> Labels: slave
>
> I have vSphere plugin 0.9 and Jenkins 1.462 (and I tried 1.463) and it caused
> matrix jobs, that do not run on vSphere slaves, to die with this error:
> Started by timer
> FATAL: null
> java.lang.NullPointerException
> at
> org.jenkinsci.plugins.vSphereCloudRunListener.onStarted(vSphereCloudRunListener.java:32)
> at hudson.model.listeners.RunListener.fireStarted(RunListener.java:188)
> at hudson.model.Run.run(Run.java:1429)
> at hudson.matrix.MatrixBuild.run(MatrixBuild.java:248)
> at hudson.model.ResourceController.execute(ResourceController.java:88)
> at hudson.model.Executor.run(Executor.java:239)
> at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
> To add insult to injury, the builds then got locked. :-(
> None of the vSphere slaves seemed to be having problems (in fact, jobs were
> building on them just fine).
> My solution was to change all my vSphere slaves to normal slaves and then
> removing the plugin. Simply changing the slaves wasn't enough.
--
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
[JIRA] (JENKINS-13730) Can't enable Email-ext plugin in jenkins 1.463.
[ https://issues.jenkins-ci.org/browse/JENKINS-13730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13730. --- Resolution: Duplicate > Can't enable Email-ext plugin in jenkins 1.463. > --- > > Key: JENKINS-13730 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13730 > Project: Jenkins > Issue Type: Bug > Components: email-ext >Reporter: brick red > -- 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
[JIRA] (JENKINS-4998) Not possible to download artifacts larger than 2GB
[ https://issues.jenkins-ci.org/browse/JENKINS-4998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-4998. -- Resolution: Duplicate JENKINS-12854 will resolve the issue. If not, please reopen. > Not possible to download artifacts larger than 2GB > -- > > Key: JENKINS-4998 > URL: https://issues.jenkins-ci.org/browse/JENKINS-4998 > Project: Jenkins > Issue Type: Bug > Components: core > Environment: Tried on SUSE. Issue probably exists all other OSes too. >Reporter: glundh > > It is not possible to download artifacts larger than 2GB. After a timeout, > the user only receives a 0 byte file. This is course a huge issue for all > environments delivering larger build artifacts. > Issue discussed further here: > http://n4.nabble.com/limit-on-artifact-size-td390948.html -- 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
[JIRA] (JENKINS-13352) Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found" when trying to download artifacts >2GB
[ https://issues.jenkins-ci.org/browse/JENKINS-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13352. --- Resolution: Duplicate Fixed by JENKINS-12854. > Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory > could not be found" when trying to download artifacts >2GB > > > Key: JENKINS-13352 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13352 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Server Win2k8 - Jenkins ver. 1.455 and 1.457 (server has > zero executors) > Slave Win2k8 R2 - Slave ver. 2.12 (21 slaves) > WebBrowser - Firefox 11.0 and Chrome 18.0.1025.142 m > The build which is failing to archive artifacts is tied to a single slave. >Reporter: Richard Taylor > > *** This issues appears to be that artifacts larger than 2GB can not be > downloaded from Jenkins server *** > We have started getting bad links to artifacts from some runs of our package > build job. > * The build completes with out error. > * The artifacts are sucesfully copied back to the server. > * The artifacts can be copied and verified ok using SMB drive share. > * Any artifacts which are larger than 2GB will fail to download from the > jenkins server. > This web page has not been found > Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found. > As a work around we are looking to split up the artifacts into multiple files > but this is a less than ideal workflow. > Thanks > Richard. -- 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
[JIRA] (JENKINS-8706) Can't download artefacts greater than or equal to 2GB, can't use file params greater than or equal to 2GB
[ https://issues.jenkins-ci.org/browse/JENKINS-8706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162595#comment-162595 ] OHTAKE Tomohiro commented on JENKINS-8706: -- Fixed in winstone. See JENKINS-12854. > Can't download artefacts greater than or equal to 2GB, can't use file params > greater than or equal to 2GB > - > > Key: JENKINS-8706 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8706 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Windows XP >Reporter: Paul M >Priority: Blocker > > When an artefact is archived it can't be downloaded if its file size is >=2GB. > Steps for upload failure: > 1. Setup a project that takes a file paremeter > 2. Start a new build, it asks for a file to be uploaded > 3. Select a file thats >=2GB > 4. The page 404's > Steps for download failure: > 1. Setup a project that archives artefacts > 2. The actual build that causes this issue generates a huge zip file (about > 2.5GB), the zip file is created using 7z NOT by Jenkins download as zip > feature. > 3. Attempt to download this using the URL at the end of the build, it will > 404, yet the download as zip or the "view" link appears to work ok -- 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
[JIRA] (JENKINS-13562) Enable animation on optional-block and advanced-block
[ https://issues.jenkins-ci.org/browse/JENKINS-13562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro updated JENKINS-13562: -- Summary: Enable animation on optional-block and advanced-block (was: Enable annimation on optional-block and advanced-block) Description: To make clear which portion is optional/advanced block, it would be better to enable animation like hetero-list in publisher branch. (was: To make clear which portion is optional/advanced block, it would be better to enable annimation like hetero-list in publisher branch.) > Enable animation on optional-block and advanced-block > - > > Key: JENKINS-13562 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13562 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro >Priority: Minor > > To make clear which portion is optional/advanced block, it would be better to > enable animation like hetero-list in publisher branch. -- 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
[JIRA] (JENKINS-13562) Enable annimation on optional-block and advanced-block
[ https://issues.jenkins-ci.org/browse/JENKINS-13562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13562. --- Assignee: OHTAKE Tomohiro Resolution: Fixed > Enable annimation on optional-block and advanced-block > -- > > Key: JENKINS-13562 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13562 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro >Priority: Minor > > To make clear which portion is optional/advanced block, it would be better to > enable annimation like hetero-list in publisher branch. -- 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
[JIRA] (JENKINS-13582) Use link "rel" attributes for "Previous Build", "Next Build" to enable keyboard shortcuts in browsers that support it
[ https://issues.jenkins-ci.org/browse/JENKINS-13582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro updated JENKINS-13582: -- Assignee: OHTAKE Tomohiro Component/s: ui-changes > Use link "rel" attributes for "Previous Build", "Next Build" to enable > keyboard shortcuts in browsers that support it > - > > Key: JENKINS-13582 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13582 > Project: Jenkins > Issue Type: Improvement > Components: gui, ui-changes >Reporter: Karl Ostmo >Assignee: OHTAKE Tomohiro >Priority: Trivial > > This Chrome plugin automatically detects links that define the "previous" and > "next" relations, and enables arrow-key shortcuts to jump to those pages: > https://chrome.google.com/webstore/detail/pkjjfohgdkeomfgelibonoddaaioaopg > Link relations are standardized in HTML5. They are discussed here: > http://blog.whatwg.org/the-road-to-html-5-link-relations#rel-first -- 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
[JIRA] (JENKINS-13588) In console view, the "display raw text" Link and the "Progress bar" have (nearly) the same position
[ https://issues.jenkins-ci.org/browse/JENKINS-13588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13588. --- Resolution: Fixed Jenkins 1.462 will move "View as plain text" link to the sidepanel. See JENKINS-13389. > In console view, the "display raw text" Link and the "Progress bar" have > (nearly) the same position > --- > > Key: JENKINS-13588 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13588 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Jenkins 1.461; Firefox 11.0; Windows XP SP 3 >Reporter: Wolfgang Hauser >Priority: Minor > Fix For: current > > > On the console view, the Progress bar and the "Display as plain text" link > have the same position, the stop button is unreachable. > I use Firefox 11.0. -- 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
[JIRA] (JENKINS-13496) Add more mimetypes recognized by default
[ https://issues.jenkins-ci.org/browse/JENKINS-13496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162016#comment-162016 ] OHTAKE Tomohiro commented on JENKINS-13496: --- The issue regarding PDF on Chrome might be related to JENKINS-13125. > Add more mimetypes recognized by default > > > Key: JENKINS-13496 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13496 > Project: Jenkins > Issue Type: Improvement > Components: core >Reporter: Arnaud Héritier >Assignee: Arnaud Héritier > > Nowadays Jenkins declares only few mimetypes : > https://github.com/jenkinsci/jenkins/blob/master/war/src/main/webapp/WEB-INF/web.xml > The issue is that the real list of mimetypes recognized depends a lot of the > container used to host jenkins. There is a large list of choices managed by > Tomcat but it is really poor for winstone and thus when we are browsing a > workspace we may have various issues on files like PDF and co. -- 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
[JIRA] (JENKINS-13125) HTTP Content-Range Header one byte past file length
[
https://issues.jenkins-ci.org/browse/JENKINS-13125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162015#comment-162015
]
OHTAKE Tomohiro commented on JENKINS-13125:
---
Reproduced with Jenkins 1.461 running on Winstone.
The archived file's length is 1716 bytes.
It seems that "last-byte-pos" in Content-Range header is always bigger by 1
byte.
{code}
GET ** HTTP/1.1
Range: bytes=0-1
Host: **:
HTTP/1.1 206 Partial Content
Server: Winstone Servlet Engine v0.9.10
Last-Modified: Wed, 25 Apr 2012 01:54:31 GMT
Expires: Wed, 25 Apr 2012 01:54:31 GMT
Accept-Ranges: bytes
Content-Type: application/java-archive
Content-Range: 0-2/1716
Content-Length: 2
Connection: Keep-Alive
Date: Wed, 25 Apr 2012 08:49:28 GMT
X-Powered-By: Servlet/2.5 (Winstone/0.9.10)
GET ** HTTP/1.1
Range: bytes=1715-
Host: **:
HTTP/1.1 206 Partial Content
Server: Winstone Servlet Engine v0.9.10
Last-Modified: Wed, 25 Apr 2012 01:54:31 GMT
Expires: Wed, 25 Apr 2012 01:54:31 GMT
Accept-Ranges: bytes
Content-Type: application/java-archive
Content-Range: 1715-1716/1716
Content-Length: 1
Connection: Keep-Alive
Date: Wed, 25 Apr 2012 08:50:00 GMT
X-Powered-By: Servlet/2.5 (Winstone/0.9.10)
{code}
> HTTP Content-Range Header one byte past file length
> ---
>
> Key: JENKINS-13125
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13125
> Project: Jenkins
> Issue Type: Bug
> Components: www
>Affects Versions: current
>Reporter: Roland Schulz
>
> Downloading a PDF artifact using Chrome (17.0.963.79 m on Windows) the HTTP
> header for the last partial entity-body sent back by Jenkins contains:
> Content-Range: 2613923-2646691/2646691\r\n
> I believe this is wrong according to
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.16 . I believe
> the last range should be 2613923-2646690/2646691, because the numbers are
> 0-indexed.
> I'm not sure whether this is caused by this or is a separate issue, but
> Chrome keeps requesting the same last partial segment and Jenkins returns the
> same one in an endless loop. Thus Chrome is stuck loading the PDF at 100% in
> the endless loop. This only happens with the Chrome embedded PDF viewer. The
> file downloads correctly with "Save as".
--
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
[JIRA] (JENKINS-13562) Enable annimation on optional-block and advanced-block
OHTAKE Tomohiro created JENKINS-13562: - Summary: Enable annimation on optional-block and advanced-block Key: JENKINS-13562 URL: https://issues.jenkins-ci.org/browse/JENKINS-13562 Project: Jenkins Issue Type: Improvement Components: ui-changes Reporter: OHTAKE Tomohiro Priority: Minor To make clear which portion is optional/advanced block, it would be better to enable annimation like hetero-list in publisher branch. -- 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
[JIRA] (JENKINS-13532) Changing analysis-core's tab makes breadcrumbs bar move down
[
https://issues.jenkins-ci.org/browse/JENKINS-13532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161806#comment-161806
]
OHTAKE Tomohiro commented on JENKINS-13532:
---
Behaviour.applySubtree($("CONTENT_TO_BE_ADDED")) will not cause effects on
other elements.
> Changing analysis-core's tab makes breadcrumbs bar move down
>
>
> Key: JENKINS-13532
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13532
> Project: Jenkins
> Issue Type: Bug
> Components: analysis-core
> Environment: Jenkins 1.460, Task Scanner 4.27
>Reporter: OHTAKE Tomohiro
>Assignee: Ulli Hafner
>Priority: Minor
> Attachments: Untitled.png
>
>
> See an attached image. If you change tabs, breadcrumbs bar moves down.
> The cause is that changing tabs invokes Behaviour.apply(document) in
> main/resources/hudson/plugins/analysis/views/TabDetail/index.jelly(8).
--
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
[JIRA] (JENKINS-13532) Changing analysis-core's tab makes breadcrumbs bar move down
OHTAKE Tomohiro created JENKINS-13532: - Summary: Changing analysis-core's tab makes breadcrumbs bar move down Key: JENKINS-13532 URL: https://issues.jenkins-ci.org/browse/JENKINS-13532 Project: Jenkins Issue Type: Bug Components: analysis-core Environment: Jenkins 1.460, Task Scanner 4.27 Reporter: OHTAKE Tomohiro Assignee: Ulli Hafner Priority: Minor Attachments: Untitled.png See an attached image. If you change tabs, breadcrumbs bar moves down. The cause is that changing tabs invokes Behaviour.apply(document) in main/resources/hudson/plugins/analysis/views/TabDetail/index.jelly(8). -- 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
[JIRA] (JENKINS-13319) Change icon for repeatableDeleteButton and show tooltip on it
[ https://issues.jenkins-ci.org/browse/JENKINS-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13319. --- Resolution: Fixed > Change icon for repeatableDeleteButton and show tooltip on it > - > > Key: JENKINS-13319 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13319 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro >Priority: Minor > > Currently icon for repeatableDeleteButton is "edit-delete.png". [1] > Change it to "user-trash.png". [3] > Discussions: (written in Japanese) > [1] https://twitter.com/#!/ohtaket/status/186631033582657538 > [2] https://twitter.com/#!/kohsukekawa/status/186913466391597056 > [3] https://twitter.com/#!/ohtaket/status/186977316025540609 > [4] https://twitter.com/#!/kohsukekawa/status/186978692772278272 > [5] https://twitter.com/#!/ohtaket/status/186983488975679488 > [6] https://twitter.com/#!/kohsukekawa/status/186983938441494529 -- 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
[JIRA] (JENKINS-13505) Apply bootstrap style to "hetero-list-add" buttons
OHTAKE Tomohiro created JENKINS-13505:
-
Summary: Apply bootstrap style to "hetero-list-add" buttons
Key: JENKINS-13505
URL: https://issues.jenkins-ci.org/browse/JENKINS-13505
Project: Jenkins
Issue Type: Improvement
Components: ui-changes
Reporter: OHTAKE Tomohiro
Assignee: OHTAKE Tomohiro
Priority: Minor
Most of the buttons have been converted from YUI to Bootstrap.
But "hetero-list-add" buttons are still YUI.
We should apply Bootstrap style to "hetero-list-add" buttons.
An example of "hetero-list-add" is:
{code}
Add build step ▾
Execute shell
Invoke Ant
...
{code}
--
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
[JIRA] (JENKINS-13261) Style quick action dropdown menu
[ https://issues.jenkins-ci.org/browse/JENKINS-13261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161754#comment-161754 ] OHTAKE Tomohiro commented on JENKINS-13261: --- OK, dropdown menu of the breadcrums and "model-link". I will create another ticket for "hetero-list-add" buttons. > Style quick action dropdown menu > > > Key: JENKINS-13261 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13261 > Project: Jenkins > Issue Type: Bug > Components: ui-changes >Reporter: Tom Bevers >Assignee: Tom Bevers > > Style the quick action dropdown menu to match the current UI-changes. -- 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
[JIRA] (JENKINS-13282) ui-changes breadcrumbs should stick to top
[
https://issues.jenkins-ci.org/browse/JENKINS-13282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161753#comment-161753
]
OHTAKE Tomohiro commented on JENKINS-13282:
---
Our goal is to apply bootstrap? I think our goal is to make the UI better.
Bootstrap is designed to be applicable to *most* of web sites.
Jenkins is not an usual blog application, but an enterprise application.
We have to modify Bootstrap rules to match Jenkins' use cases.
If you think it is better to follow bootstrap styling of breadcrums,
please reset margin and padding of the breadcrum.
> ui-changes breadcrumbs should stick to top
> --
>
> Key: JENKINS-13282
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13282
> Project: Jenkins
> Issue Type: New Feature
> Components: ui-changes
>Reporter: OHTAKE Tomohiro
>Assignee: OHTAKE Tomohiro
>
> Comment by KK
> http://groups.google.com/group/jenkinsci-dev/browse_thread/thread/61d571f2be751121/659c24674d13542c?show_docid=659c24674d13542c
> {quote}
> - The menu of the top banner doesn't seem very useful to me. Right now it
> always shows the same 4 things from the action menu of the top page, which is
> probably not what you intended. But even if it changes per page, I think it'd
> end up just repeating what's on the left.
> - I liked our recent breadcrumb that sticks to the top of the page.
> {quote}
> I agree with him because:
> - Jenkins pages are highly hierarchical. Breadcrumbs may become longer
> especially when we use JUnit Test Result, Analysis Plugins and Nested View.
> - The first item of the breadcumbs provides a link to root. I don't think
> a.brand should be always visible.
> - I seldom click "USER_NAME | log out" links.
--
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
[JIRA] (JENKINS-13282) ui-changes breadcrumbs should stick to top
[
https://issues.jenkins-ci.org/browse/JENKINS-13282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JENKINS-13282 started by OHTAKE Tomohiro.
> ui-changes breadcrumbs should stick to top
> --
>
> Key: JENKINS-13282
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13282
> Project: Jenkins
> Issue Type: New Feature
> Components: ui-changes
>Reporter: OHTAKE Tomohiro
>Assignee: OHTAKE Tomohiro
>
> Comment by KK
> http://groups.google.com/group/jenkinsci-dev/browse_thread/thread/61d571f2be751121/659c24674d13542c?show_docid=659c24674d13542c
> {quote}
> - The menu of the top banner doesn't seem very useful to me. Right now it
> always shows the same 4 things from the action menu of the top page, which is
> probably not what you intended. But even if it changes per page, I think it'd
> end up just repeating what's on the left.
> - I liked our recent breadcrumb that sticks to the top of the page.
> {quote}
> I agree with him because:
> - Jenkins pages are highly hierarchical. Breadcrumbs may become longer
> especially when we use JUnit Test Result, Analysis Plugins and Nested View.
> - The first item of the breadcumbs provides a link to root. I don't think
> a.brand should be always visible.
> - I seldom click "USER_NAME | log out" links.
--
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
[JIRA] (JENKINS-13282) ui-changes breadcrumbs should stick to top
[
https://issues.jenkins-ci.org/browse/JENKINS-13282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
OHTAKE Tomohiro reassigned JENKINS-13282:
-
Assignee: OHTAKE Tomohiro
> ui-changes breadcrumbs should stick to top
> --
>
> Key: JENKINS-13282
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13282
> Project: Jenkins
> Issue Type: New Feature
> Components: ui-changes
>Reporter: OHTAKE Tomohiro
>Assignee: OHTAKE Tomohiro
>
> Comment by KK
> http://groups.google.com/group/jenkinsci-dev/browse_thread/thread/61d571f2be751121/659c24674d13542c?show_docid=659c24674d13542c
> {quote}
> - The menu of the top banner doesn't seem very useful to me. Right now it
> always shows the same 4 things from the action menu of the top page, which is
> probably not what you intended. But even if it changes per page, I think it'd
> end up just repeating what's on the left.
> - I liked our recent breadcrumb that sticks to the top of the page.
> {quote}
> I agree with him because:
> - Jenkins pages are highly hierarchical. Breadcrumbs may become longer
> especially when we use JUnit Test Result, Analysis Plugins and Nested View.
> - The first item of the breadcumbs provides a link to root. I don't think
> a.brand should be always visible.
> - I seldom click "USER_NAME | log out" links.
--
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
[JIRA] (JENKINS-13236) start identical job with different parameters in parallel execution
[ https://issues.jenkins-ci.org/browse/JENKINS-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13236. --- Resolution: Not A Defect There is a checkbox "Execute concurrent builds if necessary" in job configuration page. I enable the checkbox and run jobs in parallel with different branches. > start identical job with different parameters in parallel execution > --- > > Key: JENKINS-13236 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13236 > Project: Jenkins > Issue Type: New Feature > Components: core >Reporter: ttgtg ttgtg > Labels: build, parallel > > Have the option for a job to run several instances in parallel. > The use case: > We have a job that gets the branch name as an input and then it builds the > project and run the test. > If two or more developers want to build different branches the first one > blocks the others. The build and test take a lot of time but with many nodes > we can do several in parallel. > There may be a problem with this option if the jobs use the same workspace, > but on our setup the workspace is set by time and date with the branch name > to prevent this problem. > As this option has potential for destruction it should be under the advance > options. -- 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
[JIRA] (JENKINS-13236) start identical job with different parameters in parallel execution
[ https://issues.jenkins-ci.org/browse/JENKINS-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro updated JENKINS-13236: -- Component/s: (was: build-pipeline) > start identical job with different parameters in parallel execution > --- > > Key: JENKINS-13236 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13236 > Project: Jenkins > Issue Type: New Feature > Components: core >Reporter: ttgtg ttgtg > Labels: build, parallel > > Have the option for a job to run several instances in parallel. > The use case: > We have a job that gets the branch name as an input and then it builds the > project and run the test. > If two or more developers want to build different branches the first one > blocks the others. The build and test take a lot of time but with many nodes > we can do several in parallel. > There may be a problem with this option if the jobs use the same workspace, > but on our setup the workspace is set by time and date with the branch name > to prevent this problem. > As this option has potential for destruction it should be under the advance > options. -- 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
[JIRA] (JENKINS-13385) Jenkins stop working after upgrade
[ https://issues.jenkins-ci.org/browse/JENKINS-13385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13385. --- Resolution: Fixed Will be fixed in 1.462. See JENKINS-13448. > Jenkins stop working after upgrade > -- > > Key: JENKINS-13385 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13385 > Project: Jenkins > Issue Type: Bug > Components: git >Affects Versions: current >Reporter: wernight >Assignee: Nicolas De Loof >Priority: Blocker > > After upgrading Jenkins to 1.459 I got this exception which is removed as > soon as I disable Git plugin 1.1.16: > SEVERE: Failed to create Guice container from all the plugins > com.google.common.collect.ComputationException: > java.lang.TypeNotPresentException: Type > hudson.plugins.view.dashboard.DashboardPortlet not present > at > com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) > at com.google.inject.internal.FailableCache.get(FailableCache.java:49) > at > com.google.inject.internal.MembersInjectorStore.get(MembersInjectorStore.java:66) > at > com.google.inject.internal.ConstructorInjectorStore.createConstructor(ConstructorInjectorStore.java:73) > at > com.google.inject.internal.ConstructorInjectorStore.access$000(ConstructorInjectorStore.java:29) > at > com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:36) > at > com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:33) > at com.google.inject.internal.FailableCache$1.apply(FailableCache.java:38) > at > com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) > at > com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) > at > com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) > at > com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) > at > com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) > at com.google.inject.internal.FailableCache.get(FailableCache.java:49) > at > com.google.inject.internal.ConstructorInjectorStore.get(ConstructorInjectorStore.java:49) > at > com.google.inject.internal.ConstructorBindingImpl.initialize(ConstructorBindingImpl.java:127) > at > com.google.inject.internal.InjectorImpl.initializeBinding(InjectorImpl.java:506) > at > com.google.inject.internal.AbstractBindingProcessor$Processor$1.run(AbstractBindingProcessor.java:171) > at > com.google.inject.internal.ProcessedBindingData.initializeBindings(ProcessedBindingData.java:44) > at > com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:123) > at > com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107) > at com.google.inject.Guice.createInjector(Guice.java:94) > at com.google.inject.Guice.createInjector(Guice.java:71) > at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:280) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:532) > at java.lang.Class.newInstance0(Class.java:372) > at java.lang.Class.newInstance(Class.java:325) > at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) > at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:616) > at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:591) > at hudson.ExtensionFinder._find(ExtensionFinder.java:149) > at > hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) > at hudson.ExtensionList.load(ExtensionList.java:278) > at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) > at hudson.ExtensionList.iterator(ExtensionList.java:138) > at > hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:282) > at hudson.ExtensionList.load(ExtensionList.java:278) > at hudson.ExtensionList.ensureLoaded(ExtensionList.java:231) > at hudson.ExtensionList.iterator(ExtensionList.java:138) > at hudson.ExtensionList.get(ExtensionList.java:129) > at > hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) > at sun.reflect.NativeMethodAccesso
[JIRA] (JENKINS-13381) Jenkins stopped after updating plugins
[ https://issues.jenkins-ci.org/browse/JENKINS-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13381. --- Resolution: Fixed Will be fixed in 1.462. See JENKINS-13448. > Jenkins stopped after updating plugins > -- > > Key: JENKINS-13381 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13381 > Project: Jenkins > Issue Type: Bug > Components: analysis-collector, core, git >Affects Versions: current > Environment: Ubuntu Server 64 bits >Reporter: Rafael Tavares >Assignee: Nicolas De Loof > Labels: git, jenkins, plugins > > Hi, > I was updating my plugins then after update I can't access anymore my > jenkins. I get the following error: > > [!] Erro > org.jvnet.hudson.reactor.ReactorException: java.lang.Error: > java.lang.reflect.InvocationTargetException > at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) > at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) > at jenkins.model.Jenkins.executeReactor(Jenkins.java:849) > at jenkins.model.Jenkins.(Jenkins.java:761) > at hudson.model.Hudson.(Hudson.java:81) > at hudson.model.Hudson.(Hudson.java:77) > at hudson.WebAppMain$2.run(WebAppMain.java:217) > Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) > at > hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) > ... 8 more > Caused by: java.lang.NullPointerException > at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74) > ... 13 more -- 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
[JIRA] (JENKINS-12966) gitTool crashes Jenkins startup
[ https://issues.jenkins-ci.org/browse/JENKINS-12966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-12966. --- Resolution: Fixed Will be fixed in 1.462. See JENKINS-13448. > gitTool crashes Jenkins startup > --- > > Key: JENKINS-12966 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12966 > Project: Jenkins > Issue Type: Bug > Components: core, git > Environment: Jenkins 1.452 > Red Hat Enterprise Linux Server release 6.2 (Santiago) > Linux 2.6.32-220.4.1.el6.x86_64 #1 SMP Thu Jan 19 14:50:54 EST > 2012 x86_64 x86_64 x86_64 GNU/Linux >Reporter: Darren Weber >Assignee: Nicolas De Loof >Priority: Blocker > Labels: git, startup > > org.jvnet.hudson.reactor.ReactorException: java.lang.Error: > java.lang.reflect.InvocationTargetException > at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) > at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) > at jenkins.model.Jenkins.executeReactor(Jenkins.java:824) > at jenkins.model.Jenkins.(Jenkins.java:736) > at hudson.model.Hudson.(Hudson.java:81) > at hudson.model.Hudson.(Hudson.java:77) > at hudson.WebAppMain$2.run(WebAppMain.java:217) > Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) > at > hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at jenkins.model.Jenkins$5.runTask(Jenkins.java:813) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) > ... 8 more > Caused by: java.lang.NullPointerException > at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74) > ... 13 more -- 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
[JIRA] (JENKINS-13394) Jenkins won't start, PerforceToolinstallation NPE
[ https://issues.jenkins-ci.org/browse/JENKINS-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13394. --- Resolution: Fixed Will be fixed in 1.462. See JENKINS-13448. > Jenkins won't start, PerforceToolinstallation NPE > - > > Key: JENKINS-13394 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13394 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: Linux, Jenkins 1.457 and 1.458 >Reporter: NetAppBlueDevil >Assignee: Rob Petti > Attachments: jenkins.log > > > Did my regular updating of plugins. Went from 1.3.10 to 1.3.12 for perforce, > now Jenkins produces this stack trace in the browser. The only way I can get > it to start up completely is to disable the perforce plugin. Backing out to > 1.3.10 did not resolve the problem. I think there is something now not right > in some config somewhere that is not being corrected on plugin install. > Help ... > org.jvnet.hudson.reactor.ReactorException: java.lang.Error: > java.lang.reflect.InvocationTargetException > at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) > at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) > at jenkins.model.Jenkins.executeReactor(Jenkins.java:849) > at jenkins.model.Jenkins.(Jenkins.java:761) > at hudson.model.Hudson.(Hudson.java:81) > at hudson.model.Hudson.(Hudson.java:77) > at hudson.WebAppMain$2.run(WebAppMain.java:217) > Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) > at > hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) > at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) > ... 8 more > Caused by: java.lang.NullPointerException > at > hudson.plugins.perforce.PerforceToolInstallation.onLoaded(PerforceToolInstallation.java:66) > ... 13 more -- 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
[JIRA] (JENKINS-13352) Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found" when trying to download artifacts >2GB
[
https://issues.jenkins-ci.org/browse/JENKINS-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161474#comment-161474
]
OHTAKE Tomohiro commented on JENKINS-13352:
---
Reproduced in Ubuntu 11.04 64bit, Jenkins 1.459, Winstone.
In Winstone case, it seems that Winstone fails to parse Content-Length header.
{code}
java.lang.NumberFormatException: For input string: "2147484672"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:484)
at java.lang.Integer.parseInt(Integer.java:514)
at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:106)
at org.kohsuke.stapler.Stapler.serveStaticResource(Stapler.java:418)
at org.kohsuke.stapler.ResponseImpl.serveFile(ResponseImpl.java:150)
{code}
[Which servlet
container|https://wiki.jenkins-ci.org/display/JENKINS/Containers] do you use
for Jenkins?
> Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory
> could not be found" when trying to download artifacts >2GB
>
>
> Key: JENKINS-13352
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13352
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Server Win2k8 - Jenkins ver. 1.455 and 1.457 (server has
> zero executors)
> Slave Win2k8 R2 - Slave ver. 2.12 (21 slaves)
> WebBrowser - Firefox 11.0 and Chrome 18.0.1025.142 m
> The build which is failing to archive artifacts is tied to a single slave.
>Reporter: Richard Taylor
>
> *** This issues appears to be that artifacts larger than 2GB can not be
> downloaded from Jenkins server ***
> We have started getting bad links to artifacts from some runs of our package
> build job.
> * The build completes with out error.
> * The artifacts are sucesfully copied back to the server.
> * The artifacts can be copied and verified ok using SMB drive share.
> * Any artifacts which are larger than 2GB will fail to download from the
> jenkins server.
> This web page has not been found
> Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found.
> As a work around we are looking to split up the artifacts into multiple files
> but this is a less than ideal workflow.
> Thanks
> Richard.
--
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
[JIRA] (JENKINS-13356) Git fast remote polling always triggers build when missing locale
[
https://issues.jenkins-ci.org/browse/JENKINS-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
OHTAKE Tomohiro resolved JENKINS-13356.
---
Resolution: Fixed
> Git fast remote polling always triggers build when missing locale
> -
>
> Key: JENKINS-13356
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13356
> Project: Jenkins
> Issue Type: Bug
> Components: git
>Reporter: Marc Günther
>Assignee: Nicolas De Loof
>Priority: Minor
>
> Symptom:
> All jobs which had fast remote polling enabled triggered on every change in
> their repository, even if it was on an unrelated branch.
> Cause:
> Fast remote polling issues a {{git ls-remote -h }} command.
> The output of this command is supposed to be the sha hash of the last commit,
> but in our case it was:
> {{bash: warning: setlocale: LC_ALL: cannot}}
> Explanation:
> We have some slaves that use a german locale. This locale does not exist on
> the Git repository server nor on the Jenkins server. Installing it on the
> Jenkins server had no effect, as the above warning comes from the Git
> repository server.
> Quick fix:
> Install the missing locale on the both servers.
> Solution:
> Installing locales on some server should not be required. Either ignore
> stderr when issuing the {{git ls-remote}} command, or manipulate the passed
> in environment to something that does not cause side effects like this.
> Question:
> Why is the environment from the slave used on the server when doing the
> polling? {{LC_ALL}} is not set on our Jenkins server, so this definitely
> comes from a slave. I also notice that variables like HOME, USER, DISPLAY are
> set to values which make no sense on the server, and can lead to more
> problems like this.
--
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
[JIRA] (JENKINS-13409) 404 when clicking on "more" in Builds-List
[ https://issues.jenkins-ci.org/browse/JENKINS-13409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13409. --- Resolution: Duplicate > 404 when clicking on "more" in Builds-List > -- > > Key: JENKINS-13409 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13409 > Project: Jenkins > Issue Type: Bug > Components: gui >Affects Versions: current > Environment: Windows Server 2008 R2 - Apache Tomcat 7.0.16 >Reporter: Robert Lachner >Priority: Minor > > Hi, > since the last few Versions of Jenkins we are getting 404 Error Messages when > there are more build in the builds-list and you click on the more Link. > So noone is able to see the older builds in the list anymore and that is a > problem for some users. > Regards, > Robert -- 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
[JIRA] (JENKINS-13231) New Breadcrumb bar covers part of Console output page
[ https://issues.jenkins-ci.org/browse/JENKINS-13231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13231. --- Resolution: Fixed Fixed in 1.457 https://github.com/jenkinsci/jenkins/commit/49bbb9950faf9ed945484ac89222d564931a44f0 > New Breadcrumb bar covers part of Console output page > - > > Key: JENKINS-13231 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13231 > Project: Jenkins > Issue Type: Bug > Components: core >Reporter: Cees Bos > Attachments: breadcrumb_consoleoutput.png > > > See attached image > !breadcrumb_consoleoutput.png! > The top right corner of the consoleoutput page is covered by the breadcrumb. -- 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
[JIRA] (JENKINS-13243) Do not replace slashes in URLs with backslashes on Windows
[ https://issues.jenkins-ci.org/browse/JENKINS-13243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13243. --- Resolution: Fixed > Do not replace slashes in URLs with backslashes on Windows > -- > > Key: JENKINS-13243 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13243 > Project: Jenkins > Issue Type: Bug > Components: xshell >Affects Versions: current > Environment: Can be reproduced on any Windows platform >Reporter: Henrik Skupin > > When you call a script which expects an URL as parameter, the slashes will > also be converted to backslashes. It results in a broken parameter for the > build. So on Windows the plugin should not convert parameters which contain > URLs. -- 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
