[JIRA] [build-flow] (JENKINS-17906) Executor dies because of AssertionError
julian tragé commented on JENKINS-17906 Executor dies because of AssertionError Version 1.509.2 fixed our problem, since 2 days no dead executors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cvs] (JENKINS-18591) CVS-Plugin sporadically fails to connect via SSH
Sascha Vogt commented on JENKINS-18591 CVS-Plugin sporadically fails to connect via SSH Created a pull-request with the modified POM (to include Jsch 1.50) Not sure, this is the correct way, as previously Jsch wasn't specified as dependency, so I guess it was included via some sort of dependency management. Anyway, here's the pull request: https://github.com/jenkinsci/cvs-plugin/pull/23 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18592) JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520
Bob Verbrugge created JENKINS-18592 JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 03/Jul/13 7:05 AM Description: Projects build with jdk1.5.0_12 fail since the upgrade to Jenkins 1.520 ===JENKINS REMOTING CAPACITY===channel started erreicht: 902 ERROR: Failed to parse POMs java.io.IOException: Remote call on Channel to Maven D:\apps\Java\jdk1.5.0_12/bin/java, -cp, D:\apps\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven-agent-1.3.jar;D:\apps\Maven\apache-maven-2.2.1\boot\classworlds-1.1.jar, hudson.maven.agent.Main, D:\apps\Maven\apache-maven-2.2.1, D:\apps\Jenkins\war\WEB-INF\lib\remoting-2.24.jar, D:\apps\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven-interceptor-1.3.jar, 51928, D:\apps\Jenkins\plugins\maven-plugin\WEB-INF\lib\maven2.1-interceptor-1.2.jar failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.maven.ProcessCache$MavenProcess.init(ProcessCache.java:112) at hudson.maven.ProcessCache.get(ProcessCache.java:231) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:694) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1593) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:491) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) Caused by: java.lang.ClassFormatError: Failed to load hudson.maven.ProcessCache$GetSystemProperties at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:291) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:229) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:113) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1544) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) 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(FutureTask.java:269) at java.util.concurrent.FutureTask.run(FutureTask.java:123) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.lang.ClassLoader.defineClass(ClassLoader.java:465) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:289) ... 22 more Environment: Windows Server 2008 Jenkins 1.520 (en 1.521) als windows service behind Apache 2.2.19 JDK jdk1.7.0_09 projects build with jdk1.5.0_12 Project: Jenkins Priority: Blocker Reporter:
[JIRA] [cvs] (JENKINS-18591) CVS-Plugin sporadically fails to connect via SSH
SCM/JIRA link daemon resolved JENKINS-18591 as Fixed CVS-Plugin sporadically fails to connect via SSH Change By: SCM/JIRA link daemon (03/Jul/13 7:32 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] [cvs] (JENKINS-18591) CVS-Plugin sporadically fails to connect via SSH
SCM/JIRA link daemon commented on JENKINS-18591 CVS-Plugin sporadically fails to connect via SSH Code changed in jenkins User: Sascha Vogt Path: pom.xml http://jenkins-ci.org/commit/cvsclient/4af5d719eb203d125dcf807a8228d64ab9e35333 Log: FIXED JENKINS-18591 - Sporadic connection failures Jsch bug http://sourceforge.net/p/jsch/bugs/58/ causes random connection failures. Fixed in Jsch 1.50 - updating dependency This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cvs] (JENKINS-18591) CVS-Plugin sporadically fails to connect via SSH
SCM/JIRA link daemon commented on JENKINS-18591 CVS-Plugin sporadically fails to connect via SSH Code changed in jenkins User: Michael Clarke Path: pom.xml http://jenkins-ci.org/commit/cvsclient/3003bc92180c2fcca84fef32b535ee418fc9037e Log: Merge pull request #1 from svogt/JENKINS-18591 FIXED JENKINS-18591 - Sporadic connection failures Compare: https://github.com/jenkinsci/cvsclient/compare/33d0c09f41a9...3003bc92180c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17382) Consider display name for sorting on main page
Kris Slowinski commented on JENKINS-17382 Consider display name for sorting on main page Also valid in Older but stable (1.509.2) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-17421) Add support for Build Blocker plugin
Frederik Fromm commented on JENKINS-17421 Add support for Build Blocker plugin Cool Idea. I will try to implement the slice. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-16683) the Build Blocker Plugin is missing from Jira
Frederik Fromm commented on JENKINS-16683 the Build Blocker Plugin is missing from Jira Ferenc is right! Where is my build-blocker-plugin jira? I remember, that it was there before. Please have a look. Thanx! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-18593) Generator parameters not replaced in *system* groovy scripts
Timor Raiman created JENKINS-18593 Generator parameters not replaced in *system* groovy scripts Issue Type: Bug Assignee: Unassigned Components: jobgenerator Created: 03/Jul/13 8:05 AM Description: Using the groovy script plugin, I can refer to generator parameters in the script using a macro notation eg: def aGeneratorParam = "$aGeneratorParam" In system groovy scripts, this does not work, and there's no way to access the generator parameters. (I could use environment variable injection to save the generator parameters into the jobs environment, but that's not nice) Project: Jenkins Priority: Major Reporter: Timor Raiman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-18594) Generator parameters not replaced in Scriptler parameter value macro expressions
Timor Raiman created JENKINS-18594 Generator parameters not replaced in Scriptler parameter value macro expressions Issue Type: New Feature Assignee: Unassigned Components: jobgenerator Created: 03/Jul/13 8:12 AM Description: It is not possible to use Generator parameters in passing values to scriptler scripts. Project: Jenkins Priority: Major Reporter: Timor Raiman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-18593) Generator parameters not replaced in *system* groovy scripts
Timor Raiman
resolved JENKINS-18593 as Cannot Reproduce
Generator parameters not replaced in *system* groovy scripts
The correct syntax is:
def aGeneratorParam = "${aGeneratorParam}"
It must the be curly braces that trigger macro replacement, $ alone is not enough.
Change By:
Timor Raiman
(03/Jul/13 8:22 AM)
Status:
Open
Resolved
Resolution:
CannotReproduce
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-18594) Generator parameters not replaced in Scriptler parameter value macro expressions
Timor Raiman
resolved JENKINS-18594 as Cannot Reproduce
Generator parameters not replaced in Scriptler parameter value macro expressions
Use curly braces to trigger macro replacement: ${aGeneratorParameter}
Change By:
Timor Raiman
(03/Jul/13 8:23 AM)
Status:
Open
Resolved
Resolution:
CannotReproduce
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Jan Krupka commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. indeed Our environment jenkins 1.521 Publish Over SSH 1.10 java version "1.6.0_27" OpenJDK Runtime Environment (IcedTea6 1.12.5) (6b27-1.12.5-0ubuntu0.12.04.1) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Ubuntu 12.04.2 LTS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18595) Uncaught TypeError when opening configuration of project (Jenkins 1.521)
C. S. created JENKINS-18595 Uncaught TypeError when opening configuration of project (Jenkins 1.521) Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: envinject Created: 03/Jul/13 8:48 AM Description: Getting the error "Uncaught TypeError: Property 'on' of object #HTMLFormElement is not a function" in textarea.js on line 18. If I disable the plugin the problem is gone. Environment: Jenkins 1.521 on Debian 7 x64 Project: Jenkins Priority: Blocker Reporter: C. S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [master-slave] (JENKINS-14304) StackOverflow on remote slave
evernat commented on JENKINS-14304 StackOverflow on remote slave Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-18596) PyLint log parsing fails
tiainpa created JENKINS-18596 PyLint log parsing fails Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 03/Jul/13 8:57 AM Description: We would like to use Warnings plug-in instead of Violations plug-in as Warnings show the fixed and new PyLint warnings better. I tried to use PyLint parser after running this command but it fails: pylint --rcfile=trunk/pylint/.pylintrc --output-format=parseable --reports=no --include-ids=yes `find . -name "*.py"` 21 pylint.log This is the error: WARNINGS Parsing warnings in files 'pylint.log' with parser PyLint ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception hudson.util.IOException2: remote file operation failed: /home/user/jenkins/workspace/pylint_app at hudson.remoting.Channel@1b0737a6:server at hudson.FilePath.act(FilePath.java:835) at hudson.FilePath.act(FilePath.java:821) at hudson.plugins.warnings.WarningsPublisher.parseFiles(WarningsPublisher.java:430) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:317) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:710) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:685) at hudson.model.Build$RunnerImpl.post2(Build.java:162) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:632) at hudson.model.Run.run(Run.java:1463) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@50fe3e37 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) at hudson.remoting.UserRequest.init(UserRequest.java:62) at hudson.remoting.Channel.call(Channel.java:662) at hudson.FilePath.act(FilePath.java:828) ... 13 more Caused by: java.io.NotSerializableException: hudson.plugins.violations.types.pylint.PyLintParser at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) at java.util.ArrayList.writeObject(ArrayList.java:710) at sun.reflect.GeneratedMethodAccessor217.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:975) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1480) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) at
[JIRA] [envinject] (JENKINS-18595) Uncaught TypeError when opening configuration of project (Jenkins 1.521)
Pete Tsamouris commented on JENKINS-18595 Uncaught TypeError when opening configuration of project (Jenkins 1.521) Had the same issue, upgraded from 1.520 to stop seeing the empty web pages on multiple configuration builds, and 1.521 could not even save configuration. Hangs and shows grey "Loading" window Ubuntu 12.04LTS x64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cvs] (JENKINS-18591) CVS-Plugin sporadically fails to connect via SSH
SCM/JIRA link daemon commented on JENKINS-18591 CVS-Plugin sporadically fails to connect via SSH Code changed in jenkins User: Michael Clarke Path: pom.xml http://jenkins-ci.org/commit/cvs-plugin/3ec70dd4f1a744a87c93f71d2a3588d7cc629c91 Log: Merge pull request #24 from svogt/JENKINS-18591 FIXED JENKINS-18591 - Update cvsclient to latest version Compare: https://github.com/jenkinsci/cvs-plugin/compare/839a9f84d88f...3ec70dd4f1a7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gui] (JENKINS-2494) Copied jobs should be disabled by default
SCM/JIRA link daemon commented on JENKINS-2494 Copied jobs should be disabled by default Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Job.java http://jenkins-ci.org/commit/jenkins/503c3bd2e6f2ec85514e16a260396ddae68f03ae Log: FIXES JENKINS-2494 Restore correct behaviour Fixes a regression in core where the display name clear on copy was triggering a save More than one way to do this, could also have used the marker interface approach This route seems slightly less fragile, though people could still add ItemListeners with order == -Double.MAX_VALUE which would then introduce intdeterminism. A marker interface would remove that indeterminism as the onCopyComplete method would be only called on the Job as the last method... but it could be hard to ensure that all ItemGroupMixin's respect the calling of onCopyComplete contract hence this approach seems better to me for that reason This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cvs] (JENKINS-18591) CVS-Plugin sporadically fails to connect via SSH
SCM/JIRA link daemon commented on JENKINS-18591 CVS-Plugin sporadically fails to connect via SSH Code changed in jenkins User: Sascha Vogt Path: pom.xml http://jenkins-ci.org/commit/cvs-plugin/b93ce65fb81ca5f19f6faab1689cb4695341d13a Log: FIXED JENKINS-18591 - Update cvsclient to latest version The new cvsclient lib should contain Jsch 1.50 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18597) provide the option to ignore system changes
Andreas Gundermann created JENKINS-18597 provide the option to ignore system changes Issue Type: New Feature Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 03/Jul/13 9:06 AM Description: The EnvInject Plugin needs to manipulate the config.xml of a Job during a build. "EnvInject plugin add technically this line and the line is removed after the run (it is a hack to achieve some plugin objectives)." (JENKINS-14144) Because of this changes scm-sync-configuration spams the repository. Maybe it is possible implement a switch for this plugin, to choose if you want to backup changes of "SYSTEM". Environment: jenkins 1.521 scm-sync-configuration 0.0.7.1 envinject 1.87 Project: Jenkins Priority: Major Reporter: Andreas Gundermann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-18596) PyLint log parsing fails
Ulli Hafner commented on JENKINS-18596 PyLint log parsing fails Actually, re-using the parsers from the violations plug-in does not work in slave builds. However, the parser has been already replaced with a new (native) parser. I still need some time to test all of the changes in the warnings plug-in before making a new 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] [warnings] (JENKINS-18596) PyLint log parsing fails
Ulli Hafner resolved JENKINS-18596 as Fixed PyLint log parsing fails Change By: Ulli Hafner (03/Jul/13 9:12 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] [github] (JENKINS-18598) Deploy created Artifact to Github as a Release
Alexander Bätz created JENKINS-18598 Deploy created Artifact to Github as a Release Issue Type: New Feature Assignee: Unassigned Components: github, plugin Created: 03/Jul/13 9:18 AM Description: Github just release their new release feature. it would be nice if the github plugin could create new tags and releases on demand and add proper binaries to the new release. https://github.com/blog/1547-release-your-software Project: Jenkins Priority: Major Reporter: Alexander Bätz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18597) provide the option to ignore system changes
Andreas Gundermann updated JENKINS-18597 provide the option to ignore system changes Change By: Andreas Gundermann (03/Jul/13 9:24 AM) Description: TheEnvInjectPluginneedstomanipulatetheconfig.xmlofaJobduringabuild.EnvInjectpluginaddtechnicallythislineandthelineisremovedaftertherun(itisahacktoachievesomepluginobjectives).(JENKINS-14144)Becauseofthischangesscm-sync-configurationspamstherepository.Maybeitis to possibleimplementaswitchforthisplugin,tochooseifyouwanttobackupchangesofSYSTEM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18589) Deadlock
teilo updated JENKINS-18589 Deadlock Change By: teilo (03/Jul/13 9:24 AM) Labels: lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18597) provide the option to ignore system changes
Andreas Gundermann updated JENKINS-18597 provide the option to ignore system changes Change By: Andreas Gundermann (03/Jul/13 9:25 AM) Description: TheEnvInjectPluginneedstomanipulatetheconfig.xmlofaJobduringabuild.EnvInjectpluginaddtechnicallythislineandthelineisremovedaftertherun(itisahacktoachievesomepluginobjectives).(JENKINS-14144)Becauseofthischangesscm-sync-configurationspamstherepository.Maybeitis to possible to implementaswitchforthisplugin,tochooseifyouwanttobackupchangesofSYSTEM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18597) provide the option to ignore system changes
Frédéric Camblor commented on JENKINS-18597 provide the option to ignore system changes I think ignoring whole system changes would be a bad thing, because it would imply undesirable behaviour to my POV (lots of commits are made by SYSTEM ... not keeping this changes would go against the backup feature of the plugin). But your use case is interesting though. Maybe could I track some "causes" for SYSTEM modification and allow to disable syncing on certain "causes" (one of the cause would be the hack by the EnvInject 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] [core] (JENKINS-18599) NullPointerException when launching builds on an ipad
Marc Seeger created JENKINS-18599 NullPointerException when launching builds on an ipad Issue Type: Bug Assignee: Unassigned Components: core Created: 03/Jul/13 9:27 AM Description: On of our developers tried to launch a build from an iPad and reproducibly ended up with this: Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:725) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:776) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:683) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:776) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:585) at org.kohsuke.stapler.Stapler.service(Stapler.java:216) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) 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
[JIRA] [core] (JENKINS-18599) NullPointerException when launching builds on an ipad
Marc Seeger
updated JENKINS-18599
NullPointerException when launching builds on an ipad
Change By:
Marc Seeger
(03/Jul/13 9:28 AM)
Description:
OnofourdeveloperstriedtolaunchabuildfromaniPadandreproduciblyendedupwiththis:{
code
quote
[JIRA] [gui] (JENKINS-1292) Keep this build forever should be available without purge turned on
Oliver Merkel commented on JENKINS-1292 Keep this build forever should be available without purge turned on Hi, If future decision is done to discard (e.g. to free blocked unnecessary resources) old builds indeed I would have expected that decision to "keep this build forever" is independend from setting "discard old builds". I encountered that use case as well. The work around described in description is unfortunately not acceptable in my case since behavior is unclear to end users. It is hard to make it pass quality gates in my scenario. Suggestion seems to be to have the "keep this build forever" available independly from discard settings. Additional suggestion is to have a hint included while displaying "keep this build forever" although discarding is completely turned off currently. Hint and marking the build is still valid then since current settings might change. Regards and all the best, Oliver This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sonar] (JENKINS-18600) Can't send new jobs to Sonar after Sonar upgrade: Not authorized
Rui Abreu created JENKINS-18600 Cant send new jobs to Sonar after Sonar upgrade: Not authorized Issue Type: Bug Affects Versions: current Assignee: Sonar Team Components: sonar Created: 03/Jul/13 9:55 AM Description: After upgrading the Sonar version to 3.5.1, news jobs that are created are unable to build due to: ERROR Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.0:sonar (default-cli) on project X: Can not execute Sonar: Not authorized. Please check the properties sonar.login and sonar.password. - The Jenkins jobs that existed prior to the upgrade, are working fine with Sonar. Project: Jenkins Priority: Major Reporter: Rui Abreu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18553) configuration is lost, and no new configuration possible
Skuli Arnlaugsson commented on JENKINS-18553 configuration is lost, and no new configuration possible I have the same result. Downgrading doesn't fix this. This plugin is vital to our process. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18553) configuration is lost, and no new configuration possible
Skuli Arnlaugsson edited a comment on JENKINS-18553 configuration is lost, and no new configuration possible I have the same result. Downgrading doesn't fix this. This plugin is vital to our process. The pipeline view appears like this now: http://www.webpagescreenshot.info/img/51d3f5a13d4a28-22873914 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sonar] (JENKINS-18600) Can't send new jobs to Sonar after Sonar upgrade: Not authorized
sbrandhof resolved JENKINS-18600 as Not A Defect Cant send new jobs to Sonar after Sonar upgrade: Not authorized It's the expected behavior. Please read http://docs.codehaus.org/display/SONAR/Release+3.4+Upgrade+Notes Change By: sbrandhof (03/Jul/13 10:04 AM) Status: Open Resolved Assignee: SonarTeam sbrandhof Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sonar] (JENKINS-18600) Can't send new jobs to Sonar after Sonar upgrade: Not authorized
sbrandhof closed JENKINS-18600 as Not A Defect Cant send new jobs to Sonar after Sonar upgrade: Not authorized Change By: sbrandhof (03/Jul/13 10:04 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18553) configuration is lost, and no new configuration possible
Torsten Zander commented on JENKINS-18553 configuration is lost, and no new configuration possible My screen looks exactly like yours and downgrading doesn't help either This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sonar] (JENKINS-18600) Can't send new jobs to Sonar after Sonar upgrade: Not authorized
Rui Abreu commented on JENKINS-18600 Cant send new jobs to Sonar after Sonar upgrade: Not authorized The username and password were already configured. The old jobs usem them successfull. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button
James Howe commented on JENKINS-18585 Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button Is there no testing done at all before a build is released? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [release] (JENKINS-10551) Check the parameter from upstream job to trigger a release build
wernight commented on JENKINS-10551 Check the parameter from upstream job to trigger a release build The main reason I'd use a release trigger is to have a release done when for example a change goes into a SCC branch or a Gerrit commit is merged into master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-18596) PyLint log parsing fails
tiainpa commented on JENKINS-18596 PyLint log parsing fails Thanks for the heads up! We'll wait for a new release of Warnings plug-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] [all-changes] (JENKINS-18601) Create view breaks during creation of new view
Wojciech Żarski created JENKINS-18601 Create view breaks during creation of new view Issue Type: Bug Affects Versions: current Assignee: wolfs Attachments: Error 400.png Components: all-changes Created: 03/Jul/13 11:16 AM Description: Create view breaks during creation of new view. Occurred after update to 1.521. Project: Jenkins Priority: Major Reporter: Wojciech Żarski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [www] (JENKINS-18601) Create view breaks during creation of new view
Wojciech Żarski updated JENKINS-18601 Create view breaks during creation of new view Change By: Wojciech Żarski (03/Jul/13 11:24 AM) Component/s: www Component/s: all-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] [createjobadvanced] (JENKINS-18602) Create Job Advanced plugin BUG
Potroshitel Jack created JENKINS-18602 Create Job Advanced plugin BUG Issue Type: Bug Assignee: bertrandgressier Attachments: Error.jpg Components: createjobadvanced, plugin Created: 03/Jul/13 11:27 AM Description: Hello, we are using the Advanced Job plugin to automatically grant our Project Managers (who are project creators with overall=Read, Job=Create) - permissions to jobs created by them. This is done by ticking the "Grant creator full control" checkbox. Now if we also check the 'Replace spaces in the job name with "-"' option in the Advanced Job plugin the following occurs: If the Project Creator creates a new job without spaces - he is granted permissions to the job. But if there are any spaces, they get replaced with "-" (and that's what we want) - but the creator is not granted any permissions to the new job. He receives the error in the attached image. Of course the issue if fixed if we grant in Jenkins Global Security job=read permissions - but this way the Project creator is able to see all of the projects (including the ones which he isn't responsible for). Due Date: 03/Jul/13 12:00 AM Environment: Windows 2008 R2 x64 Project: Jenkins Priority: Minor Reporter: Potroshitel Jack This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ws-cleanup] (JENKINS-18333) Cleanup plugin doesn't work with artifact deployer - the clean up order is wrong
vjuranek commented on JENKINS-18333 Cleanup plugin doesnt work with artifact deployer - the clean up order is wrong Hi, ws cleanup run after artifact deployer. The problem is, if I get it right, that ws clenaup is called for each matrix combination while artifact deployer is called only for matrix parent. As matrix aggregators are called after all sub-jobs are finished, workspace of sub-jobs are already removed so there's nothing to deploy. I can implement an option to skip cleanup on matrix sub-jobs but IMHO make more sense to run artifact deployer on each matrix sub-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] [artifactdeployer] (JENKINS-18333) Cleanup plugin doesn't work with artifact deployer - the clean up order is wrong
Thomas Fields updated JENKINS-18333 Cleanup plugin doesnt work with artifact deployer - the clean up order is wrong Change By: Thomas Fields (03/Jul/13 12:42 PM) Component/s: artifactdeployer Component/s: ws-cleanup This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18595) Uncaught TypeError when opening configuration of project (Jenkins 1.521)
Damien Coraboeuf commented on JENKINS-18595 Uncaught TypeError when opening configuration of project (Jenkins 1.521) Will it be fixed asap for the 1.522? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15814) Make it possible to define start and end of a day
Dirk Kuypers commented on JENKINS-15814 Make it possible to define start and end of a day Matthias is a student working for us and changed the plugin to enable time-shifting: https://github.com/jenkinsci/dashboard-view-plugin/pull/18 As we are no Java shop we are not sure about the code quality, so please review... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-16683) the Build Blocker Plugin is missing from Jira
Larry Shatzer, Jr. commented on JENKINS-16683 the Build Blocker Plugin is missing from Jira https://issues.jenkins-ci.org/browse/JENKINS/component/17470, it's just build-blocker. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15340) Add 'Are you sure' on Reload configuration from disk
Martin dAnjou commented on JENKINS-15340 Add Are you sure on Reload configuration from disk Asking "Are you sure" tells nothing to the user about the consequences. Instead, these kinds of confirmation boxes should tell the user what will happen and what to expect before asking the user if they are sure. Telling the use "it's expensive" is not informative either. Telling the use "you will lose all in-flight builds and all pending builds" is informative. I have "by accident" reloaded configuration from disk, and I would have liked to known the consequences (they were bad). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [config-rotator] (JENKINS-18603) View tag should use the remote computername as postfix (Praqma case 9695)
Mads Nielsen created JENKINS-18603 View tag should use the remote computername as postfix (Praqma case 9695) Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: config-rotator Created: 03/Jul/13 1:59 PM Description: View tag should use the remote computername as postfix Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-18605) Cannot get RemoteAgent's ClassID for test type PERFORMANCE-TEST
adarsh yajaman created JENKINS-18605 Cannot get RemoteAgents ClassID for test type PERFORMANCE-TEST Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 03/Jul/13 2:08 PM Description: Hi there, While executing test in jenkins (hp alm automation tool plugin) observing the below exception. Cannot get RemoteAgent's ClassID for test type PERFORMANCE-TEST Anyone facing similar issue? Thanks, Adarsh Due Date: 03/Jul/13 12:00 AM Project: Jenkins Priority: Major Reporter: adarsh yajaman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [favorite] (JENKINS-18604) Does not work with recursive views that include jobs within folders
SCM/JIRA link daemon commented on JENKINS-18604 Does not work with recursive views that include jobs within folders Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/plugins/favorite/filter/FavoriteFilter.java http://jenkins-ci.org/commit/favorite-plugin/6376257036aa2a863423680ff04ee9e142fc5748 Log: FIXED JENKINS-18604 Simpler to just add the ones that are favorite Simplifies the code and fixes the bug: double win!!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gui] (JENKINS-2494) Copied jobs should be disabled by default
stephenconnolly resolved JENKINS-2494 as Fixed Copied jobs should be disabled by default Change By: stephenconnolly (03/Jul/13 2:20 PM) Status: Reopened 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] [jira] (JENKINS-16683) the Build Blocker Plugin is missing from Jira
Ferenc Kovacs resolved JENKINS-16683 as Fixed the Build Blocker Plugin is missing from Jira Change By: Ferenc Kovacs (03/Jul/13 2:25 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] [msbuild] (JENKINS-18582) Handling of partially quoted arguments in MSBuild plugin broken
Dirk Kuypers commented on JENKINS-18582 Handling of partially quoted arguments in MSBuild plugin broken Hm, not sure if I followed the right workflow but I could not find a way to mark this as duplicated without resolving it. So if this was not right, have mercy with 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] [dimensionsscm] (JENKINS-18606) Serena dimensions plugin : Tagging a Successful build in Dimensions as a baseline FAILED
Gia bao NGUYEN updated JENKINS-18606 Serena dimensions plugin : Tagging a Successful build in Dimensions as a baseline FAILED Change By: Gia bao NGUYEN (03/Jul/13 2:32 PM) Description: WetrytointegrateDimensionpluginintoourbuildprocessusingTaggingaSuccessfulbuildinDimensionsfeaturewithoutsuccess.Thebuildpassedcorrectlythen failedat baseline tag taggin step failed :.FATAL:UnabletotagbuildinDimensions-Dimensioncommandfailed- (CBLSDO:F01_00_000_TESTTIP_ALL_SOCLE_V5/WORKSET=SDO:F01_00_000/SCOPE=PART/TEMPLATE_ID=CE_ENCIC98/PART=SDO:SDO.A;1/TYPE=BL_CIC/DESCRIPTION=BaselinecreatedbyHudson/JenkinsforjobSDO_100-build3) (BaselineSDO:F01_00_000_TESTTIP_ALL_SOCLE_V5hasbeenforwardedtoXPCM0005318EError:YouhavenotspecifiedanyRequestsorRequirementstoprocess)BuildstepTagsuccessfulbuildsinDimensionsasabaselinechangedbuildresulttoFAILUREBuildstepTagsuccessfulbuildsinDimensionsasabaselinemarkedbuildasfailure1)Anyonegotthisproblemyet?Whereistheproblem?2)Howcanbeovercomethisproblem?Finnally,Ithinktheoption/CHANGE_DOC_IDSofCBLcommandismissinginthisfeature(forexample:tagaDMbaselinefromasuccessfulbuildwithDM_REQUESTparameter)ManythanksGiabao This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15340) Add 'Are you sure' on Reload configuration from disk
Martin dAnjou edited a comment on JENKINS-15340 Add Are you sure on Reload configuration from disk Asking "Are you sure" tells nothing to the user about the consequences. Instead, these kinds of confirmation boxes should tell the user what will happen and what to expect before asking the user if they are sure. Telling the use "it's expensive" is not informative either. Telling the user "you will lose all in-flight builds and all pending builds" is informative. I have "by accident" reloaded configuration from disk, and I would have liked to know the consequences (they were bad). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvfb] (JENKINS-18607) Xvfb plugin doesn't work on matrix jobs with slaves on the same machine
taksan commented on JENKINS-18607 Xvfb plugin doesnt work on matrix jobs with slaves on the same machine Just to mention, Xvnc's plugin address this problem by trying to guess which displays are under use and try a different display number. Perhaps you could try a similar strategy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [xvfb] (JENKINS-18607) Xvfb plugin doesn't work on matrix jobs with slaves on the same machine
taksan created JENKINS-18607 Xvfb plugin doesnt work on matrix jobs with slaves on the same machine Issue Type: Bug Assignee: zregvart Components: xvfb Created: 03/Jul/13 2:51 PM Description: In our jenkins configuration we have several slaves on the same linux server and we have some jobs that run on these slaves. Because each slave has just a single executor, when we try to run the job with Xvfb plugin, all slaves try to run with the same display and therefore fail. Environment: linux Project: Jenkins Priority: Major Reporter: taksan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [role-strategy] (JENKINS-18377) Performance problem when listing many jobs
Walter Kacynski commented on JENKINS-18377 Performance problem when listing many jobs I am also experiencing this problem, but not with that many jobs. This started occurring after an upgrade from Jenkins 1.510 to 1.521 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit-trigger] (JENKINS-18391) Gerrit Version is null after upgrade to 2.10.1
Vadi Kumar commented on JENKINS-18391 Gerrit Version is null after upgrade to 2.10.1 I am having the same issue as teilo. I am using Gerrit 2.5 and tried with latest plugin and 2.0.9. I get the error Jul 03, 2013 1:21:41 AM com.sonyericsson.hudson.plugins.gerrit.gerritevents.GerritHandler shutdown INFO: Shutting down the ssh connection. Jul 03, 2013 1:21:41 AM com.sonyericsson.hudson.plugins.gerrit.gerritevents.GerritHandler run INFO: Starting Up... Jul 03, 2013 1:21:41 AM com.sonyericsson.hudson.plugins.gerrit.trigger.version.GerritVersionChecker createVersionNumber SEVERE: Gerrit version number is null or the empty string. Jul 03, 2013 1:21:41 AM com.sonyericsson.hudson.plugins.gerrit.gerritevents.GerritHandler run INFO: Ready to receive data from Gerrit However, ssh into jenkins user returns proper version string -bash-4.1$ ssh -p 29418 jenkins@10.10.0.65 gerrit version gerrit version 2.5 -bash-4.1$ Any help will be greatly appreciated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [msbuild] (JENKINS-18582) Handling of partially quoted arguments in MSBuild plugin broken
candritzky commented on JENKINS-18582 Handling of partially quoted arguments in MSBuild plugin broken @Dirk - I'm fine with marking this as resolved as long as it is tracked in a linked workitem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18608) When updating a plugin, check versions of dependencies
Kohsuke Kawaguchi created JENKINS-18608 When updating a plugin, check versions of dependencies Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: update-center Created: 03/Jul/13 3:38 PM Description: and update them as well if necessary. If optional dependencies are present and they need to be updated, too. Project: Jenkins Priority: Major Reporter: 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] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters
Shannon Kerr updated JENKINS-18534 Cannot add new build to queue from same project with different parameters Change By: Shannon Kerr (03/Jul/13 4:13 PM) Description: (ChangedtoBlockerasthisbugispreventingusfromrollingoutJenkinstoproductionrightnow,but I couldcompletelychangeourimplementationandreducethistoCriticalorMajorIsuppose,butthatwouldbequiteabitofwork)I startaparameterizedbuildfromprojectAviathebuildbutton.Asecondparameterizedbuildfromthesameprojectwasthenstartedviathebuildbutton,butwithdifferentparametervalues.Insteadofhavingtwojobsinthequeue,thesecondjobisnotaddedandinsteadtakesoverthefirstjobinthequeue.Ifthejobswerestartedbydifferentusers,bothusersnamesshowupastheStartedbyusers.Onlythesecondusersparametersareusedandretained.Thefirstusersjobisjustlost.Imgoingtoseeifthiseverworked,butImprettysureitdid.ImstillprettynewtoJenkins,butIthoughtIhadtestedthisoutbeforeandhadseentwoinstancesofthesamejobsittinginthequeue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18510) JavaScript Compiles script Tag Inline
Michael Chamberlain
commented on JENKINS-18510
_javascript_ Compiles script Tag Inline
We seem to have the exact same issue too..
This is after upgrading to 1.520 (still there after 1.521)
makeStaplerProxy('/$stapler/bound/2ed077d6-01d2-460d-ac3a-9f5edac59de3','4a71cfa0-f512-4721-9df0-11a6d592deb3',triggerManualBuild,retryBuild,rerunBuild), Handlebars.compile(buildCardTemplateSource), Handlebars.compile(projectCardTemplateSource), 0);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button
Vincent Latombe commented on JENKINS-18585 Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button Actually, the problem is not visible with a pure jenkins core, however it happens if you have plugins like EnvInject 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] [build-pipeline] (JENKINS-18510) JavaScript Compiles script Tag Inline
Michael Chamberlain
edited a comment on JENKINS-18510
_javascript_ Compiles script Tag Inline
We seem to have the exact same issue too.. (This seems to be a duplicate of: https://issues.jenkins-ci.org/browse/JENKINS-18553)
This is after upgrading to 1.520 (still there after 1.521)
makeStaplerProxy('/$stapler/bound/2ed077d6-01d2-460d-ac3a-9f5edac59de3','4a71cfa0-f512-4721-9df0-11a6d592deb3',triggerManualBuild,retryBuild,rerunBuild), Handlebars.compile(buildCardTemplateSource), Handlebars.compile(projectCardTemplateSource), 0);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18553) configuration is lost, and no new configuration possible
Michael Chamberlain commented on JENKINS-18553 configuration is lost, and no new configuration possible I think this is the same as: https://issues.jenkins-ci.org/browse/JENKINS-18510 ?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18078) groovy-html does not html encode lines from the build log
Josh Unger
commented on JENKINS-18078
groovy-html does not html encode lines from the build log
I did and it works. But, it is my understanding that you can configure a groovy script to automatically escape any dynamic _expression_ (${}). Can we do this instead so you escaping for free? I couldn't find a great example on how to do this but it appears the Play Framework does this with Groovy templates... middle of the page read this - http://www.playframework.com/documentation/1.2.4/templates.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-18078) groovy-html does not html encode lines from the build log
Alex Earl commented on JENKINS-18078 groovy-html does not html encode lines from the build log I think that's part of the playframework itself. Since many people use plain text emails, I don't want to do this for them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [security] (JENKINS-1684) 403 errors on project configuration with matrix-based security
Dmytro F commented on JENKINS-1684 403 errors on project configuration with matrix-based security I have similar problem on 1.520. "Build now" doesn't work. "Post-build" dropdown does nothing. In all these cases console shows "POST ... 403 Fobidden". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18078) groovy-html does not html encode lines from the build log
Josh Unger commented on JENKINS-18078 groovy-html does not html encode lines from the build log Good point about the plain text. So just update the sample HTML templates to include this line? I think the Jelly ones automatically escape? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18595) Uncaught TypeError when opening configuration of project (Jenkins 1.521)
Peter Loron commented on JENKINS-18595 Uncaught TypeError when opening configuration of project (Jenkins 1.521) Ugh. Running into this as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-1684) 403 errors on project configuration with matrix-based security
Dmytro F commented on JENKINS-1684 403 errors on project configuration with matrix-based security I have found "Prevent Cross Site Request Forgery exploits" was causing this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18609) Triggers two mails: UNSTABLE and REGRESSION
Stéphane Bruckert
created JENKINS-18609
Triggers two mails: UNSTABLE and REGRESSION
Issue Type:
Bug
Affects Versions:
current
Assignee:
Stéphane Bruckert
Attachments:
triggers.JPG
Components:
email-ext
Created:
03/Jul/13 5:01 PM
Description:
In my job configuration, I selected all triggers, because I want as much information as possible. But I received two emails for the same build. I guess this is not normal.
Build step 'Publish JUnit test result report' changed build result to UNSTABLE
Email was triggered for: Unstable
Email was triggered for: Regression
Sending email for trigger: Unstable
Sending email to: stephane.bruckert@
Sending email for trigger: Regression
Sending email to: stephane.bruckert@
Finished: UNSTABLE
REGRESSION has a reason to be triggered because new unit tests failed.
However, UNSTABLE shouldn't be triggered because REGRESSION should override it.
The problem looks to be in src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java. Contrary to NthFailureTrigger.java or StillUnstableTrigger.java, it doesn't call the method addTriggerNameToReplace in order to discard the previous triggers.
So, the descriptor of RegressionTrigger.java should have a constructor with the following content:
public DescriptorImpl() Unknown macro: {
addTriggerNameToReplace(UnstableTrigger.TRIGGER_NAME);
}
I am waiting for you to agree that this is a bug, before correcting it on the repository, if you agree.
Thank you very much!
Due Date:
04/Jul/13 12:00 AM
Environment:
Jenkins 1.513
Email-ext 2.28
Default email plugin E-mail Notification is NOT activated. This is a sure fact.
Fix Versions:
current
Project:
Jenkins
Labels:
plugin
Priority:
Major
Reporter:
Stéphane Bruckert
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-18609) Triggers two mails: UNSTABLE and REGRESSION
Stéphane Bruckert
updated JENKINS-18609
Triggers two mails: UNSTABLE and REGRESSION
Change By:
Stéphane Bruckert
(03/Jul/13 5:14 PM)
Description:
Inmyjobconfiguration,Iselectedalltriggers,becauseIwantasmuchinformationaspossible.ButIreceivedtwoemailsforthesamebuild.Iguessthisisnotnormal.{quote}BuildstepPublishJUnittestresultreportchangedbuildresulttoUNSTABLEEmailwastriggeredfor:UnstableEmailwastriggeredfor:RegressionSendingemailfortrigger:UnstableSendingemailto:stephane.bruckert@Sendingemailfortrigger:RegressionSendingemailto:stephane.bruckert@Finished:UNSTABLE{quote}REGRESSIONhasareasontobetriggeredbecausenewunittestsfailed.However,UNSTABLEshouldntbetriggeredbecauseREGRESSIONshouldoverrideit.Theproblemlookstobein{{src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java}}.Contraryto{{NthFailureTrigger.java}}or{{StillUnstableTrigger.java}},itdoesntcallthemethod{{addTriggerNameToReplace}}inordertodiscardtheprevioustriggers.So,thedescriptorof{{RegressionTrigger.java}}shouldhaveaconstructorwiththefollowingcontent:{
quote
code:title=RegressionTrigger.java|borderStyle=solid
}publicDescriptorImpl(){addTriggerNameToReplace(UnstableTrigger.TRIGGER_NAME);}{
quote
code
}Iamwaitingforyoutoagreethatthisisabug,beforecorrectingitontherepository,ifyouagree.Thankyouverymuch!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-18610) Multijob summary shows incorrectjobs build numbers
David Caro created JENKINS-18610 Multijob summary shows incorrectjobs build numbers Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 03/Jul/13 5:18 PM Description: When a multijob plugin launches subjobs, in the summary it shows the wrong build number for those jobs, it shows the current running build number, even if the job it launched is in the queue waiting for the current running job to finish. Also it does not update the buid number shown in the summary when it's build finishes. A working example: Jobs: Multijob1 , runs Job1 and Job2 in a phase with the option 'Mark phase as successful when jobs statuses are' set as successful Job1 (waits for 20 seconds and fails) Job2 (waits 90 seconds and fails) Launch Multijob, two times you will end up with: Multijob#1, with the following jobs on it's summary: Job1#1 Job2#1 Multijob#2, with the following jobs on it's summary: Job1#2 Job2#1 Job1#1 pointing to Multijob#1 Job1#2 poinitng to Multijob#2 Job2#1 pointing to Multijob#1 Job2#2 pointing to Multijob#2 Where the finishing order is: Job1#1 Multijob#1 Job1#2 Multijob#2 Job2#1 Job2#2 Environment: Jenkins 1.512 Multijob Plugin 1.9 Project: Jenkins Priority: Major Reporter: David Caro This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-18610) Multijob summary shows incorrect job build numbers
David Caro updated JENKINS-18610 Multijob summary shows incorrect job build numbers Change By: David Caro (03/Jul/13 5:18 PM) Summary: Multijobsummaryshows incorrectjobs incorrectjob buildnumbers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
Greg Hansen commented on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request Just tried this with a new installation of the latest version of Subversion server (1.8) on a freshly-installed machine running CentOS 6.3, and get the same error. We tried increasing the "KeepAlive" timeout from 15 seconds to 60 seconds, but still observed the 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] [subversion] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
Greg Hansen edited a comment on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request Just tried this with a new installation of the latest version of Subversion server (1.8) on a freshly-installed machine running CentOS 6.3, and get the same error. We tried increasing the "KeepAlive" timeout from 15 seconds to 60 seconds (restarted both httpd and jenkins), but still observed the 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] [jenkins-multijob-plugin] (JENKINS-18611) Sometimes multijob is set as succeeded without running any downstream jobs whe running in parallel
David Caro created JENKINS-18611 Sometimes multijob is set as succeeded without running any downstream jobs whe running in parallel Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 03/Jul/13 5:44 PM Description: When running several multijob build in parallel (for the same mtijob) it sometimes sets some of them as 'suceeded' without getting any result from downstream jobs, where is an example of the console output, I'll try to track down and I'll post everything I find out (if any): Started by user anonymous EnvInject - Loading node environment variables. Building on master in workspace /var/lib/jenkins/workspace/popopo@3 Run condition Always enabling prebuild for step MultiJob Phase Starting build job timeout_X. Starting build job timeout_20. Run condition Always enabling perform for step MultiJob Phase Notifying upstream projects of job completion Finished: SUCCESS As you can see, there's no return from the started builds. Environment: Jenkins 1.512 MultiJob 1.9 Project: Jenkins Priority: Critical Reporter: David Caro This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18078) groovy-html does not html encode lines from the build log
Alex Earl resolved JENKINS-18078 as Fixed groovy-html does not html encode lines from the build log Added call to StringEscapeUtils.escapeHtml to template. Change By: Alex Earl (03/Jul/13 5:49 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] [email-ext] (JENKINS-18609) Triggers two mails: UNSTABLE and REGRESSION
Stéphane Bruckert
updated JENKINS-18609
Triggers two mails: UNSTABLE and REGRESSION
Change By:
Stéphane Bruckert
(03/Jul/13 5:54 PM)
Description:
Inmyjobconfiguration,Iselectedalltriggers,becauseIwantasmuchinformationaspossible.ButIreceivedtwoemailsforthesamebuild.
Iguess
IMHO,
thisisnot
normal
theexpectedbehavior(oritisabug)becauseabuildwithREGRESSIONSindirectlymeansthatthebuildisUNSTABLE
.{quote}BuildstepPublishJUnittestresultreportchangedbuildresulttoUNSTABLEEmailwastriggeredfor:UnstableEmailwastriggeredfor:RegressionSendingemailfortrigger:UnstableSendingemailto:stephane.bruckert@Sendingemailfortrigger:RegressionSendingemailto:stephane.bruckert@Finished:UNSTABLE{quote}REGRESSIONhasareasontobetriggeredbecausenewunittestsfailed.However,UNSTABLEshouldntbetriggeredbecauseREGRESSIONshouldoverrideit.Theproblemlookstobein{{src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java}}.Contraryto{{NthFailureTrigger.java}}or{{StillUnstableTrigger.java}},itdoesntcallthemethod{{addTriggerNameToReplace}}inordertodiscardtheprevioustriggers.So,thedescriptorof{{RegressionTrigger.java}}shouldhaveaconstructorwiththefollowingcontent:{code:title=RegressionTrigger.java|borderStyle=solid}publicDescriptorImpl(){addTriggerNameToReplace(UnstableTrigger.TRIGGER_NAME);}{code}Iamwaitingforyoutoagreethatthisisabug,beforecorrectingitontherepository,ifyouagree.Thankyouverymuch!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [jclouds] (JENKINS-15929) Visiting Configure System page in Jenkins causes deadlock in JClouds plugin, freezing entire system
Adam Rofer commented on JENKINS-15929 Visiting Configure System page in Jenkins causes deadlock in JClouds plugin, freezing entire system We are using Oracle JDK 1.6.0_33 in this case, let me see if I can dig up the thread dump from before. I have since retried and reproduced the issue (a month ago), so if I cannot find the old dump I can easily reproduce it again. Reproduction of this issue is pretty simple. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18609) Triggers two mails: UNSTABLE and REGRESSION
Stéphane Bruckert
updated JENKINS-18609
Triggers two mails: UNSTABLE and REGRESSION
Change By:
Stéphane Bruckert
(03/Jul/13 5:56 PM)
Description:
Inmyjobconfiguration,Iselectedalltriggers,becauseIwantasmuchinformationaspossible
(seescreenshot)
.ButIreceivedtwoemailsforthesamebuild.IMHO,thisisnottheexpectedbehavior(oritisabug)becauseabuildwithREGRESSIONSinevitablymeansthatthebuildisUNSTABLE.{quote}BuildstepPublishJUnittestresultreportchangedbuildresulttoUNSTABLEEmailwastriggeredfor:UnstableEmailwastriggeredfor:RegressionSendingemailfortrigger:UnstableSendingemailto:stephane.bruckert@Sendingemailfortrigger:RegressionSendingemailto:stephane.bruckert@Finished:UNSTABLE{quote}REGRESSIONhasareasontobetriggeredbecausenewunittestsfailed.However,UNSTABLEshouldntbetriggeredbecauseREGRESSIONshouldoverrideit.Theproblemlookstobein{{src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java}}.Contraryto{{NthFailureTrigger.java}}or{{StillUnstableTrigger.java}},itdoesntcallthemethod{{addTriggerNameToReplace}}inordertodiscardtheprevioustriggers.So,thedescriptorof{{RegressionTrigger.java}}shouldhaveaconstructorwiththefollowingcontent:{code:title=RegressionTrigger.java|borderStyle=solid}publicDescriptorImpl(){addTriggerNameToReplace(UnstableTrigger.TRIGGER_NAME);}{code}Iamwaitingforyoutoagreethatthisisabug,beforecorrectingitontherepository,ifyouagree.Thankyouverymuch!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-18609) Triggers two mails: UNSTABLE and REGRESSION
Stéphane Bruckert
updated JENKINS-18609
Triggers two mails: UNSTABLE and REGRESSION
Change By:
Stéphane Bruckert
(03/Jul/13 5:55 PM)
Description:
Inmyjobconfiguration,Iselectedalltriggers,becauseIwantasmuchinformationaspossible.ButIreceivedtwoemailsforthesamebuild.IMHO,thisisnottheexpectedbehavior(oritisabug)becauseabuildwithREGRESSIONS
indirectly
inevitably
meansthatthebuildisUNSTABLE.{quote}BuildstepPublishJUnittestresultreportchangedbuildresulttoUNSTABLEEmailwastriggeredfor:UnstableEmailwastriggeredfor:RegressionSendingemailfortrigger:UnstableSendingemailto:stephane.bruckert@Sendingemailfortrigger:RegressionSendingemailto:stephane.bruckert@Finished:UNSTABLE{quote}REGRESSIONhasareasontobetriggeredbecausenewunittestsfailed.However,UNSTABLEshouldntbetriggeredbecauseREGRESSIONshouldoverrideit.Theproblemlookstobein{{src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java}}.Contraryto{{NthFailureTrigger.java}}or{{StillUnstableTrigger.java}},itdoesntcallthemethod{{addTriggerNameToReplace}}inordertodiscardtheprevioustriggers.So,thedescriptorof{{RegressionTrigger.java}}shouldhaveaconstructorwiththefollowingcontent:{code:title=RegressionTrigger.java|borderStyle=solid}publicDescriptorImpl(){addTriggerNameToReplace(UnstableTrigger.TRIGGER_NAME);}{code}Iamwaitingforyoutoagreethatthisisabug,beforecorrectingitontherepository,ifyouagree.Thankyouverymuch!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [jclouds] (JENKINS-15929) Visiting Configure System page in Jenkins causes deadlock in JClouds plugin, freezing entire system
Adam Rofer updated JENKINS-15929 Visiting Configure System page in Jenkins causes deadlock in JClouds plugin, freezing entire system Stack dumps from the time this issue was reproduced Change By: Adam Rofer (03/Jul/13 6:01 PM) Attachment: 2012-11-29jenkinsfrozestackdumps.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jclouds] (JENKINS-15929) Visiting Configure System page in Jenkins causes deadlock in JClouds plugin, freezing entire system
Adam Rofer reopened JENKINS-15929 Visiting Configure System page in Jenkins causes deadlock in JClouds plugin, freezing entire system Attached requested jstack output. Let me know if I need to reproduce it again (it has since been reproduced about 1-2 months ago on the latest Jenkins version available at that time) Change By: Adam Rofer (03/Jul/13 6:03 PM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds] (JENKINS-15929) Visiting Configure System page in Jenkins causes deadlock in JClouds plugin, freezing entire system
Adam Rofer edited a comment on JENKINS-15929 Visiting Configure System page in Jenkins causes deadlock in JClouds plugin, freezing entire system Stack dumps from the time this issue was reproduced (1.492 ~ Nov 29, 2012) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sonar] (JENKINS-18600) Can't send new jobs to Sonar after Sonar upgrade: Not authorized
sbrandhof commented on JENKINS-18600 Cant send new jobs to Sonar after Sonar upgrade: Not authorized You should request the user mailing-list: http://www.sonarqube.org/get-support/ 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] [build-pipeline] (JENKINS-18510) JavaScript Compiles script Tag Inline
Łukasz Jąder commented on JENKINS-18510 _javascript_ Compiles script Tag Inline It looks like fix for this issue is already in plugin repo https://github.com/jenkinsci/build-pipeline-plugin/commits/master - waiting for 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] [www] (JENKINS-13125) HTTP Content-Range Header one byte past file length
Christian Simon commented on JENKINS-13125 HTTP Content-Range Header one byte past file length I've got exactly the same PDF problem here on chrome 28.0 (linux x64) with jenkins 1.517 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15340) Add 'Are you sure' on Reload configuration from disk
Daniel Beck commented on JENKINS-15340 Add Are you sure on Reload configuration from disk Martin: Recent Jenkins versions (1.507+) are considered to no longer lose information on running builds when reloading, see JENKINS-3265. This warning (now) exists primarily to prevent accidental reloads that make the Jenkins UI unavailable for several minutes (especially with larger instances). I experienced some build data loss in combination with 'Cloudbees Restart Aborted Builds Plugin' (Jenkins Enterprise) but without that plugin, have repeatedly and successfully reloaded configuration from disk without losing in-progress build information. If you're on a recent Jenkins version and lost data, you should probably file a new issue and provide more information about your environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button
Łukasz Jąder commented on JENKINS-18585 Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button Quick and dirty fix before 1.522 release: 1. Extract textarea.js from jenkins.war/WEB-INF/lib/jenkins-core-1.521.jar/lib/form/textarea/ 2. Modify line 18 as in https://github.com/jenkinsci/jenkins/commit/0256f0a74e9b3373fa9fa14ba32bf9cb99dd5ec3 3. Place modified file textarea.js into war/WEB-INF/classes/lib/form/textarea/ 4. Restart jenkins service (optionally clearing browser cache for jenkins). Disclaimer: I'm not sure how this modified file will be handled on jenkins update. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18609) Triggers two mails: UNSTABLE and REGRESSION
Stéphane Bruckert
updated JENKINS-18609
Triggers two mails: UNSTABLE and REGRESSION
Change By:
Stéphane Bruckert
(03/Jul/13 7:11 PM)
Description:
Inmyjobconfiguration,Iselectedalltriggers,becauseIwantasmuchinformationaspossible(seescreenshot).ButIreceivedtwoemailsforthesamebuild.IMHO,thisisnottheexpectedbehavior(oritisabug)becauseabuildwithREGRESSIONSinevitablymeansthatthebuildisUNSTABLE.{quote}BuildstepPublishJUnittestresultreportchangedbuildresulttoUNSTABLEEmailwastriggeredfor:UnstableEmailwastriggeredfor:RegressionSendingemailfortrigger:UnstableSendingemailto:stephane.bruckert@Sendingemailfortrigger:RegressionSendingemailto:stephane.bruckert@Finished:UNSTABLE{quote}REGRESSIONhasareasontobetriggeredbecausenewunittestsfailed.However,UNSTABLEshouldntbetriggeredbecauseREGRESSIONshouldoverrideit.Theproblemlookstobein{{src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java}}.Contraryto{{NthFailureTrigger.java}}or{{StillUnstableTrigger.java}},itdoesntcallthemethod{{addTriggerNameToReplace}}inordertodiscardtheprevioustriggers.So,thedescriptorof{{RegressionTrigger.java}}shouldhaveaconstructorwiththefollowingcontent:{code:title=RegressionTrigger.java|borderStyle=solid}publicDescriptorImpl(){addTriggerNameToReplace(UnstableTrigger.TRIGGER_NAME);}{code}Iamwaitingforyoutoagreethatthisisabug,before
correcting
lettingmecorrect
itontherepository,ifyouagree.Thankyouverymuch!
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
pancake commented on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request Greg, it should be minutes or even tens of minutes (depends on WC size and hardware of the box that performs the checkout). Jenkins' KeepAlive has nothing to do with the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [translation] (JENKINS-18612) Confusing behavior for not logged users (403 Forbidden)
Adam Gabryś created JENKINS-18612 Confusing behavior for not logged users (403 Forbidden) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: translation Created: 03/Jul/13 7:59 PM Description: I set Discover right for the anonymous users. When a visitor goes to the login page, he will see the link "Help us localize this page" with a broken image (403 Forbidden). When he click ion the link, nothing happens (403 Forbidden for the file ...plugin/translation/dialog.js). It's a little confusing for the guests. Maybe better idea will be hide the link on the login page or move image and _javascript_ to readable location for the anonymous users? Environment: jenkins-1.521-1.1.noarch java-1.7.0-openjdk-1.7.0.25-2.3.10.4.el6_4.x86_64 Linux synthia.gabrys 2.6.32-358.11.1.el6.x86_64 #1 SMP Wed Jun 12 03:34:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Priority: Trivial Reporter: Adam Gabryś This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18589) Deadlock
dogfood commented on JENKINS-18589 Deadlock Integrated in jenkins_main_trunk #2687 Result = UNSTABLE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
