[JIRA] [project-inheritance] (JENKINS-21817) Initialization issues if Rebuild plugin is not installed
Oleg Nenashev created JENKINS-21817 Initialization issues if Rebuild plugin is not installed Issue Type: Bug Assignee: Martin Schröder Components: project-inheritance Created: 15/Feb/14 10:34 AM Description: Seems that classes with Rebuild plugin dependencies are not marked as "optional". Feb 15, 2014 2:27:50 PM hudson.ExtensionFinder$Sezpoz _find WARNING: Failed to load hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor java.lang.InstantiationException: file:/C:/Users/nenashev/Documents/Jenkins/contrib/ownership-plugin/work/plugins/project-inheritance/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:611) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:600) at hudson.ExtensionFinder$GuiceFinder.init(ExtensionFinder.java:259) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at java.lang.Class.newInstance(Class.java:374) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:625) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:600) at hudson.ExtensionFinder._find(ExtensionFinder.java:151) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:318) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:311) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.get(ExtensionList.java:153) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1066) at hudson.maven.PluginImpl.init(PluginImpl.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:888) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.ClassNotFoundException: hudson.plugins.project_inheritance.projects.rebuild.RebuildValidatorSuppressor at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:942) at java.lang.ClassLoader.loadClass(ClassLoader.java:425) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 35 more Environment: jenkins-1.509.2 Project: Jenkins Priority: Major Reporter: Oleg Nenashev
[JIRA] [scm-sync-configuration] (JENKINS-14847) Apply button not taken into account
Jason Tran edited a comment on JENKINS-14847 Apply button not taken into account Update (regarding issue Jenkins 21807): As soon as I enter URL, without clicking 'Apply' or 'Save' button, I would receive this crash/error message (also reported in 21807). javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) 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:96) 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:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) 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 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] [cobertura] (JENKINS-12808) cobertura-maven-plugin: cannot be deactivated + fails with NullPointerException + version 2.5.1 cannot be overwritten
evernat resolved JENKINS-12808 as Incomplete cobertura-maven-plugin: cannot be deactivated + fails with NullPointerException + version 2.5.1 cannot be overwritten No response from the reporter, so resolving as incomplete. Change By: evernat (15/Feb/14 12:11 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-21390) Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Oleg Nenashev updated JENKINS-21390 Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration I see the stack overflow error after clicking on "Build" inside "Build Specific Version". It seems to be an issue inside "Inheritance Plugin". Accessing to project properties from security plugins leads to such recursions, because the plugin calls permission checks. I'll re-assign the issue to Inheritance plugin in order to get Martin's feedback ... at hudson.security.SidACL$1.hasPermission(SidACL.java:141) at hudson.security.SidACL._hasPermission(SidACL.java:69) at hudson.security.SidACL.hasPermission(SidACL.java:51) at hudson.security.ACL.hasPermission(ACL.java:64) at hudson.model.AbstractItem.hasPermission(AbstractItem.java:448) at jenkins.model.Jenkins.getItem(Jenkins.java:2236) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProjectByName(InheritanceProject.java:521) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProjectFromRequest(InheritanceProject.java:1826) at hudson.plugins.project_inheritance.projects.InheritanceProject.getUserDesiredVersionFromRequest(InheritanceProject.java:1930) at hudson.plugins.project_inheritance.projects.InheritanceProject.getUserDesiredVersion(InheritanceProject.java:2015) at hudson.plugins.project_inheritance.projects.InheritanceProject.getUserDesiredVersion(InheritanceProject.java:2008) at hudson.plugins.project_inheritance.projects.inheritance.InheritanceGovernor.retrieveFullyDerivedField(InheritanceGovernor.java:182) at hudson.plugins.project_inheritance.projects.InheritanceProject.getAllProperties(InheritanceProject.java:2818) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProperty(InheritanceProject.java:2953) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProperty(InheritanceProject.java:2945) at com.synopsys.arc.jenkins.plugins.ownership.jobs.JobOwnerHelper.getOwnerProperty(JobOwnerHelper.java:57) at com.synopsys.arc.jenkins.plugins.ownership.security.rolestrategy.AbstractOwnershipRoleMacro.getOwnership(AbstractOwnershipRoleMacro.java:68) at com.synopsys.arc.jenkins.plugins.ownership.security.rolestrategy.AbstractOwnershipRoleMacro.hasPermission(AbstractOwnershipRoleMacro.java:94) at com.synopsys.arc.jenkins.plugins.ownership.security.rolestrategy.OwnerRoleMacro.hasPermission(OwnerRoleMacro.java:56) at com.michelin.cio.hudson.plugins.rolestrategy.RoleMap.hasPermission(RoleMap.java:77) at com.michelin.cio.hudson.plugins.rolestrategy.RoleMap.access$000(RoleMap.java:51) at com.michelin.cio.hudson.plugins.rolestrategy.RoleMap$AclImpl.hasPermission(RoleMap.java:302) at hudson.security.SidACL$1.hasPermission(SidACL.java:141) at hudson.security.SidACL._hasPermission(SidACL.java:69) at hudson.security.SidACL.hasPermission(SidACL.java:51) at hudson.security.ACL.hasPermission(ACL.java:64) at hudson.model.AbstractItem.hasPermission(AbstractItem.java:448) at jenkins.model.Jenkins.getItem(Jenkins.java:2236) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProjectByName(InheritanceProject.java:521) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProjectFromRequest(InheritanceProject.java:1826) at hudson.plugins.project_inheritance.projects.InheritanceProject.getUserDesiredVersionFromRequest(InheritanceProject.java:1930) at hudson.plugins.project_inheritance.projects.InheritanceProject.getUserDesiredVersion(InheritanceProject.java:2015) at hudson.plugins.project_inheritance.projects.InheritanceProject.getUserDesiredVersion(InheritanceProject.java:2008) at hudson.plugins.project_inheritance.projects.inheritance.InheritanceGovernor.retrieveFullyDerivedField(InheritanceGovernor.java:182) at hudson.plugins.project_inheritance.projects.InheritanceProject.getAllProperties(InheritanceProject.java:2818) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProperty(InheritanceProject.java:2953) at hudson.plugins.project_inheritance.projects.InheritanceProject.getProperty(InheritanceProject.java:2945) at com.synopsys.arc.jenkins.plugins.ownership.jobs.JobOwnerHelper.getOwnerProperty(JobOwnerHelper.java:57) at com.synopsys.arc.jenkins.plugins.ownership.security.rolestrategy.AbstractOwnershipRoleMacro.getOwnership(AbstractOwnershipRoleMacro.java:68) at
[JIRA] [ownership] (JENKINS-21390) Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Oleg Nenashev updated JENKINS-21390 Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Change By: Oleg Nenashev (15/Feb/14 12:41 PM) Labels: jobpluginssecuritystacktrace This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ownership] (JENKINS-21390) Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Oleg Nenashev commented on JENKINS-21390 Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration JEKINNS-21021 is a similar issue. I suppose that there is nothing to do inside ownership and role-strategy 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/groups/opt_out.
[JIRA] [core] (JENKINS-21818) Don't show link to .../*fingerprint* when no fingerprints have been recorded in the instance
Daniel Beck created JENKINS-21818 Dont show link to .../*fingerprint* when no fingerprints have been recorded in the instance Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Feb/14 3:57 PM Description: When browsing e.g. a job's workspace, each readable file links to .../fingerprint. This makes no sense when there are no fingerprints in Jenkins recorded at all. Project: Jenkins Priority: Minor Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21818) Don't show link to .../*fingerprint* when no fingerprints have been recorded in the instance
Daniel Beck
updated JENKINS-21818
Dont show link to .../*fingerprint* when no fingerprints have been recorded in the instance
Change By:
Daniel Beck
(15/Feb/14 4:00 PM)
Description:
Whenbrowsinge.g.ajobsworkspace,eachreadablefilelinksto{{.../
\
*fingerprint
\
*}}.ThismakesnosensewhentherearenofingerprintsinJenkinsrecordedatall.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-21818) Don't show link to .../*fingerprint* when no fingerprints have been recorded in the instance
Daniel Beck assigned JENKINS-21818 to Daniel Beck Dont show link to .../*fingerprint* when no fingerprints have been recorded in the instance Change By: Daniel Beck (15/Feb/14 4:01 PM) Assignee: DanielBeck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachment in email-ext plugin
Alex Earl commented on JENKINS-21760 Unable to attach pdf as an attachment in email-ext plugin I am unable to replicate this issue. I added a unit test and with the attachment pattern value of *.pdf, the PDF is attached correctly. Please attach a screenshot of your attachments pattern from the job 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-21819) Add 'tail' functionality for files in the workspace
Daniel Beck created JENKINS-21819 Add tail functionality for files in the workspace Issue Type: New Feature Assignee: Daniel Beck Components: core Created: 15/Feb/14 4:31 PM Description: For programs logging into the workspace, it'd be useful if there was a way to view just the end of a file, similar to the Unix 'tail' tool. Project: Jenkins Priority: Major Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17849) Collapsing multiple jobs in one project
Markus KARG commented on JENKINS-17849 Collapsing multiple jobs in one project Sorry for letting you wait so long. Here is an example what the problem actually is like. We are producing DVD images which are mostly an assembly of hundreds of unrelated Maven projects (some of them are deeply nested multi-module, some of them are simple but unrelated) think of something similar to a Linux Distro DVD, but for business software instead of an OS. Once the DVD image master is released (which should be a single mouse click or REST API call against Jenkins server), we provide support contracts to maintain these in a many-years term stability-only way. The contracts force us to be able to provide bug fixes for all the contained projects even after years, but not any new features. This leads to thousands of projects over time, so manual job management is impossible. Hence, at time of DVD release, there must be a MVN release:perform get issued for all of the contained projects of that DVD, labelled as the version of the DVD, as this will become single SVN branches in lots of SVN repos for maintenance of that contained products. At the same time, all of that projects must be cloned and updated regarding SVN URL and job name in Jenkins, as we certainly want to have CI for that new branches. And certainly, we now want to have a new view created that lists only the projects contained in that release to not being forced to filter manually each time we look at Jenkins. I do not see how this can be done easily and in a stable way using any of the existing plugins. Maybe the CloudBees Free Enterprise Plugin solves this, but if that is the case, it would be good if someone of CloudBees would simply confirm that the above workflow will be solved. I hope that makes clearer why we think that nested projects is a needed core feature: It would provide the core structure and the core API so all tools and plugins would now how to handle the nesting structure, and would be inter-operable instead of reinventing that hierarchic thinking on their own in an incompatible way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [maven] (JENKINS-21054) IllegalArgumentException related to mavenHome on Git polling
Mark Waite updated JENKINS-21054 IllegalArgumentException related to mavenHome on Git polling Change By: Mark Waite (15/Feb/14 5:20 PM) Description: WehaveseveralMavenjobs,andonanewonewesetupinthepastfewdaysweareseeingsomestrangeerrorsintheGitpollinglog.MuchofthetimetheGitpollingworksfine,butseveraltimesperdaywegetthiserror(seeattachedfromGitpollinglog).ThemavenHomepathmentionedintheerrormessageisavalidpathonthemaster,butnotontheslaveswherethisjobisactuallyrunning(theslavehasasignificantlydifferentdirectorystructurethanthemaster).IhavesetthetoollocationforMavenontheslavestothecorrectlocation. ThemessageinthestacktraceisUnabletodeterminemavenversion.TheexceptionisgeneratedthroughacalltoGitSCM,buttherootproblemseemstobeinthemavenversionreadingcodeusedontheslavenode,notintheGitplugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [maven] (JENKINS-21054) IllegalArgumentException related to mavenHome on Git polling
Mark Waite updated JENKINS-21054 IllegalArgumentException related to mavenHome on Git polling Change By: Mark Waite (15/Feb/14 5:21 PM) Component/s: maven Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-19154) Publish test results in real time
SCM/JIRA link daemon commented on JENKINS-19154 Publish test results in real time Code changed in jenkins User: Oliver Gondža Path: test/src/test/java/hudson/tasks/junit/TestResultPublishingTest.java http://jenkins-ci.org/commit/jenkins/9e6a79deb7a859d25104fbcfaccad48a06e0d7f9 Log: JENKINS-19154 Add test This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21254) /login offers link to /opensearch.xml which anonymous users cannot retrieve
SCM/JIRA link daemon commented on JENKINS-21254 /login offers link to /opensearch.xml which anonymous users cannot retrieve Code changed in jenkins User: Jesse Glick Path: core/src/main/resources/lib/layout/layout.jelly test/src/main/java/org/jvnet/hudson/test/JenkinsRule.java test/src/test/java/lib/layout/LayoutTest.java http://jenkins-ci.org/commit/jenkins/39865664cba56b9e01a76eb7ed73c12e318d98f8 Log: FIXED JENKINS-21254 Ensuring that all links offered on the /login page can be read even by anonymous users without Jenkins.READ. (cherry picked from commit 7c91c402a7c491d51f776178898ee473989ab6c9) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21024) Miscellaneous exceptions in config.xml can prevent entire job from loading
SCM/JIRA link daemon commented on JENKINS-21024 Miscellaneous exceptions in config.xml can prevent entire job from loading Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/util/CopyOnWriteList.java core/src/main/java/hudson/util/RobustCollectionConverter.java core/src/main/java/hudson/util/RobustReflectionConverter.java core/src/main/java/hudson/util/xstream/ImmutableListConverter.java test/src/test/groovy/hudson/model/RunMapTest.groovy test/src/test/java/hudson/util/RobustReflectionConverterTest.java test/src/test/resources/hudson/util/RobustReflectionConverterTest/randomExceptionsReported.zip http://jenkins-ci.org/commit/jenkins/15fcf7c78b456321b1c0d306675b0907298ea770 Log: FIXED JENKINS-21024 Catch a full range of XStreamException’s during deserialization, including rethrown exceptions from readResolve. (cherry picked from commit c3508113f0e1659f0e6c1064f31cb2ac1caa2ef3) Conflicts: changelog.html core/src/main/java/hudson/util/RobustReflectionConverter.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19826) Apply button does not work in IE Compat View
SCM/JIRA link daemon
commented on JENKINS-19826
Apply button does not work in IE Compat View
Code changed in jenkins
User: Jesse Glick
Path:
core/src/main/resources/lib/form/apply/apply.js
http://jenkins-ci.org/commit/jenkins/eca76d7700231a83db3db98d43e570670f48fc23
Log:
FIXED JENKINS-19826 element.setAttribute('name', …) does not work in IE in compatibility mode, so use prototype’s Element(…) which does.
(cherry picked from commit dda099c19a7a015d9c2fc655754dbb07b1b39455)
Conflicts:
changelog.html
Compare: https://github.com/jenkinsci/jenkins/compare/14214d9b2785...eca76d770023
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-21183) NPE from xstream.core.JVM.isOpenJDK
SCM/JIRA link daemon commented on JENKINS-21183 NPE from xstream.core.JVM.isOpenJDK Code changed in jenkins User: Jesse Glick Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/620513fff556be570c54a368bf92c404a2bb96c4 Log: FIXED JENKINS-21183 Updated XStream to pick up NPE fix. (cherry picked from commit 8011acf02828a3aaa666af1b1db873af1031a11a) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21819) Add 'tail' functionality for (log) files in the workspace
Daniel Beck updated JENKINS-21819 Add tail functionality for (log) files in the workspace Change By: Daniel Beck (15/Feb/14 5:35 PM) Summary: Addtailfunctionalityfor (log) filesintheworkspace This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21820) Update credentials plugin to 1.9.4
Oliver Gondža created JENKINS-21820 Update credentials plugin to 1.9.4 Issue Type: Bug Assignee: stephenconnolly Components: core, credentials Created: 15/Feb/14 5:37 PM Description: Filling to be backported. https://github.com/jenkinsci/jenkins/pull/1104 Project: Jenkins Priority: Major Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21820) Update credentials plugin to 1.9.4
SCM/JIRA link daemon commented on JENKINS-21820 Update credentials plugin to 1.9.4 Code changed in jenkins User: Oliver Gondža Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/c504368c4c7912c4a293aca0233c8946f2e54d4a Log: Merge pull request #1104 from stephenc/stable FIXED JENKINS-21820 Update credentials plugin Compare: https://github.com/jenkinsci/jenkins/compare/eca76d770023...c504368c4c79 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21820) Update credentials plugin to 1.9.4
SCM/JIRA link daemon resolved JENKINS-21820 as Fixed Update credentials plugin to 1.9.4 Change By: SCM/JIRA link daemon (15/Feb/14 5:38 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] [xunit] (JENKINS-21278) java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102)
SCM/JIRA link daemon commented on JENKINS-21278 java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102) Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitProcessor.java http://jenkins-ci.org/commit/xunit-plugin/5903ca8d8d43928fa60f9543c1491d829b5d69b0 Log: Add Help to fix JENKINS-21278 Compare: https://github.com/jenkinsci/xunit-plugin/compare/667389511e47...5903ca8d8d43 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [junit] (JENKINS-7866) junit report test count graph has wrong colours
Daniel Beck updated JENKINS-7866 junit report test count graph has wrong colours Change By: Daniel Beck (15/Feb/14 6:08 PM) Labels: lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
swolk commented on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Upgraded to 1.3.27 and still see same issue. Build triggers because it detects changes but it doesn't list the changes. I don't see a timeout in global configuration. I set absolute timeout of 150 minutes for each project using Build-Timeout 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
swolk updated JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Change By: swolk (15/Feb/14 7:52 PM) Environment: Jenkins1. 509 532 . 3 2 LTS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
Rob Petti commented on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Please include syncing logs, as that will show the commands run when grabbing changes. Also make sure you are not configured to sync to a label/changeset, and that you do not have changelogs disabled. The perforce timeout option is in the global Jenkins configuration screen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [utplsql] (JENKINS-21752) Test result graph is not always displayed
kusemuckl closed JENKINS-21752 as Fixed Test result graph is not always displayed Fixed in 0.6.1 Change By: kusemuckl (15/Feb/14 8:20 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] [utplsql] (JENKINS-21657) utplsql Plugin 0.5 utassert.isnull is not correctly parsed when comparing with null
kusemuckl closed JENKINS-21657 as Fixed utplsql Plugin 0.5 utassert.isnull is not correctly parsed when comparing with null Fixed in 0.6.1 Change By: kusemuckl (15/Feb/14 8:21 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
swolk commented on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Think I may have figured it out. Even though the View Mask option is false, it is using the value defined in it. I will clear out the value and see if it fixes it. Looks like a bug though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
swolk edited a comment on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Think I may have figured it out. Even though the View Mask option is false, it is using the value defined in it. I will clear out the value and see if it fixes it. Looks like a bug though. I cleared out the value, but now the option stays checked and it will not let me clear it. When I save, it comes back checked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
Rob Petti commented on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Which view mask option? There are several. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
SCM/JIRA link daemon commented on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Code changed in jenkins User: Rob Petti Path: src/main/java/hudson/plugins/perforce/PerforceSCM.java http://jenkins-ci.org/commit/perforce-plugin/4663c3c313b79f79bfb1414a6b7746e9b2c97004 Log: JENKINS-19649 fix issue where view mask and clean can get stuck in an enabled state This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
Rob Petti commented on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 I see that the "use view mask" option gets stuck, but as long as the other 3 are disabled it should still work correctly. I'll fix the aforementioned option getting stuck, but I don't think it explains your issue as long as you have "Use View Mask for Changelog" option turned off. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
swolk updated JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Change By: swolk (15/Feb/14 10:12 PM) Attachment: A.png Attachment: B.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
swolk commented on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Hi Rob, please see the attached screenshots. Screenshot A shows how the Use View MAsk option is not selected, so no matter how it is configured, it should not be used. Screenshot B shows how the View Mask settings are configured when I check the 'Use View Mask' option. The bug is that these View Mask settings are getting applied to the build even though the 'Use View Mask' parent option is disabled or false. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git] (JENKINS-20896) Git 2.0: fast remote polling fails (missing in-URL password)
Mark Waite resolved JENKINS-20896 as Fixed Git 2.0: fast remote polling fails (missing in-URL password) Closing this bug since one user has reported it is resolved with git plugin 2.0.1 and git-client-plugin 2.0.1. Change By: Mark Waite (15/Feb/14 10:13 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] [git] (JENKINS-20896) Git 2.0: fast remote polling fails (missing in-URL password)
Mark Waite closed JENKINS-20896 as Fixed Git 2.0: fast remote polling fails (missing in-URL password) Change By: Mark Waite (15/Feb/14 10:13 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
swolk
commented on JENKINS-19649
changelog.xml is empty after upgrading to 1.3.25
This change seems to have caused the issue:
https://github.com/jenkinsci/perforce-plugin/commit/3de2bc83b884f68027f523375674163137ff2040#diff-a6a8e160fa20240410923ec7114cfacf
-if (useViewMaskForSyncing useViewMask) {
+if (useViewMaskForChangeLog) {
The extra useViewMask condition was removed which I believe is causing 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] [git] (JENKINS-21476) Git Plugin cloning from Windows Git Server
Mark Waite closed JENKINS-21476 as Cannot Reproduce Git Plugin cloning from Windows Git Server Change By: Mark Waite (15/Feb/14 10:52 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] [git] (JENKINS-21476) Git Plugin cloning from Windows Git Server
Mark Waite resolved JENKINS-21476 as Cannot Reproduce Git Plugin cloning from Windows Git Server The message seems to indicate that there is a problem connecting to the repository based on the provided credentials. The stack trace line numbers do not match git-client-plugin 1.6.0, 1.6.1, or 1.6.2. I'm closing this bug report because I have no hope of duplicating the problem when it appears the original submitter may be several revisions out of date. Change By: Mark Waite (15/Feb/14 10:52 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [credentials] (JENKINS-19927) git-client plugin version 1.3.0 depends on ssh-agent which depends on credentials plugin version 1.6 or newer
Mark Waite closed JENKINS-19927 as Not A Defect git-client plugin version 1.3.0 depends on ssh-agent which depends on credentials plugin version 1.6 or newer Change By: Mark Waite (15/Feb/14 10:57 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] [git-client] (JENKINS-21745) [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL
Mark Waite commented on JENKINS-21745 [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL Have you upgraded your credentials plugin to the current version? I just ran a fresh install of Jenkins 1.532.2 on two different machines with the latest versions of all the plugins (git-plugin 2.0.1, git-client-plugin 1.6.2, credentials plugin 1.10). I confirmed that it handles various credential and non-credential scenarios as expected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Mark Waite commented on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary Wouldn't you be better served by upgrading your git version on Ubuntu 10.04 LTS by using the instructions from askubuntu.com ? http://askubuntu.com/questions/333095/install-a-more-recent-version-of-git-on-a-lts This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Mark Waite edited a comment on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary Wouldn't you be better served by upgrading your git version on Ubuntu 10.04 LTS by using the instructions from askubuntu.com ? http://askubuntu.com/questions/333095/install-a-more-recent-version-of-git-on-a-lts I admit that it is using a PPA to upgrade that package, but I suspect that you can upgrade your git version using that technique without disrupting the rest of the operating system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
Rob Petti commented on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Yes, I understand, and that's what I fixed in my last commit. I'm saying you need to disable "Use View Mask for Changelog" in order to get it working for your currently deployed version. I'll take a look at the change you linked, but it was working fine before some later configuration changes were made. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
SCM/JIRA link daemon resolved JENKINS-19649 as Fixed changelog.xml is empty after upgrading to 1.3.25 Change By: SCM/JIRA link daemon (16/Feb/14 12:33 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
SCM/JIRA link daemon commented on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Code changed in jenkins User: Rob Petti Path: src/main/java/hudson/plugins/perforce/PerforceSCM.java src/test/java/hudson/plugins/perforce/PerforceSCMTest.java http://jenkins-ci.org/commit/perforce-plugin/ea1acb177d01e4e311df9df1f8fc069ed0efd1c1 Log: FIXED JENKINS-19649 viewmask config fix fixed condition for using the view mask for changelog fixed issue where view mask for changelog option could be enabled when loading config added test for optional configuration sections This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-19649) changelog.xml is empty after upgrading to 1.3.25
swolk commented on JENKINS-19649 changelog.xml is empty after upgrading to 1.3.25 Rob, you rock! Thank you very much for addressing this. I went ahead on directly edited my jobs' config.xml files and set all ViewMask properties to false and reloaded Jenkins from them just in case. I'm on 1.3.27 now and everything is 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
dev @ doxo.com commented on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary Answering that question is of course purely a matter of opinion. In this case I don't believe so. I avoid using non-standard packages for critical binaries if I can help it. In this case we're talking about supporting a progress bar being written to standard out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-21219) CopyArtifact plugin 1.27+ does not set COPYARTIFACT_BUILD_NUMBER_* variable for a build in a folder
ikedam commented on JENKINS-21219 CopyArtifact plugin 1.27+ does not set COPYARTIFACT_BUILD_NUMBER_* variable for a build in a folder As long as I tested, it seems work. project with artifacts to copy project copied artifacts a set environment variable Notes /folderA/projectSrc /folderA/projectDest COPYARTIFACT_BUILD_NUMBER_PROJECTSRC /folderA/projectSrc /folderB/projectDest COPYARTIFACT_BUILD_NUMBER__FOLDERA_PROJECTSRC ../folderA/projectSrc /projectSrc /folderA/projectDest COPYARTIFACT_BUILD_NUMBER__FOLDERA_PROJECTSRC ../projectSrc /projectSrc /folderA/folderB/projectDest COPYARTIFACT_BUILD_NUMBER__FOLDERA_PROJECTSRC ../../projectSrc /folderA/projectSrc projectDest COPYARTIFACT_BUILD_NUMBER_FOLDERA_PROJECTSRC folderA/projectSrc As I do not use Jenkins Enterprise (and folder-plugin), the only way to test reproduction is writing test codes... See following codes what I tested if you'd like to see Java codes. https://github.com/jenkinsci/copyartifact-plugin/pull/31 I thinks your problem is one of followings: COPYARTIFACT_BUILD_NUMBER_* is set in your environment even with CopyArtifact plugin 1.27, but its exact name differs from that in CopyArtifact plugin = 1.28. In fact, they should differ for folder support introcuded in CopyArtifact 1.28. Your problem happens only combined with folder-plugin (Does not reproduce with MockFolder which is available for testing purpose). Your problem happens only on Jenkins 1.544. Would you dump all the environment variables available after copying artifacts? That can be done with executing export in Execute shell after Copy artifacts from another project. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-21821) Write documents to copying permission
ikedam created JENKINS-21821 Write documents to copying permission Issue Type: Task Assignee: ikedam Components: copyartifact Created: 16/Feb/14 3:58 AM Description: There are cases that copying artifacts fail with permission issue. Write a documents about those topics: Project name with variables Using QueueItemAuthenticator (JENKINS-14999) Using CopyArtifactPermissionProperty (JENKINS-20398) Project: Jenkins Priority: Minor Reporter: ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [copyartifact] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
ikedam closed JENKINS-14999 as Fixed Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter Fixed in Copyartifact 1.29 Change By: ikedam (16/Feb/14 4:01 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] [copyartifact] (JENKINS-20398) Add a feature to configure projects to allow copy artifacts
ikedam closed JENKINS-20398 as Fixed Add a feature to configure projects to allow copy artifacts Released in Copyartifact 1.30. Change By: ikedam (16/Feb/14 4: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] [copyartifact] (JENKINS-21274) CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled
ikedam commented on JENKINS-21274 CopyArtifact plugin version 1.28 does not work if Maven plugin is disabled This should be fixed in Copyartifact 1.30 (will be available in a day). Please try. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [copyartifact] (JENKINS-19693) Build Number field expect positive number, so it is impossible to use named builds here
ikedam closed JENKINS-19693 as Fixed Build Number field expect positive number, so it is impossible to use named builds here Fixed in Copyartifact 1.30. Change By: ikedam (16/Feb/14 4:01 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] [authorize-project] (JENKINS-21117) Plugin does not load AuthorizeProjectStrategy global configurations on Jenkins start
ikedam commented on JENKINS-21117 Plugin does not load AuthorizeProjectStrategy global configurations on Jenkins start I think you mean AuthorizeProjectStrategyDescriptor does not call Descriptor#load() in its construction. As I described in https://github.com/jenkinsci/authorize-project-plugin/pull/1#discussion_r8547320 , I want AuthorizeProjectStrategyDescriptor acts just like Descriptor and not to call Descriptor#load() automatically. Also see comments in Descriptor#init, https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Descriptor.java#L249 . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [svnmerge] (JENKINS-11379) Local module directory not copied from trunk project when creating a feature branch
SCM/JIRA link daemon commented on JENKINS-11379 Local module directory not copied from trunk project when creating a feature branch Code changed in jenkins User: Hugues Chabot Path: src/main/java/jenkins/plugins/svnmerge/IntegratableProjectAction.java http://jenkins-ci.org/commit/svnmerge-plugin/23619da64fac66d2bd2f553dd10c33fb1e3f1f46 Log: Merge pull request #4 from ain322/JENKINS-11379 FIXED JENKINS-11379 add original localDir to new ModuleLocation Compare: https://github.com/jenkinsci/svnmerge-plugin/compare/f2b6945e64a5...23619da64fac This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [svnmerge] (JENKINS-11379) Local module directory not copied from trunk project when creating a feature branch
SCM/JIRA link daemon commented on JENKINS-11379 Local module directory not copied from trunk project when creating a feature branch Code changed in jenkins User: Gergely Toth Path: src/main/java/jenkins/plugins/svnmerge/IntegratableProjectAction.java http://jenkins-ci.org/commit/svnmerge-plugin/39180697dee473ad766c28a16ebc57fb89b7d32d Log: Fix for issue JENKINS-11379 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [svnmerge] (JENKINS-11380) Creating a branch in a subfolder of /branches creates two Jenkins projects
Hugues Chabot resolved JENKINS-11380 as Duplicate Creating a branch in a subfolder of /branches creates two Jenkins projects Change By: Hugues Chabot (16/Feb/14 4:42 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-21238) Ability to run the generated job immediately after generation
SCM/JIRA link daemon commented on JENKINS-21238 Ability to run the generated job immediately after generation Code changed in jenkins User: syl20bnr Path: src/main/java/org/jenkinsci/plugins/jobgenerator/GeneratorRun.java src/main/java/org/jenkinsci/plugins/jobgenerator/JobGenerator.java src/main/resources/org/jenkinsci/plugins/jobgenerator/JobGenerator/configure-entries.jelly src/main/resources/org/jenkinsci/plugins/jobgenerator/JobGenerator/help-autoRunJob.html http://jenkins-ci.org/commit/jobgenerator-plugin/396f195ac9c43744c8a45270208b8423c44b0755 Log: JENKINS-21238 Ability to run the generated job immediately after generation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-21238) Ability to run the generated job immediately after generation
Sylvain Benner edited a comment on JENKINS-21238 Ability to run the generated job immediately after generation Hi François, I added a combo box in the job generator configuration page, it will be available shortly in the 1.21. Tell me if it does the 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] [jobgenerator] (JENKINS-21238) Ability to run the generated job immediately after generation
Sylvain Benner resolved JENKINS-21238 as Fixed Ability to run the generated job immediately after generation Hi François, I added a combo box in the job generator configuration page. Tell me if it does the job. Change By: Sylvain Benner (16/Feb/14 5:00 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] [jobgenerator] (JENKINS-21461) Promotions, configured in generator job don't appear in generated job.
Sylvain Benner assigned JENKINS-21461 to Sylvain Benner Promotions, configured in generator job dont appear in generated job. Change By: Sylvain Benner (16/Feb/14 5:08 AM) Assignee: SylvainBenner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-21461) Promotions, configured in generator job don't appear in generated job.
Sylvain Benner commented on JENKINS-21461 Promotions, configured in generator job dont appear in generated job. Hi Alex, I'll try to look at this issue but you may have to be patient since I don't use this 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] [git] (JENKINS-21553) Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL
Sylvain Benner updated JENKINS-21553 Creating a new job: internal server error when using an HTTPS:// git source URL rather than a GIT:// URL Not related to the jobgenerator plugin, so I remove this component from the issue. Change By: Sylvain Benner (16/Feb/14 5:11 AM) Component/s: jobgenerator This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Mark Waite commented on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary I believe you have misunderstood what you are sacrificing by staying with an outdated version of a critical part of the Jenkins process. Nicolas noted that credentials support is not available in that git version. Substantial work has been put into the git and subversion plugins to support credentials. It may not be relevant to you, but it is relevant to the larger community of Jenkins users. If you are unwilling to update git, then you could evaluate the recently added JGit support. It is not yet full featured, but when a feature is missing it will generally tell you clearly that the feature is missing. If neither of those meet your needs then you will probably need to pin an older version of the git plugin and accept that the new features won't be available to you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [maven] (JENKINS-21555) Internal server error during job creation: HTTPS:// link to Git Lab project page for Merge Builder configuration
Sylvain Benner updated JENKINS-21555 Internal server error during job creation: HTTPS:// link to Git Lab project page for Merge Builder configuration Not related to the jobgenerator plugin, so I remove this component from the issue. I put maven as a replacement component, it may be not related to this though. Change By: Sylvain Benner (16/Feb/14 5:13 AM) Component/s: maven Component/s: jobgenerator This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-21742) Job generator parameters are not resolved correctly for normal build steps
Sylvain Benner commented on JENKINS-21742 Job generator parameters are not resolved correctly for normal build steps Hi Balázs, Thank you for creating the issue, I will look into it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-21742) Job generator parameters are not resolved correctly for normal build steps
Sylvain Benner assigned JENKINS-21742 to Sylvain Benner Job generator parameters are not resolved correctly for normal build steps Change By: Sylvain Benner (16/Feb/14 5:16 AM) Assignee: SylvainBenner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-21741) Add ParameterFactories option to trigger parameterized build on other projects post-build actions
Sylvain Benner assigned JENKINS-21741 to Sylvain Benner Add ParameterFactories option to trigger parameterized build on other projects post-build actions Change By: Sylvain Benner (16/Feb/14 5:17 AM) Assignee: SylvainBenner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git] (JENKINS-21270) Add licenses to jenkins core and plugins
Mark Waite updated JENKINS-21270 Add licenses to jenkins core and plugins Change By: Mark Waite (16/Feb/14 5:17 AM) Component/s: git-client This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jobgenerator] (JENKINS-21741) Add ParameterFactories option to trigger parameterized build on other projects post-build actions
Sylvain Benner commented on JENKINS-21741 Add ParameterFactories option to trigger parameterized build on other projects post-build actions Thank you for the report. I will look into this soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [github-api] (JENKINS-21270) Add licenses to jenkins core and plugins
Mark Waite commented on JENKINS-21270 Add licenses to jenkins core and plugins Removed git-plugin and git-client-plugin after confirming that both those plugins include a license section in their pom.xml. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [github-api] (JENKINS-21270) Add licenses to jenkins core and plugins
Mark Waite updated JENKINS-21270 Add licenses to jenkins core and plugins Change By: Mark Waite (16/Feb/14 5:18 AM) Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Mark Waite closed JENKINS-21137 as Wont Fix git fetch does not have support for --progress option in 1.7.x version of git client binary Change By: Mark Waite (16/Feb/14 5:23 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] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Mark Waite resolved JENKINS-21137 as Wont Fix git fetch does not have support for --progress option in 1.7.x version of git client binary Change By: Mark Waite (16/Feb/14 5:23 AM) Status: Reopened Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-21032) git executable should be determined by node, not by the host
Mark Waite commented on JENKINS-21032 git executable should be determined by node, not by the host As far as I can tell, the default git executable is "git", not git.exe. That works on both Windows and Linux if the PATH setting includes the directory which contains the git executable. I assume your master node is a Windows machine with a Linux slave, and you set the Git location in the Jenkins global configuration to either be git.exe, or to be c:\Program Files\Git\bin\git.exe. If you'll set it to "git" rather than "git.exe" (or leave it unset), I believe it will work in both environments. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [git-client] (JENKINS-19294) Build tagging does not work when using a local subdirectory for the GIT repo
Mark Waite closed JENKINS-19294 as Fixed Build tagging does not work when using a local subdirectory for the GIT repo Change By: Mark Waite (16/Feb/14 5:41 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] [git-client] (JENKINS-19294) Build tagging does not work when using a local subdirectory for the GIT repo
Mark Waite resolved JENKINS-19294 as Fixed Build tagging does not work when using a local subdirectory for the GIT repo Confirmed that I'm able to tag each build using the JGit implementation in git-client-plugin 1.6.2 and git-plugin 2.0.1 Change By: Mark Waite (16/Feb/14 5:41 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] [git-client] (JENKINS-21015) NullPointerException in Jenkins Git Plugin
Mark Waite closed JENKINS-21015 as Fixed NullPointerException in Jenkins Git Plugin Change By: Mark Waite (16/Feb/14 5:44 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] [git-client] (JENKINS-21015) NullPointerException in Jenkins Git Plugin
Mark Waite resolved JENKINS-21015 as Fixed NullPointerException in Jenkins Git Plugin Fixed in git-client-plugin 1.6.2, and possibly was already fixed in 1.6.1 Change By: Mark Waite (16/Feb/14 5:43 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] [git-client] (JENKINS-21369) Git client fails to remove files/directories with git clean -fdx
Mark Waite commented on JENKINS-21369 Git client fails to remove files/directories with git clean -fdx Can you provide more details that would make this a repeatable bug? The stack trace shows you are using the command line git implementation. That implementation has no known problems with leaving files open. If you can provide a repeatable case, it has a much better chance of being investigated. The JGit implementation has known problems with leaving files open (see JENKINS-19994). There is also a risk that some other program is keeping the files open. There were cases in the past where a virus scanner prevented a directory from being deleted because it was keeping one or more files open from the directory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
