[JIRA] [git-client] (JENKINS-22376) git-client explicitly setting core.symlinks in .git/config
Christian van der Leeden commented on JENKINS-22376 git-client explicitly setting core.symlinks in .git/config Same problem here. Just checked with a fresh jenkins installation, but symlink support with git is broken. The basic problem is that the git-client does a git init with JGit, which will create the .git/config file (bare) and add the symlinks = false This in turn lets the git command line client not support symlinks. So the whole point of using the git command line client instead of JGit to support symlinks is currently not working. 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-22376) git-client explicitly setting core.symlinks in .git/config
Christian van der Leeden edited a comment on JENKINS-22376 git-client explicitly setting core.symlinks in .git/config Same problem here. Just checked with a fresh jenkins installation, but symlink support with git is broken. The basic problem is that the git-client does a git init with JGit, which will create the directory and the .git/config file and add the symlinks = false This in turn lets the git command line client not support symlinks. So the whole point of using the git command line client instead of JGit to support symlinks is currently not working. 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-22376) git-client explicitly setting core.symlinks in .git/config
Christian van der Leeden edited a comment on JENKINS-22376 git-client explicitly setting core.symlinks in .git/config Same problem here. Just checked with a fresh jenkins installation, but symlink support with git is broken. The basic problem is that the git-client does a git init with JGit, which will create the directory and the .git/config file and add the symlinks = false This in turn lets the git command line client not support symlinks. So the whole point of using the git command line client instead of JGit to support symlinks is currently not working. As regression: It seems to be a problem of JGit 3.3. Downgrading to git-client 1.6.4 (JGit 3.2) is at least not creating this core property. To downgrade, download it here: http://mirrors.jenkins-ci.org/plugins/git-client/1.6.4/ and copy it over the git-client.jpi in the plugins directory and restart jenkins. For JGit 3.3: It is in FileRepository.java in create() method. There is a symlink check (if the OS supports symlinks) which seems to be broken. 3.2 doesn't include this check. 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-22319) Updating Git plugin causes existing builds to immediately fail
Ben Cooksley commented on JENKINS-22319 Updating Git plugin causes existing builds to immediately fail Our build process is a little unusual. It is made up of two components: 1) The setup script, which determines the branch to actually build (this information is published in a JSON file) and then creates a branch locally called "jenkins" pointed at this branch. This script runs in the Pre-SCM phase. This can be seen in the above output - "Branch jenkins set up to track remote branch master from origin". 2) The primary build phase. The Git plugin is invoked between component #1 and #2. Does this help? 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-22376) git-client explicitly setting core.symlinks in .git/config
Christian van der Leeden edited a comment on JENKINS-22376 git-client explicitly setting core.symlinks in .git/config Same problem here. Just checked with a fresh jenkins installation, but symlink support with git is broken. The basic problem is that the git-client does a git init with JGit, which will create the directory and the .git/config file and add the symlinks = false This in turn lets the git command line client not support symlinks. So the whole point of using the git command line client instead of JGit to support symlinks is currently not working. As regression: It seems to be a problem of JGit 3.3 For JGit 3.3: It is in FileRepository.java in create() method. There is a symlink check (if the OS supports symlinks) which seems to be broken. 3.2 doesn't include this check. My Workaround: Downgrading to git-client 1.6.4 (JGit 3.2) doesn't set this property. To downgrade, download it here: http://mirrors.jenkins-ci.org/plugins/git-client/1.6.4/ and copy it over the git-client.jpi in the plugins directory and restart jenkins. 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Sergey Saraev commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Hello Kohsuke. I can confirm problem for version 2.3-SNAPSHOT reported by Pedro. Maybe there are newer versions available to test? 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] [accelerated-build-now] (JENKINS-22349) Jenkins can't sync files from MKS server on master node
Ivan Yan commented on JENKINS-22349 Jenkins cant sync files from MKS server on master node Anybody who meet this issue or any solutions for it? Thanks. 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] [ws-cleanup] (JENKINS-22378) Workspace Cleanup Plugin fails on cygwin unix slave
Tomas Kislan created JENKINS-22378 Workspace Cleanup Plugin fails on cygwin unix slave Issue Type: Bug Assignee: vjuranek Components: ws-cleanup Created: 27/Mar/14 10:15 AM Description: When either pre or post ws cleanup is run, it fails with exception Deleting project workspace... Cannot delete workspace :remote file operation failed: /home/dtcdt/projects/jenkins/workspace/CommonLib/label/Build-Win2003R2 at hudson.remoting.Channel@6701c06:Build-Win2003R2 ERROR: Publisher hudson.plugins.ws_cleanup.WsCleanup aborted due to exception hudson.AbortException: Cannot delete workspace: remote file operation failed: /home/dtcdt/projects/jenkins/workspace/CommonLib/label/Build-Win2003R2 at hudson.remoting.Channel@6701c06:Build-Win2003R2 at hudson.plugins.ws_cleanup.WsCleanup.perform(WsCleanup.java:180) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:754) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1710) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Finished: FAILURE Environment: CentOS release 6.5 (Final) Jenkins 1.532 Workspace Cleanup 0.20 Cygpath plugin 1.5 Project: Jenkins Labels: slave Priority: Major Reporter: Tomas Kislan 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] [jenkins-multijob-plugin] (JENKINS-22379) job status overwritten for different instances of same sub job
Christian Hennig created JENKINS-22379 job status overwritten for different instances of same sub job Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Multijob_completed.png, Multijob_running.png Components: jenkins-multijob-plugin Created: 27/Mar/14 10:15 AM Description: Our multi-jobs sequentially execute multiple instances of the same jobs but with different parameters (e.g build configuration and platform). The problem is that during execution of the first occurence all other instances of the same partial job in the multijob are also marked as running. Additionally the result (success, error) and duration of the prior executions are overwritten by the last run. So for example if the Debug build had an error but the release build was successful, all jobs are marked as successful in the end. Due Date: 27/Mar/14 12:00 AM Environment: Windows Server 2k8 Project: Jenkins Labels: plugin Priority: Major Reporter: Christian Hennig 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] [jenkins-multijob-plugin] (JENKINS-22379) jenkins-multijob-plugin - job status overwritten for different instances of same sub job
Christian Hennig updated JENKINS-22379 jenkins-multijob-plugin - job status overwritten for different instances of same sub job Change By: Christian Hennig (27/Mar/14 10:17 AM) Summary: jenkins-multijob-plugin- jobstatusoverwrittenfordifferentinstancesofsamesubjob 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] [maven] (JENKINS-22380) Request parent child hierarchical sorting for Maven modules listing
Kiron Krishnankutty created JENKINS-22380 Request parent child hierarchical sorting for Maven modules listing Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: maven, maven2 Created: 27/Mar/14 10:45 AM Description: For multi-module maven projects, the module listing page currently sorts by the module name by default and by other available column names. It would be great to have a option to see the module list sorted in parent child hierarchy. Project: Jenkins Priority: Trivial Reporter: Kiron Krishnankutty 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-14447) Clone on Slave Fails
Mike Crowe commented on JENKINS-14447 Clone on Slave Fails The same problem suddenly started happening for us too with matrix child jobs on Jenkins 1.532.2 when I upgraded the Git client plugin to v1.6.5 and the Git plugin to v2.0.4. We were previously running Git plugin v1.4.0. Unfortunately I don't know what version of the Git client plugin we were using but it will have been contemporary with that. We didn't see this problem with those versions. The Jenkins master has been restarted several times (which seems to cause the slaves to be restarted too.) I haven't tried rebooting the slave but I see no reason why this would make any difference. 23:09:39 Started by upstream project "nightly-brightsign-master" build number 895 23:09:39 originally caused by: 23:09:39 Started by timer 23:09:41 Building remotely on bob in workspace /home/jenkins/workspace/nightly-brightsign-master/MACHINE/panther_puma/label/nightly 23:09:41 Checkout:nightly / /home/jenkins/workspace/nightly-brightsign-master/MACHINE/panther_puma/label/nightly - hudson.remoting.Channel@5e4c03d4:bob 23:09:41 Using strategy: Default 23:09:41 Last Built Revision: Revision 3ed2f7fb57edea2411d450caac3a53cf54323a59 (origin/master) 23:09:41 Using shallow clone 23:09:41 Wiping out workspace first. 23:09:41 Cloning the remote Git repository 23:09:41 Cloning repository gitolite@cam-git:bcm7425/bcm7425-oe 23:09:41 git --version 23:09:41 git version 1.7.10.4 23:09:41 ERROR: Error cloning remote repo 'origin' : Could not clone gitolite@cam-git:bcm7425/bcm7425-oe 23:09:41 hudson.plugins.git.GitException: Could not clone gitolite@cam-git:bcm7425/bcm7425-oe 23:09:41 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clone(CliGitAPIImpl.java:220) 23:09:41 at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1006) 23:09:41 at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:942) 23:09:41 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2439) 23:09:41 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 23:09:41 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 23:09:41 at hudson.remoting.Request$2.run(Request.java:328) 23:09:41 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 23:09:41 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 23:09:41 at java.util.concurrent.FutureTask.run(FutureTask.java:166) 23:09:41 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 23:09:41 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 23:09:41 at java.lang.Thread.run(Thread.java:724) 23:09:41 Caused by: hudson.plugins.git.GitException: Command "git clone --progress -o origin --depth 1 gitolite@cam-git:bcm7425/bcm7425-oe /home/jenkins/workspace/nightly-brightsign-master/MACHINE/panther_puma/label/nightly" returned status code 128: 23:09:41 stdout: 23:09:41 stderr: fatal: Could not get current working directory: No such file or directory 23:09:41 23:09:41 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:774) 23:09:41 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.clone(CliGitAPIImpl.java:218) 23:09:41 ... 12 more 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] [core] (JENKINS-22247) Provide an extension point to define user id case sensitivity contract
SCM/JIRA link daemon commented on JENKINS-22247 Provide an extension point to define user id case sensitivity contract Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/security/LDAPSecurityRealm.java http://jenkins-ci.org/commit/ldap-plugin/64fcf64850a2dd3ab668887212264f880f45042b Log: Add a hack to work-around JENKINS-22247 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] [ircbot] (JENKINS-22360) Missing space in IRC notifications
Marius Gedminas commented on JENKINS-22360 Missing space in IRC notifications This is very interesting! My IRC client is XChat-GNOME. The space is missing visually, it's missing in ~/.xchat2/xchatlogs/*.log file, and it's missing when I copy paste the text. I'm also connecting to the IRC server through an IRC proxy (znc). I wonder if one of those components might be eating the space in front of the IRC color code. I'll report back after I've narrowed this 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/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
chikigai commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Although I thought I had everything fixed, it looks like I'm still facing issues with commit notifications. I no longer get authentication errors with the actual checkout, but the commit notifications via hook scripts are randomly failing. The log shows "Failed to handle Subversion commit notification" followed by the same authentication error details as posted before. I've run out of ideas of where to look for possible causes. 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] [template-project] (JENKINS-22381) The plugin do not fail the build if a template is removed
William Bernardet created JENKINS-22381 The plugin do not fail the build if a template is removed Issue Type: Bug Assignee: huybrechts Components: template-project Created: 27/Mar/14 11:56 AM Description: In case the template job is removed the ProxyBuilder keeps going without notifying the end user about the issue. The builder should fail and report the issue to the user, rather than just hiding the issue. The problems come from the getProjectBuilders, if the returned project is null then it should throw an exception to signal that template doesn't exists anymore. And if Case the project type is not handled, it should throw an exception as well indicating the plugin do not support this type of project... Project: Jenkins Priority: Major Reporter: William Bernardet 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] [disk-usage] (JENKINS-21325) Strange Disk Usage message.
Anders Hammar commented on JENKINS-21325 Strange Disk Usage message. I believe this has been fixed in commit 54986c7e. 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] [teamconcert] (JENKINS-22013) With Team concert plugin saving the configuration always gives error.
Heather Fraser-Dube resolved JENKINS-22013 as Cannot Reproduce With Team concert plugin saving the configuration always gives error. Insufficient information to further investigate. Team Concert plugin is not within the stack trace. Change By: Heather Fraser-Dube (27/Mar/14 12:23 PM) Status: Open Resolved Resolution: CannotReproduce 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] [build-token-root] (JENKINS-22382) javax.servlet.ServletException: java.lang.NoSuchMethodError:
jenkins jenkins created JENKINS-22382 javax.servlet.ServletException: java.lang.NoSuchMethodError: Issue Type: Bug Assignee: Jesse Glick Components: build-token-root Created: 27/Mar/14 12:25 PM Description: javax.servlet.ServletException: java.lang.NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission(Lhudson/model/AbstractProject;Lhudson/model/BuildAuthorizationToken;Lorg/kohsuke/stapler/StaplerRequest;Lorg/kohsuke/stapler/StaplerResponse;)V at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) 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:74) 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
[JIRA] [active-directory] (JENKINS-16505) Adding a plugin mixing authentication via proxy and ldap permissions
Wilder Rodrigues commented on JENKINS-16505 Adding a plugin mixing authentication via proxy and ldap permissions The newest version of the plugin is available and now the groups can be loaded via LDAP: https://wiki.jenkins-ci.org/display/JENKINS/Reverse+Proxy+Auth+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/d/optout.
[JIRA] [active-directory] (JENKINS-16505) Adding a plugin mixing authentication via proxy and ldap permissions
Wilder Rodrigues resolved JENKINS-16505 as Fixed Adding a plugin mixing authentication via proxy and ldap permissions https://wiki.jenkins-ci.org/display/JENKINS/Reverse+Proxy+Auth+Plugin Change By: Wilder Rodrigues (27/Mar/14 12:35 PM) Status: Open Resolved Fix Version/s: current 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] [reverse-proxy-auth] (JENKINS-16299) Add groups to reverse proxy auth
Wilder Rodrigues resolved JENKINS-16299 as Fixed Add groups to reverse proxy auth https://wiki.jenkins-ci.org/display/JENKINS/Reverse+Proxy+Auth+Plugin Change By: Wilder Rodrigues (27/Mar/14 12:36 PM) Status: Open Resolved Assignee: WilderRodrigues Fix Version/s: current 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] [active-directory] (JENKINS-16505) Adding a plugin mixing authentication via proxy and ldap permissions
Wilder Rodrigues assigned JENKINS-16505 to Wilder Rodrigues Adding a plugin mixing authentication via proxy and ldap permissions Change By: Wilder Rodrigues (27/Mar/14 12:37 PM) Assignee: KohsukeKawaguchi WilderRodrigues 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] [reverse-proxy-auth] (JENKINS-16299) Add groups to reverse proxy auth
Wilder Rodrigues commented on JENKINS-16299 Add groups to reverse proxy auth It has been released: https://wiki.jenkins-ci.org/display/JENKINS/Reverse+Proxy+Auth+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/d/optout.
[JIRA] [sloccount] (JENKINS-22303) Should have option to not care about build failure status
Greg Moncreaff commented on JENKINS-22303 Should have option to not care about build failure status So. We aren't using a big honking make in a single build step. We have many individual build steps that run typically single tool focused shell scripts. Most of those are 'quality' scripts that are running code through various tools, and collecting data for warnings parsers. We are attempting to use health thresh holding with static analysis to get extra attention when the mountain of technical debt grows (a containment strategy). Since we are a big institution, nothing is resolved quickly, so sometimes jobs remain in that attention getting state for a long while (weeks to quarters), even if development of new capabilities is active in the code base that job is monitoring. Not my call. I'm just the CI tool smith, not the prioritization/funding/process manager. Typically, an actual compile or script fault occurs 1% of the time, but a build 'quality' health thresh hold breach is 99% of why we have builds marked failed. Thus, we would like SLOCCount to able to be configured to run regardless of build health. 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] [ircbot] (JENKINS-22360) Missing space in IRC notifications
Marius Gedminas commented on JENKINS-22360 Missing space in IRC notifications I've ruled out znc and xchat. We're logging our dev channel with Supybot (that connects directly to the IRC server), and the IRC logs are also showing "Project app build #2131:STILL FAILING in 18 min: https://..." with no space in front of STILL FAILING. 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] [update-center] (JENKINS-22162) no GUI update option for snapshot builds of Jenkins
steve steve commented on JENKINS-22162 no GUI update option for snapshot builds of Jenkins https://URL/pluginManager/checkUpdates that check never finishes. "searching for updates..." for 15mins. 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] [ircbot] (JENKINS-22360) Missing space in IRC notifications
Marius Gedminas commented on JENKINS-22360 Missing space in IRC notifications I think this line might be accidentally eating the space: https://github.com/jenkinsci/ircbot-plugin/blob/master/src/main/java/hudson/plugins/ircbot/v2/IRCColorizer.java#L72 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] [ircbot] (JENKINS-22360) Missing space in IRC notifications
Marius Gedminas commented on JENKINS-22360 Missing space in IRC notifications I've created a pull request for this, but I'm not sure how to test it: https://github.com/jenkinsci/ircbot-plugin/pull/13 I think I should be able to build an .hpi file and install it via https://jenkins.example.com/pluginManager/advanced? Only I'm not familiar with the Java build ecosystem. If you could give me some tips on what to do after cloning https://github.com/jenkinsci/ircbot-plugin, I'd appreciate it (I'm on Ubuntu 13.10). 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-22319) Updating Git plugin causes existing builds to immediately fail
Mark Waite commented on JENKINS-22319 Updating Git plugin causes existing builds to immediately fail I think I'm beginning to understand. I assume you're using the pre-scm-buildstep plugin to determine the branch to build, to create that branch, and to checkout that branch. Does your job fail at least once if you wipe the workspace? I assume the initial workspace creation doesn't happen until after the pre-scm-buildstep, but your pre-scm-buildstep requires that the workspace exists in order to perform the checkout. I've been able to replicate enough of your scenario to see that it fails for me as well. I created a pre-scm-buildstep shell script which performs the following commands: git checkout master || git checkout -b master -t origin/master git branch -D jenkins git checkout -b jenkins a449a3e5a101623cdd70d9eecdbe0ca0335a86b3 That allows the build to proceed, but it still fails if the Branches to build is "refs/heads/jenkins". With enough shell script work, I suspect something like that can be made to work even in the case where the workspace has been wiped prior to the start of the job. Unfortunately, I consider this a very special case that probably won't get a lot of attention in the plugins (git-plugin and git-client-plugin) unless you're willing to invest time to help with it. You might consider evaluating the current tip of the git-plugin branch on GitHub, since it includes an unreleased change that affects this area. If it works for your case, then this bug will be fixed with the next release of the git-plugin. If that does not fix this case, then you could consider that change as a base and attempt to submit a pull request which will cover your case as well. 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] [dry] (JENKINS-22356) No parser found for duplicated code
clausfod commented on JENKINS-22356 No parser found for duplicated code We are running the analysis via ANT and uses PMD 4.2.5 on a 1.4 JVM. The error started when I upgraded to 1.552 from 1.546 (I think it was from 1.546) - still appears in the latest Jenkins version. Kind regards Claus Nielsen 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] [subversion] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command
Satya Asati created JENKINS-22383 Failure found during the build process of RTRT using windows batch command Issue Type: Task Assignee: Unassigned Components: subversion Created: 27/Mar/14 1:52 PM Description: When we executed the RTRT unit test script using Windows batch command as mentioned below But at build phase we got failure which is due to Windows batch command and when we are perform post build action-Publish junit test report using XRD file generated by RTRT tool. We are getting error which is also mentioned in below error message. So please help us to resolve this issue. Started by user anonymous Building in workspace D:\ Cleaning local Directory ROOT/SOURCE Checking out http://sreublr213.eu.labinal.snecma/svn/carmeq/trunk/SOURCE at revision '2014-03-27T17:48:03.285 +0530' At revision 24 no change for http://sreublr213.eu.labinal.snecma/svn/carmeq/trunk/SOURCE since the previous build [] $ cmd /c call C:\Windows\TEMP\hudson642869198705461714.bat D:\studio.exe -r "D:\ROOT\TEST\2_Units_Module\SWK_RGL\SiLMSVS2010\Implementierung\ARAComponent\ARAComponent.rtp" -html "D:\ROOT\TEST\2_Units_Module\SWK_RGL\SiLMSVS2010\Reports\ARAComponent\Result" TestNode: ARAComponent.ARAComponent 113 Test Case Passed 0 Test Case Failed D:/ROOT/TEST/2_Units_Module/SWK_RGL/SiLMSVS2010/Reports/ARAComponent/Result\index.html The HTML report exportation succeeded. D:\exit 1 Build step 'Execute Windows batch command' marked build as failure Recording test results ERROR: Failed to archive test reports java.io.IOException: Failed to read D:\ROOT\TEST\2_Units_Module\SWK_RGL\SiLMSVS2010\Implementierung\ARAComponent\VS_SiL\ARAComponent.xrd Is this really a JUnit report file? Your configuration must be matching too many files at hudson.tasks.junit.TestResult.parse(TestResult.java:281) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:229) at hudson.tasks.junit.TestResult.parse(TestResult.java:164) at hudson.tasks.junit.TestResult.parse(TestResult.java:147) at hudson.tasks.junit.TestResult.init(TestResult.java:123) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:117) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:90) at hudson.FilePath.act(FilePath.java:914) at hudson.FilePath.act(FilePath.java:887) at hudson.tasks.junit.JUnitParser.parse(JUnitParser.java:87) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:121) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) 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: org.dom4j.DocumentException: Error on line 68 of document file:///D:/ROOT/TEST/2_Units_Module/SWK_RGL/SiLMSVS2010/Implementierung/ARAComponent/VS_SiL/ARAComponent.xrd : The prefix "XROD" for element "XROD:NODE" is not bound. Nested exception: The prefix "XROD" for element "XROD:NODE" is not bound. at org.dom4j.io.SAXReader.read(SAXReader.java:482) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:123) at hudson.tasks.junit.TestResult.parse(TestResult.java:273) ... 20 more Caused by: org.xml.sax.SAXParseException; systemId: file:///D:/ROOT/TEST/2_Units_Module/SWK_RGL/SiLMSVS2010/Implementierung/ARAComponent/VS_SiL/ARAComponent.xrd; lineNumber: 68; columnNumber: 85; The prefix "XROD" for element "XROD:NODE" is not bound. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at
[JIRA] [ircbot] (JENKINS-22360) Missing space in IRC notifications
Marius Gedminas commented on JENKINS-22360 Missing space in IRC notifications A coworker suggested that 'pom.xml' files are used by Maven, so `sudo apt-get install maven' followed by 'mvn' produced a target/ircbot.hpi, which I'm trying to test now. Unfortunately the plugin I built fails to connect to IRC with a non-specific Mar 27, 2014 1:57:40 PM WARNING hudson.plugins.ircbot.v2.IRCConnection connect Error connecting to irc: java.lang.NullPointerException BTW here's a screenshot of the bug: http://i.imgur.com/JKa4QQN.png. I'd hoped to mention it together with a screenshot for the fix, but see above 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] [build-token-root] (JENKINS-22382) javax.servlet.ServletException: java.lang.NoSuchMethodError:
jenkins jenkins commented on JENKINS-22382 javax.servlet.ServletException: java.lang.NoSuchMethodError: This plug-in was working fine until a recent Jenkins upgrade (either 1.555 or 1.556). It looks like your plug-in is using deprecated classes. 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] [url-change-trigger] (JENKINS-22258) url content not saved across cron inactive times
Trevor Baker resolved JENKINS-22258 as Not A Defect url content not saved across cron inactive times This seems to be working now. I'll reopen later if new info presents. Change By: Trevor Baker (27/Mar/14 2:11 PM) Status: Open Resolved Resolution: NotADefect 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] [parameterized-remote-trigger] (JENKINS-22384) Add EnvironmentVar feature to allow people access to Remote job
Tim Brown created JENKINS-22384 Add EnvironmentVar feature to allow people access to Remote job Issue Type: New Feature Assignee: Maurice W. Components: parameterized-remote-trigger Created: 27/Mar/14 2:13 PM Description: The Parameterized Build plugin give people access to the following environment variables: - LAST_TRIGGERED_JOB_NAME="Last project started" - TRIGGERED_BUILD_NUMBER_project name="Last build number triggered" - TRIGGERED_JOB_NAMES="Comma separated list of all triggered projects" - TRIGGERED_BUILD_NUMBERS_project name="Comma separated list of build numbers triggered" - TRIGGERED_BUILD_RESULT_project name="Last triggered build result of project" - TRIGGERED_BUILD_RESULT_project nameRUNbuild number="Result of triggered build for build number" - TRIGGERED_BUILD_RUN_COUNT_project name="Number of builds triggered for the project" It would be good if the Remote Parameterised Plugin could give people access to at least: - TRIGGERED_BUILD_NUMBER_project name="Last build number triggered" As we are trying to download artifacts using the lastSuccessul link, and this is failing when another job is kicked off on the remote job. I have a POC working if you'd like the code - needs Unit Tests though (has only been bench tested). Project: Jenkins Priority: Minor Reporter: Tim Brown 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] [subversion] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command
Satya Asati started work on JENKINS-22383 Failure found during the build process of RTRT using windows batch command Change By: Satya Asati (27/Mar/14 2:19 PM) Status: Open InProgress 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] [performance-plugin] (JENKINS-22385) Scalability issue storing individual results in memory
Nicolas De Loof created JENKINS-22385 Scalability issue storing individual results in memory Issue Type: Bug Assignee: Manuel Carrasco Components: performance-plugin Created: 27/Mar/14 2:19 PM Description: Used to collect large JMeter test reports, JMeterParser consumes all JVM heap. As UriReport stores individual httpSamples the report is fully loaded in memory, making performance plugin useless for non-trivial performance test suites. Suggestion : rely on https://wiki.jenkins-ci.org/display/JENKINS/Database+Plugin to store individual performance results, and let database compute aggregates. Project: Jenkins Priority: Major Reporter: Nicolas De Loof 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] [subversion] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command
Satya Asati stopped work on JENKINS-22383 Failure found during the build process of RTRT using windows batch command Change By: Satya Asati (27/Mar/14 2:19 PM) Status: InProgress Open 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] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
James Griffin commented on JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. these would have to be launched by a unique build project to handle the scheduler and polling. but having the substitution for definition/workspace will still allow us to cut down on the rest of the project chain. going forward, this will allow our new release process to be limited to "create new definition + create new scheduler". All other build steps remain the same. At roughly 5-10 new releases a month that is a major performance gain for manual work. 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] [ircbot] (JENKINS-22360) Missing space in IRC notifications
Marius Gedminas commented on JENKINS-22360 Missing space in IRC notifications The CI bot built an .hpi of my pull request, and I tried it instead of the .hpi I built on my laptop: https://jenkins.ci.cloudbees.com/job/plugins/job/ircbot-plugin/27/ It works! http://i.imgur.com/sJvY0dp.png 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] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Christoph Vogtländer commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I can confirm that commit notifications via hook scripts are randomly failing for svn:externals as reported by chikigai. Without svn:externals everything seems to work as expected. In my case svn:externals point to other repositories on the same server and and the access rights do not differ from the main repository. So using the same credentials for svn:externals should work. 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] [subversion] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command
Satya Asati assigned JENKINS-22383 to Unassigned Failure found during the build process of RTRT using windows batch command Change By: Satya Asati (27/Mar/14 2:22 PM) Assignee: jenkinsjenkins 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] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
SCM/JIRA link daemon commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Code changed in jenkins User: Rino Path: src/main/java/hudson/plugins/svn_tag/SvnTagPlugin.java http://jenkins-ci.org/commit/svn-tag-plugin/172d2cec18edc96b001c2f59f579388d370ff3ef Log: JENKINS-21797: commit client created per module location 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] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
SCM/JIRA link daemon commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Code changed in jenkins User: Marc Schöchlin Path: pom.xml src/main/java/hudson/plugins/svn_tag/SvnTagPlugin.java http://jenkins-ci.org/commit/svn-tag-plugin/27285688a13f32b8e47643f0ea3aa2a460686ce0 Log: Merge pull request #4 from rinokadijk/master FIXED: JENKINS-21797 Subversion-Tagging Plugin can't create tag because of missing credentials Compare: https://github.com/jenkinsci/svn-tag-plugin/compare/edee3b6892fa...27285688a13f 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] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
SCM/JIRA link daemon commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Code changed in jenkins User: Rino Path: pom.xml http://jenkins-ci.org/commit/svn-tag-plugin/4e17b3261486a29a284dfe543a0da488246f3f5e Log: JENKINS-21797: dependency 2.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 -- 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] [subversion] (JENKINS-22383) Failure found during the build process of RTRT using windows batch command
Satya Asati assigned JENKINS-22383 to jenkins jenkins Failure found during the build process of RTRT using windows batch command Change By: Satya Asati (27/Mar/14 2:22 PM) Assignee: jenkinsjenkins 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] [warnings] (JENKINS-22386) Warnings Plugin cannot show details for MSBuild warnings
Bob Tracy created JENKINS-22386 Warnings Plugin cannot show details for MSBuild warnings Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Attachments: console log.txt, stack trace.txt Components: warnings Created: 27/Mar/14 2:42 PM Description: Warnings Plugin set to "Scan console log" Parser set to MSBuild Warnings Plugin correctly identifies the warning and shows its summary in the "MSBuild Warnings" page. However, when I click on the link to show the file containing the specific warning, I get a stack trace from java.io.FileInputStream.open (attached). Additional info: I tried this with "Resolve relative paths" both checked and unchecked. It did not seem to make any difference. I also tried using MSBuild both with and without the "/m" command-line option for building multiple projects in parallel. This option changes the console log format by appending the parallel build number to all lines of text. The Warnings Plugin was not affected by either setting of /m. I think the problem is caused by MSBuild's output format which is: Filename(line,column) : warning number: description full path to project file I think the solution is to get the directory from project file and then append the relative filename of the file containing the warning. For example: PbuAfg.cs(90,9): warning CS0168: The variable 'warnme' is declared but never used C:\Program Files (x86)\Jenkins\workspace\gurb\Platforms\Afg\PbuAfg\PbuAfg.csproj The file containing the warning is: PbuAfg.cs The project file is: C:\Program Files (x86)\Jenkins\workspace\gurb\Platforms\Afg\PbuAfg\PbuAfg.csproj Get the directory part of the project: C:\Program Files (x86)\Jenkins\workspace\gurb\Platforms\Afg\PbuAfg\ Append the filename: C:\Program Files (x86)\Jenkins\workspace\gurb\Platforms\Afg\PbuAfg\PbuAfg.cs This yields the full path to the file. Environment: Windows 7 x64, US English MSBuild 12.0.30110.0 Single Jenkins server running on this machine. No slaves involved. Project: Jenkins Labels: warnings Priority: Major Reporter: Bob Tracy 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] [jclouds] (JENKINS-21864) Rename jclouds plugin to better reflect what it *does*
Andrew Phillips updated JENKINS-21864 Rename jclouds plugin to better reflect what it *does* Change By: Andrew Phillips (27/Mar/14 2:44 PM) Component/s: jclouds 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] [jclouds] (JENKINS-21864) Rename jclouds plugin to better reflect what it does
Andrew Phillips updated JENKINS-21864 Rename jclouds plugin to better reflect what it does Change By: Andrew Phillips (27/Mar/14 2:45 PM) Summary: Renamejcloudsplugintobetterreflectwhatit * does * 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] [tfs] (JENKINS-22387) Default workspace name is not configurable
Gareth Curtis created JENKINS-22387 Default workspace name is not configurable Issue Type: Improvement Assignee: redsolo Components: tfs Created: 27/Mar/14 3:18 PM Description: I want to configure the default workspace name for new jobs, so that I can include the computer name. Because we want to be able copy a job to a different computer and it should just run. But at the moment it tries to use a workspace which already exists. Project: Jenkins Priority: Major Reporter: Gareth Curtis 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] [core] (JENKINS-13357) Autoinstall JDK from download.oracle.com no longer works
Roberto Vieira commented on JENKINS-13357 Autoinstall JDK from download.oracle.com no longer works Same error here, on an existent working version 1.542 which was working ok, and on a recently installed 1.555any hint on why has this reappeared? is it an ORACLE issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21625) Subversion Polling does not work properly whenever using variables in the Repository URL
Milos Svasek updated JENKINS-21625 Subversion Polling does not work properly whenever using variables in the Repository URL Change By: Milos Svasek (27/Mar/14 3:23 PM) Priority: Major Blocker 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] [subversion] (JENKINS-21625) Subversion Polling does not work properly whenever using variables in the Repository URL
Milos Svasek commented on JENKINS-21625 Subversion Polling does not work properly whenever using variables in the Repository URL Please fix it, it's blocker for us! We really need to use variables in Subversion URL. Thanks in advance. 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] [credentials] (JENKINS-22078) SVN fails revision check for external subprojects
davida2009 commented on JENKINS-22078 SVN fails revision check for external subprojects We have a similar situation but got a solution from Stephen. When using an external its now necessary to specify an 'Additional Credential' on the project's configuration page. For our svn server, the realm is 'CollabNet Subversion Repository', but yours may be different. 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] [disk-usage] (JENKINS-19070) Disk usage doesn't work - 1.523+
Anders Hammar commented on JENKINS-19070 Disk usage doesnt work - 1.523+ I'm using disk-usage v0.23 on Jenkins LTS 1.532.2 and it works just fine. I think this ticket should be 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] [core] (JENKINS-22382) javax.servlet.ServletException: java.lang.NoSuchMethodError:
Jesse Glick updated JENKINS-22382 javax.servlet.ServletException: java.lang.NoSuchMethodError: Actually a binary incompatibility in core. Change By: Jesse Glick (27/Mar/14 3:53 PM) Labels: apiregression Component/s: core Component/s: build-token-root 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] [disk-usage] (JENKINS-22389) Job directory size shown in trend graph does not show the trend
Anders Hammar created JENKINS-22389 Job directory size shown in trend graph does not show the trend Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage Created: 27/Mar/14 3:55 PM Description: In the trend graph, the job directory size shown is not the trend. It is the current size for all plotted builds. Environment: plugin 0.24-SNAPSHOT (and 0.23 I think) Project: Jenkins Priority: Major Reporter: Anders Hammar 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] [core] (JENKINS-22382) javax.servlet.ServletException: java.lang.NoSuchMethodError:
Jesse Glick started work on JENKINS-22382 javax.servlet.ServletException: java.lang.NoSuchMethodError: Change By: Jesse Glick (27/Mar/14 3:54 PM) Status: Open InProgress 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] [disk-usage] (JENKINS-13572) Disk usage trend graph is not displayed on project page
Anders Hammar commented on JENKINS-13572 Disk usage trend graph is not displayed on project page I use disk-usage plugin v0.23 on Jenkins LTS 1.532.2 and it works just fine. I think this ticket can be 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] [core] (JENKINS-22382) NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission(…) from Build Token Root plugin
Jesse Glick
updated JENKINS-22382
NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission(…) from Build Token Root plugin
Change By:
Jesse Glick
(27/Mar/14 3:55 PM)
Summary:
javax.servlet.ServletException
NoSuchMethodError
:
java
hudson
.
lang
model
.
NoSuchMethodError:
BuildAuthorizationToken.checkPermission(…)fromBuildTokenRootplugin
Description:
{code:none}
javax.servlet.ServletException:java.lang.NoSuchMethodError:hudson.model.BuildAuthorizationToken.checkPermission(Lhudson/model/AbstractProject;Lhudson/model/BuildAuthorizationToken;Lorg/kohsuke/stapler/StaplerRequest;Lorg/kohsuke/stapler/StaplerResponse;)V atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:848) atorg.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) atorg.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) atorg.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) atorg.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
[JIRA] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Kohsuke Kawaguchi commented on JENKINS-20769 Failed to execute command Pipe.EOF I found it interesting that this problem appears to be only seen with ProxyWriter, while more or less equivalent and more prevelant ProxyOutputStream do not show up in the stack. 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
dimitkoto commented on JENKINS-20769 Failed to execute command Pipe.EOF +1 I am also experiencing the same issue with the ProxyWriter only mentioned in the stack, the same way as the ones in the earlier comments. 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] [ircbot] (JENKINS-22360) Missing space in IRC notifications
SCM/JIRA link daemon commented on JENKINS-22360 Missing space in IRC notifications Code changed in jenkins User: Marius Gedminas Path: src/main/java/hudson/plugins/ircbot/v2/IRCColorizer.java http://jenkins-ci.org/commit/ircbot-plugin/d9672576e9775e9c1962e55512edf2b98530f9d4 Log: Don't drop the space in front of the build status Should fix https://issues.jenkins-ci.org/browse/JENKINS-22360 (I haven't tested the fix yet.) 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] [ircbot] (JENKINS-22360) Missing space in IRC notifications
kutzi resolved JENKINS-22360 as Fixed Missing space in IRC notifications Change By: kutzi (27/Mar/14 4:45 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/d/optout.
[JIRA] [multiple-scms] (JENKINS-22390) Plug-in things there are changes when there are not
David Humeniuk created JENKINS-22390 Plug-in things there are changes when there are not Issue Type: Bug Affects Versions: current Assignee: Kevin Bell Components: multiple-scms Created: 27/Mar/14 4:49 PM Description: Get a message like below that says changes are found so the build runs at each polling interval. However, both repositories have the latest changes (SVN rev. 6 is the latest, SHA-1 commit hash is for the latest revision for the branch. I have other jobs that use only the Git branch with the basic plug-in that does not have any issues. Also, I have a job that is using origin/master branch with the multiple SCM plug-in and it doesn't have the same issue. Started on Mar 27, 2014 12:40:23 PM Polling SCM changes on centos Received SCM poll call on centos for THOSE-Release-Docs on Mar 27, 2014 12:47:48 PM https://xxx.yyy.com/svn/project-name/trunk is at revision 6 Using strategy: Default [poll] Last Built Revision: Revision d8dafe61061a336db85a27c148bf57e2fc54b006 (origin/release/0.7.0) using .gitcredentials to set credentials Done. Took 7.7 sec Changes found Project: Jenkins Priority: Major Reporter: David Humeniuk 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] [multiple-scms] (JENKINS-22390) Plug-in things there are changes when there are not
David Humeniuk updated JENKINS-22390 Plug-in things there are changes when there are not Change By: David Humeniuk (27/Mar/14 4:51 PM) Environment: Jenkins1.532.2,multipleSCMplug-in0.3,Gitclientplug-in1.6.6,Gitplug-in2.0.4 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] [core] (JENKINS-9688) Build runs on master without executor and get stuck
dimitkoto commented on JENKINS-9688 Build runs on master without executor and get stuck I still have the same issue, using Jenkins ver. 1.552 on 64bit Linux RHEL, and only Restart of Jenkins is able to resolve these zombie jobs staying there forever and preventing new builds from starting. 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] [core] (JENKINS-21989) ReverseProxySetupMonitor broken in Jenkins release 1.552
Townsend Duong commented on JENKINS-21989 ReverseProxySetupMonitor broken in Jenkins release 1.552 Thanks for the update and sample configuration. The NoDecode value is not available in the Apache version in SLES11SP3, but I confirmed that it solves the problem if I use a newer version of Apache. 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] [core] (JENKINS-22382) NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission(…) from Build Token Root plugin
SCM/JIRA link daemon resolved JENKINS-22382 as Fixed NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission(…) from Build Token Root plugin Change By: SCM/JIRA link daemon (27/Mar/14 5:05 PM) Status: InProgress 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] [core] (JENKINS-22382) NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission(…) from Build Token Root plugin
SCM/JIRA link daemon commented on JENKINS-22382 NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission(…) from Build Token Root plugin Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/BuildAuthorizationToken.java http://jenkins-ci.org/commit/jenkins/606d84c5b6a376dca545dbee32598ad17cfb2ec1 Log: FIXED JENKINS-22382 Need to restore deprecated overload of BuildAuthorizationToken.checkPermission for binary compatibility. 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Jesse Glick commented on JENKINS-20769 Failed to execute command Pipe.EOF @kohsuke as noted in my eb3a4c3 commit comment I have observed this also in ProxyOutputStream. 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
SCM/JIRA link daemon resolved JENKINS-20769 as Fixed Failed to execute command Pipe.EOF Change By: SCM/JIRA link daemon (27/Mar/14 5:32 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/d/optout.
[JIRA] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
SCM/JIRA link daemon commented on JENKINS-20769 Failed to execute command Pipe.EOF Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/ProxyWriter.java http://jenkins-ci.org/commit/remoting/57c3f1ab9e866ae237a568bd57382b6fe900ab98 Log: JENKINS-20769 Unexport is new, so for older versions fall back to EOF. Better to have a bogus error message than memory leak. 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
SCM/JIRA link daemon commented on JENKINS-20769 Failed to execute command Pipe.EOF Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/ProxyInputStream.java src/main/java/hudson/remoting/ProxyOutputStream.java http://jenkins-ci.org/commit/remoting/ec1a7c8e982d6cad5cbdd3d4b9ca3c06404f037c Log: Revert "JENKINS-20769 Trying to fix/suppress some related observed or actual NPEs." This reverts commit eb3a4c380e695580174ce381a8330e8e2b8a9b2e. Reverting this commit to unmask the problem. 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
SCM/JIRA link daemon commented on JENKINS-20769 Failed to execute command Pipe.EOF Code changed in jenkins User: Kohsuke Kawaguchi Path: src/test/java/hudson/remoting/ProxyWriterTest.java http://jenkins-ci.org/commit/remoting/e498f5aa99af88d5d2e621fbb1e85b2d6306e61f Log: JENKINS-20769 adding a test case that reproduces the problem. 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
SCM/JIRA link daemon commented on JENKINS-20769 Failed to execute command Pipe.EOF Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/ProxyWriter.java http://jenkins-ci.org/commit/remoting/d1e0fe07d8f72d37d9064404f94f7ae3bd6b223a Log: Revert "NPE observed in log while trying to reconnect a slave." This reverts commit 622af099d6b94569c873b8fcd2d1bc65860a8cc6. Simiarly, reverting to unmask the root cause of JENKINS-20769. These problems are indicative of a deeper problem, and shouldn't be just swept under the rug. 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
SCM/JIRA link daemon commented on JENKINS-20769 Failed to execute command Pipe.EOF Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/remoting/ProxyOutputStream.java src/main/java/hudson/remoting/ProxyWriter.java http://jenkins-ci.org/commit/remoting/96c670de534de269bcde729a932655842a3aea2a Log: FIXED JENKINS-20769 When ProxyWriter is finalized, it should attempt to release a remote reference count, but it shouldn't try to close the stream. For one, the other side that had exported the writer might be still using it (imagine exporting System.out), and secondly, the said object could have already been unexported, for example if the closure that brought ProxyWriter to this side has already returned, since RemoteWriter is auto-unexporting. Compare ProxyOutputStream impl vs ProxyWriter impl and the difference becomes clearer. 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Kohsuke Kawaguchi commented on JENKINS-20769 Failed to execute command Pipe.EOF I have fixed this problem with ProxyWriter. As noted in my comment of 96c670de534de269bcde729a932655842a3aea2a, the problem is that this EOF command was bogus. ProxyOutputStream handles this correctly, which explains why we see this on ProxyWriter but not on ProxyOutputStream (or at least less of, given Jesse Glick comment above that he has seen it with ProxyOutputStream. 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] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Kohsuke Kawaguchi commented on JENKINS-20769 Failed to execute command Pipe.EOF The stack trace Jesse cites in eb3a4c3 is the following, and this is a very different pattern. This is not from EOF but for Flush, and it wasn't induced by a finalizer. This one smells a genuine reference counting error, and should be tracked separately: java.lang.NullPointerException at hudson.remoting.ProxyOutputStream$Flush$1.run(ProxyOutputStream.java:305) at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:111) 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] [core] (JENKINS-22382) NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission(…) from Build Token Root plugin
dogfood commented on JENKINS-22382 NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission(…) from Build Token Root plugin Integrated in jenkins_main_trunk #3262 FIXED JENKINS-22382 Need to restore deprecated overload of BuildAuthorizationToken.checkPermission for binary compatibility. (Revision 606d84c5b6a376dca545dbee32598ad17cfb2ec1) Result = SUCCESS Jesse Glick : 606d84c5b6a376dca545dbee32598ad17cfb2ec1 Files : core/src/main/java/hudson/model/AbstractProject.java changelog.html core/src/main/java/hudson/model/BuildAuthorizationToken.java 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] [core] (JENKINS-22374) JNLP slaves blocked by default using Java 7u45/51
Kohsuke Kawaguchi commented on JENKINS-22374 JNLP slaves blocked by default using Java 7u45/51 According to JAR File manifests for security, looks like the correct value is "all-permissions". 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] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
bbonn commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart Hi Heather, Just wanted to give you some more information on this. A team member had done some looking and had this to add: "It is possible that the failure in RTC plugin is because the classpath becomes so long that part of it is cutting off. We have seen BuildClient (in the HPI), ScmPackage (in the toolkit), and now OperationCanceledException (in the toolkit) all having a NoClassDefFoundError. The RTC toolkit is pulling in over 100 jar files which by itself doesn’t seem like it would be too many but maybe it has something to do with the problem. We did a test where we created a share which had a shorter path than what the agent was using previously. This resolved the problem in almost all cases. But sometimes the error still appears." Does this make sense as a possible cause to what we are seeing? 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-22391) git-client-plugin 1.6.5 incorrectly converts symlinks to regular files, even with command line git
Mark Waite created JENKINS-22391 git-client-plugin 1.6.5 incorrectly converts symlinks to regular files, even with command line git Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 27/Mar/14 6:45 PM Description: From Christopher Orr on the Jenkins mailing list: If Jenkins clones a git repo on a machine running Java 1.6, the repo will be created with "core.symlinks = false" in the .git/config file. This causes Bad Things to happen if your git repo happens to rely on the use of symlinks. This happens because the Git Client plugin no longer uses "git clone" to clone a repo, but rather a combination of "git init" then "git fetch", and because the "git init" behaviour is implemented by jgit, even if you're using the default git CLI implementation. As of jgit 3.3.0, if you're running on a JVM which does not support symlinks (Java 1.6 or older), then the library will explicitly set "core.symlinks" to false when creating the .git directory. This means "git init" will create a repo which claims not to support symlinks, even if your file system does support symlinks. "git fetch" will then be executed (via the git binary, rather than jgit) and will respect the erroneous "core.symlinks" config value. Therefore you end up with files rather than the symlinks you expected in your cloned repo. (We actually saw this on an OS X 10.9 server with Jenkins running under Java 1.7 (with Java 1.6 also on the server as the non-default Java install), but jgit — for some reason — seems to think it's running on Java 1.6 and so believes symlinks aren't supported). Partly this seems to be a Git Client problem, but also (arguably) a jgit problem, as they explicitly configure new repos to reject symlinks, under the assumption that the repo will always be manipulated via jgit. But at least this merge from today would appear to fix the Git Client plugin by removing the use of jgit for "git init" for the CLI implementation: https://github.com/jenkinsci/git-client-plugin/commit/f5b27a9 Environment: All platforms if running JDK 6, may also affect JDK 7 platforms Project: Jenkins Priority: Major Reporter: Mark Waite 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-22391) git-client-plugin 1.6.5 incorrectly converts symlinks to regular files, even with command line git
Mark Waite started work on JENKINS-22391 git-client-plugin 1.6.5 incorrectly converts symlinks to regular files, even with command line git Change By: Mark Waite (27/Mar/14 7:24 PM) Status: Open InProgress 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-22391) git-client-plugin 1.6.5 incorrectly converts symlinks to regular files, even with command line git
Mark Waite resolved JENKINS-22391 as Fixed git-client-plugin 1.6.5 incorrectly converts symlinks to regular files, even with command line git Will be fixed with the release of git-client-plugin 1.7.0 Change By: Mark Waite (27/Mar/14 7:24 PM) Status: InProgress 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-22376) git-client explicitly setting core.symlinks in .git/config
Mark Waite assigned JENKINS-22376 to Mark Waite git-client explicitly setting core.symlinks in .git/config Change By: Mark Waite (27/Mar/14 7:31 PM) Assignee: NicolasDeLoof MarkWaite 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] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials FYI my earlier fix has become PR 70 and was merged today, so using a snapshot build should resolve commit hook and subversion tagging plugin related issues. 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] [jenkins-cloudformation] (JENKINS-22392) hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml
Steve Crow created JENKINS-22392 hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-cloudformation Created: 27/Mar/14 7:50 PM Description: version 1.556 packages on centos just started doing this hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at hudson.WebAppMain$3.run(WebAppMain.java:234) Caused by: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:910) at jenkins.model.Jenkins.init(Jenkins.java:809) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at jenkins.model.Jenkins$17.run(Jenkins.java:2561) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:899) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) Caused by: com.thoughtworks.xstream.converters.ConversionException: -1 : -1 Debugging information message : -1 cause-exception : java.lang.ArrayIndexOutOfBoundsException cause-message : -1 class : hudson.model.Hudson required-type : hudson.model.Hudson converter-type : hudson.util.RobustReflectionConverter path: /hudson/disabledAdministrativeMonitors line number : 3 version : not available --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at hudson.XmlFile.unmarshal(XmlFile.java:163) ... 9 more Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at com.thoughtworks.xstream.core.util.OrderRetainingMap.entrySet(OrderRetainingMap.java:77) at java.util.HashMap.putMapEntries(HashMap.java:511) at java.util.HashMap.putAll(HashMap.java:784) at com.thoughtworks.xstream.core.util.OrderRetainingMap.init(OrderRetainingMap.java:36) at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildMap(FieldDictionary.java:135) at com.thoughtworks.xstream.converters.reflection.FieldDictionary.fieldOrNull(FieldDictionary.java:113) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.getFieldOrNull(PureJavaReflectionProvider.java:186) at hudson.util.RobustReflectionConverter.fieldDefinedInClass(RobustReflectionConverter.java:344) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:283) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:228) at
[JIRA] [git-client] (JENKINS-22391) git-client-plugin 1.6.5 incorrectly converts symlinks to regular files, even with command line git
Mark Waite resolved JENKINS-22391 as Duplicate git-client-plugin 1.6.5 incorrectly converts symlinks to regular files, even with command line git Duplicate of JENKINS-22376 Change By: Mark Waite (27/Mar/14 8:01 PM) Status: Reopened 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 -- 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-22391) git-client-plugin 1.6.5 incorrectly converts symlinks to regular files, even with command line git
Mark Waite reopened JENKINS-22391 git-client-plugin 1.6.5 incorrectly converts symlinks to regular files, even with command line git Change By: Mark Waite (27/Mar/14 8:01 PM) 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 -- 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-22376) git-client explicitly setting core.symlinks in .git/config
Mark Waite commented on JENKINS-22376 git-client explicitly setting core.symlinks in .git/config Will be fixed with the release of git-client-plugin 1.7.0 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-22376) git-client explicitly setting core.symlinks in .git/config
Mark Waite edited a comment on JENKINS-22376 git-client explicitly setting core.symlinks in .git/config Will be fixed with the release of git-client-plugin 1.7.0. The "git init" for command line git will be done by command line git instead of using JGit. There may be slightly lower performance, but it seems reasonable to prefer the command line implementation as much as we reasonably can when the user chooses the command line implementation 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-22343) JGitAPIImpl fails to show first revision
Mark Waite updated JENKINS-22343 JGitAPIImpl fails to show first revision Change By: Mark Waite (27/Mar/14 8:14 PM) Component/s: git 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/d/optout.
[JIRA] [websphere-deployer] (JENKINS-22393) Problem deploying EAR to WAS 7
ingmartinlopez created JENKINS-22393 Problem deploying EAR to WAS 7 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: websphere-deployer Created: 27/Mar/14 8:17 PM Description: Hello. I'm having an issue: I can't deploy an EAR to a remote WebSphere, I'm getting this error: Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- facturador-ear-1.0.30.ear --- FATAL: Implementing class java.lang.IncompatibleClassChangeError: Implementing class at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1128) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:704) at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1299) at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1355) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1128) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:704) at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1299) at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1355) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) at com.ibm.ws.amm.commonarchive.AnnotationsProcessorImpl.merge(AnnotationsProcessorImpl.java:70) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl.processAnnotations(WARFileImpl.java:302) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl.getDeploymentDescriptor(WARFileImpl.java:248) at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.WARFileImpl.getDeploymentDescriptor(WARFileImpl.java:178) at com.ibm.websphere.management.application.AppDeploymentUtil.getModuleVersion(AppDeploymentUtil.java:1458) at com.ibm.websphere.management.application.AppDeploymentUtil.isEE5SchemaDD(AppDeploymentUtil.java:1419) at com.ibm.ws.management.application.client.AppInstallHelper.checkIfEE5ModulesContainXMIBindings(AppInstallHelper.java:1098) at com.ibm.ws.management.application.client.AppInstallHelper.checkIfEE5ModulesContainXMIBindings(AppInstallHelper.java:1063) at com.ibm.ws.management.application.client.AppInstallHelper.checkForEE5Restrictions(AppInstallHelper.java:324) at com.ibm.ws.management.application.client.AppInstallHelper.getAppDeploymentInfo(AppInstallHelper.java:377) at com.ibm.websphere.management.application.AppManagementFactory.readArchive(AppManagementFactory.java:100) at com.ibm.websphere.management.application.AppManagementFactory.readArchive(AppManagementFactory.java:70) at com.ibm.websphere.management.application.client.AppDeploymentController.readArchive(AppDeploymentController.java:208) at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:108) at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.getAppName(WebSphereDeploymentService.java:98) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.getAppName(WebSphereDeployerPlugin.java:268) at
[JIRA] [analysis-collector] (JENKINS-22394) Only one of multiple warnings parser is reported in Combined Analysis results
Greg Moncreaff created JENKINS-22394 Only one of multiple warnings parser is reported in Combined Analysis results Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: analysis-collector, analysis-core, warnings Created: 27/Mar/14 8:21 PM Description: When I started I had just one warnings parser script, and it was pulled into the combined results on the job splash page and dashboards. Since then I've added almost half a dozen other warnings parsers (manage jenkins . configure system . warnings) but none of the additional has ever been combined. Due Date: 30/Apr/14 12:00 AM Environment: win7 Project: Jenkins Priority: Major Reporter: Greg Moncreaff 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-22343) JGitAPIImpl fails to show first revision
Mark Waite commented on JENKINS-22343 JGitAPIImpl fails to show first revision Thanks very much for including a unit test to illustrate the problem / question. Since the API you're testing is inside the git plugin, I changed the component from git-client to git. If the ultimate problem is in git-client, we can reassign it, and can write a test which does not require the GitChangeSet object. 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] [periodic-reincarnation] (JENKINS-22132) Ratchet back PeriodicReincarnation logging or run periodicity
Yordan Boev commented on JENKINS-22132 Ratchet back PeriodicReincarnation logging or run periodicity It is possible now. There was a flaw in the AsyncPeriodicWork class from Jenkins. I have made some changes to it so that classes that extend it can override methods that set logging levels in order to reduce unwanted logging messages. The change is already in the newer versions of Jenkins. PeriodicReincarnation should just override getNormalLoggingLevel() and getNormalLoggingLevel() from https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AsyncPeriodicWork.java in order to stop the "every-minute-spam" in the console. Jenkins version should be at least 1.551 for this to work. 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] [core] (JENKINS-22374) JNLP slaves blocked by default using Java 7u45/51
Kohsuke Kawaguchi resolved JENKINS-22374 as Duplicate JNLP slaves blocked by default using Java 7u45/51 Will track this in JENKINS-20204, which has a lot more votes. Change By: Kohsuke Kawaguchi (27/Mar/14 8:59 PM) Status: Open Resolved Assignee: KohsukeKawaguchi 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 -- 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] [core] (JENKINS-20204) Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file
SCM/JIRA link daemon commented on JENKINS-20204 Latest release of Java 7 blocks the connection to slaves due to no permissions attribute in the JAR file Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml http://jenkins-ci.org/commit/remoting/07570271165133ef0b3a5b41134e4bcc59a6b410 Log: FIXED JENKINS-20204 Keep up with the new security requirements with Java7u51. Reference: http://docs.oracle.com/javase/8/docs/technotes/guides/jweb/security/manifest.html Reference: http://docs.oracle.com/javase/8/docs/technotes/guides/jweb/security/mixed_code.html 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.
