[JIRA] (JENKINS-17165) Publish over FTP plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504
Ramakrishna Bejawar created JENKINS-17165 Publish over FTP plugin with version 1.9 doesnt work after Jenkins upgrade to Version 1.504 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: publish-over-ftp Created: 12/Mar/13 6:51 AM Description: I upgraded my Jenkins to Version 1.504, afer that "Publish over FTP" plugin with version 1.9 does'nt work. Suspecting Is it the issue after Jenkins upgrade or else issue is with the plugin. Please kindly investigate on "publish over ftp" plug-in with version 1.9. Thanks.. Environment: on RHEL 6.2 Fix Versions: current Project: Jenkins Labels: jenkins plugin publishing ftp Priority: Major Reporter: Ramakrishna Bejawar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17166) Counting in the Test Trend Chart differs to the number of tests in the Grid
Thomas Fürer created JENKINS-17166 Counting in the Test Trend Chart differs to the number of tests in the Grid Issue Type: Bug Assignee: Peter Hayes Attachments: countingFailure.PNG Components: dashboard-view Created: 12/Mar/13 7:26 AM Description: As the screenshot demonstrate, the total count of tests is in my suite 8138 but the Trend Chart shows me more then 9000 tests. Settings: "640x220", "All Tests" in the last "30" days Environment: Jenkins: 1.496 Dashboard-plugin: 2.4 Project: Jenkins Priority: Major Reporter: Thomas Fürer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17165) Publish over FTP plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504
bap assigned JENKINS-17165 to bap Publish over FTP plugin with version 1.9 doesnt work after Jenkins upgrade to Version 1.504 Change By: bap (12/Mar/13 7:54 AM) Assignee: bap This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16840) Unable to connect to Mantis
sogabe commented on JENKINS-16840 Unable to connect to Mantis "(cause Access denied)" means that your mantis account is not allowed to connect it. Check your mantis account. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16786) Please make the N/A white, not black. :-)
Andreas Sandberg commented on JENKINS-16786 Please make the N/A white, not black. :-) I agree with Jason, we have a couple of Jenkins jobs that do not run code coverage (they are not build jobs), and I also think that the column should rather be visible if selected instead of the opposite. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17167) Add search box support
Ulli Hafner created JENKINS-17167 Add search box support Issue Type: New Feature Assignee: Ulli Hafner Components: analysis-core Created: 12/Mar/13 8:42 AM Description: Jenkins has an extension point to provide shortcuts using the search box: https://wiki.jenkins-ci.org/display/JENKINS/Search+Box Project: Jenkins Priority: Minor Reporter: Ulli Hafner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-9066) Aggregation of downstream project reports for static analysis reports
Ulli Hafner updated JENKINS-9066 Aggregation of downstream project reports for static analysis reports Change By: Ulli Hafner (12/Mar/13 8:45 AM) Issue Type: Improvement NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17168) Integrate functionality of analysis-collector plug-in into analysis-core
Ulli Hafner created JENKINS-17168 Integrate functionality of analysis-collector plug-in into analysis-core Issue Type: New Feature Assignee: Ulli Hafner Components: analysis-collector, analysis-core Created: 12/Mar/13 8:47 AM Project: Jenkins Priority: Major Reporter: Ulli Hafner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-2776) Show SupressWarnings directives of PMD report
Ulli Hafner updated JENKINS-2776 Show SupressWarnings directives of PMD report Change By: Ulli Hafner (12/Mar/13 8:56 AM) Issue Type: Improvement NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17145) URLTrigger gives severe error message, envinject NPE
dmeibusch commented on JENKINS-17145 URLTrigger gives severe error message, envinject NPE This is with version 0.28. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17169) Add navigation support using the context menu
Ulli Hafner updated JENKINS-17169 Add navigation support using the context menu Change By: Ulli Hafner (12/Mar/13 10:34 AM) Description: Thestaticanalysisplug-insshouldprovidesomeactionsforthenewcontextmenuinordertosimplifythenavigationtotheresults. *Navigatetotheneworfixedwarnings*Navigatetowarningsbypriority(ifavailable)*Navigatetowarningsbymodule(ifavailable) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17169) Add navigation support using the context menu
Ulli Hafner created JENKINS-17169 Add navigation support using the context menu Issue Type: New Feature Assignee: Ulli Hafner Components: analysis-core Created: 12/Mar/13 10:32 AM Description: The static analysis plug-ins should provide some actions for the new context menu in order to simplify the navigation to the results. Project: Jenkins Priority: Minor Reporter: Ulli Hafner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17168) Integrate functionality of analysis-collector plug-in into analysis-core
Ulli Hafner updated JENKINS-17168 Integrate functionality of analysis-collector plug-in into analysis-core Change By: Ulli Hafner (12/Mar/13 10:36 AM) Description: Currentlyanadditionalplug-inisrequiredinordertoshowtheaggregationviews.However,itmakesmoresensetointegratethisfunctionalityintoanalysiscoreandexposetheavailableplug-insusinganextensionpoint.Sootherplug-insthatderiveontheanalysis-coreplug-inwillautomaticallybenefitfromthesefeatures. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Michael Pailloncy updated JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request Change By: Michael Pailloncy (12/Mar/13 10:50 AM) Labels: auto-installcore perforce performance tools This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Michael Pailloncy created JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request Issue Type: Bug Assignee: Unassigned Attachments: config-JDK-installs.txt, nexus-access-log.txt Components: core Created: 12/Mar/13 10:50 AM Description: I've configured automatic tools installation (JDK, Maven, Git, ...) in Jenkins with "Extract .zip/.tar" feature pointing to a Nexus URL (like this : "http://nexus:8081/nexus/content/repositories/jenkins-ci-tools/fr/mipih/ic/tools/jdk/oracle-hotspot/1.6.0_25_64bits/oracle-hotspot-1.6.0_25_64bits-linux.zip"). An example of JDK tools declaration in config.xml is in attachment (config-JDK-installs.txt). The problem is that Jenkins floods Nexus of HTTP requests corresponding to all of this tools every minute. This feature has been improved by https://issues.jenkins-ci.org/browse/JENKINS-16215 in the version 1.500 of Jenkins but Nexus still faces with a flood of requests returning 304 response. I've activated access logs of Nexus (nexus-access-log.txt). Each minute, between 26 and 28 seconds, Jenkins creates more than 130 HTTP request to get all tools parametered in global configuration. I've 13 tools configured in global configuration. 96 HTTP requests only for oracle-hotspot-1.6.0_25_64bits-linux.zip in 3 seconds. I've created this ticket with Critical priority because Nexus is overloaded each day. I've tried to look in Jenkins core but I cannot see why Jenkins is trying to download again and again these tools. Any idea ? Jenkins is supposed to call the auto-installer feature only when a build which need a non installed tools is triggered right ? Are there any other cases ? Thanks in advance! Environment: Jenkins 1.504 - RHEL 6 - JDK 1.6 Hotspot 9 slaves node (1 AIX, 5 RHEL, 3 Windows) Project: Jenkins Labels: core perforce auto-install tools Priority: Critical Reporter: Michael Pailloncy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Michael Pailloncy updated JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request Change By: Michael Pailloncy (12/Mar/13 10:53 AM) Description: Iveconfiguredautomatictoolsinstallation(JDK,Maven,Git,...)inJenkinswithExtract*.zip/*.tarfeaturepointingtoaNexusURL(likethis:http://nexus:8081/nexus/content/repositories/jenkins-ci-tools/fr/mipih/ic/tools/jdk/oracle-hotspot/1.6.0_25_64bits/oracle-hotspot-1.6.0_25_64bits-linux.zip).AnexampleofJDKtoolsdeclarationinconfig.xmlisinattachment(config-JDK-installs.txt).TheproblemisthatJenkinsfloodsNexusofHTTPrequestscorrespondingtoallofthistoolseveryminute.Thisfeaturehasbeenimprovedbyhttps://issues.jenkins-ci.org/browse/JENKINS-16215intheversion1.500ofJenkinsbutNexusstillfaceswithafloodofrequestsreturning304response.IveactivatedaccesslogsofNexus(nexus-access-log.txt).Eachminute,between26and28seconds,Jenkinscreatesmorethan130HTTPrequeststryingtodownloadalltoolsparameteredinglobalconfiguration.Ive13toolsconfiguredinglobalconfiguration.96HTTPrequestsonlyfororacle-hotspot-1.6.0_25_64bits-linux.zipin3seconds.IvecreatedthisticketwithCriticalprioritybecauseNexusisoverloadedeachday.IvetriedtolookinJenkinscorebutIcannotseewhyJenkinsistryingtodownloadagainandagainthesetools.Anyidea?Jenkinsissupposedtocalltheauto-installerfeatureonlywhenabuildwhichneedanoninstalled tools tool istriggeredright?Arethereanyothercases?Thanksinadvance! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Michael Pailloncy updated JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request Change By: Michael Pailloncy (12/Mar/13 10:52 AM) Description: Iveconfiguredautomatictoolsinstallation(JDK,Maven,Git,...)inJenkinswithExtract*.zip/*.tarfeaturepointingtoaNexusURL(likethis:http://nexus:8081/nexus/content/repositories/jenkins-ci-tools/fr/mipih/ic/tools/jdk/oracle-hotspot/1.6.0_25_64bits/oracle-hotspot-1.6.0_25_64bits-linux.zip).AnexampleofJDKtoolsdeclarationinconfig.xmlisinattachment(config-JDK-installs.txt).TheproblemisthatJenkinsfloodsNexusofHTTPrequestscorrespondingtoallofthistoolseveryminute.Thisfeaturehasbeenimprovedbyhttps://issues.jenkins-ci.org/browse/JENKINS-16215intheversion1.500ofJenkinsbutNexusstillfaceswithafloodofrequestsreturning304response.IveactivatedaccesslogsofNexus(nexus-access-log.txt).Eachminute,between26and28seconds,Jenkinscreatesmorethan130HTTP request requeststrying to get download alltoolsparameteredinglobalconfiguration.Ive13toolsconfiguredinglobalconfiguration.96HTTPrequestsonlyfororacle-hotspot-1.6.0_25_64bits-linux.zipin3seconds.IvecreatedthisticketwithCriticalprioritybecauseNexusisoverloadedeachday.IvetriedtolookinJenkinscorebutIcannotseewhyJenkinsistryingtodownloadagainandagainthesetools.Anyidea?Jenkinsissupposedtocalltheauto-installerfeatureonlywhenabuildwhichneedanoninstalledtoolsistriggeredright?Arethereanyothercases?Thanksinadvance! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-13915) NPE Exception, possibly caused by disabled jobs?
Ben Golding resolved JENKINS-13915 as Fixed NPE Exception, possibly caused by disabled jobs? This issue hasn't occurred for a while for me (I'm currently using 0.8) so marking fixed. Change By: Ben Golding (12/Mar/13 10:57 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15519) BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException
Ben Golding resolved JENKINS-15519 as Fixed BuildFlow job randomly fails with FATAL: null java.lang.NullPointerException JENKINS-13915 now marked fixed (in 0.8), also marking this one as fixed. Change By: Ben Golding (12/Mar/13 10:59 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
kutzi commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Did you look into http://stackoverflow.com/questions/9330367/how-to-configure-jenkins-to-run-on-port-80 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17171) Token macro expansion not working in Groovy plugin 1.13
Marco Clemencic
created JENKINS-17171
Token macro expansion not working in Groovy plugin 1.13
Issue Type:
Bug
Affects Versions:
current
Assignee:
vjuranek
Components:
groovy
Created:
12/Mar/13 11:21 AM
Description:
Hi,
I've been happily using the Groovy plugin 1.12 to execute some complex code in the macro expansion.
Unfortunately, in 1.13 it does not work anymore. This is what I get in the output of a job:
FATAL: null
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:542)
at groovy.lang.Binding.setVariable(Binding.java:77)
at groovy.lang.GroovyShell.setVariable(GroovyShell.java:568)
at hudson.plugins.groovy.SystemGroovy.perform(SystemGroovy.java:76)
at hudson.plugins.groovy.GroovyTokenMacro.evaluate(GroovyTokenMacro.java:68)
at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:177)
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:177)
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:153)
at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setDisplayName(BuildNameSetter.java:50)
at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setUp(BuildNameSetter.java:37)
at hudson.model.Build$BuildExecution.doRun(Build.java:154)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:593)
at hudson.model.Run.execute(Run.java:1567)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
For the test I used the Build Name Setter plugin with the option
${GROOVY,script="return 'build_name'"}
but the failure is reproducible with anything that call token expansion and with any Groovy code (I use something more complex than that in my real jobs).
To be able to work I had to revert 1.12, but I would profit from the change in 1.13 because I actually need to manipulate an environment variable in the token.
Thanks
Marco
Project:
Jenkins
Priority:
Blocker
Reporter:
Marco Clemencic
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-17154) CppCheck plugin cannot process result xml from slave node
Balint Kovacs commented on JENKINS-17154 CppCheck plugin cannot process result xml from slave node Workaround: On slave (creating result) Run cppcheck script to create cppcheck-result.xml Setup "Archive the artifacts" postbuild action to archive cppcheck-result.xml On master (publishing result) Add a build step to copy artifacts from another project Publish cpp checker result This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17154) CppCheck plugin cannot process result xml from slave node
Balint Kovacs updated JENKINS-17154 CppCheck plugin cannot process result xml from slave node Change By: Balint Kovacs (12/Mar/13 11:26 AM) Priority: Critical Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17171) Token macro expansion not working in Groovy plugin 1.13
Marco Clemencic updated JENKINS-17171 Token macro expansion not working in Groovy plugin 1.13 Change By: Marco Clemencic (12/Mar/13 11:35 AM) Environment: Jenkins1.505,Groovy1.13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15714) HTTP 500 Internal Exception accessing Maven Repository URL for specific builds
dmeibusch commented on JENKINS-15714 HTTP 500 Internal Exception accessing Maven Repository URL for specific builds Is there anyway we can move this issue 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-12660) Fail to start the windows service when trying to launch slave node
Per Arnold Blaasmo commented on JENKINS-12660 Fail to start the windows service when trying to launch slave node Adding ".\" before the username worked for me. Using '.\' is the same as using the local domain. If you type in .\ before the username, that will instruct it that you are logging onto the local computer. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17172) JDepend - handle multi project builds and wildcards paths
cforce created JENKINS-17172 JDepend - handle multi project builds and wildcards paths Issue Type: New Feature Assignee: Unassigned Components: jdepend Created: 12/Mar/13 12:02 PM Description: Jpendend only allows one relative or aboslute path and so only one jdepend source file to be recognized. We have a build project which runs several project builds in own jenkins job and so created several jpdend files. The plugin shall be able to handle many files and integrate them in one report. This needs the plugins also to be able to read from several paths and therfore shall support multipath config and wildcards like */reports/jdepend.xml (searches in any subfolder with name reports in any folder deep level for file with name starting with jdepend and ending with extension.xml Project: Jenkins Priority: Major Reporter: cforce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16287) Race condition in 'build' CLI command
Adam Szikes commented on JENKINS-16287 Race condition in build CLI command I have the same problem as well. Jenkins 1.492, XP x86 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16929) GNU make + GCC parser can't handle UTF-8
SCM/JIRA link daemon commented on JENKINS-16929 GNU make + GCC parser cant handle UTF-8 Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/WarningsPublisher.java http://jenkins-ci.org/commit/warnings-plugin/5934c43401b60d239f6a8820e15ee67be5c5afc7 Log: FIXED JENKINS-16929 Use UTF-8 encoding when parsing the console log. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
Andreas Sandberg updated JENKINS-10442 RestartNotSupportedException when trying to do safeRestart Change By: Andreas Sandberg (12/Mar/13 1:01 PM) Environment: Jenkins1.421onRHEL5.4x86_64 ,alsoreproducedonJenkins1.505 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-10442) RestartNotSupportedException when trying to do safeRestart
Andreas Sandberg commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart Same error when navigating to /restart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-10537) java.net.SocketTimeoutException: Read timed out
Ireneusz Makowski commented on JENKINS-10537 java.net.SocketTimeoutException: Read timed out I have the same issue on 1.480.3 >From time to time my slaves are going down This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17174) Javascript proxy failes when sending html/xml formated messages
Marcus Jacobsson updated JENKINS-17174 _javascript_ proxy failes when sending html/xml formated messages Change By: Marcus Jacobsson (12/Mar/13 1:10 PM) Environment: Jenkins1.480.3 testedonUbuntu12.04andWindows7bothusingdebuginginmavenandtomcat This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-6691) EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active
Kevin Fleming commented on JENKINS-6691 EC2 plugin will launch more instances than cap allows if enough jobs are queued up while no instances are active Ahh... oops. I'm wrong This is fixed in a branch of mine that is queued for the 1.19 release of the plugin; there is a build currently being tested to be the 1.18 release. Once that is pushed out Francis plans to merge my template-instance-cap-fix branch, which corrects this issue among others, but requires Jenkins 1.503 or later. If you'd like to help test my branch, it's at github.com/kpfleming/jenkins-ec2-plugin, called template-instance-cap-fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17175) User.getBuilds too slow to render synchronously
Jesse Glick created JENKINS-17175 User.getBuilds too slow to render synchronously Issue Type: Bug Assignee: Jesse Glick Components: core Created: 12/Mar/13 1:49 PM Description: /user/*/builds calls User.getBuilds which traverses all projects and looks for builds authored by that person. The search is limited to the past week or 10 builds; but 10 builds for every project is still a lot, and a project which is frequently built may have many more than 10 builds in the last week. At any rate, the computation is done in the HTTP request thread and in practice can take many seconds to run. Should be moved into ProgressiveRendering instead. Project: Jenkins Labels: performance Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17176) The Restrict matrix execution to subset Groovy filter is not evaluate
Adrien Lecharpentier
created JENKINS-17176
The Restrict matrix execution to subset Groovy filter is not evaluate
Issue Type:
Bug
Assignee:
huybrechts
Components:
parameterized-trigger
Created:
12/Mar/13 2:02 PM
Description:
The "groovy filter" value of the "Restrict matrix execution to subset" is never evaluated. So we cannot use this feature to trigger different jobs depending on a variable value by setting the filter to "${VAR}".contains("alu").
I'm preparing a pull-request for this. I will update the issue then.
Project:
Jenkins
Priority:
Major
Reporter:
Adrien Lecharpentier
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-17013) Git plugin fails with NPE (Jenkins 1.502, 1.503)
SCM/JIRA link daemon commented on JENKINS-17013 Git plugin fails with NPE (Jenkins 1.502, 1.503) Code changed in jenkins User: Nicolas De Loof Path: pom.xml src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/d2e7c1f7c0c91922f37429aea9e79c6ab142a40d Log: JENKINS-17013 NullPointerException when no "Default" GitTool installation is set This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17177) Conditional BuildStep Plugin broken in Maven Project - easily reproducible
Steve Boardwell created JENKINS-17177 Conditional BuildStep Plugin broken in Maven Project - easily reproducible Issue Type: Bug Affects Versions: current Assignee: domi Components: conditional-buildstep, run-condition Created: 12/Mar/13 2:19 PM Description: When the build status is set as FAILURE by a triggered Build in a pre-build step, the current build status is not recognised in a post-build conditional step, and the step in performed regardless of the condition. Steps to reproduce: create a freestyle project 'i_will_fail' add step "run shell" with "exit 1" as content create maven project add pre-build step Trigger 'i_will_fail' block job until 'i_will_fail' returns...leave default marks build as. for the main build some test pom.xml and goals validate (this is irrelevant) post-steps - run regardless of result add a conditional post-build step with current build status success. this step will run even if the build has been marked as failed in the pre-build step. Here is the output from a test I made. Started by user lostinberlin [EnvInject] - Loading node environment variables. Building in workspace /var/lib/jenkins/jobs/_lostinberlin_Sandbox_Maven/workspace Run condition [Current build status] enabling prebuild for step [Execute shell] Run condition [Current build status] enabling prebuild for step [Execute shell] [workspace] $ /bin/sh -xe /tmp/hudson3522507109509654665.sh + echo '_lostinberlin_Sandbox_Maven : Starting...' _lostinberlin_Sandbox_Maven : Starting... Waiting for the completion of _lostinberlin_Sandbox _lostinberlin_Sandbox #18 completed. Result was FAILURE Build step 'Trigger/call builds on other projects' marked build as failure Run condition [Current build status] enabling perform for step [Execute shell] [workspace] $ /bin/sh -xe /tmp/hudson3662062057434345391.sh + echo '_lostinberlin_Sandbox_Maven : In post-build steps. I should not be run...' _lostinberlin_Sandbox_Maven : In post-build steps. I should not be run... Notifying upstream projects of job completion Finished: FAILURE Environment: RHEL 6.2 Project: Jenkins Priority: Major Reporter: Steve Boardwell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17170) Jenkins auto install tools feature floods Nexus of HTTP request
Michael Pailloncy updated JENKINS-17170 Jenkins auto install tools feature floods Nexus of HTTP request Change By: Michael Pailloncy (12/Mar/13 2:35 PM) Description: Iveconfiguredautomatictoolsinstallation(JDK,Maven,Git,...)inJenkinswithExtract*.zip/*.tarfeaturepointingtoaNexusURL(likethis:http://nexus:8081/nexus/content/repositories/jenkins-ci-tools/fr/mipih/ic/tools/jdk/oracle-hotspot/1.6.0_25_64bits/oracle-hotspot-1.6.0_25_64bits-linux.zip).AnexampleofJDKtoolsdeclarationinconfig.xmlisinattachment(config-JDK-installs.txt).TheproblemisthatJenkinsfloodsNexusofHTTPrequests corresponding to allofthis downloadsomeconfigured toolseveryminute.Thisfeaturehasbeenimprovedbyhttps://issues.jenkins-ci.org/browse/JENKINS-16215intheversion1.500ofJenkinsbutNexusstillfaceswithafloodofrequestsreturning304response.IveactivatedaccesslogsofNexus(nexus-access-log.txt).Eachminute,between26and28seconds,Jenkinscreatesmorethan130HTTPrequeststryingtodownload all some toolsparameteredinglobalconfiguration.Ive13toolsconfiguredinglobalconfiguration.96HTTPrequestsonlyfororacle-hotspot-1.6.0_25_64bits-linux.zipin3seconds. Eachtime,therepartitionofHTTPrequestsisthesame:96-oracle-hotspot-1.6.0_25_64bits-linux.zip22-maven-2.2.1.zip5-maven-3.0.3.zip3-ibm-j9-1.5.0_sr8a_32bits.zip3-git-1.7.5.1-aix.zip1-maven-3.0.4.zip1-oracle-hotspot-1.5.0_22_64bits-linux.zip1-oracle-hotspot-1.6.0_26_32bits-windows.zip IvecreatedthisticketwithCriticalprioritybecauseNexusisoverloadedeachday.IvetriedtolookinJenkinscorebutIcannotseewhyJenkinsistryingtodownloadagainandagainthesetools.Anyidea?Jenkinsissupposedtocalltheauto-installerfeatureonlywhenabuildwhichneedanoninstalledtoolistriggeredright?Arethereanyothercases?Thanksinadvance! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17178) Upstream job name/link not listed when job at the bottom of hierarchy
Jakub Czaplicki created JENKINS-17178 Upstream job name/link not listed when job at the bottom of hierarchy Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 12/Mar/13 2:42 PM Description: When a job is at the bottom in a hierarchy of jobs, the "Upstream Projects" list is missing on its "main" page. The dependency graph doesn't show the upstream hierarchy either. Project: Jenkins Labels: jenkins ui upstream downstream Priority: Major Reporter: Jakub Czaplicki This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Thank you, but mine is a RHEL/CentOS flavor, and it is referencing the same process that is failing for me just in the Ubuntu OS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-6744) Need Good Run parameter
Geoff Cummings commented on JENKINS-6744 Need Good Run parameter Yes, I think it is the same as JENKINS-7280 "works just like the existing "Run Parameter", but is filtered to only include builds that have finished and didn't fail" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16345) CLI does not work through reverse proxy
Eric Cambray commented on JENKINS-16345 CLI does not work through reverse proxy Hi, same here (but not the exact same trace) : Exception in thread "main" java.io.EOFException: unexpected stream termination at hudson.remoting.ClassicCommandTransport.create(ClassicCommandTransport.java:100) at hudson.remoting.Channel.init(Channel.java:392) at hudson.remoting.Channel.init(Channel.java:388) at hudson.remoting.Channel.init(Channel.java:349) at hudson.remoting.Channel.init(Channel.java:345) at hudson.remoting.Channel.init(Channel.java:333) at hudson.cli.CLI.connectViaHttp(CLI.java:157) at hudson.cli.CLI.init(CLI.java:140) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:68) at hudson.cli.CLI._main(CLI.java:439) at hudson.cli.CLI.main(CLI.java:374) I had just launch a - "java -jar jenkins-cli.jar -s http://my.jenkins.server version" Any idea? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17013) Git plugin fails with NPE (Jenkins 1.502, 1.503)
SCM/JIRA link daemon commented on JENKINS-17013 Git plugin fails with NPE (Jenkins 1.502, 1.503) Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/9ed0f0ba7969da27609e211e5e6368722534de8d Log: JENKINS-17013 use default git installation if none matches You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober edited a comment on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Thank you, and reading the page this is a similar issue. But mine is a RHEL/CentOS flavor, and it is referencing the same process that is failing for me in the Ubuntu OS. and references a fix that I do not know if there is a authbind system in RHEL/CentOS? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16345) CLI does not work through reverse proxy
Eric Cambray edited a comment on JENKINS-16345 CLI does not work through reverse proxy Hi, same here (but not the exact same trace) : Exception in thread "main" java.io.EOFException: unexpected stream termination at hudson.remoting.ClassicCommandTransport.create(ClassicCommandTransport.java:100) at hudson.remoting.Channel.init(Channel.java:392) at hudson.remoting.Channel.init(Channel.java:388) at hudson.remoting.Channel.init(Channel.java:349) at hudson.remoting.Channel.init(Channel.java:345) at hudson.remoting.Channel.init(Channel.java:333) at hudson.cli.CLI.connectViaHttp(CLI.java:157) at hudson.cli.CLI.init(CLI.java:140) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:68) at hudson.cli.CLI._main(CLI.java:439) at hudson.cli.CLI.main(CLI.java:374) I had just launch a - "java -jar jenkins-cli.jar -s http://my.jenkins.server version" Any idea? The error on the server side : [Tue Mar 12 16:02:12 2013] [error] [client 85.170.86.148] (70007)The timeout specified has expired: Error reading chunk [Tue Mar 12 16:02:12 2013] [error] (-3)Unknown error 18446744073709551613: proxy: prefetch request body failed to 127.0.0.1:8080 (localhost) from 85.170.86.148 () This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17064) Unable to edit some build definitions
Alex Earl commented on JENKINS-17064 Unable to edit some build definitions I'm pretty sure I fixed this in https://github.com/jenkinsci/email-ext-plugin/commit/d9c22323105baa7902a6bd25a49b04a717dbe82c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17161) email-ext Default Content does not process text for environment variables, even though default subject does
Alex Earl commented on JENKINS-17161 email-ext Default Content does not process text for environment variables, even though default subject does So, this is not 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] (JENKINS-17101) Not able to login with chrome, chromium, opera - Only works with firefox
Martin K. commented on JENKINS-17101 Not able to login with chrome, chromium, opera - Only works with firefox Upgraded to Jenkins ver. 1.505 = still not possible to login. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17127) Pass DISPLAY as environment variable to Maven builds
zregvart commented on JENKINS-17127 Pass DISPLAY as environment variable to Maven builds Hi Uwe, are you certain that jenkins started the firefox process? From what I see in your example output parent process of the firefox process has PID 31323, whilst maven/java processes have PID 31236 and 31202. DISPLAY environment variable should be set in all processes started by the jenkins job, even in the ones started by "Invoke top-level Maven targets". You can check this with exec-maven-plugin, i.e.: ?xml version="1.0" encoding="UTF-8"? project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd" modelVersion4.0.0/modelVersion groupIdfreestyle/groupId artifactIdsample/artifactId packagingjar/packaging version1.0.0-SNAPSHOT/version build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId version1.2.1/version executions execution idshow-display/id phasecompile/phase goals goalexec/goal /goals configuration executableenv/executable /configuration /execution /executions /plugin /plugins /build /project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17178) Upstream job name/link not listed when job at the bottom of hierarchy
Jakub Czaplicki updated JENKINS-17178 Upstream job name/link not listed when job at the bottom of hierarchy Change By: Jakub Czaplicki (12/Mar/13 3:45 PM) Description: Asubprojectjobdoesnt Subprojectjobsdonot showtheUpstreamProjects.Thedependencygraphdoesntshowtheupstreamhierarchyeither. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17178) Upstream job name/link not listed when job at the bottom of hierarchy
Jakub Czaplicki updated JENKINS-17178 Upstream job name/link not listed when job at the bottom of hierarchy Change By: Jakub Czaplicki (12/Mar/13 3:45 PM) Description: Whena Asubproject job isat doesntshow the bottominahierarchyofjobs,the UpstreamProjects listismissingonitsmainpage .Thedependencygraphdoesntshowtheupstreamhierarchyeither. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16140) Clock on this slave is out of sync with the master
Ed Randall edited a comment on JENKINS-16140 Clock on this slave is out of sync with the master Are you sure it is jenkins' responsibility to synchronize the clock (it is an operating system service after all). Can you not use the appropriate VM service or NTP to synchronize the clocks? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16140) Clock on this slave is out of sync with the master
Ed Randall commented on JENKINS-16140 Clock on this slave is out of sync with the master Are you sure it is jenkmins' responsibility to synchronize the clock (it is an operating system service after all). Can you not use the appropriate VM service or NTP to synchronize the clocks? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16646) Git push tag only in case if build SUCCESS only, UNSTABLE result is not push a tag.
Nicolas De Loof commented on JENKINS-16646 Git push tag only in case if build SUCCESS only, UNSTABLE result is not push a tag. if "UNSTABLE status in general can be "stable" with warnings" then your job is just misconfigured. if "warnings" aren't relevant they shouldn't break the build. I don't consider an UNSTABLE build to be production-ready, so should not be tagged and go further in the build-pipeline This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-14321) Git plugin's 'Fast remote polling' uses slave environment, not master environment.
SCM/JIRA link daemon commented on JENKINS-14321 Git plugins Fast remote polling uses slave environment, not master environment. Code changed in jenkins User: ciaranj Path: src/main/java/hudson/plugins/git/util/GitUtils.java http://jenkins-ci.org/commit/git-plugin/df304f7fe1d85798410ad7c3165a7d3cadcb4d05 Log: FIXES JENKINS-14321 - Do not re-use last build's environment for remote polling Fixes, the original 'fix' in 3d9a73d26b129249c51fccfca6060280197b25eb it appears that a crucial check on the newly implemented argument wasn't actually implemented. I've changed the condition to test this rather than set 'b' to null if reuseLastBuildEnv is set to true as 'b' is de-referenced later in the getPollEnvironment method. Rather worryingly it appears that the existing code in getPollEnvironment tests at one point whether 'b' is null, but then later (outside this test) derefences it anyway, but this commit does not make that particular problem any worse. Signed-off-by: ciaranj ciar...@gmail.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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-14321) Git plugin's 'Fast remote polling' uses slave environment, not master environment.
SCM/JIRA link daemon commented on JENKINS-14321 Git plugins Fast remote polling uses slave environment, not master environment. Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/util/GitUtils.java http://jenkins-ci.org/commit/git-plugin/18e799814060256cabc7b607c919f356c184352f Log: Merge pull request #102 from ciaranj/make_fast_poll_use_master_env FIXES JENKINS-14321 - Do not re-use last build's environment for remote polling Compare: https://github.com/jenkinsci/git-plugin/compare/90a8af41cabe...18e799814060 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
kutzi commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Yes, I've seen that you're using a different Linux flavor, but I think the general problem is the same. And furthermore I wanted to point out that this looks like a general Linux issue - i.e. that you cannot bind to a port 1024 with a non-root user - and not a Jenkins issue per se. If you search on the web you'll surely find several pages which describe how to solve this in general for RHEL. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17179) allow to configure where plugin created its own jdepend file
cforce created JENKINS-17179 allow to configure where plugin created its own jdepend file Issue Type: New Feature Assignee: Unassigned Components: jdepend Created: 12/Mar/13 4:10 PM Description: I have the problem that of #issue JENKINS-17172 i can't reuse my jdpened file and therfore hoped that the plugin will create itself, so left the path edit field empty. The plugin tried to create file here " C:\opt\Tomcat\temp\jdepend6688434096236663120.xml" where i have no write rights, only on path D:\. If i set another path th eplugin tried to read existing file from where i expect it to write its own file to. It's a chicken egg problem because its two things which are triggered with on path. I need to configure where to create the file, or even know which envrionment variables is used. Project: Jenkins Priority: Major Reporter: cforce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. I understand what you are saying about binding to the port it just like the Apache user for httpd and port 80, but this issue also manifest when I try to make this a headless system and change the port to -1 That is what lead me to this as an issue with the Jenkins system and not a port binding issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Jesse Glick commented on JENKINS-15156 Builds disappear from build history after completion Jenkins changelogs are not particularly trustworthy. The last commit did not add a changelog entry since it was done just to fix a test failure; I never reproduced any user-visible problem. I will add one now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17159) Exception using notifyCommit with a bare path
Jesse Glick resolved JENKINS-17159 as Not A Defect Exception using notifyCommit with a bare path /local/filesystem/path is not an (absolute) URL. If that happened to work in earlier releases, it was by accident. Change By: Jesse Glick (12/Mar/13 4:22 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15156) Builds disappear from build history after completion
SCM/JIRA link daemon commented on JENKINS-15156 Builds disappear from build history after completion Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/c596ed517c3f67bff172cfa0d3ac62e01d35dd54 Log: JENKINS-15156 Noting. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-6203) Git plugin uses default encoding to read change log file
SCM/JIRA link daemon commented on JENKINS-6203 Git plugin uses default encoding to read change log file Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitChangeLogParser.java src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/cdf149a73a51861bff07897aa42fa0535b88f99e Log: FIXED JENKINS-6203 force UTF-8 when reading change log according to https://www.kernel.org/pub/software/scm/git/docs/git-log.html, git CLI uses UTF-8 by default to produce change log entries, so no impact on git-client. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16932) Exception: net.sf.json.JSONException: JSONObject[tag] not found when doing a rebuild
Marco Clemencic commented on JENKINS-16932 Exception: net.sf.json.JSONException: JSONObject[tag] not found when doing a rebuild Hi, I just got hit by this bug, but I found an easy work-around that can help for the fix. In my (complex) configuration, I have a parameterized job that triggers another one using the parameterized trigger. To simplify the configuration I use the parameters set "Current build parameters", which ends up sending to the triggered job more parameters than what it actually accepts. With Jenkins 1.500 and Rebuild 1.16 it worked, but now I'm using Jenkins 1.505 and Rebuild 1.18 and it does not work anymore. If I modify the configuration of the job I'm triggering to add dummy versions of the missing parameters, then the rebuilding works again I hope it helps. Cheers Marco This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17013) Git plugin fails with NPE (Jenkins 1.502, 1.503)
Nicolas De Loof commented on JENKINS-17013 Git plugin fails with NPE (Jenkins 1.502, 1.503) git-client 1.0.4 + git 1.3.0 includes a workaround trying to address this issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Per the docs and the notes this setting should be modifiable, and the system should use the non-privileged user that is set it the /etc/sysconfig/jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16932) Exception: net.sf.json.JSONException: JSONObject[tag] not found when doing a rebuild
Marco Clemencic commented on JENKINS-16932 Exception: net.sf.json.JSONException: JSONObject[tag] not found when doing a rebuild I'm sorry, I've been too quick in adding the comment... I checked a bit better and I noticed that the only parameter that needs to be passed over to the triggered job is that of type "Node". My trigger job has got a parameter node of type Node. If the triggered job does have a parameter "node" (type String is enough), then it works, but removing that dummy parameter breaks the rebuild. Cheers Marco This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17180) Support for bugzilla instance per project
Prachi Kumari created JENKINS-17180 Support for bugzilla instance per project Issue Type: Improvement Assignee: Unassigned Components: bugzilla Created: 12/Mar/13 5:07 PM Description: We have several projects that we want to build and test automatically using Jenkins. The problem we face right now is that some of these projects already have their own Bugzilla installations to take care of issue tracking. Because of multiple partners in the projects, it is not possible to move all those different Bugzilla installations to a new common location. Hence, this shortcoming of Jenkins that we cannot configure bug tracking per project is a major impediment that we are unable to start using Jenkins. Environment: All Project: Jenkins Labels: jenkins issue-tracking Priority: Major Reporter: Prachi Kumari This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-11547) Jobs trigger continually even though there are no changes due to git repository being corrupt
Nicolas De Loof resolved JENKINS-11547 as Fixed Jobs trigger continually even though there are no changes due to git repository being corrupt fixed by switching to JGit implementation in git-client plugin using git cli and parsing output is a fragile solution that I expect to fully replace with pure JGit Change By: Nicolas De Loof (12/Mar/13 5:08 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17181) A list of all bugs/issues per project
Prachi Kumari created JENKINS-17181 A list of all bugs/issues per project Issue Type: Improvement Assignee: Unassigned Components: dashboard-view Created: 12/Mar/13 5:11 PM Description: In the current version of Jenkins, there is no possibility to see a complete list of all bugs, fixed bugs, open bugs etc. per project. Environment: All Project: Jenkins Labels: jenkins issue-tracking bugtracker dashboard Priority: Major Reporter: Prachi Kumari This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17180) Support for bugzilla instance per project
Prachi Kumari updated JENKINS-17180 Support for bugzilla instance per project Change By: Prachi Kumari (12/Mar/13 5:13 PM) Labels: bugtracker issue-trackingjenkins 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] (JENKINS-17181) A list of all bugs/issues per project
Prachi Kumari updated JENKINS-17181 A list of all bugs/issues per project Change By: Prachi Kumari (12/Mar/13 5:14 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] (JENKINS-15156) Builds disappear from build history after completion
dogfood commented on JENKINS-15156 Builds disappear from build history after completion Integrated in jenkins_main_trunk #2362 JENKINS-15156 Noting. (Revision c596ed517c3f67bff172cfa0d3ac62e01d35dd54) Result = SUCCESS Jesse Glick : c596ed517c3f67bff172cfa0d3ac62e01d35dd54 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17182) After upgrade of Jenkins and FTP Plugin, transfer set being ignored
Craig Tataryn created JENKINS-17182 After upgrade of Jenkins and FTP Plugin, transfer set being ignored Issue Type: Bug Affects Versions: current Assignee: benjaminjaton Attachments: Screen SharingScreenSnapz003.png Components: ftppublisher Created: 12/Mar/13 6:11 PM Description: Afte upgrading from Jenkins 1.456 to 1.504 and upgrading the FTP Plugin from 1.6 to 1.9, a transfer set I had which was to transfer all *.json files from a folder in my workspace called "generated" stopped working, instead all files from my root workspace folder were uploaded instead (not including subdirectories) WORKAROUND: downgraded to FTP Plugin 1.6, desired transfer set resumed working Project: Jenkins Priority: Major Reporter: Craig Tataryn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17183) Exception: java.lang.NullPointerException
C. Alex Reober created JENKINS-17183 Exception: java.lang.NullPointerException Issue Type: Bug Affects Versions: current Assignee: jieryn Attachments: jenkins_job-import_issue.txt Components: core, job-import Created: 12/Mar/13 6:17 PM Description: Run the job importer Enter the "Remote Jenkins URL:" Hit Query! button Remote Jenkins Job Selection show the job with the check box Check the box Hit Import! GET the info in the attached file. Environment: Jenkins 1.504 and Job-Import Plugin 1.0 Project: Jenkins Priority: Major Reporter: C. Alex Reober This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17183) Exception: java.lang.NullPointerException
C. Alex Reober commented on JENKINS-17183 Exception: java.lang.NullPointerException Could be the same as JENKINS-15040 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16845) NullPointer in getPreviousBuild
Jose Sa commented on JENKINS-16845 NullPointer in getPreviousBuild Jenkins upgraded to 1.505, but errors still shown during initialization causing jobs to fail loading: INFO: Augmented all extensions Mar 12, 2013 12:27:27 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job RS_OSS5_ACOMNDS_LV2_BRINGUP_GA68 java.lang.NullPointerException at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:214) at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:349) at hudson.model.Run.onLoad(Run.java:319) at hudson.model.RunMap.retrieve(RunMap.java:226) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:657) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:640) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:446) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:311) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1043) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:140) at hudson.plugins.robot.RobotProjectAction.getLastBuildWithRobot(RobotProjectAction.java:114) at hudson.plugins.robot.RobotProjectAction.getLastBuildAction(RobotProjectAction.java:67) at hudson.plugins.robot.RobotPublisher.getProjectActions(RobotPublisher.java:210) at hudson.model.Project.createTransientActions(Project.java:211) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:701) at hudson.model.AbstractProject.onLoad(AbstractProject.java:300) at hudson.model.Project.onLoad(Project.java:83) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2540) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:883) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17182) After upgrade of Jenkins and FTP Plugin, transfer set being ignored
Craig Tataryn updated JENKINS-17182 After upgrade of Jenkins and FTP Plugin, transfer set being ignored Change By: Craig Tataryn (12/Mar/13 6:40 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10736) No support for UnitTest XML reporting per sub job when using matrix projects
Ireneusz Makowski edited a comment on JENKINS-10736 No support for UnitTest XML reporting per sub job when using matrix projects Have you look at it? I have the same issue when NUnit report is selected as source This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-10736) No support for UnitTest XML reporting per sub job when using matrix projects
Ireneusz Makowski commented on JENKINS-10736 No support for UnitTest XML reporting per sub job when using matrix projects Have you look at 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] (JENKINS-17183) Exception: java.lang.NullPointerException
C. Alex Reober commented on JENKINS-17183 Exception: java.lang.NullPointerException Confirmed it is not the same issue removed security from the systems and am still getting the error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-14144) Build config history getting spammed
Kevin Behrens commented on JENKINS-14144 Build config history getting spammed I'm seeing this issue too. I wanted to point out that it not only affects the utility of Job config history, but also SCM Sync configuration plugin. My setup is old, dating to 2012/07 jenkins 1.473 envinject 1.60 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17141) Integration with Claim plugin
John Tangney updated JENKINS-17141 Integration with Claim plugin Change By: John Tangney (12/Mar/13 8:37 PM) Component/s: jenkinswalldisplay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16075) Lint icon not shown when selecting a particular build
Mark Wigzell reopened JENKINS-16075 Lint icon not shown when selecting a particular build Installed 1.505 Jenkins with 2.0.3 of Android Lint plugin, lint icon still broken. Reason is that the root of the icon path is doubled in the actual HTML for the respective pages in Jenkins build display. Change By: Mark Wigzell (12/Mar/13 9:09 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16089) Standard view columns interact force builds to be eagerly loaded
SCM/JIRA link daemon commented on JENKINS-16089 Standard view columns interact force builds to be eagerly loaded Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/Util.java core/src/main/java/hudson/model/Job.java core/src/main/java/hudson/model/PermalinkProjectAction.java core/src/main/java/hudson/model/Result.java core/src/main/java/jenkins/model/PeepholePermalink.java http://jenkins-ci.org/commit/jenkins/88feabb4296d6483bdb5c85fed489e5014161ca5 Log: FIXED JENKINS-16089 Remember the permalink target as symlink (or simple text file) so that looking that up doesn't cause the walk of the build history. I think this is more in line with our general preference of making $JENKINS_HOME useful (than trying to persist cache into a blackbox.) Having a general purpose in-memory cache could be useful, so I'll see if I can add that, too, in a way that allows someone to plug different backend. Compare: https://github.com/jenkinsci/jenkins/compare/c596ed517c3f...88feabb4296d You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16089) Standard view columns interact force builds to be eagerly loaded
SCM/JIRA link daemon resolved JENKINS-16089 as Fixed Standard view columns interact force builds to be eagerly loaded Change By: SCM/JIRA link daemon (12/Mar/13 9:41 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17184) Allow setting a custom timeout when unlocking the keychain
Joseph Humphrey created JENKINS-17184 Allow setting a custom timeout when unlocking the keychain Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: xcode Created: 12/Mar/13 10:37 PM Description: I have large project that takes a long to compile after a clean or when the workspace is wiped. Since it takes so long the keychain is locked by time the codesign step is reached so I will always have a failed build after the workspace is cleaned and need to build it a second time. The keychain has an option to set the timeout using set-keychain-settings. The options are to lock the keychain when the system sleeps or after a specified interval. It would be nice to be able to select one of these values and customize a timeout on the unlock keychain step. Due Date: 12/May/13 12:00 AM Environment: Mac Mini - OSX 10.7.5 Project: Jenkins Labels: configuration Priority: Minor Reporter: Joseph Humphrey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16089) Standard view columns interact force builds to be eagerly loaded
dogfood commented on JENKINS-16089 Standard view columns interact force builds to be eagerly loaded Integrated in jenkins_main_trunk #2363 FIXED JENKINS-16089 (Revision 88feabb4296d6483bdb5c85fed489e5014161ca5) Result = UNSTABLE kohsuke : 88feabb4296d6483bdb5c85fed489e5014161ca5 Files : core/src/main/java/jenkins/model/PeepholePermalink.java core/src/main/java/hudson/Util.java core/src/main/java/hudson/model/Result.java core/src/main/java/hudson/model/PermalinkProjectAction.java core/src/main/java/hudson/model/Job.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-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/1c89eec7a83dfdffdc73cf88168e2d5c55f0b512 Log: JENKINS-16248 warn user when non-http URL is used (cherry picked from commit 73722c47170dff62aa86905b02acc78ac8587271) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15098) svnexternals causing issues with concurrent builds
Sai K reopened JENKINS-15098 svnexternals causing issues with concurrent builds I am also seeing the same issue with concurrent builds of the same job on the same node. I am using Linux. Change By: Sai K (12/Mar/13 11:39 PM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17037) Null pointer exception when publishing results
sogabe commented on JENKINS-17037 Null pointer exception when publishing results Are you using phpunit2 task in a build.xml? If so, you have to use exec task as follows. exec dir="." command="phpunit --log-junit 'reports/unitreport.xml' --coverage-html 'reports/coverage' --coverage-clover 'reports/coverage/coverage.xml' test/" / Phpunit2 task generate coverage xml, but it is incompatible with clover. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16907) Conflict with standard clover plugin
sogabe resolved JENKINS-16907 as Duplicate Conflict with standard clover plugin Change By: sogabe (13/Mar/13 12:03 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15626) java.lang.IllegalArgumentException: CloverPublisher is ambiguous; matches both org.jenkinsci.plugins.cloverphp.CloverPublisher and hudson.plugins.clover.CloverPublisher
sogabe assigned JENKINS-15626 to sogabe java.lang.IllegalArgumentException: CloverPublisher is ambiguous; matches both org.jenkinsci.plugins.cloverphp.CloverPublisher and hudson.plugins.clover.CloverPublisher Change By: sogabe (13/Mar/13 12:04 AM) Assignee: stephenconnolly sogabe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17185) Trailing slash shouldn't be required for webhook url
Patrick Connolly updated JENKINS-17185 Trailing slash shouldnt be required for webhook url Change By: Patrick Connolly (13/Mar/13 1:00 AM) Description: Thiswasntmanifestinginthebrowser,asmybrowserwasautomaticallyprefixingtheurlwithaslash,butIfinallyconfirmeditwithplainolcurl`curlhttp://ci. lassonde example . mpdagile. com/github-webhook/`-result:sameerroraboutpayloadthatyouseeinthebrowser`curlcurlhttp://ci. lassonde example . mpdagile. com/github-webhook`-result:silence.nooutput.Ispentlike2hourstryingtofigurethisout,butmostlybecauseIdidntrealizethatthegithubserviceUpdatesettingsbuttonneededtobepushedbeforeTestHookwouldwork.Butthatsanissueforgithub:) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17185) Trailing slash shouldn't be required for webhook url
Patrick Connolly created JENKINS-17185 Trailing slash shouldnt be required for webhook url Issue Type: Bug Assignee: Unassigned Components: github Created: 13/Mar/13 1:00 AM Description: This wasn't manifesting in the browser, as my browser was automatically prefixing the url with a slash, but I finally confirmed it with plain ol curl `curl http://ci.lassonde.mpdagile.com/github-webhook/` result: same error about payload that you see in the browser `curl curl http://ci.lassonde.mpdagile.com/github-webhook` result: silence. no output. I spent like 2 hours trying to figure this out, but mostly because I didn't realize that the github service "Update settings" button needed to be pushed before "Test Hook" would work. But that's an issue for github Environment: github v1.5, Jenkins ver. 1.505 Project: Jenkins Priority: Major Reporter: Patrick Connolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16089) Standard view columns interact force builds to be eagerly loaded
SCM/JIRA link daemon commented on JENKINS-16089 Standard view columns interact force builds to be eagerly loaded Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/AbstractBuild.java core/src/main/java/hudson/model/Job.java core/src/main/java/jenkins/model/PeepholePermalink.java core/src/test/java/hudson/model/StubJob.java test/src/test/groovy/jenkins/model/PeepholePermalinkTest.groovy http://jenkins-ci.org/commit/jenkins/f7c9e810605e89b4f8d841cfc2df2342037982f1 Log: JENKINS-16089 Revising 88feabb4296d6483bdb5c85fed489e5014161ca5 Based on comments from Jesse, revising the fix. I'm now putting permlinks inside the builds/ directory to avoid the computing hassle involved in the split $JENKINS_HOME. What we historically had in $JENKINS_HOME/jobs/JOB/lastSuccessfulBuild is also now subsumed by this feature. I initially attempted to create these permalinks in the buidl root directory, but turns out those symlinks aren't the same name as the ID of permalinks, so it doesn't mesh well. And finally, a test! Compare: https://github.com/jenkinsci/jenkins/compare/88feabb4296d...f7c9e810605e You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15560) Lazy loading cause’s http links from other html pages into Jenkins do not work properly
Kohsuke Kawaguchi commented on JENKINS-15560 Lazy loading cause’s http links from other html pages into Jenkins do not work properly So what exactly happens when you say those links don't work? 404? Something else? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-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 404 error code is the result. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16089) Standard view columns interact force builds to be eagerly loaded
dogfood commented on JENKINS-16089 Standard view columns interact force builds to be eagerly loaded Integrated in jenkins_main_trunk #2364 JENKINS-16089 Revising 88feabb4296d6483bdb5c85fed489e5014161ca5 (Revision f7c9e810605e89b4f8d841cfc2df2342037982f1) Result = UNSTABLE kohsuke : f7c9e810605e89b4f8d841cfc2df2342037982f1 Files : test/src/test/groovy/jenkins/model/PeepholePermalinkTest.groovy core/src/main/java/hudson/model/AbstractBuild.java core/src/main/java/hudson/model/Job.java core/src/main/java/jenkins/model/PeepholePermalink.java core/src/test/java/hudson/model/StubJob.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
