[JIRA] [google-play-android-publisher-plugin] (JENKINS-27330) Add ability to re-assign release track of existing APKs
Christopher Orr closed JENKINS-27330 as Fixed Add ability to re-assign release track of existing APKs Version 1.3 of the plugin has been released, which adds a "Move Android APKs to a different release track" build step. Change By: Christopher Orr (22/Mar/15 10:02 AM) Status: InProgress Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26472) Jenkins maven-project plugin doesn't support reactor module exclusion
Andreas Horst commented on JENKINS-26472 Jenkins maven-project plugin doesnt support reactor module exclusion Please reconsider effectively simply ignoring this issue as it is clearly a fault in the Maven integration in Jenkins. Luckily we were able to workaround this fault but that should not be the regular approach here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-publish-plugin] (JENKINS-25690) Pull base docker image to make sure it's up to date
Jo Vandeginste commented on JENKINS-25690 Pull base docker image to make sure its up to date I have submitted a pull request that solves exactly that with the recent --pull=true flag for the docker build command https://github.com/jenkinsci/docker-build-publish-plugin/pull/10 If accepted and merged, this issue will be solved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cvs-plugin] (JENKINS-27538) SCM polling error due to CVS authentication failure while running rlog command ($HOME variable not expanded for private key paths)
Chaitanya Pinnamaneni created JENKINS-27538 SCM polling error due to CVS authentication failure while running rlog command ($HOME variable not expanded for private key paths) Issue Type: Bug Assignee: Unassigned Attachments: cvs-config.png, SI-Jenkkns.pdf Components: cvs-plugin Created: 22/Mar/15 10:50 AM Description: After upgrading to CVS Plugin 2.12 (from 1.6), the SCM polling is failing. CVS checkout/update Works fine with same settings (Both on Master Slaves) CVS Authentication values : Refer to attached screenshot Only SCM polling is affected and looking at the error it seems the $HOME Variable not expanded (Though CVS checkout works fine) Any help would be greatly appreciated. CVS Polling Log Started on Mar 21, 2015 10:08:00 PM cvs rlog -S -d21 Mar 2015 19:13:12 +110021 Mar 2015 22:08:00 +1100 lendfast-core-root ERROR: Failed to record SCM polling for hudson.maven.MavenModuleSet@5b0973cf[lendfast-core-root-HEAD-Build] java.lang.RuntimeException: CVS authentication failure while running rlog command at hudson.scm.AbstractCvs.executeRlog(AbstractCvs.java:704) at hudson.scm.AbstractCvs.getRemoteLogForModule(AbstractCvs.java:660) at hudson.scm.AbstractCvs.calculateRepositoryState(AbstractCvs.java:611) at hudson.scm.AbstractCvs.compareRemoteRevisionWith(AbstractCvs.java:515) at hudson.scm.CVSSCM.compareRemoteRevisionWith(CVSSCM.java:224) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1446) at hudson.model.AbstractProject.poll(AbstractProject.java:1349) at jenkins.triggers.SCMTriggerItem$SCMTriggerItems$Bridge.poll(SCMTriggerItem.java:119) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:515) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:544) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.netbeans.lib.cvsclient.connection.AuthenticationException: SSH connection failed. at org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:141) at org.netbeans.lib.cvsclient.Client$1.run(Client.java:374) ... 1 more Caused by: com.jcraft.jsch.JSchException: java.io.FileNotFoundException: $HOME/.ssh/id_dsa (No such file or directory) at com.jcraft.jsch.KeyPair.load(KeyPair.java:524) at com.jcraft.jsch.IdentityFile.newInstance(IdentityFile.java:40) at com.jcraft.jsch.JSch.addIdentity(JSch.java:389) at com.jcraft.jsch.JSch.addIdentity(JSch.java:370) at org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:135) ... 2 more Caused by: java.io.FileNotFoundException: $HOME/.ssh/id_dsa (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.init(FileInputStream.java:138) at java.io.FileInputStream.init(FileInputStream.java:93) at com.jcraft.jsch.Util.fromFile(Util.java:492) at com.jcraft.jsch.KeyPair.load(KeyPair.java:521) ... 6 more Environment: Environment : Refer to attched pdf Jenkins Version: Jenkins ver. 1.596.1 Operating System : CentOS 6 (86_x64) CVS plugin versions : 2.12 Concurrent Versions System (CVS) 1.11.23 (client/server) Running Jenkins directly Project: Jenkins Priority: Critical Reporter: Chaitanya Pinnamaneni
[JIRA] [core] (JENKINS-27468) Jenkins exposes internal port on redirections
Pavel Batanov updated JENKINS-27468 Jenkins exposes internal port on redirections Change By: Pavel Batanov (22/Mar/15 1:33 PM) Summary: Jenkinsexposesinternalport whileredirectingtotrailedslashURLsfromno-slashURLs. onredirections This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-27537) Regular list project view failing to load with Build Pipeline 1.4.5 installed
David Resnick created JENKINS-27537 Regular list project view failing to load with Build Pipeline 1.4.5 installed Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 22/Mar/15 7:45 AM Description: Upgrading build-pipeline plugin beyond 1.4.5 (so far 1.4.6 and 1.4.7) breaks the regular job list view. Instead of jobs, the following stack trace is displayed: Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.602.jar!/hudson/model/View/index.jelly:42:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.602.jar!/lib/hudson/projectView.jelly:67:24: d:invokeBody java.lang.ClassCastException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:46) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) 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:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at
[JIRA] [build-pipeline-plugin] (JENKINS-27537) Regular list project view failing to load with Build Pipeline 1.4.5 installed
Daniel Beck commented on JENKINS-27537 Regular list project view failing to load with Build Pipeline 1.4.5 installed Could you try to determine which project(s) cause the view to fail to display? I have a suspicion this is due to https://github.com/jenkinsci/build-pipeline-plugin/commit/bd77518bb3b9220f979f7906b210b2dd2225bada making the cause static. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [docker-build-publish-plugin] (JENKINS-25690) Pull base docker image to make sure it's up to date
Jo Vandeginste assigned JENKINS-25690 to Jo Vandeginste Pull base docker image to make sure its up to date Change By: Jo Vandeginste (22/Mar/15 9:21 AM) Assignee: MichaelNeale JoVandeginste This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [github-plugin] (JENKINS-26145) Narrow down github auth scope for user logins
Pedro Algarvio commented on JENKINS-26145 Narrow down github auth scope for user logins It's not like you give access to your account to a third party, but to software you run yourself and can read the source code of. Therefore I don't see how this can be classified as anything more severe than Minor. Let's consider the following... Your company has a Jenkins installation using this plugin. This plugin requests access to ALL repositories, including your private repositories, not just your company's private repositories. Do you really think that your company should have access to your private repositories?! After reading the source code I think that the permissions were broaden to support the Github Commiter Authorization Strategy. If this is the case, I think that only when using Github Commiter Authorization Strategy the permissions should be broaden. Of course, preferably, you should be able to tell the plugin what permissions you want to ask from your users, and the plugin should warn if any of it's enabled features require more permissions... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23543) Launchctl does not load Jenkins on OS X 10.10 Yosemite
Daniel Beck resolved JENKINS-23543 as Duplicate Launchctl does not load Jenkins on OS X 10.10 Yosemite Alright, it's still early, so I didn't see this was resolved as Duplicate. There is no reason to reopen issues resolved or closed as Duplicate other than having determined that it is not the same issue as the linked one. As you can see, the linked issue is still unresolved, so it's unsurprising you're still seeing this problem. Please read how this issue tracker is used on https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking Change By: Daniel Beck (22/Mar/15 7:14 AM) Status: Reopened Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27270) Support jobs organized under folders
Stephan Pauxberger commented on JENKINS-27270 Support jobs organized under folders Pull Request: https://github.com/Diabol/delivery-pipeline-plugin/pull/98 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [findbugs-plugin] (JENKINS-19096) Findbugs Reporting not working with Maven 3.1
Ulli Hafner resolved JENKINS-19096 as Fixed Findbugs Reporting not working with Maven 3.1 This issue is also fixed by pull request for JENKINS-26923. Change By: Ulli Hafner (22/Mar/15 4:29 PM) Status: Open Resolved Assignee: olamy UlliHafner 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] [delivery-pipeline-plugin] (JENKINS-27539) NPE when using jobs with the same name in different folders
Stephan Pauxberger commented on JENKINS-27539 NPE when using jobs with the same name in different folders Pull Request: https://github.com/Diabol/delivery-pipeline-plugin/pull/98 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jabber-plugin] (JENKINS-10742) Send HTML jabber messages
kutzi commented on JENKINS-10742 Send HTML jabber messages The only idea I've got currently would be a complete separation of model and view. I.e. the BotCommands would only return the model for the messages and the concrete implementations would decide on how to render this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jabber-plugin] (JENKINS-10742) Send HTML jabber messages
kutzi commented on JENKINS-10742 Send HTML jabber messages Thomas, it's really a difficult question on how to approach this issue. Not only the IMChat interface would have needed to be changed, but also all BotCommands, the BuildToChatNotifiers and possibly more. You could introduce a sub-interface of IMChat which accepts additionally a rich-text message in addition to the string message. But the rich-text format would be dependend on the concrete implementation (RT messages in Jabber look probably totally different than those in IRC). So no real solution IMO. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [weblogic-deployer-plugin] (JENKINS-26366) Error deploying to WebLogic when using Promoted Builds plugin
Raphael CHAUMIER commented on JENKINS-26366 Error deploying to WebLogic when using Promoted Builds plugin Hi, I didn't work on it again. I'll have more time to do this week. So the next release will occur on the next week-end. Regards, This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [weblogic-deployer-plugin] (JENKINS-26992) WebLogic deployer does not expand variables
Raphael CHAUMIER updated JENKINS-26992 WebLogic deployer does not expand variables Change By: Raphael CHAUMIER (22/Mar/15 5:49 PM) Labels: weblgoc-deployer-plugin-2.13 weblogic-deployer-plugin-2. 14 13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
ryangardner commented on JENKINS-25127 Hook uninstalled if job is in a subfolder I sent a pull request with the above fix. It fixed the issue for me. https://github.com/jenkinsci/github-plugin/pull/51#issuecomment-84089491 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [weblogic-deployer-plugin] (JENKINS-19962) Add the ability to declare a job successful even if there's no changes
Raphael CHAUMIER updated JENKINS-19962 Add the ability to declare a job successful even if theres no changes Change By: Raphael CHAUMIER (22/Mar/15 5:48 PM) Labels: deploymentweblogic weblogic-deployer-plugin-2.14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-26472) Jenkins maven-project plugin doesn't support reactor module exclusion
Jakub Bochenski commented on JENKINS-26472 Jenkins maven-project plugin doesnt support reactor module exclusion Yeah it seems to me now I should have just followed the advice on the net and not use the maven plugin at all. there is no way you can replicate the injected hooks that Jenkins puts into your Maven build When it blows up, and it will blow up, it blows up big http://javaadventure.blogspot.com/2013/11/jenkins-maven-job-type-considered-evil.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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27539) NPE when using jobs with the same name in different folders
Stephan Pauxberger created JENKINS-27539 NPE when using jobs with the same name in different folders Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 22/Mar/15 4:27 PM Description: When using the same basic item name for more than one job in different folders, and those items are used in a pipeline, the view is not displayed (Error communicating to server! Server Error) The stacktrace shows an NPE: Caused by: java.lang.NullPointerException at org.jgrapht.graph.AbstractGraph.assertVertexExist(Unknown Source) at org.jgrapht.graph.AbstractBaseGraph$DirectedSpecifics.getEdgeContainer(Unknown Source) at org.jgrapht.graph.AbstractBaseGraph$DirectedSpecifics.outDegreeOf(Unknown Source) at org.jgrapht.graph.AbstractBaseGraph.outDegreeOf(Unknown Source) at se.diabol.jenkins.pipeline.domain.Stage.findAllRunnablePaths(Stage.java:267) at se.diabol.jenkins.pipeline.domain.Stage.placeStages(Stage.java:225) at se.diabol.jenkins.pipeline.domain.Stage.extractStages(Stage.java:164) at se.diabol.jenkins.pipeline.domain.Pipeline.extractPipeline(Pipeline.java:123) at se.diabol.jenkins.pipeline.DeliveryPipelineView.getComponent(DeliveryPipelineView.java:323) at se.diabol.jenkins.pipeline.DeliveryPipelineView.getPipelines(DeliveryPipelineView.java:293) ... 90 more The reason is that ProjectUtil.getAllDownstreamProjects() stores the projects in a map using the simple name as a key. So of all equally named projects only one is retained, so the firstProject is usually not found as vertex in the graph leading to the NPE. I will create a Pull Request for that. Environment: 0.8.10 Project: Jenkins Priority: Major Reporter: Stephan Pauxberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [weblogic-deployer-plugin] (JENKINS-26366) Error deploying to WebLogic when using Promoted Builds plugin
Raphael CHAUMIER started work on JENKINS-26366 Error deploying to WebLogic when using Promoted Builds plugin Change By: Raphael CHAUMIER (22/Mar/15 5:47 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-27537) Regular list project view failing to load with Build Pipeline 1.4.5 installed
Patrik Boström commented on JENKINS-27537 Regular list project view failing to load with Build Pipeline 1.4.5 installed Any more details about the exception in logfiles? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-26472) Jenkins maven-project plugin doesn't support reactor module exclusion
Daniel Beck commented on JENKINS-26472 Jenkins maven-project plugin doesnt support reactor module exclusion Please reconsider effectively simply ignoring this issue I really doubt anyone is actively ignoring this issue. If you're referring to me reducing priority, please note that before I reviewed most of the unresolved core issues in this tracker, we had dozens and dozens of blocker/critical core issues (in many cases, just like this one, they weren't actually that severe), and nobody cared about those either. It's not like an alarm goes off somewhere whenever an issue with high "priority" gets filed. As far as I can tell, priority is given to regressions, issues affecting many users, and issues that the developers themselves want to see fixed (and, in the case of Cloudbees employed Jenkins devs, issues from customer support requests). This issue seems to be none of the above. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-27540) FILE macro is generically useful and could be part of the token-macro plugin
Christopher Orr
created JENKINS-27540
FILE macro is generically useful and could be part of the token-macro plugin
Issue Type:
Improvement
Assignee:
Alex Earl
Components:
email-ext-plugin, token-macro-plugin
Created:
22/Mar/15 7:46 PM
Description:
Email-ext defines a ${FILE, path='foo.txt'} token macro which makes it possible to read in the contents of a file.
This seems generic enough to be useful in many cases (like $PROPFILE), and indeed I wanted to integrate the $FILE macro into one of my plugins. But it seems weird to depend on the email-ext plugin, and I didn't really want to copy the code into my own plugin.
So would it be possible to move this macro implementation up to the token-macro-plugin itself?
Project:
Jenkins
Priority:
Minor
Reporter:
Christopher Orr
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-27315) Add git commit author email as environment variable
Mark Waite resolved JENKINS-27315 as Wont Fix Add git commit author email as environment variable Change By: Mark Waite (23/Mar/15 12:45 AM) Status: Open 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/d/optout.
[JIRA] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
Baptiste Mathus commented on JENKINS-26186 Last Build Trigger Column does not print author name Thanks a lot Daniel, I wasn't aware it was possible. So that's obviously what I'm gonna do. Thanks again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23543) Launchctl does not load Jenkins on OS X 10.10 Yosemite
Daniel Beck edited a comment on JENKINS-23543 Launchctl does not load Jenkins on OS X 10.10 Yosemite Dominik Pich: Please be more specific. What version did you try, what exactly happened? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23543) Launchctl does not load Jenkins on OS X 10.10 Yosemite
Daniel Beck commented on JENKINS-23543 Launchctl does not load Jenkins on OS X 10.10 Yosemite ~dajidjan: Please be more specific. What version did you try, what exactly happened? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [docker-build-publish-plugin] (JENKINS-25690) Pull base docker image to make sure it's up to date
Michael Neale commented on JENKINS-25690 Pull base docker image to make sure its up to date Thanks Jo - put some comments on the PR. Looks good, and thanks for this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [google-play-android-publisher-plugin] (JENKINS-27330) Add ability to re-assign release track of existing APKs
Ivan Narino commented on JENKINS-27330 Add ability to re-assign release track of existing APKs Thank you so much! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-27540) FILE macro is generically useful and could be part of the token-macro plugin
Alex Earl commented on JENKINS-27540 FILE macro is generically useful and could be part of the token-macro plugin I'm not sure if that would work, but there could be a separate token created in token-macro or something, and then an alias could be used in email-ext, while retaining the current token. Or maybe it would just work to release the two plugins at the same time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extensible-choice-parameter-plugin] (JENKINS-27375) Add options to enable / disable choice providers
ikedam assigned JENKINS-27375 to ikedam Add options to enable / disable choice providers Change By: ikedam (22/Mar/15 10:37 PM) Assignee: 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/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-26366) Error deploying to WebLogic when using Promoted Builds plugin
Raphael CHAUMIER commented on JENKINS-26366 Error deploying to WebLogic when using Promoted Builds plugin Can you tell me more about the way you configure your 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/d/optout.
[JIRA] [svn-tag-plugin] (JENKINS-27339) svn-tag : Unable to import build artificatcs to SVN
monika verma commented on JENKINS-27339 svn-tag : Unable to import build artificatcs to SVN Hello, When can I expect the response ? Regards Monika This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ldap-plugin] (JENKINS-23214) LDAP Plugin occasionally does not connect LDAP server
Manoj Binjola commented on JENKINS-23214 LDAP Plugin occasionally does not connect LDAP server Hi, is there any update on this issue. Please let us know if its not related to Jenkins, so that we could focus on other aspects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
