[JIRA] [scm-sync-configuration-plugin] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Arun Thomas commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 @Dan Rough: Yes, I am able to rename without errors with the current plugins. I remember having issues when renaming jobs with the older versions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration-plugin] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Arun Thomas commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 SCM Sync plugin is working for me. Jenkins: 1.599 Sub-version plugin: 2.5 SCM Sync Configuration plugin: 0.0.8 Environment: Windows Server 2008 Could this have been resolved? Has anyone else tried the latest plugins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration-plugin] (JENKINS-26963) Form too large when applying changes
Arun Thomas created JENKINS-26963 Form too large when applying changes Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 14/Feb/15 12:08 AM Description: After upgrading Jenkins and all my plugins to the latest versions, I can no longer commit changes to certain jobs due to their size. Stack trace javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 21354920 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] [scm-sync-configuration-plugin] (JENKINS-26963) Form too large when applying changes
Arun Thomas commented on JENKINS-26963 Form too large when applying changes Seems like a duplicate of JENKINS-20327. I was able to workaround this by adding -Dorg.eclipse.jetty.server.Request.maxFormContentSize=50 in the arguments XML node of my jenkins.xml file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [scm-sync-configuration-plugin] (JENKINS-26963) Form too large when applying changes
Arun Thomas updated JENKINS-26963 Form too large when applying changes Reducing Priority since there is a workaround. Change By: Arun Thomas (14/Feb/15 2:15 AM) Priority: Blocker Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [parameterized-trigger] (JENKINS-22600) Sub-projects appeared as Static and Other executed recently at job main page
Arun Thomas assigned JENKINS-22600 to Unassigned Sub-projects appeared as Static and Other executed recently at job main page Change By: Arun Thomas (12/Sep/14 10:33 PM) Assignee: huybrechts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [parameterized-trigger] (JENKINS-22600) Sub-projects appeared as Static and Other executed recently at job main page
Arun Thomas commented on JENKINS-22600 Sub-projects appeared as Static and Other executed recently at job main page The page load time increases unbearably when many downstream projects are triggered. Having multiple downstream projects creates sections of "Static" and "Other Executed Recently" that are unnecessarily duplicated. I tried what Vitaliy suggested of placing jobs in a sub-folder on our server but then the jobs do not show up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22600) Sub-projects appeared as Static and Other executed recently at job main page
Arun Thomas assigned JENKINS-22600 to cjo9900 Sub-projects appeared as Static and Other executed recently at job main page Change By: Arun Thomas (12/Sep/14 10:37 PM) Assignee: cjo9900 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [lastfailureversioncolumn] (JENKINS-23885) Time duration missing for inheritance projects
Arun Thomas commented on JENKINS-23885 Time duration missing for inheritance projects Seems like the bug has been fixed with v1.577 of Jenkins. Perhaps this was not an issue with the plugin at all. I have v1.5.0 of the inheritance plugin installed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [project-inheritance] (JENKINS-23993) Page load time of inheritance projects
Arun Thomas created JENKINS-23993 Page load time of inheritance projects Issue Type: Improvement Assignee: Unassigned Components: project-inheritance Created: 26/Jul/14 2:11 AM Description: The page load time for any inheritance-plugin-based project is much longer than for a traditional Jenkins project. Please improve this in future versions. Environment: Windows 7 64-bit, Mozilla Firefox browser Project: Jenkins Priority: Minor Reporter: Arun Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [project-inheritance] (JENKINS-23887) View Full Build Flow does not correctly order build steps
Arun Thomas updated JENKINS-23887 View Full Build Flow does not correctly order build steps Change By: Arun Thomas (22/Jul/14 8:48 PM) Priority: Minor Trivial This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [lastfailureversioncolumn] (JENKINS-23885) Time duration missing for inheritance projects
Arun Thomas updated JENKINS-23885 Time duration missing for inheritance projects Change By: Arun Thomas (22/Jul/14 8:51 PM) Priority: Trivial Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [lastfailureversioncolumn] (JENKINS-23885) Time duration missing for inheritance projects
Arun Thomas created JENKINS-23885 Time duration missing for inheritance projects Issue Type: Bug Assignee: Unassigned Components: lastfailureversioncolumn, lastsuccessdescriptioncolumn Created: 18/Jul/14 9:20 PM Description: The time duration for Last Success and Last Failure are replaced by "N/A" on all the projects created with the inheritance plugin. Environment: Windows 7 64-bit Project: Jenkins Priority: Trivial Reporter: Arun Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [lastfailureversioncolumn] (JENKINS-23885) Time duration missing for inheritance projects
Arun Thomas updated JENKINS-23885 Time duration missing for inheritance projects Change By: Arun Thomas (18/Jul/14 9:24 PM) Description: ThetimedurationforLastSuccessandLastFailurearereplacedbyN/Aonalltheprojectscreatedwiththeinheritanceplugin inListViewmode . Component/s: project-inheritance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [project-inheritance] (JENKINS-23886) Last successful build artifacts not showing in the main project page.
Arun Thomas created JENKINS-23886 Last successful build artifacts not showing in the main project page. Issue Type: Improvement Assignee: Unassigned Components: project-inheritance Created: 18/Jul/14 9:27 PM Description: For a simple project, after a build runs and artifacts are created, they show up in the main project window. For inheritance projects, they do not. Please add this feature. Project: Jenkins Priority: Minor Reporter: Arun Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [project-inheritance] (JENKINS-23887) View Full Build Flow does not correctly order build steps
Arun Thomas created JENKINS-23887 View Full Build Flow does not correctly order build steps Issue Type: Bug Assignee: Unassigned Components: project-inheritance Created: 18/Jul/14 9:36 PM Description: I have one child project inheriting from two ordered parent projects. The first parent project is responsible for setting up the environment, then the child project runs, and then the second parent project is responsible for moving the artifacts and archiving them. The flow is: 1. Preparation(Parent1) 2. Build(Child) 3. Clean-up/Archive(Parent2) When the build is executed, the steps run correctly in the expected order. The minor issue, however, is in the "View Full Build Flow" list, the projects seem to be out of order. 1. Preparation 2. Clean-up/Archive 3. Build This does not affect the build process which is good. Nonetheless, it is misleading. Environment: Windows 7 64 bit Project: Jenkins Priority: Minor Reporter: Arun Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.