[JIRA] [mercurial] (JENKINS-17632) Please add an option for uncompressed cloning
Dirk Heinrichs commented on JENKINS-17632 Please add an option for uncompressed cloning Please define "read-only repo". For me, that's a repo where the cloning user doesn't have write access as configured per Mercurial ACL extension. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [fstrigger] (JENKINS-12354) Scanning a network folder such as \\some_network_folder\to_scan doesn't work
Bernhard Berbuir commented on JENKINS-12354 Scanning a network folder such as \\some_network_folder\to_scan doesnt work I have the same problem. My job is bound to a windows slave which runs as LocalSystem (it is executing GUI tests and has to interact with the desktop). This slave / service does not have access to the network share. I would like to see something similar to the perforce plugin: it allows to restrict the polling to the master. My Jenkins master is running under a dedicated user and has access to the network share. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Stefan Cordes
edited a comment on JENKINS-17508
The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.
Got an
Jan 28, 2014 9:03:44 AM hudson.model.Run execute
SEVERE: Failed to rotate log
java.io.IOException: e:\jenkins\jobs\.\modules\com$\builds\2013-10-23_11-57-46 looks to have already been deleted
{{ at hudson.model.Run.delete(Run.java:1432)}}
{{ at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:430)}}
{{ at hudson.tasks.LogRotator.perform(LogRotator.java:124)}}
{{ at hudson.model.Job.logRotate(Job.java:437)}}
{{ at hudson.maven.MavenModuleSet.logRotate(MavenModuleSet.java:840)}}
{{ at hudson.model.Run.execute(Run.java:1728)}}
{{ at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)}}
{{ at hudson.model.ResourceController.execute(ResourceController.java:88)}}
{{ at hudson.model.Executor.run(Executor.java:246)}}
with Jenkins ver. 1.532.1.
(Mentioned directory 2013-10-23_11-57-46 is not existing on file system).
LogRotator should continue deleting all other matching 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] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Stefan Cordes
commented on JENKINS-17508
The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.
Got an
{{Jan 28, 2014 9:03:44 AM hudson.model.Run execute
SEVERE: Failed to rotate log
java.io.IOException: e:\jenkins\jobs\.\modules\com$\builds\2013-10-23_11-57-46 looks to have already been deleted
at hudson.model.Run.delete(Run.java:1432)
at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:430)
at hudson.tasks.LogRotator.perform(LogRotator.java:124)
at hudson.model.Job.logRotate(Job.java:437)
at hudson.maven.MavenModuleSet.logRotate(MavenModuleSet.java:840)
at hudson.model.Run.execute(Run.java:1728)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)}}
with Jenkins ver. 1.532.1.
(Mentioned directory 2013-10-23_11-57-46 is not existing on file system).
LogRotator should continue deleting all other matching 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] [fstrigger] (JENKINS-12354) Scanning a network folder such as \\some_network_folder\to_scan doesn't work
Bernhard Berbuir edited a comment on JENKINS-12354 Scanning a network folder such as \\some_network_folder\to_scan doesnt work I have the same problem. My job is bound to a windows slave which runs as LocalSystem (it is executing GUI tests and has to interact with the desktop). This slave / service does not have access to the network share. I would like to see something similar to the perforce plugin: it allows to restrict the polling to the master. My Jenkins master is running under a dedicated user and has access to the network share. As a workaround I have defined a "trigger" job which does only the polling. This job starts the "worker" job when a file has changed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Stefan Cordes
edited a comment on JENKINS-17508
The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.
Got an
Jan 28, 2014 9:03:44 AM hudson.model.Run execute
SEVERE: Failed to rotate log
java.io.IOException: e:\jenkins\jobs\.\modules\com$\builds\2013-10-23_11-57-46 looks to have already been deleted
{{ at hudson.model.Run.delete(Run.java:1432)}}
{{ at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:430)}}
{{ at hudson.tasks.LogRotator.perform(LogRotator.java:124)}}
{{ at hudson.model.Job.logRotate(Job.java:437)}}
{{ at hudson.maven.MavenModuleSet.logRotate(MavenModuleSet.java:840)}}
{{ at hudson.model.Run.execute(Run.java:1728)}}
{{ at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)}}
{{ at hudson.model.ResourceController.execute(ResourceController.java:88)}}
{{ at hudson.model.Executor.run(Executor.java:246)}}
with Jenkins ver. 1.532.1.
(Mentioned directory 2013-10-23_11-57-46 is not existing on file system).
LogRotator should continue deleting all other matching 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] [mercurial] (JENKINS-17632) Please add an option for uncompressed cloning
Anatoly Bubenkov commented on JENKINS-17632 Please add an option for uncompressed cloning yes, or, if using just plain ssh access to the remote mercurial repo, where cloning user only has read access This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20502) Cannot find any revision to build on clean workspace
cb372 commented on JENKINS-20502 Cannot find any revision to build on clean workspace Unfortunately, this does not seem to be fixed (for me, at least) in 2.0.1. Steps to reproduce: 1. Create a new job. Use a git repo with multiple branches. Set the 'Branches to build Branch specifier' to a specific branch, e.g. 'feature/my-feature' 2. Run a build Result: Building in workspace /var/lib/jenkins/main/jobs/JOB_NAME/workspace Fetching changes from the remote Git repository Fetching upstream changes from ssh://...REPO URL... ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. Finished: FAILURE Notes: the clone works fine if I don't specify a branch even after a successful clone, if I edit the job config to specify a branch, it fails with the same error as above. I don't know much about the internals of the Git plugin, but it looks like it's not doing a fetch, so it doesn't know what remote branches are available. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rtc] (JENKINS-21477) Enable multiple Jazz servers per project
x29a commented on JENKINS-21477 Enable multiple Jazz servers per project Hi there and thanks for your comment. The problem with my scenario is, that Server A and Server B cannot communicate with each other, only the Jenkins instance has access to both. I do understand that working around this special case is not the job of a SCM plugin, but i do see more situations in which the described functionality could be useful. But i also understand that this is somewhat unimportant in relation to other tasks for your team. Anyway, i think the only solution for me right now is to use multiple jobs (maybe there is a plugin that can work around the hardcoded dependencies). Maybe, in the far future, this plugin will handle this case for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20502) Cannot find any revision to build on clean workspace
cb372 commented on JENKINS-20502 Cannot find any revision to build on clean workspace Found a workaround: 1. Leave the 'Branches to build Branch specifier' field blank 2. Click the Advanced button, and set a custom refspec: +refs/heads/feature/my-feature:refs/remotes/origin/feature/my-feature With these settings, the plugin will correctly perform a fetch and then check out only the 'feature/my-feature' branch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21531) It is failing to execute build using URL and throwing the following error You must use POST method to trigger builds.
rakesh kumar created JENKINS-21531 It is failing to execute build using URL and throwing the following error You must use POST method to trigger builds. Issue Type: Bug Assignee: Unassigned Components: jenkins-multijob-plugin Created: 28/Jan/14 8:55 AM Description: While invoking build using URL it is throwing the following error, It was working in earlier version. Version : 1.548 URL : http://im-jenkins01:8080/view/Project/job/Job_name/build?delay=0sec You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin. Project: Jenkins Priority: Blocker Reporter: rakesh kumar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [fitnesse] (JENKINS-20174) Corrupt FitNesse plugin XML report generated
Thierry Sorgnard
commented on JENKINS-20174
Corrupt FitNesse plugin XML report generated
I have same problem with Fitnesse plugin version 1.8., Jenkins 1.523
same pb in my xml file.
It looks like jenkins is writing two time same downloaded xml content into file.
My tests take 4 hours to run (this is expected)
Here is standard output.
Started by timer
Building in workspace C:\Users\Administrator\.jenkins\workspace\FITNESSE_
Deleting project workspace... done
hudson.plugins.fitnesse.FitnesseBuilder: {fitnesseTargetPage=.SuiteIteration19suiteFilter=ECRAN_, fitnesseTargetIsSuite=true, fitnesseHost=, fitnesseHttpTimeout=4800, fitnessePortRemote=8080, fitnesseStart=False, fitnessePathToXmlResultsOut=fitnesse-results.xml}
Connnecting to http://:8080/.SuiteIteration19?suitesuiteFilter=ECRAN_format=xmlincludehtml
Connected: 200/OK
2k...
5k...
8k...
11k...
2334k...
2337k...
2342k...
2345k...
Xml results saved as windows-1252 to C:\Users\Administrator\.jenkins\workspace\FITNESSE_\fitnesse-results.xml
Reading results as windows-1252 from C:\Users\Administrator\.jenkins\workspace\FITNESSE_\fitnesse-results.xml
Parsing results...
javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: The processing instruction target matching "xXmMlL" is not allowed.
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source)
at hudson.plugins.fitnesse.NativePageCountsParser.transformRawResults(NativePageCountsParser.java:25)
at hudson.plugins.fitnesse.NativePageCountsParser.parse(NativePageCountsParser.java:17)
at hudson.plugins.fitnesse.FitnesseResultsRecorder.getResults(FitnesseResultsRecorder.java:131)
at hudson.plugins.fitnesse.FitnesseResultsRecorder.getResults(FitnesseResultsRecorder.java:109)
at hudson.plugins.fitnesse.FitnesseResultsRecorder.perform(FitnesseResultsRecorder.java:73)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
at hudson.model.Run.execute(Run.java:1618)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:247)
Caused by: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: The processing instruction target matching "xXmMlL" is not allowed.
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.getDOM(Unknown Source)
... 16 more
Caused by: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: The processing instruction target matching "xXmMlL" is not allowed.
at com.sun.org.apache.xalan.internal.xsltc.dom.XSLTCDTMManager.getDTM(Unknown Source)
at com.sun.org.apache.xalan.internal.xsltc.dom.XSLTCDTMManager.getDTM(Unknown Source)
... 17 more
-
javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: The processing instruction target matching "xXmMlL" is not allowed.
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.getDOM(Unknown Source)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source)
at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source)
at hudson.plugins.fitnesse.NativePageCountsParser.transformRawResults(NativePageCountsParser.java:25)
at hudson.plugins.fitnesse.NativePageCountsParser.parse(NativePageCountsParser.java:17)
at hudson.plugins.fitnesse.FitnesseResultsRecorder.getResults(FitnesseResultsRecorder.java:131)
at hudson.plugins.fitnesse.FitnesseResultsRecorder.getResults(FitnesseResultsRecorder.java:109)
at hudson.plugins.fitnesse.FitnesseResultsRecorder.perform(FitnesseResultsRecorder.java:73)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
at
Web Strategies
Hello, I am Ayush Dixit. I was surfing through your site and can see that you are offering Online Development services to your clients. We will be happy to execute SEO Web Design and Development projects at a much lower cost than what you have in house - No compromise on quality! We are at present partnering with over 30 firms from UK, US, Australia and parts of Europe. We specialize in SEO, SMO, SEM, PPC, and Website Design Development. To brief you about our company: . We are a group of 75+ professionals. . We have been in business from last 5 years. . We have served 6700+ clients. . We are an offshore execution partner for leading Digital Agencies in US, UK Australia and across the Globe. I shall look forward to hear from you soon. Once have the consent from your end would have the next step would be to implement your requirements with immediate effect. Feel free to discuss any other queries. Truly yours, Ayush Dixit Business Development Manager -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-remote-trigger] (JENKINS-20828) Allow to block the build untill target job finished
Tim Brown commented on JENKINS-20828 Allow to block the build untill target job finished https://github.com/timbrown5/parameterized-remote-trigger-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] [parameterized-remote-trigger] (JENKINS-20828) Allow to block the build untill target job finished
Tim Brown commented on JENKINS-20828 Allow to block the build untill target job finished I have commited the code to the following fork: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven-info] (JENKINS-21450) NPE on Selected Module Last Version when Jenkins Job Name != artifactId
Bert Geens commented on JENKINS-21450 NPE on Selected Module Last Version when Jenkins Job Name != artifactId Hmm, I probably messed up and used a build with additional debug statements, my apologies for that. This is the exception with a vanilla 0.1.2 plugin form the update center (double checked it this time): Jan 28, 2014 10:48:01 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.getVersion(job) in /view/WIP/. Reason: java.lang.NullPointerException java.lang.NullPointerException at jenkins.plugins.maveninfo.columns.LastVersionColumn.getModulePattern(LastVersionColumn.java:100) at jenkins.plugins.maveninfo.columns.LastVersionColumn.getVersion(LastVersionColumn.java:105) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven-info] (JENKINS-21450) NPE on Selected Module Last Version when Jenkins Job Name != artifactId
Bert Geens edited a comment on JENKINS-21450 NPE on Selected Module Last Version when Jenkins Job Name != artifactId Hmm, I probably messed up and used a build with additional debug statements, my apologies for that. This is the exception with a vanilla 0.1.2 plugin form the update center (double checked it this time): Jan 28, 2014 10:48:01 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.getVersion(job) in /view/WIP/. Reason: java.lang.NullPointerException java.lang.NullPointerException at jenkins.plugins.maveninfo.columns.LastVersionColumn.getModulePattern(LastVersionColumn.java:100) at jenkins.plugins.maveninfo.columns.LastVersionColumn.getVersion(LastVersionColumn.java:105) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) It doesn't seem to happen with the latest version from Git anymore, so it seems cb9649c has fixed it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21487) Frozen UI
Arnaud Héritier commented on JENKINS-21487 Frozen UI Another White Screen Of the Death : https://gist.github.com/aheritier/8665709 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-21497) Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher
SCM/JIRA link daemon commented on JENKINS-21497 Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher Code changed in jenkins User: ikedam Path: src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java http://jenkins-ci.org/commit/flexible-publish-plugin/9145b7c4efeed18c0df027f8e378ce099edda8e4 Log: JENKINS-21497 Fixed a wrong error message when failed to instantiate a publisher. Compare: https://github.com/jenkinsci/flexible-publish-plugin/compare/f60940f04492...9145b7c4efee This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21512) Cli for ContextHashCode
Ralf Hain commented on JENKINS-21512 Cli for ContextHashCode Not stucking any more on 'FormValidation'. (EncodingValidator.java: outcommened everything but readFile()) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING OK, I had to fiddle a bit, as the delete dropdown menu item gave me a 403 bad crumb error, but if instead I selected the configure dropdown for the module, there was an option to delete the module in the left hand menu, which worked fine. If you then list the modules belonging to the build, the module still shows as present, but the status ball is greyed out. Running the build causes the module to be reinstantiated. This is a pretty painful workround, as I have many dozens of Maven builds each with a handful or two of modules. Worse, I can't actually validate it in my test system, since I can't reproduce the error there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney edited a comment on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING OK, I had to fiddle a bit, as the delete dropdown menu item gave me a 403 bad crumb error, but if instead I selected the configure dropdown for the module, there was an option to delete the module in the left hand menu, which worked fine. If you then list the modules belonging to the build, the module still shows as present, but the status ball is greyed out. Running the build causes the module to be reinstantiated. This is a pretty painful workround, as I have many dozens of Maven builds each with a handful or two of modules. Worse, I can't actually validate it in my test system, since I can't reproduce the error there. But if it works it's better than nothing... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-16638) child builds going missing from matrix jobs
Sven Appenrodt commented on JENKINS-16638 child builds going missing from matrix jobs Upgraded to Jenkins version 1.539 several days (or months ago). LogRotation is set to X days and Y builds and another job is set to Y builds only. Problem does not occur anymore on both machines. Please can anyone confirm this? Then also bug 15799 can be set to "fixed".. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21180) Attach Build Log conflicts with the ansi-color plugin
Alex Earl resolved JENKINS-21180 as Fixed Attach Build Log conflicts with the ansi-color plugin Changed the way that the logfile is retrieved to remove the annotations. Change By: Alex Earl (28/Jan/14 12:12 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] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
David Frank
commented on JENKINS-21373
Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
hi,
looking at the code (for the first time - so forgive me if I'm wrong..) I think method
private EnvVars getEnvVars(Hudson h) { return getEnvVars(h.getGlobalNodeProperties()); }
is no longer there (compared with https://github.com/jenkinsci/jenkins/blob/934e9d336b7fb1fb41506fdd525ac98acbf91240/core/src/main/java/hudson/os/windows/ManagedWindowsServiceLauncher.java) with leads to code in
private EnvVars getEnvVars(SlaveComputer computer)
fetching only environment variables by calling
private EnvVars getEnvVars(Node n) { return getEnvVars(n.getNodeProperties()); }
twice instead of merging local and global ones.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
David Frank
edited a comment on JENKINS-21373
Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
hi,
looking at the code (for the first time - so forgive me if I'm wrong..) I think method
private EnvVars getEnvVars(Hudson h) { return getEnvVars(h.getGlobalNodeProperties()); }
is no longer there (compared with https://github.com/jenkinsci/jenkins/blob/934e9d336b7fb1fb41506fdd525ac98acbf91240/core/src/main/java/hudson/os/windows/ManagedWindowsServiceLauncher.java) with leads to code in
private EnvVars getEnvVars(SlaveComputer computer)
fetching only node-local environment variables by calling
private EnvVars getEnvVars(Node n) { return getEnvVars(n.getNodeProperties()); }
twice instead of merging local and global ones.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-21497) Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher
ikedam commented on JENKINS-21497 Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher xunit-plugin generates broken HTML like this: tr td class="setting-leftspace" /td td class="setting-name"Choose your threshold mode/td td class="setting-main" input name="thresholdMode" value="1" type="radio" checked="true" / label class="attach-previous"Use a number of tests/label br / input name="thresholdMode" value="2" type="radio" /label class="attach-previous"Use a percent of tests/label /td /tr tr class="validation-error-area"td colspan="2"/tdtd/td/tr /tbody/table /td/tr /td/tr br /br / !-- This is wrong HTML -- trtd colspan="3" tr td/td td/td td Web browsers converts this HTML like this: ... tr class="dropdownList-container" td colspan="2"/td td colspan="2" br /br / !-- wrong HTML comes here -- table name="publisher" width="100%" tbody tr class="dropdownList-start rowvg-start" td style="display:none" input name="stapler-class" value="hudson.tasks.test.AggregatedTestResultPublisher" type="hidden" /td ... This cause dropdownList work wrong as invalid "br" tags prevents it find out "tr.dropdownList-start". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and (-webkit-min-device=
-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important=
; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=3Demail-body
table id=3Demail-wrap align=3Dcenter border=3D0 cellpadding=3D0 ce=
llspacing=3D0 style=3Dbackground-color:#f0f0f0;color:#00;width:100%;=
tr valign=3Dtop
td id=3Demail-page style=3Dpadding:16px !important;
table align=3Dcenter border=3D0 cellpadding=3D0 cellspac=
ing=3D0 style=3Dbackground-color:#ff;border:1px solid #bb;color:=
#00;width:100%;
tr valign=3Dtop
td bgcolor=3D#33 style=3Dbackground-color:#=
33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:=
12px;line-height:1;img src=3Dhttps://issues.jenkins-ci.org/s/en_US-jh6o=
7l/733/41/_/jira-logo-scaled.png alt=3D style=3Dvertical-align:top; /=
/td
/trtr valign=3Dtop
td id=3Demail-banner style=3Dpadding:32px 32px 0 32px;
=20
=20
=20
table align=3Dleft border=3D0 cellpadding=3D0 cellspacin=
g=3D0 width=3D100% style=3Dwidth:100%;
tr valign=3Dtop
td style=3Dcolor:#505050;font-family:Arial,FreeSans,Helvetica,san=
s-serif;padding:0;
img id=3Demail-avatar src=3Dhtt=
ps://issues.jenkins-ci.org/secure/useravatar?avatarId=3D10292 alt=3D hei=
ght=3D48 width=3D48 border=3D0 align=3Dleft style=3Dpadding:0;marg=
in: 0 16px 16px 0; /
div id=3Demail-action style=3Dpadding: 0 0 8px =
0;font-size:12px;line-height:18px;
a class=3Duser-hover rel=3Djeffi i=
d=3Demail_jeffi href=3Dhttps://issues.jenkins-ci.org/secure/ViewProfile.=
jspa?name=3Djeffi style=3Dcolor:#355564;Jean-Fran=C3=A7ois DAHAN/a
commented on img src=3Dhttps://issues.jenkins-ci.org/images/icons/bu=
g.gif height=3D16 width=3D16 border=3D0 align=3Dabsmiddle alt=3DB=
ug a
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and (-webkit-min-device=
-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important=
; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=3Demail-body
table id=3Demail-wrap align=3Dcenter border=3D0 cellpadding=3D0 ce=
llspacing=3D0 style=3Dbackground-color:#f0f0f0;color:#00;width:100%;=
tr valign=3Dtop
td id=3Demail-page style=3Dpadding:16px !important;
table align=3Dcenter border=3D0 cellpadding=3D0 cellspac=
ing=3D0 style=3Dbackground-color:#ff;border:1px solid #bb;color:=
#00;width:100%;
tr valign=3Dtop
td bgcolor=3D#33 style=3Dbackground-color:#=
33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:=
12px;line-height:1;img src=3Dhttps://issues.jenkins-ci.org/s/en_US-jh6o=
7l/733/41/_/jira-logo-scaled.png alt=3D style=3Dvertical-align:top; /=
/td
/trtr valign=3Dtop
td id=3Demail-banner style=3Dpadding:32px 32px 0 32px;
=20
=20
=20
table align=3Dleft border=3D0 cellpadding=3D0 cellspacin=
g=3D0 width=3D100% style=3Dwidth:100%;
tr valign=3Dtop
td style=3Dcolor:#505050;font-family:Arial,FreeSans,Helvetica,san=
s-serif;padding:0;
nbsp; div id=3Demail=
-action style=3Dpadding: 0 0 8px 0;font-size:12px;line-height:18px;
a class=3Duser-hover rel=3Djeffi i=
d=3Demail_jeffi href=3Dhttps://issues.jenkins-ci.org/secure/ViewProfile.=
jspa?name=3Djeffi style=3Dcolor:#355564;Jean-Fran=C3=A7ois DAHAN/a
edited a comment on img src=3Dhttps://issues.jenkins-ci.org/images/i=
cons/bug.gif height=3D16 width=3D16 border=3D0 align=3Dabsmiddle a=
lt=3DBug a style=3D'color:#355564;text-decoration:none;' href=3D'https:=
//issues.jenkins-ci.org/browse/JENKINS-10974'JENKINS-10974/a
/div
div id=3Demail-summary
[JIRA] [xunit] (JENKINS-21532) Broken HTML in job configuration page
ikedam created JENKINS-21532 Broken HTML in job configuration page Issue Type: Bug Assignee: Gregory Boissinot Components: xunit Created: 28/Jan/14 12:52 PM Description: brbr before Extra Configuration block is placed in bad place in HTML like this: ... tr td class="setting-leftspace" /td td class="setting-name"Choose your threshold mode/td td class="setting-main" input name="thresholdMode" value="1" type="radio" checked="true" / label class="attach-previous"Use a number of tests/label br / input name="thresholdMode" value="2" type="radio" /label class="attach-previous"Use a percent of tests/label /td /tr tr class="validation-error-area"td colspan="2"/tdtd/td/tr /tbody/table /td/tr /td/tr br /br / !-- This is wrong HTML -- trtd colspan="3" tr td/td td/td ... This happens used as both builder and publisher. Especially combined with Flexible Publish Plugin, this cause drop-down lists not to work (JENKINS-21497). Environment: xunit-plugin 1.80 Project: Jenkins Priority: Major Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and (-webkit-min-device=
-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important=
; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=3Demail-body
table id=3Demail-wrap align=3Dcenter border=3D0 cellpadding=3D0 ce=
llspacing=3D0 style=3Dbackground-color:#f0f0f0;color:#00;width:100%;=
tr valign=3Dtop
td id=3Demail-page style=3Dpadding:16px !important;
table align=3Dcenter border=3D0 cellpadding=3D0 cellspac=
ing=3D0 style=3Dbackground-color:#ff;border:1px solid #bb;color:=
#00;width:100%;
tr valign=3Dtop
td bgcolor=3D#33 style=3Dbackground-color:#=
33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:=
12px;line-height:1;img src=3Dhttps://issues.jenkins-ci.org/s/en_US-jh6o=
7l/733/41/_/jira-logo-scaled.png alt=3D style=3Dvertical-align:top; /=
/td
/trtr valign=3Dtop
td id=3Demail-banner style=3Dpadding:32px 32px 0 32px;
=20
=20
=20
table align=3Dleft border=3D0 cellpadding=3D0 cellspacin=
g=3D0 width=3D100% style=3Dwidth:100%;
tr valign=3Dtop
td style=3Dcolor:#505050;font-family:Arial,FreeSans,Helvetica,san=
s-serif;padding:0;
nbsp; div id=3Demail=
-action style=3Dpadding: 0 0 8px 0;font-size:12px;line-height:18px;
a class=3Duser-hover rel=3Djeffi i=
d=3Demail_jeffi href=3Dhttps://issues.jenkins-ci.org/secure/ViewProfile.=
jspa?name=3Djeffi style=3Dcolor:#355564;Jean-Fran=C3=A7ois DAHAN/a
edited a comment on img src=3Dhttps://issues.jenkins-ci.org/images/i=
cons/bug.gif height=3D16 width=3D16 border=3D0 align=3Dabsmiddle a=
lt=3DBug a style=3D'color:#355564;text-decoration:none;' href=3D'https:=
//issues.jenkins-ci.org/browse/JENKINS-10974'JENKINS-10974/a
/div
div id=3Demail-summary
[JIRA] [xunit] (JENKINS-21532) Broken HTML in job configuration page
ikedam commented on JENKINS-21532 Broken HTML in job configuration page pull request https://github.com/jenkinsci/xunit-plugin/pull/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] [flexible-publish] (JENKINS-21497) Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher
ikedam resolved JENKINS-21497 as Wont Fix Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher I created a ticket for xunit plugin: JENKINS-21532 This would be fixed in that ticket. Won't fix in this ticket. Please contact to the maintainer of xunit plugin if you want to hurry that fix. Change By: ikedam (28/Jan/14 1:07 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] [active-directory] (JENKINS-11990) After updating Active Directory plugin the Jenkins People database is experiencing massive performance issues synching because it is trying to authenticate us
alexlombardi commented on JENKINS-11990 After updating Active Directory plugin the Jenkins People database is experiencing massive performance issues synching because it is trying to authenticate users that are no longer in company Active Directory but are part of the Jenkins Database Problem still persists evermat. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21532) Broken HTML in job configuration page
SCM/JIRA link daemon resolved JENKINS-21532 as Fixed Broken HTML in job configuration page Change By: SCM/JIRA link daemon (28/Jan/14 1:30 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] [xunit] (JENKINS-21532) Broken HTML in job configuration page
SCM/JIRA link daemon commented on JENKINS-21532 Broken HTML in job configuration page Code changed in jenkins User: Gregory Boissinot Path: src/main/resources/org/jenkinsci/plugins/xunit/XUnitBuilder/config.jelly src/main/resources/org/jenkinsci/plugins/xunit/XUnitPublisher/config.jelly http://jenkins-ci.org/commit/xunit-plugin/e0369f6aa2eaa36488e7dfb8a464bee4ac444eeb Log: Merge pull request #18 from ikedam/feature/JENKINS-21532 JENKINS-21532 Fixed wrong placed brs. Compare: https://github.com/jenkinsci/xunit-plugin/compare/b763e52bceb8...e0369f6aa2ea This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21532) Broken HTML in job configuration page
SCM/JIRA link daemon commented on JENKINS-21532 Broken HTML in job configuration page Code changed in jenkins User: ikedam Path: src/main/resources/org/jenkinsci/plugins/xunit/XUnitBuilder/config.jelly src/main/resources/org/jenkinsci/plugins/xunit/XUnitPublisher/config.jelly http://jenkins-ci.org/commit/xunit-plugin/bf7575017f1c85aa7ce3ee35f40a74d17d95d984 Log: FIXED JENKINS-21532 Fixed wrong placed brs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-21533) Links when using folders is wrong
Patrik Boström created JENKINS-21533 Links when using folders is wrong Issue Type: Bug Assignee: Unassigned Components: delivery-pipeline Created: 28/Jan/14 1:36 PM Description: When using folders, links to the actual job is wrong in view. Environment: Folders plugin Project: Jenkins Priority: Minor Reporter: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-14675) Schema 'DBUSER' does not exist error in integrity plugin
Gregory Pierre commented on JENKINS-14675 Schema DBUSER does not exist error in integrity plugin We have the same problem on our environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21326) email-ext.jar might need to be rebuilt in email-ext 2.37
Nick Jones commented on JENKINS-21326 email-ext.jar might need to be rebuilt in email-ext 2.37 Thanks Alex; the 2.37.2 version fixed this issue for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21479) Poll SCM trigger no functioning during the first execution
Gregory Pierre updated JENKINS-21479 Poll SCM trigger no functioning during the first execution Change By: Gregory Pierre (28/Jan/14 2:51 PM) Summary: PollSCMtriggernofunctioning withvariantprojects duringthefirstexecution Description: The integrityplugindoesntdetectanychangessincethelastcheckpoint:StartedonJan22,20144:39:21PMPreparingtoexecutesiprojectinfofor#/Projects/MyProject#Core/MySubProject#d=MYDEVPATH_7.2Preparingtoexecutesiviewprojectfor#/Projects/MyProject#Core/MySubProject#d=MYDEVPATH_7.2Nonewchangesdetectedinproject!Done.Took8secNochangesHowever,therewerechangesandIcouldlistthemmanuallyusing firsttime simods.ThePoll poll SCM triggerworksfinewithmainlineprojects.Theissueshowedupwhenwecreated isexecuted,itfailsbecauseof a developmentpath java . lang.NullPointerException This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21326) email-ext.jar might need to be rebuilt in email-ext 2.37
Alex Earl closed JENKINS-21326 as Fixed email-ext.jar might need to be rebuilt in email-ext 2.37 Change By: Alex Earl (28/Jan/14 3:06 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] [git] (JENKINS-21270) Add licenses to jenkins core and plugins
Alex Earl updated JENKINS-21270 Add licenses to jenkins core and plugins Removing email-ext as I have added the MIT license to the pom Change By: Alex Earl (28/Jan/14 3:27 PM) Component/s: email-ext This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [synergy] (JENKINS-20838) Synergy plug-in update command
Garnik Arakelian
updated JENKINS-20838
Synergy plug-in update command
Change By:
Garnik Arakelian
(28/Jan/14 3:42 PM)
Description:
Hello,IamusingJenkins(version1.504)withSynergyplug-in(version1.
6
7
)andSynergy7.1.Afterseveraltries,Inoticedthatiftheprojectsstatesare“visible”or“shared”thentheplug-indonotupdatethem,butitjustdosea“copytofilesystem”.Wehavedonesomechangesin“SynergySCM.java”class,especiallyin“isStaticProject”methodasfollows: privatebooleanisStaticProject(Stringproject,FilePathworkspace)throwsIOException,InterruptedException,SynergyException{ //Getprojectstate. GetProjectStateCommandcommand=newGetProjectStateCommand(project); getCommands().executeSynergyCommand(workspace,command); Stringstate=command.getState(); //Computeresult. if(prep.equals(state)){ //Integrationtesting,becomebuildmanager. SetRoleCommandsetRoleCommand=newSetRoleCommand(SetRoleCommand.BUILD_MANAGER); getCommands().executeSynergyCommand(workspace,setRoleCommand); returnfalse; }elseif(working.equals(state)){ //DevelopmentprojectwithInsulated/Collaborative/CustomDevelopmentpurpose. returnfalse; }elseif(visible.equals(state)){ //DevelopmentprojectwithVisibleDevelopmentpurpose. returnfalse; }elseif(shared.equals(state)){ //DevelopmentprojectwithSharedDevelopmentpurpose. returnfalse; }else{ //Releasedprojectpartofabaseline. returntrue; } }Then,I’vegeneratedthe.hpifile.Itworksverywell.Bestregards.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [synergy] (JENKINS-20838) Synergy plug-in update command with visible or shared projects
Garnik Arakelian updated JENKINS-20838 Synergy plug-in update command with visible or shared projects Change By: Garnik Arakelian (28/Jan/14 3:45 PM) Summary: Synergyplug-inupdatecommand withvisibleorsharedprojects This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [synergy] (JENKINS-20838) Synergy plug-in update command with visible or shared projects
Garnik Arakelian updated JENKINS-20838 Synergy plug-in update command with visible or shared projects Change By: Garnik Arakelian (28/Jan/14 4:00 PM) Assignee: GarnikArakelian jribette This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [synergy] (JENKINS-21534) Synergy scan scm tool option with MasterLinux+SlaveWindows configuration
Garnik Arakelian created JENKINS-21534 Synergy scan scm tool option with MasterLinux+SlaveWindows configuration Issue Type: Bug Assignee: jribette Components: synergy Created: 28/Jan/14 4:03 PM Description: Hi all, I am using Jenkins (version 1.504) with Synergy plug-in (version 1.7) and Synergy 7.1. The master runs on Linux and the synergy job is tied to a Windows 7 slave. I tick the “Scan scm tool” option under the heading “What triggers the build” to detect any changes in Synergy. The “Check for modifications” option is disabled. And I’ve “ccm command failed” as follows: Started on Jan 27, 2014 10:33:22 AM $ "C:\Program Files (x86)\IBM\Rational\Synergy\7.1\bin\ccm" start -d /opt/ccm/databases/hdf_fcc_eqsw -nogui -m -q -s http://synergy7.sds.safran:8410 -pw ** Hdf_FCC_Drv_UpdateWorkspace $ "C:\Program Files (x86)\IBM\Rational\Synergy\7.1\bin\ccm" start -d /opt/ccm/databases/hdf_fcc_eqsw -nogui -m -q -s http://synergy7.sds.safran:8410 -pw ccm command failed Invalid username or password. The username or password is invalid. Recommendation: Verify that server address, username, and password are correct. If the engine host is an Windows machine, then also check if ccm_ess is running. Command: The environment was : TERM=linux SHELL=/bin/bash JENKINS_HOME=/var/lib/jenkins SHLVL=1 PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games MAIL=/var/mail/jenkins XDG_SESSION_COOKIE=e1fc9e0623aee5423a92a1aa0004-1364372822.961271-1296189256 USER=jenkins PWD=/jenkins HOME=/var/lib/jenkins LOGNAME=jenkins _=/usr/bin/daemon LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk/jre/../lib/amd64 LANG=C CCM_UILOG=C:\Program Files\IBM\Rational\Synergy\7.1\bin\ccm_ui.log CCM_ENGLOG=C:\Program Files\IBM\Rational\Synergy\7.1\bin\ccm_eng.log Done. Took 10 sec No changes I think the Synergy plug-in missdetects that the job is running on a Windows slave because the username is not present in the ccm start command. I tried to run the same job from within a Windows Jenkins master and it the username is properly present in the start command. Also, the same job (Linux master+Windows slave) works well (username is present) when the build is triggered periodically. Are there any solutions to this problem? Thank you Best regards. Due Date: 28/Jan/14 12:00 AM Environment: windows xp Fix Versions: current Project: Jenkins Labels: scm plugins jenkins Priority: Major Reporter: Garnik Arakelian This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21479) Poll SCM trigger no functioning during the first execution
Cletus DSouza commented on JENKINS-21479 Poll SCM trigger no functioning during the first execution Thanks! Will review this suggestion for the next release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18203) Enable use of managed files for templates
Walter Kacynski reopened JENKINS-18203 Enable use of managed files for templates Can you update the token help to include the "managed:" syntax? Change By: Walter Kacynski (28/Jan/14 4:30 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18203) Enable use of managed files for templates
Alex Earl commented on JENKINS-18203 Enable use of managed files for templates Good idea, I'll do that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven-repo-cleaner] (JENKINS-15728) Remote slave with Maven Repo Cleaner enabled as post build task fails.
Guang Su commented on JENKINS-15728 Remote slave with Maven Repo Cleaner enabled as post build task fails. Hi, I have the same problem too using Jenkins version 1.532.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-16207) Changes Summary diff link broken after migration to TFS 2012
Bryan Fife commented on JENKINS-16207 Changes Summary diff link broken after migration to TFS 2012 I am also facing this issue. Would appreciate any kind of quick fix or workaround if possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-21535) TestLink plugin - cant get custm field values as variables in job
gustavo labbate godoy
created JENKINS-21535
TestLink plugin - cant get custm field values as variables in job
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Components:
testlink
Created:
28/Jan/14 5:47 PM
Description:
I have a job in jenkis that must read values of three custom fields in testlink, but reads only one.
The only one variable readed is the default 'Java Class', any other new isn't read.
Here are my environment:
Jenkins version: 1.530
TestLink version: 1.9.4
Plugin version: 3.2
This is my configuration, in Iterative Build steps. I follow the instructions on the plugin site (https://wiki.jenkins-ci.org/display/JENKINS/TestLink+Plugin)
When I try to access the variables like that:
#!/bin/sh
echo 1 - ${TESTLINK_TESTCASE_JAVA_CLASS}
echo 2 - ${TESTLINK_JAVA_METHOD}
echo 3 - ${TESTLINK_TESTCASE_JAVA_METHOD}
echo 4 - TESTLINK_TESTCASE_${JAVA_METHOD}
echo 5 - $TESTLINK_TESTCASE_JAVA_METHOD
I got this output:
1 - br.com.cpqd.testeokeanos.unittests.ManterConceitoIncluirTest#deveIncluirConceito
2 -
3 -
4 - TESTLINK_TESTCASE_
5 -
There is a way to debug or print all variables? I need to know if Jenkins can read my values from TestLink.
I see this jira https://issues.jenkins-ci.org/browse/JENKINS-17622 but i think its not related.
Project:
Jenkins
Priority:
Major
Reporter:
gustavo labbate godoy
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-21535) TestLink plugin - cant get custom field values as variables in job
gustavo labbate godoy updated JENKINS-21535 TestLink plugin - cant get custom field values as variables in job Change By: gustavo labbate godoy (28/Jan/14 5:51 PM) Summary: TestLinkplugin-cantget custm custom fieldvaluesasvariablesinjob This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-21535) TestLink plugin - cant get custom field values as variables in job
gustavo labbate godoy
updated JENKINS-21535
TestLink plugin - cant get custom field values as variables in job
Change By:
gustavo labbate godoy
(28/Jan/14 5:52 PM)
Description:
Ihaveajobinjenkisthatmustreadvaluesofthreecustomfieldsintestlink,butreadsonlyone.Theonlyonevariable
readed
read
isthedefaultJavaClass,anyothernewisntread.Herearemyenvironment:Jenkinsversion:1.530TestLinkversion:1.9.4Pluginversion:3.2Thisismyconfiguration,inIterativeBuildsteps.Ifollowtheinstructionsonthepluginsite(https://wiki.jenkins-ci.org/display/JENKINS/TestLink+Plugin)WhenItrytoaccessthevariableslikethat:#!/bin/shecho1-${TESTLINK_TESTCASE_JAVA_CLASS}echo2-${TESTLINK_JAVA_METHOD}echo3-${TESTLINK_TESTCASE_JAVA_METHOD}echo4-TESTLINK_TESTCASE_${JAVA_METHOD}echo5-$TESTLINK_TESTCASE_JAVA_METHODIgotthisoutput:1-br.com.cpqd.testeokeanos.unittests.ManterConceitoIncluirTest#deveIncluirConceito2-3-4-TESTLINK_TESTCASE_5-Thereisawaytodebugorprintallvariables?IneedtoknowifJenkinscanreadmyvaluesfromTestLink.Iseethisjirahttps://issues.jenkins-ci.org/browse/JENKINS-17622butithinkitsnotrelated.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20502) Cannot find any revision to build on clean workspace
David Vo commented on JENKINS-20502 Cannot find any revision to build on clean workspace One small suggestion that worked for me - did you see if your Git plugin was "pinned" (to a previous version) after you upgraded to 2.0.1? I upgraded the plugin and thought I was good to go but as soon as I unpinned it, it worked. I clean the workspace before each build and I no longer see the error above. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [phing] (JENKINS-20835) calling phing long running targets spawn new phing processes enlessly
Frank K commented on JENKINS-20835 calling phing long running targets spawn new phing processes enlessly I'm facing the very same issue on a fresly installed Jenkins on Ubuntu 12.04. Running Phing trough Jenkins results in a massive list of processes, a high load and unresponsive server. Running the exact same command manually on the commandline works just fine and only launches one process. This is quite a serious issue, I can't believe there hasn't been any response whatsoever in the past ~2 months since this issue has been reported! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [phing] (JENKINS-20835) calling phing long running targets spawn new phing processes enlessly
Frank K edited a comment on JENKINS-20835 calling phing long running targets spawn new phing processes enlessly I'm facing the very same issue on a freshly installed Jenkins on Ubuntu 12.04. Running Phing trough Jenkins results in a massive list of processes, a high load and unresponsive server. Running the exact same command manually on the commandline works just fine and only launches one process. This is quite a serious issue, I can't believe there hasn't been any response whatsoever in the past ~2 months since this issue has been reported! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Frank K commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Jenkins uses /tmp by default, tricky but shouldn't matter unless you have cleanup crons/scripts running. I have changed `/etc/default/jenkins` to point the tmp folder somewhere else (/var/lib/jenkins/tmp, /var/run/jenkins and even /opt/jenkins) but even then it loses the static assets (the whole 0.0.0.0--jetty unpacked war!) If I create the mentioned war folder Jenkins fails to even start. Strange stuff... TL;DR: This appears to be something else and not because its in the /tmp folder... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21474) Jenkins crash on startup after upgrade from 1.546 to 1.548
Gautam Jayaprakash updated JENKINS-21474 Jenkins crash on startup after upgrade from 1.546 to 1.548 Really assigning to Kohsuke this time. Kohsuke, it was suggested that I assign this to you for triage in the IRC room. Change By: Gautam Jayaprakash (28/Jan/14 6:21 PM) Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21536) GIT_BRANCH should be set to checkout branch
Milosz Sotomski updated JENKINS-21536 GIT_BRANCH should be set to checkout branch Change By: Milosz Sotomski (28/Jan/14 6:59 PM) Summary: GIT_BRANCHshould notchangeaftermerge besettocheckoutbranch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21536) GIT_BRANCH should not change after merge
Milosz Sotomski created JENKINS-21536 GIT_BRANCH should not change after merge Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 28/Jan/14 6:58 PM Description: I checkout origin/myBranch. Because last commit is also on master branch the GIT_BRANCH is set to master. Project: Jenkins Priority: Major Reporter: Milosz Sotomski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21536) GIT_BRANCH should not change after merge
Milosz Sotomski updated JENKINS-21536 GIT_BRANCH should not change after merge Change By: Milosz Sotomski (28/Jan/14 7:08 PM) Description: Icheckoutorigin/myBranch.BecauselastcommitisalsoonmasterbranchtheGIT_BRANCHissettomaster. SimilarissuewhenIusemergebeforeuseoptionandsetbranchtomergetoGIT_BRANCHissettolatestcommit(inthiscaseorigin/master)notthecheckoutedbranch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21536) GIT_BRANCH should not change after merge
Milosz Sotomski updated JENKINS-21536 GIT_BRANCH should not change after merge Change By: Milosz Sotomski (28/Jan/14 7:05 PM) Summary: GIT_BRANCHshould besettocheckoutbranch notchangeaftermerge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Interesting, I'm similar issues after implementing LTS 1.532.1.2 in Jenkins Enterprise. In my OSS 1.532.1 installation, I don't see this problem. I'm wondering if there is a plug-in conflict of some sort. I enabled the debug mode the majority of time seems to be spent between this two operations: 14:16:34 NOT overriding default server settings, using Mailer to create session 14:16:40 messageContentType = text/html; charset=UTF-8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Isn't that in seconds though? 6 seconds? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [windows-slaves] (JENKINS-21484) Jenkins Windows slave service exe requires .NET 2.0 only. Allow it to work with later .NET versions.
Richard Otter commented on JENKINS-21484 Jenkins Windows slave service exe requires .NET 2.0 only. Allow it to work with later .NET versions. The point of this improvement request is to make creation of a Windows node easier. There is a list of about 20 steps that need to happen before Jenkins and Windows are happy together. Making this simple improvement will eliminate 2 of them. Using the current Jenkins build, trying to connect to a node which does not have the old version of .NET shows a connection log that just hangs on "starting service". Trouble shooting is not straightforward for the novice Jenkins user. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Agreed, in my case the difference is much less extreme, however there is a noticeable difference between my master installations. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) It's possible the Mailer plugin is different between the two installations? What version of the Mailer is on each? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-21266) Unable to clone repository if Multi SCMs and Multi Configuration Project
Chris Bush commented on JENKINS-21266 Unable to clone repository if Multi SCMs and Multi Configuration Project Seconded. Would be great if this could work. I'll have a look at the source code and see if I can poke around with it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21459) Jenkins don't run jobs from queue (there are available executors)
Ronan Araújo commented on JENKINS-21459 Jenkins dont run jobs from queue (there are available executors) Someone has predictive to work on this bug? I my case, the suggested solution by Serj Rashitov will generate a lot of rework. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) I have tried mailer 1.6 and mailer 1.8 on my "slow" installation and both given the same timing effects. I have Mailer 1.6 on my "speedy" installation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Can you provide a dump of all the plugins and their versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21537) Option to use Global User and Password when RTC url is overidden
bbonn created JENKINS-21537 Option to use Global User and Password when RTC url is overidden Issue Type: Improvement Assignee: Unassigned Components: teamconcert Created: 28/Jan/14 8:46 PM Description: Hi there, We are rolling out the plugin in a large environment. One big nuisance for us is the need to enter a user name and password when the "Override global RTC repository connection" box is checked. We use a generic build user and we don't like to give out the password for it. Other SCM plugins will default to the global user and password if the fields are left blank. This would be optimum. Let me know if you need any clarification. Thanks! Environment: Jenkins Master - Windows Server 2008 Slaves - Windows Linux Project: Jenkins Priority: Major Reporter: bbonn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase] (JENKINS-21100) Parametrize config spec configuration
Waldek M commented on JENKINS-21100 Parametrize config spec configuration I concur. Currently it's possible to get the build parameters and generate a config spec, and then set it on the view as a build preparation step. But this way, most of the plugin's benefits are gone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase] (JENKINS-21538) Update the plugin website - screenshots and documentation
Waldek M created JENKINS-21538 Update the plugin website - screenshots and documentation Issue Type: Improvement Affects Versions: current Assignee: Vincent Latombe Components: clearcase Created: 28/Jan/14 9:10 PM Description: The screenshot on https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+Plugin is a bit outdated and especially the Advanced configuration is different under 1.4 plugin. Since the website (and the inline help) is the only source of plugin documentation, it would be really great to have it up to date. Project: Jenkins Priority: Minor Reporter: Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Daniel Barker commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity This issue has been pointed to by the release notes for 1.549, but this is still marked as "In Progress" and "Unresolved." What is the actual status? I'd like to know before I update our instance. Thank you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21457) Replace description in error dialog instead of appending
SCM/JIRA link daemon commented on JENKINS-21457 Replace description in error dialog instead of appending Code changed in jenkins User: Daniel Beck Path: changelog.html http://jenkins-ci.org/commit/jenkins/a4e427123024afa3773e9a44d44e93c94694c5f8 Log: Moved JENKINS-21457 from 1.549 to 1.550 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
akiko_pusu commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity I've also just downloaded and updated to version 1.549, RPM for CentOS jenkins-1.549-1.1.noarch. But it seems there is no change in /etc/default/jenkins and restored directory is still the same, /tmp/jetty-x. So I wonder this issue is fixed or not. My workaround is excluding /tmp/jetty* directory from tmpwatch cron with -X '/tmp/jetty*' option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21539) In groovy postbuild, manager.hudson.rootUrl is null initially but the UI says it's http://localhost:8080
Martin dAnjou created JENKINS-21539 In groovy postbuild, manager.hudson.rootUrl is null initially but the UI says its http://localhost:8080 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 29/Jan/14 12:11 AM Description: When Jenkins is freshly installed, the value printed by the groovy post-build script containing: manager.listener.logger.println(manager.hudson.rootUrl) is null (empty). When going to the Jenkins - Manage Jenkins - Configure System page, the Jenkins Url parameter is set to http://localhost:8080/ Clearly, inside of Jenkins the value is null, but the UI says it is not null (the localhost:8080 is not a null value). Steps to reproduce: 1. Download Jenkins and do a fresh install, and launch 2. Download the Groovy Postbuild plugin 3. Create a freestyle job, add a groovy postbuild step, and paste the one line manager.listener.logger.println(manager.hudson.rootUrl) in the box 4. Run the job, look at the Console, it will say "null" (instead of the Url) 5. Go to the main Jenkins Configuration page http://localhost:8080/configure, scroll to the bottom and save the page 6. Re-run the job, look at the console. The value of manager.hudson.rootUrl is now set. This is a bug because the internal value is null when the UI says it is not. This is an initial condition problem. Environment: linux, jenkins 1.549 Project: Jenkins Priority: Minor Reporter: Martin dAnjou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Christian Höltje commented on JENKINS-20994 Make Just accept and fetch from a build workspace more full featured I currently delete the workspace before and after a build anyway; I don't trust Jazz to clean out the directory. I'd trust if there was a checkbox to reset the workspace to prestine. In "git" lingo that'd be: "git reset; git checkout ; git clean -xfd" So deleting the .jazz directory wouldn't be horrible for me. But it has to hapen at exactly the right time After maven release has finished creating the snapshot and pushing it up, but before it starts building the release copies. re: "well-formed" it is really a convention, I guess... I didn't have a good name for it. But it is any Component that: 1) Only has one directory at the top-level. 2) The directory must match the component name. 3) Has no other files in the top-level. The people in the group seem to think this is a normal convention for RTC. If it isn't, I'd like to hear more. re: automated creation of build definitions Let me explain how I set this up without the build definitions and then explain how I'd automate build definitions... I have several jobs: Create-and-destroy-workspaces: This creates workspaces matching the pattern: Jenkins_(component_name)_(suffix_for_stream). In pseudo-code: For each stream: For each component in stream: create workspace unless workspace exists For each workspace matching /Jenkins_.*/ delete workspace unless stream and component exists List workspaces: Basically, it runs: scm workspaces list --json workspaces.json Build Jobs: For each workspace in workspaces.json: Create job using the Job DSL plugin So what I'd do is add a forth job that would use the workspaces.json and generate the build definitions. Or I could add it in the Create-and-destroy-workspaces job, if needed extra info only available there. I hope that answers your questions. If you want a demo, contact me at IBM. I'm choltje in the US. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Christian Höltje edited a comment on JENKINS-20994 Make Just accept and fetch from a build workspace more full featured I currently delete the workspace before and after a build anyway; I don't trust Jazz to clean out the directory. I'd trust if there was a checkbox to reset the workspace to prestine. In "git" lingo that'd be: "git reset; git checkout ; git clean -xfd" So deleting the .jazz directory wouldn't be horrible for me. But it has to hapen at exactly the right time After maven release has finished creating the snapshot and pushing it up, but before it starts building the release copies. re: "well-formed" it is really a convention, I guess... I didn't have a good name for it. But it is any Component that: 1) Only has one directory at the top-level. 2) The directory must match the component name. 3) Has no other files in the top-level. The people in the group seem to think this is a normal convention for RTC. If it isn't, I'd like to hear more. re: automated creation of build definitions Let me explain how I set this up without the build definitions and then explain how I'd automate build definitions... I have several jobs: Create-and-destroy-workspaces: This creates workspaces matching the pattern: Jenkins_(component_name)_(suffix_for_stream). In pseudo-code: For each stream: For each component in stream: create workspace unless workspace exists For each workspace matching /Jenkins_.*/ delete workspace unless stream and component exists List workspaces: Basically, it runs: scm workspaces list --json workspaces.json Build Jobs: For each workspace in workspaces.json: Create job using the Job DSL plugin So what I'd do is add a forth job that would use the workspaces.json and generate the build definitions. Or I could add it in the Create-and-destroy-workspaces job, if needed extra info only available there. I hope that answers your questions. If you want a demo, contact me at IBM. I'm choltje in the US. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18911) Views should find all jobs that are discoverable OR read (currently only read)
Christian Höltje commented on JENKINS-18911 Views should find all jobs that are discoverable OR read (currently only read) With discoverable, but not read access I would expect: The views would all exist. Each view would have the job names (which link to the jobs pages) Possibly the other columns would exist too or the view would be simplified to only show name. I'm not sure and I'm fine either way. If the user clicked on a job (to go to a job URL) then I would expect them to go to the login page. Does that help? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-21497) Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher
Christian Höltje commented on JENKINS-21497 Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher Fast work! You guys rock! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21532) Broken HTML in job configuration page
Christian Höltje commented on JENKINS-21532 Broken HTML in job configuration page Awesome! Is it possible we can add some sort of HTML static checker for all .jelly to prevent this in the future? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Christian Höltje commented on JENKINS-21483 java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. at com.ibm.team.repository.common.internal.util.ModelElementDescriptor$EvolutionDescriptorComponentVersionComparator.compare(ModelElementDescriptor.java:223) at com.ibm.team.repository.common.internal.util.ModelElementDescriptor$EvolutionDescriptorComponentVersionComparator.compare(ModelElementDescriptor.java:1) at java.util.TreeMap.compare(TreeMap.java:1188) at java.util.TreeMap.put(TreeMap.java:531) at java.util.TreeSet.add(TreeSet.java:255) at com.ibm.team.repository.common.internal.util.ModelElementDescriptor.processEvolutionElement(ModelElementDescriptor.java:70) at com.ibm.team.repository.common.internal.util.ModelElementDescriptor.processChild(ModelElementDescriptor.java:63) at com.ibm.team.repository.common.transport.AbstractElementDescriptor.processChildren(AbstractElementDescriptor.java:725) at com.ibm.team.repository.common.transport.AbstractElementDescriptor.init(AbstractElementDescriptor.java:60) at com.ibm.team.repository.common.internal.util.AbstractComponentChildElementDescriptor.init(AbstractComponentChildElementDescriptor.java:30) at com.ibm.team.repository.common.internal.util.ModelElementDescriptor.init(ModelElementDescriptor.java:47) at com.ibm.team.repository.common.internal.util.ComponentElementDescriptor.processChild(ComponentElementDescriptor.java:262) at com.ibm.team.repository.common.transport.AbstractElementDescriptor.processChildren(AbstractElementDescriptor.java:725) at com.ibm.team.repository.common.transport.AbstractElementDescriptor.init(AbstractElementDescriptor.java:60) at com.ibm.team.repository.common.internal.util.ComponentElementDescriptor.init(ComponentElementDescriptor.java:39) at com.ibm.team.repository.common.internal.util.ComponentRegistry.handleExtensionAdded(ComponentRegistry.java:859) at com.ibm.team.repository.common.internal.util.ComponentRegistry.handleExtensionAdded(ComponentRegistry.java:1) at com.ibm.team.repository.common.util.ExtensionRegistryReader.basicHandleExtensionAdded(ExtensionRegistryReader.java:205) at com.ibm.team.repository.common.util.ExtensionRegistryReader.handleExtensionAddedToRegistry(ExtensionRegistryReader.java:624) at com.ibm.team.repository.common.util.ExtensionRegistryReader.addContributedExtensions(ExtensionRegistryReader.java:143) at com.ibm.team.repository.common.util.ExtensionRegistryReader.start(ExtensionRegistryReader.java:1132) at com.ibm.team.repository.common.util.ExtensionRegistryReader.earlyStart(ExtensionRegistryReader.java:318) at com.ibm.team.repository.common.util.ExtensionRegistryReader.init(ExtensionRegistryReader.java:114) at com.ibm.team.repository.common.internal.util.ComponentRegistry.init(ComponentRegistry.java:75) at com.ibm.team.repository.common.internal.util.ComponentRegistry.clinit(ComponentRegistry.java:47) at com.ibm.team.repository.common.LogFactory.getLog(LogFactory.java:71) at com.ibm.team.repository.client.internal.TeamRepositoryService.clinit(TeamRepositoryService.java:71) at com.ibm.team.repository.client.TeamPlatform.getTeamRepositoryService(TeamPlatform.java:128) at com.ibm.team.build.internal.scm.RepositoryManager.getTeamRepository(RepositoryManager.java:172) at com.ibm.team.build.internal.scm.RepositoryManager.createForUsernameAndPassword(RepositoryManager.java:119) at com.ibm.team.build.internal.hjplugin.rtc.BuildClient.createRepositoryManager(BuildClient.java:149) at com.ibm.team.build.internal.hjplugin.rtc.BuildClient.createRepositoryConnection(BuildClient.java:113) at com.ibm.team.build.internal.hjplugin.rtc.BuildClient.getRepositoryConnection(BuildClient.java:101) at com.ibm.team.build.internal.hjplugin.rtc.RTCFacade.incomingChanges(RTCFacade.java:206) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[JIRA] [teamconcert] (JENKINS-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Christian Höltje commented on JENKINS-21483 java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. I think this is due to using Java 7 java-1.7.0-openjdk-1.7.0.51.x86_64 I just ran across this with the SCMTools which have a similar trackback when run under Java 7. I just switched Jenkins to use Java 6 and the traceback went away. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-21540) NPE while renaming job lost all histories of job
hiteswar kumar created JENKINS-21540 NPE while renaming job lost all histories of job Issue Type: Bug Assignee: Unassigned Components: copyartifact Created: 29/Jan/14 4:46 AM Description: when do rename job by UI, it shows below stacktrace but job is renamed and lost all its previous histories. please share if have already fix of this? action- rename by UI http://JENKINS_SERVER/job/test123_test/doRename stacktrace Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at com.cisco.step.jenkins.plugins.people.redirector.PeopleRedirectorPlugin$1.doFilter(PeopleRedirectorPlugin.java:91) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at
[JIRA] [core] (JENKINS-8423) Slave priority
Dmitry Aleksandrov commented on JENKINS-8423 Slave priority I have found recently developed plugin with this functionality: Scoring Load Balancer plugin https://wiki.jenkins-ci.org/display/JENKINS/Scoring+Load+Balancer+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] [copyartifact] (JENKINS-21540) NPE while renaming job
hiteswar kumar updated JENKINS-21540 NPE while renaming job Change By: hiteswar kumar (29/Jan/14 7:08 AM) Summary: NPEwhilerenamingjob lostallhistoriesofjob Description: whendorenamejobbyUI,itshowsbelowstacktracebutjobisrenamed andlostallitsprevioushistories. pleaseshareifhavealreadyfixofthis?action-renamebyUIhttp://JENKINS_SERVER/job/test123_test/doRenamestacktraceStatusCode:500Exception:java.lang.NullPointerExceptionStacktrace:javax.servlet.ServletException:java.lang.NullPointerException atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:659) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:659) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:659) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:488) atorg.kohsuke.stapler.Stapler.service(Stapler.java:162) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:717) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) atnet.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) atnet.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) atorg.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) atcom.cisco.step.jenkins.plugins.people.redirector.PeopleRedirectorPlugin$1.doFilter(PeopleRedirectorPlugin.java:91) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
[JIRA] [maven] (JENKINS-21541) After I upgrade to 1.547, Maven Build fails with ERROR: Failed to parse POMs java.net.SocketException: Connection reset
Senthil Kumar Chandran created JENKINS-21541 After I upgrade to 1.547, Maven Build fails with ERROR: Failed to parse POMs java.net.SocketException: Connection reset Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Jenkins_Image.JPG Components: maven Created: 29/Jan/14 7:19 AM Description: Recently, i've upgraded the Jenkins from 1.532 to 1.547, but after upgradation, Maven build alone fails with the following reason, if i restart the Jenkins, build is getting succeeded but it fails after some time (say fails after 5 hours) and also some of the image is not visible (attached screenshot) /eas/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.4.jar:/eas/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /eas/jenkins/home/tools/hudson.tasks.Maven_MavenInstallation/3.0.4 /tmp/jetty-0.0.0.0-8080-jenkins.war-any/webapp/WEB-INF/lib/remoting-2.33.jar /eas/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.4.jar /eas/jenkins/home/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar 51932 Exception in thread "main" java.lang.ClassNotFoundException: hudson.remoting.Launcher at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:135) at org.jvnet.hudson.maven3.agent.Maven3Main.main(Maven3Main.java:64) ERROR: Failed to parse POMs java.net.SocketException: Connection reset at java.net.SocketInputStream.read(Unknown Source) at java.io.FilterInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at hudson.remoting.ClassicCommandTransport.create(ClassicCommandTransport.java:133) at hudson.remoting.Channel.init(Channel.java:406) at hudson.remoting.Channel.init(Channel.java:402) at hudson.remoting.Channel.init(Channel.java:363) at hudson.remoting.Channel.init(Channel.java:359) at hudson.remoting.Channel.init(Channel.java:355) at hudson.slaves.Channels$1.init(Channels.java:71) at hudson.slaves.Channels.forProcess(Channels.java:71) at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:253) at hudson.maven.ProcessCache.get(ProcessCache.java:235) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:749) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) at hudson.model.Run.execute(Run.java:1678) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Archiving artifacts Finished: FAILURE Due Date: 29/Jan/14 12:00 AM Environment: Maven 2, Project: Jenkins Labels: jenkins Priority: Major Reporter: Senthil Kumar Chandran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] [core] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Joël Royer commented on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated Issue is still present in 1.549!!! I have a nested view, with one sub-view (type list view). Admin users can see nested view and its sub-view, and all jobs associated with it. Ragulars users (with only Global Read permission), can't see the nested view. But they can see jobs in the tab "All". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
