[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Vlad Aginsky updated JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session this is how it looks for me at chrome Version 26.0.1410.64 m Change By: Vlad Aginsky (20/May/13 6:40 AM) Attachment: jenkins-gui.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/groups/opt_out.
[JIRA] [subversion] (JENKINS-2556) Use svn switch where applicable
Matt Doran commented on JENKINS-2556 Use svn switch where applicable Any thoughts pushing a new build of the SVN plugin that includes this fix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Vlad Aginsky edited a comment on JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session this is how it looks for me at chrome Version 26.0.1410.64 m(attached) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session
Vlad Aginsky edited a comment on JENKINS-17684 Dashboard web pages dont render correctly in Chrome because of bad cache/session this is how it looks for me at chrome Version 26.0.1410.64 m(attached jenkins-gui.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/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
kutzi assigned JENKINS-17526 to Kohsuke Kawaguchi Broken CSS when reloading Jenkins after a time of inactivity Change By: kutzi (20/May/13 8:23 AM) Assignee: IRCbotRunby Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17347) xpath functions are broken in API (Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. is back)
benza assigned JENKINS-17347 to IRCbot Run by Kohsuke xpath functions are broken in API (Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. is back) Change By: benza (20/May/13 9:18 AM) Assignee: IRCbotRunbyKohsuke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-18009) Issue getting user ID and resolving permissions
Michele Sacchetti
created JENKINS-18009
Issue getting user ID and resolving permissions
Issue Type:
Bug
Affects Versions:
current
Assignee:
Thorsten Heit
Components:
crowd2
Created:
20/May/13 9:50 AM
Description:
we recently moved from LDAP to Crowd authentication via Crowd2 plugin.
we are experiencing an issue with a internal custom plugin which check users permissions before executing.
we retrieve build user via
Cause.UserIdCause mycause = (Cause.UserIdCause)build.getCause(Cause.UserIdCause.class);
variables.put("BUILD_USERID", mycause.getUserId());
variables.put("BUILD_USERNAME", mycause.getUserName());
Both variables seems to return the same value, which is
Name Surname (name.surname)
while we expect at least one of the two to be simply
name.surname
so that it could be passed to
UserDetails ud = Jenkins.getInstance().getSecurityRealm().loadUserByUsername(build_user);
With current values, the method is failing since the id is not correctly recognized and Crowd group membership not correctly resolved causing the error:
ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com
org.springframework.dao.DataRetrievalFailureException: The user 'Name Surname (name.surname)' does not have the permission to login and/or is not a member of the following user group(s) in your Crowd server: 'Jenkins-build-user'
at de.theit.jenkins.crowd.CrowdUserDetailsService.loadUserByUsername(CrowdUserDetailsService.java:94)
at de.theit.jenkins.crowd.CrowdSecurityRealm.loadUserByUsername(CrowdSecurityRealm.java:281)
at com.buongiorno.jenkinsci.plugins.delivery.ScriptBuildWrapper.setUp(ScriptBuildWrapper.java:95)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:600)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:584)
at hudson.model.Run.execute(Run.java:1575)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
Project:
Jenkins
Priority:
Major
Reporter:
Michele Sacchetti
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mantis] (JENKINS-16840) Unable to connect to Mantis
Christian Kotzbauer commented on JENKINS-16840 Unable to connect to Mantis I did some research and now I believe that it is only indirectly a problem of the plugin. The error already exists in the libraries such as Axis used by the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mantis] (JENKINS-16840) Unable to connect to Mantis
sogabe commented on JENKINS-16840 Unable to connect to Mantis What is the error you found? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-2556) Use svn switch where applicable
kutzi commented on JENKINS-2556 Use svn switch where applicable After I've burned 2 release numbers because of a stupid maven bug (http://www.shredzone.de/cilla/page/373/maven-release-plugin-and-git-fix.html), I've released it as 1.48 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-16512) v1.3.x perforce plugin doesn't work with the latest perforce 2012.2
Tom Hollis commented on JENKINS-16512 v1.3.x perforce plugin doesnt work with the latest perforce 2012.2 This issue has just occurred for me also, so it must be a perforce option as I get exactly the same string. For me p4 where works fine p4 where //... comes back with: Some commands just want to watch the database churn. Fix your workspace mapping. Are these command not equivalent? Is p4 where less intensive that p4 where //... and that is why our servers are complaining Tom This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18010) IOException: Insufficient system resources... when archiving artifacts
pancake created JENKINS-18010 IOException: Insufficient system resources... when archiving artifacts Issue Type: Bug Assignee: Unassigned Components: core Created: 20/May/13 11:54 AM Description: This started occurring sometimes after upgrading Jenkins ver. 1.480.1 - 1.509.1. ERROR: Failed to archive artifacts: ... hudson.util.IOException2: hudson.util.IOException2: Failed to extract ... at hudson.FilePath.readFromTar(FilePath.java:2014) at hudson.FilePath.copyRecursiveTo(FilePath.java:1926) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:137) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724) at hudson.model.Run.execute(Run.java:1600) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: java.io.IOException: unexpected EOF with 3584 bytes unread at hudson.org.apache.tools.tar.TarInputStream.read(TarInputStream.java:349) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1025) at org.apache.commons.io.IOUtils.copy(IOUtils.java:999) at hudson.util.IOUtils.copy(IOUtils.java:37) at hudson.FilePath.readFromTar(FilePath.java:2004) ... 11 more at hudson.FilePath.copyRecursiveTo(FilePath.java:1933) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:137) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:802) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:774) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:724) at hudson.model.Run.execute(Run.java:1600) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Insufficient system resources exist to complete the requested service at hudson.remoting.Channel$4.adapt(Channel.java:705) at hudson.remoting.Channel$4.adapt(Channel.java:700) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.FilePath.copyRecursiveTo(FilePath.java:1929) ... 10 more Caused by: java.io.IOException: Insufficient system resources exist to complete the requested service at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(Unknown Source) at hudson.util.io.TarArchiver.visit(TarArchiver.java:114) at hudson.util.DirScanner$Glob.scan(DirScanner.java:133) at hudson.FilePath.writeToTar(FilePath.java:1978) at hudson.FilePath.access$1000(FilePath.java:168) at hudson.FilePath$36.invoke(FilePath.java:1919) at hudson.FilePath$36.invoke(FilePath.java:1915) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Environment: Jenkins ver. 1.509.1, Copy Artifact Plugin 1.25. Server: CentOS 6.3 x64, jre 1.7.0_04.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson created JENKINS-18011 Deadlock issue remote slaves Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 20/May/13 12:03 PM Description: Jenkins slaves running on Windows have a tendency to deadlock when programs are sending a lot of data simultaneously. Reading the threaddump from VisualVM we can see that proc.java tries to write to deadlock stream resulting in hanging builds """ String msg = "Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information"; Throwable e = new Exception().fillInStackTrace(); LOGGER.log(Level.WARNING,msg,e); """ "pool-1-thread-833" - Thread t@1926010 java.lang.Thread.State: BLOCKED at java.util.logging.StreamHandler.publish(Unknown Source) waiting to lock 1502546 (a java.util.logging.ConsoleHandler) owned by "pool-1-thread-927" t@1926604 at java.util.logging.ConsoleHandler.publish(Unknown Source) at java.util.logging.Logger.log(Unknown Source) at java.util.logging.Logger.doLog(Unknown Source) at java.util.logging.Logger.log(Unknown Source) at hudson.Proc$LocalProc.join(Proc.java:330) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:993) at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Environment: Linux Master runing programs on Windows slaves Verified in Jenkins 1.480.1 and Jenkins 1.509.1 Project: Jenkins Labels: slave Priority: Major Reporter: Marcus Jacobsson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson commented on JENKINS-18011 Deadlock issue remote slaves Related to https://github.com/jenkinsci/jenkins/pull/665 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-7057) Invalid Illegal email address exception
Alex Earl closed JENKINS-7057 as Fixed Invalid Illegal email address exception Change By: Alex Earl (20/May/13 12:15 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-3605) provide access to arbitrary environment variables
Alex Earl closed JENKINS-3605 as Fixed provide access to arbitrary environment variables Change By: Alex Earl (20/May/13 12:15 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-5816) Password is stored in plain text
Alex Earl closed JENKINS-5816 as Fixed Password is stored in plain text Change By: Alex Earl (20/May/13 12:15 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-7402) Build log regex matches encoded console notes
Alex Earl closed JENKINS-7402 as Fixed Build log regex matches encoded console notes Change By: Alex Earl (20/May/13 12:15 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-5813) $BUILD_STATUS in email subject is always 'Building'
Alex Earl closed JENKINS-5813 as Cannot Reproduce $BUILD_STATUS in email subject is always Building Change By: Alex Earl (20/May/13 12:15 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-6527) Unexpanded content token reference in Extended email notification
Alex Earl closed JENKINS-6527 as Not A Defect Unexpanded content token reference in Extended email notification Change By: Alex Earl (20/May/13 12:15 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-5970) Provide an option to include or exclude console output annotations
Alex Earl closed JENKINS-5970 as Duplicate Provide an option to include or exclude console output annotations Change By: Alex Earl (20/May/13 12:16 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-6335) Extended E-mail Notification Plugin does not persist changes to the Hudson URL
Alex Earl closed JENKINS-6335 as Duplicate Extended E-mail Notification Plugin does not persist changes to the Hudson URL Change By: Alex Earl (20/May/13 12:16 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-7514) Custom Jelly Content for email-ext plugin - for sending nice custom messages
Alex Earl closed JENKINS-7514 as Fixed Custom Jelly Content for email-ext plugin - for sending nice custom messages Change By: Alex Earl (20/May/13 12:16 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-6193) overwrite-Hudson URL value is always used
Alex Earl closed JENKINS-6193 as Fixed overwrite-Hudson URL value is always used Change By: Alex Earl (20/May/13 12:16 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-5486) email-ext $CHANGES_SINCE_LAST_SUCCESS showPaths does not work
Alex Earl closed JENKINS-5486 as Fixed email-ext $CHANGES_SINCE_LAST_SUCCESS showPaths does not work Change By: Alex Earl (20/May/13 12:16 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-8582) Exception while replacing JELLY_SCRIPT. Please report this as a bug.
Alex Earl closed JENKINS-8582 as Fixed Exception while replacing JELLY_SCRIPT. Please report this as a bug. Change By: Alex Earl (20/May/13 12:16 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-5936) Need tokens to get failed tests count and total tests count, to put them in mail subject easy
Alex Earl closed JENKINS-5936 as Fixed Need tokens to get failed tests count and total tests count, to put them in mail subject easy Change By: Alex Earl (20/May/13 12:17 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-8683) EMail still contains 'hudson' instead of 'jenkins'
Alex Earl closed JENKINS-8683 as Wont Fix EMail still contains hudson instead of jenkins Change By: Alex Earl (20/May/13 12:17 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-8071) Should be able to optionally prevent duplicate email notifications
Alex Earl closed JENKINS-8071 as Fixed Should be able to optionally prevent duplicate email notifications Change By: Alex Earl (20/May/13 12:16 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-5411) Send the still unstable email rather than the unstable email, when the previous status was fail, and the status before that was unstable.
Alex Earl closed JENKINS-5411 as Fixed Send the still unstable email rather than the unstable email, when the previous status was fail, and the status before that was unstable. Change By: Alex Earl (20/May/13 12:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-8190) DEFAULT_EMAIL_LIST token
Alex Earl closed JENKINS-8190 as Fixed DEFAULT_EMAIL_LIST token Change By: Alex Earl (20/May/13 12:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-8011) Email-ext: Support setting charset option for email.
Alex Earl closed JENKINS-8011 as Fixed Email-ext: Support setting charset option for email. Change By: Alex Earl (20/May/13 12:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-7740) Add Requester as possible mail destination
Alex Earl closed JENKINS-7740 as Fixed Add Requester as possible mail destination Change By: Alex Earl (20/May/13 12:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-9818) NullPointerException trying to test email configuration by sending an email to admin email address
Alex Earl closed JENKINS-9818 as Not A Defect NullPointerException trying to test email configuration by sending an email to admin email address Change By: Alex Earl (20/May/13 12:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-10361) Extended email plugin should support attaching a file via a new token ${ATTACH_FILE, path}
Alex Earl
closed JENKINS-10361 as Duplicate
Extended email plugin should support attaching a file via a new token ${ATTACH_FILE, path}
Change By:
Alex Earl
(20/May/13 12:19 PM)
Status:
Resolved
Closed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-9948) Add ability to modify recipient list from script
Alex Earl closed JENKINS-9948 as Fixed Add ability to modify recipient list from script Change By: Alex Earl (20/May/13 12:19 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-10292) email-ext doesn't send email when subject contains specific words like fail or start
Alex Earl closed JENKINS-10292 as Fixed email-ext doesnt send email when subject contains specific words like fail or start Change By: Alex Earl (20/May/13 12:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-9018) Allow email-ext to attach files to emails
Alex Earl closed JENKINS-9018 as Fixed Allow email-ext to attach files to emails Change By: Alex Earl (20/May/13 12:19 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-9990) Would really like a delta of failed tests in the email-ext plugin
Alex Earl closed JENKINS-9990 as Not A Defect Would really like a delta of failed tests in the email-ext plugin Change By: Alex Earl (20/May/13 12:19 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-10990) Send email for NOT_BUILT and ABORTED builds
Alex Earl closed JENKINS-10990 as Fixed Send email for NOT_BUILT and ABORTED builds Change By: Alex Earl (20/May/13 12:20 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [walldisplay] (JENKINS-18012) Wall Display does not work for My Views
nikos dimitrakas created JENKINS-18012 Wall Display does not work for My Views Issue Type: Bug Affects Versions: current Assignee: Christian Pelster Components: walldisplay Created: 20/May/13 12:26 PM Description: After upgrade to Jenkins 1.515 Wall Display shows "Not Found" for all views under "My Views". Works fine for global views. Also if a view under "My Views" has the same name as a global view, the global view is presented when opening the Wall Display from within my view with the given name. Project: Jenkins Priority: Major Reporter: nikos dimitrakas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-12543) CLI permissions
Richard Scorer commented on JENKINS-12543 CLI permissions I am still encountering this in Jenkins 1.515 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson commented on JENKINS-18011 Deadlock issue remote slaves 2013-05-20 13:54:07 Full thread dump Java HotSpot(TM) Client VM (23.7-b01 mixed mode): "RMI TCP Connection(7)-10.158.226.24" - Thread t@1933099 java.lang.Thread.State: RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) locked 9adbe1 (a java.io.BufferedInputStream) at java.io.FilterInputStream.read(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers: locked 1647392 (a java.util.concurrent.ThreadPoolExecutor$Worker) "pool-1-thread-1016" - Thread t@1933098 java.lang.Thread.State: TIMED_WAITING at sun.misc.Unsafe.park(Native Method) parking to wait for 9aa718 (a java.util.concurrent.SynchronousQueue$TransferStack) at java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source) at java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(Unknown Source) at java.util.concurrent.SynchronousQueue$TransferStack.transfer(Unknown Source) at java.util.concurrent.SynchronousQueue.poll(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers: None "RMI TCP Connection(6)-10.158.226.24" - Thread t@1933097 java.lang.Thread.State: RUNNABLE at sun.management.ThreadImpl.dumpThreads0(Native Method) at sun.management.ThreadImpl.dumpAllThreads(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(Unknown Source) at com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(Unknown Source) at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(Unknown Source) at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(Unknown Source) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(Unknown Source) at com.sun.jmx.mbeanserver.PerInterface.invoke(Unknown Source) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(Unknown Source) at javax.management.StandardMBean.invoke(Unknown Source) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown Source) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.access$300(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source) at sun.reflect.GeneratedMethodAccessor174.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Locked ownable synchronizers:
[JIRA] [email-ext] (JENKINS-9187) Jelly Content uses different BUILD_URL
Alex Earl closed JENKINS-9187 as Not A Defect Jelly Content uses different BUILD_URL Change By: Alex Earl (20/May/13 12:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-2651) Enhance email notification to optionally (per job) send email on success, not just failure or back on track
Alex Earl closed JENKINS-2651 as Not A Defect Enhance email notification to optionally (per job) send email on success, not just failure or back on track Change By: Alex Earl (20/May/13 12:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-11481) When using $JOB_NAME on email Subject or email Content the real value is not being poputaled.
Alex Earl closed JENKINS-11481 as Not A Defect When using $JOB_NAME on email Subject or email Content the real value is not being poputaled. Change By: Alex Earl (20/May/13 12:49 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-14463) email ext plugin : full console log mail
Alex Earl closed JENKINS-14463 as Not A Defect email ext plugin : full console log mail Change By: Alex Earl (20/May/13 12:49 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-14634) Add support for customized username to email-address inference
Alex Earl closed JENKINS-14634 as Not A Defect Add support for customized username to email-address inference Change By: Alex Earl (20/May/13 12:49 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-12289) Multi-line commit messages should be configurable to appear in Email-Ext build change notifications
Alex Earl closed JENKINS-12289 as Not A Defect Multi-line commit messages should be configurable to appear in Email-Ext build change notifications Change By: Alex Earl (20/May/13 12:49 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-6724) Allow user to select/choose all svn repositories
Alex Earl closed JENKINS-6724 as Not A Defect Allow user to select/choose all svn repositories Change By: Alex Earl (20/May/13 12:49 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-9865) email-ext Change set does not show affected files details
Alex Earl closed JENKINS-9865 as Not A Defect email-ext Change set does not show affected files details Change By: Alex Earl (20/May/13 12:49 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-14776) Not able to add editable e-mail notification
Alex Earl closed JENKINS-14776 as Not A Defect Not able to add editable e-mail notification Change By: Alex Earl (20/May/13 12:50 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-12268) Merge downstream job resuls in a single email
Alex Earl closed JENKINS-12268 as Not A Defect Merge downstream job resuls in a single email Change By: Alex Earl (20/May/13 12:50 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16423) Add option for CC and BCC
Alex Earl closed JENKINS-16423 as Not A Defect Add option for CC and BCC Change By: Alex Earl (20/May/13 12:50 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16237) Extended email plugin no longer sends messages on latest
Alex Earl closed JENKINS-16237 as Not A Defect Extended email plugin no longer sends messages on latest Change By: Alex Earl (20/May/13 12:50 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Alex Earl closed JENKINS-16163 as Not A Defect NullPointerException when sending post build emails - all triggers appear to be impacted Change By: Alex Earl (20/May/13 12:51 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16409) Add a Script trigger
Alex Earl closed JENKINS-16409 as Not A Defect Add a Script trigger Change By: Alex Earl (20/May/13 12:50 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-15127) Email-Ext : Date Token
Alex Earl closed JENKINS-15127 as Not A Defect Email-Ext : Date Token Change By: Alex Earl (20/May/13 12:50 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16746) Unable to send email since Jenkins 1.500
Alex Earl closed JENKINS-16746 as Not A Defect Unable to send email since Jenkins 1.500 Change By: Alex Earl (20/May/13 12:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16779) PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin
Alex Earl closed JENKINS-16779 as Not A Defect PROPFILE token does not evaluate in the Editable E-mail Notification for the email-ext plugin Change By: Alex Earl (20/May/13 12:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16910) Email Ext-Plugin doesn't work with Jenkins 1.502
Alex Earl closed JENKINS-16910 as Not A Defect Email Ext-Plugin doesnt work with Jenkins 1.502 Change By: Alex Earl (20/May/13 12:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Alex Earl closed JENKINS-16373 as Not A Defect email-ext cant access SVN_REVISION_1 Change By: Alex Earl (20/May/13 12:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17659) Attach URLTrigger Log to email
Alex Earl closed JENKINS-17659 as Not A Defect Attach URLTrigger Log to email Change By: Alex Earl (20/May/13 12:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-11309) Email notifications are sent on build failures regardless of options
Alex Earl closed JENKINS-11309 as Cannot Reproduce Email notifications are sent on build failures regardless of options Change By: Alex Earl (20/May/13 12:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-7756) Content types use \n at end of lines instead of br for html emails
Alex Earl closed JENKINS-7756 as Cannot Reproduce Content types use \n at end of lines instead of br for html emails Change By: Alex Earl (20/May/13 12:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-9759) Allow access to build parameters
Alex Earl closed JENKINS-9759 as Cannot Reproduce Allow access to build parameters Change By: Alex Earl (20/May/13 12:52 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-13893) email-ext crashes when job log contains left or right simple-quote ''
Alex Earl closed JENKINS-13893 as Cannot Reproduce email-ext crashes when job log contains left or right simple-quote Change By: Alex Earl (20/May/13 12:53 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-14069) Access denied when installing email-ext.jpi through Update Center
Alex Earl closed JENKINS-14069 as Cannot Reproduce Access denied when installing email-ext.jpi through Update Center Change By: Alex Earl (20/May/13 12:53 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-5206) Allowing TLS smpt connection, fixing authentification (patch for older version than current)
Alex Earl closed JENKINS-5206 as Cannot Reproduce Allowing TLS smpt connection, fixing authentification (patch for older version than current) Change By: Alex Earl (20/May/13 12:53 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-15442) email-ext plugin does not save configuration on job
Alex Earl closed JENKINS-15442 as Cannot Reproduce email-ext plugin does not save configuration on job Change By: Alex Earl (20/May/13 12:53 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17838) full build log not in content of email
Alex Earl closed JENKINS-17838 as Cannot Reproduce full build log not in content of email Change By: Alex Earl (20/May/13 12:53 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-12577) Email notification hangs due to NullPointerException
Alex Earl closed JENKINS-12577 as Cannot Reproduce Email notification hangs due to NullPointerException Change By: Alex Earl (20/May/13 12:53 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18011) Deadlock issue remote slaves
Marcus Jacobsson edited a comment on JENKINS-18011 Deadlock issue remote slaves Related to https://github.com/jenkinsci/jenkins/pull/782 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-9594) Should be able to send test e-mail based on previous build
Alex Earl commented on JENKINS-9594 Should be able to send test e-mail based on previous build My initial implementation will not support the text area for editing/saving the template, but will allow you to see the rendered content based on a previous build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-9594) Should be able to send test e-mail based on previous build
SCM/JIRA link daemon commented on JENKINS-9594 Should be able to send test e-mail based on previous build Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/EmailExtTemplateAction.java src/main/java/hudson/plugins/emailext/EmailExtensionPlugin.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/resources/hudson/plugins/emailext/EmailExtTemplateAction/index.jelly src/main/resources/hudson/plugins/emailext/EmailExtTemplateAction/index.properties src/main/resources/hudson/plugins/emailext/Messages.properties src/main/webapp/images/template-debugger.png http://jenkins-ci.org/commit/email-ext-plugin/5957b9fc6229fb20b2c7d57f1700747a6d361256 Log: Fixed JENKINS-9594 Added action to the project that contains the email-ext as a publisher which allows the user to enter a template name, select a previous build and see the rendered template. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-9594) Should be able to send test e-mail based on previous build
Alex Earl resolved JENKINS-9594 as Fixed Should be able to send test e-mail based on previous build Change By: Alex Earl (20/May/13 1:38 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/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18013) Make Project Name to be a hyperlink
Jarek Kapica created JENKINS-18013 Make Project Name to be a hyperlink Issue Type: Improvement Assignee: Fred G Components: extra-columns Created: 20/May/13 1:45 PM Description: When showing "Project Name" in "Project description" column, it should be a hyperlink to project details as is normally with the default "Project Name" column. That would allow taking off the default "Project Name" column from the view. Currently without the default column, there is no lonk to the project overview screen. It would be ideal if the link is active as currently is. I.e. showing submenu when hovering over it. But it would also be ok if it is just plain link. Project: Jenkins Priority: Major Reporter: Jarek Kapica This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18013) Make Project Name to be a hyperlink
Jarek Kapica updated JENKINS-18013 Make Project Name to be a hyperlink Change By: Jarek Kapica (20/May/13 1:46 PM) Description: WhenshowingProjectNameinProjectdescriptioncolumn,itshouldbeahyperlinktoprojectdetailsasisnormallywiththedefaultProjectNamecolumn.ThatwouldallowtakingoffthedefaultProjectNamecolumnfromtheview.Currentlywithoutthedefaultcolumn,thereisno lonk link totheprojectoverviewscreen.Itwouldbeidealifthelinkisactiveascurrentlyis.I.e.showingsubmenuwhenhoveringoverit.Butitwouldalsobeokifitisjustplainlink. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sounds] (JENKINS-13825) Sounds plugin configuration System command is empty
oxcafebabe commented on JENKINS-13825 Sounds plugin configuration System command is empty I've had a look at this, but for all the tests I've run the current code is still correct. I haven't been able to reproduce the systemCommand value coming back in the playMethod object. All I can think is that in later versions of Jenkins it does, but I've not found a version that does (I only went up to 400). If we apply the suggested patch it will break all old versions. If we can find which version causes the bug we can maybe add some version dependent code (yuk!). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17988) Broken image links when using CloudBees Folders plugin
Jesse Glick resolved JENKINS-17988 as Fixed Broken image links when using CloudBees Folders plugin Change By: Jesse Glick (20/May/13 2:48 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Eric Freeman
created JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Components:
email-ext
Created:
20/May/13 3:14 PM
Description:
After upgrading Email-ext plugin to 2.29 from 2.27.1 using the ${ENV, var="FOO"} format no longer works. $FOO does however. Once I reverted back to 2.27.1 it started working again.
Environment:
Jenkins 1.514
Project:
Jenkins
Priority:
Major
Reporter:
Eric Freeman
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-16512) v1.3.x perforce plugin doesn't work with the latest perforce 2012.2
Rob Petti commented on JENKINS-16512 v1.3.x perforce plugin doesnt work with the latest perforce 2012.2 That's very strange, because it works fine for me. 'p4 where //...' is extremely lightweight, and takes next to no time at all to execute, so I have no idea why your server would be blocking it. Can you try 'p4 where //workspace/...' and see if it returns the same thing? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Do you have the token-macro plugin installed?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Eric Freeman
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I do have the token-macro plugin installed. Is this a conflict causing an issue for me?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I just tried with 2.29 and I was able to use both formats. ${ENV, var="USERNAME"} and $USERNAME both worked and produced the correct output. You need to verify that token-macro is installed and enabled.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
No, the email-ext plugin relies on the token-macro plugin. Please make sure token-macro is updated to 1.6
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-16512) v1.3.x perforce plugin doesn't work with the latest perforce 2012.2
Tom Hollis commented on JENKINS-16512 v1.3.x perforce plugin doesnt work with the latest perforce 2012.2 I would love to, but I spoke to the perforce administrators and they sorted it out. I can ask them what they did if that will help Tom This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-16512) v1.3.x perforce plugin doesn't work with the latest perforce 2012.2
Rob Petti commented on JENKINS-16512 v1.3.x perforce plugin doesnt work with the latest perforce 2012.2 That would help a lot, 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/groups/opt_out.
[JIRA] [sounds] (JENKINS-13825) Sounds plugin configuration System command is empty
Hua Zhang
commented on JENKINS-13825
Sounds plugin configuration System command is empty
I also suspected that the reason might be the behaviour change of the XML serializaton in some underlying library. IIRC, the plugin was broken after I upgraded Jenkins, not the plugin itself. My best guess is some version near 1.463 since I upgrade Jenkins quite frequently, so I tend to believe that this occurs between 1.45x - 1.463, of course I could very probably be wrong for its so long time ago.
I debugged against 1.460, the JSONObject is not a flat structure (was it before?), so playMethod is now a child node of the json object, therefore directly json.optString("systemCommand") would return null.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sounds] (JENKINS-13825) Sounds plugin configuration System command is empty
Hua Zhang
edited a comment on JENKINS-13825
Sounds plugin configuration System command is empty
I also suspected that the reason might be the behaviour change of the XML serializaton in some underlying library. IIRC, the plugin config was broken after I upgraded Jenkins, not the plugin itself. My best guess is some version near 1.463 since I upgrade Jenkins quite frequently, so I tend to believe that this occurs between 1.45x - 1.463, of course I could very probably be wrong for its so long time ago.
I debugged against 1.460, the JSONObject is not a flat structure (was it before?), so playMethod is now a child node of the json object, therefore directly json.optString("systemCommand") would return null.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Eric Freeman
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
I have that plugin installed and is version 1.6. I updated to 2.9 again and still see the same issue. Now I can't downgrade to 2.27.1 and I'm broken again unless I update all these variables.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.
Alex Earl
commented on JENKINS-18014
[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.
Is there anything in the jenkins log? I can't reproduce this with the 1.508.1 LTS (which is what email-ext is based on for core dependency) + email-ext 2.29 and token-macro 1.6
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-18015) Breakage on Android SDK r22
Brian Lee created JENKINS-18015 Breakage on Android SDK r22 Issue Type: Bug Affects Versions: current Assignee: Christopher Orr Components: android-emulator Created: 20/May/13 4:52 PM Description: In Android SDK r22, aapt was moved from platform-tools/ to build-tools/17.0.0/. This causes Android Emulator plug-in to stop working with the following error: android Required Android tools not found in PATH; cannot continue Putting $ANDROID_HOME/build-tools/17.0.0/ in the path variable doesn't resolve the issue. The temporary workaround is to create a soft-link under $ANDROID_HOME/platform-tools/ to $ANDROID_HOME/build-tools/17.0.0/aapt Project: Jenkins Priority: Minor Reporter: Brian Lee This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15642) ArrayIndexOutOfBounds exception with Maven build when triggered by SCM change
Jesse Glick resolved JENKINS-15642 as Duplicate ArrayIndexOutOfBounds exception with Maven build when triggered by SCM change Change By: Jesse Glick (20/May/13 4:59 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15652) ArrayIndexOutOfBoundsException from AbstractLazyLoadRunMap.search
Jesse Glick updated JENKINS-15652 ArrayIndexOutOfBoundsException from AbstractLazyLoadRunMap.search Change By: Jesse Glick (20/May/13 5:01 PM) Summary: Allexecutorsdeadwithitem.isStuck(): ArrayIndexOutOfBoundsException andmoreinlogs fromAbstractLazyLoadRunMap.search Labels: exception Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-15957) All build executors permanently Dead!
Jesse Glick resolved JENKINS-15957 as Duplicate All build executors permanently Dead! Change By: Jesse Glick (20/May/13 5:07 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17715) Display Name is not shown
Bruce Coveny commented on JENKINS-17715 Display Name is not shown This states resolved but I we are on version 1.514 and are still seeing the Job Name being shown in the tabs on the main screen and not the Job Display Name. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17715) Display Name is not shown
Bruce Coveny edited a comment on JENKINS-17715 Display Name is not shown This states resolved but we are on version 1.514 and are still seeing the Job Name being shown in the tabs on the main screen and not the Job Display Name. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Jaen S commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Experiencing this daily as well. Fairly frustrating. Jenkins 1.514 java version "1.6.0_27" OpenJDK Runtime Environment (IcedTea6 1.12.3) (6b27-1.12.3-0ubuntu1~12.04.1) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Stack trace of looping thread: java.lang.Thread.State: RUNNABLE at java.util.zip.Deflater.deflateBytes(Native Method) at java.util.zip.Deflater.deflate(Deflater.java:322) - locked 0x8cbec4d8 (a java.util.zip.ZStreamRef) at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:176) at java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:135) at java.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:89) - locked 0x8cbec490 (a java.util.zip.GZIPOutputStream) at org.kohsuke.stapler.compression.FilterServletOutputStream.write(FilterServletOutputStream.java:31) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:220) at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:315) at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:148) - locked 0x8cc1a478 (a java.io.OutputStreamWriter) at java.io.OutputStreamWriter.close(OutputStreamWriter.java:233) at java.io.PrintWriter.close(PrintWriter.java:312) - locked 0x8cc1a478 (a java.io.OutputStreamWriter) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:78) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:53) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17715) Display Name is not shown
sogabe commented on JENKINS-17715 Display Name is not shown This is fixed in 1.515. see changelog. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
