[JIRA] [extra-columns] (JENKINS-20910) Latest build parameters columns
SCM/JIRA link daemon resolved JENKINS-20910 as Fixed Latest build parameters columns Change By: SCM/JIRA link daemon (16/Dec/13 1:39 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 -- 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] [extra-columns] (JENKINS-20910) Latest build parameters columns
SCM/JIRA link daemon commented on JENKINS-20910 Latest build parameters columns Code changed in jenkins User: Fred G Path: src/main/java/jenkins/plugins/extracolumns/BuildParametersColumn.java src/main/resources/jenkins/plugins/extracolumns/BuildParametersColumn/column.jelly src/main/resources/jenkins/plugins/extracolumns/BuildParametersColumn/columnHeader.jelly src/main/resources/jenkins/plugins/extracolumns/BuildParametersColumn/columnHeader_de.properties src/main/resources/jenkins/plugins/extracolumns/BuildParametersColumn/config.jelly src/main/resources/jenkins/plugins/extracolumns/BuildParametersColumn/config_de.properties src/main/resources/jenkins/plugins/extracolumns/Messages.properties src/main/resources/jenkins/plugins/extracolumns/Messages_de.properties http://jenkins-ci.org/commit/extra-columns-plugin/2d0c0373755ae0aa85dbfbc74dab4b851dc32519 Log: [FIXED JENKINS-20910] Added "Build parameters" column Compare: https://github.com/jenkinsci/extra-columns-plugin/compare/86169ef8a62d...2d0c0373755a 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] [jacoco] (JENKINS-20854) Jacoco plugin not working in jenkins
Ognjen Bubalo commented on JENKINS-20854 Jacoco plugin not working in jenkins Hi Fabian, You don't get line coverage info, but you get other coverage measures? Thanks, Ogi 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-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Daniel Barth created JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 15/Dec/13 8:29 PM Description: Several problems appeared with git credentials temp file and local config after updating git-client-plugin to 1.5 using URL credentials and/or Jenkins credential store. URL variant: Baue auf Master in workspace D:\Jenkins\jobs\Test\workspace Fetching changes from the remote Git repository Fetching upstream changes from http://user@host/git.git FATAL: Failed to fetch from http://user@host/git.git hudson.plugins.git.GitException: Failed to fetch from http://user@host/git.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress http://user@host/git.git +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: error: unknown option `store=D:Tomcat-Tempgit2760255774910937069.credentials' usage: git credential-store [options] --file fetch and store credentials in error: unknown option `store=D:Tomcat-Tempgit2760255774910937069.credentials' usage: git credential-store [options] --file fetch and store credentials in fatal: Authentication failed for 'http://user@host/git.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1098) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:984) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:68) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:217) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:223) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:229) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:610) ... 10 more Jenkins credential store variant: Baue auf Master in workspace D:\Jenkins\jobs\Test\workspace Fetching changes from the remote Git repository Fetching upstream changes from http://user@host/git.git using .gitcredentials to set credentials FATAL: Failed to fetch from http://user@host/git.git hudson.plugins.git.GitException: Failed to fetch from http://user@host/git.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.plugins.git.GitException: Command "git config --local --remove-section credential.helper" returned status code 128: stdout: stderr: fatal: No such section! at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1098) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1075) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Daniel Beck commented on JENKINS-20630 Jenkins fails to start Linards L: The error you describe seems to be completely different from the original error. It looks like something's wrong with your (security realm?) configuration. What makes you think your error is the same as, or even just related to the original issue reported here? (Also, just in case you didn't know this: Every new comment and edit of a comment here gets send via email to everyone watching this issue, almost 70 people. 15 such notifications in two hours like the day before yesterday is a bit much. Maybe consider keeping the number of edits down.) 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] [core] (JENKINS-20630) Jenkins fails to start
Linards L commented on JENKINS-20630 Jenkins fails to start Repeatd update process. Now only updatable plugin was: Parameterized Trigger Plugin This plugin lets you trigger new builds when your build has completed, with various ways of specifying parameters for the new build. 2.21 2.20 Result is the same. First reboot is ok. Second - after updating plugin - total crash. 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] [core] (JENKINS-20630) Jenkins fails to start
Linards L edited a comment on JENKINS-20630 Jenkins fails to start Repeated update process. Now only updatable plugin was: Parameterized Trigger Plugin This plugin lets you trigger new builds when your build has completed, with various ways of specifying parameters for the new build. 2.22 2.21 Result is the same. First reboot is ok. Second - after updating plugin - total crash. Again back to v1.529. 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-client] (JENKINS-21015) NullPointerException in Jenkins Git Plugin
Imesh Gunaratne updated JENKINS-21015 NullPointerException in Jenkins Git Plugin Change By: Imesh Gunaratne (15/Dec/13 5:35 PM) Description: The following error was raised when a new Maven job was created using a Git repo without credentials :Jenkins version: 1.543javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at or
[JIRA] [git-client] (JENKINS-21015) NullPointerException in Jenkins Git Plugin
Imesh Gunaratne created JENKINS-21015 NullPointerException in Jenkins Git Plugin Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git-client Created: 15/Dec/13 5:34 PM Description: The following error was raised when a new Maven job was created using a Git repo: Jenkins version: 1.543 javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.
[JIRA] [analysis-core] (JENKINS-10596) Improve handling of source code files with duplicate relative path names
Ulli Hafner edited a comment on JENKINS-10596 Improve handling of source code files with duplicate relative path names Which parser are you using? Did you enable the scan workspace option? 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-20569) Polling with excluded regions don't prevent job triggered
Mark Waite commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered I disagree that polling using workspace should be the default. Polling using workspace is significantly slower than remote polling. When we have a new feature (like fast remote polling support) that significantly improves performance, it is better to make the faster performance the default so that new users and new jobs have the benefit of the faster performance without any special actions. It is unfortunate that fast remote polling does not work in all cases, but I think it is still better to use that as the default rather than polling using workspace by default, then allowing users the option to execute faster. 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] [scm-sync-configuration] (JENKINS-8871) Allow to use other SVN protocol than http/https
wolfgang häfelinger closed JENKINS-8871 as Fixed Allow to use other SVN protocol than http/https Problem got fixed in 1.514 by upgrading internal plugins. Change By: wolfgang häfelinger (15/Dec/13 4:22 PM) Status: Open Closed 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/groups/opt_out.
[JIRA] [www] (JENKINS-338) Cannot use svn protocol for Subversion
wolfgang häfelinger closed JENKINS-338 as Fixed Cannot use svn protocol for Subversion Fixed in version 1.514 by upgrading internal plugins. Change By: wolfgang häfelinger (15/Dec/13 4:23 PM) Status: Reopened Closed 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-8871) Allow to use other SVN protocol than http/https
wolfgang häfelinger assigned JENKINS-8871 to wolfgang häfelinger Allow to use other SVN protocol than http/https Change By: wolfgang häfelinger (15/Dec/13 4:21 PM) Assignee: Frédéric Camblor wolfgang häfelinger 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] [www] (JENKINS-338) Cannot use svn protocol for Subversion
wolfgang häfelinger reopened JENKINS-338 Cannot use svn protocol for Subversion Change By: wolfgang häfelinger (15/Dec/13 4:20 PM) Resolution: Incomplete Status: Closed Reopened Assignee: wolfgang häfelinger 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] [scm-sync-configuration] (JENKINS-8871) Allow to use other SVN protocol than http/https
wolfgang häfelinger commented on JENKINS-8871 Allow to use other SVN protocol than http/https The very standard Subversion svn:// protocol is supported since release 1.514 , release May 1st, 2013. 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] [www] (JENKINS-338) Cannot use svn protocol for Subversion
wolfgang häfelinger commented on JENKINS-338 Cannot use svn protocol for Subversion This was neither a user error or nor a fluke. Rather a problem easy to reproduce. Run a basic Subversion 'svnserve' server, create a basic project in Jenkins/Hudson and use URL like 'svn://localhost/path/to/my/svn/repo'. When doing so, Jenkin/Hudson reports that repository '/path/to/my/svn/repo' does not exist. The first Jenkins release which allows to use protocol svn:// is 1.514 released May 1st, 2013. The problem is as such not mentioned in the ChangeLog, it appears that upgrading to a less buggy svnkit version must have overcome a problem which should never have existed in the first place. 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] [findbugs] (JENKINS-20874) Slow FindBugsPlugin.start is wasted
Ulli Hafner commented on JENKINS-20874 Slow FindBugsPlugin.start is wasted Well, it's less than a second we will gain but it is quite easy to change that the messages will be read on demand (but it has the drawback of a synchronized piece of code during Jenkins runtime, this is not needed currently). I think over the Christmas vacation I'll have some spare time... Would it help if we make some performance tests with Jenkins? I'm planning a lecture/project about "testing enterprise applications" in the summer term in our department: maybe my master students can set up a performance test suite to detect existing bottle necks. These tests could also run in CI to prevent that the performance degenerates if a new feature is added... 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
Christian Galsterer commented on JENKINS-17742 Pick Up Committer from Upstream Job But wouldn't this also apply for the groovy script, that one need different ways to retrieve the upstream builds and does this also not apply then to the build in "Send to Requester" feature which calculates the root upstream build using the Jenkins core feature and is not aware of the "Build Flow 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 -- 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] [mailer] (JENKINS-20954) Cannot save email recipients
Dejan Stojadinovic edited a comment on JENKINS-20954 Cannot save email recipients +1 Jenkins Mailer Plugin 1.6 and Jenkins 1.532.1 LTS combination is affected also; will try to downgrade plugin (from 1.6 to 1.5). 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] [checkstyle] (JENKINS-20070) Restore sax parser system property after XML parsing
Ulli Hafner updated JENKINS-20070 Restore sax parser system property after XML parsing Change By: Ulli Hafner (15/Dec/13 3:01 PM) Summary: Checkstyle sets system property for Restore sax parser system property after XML parsing 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] [checkstyle] (JENKINS-20070) Checkstyle sets system property for sax parser
Ulli Hafner updated JENKINS-20070 Checkstyle sets system property for sax parser Change By: Ulli Hafner (15/Dec/13 3:00 PM) Component/s: findbugs Component/s: pmd 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] [core] (JENKINS-21014) Calculate Maven dependency graph also in verify lifecycle to deploy to local remote repository only when maven verify is succesfull and to allow proper working of "Build
Christian Galsterer created JENKINS-21014 Calculate Maven dependency graph also in verify lifecycle to deploy to local remote repository only when maven verify is succesfull and to allow proper working of "Build whenever a SNAPSHOT dependency is built" Issue Type: New Feature Assignee: Unassigned Attachments: verify.patch Components: core, maven Created: 15/Dec/13 2:40 PM Description: Currently the dependency graph for "Build whenever a SNAPSHOT dependency is built" maven jobs works only for Maven install and deploy lifecycle. If you want to split your job into two steps where the first step verifies that your maven project compiles and all test are successful and in the second step one then upload the new artefacts to your remote repository (if the first step works fine) this currently works of you run the first step with mvn clean install but not with clean verify. The problem with that when your build fails is (e.g. compilation problems, broken tests) that one has a set of artefacts in your local repository which is incomplete and in the worst case also incompatible as some parts already new and same parts are old and they are not compatible, e.g. by an API change. So solve this the artefacts shall only be deployed to the local and remote depository when the verify phase was successful. In order to make the "Build whenever a SNAPSHOT dependency is built" feature working, the dependency graph needs to be created not only for the install and verify lifecycle phase, but already for the verify phase. Please find attached a patch which contains these changes. If you think the patch is correct, please let me know and I create a proper hit pull request. Project: Jenkins Priority: Major Reporter: Christian Galsterer 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] [mailer] (JENKINS-20954) Cannot save email recipients
Dejan Stojadinovic commented on JENKINS-20954 Cannot save email recipients +1 Jenkins Mailer Plugin 1.6 and Jenkins 1.532.1 LTS combination is affected also; will try to downgrade plugin from (1.6 to 1.5). 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] [subversion] (JENKINS-20165) svn:externals files not polled for changes
Yoichi Nakayama assigned JENKINS-20165 to Ronny Schuetz svn:externals files not polled for changes Change By: Yoichi Nakayama (15/Dec/13 1:58 PM) Assignee: Yoichi Nakayama Ronny Schuetz 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] [subversion] (JENKINS-4613) Log message when svn URL is wrong could be better
Yoichi Nakayama closed JENKINS-4613 as Fixed Log message when svn URL is wrong could be better Change By: Yoichi Nakayama (15/Dec/13 1:59 PM) 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/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-21013) Matrix project support for "Parameters from properties file"
ikedam created JENKINS-21013 Matrix project support for "Parameters from properties file" Issue Type: Improvement Assignee: ikedam Components: parameterized-trigger Created: 15/Dec/13 1:57 PM Description: "Parameters from properties file" refers properties files generated in the workspace. With matrix projects (muti-configuration projects), workspaces of parent builds and those of child builds are differ. Especially if builds are distributed builds, workspaces are on different computers. The current implementation of "Parameters from properties file" refers only parent builds, it is difficult to apply matrix projects. This issue improved "Parameters from properties file" as following: Display an option "refer files in child builds" if it is a matrix project. It may be always applied for matrix projects, but implement like this for backward compatibility. "Combination filter" field to filter child builds. "Only for Exact Runs" field to apply only for child builds triggered by that parent build. And this is improvement of the pull request https://github.com/jenkinsci/parameterized-trigger-plugin/pull/57 . Project: Jenkins Priority: Major Reporter: ikedam 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] [analysis-core] (JENKINS-10596) Improve handling of source code files with duplicate relative path names
Ulli Hafner commented on JENKINS-10596 Improve handling of source code files with duplicate relative path names Which parser are you using? 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] [parameterized-trigger] (JENKINS-17176) The "Restrict matrix execution to subset" Groovy filter is not evaluate
ikedam closed JENKINS-17176 as Cannot Reproduce The "Restrict matrix execution to subset" Groovy filter is not evaluate As commented https://github.com/jenkinsci/parameterized-trigger-plugin/pull/37, it seems work in Jenkins 1.509.2. If the problem remains, reopen this issue and please let me know the steps to reproduce. Change By: ikedam (15/Dec/13 1:45 PM) Status: Open Closed Resolution: Cannot Reproduce 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] [copyartifact] (JENKINS-20398) Add a feature to configure projects to allow copy artifacts
ikedam commented on JENKINS-20398 Add a feature to configure projects to allow copy artifacts Sent a pull request https://github.com/jenkinsci/copyartifact-plugin/pull/27 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] [email-ext] (JENKINS-17742) Pick Up Committer from Upstream Job
Alex Earl commented on JENKINS-17742 Pick Up Committer from Upstream Job For instance, more people are using the Build Flow plugin, the Upstream stuff doesn't work the same way with a Build Flow job as it does with a normal job. You have to access it differently. 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] [custom-tools] (JENKINS-20909) Provide an advanced section to simplify configs
SCM/JIRA link daemon commented on JENKINS-20909 Provide an advanced section to simplify configs Code changed in jenkins User: Oleg Nenashev Path: src/main/resources/com/cloudbees/jenkins/plugins/customtools/CustomTool/config.jelly http://jenkins-ci.org/commit/customtools-plugin/d24cc48b04dbd1d90fd86ecf1bf3c002a55d253e Log: [FIXED JENKINS-20909] - Custom Tool Configuration section hides most of configuration fields Resolves https://issues.jenkins-ci.org/browse/JENKINS-20909 Signed-off-by: Oleg Nenashev 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] [custom-tools] (JENKINS-20909) Provide an advanced section to simplify configs
SCM/JIRA link daemon resolved JENKINS-20909 as Fixed Provide an advanced section to simplify configs Change By: SCM/JIRA link daemon (15/Dec/13 1:03 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 -- 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] [custom-tools] (JENKINS-20909) Provide an advanced section to simplify configs
SCM/JIRA link daemon commented on JENKINS-20909 Provide an advanced section to simplify configs Code changed in jenkins User: Oleg Nenashev Path: src/main/resources/com/cloudbees/jenkins/plugins/customtools/CustomTool/config.jelly http://jenkins-ci.org/commit/customtools-plugin/c7217ae0f2f6d25b422b2239c5f45fca6311f04f Log: Merge pull request #14 from synopsys-arc-oss/advanced-config-refactoring [FIXED JENKINS-20909] - Custom Tool Configuration section hides most of configuration fields Compare: https://github.com/jenkinsci/customtools-plugin/compare/832d125511ed...c7217ae0f2f6 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] [subversion] (JENKINS-4613) Log message when svn URL is wrong could be better
SCM/JIRA link daemon commented on JENKINS-4613 Log message when svn URL is wrong could be better Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/scm/subversion/UpdateUpdater.java http://jenkins-ci.org/commit/subversion-plugin/32601b2522ec4910921cd29e772e501c4fd89857 Log: Merge pull request #58 from yoichi/JENKINS-4613 [FIXED JENKINS-4613]compare hostname in case-insensitive manner Compare: https://github.com/jenkinsci/subversion-plugin/compare/05651e105c1e...32601b2522ec 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] [subversion] (JENKINS-4613) Log message when svn URL is wrong could be better
SCM/JIRA link daemon resolved JENKINS-4613 as Fixed Log message when svn URL is wrong could be better Change By: SCM/JIRA link daemon (15/Dec/13 12:11 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 -- 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] [subversion] (JENKINS-20165) svn:externals files not polled for changes
SCM/JIRA link daemon commented on JENKINS-20165 svn:externals files not polled for changes Code changed in jenkins User: Yoichi Nakayama Path: src/test/java/hudson/scm/SubversionSCMTest.java src/test/resources/hudson/scm/JENKINS-20165.zip http://jenkins-ci.org/commit/subversion-plugin/224154b844fc7b79e50937f6b907defa673e9889 Log: add test for JENKINS-20165 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] [subversion] (JENKINS-20165) svn:externals files not polled for changes
SCM/JIRA link daemon commented on JENKINS-20165 svn:externals files not polled for changes Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/scm/subversion/SubversionUpdateEventHandler.java src/test/java/hudson/scm/SubversionSCMTest.java src/test/resources/hudson/scm/JENKINS-20165.zip http://jenkins-ci.org/commit/subversion-plugin/05651e105c1e04595a2d2231c6a64a24bbbda0e9 Log: Merge pull request #56 from yoichi/JENKINS-20165 [FIXED JENKINS-20165] poll externals to file correctly with 1.6 working copy Compare: https://github.com/jenkinsci/subversion-plugin/compare/3c89f87f5930...05651e105c1e 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] [subversion] (JENKINS-20165) svn:externals files not polled for changes
SCM/JIRA link daemon resolved JENKINS-20165 as Fixed svn:externals files not polled for changes Change By: SCM/JIRA link daemon (15/Dec/13 12:09 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 -- 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-20569) Polling with excluded regions don't prevent job triggered
Liya Katz commented on JENKINS-20569 Polling with excluded regions don't prevent job triggered Polling using workspace should be the default behavior (backward compatibility!) and "remote Polling" should be an option 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.
