[JIRA] (JENKINS-16165) Configure screen stuck in LOADING state
Matti Linnanvuori commented on JENKINS-16165 Configure screen stuck in LOADING state I probably have the same bug in Debian: Skip to content Jenkins Plugin Manager Back to Dashboard Manage Jenkins Installed Updates Available Advanced Enabled Name Version Previously installed version Pinned LDAP Plugin 1.2 External Monitor Job Type Plugin 1.1 pam-auth 1.0 Jenkins Jira Issue Updater This plugin can update Jira issues by changing their workflow status and adding comments. 1.3 ant 1.1 javadoc 1.0 Jenkins CVS Plug-in Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient. 2.7 Maven Integration plugin 1.480.1 Jenkins JIRA plugin This plugin integrates Jenkins to Atlassian JIRA. 1.35 Jenkins Translation Assistance plugin 1.10 Static Analysis Utilities This plug-in provides utilities for the static code analysis plug-ins. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 1.48 Android Lint Plugin This plugin parses Android Lint analysis results and visualises the issues found. 2.0.2 Jenkins Subversion Plug-in 1.44 Jenkins SSH Slaves plugin 0.22 Jenkins GIT plugin This plugin integrates GIT with Jenkins. 1.1.26 Help us localize this page Page generated: Jan 3, 2013 2:59:27 AMREST APIJenkins ver. 1.480.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16165) Configure screen stuck in LOADING state
Matti Linnanvuori edited a comment on JENKINS-16165 Configure screen stuck in LOADING state I probably have the same bug in Debian GNU/Linux wheezy/sid. After restarting Jenkins a couple of times I can configure a job again. Jenkins Plugin Manager Back to Dashboard Manage Jenkins Installed Updates Available Advanced Enabled Name Version Previously installed version Pinned LDAP Plugin 1.2 External Monitor Job Type Plugin 1.1 pam-auth 1.0 Jenkins Jira Issue Updater This plugin can update Jira issues by changing their workflow status and adding comments. 1.3 ant 1.1 javadoc 1.0 Jenkins CVS Plug-in Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient. 2.7 Maven Integration plugin 1.480.1 Jenkins JIRA plugin This plugin integrates Jenkins to Atlassian JIRA. 1.35 Jenkins Translation Assistance plugin 1.10 Static Analysis Utilities This plug-in provides utilities for the static code analysis plug-ins. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 1.48 Android Lint Plugin This plugin parses Android Lint analysis results and visualises the issues found. 2.0.2 Jenkins Subversion Plug-in 1.44 Jenkins SSH Slaves plugin 0.22 Jenkins GIT plugin This plugin integrates GIT with Jenkins. 1.1.26 Help us localize this page Page generated: Jan 3, 2013 2:59:27 AMREST APIJenkins ver. 1.480.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16165) Configure screen stuck in LOADING state
Matti Linnanvuori updated JENKINS-16165 Configure screen stuck in LOADING state Java thread dump Change By: Matti Linnanvuori (03/Jan/13 8:16 AM) Attachment: jenkins.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16245) Grails plugin - cannot execute two-word command
Wojtek Erbetowski resolved JENKINS-16245 as Not A Defect Grails plugin - cannot execute two-word command Change By: Wojtek Erbetowski (03/Jan/13 8:25 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16245) Grails plugin - cannot execute two-word command
Wojtek Erbetowski commented on JENKINS-16245 Grails plugin - cannot execute two-word command Thanks that worked. I missed that the first time due to some other error. So the proper way to chain commands seems to be test-app "tomcat undeploy" "tomcat deploy" in a single command execution. That's even quite nice. Thanks again! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16203) Jenkins tools auto install dir has changed
Vincent Latombe commented on JENKINS-16203 Jenkins tools auto install dir has changed I fail to understand how is this a problem. When using tools installation you shouldn't care in which actual path the tool is installed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15045) Support Github commit status API
David Henderson commented on JENKINS-15045 Support Github commit status API Any work I can do to move this forward? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16239) NPE in getRootDir
Krzysztof Malinowski commented on JENKINS-16239 NPE in getRootDir I did upgrade from 1.495 to 1.496 and EnvInject from 1.75 to 1.78. Reverted both core and envinject back to 1.495 and 1.75 respectively, but the issue still exists. It is possible that issue has been existing for some time now only I discovered it yesterday. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8334) maven-plugin insists on Surefire to run tests
Alexander Bertram commented on JENKINS-8334 maven-plugin insists on Surefire to run tests This is super important for supporting alternate JVM languages in maven builds. The xUnit plugin plugs into the free-style build, so it doesn't help if your project is configured as a maven build. Why not just check for junit xml files after all the plugins have executed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16239) NPE in getRootDir
Krzysztof Malinowski commented on JENKINS-16239 NPE in getRootDir I also discovered that this error is being reported permanently, upon navigating Jenkins UI. There are reported multiple times at once. Here is the more complete stack trace: java.lang.NullPointerException at hudson.model.Run.getRootDir(Run.java:927) at org.jenkinsci.lib.envinject.EnvInjectAction.readResolve(EnvInjectAction.java:86) at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:46) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:61) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:61) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:332) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:274) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:221) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at
[JIRA] (JENKINS-16250) change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph
Harish Balan created JENKINS-16250 change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph Issue Type: Task Affects Versions: current Assignee: Ulli Hafner Components: checkstyle Created: 03/Jan/13 10:22 AM Description: I am running Jenkins 1.432 with checkstyl 3.14. The default job with hardcoded sourceDirectory and configLocation creates the checkstyle-result.xml inside the job/target/ folder. But I need to allow users to access the result xml file through HTTP access. For this, I have redirected the outputFile into job/workspace/target folder. But in this case, the result xml is correctly getting generated but neither the trend graphs nor the usual checkstyle warnings section shows the checkstyle warnings. Do i need to configure anywhere to direct the trend graph to look into this particular folder for the result xml file? Kindly help to understand the configuration required here to make the trend graphs read the result xml from job/workspace/target folder. Environment: Jenkins 1.432 / checkstyle 3.14 Project: Jenkins Priority: Critical Reporter: Harish Balan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16250) change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph
Ulli Hafner edited a comment on JENKINS-16250 change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph Are you using a freestyle or maven project type? In case of a freestyle job: you can simply change the file pattern that the plug-in is looking for using the UI. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9896) Trend report only displays the last build
Krystian Nowak commented on JENKINS-9896 Trend report only displays the last build I was also able to confirm - e.g. if jtl files produced in target/jmeter/results e.g. by jmeter-maven-plugin (http://wiki.apache.org/jmeter/JMeterMavenPlugin or https://github.com/Ronnie76er/jmeter-maven-plugin) are in form of NAME-DDMMYY.jtl e.g. my-nice-test-130103.jtl, then the results are grouped by the whole filename and then only results for given day are taken into account for given graph/chart. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16250) change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph
Harish Balan commented on JENKINS-16250 change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph Hi Ulli, Thanks for responding. I am using a maven 2/3 project. In that case, can you help me in where i would need to configure that? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8166) hudson.util.IOException2: remote file operation failed
evernat resolved JENKINS-8166 as Incomplete hudson.util.IOException2: remote file operation failed No response from the reporter, so resolving as incomplete. Change By: evernat (03/Jan/13 11:35 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8384) Copying a compressed tar file from a 64 bit master to a slave running SUSE Linux fails
evernat resolved JENKINS-8384 as Incomplete Copying a compressed tar file from a 64 bit master to a slave running SUSE Linux fails No response from the reporter, so resolving as incomplete. Change By: evernat (03/Jan/13 11:36 AM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16214) Serena dimensions dependencies missing from jenkins-war 1.494
Francesco Grossi
commented on JENKINS-16214
Serena dimensions dependencies missing from jenkins-war 1.494
For the time being we've manually copied the missing jars to the ${webroot}/WEB-INF/lib/.
In case someone has better ideas or notice something I've missed doing, as for example, in order to make jenkins deploy plugins dependencies along with hpi, please let me know (for instance: shall I have to change my pom with regards to dependencies' scope? )
Many thanks
Francesco
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16250) change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph
Harish Balan assigned JENKINS-16250 to Ulli Hafner change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph i think i had by mistake assigned the issue to myself when i was trying to enter my comments Change By: Harish Balan (03/Jan/13 11:39 AM) Assignee: HarishBalan UlliHafner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9896) Trend report only displays the last build
Krystian Nowak edited a comment on JENKINS-9896 Trend report only displays the last build I was also able to confirm - e.g. if jtl files produced in target/jmeter/results e.g. by jmeter-maven-plugin (http://wiki.apache.org/jmeter/JMeterMavenPlugin or https://github.com/Ronnie76er/jmeter-maven-plugin) are in form of NAME-DDMMYY.jtl e.g. my-nice-test-130103.jtl, then the results are grouped by the whole filename and then only results for given day are taken into account for given graph/chart. Here goes the workaround - http://ribblescode.wordpress.com/2012/04/16/how-to-automate-jmeter-tests-with-maven-and-jenkins-hudson-8/ in section Fix the project: configuration testResultsTimestampfalse/testResultsTimestamp /configuration in plugin's configuration This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16250) change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph
Ulli Hafner commented on JENKINS-16250 change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph You need to switch to a freestyle project until that is 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
[JIRA] (JENKINS-16214) Serena dimensions dependencies missing from jenkins-war 1.494
evernat commented on JENKINS-16214 Serena dimensions dependencies missing from jenkins-war 1.494 When I look into jenkins.war 1.463 at 1, I do not see darius.jar, dmclient.jar, dmfile.jar or dmnet.jar, unlike what you said. Moreover, the plugin's doc 2 says to copy those files into "WEB-INF/lib" as you have done. So, I suppose that you need to continue to do that and I suppose that this is not a defect. Should we close this issue as not a defect? 1 http://mirrors.jenkins-ci.org/war/1.463/jenkins.war 2 https://wiki.jenkins-ci.org/display/JENKINS/Dimensions+Plugin#DimensionsPlugin-Installation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16229) Breaks CopyArtifact Plugin
Bue Petersen commented on JENKINS-16229 Breaks CopyArtifact Plugin Thanks for the bug report. We will look into that as soon as possible, and release it our next development iteration. You might be asked to elaborate further, in which case we will post our request on here. Best regards, Bue Petersen Praqma A/S This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16229) Breaks CopyArtifact Plugin
Bue Petersen edited a comment on JENKINS-16229 Breaks CopyArtifact Plugin Thanks for the bug report. We will look into that as soon as possible, and release a fix in our next development iteration. You might be asked to elaborate further, in which case we will post our request in here. Best regards, Bue Petersen Praqma A/S This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16214) Serena dimensions dependencies missing from jenkins-war 1.494
Francesco Grossi commented on JENKINS-16214 Serena dimensions dependencies missing from jenkins-war 1.494 Ok Of course you are right . It might be my predecessor rebuilt the war as my local copy has them . Yes of course you can close it as no defect Many thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16251) HtmlPublisher 1.2 doesn't load from disk under Jenkins 1.492
cedd burge created JENKINS-16251 HtmlPublisher 1.2 doesnt load from disk under Jenkins 1.492 Issue Type: Bug Affects Versions: current Assignee: mcrooney Components: htmlpublisher Created: 03/Jan/13 12:42 PM Description: When using HtmlPublisher 1.2 in Jenkins 1.492 I can add a new html report to the configurartion using the web interface without any problems and everything works fine. If I "Reload Configuration From Disk", the htmlpublisher post build action disappears, and instead I get a "You have data stored in an older format and/or unreadable data." message from Jenkins. If I go to the "Manage Old Data" the following is shown: hudson.model.FreeStyleProject Job Name CannotResolveClassException: htmlpublisher.HtmlPublisher : htmlpublisher.HtmlPublisher The xml in the config file is as follows: htmlpublisher.HtmlPublisher plugin="htmlpublisher@1.2" reportTargets htmlpublisher.HtmlPublisherTarget reportNameErrors/reportName reportDir$Workspace\Results/reportDir reportFileserrors.xml/reportFiles keepAlltrue/keepAll wrapperNamehtmlpublisher-wrapper.html/wrapperName /htmlpublisher.HtmlPublisherTarget /reportTargets /htmlpublisher.HtmlPublisher Reverting to htmlpublisher 1.0 fixes the problem Environment: Windows Project: Jenkins Priority: Major Reporter: cedd burge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16203) Jenkins tools auto install dir has changed
Vincent Latombe commented on JENKINS-16203 Jenkins tools auto install dir has changed As kohsuke points out in the commit, display name is for UI and can change based on locale so it is probably a better idea to use an ID. As I already said, readability shouldn't matter since you are not supposed to care about paths where tools are automatically installed. You tried to solve an issue (embedding additional libs in a tool) but you didn't use the proper solution, which is to build a .zip with tool + additional libs, and to use this .zip as source of tool installation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8334) maven-plugin insists on Surefire to run tests
kutzi assigned JENKINS-8334 to kutzi maven-plugin insists on Surefire to run tests Change By: kutzi (03/Jan/13 1:01 PM) Assignee: kutzi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8334) maven-plugin insists on Surefire to run tests
kutzi commented on JENKINS-8334 maven-plugin insists on Surefire to run tests Why not just check for junit xml files after all the plugins have executed? That's just not how the Maven jobs work and it would mean a major refactoring to change that - and I'm not even positive that this is a desirable change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8334) maven-plugin insists on Surefire to run tests
kutzi commented on JENKINS-8334 maven-plugin insists on Surefire to run tests Using a startup switch - like hhuynh - is maybe not a good solution as this would AFAIK mean that every executed mojo (not just test mojos) is handled by the SurefireArchiver - which could mean a significant overhead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15353) Missing descriptor exception in Jenkins log for Throttle Concurrent Builds plugin
Oliver Whiteman commented on JENKINS-15353 Missing descriptor exception in Jenkins log for Throttle Concurrent Builds plugin Is there any update on this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16203) Jenkins tools auto install dir has changed
michael d commented on JENKINS-16203 Jenkins tools auto install dir has changed Can I tell Jenkins to auto deploy my custom zipped tool to slaves ? I wasn't aware of this solution, if so, it is much better solution than what i used This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16214) Serena dimensions dependencies missing from jenkins-war 1.494
evernat resolved JENKINS-16214 as Not A Defect Serena dimensions dependencies missing from jenkins-war 1.494 Change By: evernat (03/Jan/13 1:58 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16250) change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph
Harish Balan commented on JENKINS-16250 change of checkstyle-result.xml folder by changing outputFile parameter leading to zero warnings in trend graph Thanks Ulli. I tried out in the freestyle project and it seems to work fine. Thanks again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16252) SourceCodePainter overwrites original files
Murat Yukselen created JENKINS-16252 SourceCodePainter overwrites original files Issue Type: Bug Assignee: stephenconnolly Attachments: coverage.xml, SourceCodePainter.patch Components: cobertura Created: 03/Jan/13 2:42 PM Description: coverage.xml contains filename attributes. If this attribute is absolute based on hudson.FilePath implementation, canvas FilePath object is created as absolute and outside of the intended cobertura job directory. SourceCodePainter overwrites this file in paintSourceCode(). Attached is a very simple patch, pointing to the problem. coverage.xml is produced on Windows by patched gcovr.py using QNX cross compiler tools. It is simplified for testing. Environment: Windows 7 Project: Jenkins Labels: plugin Priority: Major Reporter: Murat Yukselen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14931) Allow the elapsed time (since the build started) to be displayed
stevengbrown assigned JENKINS-14931 to stevengbrown Allow the elapsed time (since the build started) to be displayed Change By: stevengbrown (03/Jan/13 2:49 PM) Assignee: stevengbrown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14931) Allow the elapsed time (since the build started) to be displayed
stevengbrown started work on JENKINS-14931 Allow the elapsed time (since the build started) to be displayed Change By: stevengbrown (03/Jan/13 2:49 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14590) Redeploy Artifacts button no longer appears on main build page of multi-module builds, requiring individual reployment of modules
Jeff Maxwell
updated JENKINS-14590
Redeploy Artifacts button no longer appears on main build page of multi-module builds, requiring individual reployment of modules
Change By:
Jeff Maxwell
(03/Jan/13 2:52 PM)
Description:
Inversionspriorto1.461onecouldredeployallartifactsofabuildfromthebuildpagefromtheRedeployArtifactsbutton.In1.461andabovetheRedeployArtifactsbuttonnolongerappearsontherootbuildpageandonlyappearsoneachcomponentpage.Thisappearstobecausedthissection:{code}hudson.maven.reporters.MavenAggregatedArtifactRecordrecords/parentreference=../../..//hudson.maven.reporters.MavenAggregatedArtifactRecord{code}
nolongerappearinginthebuild.xml.Thisbugmakesredeployinglargemulti-moduleprojectsproblematic,complicatingpromotionofabuildfromastagingtoareleaserepository
h4.WorkaroundUsingapostbuildgroovystepsimilartothecodebelow:{code}defmavenModuleSetBuild=Thread.currentThread().executor.executable;mavenModuleSetBuild.addAction(newMavenAggregatedArtifactRecord(mavenModuleSetBuild));{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8334) maven-plugin insists on Surefire to run tests
Alexander Bertram commented on JENKINS-8334 maven-plugin insists on Surefire to run tests Could we use a "duck-typing" approach? Some conventions that could identify test plugins? That is, a test goal is a maven goal that is called "test", then check for output xml files? Likewise, if there exists a property testFailureIgnore, then set it to true? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16253) Configuration values in UI are reset to defaults
Andreas Bosch created JENKINS-16253 Configuration values in UI are reset to defaults Issue Type: Bug Affects Versions: current Assignee: Julien RENAUT Components: xfpanel Created: 03/Jan/13 3:43 PM Description: I changed the sort order to "Alphabetical" instead of "Failed first" and also "Show Responsibles" to "every committer since the last successful build" instead of "not at all". Both changes were applied successfully, but when I returned to the configuration page, both values were reset to the original values (i.e. "Failed first" and "not at all"). It seems like the UI does not reflect the actual values from the configuration. Project: Jenkins Labels: plugin Priority: Minor Reporter: Andreas Bosch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16254) Unable to use Build Name Setter Plugin
emszpak created JENKINS-16254 Unable to use Build Name Setter Plugin Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: build-flow Created: 03/Jan/13 4:00 PM Description: It is very useful to be able to set a build name for parametrized builds using Build Name Setter Plugin. In a build flow job type there is no "Build Environment" section. Similar situation with Description Setter Plugin. Environment: build-flow-plugin 0.6, Jenkins 1.480.1 Project: Jenkins Priority: Major Reporter: emszpak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Niklaus Giger updated JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Memory dump with arguments "-XX:+CMSClassUnloadingEnabled -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/jenkins/memory.dump" and PeriodicBackup with version 1.2-SNAPSHOT (private-12/29/2012 17:07-johno) Change By: Niklaus Giger (03/Jan/13 4:05 PM) Attachment: memory.dump.bz2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8334) maven-plugin insists on Surefire to run tests
kutzi commented on JENKINS-8334 maven-plugin insists on Surefire to run tests Sounds reasonable. I'll look into 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
[JIRA] (JENKINS-16249) xUnit PHPUNIT group by testsuites
Jonathan Dell commented on JENKINS-16249 xUnit PHPUNIT group by testsuites Here are the xml files processed by the xUnit plugin https://dl.dropbox.com/u/2406744/phpunit-xml.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded
Chris Eagan commented on JENKINS-12124 random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded This happens for me now with the FindBugs 4.45 Plug-in and Jenkins 1.496. I downgraded the FindBugs Plug-in to 4.42 and everything works again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Heap dump looks better than before. This time it blew up at "Pipe writer thread: Jenkins-win7" prio=5 tid=16893 RUNNABLE at java.lang.OutOfMemoryError.init(OutOfMemoryError.java:25) at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) Local Variable: java.lang.Class[]#7844 at java.lang.Class.newInstance(Class.java:308) Local Variable: class sun.reflect.GeneratedSerializationConstructorAccessor6164 at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) Local Variable: sun.reflect.MethodAccessorGenerator$1#1 at java.security.AccessController.doPrivileged(Native Method) at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) Local Variable: java.lang.String#60850 Local Variable: sun.reflect.ByteVectorImpl#1 Local Variable: java.lang.Class#9 .. winstone.classLoader.WebappClassLoader seems to be holding on to quite a lot of classes, but this might as well be normal behaviour. What are your current memory settings for the JVM? If they have been omitted please try restarting the JVM with the following flags "-XX:MaxPermSize=256m -Xmx768m -XX:+CMSClassUnloadingEnabled -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/jenkins/memory.dump". To rule out memory leaks with the Winstone container you could also try running Jenkins on Tomcat to see if it helps or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford edited a comment on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Heap dump looks better than before. This time it blew up at "Pipe writer thread: Jenkins-win7" prio=5 tid=16893 RUNNABLE at java.lang.OutOfMemoryError.init(OutOfMemoryError.java:25) at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389) at java.lang.Class.getConstructor0(Class.java:2699) at java.lang.Class.newInstance0(Class.java:326) Local Variable: java.lang.Class[]#7844 at java.lang.Class.newInstance(Class.java:308) Local Variable: class sun.reflect.GeneratedSerializationConstructorAccessor6164 at sun.reflect.MethodAccessorGenerator$1.run(MethodAccessorGenerator.java:381) Local Variable: sun.reflect.MethodAccessorGenerator$1#1 at java.security.AccessController.doPrivileged(Native Method) at sun.reflect.MethodAccessorGenerator.generate(MethodAccessorGenerator.java:377) Local Variable: java.lang.String#60850 Local Variable: sun.reflect.ByteVectorImpl#1 Local Variable: java.lang.Class#9 .. What are your current memory settings for the JVM? If they have been omitted please try restarting the JVM with the following flags "-XX:MaxPermSize=256m -Xmx768m -XX:+CMSClassUnloadingEnabled -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/jenkins/memory.dump". winstone.classLoader.WebappClassLoader seems to be holding on to quite a lot of classes, but this might as well be normal behaviour. To rule out memory leaks with the Winstone container you could also try running Jenkins on Tomcat to see if it helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16255) Jenkins doesn't handle system wide environment variables which exist in different cases
Henrik Skupin created JENKINS-16255 Jenkins doesnt handle system wide environment variables which exist in different cases Issue Type: Bug Affects Versions: current Assignee: Jørgen Tjernø Components: environment-script Created: 03/Jan/13 5:11 PM Description: If system-wide environment variables have been set via /etc/environment those are not accessible if they exist in lower-case and capital case letters. Jenkins combines both variables into a single one, and updates the first detected variable with the value of the second one. Here some examples: Example 1: /etc/environment http_proxy=http://proxy.dmz.example.org:8080 HTTP_PROXY=http://proxy.dmz.example.org:8080 - Jenkins: HTTP_PROXY=http://proxy.dmz.example.org:8080 Example 2: Shell: export test=1 export TEST=2 - Jenkins TEST=1 Jenkins should not modify set environment variables because it will cause problems with tools which rely on the right capitalization. One example is mercurial which needs the lower case version of the proxy configuration. It will no longer work when both variables are set. Environment: Ubuntu 12.04 x86 Project: Jenkins Priority: Major Reporter: Henrik Skupin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16251) HtmlPublisher 1.2 doesn't load from disk under Jenkins 1.492
cedd burge commented on JENKINS-16251 HtmlPublisher 1.2 doesnt load from disk under Jenkins 1.492 I have an instance of Jenkins running on a different server (Jenkins 1.494) that this issue does not effect. Eg version 1.2 of htmlpublisher works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16237) Extended email plugin no longer sends messages on latest
Slide-O-Mix commented on JENKINS-16237 Extended email plugin no longer sends messages on latest Can you post the log output from javamail? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16255) Jenkins doesn't handle system wide environment variables which exist in different cases
Henrik Skupin updated JENKINS-16255 Jenkins doesnt handle system wide environment variables which exist in different cases Change By: Henrik Skupin (03/Jan/13 5:18 PM) Component/s: core Component/s: environment-script This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16255) Jenkins doesn't handle system wide environment variables which exist in different cases
Henrik Skupin updated JENKINS-16255 Jenkins doesnt handle system wide environment variables which exist in different cases Change By: Henrik Skupin (03/Jan/13 5:19 PM) Assignee: JørgenTjernø This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16255) Jenkins doesn't handle system wide environment variables which exist in different cases
Henrik Skupin commented on JENKINS-16255 Jenkins doesnt handle system wide environment variables which exist in different cases Oh and one more example: shell: export test=1 - Jenkins test=1 As you can see we keep the lower letters if no variable with the same name and capital letters 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
[JIRA] (JENKINS-13790) Subversion externals fail
Griffin Myers commented on JENKINS-13790 Subversion externals fail Many thanks to Tom Palmer for his fix. I've manually built the SVN plugin with his mods (followed instructions here: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-BuildingaPlugin) and svn:externals polling functionality seems to be restored. I've tested this with multiple Jenkins projects with wc 1.7 with many, many directory externals without any issues. The only thing I haven't tested are file externals, which I know were also problematic with recent official releases of the 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
[JIRA] (JENKINS-13771) Jenkins not being triggered on a change to an external with new 1.4 SVN plugin.
Griffin Myers commented on JENKINS-13771 Jenkins not being triggered on a change to an external with new 1.4 SVN plugin. Many thanks to Tom Palmer for his fix. I've manually built the SVN plugin with his mods (followed instructions here: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-BuildingaPlugin) and svn:externals polling functionality seems to be restored. I've tested this with multiple Jenkins projects with wc 1.7 with many, many directory externals without any issues. The only thing I haven't tested are file externals, which I know were also problematic with recent official releases of the 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
[JIRA] (JENKINS-16244) View.hasPeople too slow to use in sidepanel.jelly
dogfood commented on JENKINS-16244 View.hasPeople too slow to use in sidepanel.jelly Integrated in jenkins_main_trunk #2169 Result = SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Niklaus Giger commented on JENKINS-13617 64-bit java.lang.OutOfMemoryError: PermGen space Restarted jenkins with the arguments suggested by you. Will let it run for about two days. If I get no memory dumps, I will move the jenkins to run under tomcat6. Thanks a lot for your 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
[JIRA] (JENKINS-15560) Lazy loading cause’s http links from other html pages into Jenkins do not work properly
Jason Swager commented on JENKINS-15560 Lazy loading cause’s http links from other html pages into Jenkins do not work properly Our Jenkins installation (1.496, Win2008R2) is having the same problems. A month ago, it was sporadic - once every 1000 builds or so. But we just finished adding a couple hundred more jobs and the problem got immediately worse. It's not just URLs to builds that is affected - other components also break for the same reason I suspect. The Copy Artifact plugin seems to have a similar problem. It will cause a build failure because it can't download artifacts from a specific build. This will happen repeatedly until someone uses a browser, goes to the job and specifically loads the problematic build. Once the build is display, the job can be run successfully. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15560) Lazy loading cause’s http links from other html pages into Jenkins do not work properly
Jason Swager updated JENKINS-15560 Lazy loading cause’s http links from other html pages into Jenkins do not work properly Due to the nature of this bug, I'm bumping the issue up to Critical. It affects not only core Jenkins functionality, but also the behavior of some plugins. Change By: Jason Swager (03/Jan/13 9:36 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16223) Update periodicbackup-plugin dependency plexus-archiver to 2.2.
Johno Crawford assigned JENKINS-16223 to Johno Crawford Update periodicbackup-plugin dependency plexus-archiver to 2.2. Change By: Johno Crawford (03/Jan/13 9:46 PM) Assignee: emanuelez JohnoCrawford This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13635) Backup warnings when performing tar.gz
Johno Crawford commented on JENKINS-13635 Backup warnings when performing tar.gz What OS is your platform? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13635) Backup warnings when performing tar.gz
Johno Crawford commented on JENKINS-13635 Backup warnings when performing tar.gz duh, Ubuntu Linux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13635) Backup warnings when performing tar.gz
Johno Crawford commented on JENKINS-13635 Backup warnings when performing tar.gz http://www.delorie.com/gnu/docs/tar/tar_114.html GNU tar was based on an early draft of the POSIX 1003.1 ustar standard. GNU extensions to tar, such as the support for file names longer than 100 characters, use portions of the tar header record which were specified in that POSIX draft as unused. Subsequent changes in POSIX have allocated the same parts of the header record for other purposes. As a result, GNU tar is incompatible with the current POSIX spec, and with tar programs that follow it. POSIX mandates that, when a file name cannot fit within 100 to 256 characters (the variance comes from the fact a / is ideally needed as the 156'th character), or a link name cannot fit within 100 characters, a warning should be issued and the file not be stored. Unless some --posix option is given (or POSIXLY_CORRECT is set), I suspect that GNU tar should disobey this specification, and automatically switch to using GNU extensions to overcome file name or link name length limitations. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13635) Backup warnings when performing tar.gz
Johno Crawford resolved JENKINS-13635 as Fixed Backup warnings when performing tar.gz Fixed next build, archiver now creates GNU tars. Change By: Johno Crawford (03/Jan/13 10:12 PM) Status: Open Resolved Assignee: JohnoCrawford 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
[JIRA] (JENKINS-13635) Backup warnings when performing tar.gz
SCM/JIRA link daemon commented on JENKINS-13635 Backup warnings when performing tar.gz Code changed in jenkins User: Johno Crawford Path: src/main/java/org/jenkinsci/plugins/periodicbackup/TarGzStorage.java http://jenkins-ci.org/commit/periodicbackup-plugin/4bf5a1269b2ba39f6a1eb6fefc57f6230aea9c48 Log: Merge pull request #5 from johnou/long-filenames JENKINS-13635: Backup warnings when performing tar.gz Compare: https://github.com/jenkinsci/periodicbackup-plugin/compare/7a3bfc8e44dc...4bf5a1269b2b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13635) Backup warnings when performing tar.gz
SCM/JIRA link daemon commented on JENKINS-13635 Backup warnings when performing tar.gz Code changed in jenkins User: Johno Crawford Path: src/main/java/org/jenkinsci/plugins/periodicbackup/TarGzStorage.java http://jenkins-ci.org/commit/periodicbackup-plugin/8b1d53035609c11acee5e8512104ea9c08810efb Log: JENKINS-13635: Backup warnings when performing tar.gz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13050) No feedback when invalid configuration refuses to save
Johno Crawford assigned JENKINS-13050 to Johno Crawford No feedback when invalid configuration refuses to save Change By: Johno Crawford (03/Jan/13 10:13 PM) Assignee: JohnoCrawford This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16248) URL Trigger plugin doesn't support file:/// URLs
garethbowles commented on JENKINS-16248 URL Trigger plugin doesnt support file:/// URLs FSTrigger works fine for my needs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-2551) Add ability to zip/compress old builds.
SCM/JIRA link daemon commented on JENKINS-2551 Add ability to zip/compress old builds. Code changed in jenkins User: Martin Schroeder Path: core/src/main/java/hudson/console/AnnotatedLargeText.java core/src/main/java/hudson/model/Run.java core/src/main/resources/hudson/model/Run/console.jelly http://jenkins-ci.org/commit/jenkins/346fc998b16f2021cbd6b3bb1cd1878a2b19ff5b Log: Enabled transparent compression support. This only works if the "transparent GZIP support" patch has been applied against Stapler. Otherwise, this patch will not compile as the new "LargeText" constructor will not be found. Additionally, the console.jelly was modified to make use of the stream instead of the raw file, which is necessary to get the correct uncompressed size of the file for skipping bytes. JENKINS-2551 JENKINS-10400 JENKINS-13655 Signed-off-by: Martin Schroeder martin.h.schroe...@intel.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10400) gzip support for consoleText
SCM/JIRA link daemon commented on JENKINS-10400 gzip support for consoleText Code changed in jenkins User: Martin Schroeder Path: core/src/main/java/hudson/console/AnnotatedLargeText.java core/src/main/java/hudson/model/Run.java core/src/main/resources/hudson/model/Run/console.jelly http://jenkins-ci.org/commit/jenkins/346fc998b16f2021cbd6b3bb1cd1878a2b19ff5b Log: Enabled transparent compression support. This only works if the "transparent GZIP support" patch has been applied against Stapler. Otherwise, this patch will not compile as the new "LargeText" constructor will not be found. Additionally, the console.jelly was modified to make use of the stream instead of the raw file, which is necessary to get the correct uncompressed size of the file for skipping bytes. JENKINS-2551 JENKINS-10400 JENKINS-13655 Signed-off-by: Martin Schroeder martin.h.schroe...@intel.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13655) Gzipped log are not shown correctly
SCM/JIRA link daemon commented on JENKINS-13655 Gzipped log are not shown correctly Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/console/AnnotatedLargeText.java core/src/main/java/hudson/model/Run.java core/src/main/resources/hudson/model/Run/console.jelly http://jenkins-ci.org/commit/jenkins/db8c92f736de3222ad0f1638f3893ca270bf877c Log: Merge pull request #586 from HedAurabesh/v1.485_gzip FIXED JENKINS-13655 Enable transparent log decompression support (Jenkins v1.485) Compare: https://github.com/jenkinsci/jenkins/compare/35e1602ed148...db8c92f736de This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13655) Gzipped log are not shown correctly
SCM/JIRA link daemon commented on JENKINS-13655 Gzipped log are not shown correctly Code changed in jenkins User: Martin Schroeder Path: core/src/main/java/hudson/console/AnnotatedLargeText.java core/src/main/java/hudson/model/Run.java core/src/main/resources/hudson/model/Run/console.jelly http://jenkins-ci.org/commit/jenkins/346fc998b16f2021cbd6b3bb1cd1878a2b19ff5b Log: Enabled transparent compression support. This only works if the "transparent GZIP support" patch has been applied against Stapler. Otherwise, this patch will not compile as the new "LargeText" constructor will not be found. Additionally, the console.jelly was modified to make use of the stream instead of the raw file, which is necessary to get the correct uncompressed size of the file for skipping bytes. JENKINS-2551 JENKINS-10400 JENKINS-13655 Signed-off-by: Martin Schroeder martin.h.schroe...@intel.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13635) Backup warnings when performing tar.gz
Johno Crawford commented on JENKINS-13635 Backup warnings when performing tar.gz https://github.com/jenkinsci/periodicbackup-plugin/commit/4bf5a1269b2ba39f6a1eb6fefc57f6230aea9c48 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13655) Gzipped log are not shown correctly
SCM/JIRA link daemon resolved JENKINS-13655 as Fixed Gzipped log are not shown correctly Change By: SCM/JIRA link daemon (03/Jan/13 10:21 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13635) Backup warnings when performing tar.gz
Johno Crawford edited a comment on JENKINS-13635 Backup warnings when performing tar.gz For clarity sake, the new limit is now 256 characters. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12846) config files under users directory not backed up
Johno Crawford assigned JENKINS-12846 to Johno Crawford config files under users directory not backed up Change By: Johno Crawford (03/Jan/13 10:25 PM) Assignee: JohnoCrawford This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13655) Gzipped log are not shown correctly
SCM/JIRA link daemon commented on JENKINS-13655 Gzipped log are not shown correctly Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/310e22dbfc0ef8753066f3059bd7cc82e80605b5 Log: JENKINS-13655 Noting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16248) URL Trigger plugin doesn't support file:/// URLs
SCM/JIRA link daemon commented on JENKINS-16248 URL Trigger plugin doesnt support file:/// URLs Code changed in jenkins User: Nicolas De Loof Path: src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java http://jenkins-ci.org/commit/urltrigger-plugin/73722c47170dff62aa86905b02acc78ac8587271 Log: JENKINS-16248 warn user when non-http URL is used This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16248) URL Trigger plugin doesn't support file:/// URLs
Gregory Boissinot updated JENKINS-16248 URL Trigger plugin doesnt support file:/// URLs Change By: Gregory Boissinot (03/Jan/13 11:21 PM) 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
[JIRA] (JENKINS-12846) config files under users directory not backed up
SCM/JIRA link daemon commented on JENKINS-12846 config files under users directory not backed up Code changed in jenkins User: Johno Crawford Path: src/main/java/org/jenkinsci/plugins/periodicbackup/ConfigOnly.java http://jenkins-ci.org/commit/periodicbackup-plugin/ba70ad8a0a962af35aa0c735e3fa68aa7415b97b Log: Merge pull request #7 from johnou/configonly-backup-users JENKINS-12846: config files under users directory not backed up. Compare: https://github.com/jenkinsci/periodicbackup-plugin/compare/353769d724f2...ba70ad8a0a96 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12846) config files under users directory not backed up
SCM/JIRA link daemon commented on JENKINS-12846 config files under users directory not backed up Code changed in jenkins User: Johno Crawford Path: src/main/java/org/jenkinsci/plugins/periodicbackup/ConfigOnly.java http://jenkins-ci.org/commit/periodicbackup-plugin/33717a9a107940018c36b41972b78b9cb3d3ad0b Log: JENKINS-12846: config files under users directory not backed 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
[JIRA] (JENKINS-13050) No feedback when invalid configuration refuses to save
Johno Crawford commented on JENKINS-13050 No feedback when invalid configuration refuses to save What browser are you using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12846) config files under users directory not backed up
Johno Crawford resolved JENKINS-12846 as Fixed config files under users directory not backed up users directory will be backed up in the next build. Change By: Johno Crawford (03/Jan/13 11:36 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12846) config files under users directory not backed up
Johno Crawford edited a comment on JENKINS-12846 config files under users directory not backed up users directory will be backed up in the next build (1.3). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13655) Gzipped log are not shown correctly
dogfood commented on JENKINS-13655 Gzipped log are not shown correctly Integrated in jenkins_main_trunk #2172 JENKINS-13655 Noting. (Revision 310e22dbfc0ef8753066f3059bd7cc82e80605b5) Result = SUCCESS Jesse Glick : 310e22dbfc0ef8753066f3059bd7cc82e80605b5 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
