[JIRA] [docker-plugin] (JENKINS-28639) Configure docker node - No page found 'configure-entries.jelly' for class com.nirima.jenkins.plugins.docker.DockerComputer
Title: Message Title Tomasz Glowski created an issue Jenkins / JENKINS-28639 Configure docker node - No page found 'configure-entries.jelly' for class com.nirima.jenkins.plugins.docker.DockerComputer Issue Type: Bug Assignee: Kanstantsin Shautsou Components: docker-plugin Created: 29/May/15 7:42 AM Environment: jenkins version: 1.614 docker plugin: 0.9.0-rc1 Priority: Major Reporter: Tomasz Glowski javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.614.jar!/hudson/model/Computer/configure.jelly:43:71: No page found 'configure-entries.jelly' for class com.nirima.jenkins.plugins.docker.DockerComputer at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) 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:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Staple
[JIRA] [docker-plugin] (JENKINS-28639) Configure docker node - No page found 'configure-entries.jelly' for class com.nirima.jenkins.plugins.docker.DockerComputer
Title: Message Title Tomasz Glowski updated an issue Jenkins / JENKINS-28639 Configure docker node - No page found 'configure-entries.jelly' for class com.nirima.jenkins.plugins.docker.DockerComputer Change By: Tomasz Glowski javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.614.jar!/hudson/model/Computer/configure.jelly:43:71: No page found 'configure-entries.jelly' for class com.nirima.jenkins.plugins.docker.DockerComputer at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) 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:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) a
[JIRA] [email-ext-plugin] (JENKINS-27523) External Default Pre-send Script
Title: Message Title Grzegorz Kotarski commented on JENKINS-27523 Re: External Default Pre-send Script This is not a workaround for me: in the script I do some imports like "import com.sonyericsson.jenkins.plugins.bfa.model.FailureCauseBuildAction" , etc. I would have to add all necessary libraries to classpath to compile it. And I would have to compile this script to import it every time it changes (script is synchronized via a version source control system) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27523) External Default Pre-send Script
Title: Message Title Grzegorz Kotarski edited a comment on JENKINS-27523 Re: External Default Pre-send Script This is not a workaround for me: in the script I do some imports like "import com.sonyericsson.jenkins.plugins.bfa.model.FailureCauseBuildAction" , etc. I would have to add all necessary libraries to classpath to compile it. And I would have to compile this script to import it every time it changes (script is synchronized via a version source control system) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title Alexander Fendt commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. Hi Guys, had the same problems since my update from Subversion Plugin 2.4.latest to 2.5 As you can see in the changelog, in version 2.5 SVNVersion is changed to SVN1.8 As far as I have SVN 1.7 installed on my machines I went back to Subversion Plugin 2.4 and everything worked fine again. Hope this helps you Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-28594) Leading underscore added to committers email address.
Title: Message Title nir h commented on JENKINS-28594 Re: Leading underscore added to committers email address. The user IDs are in the form of "domain_user", user accounts are in the form of "domain\user". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-28564) Add new option "Always link to last build on job page" for html-publisher
Title: Message Title Carsten Lenz commented on JENKINS-28564 Re: Add new option "Always link to last build on job page" for html-publisher I created https://github.com/jenkinsci/job-dsl-plugin/pull/492 for this Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27523) External Default Pre-send Script
Title: Message Title Alex Earl commented on JENKINS-27523 Re: External Default Pre-send Script You don't need to compile the script for it to be part of the class path. Groovy scripts will be compiled on the fly when they are imported. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28532) Jobs get stuck in the queue
Title: Message Title James Howe commented on JENKINS-28532 Re: Jobs get stuck in the queue I think the non-fixable blocking may be due to a detected circular dependency. Job A has job B listed as upstream, but job B should actually be a few layers downstream of job A. Both jobs, and all jobs downstream and in-between, are blocked with no message. This would have been computed using historical fingerprints? Any way to sort this out? At the moment I just have to cancel them all and manually trigger the bottom one. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28616) Don't Email send to a somebody
Title: Message Title Alex Earl closed an issue as Fixed Please use the mailing list for questions. Jenkins / JENKINS-28616 Don't Email send to a somebody Change By: Alex Earl Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-28594) Leading underscore added to committers email address.
Title: Message Title Alex Earl commented on JENKINS-28594 Re: Leading underscore added to committers email address. You mean in TFS or in Jenkins? If you view one of the people, does the account have a valid email address specified? On a side note, I submitted a PR to fix the logging in the TFS plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-28594) Leading underscore added to committers email address.
Title: Message Title Alex Earl commented on JENKINS-28594 Re: Leading underscore added to committers email address. Adding a logger for hudson.tasks.MailAddressResolver would be interesting too. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-28594) Leading underscore added to committers email address.
Title: Message Title nir h commented on JENKINS-28594 Re: Leading underscore added to committers email address. I mean the user IDs on link you sent me (not sure if this means Jenkins or TFS). If I check the configuration for specific user, it shows the email with the "domain_" prefix. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [groovyaxis-plugin] (JENKINS-12762) Groovy script using command.execute() never finishes
Title: Message Title Noël Bardelot commented on JENKINS-12762 Re: Groovy script using command.execute() never finishes Still there in 1.580.1. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-28594) Leading underscore added to committers email address.
Title: Message Title Alex Earl commented on JENKINS-28594 Re: Leading underscore added to committers email address. If you delete the email for one of the users, it would help to see what is setting the email addresses to the domain_u...@foo.com (along with adding the logger for hudson.tasks.MailAddressResolver). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-28594) Leading underscore added to committers email address.
Title: Message Title nir h commented on JENKINS-28594 Re: Leading underscore added to committers email address. May 29, 2015 12:23:36 PM FINE hudson.tasks.MailAddressResolver Resolving e-mail address for "domain\user" ID=domain_user Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-28594) Leading underscore added to committers email address.
Title: Message Title nir h commented on JENKINS-28594 Re: Leading underscore added to committers email address. Deleted, all logs and behaviors remained the same. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [active-directory-plugin] (JENKINS-28594) Leading underscore added to committers email address.
Title: Message Title Alex Earl commented on JENKINS-28594 Re: Leading underscore added to committers email address. Can you delete the user itself from Jenkins? I'm trying to get the MailAddressResolver to get to this point: https://github.com/jenkinsci/mailer-plugin/blob/master/src/main/java/hudson/tasks/MailAddressResolver.java#L120 Which should tell which MailAddressResolver is resolving the address. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27523) External Default Pre-send Script
Title: Message Title Grzegorz Kotarski commented on JENKINS-27523 Re: External Default Pre-send Script Ahh, you're right, thanks! closing issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27523) External Default Pre-send Script
Title: Message Title Grzegorz Kotarski closed an issue as Not A Defect workaround Jenkins / JENKINS-27523 External Default Pre-send Script Change By: Grzegorz Kotarski Status: Reopened Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-28639) Configure docker node - No page found 'configure-entries.jelly' for class com.nirima.jenkins.plugins.docker.DockerComputer
Title: Message Title Kanstantsin Shautsou resolved as Incomplete 1) https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription 2) 0.9.0-rc1 is not latest build Jenkins / JENKINS-28639 Configure docker node - No page found 'configure-entries.jelly' for class com.nirima.jenkins.plugins.docker.DockerComputer Change By: Kanstantsin Shautsou Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mailer-plugin] (JENKINS-27262) email is not sent
Title: Message Title Ferry Huberts commented on JENKINS-27262 Re: email is not sent Guys, Please please fix this! I marked it critical for a reason. There really is no need to remove 'unresolved' entries: if mail can't be sent the the mail server administrator will get reports from the mail agent. This is truly killing our workflow. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-28640) Quotationmarks in commit message leads to merge failure
Title: Message Title Bue Petersen created an issue Jenkins / JENKINS-28640 Quotationmarks in commit message leads to merge failure Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 29/May/15 10:04 AM Environment: Pretested Integration Plugin 2.2.3 Windows Priority: Critical Reporter: Bue Petersen From a customer we got the following report about failed merge, due to quotation marks in the git commit message. Example (customer specific information removed) 07:28:45 [ready2master] $ git.exe pull origin master 07:28:51 Preparing to merge changes in commit 1b395e86024bf8f5d6cad09953d8c70f94987b98 to integration branch master 07:28:52 [PREINT] git.exe merge -m "Accumulated commit of the following from branch 'origin/ready/my-dev': 07:28:52 07:28:52 commit 1b395e86024bf8f5d6cad09953d8c70f94987b98 07:28:52 Author: Praqma Support 07:28:52 Date: on maj 13 07:26:39 2015 +0200 07:28:52 07:28:52 Changes scons varible test to "build=rel or test" 07:28:52 07:28:52 07:28:52 " 1b395e86024bf8f5d6cad09953d8c70f94987b98 --no-ff 07:28:52 [ready2master] $ git.exe merge -m 'Accumulated commit of the following from branch 'origin/ready/my-dev': 07:28:52 07:28:52 commit 1b395e86024bf8f5d6cad09953d8c70f94987b98 07:28:52 Aut
[JIRA] [mailer-plugin] (JENKINS-27262) email is not sent
Title: Message Title Alex Earl commented on JENKINS-27262 Re: email is not sent I don't know if there is currently a maintainer for the Mailer plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-28640) Quotationmarks in commit message leads to merge failure (Praqma case 13083)
Title: Message Title Bue Petersen updated an issue Jenkins / JENKINS-28640 Quotationmarks in commit message leads to merge failure (Praqma case 13083) Change By: Bue Petersen Summary: Quotationmarks in commit message leads to merge failure (Praqma case 13083) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-28640) Quotationmarks in commit message leads to merge failure (Praqma case 13083)
Title: Message Title Bue Petersen commented on JENKINS-28640 Re: Quotationmarks in commit message leads to merge failure (Praqma case 13083) Related to earlier reported problem, that was reproduced JENKINS-27662 . From the log and other information received, the following can be relevant for reproducing the problem: It is a Windows OS It seems to be running Danish language The merge fails, as it can't understand 'or' which comes from test to "build=rel or test" where the quotation just before build end the commit message given to merge. I suggest to extend the tests written for JENKINS-27662 . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-28640) Quotationmarks in commit message leads to merge failure (Praqma case 13083)
Title: Message Title Bue Petersen commented on JENKINS-28640 Re: Quotationmarks in commit message leads to merge failure (Praqma case 13083) Test repository for the test in JENKINS-27662 is generated like this: ... git commit -m "This is a commit message with double quotes (commit made on Windows), eg. \"test quotes\"." ... It might be the problem, the line should maybe have looked like this: ... git commit -m 'This is a commit message with double quotes (commit made on Windows), eg. "test quotes".' ... https://github.com/Praqma/pretested-integration-plugin/blob/master/src/test/resources/commitMessagesWithDoubleQuotes_windows.bat Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-28596) Hardcoded branch name when resolving commit messages (Praqma case 13073)
Title: Message Title Bue Petersen updated an issue Jenkins / JENKINS-28596 Hardcoded branch name when resolving commit messages (Praqma case 13073) Change By: Bue Petersen Environment: Pretested Integration Plugin 2.2.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mailer-plugin] (JENKINS-27262) email is not sent
Title: Message Title Ferry Huberts commented on JENKINS-27262 Re: email is not sent Well, someone can easily fix this, right? The offending commit was already identified. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-28596) Hardcoded branch name when resolving commit messages (Praqma case 13073)
Title: Message Title
Bue Petersen commented on JENKINS-28596
Re: Hardcoded branch name when resolving commit messages (Praqma case 13073)
Pretested Integration Plugin 2.2.3
which uses
org.jenkins-ci.plugins git 2.2.0
https://github.com/jenkinsci/pretested-integration-plugin/blob/pretested-integration-2.2.3/pom.xml
I do think actually the problem is in our code... as ObjectId to = repo.resolve("master"); is using a hard-coded name master, instead of the branch the user chose as integration branch in our plugin.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-28601) Order of job table reverse
Title: Message Title Oleg Nenashev edited a comment on JENKINS-28601 Re: Order of job table reverse I suppose it's a regression from after the fix of JENKINS-17290 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28601) Order of job table reverse
Title: Message Title Oleg Nenashev commented on JENKINS-28601 Re: Order of job table reverse I suppose it's a regression from JENKINS-17290 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mailer-plugin] (JENKINS-27262) email is not sent
Title: Message Title Alex Earl commented on JENKINS-27262 Re: email is not sent Which commit was identified? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title Oliver Gondža assigned an issue to Oliver Gondža Jenkins / JENKINS-27103 Include/Exclude options not shown in post-build selection list Change By: Oliver Gondža Assignee: vjuranek Oliver Gondža Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-28549) Random NPEs on jenkins start at GerritProjectList.addProject
Title: Message Title rsandell closed an issue as Won't Fix Code path removed in 2.14 in favour of other feature Jenkins / JENKINS-28549 Random NPEs on jenkins start at GerritProjectList.addProject Change By: rsandell Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-27741) Jenkins fails to report gerrit notifications spontaneously and on restart.
Title: Message Title rsandell commented on JENKINS-27741 Re: Jenkins fails to report gerrit notifications spontaneously and on restart. Will need fine level logs from com.sonymobile.tools.gerrit.gerritevents.workers.cmd and com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title Oliver Gondža commented on JENKINS-27103 Re: Include/Exclude options not shown in post-build selection list Broke somewhere between Jenkins 1.565 and 1.580. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-28593) Make gerrit comments configurable
Title: Message Title rsandell resolved as Won't Fix Works already Jenkins / JENKINS-28593 Make gerrit comments configurable Change By: rsandell Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-trigger-plugin] (JENKINS-28593) Make gerrit comments configurable
Title: Message Title rsandell commented on JENKINS-28593 Re: Make gerrit comments configurable You can provide a comment file in the workspace with any content you want. As well as provide other comments via the config. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title Oliver Gondža commented on JENKINS-27103 Re: Include/Exclude options not shown in post-build selection list I am able to reproduce that in Chromium, though not in firefox. Ioannis Moutsatsos, what was your browser? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [script-security-plugin] (JENKINS-25119) Sandbox cannot handle methods Groovy provides additionally
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25119 Re: Sandbox cannot handle methods Groovy provides additionally Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SandboxInterceptorTest.java http://jenkins-ci.org/commit/script-security-plugin/c6d43e762aa89ed0f13182059d219775708baa61 Log: Merge pull request #14 from jglick/ JENKINS-25119 -addendum JENKINS-25119 Cleaning up test from #7 Compare: https://github.com/jenkinsci/script-security-plugin/compare/6f16f00e0f19...c6d43e762aa8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [script-security-plugin] (JENKINS-28586) Method access/properties inside Closure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28586 Re: Method access/properties inside Closure Code changed in jenkins User: Jesse Glick Path: http://jenkins-ci.org/commit/script-security-plugin/b924d4af32075a720fda5c94af56255e81cd1830 Log: Merge branch 'master' into JENKINS-28586 Compare: https://github.com/jenkinsci/script-security-plugin/compare/521a7af4dc91...b924d4af3207 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-workflow-plugin] (JENKINS-28607) Demo to get plugin from UC
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28607 Re: Demo to get plugin from UC Code changed in jenkins User: Jesse Glick Path: .gitignore demo/Dockerfile_release demo/Dockerfile_snapshot demo/Makefile demo/docker-workflow-version.txt demo/get-snapshots.sh demo/plugins.txt demo/workflow-version.txt http://jenkins-ci.org/commit/docker-workflow-plugin/11529e37476f57505e74837a5c5f61529f2054e9 Log: Merge pull request #1 from jglick/Dockerfile_release- JENKINS-28607 JENKINS-28607 Getting released plugin versions from the update center Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/d11c0a76d528...11529e37476f Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-workflow-plugin] (JENKINS-28607) Demo to get plugin from UC
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28607 Demo to get plugin from UC Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-workflow-plugin] (JENKINS-28607) Demo to get plugin from UC
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28607 Re: Demo to get plugin from UC Code changed in jenkins User: Jesse Glick Path: .gitignore demo/Dockerfile_release demo/Dockerfile_snapshot demo/Makefile demo/docker-workflow-version.txt demo/get-snapshots.sh demo/plugins.txt demo/workflow-version.txt http://jenkins-ci.org/commit/docker-workflow-plugin/1beac603eea45e8f44479fe992b044ba862b277d Log: [FIXED JENKINS-28607] Getting released plugin versions from the update center. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title Oliver Gondža edited a comment on JENKINS-27103 Re: Include/Exclude options not shown in post-build selection list - I am able to reproduce that in Chromium, though not in firefox. [~ioannis], what was your browser? -The width was configured as 15% or the parent box. In different situations the label does not fix in whole, or as reported, no text was visible at all Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-27103 Include/Exclude options not shown in post-build selection list Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ws-cleanup-plugin] (JENKINS-27103) Include/Exclude options not shown in post-build selection list
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27103 Re: Include/Exclude options not shown in post-build selection list Code changed in jenkins User: Oliver Gondža Path: src/main/resources/hudson/plugins/ws_cleanup/Pattern/config.jelly http://jenkins-ci.org/commit/ws-cleanup-plugin/ca3971eb6b69608f231811ee089f9f241b5a4387 Log: [FIXED JENKINS-27103] Require minimal width for pattern labels Compare: https://github.com/jenkinsci/ws-cleanup-plugin/compare/4856854cd748...ca3971eb6b69 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ws-cleanup-plugin] (JENKINS-13553) Deleting project workspace Plugin: Jenkins hudson.Util.deleteFile Error
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-13553 Deleting project workspace Plugin: Jenkins hudson.Util.deleteFile Error Change By: Oliver Gondža Labels: Jenkins-Workspace-Cleanup-Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ws-cleanup-plugin] (JENKINS-25317) WS cleanup is not able to delete workspace containing non-ascii characters
Title: Message Title Oliver Gondža resolved as Cannot Reproduce No reply in 3 months, closing as it likely is a configuration error. Jenkins / JENKINS-25317 WS cleanup is not able to delete workspace containing non-ascii characters Change By: Oliver Gondža Status: Open Resolved Assignee: vjuranek Oliver Gondža Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.go
[JIRA] [ws-cleanup-plugin] (JENKINS-19274) Loading overlay remains on screen
Title: Message Title Oliver Gondža commented on JENKINS-19274 Re: Loading overlay remains on screen Can this be reproduced in modern Jenkins and latest plugin version? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ws-cleanup-plugin] (JENKINS-19717) Unable to remove Python virtual environment when specifying includes/excludes
Title: Message Title Oliver Gondža commented on JENKINS-19717 Re: Unable to remove Python virtual environment when specifying includes/excludes Can this be reproduced with recent plugin version? In this case the cause information is missing (null) because of a bug that is fixed already. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mesos-plugin] (JENKINS-28641) Allow for configuration of a custom command shell when using docker
Title: Message Title nickithewatt created an issue Jenkins / JENKINS-28641 Allow for configuration of a custom command shell when using docker Issue Type: Improvement Assignee: Vinod Kone Components: mesos-plugin Created: 29/May/15 1:16 PM Priority: Minor Reporter: nickithewatt By default, when using the docker configuration option, the approach used by mesos to run a docker based jenkins slave is by passing the jenkins slave commands as arguments to the standard shell e.g. ```/bin/sh -c java -jar ... ```. There may be cases (for example when wanting to run a docker-in-docker aka dind image) where a custom shell command is desired instead so that more than just the jenkins slave command can be executed. I.e. start docker then run the jenkins slave command. This has been highlighted in a google group chat as well. See https://groups.google.com/forum/#!topic/jenkins-mesos/JgFCmqOO7Fg It would be nice to be able to override this behaviour to make it possible. Add Comment
[JIRA] [mailer-plugin] (JENKINS-27262) email is not sent
Title: Message Title Ferry Huberts commented on JENKINS-27262 Re: email is not sent See https://github.com/jenkinsci/mailer-plugin/pull/20 Please release the plugin right after pulling this in Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Kevin Phillips commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Just a quick ping-back on this issue. Outstanding for like 4 years, no comments for months now, and all for a debilitating, crippling problem in the system! I did notice the pull request Daniel Webber created, which does seem to have some more recent activity on it but still no complete resolution to the issue even in the latest LTS release. Are there plans for finishing this work any time soon? We are still stuck on an LTS version from like a year or two ago because we can not accept this bug into our production environment. If there is any way to get this fix in sooner rather than later I know I'd appreciate it and I'm sure many others would as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Alexey Larsky updated an issue Jenkins / JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Change By: Alexey Larsky Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mesos-plugin] (JENKINS-28641) Allow for configuration of a custom command shell when using docker
Title: Message Title nickithewatt commented on JENKINS-28641 Re: Allow for configuration of a custom command shell when using docker Here is a PR which adds this functionality: https://github.com/jenkinsci/mesos-plugin/pull/112 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mesos-plugin] (JENKINS-28641) Allow for configuration of a custom command shell when using docker
Title: Message Title nickithewatt updated an issue Jenkins / JENKINS-28641 Allow for configuration of a custom command shell when using docker Change By: nickithewatt By default, when using the docker configuration option, the approach used by mesos to run a docker based jenkins slave is by passing the jenkins slave commands as arguments to the standard shell e.g. ``` /bin/sh -c java -jar ... ```. There may be cases (for example when wanting to run a docker-in-docker akadind image) where a custom shell command is desired instead so that more than just the jenkins slave command can be executed. I.e. start docker then run the jenkins slave command.This has been highlighted in a google group chat as well. See https://groups.google.com/forum/#!topic/jenkins-mesos/JgFCmqOO7FgIt would be nice to be able to override this behaviour to make it possible. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mesos-plugin] (JENKINS-28641) Allow for configuration of a custom command shell when using docker
Title: Message Title nickithewatt updated an issue Jenkins / JENKINS-28641 Allow for configuration of a custom command shell when using docker Change By: nickithewatt Labels: pull_request Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-25975) More reliable test infrastructure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25975 Re: More reliable test infrastructure Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/SingleJobTestBase.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowRunTest.java aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java support/src/test/java/org/jenkinsci/plugins/workflow/test/steps/WatchYourStep.java http://jenkins-ci.org/commit/workflow-plugin/d3ba64ddd6eaaacad401624d5b17809ebbec9b30 Log: [FIXED JENKINS-25975] Finally able to delete WatchYourStep; using SemaphoreStep instead. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-25975) More reliable test infrastructure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25975 Re: More reliable test infrastructure Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java durable-task-step/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java http://jenkins-ci.org/commit/workflow-plugin/27e5b23046ae4e913edff0fa05256fdfafff0029 Log: JENKINS-25975 Seem to have fixed a race condition whereby quick `sh` steps would sometimes not print all of their output. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-25975) More reliable test infrastructure
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-25975 More reliable test infrastructure Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Title: Message Title lacostej commented on JENKINS-24386 Re: Unity Test Tools package returns 2 or 3 for failed integration testing. Released as part of v1.0. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28642) Add Support to the New Workflow Plugin
Title: Message Title Flávio Augusto Valones created an issue Jenkins / JENKINS-28642 Add Support to the New Workflow Plugin Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: embeddable-build-status-plugin Created: 29/May/15 2:21 PM Environment: Jenkins 1.609 workflow-plugin 1.6 embeddable-build-status-plugin 1.7 Labels: workflow Priority: Major Reporter: Flávio Augusto Valones The new Job type added by the workflow-plugin cannot be casted to AbstractProject: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject at org.jenkinsci.plugins.badge.RunBadgeAction.(RunBadgeAction.java:18) at org.jenkinsci.plugins.badge.RunBadgeActionFactory.createFor(RunBadgeActionFactory.java:21) at hudson.model.Run.getTransientActions(Run.java:376)
[JIRA] [maven-plugin] (JENKINS-19844) Maven agent socket bind too inflexible (allow Jenkins in virtualized environment)
Title: Message Title Lucien Weller reopened an issue Jenkins / JENKINS-19844 Maven agent socket bind too inflexible (allow Jenkins in virtualized environment) Change By: Lucien Weller Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-19844) Maven agent socket bind too inflexible (allow Jenkins in virtualized environment)
Title: Message Title Lucien Weller resolved as Fixed Sorry reopened by mistake... Jenkins / JENKINS-19844 Maven agent socket bind too inflexible (allow Jenkins in virtualized environment) Change By: Lucien Weller Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-19844) Maven agent socket bind too inflexible (allow Jenkins in virtualized environment)
Title: Message Title Lucien Weller edited a comment on JENKINS-19844 Re: Maven agent socket bind too inflexible (allow Jenkins in virtualized environment) Sorry reopened by mistake... But @Roberto Andrade: you're pull request seams not to be fully ok. Can you fix it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-19844) Maven agent socket bind too inflexible (allow Jenkins in virtualized environment)
Title: Message Title Lucien Weller edited a comment on JENKINS-19844 Re: Maven agent socket bind too inflexible (allow Jenkins in virtualized environment) Sorry reopened by mistake... But @Roberto Andrade: you're pull request seams not to be fully ok. Can you fix it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-28498) Null Pointer when publishing assets and server is down
Title: Message Title Paul Allen closed an issue as Fixed Resolved in 1.2.3 Jenkins / JENKINS-28498 Null Pointer when publishing assets and server is down Change By: Paul Allen Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-28450) Publish Assets submit files even if build steps marked as failure
Title: Message Title Paul Allen commented on JENKINS-28450 Re: Publish Assets submit files even if build steps marked as failure On the PostBuild step for Tagging/Labeling I have a 'Only tag on build success' check box. Perhaps the same would work for Publish? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Kevin Phillips commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed @steve carter First, let me thank you for summarizing the earlier comment threads. That does help bring everything into focus. 4) Jenkins, in order to catch rogue processes at job end (i.e. those that have broken ties with their parent process) scans the whole process space for those with the particular BUILD_ID in their environment, and kills them. This is correct and good behavior by Jenkins. Agreed. This is a perfectly valid and useful enhancement for the majority of cases. However, given the debilitating effect it has on this specific use case combined with the fact that the change was included on an LTS release which is expected to be kept as stable as possible is where I take issue. I see this problem as a bug, albeit a difficult to detect bug and admittedly a bug that is really caused by some questionable behavior provided by the Microsoft build tools, but a bug none the less. In that case critical, production halt kind of bugs like this should be fixed immediately or reverted until an appropriate fix can be made. Doing otherwise reduces users' confidence in the stability of the tool. There is a reason shops like ours choose to use LTS editions for production work - to avoid problems like this that may be found on the latest, cutting edge versions. 8) Solution 1: start pdbsrv with a BUILD_ID that doesn't match the build jobs. Then pdbsrv will not be killed at the end of the job. This should be called a workaround or hack rather than a solution. That point aside, this workaround again won't work for our particular build environment. We use the BUILD_ID throughout our build processes to embed metadata in the binary files we generate. If we reset that environment variable as part of our build this metadata will essentially get corrupted. Changing our tooling to use an alternative environment variable would require significant effort as well, having to be propagated out to dozens of products across several release branches each. 9) Solution 2: use Daniel's whitelist feature to not kill pdbsrv at the end of the job. Based on my review of his pull request, Daniel's feature has not yet been completed nor has it been included in any actual LTS release. I do believe this would be a reasonable and appropriate solution to this defect though, so hopefully this work can be completed sooner rather than later. 10) The problem with Solutions 1 and 2 are this: pdbsrv still has a timeout, so you will get sporadic failures when the server goes away. I know some earlier posters did indicate that this was an issue for them I have not been able to reproduce the problem as described. When a compile begins and this process is running it makes use of the existing process, and if the process is not already running it starts it. I have never had a compile running and seen the mspdbsrv process terminate mid-compile without any other background process or system event occurring. Also, I work with many development teams including many dozens of developers
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Kevin Phillips commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed PS: Sorry for the rant. My team and I have been aggravated for some time now, hoping this bug would be fixed so we can move off the old version of Jenkins we're currently stuck on and thus able to pick up some new bug fixes both in the core as well as in numerous plugins which only support newer versions. Hopefully I don't come across as overly adversarial. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-28448) "Publish Assets delete files when no shelve is used for review
Title: Message Title Paul Allen commented on JENKINS-28448 Re: "Publish Assets delete files when no shelve is used for review If the files are in the 'have' list metadata for the workspace being used to do the Publish, but not physically present, then the reconcile command will mark the files for delete. I guess this could happen if: the Workspace root was incorrectly set, a cleanup had removed all the workspace's files, or the Publish step happened on a different slave to the build. To prevent these kind of accidents, perhaps I should disable 'delete' actions in Publish. I think 99% of most uses-cases are add or edit operations. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Alexey Larsky updated an issue Jenkins / JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Change By: Alexey Larsky Environment: Windows XP, Windows 7 using MSBuild or devenv.exe to build MS Visual Studio Projects Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-26486) Workspace fails to update when Replace missing/modified files is checked
Title: Message Title Paul Allen commented on JENKINS-26486 Re: Workspace fails to update when Replace missing/modified files is checked The latest release uses the 2014.1 p4 clean feature (reconcile -w). It might resolve this for users on 2014.1 or above, but I will leave this issue open as it still needs fixing for older versions. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-25468) Add a "Verbosity" option to allow detailed p4 info
Title: Message Title Paul Allen closed an issue as Fixed Added even more logging in release 1.2.3. Jenkins / JENKINS-25468 Add a "Verbosity" option to allow detailed p4 info Change By: Paul Allen Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cloudfoundry-plugin] (JENKINS-28602) Error: Default domain calculated from "api" domain
Title: Message Title Andreas Buchen commented on JENKINS-28602 Re: Error: Default domain calculated from "api" domain > a little refactoring [...] so I'll work on that Cool. I quickly glanced at the code, but I believe you are much better placed to refactor it as you see fit Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title
Andreas Buchen commented on JENKINS-28311
Re: Create CloudFoundry services via Plug-in
"Create services if they don't exist" under that, so it's available for either services in manifest files or services in the Jenkins config.
Not sure if this sufficient. At least to my knowledge, the manifest only contains the service instance name. But you would need service name ("postgress") and plan ("free") to actually be able to create it. I guess those additional parameters one would have to provide to the Jenkins plug-in?!?
One cloud also also think along the lines of having another "post build action" besides "deploy to CF". For example, create (and drop and create) service instance.
Thanks for the great work. The plug-in is being used daily
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [buildresult-trigger-plugin] (JENKINS-25753) BuildResultTrigger doesn't trigger build
Title: Message Title Alexandru Gheorghe commented on JENKINS-25753 Re: BuildResultTrigger doesn't trigger build Same with H 17 * * 5, the upstream job (makes the upstream/downstream automatically when i try to monitor a job) has its state as SUCCESS however after poll it says "No changes" and just stays like that. It should trigger upon "SUCCESS" and my option to "Combine all job info" is disabled. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [buildresult-trigger-plugin] (JENKINS-25753) BuildResultTrigger doesn't trigger build
Title: Message Title Alexandru Gheorghe updated an issue Jenkins / JENKINS-25753 BuildResultTrigger doesn't trigger build Change By: Alexandru Gheorghe Component/s: buildresulttrigger Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [hp-application-automation-tools-plugin] (JENKINS-28609) Could not create scheduler, please verify ALM client installation
Title: Message Title Tyler Hoffman closed an issue as Fixed Issue seems to have been related to HP Client Registration add-in not being properly installed Jenkins / JENKINS-28609 Could not create scheduler, please verify ALM client installation Change By: Tyler Hoffman Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [logstash-plugin] (JENKINS-28546) logstash doesn't connect to a server and puts no messages out
Title: Message Title Rinaldo DiGiorgio commented on JENKINS-28546 Re: logstash doesn't connect to a server and puts no messages out Can I get any details on what the expectations are for using the plugin. The directions imply it just works. I have a new elasticsearch instance and I try to connect and nothing happens. I have downloaded the source and will start to look at it. Does the index need to exist? Many river plugins in elasticsearch just create the index does this plugin do that? I am leaving the username and the password blank will this cause the failure. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Lars Rosenboom edited a comment on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Maybe there is a way to shut down the mspdbsrv.exe softly, so it stops only after all active request (by msbuild.exe or devenv.exe in parallel builds) are done. Then it should simply restart on the next request.Another solution would be to allow the user to give a list of process names not to kill (or maybe hardcode not to kill mspdbsrv.exe). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Lars Rosenboom commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Maybe there is a way to shut down the mspdbsrv.exe softly, so it stops only after all active request (by msbuild.exe or devenv.exe in parallel builds) are done. Then it should simply restart on the next request. Another solution would be to allow the user to give a list of process names not to kill (or maybe hardcode not to kill mspdbsrv.exe). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Gavin Swanson commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Stopping after a timeout period after all active requests and continuing to run when it gets a new request are the way mspdbsrv runs normally when something doesn't go around killing it (ala Jenkins). I believe the correct solution is a whitelist. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-traceability-plugin] (JENKINS-28643) timestamps in the UI are not correct
Title: Message Title James Nord created an issue Jenkins / JENKINS-28643 timestamps in the UI are not correct Issue Type: Bug Assignee: Oleg Nenashev Attachments: dt_screenshot.png Components: docker-traceability-plugin Created: 29/May/15 4:41 PM Priority: Minor Reporter: James Nord see screenshot from submission of events via Docker events hook. Add Comment
[JIRA] [s3-plugin] (JENKINS-26297) S3 download link incorrect when Destination bucket includes a path prefix
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26297 Re: S3 download link incorrect when Destination bucket includes a path prefix Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/s3/S3Profile.java src/main/java/hudson/plugins/s3/callable/S3UploadCallable.java http://jenkins-ci.org/commit/s3-plugin/ab3afa1be121fd90693b23f353e915ec552da98c Log: Merge pull request #58 from ndeloof/JENKINS-26297 use the user bucketname entry that includes prefixes in fingerprint Compare: https://github.com/jenkinsci/s3-plugin/compare/c6308fef7279...ab3afa1be121 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Title: Message Title Mark McNeely commented on JENKINS-24386 Re: Unity Test Tools package returns 2 or 3 for failed integration testing. Hey Lacostej, I can help you test it if you still need it. For some reason the site was inaccessible yesterday so I couldn't respond. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman Labels: core plugins update Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman Just switched from Jenkins 1.611 to 1.614. Jenkins 1.615 has the same issueJenkins Plugin Manager, in "Updates" tab I have selected all 3 plugins to update and started the update by clickning clicking "Download now and install after restart" (see picture !Plugin1.png|thumbnail!), but update did not performed!I came back to the Plugin Manager. Selected the same plugins and started the update (see picture !Plugin2.png|thumbnail!). The same plugins appeared with status pending twice and still now any activity! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28633) Plugin update does not work any more
Title: Message Title Grigoriy Milman updated an issue Jenkins / JENKINS-28633 Plugin update does not work any more Change By: Grigoriy Milman Labels: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28110) 1.610 “Failed to instantiate” error
Title: Message Title
Irina Vinokurova reopened an issue
Sorry but i have the same problem in Jenkins v. 1.611
Stacktrace:
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.performance.PerformancePublisher from {"parsers":{"glob":"result.xml","kind":"hudson.plugins.performance.JMeterParser$DescriptorImpl"},"modeOfThreshold":"false","errorUnstableThreshold":"0","errorFailedThreshold":"0","errorUnstableResponseTimeThreshold":"","relativeUnstableThresholdNegative":"0.0","relativeUnstableThresholdPositive":"0.0","relativeFailedThresholdNegative":"0.0","relativeFailedThresholdPositive":"0.0","compareBuildPrevious":"true","nthBuildNumber":"0","comparisonType":"ART","modePerformancePerTestCase":true,"modeThroughput":true,"stapler-class":"hudson.plugins.performance.PerformancePublisher","$class":"hudson.plugins.performance.PerformancePublisher"}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.
[JIRA] [core] (JENKINS-28110) 1.610 “Failed to instantiate” error
Title: Message Title Johannes Schüth commented on JENKINS-28110 Re: 1.610 “Failed to instantiate” error @kefirkin Yes, 1.611 was also affected. Please update to a newer version. Afaik the earliest version that contains the fix is 1.612 https://github.com/jenkinsci/jenkins/commit/1f41bec8ef656da014b7145fdff82563c030ca29 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28110) 1.610 “Failed to instantiate” error
Title: Message Title Irina Vinokurova commented on JENKINS-28110 Re: 1.610 “Failed to instantiate” error Thank's a lot! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-client-plugin] (JENKINS-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Title: Message Title Daren Smith commented on JENKINS-26757 Re: "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs Seeing a similar issue sporadically using GIT plugin 2.3.5, GIT client plugin 1.17.1, and Jenkins 1.607 with Stash. Re-queuing the build has resolved the issue each time, but we were not seeing it when running 1.574 and earlier plugins prior to upgrading. I will review the logs and add any detail that I can find associated with the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [hp-application-automation-tools-plugin] (JENKINS-25477) Unable to connect to ALM 12.01
Title: Message Title Winston Polhamus updated an issue Jenkins / JENKINS-25477 Unable to connect to ALM 12.01 Change By: Winston Polhamus Priority: Major Trivial Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [hp-application-automation-tools-plugin] (JENKINS-25477) Unable to connect to ALM 12.01
Title: Message Title Winston Polhamus commented on JENKINS-25477 Re: Unable to connect to ALM 12.01 We are now integrating via the Perf. Center API, so this is no longer an issue for us. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-client-plugin] (JENKINS-26757) "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs
Title: Message Title Mark Waite commented on JENKINS-26757 Re: "Error cloning remote repo 'origin'" with username:passw...@bitbucket.org URLs Daren Smith as far as I can tell from my experiments and the description from Flavio Donzé and the duplicate bug JENKINS-24368, no amount of retries will allow an https based URL with embedded username and password to work with a private bitbucket (or Stash) repository. While your failure may have similar symptoms (failure cloning the repo), I believe it is a different bug, or it is a configuration issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Title: Message Title lacostej commented on JENKINS-24386 Re: Unity Test Tools package returns 2 or 3 for failed integration testing. Hei Mark, thanks for the help! I've added integration tests so it should go reasonably well, but some user feedback from those who requested the feature might help! v1.0 was released with the feature. The plugins update site hasn't picked it up yet I think, but you can fetch it from here: http://updates.jenkins-ci.org/download/plugins/unity3d-plugin/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-28644) Trigger job when polling off if sha1 specified in push notification
Title: Message Title Leif Gruenwoldt created an issue Jenkins / JENKINS-28644 Trigger job when polling off if sha1 specified in push notification Issue Type: Improvement Assignee: Nicolas De Loof Components: git-plugin Created: 29/May/15 6:07 PM Priority: Minor Reporter: Leif Gruenwoldt The documentation suggests that polling is not required when the "sha1" commitID param is given, so should it not be possible to trigger a build this way with polling turned off for the job? From testing it appears polling is still required in this case too. "Commit ID is optional. If set, it will immediately trigger a build, without requirement to poll for changes." I have > 100 Jenkins jobs I'd like to migrate to this style post-receive job trigger however having to modify the job configuration in this way for eachone sounds like a very long afternoon. Add Comment
