[JIRA] [p4-plugin] (JENKINS-26733) During build root path to is changes to and host to
Alexey Larsky created JENKINS-26733 During build root path to is changes to and host to Issue Type: Bug Assignee: Unassigned Attachments: p4settings.png Components: p4-plugin Created: 02/Feb/15 7:45 AM Description: During build root path to is changes to and host to . On version 1.1.2 was the same behavior. On version 1.1.0 it worked. Environment: version 1.1.3 Project: Jenkins Priority: Critical Reporter: Alexey Larsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26613) StackOverflowError while parsing POMs
Bert Jan Schrijver commented on JENKINS-26613 StackOverflowError while parsing POMs Same here. Upgraded from 1.593 to 1.598; got the same error. Downgrade to 1.597 fixed it. Stacktrace: Fetching upstream changes from <...> Checking out Revision <...> Parsing POMs using global settings config with name globalSettings FATAL: null java.lang.StackOverflowError at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy60.lookup(Unknown Source) at sun.reflect.GeneratedMethodAccessor170.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy60.lookup(Unknown Source) <...> This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [digitalocean-plugin] (JENKINS-26732) Cannot install java on all debian machines thank to missing update
Andreas Pieber created JENKINS-26732 Cannot install java on all debian machines thank to missing update Issue Type: Bug Assignee: Andreas Pieber Components: digitalocean-plugin Created: 02/Feb/15 7:24 AM Description: Some debian Machines on digitalocean actually require an apt-get update before install could be executed. Project: Jenkins Priority: Minor Reporter: Andreas Pieber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [digitalocean-plugin] (JENKINS-26732) Cannot install java on all debian machines thank to missing update
Andreas Pieber resolved JENKINS-26732 as Fixed Cannot install java on all debian machines thank to missing update This had been fixed in https://github.com/jenkinsci/digitalocean-plugin/pull/3 Change By: Andreas Pieber (02/Feb/15 7:25 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core-plugin] (JENKINS-26731) Replace "about.md" by a (parsable) markup format
Nicolas De Loof created JENKINS-26731 Replace "about.md" by a (parsable) markup format Issue Type: Improvement Assignee: Steven Christou Components: support-core-plugin Created: 02/Feb/15 7:21 AM Description: To automate support bundle analysis, we need to parse the about.md file. For sure we can parse markdown, but would be so easier if this one uses yaml or json. Project: Jenkins Priority: Minor Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [digitalocean-plugin] (JENKINS-26352) Cannot create Jenkins slaves
Andreas Pieber commented on JENKINS-26352 Cannot create Jenkins slaves I've fixed this issue in https://github.com/jenkinsci/digitalocean-plugin/pull/4. Independently there are additional problems with the current implementation of the plugin, I'll fix in further pull requests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [digitalocean-plugin] (JENKINS-26352) Cannot create Jenkins slaves
Andreas Pieber assigned JENKINS-26352 to Andreas Pieber Cannot create Jenkins slaves Change By: Andreas Pieber (02/Feb/15 7:21 AM) Assignee: Andreas Pieber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [digitalocean-plugin] (JENKINS-26352) Cannot create Jenkins slaves
Andreas Pieber started work on JENKINS-26352 Cannot create Jenkins slaves Change By: Andreas Pieber (02/Feb/15 7:21 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-26730) Copy publisher results from Multijob subjobs
Arno Moonen created JENKINS-26730 Copy publisher results from Multijob subjobs Issue Type: New Feature Assignee: Unassigned Components: multijob-plugin Created: 02/Feb/15 7:09 AM Description: Within our company we often use the Multijob plugin to set-up different pipelines. Some of the jobs within such a pipeline run unit tests or static code analysis tools, and publish the results. However, in the main job (the actual Multijob) we would also like to include some (or all) of the publisher results. Currently we achieve this results by simply copying all the configuration of the publishers to the Multijob, but this is really hard to maintain. Besides, it seems a waste of resources to regenerate reports each time. Therefor I would like to request a new feature which allows us to copy the publisher results from subjobs to the multijob. All results would be fine, but allowing a subset would be even better. Project: Jenkins Labels: multijob publisher Priority: Minor Reporter: Arno Moonen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26499) javax.servlet.ServletException at Job view
Sir Hellsing commented on JENKINS-26499 javax.servlet.ServletException at Job view Hi, I got the same problem after upgrading from jenkins <1.597 to 1.598. In my case it was the Disk-Usage Plugin. Try updating it. From the release notes: Release 0.25 (January 26, 2015) Plugin doesn't rely on the format of Run.id any more (pull #26) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26015) Layout broken since 1.593
Baskaran D commented on JENKINS-26015 Layout broken since 1.593 @BenjaminDewez Can you please explain the issue on . Is it the missing top-border on Customized-View? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [embeddable-build-status-plugin] (JENKINS-26705) Support flat style badges
SCM/JIRA link daemon commented on JENKINS-26705 Support flat style badges Code changed in jenkins User: Marius Gedminas Path: src/main/java/org/jenkinsci/plugins/badge/BadgeAction.java src/main/java/org/jenkinsci/plugins/badge/BadgeActionFactory.java src/main/java/org/jenkinsci/plugins/badge/ImageResolver.java src/main/java/org/jenkinsci/plugins/badge/PublicBadgeAction.java src/main/java/org/jenkinsci/plugins/badge/RunBadgeAction.java src/main/java/org/jenkinsci/plugins/badge/RunBadgeActionFactory.java src/main/resources/org/jenkinsci/plugins/badge/BadgeAction/index.groovy src/main/resources/org/jenkinsci/plugins/badge/BadgeAction/index.properties src/main/resources/org/jenkinsci/plugins/badge/RunBadgeAction/index.groovy src/main/resources/org/jenkinsci/plugins/badge/RunBadgeAction/index.properties src/main/webapp/status/build-failing-red-flat.svg src/main/webapp/status/build-passing-brightgreen-flat.svg src/main/webapp/status/build-running-blue-flat.svg src/main/webapp/status/build-unknown-lightgrey-flat.svg src/main/webapp/status/build-unstable-yellow-flat.svg src/test/java/org/jenkinsci/plugins/badge/PublicBadgeActionTest.java http://jenkins-ci.org/commit/embeddable-build-status-plugin/f13eccb8551fd3c888f3f44856b539c344d0da62 Log: Add flat-styled images, make them default You can get the old "plastic" style badges by adding ?style=plastic to the badge URL. The new images were generated with wget https://img.shields.io/badge/build-failing-red.svg?style=flat -O build-failing-red-flat.svg wget https://img.shields.io/badge/build-passing-brightgreen.svg?style=flat -O build-passing-brightgreen-flat.svg wget https://img.shields.io/badge/build-running-blue.svg?style=flat-O build-running-blue-flat.svg wget https://img.shields.io/badge/build-unknown-lightgrey.svg?style=flat -O build-unknown-lightgrey-flat.svg wget https://img.shields.io/badge/build-unstable-yellow.svg?style=flat -O build-unstable-yellow-flat.svg Fixes JENKINS-26705. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [versionnumber-plugin] (JENKINS-26729) Endless loop when evaluating environment variables
Jason W
created JENKINS-26729
Endless loop when evaluating environment variables
Issue Type:
Bug
Assignee:
Unassigned
Components:
versionnumber-plugin
Created:
02/Feb/15 6:28 AM
Description:
Recreation
Have 2 jobs:
Job 1 triggers Job 2 using the "Trigger/call builds on other projects"
Uses "Predefined parameter": test_loop=${test_loop}
Job 2 uses "Create a formatted version number" where:
"Environment Variable Name": test_loop
"Version Number Format String": ${test_loop}
Outcome
This causes the Job 2 to be stuck in an endless loop as test_loop keeps getting translated into ${test_loop} and tries to be translated again and again...
threadDump looks as follows:
Executor #0 for master : executing test_endless_loop #5
"Executor #0 for master : executing test_endless_loop #5" Id=116 Group=main RUNNABLE
at org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.formatVersionNumber(VersionNumberBuilder.java:341)
at org.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.setUp(VersionNumberBuilder.java:364)
...
I stumbled on this by accident and this configuration should be avoided, but still it cause a job to be stuck in an endless loop which could not be stopped.
Stopping it was only by restarting the server.
Environment:
Jenkins ver. 1.580.3
Version Number Plug-In 1.4.1
Parameterized Trigger plugin 2.25
Project:
Jenkins
Labels:
stuck
endless_loop
Priority:
Minor
Reporter:
Jason W
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-26728) scm sync plugin won't reload without saving first
thedug created JENKINS-26728 scm sync plugin won't reload without saving first Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 02/Feb/15 4:44 AM Description: If you are rebuilding your jenkins instance and need to recover using git, the scm sync plugin requires that you add the git url and then save settings. Saving the settings commits the current values to git. This means that your server settings will not be loaded, only your jobs. Project: Jenkins Priority: Major Reporter: thedug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-25786) Renaming Job Causes a poisoned commitQueue
thedug commented on JENKINS-25786 Renaming Job Causes a poisoned commitQueue I've run into the same thing. I usually just go into the checkOutConfiguration and try to make it match. Sometimes it seems to get into a state where there are recursive references, I usually delete those extra folders. Commit and Push to git. Then restart jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-26727) SCM Sync not triggering when saving jobs
thedug created JENKINS-26727 SCM Sync not triggering when saving jobs Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 02/Feb/15 4:42 AM Description: The scm scync plugin is only committing when I make changes under manage Jenkins. Project: Jenkins Priority: Major Reporter: thedug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
Arunkumar Perumal commented on JENKINS-22853 SEVERE: Trying to unexport an object that's already unexported Its strange. The builds are running successfully for a couple of days but after that I'm getting this error in Jenkins console. ERROR: Error fetching remote repo 'origin' ERROR: Error fetching remote repo 'origin' When I look for server logs, I see below; Jan 30, 2015 7:05:17 PM hudson.triggers.SCMTrigger$Runner run INFO: SCM changes detected in XDK-Ide. Triggering #163 Jan 30, 2015 7:05:24 PM hudson.remoting.ExportTable unexportByOid SEVERE: Trying to unexport an object that's already unexported java.lang.IllegalStateException: Invalid object ID 102 iota=12324 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:348) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:371) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:38) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: java.lang.Exception: Object appears to be deallocated at lease before Fri Jan 30 16:15:36 CET 2015 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:344) ... 5 more Jan 30, 2015 7:05:24 PM hudson.remoting.ExportTable unexportByOid SEVERE: 2nd unexport attempt is here Command hudson.remoting.UnexportCommand@1fe8ba9 created at at hudson.remoting.Command.(Command.java:67) at hudson.remoting.Command.(Command.java:50) at hudson.remoting.UnexportCommand.(UnexportCommand.java:33) at hudson.remoting.RemoteInvocationHandler.finalize(RemoteInvocationHandler.java:221) at java.lang.System$2.invokeFinalize(Unknown Source) at java.lang.ref.Finalizer.runFinalizer(Unknown Source) at java.lang.ref.Finalizer.access$100(Unknown Source) at java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source) After restarting the slave, there was no errors again. Any help ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26680) Extraneous Forward-Slash in ssh:// path to repository
Mark Waite edited a comment on JENKINS-26680 Extraneous Forward-Slash in ssh:// path to repository I suspect there is something in the plugin which is attempting to rewrite the URL and is adding the extra slash. I think the syntax ssh://user@hostname:relative_path/repo.git is ambiguous, though it seems to be understood by git. I use ssh://user@hostname:port_number/absolute_path/repo.git to allow my Jenkins job ssh access through port_number to a git repository on hostname at /absolute_path/repo.git. On my computer named "wheezy64b", I specify the URL as ssh://mwaite@wheezy64b:45022/var/lib/git/mwaite/jenkins/git-client-plugin.git I can use ssh://user@hostname:ssh/absolute_path/repo.git to allow my Jenkins job ssh access through the ssh port to a git repository on hostnanme at /absolute_path/repo.git. On my computer named "mark-pc1", I specify the URL as ssh://mwaite@mark-pc1:ssh/var/lib/git/mwaite/jenkins/git-client-plugin.git I'm impressed that the git command recognizes the relative path, since it seems like my second syntax (using the word "ssh" for the ssh port number) creates a conflicting case with your relative path case. I agree that this is a bug in the git plugin or the git client plugin, though considering the ambiguity in the ssh URL syntax, I don't think I will ever work on fixing that bug. The fix would need to identify those cases where the plugin rewrites the URL and intentionally decide not to rewrite the URL, at least for this case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)
Dmytro Kryvenko created JENKINS-26726 java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70) Issue Type: Bug Assignee: Dmytro Kryvenko Components: delivery-pipeline-plugin Created: 02/Feb/15 2:24 AM Description: Steps to reproduce: 1. Create jobs A, B and C 2. C should be a downstream job for both A and B 3. A and B doesn't have direct relations 4. Create two Delivery Pipeline instances pA and pB (starting from A and B jobs accordingly) 5. Run job A and wait for finish job C 6. Rebuild job A and wait again 7. Run job B and open pB pipeline in browser - you will see Server Error 8. In the meantime Jenkins log will contains following error: WARNING: Error while serving https://jenkins.myorg.com/view/pB/api/json java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor487.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) 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:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) 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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:99) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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 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(
[JIRA] [git-client-plugin] (JENKINS-23345) Git Plugin should have an option to use clone instead of init/fetch
Mark Waite commented on JENKINS-23345 Git Plugin should have an option to use clone instead of init/fetch In order to satisfy my curiosity about the performance difference between "git clone" and "git fetch", I ran a pair of tests to compare them. I used git 2.2.1 on a Ubuntu 14.04 64 bit machine with a solid state disc as the file system hosting both the source repository and the destination repository. I used a local copy of the linux kernel repository as it exists at commit 69e273c0b0a3c337a521d083374c918dc52c666f. That repository on my disc is about 1.3 GB and contains many, many objects. For a report on the relative activity of the linux kernel repository, refer to What I found: $ time git clone ssh://mark-pc1/var/lib/git/mwaite/linux.git - 2m41s $ time (mkdir fetch;cd fetch;git init; git fetch ssh://mark-pc1/var/lib/git/mwaite/linux.git) - 2m52s The "git fetch" time was consistently about 7% slower than the "git clone" time. Your experience is significantly different, since you note in the original report that "git fetch takes 14 mins, git clone takes about 4 minutes." I don't plan to make any change in the git plugin based on that, but wanted to record my observed results in case others are concerned about the apparent difference between "git clone" and "git fetch". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [email-ext-plugin] (JENKINS-7514) Custom Jelly Content for email-ext plugin - for sending nice custom messages
AnneTheAgile commented on JENKINS-7514 Custom Jelly Content for email-ext plugin - for sending nice custom messages As of today, searching for 'CustomJellyContent' in https://github.com/jenkinsci/email-ext-plugin/tree/master/src/main/resources/hudson/plugins/emailext/templates yields no hits. So perhaps this patch was refactored? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26680) Extraneous Forward-Slash in ssh:// path to repository
Mark Waite commented on JENKINS-26680 Extraneous Forward-Slash in ssh:// path to repository I performed some further tests with multiple versions of git. I can't find a way to make any of them work with a relative path in an ssh URL. The tests used git / operating system versions: git 1.7.1, CentOS 6.6, "git clone ssh://mwaite@mark-pc1:bin/" fails and reports "ssh: Could not resolve hostname mark-pc1:bin: Name or service not known" git 1.7.2.5, Debian 6, "git clone ssh://mwaite@mark-pc1:bin/" fails and reports "ssh: Could not resolve hostname mark-pc1:bin: Name or service not known" git 1.7.10.4, Debian 7,"git clone ssh://mwaite@mark-pc1:bin/" fails and reports "ssh: Could not resolve hostname mark-pc1:bin: Name or service not known" git 2.1.4, Debian Testing, "git clone ssh://mwaite@mark-pc1:bin/" fails and reports "fatal: '/' does not appear to be a git repository" git 2.2.1, Ubuntu 14.04, "git clone ssh://mwaite@mark-pc1:bin/" fails and reports "fatal: '/' does not appear to be a git repository" What git version are you running which passed that test? Are you using command line git or JGit? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
SCM/JIRA link daemon commented on JENKINS-12523 Could not initialize class org.libvirt.Connect Code changed in jenkins User: g-k-r Path: pom.xml src/main/java/hudson/plugins/libvirt/VirtualMachineManagement.java http://jenkins-ci.org/commit/libvirt-slave-plugin/f01db463cea91000c693eb169b46fb722ac6dcfe Log: Merge pull request #10 from g-k-r/JENKINS-12523 package old JNA version 3.3.0 with the plugin Compare: https://github.com/jenkinsci/libvirt-slave-plugin/compare/06470747e503...f01db463cea9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [libvirt-slave-plugin] (JENKINS-12523) Could not initialize class org.libvirt.Connect
SCM/JIRA link daemon commented on JENKINS-12523 Could not initialize class org.libvirt.Connect Code changed in jenkins User: G.Kr Path: pom.xml src/main/java/hudson/plugins/libvirt/VirtualMachineManagement.java http://jenkins-ci.org/commit/libvirt-slave-plugin/fb3cbbec03f8bc0ec323a3cd4121128699e54085 Log: package old JNA version 3.3.0 with the plugin fixes #JENKINS-12523 https://issues.jenkins-ci.org/browse/JENKINS-12523 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [slack-plugin] (JENKINS-26066) NPE for completed project without a slack configuration
SCM/JIRA link daemon resolved JENKINS-26066 as Fixed NPE for completed project without a slack configuration Change By: SCM/JIRA link daemon (01/Feb/15 7:34 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slack-plugin] (JENKINS-26066) NPE for completed project without a slack configuration
SCM/JIRA link daemon commented on JENKINS-26066 NPE for completed project without a slack configuration Code changed in jenkins User: Sam Gleske Path: src/main/java/jenkins/plugins/slack/ActiveNotifier.java http://jenkins-ci.org/commit/slack-plugin/5ae2f2088e8db606ecbc2695a986a839d9faa72d Log: Merge PR #35 Add null check and log FIXED JENKINS-26066 https://issues.jenkins-ci.org/browse/JENKINS-26066 Compare: https://github.com/jenkinsci/slack-plugin/compare/cc82580a06fa...5ae2f2088e8d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [slack-plugin] (JENKINS-26066) NPE for completed project without a slack configuration
SCM/JIRA link daemon commented on JENKINS-26066 NPE for completed project without a slack configuration Code changed in jenkins User: timp21337 Path: src/main/java/jenkins/plugins/slack/ActiveNotifier.java http://jenkins-ci.org/commit/slack-plugin/d72d4b681e34339ba47123c264b1f28d181b34da Log: [FIXED JENKINS-26066] Add null check and log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [slack-plugin] (JENKINS-26066) NPE for completed project without a slack configuration
Sam Gleske assigned JENKINS-26066 to Sam Gleske NPE for completed project without a slack configuration Change By: Sam Gleske (01/Feb/15 7:15 PM) Assignee: Sam Gleske This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ec2-plugin] (JENKINS-26725) Tries spawning more and more EC2 slaves when master runs out of space
Daniel Doubrovkine updated JENKINS-26725 Tries spawning more and more EC2 slaves when master runs out of space Change By: Daniel Doubrovkine (01/Feb/15 5:53 PM) Attachment: jenkins.log Attachment: jenkins.log.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ec2-plugin] (JENKINS-26725) Tries spawning more and more EC2 slaves when master runs out of space
Daniel Doubrovkine
created JENKINS-26725
Tries spawning more and more EC2 slaves when master runs out of space
Issue Type:
Bug
Assignee:
Francis Upton
Components:
ec2-plugin
Created:
01/Feb/15 5:48 PM
Description:
First we start seeing these:
Feb 1, 2015 7:11:00 AM hudson.model.Executor run
SEVERE: Unexpected executor death
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:300)
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:220)
at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:315)
at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:148)
at java.io.OutputStreamWriter.close(OutputStreamWriter.java:233)
at java.io.BufferedWriter.close(BufferedWriter.java:265)
at hudson.util.AtomicFileWriter.close(AtomicFileWriter.java:94)
at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:109)
at hudson.util.TextFile.write(TextFile.java:121)
at hudson.model.Job.saveNextBuildNumber(Job.java:274)
at hudson.model.Job.assignBuildNumber(Job.java:332)
at hudson.model.Run.(Run.java:286)
at hudson.model.AbstractBuild.(AbstractBuild.java:167)
at hudson.model.Build.(Build.java:92)
at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:34)
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:534)
at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:186)
at hudson.model.AbstractProject.newBuild(AbstractProject.java:1001)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1194)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
at hudson.model.Executor.run(Executor.java:213)
Feb 1, 2015 7:13:49 AM hudson.model.AsyncPeriodicWork$1 run
And then more instances get started:
INFO: Excess workload after pending Spot instances: 1
Feb 1, 2015 12:39:37 PM hudson.plugins.ec2.EC2Cloud addProvisionedSlave
INFO: Provisioning for AMI ami-cc8871a4; Estimated number of total slaves: 15; Estimated number of slaves for ami ami-cc8871a4: 11
Launching ami-cc8871a4 for template generic-slave-cc8871a4
Feb 1, 2015 12:39:37 PM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply
INFO: Started provisioning generic-slave-cc8871a4 (ami-cc8871a4) from ec2-us-east-1 with 1 executors. Remaining excess workload: -0.07
Feb 1, 2015 12:39:37 PM hudson.plugins.ec2.SlaveTemplate provisionOndemand
INFO: Launching ami-cc8871a4 for template generic-slave-cc8871a4
Looking for existing instances with describe-instance: {InstanceIds: [],Filters: [{Name: image-id,Values: [ami-cc8871a4]}, {Name: instance.group-name,Values: [default, build_slaves]}, {N
ame: key-name,Values: [artsy_build_keypair]}, {Name: instance-type,Values: [c1.medium]}, {Name: tag:Name,Values: [build-slave-20140619]}, {Name: instance-state-name,Values: [stopped, sto
pping]}],}
No existing instance found - created: {InstanceId: i-988b7077,ImageId: ami-cc8871a4,State:
Unable to find source-code formatter for language: 0,name: pending. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, java
,PrivateDnsName: ,PublicDnsName: ,StateTransitionReason: ,KeyName: artsy
_build_keypair,AmiLaunchIndex: 0,ProductCodes: [],InstanceType: c1.medium,LaunchTime: Sun Feb 01 12:39:38 EST 2015,Placement: {AvailabilityZone: us-east-1a,GroupName: ,Tenancy: default},
KernelId: aki-88aa75e1,Monitoring: {State: disabled},StateReason:
Unable to find source-code formatter for language: pending,message: pending. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, java
,Architecture: x86_64,RootDeviceType: ebs,RootDeviceName
[JIRA] [core] (JENKINS-26723) Show displayName in build remote API
Patrik Boström assigned JENKINS-26723 to Unassigned Show displayName in build remote API Change By: Patrik Boström (01/Feb/15 5:17 PM) Assignee: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26723) Show displayName in build remote API
Patrik Boström commented on JENKINS-26723 Show displayName in build remote API Created PR https://github.com/jenkinsci/jenkins/pull/1558 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26724) "Delete build" and "Delete project" actions are confusingly similar
Daniel Beck commented on JENKINS-26724 "Delete build" and "Delete project" actions are confusingly similar I'd prefer the Delete Project dialogue to be very different from Delete Build Assuming freestyle projects, one is a link labeled Delete Project that opens a _javascript_ popup dialog (possibly dimming the rest of the web page, e.g. in Firefox) asking Are you sure about deleting the Project ‘name’?; while the other is a link labeled Delete Build that navigates to an entirely new web page that asks Are you sure about deleting the build?. There is no way these could be confused if you've ever actually looked at both of them. They hardly cannot be any more different from each other without adding superfluous speed bumps like requiring password authorisation I'd enjoy this a lot the next time I clean up my instance and need to delete a few dozen obsolete projects… This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26576) old builds not getting cleaned up
Arpit Gupta commented on JENKINS-26576 old builds not getting cleaned up Upgraded to 1.598 and the older jobs are now getting cleaned 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] [core] (JENKINS-26571) Job page becomes un responsive when there are a lot of builds in the queue
Arpit Gupta commented on JENKINS-26571 Job page becomes un responsive when there are a lot of builds in the queue Ignore the above comment. Wrong jira. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26571) Job page becomes un responsive when there are a lot of builds in the queue
Arpit Gupta commented on JENKINS-26571 Job page becomes un responsive when there are a lot of builds in the queue Upgraded to 1.598 and the older jobs are now getting cleaned 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] [core] (JENKINS-22811) Folder loading can be broken by a NPE in a build wrapper in one job
SCM/JIRA link daemon commented on JENKINS-22811 Folder loading can be broken by a NPE in a build wrapper in one job Code changed in jenkins User: christ66 Path: core/src/main/java/hudson/model/ItemGroupMixIn.java http://jenkins-ci.org/commit/jenkins/937ed1b9ca6d43e8aed04ef8b3b1dd0a6c001256 Log: JENKINS-22811 Remove redundant catch exception (cherry picked from commit d58c3cd5d6ac851f0a28b1c1bb6dbeb02fd2b1c9) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22811) Folder loading can be broken by a NPE in a build wrapper in one job
SCM/JIRA link daemon commented on JENKINS-22811 Folder loading can be broken by a NPE in a build wrapper in one job Code changed in jenkins User: christ66 Path: test/src/test/java/hudson/model/ItemGroupMixInTest.java http://jenkins-ci.org/commit/jenkins/383223bc467d8e3b77dce0cdc4b542f154e1adc1 Log: JENKINS-22811 Obtain folder from jenkins instead of using local variable. (cherry picked from commit 8f24c4aa5ccd944c4647e9f99077cad46cb24a2d) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22811) Folder loading can be broken by a NPE in a build wrapper in one job
SCM/JIRA link daemon commented on JENKINS-22811 Folder loading can be broken by a NPE in a build wrapper in one job Code changed in jenkins User: christ66 Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/Actionable.java http://jenkins-ci.org/commit/jenkins/ee309ef92096610259b0ec01e82940ba022bed1a Log: JENKINS-22811 Fix log message to report more verbose message. (cherry picked from commit da1c74f619feea134aa887b1e5b1774307ea0e47) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22811) Folder loading can be broken by a NPE in a build wrapper in one job
SCM/JIRA link daemon commented on JENKINS-22811 Folder loading can be broken by a NPE in a build wrapper in one job Code changed in jenkins User: christ66 Path: test/src/test/java/hudson/model/ItemGroupMixInTest.java http://jenkins-ci.org/commit/jenkins/82adc7ff70438ef2484aecfa7d5f31a98b3d9783 Log: JENKINS-22811 Mark test extension with the correct annotation (cherry picked from commit fa40c102f5dbd8b02470317d730a3778c9153b64) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22811) Folder loading can be broken by a NPE in a build wrapper in one job
SCM/JIRA link daemon commented on JENKINS-22811 Folder loading can be broken by a NPE in a build wrapper in one job Code changed in jenkins User: christ66 Path: test/src/test/java/hudson/model/ItemGroupMixInTest.java http://jenkins-ci.org/commit/jenkins/13774a105d6b750689afe67261f85c5fd949d371 Log: JENKINS-22811 Remove unnecessary check in test unit. Fix misleading test unit comment. (cherry picked from commit 3661ed5093ee1f4dd508bbea8272de447fcc6996) Compare: https://github.com/jenkinsci/jenkins/compare/16ee133b4807...13774a105d6b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22811) Folder loading can be broken by a NPE in a build wrapper in one job
SCM/JIRA link daemon commented on JENKINS-22811 Folder loading can be broken by a NPE in a build wrapper in one job Code changed in jenkins User: christ66 Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/Actionable.java core/src/main/java/hudson/model/Project.java test/src/test/java/hudson/model/ItemGroupMixInTest.java test/src/test/resources/hudson/model/ItemGroupMixInTest/xmlFileReadExceptionOnLoad.zip http://jenkins-ci.org/commit/jenkins/758cb5be1eee8d600734c97a15666002d7c1d39a Log: JENKINS-22811 If a project action fails to load we should log the project action and continue to load the project. (cherry picked from commit c3eb1cac794e2cf8efcb26695e8eb27ed80ece5c) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22811) Folder loading can be broken by a NPE in a build wrapper in one job
SCM/JIRA link daemon commented on JENKINS-22811 Folder loading can be broken by a NPE in a build wrapper in one job Code changed in jenkins User: christ66 Path: test/src/test/java/hudson/model/ItemGroupMixInTest.java http://jenkins-ci.org/commit/jenkins/8b528efc49c2735fd3418b4fcb94832190339425 Log: JENKINS-22811 Fixed compilation error (cherry picked from commit b5213b3815d3223f619113ebbccde4a8733df4c0) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Steven Christou commented on JENKINS-26612 svn: absolutely unacceptably SLOW Tim Jaacks Were the thread dumps taken using subversion plugin 2.5 or 2.4.5? at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99) CheckoutUpdater.java#99 does not match with the perform method for 2.5. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Steven Christou started work on JENKINS-26612 svn: absolutely unacceptably SLOW Change By: Steven Christou (01/Feb/15 1:59 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [windows-slaves-plugin] (JENKINS-22692) Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues
Oleg Nenashev updated JENKINS-22692 Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues Change By: Oleg Nenashev (01/Feb/15 1:15 PM) Labels: winsw This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [windows-slaves-plugin] (JENKINS-22692) Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues
Oleg Nenashev assigned JENKINS-22692 to Oleg Nenashev Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues Change By: Oleg Nenashev (01/Feb/15 1:15 PM) Assignee: Kohsuke Kawaguchi Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26724) "Delete build" and "Delete project" actions are confusingly similar
David Brown commented on JENKINS-26724 "Delete build" and "Delete project" actions are confusingly similar Thank you, @oleg. Unfortunately I'm running v2.2 of that plug-in. I see the feature to restore deleted projects was introduced at 2.5 so I need to upgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26724) "Delete build" and "Delete project" actions are confusingly similar
Oleg Nenashev updated JENKINS-26724 "Delete build" and "Delete project" actions are confusingly similar Change By: Oleg Nenashev (01/Feb/15 10:34 AM) Summary: Project deleted in error "Delete build" and "Delete project" actions are confusingly similar Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26724) Project deleted in error
Oleg Nenashev updated JENKINS-26724 Project deleted in error Reassigned the issue to Jenkins core. BTW, "Job Config History" Plugin can help you to restore jobs even after their deletion. Change By: Oleg Nenashev (01/Feb/15 10:33 AM) Assignee: Oleg Nenashev Component/s: core Component/s: _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/d/optout.
[JIRA] [_test] (JENKINS-26724) Project deleted in error
David Brown created JENKINS-26724 Project deleted in error Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 01/Feb/15 10:25 AM Description: Having accidentally deleted a Project/Job, it occurs to me that the "Are you sure?" dialogue which is presented before the deletion is performed is too similar to that used when deleting BUILDS. I frequently have to delete builds, so I am a little trigger-happy when I see the "Are you sure" question. I realise that this is my own stupid fault (user error), and I've seen references on here to plug-ins that may enable a restore (assuming said plug-in was already installed prior to the error). I've also seen a suggestion that the "Delete Project" option can be disabled per user. I'd prefer the Delete Project dialogue to be very different from Delete Build, perhaps requiring password authorisation, so as to reduce the risk. Project: Jenkins Priority: Minor Reporter: David Brown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26723) Show displayName in build remote API
Patrik Boström created JENKINS-26723 Show displayName in build remote API Issue Type: Improvement Assignee: Patrik Boström Components: core Created: 01/Feb/15 8:48 AM Description: In the build remote API should also show the displayName. It is commonly used to set a version number of the build in for example build pipelines. Example (https://ci.jenkins-ci.org/view/Jenkins%20core/job/jenkins_main_trunk/3961/api/json) Current API shows fullDisplayName which includes the projectname and displayname: "jenkins_main_trunk #3961" The displayName should show just "#3961". Makes it easier to for example create external information radiators showing the version/build number for different jobs. Project: Jenkins Priority: Minor Reporter: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloudformation-plugin] (JENKINS-16860) Support for cloudformation CAPABILITIES option
Jithin Xavier commented on JENKINS-16860 Support for cloudformation CAPABILITIES option I'm getting this error after creating cloudformation successfully and build end up with FAILED status. Successfully created stack: testStack-1 FATAL: null java.lang.NullPointerException at com.syncapse.jenkinsci.plugins.awscloudformationwrapper.CloudFormationBuildStep.perform(CloudFormationBuildStep.java:76) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
