[JIRA] [maven] (JENKINS-18922) Upgrading to 1.524 ("Upgrade Automatically") breaks jenkins
Rene Hess
commented on JENKINS-18922
Upgrading to 1.524 ("Upgrade Automatically") breaks jenkins
I saw a similar behaviour, but not with Maven, but with the Git plugin.
Removing the Git plugin solved it, too.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18878) Gerrit-trigger-plugin does not trigger jobs at all when the connection is unavailable to Jenkins server
Joel Huttunen updated JENKINS-18878 Gerrit-trigger-plugin does not trigger jobs at all when the connection is unavailable to Jenkins server Change By: Joel Huttunen (26/Jul/13 6:52 AM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18925) broken "Slaves statistics" Dashboard Portlet, displaying raw makeStaplerProxy() javascript function instead of numbers
Rene Hess commented on JENKINS-18925 broken "Slaves statistics" Dashboard Portlet, displaying raw makeStaplerProxy() _javascript_ function instead of numbers Same problem here. Build statistics working correctly, though This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18641) People View does Not Populate (makeStaplerProxy)
Yves Schumann edited a comment on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Right, still existing on 1.524 running on Ubuntu 12.04 and accessed with Chrome, FF, Safari and IE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18641) People View does Not Populate (makeStaplerProxy)
Yves Schumann commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Right, still existing on 1.524 running on Ubuntu 12.04 and accessed with Chrome, FF and IE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18879) Collecting finbugs analysis results randomly fails with exception
Ramin Baradari commented on JENKINS-18879 Collecting finbugs analysis results randomly fails with exception I downgraded our installation to Jenkins ver. 1.521 but the problem still occurred over night. Jenkins SSH Slaves plugin is at 0.27 Static Analysis Utilities is at 1.50 FindBugs Plug-in is at 4.49 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
kevin ran commented on JENKINS-18667 NullPointerException when saving job config A shame. I actually need BuildResultTrigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18927) Builds disappear from build history after completion
James li commented on JENKINS-18927 Builds disappear from build history after completion Add a comment: 7.The job was been renamed via page which has this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13314) Remote API does not include downstream/upstream build info
Jonathan Yen commented on JENKINS-13314 Remote API does not include downstream/upstream build info Will someone be able to work on this? It would be helpful to have. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [violations] (JENKINS-17548) FxCop results not being displayed for non-source files
Ryan Davis commented on JENKINS-17548 FxCop results not being displayed for non-source files I'm experiencing something similar, here's my analysis. For me, FxCop generates messages at three levels: Namespace, Module (dll), Type, and Method. In the initial fxcop xml output, these are all all represented by blocks, potentially inside , , , and , elements depending on what the message is. The elements inside elements have Path, File, and Line attributes; for me these come through to the Violations plugin no problem. If I have something like: Make 'LogFilterAttribute' sealed ... Then the violations report will list src/Core/Logging.cs properly in the table, and I can click on it and see the issue on the right line as normal. The problem happens when the doesn't have the file information. For me, this happens a lot: ... "TestController" ...> "#A" ...> "#B" ...> In some cases, FxCop can't figure out where some code is, and if fxcop doesn't know, then the Violations plugin doesn't know. From http://blogs.msdn.com/b/codeanalysis/archive/2007/05/12/faq-why-is-file-and-line-information-available-for-some-warnings-in-fxcop-but-not-for-others.aspx: FxCop and Visual Studio Code Analysis both use the information stored in the Program Database (PDB) file to map members back to a particular source file. Unfortunately, because this file was orginally only designed for use by a debugger, it only contains information about actual executable code. This means that FxCop cannot find non-executable code such as namespaces, types, fields, interface methods and abstract methods. So the root problem here is that FxCop is reflecting on assemblies instead of parsing source code (like every other lint tool). That's the source of a lot of the "blank" pages; FxCop can't determine a source location, so it can't tell Violations. Also, some C# elements can't really have a source file... what would be the right source file for the warning about "don't put underscores in your namespace"? I think it's possible to apply some heuristics to find a reasonable source file, but that'd be on a warning-by-warning basis, and that's really FxCop's job. My best bet would be to modify the violations plugin to: show violations even when there is no source - just print a table of the violations if there's no file - change FileModelProxy.getFileContent to check if fileModel.getLines has any entries, and if not render a different table of just the violations. change the fxcop parser; when it sees file information, remember it for that type. In FxCopParser.parseIssue call something like model.getFileModel(parentName).setSourceFile(sourceFile) (with null checks). This would still fail for partial classes and namespaces, but would catch the most common cases. If I can get a java dev environment going and steal more time I'll try to get a couple of pull requests on github to cover these. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [violations] (JENKINS-12955) Stylecop file report is blank
Ryan Davis commented on JENKINS-12955 Stylecop file report is blank Actually, after reading more closely I think I'm chasing a similar FxCop bug, and everyone else here is chasing a StyleCop bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18930) Missing TestResultColumn() constructor
Fred G assigned JENKINS-18930 to Greg Nion Missing TestResultColumn() constructor Change By: Fred G (25/Jul/13 11:16 PM) Assignee: Fred G Greg Nion This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [violations] (JENKINS-12955) Stylecop file report is blank
Ryan Davis commented on JENKINS-12955 Stylecop file report is blank I'm experiencing something similar, but I think I found a pattern. For me, FxCop generates messages at three levels: Namespace, Module (dll), Type, and Method. In the initial fxcop xml output, these are all all represented by blocks, potentially inside , , , and , elements depending on what the message is. The elements inside elements have Path, File, and Line attributes; for me these come through to the Violations plugin no problem. If I have something like: Make 'LogFilterAttribute' sealed ... Then the violations report will list src/Core/Logging.cs properly in the table, and I can click on it and see the issue on the right line as normal. The problem happens when the doesn't have the file information. For me, this happens a lot: ... "TestController" ...> "#A" ...> "#B" ...> In some cases, FxCop can't figure out where some code is, and if fxcop doesn't know, then the Violations plugin doesn't know. From http://blogs.msdn.com/b/codeanalysis/archive/2007/05/12/faq-why-is-file-and-line-information-available-for-some-warnings-in-fxcop-but-not-for-others.aspx: FxCop and Visual Studio Code Analysis both use the information stored in the Program Database (PDB) file to map members back to a particular source file. Unfortunately, because this file was orginally only designed for use by a debugger, it only contains information about actual executable code. This means that FxCop cannot find non-executable code such as namespaces, types, fields, interface methods and abstract methods. So the root problem here is that FxCop is reflecting on assemblies instead of parsing source code (like every other lint tool). That's the source of a lot of the "blank" pages; FxCop can't determine a source location, so it can't tell Violations. Also, some C# elements can't really have a source file... what would be the right source file for the warning about "don't put underscores in your namespace"? I think it's possible to apply some heuristics to find a reasonable source file, but that'd be on a warning-by-warning basis, and that's really FxCop's job. My best bet would be to modify the violations plugin to: show violations even when there is no source - just print a table of the violations if there's no file - change FileModelProxy.getFileContent to check if fileModel.getLines has any entries, and if not render a different table of just the violations. change the fxcop parser; when it sees file information, remember it for that type. In FxCopParser.parseIssue call something like model.getFileModel(parentName).setSourceFile(sourceFile) (with null checks). This would still fail for partial classes and namespaces, but would catch the most common cases. If I can get a java dev environment going and steal more time I'll try to get a couple of pull requests on github to cover these. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18930) Missing TestResultColumn() constructor
Fred G commented on JENKINS-18930 Missing TestResultColumn() constructor Here is a test version that contains the fix: https://jenkins.ci.cloudbees.com/job/plugins/job/extra-columns-plugin/ws/target/extra-columns.hpi Can you confirm that it works? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clang-scanbuild] (JENKINS-18941) Not possible to set report directory used by Clang-Scan publisher
Brian Bassett created JENKINS-18941 Not possible to set report directory used by Clang-Scan publisher Issue Type: Bug Affects Versions: current Assignee: Josh Kennedy Components: clang-scanbuild Created: 25/Jul/13 11:02 PM Description: The Clang-Scan publisher looks for its reports in a hardcoded directory ($WORKSPACE/clangScanBuildReports). I have a requirement that all generated artifacts (including the report from scan-build) be created in a top-level build directory. Please make the publisher configurable to be able to specify the location or the reports (having it default to $WORKSPACE/clangScanBuildReports is perfectly reasonable). Environment: Jenkins 1.524 Clang Scan-Build Plugin 1.4 Project: Jenkins Priority: Minor Reporter: Brian Bassett This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [port-allocator] (JENKINS-18786) Port allocation blocks jobs from executing concurrently
SCM/JIRA link daemon commented on JENKINS-18786 Port allocation blocks jobs from executing concurrently Code changed in jenkins User: pepov Path: src/main/java/org/jvnet/hudson/plugins/port_allocator/PortAllocator.java http://jenkins-ci.org/commit/port-allocator-plugin/4af186b01585328bf0ae3299018f9872784c01d9 Log: JENKINS-18786 remove ResourceActivity, that blocks jobs on different slaves This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Johno Crawford commented on JENKINS-18848 Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin Please try 1.23.2 and let me know if the above mentioned issues are now resolved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18940) {wl.source} command line override token doesn't get replaced
Jeremy Love
created JENKINS-18940
{wl.source} command line override token doesn't get replaced
Issue Type:
Bug
Assignee:
Raphael CHAUMIER
Components:
weblogic-deployer
Created:
25/Jul/13 10:24 PM
Description:
When using the command line override feature, the {wl.source} token isn't replaced at execution. The literal string "{wl.source}" remains as a command line argument.
WebLogic Deployment Command Line:
-user {wl.login} -password {wl.password} -debug -verbose -stage -remote -upload -source {wl.source} -targets {wl.targets} -adminurl t3s://{wl.host}:{wl.port} -deploy
Logs from build:
[WeblogicDeploymentPlugin] - Deploying the artifact on the following target : (name=myserver) (host=localhost) (port=7002)
[WeblogicDeploymentPlugin] - EXECUTING TASK ...
$ C:\PROGRA~1\Java\JDK17~1.0_0\bin/java -Xms128M -Xmx256M -cp C:\oracle\MIDDLE~1\1212~1.0\wlserver/server/lib/weblogic.jar weblogic.Deployer -user weblogic -password welcome1 -debug -verbose -stage -remote -upload -source {wl.source} -targets myserver -adminurl t3s://localhost:7002 -deploy
ERROR: [WeblogicDeploymentPlugin] - Command C:\PROGRA~1\Java\JDK17~1.0_0\bin/java|-Xms128M|-Xmx256M|-cp|C:\oracle\MIDDLE~1\1212~1.0\wlserver/server/lib/weblogic.jar|weblogic.Deployer|-user|weblogic|-password|welcome1|-debug|-verbose|-stage|-remote|-upload|-source|{wl.source}|-targets|myserver|-adminurl|t3s://localhost:7002|-deploy completed abnormally (exit code = 1)
Project:
Jenkins
Priority:
Major
Reporter:
Jeremy Love
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [port-allocator] (JENKINS-18786) Port allocation blocks jobs from executing concurrently
Peter Wilcsinszky assigned JENKINS-18786 to Richard Mortimer Port allocation blocks jobs from executing concurrently Change By: Peter Wilcsinszky (25/Jul/13 10:05 PM) Assignee: Peter Wilcsinszky Richard Mortimer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [port-allocator] (JENKINS-18786) Port allocation blocks jobs from executing concurrently
Peter Wilcsinszky commented on JENKINS-18786 Port allocation blocks jobs from executing concurrently With pull request 4 it will be ok with pooled ports too, I've just tested it. Please merge that and release it as well! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18930) Missing TestResultColumn() constructor
SCM/JIRA link daemon resolved JENKINS-18930 as Fixed Missing TestResultColumn() constructor Change By: SCM/JIRA link daemon (25/Jul/13 10:03 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18930) Missing TestResultColumn() constructor
SCM/JIRA link daemon commented on JENKINS-18930 Missing TestResultColumn() constructor Code changed in jenkins User: Fred G Path: src/main/java/jenkins/plugins/extracolumns/ConfigureProjectColumn.java src/main/java/jenkins/plugins/extracolumns/DescriptionColumn.java src/main/java/jenkins/plugins/extracolumns/DisableProjectColumn.java src/main/java/jenkins/plugins/extracolumns/LastBuildConsoleColumn.java src/main/java/jenkins/plugins/extracolumns/TestResultColumn.java http://jenkins-ci.org/commit/extra-columns-plugin/15c3a251d5fbcc79e6c4d6e1d6b36745a0728eb4 Log: [FIXED JENKINS-18930] Missing TestResultColumn() constructor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18930) Missing TestResultColumn() constructor
Fred G started work on JENKINS-18930 Missing TestResultColumn() constructor Change By: Fred G (25/Jul/13 9:58 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sauce-ondemand] (JENKINS-18939) Add Appium device options
Ross Rowe created JENKINS-18939 Add Appium device options Issue Type: Improvement Assignee: Ross Rowe Components: sauce-ondemand Created: 25/Jul/13 9:41 PM Project: Jenkins Priority: Major Reporter: Ross Rowe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18938) COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names
Martin d'Anjou created JENKINS-18938 COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: copyartifact Created: 25/Jul/13 9:20 PM Description: The COPYARTIFACT_BUIL_NUMBER_ variable name does not preserve numbers in job names. It removes numbers from job names. For example, if the job is called martin-test1, then the variable name name is: COPYARTIFACT_BUILD_NUMBER_MARTIN_TEST_ (the number has been removed) To reproduce: create a job whose name has a number in it, e.g. martin-test1 run the job once to create some artifacts, and archive them create another job whose purpose is to copy the artifacts from the first job in the build phase of the second job, print the environment variables, e.g. with env, and examine the COPYARTIFACT_BUILD_NUMBER_ variable name. It should be missing the numbers This was tested in Jenkins 1.524, with version 1.27 of the Copy Artifacts plugin. Environment: Linux Project: Jenkins Priority: Major Reporter: Martin d'Anjou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18937) Add DSL support for the Timestamper plugin
wolfs created JENKINS-18937 Add DSL support for the Timestamper plugin Issue Type: Bug Assignee: Justin Ryan Components: job-dsl-plugin Created: 25/Jul/13 9:09 PM Description: Support https://wiki.jenkins-ci.org/display/JENKINS/Timestamper. Project: Jenkins Priority: Minor Reporter: wolfs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jacoco] (JENKINS-16790) Link from Dashboard to coverage report
centic resolved JENKINS-16790 as Fixed Link from Dashboard to coverage report Should be fixed in next version of the jacoco plugin. Change By: centic (25/Jul/13 9:05 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] [postbuildscript] (JENKINS-18936) checkbox is not staying checked
Matthew Stoltenberg updated JENKINS-18936 checkbox is not staying checked Change By: Matthew Stoltenberg (25/Jul/13 8:48 PM) Summary: checkbox is not staying checked This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [postbuildscript] (JENKINS-18936) checkbox is staying checked
Matthew Stoltenberg created JENKINS-18936 checkbox is staying checked Issue Type: Bug Assignee: Gregory Boissinot Components: postbuildscript Created: 25/Jul/13 8:48 PM Description: I configure a script to run in Post-build on if the build fails. Next time I open the configuration for that job, the checkbox is unchecked. Project: Jenkins Priority: Major Reporter: Matthew Stoltenberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
Gavin Swanson resolved JENKINS-18338 as Not A Defect Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." I believe that although this is a communication/documentation issue it is in fact not a bug. The main problem here is the addition of the new permission requirements in gerrit which makes this not a Jenkins bug. The secondary problem which may require it's own bug (on Gerrit or Gerrit Trigger) is the potential issue with the --verified flag no longer working. Change By: Gavin Swanson (25/Jul/13 8:05 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
Gavin Swanson commented on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." I upgraded from gerrit 2.5 to gerrit 2.7 via 2.6 (was only running 2.6 for a day or so). The only change I've made to the configuration of the way Gerrit and Jenkins interact is to add the Stream Events permission. Once that was added everything started working again. I have not had to make any changes to the Gerrit Trigger lines that actually mark things as verified, etc. Although this permission is documented it would have been nice to see something in the Release notes that called out this sort of interaction as requiring 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] [git] (JENKINS-18303) Cannot do checkout of a git repository in BitBucket in Jenkins
Evan Brunner commented on JENKINS-18303 Cannot do checkout of a git repository in BitBucket in Jenkins I spent a day on a similar issue with the exact same symptoms. I think it's more than likely related to your ssh setup re::known_hosts. There's no good debug feedback on this issue from jenkins - it just hangs indefinitely an doesn't tell you whether or not the clone is being executed. Here's the stackOverflow answer that set me in the right direction. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18934) Latest install of version 1.524 disables Maven
Amir Raminfar resolved JENKINS-18934 as Postponed Latest install of version 1.524 disables Maven Change By: Amir Raminfar (25/Jul/13 6:53 PM) Status: Open Resolved Resolution: Postponed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18934) Latest install of version 1.524 disables Maven
Amir Raminfar commented on JENKINS-18934 Latest install of version 1.524 disables Maven OK so here is some update. I completely removed the plugins directory and was able to get version 1.524 working. I will resolve this ticket but not close because it might need to be looked at. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Matt Legrand created JENKINS-18935 Make Subversion plugin support Subversion 1.8 Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: subversion Created: 25/Jul/13 6:38 PM Description: Subversion 1.8 is available but the SVN plugin doesn't support it. For example, Configure|Subversion Workspace Version only offers 1.4 thru 1.7. https://issues.jenkins-ci.org/browse/JENKINS-18844 is related. Environment: All Project: Jenkins Priority: Major Reporter: Matt Legrand This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-18920) [JobConfigurationHistory] Keep history only for existing builds
Kathi Stutz updated JENKINS-18920 [JobConfigurationHistory] Keep history only for existing builds Change By: Kathi Stutz (25/Jul/13 6:35 PM) Priority: Major Minor Description: As of today, the maximum number of history entries can be limited by numbers or "days to keep".It would be nice if there was an option to keep only the configurations that jobs builds exist for (plus maybe one older configuration).If there are builds being discarded in Jenkins because of "max # of builds to keep", the job configurations should be discarded as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18934) Latest install of version 1.524 disables Maven
Amir Raminfar edited a comment on JENKINS-18934 Latest install of version 1.524 disables Maven I was able to fetch v1.523 and use dpkg to install older version. My jobs are back up. Edit - I was wrong. Trying to build a job fails. I see there is an update to maven plugin. Trying to update to see if that works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18934) Latest install of version 1.524 disables Maven
Amir Raminfar commented on JENKINS-18934 Latest install of version 1.524 disables Maven I was able to fetch v1.523 and use dpkg to install older version. My jobs are back up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18934) Latest install of version 1.524 disables Maven
Amir Raminfar updated JENKINS-18934 Latest install of version 1.524 disables Maven Change By: Amir Raminfar (25/Jul/13 6:06 PM) Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18934) Latest install of version 1.524 disables Maven
Amir Raminfar created JENKINS-18934 Latest install of version 1.524 disables Maven Issue Type: Bug Assignee: Unassigned Components: maven Created: 25/Jul/13 6:02 PM Description: The latest version upgrade has completely disabled all my maven jobs. Attempting to create a new job does not work because maven plugin is disabled. Reinstalling does not work. I cannot downgrade. Logs are at https://gist.github.com/amir20/6082188 Marking this as critical as it has completely stopped our build system. Project: Jenkins Priority: Critical Reporter: Amir Raminfar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
Simon Watts commented on JENKINS-18667 NullPointerException when saving job config I had the same stack trace when trying to save jobs that had BuildResultTrigger configured This problem occurred in Jenkins 1.522 and 1.523 on CentOS - I tried downgrading to 1.521 but still had the same problem I've removed BuildResultTrigger for now and that fixes 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] [hockeyapp] (JENKINS-17807) HockeyAppRecorder.getProjectActions throws NullPointerException
Jeff Ishaq commented on JENKINS-17807 HockeyAppRecorder.getProjectActions throws NullPointerException There appears to be two different places for logging issues for this plugin. This one here, and one on github. I have just crossposted this defect on github here in hopes that it gets noticed: https://github.com/ohoeltke/hockeyapp-plugin/issues/2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18828) Jobs disappear
Joe Mihalich edited a comment on JENKINS-18828 Jobs disappear This problem happened to me when i upgraded from 522 to 524 yesterday. Restoring to 522 fixed the problem. I also have projects with display names with spaces and dashes in them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18828) Jobs disappear
Joe Mihalich commented on JENKINS-18828 Jobs disappear This problem happened to me when i upgraded from 522 to 524 yesterday. Restoring to 522 fixed the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [violations] (JENKINS-17722) Violations Codenarc Parser doesn't respect SourceDirectory XML tag
Sune Wettersteen commented on JENKINS-17722 Violations Codenarc Parser doesn't respect SourceDirectory XML tag Looks like there has been quite some activity on this. Any idea when this fix will be released with a plugin update? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-7823) Wrong Permission of slave workspace
Tony Panza commented on JENKINS-7823 Wrong Permission of slave workspace I have sponsored a bounty for this issue on Freedom Sponsors: http://www.freedomsponsors.org/core/issue/307/wrong-permission-of-slave-workspace This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18929) OutOfMemoryError: PermGen space
David Ishee updated JENKINS-18929 OutOfMemoryError: PermGen space Change By: David Ishee (25/Jul/13 4:52 PM) Environment: Jenkins 1.509.2Standalone Jelly serviceRed Hat Enterprise Linux Server release 5.9 (Tikanga)java -versionjava version "1.6.0_17"Java(TM) SE Runtime Environment (build 1.6.0_17-b04)Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode) Using -Xmx1500M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-14713) Cancel permission is granted for users having build permission
Hangsu Ma commented on JENKINS-14713 Cancel permission is granted for users having build permission pull request here: https://github.com/jenkinsci/jenkins/pull/882 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-18745) Add support of "MailAddressResolver" in the Ownership plugin
Oleg Nenashev resolved JENKINS-18745 as Fixed Add support of "MailAddressResolver" in the Ownership plugin Merged MailAddressResolver into the main branch. Old solution has been removed. Change By: Oleg Nenashev (25/Jul/13 4:21 PM) Status: In Progress 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] [ownership] (JENKINS-18745) Add support of "MailAddressResolver" in the Ownership plugin
Oleg Nenashev assigned JENKINS-18745 to Oleg Nenashev Add support of "MailAddressResolver" in the Ownership plugin Change By: Oleg Nenashev (25/Jul/13 4:20 PM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-18740) Add support of co-owners
Oleg Nenashev assigned JENKINS-18740 to Oleg Nenashev Add support of co-owners Change By: Oleg Nenashev (25/Jul/13 4:20 PM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-18740) Add support of co-owners
Oleg Nenashev resolved JENKINS-18740 as Fixed Add support of co-owners Merged pull request into main branch Change By: Oleg Nenashev (25/Jul/13 4:20 PM) Status: In Progress 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] [ownership] (JENKINS-18738) Add integration with security plugins (Target: Role Strategy Plugin)
Oleg Nenashev resolved JENKINS-18738 as Fixed Add integration with security plugins (Target: Role Strategy Plugin) https://github.com/jenkinsci/ownership-plugin/pull/2 Change By: Oleg Nenashev (25/Jul/13 4:19 PM) Status: In Progress 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] [ownership] (JENKINS-18738) Add integration with security plugins (Target: Role Strategy Plugin)
Oleg Nenashev started work on JENKINS-18738 Add integration with security plugins (Target: Role Strategy Plugin) Change By: Oleg Nenashev (25/Jul/13 4:19 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-18738) Add integration with security plugins (Target: Role Strategy Plugin)
Oleg Nenashev assigned JENKINS-18738 to Oleg Nenashev Add integration with security plugins (Target: Role Strategy Plugin) Change By: Oleg Nenashev (25/Jul/13 4:19 PM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-18744) Expose ownership variables to the build environmanet
Oleg Nenashev commented on JENKINS-18744 Expose ownership variables to the build environmanet Will be merged into 0.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-18744) Expose ownership variables to the build environmanet
Oleg Nenashev resolved JENKINS-18744 as Fixed Expose ownership variables to the build environmanet https://github.com/jenkinsci/ownership-plugin/pull/3 Change By: Oleg Nenashev (25/Jul/13 4:09 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] [coverity] (JENKINS-18933) JNA version needs upgrade to avoid conflicts in /tmp when building
Eric Hawicz
created JENKINS-18933
JNA version needs upgrade to avoid conflicts in /tmp when building
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
coverity
Created:
25/Jul/13 3:57 PM
Description:
When building the coverity-plugin on a machine where someone else has already built it, the tests fail to run with:
java.lang.Error: Failed to create temporary file for jnidispatch library: java.io.IOException: Permission denied
This is because a /tmp/jna directory is created owned by the first user that did the build. Apparently, a new version of JNA fixes this and creates /tmp/jna-${user} instead, so "something" needs to be changed to update that.
http://issues.tmatesoft.com/issue/SGT-475 talks about a similar issue.
Project:
Jenkins
Priority:
Minor
Reporter:
Eric Hawicz
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-18933) JNA version needs upgrade to avoid conflicts in /tmp/jna when building
Eric Hawicz updated JENKINS-18933 JNA version needs upgrade to avoid conflicts in /tmp/jna when building Change By: Eric Hawicz (25/Jul/13 3:58 PM) Summary: JNA version needs upgrade to avoid conflicts in /tmp /jna when building This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18907) Add feature to expose the latest revision number of a checkout
Kevin Phillips edited a comment on JENKINS-18907 Add feature to expose the latest revision number of a checkout Also, in response to this other earlier comment, while I do agree the plugin is working as intended, the use cases I describe in my earlier comments illustrate the need for accessing the latest revision instead of / as well as the last changed revision. These revisions serve different purposes for different use cases - which is why the SVN tools expose them both to the user as needed. To relate this request to functionality in the standard SVN client toolset, currently the SVN plugin exposes the revision generated by the command "svnversion . -c" but I would also like the ability to get the results of "svnversion ." as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18907) Add feature to expose the latest revision number of a checkout
Kevin Phillips commented on JENKINS-18907 Add feature to expose the latest revision number of a checkout Also, in response to this other earlier comment, while I do agree the plugin is working as intended, the use cases I describe in my earlier comments illustrate the need for accessing the latest revision instead of / as well as the last changed revision. These revisions serve different purposes for different use cases - which is why the SVN tools expose them both to the user as need. To relate this request to functionality in the standard SVN client toolset, currently the SVN plugin exposes the revision generated by the command "svnversion . -c" but I would also like the ability to get the results of "svnversion ." as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18292) Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path
Heather Fraser-Dube commented on JENKINS-18292 Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path Created a work item in jazz.net corresponding to this issue. 274151: Absolute path in build definition is treated as a relative path by Jenkins 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] [subversion] (JENKINS-18932) Problems updating subversion plugin/starting Jenkins
Wolfgang Grossinger created JENKINS-18932 Problems updating subversion plugin/starting Jenkins Issue Type: Bug Assignee: Unassigned Components: subversion Created: 25/Jul/13 3:32 PM Description: We are running Jenkins on Windows 7 on WebSphere 7 and have a mutitude of problems with updating plugins because of one thing, as it seems. In .jenkins\plugins\subversion\WEB-INF\lib there is antlr-runtime-3.4.jar which is locket in some way when Jenkis tries to update subversion. I am not sure if this is a special problem of Windows/WebSphere but because of this, we have also Problems after updating other plugins or restarting Jenkins - the plugins are just not available and if you don't be careful, you lose all your subversion settings and can reconfigure subversion manually again. It would be very helpful if the update/plugin-start process would be a little bit more fault tolerant, so that not everything else is omittet after a restart especially as it seems that this specific jar is absolutely irrelevant and not changed during the update. We have also weird results after such an issue that Jenkins is somehow set back to older versions of plugins we already had installed successfully. Environment: Windows 7 64 bit / WebSphere 7 Project: Jenkins Priority: Major Reporter: Wolfgang Grossinger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18907) Add feature to expose the latest revision number of a checkout
Kevin Phillips commented on JENKINS-18907 Add feature to expose the latest revision number of a checkout In response to this earlier comment, while I think it may be helpful in certain cases to expose the revisions of any / all externals to Jenkins builds, to help limit the scope of this particular enhancement request (and possibly to keep the resulting changes as generic and generally applicable as possible) I think it will suffice to simply expose the "latest" SVN revision for a checkout to the build environment as mentioned in the description. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18658) NPE in FSTrigger upon configuration save
David MacBride commented on JENKINS-18658 NPE in FSTrigger upon configuration save The stack trace is different that in JENKINS-18667. In the issue reported in 18658 the stack treace says: Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.fstrigger.triggers.FileNameTrigger.getLogFile(FileNameTrigger.java:65) Perhaps it is an issue in a common parent class. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clone-workspace] (JENKINS-6890) clone-workspace-scm doesn't work when source job is a matrix job.
Peter Kovacs commented on JENKINS-6890 clone-workspace-scm doesn't work when source job is a matrix job. Thanks, will try. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clone-workspace] (JENKINS-6890) clone-workspace-scm doesn't work when source job is a matrix job.
Uladzimir Mihura updated JENKINS-6890 clone-workspace-scm doesn't work when source job is a matrix job. You can try this. Just build from my repo. Change By: Uladzimir Mihura (25/Jul/13 3:08 PM) Attachment: clone-workspace-scm.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
Piotr Szwed edited a comment on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." @rin_ne - I think that the custom command feature in management page would be the best idea, it allows to integrate the plugin even with modified Gerrit workflows which are very different that the default one (all the labels and values (+1,+2,+3..) are customizable in Gerrit). However.. "ssh gerrit gerrit review --label Verified=1" -does not work too with 2.7, with 2.6 it works like expected. "ssh gerritblr gerrit review --label Code-Review=2" -works fine on both, 2.6 and 2.7 Seems like a bug in Gerrit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clone-workspace] (JENKINS-6890) clone-workspace-scm doesn't work when source job is a matrix job.
Uladzimir Mihura edited a comment on JENKINS-6890 clone-workspace-scm doesn't work when source job is a matrix job. You can try this: clone-workspace-scm.hpi Just build from my repo. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buildresult-trigger] (JENKINS-18931) Build is triggered incorrectly when a triggered build starts running
teilo
created JENKINS-18931
Build is triggered incorrectly when a triggered build starts running
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
buildresult-trigger, buildresulttrigger
Created:
25/Jul/13 3:05 PM
Description:
if the buildresult is set to trigger with a schedule of every minute
(* * * * ) and you have a long runnign upstream job, the job with a trigger will trigger when the upstream job **starts building*
This appears to be due to a Null POinter Exception as the trigger gets the status of the LastBuild - but the lastBuild may be currently building and return a null status.
see private boolean isMatchingExpectedResults(String jobName, CheckedResult[] expectedResults, XTriggerLog log) in src/main/java/org/jenkinsci/plugins/buildresulttrigger/BuildResultTrigger.java
Polling started on Jul 25, 2013 2:47:53 PM
Polling for the job cms-at_master-LEVEL-1
Looking nodes where the poll can be run.
Looking for a candidate node to run the poll.
Trying to find an eligible node with the assigned project label RH53_ATC.
Polling remotely on cabci-cf-rh53-x64-atc01
Checking changes for job CMS/cms-subsystem/cms-subsystem/commit.
There are no new builds for the job CMS/cms-subsystem/cms-subsystem/commit.
Checking changes for job CMS/vcm/vcm-app/commit.
There is at least one new build for the job CMS/vcm/vcm-app/commit. Checking expected job build results.
Checking SUCCESS
[ERROR] - Polling error...
See also the output from the script console
AbstractProject jobObj = Hudson.getInstance().getItemByFullName("CMS/vcm/vcm-app/commit/", AbstractProject.class);
Run jobObjLastBuild = jobObj.getLastBuild();
Result jobObjectLastResult = jobObjLastBuild.getResult();
println("run: " + jobObjLastBuild.number);
println("status: " + jobObjLastBuild.result);
println("isBuilding: " + jobObjLastBuild.building);
run: 1089
status: null
isBuilding: true
The polling error then causes a build to be triggered which will trigger the build prematurely and when the build has finished the build will not be triggered.
Environment:
jenkins 1.509.2
build result trigger 0.12
Project:
Jenkins
Priority:
Blocker
Reporter:
teilo
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." @rin_ne - I think that the custom command feature in management page would be the best idea, it allows to integrate the plugin even with customized Gerrit workflows which is different that the default one (all the labels and values (+1,+2,+3..) are customizable in Gerrit). However.. "ssh gerrit gerrit review --label Verified=1" -does not work too with 2.7, with 2.6 it works like expected. "ssh gerritblr gerrit review --label Code-Review=2" -works fine on both, 2.6 and 2.7 Seems like a bug in Gerrit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-18930) Missing TestResultColumn() constructor
Greg Nion
created JENKINS-18930
Missing TestResultColumn() constructor
Issue Type:
Bug
Assignee:
Fred G
Components:
extra-columns
Created:
25/Jul/13 2:50 PM
Description:
Hi,
I need to programmatically create some sectioned views (via groovy script to ease maintenance of hundreds of jobs on multiple projects/teams/views)
I was previously using version 1.2 of the plugin with an old version of Jenkins. All was OK.
Since we migrated to Jenkins 1.509.2 + plugin 1.10 my script doesn't work any more because of:
"Failed to instantiate class jenkins.plugins.extracolumns.TestResultColumn from null"
Looking at:
hudson.model.Descriptor.newInstance(StaplerRequest req, JSONObject formData)
showed it "return verifyNewInstance(clazz.newInstance());" where clazz is jenkins.plugins.extracolumns.TestResultColumn and can't instantiate a new instance as there is only one constructor that needs an int in parameter.
It would be handy to add a no param constructor that set the int to a default value to be able to run column creation through their Descriptor and not have to add a specific case for TestResultColumn.
This is a snippet of my groovy script:
import hudson.DescriptorExtensionList
import hudson.model.*
import hudson.model.Descriptor.FormException
import hudson.plugins.sectioned_view.*
import hudson.util.*
import hudson.views.*
DEFAULT_COLUMNS = [
BuildButtonColumn.class // OK
,com.robestone.hudson.compactcolumns.JobNameColumn.class// OK
,LastDurationColumn.class // OK
,jenkins.plugins.extracolumns.TestResultColumn.class// NOK
]
println("Init our columns ...")
myColumns = [];
DescriptorExtensionList> all = ListViewColumn.all();
for (Classextends ListViewColumn> d: DEFAULT_COLUMNS) {
Descriptor des = all.find(d);
if (des != null) {
println("Case " + d)
switch(d) {
case jenkins.plugins.extracolumns.TestResultColumn.class:
println("descriptor = " + des)
println("descriptor.clazz = " + des.clazz)
println()
try {
clazzInst = d.newInstance()
println("+++Successfully run TestResultColumn.newInstance() = " + clazzInst)
myColumns.add(clazzInst);
} catch (Exception exp) {
println("!!!Exception while instantiating new TestResultColumn(): " + exp.getMessage())
}
try {
clazzInst0 = d.newInstance(0)
println("+++Successfully run new TestResultColumn.newInstance(0) = " + clazzInst0)
myColumns.add(clazzInst0);
} catch (Exception exp) {
println("!!!Exception while instantiating new TestResultColumn(0): " + exp.getMessage())
}
try {
tmp = des.newInstance(null,null)
myColumns.add(tmp);
println("+++Successfully run TestResultColumn.DescriptorImpl.newInstance(null, null) = " + tmp)
} catch (Error exp) {
println("!!!Error while TestResultColumn.DescriptorImpl.newInstance(null, null): " + exp.getMessage())
}
break
default:
myColumns.add(des.newInstance(null, null));
break
}
}
else
{
println("No descriptior found for " + d)
}
}
println("\nResulting columns ...")
myColumns.each {println(it)}
Give me your thoughts. Maybe there is another way to do this!
Cheers,
Greg
Environment:
Groovy script
Project:
Jenkins
Priority:
Major
R
[JIRA] [core] (JENKINS-18929) OutOfMemoryError: PermGen space
David Ishee created JENKINS-18929 OutOfMemoryError: PermGen space Issue Type: Bug Assignee: Unassigned Attachments: stack.txt Components: core Created: 25/Jul/13 2:46 PM Description: We get frequent out of memory errors. They happen every few days. Here is a stack trace that showed up in the browser today: Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/local/IMAT/.jenkins/war/WEB-INF/lib/jenkins-core-1.509.2.jar!/lib/layout/layout.jelly:85:72: PermGen space Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/local/IMAT/.jenkins/war/WEB-INF/lib/jenkins-core-1.509.2.jar!/lib/layout/layout.jelly:85:72: PermGen space at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) 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:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServl
[JIRA] [clone-workspace] (JENKINS-6890) clone-workspace-scm doesn't work when source job is a matrix job.
Peter Kovacs commented on JENKINS-6890 clone-workspace-scm doesn't work when source job is a matrix job. Can someone upload a snapshot build, so we can try to install? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Ronald Müller commented on JENKINS-18848 Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin Hi, i can confirm, that projects will be build, if you put "something" to "Ivy settings" text-field in the project-configuration-panel. As already stated here: there will be a form-validation error "Ivy settings file must be a relative path." or something else, but the project builds successfully afterwards. So this could be a workaround for very urgent projects. In my scenario this text-field is always left blank, as the ivy-settings-file is configured in ant-buildscript itself via So IMHO it is definitly a bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18928) Conole annotator block console text output
teilo created JENKINS-18928 Conole annotator block console text output Issue Type: Bug Assignee: Unassigned Components: core Created: 25/Jul/13 2:36 PM Description: The the hyperlinkNote is called with text that contains a line feed then no further console output will be seen in the normal jenkins view (the raw view will still work). This is easily reproduced by having a maven build with a module that contains a element that contains a linefeed (which is acceptable.) and hacing another job that is set to copy its artifacts. e.g. the console output (raw) would be Copied 1 artifacts from "foo » Maven name from module containing no line feed" build number 1087 Copied 0 artifacts from "foo » Maven name from module containing a linefeed and some indentation" build number 1087 ... rest of console output the last line that is shown in the html console output is "Copied 1 artifacts from "foo » Maven name from module containing no line feed" build number 1087" This makes the console output unuseable. although changing the name in the maven project would seem an easy workaround - automatic formatters will change it back without human intervention. Environment: Jenkins 1.509.LTS, CopyArtifactPlugin 1.27 Project: Jenkins Priority: Critical Reporter: teilo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buildresulttrigger] (JENKINS-18667) NullPointerException when saving job config
Jonathan Brecher commented on JENKINS-18667 NullPointerException when saving job config Same as JENKINS-18658? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18658) NPE in FSTrigger upon configuration save
Jonathan Brecher commented on JENKINS-18658 NPE in FSTrigger upon configuration save Same as JENKINS-18667? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-17810) Multijob hierarchy is not shown when jobs inside of the phases are "Monitor an external job"
Oren Weinberg commented on JENKINS-17810 Multijob hierarchy is not shown when jobs inside of the phases are "Monitor an external job" add the exception: Jul 25, 2013 4:57:27 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.view.getRootItem(it). Reason: java.lang.ClassCastException: hudson.model.ExternalJob cannot be cast to hudson.model.AbstractProject java.lang.ClassCastException: hudson.model.ExternalJob cannot be cast to hudson.model.AbstractProject at com.tikal.jenkins.plugins.multijob.views.MultiJobView.addMultiProject(MultiJobView.java:137) at com.tikal.jenkins.plugins.multijob.views.MultiJobView.addTopLevelProject(MultiJobView.java:107) at com.tikal.jenkins.plugins.multijob.views.MultiJobView.getRootItem(MultiJobView.java:101) at sun.reflect.GeneratedMethodAccessor366.invoke(Unknown Source) 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:72) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) 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.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:107) at org.kohsuke.stapler.jelly.JellyFacet.handleInde
[JIRA] [core] (JENKINS-18927) Builds disappear from build history after completion
James li started work on JENKINS-18927 Builds disappear from build history after completion Change By: James li (25/Jul/13 1:48 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18927) Builds disappear from build history after completion
James li updated JENKINS-18927 Builds disappear from build history after completion Change By: James li (25/Jul/13 1:43 PM) Description: My problem is similar with JENKINS-15156.1.Builds disappearing from the "Build History" listing on the project page.2.The other jobs was normally.3.Nothing was noted in the logs.4.The data was still present on the disk and doing a reload from disk brought the build back.5.Happend randomly.6.Upgrade to 1.523 and the problem is still exist. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18927) Builds disappear from build history after completion
James li created JENKINS-18927 Builds disappear from build history after completion Issue Type: Bug Assignee: Unassigned Attachments: jenkins_lost_builds.png Components: core Created: 25/Jul/13 1:41 PM Description: My problem is similar with JENKINS-15156. 1.Builds disappearing from the "Build History" listing on the project page. 2.The other jobs was normally. 3.Nothing was noted in the logs. 4.The data was still present on the disk and doing a reload from disk brought the build back. 5.Happend randomly. 6.Upgrade to 1.523 and the problem still exist. Environment: Master:Jenkins 1.509,on CentOS 5.8 Slave:via java web start(commnd:java -jar slave.jar -jnlpUrl http://jenkins/XXX -secret XXX) Project: Jenkins Priority: Major Reporter: James li This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Jerome Martin commented on JENKINS-18848 Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin I have configure the "ivy settings file" with an absolute file /tmp/empty.txt (existing or not): it works but I have a message on Jenkins : Ivy settings file must be a relative path. a local, non existing file empty.txt: it works but I have the message : No such file: 'empty.txt' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-10524) winstone.ClientSocketException: Failed to write to client
Jesse Glick commented on JENKINS-10524 winstone.ClientSocketException: Failed to write to client https://github.com/stapler/stapler/commit/a6307f473e44aa4fd6a26275304d738dba5201c9 (once integrated into Jenkins core) might work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-15384) TFS Plugin does not seem to work (can't get latest)
Sukesh Nambiar edited a comment on JENKINS-15384 TFS Plugin does not seem to work (can't get latest) . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-15384) TFS Plugin does not seem to work (can't get latest)
Sukesh Nambiar
edited a comment on JENKINS-15384
TFS Plugin does not seem to work (can't get latest)
Looks like this issue is related to the Local Workfolder path, which is . by default.
The TFS clients (latest ones) does not accept . as the working folder.
A solution for this could be to use the ${WORKSPACE}. But it looks like the plugin does not expand the ${WORKSPACE} variable when evaluating the Local Workfolder property.
I am using a linux machine and it works when I give the absolute path like /var/lib/jenkins/workspace/test-project (where test-project is the jenkins project name).
This should be a fix in the TFS 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] [tfs] (JENKINS-15384) TFS Plugin does not seem to work (can't get latest)
Sukesh Nambiar
commented on JENKINS-15384
TFS Plugin does not seem to work (can't get latest)
Looks like this issue is related to the Local Workfolder path, which is . by default.
The TFS clients (latest ones) does not accept . as the working folder.
A solution for this could be to use the ${WORKSPACE}. But it looks like the plugin does not expand the ${WORKSPACE} variable when evaluating the Local Workfolder property.
I am using a linux machine and it works when I give the absolute path like /var/lib/jenkins/workspace/test-project (where test-project) is the jenkins project name.
This should be a fix in the TFS plugin.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
Jesse Glick edited a comment on JENKINS-10524 winstone.ClientSocketException: Failed to write to client Jenkins 1.521 included https://github.com/stapler/stapler/commit/ac0b5683c4a3a45c3b987baf264674934470b668 which installs a new pretty exception handler that may affect the symptoms of this bug somehow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivy] (JENKINS-18848) Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin
Johno Crawford commented on JENKINS-18848 Ivy-Projects ends up with a NPE on build after update Jenkins and Ivy-Plugin @Jerome would you please confirm if it works if you specify a dummy file (which exists)? I can investigate this issue after work today. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-10524) winstone.ClientSocketException: Failed to write to client
Jesse Glick commented on JENKINS-10524 winstone.ClientSocketException: Failed to write to client Jenkins 1.521 included https://github.com/stapler/stapler/commit/ac0b5683c4a3a45c3b987baf264674934470b668 which installs a new pretty exception handler that no longer sends anything to the log, which I think is wrong in a different way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-18782) slave connection failed starting with 1.519
Stevo Slavić commented on JENKINS-18782 slave connection failed starting with 1.519 When my build runs on master, it's successful. I'm getting similar stack trace and failing build when it's run on slave: ERROR: Failed to parse POMs hudson.util.IOException2: java.lang.reflect.InvocationTargetException at hudson.maven.Maven3Builder.call(Maven3Builder.java:162) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.Exception: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:177) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) ... 10 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:174) ... 11 more Caused by: java.lang.NoClassDefFoundError: org/apache/commons/collections/map/LRUMap at hudson.util.LRUStringConverter.(LRUStringConverter.java:24) at hudson.maven.reporters.MavenArtifact.(MavenArtifact.java:75) at hudson.maven.reporters.MavenArtifactArchiver.postBuild(MavenArtifactArchiver.java:101) at hudson.maven.Maven3Builder$MavenExecutionListener.sessionEnded(Maven3Builder.java:297) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:64) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:170) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) ... 18 more Caused by: java.lang.ClassNotFoundException: org.apache.commons.collections.map.LRUMap at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:237) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 28 more Caused by: java.util.concurrent.ExecutionException: java.util.zip.ZipException: error in opening zip file at hudson.remoting.ResourceImageInJar$1.adapt(ResourceImageInJar.java:48) at hudson.remoting.ResourceImageInJar$1.adapt(ResourceImageInJar.java:42) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:229) ... 30 more Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.(ZipFile.java:127) at java.util.jar.JarFile.(JarFile.java:136) at java.util.jar.JarFile.(JarFile.java:73) at sun.net.www.protocol.jar.URLJarFile.(URLJarFile.java:72) at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:48) at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:55) at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:104) at sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:132) at java.net.URL.openStream(URL.java:1010) at hudson.remoting.ResourceImageInJar$1.adapt(ResourceImageInJar.java:46) ... 33 more This message is automatically generated by JIRA. If you think it wa
[JIRA] [gerrit-trigger] (JENKINS-18878) Gerrit-trigger-plugin does not trigger jobs at all when the connection is unavailable to Jenkins server
rin_ne commented on JENKINS-18878 Gerrit-trigger-plugin does not trigger jobs at all when the connection is unavailable to Jenkins server That's normal. gerrit sends event to active connection only. There is no event queuing feature in gerrit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." 1. You need to add explicitly a new access right (All Projects: Global Capabilities->Administrate Server->Stream Events) to the Non-Interactive Users group. This is something new and it was not necessary for the previous Gerrit releases (<2.7). Seems it is already noted in Gerrit 2.7 document. http://gerrit-documentation.googlecode.com/svn/Documentation/2.7/cmd-stream-events.html#_access $ ssh gerrit gerrit review --verified +1 9990133e3df3b777a1fc5ba8d8d59677bdc65856 fatal: "--verified" is not a valid option It works perfectly fine with the Gerrit 2.6. I didn't find any sensible error message in the logs (Jenkins + Gerrit), so it is not easy to find the problem. This might be a bug or new feature. BTW, did you try to use --label option instead --verified option? http://gerrit-documentation.googlecode.com/svn/Documentation/2.7/cmd-review.html#_synopsis If works fine with --label option, may be able to customize the above command using custom command feature in management page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [reviewboard] (JENKINS-18926) ReviewBoard Publisher
amit anand created JENKINS-18926 ReviewBoard Publisher Issue Type: Bug Affects Versions: current Assignee: rshelley Components: reviewboard Created: 25/Jul/13 12:08 PM Description: Review Board Publisher Skip to content title help for search log in | sign up Jenkins Jenkins project Bug tracker Mailing Lists Twitter: @jenkinsci Oops! A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/root/.hudson/war/WEB-INF/lib/jenkins-core-1.524.jar!/lib/form/section.jelly:48:21: (class: hudson/plugins/reviewboard/ReviewboardPublisher, method: submitChangeToReviewBoard signature: (Ljava/lang/Long;Ljava/lang/String;Ljava/lang/Long;Ljava/lang/String;Ljava/lang/String;Ljava/util/Collection;Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/model/BuildListener;)Lhudson/plugins/reviewboard/ReviewInfoAction Incompatible argument to function at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:197) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:171) 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:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118) 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.acegisecuri
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." Linked Gerrit's thread: https://code.google.com/p/gerrit/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Type%20Stars%20Milestone%20Status%20Priority%20Owner%20Summary&groupby=&sort=&id=1963 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
Piotr Szwed edited a comment on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." Ok. I did some testing. There are 2 issues. 1. You need to add explicitly a new access right (All Projects: Global Capabilities->Administrate Server->Stream Events) to the Non-Interactive Users group. This is something new and it was not necessary for the previous Gerrit releases (<2.7). The symptom of the missing access right is: "gerrit.stream-events 0ms 2ms not-admin" - in the Gerrit's sshd_log file. I believe there should be added some note about it in the documentation (of both: Gerrit and Gerrit Trigger Plugin) 2. Gerrit 2.7 is not backward compatible or there was a bug introduced in the 2.7 version: The problem: $ ssh gerrit gerrit review --verified +1 9990133e3df3b777a1fc5ba8d8d59677bdc65856 fatal: "--verified" is not a valid option It works perfectly fine with the Gerrit 2.6. I didn't find any sensible error message in the logs (Jenkins + Gerrit), so it is not easy to find the problem. I will ask Gerrit's community if it is a feature or a bug.. , there is a possibility to use different parameter (--label) instead of --verified, but We should know first what is the proposed solution by Gerrit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
Piotr Szwed edited a comment on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." Ok. I did some testing. There are 2 issues. 1. You need to add explicitly a new access right (All Projects: Global Capabilities->Administrate Server->Stream Events) to the Non-Interactive Users group. This is something new and it was not necessary for the previous Gerrit releases (<2.7). The symptom of the missing access right is: "gerrit.stream-events 0ms 2ms not-admin" - in the Gerrit's sshd_log file. I believe there should be added some note about it in the documentation (of both: Gerrit and Gerrit Trigger Plugin) 2. Gerrit 2.7 is not backward compatible or there was a bug introduced in the 2.7 version: The problem: $ ssh gerrit gerrit review --verified +1 9990133e3df3b777a1fc5ba8d8d59677bdc65856 fatal: "--verified" is not a valid option It works perfectly fine with the Gerrit 2.6. I didn't find any sensible error message, so it is not easy to find the problem. I will ask Gerrit's community if it is a feature or a bug.. , there is a possibility to use different parameter (--label) instead of --verified, but We should know first what is the proposed solution by Gerrit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server."
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - "The connection to Gerrit is down! Check your settings and the Gerrit server." Ok. I did some testing. There are 2 issues. 1. You need to add explicitly new access right (All Projects: Global Capabilities->Administrate Server->Stream Events) for the Non-Interactive Users group. This was not necessary with the previous Gerrit releases, so after the upgrading to >2.7 - it is missing. The symptom of the missing access right is: gerrit.stream-events 0ms 2ms not-admin In the gerrit sshd_log file. I believe there should be some note in the Gerrit's and Gerrit Trigger Plugin about the fact. 2. Gerrit 2.7 is not backward compatible or there was a bug introduced in the version: The problem: $ ssh gerrit gerrit review --verified +1 9990133e3df3b777a1fc5ba8d8d59677bdc65856 fatal: "--verified" is not a valid option It works perfeclty fine with the Gerrit 2.6. I didn't find any sensible error message, so it is not easy to find the root cause. Would be nice if someone confirms it. I will ask Gerrit's community if it is a feature or a bug.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18849) java.lang.ClassNotFoundException: hudson.maven.AbstractMavenProject
Francisco Ruiz commented on JENKINS-18849 java.lang.ClassNotFoundException: hudson.maven.AbstractMavenProject The same error on 1.524 but apparently related to Violations plugin Caused by: java.lang.NoClassDefFoundError: hudson/maven/AbstractMavenProject at hudson.plugins.violations.hudson.ViolationsFreestyleDescriptor.isApplicable(ViolationsFreestyleDescriptor.java:104) at hudson.tasks.BuildStepDescriptor.filter(BuildStepDescriptor.java:84) at hudson.Functions.getPublisherDescriptors(Functions.java:766) 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:616) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18925) broken "Slaves statistics" Dashboard Portlet, displaying raw makeStaplerProxy() javascript function instead of numbers
Michael Prokop
created JENKINS-18925
broken "Slaves statistics" Dashboard Portlet, displaying raw makeStaplerProxy() _javascript_ function instead of numbers
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Attachments:
screenshot.2013-07-25T12-37-03.png
Components:
core
Created:
25/Jul/13 10:45 AM
Description:
At least since Jenkins version 1.520 (up and including version 1.524) the "Slaves statistics" Dashboard Portlet is broken for me (I've reported it as part of https://issues.jenkins-ci.org/browse/JENKINS-18510 but this seems to be a different issue since its fix doesn't resolve my issue).
I get:
makeStaplerProxy('/$stapler/bound/[snip]','[snip]',['getSlaves','getOnlineSlaves','getOfflineSlaves','getDisconnectedSlaves','getTasksInQueue','getRunningJobs']) function repeat()[snip]
instead of the actual slave statistics, also see attached screenshot.
Inside the HTML source I see:
var buildStat =