[JIRA] [plugin] (JENKINS-22158) Wrong parsing of revision for externals causes infinite builds
Yoichi Nakayama commented on JENKINS-22158 Wrong parsing of revision for externals causes infinite builds Could you show as the property value of svn:externals? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [plugin] (JENKINS-22158) Wrong parsing of revision for externals causes infinite builds
Yoichi Nakayama edited a comment on JENKINS-22158 Wrong parsing of revision for externals causes infinite builds Could you show us the property value of svn:externals? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [plugin] (JENKINS-22158) Wrong parsing of revision for externals causes infinite builds
Yoichi Nakayama resolved JENKINS-22158 as Duplicate Wrong parsing of revision for externals causes infinite builds This issue will be handled in JENKINS-22199 Change By: Yoichi Nakayama (21/Mar/14 2:57 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21683) StringIndexOutOfBoundsException on creating change log after externals changes detected by polling
Yoichi Nakayama resolved JENKINS-21683 as Duplicate StringIndexOutOfBoundsException on creating change log after externals changes detected by polling This issue will be handled in JENKINS-22199 Change By: Yoichi Nakayama (21/Mar/14 2:57 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-with-parameters] (JENKINS-19210) The problem with parameterized build and subversion plugin
Yoichi Nakayama edited a comment on JENKINS-19210 The problem with parameterized build and subversion plugin Did you check "Validate repository URLs up to the first variable name" in the global configuration? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-with-parameters] (JENKINS-19210) The problem with parameterized build and subversion plugin
Yoichi Nakayama commented on JENKINS-19210 The problem with parameterized build and subversion plugin Did you checked "Validate repository URLs up to the first variable name" in the global configuration? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542
Yoichi Nakayama commented on JENKINS-20898 SVN post commit hook not working after update to 1.542 Following part seems wrong (should be output of svnlook command): "look changed --revision 12594 /app/subversion/csvn/data/repositories/project" Please check the content of your post-commit hook. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542
Yoichi Nakayama commented on JENKINS-20898 SVN post commit hook not working after update to 1.542 I've tried to reproduce it with Jenkins 1.542 and Subversion-PI 1.54 on Ubuntu, but build is triggered as expected. There may be some missing conditions. How can I reproduce 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/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama commented on JENKINS-19142 Dont add jobs to a view How about the following? In newJob page of ListView, a checkbox to control whether to add new job to the view. In config page of ListView, a checkbox to control default status of checkbox in newJob page. Implemented in: https://github.com/yoichi/jenkins/compare/JENKINS-19142-3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-18029) In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it
Yoichi Nakayama commented on JENKINS-18029 In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it analysis-core uses 10 line offset for the link as: https://github.com/jenkinsci/analysis-core-plugin/blob/c27e8fe79ca4fecc4e485e3fda23982e37b59f4e/src/main/java/hudson/plugins/analysis/util/model/AbstractAnnotation.java#L424 Showing some lines before the target line is useful to read the context, too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-18029) In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it
Yoichi Nakayama edited a comment on JENKINS-18029 In CppCheck plugin selected line with static analysis violation is hidden because breadcrumb covers it For reference, analysis-core uses 10 line offset for the link as: https://github.com/jenkinsci/analysis-core-plugin/blob/c27e8fe79ca4fecc4e485e3fda23982e37b59f4e/src/main/java/hudson/plugins/analysis/util/model/AbstractAnnotation.java#L424 Showing some lines before the target line is useful to read the context, too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20690) Subversion changes using Assembla
Yoichi Nakayama commented on JENKINS-20690 Subversion changes using Assembla When "(Auto)" is selected, it searches for a job which uses same SCM class and SCMDescriptor#isBrowserReuseable() returns true. If the one is found, select same browser. For SubversionSCM case, it searches a job which uses same repository URL (obtained by SvnHelper#getUrlWithoutRevision). Do you have any other project which uses same repository URL and "Repository browser" = "Assembla"? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama commented on JENKINS-19142 Dont add jobs to a view Daniel, I understand that there is no need to add job into View automatically, for your use case. How about introducing a global config disable/enable the behavior? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama edited a comment on JENKINS-19142 Dont add jobs to a view Daniel, I understand that there is no need to add job into View automatically, for your use case. How about introducing a global config to disable/enable the behavior? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-4613) Log message when svn URL is wrong could be better
Yoichi Nakayama closed JENKINS-4613 as Fixed Log message when svn URL is wrong could be better Change By: Yoichi Nakayama (15/Dec/13 1:59 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20165) svn:externals files not polled for changes
Yoichi Nakayama assigned JENKINS-20165 to Ronny Schuetz svn:externals files not polled for changes Change By: Yoichi Nakayama (15/Dec/13 1:58 PM) Assignee: YoichiNakayama RonnySchuetz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20690) Subversion changes using Assembla
Yoichi Nakayama commented on JENKINS-20690 Subversion changes using Assembla Cameron, In the job configuration, what do you select as "Repository browser"? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17768) Repository URL with parameter triggers failure of the field checker
Yoichi Nakayama commented on JENKINS-17768 Repository URL with parameter triggers failure of the field checker Check "Validate repository URLs up to the first variable name" in global configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17768) Repository URL with parameter triggers failure of the field checker
Yoichi Nakayama edited a comment on JENKINS-17768 Repository URL with parameter triggers failure of the field checker Check "Validate repository URLs up to the first variable name" in the Subversion section of the global configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-14865) svn version mismatch
Yoichi Nakayama commented on JENKINS-14865 svn version mismatch How can I make jenkins check out as 1.7 does? Select 1.7 at "Subversion Workspace Version" in the Subversion section of the global configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-12477) Misleading help text for subversion option in global configuration
Yoichi Nakayama resolved JENKINS-12477 as Fixed Misleading help text for subversion option in global configuration I found this issue is fixed by https://github.com/jenkinsci/subversion-plugin/commit/444a31ace35f5c9978f838b88cb865440e413046 Change By: Yoichi Nakayama (14/Dec/13 1:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clang-scanbuild] (JENKINS-10875) Clang Scan-build chart links are broken
Yoichi Nakayama updated JENKINS-10875 Clang Scan-build chart links are broken Change By: Yoichi Nakayama (14/Dec/13 1:42 PM) Component/s: clang-scanbuild This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clang-scanbuild] (JENKINS-10875) Clang Scan-build chart links are broken
Yoichi Nakayama commented on JENKINS-10875 Clang Scan-build chart links are broken In ClangBuildGraph.java, "/" is hard-coded in ClangBuildGraph#generateURL This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-9357) subversion plugin failed project
Yoichi Nakayama updated JENKINS-9357 subversion plugin failed project Change By: Yoichi Nakayama (14/Dec/13 1:53 PM) Component/s: subversion This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9328) Unclear text in for Tabs with no jobs
Yoichi Nakayama updated JENKINS-9328 Unclear text in for Tabs with no jobs Change By: Yoichi Nakayama (14/Dec/13 1:54 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clang-scanbuild] (JENKINS-10875) Clang Scan-build chart links are broken
Yoichi Nakayama edited a comment on JENKINS-10875 Clang Scan-build chart links are broken In ClangBuildGraph.java, "/" is hard-coded in URLAndTooltipBuilder#generateURL This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-7390) Subversion-Plugin - Ignore svn:external
Yoichi Nakayama commented on JENKINS-7390 Subversion-Plugin - Ignore svn:external Typically developers use certain svn tag releases in their projects - therefore it is not ncessary to poll this tag-releases every minute. Specify revision explicitly in svn:externals, then unnecessary poll will be avoided. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama commented on JENKINS-19142 Dont add jobs to a view Introducing new config independent from job selector was not a good idea. I've reworked to add option to disable job selector: https://github.com/yoichi/jenkins/commit/f00ecb653173b27785d3e9719a4848ad6377b178 If job selector is disabled, new job won't be added to the 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542
Yoichi Nakayama edited a comment on JENKINS-20898 SVN post commit hook not working after update to 1.542 Is the contents of "Subversion Polling Log" of the job updated when hook runs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542
Yoichi Nakayama commented on JENKINS-20898 SVN post commit hook not working after update to 1.542 Does the contents of "Subversion Polling Log" of the job updated? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama commented on JENKINS-19142 Dont add jobs to a view Steffen, Thank you for the clarification. Is it sufficient to introduce a new configuration to view as follows? https://github.com/yoichi/jenkins/commit/d0b7ab6d86b7883271d452caaa435520339956cb This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama commented on JENKINS-19142 Dont add jobs to a view For my clarification: what is "root" in this context? Is it the "Default view" as configured in the Jenkins main configuration? No, it is not "Default View". It indicates /newJob instead of /view/Viewname/newJob. There might be more appropriate name... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama commented on JENKINS-19142 Dont add jobs to a view Why don't you click "New Job" in the context menu via the breadcrumb list? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Yoichi Nakayama updated JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated Facundo, The behavior described in my previous post is same for ListView and AllView, then the remaining problem is not specific to NestedView. Change By: Yoichi Nakayama (11/Dec/13 10:29 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama commented on JENKINS-19142 Dont add jobs to a view First order approximation could be whether there are any jobs selected for manual inclusion. If all of them are deselected, and the contents of the view entirely computed using regexp and/or filters, don't add the job to the list. When a user invoke "New Job" from a view, I think the expected behavior is that new item is included in the view. Now I think the point of the problem is any item will be checked in View configuration page even if it matches regexp. Following patch avoids such double inclusion: https://github.com/yoichi/jenkins/commit/01269b8dec9dc40dfac7e197a40053abb67f52a6 How about that? FWIW a Greasemonkey userscript might also be able to change the 'New Job' URL from /view/Viewname/newJob to /newJob to prevent the job from being added to the view automatically. Same result is achieved by clicking "New Job" in the top-level context menu via the breadcrumb list, as I mentioned above. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama commented on JENKINS-19142 Dont add jobs to a view Same result is achieved by clicking "New Job" in the top-level context menu via the breadcrumb list, as I mentioned above. I noticed it is not true if default view configuration is not AllView. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19142) Don't add jobs to a view
Yoichi Nakayama edited a comment on JENKINS-19142 Dont add jobs to a view Same result is achieved by clicking "New Job" in the top-level context menu via the breadcrumb list, as I mentioned above. I noticed it is not true if default view configuration is not AllView. One extra step is needed in that case: select AllView before adding a job This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-20616) nested view does not appear at the end of breadcrumb list
Yoichi Nakayama resolved JENKINS-20616 as Fixed nested view does not appear at the end of breadcrumb list Change By: Yoichi Nakayama (23/Nov/13 8:46 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/groups/opt_out.
[JIRA] [nested-view] (JENKINS-20616) nested view does not appear at the end of breadcrumb list
Yoichi Nakayama closed JENKINS-20616 as Fixed nested view does not appear at the end of breadcrumb list Change By: Yoichi Nakayama (23/Nov/13 8:47 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-19698) cannot configure nested view with default subview
Yoichi Nakayama closed JENKINS-19698 as Fixed cannot configure nested view with default subview Now we can open configure page via breadcrumb list Change By: Yoichi Nakayama (23/Nov/13 9:02 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8431) 'Filter build executors' not working for multi-configuration jobs
Yoichi Nakayama resolved JENKINS-8431 as Fixed Filter build executors not working for multi-configuration jobs I think this issue has been fixed by https://github.com/jenkinsci/jenkins/commit/48fc05d2cb345c31684786b77fd70cfeaaa89bda Change By: Yoichi Nakayama (23/Nov/13 7:36 PM) Status: Open Resolved Assignee: CeesBos Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8431) 'Filter build executors' not working for multi-configuration jobs
Yoichi Nakayama edited a comment on JENKINS-8431 Filter build executors not working for multi-configuration jobs I think this issue has been fixed by https://github.com/jenkinsci/jenkins/commit/48fc05d2cb345c31684786b77fd70cfeaaa89bda and https://github.com/jenkinsci/jenkins/commit/b46c7be54a792e7e550a88b43f4346beca9c67b1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17042) Replace Back to Dashboard link with Back to view name
Yoichi Nakayama commented on JENKINS-17042 Replace Back to Dashboard link with Back to view name FYI, CloudBees Folders Plugin does provide "Up" link to upper ViewGroup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18128) Filtering build queue/executors does not work in nested view
Yoichi Nakayama updated JENKINS-18128 Filtering build queue/executors does not work in nested view Change By: Yoichi Nakayama (21/Nov/13 6:17 PM) Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudbees-folder] (JENKINS-18128) Filtering build queue/executors does not work in nested view
Yoichi Nakayama updated JENKINS-18128 Filtering build queue/executors does not work in nested view I've sent a pull request https://github.com/jenkinsci/jenkins/pull/1030 It also fixes similar problem with Folder under ListView Change By: Yoichi Nakayama (21/Nov/13 10:52 PM) Component/s: cloudbees-folder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-20616) nested view does not appear at the end of breadcrumb list
Yoichi Nakayama
commented on JENKINS-20616
nested view does not appear at the end of breadcrumb list
A result of the investigation, the direct cause was found.
It is filtered by
j:if test="${h.isModel(anc.object) and anc.prev.url!=anc.url}"
in breadcrumbBar.jelly, since NestedView$DefaultViewProxy is not a ModelObject.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-20616) nested view does not appear at the end of breadcrumb list
Yoichi Nakayama assigned JENKINS-20616 to Yoichi Nakayama nested view does not appear at the end of breadcrumb list Change By: Yoichi Nakayama (22/Nov/13 1:08 AM) Assignee: YoichiNakayama This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-20616) nested view does not appear at the end of breadcrumb list
Yoichi Nakayama commented on JENKINS-20616 nested view does not appear at the end of breadcrumb list I've sent a pull request https://github.com/jenkinsci/nested-view-plugin/pull/18 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18128) Filtering build queue/executors does not work in nested view
Yoichi Nakayama commented on JENKINS-18128 Filtering build queue/executors does not work in nested view At first, I've tried to solve this by the change of NestedView class: https://github.com/jenkinsci/nested-view-plugin/pull/16 But the approach requires duplicate code and increase maintenance cost of the Nested View plugin. I noticed that it is better to extend the filter logic defined in View class to respect ViewGroup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-20616) nested view does not appear at the end of breadcrumb list
Yoichi Nakayama created JENKINS-20616 nested view does not appear at the end of breadcrumb list Issue Type: Bug Assignee: Unassigned Components: nested-view Created: 16/Nov/13 9:29 PM Description: When one opens a nested view, the nested view itself does not appear at the end of breadcrumb list. Environment: Nested View Plugin 1.13 Project: Jenkins Priority: Minor Reporter: Yoichi Nakayama This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20500) Build queue is not filtered after progress updated
Yoichi Nakayama commented on JENKINS-20500 Build queue is not filtered after progress updated I've sent a pull request https://github.com/jenkinsci/jenkins/pull/1011 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-8238) Improve nestedview management by adding some buttons / links
Yoichi Nakayama edited a comment on JENKINS-8238 Improve nestedview management by adding some buttons / links Add somewhere a button to add a subview when there is at least existing one (like when there is no subview). for example to keep this link already at the end of the nested view. There is a "+” link in the tab (to add view on the same level). Or, you can use "New View" link in the side panel (to add subview under current nested view). Same thing to manage the view when we decide to enable subview. In this case we have to play with UR .. not really user friendly for all peoples. There is a “Edit View” link in the side panel. Do you want alternative methods? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Yoichi Nakayama commented on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated What is the remaining problem? A user assigned to role with Overall.Read Job.Read View.Read can see nested views. Tested on Jenkins 1.538 Role-based Authorization Strategy 2.1.0 Nested View Plugin 1.13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-8238) Improve nestedview management by adding some buttons / links
Yoichi Nakayama commented on JENKINS-8238 Improve nestedview management by adding some buttons / links Add somewhere a button to add a subview when there is at least existing one (like when there is no subview). for example to keep this link already at the end of the nested view. There is a "+” link in the tab. Same thing to manage the view when we decide to enable subview. In this case we have to play with UR .. not really user friendly for all peoples. There is a “Edit View” link in the side panel. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20500) Build queue is not filtered after progress updated
Yoichi Nakayama assigned JENKINS-20500 to Yoichi Nakayama Build queue is not filtered after progress updated Change By: Yoichi Nakayama (13/Nov/13 3:35 PM) Assignee: YoichiNakayama This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20548) View - Filter Build Executors always filters based on the default view
Yoichi Nakayama commented on JENKINS-20548 View - Filter Build Executors always filters based on the default view I think this bug describes the problem more accurately. It's correct. I've found the cause of the problem. I'll send a pull request. Thanks, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-19698) cannot configure nested view with default subview
Yoichi Nakayama assigned JENKINS-19698 to Yoichi Nakayama cannot configure nested view with default subview Change By: Yoichi Nakayama (10/Nov/13 7:39 AM) Assignee: YoichiNakayama This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-18128) Filtering build queue/executors does not work in nested view
Yoichi Nakayama assigned JENKINS-18128 to Yoichi Nakayama Filtering build queue/executors does not work in nested view Change By: Yoichi Nakayama (10/Nov/13 12:58 AM) Assignee: YoichiNakayama This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine
Yoichi Nakayama commented on JENKINS-18312 changelog browsing uses the wrong path to Redmine The pull request has been merged, and commits "maven-release-plugin prepare release redmine-0.14" came, but 0.14 is unavailable. What is happening? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-18254) When code is checked in SVN, how to let jenkins check out code and build a job immediately?
Yoichi Nakayama commented on JENKINS-18254 When code is checked in SVN, how to let jenkins check out code and build a job immediately? why don't you try post-commit hook instruction in https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11799) GCC - better categories - Parser GNU compiler (gcc)
Yoichi Nakayama commented on JENKINS-11799 GCC - better categories - Parser GNU compiler (gcc) johnu, Thank you for correcting the code. I found 4.19 is released, but Changelog is not written in https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11799) GCC - better categories - Parser GNU compiler (gcc)
Yoichi Nakayama reopened JENKINS-11799 GCC - better categories - Parser GNU compiler (gcc) I've implemented classification of warnings produced by gcc 4.6 or later. https://github.com/yoichi/warnings-plugin/commit/04da9970e546183c1c1d3e204c7b8254525de241 Change By: Yoichi Nakayama (12/Jan/13 2:39 PM) Resolution: WontFix 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
