[JIRA] [jacoco] (JENKINS-23426) Crash publishing jacoco report across all projects with 1.0.15
centic resolved JENKINS-23426 as Fixed Crash publishing jacoco report across all projects with 1.0.15 It seems if some other plugin already pulls in newer asm, it worked, only if no other plugin uses asm, then this can show up. We now updated the dependency on asm to 5.0.1 and also updated the dependency from org.kohsuke.asm4 to asm5, version 1.0.16 will contain this fix. Change By: centic (24/Jun/14 6:45 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Sending emails
Failed builds will by default have changelist in the email. Regards, Vishal On Mon, Jun 23, 2014 at 9:02 PM, merlin wrote: > Hi > > I want to send an email where it contains the changes made in the code with > the developer's name and time at which code was committed. Is this > possible? > > thank you > > > > -- > View this message in context: > http://jenkins-ci.361315.n4.nabble.com/Sending-emails-tp4707540.html > Sent from the Jenkins issues mailing list archive at Nabble.com. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Issues" group. > To unsubscribe from this 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. > -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jacoco] (JENKINS-23426) Crash publishing jacoco report across all projects with 1.0.15
centic assigned JENKINS-23426 to centic Crash publishing jacoco report across all projects with 1.0.15 Change By: centic (24/Jun/14 6:40 AM) Assignee: Ognjen Bubalo centic 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] (JENKINS-22843) Show test result in task if any
Tommy Tynjä updated JENKINS-22843 Show test result in task if any It would also be nice to be able to hover over the task to get a more descriptive text. See proposed hover text in the attached screenshot. Change By: Tommy Tynjä (24/Jun/14 6:31 AM) Attachment: hover_test_step.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jens Brejner commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Hi Jonathan. I am not sure it is related to the component component. Please post the complete, failing build log and the configuration of the project (config.xml). BR Jens 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] [component] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jens Brejner updated JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Change By: Jens Brejner (24/Jun/14 6:21 AM) Summary: (our case 11519) Post build step not run and difficult to know why 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] (JENKINS-23537) Trigger button is not rendered correctly on Firefox
Tommy Tynjä
commented on JENKINS-23537
Trigger button is not rendered correctly on Firefox
I suggest a more intuitive text to fall back on if the button cannot be rendered. It is not obvious that the current text ("Manual!") is a link placeholder. I would appreciate something like "Trigger manually" instead. The text doesn't need to be in bold either, I think it would make more sense to have it underlined.
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] [plugin] (JENKINS-4960) Provide a SCMCheckoutStrategy to checkout only once for all matrix entries
Oleg Nenashev updated JENKINS-4960 Provide a SCMCheckoutStrategy to checkout only once for all matrix entries Change By: Oleg Nenashev (24/Jun/14 5:18 AM) Status: Reopened Open 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] [plugin] (JENKINS-4960) Provide a SCMCheckoutStrategy to checkout only once for all matrix entries
Oleg Nenashev assigned JENKINS-4960 to Unassigned Provide a SCMCheckoutStrategy to checkout only once for all matrix entries Change By: Oleg Nenashev (24/Jun/14 5:19 AM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-4960) Provide a SCMCheckoutStrategy to checkout only once for all matrix entries
Oleg Nenashev updated JENKINS-4960 Provide a SCMCheckoutStrategy to checkout only once for all matrix entries Change By: Oleg Nenashev (24/Jun/14 5:19 AM) Component/s: plugin Component/s: matrix 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-12660) Fail to start the windows service when trying to launch slave node
Oleg Nenashev updated JENKINS-12660 Fail to start the windows service when trying to launch slave node Change By: Oleg Nenashev (24/Jun/14 5:17 AM) URL: https://github.com/kohsuke/winsw/issues/45 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-12660) Fail to start the windows service when trying to launch slave node
Oleg Nenashev assigned JENKINS-12660 to Oleg Nenashev Fail to start the windows service when trying to launch slave node Change By: Oleg Nenashev (24/Jun/14 5:14 AM) Assignee: Kohsuke Kawaguchi Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12660) Fail to start the windows service when trying to launch slave node
Oleg Nenashev commented on JENKINS-12660 Fail to start the windows service when trying to launch slave node Its is mostly a documentation bug. WinSW should explicitly mention that user name should be specified along with its domain 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-12660) Fail to start the windows service when trying to launch slave node
Oleg Nenashev updated JENKINS-12660 Fail to start the windows service when trying to launch slave node Change By: Oleg Nenashev (24/Jun/14 5:12 AM) Labels: winsw Component/s: core 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] (JENKINS-23528) Unable to select credentials when using git as Source Code Management
Oleg Nenashev commented on JENKINS-23528 Unable to select credentials when using git as Source Code Management Please provide the system info. See https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking#IssueTracking-Whattoputinthedescriptionofanissuereport%3F 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-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Oleg Nenashev commented on JENKINS-23281 Jenkins.getUser(...) is debilitatingly slow with a large number of users In addition, User.getAll() seems to be unsafe against multiple caller threads. 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-23281) Jenkins.getUser(...) is debilitatingly slow with a large number of users
Oleg Nenashev commented on JENKINS-23281 Jenkins.getUser(...) is debilitatingly slow with a large number of users Does User.getAll() really need to reload every user's config.xml every 10 seconds? No idea why Jenkins performs such loading, but it's a legacy behavior, hence we cannot just remove it. I propose to add a switch variable, which will make Jenkins to load users on the startup only. 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-23455) Deadlock during startup
Oleg Nenashev resolved JENKINS-23455 as Duplicate Deadlock during startup Change By: Oleg Nenashev (24/Jun/14 4:37 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23481) Master computer is not notified using ComputerListener
Oleg Nenashev started work on JENKINS-23481 Master computer is not notified using ComputerListener Change By: Oleg Nenashev (24/Jun/14 4:33 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Sending emails
Hi I want to send an email where it contains the changes made in the code with the developer's name and time at which code was committed. Is this possible? thank you -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Sending-emails-tp4707540.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [hockeyapp] (JENKINS-23549) HockeyApp Plugin : ArrayIndexOutOfBoundsException
yasu yana created JENKINS-23549 HockeyApp Plugin : ArrayIndexOutOfBoundsException Issue Type: Bug Assignee: Unassigned Components: hockeyapp Created: 24/Jun/14 2:59 AM Description: When ipa file not found, it cause ArrayIndexOutOfBoundsException. Uploading to HockeyApp... java.lang.ArrayIndexOutOfBoundsException: 0 at hockeyapp.HockeyappRecorder.perform(HockeyappRecorder.java:321) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1695) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Environment: HockeyApp Plugin version1.1.0 Project: Jenkins Priority: Minor Reporter: yasu yana 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] [ssh-credentials] (JENKINS-23511) InvalidClassException for SSHAuthenticator$1 when doing a git clone on an AIX slave
Robert Clark updated JENKINS-23511 InvalidClassException for SSHAuthenticator$1 when doing a git clone on an AIX slave I've been able to correct this with a local build of the SSH credentials plugin, so I've removed the "git" component. A pull request with the fix is available from https://github.com/jenkinsci/ssh-credentials-plugin/pull/6 Change By: Robert Clark (24/Jun/14 1:17 AM) Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-20850) when using default workspace "default" folder is also copied
ikedam commented on JENKINS-20850 when using default workspace "default" folder is also copied It sounds that you specified "Target directory". It can be empty. 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] [copyartifact] (JENKINS-17880) Not all files are copied.
ikedam resolved JENKINS-17880 as Duplicate Not all files are copied. Duplicates JENKINS-14900 Change By: ikedam (24/Jun/14 12:31 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-17880) Not all files are copied.
ikedam assigned JENKINS-17880 to ikedam Not all files are copied. Change By: ikedam (24/Jun/14 12:30 AM) 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] [ant] (JENKINS-15886) parameterized builds start default ant target in Ant-Task
ikedam updated JENKINS-15886 parameterized builds start default ant target in Ant-Task This is a parameter escaping issue of ant-plugin, and should be fixed in ant-plugin (or might be Jenkins core, I'm not sure how ant-plugin launches native processes). Change By: ikedam (24/Jun/14 12:19 AM) Component/s: copyartifact 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] [valgrind] (JENKINS-16999) No delete button to remove valgrind report publisher
Mohamed Galal El-Din updated JENKINS-16999 No delete button to remove valgrind report publisher The delete button exist in my version. Change By: Mohamed Galal El-Din (23/Jun/14 11:53 PM) Attachment: jenkins.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-16999) No delete button to remove valgrind report publisher
Mohamed Galal El-Din commented on JENKINS-16999 No delete button to remove valgrind report publisher I have the delete button on my instance, below are my versions Jenkins version 1.567 Valgrind plug-in version 0.20 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] (JENKINS-14656) Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually
ikedam resolved JENKINS-14656 as Fixed Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually Looks fixed in https://github.com/jenkinsci/build-pipeline-plugin/pull/8 , build-pipeline-1.4. Change By: ikedam (23/Jun/14 11:49 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-12410) Downstream jobs not associated with upstream parent job properly
ikedam commented on JENKINS-12410 Downstream jobs not associated with upstream parent job properly @kbeal I cannot get what you say at all. What is VM? I cannot get how a virtual machine relates to this problem. What is +1? Which job reported NPE? 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] [ssh-slaves] (JENKINS-15804) Possibility to set shell per node
Chris Thalinger commented on JENKINS-15804 Possibility to set shell per node Well, the shell is used if your build task is using a "Execute shell" build step. In that case the global shell configuration is picked up. In a heterogeneous build farm including Unix and Windows systems this won't work. 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] [active-directory] (JENKINS-23548) Grow Up Usa - Obat Peninggi Badan
obat perangsangg assigned JENKINS-23548 to 123qwe 123qwe Grow Up Usa - Obat Peninggi Badan Change By: obat perangsangg (23/Jun/14 10:56 PM) Assignee: obat perangsangg 123qwe 123qwe 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] [active-directory] (JENKINS-23548) Grow Up Usa - Obat Peninggi Badan
obat perangsangg resolved JENKINS-23548 as Not A Defect Grow Up Usa - Obat Peninggi Badan Change By: obat perangsangg (23/Jun/14 10:50 PM) Status: Open Resolved Assignee: obat perangsangg Fix Version/s: current Resolution: Not A Defect 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] [active-directory] (JENKINS-23548) Grow Up Usa - Obat Peninggi Badan
obat perangsangg updated JENKINS-23548 Grow Up Usa - Obat Peninggi Badan Change By: obat perangsangg (23/Jun/14 10:51 PM) Labels: badan grow obat peninggi up usa 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] [active-directory] (JENKINS-23548) Grow Up Usa - Obat Peninggi Badan
obat perangsangg created JENKINS-23548 Grow Up Usa - Obat Peninggi Badan Issue Type: Task Affects Versions: current Assignee: Unassigned Components: active-directory Created: 23/Jun/14 10:49 PM Description: Grow Up Usa adalah Obat Peninggi Badan yang sangat ampuh dalam memproses pertumbuhan Badan anda. http://www.pelangsingbadan.info/grow-up-usa/ Project: Jenkins Priority: Major Reporter: obat perangsangg 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] [testInProgress] (JENKINS-23547) Obat Perangsang Pria Wanita Murah
obat perangsangg resolved JENKINS-23547 as Not A Defect Obat Perangsang Pria Wanita Murah please approved Change By: obat perangsangg (23/Jun/14 10:42 PM) Status: In Progress Resolved Fix Version/s: current Resolution: Not A Defect 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] [testInProgress] (JENKINS-23547) Obat Perangsang Pria Wanita Murah
obat perangsangg started work on JENKINS-23547 Obat Perangsang Pria Wanita Murah Change By: obat perangsangg (23/Jun/14 10:39 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testInProgress] (JENKINS-23547) Obat Perangsang Pria Wanita Murah
obat perangsangg created JENKINS-23547 Obat Perangsang Pria Wanita Murah Issue Type: Task Affects Versions: current Assignee: cchabanois Components: testInProgress Created: 23/Jun/14 10:35 PM Description: Obat Perangsang Pria Wanita Kini Bisa Anda dapatkan di Toko Online ObatPerangsangPria.com Project: Jenkins Priority: Major Reporter: obat perangsangg 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] [clearcase] (JENKINS-23546) history command which get changes is wrong
George Kinlay created JENKINS-23546 history command which get changes is wrong Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Components: clearcase Created: 23/Jun/14 10:07 PM Description: The command used to calculate change set is clear-case plug-in is wrong it gets entire history from all the vobs rather it should get only from directories listed in load rules this is wrong cleartool lshistory -all -since this is right (remove "-all") cleartool lshistory -since Project: Jenkins Priority: Major Reporter: George Kinlay 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] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Jason Miller
commented on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
I don't think this is fixed, or else there's been a regression (Jenkins 1.565).
If I have a simple build that uses a BRANCH parameter that defaults to 'master', it will always trigger when notified to look for changes by Stash (via the /git/notifyCommit api), even if there's no changes.
Git polling log looks like this:
Started on Jun 23, 2014 2:01:35 PM
Using strategy: Default
[poll] Last Built Revision: Revision f22fe57691485df88098480c2e56c4e51a68ad67 (origin/master)
using GIT_SSH to set credentials
> git ls-remote -h ssh://g...@stash.domain.com/project/repository.git ${BRANCH}
Done. Took 0.45 sec
Changes found
We're not using wildcards, it's just a simple string parameter with a default setting.
Versions:
Jenkins 1.565
Git client plugin 1.9.1
Git plugin 2.2.1
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22677) Allow Post-Steps to run on failed/unstable builds
sebastian_dietrich commented on JENKINS-22677 Allow Post-Steps to run on failed/unstable builds In Jenkins when defining a build, one can define post-build-steps. This is done in /configure, the section is called "Post Steps". There one can select the following options: Run only if build succeeds Run only if build succeeds or is unstable Run regardless of build result I'd like to run a post step, when the build does not succeed. In my specific case I want to run a maven build with "mvn test" and only upon failure a build with "mvn clean test". That is why I need a 4th option * Run only if build is unstable 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] [warnings] (JENKINS-23499) warnings enforces serial execution of concurrent build
Roland Schulz commented on JENKINS-23499 warnings enforces serial execution of concurrent build Sorry. I didn't realize that "compute new warnings" is causing 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] [sbt] (JENKINS-23545) Linux master, windows slave causes the sbt plugin to create an incorrect path to java
Mike Chmielewski created JENKINS-23545 Linux master, windows slave causes the sbt plugin to create an incorrect path to java Issue Type: Bug Assignee: uzilan Components: sbt Created: 23/Jun/14 9:09 PM Description: I have a build job that runs on the windows build slave. I am using the built-in Jenkins JDK installer to install a local 1.7 JDK on the slave. This succeeds. However, when sbt tries to run, it errors out because it incorrectly constructs the path to the java executable: cmd.exe /C /c:\h2_tritium_ui\tools\hudson.model.JDK\Latest_1.7/bin/java -Dsbt.log.noformat=true -jar c:\manually_installed_tools\sbt\bin\sbt-launch.jar test Note the leading forward slash. I figure it is assuming a linux box. Environment: CentOS 6.4 master, Windows 7 slave Project: Jenkins Priority: Major Reporter: Mike Chmielewski 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] (JENKINS-23532) Manual trigger execution causes TriggerException
Tommy Tynjä commented on JENKINS-23532 Manual trigger execution causes TriggerException Added a more descriptive error message, which suggests removing the folder prefix if present, since this is not handled properly by the Build Pipeline Plugin: https://github.com/Diabol/delivery-pipeline-plugin/pull/71 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] (JENKINS-23532) Manual trigger execution causes TriggerException
Tommy Tynjä started work on JENKINS-23532 Manual trigger execution causes TriggerException Change By: Tommy Tynjä (23/Jun/14 8:59 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter] (JENKINS-21337) Add support for cloudbees-folders
Magnus Sandberg started work on JENKINS-21337 Add support for cloudbees-folders Change By: Magnus Sandberg (23/Jun/14 7:35 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter] (JENKINS-21356) Add support for using JobProperty to join a Job to a JobGroup
Magnus Sandberg started work on JENKINS-21356 Add support for using JobProperty to join a Job to a JobGroup Change By: Magnus Sandberg (23/Jun/14 7:35 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter] (JENKINS-23538) Remove support for Legacy Sorter
Magnus Sandberg started work on JENKINS-23538 Remove support for Legacy Sorter Change By: Magnus Sandberg (23/Jun/14 7:34 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-23544) Jacoco-plugin fails to compile when depending on newer jenkins builds.
Scott Greene created JENKINS-23544 Jacoco-plugin fails to compile when depending on newer jenkins builds. Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 23/Jun/14 7:26 PM Description: The plugin fails to build due to many test failures. There is two main failures: 1) Classes extending HudsonTestCase which was deprecated and succeeded by JenkinsRule are throwing a MojoNotFoundException. These classes likely just need to change to using the JenkinsRule API. 2) JaCoCoColumnTest has multiple NullPointerExceptions (on 1.554.2). This appears to be as more complex issue relating to changes in the test-harness APIs as the exception is occurring in the Job class because there appears to be no Jenkins 'instance' running. This exception changes to an IllegalStateException in AbstractItem on Git master as extra null safeties were added. Environment: Apache Maven 3.2.1 Java version: 1.6.0_65, vendor: Apple Inc. Jenkins 1.554.2 and Git master as of commit 1aec030e0811e9046d2f57395dac98872de715fa Project: Jenkins Priority: Minor Reporter: Scott Greene 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] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Mike Kobler commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted David, You might try upgrading the slaves with the new slave.jar that comes with 1.568. (I was running 1.561 and seeing the issue, but only with a newer version of the slave.jar. Slaves running an older version did not show the issue). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-12410) Downstream jobs not associated with upstream parent job properly
Ken Beal reopened JENKINS-12410 Downstream jobs not associated with upstream parent job properly We are experiencing this. We have a job flow like Detect -> Monitor -> Deploy -> Test1 -> Test2 -> Test3 -> Upload -> Report -> Delete. Not all the VMs we deploy are being deleted. Upon investigation, when I looked at the Delete job at the top of its console output, it shows the chain of jobs that ran. However, when I then looked at "Deploy+1", it ran "Test1+1", but looking in that job's console output, it shows it ran Test2 – not "Test2+1"! We are using the Parameterized Trigger Plugin (latest version, 2.25), as well as Email-Ext (latest version, 2.38.1). Change By: Ken Beal (23/Jun/14 6:35 PM) Resolution: Fixed Status: Resolved Reopened 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 Roy created JENKINS-23543 Launchctl does not load Jenkins on OS X 10.10 Yosemite Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 23/Jun/14 6:01 PM Description: After upgrading to OS X 10.10 Yosemite on my development machine, the Jenkins launchctl plists do not load the Jenkins executable properly. I can start the application manually via command line, but when the application is started via launchctl, console reports: 2014-06-23 1:59:27.341 PM com.apple.xpc.launchd[1]: (jenkins[2498]) Service could not initialize: 14A261i: xpcproxy + 13932 [1334][CD35772A-D98C-3BCA-B180-FA143320A63E]: 0xd 2014-06-23 1:59:27.344 PM com.apple.xpc.launchd[1]: (jenkins) Service only ran for 0 seconds. Pushing respawn out by 10 seconds. This repeats indefinitely until the launchctl script is unloaded. I have tried to reinstall Jenkins but this does not correct the problem. System specs: Model Name: MacBook Pro Model Identifier: MacBookPro10,1 Processor Name: Intel Core i7 Processor Speed: 2.7 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 6 MB Memory: 16 GB Environment: OS X 10.10 Yosemite Project: Jenkins Priority: Major Reporter: Daniel Roy 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] [sbt] (JENKINS-23542) Add license info to sbt plugin
Matthew Fulgo created JENKINS-23542 Add license info to sbt plugin Issue Type: Task Assignee: uzilan Components: sbt Created: 23/Jun/14 3:31 PM Description: There is no OSS licensing information associated with the SBT Plugin project: https://github.com/jenkinsci/sbt-plugin This is a blocker for several of us to be able to contribute to this plugin. Project: Jenkins Priority: Trivial Reporter: Matthew Fulgo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23541) AbstractMethodError when migrating subversion PerJobCredentialStore from 1.54 to 2.4
recampbell created JENKINS-23541 AbstractMethodError when migrating subversion PerJobCredentialStore from 1.54 to 2.4 Issue Type: Bug Assignee: Unassigned Components: subversion Created: 23/Jun/14 2:42 PM Description: Upon upgrading from subversion plugin 1.54 to 2.4 (w/ credentials plugin 1.14), I receive this exception on startup Caused by: java.lang.AbstractMethodError: hudson.scm.SubversionSCM$DescriptorImpl$Credential.toCredentials(Lhudson/model/ModelObject;Ljava/lang/String;)Lcom/cloudbees/plugins/credentials/common/StandardCredentials; at hudson.scm.SubversionSCM$DescriptorImpl.migrateCredentials(SubversionSCM.java:1676) at hudson.scm.PerJobCredentialStore.migrateCredentials(PerJobCredentialStore.java:109) Full stack trace: https://gist.github.com/recampbell/1e4b4462ada0ca6662d4 at hudson.scm.SubversionSCM$DescriptorImpl.migratePerJobCredentials(SubversionSCM.java:1657) at hudson.scm.SubversionSCM.perJobCredentialsMigration(SubversionSCM.java:1589) ... 13 more Project: Jenkins Labels: subversion Priority: Major Reporter: recampbell 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] [jobconfighistory] (JENKINS-23527) Job configuration history is missing (not recorded) for some jobs
Martin Burger commented on JENKINS-23527 Job configuration history is missing (not recorded) for some jobs Do you mean upgrading Jenkins itself? I just upgraded Jenkins from 1.567 to 1.568. I changed some job configuration values afterwards; for some jobs those changes are recorded, for other jobs they are not. Note that this behavior stays the same for each job. Thus, the same jobs keep not working, the other ones keep working. In this sense, the behavior is consistent over time; at least since it stopped to work. 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] [svnmerge] (JENKINS-23371) Manually-triggered integration
Chris Platts commented on JENKINS-23371 Manually-triggered integration Thanks for the reply, Both the parent and the branch projects have only one SVN module defined, however they do both use SVN Externals to pull in other libraries from our SVN repository. These externals are not modified in the projects into which they're pulled, so they should be clean (for us, modifying an external from anywhere other than a separate check-out of the external itself is a smack-able offence ) 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] [component] (JENKINS-23540) Post build step not run and difficult to know why
Jonathan Grant created JENKINS-23540 Post build step not run and difficult to know why Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: component Created: 23/Jun/14 1:53 PM Description: I just installed on Windows7, after checkout from SVN, my post build "BAT" file doesn't run.. and unclear why - could the output trigger be included to make it simpler to see why not running? The trigger used to work ok in Hudson. Thank you for any suggestions [snip] AUinternal.zip U. At revision 21668 Triggering default default completed with result FAILURE Finished: FAILURE Environment: Windows7 Project: Jenkins Priority: Minor Reporter: Jonathan Grant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [embeddable-build-status] (JENKINS-21112) Add 2x Image(s) Or Use HTML To Better Support Retina Screens
SCM/JIRA link daemon commented on JENKINS-21112 Add 2x Image(s) Or Use HTML To Better Support Retina Screens Code changed in jenkins User: Marius Gedminas Path: src/main/java/org/jenkinsci/plugins/badge/ImageResolver.java src/main/java/org/jenkinsci/plugins/badge/StatusImage.java src/main/webapp/status/build-failing-red.svg src/main/webapp/status/build-passing-brightgreen.svg src/main/webapp/status/build-running-blue.svg src/main/webapp/status/build-unknown-lightgrey.svg src/main/webapp/status/build-unstable-yellow.svg src/main/webapp/status/failure.png src/main/webapp/status/running.png src/main/webapp/status/success.png src/main/webapp/status/unknown.png src/main/webapp/status/unstable.png http://jenkins-ci.org/commit/embeddable-build-status-plugin/be474fad42c8b36e93ec59eab502fa4ad01d6475 Log: Replace PNG icons with shields.io-style SVG icons Fixes https://issues.jenkins-ci.org/browse/JENKINS-23062 and https://issues.jenkins-ci.org/browse/JENKINS-21112 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [embeddable-build-status] (JENKINS-23062) Use shields.io-style badges
SCM/JIRA link daemon commented on JENKINS-23062 Use shields.io-style badges Code changed in jenkins User: Marius Gedminas Path: src/main/java/org/jenkinsci/plugins/badge/ImageResolver.java src/main/java/org/jenkinsci/plugins/badge/StatusImage.java src/main/webapp/status/build-failing-red.svg src/main/webapp/status/build-passing-brightgreen.svg src/main/webapp/status/build-running-blue.svg src/main/webapp/status/build-unknown-lightgrey.svg src/main/webapp/status/build-unstable-yellow.svg src/main/webapp/status/failure.png src/main/webapp/status/running.png src/main/webapp/status/success.png src/main/webapp/status/unknown.png src/main/webapp/status/unstable.png http://jenkins-ci.org/commit/embeddable-build-status-plugin/be474fad42c8b36e93ec59eab502fa4ad01d6475 Log: Replace PNG icons with shields.io-style SVG icons Fixes https://issues.jenkins-ci.org/browse/JENKINS-23062 and https://issues.jenkins-ci.org/browse/JENKINS-21112 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] (JENKINS-23536) Remove h2: 'Aggregated view' when 'Number of pipeline instances per pipeline' = 0
Patrik Boström resolved JENKINS-23536 as Fixed Remove h2: 'Aggregated view' when 'Number of pipeline instances per pipeline' = 0 Change By: Patrik Boström (23/Jun/14 1:44 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-23536) Remove h2: 'Aggregated view' when 'Number of pipeline instances per pipeline' = 0
Patrik Boström commented on JENKINS-23536 Remove h2: 'Aggregated view' when 'Number of pipeline instances per pipeline' = 0 Fixed in commit: https://github.com/Diabol/delivery-pipeline-plugin/commit/978301fc575ddd2ed5bfae444c97c84fe5c54a0b 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] (JENKINS-23491) CVS Plugin deletes all files in workspace when "Use Update" is not selected
Pavel Saab commented on JENKINS-23491 CVS Plugin deletes all files in workspace when "Use Update" is not selected I do have the Delete Workspace plugin installed and configured to exclude certain items from being deleted in the job's workspace. However, your plugin does not respect those settings and wipes out everything under the workspace. Why does it need to do that? Can you limit it to only delete items that were checked out from CVS? 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] [testng] (JENKINS-23539) Initialize TestNgResult from testng result xml tag
Peter Fouquet created JENKINS-23539 Initialize TestNgResult from testng result xml tag Issue Type: Improvement Assignee: Nalin Makar Components: testng Created: 23/Jun/14 1:10 PM Description: It would be very good for tests with many test results to initialize the values for total, pass, failed and skip from the testng result tag. For example to show the following testng-result.xml with from a job with many testcases, without writing a test result for each testmethod. Project: Jenkins Priority: Major Reporter: Peter Fouquet 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] [testng] (JENKINS-23539) Initialize TestNgResult from testng result xml tag
Peter Fouquet updated JENKINS-23539 Initialize TestNgResult from testng result xml tag Change By: Peter Fouquet (23/Jun/14 1:11 PM) Description: It would be very good for tests with many test results to initialize the values for total, pass, failed and skip from the testng result tag. For example to show the following testng-result.xml with from a job with many testcases, without writing a test result for each testmethod. / > 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] [ws-cleanup] (JENKINS-13444) Workspace Cleanup plugin seems to be following symlinks and deleting files outside its workspace
Thomas Herrlin commented on JENKINS-13444 Workspace Cleanup plugin seems to be following symlinks and deleting files outside its workspace I have confirmed integration of fix between 0.20 and 0.21 with a simple testcase: Execute shell: mkdir -p a touch a/a.file ln -s a b Delete workspace when build is done: Apply pattern also on directories: False Exclude: a/a.file Version 0.20: a and b are preserved. a/a.file deleted (via symlink b). Version 0.21: a and a/a.file are preserved. b deleted (b treated as a file). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16018) Not all builds show in the build history dashboard on job
Andreas W commented on JENKINS-16018 Not all builds show in the build history dashboard on job Happens also with 1.554.1 LTS. This is really critical and annoying for us. Maybe also related to https://issues.jenkins-ci.org/browse/JENKINS-18678 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Lukas Goormann edited a comment on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Having similar issue with Jenkins 1.568, Subversion Plugin 2.4 and Credentials Plugin 1.14 when using a variable in the SVN URL and the SCM build trigger. Ouput of the Subversion-Request-Log: Started on 23.06.2014 14:27:01 Received SCM poll call on for RC.TR.app.core.build.All on 23.06.2014 14:27:01 ERROR: Abfrage der aktuellen Revision schlug fehl für Repository https:// .../correctVariableRepacement org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/.../correctVariableRepacement failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461) at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1235) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1415) at hudson.scm.SCM.poll(SCM.java:401) at hudson.model.AbstractProject._poll(AbstractProject.java:1428) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:509) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:538) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 33 more Done. Took 0,12 Sekunden No changes Will either one of the provided Patches help here? and how to apply it? or is another fix needed? Thanks in advance... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators.
[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Lukas Goormann edited a comment on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Having similar issue with Jenkins 1.568, Subversion Plugin 2.4 and Credentials Plugin 1.14 when using a variable in the SVN URL on and the SCM build trigger. Ouput of the Subversion-Request-Log: Started on 23.06.2014 14:27:01 Received SCM poll call on for RC.TR.app.core.build.All on 23.06.2014 14:27:01 ERROR: Abfrage der aktuellen Revision schlug fehl für Repository https:// .../correctVariableRepacement org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/.../correctVariableRepacement failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461) at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1235) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1415) at hudson.scm.SCM.poll(SCM.java:401) at hudson.model.AbstractProject._poll(AbstractProject.java:1428) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:509) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:538) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 33 more Done. Took 0,12 Sekunden No changes Will either one of the provided Patches help here? and how to apply it? or is another fix needed? Thanks in advance... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators.
[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Lukas Goormann edited a comment on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Having the described issue with Jenkins 1.568, Subversion Plugin 2.4 and Credentials Plugin 1.14: Started on 23.06.2014 14:27:01 Received SCM poll call on for RC.TR.app.core.build.All on 23.06.2014 14:27:01 ERROR: Abfrage der aktuellen Revision schlug fehl für Repository https:// .../correctVariableRepacement org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/.../correctVariableRepacement failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461) at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1235) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1415) at hudson.scm.SCM.poll(SCM.java:401) at hudson.model.AbstractProject._poll(AbstractProject.java:1428) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:509) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:538) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 33 more Done. Took 0,12 Sekunden No changes 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 unsubscr
[JIRA] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
David Riggleman commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted I'm still seeing this problem in 1.568. In my case, the slave nodes are being disconnected due to a ping timeout. Up until recently (not sure exact version but around version 1.560 sounds right), I never had any issues with the slave nodes not connecting. Here's a snippet of the logs. I can provide more info if needed. Connection #19 failed java.io.IOException: NioChannelHub is not currently running at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:446) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:220) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:149) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:159) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:36) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:52) at jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:120) at jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:63) at jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:57) at jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:31) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:157) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Lukas Goormann commented on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Having the described issue with Jenkins 1.568, Subversion Plugin 2.4 and Credentials Plugin 1.14: Started on 23.06.2014 14:27:01 Received SCM poll call on for RC.TR.app.core.build.All on 23.06.2014 14:27:01 ERROR: Abfrage der aktuellen Revision schlug fehl für Repository https:// .../correctVariableRepacement org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/.../correctVariableRepacement failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461) at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1235) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78) at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1415) at hudson.scm.SCM.poll(SCM.java:401) at hudson.model.AbstractProject._poll(AbstractProject.java:1428) at hudson.model.AbstractProject.poll(AbstractProject.java:1331) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:509) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:538) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185)}} at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 33 more Done. Took 0,12 Sekunden No changes 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
[JIRA] [prioritysorter] (JENKINS-23538) Remove support for Legacy Sorter
Magnus Sandberg created JENKINS-23538 Remove support for Legacy Sorter Issue Type: New Feature Assignee: Magnus Sandberg Components: prioritysorter Created: 23/Jun/14 12:40 PM Description: Remove the Legacy Sorter, keep code for conversion from Legacy to Advanced. Project: Jenkins Priority: Major Reporter: Magnus Sandberg 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] [valgrind] (JENKINS-23529) The plugin publisher reports no error although the generated xml contains memory violations
Johannes Ohlemacher started work on JENKINS-23529 The plugin publisher reports no error although the generated xml contains memory violations Change By: Johannes Ohlemacher (23/Jun/14 11:34 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23534) Unable to set number of executors on slave through Groovy system script
vjuranek updated JENKINS-23534 Unable to set number of executors on slave through Groovy system script Changed to feature request and more into core component. Groovy plugin just provides convenient access to Jenkins classes, if any public API is missing, it should be added into Jenkins core, not implemented as some workaround in Groovy plugin. Change By: vjuranek (23/Jun/14 11:18 AM) Issue Type: Bug New Feature Component/s: core Component/s: groovy 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] [junit] (JENKINS-23480) Test Report shows test passed that actually did not run due to initialization errors
Benjamin Sailer updated JENKINS-23480 Test Report shows test passed that actually did not run due to initialization errors Change By: Benjamin Sailer (23/Jun/14 11:07 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-23480) Test Report shows test passed that actually did not run due to initialization errors
Benjamin Sailer updated JENKINS-23480 Test Report shows test passed that actually did not run due to initialization errors Change By: Benjamin Sailer (23/Jun/14 11:07 AM) Component/s: junit 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] (JENKINS-23537) Trigger button is not rendered correctly on Firefox
Patrik Boström updated JENKINS-23537 Trigger button is not rendered correctly on Firefox Change By: Patrik Boström (23/Jun/14 10:57 AM) Attachment: Manual-firefox.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23486) MSI Package: Remove the entire C:\Program Files\Jenkins during the uninstallation
Oleg Nenashev updated JENKINS-23486 MSI Package: Remove the entire C:\Program Files\Jenkins during the uninstallation Modified the issue's description. Change By: Oleg Nenashev (23/Jun/14 10:45 AM) Summary: Uninstalling Jenkins leaves MSI Package: Remove the entire C:\ Program Files full of files \Jenkins during the uninstallation Issue Type: Bug New Feature 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] (JENKINS-23537) Trigger button is not rendered correctly on Firefox
Patrik Boström created JENKINS-23537 Trigger button is not rendered correctly on Firefox Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline Created: 23/Jun/14 10:39 AM Description: Trigger button is not rendered correctly on Firefox. Project: Jenkins Priority: Minor Reporter: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-23536) Remove h2: 'Aggregated view' when 'Number of pipeline instances per pipeline' = 0
Marcus Philip updated JENKINS-23536 Remove h2: 'Aggregated view' when 'Number of pipeline instances per pipeline' = 0 Screenshot after fix Change By: Marcus Philip (23/Jun/14 10:26 AM) Attachment: Screen Shot 2014-06-23 at 12.22.52.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-23536) Remove h2: 'Aggregated view' when 'Number of pipeline instances per pipeline' = 0
Marcus Philip created JENKINS-23536 Remove h2: 'Aggregated view' when 'Number of pipeline instances per pipeline' = 0 Issue Type: Improvement Assignee: Unassigned Components: delivery-pipeline Created: 23/Jun/14 10:16 AM Description: The h2 'Aggregated view' steals lot of screen space and is not relevant when number of pipeline instances per pipeline is 0. Environment: DPP: 0.8.1 Jenkins: 1.565 Project: Jenkins Labels: plugin UI Priority: Minor Reporter: Marcus Philip 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] [xcode] (JENKINS-23535) NullPointerException when packaging IPA (Xcode plugin 1.4.2 & Jenkins 1.568)
Alex N. updated JENKINS-23535 NullPointerException when packaging IPA (Xcode plugin 1.4.2 & Jenkins 1.568) Change By: Alex N. (23/Jun/14 10:00 AM) Fix Version/s: current Affects Version/s: current 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] [xcode] (JENKINS-23535) NullPointerException when packaging IPA (Xcode plugin 1.4.2 & Jenkins 1.568)
Alex N. created JENKINS-23535 NullPointerException when packaging IPA (Xcode plugin 1.4.2 & Jenkins 1.568) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: xcode Created: 23/Jun/14 9:58 AM Description: When packaging the IPA file, I get a NullPointerException. Cleaning up previously generated .ipa files Cleaning up previously generated .dSYM.zip files Packaging IPA FATAL: null java.lang.NullPointerException at au.com.rayh.XCodeBuilder.perform(XCodeBuilder.java:575) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1597) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) All was fine in version 1.3.3 of the Xcode plugin. Fix Versions: current Project: Jenkins Priority: Blocker Reporter: Alex N. 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] [groovy] (JENKINS-23534) Unable to set number of executors on slave through Groovy system script
David Engster updated JENKINS-23534 Unable to set number of executors on slave through Groovy system script Change By: David Engster (23/Jun/14 9:50 AM) Component/s: slave-status 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] [groovy] (JENKINS-23534) Unable to set number of executors on slave through Groovy system script
David Engster
created JENKINS-23534
Unable to set number of executors on slave through Groovy system script
Issue Type:
Bug
Affects Versions:
current
Assignee:
vjuranek
Components:
groovy, slave-status
Created:
23/Jun/14 9:49 AM
Description:
I would like to set the number of executors on a slave node in a build step. I tried doing that with a Groovy system script, but it seems to me this is not possible, since the setNumExecutors(int) method is only implemented by jenkins.model.Jenkins, which will however only affect the master node. The method is not accessible through the 'Node', 'Slave' or 'Computer' classes, which would allow me to do that on a slave. For example, like this
Hudson.instance.getComputer("SlaveName").setNumExecutors(1)
Project:
Jenkins
Labels:
groovy
api
slave
executor
Priority:
Minor
Reporter:
David Engster
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-23486) Uninstalling Jenkins leaves Program Files full of files
Jonathan Grant commented on JENKINS-23486 Uninstalling Jenkins leaves Program Files full of files Hi Thanks for the reply Normally user data is stored under c:\users\username\AppData\AppName etc It seems nicer to me if the uninstall would remove the "C:\Program Files\Jenkins" folder. Or maybe it could have an option as part of the uninstaller to ask the user the question? Thanks 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] [clearcase-ucm] (JENKINS-23533) Enhance filtering for mail sending (case 10301)
Mads Nielsen updated JENKINS-23533 Enhance filtering for mail sending (case 10301) Change By: Mads Nielsen (23/Jun/14 9:31 AM) Summary: Enhance filtering for mail sendgin sending (case 10301) 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] [parameter-separator] (JENKINS-23530) Ability to Add Text to parameter seperator sections
steven armstrong commented on JENKINS-23530 Ability to Add Text to parameter seperator sections Thanks for the quick turn around, looks good can we get this added to a 0.6 release. Thanks. 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] (JENKINS-23532) Manual trigger execution causes TriggerException
Tommy Tynjä commented on JENKINS-23532 Manual trigger execution causes TriggerException The error occurs within the build pipeline plugin which doesn't seem to handle folders properly. This error occurs if the build steps reside within a folder, e.g. "MyProject", and the upstream project for the manually triggered step is configured with the downstream project name including the folder name, e.g. "MyProject/Deploy-env02". It would be desirable if this convention was supported, but a workaround is to just remove the folder name from the "Downstream Project Names" settings in the "Build other projects (manual step)" post-build action, e.g. to just state "Deploy-env02", and the manual trigger will work. Proposing that a more descriptive error message is returned when this error occurs. 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] [clearcase-ucm] (JENKINS-23533) Enhance filtering for mail sendgin (case 10301)
Mads Nielsen created JENKINS-23533 Enhance filtering for mail sendgin (case 10301) Issue Type: Improvement Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 23/Jun/14 8:43 AM Fix Versions: current Project: Jenkins Priority: Major Reporter: Mads Nielsen 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-23437) NPE when binding JSON form data without 'properties' field
Oleg Nenashev commented on JENKINS-23437 NPE when binding JSON form data without 'properties' field BTW, the bug fix in https://github.com/jenkinsci/jenkins/pull/1280 seems to be valid. 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] (JENKINS-23532) Manual trigger execution causes TriggerException
Tommy Tynjä created JENKINS-23532 Manual trigger execution causes TriggerException Issue Type: Bug Assignee: Tommy Tynjä Components: delivery-pipeline Created: 23/Jun/14 8:10 AM Description: An error message "Could not trigger build!" is displayed in the delivery pipeline view when trying to execute the manual step, which has been setup using the build pipeline plugin. The API URL returns a HTTP 500. The error seems to occur regardless of whether the current build step has a configured upstream trigger or not. The following stacktrace can be found in the Jenkins log: jun 23, 2014 8:48:30 FM SEVERE au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView triggerBuild No upstream trigger found for this projectMyProject » Deploy-env02 jun 23, 2014 8:48:30 FM WARNING se.diabol.jenkins.pipeline.DeliveryPipelineView triggerManual Could not trigger manual build MyProject/Deploy-env02 for upstream MyProject/Deploy-env01-smoke_tests id: 105 se.diabol.jenkins.pipeline.trigger.TriggerException: Could not trigger at se.diabol.jenkins.pipeline.trigger.BPPManualTrigger.triggerManual(BPPManualTrigger.java:35) at se.diabol.jenkins.pipeline.DeliveryPipelineView.triggerManual(DeliveryPipelineView.java:265) at se.diabol.jenkins.pipeline.PipelineApi.doManualStep(PipelineApi.java:47) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.do
[JIRA] [disk-usage] (JENKINS-23519) Misspelling in Disk Usage plugin
Harald Albers resolved JENKINS-23519 as Fixed Misspelling in Disk Usage plugin see https://github.com/jenkinsci/disk-usage-plugin/commit/f44734e30ea295afd9756b9a66784404b6a5204d Change By: Harald Albers (23/Jun/14 7:06 AM) Status: Open Resolved Assignee: Lucie Votypkova Harald Albers 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.
