[JIRA] [core] (JENKINS-17590) Builds fail because of slave went offline during the build
Andrew Erickson resolved JENKINS-17590 as Duplicate Builds fail because of slave went offline during the build duplicate, moving activity to JENKINS-16778 Change By: Andrew Erickson (31/May/13 5:57 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [timestamper] (JENKINS-16778) Timestamper makes the build fail if the slave if put offline during the build.
Andrew Erickson commented on JENKINS-16778 Timestamper makes the build fail if the slave if put offline during the build. Steven, Joris, (or anyone with permissions - not sure where to see a list of people), Will you please publish a 1.5.4 with this latest fix? Thanks, Andy This message is automatically generated by JIRA. 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-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
Niels Beekman commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process 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) This message is automatically generated by JIRA. 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] [job-dsl-plugin] (JENKINS-18141) BuildParameters: Support for Password
Justin Ryan commented on JENKINS-18141 BuildParameters: Support for Password For a basis for the method: https://github.com/andrewharmellaw/job-dsl-plugin/commit/37a818537991e801b39c6f40daee751c79764a93 This message is automatically generated by JIRA. 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] [timestamper] (JENKINS-16778) Timestamper makes the build fail if the slave if put offline during the build.
Martin Schröder commented on JENKINS-16778 Timestamper makes the build fail if the slave if put offline during the build. Seconded. We're not that keen on using a self-compiled version, either. It should be a measure of last resort, after all. Plus, it always raises inquisitive questions by users when your productive server contains a "-SNAPSHOT" plugin. Best regards, Martin. This message is automatically generated by JIRA. 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] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi created JENKINS-18155 Recent changes view slow because of JIRA plugin Issue Type: Improvement Assignee: Unassigned Components: jira Created: 31/May/13 7:53 AM Description: When displaying the changes view when you have many changes with associated JIRA tickets, the operation can be quite slow. Seems like the JiraChangeLogAnnotator is trying to get each JIRA issue in a single call, even if the issue has already been fetched previously - e.g. because another change already had the same issue Project: Jenkins Priority: Major Reporter: kutzi This message is automatically generated by JIRA. 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] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi commented on JENKINS-18155 Recent changes view slow because of JIRA plugin Thread dump: Handling GET /job/X/changes : RequestHandlerThread22349 "Handling GET /job/X/changes : RequestHandlerThread22349" Id=1061466 Group=main RUNNABLE at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) locked java.io.BufferedInputStream@78cdd495 at org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583) at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165) at org.apache.axis.client.Call.invokeEngine(Call.java:2784) at org.apache.axis.client.Call.invoke(Call.java:2767) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at hudson.plugins.jira.soap.JirasoapserviceV2SoapBindingStub.getIssue(JirasoapserviceV2SoapBindingStub.java:3881) at hudson.plugins.jira.JiraSession.getIssue(JiraSession.java:120) at hudson.plugins.jira.JiraSite.getIssue(JiraSite.java:293) at hudson.plugins.jira.JiraChangeLogAnnotator.annotate(JiraChangeLogAnnotator.java:72) at hudson.scm.ChangeLogSet$Entry.getMsgAnnotated(ChangeLogSet.java:210) at sun.reflect.GeneratedMethodAccessor766.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsString(ExpressionSupport.java:46) at org.apache.commons.jelly.tags.core.ExprTag.doTag(ExprTag.java:42) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
[JIRA] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi assigned JENKINS-18155 to kutzi Recent changes view slow because of JIRA plugin Change By: kutzi (31/May/13 7:56 AM) Assignee: kutzi This message is automatically generated by JIRA. 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] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi commented on JENKINS-18155 Recent changes view slow because of JIRA plugin Idea: cache recently accessed issues This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-18155) 'Recent changes' view slow because of JIRA plugin
kutzi commented on JENKINS-18155 Recent changes view slow because of JIRA plugin Wondering why it seems to be so slow on every display - shouldn't the issues be saved to the build after the 1st display? This message is automatically generated by JIRA. 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] [doxygen] (JENKINS-18154) HTML output directory is incorrect when folderWhereYouRunDoxygen is used
SCM/JIRA link daemon commented on JENKINS-18154 HTML output directory is incorrect when folderWhereYouRunDoxygen is used Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/doxygen/DoxygenDirectoryParser.java src/test/java/hudson/plugins/doxygen/DoxygenArchiverTest.java http://jenkins-ci.org/commit/doxygen-plugin/8a61bf917a5b9fe9cd669d4fcdc3966965e4198c Log: Merge pull request #5 from kbriggs/bugfix-JENKINS-18154 JENKINS-18154 Use correct HTML output with folderWhereYouRunDoxygen Compare: https://github.com/jenkinsci/doxygen-plugin/compare/e05b4e9fdc8c...8a61bf917a5b This message is automatically generated by JIRA. 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] [slave-setup] (JENKINS-17994) Make executor number available for defining workspace location
Roel Van de Paar commented on JENKINS-17994 Make executor number available for defining workspace location We also have this issue. It would be great to have the executor number within the workspace path /1/, /2/, etc. for example. This message is automatically generated by JIRA. 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] [slave-setup] (JENKINS-17994) Make executor number available for defining workspace location
Alexey Bychko commented on JENKINS-17994 Make executor number available for defining workspace location there is a problem with dynamically created workspaces: seems jenkins uses static workspaces and paths and there is a possibility to get lost all previously created workspaces and get ENOSPACE at some point. and no ability to update the code - it will be fresh checkout, always This message is automatically generated by JIRA. 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-13977) Broken breadcrumb link drops me on contextMenu
evernat resolved JENKINS-13977 as Fixed Broken breadcrumb link drops me on contextMenu Resolving the issue, since it is said as fixed. Reopen if not fixed. Change By: evernat (31/May/13 9:26 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [doxygen] (JENKINS-18154) HTML output directory is incorrect when folderWhereYouRunDoxygen is used
Gregory Boissinot resolved JENKINS-18154 as Fixed HTML output directory is incorrect when folderWhereYouRunDoxygen is used Change By: Gregory Boissinot (31/May/13 9:43 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [template-project] (JENKINS-16800) When including publishers from another job, the link to the report is not added
SCM/JIRA link daemon commented on JENKINS-16800 When including publishers from another job, the link to the report is not added Code changed in jenkins User: William Bernardet Path: src/main/java/hudson/plugins/templateproject/ItemListenerImpl.java src/main/java/hudson/plugins/templateproject/ProxyBuilder.java src/main/java/hudson/plugins/templateproject/ProxyPublisher.java src/main/java/hudson/plugins/templateproject/UpdateTransientProperty.java http://jenkins-ci.org/commit/template-project-plugin/97547e3edcb877fd23b4ef017a33ac05d60e580b Log: Fix proposal for JENKINS-16800 This message is automatically generated by JIRA. 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] [template-project] (JENKINS-16800) When including publishers from another job, the link to the report is not added
SCM/JIRA link daemon commented on JENKINS-16800 When including publishers from another job, the link to the report is not added Code changed in jenkins User: Nicolas De loof Path: pom.xml src/main/java/hudson/plugins/templateproject/ItemListenerImpl.java src/main/java/hudson/plugins/templateproject/ProxyBuilder.java src/main/java/hudson/plugins/templateproject/ProxyPublisher.java src/main/java/hudson/plugins/templateproject/UpdateTransientProperty.java http://jenkins-ci.org/commit/template-project-plugin/b161898e4453eda7dcf611e50ccc0a8dba5687e1 Log: Merge pull request #5 from williambernardet/master Fix proposal for JENKINS-16800 Compare: https://github.com/jenkinsci/template-project-plugin/compare/87030edf5d24...b161898e4453 This message is automatically generated by JIRA. 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-17416) Improve label Wipe Out Workspace
Michael Pailloncy resolved JENKINS-17416 as Fixed Improve label Wipe Out Workspace Change By: Michael Pailloncy (31/May/13 10:06 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18125) Changelog empty or contains all changes
Alex Whitman commented on JENKINS-18125 Changelog empty or contains all changes I believe I've figured out why all of the changes appear in each build changelog rather than just the actual changes in the pull request. In the `if` block at https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L1128 the merge is performed with the specified branch. However, as far as I can tell, nowhere in that block is the merge branch updated from `origin` so the merge is always on top of, potentially, an out of date copy of the branch. Therefore `git whatchanged` is looking at an old rev as the starting point. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18125) Changelog empty or contains all changes
Mark Waite commented on JENKINS-18125 Changelog empty or contains all changes I think that is "by design" of the git plugin. A GitHub pull request is a request to merge something, and the GitHub Pull Request plugin needs a destination for that merge. I assume that destination is set in the git plugin advanced options section. I think you'll also need to add a post-build step to use the Git publisher to push the merged changes back to the destination branch. If you don't add that post-build step, then the git plugin will perform the merge to the base branch each time, and report all the differences each time (I think). At least, that is how my experiments have worked when using the git plugin to merge changes from multiple git branches (without the GitHub pull request 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] [envinject] (JENKINS-16233) EnvInject plugin using a cached value for ${WORKSPACE}
Magnus Jacobsson
commented on JENKINS-16233
EnvInject plugin using a cached value for ${WORKSPACE}
Is this the same problem as JENKINS-13348?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18125) Changelog empty or contains all changes
Alex Whitman commented on JENKINS-18125 Changelog empty or contains all changes I have it set to merge into 'master' before build. The issue is that 'master' doesn't appear to get updated from origin. Take this scenario: master is at version 1 pull request is opened and jenkins merges into master v1 and then builds pull request is merged and master is now v2 new pull request is opened, jenkins hasn't updated master to v2 and so merges into v1 and builds Looking through the code, at no point is a `git pull` or `git fetch/merge` done on master (or whatever the specified merge branch is) before merging the pull request changes. This message is automatically generated by JIRA. 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] [artifactory] (JENKINS-13900) Changing the artifactory server doesn't change the server used in jobs
Phil Ostler commented on JENKINS-13900 Changing the artifactory server doesnt change the server used in jobs I believe I'm seeing the same but only when performing a Maven release. Normal SNAPSHOT builds correctly push to Artifactory but fail with the old URL being inaccessible on release. This message is automatically generated by JIRA. 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] [ldap] (JENKINS-16443) Multiple LDAP server
teilo commented on JENKINS-16443 Multiple LDAP server multiple domains can be supported if they are withing the same forest - by using the global catalogue LDAP port (3268). If they are not in the same forest (i.e. just a trust domain) then this does not work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jacoco] (JENKINS-14010) Create the wiki page for this plugin on the Jenkins wiki
SCM/JIRA link daemon commented on JENKINS-14010 Create the wiki page for this plugin on the Jenkins wiki Code changed in jenkins User: Alex Earl Path: email-ext/taglib b/src/main/resources/lib/email-ext/taglib 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/java/hudson/plugins/emailext/plugins/EmailTrigger.java src/main/java/hudson/plugins/emailext/plugins/EmailTriggerDescriptor.java src/main/java/hudson/plugins/emailext/plugins/trigger/AbortedTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/AbstractScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/BuildingTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FirstFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FixedTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/ImprovementTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/NotBuiltTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/NthFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/PreBuildScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/PreBuildTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/ScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/SecondFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/StillFailingTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/StillUnstableTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/SuccessTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/UnstableTrigger.java src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/config.groovy src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/help-tokens.groovy src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/help-tokens.properties src/main/resources/hudson/plugins/emailext/plugins/EmailTrigger/config.groovy src/main/resources/hudson/plugins/emailext/plugins/EmailTrigger/config.properties src/main/resources/hudson/plugins/emailext/plugins/trigger/PreBuildScriptTrigger/local-config.groovy src/main/resources/hudson/plugins/emailext/plugins/trigger/ScriptTrigger/local-config.groovy src/main/resources/lib/email-ext/mailtype.jelly src/main/resources/lib/email-ext/mailtype.properties src/main/resources/lib/email-ext/mailtype_ja.properties src/main/resources/lib/email-ext/mailtype_zh_TW.properties src/main/resources/lib/email-ext/tokenhelp.jelly http://jenkins-ci.org/commit/email-ext-plugin/fb5e4581b60d0bd6391941bb908476fc93556e89 Log: Fix JENKINS-14010 Changed triggers to use extension point and Decribable/Descriptor and then moved to a hetero-list for adding them to a job. This message is automatically generated by JIRA. 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] [robot-plugin] (JENKINS-18156) Robotframework is not available in post build actions of Jenkins 1.515/1.516
md42 created JENKINS-18156 Robotframework is not available in post build actions of Jenkins 1.515/1.516 Issue Type: Bug Affects Versions: current Assignee: jpiironen Components: robot-plugin Created: 31/May/13 1:45 PM Description: I cannot see the Post-build Action "Publish Robot Framework test results" described in https://wiki.jenkins-ci.org/x/TIDOAg Steps to Reproduce: Have the latest (1.2.3) Robot Framework Plugin installed Open a jenkins job select Button "Add post-build step" The Item "Publish Robot Framework test results" should appear. Can you reproduce? Environment: Ubuntu, Jenkins 1.516 Project: Jenkins Priority: Major Reporter: md42 This message is automatically generated by JIRA. 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] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59
Simon Johansson updated JENKINS-18095 nose generated xunit reports are rejected by xunit 1.59 Change By: Simon Johansson (31/May/13 2:02 PM) Attachment: nosetests.xml This message is automatically generated by JIRA. 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] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59
Simon Johansson commented on JENKINS-18095 nose generated xunit reports are rejected by xunit 1.59 I seem to have the same issue, I generate XML like so; "nosetests --with-xunit" Runnig post-build action "Publish JUnit test result report" over the file works fine, but using "Publish xUnit test result report" with JUnit patters I get the following error xUnit INFO - Starting to record. xUnit INFO - Processing JUnit xUnit INFO - JUnit - 1 test report file(s) were found with the pattern '**/nosetests.xml' relative to '/var/lib/jenkins/jenkins-data/jobs/Skuscraper/workspace' for the testing framework 'JUnit'. xUnit ERROR - The result file '/var/lib/jenkins/jenkins-data/jobs/Skuscraper/workspace/skuscraper/nosetests.xml' for the metric 'JUnit' is not valid. The result file has been skipped. xUnit INFO - Fail BUILD because 'set build failed if errors' option is activated. xUnit INFO - There are errors when processing test results. xUnit INFO - Skipping tests recording. xUnit INFO - Stop build. I have attached my nosetests.xml. This message is automatically generated by JIRA. 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] [ldap] (JENKINS-17281) Please add a config option for groupSearchFilter
Steffen Breitbach commented on JENKINS-17281 Please add a config option for groupSearchFilter +1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jacoco] (JENKINS-14010) Create the wiki page for this plugin on the Jenkins wiki
Alex Earl commented on JENKINS-14010 Create the wiki page for this plugin on the Jenkins wiki My commit message referenced the incorrect JIRA item, please disregard the changes to email-ext as pertaining to this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18157) Email Template Testing can't find passed script file
Volodja Medvid created JENKINS-18157 Email Template Testing cant find passed script file Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 31/May/13 3:12 PM Description: Newly implemented Email Template Testing feature doesn't work. If name of template file is passed with extension following error occurs: Jelly script [myscript.jelly] was not found in $JENKINS_HOME/email-templates. If name of template file is passed without extension following error occurs: Template [myscript] was not found in $JENKINS_HOME/email-templates. additionally a validation error is shown: The file 'myscript' does not exist The problem is that EmailExtTemplateAction.doTemplateFileCheck() and EmailExtTemplateAction.renderTemplate() methods expect that template name includes extension. But JellyScriptContent.getTemplateInputStream() expects that template name doesn't contains extension. Environment: OS: Windows 7 Jenkins: 1.516 Email-ext: 2.30.2 Project: Jenkins Priority: Major Reporter: Volodja Medvid This message is automatically generated by JIRA. 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-18157) Email Template Testing can't find passed Jelly script file
Alex Earl commented on JENKINS-18157 Email Template Testing cant find passed Jelly script file Thanks for testing this I'll see if I can get a fix in for the next release. This message is automatically generated by JIRA. 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] [maven] (JENKINS-14351) Outdated JRuby libs
Jesse Glick assigned JENKINS-14351 to Jesse Glick Outdated JRuby libs Change By: Jesse Glick (31/May/13 3:14 PM) Assignee: JesseGlick This message is automatically generated by JIRA. 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] [maven] (JENKINS-14351) Outdated JRuby libs
Jesse Glick started work on JENKINS-14351 Outdated JRuby libs Change By: Jesse Glick (31/May/13 3:14 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18157) Email Template Testing can't find passed Jelly script file
Volodja Medvid updated JENKINS-18157 Email Template Testing cant find passed Jelly script file Change By: Volodja Medvid (31/May/13 3:15 PM) Summary: EmailTemplateTestingcantfindpassed Jelly scriptfile This message is automatically generated by JIRA. 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-18157) Email Template Testing can't find passed Jelly script file
Volodja Medvid
updated JENKINS-18157
Email Template Testing cant find passed Jelly script file
Change By:
Volodja Medvid
(31/May/13 3:16 PM)
Description:
NewlyimplementedEmailTemplateTestingfeaturedoesntwork
forJellyscripts
.
Ifnameoftemplatefileispassedwithextensionfollowingerroroccurs:{noformat}Jellyscript[myscript.jelly]wasnotfoundin$JENKINS_HOME/email-templates.{noformat}Ifnameoftemplatefileispassedwithoutextensionfollowingerroroccurs:{noformat}Template[myscript]wasnotfoundin$JENKINS_HOME/email-templates.{noformat}additionallyavalidationerrorisshown:{noformat}Thefilemyscriptdoesnotexist{noformat}Theproblemisthat{{EmailExtTemplateAction.doTemplateFileCheck()}}and{{EmailExtTemplateAction.renderTemplate()}}methodsexpectthattemplatenameincludesextension.But{{JellyScriptContent.getTemplateInputStream()}}expectsthattemplatenamedoesntcontainsextension.
This message is automatically generated by JIRA.
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] [flexible-publish] (JENKINS-18158) Flexible Publish plugin doesn't always respect job ancestry
Kevin Phillips created JENKINS-18158 Flexible Publish plugin doesnt always respect job ancestry Issue Type: Bug Affects Versions: current Assignee: bap Components: flexible-publish Created: 31/May/13 3:19 PM Description: It seems that when using the flexible publish plugin to trigger other projects doesn't hook into the Jenkins project ancestry properly. For example, choosing "Flexible Publish - Trigger / call builds on other projects" and point it to another Jenkins job does not cause the target job to show up in the dependency graph as a child of the first project. Similarly the "block on upstream and downstream jobs" options in either job configuration doesn't respect the relationship between the two jobs. Further, given the fact that according to the plugin wiki page the standard "trigger other job" post-build stage is not currently supported by the plugin, which seems to be the only other way to conditionally trigger other jobs based on criteria provided by the current job. Project: Jenkins Priority: Major Reporter: Kevin Phillips This message is automatically generated by JIRA. 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] [deploy] (JENKINS-11030) Deploying to Glassfish fails with a ClassCastException
Steve Katra commented on JENKINS-11030 Deploying to Glassfish fails with a ClassCastException I am also experiencing this problem. I have a war which deploys fine to tomcat but when I try to deploy it to glassfish it throws the exceptions below. Its probably important to note that I'm running Jenkins on the same glassfish instance as I'm trying to deploy to locally. I'm using the deploy plugin with the following settings: war/ear file: **/daf-1.0.0-BUILD-SNAPSHOT.war context: daf container: Glassfish 3.x GlassFish admin port: 4848 GlassFish hostname: 127.0.0.1 [#|2013-05-31T11:46:32.180-0400|WARNING|glassfish3.1.2|hudson.model.AbstractBuild|_ThreadID=105;_ThreadName=Executor #1 for master : executing daf-deploy-master #3;|Publisher hudson.plugins.deploy.DeployPublisher aborted due to exception org.codehaus.cargo.util.CargoException: Cannot communicate with the server at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:126) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:904) at hudson.FilePath.act(FilePath.java:877) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) 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: javax.enterprise.deploy.spi.exceptions.TargetException: Error getting required modules at org.glassfish.deployapi.SunDeploymentManager.getModules(SunDeploymentManager.java:313) at org.glassfish.deployapi.SunDeploymentManager.getRunningModules(SunDeploymentManager.java:200) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.findTargetModule(AbstractJsr88Deployer.java:350) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:122) ... 16 more Caused by: java.lang.ClassCastException: org.glassfish.deployapi.TargetImpl cannot be cast to org.glassfish.deployapi.TargetImpl at org.glassfish.deployapi.SunDeploymentManager.getModules(SunDeploymentManager.java:300) ... 19 more javax.enterprise.deploy.spi.exceptions.TargetException: Error getting required modules at org.glassfish.deployapi.SunDeploymentManager.getModules(SunDeploymentManager.java:313) at org.glassfish.deployapi.SunDeploymentManager.getRunningModules(SunDeploymentManager.java:200) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.findTargetModule(AbstractJsr88Deployer.java:350) at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:122) at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:64) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:90) at hudson.plugins.deploy.CargoContainerAdapter$1.invoke(CargoContainerAdapter.java:77) at hudson.FilePath.act(FilePath.java:904) at hudson.FilePath.act(FilePath.java:877) at hudson.plugins.deploy.CargoContainerAdapter.redeploy(CargoContainerAdapter.java:77) at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:47) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) 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
[JIRA] [dashboard-view] (JENKINS-17571) The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process
dave commented on JENKINS-17571 The main Jenkins dashboard page is slow to reload, seems to cause unusually high CPU load in the process Linux tgts-jenkins 2.6.35-22-server #35-Ubuntu SMP Sat Oct 16 22:02:33 UTC 2010 x86_64 GNU/Linux Ubuntu 10.10 and java version "1.6.0_21" Java(TM) SE Runtime Environment (build 1.6.0_21-b06) Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-18159) Triggering build via post-receive hook does not honor Ignore post-commit hooks setting.
Deniz Bahadir created JENKINS-18159 Triggering build via post-receive hook does not honor Ignore post-commit hooks setting. Issue Type: Improvement Assignee: Nicolas De Loof Components: git Created: 31/May/13 4:09 PM Description: I have two build-projects which use the code from the same git-repository. Project 1 shall be triggered immediately when new changes are pushed to the git-repository. This works as expected by setting up a post-receive hook and enabling SCM polling (without setting any time). Project 2 shall be triggered nightly but only if changes where pushed to the git-repository since the last build. This does work in general as expected: After configuring SCM polling with a specific time, the build gets triggered at night if changes were pushed to the git-repository and will not be triggered if no new changes were pushed since the last successful run. (So far, so good.) However, because of the post-receive hook I set up for project 1 this project 2 will also get triggered every time new commits were pushed to the repository. This, of course, is not what I wanted. In project 2's configuration of SCM-polling I also enabled the checkbox "Ignore post-commit hooks" which obviously should prevent this behavior. However, as the comment states, the SCM-plugin must also support this setting. Could it be that the git-plugin does not check this "Ignore post-commit hooks" setting and therefore ignores it? Would it be possible to implement the correct behavior and do not trigger a build if the checkbox is checked? Environment: Jenkins 1.509.1 LTS, Ubuntu 12.04 LTS (x64) Project: Jenkins Priority: Major Reporter: Deniz Bahadir This message is automatically generated by JIRA. 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] [junit-attachments] (JENKINS-18160) Turn off display of class level attachments, prefering test case level
Luke Daley created JENKINS-18160 Turn off display of class level attachments, prefering test case level Issue Type: Improvement Assignee: huybrechts Components: junit-attachments Created: 31/May/13 4:23 PM Description: Would it be possible to add a way to disable showing attachments on the test class page, when they are actually attached to the test case? I have a situation where there is a test class with a lot of test cases, where those test cases can have a lot of attachments. This means that the test class result page blows out with lots of attachment links, and it's not really helpful at this level. It seems reasonable to me to just not show attachments at the class level if they are attached at the case level, and maybe add some kind of visual indication against each test case on the class page for how many attachments there are for each test case. Project: Jenkins Priority: Major Reporter: Luke Daley This message is automatically generated by JIRA. 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] [junit-attachments] (JENKINS-18160) Turn off display of class level junit attachments, prefering test case level
Luke Daley updated JENKINS-18160 Turn off display of class level junit attachments, prefering test case level Change By: Luke Daley (31/May/13 4:24 PM) Summary: Turnoffdisplayofclasslevel junit attachments,preferingtestcaselevel This message is automatically generated by JIRA. 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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Rami Cohen commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 I have Jenkins 1.515 running on Windows 7 64-bit and Java 1.7.0_17. I see many instances of this error in my log file and it constantly breaks my job chains. I checked the C:\Program Files (x86)\Jenkins\jobs\job name\builds folder and noticed that for each job there is a folder with a name formatted like a date (like 2013-05-24_10-59-49) which contains the actual build data and a shortcut to that folder named after the build number. It looks like the parser is trying to parse the shortcut name instead of the folder name. How soon can this be fixed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-10131) Git polling shouldn't need a workspace on a slave.
jake bishop edited a comment on JENKINS-10131 Git polling shouldnt need a workspace on a slave. Any news on this? I can turn on fast remote polling to get around this. But that is not really a solution because then I can only use one branch (without wildcards). This message is automatically generated by JIRA. 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-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Benny Bottema created JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects Issue Type: Bug Assignee: Unassigned Components: build-pipeline Created: 31/May/13 5:15 PM Description: Came here through the Build Pipeline plugin issue tracker link. Since the migration from google code, an annoying bug got lost, which I wanted to reinstate here. There's a problem when reusing a parameterized downstream project in several upstream projects (with manual run trigger). Only the first upstream project successfully invokes the downstream project retaining parameters set using the groovy script workaround. Other invocations leave the parameters empty in the downstream project. Case in point: 30 application projects, 4 environments to deploy to. With this bug we need to duplicate a deploy script per application (per environment). So instead of 4 deploy scripts, we now have 120 deploy scripts. Related issues: https://code.google.com/p/build-pipeline-plugin/issues/detail?id=54 https://code.google.com/p/build-pipeline-plugin/issues/detail?id=53 Project: Jenkins Labels: plugins Priority: Major Reporter: Benny Bottema This message is automatically generated by JIRA. 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-14351) Outdated JRuby libs
Jesse Glick updated JENKINS-14351 Outdated JRuby libs Change By: Jesse Glick (31/May/13 5:46 PM) Labels: jnanativeunix Component/s: core Component/s: other Component/s: maven URL: https://github.com/jenkinsci/jenkins/pull/770 This message is automatically generated by JIRA. 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-14351) Outdated JRuby libs
Jesse Glick updated JENKINS-14351 Outdated JRuby libs Change By: Jesse Glick (31/May/13 6:36 PM) Labels: jna lts-candidate nativeunix This message is automatically generated by JIRA. 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-14351) Outdated JRuby libs
SCM/JIRA link daemon commented on JENKINS-14351 Outdated JRuby libs Code changed in jenkins User: Jesse Glick Path: changelog.html core/pom.xml core/src/main/java/hudson/Util.java core/src/main/java/hudson/cli/ClientAuthenticationCache.java core/src/main/java/hudson/os/PosixAPI.java core/src/main/java/hudson/os/PosixException.java core/src/main/java/hudson/tools/ZipExtractionInstaller.java core/src/main/java/hudson/util/IOUtils.java core/src/main/java/hudson/util/jna/GNUCLibrary.java http://jenkins-ci.org/commit/jenkins/2a1d1631bd4d3e6d37d82295089d70e229ea0548 Log: FIXED JENKINS-14351 jna-posix → jnr-posix upgrade (opt in). This message is automatically generated by JIRA. 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-14351) Outdated JRuby libs
SCM/JIRA link daemon resolved JENKINS-14351 as Fixed Outdated JRuby libs Change By: SCM/JIRA link daemon (31/May/13 6:37 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] [git] (JENKINS-12316) git plugin should NOT tag every build by default
owenmehegan commented on JENKINS-12316 git plugin should NOT tag every build by default I agree that this behavior is annoying and should not be on by default. All of my repos now have tens or hundreds of jenkins tags that I don't care about, and running 'git tag' on them produces a pretty useless output. Can this be off by default? This message is automatically generated by JIRA. 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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Jesse Glick commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Recent commenters: yes there should be some directories with timestamps as names, and some numeric shortcuts pointing to those directories. Jenkins tries two different ways to follow the shortcut to the directory name, so that it parses the timestamp out of the real directory name, but apparently on some Windows systems both ways are failing and we do not know why. If you can reproduce, please check (1) what hudson.Util.resolveSymlinkToFile says when given the path to the shortcut; (2) what java.io.File.getCanonicalFile says. Also include a dir listing of builds. This message is automatically generated by JIRA. 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] [update-center] (JENKINS-10062) http://updates.jenkins-ci.org/update-center.json should returns JSONP and not JSON
farshidce commented on JENKINS-10062 http://updates.jenkins-ci.org/update-center.json should returns JSONP and not JSON we did run into a situation where the production instance does not have any graphical package installed and it was impossible to get the update json file because of that. a workaround would also be to allow the user to upload the json file instead of letting browser fetch that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-14351) Outdated JRuby libs
dogfood commented on JENKINS-14351 Outdated JRuby libs Integrated in jenkins_main_trunk #2565 FIXED JENKINS-14351 jna-posix → jnr-posix upgrade (opt in). (Revision 2a1d1631bd4d3e6d37d82295089d70e229ea0548) Result = SUCCESS Jesse Glick : 2a1d1631bd4d3e6d37d82295089d70e229ea0548 Files : core/src/main/java/hudson/cli/ClientAuthenticationCache.java core/pom.xml core/src/main/java/hudson/util/IOUtils.java core/src/main/java/hudson/Util.java core/src/main/java/hudson/tools/ZipExtractionInstaller.java core/src/main/java/hudson/os/PosixAPI.java core/src/main/java/hudson/os/PosixException.java changelog.html core/src/main/java/hudson/util/jna/GNUCLibrary.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18157) Email Template Testing can't find passed Jelly script file
SCM/JIRA link daemon commented on JENKINS-18157 Email Template Testing cant find passed Jelly script file Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/content/JellyScriptContent.java http://jenkins-ci.org/commit/email-ext-plugin/16a8d52dc4d65b586dc5310a07152d68a0cd78c0 Log: Fixed JENKINS-18157 Check if file already ends with .jelly and don't add if it does. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [embeddable-build-status] (JENKINS-17798) build badge icon requires authentication
SCM/JIRA link daemon commented on JENKINS-17798 build badge icon requires authentication Code changed in jenkins User: imod Path: pom.xml src/main/java/org/jenkinsci/plugins/badge/BadgeActionFactory.java src/main/java/org/jenkinsci/plugins/badge/ImageResolver.java src/main/java/org/jenkinsci/plugins/badge/PluginImpl.java src/main/java/org/jenkinsci/plugins/badge/PublicBadgeAction.java src/main/resources/org/jenkinsci/plugins/badge/BadgeAction/index.groovy src/main/resources/org/jenkinsci/plugins/badge/BadgeAction/index.properties src/main/resources/org/jenkinsci/plugins/badge/Messages.properties src/test/java/org/jenkinsci/plugins/badge/PublicBadgeActionTest.java http://jenkins-ci.org/commit/embeddable-build-status-plugin/7d2b5945c5a279ab4545aa41dedcd453eb66b15f Log: FIXED JENKINS-17798 expose build badge via unprotected URL, but with new Permission This message is automatically generated by JIRA. 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] [embeddable-build-status] (JENKINS-17798) build badge icon requires authentication
SCM/JIRA link daemon resolved JENKINS-17798 as Fixed build badge icon requires authentication Change By: SCM/JIRA link daemon (31/May/13 8:35 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] [embeddable-build-status] (JENKINS-17798) build badge icon requires authentication
SCM/JIRA link daemon commented on JENKINS-17798 build badge icon requires authentication Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/badge/BadgeActionFactory.java src/main/java/org/jenkinsci/plugins/badge/ImageResolver.java src/main/java/org/jenkinsci/plugins/badge/PluginImpl.java src/main/java/org/jenkinsci/plugins/badge/PublicBadgeAction.java src/main/resources/org/jenkinsci/plugins/badge/BadgeAction/index.groovy src/main/resources/org/jenkinsci/plugins/badge/BadgeAction/index.properties src/main/resources/org/jenkinsci/plugins/badge/Messages.properties src/test/java/org/jenkinsci/plugins/badge/PublicBadgeActionTest.java http://jenkins-ci.org/commit/embeddable-build-status-plugin/3a6e78d3e0a4127e990b2cb39b2d9ab1faa2c71e Log: Merge pull request #4 from imod/unprotected-status FIXED JENKINS-17798 expose build badge via unprotected URL, but with new Permission Compare: https://github.com/jenkinsci/embeddable-build-status-plugin/compare/11843c79f8e3...3a6e78d3e0a4 This message is automatically generated by JIRA. 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-18157) Email Template Testing can't find passed Jelly script file
Alex Earl resolved JENKINS-18157 as Fixed Email Template Testing cant find passed Jelly script file Added check if template name already ends with .jelly and don't append if it does. Change By: Alex Earl (31/May/13 8:36 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] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Amit Kulkarni commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Same issue, running on Ubuntu 12.04 LTS. I had started to doubt my build when I stumbled on this thread. This message is automatically generated by JIRA. 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] [parameters] (JENKINS-18163) Add a spacer or header parameter to allow for some formatting of list of parameters on the Build with parameters page
Michael Chmielewski created JENKINS-18163 Add a spacer or header parameter to allow for some formatting of list of parameters on the Build with parameters page Issue Type: Improvement Assignee: Unassigned Components: parameters Created: 31/May/13 8:42 PM Description: I have a release package job that takes about 10-15 parameters to control what artifacts from several packages (and which artifacts from within a project) are packaged and archived by this job. There are also a few to determine the output structure of the combining of the different artifacts. The list is long enough that it could be relatively easy to chose/check the wrong parameters. It would be nice to add a spacer (like a horizontal rule element) or header (text to designate a section) to better format the page and separate different parameters out into logical groups. Project: Jenkins Priority: Minor Reporter: Michael Chmielewski This message is automatically generated by JIRA. 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] [matrix] (JENKINS-18164) Matrix Jobs Do Not Get Run When Updating a Dynamic Axis
tim johnston created JENKINS-18164 Matrix Jobs Do Not Get Run When Updating a Dynamic Axis Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: matrix Created: 31/May/13 8:44 PM Description: I have a top level job X. In X, I am using kicking off job Y using the File Parameter Factory option in parameterized builds. The configuration files contain a property, axis_values, which is a space separated list of different axis's for job Y. Let's say that job X has one configuration file and it contains axis_values=A B C. I kick off job X, which in turn kicks one instance of job Y. Job Y iterates correctly through A, B and C. Next, I change the configuration file and I set axis_values=A B C D E. I kick off job X and job Y starts. Job Y runs correctly for A, B and C. But, job Y fails to run D and E. It says that "D appears to be cancelled" and "E appears to be cancelled". I see the following in the log: 31-May-2013 3:57:48 PM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at hudson.model.Executor.run(Executor.java:238) The only workaround that I have found is that it will work correctly if I put the new values at the start of the axis. (ie. axis_values=D E A B C) List of (possibly) relevant plugins installed; dynamic axis environment injector jenkins parameterized trigger matrix sorter node and label parameter plugin Environment: Windows Project: Jenkins Priority: Critical Reporter: tim johnston This message is automatically generated by JIRA. 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
Amit Kulkarni edited a comment on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Same issue, running on Ubuntu 12.04 LTS. Additionally, ONLY when the CSS is broken, I can delete existing users. Other times, the "delete" link on left side is not visible. Does anyone else also have this issue ? Are they related ? This message is automatically generated by JIRA. 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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
dogfood commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Integrated in jenkins_main_trunk #2566 JENKINS-15587 Diagnostics. (Revision eff5635b75a63a536f8ad24231b3eba3cbc4b63e) Result = SUCCESS Jesse Glick : eff5635b75a63a536f8ad24231b3eba3cbc4b63e Files : core/src/main/java/hudson/model/Run.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [violations] (JENKINS-13567) NullPointerException on hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end
Andrew Phillips commented on JENKINS-13567 NullPointerException on hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end Also observed in our jclouds builds. Can help set up a reproducible test case, if that would be useful. 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] [concurrent-build] (JENKINS-13810) Maven modules marked to wrong build when running concurrent job
Jyrki Puttonen commented on JENKINS-13810 Maven modules marked to wrong build when running concurrent job I've changed to freestyle project with Maven buildsteps at the end of February, and this was valid then. Jenkins version was 1.502. This message is automatically generated by JIRA. 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.
