[JIRA] [core] (JENKINS-22247) Provide an extension point to define user id case sensitivity contract
CreativeAdmin CreativeAdmin commented on JENKINS-22247 Provide an extension point to define user id case sensitivity contract Hi, Where is extension point ? Can't see how to allow case insensitve user id. I'm using AD plugin + Role strategy Plugin, last version. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-25394) Sort failure causes on management page
Jan Feindt updated JENKINS-25394 Sort failure causes on management page In my install you can click on name to change ordering Change By: Jan Feindt (12/Nov/14 9:51 AM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25560) Multi-line messages shall be displayed with line breaks
Matthias Moers created JENKINS-25560 Multi-line messages shall be displayed with line breaks Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core-plugin, warnings-plugin Created: 12/Nov/14 9:57 AM Description: We have a compiler that outputs multi-line warnings, like below example: Compiling source file sources/source.c In file included from sources/source.c:25:0: includes/header.h:47:39: warning: 13492 redundant redeclaration of 'symbolXYZ' -Wredundant-decls includes/anotherHeader.h:150:32: note: previous declaration of 'symbolXYZ' was here We have implemented a parser for the warnings plugin that correctly retains the line breaks, but analysis-core plugin displays these messages without line breaks. For debugging purposes the line breaks are very useful, thus the analysis-core plugin shall also display them. Environment: Jenkins 1.565.1 analysis-core 1.57 warnings 4.40 Project: Jenkins Priority: Trivial Reporter: Matthias Moers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [join-plugin] (JENKINS-22348) Join Plugin: intermittent NullPointerException in child project when all downstream projects complete
miguel Rodrigues commented on JENKINS-22348 Join Plugin: intermittent NullPointerException in child project when all downstream projects complete I've been experiencing this issue also. Jenkins logs don't give more information. It is intermittent, regardless of no changes. Any ideas? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-14541) Option to checkout with --quiet (or equivalent)
KY Lee commented on JENKINS-14541 Option to checkout with --quiet (or equivalent) Yes, 80% of my build logs are merely svn checkout logs. If possible, i would like the checkout logs to either be piped to an external file when being quiet but still want something logged that is not part of the build logs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-14541) Option to checkout with --quiet (or equivalent)
Tim-Christian Bloss commented on JENKINS-14541 Option to checkout with --quiet (or equivalent) Same here. svn checkout logs fill between 50% and 90% of our build logs. Would be great if SVN-CheckOut could be quiet by default, only showing messages if starting/finishing checkout (status info) an error occured: print everything a warning occured: print warning a new option like "printAllSvnMessages" is set to true This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25547) Clients on slave nodes are not auto-created
SCM/JIRA link daemon commented on JENKINS-25547 Clients on slave nodes are not auto-created Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/main/java/org/jenkinsci/plugins/p4/workspace/ManualWorkspaceImpl.java src/main/java/org/jenkinsci/plugins/p4/workspace/SpecWorkspaceImpl.java src/main/java/org/jenkinsci/plugins/p4/workspace/StreamWorkspaceImpl.java src/main/java/org/jenkinsci/plugins/p4/workspace/TemplateWorkspaceImpl.java http://jenkins-ci.org/commit/p4-plugin/73a50e272936eead3d83420cd1d185ed61b6bcc6 Log: Clone Workspace Object Seems Jenkins makes re-entrant calls to the PerforceScm Object and caused the Workspace Object to get trampled. JENKINS-25547 Compare: https://github.com/jenkinsci/p4-plugin/compare/064a92708915...73a50e272936 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25303) P4 Plugin slows down Perforce Server
Paul Allen closed JENKINS-25303 as Fixed P4 Plugin slows down Perforce Server 1.0.17 Change By: Paul Allen (12/Nov/14 11:03 AM) Status: Open Closed 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/d/optout.
[JIRA] [p4-plugin] (JENKINS-23974) Private maven repo got wipe out every build
Paul Allen closed JENKINS-23974 as Not A Defect Private maven repo got wipe out every build Resolved by using the Workspace view. Change By: Paul Allen (12/Nov/14 11:06 AM) Status: Reopened Closed 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/d/optout.
[JIRA] [p4-plugin] (JENKINS-24105) Test failures on windows
Paul Allen closed JENKINS-24105 as Fixed Test failures on windows Fixed for 1.0.18 Test framework retries P4D shutdown/connection. Change By: Paul Allen (12/Nov/14 11:08 AM) Status: Open Closed 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/d/optout.
[JIRA] [core] (JENKINS-25561) Wrong column number in executor status table
Donato Tagliabue created JENKINS-25561 Wrong column number in executor status table Issue Type: Bug Assignee: Unassigned Attachments: wrong_executor_table.png Components: core Created: 12/Nov/14 11:08 AM Description: The table for the status of executors (see picture) has a wrong format. This is due I think to an extra column (I've customized the css to have a cell border, but the problem exists in any case). If you look at the HTML source (this is from "Jenkins on Jenkins"): tr th class="pane" colspan="3"a class="model-link inside" href=""img style="width: 16px; height: 16px; " class="icon-computer icon-sm" src="" / celery/a/th /tr tr td class="pane" align="right" style="vertical-align: top"1/td td class="pane"Inattivo/td td class="pane"/td td class="pane"/td /tr the colspan 3 seems incorrect or, viceversa, there is an extra column (td class="pane"/td), which was not present in older versions. Environment: Found in v1.580 and higher. not present in v1.570 Project: Jenkins Priority: Minor Reporter: Donato Tagliabue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Paul Allen closed JENKINS-25341 as Fixed Improve reconcile by using -m option Fixed for 1.0.18 Change By: Paul Allen (12/Nov/14 11:08 AM) Status: Open Closed 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/d/optout.
[JIRA] [core] (JENKINS-25561) Wrong column number in executor status table
Daniel Beck updated JENKINS-25561 Wrong column number in executor status table Change By: Daniel Beck (12/Nov/14 11:13 AM) Labels: user-experience This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-25562) Implement authentication via passphrase-protected private-key
Dmitrijs Sahlovs created JENKINS-25562 Implement authentication via passphrase-protected private-key Issue Type: New Feature Assignee: Unassigned Components: cli Created: 12/Nov/14 11:17 AM Description: For now the only possibility to use password-protected keys is to type password by hands after each command. I would like to automate this process by beeing able to pass password for private key as jenkins-cli parameter. Project: Jenkins Priority: Major Reporter: Dmitrijs Sahlovs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Morne Joubert commented on JENKINS-25341 Improve reconcile by using -m option that was quick!, i was just about to test 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/d/optout.
[JIRA] [viewVC-plugin] (JENKINS-25563) ViewVC links for classic CVS integration are not generated
Daniel Fischer created JENKINS-25563 ViewVC links for classic CVS integration are not generated Issue Type: Bug Assignee: Unassigned Components: viewVC-plugin Created: 12/Nov/14 11:31 AM Description: The ViewVC integration is not working if I configure it under advanced repository properties on the classic "CVS" integration. If I configure the ViewVC repository browser on the "CVS Projectset" the links are shown correctly. I am using Jenkins 1.580.1 LTS on tomcat 6 and CVS Plugin v2.12 and ViewVC Plugin v1.7. Environment: OS: SLES 11 SP3, Jenkins 1.580.1 LTS on tomcat 6 Project: Jenkins Labels: plugin viewvc cvs viewcvs Priority: Major Reporter: Daniel Fischer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-21065) Hijacked files should be overwritten by files from versioned files in vob (our case 10498)
SCM/JIRA link daemon commented on JENKINS-21065 Hijacked files should be overwritten by files from versioned files in vob (our case 10498) Code changed in jenkins User: Mads Nielsen Path: pom.xml http://jenkins-ci.org/commit/config-rotator-plugin/6dab85a6a94011dc2293b7ed815edea6dc57190a Log: Fixed JENKINS-21065, Overwrite hijacked files This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-22058) Infinite loop on hanging rebase (our case 10651)
SCM/JIRA link daemon commented on JENKINS-22058 Infinite loop on hanging rebase (our case 10651) Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java http://jenkins-ci.org/commit/config-rotator-plugin/30d8e4185fc26496ec1321842916cb9fd3c942ac Log: Updated pom to use latest cool for JENKINS-22058 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-23653) Improve performance while establishing view (case 11425)
SCM/JIRA link daemon commented on JENKINS-23653 Improve performance while establishing view (case 11425) Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/FB8790.java http://jenkins-ci.org/commit/config-rotator-plugin/929c7f4d16cbe9e4e1a33fa961fa2b7fbf152e25 Log: Merge pull request #5 from MadsNielsen/JENKINS-23653 Implemented JENKINS-23653 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-22058) Infinite loop on hanging rebase (our case 10651)
SCM/JIRA link daemon commented on JENKINS-22058 Infinite loop on hanging rebase (our case 10651) Code changed in jenkins User: Mads Nielsen Path: Git/tmp_junit1210676878204429626_junit4098927748112959854_git.xml Git/tmp_junit1264708815920718248_junit4828316997464788678_git.xml Git/tmp_junit4084533581155230280_junit6438606225498654317_git.xml Git/tmp_junit42712223923726365_junit9020910868288420916_git.xml Git/tmp_junit438409429968608014_junit2989476551062932327_git.xml Git/tmp_junit8917086491365665766_junit6930540003725199753_git.xml pom.xml src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java src/test/java/net/praqma/jenkins/configrotator/ConfigRotatorProject.java src/test/java/net/praqma/jenkins/configrotator/ConfigRotatorRule.java src/test/java/net/praqma/jenkins/configrotator/ConfigRotatorRule2.java src/test/java/net/praqma/jenkins/configrotator/SystemValidator.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/ConfigTest.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/FB8790.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/JENKINS17830.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/JENKINS22058.java src/test/java/net/praqma/jenkins/configrotator/unit/scm/clearcase/ClearCaseBaseLineCompareTest.java http://jenkins-ci.org/commit/config-rotator-plugin/a668bb7d0c373d9f185d5c902757ee3642d14b96 Log: JENKINS-22058 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-20981) The component selection screen has bugged layout our case 10446
SCM/JIRA link daemon commented on JENKINS-20981 The component selection screen has bugged layout our case 10446 Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/resources/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM/config.jelly http://jenkins-ci.org/commit/config-rotator-plugin/15296c2889b8d54bc3ecfbfc59dda158502578d0 Log: Fixed JENKINS-20981 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-22058) Infinite loop on hanging rebase (our case 10651)
SCM/JIRA link daemon commented on JENKINS-22058 Infinite loop on hanging rebase (our case 10651) Code changed in jenkins User: Mads Nielsen Path: Git/tmp_junit1210676878204429626_junit4098927748112959854_git.xml Git/tmp_junit1264708815920718248_junit4828316997464788678_git.xml Git/tmp_junit4084533581155230280_junit6438606225498654317_git.xml Git/tmp_junit42712223923726365_junit9020910868288420916_git.xml Git/tmp_junit438409429968608014_junit2989476551062932327_git.xml Git/tmp_junit8917086491365665766_junit6930540003725199753_git.xml pom.xml src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java src/test/java/net/praqma/jenkins/configrotator/ConfigRotatorProject.java src/test/java/net/praqma/jenkins/configrotator/ConfigRotatorRule.java src/test/java/net/praqma/jenkins/configrotator/ConfigRotatorRule2.java src/test/java/net/praqma/jenkins/configrotator/SystemValidator.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/ConfigTest.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/FB8790.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/JENKINS17830.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/JENKINS22058.java src/test/java/net/praqma/jenkins/configrotator/unit/scm/clearcase/ClearCaseBaseLineCompareTest.java http://jenkins-ci.org/commit/config-rotator-plugin/39d8ab731f0e345f954842d751c175988c606f51 Log: Merge pull request #4 from MadsNielsen/JENKINS-22058 Fixed JENKINS-22058 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-21066) Config Rotator jobs builds needlessly (our case 10378)
SCM/JIRA link daemon commented on JENKINS-21066 Config Rotator jobs builds needlessly (our case 10378) Code changed in jenkins User: Mads Nielsen Path: src/main/java/net/praqma/jenkins/configrotator/AbstractConfigurationRotatorSCM.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotator.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java http://jenkins-ci.org/commit/config-rotator-plugin/47ce865bcc920a6d2cace254d46e9b7e3c06812b Log: Fixed JENKINS-21066 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-22832) Unable to create view when stream exists ( our case 11220 )
SCM/JIRA link daemon commented on JENKINS-22832 Unable to create view when stream exists ( our case 11220 ) Code changed in jenkins User: Mads Nielsen Path: src/main/java/net/praqma/jenkins/configrotator/AbstractConfigurationRotatorSCM.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java http://jenkins-ci.org/commit/config-rotator-plugin/c290f4773d04113a841f9d6c076d564dfe9f77f4 Log: Fixed JENKINS-22832 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-24822) Reconfiguration not triggered on save when job altered. Our case 12025
SCM/JIRA link daemon commented on JENKINS-24822 Reconfiguration not triggered on save when job altered. Our case 12025 Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotator.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorBuildAction.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java http://jenkins-ci.org/commit/config-rotator-plugin/7fcb755d02449173aa8695e6fa151915517e7d00 Log: Fixed JENKINS-24822 Compare: https://github.com/jenkinsci/config-rotator-plugin/compare/9b6970bfdf89...7fcb755d0244 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-21068) Clarify error messages when invalid component is specified (our case 10417)
SCM/JIRA link daemon commented on JENKINS-21068 Clarify error messages when invalid component is specified (our case 10417) Code changed in jenkins User: Mads Nielsen Path: pom.xml src/main/java/net/praqma/jenkins/configrotator/AbstractConfigurationComponent.java src/main/java/net/praqma/jenkins/configrotator/AbstractConfigurationRotatorSCM.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotator.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorBuildAction.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorFeedAction.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorProjectAction.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorReport.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorRunListener.java src/main/java/net/praqma/jenkins/configrotator/scm/ConfigRotatorChangeLogEntry.java src/main/java/net/praqma/jenkins/configrotator/scm/ConfigRotatorChangeLogSet.java src/main/java/net/praqma/jenkins/configrotator/scm/ConfigRotatorVersion.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCMConfiguration.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCMConfigurationComponent.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/EndView.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/GetConfiguration.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java src/main/java/net/praqma/jenkins/configrotator/scm/git/Git.java src/main/java/net/praqma/jenkins/configrotator/scm/git/GitConfigurationComponent.java src/main/java/net/praqma/jenkins/configrotator/scm/git/GitTarget.java src/main/java/net/praqma/jenkins/configrotator/scm/git/ResolveChangeLog.java src/main/java/net/praqma/jenkins/configrotator/scm/git/ResolveConfigurationComponent.java src/test/java/net/praqma/jenkins/configrotator/functional/ModelTest.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/ClearCaseUCMConfigurationTest.java src/test/java/net/praqma/jenkins/configrotator/functional/scm/clearcase/ConfigTest.java http://jenkins-ci.org/commit/config-rotator-plugin/8e6412f3a0573e2ede3f3b5e0494629cb59a7a45 Log: Fixed JENKINS-21068, implemented better error message This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-21069) Improve the performance of config rotator (our case 10377)
SCM/JIRA link daemon commented on JENKINS-21069 Improve the performance of config rotator (our case 10377) Code changed in jenkins User: Mads Nielsen Path: .gitignore Git/tmp_junit1210676878204429626_junit4098927748112959854_git.xml Git/tmp_junit1264708815920718248_junit4828316997464788678_git.xml Git/tmp_junit4084533581155230280_junit6438606225498654317_git.xml Git/tmp_junit42712223923726365_junit9020910868288420916_git.xml Git/tmp_junit438409429968608014_junit2989476551062932327_git.xml Git/tmp_junit8917086491365665766_junit6930540003725199753_git.xml pom.xml src/main/java/net/praqma/jenkins/configrotator/AbstractConfigurationRotatorSCM.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotator.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorBuildAction.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorFeedAction.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorProjectAction.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorPublisher.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorRunListener.java src/main/java/net/praqma/jenkins/configrotator/ConfigurationRotatorSCMDescriptor.java src/main/java/net/praqma/jenkins/configrotator/scm/ConfigRotatorChangeLogEntry.java src/main/java/net/praqma/jenkins/configrotator/scm/ConfigRotatorChangeLogParser.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCM.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCMConfigRotatorChangeLogParser.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCMConfiguration.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCMPostBuild.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/ClearCaseUCMTarget.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/EndView.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/GetConfiguration.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/LoadEntity.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/NextBaseline.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/PrepareWorkspace.java src/main/java/net/praqma/jenkins/configrotator/scm/clearcaseucm/RemoteUtil.java http://jenkins-ci.org/commit/config-rotator-plugin/02ae5f51ce7ea1221dbb9dfb22c3527c471d96ff Log: FIXED JENKINS-21069 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator-plugin] (JENKINS-24822) Reconfiguration not triggered on save when job altered. Our case 12025
Mads Nielsen resolved JENKINS-24822 as Fixed Reconfiguration not triggered on save when job altered. Our case 12025 Change By: Mads Nielsen (12/Nov/14 11:58 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs
Kevin Phillips commented on JENKINS-19728 Much needed dependency management between jobs That is more-or-less how I envisioned the tool working actually. Just to be clear, here is the rationale behind that particular need. In our case we have numerous interdependent 'modules' in our codebase, which have been mapped onto jobs in Jenkins. Further, the 'unit' tests associated with some of these modules require a significant amount of time to run. So in an effort to improve turnaround time on our farm we try to run unit tests for modules in parallel to compilation processes. This is probably best explained with an example: Suppose Module B depends on Module A, and each one has a compile phase and test phase. Further, suppose each phase takes 5 minutes to complete. If run in sequence - module A build, module A test, module B build, module B test - we'd require 20 minutes for full completion. However, seeing as how module B build really only depends on module A being built we can run module A's tests at the same time, so now we get - module A builds, module A tests and module B builds both run in parallel, module B tests are then run after module B finishes compiling. In this scenario the full time to completion is reduced to 15 minutes. These benefits are even more noticeable in those cases when the 'unit' tests for a module take significantly longer to complete than the average compilation time. When scaled across 20+ interdependent modules this strategy reduced our total build time for a complete end-to-end build from 10+ hours to 3 or less. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Paul Allen commented on JENKINS-25341 Improve reconcile by using -m option Looks like Jenkins Update center release is broken/down. 1.0.18 didn't go out? Investigating... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs
Kevin Phillips edited a comment on JENKINS-19728 Much needed dependency management between jobs That is more-or-less how I envisioned the tool working actually. Just to be clear, the rationale for that particular requirement is caused by the size of our codebase and the sheer time required to build and test all interdependent modules. For example, we have 20+ interdependent modules in our codebase, each of which requiring its own separate compile and test phase. In many cases the test phases take much longer to complete than the compilation phase so we tend to try avoiding execution of unit tests when they are not necessary. We do this currently by only running tests when a compile is performed, and compiles are only performed when there are commits to a module or one of its dependencies. So, if Module B depends on Module A and someone commits a change to Module A we want to build and test Module A then Module B. However, if a change is made only to Module B we don't want to re-build or re-test Module A. We manage this at the moment using commit triggers in Jenkins. When changes are made to Module B we only trigger Module B's compile and test, which will then in turn trigger any downstream modules that depend on 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/d/optout.
[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs
Kevin Phillips edited a comment on JENKINS-19728 Much needed dependency management between jobs That is more-or-less how I envisioned the tool working actually. Just to be clear, the rationale for that particular requirement is caused by the size of our codebase and the sheer time required to build and test all interdependent modules. For example, we have 20+ interdependent modules in our codebase, each of which requiring its own separate compile and test phase. In many cases the test phases take much longer to complete than the compilation phase so we tend to try avoiding execution of unit tests when they are not necessary. We do this currently by only running tests when a compile is performed, and compiles are only performed when there are commits to a module or one of its dependencies. So, if Module B depends on Module A and someone commits a change to Module A we want to build and test Module A then Module B. However, if a change is made only to Module B we don't want to re-build or re-test Module A. We manage this at the moment using commit triggers in Jenkins. When changes are made to Module B we only trigger Module B's compile and test, which will then in turn trigger any downstream modules that depend on it. To give more practical results for reference, consider you have 26 modules dependent on one another, Modules A-Z. Further, suppose each module has an associated test phase that requires 5 minutes to complete. If someone commits a change to Module Z and all modules in the pipeline get rebuilt and tested, even if the build/rebuild process for each is instant - which typically they aren't - it will still require 2h+ to run through the pipeline. However, if we can only rebuild and retest Module Z we can complete the process in 5 minutes (plus the time to recompile of course) which provides significantly faster feedback to developers. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs
Kevin Phillips edited a comment on JENKINS-19728 Much needed dependency management between jobs That is more-or-less how I envisioned the tool working actually. Just to be clear, the rationale for that particular requirement is caused by the size of our codebase and the sheer time required to build and test all interdependent modules. For example, we have 20+ interdependent modules in our codebase, each of which requiring its own separate compile and test phase. In many cases the test phases take much longer to complete than the compilation phase so we tend to try avoiding execution of unit tests when they are not necessary. We do this currently by only running tests when a compile is performed, and compiles are only performed when there are commits to a module or one of its dependencies. So, if Module B depends on Module A and someone commits a change to Module A we want to build and test Module A then Module B. However, if a change is made only to Module B we don't want to re-build or re-test Module A. We manage this at the moment using commit triggers in Jenkins. When changes are made to Module B we only trigger Module B's compile and test, which will then in turn trigger any downstream modules that depend on it. To give more practical results for reference, consider you have 26 modules dependent on one another, Modules A-Z. Further, suppose each module has an associated test phase that requires 5 minutes to complete. If someone commits a change to Module Z and all modules in the pipeline get rebuilt and tested, even if the build/rebuild process for each is instant - which typically they aren't - it will still require 2h+ to run through the pipeline. However, if we can only rebuild and retest Module Z we can complete the process in 5 minutes (plus the time to recompile of course) which provides significantly faster feedback to developers. Granted our particular needs are somewhat exacerbated by the sheer size of our codebase, I would be surprised if even smaller shops wouldn't see an obvious benefit to this. Even if you only have 2 or 3 interdependent modules that exhibit the same behavior you would see noticeable improvements in turnaround time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13978) Add posibility to copy view
Ulli Hafner commented on JENKINS-13978 Add posibility to copy view Wouldn't it be more comfortable if this would be exposed as an action on the view itself? I.e., have a context menu "Copy" for each view. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cygpath-plugin] (JENKINS-7303) Could not find cygpath on Win64 machine
Jan Krag commented on JENKINS-7303 Could not find cygpath on Win64 machine It seems, from the above, and reading the provided links, that the current implementation of directly looking up in the SOFTWARE\Wow6432Node\ is not actually a recommended way of doing it, as \Wow6432Node is an implementation detail, and may break compatibility in the future (or past?). Also, in our investigation, we have found that the whole Wow64 registry translation seems extremely fragile, and gives rise to al sorts of confusion, and the mapping is not even the same on different versions of windows. We are currently investigating a situation where two machines seem to behave differently. Both are running 64 bit java (as reported by java -version in Execute shell), and both have only a 64bit Cygwin installed, and referenced in Software\Cygwin\setuprootdir. One of them finds cygpath just fine, the other doesn't, and the main difference between these machines is that one is running Win 7, the other Win Server 2012. On both machines we have tried running reg query HKLM\Software\Cygwin\setup /v rootdir /reg:32 ERROR: The system was unable to find reg query HKLM\Software\Cygwin\setup /v rootdir /reg:64 rootdir REG_SZ c:\cygwin64 If we run reg query HKLM\Software\Cygwin\setup /v rootdir without the view specifier, we get the positive answer, but if we run it in a 32bit command prompt, we get the error. Our temporary conclusion is that the current code seems to work on a 2012 Server, but not on a Win 7 box. I am not an experienced plugin dev, so I might be missing the obvious, but couldn't the plugin start with: checking for a CYGWIN_HOME environment variable before it starts messing around in the registry? just trying the path, as it might actually be set up just fine? This Env var might not be set by default by the cygwin installation, but it is easy to set and control, either directly on the slave machine or through Jenkins and would also make it much easier to force the use of a specific installed cygwin. (e.g. if you have both cygwin and cygwin64 on the slave). Any comments? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-24463) PyLint parse missing errors
Ulli Hafner commented on JENKINS-24463 PyLint parse missing errors Thanks for the detailed feedback. Currently there is no possibility to pre-validate an input file. I think this could be added as optional step for each parser and if the validation fails then a corresponding warning could be shown. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Tim Bradt commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 Glad to hear externals work since we have 3 of them. @Jason/Shannon - For reasons I won't go into, we also have a large repository which takes 30-40 minutes for a full checkout (we then build pieces of it using custom workspaces), so deleting and checking out for every build would definitely be undesirable. "Emulate clean checkout.." works great for us. If we have to delete the working copy in order to do the upgrade via new checkout, that's fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-25278) Plugin hangs up parsing Maven warnings
SCM/JIRA link daemon commented on JENKINS-25278 Plugin hangs up parsing Maven warnings Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/MavenConsoleParser.java src/main/java/hudson/plugins/warnings/parser/Warning.java http://jenkins-ci.org/commit/warnings-plugin/d76a266d351fc98fed5ef7f62e2d72b1f88689f5 Log: Merge pull request #47 from alecharp/hotfix/maven-log-creates-oom-error JENKINS-25278 Improve performance of maven parser. Compare: https://github.com/jenkinsci/warnings-plugin/compare/9cd57758c307...d76a266d351f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Oliver Gondža commented on JENKINS-25424 Exception when editing nodes Caused by my fix for JENKINS-24773. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-24280) Environment variables get corrupted when using Node parameter
Jeff G commented on JENKINS-24280 Environment variables get corrupted when using Node parameter It works when I pin it to a single node via the "Restrict where this project can be run" job configuration. It still does not work when using the Node Parameter Plugin for a single node either. Unfortunately, we do not have the resources available to set up a new Jenkins instance to test this. Based on the other comments, this is easy to reproduce for anyone who wants to attempt to fix it. Added information. This is only a problem for my two Windows slave nodes. I have the same configuration for several Linux nodes and it is able to find the 'sh' command without issue. This matches the first comment of this defect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25564) Links from build description open in same page
Alexander Obuhovich created JENKINS-25564 Links from build description open in same page Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Nov/14 1:23 PM Description: I'm setting following (from Web UI) as build description: a href="" target="_blank"http://www.google.com/a and when link is clicked it's opened in same browser tab and now new one. I guess "target" attribute is ignored somehow. Project: Jenkins Priority: Minor Reporter: Alexander Obuhovich This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-25523) Multiple SCMs Plugin doesn't work with Mercurial plugin 1.51
Sergey Grinev updated JENKINS-25523 Multiple SCMs Plugin doesnt work with Mercurial plugin 1.51 Change By: Sergey Grinev (12/Nov/14 1:23 PM) Summary: MultipleSCMsPlugindoesntworkwithMercurial since plugin 1. 588 51 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-25523) Multiple SCMs Plugin doesn't work with Mercurial plugin 1.51
Sergey Grinev commented on JENKINS-25523 Multiple SCMs Plugin doesnt work with Mercurial plugin 1.51 I can confirm as well that downgrading Mercurial plugin helps with different Jenkins version. I've updated issue summary accordingly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-25565) data.buildDuration always 0
Ferchaud Matthieu
created JENKINS-25565
data.buildDuration always 0
Issue Type:
Bug
Assignee:
Unassigned
Components:
logstash-plugin
Created:
12/Nov/14 1:49 PM
Description:
Hi,
I installed the plugin logstash. Everything works except for the data buildDuration which is always equal to 0.
{
"_index": "logstash-2014.11.12",
"_type": "logs",
"_id": "tmeu84-rToWJ_8N6PuHBzg",
"_score": null,
"_source": {
"data": {
"id": "2014-11-12_13-59-37",
"result": "SUCCESS",
"projectName": "testredmine",
"displayName": "#26",
"fullDisplayName": "testredmine #26",
"url": "job/testredmine/26/",
"buildHost": "Jenkins",
"buildLabel": "",
"buildNum": 26,
"buildDuration": 0,
"timestamp": "2014-11-12T13:59:37+0100",
"rootProjectName": "testredmine",
"rootProjectDisplayName": "#26",
"rootBuildNum": 26,
"buildVariables": {}
},
"message": [
"[EnvInject] - Loading node environment variables.",
"Building on master in workspace /home/jenkins/data/jobs/testredmine/workspace",
"FSSCM.checkout /tmp/testlogstash/ to /home/jenkins/data/jobs/testredmine/workspace",
"FSSCM.check completed in 19 milliseconds",
"Hello, null!",
"[workspace] $ /bin/sh -xe /tmp/hudson7203903808744352734.sh",
"+ sleep 5"
],
"source": "jenkins",
"source_host": "http://jenkins-test/",
"@timestamp": "2014-11-12T13:59:37.000+01:00",
"version": 1,
"@version": "1"
},
"sort": [
1415797177000,
1415797177000
]
}
Environment:
Jenkins 1.541
Logstash plugin 1.0.1
Project:
Jenkins
Labels:
plugin
logstash
Priority:
Minor
Reporter:
Ferchaud Matthieu
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-9992) Execute Groovy script after the launch of the downstream jobs
Kanstantsin Shautsou resolved JENKINS-9992 as Not A Defect Execute Groovy script after the launch of the downstream jobs Groovy post build action works in non blocking mode. If you want control external executions use "System groovy build step" from "groovy plugin" Change By: Kanstantsin Shautsou (12/Nov/14 2:07 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/d/optout.
[JIRA] [git-plugin] (JENKINS-6334) Support for displaying changesets in submodule updates
Patrick White commented on JENKINS-6334 Support for displaying changesets in submodule updates Any movement on this? This is severely limiting our workflow as we use a lot of submodules, and care more about the cumulative changes in them. I have zero experience with developing jenkins, but would be willing to try. Is the patch somewhat valid still? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-alias-setter-plugin] (JENKINS-25566) Don't create multiple aliases with a single build
Patrice Matignon created JENKINS-25566 Dont create multiple aliases with a single build Issue Type: Improvement Assignee: Oliver Gondža Components: build-alias-setter-plugin Created: 12/Nov/14 2:12 PM Description: Exceprt form the online help: "The update actually happens twice during the build; once right after the check out, and once before the build is completed." As a result, when setting the build alias, you cna end up with 2 aliases if the information you use, is not available on the first pass (or change before the second pass). Normally I would think you only want the final version (that is my use case), and would like to see the plugin cleanup the first alias when it differs from the second one. (maybe some other users would prefer to have a checkbox config item to be able to preserve both ?) Project: Jenkins Priority: Major Reporter: Patrice Matignon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth-plugin] (JENKINS-25567) Matrix-based security does not allow read-only on Configure System
Herbert Quartel created JENKINS-25567 Matrix-based security does not allow read-only on Configure System Issue Type: Bug Assignee: Jesse Glick Components: matrix-auth-plugin Created: 12/Nov/14 2:17 PM Description: Hi, I do not exactly know it this is a bug or not. For our jenkins setup we use Matrix-based security using 2 groups (CI_Admins and CI_Users) We want to prevent that CI_Users ALTER Jenkins configuration (So the stuff under Manage Jenkins) , however , they should be able to VIEW the Jenkins configuration, and most notably the Global properties under Configure System. I do not see a way to do this using the security matrix. Overall-- Read is enabled for CI_Users Environment: Jenkins ver. 1.585, Matrix Authorization Strategy Plugin 1.1 Project: Jenkins Labels: configuration jenkins authorisation Priority: Minor Reporter: Herbert Quartel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs
Donald Morton commented on JENKINS-19728 Much needed dependency management between jobs I have this same use case. We have an application with thousands of modules that all depend on one another in various ways. It takes 10 hours to build the whole thing. This makes it hard to respond quickly if something goes wrong. A partial build operator would be great. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
David Ishee commented on JENKINS-17704 Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild We are still using this plugin, just wanted to report the 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/d/optout.
[JIRA] [git-plugin] (JENKINS-25568) Wrong file link for GitLab 4.2
Olaf Mandel created JENKINS-25568 Wrong file link for GitLab 4.2 Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 12/Nov/14 2:44 PM Description: Nick Oliver (PixnBits) reports in a comment on GitHub to the commit 73249eeac564567f86d8e7d70cf85efa5e5f0b5b that the file link for GitLab version 4.2 is wrong. wrong : GitLab URLHash/tree/File path correct: GitLab URLtree/Hash/File path It is unclear if the current format is completely wrong or if some GitLab version really needs this. Project: Jenkins Labels: plugin git Priority: Minor Reporter: Olaf Mandel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-25569) Lockable resource job stuck at default is still in the queue: Waiting for resources [my_resource]
Jonathan Strickland created JENKINS-25569 Lockable resource job stuck at default is still in the queue: Waiting for resources [my_resource] Issue Type: Bug Assignee: Unassigned Components: lockable-resources-plugin Created: 12/Nov/14 2:44 PM Description: We allocated two resources (routers in our environment). When we kick off the job we see the resource is allocated, but the job stays in a "waiting for resource state" indefinitely. I have included debug images of the global resource configuration, job, and job output. Environment: Jenkins ver. 1.589 Lockable Resources plugin 1.5 Project: Jenkins Labels: plugin lockable Priority: Major Reporter: Jonathan Strickland This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25570) Wait-for-condition step
Jesse Glick
created JENKINS-25570
Wait-for-condition step
Issue Type:
New Feature
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
12/Nov/14 2:52 PM
Description:
WatchYourStep (in test sources) is actually similar to something that has been requested: a way to wait until a named file appears in the workspace, or until the content of a file has changed, etc. All these things could be handled by a step like this:
waitForCond {
readFile 'flag'
}
or
waitForCond {
readFile('flag') == 'ready'
}
Roughly similar to retry, it would run its block, and if the block either throws an exception or returns false, it would run it again. Or it might be more intuitive to expect only a boolean return value and force the first example to be written as
waitForCond {
try {
readFile 'flag'
return true
} catch (FileNotFoundException _) {
return false
}
}
(Even if an exception is permitted as a synonym for false, InterruptedException should be thrown up.)
Unlike retry there would not need to be any limit to the number of retries, and there would be an exponentially increasing delay between successive retries: run the first time immediately, then retry after 100ms, then continue to multiply the delay by a factor of 1.3 or something like that (perhaps up to some maximum delay like DurableTaskStep has).
Project:
Jenkins
Priority:
Minor
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/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-25569) Lockable resource job stuck at default is still in the queue: Waiting for resources [my_resource]
Jonathan Strickland updated JENKINS-25569 Lockable resource job stuck at default is still in the queue: Waiting for resources [my_resource] Change By: Jonathan Strickland (12/Nov/14 2:47 PM) Attachment: lock_debug_images.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Levon Saldamli commented on JENKINS-25424 Exception when editing nodes I've committed a fix but I can't get the mvn release plugin to make a release. Does anyone know how to make it work or what steps it does so I can do it manually? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-25570) Wait-for-condition step
Jesse Glick updated JENKINS-25570 Wait-for-condition step Change By: Jesse Glick (12/Nov/14 2:57 PM) Priority: Minor 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/d/optout.
[JIRA] [core] (JENKINS-18781) Configurable channel timeout for slaves
Charles Ritchea commented on JENKINS-18781 Configurable channel timeout for slaves I'm experiencing this as well. It seems to only impact one job of many, and I can't think of anything special about that job except that it's the newest. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25559) Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions
Oleg Nenashev reopened JENKINS-25559 Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions The fix does not resolve the issue New PR: https://github.com/jenkinsci/perforce-plugin/pull/61 Seems MacroSubstitutionHelper should catch recursion calls to prevent the issue Change By: Oleg Nenashev (12/Nov/14 3:09 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25559) Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions
Rob Petti commented on JENKINS-25559 Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions This is a configuration issue, isn't it? If you don't have the nodename, hostname, or hash in the client name for slaves option, then you will get collisions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25559) Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions
Oleg Nenashev
commented on JENKINS-25559
Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions
If PerforceSCM fails to resolve the client name (it happens due to unresolved EXECUTOR_NUMBER), it fall-backs to a default value without a hash.
Currently, I'm working on this issue. The proper way would be to limit the number of nested recursions in buildEnvVars() by 2 instead of 1 (current implementation)
private String getEffectiveClientName(@Nonnull AbstractBuild build, @CheckForNull MapString,String env)
throws ParameterSubstitutionException, InterruptedException {
Node buildNode = build.getBuiltOn();
FilePath workspace = build.getWorkspace();
String effectiveP4Client = this.p4Client;
try Unknown macro: {
effectiveP4Client = getEffectiveClientName(effectiveP4Client, build);
} catch (Exception e) Unknown macro: {
new StreamTaskListener(System.out).getLogger().println(
Could not get effective client name}
effectiveP4Client = MacroStringHelper.substituteParameters(effectiveP4Client, this, build, env);
return effectiveP4Client;
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25559) Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions
Oleg Nenashev
edited a comment on JENKINS-25559
Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions
If PerforceSCM fails to resolve the client name (it happens due to unresolved EXECUTOR_NUMBER), it fall-backs to a default value without a hash.
Currently, I'm working on this issue. The proper way would be to limit the number of nested recursions in buildEnvVars() by 2 instead of 1 (current implementation)
private String getEffectiveClientName(@Nonnull AbstractBuild build, @CheckForNull MapString,String env)
throws ParameterSubstitutionException, InterruptedException {
Node buildNode = build.getBuiltOn();
FilePath workspace = build.getWorkspace();
String effectiveP4Client = this.p4Client;
try {
effectiveP4Client = getEffectiveClientName(effectiveP4Client, build);
} catch (Exception e) {
new StreamTaskListener(System.out).getLogger().println(
"Could not get effective client name: " + e.getMessage());
}
effectiveP4Client = MacroStringHelper.substituteParameters(effectiveP4Client, this, build, env);
return effectiveP4Client;
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Kevin Phillips commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed One thing I felt needed to be expressed here is that the fact that this defect arose in an update to the LTS edition at all worries me. Combined with the fact that this defect has been opened and under active discussion for months now without any 'real' resolution - other than some hacks and workarounds - is even more concerning. According to the Jenkins website LTS editions should "...change(s) less often and only for important bug fixes...". This policy seems to have been completely negated here. Given the severity / impact of this change I would have expected whatever "improvement" was made that caused this problem would have been reserved for the "latest" release, or at the very least reverted from the LTS edition after this problem was discovered. Perhaps someone with more knowledge about the cause of this error could elaborate on why neither of these approaches has been taken here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-25559) Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions
Oleg Nenashev commented on JENKINS-25559 Missing hash in client names with EXECUTOR_NUMBER leads to workspace collisions Rob Petti IMO it would be preferable to completely prohibit runtime variables in client names, but it will break many use-cases. I'll try to find a convenient solution This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25568) Wrong file link for GitLab 4.2
SCM/JIRA link daemon commented on JENKINS-25568 Wrong file link for GitLab 4.2 Code changed in jenkins User: Olaf Mandel Path: src/main/java/hudson/plugins/git/browser/GitLab.java src/test/java/hudson/plugins/git/browser/GitLabTest.java http://jenkins-ci.org/commit/git-plugin/809fec067119947d9ac61dc451b2dc5cf3562603 Log: GitLab: fix file link for version 4.2 This was suggested in a comment to commit 73249eeac564567f86d8e7d70cf85efa5e5f0b5b by Nick Oliver (PixnBits). FIXES JENKINS-25568 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25568) Wrong file link for GitLab 4.2
SCM/JIRA link daemon commented on JENKINS-25568 Wrong file link for GitLab 4.2 Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/browser/GitLab.java src/test/java/hudson/plugins/git/browser/GitLabTest.java http://jenkins-ci.org/commit/git-plugin/d265da5b220210b74ecce8e786d1d0f4f0198463 Log: Merge pull request #270 from olafmandel/JENKINS-25568 FIXED JENKINS-25568 GitLab: fix file link for version 4.2 Compare: https://github.com/jenkinsci/git-plugin/compare/699fdc983256...d265da5b2202 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25568) Wrong file link for GitLab 4.2
SCM/JIRA link daemon resolved JENKINS-25568 as Fixed Wrong file link for GitLab 4.2 Change By: SCM/JIRA link daemon (12/Nov/14 3:52 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/d/optout.
[JIRA] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Paul Allen commented on JENKINS-25341 Improve reconcile by using -m option Finally got it released 1.0.20 - Jenkins now uses a new maven-release-plugin (2.5.1) This might be the last release I make to support Jenkins 1.532.3, looks like I will need to move forward to 1.565.3 or newer. LTS versions: http://jenkins-ci.org/changelog-stable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
mike bayliss commented on JENKINS-17658 Provide a token so that build failure causes can be included in build failure emails The token can be used in the default content box, so I presume that BFA is actually started by email-ext plugin in that case. I've looked at the code but java/groovy isn't my strong point and I can't work out how to start the BFA from the groovy template. If somebody can provide that information there isn't any need for code changes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24006) Customize number of Junit test failures that affect weather
Mark Sinclair commented on JENKINS-24006 Customize number of Junit test failures that affect weather Thanks Jesse, I also put up a question on google groups to see if I'm doing something wrong in my xml generation: https://groups.google.com/d/topic/jenkinsci-users/-StbbZ0s8jI/discussion This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [custom-job-icon-plugin] (JENKINS-25571) HTTP 404 when deleting existing icon
Verny Quartara Gutierrez created JENKINS-25571 HTTP 404 when deleting existing icon Issue Type: Bug Assignee: Unassigned Components: custom-job-icon-plugin Created: 12/Nov/14 4:19 PM Description: When trying to delete an existing icon, by clicking the "Delete" button, nothing happens. Looking at the HTTP requests, I can see a 404 error with the following URL: http://192.168.1.62/descriptor/jenkins.plugins.jobicon.CustomIconProperty/deleteIcon?icon=d6813e9699d6e81bd64b5c528e22c59ccc3eef25 Environment: Jenkins v1588 Project: Jenkins Priority: Major Reporter: Verny Quartara Gutierrez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-25572) Admins can't run 'trigger only' tests
Travis Johnson created JENKINS-25572 Admins cant run trigger only tests Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 12/Nov/14 4:24 PM Description: When set to 'trigger only', Admins cannot run tests. I've found this is because when the user who comments is an admin (as opposed to whitelisted), the 'triggered' variable is not set. Environment: Jenkins: 1.580.1 ghprb-plugin: 1.16-5 OS: Ubuntu 12.04.5 Project: Jenkins Priority: Minor Reporter: Travis Johnson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-25572) Admins can't run 'trigger only' tests
Travis Johnson commented on JENKINS-25572 Admins cant run trigger only tests I have a PR that I believe fixes this, but I've not (yet) written any tests for this. I don't have a java setup atm, but if no one else does I'll eventually make a test for it: https://github.com/jenkinsci/ghprb-plugin/pull/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/d/optout.
[JIRA] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Andre Untiedt commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap I was able make it work using a Freestyle project with Maven 3.2.1. Jenkins 1.581 Maven Integration plugin 2.7.1 PMD plugin 3.39 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-25573) Junit plugin always produces 100% health report
Mark Sinclair created JENKINS-25573 Junit plugin always produces 100% health report Issue Type: Bug Assignee: Unassigned Attachments: its-always-sunny-in-junit-land.png Components: junit-plugin Created: 12/Nov/14 4:33 PM Description: Junit is always reporting 100% health report, regardless of number of failing testcases. I have a job with 1 of 1 test failing and still getting a 100% health report. Hovering over the (sunny) weather icon for the job gives this popup (see attached screenshot): "Test Result: 1 test failing out of a total of 1 test. 100% This statement above indicates there is something wrong with the plugin. I'm not sure why it would report 100% health when all tests are failing. This may be related to adding the health scale amplification factor, but I'm not sure. I have tried different values for the healthScaleFactor, all produce 100% health. https://issues.jenkins-ci.org/browse/JENKINS-24006 This is the XML I am testing with. Note this is a custom XML I'm creating to mimic a real Junit XML. ?xml version="1.0" encoding="UTF-8"? testsuitesname="all_tests" errors="1" tests="1" failures="1" testsuite name="all_tests" errors="1" tests="1" failures="1" testcase classname="myblock" name="mytest " time="30.57" failure message="testfailed" /failure /testcase /testsuite /testsuites It is possible I'm doing something wrong, so I also posted here: https://groups.google.com/forum/#!topic/jenkinsci-users/-StbbZ0s8jI/discussion Environment: version 1.589 Junit version 1.2 Project: Jenkins Priority: Major Reporter: Mark Sinclair This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-25574) whitelisted users existing PR's are not accepted
Travis Johnson created JENKINS-25574 whitelisted users existing PRs are not accepted Issue Type: Bug Assignee: Honza Brázdil Components: ghprb-plugin Created: 12/Nov/14 4:35 PM Description: If you whitelist a user, any PR's already detected by the plugin do not get accepted and start building. This (I've found) is because the PR's author is only checked against the whitelist upon initial detection of the PR, and never after. I have a PR out that (I believe) fixes this, but I've not written a test for it as I don't have a java setup atm. Should no one else do this I'll eventually do it myself: https://github.com/jenkinsci/ghprb-plugin/pull/60 Environment: Jenkins: 1.580.1 ghprb-plugin: 1.16-5 OS: Ubuntu 12.04.5 Project: Jenkins Priority: Minor Reporter: Travis Johnson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-25574) whitelisted users existing PR's are not accepted
Travis Johnson updated JENKINS-25574 whitelisted users existing PRs are not accepted Change By: Travis Johnson (12/Nov/14 4:36 PM) Description: Ifyouwhitelistauser,anyPRsalreadydetectedbytheplugindonotgetacceptedandstartbuilding.This(Ivefound)isbecausethePRsauthorisonlycheckedagainstthewhitelistuponinitialdetectionofthePR,andneverafter. IhaveaPRoutthat(Ibelieve)fixesthis,butIvenotwrittenatestforitasIdonthaveajavasetupatm.ShouldnooneelsedothisIlleventuallydoitmyself:https://github.com/jenkinsci/ghprb-plugin/pull/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/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-25574) whitelisted users existing PR's are not accepted
Travis Johnson commented on JENKINS-25574 whitelisted users existing PRs are not accepted I have a PR out that (I believe) fixes this, but I've not written a test for it as I don't have a java setup atm. Should no one else do this I'll eventually do it myself: https://github.com/jenkinsci/ghprb-plugin/pull/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/d/optout.
[JIRA] [git-plugin] (JENKINS-25568) Wrong file link for GitLab 4.2
SCM/JIRA link daemon commented on JENKINS-25568 Wrong file link for GitLab 4.2 Code changed in jenkins User: Olaf Mandel Path: src/main/java/hudson/plugins/git/browser/GitLab.java src/test/java/hudson/plugins/git/browser/GitLabTest.java http://jenkins-ci.org/commit/git-plugin/01eece1ecc3bf37ea4bce5f397b043d2ddd23154 Log: GitLab: fix file link for version 4.2 This was suggested in a comment to commit 73249eeac564567f86d8e7d70cf85efa5e5f0b5b by Nick Oliver (PixnBits). FIXES JENKINS-25568 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25341) Improve reconcile by using -m option
Morne Joubert commented on JENKINS-25341 Improve reconcile by using -m option excellent , will see if i have time to test tomorrow. I am on LTS 1.565.2, .3 is too buggy so no problem there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [skype-notifier] (JENKINS-25575) AbstractMethodError preventing Jenkins skype notifications
Martin Cassidy created JENKINS-25575 AbstractMethodError preventing Jenkins skype notifications Issue Type: Bug Assignee: jarlebh Components: skype-notifier, skype-plugin Created: 12/Nov/14 5:02 PM Description: The plugin is no longer working, the error log is filled up with the following: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor214.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Oliver Gondža commented on JENKINS-25424 Exception when editing nodes Levon Saldamli probably #1 in https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-25576) Create a new LDAP test that runs with a real LDAP server
Bowen Cheng created JENKINS-25576 Create a new LDAP test that runs with a real LDAP server Issue Type: Improvement Assignee: Bowen Cheng Components: acceptance-test-harness Created: 12/Nov/14 5:07 PM Description: A new LDAP plugin integration test that runs with real LDAP server is added to ATH. There was an existing LdapPluginTest which requires Docker to run. Project: Jenkins Labels: ldap test Priority: Major Reporter: Bowen Cheng This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Kanstantsin Shautsou commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Freestyle project != maven project. Maven project provides deep integration that has such penalties. Freestyle just executes real mvn binary. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-alias-setter-plugin] (JENKINS-25566) Don't create multiple aliases with a single build
Oliver Gondža commented on JENKINS-25566 Dont create multiple aliases with a single build The reason we follow this pattern is that necessary information might be available at the very beginning so we can set the alias even though the build is in progress. Build name/description setter plugins follow the same path, though the information is overwritten by the end of the build. I guess the aliases set at the beginning can be replaced entirely with final ones at the end of the build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16709) Copy *this* job
Ulli Hafner commented on JENKINS-16709 Copy *this* job This would be very useful. (And I don't think this should be part of a plugin, this is a core functionality.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-alias-setter-plugin] (JENKINS-25566) Don't create multiple aliases with a single build
Patrice Matignon commented on JENKINS-25566 Dont create multiple aliases with a single build Yes, I understand the reason for doing it at the beginning and then again at the end - I'm fine with that. I'd simply like to discard/clean-up the first alias if the second pass creates a different link, to keep things tidy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
Michael Merritt edited a comment on JENKINS-17704 Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild We're also experiencing this same issue, but environment ubuntu 14.04. Are people just not using this plug-in? Thanks. (wasn't sure to log a separate bug for ubuntu). Jenkins v1.589 Multi-job 1.15 Update: Reverting to 1.13 resolved the warning for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-25576) Create a new LDAP test that runs with a real LDAP server
Bowen Cheng updated JENKINS-25576 Create a new LDAP test that runs with a real LDAP server Change By: Bowen Cheng (12/Nov/14 6:37 PM) Description: AnewLDAPpluginintegrationtestthatrunswithrealLDAPserveris addedto neededbyusin ATH.There was is anexistingLdapPluginTestwhichrequiresDockertorun. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-25576) Create a new LDAP test that runs with a real LDAP server
Bowen Cheng started work on JENKINS-25576 Create a new LDAP test that runs with a real LDAP server Change By: Bowen Cheng (12/Nov/14 6:46 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation
Astro Ashtar reopened JENKINS-19743 Massive parallel builds sometimes cause errors in LogRotation I get this same issue. Nov 12, 2014 9:07:25 AM hudson.model.Run execute SEVERE: Failed to rotate log java.io.IOException: Run-a-Windows-Job #502803: C:\Program Files (x86)\Jenkins\jobs\Run-a-Windows-Job\builds\2014-11-11_22-58-01 looks to have already been deleted; siblings: .2014-11-11_22-58-01, 2014-11-11_11-09-14, 2014-11-11_11-14-13, 2014-11-11_11-19-54, 2014-11-11_11-19-58, 2014-11-11_11-20-00, 2014-11-11_11-20-01, 2014-11-11_11-20-02, 2014-11-11_11-20-03, 2014-11-11_11-20-04, 2014-11-11_18-08-01, 2014-11-11_18-10-01, 2014-11-11_18-18-01, 2014-11-11_18-20-01, 2014-11-11_18-28-01, 2014-11-11_18-30-01, 2014-11-11_18-38-01, 2014-11-11_18-40-02, 2014-11-11_18-48-01, 2014-11-11_18-58-01, 2014-11-11_19-00-01, 2014-11-11_19-00-02, 2014-11-11_19-08-01, 2014-11-11_19-10-01, 2014-11-11_19-18-01, 2014-11-11_19-20-01, 2014-11-11_19-28-01, 2014-11-11_19-30-01, 2014-11-11_19-38-01, 2014-11-11_19-40-01, 2014-11-11_19-48-01, 2014-11-11_19-58-01, 2014-11-11_20-00-01, 2014-11-11_20-00-02, 2014-11-11_20-08-01, 2014-11-11_20-10-01, 2014-11-11_20-18-01, 2014-11-11_20-20-01, 2014-11-11_20-28-01, 2014-11-11_20-30-01, 2014-11-11_20-38-01, 2014-11-11_20-40-01, 2014-11-11_20-48-01, 2014-11-11_20-58-01, 2014-11-11_21-00-01, 2014-11-11_21-00-03, 2014-11-11_21-08-01, 2014-11-11_21-10-01, 2014-11-11_21-18-01, 2014-11-11_21-20-01, 2014-11-11_21-28-01, 2014-11-11_21-30-01, 2014-11-11_21-38-01, 2014-11-11_21-40-01, 2014-11-11_21-48-01, 2014-11-11_21-58-01, 2014-11-11_22-00-02, 2014-11-11_22-00-03, 2014-11-11_22-08-01, 2014-11-11_22-10-01, 2014-11-11_22-18-01, 2014-11-11_22-20-01, 2014-11-11_22-28-01, 2014-11-11_22-30-01, 2014-11-11_22-38-01, 2014-11-11_22-40-01, 2014-11-11_22-48-01, 2014-11-11_23-00-01, 2014-11-11_23-00-02, 2014-11-11_23-08-01, 2014-11-11_23-10-01, 2014-11-11_23-18-01, 2014-11-11_23-20-01, 2014-11-11_23-28-02, 2014-11-11_23-30-01, 2014-11-11_23-38-02, 2014-11-11_23-40-01, 2014-11-11_23-48-02, 2014-11-11_23-53-02, 2014-11-11_23-58-02, 2014-11-12_00-01-16, 2014-11-12_00-01-23, 2014-11-12_00-08-01, 2014-11-12_00-10-01, 2014-11-12_00-18-01, 2014-11-12_00-20-01, 2014-11-12_00-28-01, 2014-11-12_00-30-01, 2014-11-12_00-38-01, 2014-11-12_00-40-01, 2014-11-12_00-48-01, 2014-11-12_00-58-01, 2014-11-12_01-00-01, 2014-11-12_01-00-02, 2014-11-12_01-08-01, 2014-11-12_01-10-01, 2014-11-12_01-18-01, 2014-11-12_01-20-01, 2014-11-12_01-28-01, 2014-11-12_01-30-01, 2014-11-12_01-38-01, 2014-11-12_01-40-01, 2014-11-12_01-48-01, 2014-11-12_01-58-01, 2014-11-12_02-00-01, 2014-11-12_02-00-02, 2014-11-12_02-08-01, 2014-11-12_02-10-01, 2014-11-12_02-18-01, 2014-11-12_02-20-01, 2014-11-12_02-28-01, 2014-11-12_02-30-01, 2014-11-12_02-38-01, 2014-11-12_02-40-01, 2014-11-12_02-41-27, 2014-11-12_02-41-28, 2014-11-12_02-41-29, 2014-11-12_02-41-30, 2014-11-12_02-41-31, 2014-11-12_02-41-32, 2014-11-12_02-41-33, 2014-11-12_02-41-34, 2014-11-12_02-41-35, 2014-11-12_02-41-36, 2014-11-12_02-41-37, 2014-11-12_02-41-39, 2014-11-12_02-41-40, 2014-11-12_02-41-41, 2014-11-12_02-43-00, 2014-11-12_02-43-06, 2014-11-12_02-43-09, 2014-11-12_02-43-12, 2014-11-12_02-43-18, 2014-11-12_02-43-21, 2014-11-12_02-43-30, 2014-11-12_02-43-31, 2014-11-12_02-43-39, 2014-11-12_02-43-57, 2014-11-12_02-44-09, 2014-11-12_02-44-39, 2014-11-12_02-44-51, 2014-11-12_02-44-54, 2014-11-12_02-44-55, 2014-11-12_02-45-00, 2014-11-12_02-45-03, 2014-11-12_02-45-30, 2014-11-12_02-45-57, 2014-11-12_02-45-58, 2014-11-12_02-46-24, 2014-11-12_02-46-33, 2014-11-12_02-46-42, 2014-11-12_02-46-51, 2014-11-12_02-46-52, 2014-11-12_02-47-00, 2014-11-12_02-47-15, 2014-11-12_02-47-30, 2014-11-12_02-47-31, 2014-11-12_02-47-48, 2014-11-12_02-47-54, 2014-11-12_02-48-01, 2014-11-12_02-48-06, 2014-11-12_02-48-09, 2014-11-12_02-48-21, 2014-11-12_02-48-45, 2014-11-12_02-48-46, 2014-11-12_02-48-48, 2014-11-12_02-49-11, 2014-11-12_02-49-18, 2014-11-12_02-49-39, 2014-11-12_02-50-06, 2014-11-12_02-50-53, 2014-11-12_02-50-57, 2014-11-12_02-51-00, 2014-11-12_02-51-03, 2014-11-12_02-51-16, 2014-11-12_02-51-23, 2014-11-12_02-51-42, 2014-11-12_02-51-48, 2014-11-12_02-52-03, 2014-11-12_02-52-09, 2014-11-12_02-52-15, 2014-11-12_02-52-18, 2014-11-12_02-52-39, 2014-11-12_02-52-42, 2014-11-12_02-52-48, 2014-11-12_02-53-12, 2014-11-12_02-53-39, 2014-11-12_02-53-45, 2014-11-12_02-53-46, 2014-11-12_02-53-54, 2014-11-12_02-53-57, 2014-11-12_02-54-00, 2014-11-12_02-54-15, 2014-11-12_02-54-18, 2014-11-12_02-54-48,
[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation
Astro Ashtar edited a comment on JENKINS-19743 Massive parallel builds sometimes cause errors in LogRotation I get this same issue. Run on Windows Server 2012. Latest Jenkins 1.589 and this has been happening for a while. I always have to restart the jenkins service. I have about 75 windows slaves. Nov 12, 2014 9:07:25 AM hudson.model.Run execute SEVERE: Failed to rotate log java.io.IOException: Run-a-Windows-Job #502803: C:\Program Files (x86)\Jenkins\jobs\Run-a-Windows-Job\builds\2014-11-11_22-58-01 looks to have already been deleted; siblings: .2014-11-11_22-58-01, 2014-11-11_11-09-14, 2014-11-11_11-14-13, 2014-11-11_11-19-54, 2014-11-11_11-19-58, 2014-11-11_11-20-00, 2014-11-11_11-20-01, 2014-11-11_11-20-02, 2014-11-11_11-20-03, 2014-11-11_11-20-04, 2014-11-11_18-08-01, 2014-11-11_18-10-01, 2014-11-11_18-18-01, 2014-11-11_18-20-01, 2014-11-11_18-28-01, 2014-11-11_18-30-01, 2014-11-11_18-38-01, 2014-11-11_18-40-02, 2014-11-11_18-48-01, 2014-11-11_18-58-01, 2014-11-11_19-00-01, 2014-11-11_19-00-02, 2014-11-11_19-08-01, 2014-11-11_19-10-01, 2014-11-11_19-18-01, 2014-11-11_19-20-01, 2014-11-11_19-28-01, 2014-11-11_19-30-01, 2014-11-11_19-38-01, 2014-11-11_19-40-01, 2014-11-11_19-48-01, 2014-11-11_19-58-01, 2014-11-11_20-00-01, 2014-11-11_20-00-02, 2014-11-11_20-08-01, 2014-11-11_20-10-01, 2014-11-11_20-18-01, 2014-11-11_20-20-01, 2014-11-11_20-28-01, 2014-11-11_20-30-01, 2014-11-11_20-38-01, 2014-11-11_20-40-01, 2014-11-11_20-48-01, 2014-11-11_20-58-01, 2014-11-11_21-00-01, 2014-11-11_21-00-03, 2014-11-11_21-08-01, 2014-11-11_21-10-01, 2014-11-11_21-18-01, 2014-11-11_21-20-01, 2014-11-11_21-28-01, 2014-11-11_21-30-01, 2014-11-11_21-38-01, 2014-11-11_21-40-01, 2014-11-11_21-48-01, 2014-11-11_21-58-01, 2014-11-11_22-00-02, 2014-11-11_22-00-03, 2014-11-11_22-08-01, 2014-11-11_22-10-01, 2014-11-11_22-18-01, 2014-11-11_22-20-01, 2014-11-11_22-28-01, 2014-11-11_22-30-01, 2014-11-11_22-38-01, 2014-11-11_22-40-01, 2014-11-11_22-48-01, 2014-11-11_23-00-01, 2014-11-11_23-00-02, 2014-11-11_23-08-01, 2014-11-11_23-10-01, 2014-11-11_23-18-01, 2014-11-11_23-20-01, 2014-11-11_23-28-02, 2014-11-11_23-30-01, 2014-11-11_23-38-02, 2014-11-11_23-40-01, 2014-11-11_23-48-02, 2014-11-11_23-53-02, 2014-11-11_23-58-02, 2014-11-12_00-01-16, 2014-11-12_00-01-23, 2014-11-12_00-08-01, 2014-11-12_00-10-01, 2014-11-12_00-18-01, 2014-11-12_00-20-01, 2014-11-12_00-28-01, 2014-11-12_00-30-01, 2014-11-12_00-38-01, 2014-11-12_00-40-01, 2014-11-12_00-48-01, 2014-11-12_00-58-01, 2014-11-12_01-00-01, 2014-11-12_01-00-02, 2014-11-12_01-08-01, 2014-11-12_01-10-01, 2014-11-12_01-18-01, 2014-11-12_01-20-01, 2014-11-12_01-28-01, 2014-11-12_01-30-01, 2014-11-12_01-38-01, 2014-11-12_01-40-01, 2014-11-12_01-48-01, 2014-11-12_01-58-01, 2014-11-12_02-00-01, 2014-11-12_02-00-02, 2014-11-12_02-08-01, 2014-11-12_02-10-01, 2014-11-12_02-18-01, 2014-11-12_02-20-01, 2014-11-12_02-28-01, 2014-11-12_02-30-01, 2014-11-12_02-38-01, 2014-11-12_02-40-01, 2014-11-12_02-41-27, 2014-11-12_02-41-28, 2014-11-12_02-41-29, 2014-11-12_02-41-30, 2014-11-12_02-41-31, 2014-11-12_02-41-32, 2014-11-12_02-41-33, 2014-11-12_02-41-34, 2014-11-12_02-41-35, 2014-11-12_02-41-36, 2014-11-12_02-41-37, 2014-11-12_02-41-39, 2014-11-12_02-41-40, 2014-11-12_02-41-41, 2014-11-12_02-43-00, 2014-11-12_02-43-06, 2014-11-12_02-43-09, 2014-11-12_02-43-12, 2014-11-12_02-43-18, 2014-11-12_02-43-21, 2014-11-12_02-43-30, 2014-11-12_02-43-31, 2014-11-12_02-43-39, 2014-11-12_02-43-57, 2014-11-12_02-44-09, 2014-11-12_02-44-39, 2014-11-12_02-44-51, 2014-11-12_02-44-54, 2014-11-12_02-44-55, 2014-11-12_02-45-00, 2014-11-12_02-45-03, 2014-11-12_02-45-30, 2014-11-12_02-45-57, 2014-11-12_02-45-58, 2014-11-12_02-46-24, 2014-11-12_02-46-33, 2014-11-12_02-46-42, 2014-11-12_02-46-51, 2014-11-12_02-46-52, 2014-11-12_02-47-00, 2014-11-12_02-47-15, 2014-11-12_02-47-30, 2014-11-12_02-47-31, 2014-11-12_02-47-48, 2014-11-12_02-47-54, 2014-11-12_02-48-01, 2014-11-12_02-48-06, 2014-11-12_02-48-09, 2014-11-12_02-48-21, 2014-11-12_02-48-45, 2014-11-12_02-48-46, 2014-11-12_02-48-48, 2014-11-12_02-49-11, 2014-11-12_02-49-18, 2014-11-12_02-49-39, 2014-11-12_02-50-06, 2014-11-12_02-50-53, 2014-11-12_02-50-57, 2014-11-12_02-51-00, 2014-11-12_02-51-03, 2014-11-12_02-51-16, 2014-11-12_02-51-23, 2014-11-12_02-51-42, 2014-11-12_02-51-48, 2014-11-12_02-52-03, 2014-11-12_02-52-09, 2014-11-12_02-52-15, 2014-11-12_02-52-18, 2014-11-12_02-52-39, 2014-11-12_02-52-42, 2014-11-12_02-52-48, 2014-11-12_02-53-12, 2014-11-12_02-53-39,
[JIRA] [git-plugin] (JENKINS-25568) Wrong file link for GitLab 4.2
Mark Waite closed JENKINS-25568 as Fixed Wrong file link for GitLab 4.2 Implemented in git plugin 2.3.1 and later and in git plugin 2.2.8 and later. Change By: Mark Waite (12/Nov/14 7:00 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-22400) Git timeout on other actions than fetch/clone
Mark Waite commented on JENKINS-22400 Git timeout on other actions than fetch/clone Timeout on submodule update is implemented in git plugin 2.3 and in git plugin 2.2.8. Timeout on clean is not yet implemented. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-20531) Retry count not working in Git plugin 2.0
Mark Waite commented on JENKINS-20531 Retry count not working in Git plugin 2.0 Fix also included in git plugin 2.2.8 released 12 Nov 2014 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25313) Deleting repository or branch from Git settings also prevents future addition
Mark Waite commented on JENKINS-25313 Deleting repository or branch from Git settings also prevents future addition Fix also included in git plugin 2.2.8 released 12 Nov 2014 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25191) Git plugin does not correctly record built revision on failed merge
Mark Waite commented on JENKINS-25191 Git plugin does not correctly record built revision on failed merge Fix also included in git plugin 2.2.8 released 12 Nov 2014 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25414) Allow remote polling if multiple repositories but single branch defined
Mark Waite commented on JENKINS-25414 Allow remote polling if multiple repositories but single branch defined Fix included in git plugin 2.2.8 released 12 Nov 2014 and in git plugin 2.3 released 10 Nov 2014 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-25577) FileNotFoundException ~/.github
daya daya
created JENKINS-25577
FileNotFoundException ~/.github
Issue Type:
Bug
Assignee:
Honza Brázdil
Attachments:
System Information [Jenkins].pdf
Components:
ghprb-plugin
Created:
12/Nov/14 8:47 PM
Description:
with "Git validated merge support" enabled
with Build Triggers "Build when a change is pushed to GitHub" and "GitHub Pull Request Builder" enabled with Admin list specified
with build trigger of pull request from non-admin user, following is the build output
GitHub pull request #3 to daya/testing-jenkins
Building in workspace /Users/dayas/.jenkins/jobs/testing-jenkins/workspace
/usr/local/bin/git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
/usr/local/bin/git config remote.origin.url https://github.com/daya/testing-jenkins/ # timeout=10
Fetching upstream changes from https://github.com/daya/testing-jenkins/
/usr/local/bin/git --version # timeout=10
using .gitcredentials to set credentials
WARNING Installed git version too old for credentials support
/usr/local/bin/git config --local credential.helper store --file=/Users/Shared/Jenkins/tmp/git8378518816609888499.credentials # timeout=10
/usr/local/bin/git fetch --tags --progress https://github.com/daya/testing-jenkins/ +refs/heads/master:refs/remotes/origin/master
/usr/local/bin/git config --local --remove-section credential # timeout=10
/usr/local/bin/git config core.sparsecheckout # timeout=10
/usr/local/bin/git checkout -f origin/master # timeout=10
/usr/local/bin/git branch -a # timeout=10
/usr/local/bin/git rev-parse master^{commit} # timeout=10
/usr/local/bin/git rev-parse remotes/origin/master^{commit} # timeout=10
/usr/local/bin/git branch -D master # timeout=10
/usr/local/bin/git checkout -b master origin/master
Opening connection
Done: 0
Counting objects
Done: 3
Finding sources
Done: 3
Getting sizes
Done: 2
Compressing objects
Done: 287
Writing objects
Done: 3
remote: Updating references
Merging refs/tags/changes/10
/usr/local/bin/git rev-parse refs/tags/changes/10^{commit} # timeout=10
/usr/local/bin/git merge 59090368c94a33dc7e8544e4b3161aabc3ef8643 # timeout=10
/usr/local/bin/git rev-parse master^{commit} # timeout=10
Checking out Revision 59090368c94a33dc7e8544e4b3161aabc3ef8643 (master)
/usr/local/bin/git config core.sparsecheckout # timeout=10
/usr/local/bin/git checkout -f 59090368c94a33dc7e8544e4b3161aabc3ef8643
/usr/local/bin/git rev-parse origin/master^{commit} # timeout=10
/usr/local/bin/git rev-list 7be695dac6701671360e2764ff784ec5f65f8ec7 # timeout=10
workspace $ /bin/sh -xe /Users/Shared/Jenkins/tmp/hudson407296555273413991.sh
+ BRANCH=
+ ./sleep.sh
sleeping for 15 seconds
woke up after 15 seconds
Putting comment on the pull request
ERROR: Failed to update the ticket
java.io.FileNotFoundException: /Users/dayas/.github (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.init(FileInputStream.java:146)
at java.io.FileInputStream.init(FileInputStream.java:101)
at org.kohsuke.github.GitHubBuilder.fromPropertyFile(GitHubBuilder.java:32)
at org.kohsuke.github.GitHubBuilder.fromPropertyFile(GitHubBuilder.java:26)
at org.kohsuke.github.GitHub.connect(GitHub.java:134)
at com.cloudbees.jenkins.plugins.github_pull.TicketUpdater.onCompleted(TicketUpdater.java:54)
at com.cloudbees.jenkins.plugins.github_pull.TicketUpdater.onCompleted(TicketUpdater.java:23)
at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199)
at hudson.model.Run.execute(Run.java:1796)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
Finished: SUCCESS
Environment:
See attachment System Information [Jenkins].pdf
Ghprb version 1.16-5
[JIRA] [xvnc-plugin] (JENKINS-25424) Exception when editing nodes
Levon Saldamli commented on JENKINS-25424 Exception when editing nodes Thanks, that seemed to work, but the upload was done to http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/xvnc/1.20/ and this version doesn't show up among the updates or at http://updates.jenkins-ci.org/download/plugins/xvnc/ which still has 1.18 (the old version). Am I missing something? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25578) Internet Explorer Compatibility
Aaron Kalsnes created JENKINS-25578 Internet Explorer Compatibility Issue Type: Improvement Assignee: Unassigned Attachments: build-pipeline-plugin.png Components: build-pipeline-plugin Created: 12/Nov/14 9:05 PM Description: The webpage is not rendering as it should. The main issue is that there are no borders around each of the boxes. Please see attachment. Environment: Internet Explorer 11, build-pipeline-plugin 1.4.4, Jenkins 1.582 Project: Jenkins Priority: Minor Reporter: Aaron Kalsnes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
