[JIRA] (JENKINS-12914) JDK Installer fails to download when using NTLM proxy with credentials
evernat resolved JENKINS-12914 as Incomplete JDK Installer fails to download when using NTLM proxy with credentials ok, I have resolved the issue as incomplete, as we both can not know if it is still an issue. Please reopen if the issue is reproduced. Change By: evernat (01/Mar/13 8:02 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-12937) Test harness fails from HEAD
evernat commented on JENKINS-12937 Test harness fails from HEAD As said by Andrew Melo: Sorry for the reply off-jenkins, I have no idea if it works now. ... Sorry! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17015) Test issue
Mads Nielsen created JENKINS-17015 Test issue Issue Type: Task Affects Versions: current Assignee: Praqma Support Components: rqm Created: 01/Mar/13 8:05 AM 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] (JENKINS-12937) Test harness fails from HEAD
evernat resolved JENKINS-12937 as Incomplete Test harness fails from HEAD Resolving as incomplete as the reporter can not test anymore. It may be fixed since a long time ago. Change By: evernat (01/Mar/13 8:07 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17009) Parameters with newlines are not applied correctly when triggering a rebuild
centic
updated JENKINS-17009
Parameters with newlines are not applied correctly when triggering a rebuild
Change By:
centic
(01/Mar/13 8:39 AM)
Description:
ForoneofmyJobsIneedmultiplelinesoftextinoneparameter,e.g.IntheparameterizedbuildtriggerpluginIspecifythisparameterwith\n:{quote}PROJECTPROPERTIES=sonar.projectKey=preismonitor-lokal\nsonar.projectName=preismonitor-lokal{quote}Thiscorrectlypassestheparameterwithnewlinecharacterstothesecondbuild.Inthebuild.xmlofthejenkins-build,thenewlinesarestorednormally{
quote
code:xml
}
hudson.model.StringParameterValue
namePROJECTPROPERTIES/name
valuesonar.projectKey=preismonitor-lokalsonar.projectName=preismonitor-lokal/value
/hudson.model.StringParameterValue
{
quote
code
}HoweverifIusetherebuild-plugintore-triggerthebuildlateron,itseemstocutoffthenewlinesandpassthestringinonesingleline,whichcausestherebuildtofail:{quote}...-Dsonar.projectKey=preismonitor-lokalsonar.projectName=preismonitor-lokal...{quote}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-13563) Attachment filepath does not support token reference
Pavel Kudrys commented on JENKINS-13563 Attachment filepath does not support token reference Hi, I'm sorry for bringing this subject back, but can I ask when we can see this feature back in a release version? Thank you in advance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16991) Access to some YUI resources lost after renaming my site
Mirko Friedenhagen commented on JENKINS-16991 Access to some YUI resources lost after renaming my site Hello Agustin, I am afraid this is more of a problem with your setup (Jenkins behind Apache). I can not really help you here and moving the issue to component core would probably not really help either so I would like to close the issue. I would suggest you tell about your setup and problems on the Jenkins-Userlist. At least you will get a lot more attention there and a lot more readers than on this ticket . Best Regards Mirko This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17016) Various Spanish translations have grammatical and orthographical errors
Galo Navarro
created JENKINS-17016
Various Spanish translations have grammatical and orthographical errors
Issue Type:
Bug
Affects Versions:
current
Assignee:
Galo Navarro
Components:
translation
Created:
01/Mar/13 9:24 AM
Description:
Intentaló de nuevo - should be "Inténtalo"
Error de autencicación - should be "autenticación"
Heche un vistazo a la información sobre la versión y la licencia - Should be "Eche".
El caracter ''~'' sólo está soportado en unix - should be "UNIX", acronym
Número erroneo de puerto - should be "erróneo"
Si tienes una cuenta de usuario y quieres asociar {0} con tu cuenta, este no es el sitio de hacerlo. - should be éste, pronoun.
Project:
Jenkins
Priority:
Trivial
Reporter:
Galo Navarro
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-16035) Publish Over SSH - With SFTP GET
Johannes Haseitl commented on JENKINS-16035 Publish Over SSH - With SFTP GET I'd very welcome that feature. I'd like to use that functionality to backup a database dump and pull it to the jenkins server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17016) Various Spanish translations have grammatical and orthographical errors
Galo Navarro started work on JENKINS-17016 Various Spanish translations have grammatical and orthographical errors Change By: Galo Navarro (01/Mar/13 9:37 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17016) Various Spanish translations have grammatical and orthographical errors
SCM/JIRA link daemon commented on JENKINS-17016 Various Spanish translations have grammatical and orthographical errors Code changed in jenkins User: Olivier Lamy Path: core/src/main/resources/hudson/Messages_es.properties core/src/main/resources/hudson/model/Messages_es.properties core/src/main/resources/hudson/security/FederatedLoginService/UnclaimedIdentityException/error_es.properties core/src/main/resources/jenkins/model/Jenkins/loginError_es.properties http://jenkins-ci.org/commit/jenkins/db230778203b350d7db14a4a0642b2096eac267a Log: Merge pull request #723 from srvaroa/master JENKINS-17016 Fix Spanish translations Thanks Compare: https://github.com/jenkinsci/jenkins/compare/36d7e31de6e2...db230778203b You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16361) @Grab Grape support
Daniel Spilker commented on JENKINS-16361 @Grab Grape support I did some investigation why this is not working. When using the @Grap annotation in a script the exception below is thrown. Adding the Ivy library to the plugin did not fix the problem. Each plugin is loaded with a separate classloader and the plugin classloaders are children of the Jenkins classloader. Since Groovy is provided by Jenkins, the Groovy classes are loaded by the Jenkins classloader. But the Ivy classes are not visible to the Jenkins classloader, they are only visible to the plugin classloader. So they can not be loaded when reference from Groovy classes which leads to the exception. There are at least two solutions for this problem: The Ivy library has to be included in Jenkins. The plugin has to bring its own Groovy library and some classloader magic has to be added so that the GroovyScriptEngine is loaded by the plugin classloader. FATAL: org/apache/ivy/core/report/ResolveReport java.lang.NoClassDefFoundError: org/apache/ivy/core/report/ResolveReport at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getDeclaredMethods(Class.java:1793) at org.codehaus.groovy.reflection.CachedClass$3$1.run(CachedClass.java:84) at java.security.AccessController.doPrivileged(Native Method) at org.codehaus.groovy.reflection.CachedClass$3.initValue(CachedClass.java:81) at org.codehaus.groovy.reflection.CachedClass$3.initValue(CachedClass.java:79) at org.codehaus.groovy.util.LazyReference.getLocked(LazyReference.java:46) at org.codehaus.groovy.util.LazyReference.get(LazyReference.java:33) at org.codehaus.groovy.reflection.CachedClass.getMethods(CachedClass.java:250) at groovy.lang.MetaClassImpl.populateMethods(MetaClassImpl.java:341) at groovy.lang.MetaClassImpl.fillMethodIndex(MetaClassImpl.java:291) at groovy.lang.MetaClassImpl.initialize(MetaClassImpl.java:2900) at org.codehaus.groovy.reflection.ClassInfo.getMetaClassUnderLock(ClassInfo.java:166) at org.codehaus.groovy.reflection.ClassInfo.getMetaClass(ClassInfo.java:182) at groovy.grape.GrapeIvy.$getStaticMetaClass(GrapeIvy.groovy) at groovy.grape.GrapeIvy.init(GrapeIvy.groovy:69) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:357) at java.lang.Class.newInstance(Class.java:310) at groovy.grape.Grape.getInstance(Grape.java:101) at groovy.grape.Grape.grab(Grape.java:136) at groovy.grape.GrabAnnotationTransformation.visit(GrabAnnotationTransformation.java:283) at org.codehaus.groovy.transform.ASTTransformationVisitor$3.call(ASTTransformationVisitor.java:302) at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:843) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:548) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:524) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:501) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:306) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:287) at groovy.util.GroovyScriptEngine$ScriptClassLoader.parseClass(GroovyScriptEngine.java:197) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:267) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:214) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:224) at javaposse.jobdsl.dsl.DslScriptLoader.runDslEngine(DslScriptLoader.java:75) at javaposse.jobdsl.plugin.ExecuteDslScripts.perform(ExecuteDslScripts.java:130) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473) at hudson.model.Run.run(Run.java:1410) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at
[JIRA] (JENKINS-8342) Excluded-regions doesn't work properly with multi commits
SCM/JIRA link daemon commented on JENKINS-8342 Excluded-regions doesnt work properly with multi commits Code changed in jenkins User: Nicolas De Loof Path: src/test/java/hudson/plugins/git/AbstractGitTestCase.java src/test/java/hudson/plugins/git/GitSCMTest.java http://jenkins-ci.org/commit/git-plugin/9625801c185976562467a016e9d6998227c08f41 Log: enable test for JENKINS-8342 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17017) Exception recovery fails
Axel Heider created JENKINS-17017 Exception recovery fails Issue Type: Bug Assignee: kutzi Components: instant-messaging, ircbot Created: 01/Mar/13 10:28 AM Description: I'm seeing the error below. Unfortunately, there is no recovery here, and the trhead is stuck. I have to restart jenkins to run anew try with changed IRC settings. hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run INFO: Trying to reconnect hudson.plugins.ircbot.v2.IRCConnection connect INFO: Connecting to :6667 as using charset UTF-8 Exception in thread "IM-Reconnector-Thread" java.lang.RuntimeException: Exception encountered when writng to socket at org.pircbotx.OutputThread.sendRawLineNow(OutputThread.java:71) at org.pircbotx.PircBotX.connect(PircBotX.java:340) at hudson.plugins.ircbot.v2.IRCConnection.connect(IRCConnection.java:118) at hudson.plugins.ircbot.v2.IRCConnectionProvider.createConnection(IRCConnectionProvider.java:37) at hudson.plugins.im.IMConnectionProvider.create(IMConnectionProvider.java:65) at hudson.plugins.im.IMConnectionProvider.access$600(IMConnectionProvider.java:22) at hudson.plugins.im.IMConnectionProvider$ConnectorRunnable.run(IMConnectionProvider.java:183) at java.lang.Thread.run(Thread.java:679) Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109) at java.net.SocketOutputStream.write(SocketOutputStream.java:153) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:220) at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:290) at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:294) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:140) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) at java.io.BufferedWriter.flush(BufferedWriter.java:253) at org.pircbotx.OutputThread.sendRawLineNow(OutputThread.java:67) ... 7 more Environment: Jenkins 1.501, IRC Plugin 2.21, IM PLugin 1.25 Project: Jenkins Priority: Blocker Reporter: Axel Heider This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17016) Various Spanish translations have grammatical and orthographical errors
dogfood commented on JENKINS-17016 Various Spanish translations have grammatical and orthographical errors Integrated in jenkins_main_trunk #2322 JENKINS-17016 Fix Spanish translations (Revision 73484301cec64ada1521d208d0a6e990746497e5) Result = SUCCESS anglorvaroa : 73484301cec64ada1521d208d0a6e990746497e5 Files : core/src/main/resources/jenkins/model/Jenkins/loginError_es.properties core/src/main/resources/hudson/model/Messages_es.properties core/src/main/resources/hudson/security/FederatedLoginService/UnclaimedIdentityException/error_es.properties core/src/main/resources/hudson/Messages_es.properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-7235) set log level for file hudson.err.log
Axel Heider commented on JENKINS-7235 set log level for file hudson.err.log Seem this has been getting much better in newe Jenkins versions. We are using 1.501 and then is only very few log data now. I suggest to close this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16936) Extension point for secure users of Api
Lance Wicks commented on JENKINS-16936 Extension point for secure users of Api Will this be implemented via the gui interface? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17003) JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect
Peter Lillevold
commented on JENKINS-17003
JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect
For those interested, here's a powershell snippet that will start/restart the Jenkins slave service in case of termination: (NOTE: replace the $jenkins variable with the name of your Windows service name)
$DebugPreference = 2
$VerbosePreference = 2
$WarningPreference = 2
$jenkins = "jenkinsslave-c__Jenkins"
$now = (Get-Date).ToString()
$jenkinsService = Get-Service | Where-Object {($_.Name -eq $jenkins) -and ($_.Status -eq [System.ServiceProcess.ServiceControllerStatus]::Stopped)}
if ($jenkinsService.count -eq 1)
{
Write-Warning ($now + " Jenkins slave not running. Starting...")
Start-Service $jenkins
}
else
{
$errorLog = (Get-Content C:\Jenkins\jenkins-slave.err.log)-1
if ($errorLog.ToLower().CompareTo("info: terminated") -eq 0)
{
Write-Warning ($now + " Jenkins was terminated. Restarting...")
Restart-Service $jenkins
}
else
{
Write-Verbose ($now + " Jenkins slave is live and kicking!")
}
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-13563) Attachment filepath does not support token reference
Alex Earl commented on JENKINS-13563 Attachment filepath does not support token reference I'm hoping to release this weekend, just running some more tests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16983) groovy script generates invalid HTML when there is an exception in maven build artifacts
SCM/JIRA link daemon commented on JENKINS-16983 groovy script generates invalid HTML when there is an exception in maven build artifacts Code changed in jenkins User: Alex Earl Path: src/main/resources/hudson/plugins/emailext/templates/groovy-html.template http://jenkins-ci.org/commit/email-ext-plugin/c58234af501263c25729de7d0c6c48a7f7fe9ae9 Log: FIX JENKINS-16983 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16983) groovy script generates invalid HTML when there is an exception in maven build artifacts
Alex Earl resolved JENKINS-16983 as Fixed groovy script generates invalid HTML when there is an exception in maven build artifacts Moved the try catch to finer granularity. Change By: Alex Earl (01/Mar/13 12:12 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] (JENKINS-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
jfigler commented on JENKINS-16474 Slow/hung web UI in 1.483+ (stuck in parseURI) Does anyone have any advice on how to reproduce this problem in 1.480.1? In large environments with a lot of real traffic, 1.480.1 appears to be experiencing this issue and becomes essentially unusable. However, in a smaller environment with much less traffic, I cannot get this defect to appear. What I'm trying to do is prove that a) this is the issue we are seeing and not something else, and b) that it is indeed gone in 1.480.3. I've tried Apache Benchmark with 20+ concurrency, and I've tried simulating traffic with 20+ tabs open with auto-refresh on... This upgrade is a little more risky since the whole 're-keying' process will take effect, so I want to make sure we won't have to rollback... again... Any advice would be greatly apprciated! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17018) keep build forever on a configuration in a matrix job is not kept forever
Chris Withers created JENKINS-17018 keep build forever on a configuration in a matrix job is not kept forever Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, matrix Created: 01/Mar/13 12:51 PM Description: Child builds that are marked as "keep forever" get deleted along with their parent build, if the parent build is not marked as "keep forever" and "Discard Old Builds" is enabled. Steps to reproduce: 1. Create a multi-configuration project 2. Enable "Discard old builds" and enter 3 for "Max # builds to keep". 3. Add a "User-defined Axis" called "test" with values "a b c". 4. Run the build. 5. Go to /job/job name/1/test=c 6. Click "keep this build forever" 7. Run the build a further 3 times. You'll now see that build #3, along with the 'c' configuration that was marked as "keep forever" have been deleted. Both the 'c' configuration and, I guess, it's parent build should not be deleted by the "discard old builds" process. Environment: Jenkins ver. 1.480.2 Project: Jenkins Priority: Major Reporter: Chris Withers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17019) Incompatible prqa plugin with older Jenkins version
Håkan Anderwall created JENKINS-17019 Incompatible prqa plugin with older Jenkins version Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: prqa Created: 01/Mar/13 12:59 PM Description: Incompatible prqa plugin with older Jenkins version core 1.424 LTS Due Date: 01/Mar/13 12:00 AM Project: Jenkins Priority: Major Reporter: Håkan Anderwall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17020) [Git plugin] Implement proper http authentication
Valentijn Scholten created JENKINS-17020 [Git plugin] Implement proper http authentication Issue Type: Improvement Assignee: Nicolas De Loof Components: git Created: 01/Mar/13 1:06 PM Description: Currently the credentials need to be provided in the repository url. This makes the credentials visible in the GUI and in de console output. The subversion plugin has a seperate username password field, I think we should implement this in the git plugin as well. Project: Jenkins Priority: Major Reporter: Valentijn Scholten This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16047) Scriptler plugin does not show Error/Exceptions anymore
SCM/JIRA link daemon commented on JENKINS-16047 Scriptler plugin does not show Error/Exceptions anymore Code changed in jenkins User: Nicolas De loof Path: src/main/java/org/jenkinsci/plugins/scriptler/util/GroovyScript.java http://jenkins-ci.org/commit/scriptler-plugin/a8455c136d7a9784124a27d0f877af960d0d54a0 Log: Merge pull request #11 from ndeloof/master fix JENKINS-16047 Compare: https://github.com/jenkinsci/scriptler-plugin/compare/fc9702bfdaea...a8455c136d7a You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16047) Scriptler plugin does not show Error/Exceptions anymore
SCM/JIRA link daemon commented on JENKINS-16047 Scriptler plugin does not show Error/Exceptions anymore Code changed in jenkins User: Nicolas De Loof Path: src/main/java/org/jenkinsci/plugins/scriptler/util/GroovyScript.java http://jenkins-ci.org/commit/scriptler-plugin/3db125c791e291c525c8362f44b6c1314a347fc7 Log: FIXED JENKINS-16047 Scriptler plugin does not show Error/Exceptions anymore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16047) Scriptler plugin does not show Error/Exceptions anymore
SCM/JIRA link daemon resolved JENKINS-16047 as Fixed Scriptler plugin does not show Error/Exceptions anymore Change By: SCM/JIRA link daemon (01/Mar/13 1:19 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] (JENKINS-5130) NPE during Surefire execution of a Maven project without any tests
kutzi resolved JENKINS-5130 as Cannot Reproduce NPE during Surefire execution of a Maven project without any tests No feedback from reporter = closing as not reproducable Change By: kutzi (01/Mar/13 1:28 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16361) @Grab Grape support
Daniel Spilker commented on JENKINS-16361 @Grab Grape support I tried to implement the two solutions I suggested above. Adding the Ivy library to jenkins.war works. The plugin does not need to be changed. Adding the Groovy library to the plugin does not work so well. Fortunately no classloader magic on the plugin side is required since Jenkins can hide classes from a plugin when the plugin specifies a "Mask-Classes" attribute in the manifest. I implemented that in a branch, see https://github.com/CoreMedia/job-dsl-plugin/commit/830fae7a0fd8a046c620600e46633166804190e3. Script execution with @Grab works. Unfortunately this needs some workaround in the gradle build and currently breaks "gradlew server". The server does not start because it can not find the Groovy classes. It also breaks rendering the GeneratedJobsBuildAction with a java.lang.VerifyError when deploying to a running instance of Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17021) Latest plugin version crashes with NPE
jsotuyod created JENKINS-17021 Latest plugin version crashes with NPE Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: findbugs Created: 01/Mar/13 1:39 PM Description: Evver since upgrading the plugin to the latest version, all my projects (all using Jenkin's built-in Maven2 builder, haven't tried with other types of projects) fail with the following stacktrace. JENKINS Archiving redacted INFO ERROR FATAL ERROR INFO INFO null INFO INFO Trace java.lang.NullPointerException at java.util.regex.Matcher.getTextLength(Matcher.java:1140) at java.util.regex.Matcher.reset(Matcher.java:291) at java.util.regex.Matcher.init(Matcher.java:211) at java.util.regex.Pattern.matcher(Pattern.java:888) at hudson.FilePath.normalize(FilePath.java:248) at hudson.FilePath.init(FilePath.java:194) at hudson.plugins.findbugs.FindBugsReporter.getOutputPath(FindBugsReporter.java:180) at hudson.plugins.findbugs.FindBugsReporter.perform(FindBugsReporter.java:175) at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:313) at hudson.maven.Maven2Builder.postExecute(Maven2Builder.java:155) at hudson.maven.MavenBuilder$Adapter.postExecute(MavenBuilder.java:310) at hudson.maven.agent.PluginManagerInterceptor$1MojoIntercepterImpl.callPost(PluginManagerInterceptor.java:170) at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:183) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:151) at hudson.maven.Maven2Builder.call(Maven2Builder.java:77) at hudson.maven.Maven2Builder.call(Maven2Builder.java:53) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at
[JIRA] (JENKINS-17019) Incompatible prqa plugin with older Jenkins version (our case 8751)
Jens Brejner updated JENKINS-17019 Incompatible prqa plugin with older Jenkins version (our case 8751) pseudo-linking to internal tracker Change By: Jens Brejner (01/Mar/13 2:11 PM) Summary: IncompatibleprqapluginwitholderJenkinsversion (ourcase8751) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16109) Slave hung archiving artifacts
Jakob Malm commented on JENKINS-16109 Slave hung archiving artifacts We are seeing this too. Only happens intermittently, and only when archiving artifacts from linux jenkins slave over ssh. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17011) More convenient job selection control
Jesse Glick commented on JENKINS-17011 More convenient job selection control Should also consider whether identifying items by relative path was a good idea to begin with. It is not always easy or even possible to evaluate a relative path when the value is needed. During form validation you can usually use hacks like @AncestorInPath to guess at the context, though not always; and there is no equivalent magic thread-local variable (that I know of) available during deserialization (Converter.unmarshal). And what was the purpose? Depending on the UI control chosen, it is not necessarily more convenient for users. It is not necessary in order to order to maintain relationships between jobs in folders created from template, since you could simply ensure that the target folder path is a variable available during template expansion. It could be used to ensure that sets of related jobs behave the same way when moved or copied to another folder, but renaming jobs—and moving only dependent jobs to other folders—anyway requires that you search for and update item name references, whether they are relative or absolute. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17015) Test issue
Lars Kruse resolved JENKINS-17015 as Wont Fix Test issue Just testing the RQM Jira component Change By: Lars Kruse (01/Mar/13 2:44 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17015) Test issue
Lars Kruse closed JENKINS-17015 as Wont Fix Test issue Change By: Lars Kruse (01/Mar/13 2:44 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17022) XML-Tag attachBuildLog ist not written to config.xml
Klaus Weyers created JENKINS-17022 XML-Tag attachBuildLog ist not written to config.xml Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: mailconfig.jpg Components: plugin Created: 01/Mar/13 3:23 PM Description: for E-Mail notification one can choose "Attach Build Log" at the extended options, when a Trigger (e.g. "failure") is added. The option is not correctly stored in the config.xml for the job. The XML-Tag attachBuildLog always says "false". On editing this manually, the value is correctly displayed in the job-page. But every time I save the configuration the value is resetted. relevant Config-page for job see attatched screenshot. Environment: Windows-XP, Jenkins 1.502, Plugin email-ext 2.25 Project: Jenkins Priority: Major Reporter: Klaus Weyers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17009) Parameters with newlines should be stored as TextParameterValue
centic assigned JENKINS-17009 to huybrechts Parameters with newlines should be stored as TextParameterValue Change By: centic (01/Mar/13 3:30 PM) Assignee: ragesh_nair huybrechts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17009) Parameters with newlines should be stored as TextParameterValue
centic
updated JENKINS-17009
Parameters with newlines should be stored as TextParameterValue
Change By:
centic
(01/Mar/13 3:30 PM)
Summary:
Parameterswithnewlines
arenotappliedcorrectlywhentriggeringarebuild
shouldbestoredasTextParameterValue
Description:
ForoneofmyJobsIneedmultiplelinesoftextinoneparameter,e.g.IntheparameterizedbuildtriggerpluginIspecifythisparameterwith\n:{quote}PROJECTPROPERTIES=sonar.projectKey=preismonitor-lokal\nsonar.projectName=preismonitor-lokal{quote}
This
The\n
correctlypassestheparameterwithnewlinecharactersto
thesecondbuild
anupcomingbiuld
.Inthebuild.xmlofthejenkins-build,thenewlinesarestorednormally
,howeverthereareproblemslateronifotherpluginsworkwiththisdatabecausetheparameter-typeisStringParameterValueinsteadofTextParameterValue:
{code:xml}hudson.model.StringParameterValuenamePROJECTPROPERTIES/namevaluesonar.projectKey=preismonitor-lokalsonar.projectName=preismonitor-lokal/value/hudson.model.StringParameterValue{code}
However
E.g.
ifIusetherebuild-plugintore-triggerthebuildlateron,itseemstocutoffthenewlinesandpassthestringinonesingleline,whichcausestherebuildtofail:{quote}...-Dsonar.projectKey=preismonitor-lokalsonar.projectName=preismonitor-lokal...{quote}
IwillattachapatchwhichcreatesaTextParameterValueifthevaluecontainsnewlines.Thismakesthisworkinallcases.
Component/s:
parameterized-trigger
Component/s:
rebuild
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-17023) Jenkins Testlink plugin Found 0 test result is show while test is runned
Abdallah Saidane created JENKINS-17023 Jenkins Testlink plugin Found 0 test result is show while test is runned Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Attachments: config.xml, configuration.jpg, pom.xml, test_result.PNG Components: testlink Created: 01/Mar/13 3:31 PM Description: Problem is that automated test is run but not test result is shown on Jenkins plz see"test_result.PNG" same behavior is observed on windows environment and Lunix Ubunu environment Console Output Result : View as plain text Edit Build Information Delete Build TestLink Previous Build SuccessConsole Output Started by user anonymous Building in workspace /var/lib/jenkins/jobs/Jenkins testlink plugin examples/workspace Preparing TestLink client API. Using TestLink URL: http://tlink.tunprojects.com/lib/api/xmlrpc.php Found 0 automated test cases in TestLink. Sorting automated test cases by TestLink test plan execution order. Executing single Build Steps. workspace $ /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven/bin/mvn test -DsuiteXmlFiles=suite.xml INFO Scanning for projects... INFO INFO INFO Building Jenkins TestLink Plug-in Tutorial 0.3-SNAPSHOT INFO INFO INFO docbkx-maven-plugin:2.0.11:generate-pdf (book-output) @ jenkins-testlink-plugin-tutorial INFO /var/lib/jenkins/jobs/Jenkins testlink plugin examples/workspace/target/book/en/book.fo is up to date. INFO Executing tasks INFO Executed tasks INFO INFO docbkx-maven-plugin:2.0.11:generate-html (book-output) @ jenkins-testlink-plugin-tutorial INFO /var/lib/jenkins/jobs/Jenkins testlink plugin examples/workspace/target/book/en/book.html is up to date. INFO Executing tasks INFO Executed tasks INFO INFO docbkx-maven-plugin:2.0.11:generate-eclipse (book-output) @ jenkins-testlink-plugin-tutorial INFO /var/lib/jenkins/jobs/Jenkins testlink plugin examples/workspace/target/book/en/book.eclipse is up to date. INFO Executing tasks INFO Executed tasks INFO INFO maven-resources-plugin:2.5:resources (default-resources) @ jenkins-testlink-plugin-tutorial debug execute contextualize INFO Using 'UTF-8' encoding to copy filtered resources. INFO skip non existing resourceDirectory /var/lib/jenkins/jobs/Jenkins testlink plugin examples/workspace/src/main/resources INFO INFO maven-compiler-plugin:2.3.2:compile (default-compile) @ jenkins-testlink-plugin-tutorial INFO No sources to compile INFO INFO maven-resources-plugin:2.5:testResources (default-testResources) @ jenkins-testlink-plugin-tutorial debug execute contextualize INFO Using 'UTF-8' encoding to copy filtered resources. INFO Copying 1 resource INFO INFO maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jenkins-testlink-plugin-tutorial INFO Nothing to compile - all classes are up to date INFO INFO maven-surefire-plugin:2.10:test (default-test) @ jenkins-testlink-plugin-tutorial INFO Surefire report directory: /var/lib/jenkins/jobs/Jenkins testlink plugin examples/workspace/target/surefire-reports --- T E S T S --- Running jenkins.plugins.testlink.examples.TestCurrentTime Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.285 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 INFO INFO BUILD SUCCESS INFO INFO Total time: 1.644s INFO Finished at: Fri Mar 01 13:02:12 CET 2013 INFO Final Memory: 7M/16M INFO Executing
[JIRA] (JENKINS-17009) Parameters with newlines should be stored as TextParameterValue
centic
updated JENKINS-17009
Parameters with newlines should be stored as TextParameterValue
Change By:
centic
(01/Mar/13 3:31 PM)
Description:
ForoneofmyJobsIneedmultiplelinesoftextinoneparameter,e.g.IntheparameterizedbuildtriggerpluginIspecifythisparameterwith\n:{quote}PROJECTPROPERTIES=sonar.projectKey=preismonitor-lokal\nsonar.projectName=preismonitor-lokal{quote}The\ncorrectlypassestheparameterwithnewlinecharacterstoanupcomingbiuld.Inthebuild.xmlofthejenkins-build,thenewlinesarestorednormally,howeverthereareproblemslateronifotherpluginsworkwiththisdatabecausetheparameter-typeisStringParameterValueinsteadofTextParameterValue:{code:xml}hudson.model.StringParameterValuenamePROJECTPROPERTIES/namevaluesonar.projectKey=preismonitor-lokalsonar.projectName=preismonitor-lokal/value/hudson.model.StringParameterValue{code}E.g.ifIusetherebuild-plugintore-triggerthebuildlateron,itseemstocutoffthenewlinesandpassthestringinonesingleline,whichcausestherebuildtofail:{quote}...-Dsonar.projectKey=preismonitor-lokalsonar.projectName=preismonitor-lokal...{quote}
Iwillattacha
Thefollowing
patch
which
createsaTextParameterValueifthevaluecontainsnewlines.Thismakesthiswork
inallcases
locallyforme:{code}diff--gita/src/main/java/hudson/plugins/parameterizedtrigger/PredefinedBuildParameters
.
javab/src/main/java/hudson/plugins/parameterizedtrigger/PredefinedBuildParameters.javaindexb1cbc73..26f2e50100644---a/src/main/java/hudson/plugins/parameterizedtrigger/PredefinedBuildParameters.java+++b/src/main/java/hudson/plugins/parameterizedtrigger/PredefinedBuildParameters.java@@-2,13+2,14@@importhudson.EnvVars;importhudson.Extension;-importhudson.model.AbstractBuild;importhudson.model.Action;-importhudson.model.Descriptor;importhudson.model.ParameterValue;+importhudson.model.TaskListener;+importhudson.model.AbstractBuild;+importhudson.model.Descriptor;importhudson.model.ParametersAction;importhudson.model.StringParameterValue;-importhudson.model.TaskListener;+importhudson.model.TextParameterValue;importjava.io.IOException;importjava.util.ArrayList;@@-38,8+39,14@@ ListParameterValuevalues=newArrayListParameterValue(); for(Map.EntryObject,Objectentry:p.entrySet()){- values.add(newStringParameterValue(entry.getKey().toString(),- env.expand(entry.getValue().toString(;+ //supportmulti-lineparameterscorrectly+ if(entry.getValue().toString().contains(\n)){+values.add(newTextParameterValue(entry.getKey().toString(),+ env.expand(entry.getValue().toString(;+ }else{+values.add(newStringParameterValue(entry.getKey().toString(),+ env.expand(entry.getValue().toString(;+ } } returnnewParametersAction(values);{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-13055) checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed
kutzi assigned JENKINS-13055 to kutzi checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed Change By: kutzi (01/Mar/13 3:41 PM) Assignee: kutzi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16661) Rebuild plugin crashes when used in conjuction with Random String Parameter Plugin
centic updated JENKINS-16661 Rebuild plugin crashes when used in conjuction with Random String Parameter Plugin Change By: centic (01/Mar/13 3:48 PM) Description: Runningaparameterizedbuildcontaininga [ RandomStringParameter |https://wiki.jenkins-ci.org/display/JENKINS/Random+String+Parameter+Plugin] andhittingrebuild-actionitfailswithanexception:StatusCode:500Exception:org.apache.commons.jelly.JellyTagException:file:/D:/Jenkins/plugins/rebuild/WEB-INF/classes/com/sonyericsson/rebuild/RebuildAction/parameterized.jelly:55:75:st:includeNopagefoundRandomStringParameterValue.jellyforclasscom.sonyericsson.rebuild.RebuildActionStacktrace:javax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:file:/D:/Jenkins/plugins/rebuild/WEB-INF/classes/com/sonyericsson/rebuild/RebuildAction/parameterized.jelly:55:75:st:includeNopagefoundRandomStringParameterValue.jellyforclasscom.sonyericsson.rebuild.RebuildAction atorg.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:658)... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17005) hudson.model.Api.INSECURE as checkbox setting
Lance Wicks closed JENKINS-17005 as Wont Fix hudson.model.Api.INSECURE as checkbox setting Change By: Lance Wicks (01/Mar/13 4:17 PM) Status: Resolved Closed Assignee: LanceWicks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17024) The SLOCCOUNT analysis Results not available in IVY builds
Grace Gorman created JENKINS-17024 The SLOCCOUNT analysis Results not available in IVY builds Issue Type: Bug Affects Versions: current Assignee: npiguet Components: sloccount Created: 01/Mar/13 4:59 PM Description: The SLOCCOUNT analysis Results option does not appear on builds using the IVY plugin. It does appear on all the other builds. Is it compatible with IVY? Due Date: 22/Mar/13 12:00 AM Environment: Windows 2008 Fix Versions: current Project: Jenkins Priority: Minor Reporter: Grace Gorman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17025) Regression in 1.503: NPE when checking if the executor is interrupted
Joel Johnson created JENKINS-17025 Regression in 1.503: NPE when checking if the executor is interrupted Issue Type: Bug Affects Versions: current Assignee: Joel Johnson Components: core Created: 01/Mar/13 5:55 PM Description: Revision 2942601 introduced an NPE. If a build's project implements Queue.FlyweightTask, build.getExecutor() returns null. This prevents any flyweight build from finishing successfully. This is a blocker because it has completely broken several jobs in our workflow, and we are forced to either downgrade or change the project type until a fix is made. There is no other workaround currently for this. Environment: Ubuntu Server Tomcat 7 Jenkins 1.503 Project: Jenkins Labels: jenkins exception build regression flyweight Priority: Blocker Reporter: Joel Johnson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17025) Regression in 1.503: NPE when checking if the executor is interrupted
Joel Johnson commented on JENKINS-17025 Regression in 1.503: NPE when checking if the executor is interrupted Pull Request fixes this bug: https://github.com/jenkinsci/jenkins/pull/724 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16661) Rebuild plugin crashes when used in conjuction with Random String Parameter Plugin
centic updated JENKINS-16661 Rebuild plugin crashes when used in conjuction with Random String Parameter Plugin This file put into src/main/resources/com/sonyericsson/rebuild/RebuildAction/ will make the rebuild plugin handle RandomStringParameterValue during a rebuild. In fact it's a simple copy of the StringParameterValue.jelly file. Currently it will re-use the previous random value when triggering a rebuild, it might make more sense to re-create a fresh random value here, but I am not sure... Change By: centic (01/Mar/13 6:13 PM) Attachment: RandomStringParameterValue.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17026) Build graph sometimes truncates missed line
Marcel L created JENKINS-17026 Build graph sometimes truncates missed line Issue Type: Bug Assignee: Ognjen Bubalo Attachments: graph.png, graph2.png Components: jacoco Created: 01/Mar/13 6:26 PM Description: The graph of missed and covered lines sometimes truncates the missed line. See examples attached. Project: Jenkins Priority: Major Reporter: Marcel L This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17027) Ratio red/green bar wrong
Marcel L created JENKINS-17027 Ratio red/green bar wrong Issue Type: Bug Assignee: Ognjen Bubalo Attachments: bug2.png Components: jacoco Created: 01/Mar/13 6:46 PM Description: The ratio M:C view on the red / green bar is wrong sometimes. Please check the calculation. See example attached Project: Jenkins Priority: Major Reporter: Marcel L This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick resolved JENKINS-16332 as Cannot Reproduce Leading and trailing underscores are added to commiters email address, unable to send build notification Still cannot reproduce. Using 1.505-SNAPSHOT (Mailer Plugin 1.4 was bundled) and dev version of Mercurial plugin, created a Maven job based on a new Hg repo created from a quickstart archetype, built it. Committed a test failure where my ~/.hgrc has [ui] username = Jesse Glick jgl...@netbeans.org and checked changelog. http://localhost:8080/user/Jesse%20Glick%20_jglick@netbeans.org_/configure now has Your name set to Jesse Glick jgl...@netbeans.org and E-mail address set to jgl...@netbeans.org, as expected. (Again it is normal for http://localhost:8080/user/Jesse%20Glick%20_jglick@netbeans.org_/ to show Jesse Glick jgl...@netbeans.org as the display name followed by Jenkins User Id: Jesse Glick jgl...@netbeans.org since IDs are always escaped to not contain dangerous characters such as , but this should not affect mail delivery or other functions since the email address is stored as a user property.) Also installed email-ext plugin, added an Unstable trigger to send to committers, committed another test failure and built again. Log showed Sending email to: jgl...@netbeans.org as expected (I did not configure SMTP so did not check that it really sent mail). If you can still reproduce an issue with the latest versions of the Mercurial plugin, Jenkins core, and the Mailer plugin (now responsible for email address maintenance in a User), feel free to debug and file a pull request with a fix. Change By: Jesse Glick (01/Mar/13 6:45 PM) Status: Reopened 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] (JENKINS-16474) Slow/hung web UI in 1.483+ (stuck in parseURI)
Jesse Glick commented on JENKINS-16474 Slow/hung web UI in 1.483+ (stuck in parseURI) I am afraid I was never able to reproduce the problem in a test environment; the fix is based on a combination of speculation, and feedback from some people I know to have encountered matching symptoms. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16936) Extension point for secure users of Api
Jesse Glick commented on JENKINS-16936 Extension point for secure users of Api It would be up to the plugin implementing the extension point whether to offer a UI interface for customizing its behavior, and if so, what the customizations would consist of. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-8971) Keep only last promoted build forever
Jose Sa commented on JENKINS-8971 Keep only last promoted build forever It would be interesting indeed that the builds "kept" had some configurations for automatic cleanup, like keeping only the last X number of builds of a given promotion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17025) Regression in 1.503: NPE when checking if the executor is interrupted
SCM/JIRA link daemon commented on JENKINS-17025 Regression in 1.503: NPE when checking if the executor is interrupted Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Build.java http://jenkins-ci.org/commit/jenkins/92fa6e57b73d27d9e7a4254c45cdc7538d1daa3d Log: Merge pull request #724 from JoelJ/patch-1 FIXED JENKINS-17025 NPE when checking if the executor is interrupted Compare: https://github.com/jenkinsci/jenkins/compare/db230778203b...92fa6e57b73d You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17025) Regression in 1.503: NPE when checking if the executor is interrupted
SCM/JIRA link daemon resolved JENKINS-17025 as Fixed Regression in 1.503: NPE when checking if the executor is interrupted Change By: SCM/JIRA link daemon (01/Mar/13 7:10 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] (JENKINS-17025) Regression in 1.503: NPE when checking if the executor is interrupted
SCM/JIRA link daemon commented on JENKINS-17025 Regression in 1.503: NPE when checking if the executor is interrupted Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/fa50b3d7e6e2a361884cb432fbf101171ebe6c01 Log: JENKINS-17025 Noting. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15882) rebuild plugin should not store non-stored password parameter
centic commented on JENKINS-15882 rebuild plugin should not store non-stored password parameter How are you triggering the job and how is the password provided? Are you manually providing the password when starting the 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] (JENKINS-17028) Build status icons don't refresh due to Cache-Control setting in HTTP response
garethbowles created JENKINS-17028 Build status icons dont refresh due to Cache-Control setting in HTTP response Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: embeddable-build-status Created: 01/Mar/13 8:04 PM Description: For our Netflix OSS projects, build status icons don't update in our GitHub pages unless we clear the browser cache. An example is at https://github.com/Netflix/RxJava I investigated with Michael Neale and we found that the HTTP response includes "Cache-Control:public", which is likely causing the problem. Michael verified that this problem doesn't happen with build status icons from BuildHive, because the HTTP rsponses from BuildHive don't include the Cache-Control setting. I looked at the plugin code to see if this was an easy fix, but it looks like the HTTP response is generated somewhere in the Stapler code, which I didn't want to mess with Environment: Plugin version 1.0 in Dev@Cloud - netflixoss.ci.cloudbees.com Project: Jenkins Priority: Major Reporter: garethbowles This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17025) Regression in 1.503: NPE when checking if the executor is interrupted
dogfood commented on JENKINS-17025 Regression in 1.503: NPE when checking if the executor is interrupted Integrated in jenkins_main_trunk #2323 JENKINS-17025 Noting. (Revision fa50b3d7e6e2a361884cb432fbf101171ebe6c01) Result = SUCCESS Jesse Glick : fa50b3d7e6e2a361884cb432fbf101171ebe6c01 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13055) checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed
kutzi commented on JENKINS-13055 checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed Ramesh: do you also get the error with newer versions? AFAI can see this should have been fixed in 1.43+ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-13055) checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed
kutzi updated JENKINS-13055 checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed Change By: kutzi (01/Mar/13 8:30 PM) Due Date: 20 1 / Mar Apr / 12 13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17017) Exception recovery fails
SCM/JIRA link daemon resolved JENKINS-17017 as Fixed Exception recovery fails Change By: SCM/JIRA link daemon (01/Mar/13 8:50 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] (JENKINS-17017) Exception recovery fails
SCM/JIRA link daemon commented on JENKINS-17017 Exception recovery fails Code changed in jenkins User: Christoph Kutzinski Path: src/main/java/hudson/plugins/ircbot/v2/IRCConnection.java http://jenkins-ci.org/commit/ircbot-plugin/3f3a6bd9e027a2f0a2585218dcfe5d2637ba9dda Log: FIXED JENKINS-17017 PircBotX#connect() sometimes fails with RuntimeExcpetion - which is not exactly what the Javadoc says This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-6203) Git plugin uses default encoding to read change log file
Alex Orlando commented on JENKINS-6203 Git plugin uses default encoding to read change log file This is still broken. It's been almost 3 years... Environment === Ubuntu 12.04.2 git 1.7.9.5 Jenkins 1.502 Jenkins GIT client plugin 1.0.2 Jenkins GIT plugin 1.2.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] (JENKINS-15306) Ability to rebuild non-parameterized projects
centic commented on JENKINS-15306 Ability to rebuild non-parameterized projects Isn't this already available via "build now"? Or what would be the difference of "rebuild" in this case? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-14077) rebuild plugin will throw java.lang.IllegalArgumentException: No such parameter definition
centic commented on JENKINS-14077 rebuild plugin will throw java.lang.IllegalArgumentException: No such parameter definition can you post the full stacktrace? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-14748) Rebuild plugin throws JellyTagException after upgrade to 477
centic resolved JENKINS-14748 as Fixed Rebuild plugin throws JellyTagException after upgrade to 477 I think this is fixed since version 1.15, at least I use it successfully with TextParameters: Version 1.15 (Oct 12, 2012) *Rebuild support for jobs having subversion/text parameter implemented. *Required Jenkins Core Version is 1.481. Change By: centic (01/Mar/13 9:21 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] (JENKINS-14077) rebuild plugin will throw java.lang.IllegalArgumentException: No such parameter definition
centic commented on JENKINS-14077 rebuild plugin will throw java.lang.IllegalArgumentException: No such parameter definition possibly a duplicate of JENKINS-9628 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-9628) Rebuild fails if some of the parameters are not explicitly defined in the built job
centic resolved JENKINS-9628 as Fixed Rebuild fails if some of the parameters are not explicitly defined in the built job The latest version of the rebuild-plugin does not throw an exception any more for empty parameters, so it should work now. Please reopen the ticket if this is still a problem for you with the latest version of the plugin. Change By: centic (01/Mar/13 9:32 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14077) rebuild plugin will throw java.lang.IllegalArgumentException: No such parameter definition
centic resolved JENKINS-14077 as Fixed rebuild plugin will throw java.lang.IllegalArgumentException: No such parameter definition The latest version of the rebuild-plugin does not throw an exception any more for empty parameters, so it should work now. Please reopen the ticket if this is still a problem for you with the latest version of the plugin. Change By: centic (01/Mar/13 9:32 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7094) Rebuild plugin not passing run type parameter into new build
centic commented on JENKINS-7094 Rebuild plugin not passing run type parameter into new build works fine for me with current version 1.18 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-6203) Git plugin uses default encoding to read change log file
evernat commented on JENKINS-6203 Git plugin uses default encoding to read change log file @Alex Do you want to maintain the git 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] (JENKINS-6077) build timeout does not work for matrix jobs
Brent Duffy commented on JENKINS-6077 build timeout does not work for matrix jobs I'm seeing a similar problem for matrix jobs with build timeout set. I've seen one case where a matrix job with a 2x2 configuration times out, but the configurations appear to keep going and cannot be stopped. At the bottom of the console output for each configuration, I see the "Build timed out (after 120 minutes). Marking the build as aborted." entries in the logs, but the spinner at the bottom is still moving and each of the configuration jobs appear to keep trying to execute. I tried to stop each configuration build the normal way (clicking the red X), which didn't work after multiple attempts, so I looked at the threads via the JavaMelody Monitoring plugin and all 4 of them are in RUNNABLE state. Trying to kill each thread does not work either, so I'm stuck here with the only choice of restarting Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9159) use a parameter value or an environment value for setting the build name build-name-setter-plugin
centic
resolved JENKINS-9159 as Duplicate
use a parameter value or an environment value for setting the build name build-name-setter-plugin
Seems to be the same issue as JENKINS-13347, there the following workaround is given, which I could verify locally as well:
instead of ${BUILD_NAME}, specify ${ENV,var="BUILD_NAME"}
Change By:
centic
(01/Mar/13 10:05 PM)
Status:
Open
Resolved
Resolution:
Duplicate
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15306) Ability to rebuild non-parameterized projects
cowwoc commented on JENKINS-15306 Ability to rebuild non-parameterized projects You're right except for one problem: there is no "build now" button in the build details view. You have to navigate up one level in order to "build now". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15769) Provide way to allow build icons without anonymous access.
Kohsuke Kawaguchi commented on JENKINS-15769 Provide way to allow build icons without anonymous access. A user without an overall read access to Jenkins is an user who is not supposed to see anything whatsoever in Jenkins. Letting them see the build status violates the access control model, and as a matter of fact the core doesn't even let us do that in the plugin. What's the use case for this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-14657) Embeddable Build Status Plugin url issue
Kohsuke Kawaguchi resolved JENKINS-14657 as Fixed Embeddable Build Status Plugin url issue Fixed as a part of JENKINS-17028 Change By: Kohsuke Kawaguchi (01/Mar/13 11:03 PM) Status: Open Resolved Assignee: KohsukeKawaguchi 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] (JENKINS-17028) Build status icons don't refresh due to Cache-Control setting in HTTP response
SCM/JIRA link daemon resolved JENKINS-17028 as Fixed Build status icons dont refresh due to Cache-Control setting in HTTP response Change By: SCM/JIRA link daemon (01/Mar/13 11:06 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] (JENKINS-17028) Build status icons don't refresh due to Cache-Control setting in HTTP response
SCM/JIRA link daemon commented on JENKINS-17028 Build status icons dont refresh due to Cache-Control setting in HTTP response Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/org/jenkinsci/plugins/badge/BadgeAction.java src/main/java/org/jenkinsci/plugins/badge/BadgeActionFactory.java src/main/java/org/jenkinsci/plugins/badge/StatusImage.java http://jenkins-ci.org/commit/embeddable-build-status-plugin/1bac74e1e2e2780504a04779175456cc8a8bda6c Log: FIXED JENKINS-17028 Some browsers appear to cache 302 requests in violation of RFC (I'm looking at you, Chrome: http://code.google.com/p/chromium/issues/detail?id=103458) I also saw this behavior with Firefox, even though I couldn't locate any bug report. Sine Chrome alone is a big enough browser share, in this change I modified the code to avoid 302 redirects and instead to service the request with 200. To avoid excessive data transfer, ETag is used to detect that the browser has the image in cache. Compare: https://github.com/jenkinsci/embeddable-build-status-plugin/compare/233087cbd8dc...1bac74e1e2e2 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-13502) Editing any job removes inaccessible downstream jobs from all accessible jobs
SCM/JIRA link daemon commented on JENKINS-13502 Editing any job removes inaccessible downstream jobs from all accessible jobs Code changed in jenkins User: Nicolas De Loof Path: changelog.html core/src/main/java/hudson/model/AbstractProject.java http://jenkins-ci.org/commit/jenkins/5d38d40e550ea918101c3b3249384c2158177698 Log: FIXED JENKINS-13502 impersonate a SYSTEM to handle upstream build trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-13502) Editing any job removes inaccessible downstream jobs from all accessible jobs
SCM/JIRA link daemon resolved JENKINS-13502 as Fixed Editing any job removes inaccessible downstream jobs from all accessible jobs Change By: SCM/JIRA link daemon (01/Mar/13 11:10 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] (JENKINS-13502) Editing any job removes inaccessible downstream jobs from all accessible jobs
SCM/JIRA link daemon commented on JENKINS-13502 Editing any job removes inaccessible downstream jobs from all accessible jobs Code changed in jenkins User: Nicolas De Loof Path: core/src/main/java/hudson/model/AbstractProject.java test/src/test/java/hudson/model/AbstractProjectTest.java http://jenkins-ci.org/commit/jenkins/dbc212e2e3ac364d08f73897c1b8f1202b5d937e Log: unit test to reproduce JENKINS-13502 and confirm fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13502) Editing any job removes inaccessible downstream jobs from all accessible jobs
SCM/JIRA link daemon commented on JENKINS-13502 Editing any job removes inaccessible downstream jobs from all accessible jobs Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractProject.java test/src/test/java/hudson/model/AbstractProjectTest.java http://jenkins-ci.org/commit/jenkins/ef9c30c665c4a5c59e1a1af54072b95831eed831 Log: Merge pull request #722 from ndeloof/master FIXED JENKINS-13502 Fix dependency graph computation when upstream build trigger is involved Compare: https://github.com/jenkinsci/jenkins/compare/fa50b3d7e6e2...ef9c30c665c4 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16931) It is not possible to define roaming jobs
Justin Ryan resolved JENKINS-16931 as Fixed It is not possible to define roaming jobs https://github.com/jenkinsci/job-dsl-plugin/pull/33 Change By: Justin Ryan (01/Mar/13 11:12 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] (JENKINS-15510) Embeddable Build Status plugin displays a Running badge for disabled jobs.
SCM/JIRA link daemon commented on JENKINS-15510 Embeddable Build Status plugin displays a Running badge for disabled jobs. Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/org/jenkinsci/plugins/badge/BadgeActionFactory.java http://jenkins-ci.org/commit/embeddable-build-status-plugin/3bc147f658537c8ec299be441a9b8eae24a1efa0 Log: FIXED JENKINS-15510 Added the "unknown" image and honor the running image properly for running jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15510) Embeddable Build Status plugin displays a Running badge for disabled jobs.
SCM/JIRA link daemon resolved JENKINS-15510 as Fixed Embeddable Build Status plugin displays a Running badge for disabled jobs. Change By: SCM/JIRA link daemon (01/Mar/13 11:15 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] (JENKINS-17029) update-center.json seems to be broken
k n created JENKINS-17029 update-center.json seems to be broken Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: update-center Created: 02/Mar/13 12:03 AM Description: update-center.json seems to be broken. The following are logs when I tried to retrieve plugin list from update center. Mar 02, 2013 8:48:10 AM hudson.model.UpdateSite updateData SEVERE: ERROR: Digest mismatch: 8jyiX+dlAY5+Mg7WaxTXh2agvR0= vs Xsay/aVf4CBCP7czYB4VuGuke0U= in update site default Environment: 1.503 Project: Jenkins Priority: Minor Reporter: k n This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-13502) Editing any job removes inaccessible downstream jobs from all accessible jobs
dogfood commented on JENKINS-13502 Editing any job removes inaccessible downstream jobs from all accessible jobs Integrated in jenkins_main_trunk #2324 FIXED JENKINS-13502 impersonate a SYSTEM to handle upstream build trigger (Revision 5d38d40e550ea918101c3b3249384c2158177698) unit test to reproduce JENKINS-13502 and confirm fix (Revision dbc212e2e3ac364d08f73897c1b8f1202b5d937e) Result = SUCCESS Nicolas De Loof : 5d38d40e550ea918101c3b3249384c2158177698 Files : core/src/main/java/hudson/model/AbstractProject.java changelog.html Nicolas De Loof : dbc212e2e3ac364d08f73897c1b8f1202b5d937e Files : test/src/test/java/hudson/model/AbstractProjectTest.java core/src/main/java/hudson/model/AbstractProject.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17029) update-center.json seems to be broken
k n updated JENKINS-17029 update-center.json seems to be broken Change By: k n (02/Mar/13 12:12 AM) Description: update-center.jsonseemstobebroken.ThefollowingarelogswhenItriedtoretrievepluginlistfromupdatecenter.Mar02,2013 8 9 : 48: 10 :31 AMhudson.model.UpdateSiteupdateDataSEVERE:ERROR:Digestmismatch: 8jyiX vSf2RQowm5ascqdUrqxTP + dlAY5+Mg7WaxTXh2agvR0 gfceI =vs Xsay 7m0Eh4cI / aVf4CBCP7czYB4VuGuke0U EmyBxB7iarllUswmHc =inupdatesite#039;default#039; This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-13154) Heavy thread congestion with FingerPrint.save
SCM/JIRA link daemon commented on JENKINS-13154 Heavy thread congestion with FingerPrint.save Code changed in jenkins User: Kohsuke Kawaguchi Path: xstream/src/java/com/thoughtworks/xstream/mapper/AnnotationMapper.java http://jenkins-ci.org/commit/xstream/d7ce9b30f56e0409c558dc1b34d0784e0755b818 Log: JENKINS-13154 Still seeing some reports of contented lock on annotatedTypes after the initial fix went in May 2012. This is really puzzling, as the processedTypes should warm up quickly and include all the relevant classes, so we shouldn't be getting to the synchronized block (unless WeakHashSet was silently dropping stuff in 1.3.x code.) This probe will hopefully shed a bit more light on what's going on, and if we are lucky, XStream 1.4 removing "Weak" from these collections might resolve the problem entirely (fingers crossed.) You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15769) Provide way to allow build icons without anonymous access.
Andrei Pozolotin commented on JENKINS-15769 Provide way to allow build icons without anonymous access. use case: publish public build status from private jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15596) Jenkins will not start as a Windows Service after KB2661254
SCM/JIRA link daemon resolved JENKINS-15596 as Fixed Jenkins will not start as a Windows Service after KB2661254 Change By: SCM/JIRA link daemon (02/Mar/13 2:52 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] (JENKINS-15596) Jenkins will not start as a Windows Service after KB2661254
SCM/JIRA link daemon commented on JENKINS-15596 Jenkins will not start as a Windows Service after KB2661254 Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/lifecycle/WindowsInstallerLink.java core/src/main/java/hudson/lifecycle/WindowsServiceLifecycle.java core/src/main/java/hudson/os/windows/ManagedWindowsServiceLauncher.java core/src/main/resources/windows-service/jenkins.exe.config msi/build.sh msi/jenkins.wxs http://jenkins-ci.org/commit/jenkins/b05d449f20c59ff858a9aca6e2dcf76b83fe3182 Log: FIXED JENKINS-15596 Disable authenticode verification on jenkins.exe and jenkins-slave.exe by generating a proper application configuration file. See: http://msdn.microsoft.com/en-us/library/cc656914.aspx See: http://msdn.microsoft.com/en-us/library/bb629393.aspx See: http://support.microsoft.com/kb/936707 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15596) Jenkins will not start as a Windows Service after KB2661254
SCM/JIRA link daemon commented on JENKINS-15596 Jenkins will not start as a Windows Service after KB2661254 Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/lifecycle/WindowsInstallerLink.java core/src/main/java/hudson/lifecycle/WindowsServiceLifecycle.java core/src/main/java/hudson/os/windows/ManagedWindowsServiceLauncher.java core/src/main/resources/windows-service/jenkins.exe.config msi/build.sh msi/jenkins.wxs war/pom.xml http://jenkins-ci.org/commit/jenkins/934e9d336b7fb1fb41506fdd525ac98acbf91240 Log: FIXED JENKINS-15596 Disable authenticode verification on jenkins.exe and jenkins-slave.exe by generating a proper application configuration file. See: http://msdn.microsoft.com/en-us/library/cc656914.aspx See: http://msdn.microsoft.com/en-us/library/bb629393.aspx See: http://support.microsoft.com/kb/936707 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15596) Jenkins will not start as a Windows Service after KB2661254
SCM/JIRA link daemon commented on JENKINS-15596 Jenkins will not start as a Windows Service after KB2661254 Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/org/jenkinsci/modules/windows_slave_installer/WindowsSlaveInstaller.java src/main/resources/org/jenkinsci/modules/windows_slave_installer/jenkins-slave.exe.config http://jenkins-ci.org/commit/windows-slave-installer-module/5170ede0e284be7019626731f8c0ad96f9ad73d9 Log: JENKINS-15596 Skip authenticode verification This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15769) Provide way to allow build icons without anonymous access.
Shawn Baker commented on JENKINS-15769 Provide way to allow build icons without anonymous access. My personal use case is that we have a Jenkins server that is separate from our Trac/Subversion server. Login information is different as well. But both systems are restricted to outside users. I would like to put the build status on the Trac wiki, but the user who is logged into Trac has different credentials on Jenkins, so the build status icons don't work. I hope this makes sense. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-14089) JUnit report - Quarantine intermittent tests
John Muczynski commented on JENKINS-14089 JUnit report - Quarantine intermittent tests Hm. That's a thought. I haven't used claim. I have the impression that you claim a BUILD. But if it were married with Quarantine, then you could claim JUnit tests, or packages full of them. Or all the new failures in a build, or just check mark half of them. I suppose that if the build only had one new commit, then you could automatically attribute failures to the commit owner. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15596) Jenkins will not start as a Windows Service after KB2661254
dogfood commented on JENKINS-15596 Jenkins will not start as a Windows Service after KB2661254 Integrated in jenkins_main_trunk #2325 FIXED JENKINS-15596 (Revision 934e9d336b7fb1fb41506fdd525ac98acbf91240) Result = UNSTABLE kohsuke : 934e9d336b7fb1fb41506fdd525ac98acbf91240 Files : core/src/main/java/hudson/lifecycle/WindowsServiceLifecycle.java core/src/main/java/hudson/lifecycle/WindowsInstallerLink.java changelog.html war/pom.xml msi/build.sh msi/jenkins.wxs core/src/main/java/hudson/os/windows/ManagedWindowsServiceLauncher.java core/src/main/resources/windows-service/jenkins.exe.config This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15995) Arguments passed to Managed Script called in Conditional BuildStep could not be saved
domi commented on JENKINS-15995 Arguments passed to Managed Script called in Conditional BuildStep could not be saved I'm currently on vacation, but I'll look into it soon... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
