[JIRA] [job-dsl-plugin] (JENKINS-19401) Include YAML library
Sam Gleske commented on JENKINS-19401 Include YAML library Pay no mind, the version of Jenkins I was using didn't support @Grab. Now that I've upgraded it works great. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Daniel Beck commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration As I wrote above, I'm sending almost exactly the same data, and it's processed correctly on the server, despite using 1.590. Uploading another screenshot of the same form field doesn't help (or I don't understand what it signifies, in that case, please explain). Is anyone able to reproduce this issue on a pristine Jenkins instance? How about after installing all the plugins you have on your prod instance (in the same versions)? If it works out of the box but installing plugins results in a problem, try to determine which plugin is responsible by disabling/enabling them until you find the culprit. 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] [promoted-builds-plugin] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Tobias Bertelsen commented on JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. I have found a workaround for this bug: The way I distribute the workload, is by having a build parameter defining the build node. This node-parameter is called Hostname. In the promotion step, you select "Restrict where this promotion process can be run" and put "$Hostname" (no quotes) in the field "Label _expression_." Again: this is a workaround, not a fix. I am surprised that this is not the default behavior and has "low" priority. I cannot see an example where it make much sense to run a promotion, without having access to the build artifacts. So +1 for me as well on fixing 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] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Martin Beller commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration @Daniel: Do you get the same Warning (label assignment is using legacy '_.assignedLabelString') when pressing the Save/Apply button? Did you verify that the config.xml file of the related job is updated properly: assignedNodebuildServer/assignedNode canRoamfalse/canRoam 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-23366) jdk8u5 installation fails on windows slaves
Giacomo Boccardo commented on JENKINS-23366 jdk8u5 installation fails on windows slaves Similar error using Jenkins 1.580.1 and JDK 1.8u25 (JDK 1.7u72 works) [EnvInject] - Loading node environment variables. Installing C:\Users\Administrator\jenkins\tools\hudson.model.JDK\JDK18Auto\jdk.exe [JDK18Auto] $ C:\Users\Administrator\jenkins\tools\hudson.model.JDK\JDK18Auto\jdk.exe /s ADDLOCAL="ToolsFeature" REBOOT=ReallySuppress INSTALLDIR=C:\Users\Administrator\jenkins\tools\hudson.model.JDK\JDK18Auto '/L \"C:\Users\Administrator\jenkins\tools\hudson.model.JDK\JDK18Auto\jdk.exe.install.log\"' Failed to install JDK. Exit code=-80 ERROR: SEVERE ERROR occurs org.jenkinsci.lib.envinject.EnvInjectException: hudson.AbortException at org.jenkinsci.plugins.envinject.service.EnvInjectVariableGetter.getBuildVariables(EnvInjectVariableGetter.java:84) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:231) at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:46) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:587) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:491) at hudson.model.Run.execute(Run.java:1745) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: hudson.AbortException at hudson.tools.JDKInstaller.install(JDKInstaller.java:277) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:141) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:68) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:205) at hudson.model.JDK.forNode(JDK.java:130) at org.jenkinsci.plugins.envinject.service.EnvInjectVariableGetter.getBuildVariables(EnvInjectVariableGetter.java:79) ... 8 more 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] [pretested-integration-plugin] (JENKINS-25545) Multiple git repository names are not check and repositories risk be merged (our case 12286)
Mads Nielsen resolved JENKINS-25545 as Fixed Multiple git repository names are not check and repositories risk be merged (our case 12286) Change By: Mads Nielsen (24/Nov/14 9:32 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25618) Use standard commit message when the squash strategy is used
Mads Nielsen resolved JENKINS-25618 as Fixed Use standard commit message when the squash strategy is used Change By: Mads Nielsen (24/Nov/14 9:32 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25618) Use standard commit message when the squash strategy is used case 12299
Mads Nielsen updated JENKINS-25618 Use standard commit message when the squash strategy is used case 12299 Change By: Mads Nielsen (24/Nov/14 9:35 AM) Summary: Usestandardcommitmessagewhenthesquashstrategyisused case12299 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] [buildresult-trigger-plugin] (JENKINS-25753) BuildResultTrigger doesn't trigger build
Victor Engmark updated JENKINS-25753 BuildResultTrigger doesnt trigger build Change By: Victor Engmark (24/Nov/14 9:44 AM) Description: Thejobwiththefollowingconfigurationnevertriggers,evenafteranunstableacceptance_testrun:triggersorg.jenkinsci.plugins.buildresulttrigger.BuildResultTriggerplugin=buildresult-trigger@0.17spec05***/speccombinedJobsfalse/combinedJobsjobsInfoorg.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfojobNamesacceptance_test/jobNamescheckedResultsorg.jenkinsci.plugins.buildresulttrigger.model.CheckedResultcheckedSUCCESS/checked/org.jenkinsci.plugins.buildresulttrigger.model.CheckedResultorg.jenkinsci.plugins.buildresulttrigger.model.CheckedResultcheckedUNSTABLE/checked/org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult/checkedResults/org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo/jobsInfo/org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger/triggers Similarissue:https://issues.jenkins-ci.org/browse/JENKINS-12427 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] [buildresult-trigger-plugin] (JENKINS-25753) BuildResultTrigger doesn't trigger build
Victor Engmark created JENKINS-25753 BuildResultTrigger doesnt trigger build Issue Type: Bug Assignee: Unassigned Components: buildresult-trigger-plugin Created: 24/Nov/14 9:44 AM Description: The job with the following configuration never triggers, even after an unstable acceptance_test run: triggers org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger plugin="buildresult-trigger@0.17" spec0 5 * * */spec combinedJobsfalse/combinedJobs jobsInfo org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo jobNamesacceptance_test/jobNames checkedResults org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult checkedSUCCESS/checked /org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult checkedUNSTABLE/checked /org.jenkinsci.plugins.buildresulttrigger.model.CheckedResult /checkedResults /org.jenkinsci.plugins.buildresulttrigger.model.BuildResultTriggerInfo /jobsInfo /org.jenkinsci.plugins.buildresulttrigger.BuildResultTrigger /triggers Environment: BuildResultTrigger 0.17 Project: Jenkins Labels: plugin build Priority: Blocker Reporter: Victor Engmark 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] [performance-plugin] (JENKINS-25138) Weird The label _some_jmeter_label caused the build to fail during comparizon
Thomas Mortagne updated JENKINS-25138 Weird The label _some_jmeter_label caused the build to fail during comparizon Change By: Thomas Mortagne (24/Nov/14 9:52 AM) Description: Iattachedanexample.AsyoucanseeinthelogIset0%everywhereinUseRelativethresholdsforbuildcomparisontomakesureitsnotfailingbecauseofthatbutIstillgetafailurewithoutanyinformationonwhyitfailed.Alsodoesnotalwaysfailonthesamelabel. Youcanseethejobonhttp://ci.xwiki.org/job/xwiki-enterprise-test-jmeter/. 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-plugin] (JENKINS-24971) valgrind not run if working directory set.
J McG commented on JENKINS-24971 valgrind not run if working directory set. Thanks for the advice. I note that the download page for the plugin lists 0.22 as the latest version: https://wiki.jenkins-ci.org/display/JENKINS/Valgrind+Plugin I quote: "Latest Release 0.22 (archives) Latest Release Date Sep 16, 2014 Required Core 1.424" We use Jenkins v1.577. I also note that the changelog lists v0.24, which appears to be unavailable, and I can't find a link to it anywhere. Please can you advise? 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-22514) Zip generated from all files in zip contains the wrong slashes
Holger Voormann commented on JENKINS-22514 Zip generated from all files in zip contains the wrong slashes The changelog says that the fix of this issue is included in 1.590. But this is wrong: see DirectoryBrowserSupport tagged with jenkins-1.590. Probably, this issue will be fixed with the upcoming version 1.591. 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-plugin] (JENKINS-24971) valgrind not run if working directory set.
Johannes Ohlemacher commented on JENKINS-24971 valgrind not run if working directory set. The release of the original version 0.23 failed and i did not notice that immediately. I did a new release (0.24) a couple of hours ago and you can download the plugin manually from here: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/valgrind/0.24/ It will take up to 12 hours until its visible in jenkins update center and on the website. That delay is very unfortunate, but it's the way the jenkins infrastructure works ;( 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-plugin] (JENKINS-24971) valgrind not run if working directory set.
J McG commented on JENKINS-24971 valgrind not run if working directory set. Thank you very much for your incredibly prompt, clear and helpful response! Thanks again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind-plugin] (JENKINS-24971) valgrind not run if working directory set.
J McG edited a comment on JENKINS-24971 valgrind not run if working directory set. (BTW: I think your considering the path relative to the working dir as a bug is what I thought too. Relative to the workspace like most of the other settings in Jenkins seems much more sensible! Thank you very much for your incredibly prompt, clear and helpful response! Thanks again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-25754) At view overview the link to Jacoco Line Coverage results is wrong
podskalsky created JENKINS-25754 At view overview the link to Jacoco Line Coverage results is wrong Issue Type: Bug Assignee: Ognjen Bubalo Attachments: 2014-11-24 11_34_58-OTTV [Jenkins].png Components: jacoco-plugin Created: 24/Nov/14 10:44 AM Description: If I configure in a view the Line Coverage column, the link to the Jacoco Line coverage results is wrong. the link includes 2 times "/view/OTTV/view/OTTV": http://cssincm.gud.siemens.at:8181/view/OTTV/view/OTTV/job/OTTV.MMSE-SearchDataCrawler.V3.0/lastSuccessfulBuild/jacoco/ Environment: Jenkins version 1.588 Project: Jenkins Priority: Minor Reporter: podskalsky 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-25755) SPDY is not working on 1.580
Ireneusz Makowski created JENKINS-25755 SPDY is not working on 1.580 Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Nov/14 10:49 AM Description: I've tried to use --spdy option but is not working. I've installed SPDY indicator in chrome to check if SPDY on Jenkins is working but is not. Could you please provide info how to enable it on Windows installation? I've also checked ci.jenkins.org with this plugin and SPDY is not working. Environment: Jenkins 1.580.1 through Apache on Windows 2008 R2 Project: Jenkins Priority: Major Reporter: Ireneusz Makowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Brendan Ragan commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed I'm getting this issue and i've only got master, develop and demo branches on my repo. My polling log says that are "No Changes" but i get a build "Started by an SCM Change" What other information do you need to resolve 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] [config-file-provider-plugin] (JENKINS-16706) Configure provided settings.xml at the Maven plugin level, not at the Maven job level
Giacomo Boccardo commented on JENKINS-16706 Configure provided settings.xml at the Maven plugin level, not at the Maven job level ...so what should be the proper way to specify globally setting.xml without configuring each job manually? 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] [sauce-ondemand-plugin] (JENKINS-25756) Use latest version of selected browsers? not working with Selenium RC
Mattias Jiderhamn created JENKINS-25756 Use latest version of selected browsers? not working with Selenium RC Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 24/Nov/14 12:41 PM Description: When selecting Selenium RC and checking "Use latest version of selected browsers?", the following NPE occurs: java.lang.NullPointerException at com.saucelabs.ci.BrowserFactory.getLatestSeleniumBrowserVersion(BrowserFactory.java:267) at com.saucelabs.ci.BrowserFactory.seleniumBrowserForKey(BrowserFactory.java:257) at hudson.plugins.sauce_ondemand.SauceEnvironmentUtil.outputSeleniumRCVariables(SauceEnvironmentUtil.java:77) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.buildEnvVars(SauceOnDemandBuildWrapper.java:252) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:883) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:56) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:167) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:677) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1706) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Project: Jenkins Priority: Minor Reporter: Mattias Jiderhamn 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] [sauce-ondemand-plugin] (JENKINS-25757) Windows 2003 is an unknown platform
Mattias Jiderhamn created JENKINS-25757 Windows 2003 is an unknown platform Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 24/Nov/14 12:46 PM Description: When configuring WebDriver to use any browser on "Windows 2003", then the platform cannot be resolved by SeleniumFactory. Supposedly "Windows Server 2003" is expected. java.lang.IllegalArgumentException: No enum constant org.openqa.selenium.Platform.Windows 2003 at java.lang.Enum.valueOf(Enum.java:236) at org.openqa.selenium.Platform.valueOf(Platform.java:30) at org.openqa.selenium.remote.DesiredCapabilities.setCapability(DesiredCapabilities.java:168) at com.saucelabs.sauce_ondemand.driver.SauceOnDemandSPIImpl.createWebDriver(SauceOnDemandSPIImpl.java:157) at com.saucelabs.sauce_ondemand.driver.SauceOnDemandSPIImpl.createWebDriver(SauceOnDemandSPIImpl.java:141) at com.saucelabs.selenium.client.factory.SeleniumFactory.createWebDriverInstance(SeleniumFactory.java:320) at com.saucelabs.selenium.client.factory.SeleniumFactory.createWebDriverInstance(SeleniumFactory.java:303) at com.saucelabs.selenium.client.factory.SeleniumFactory.createWebDriver(SeleniumFactory.java:109) ... Project: Jenkins Priority: Major Reporter: Mattias Jiderhamn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Mark Waite commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed Brendan Ragan we need enough information to be able to duplicate your problem. In your case, if you're able to isolate a series of steps or conditions which cause the problem, then the problem also should have a new bug report. This bug report has wandered far from its original problem description with several statements of "I'm seeing the same bug" which are then followed by statements which seem to me to contradict the original bug report. For example, the original bug report says: None of my jobs using "Poll SCM" in "Build Triggers". But I see them running with build cause "Started by an SCM change" though very often there are no changes at all. And Polling Log is always empty. Later comments then include copies of a non-empty polling log even though the original report says that the polling log is always empty. Later comments refer to use of a web hook, but web hooks don't have any affect on jobs which are not configured to "Poll SCM". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Brendan Ragan commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed Mark Waite - the issue i'm actually seeing is that Poll SCM (or Feature aware poll SCM) is enabled at an interval of 5 minutes but even though no changes are detected it continues to build. Should I create a new issue for this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Mark Waite commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed Brendan Ragan you should create a new issue for it. Refer to how to report an issue for key items that will give your issue report a better chance of success. A bug report to an open source project (like Jenkins) is an attempt to persuade someone to use their personal time to work on the bug you found. Every barrier you inadvertently insert between effective use of their personal time and your bug report is a risk that your bug report won't receive the attention you want. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-23123) NPE from MavenSiteArchiver.getModulePath
Aldric Berges commented on JENKINS-23123 NPE from MavenSiteArchiver.getModulePath Hi, We are having the same issue on our projects. The workaround did the trick. Of course, sites are no more archived. Environment : Jenkins ver. 1.590 Maven 3.0.5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobgenerator-plugin] (JENKINS-23390) Custom workspace setting disappears randomly
Pete W updated JENKINS-23390 Custom workspace setting disappears randomly Change By: Pete W (24/Nov/14 1:57 PM) Environment: Jenkins1.549onUbuntuPrecise Jenkins1.590onWindowsServer2012 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-plugin] (JENKINS-13750) Failed to retrieve tokenGroups
Giacomo Boccardo commented on JENKINS-13750 Failed to retrieve tokenGroups Still happening on Jenkins 1.580.1 using Active Directory Plugin 1.39. 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-25737) 'Run Parameter' build parameter is null when SCM/pre-SCM phase is started on remote-node.
Mike Delaney updated JENKINS-25737 Run Parameter build parameter is null when SCM/pre-SCM phase is started on remote-node. Change By: Mike Delaney (24/Nov/14 2:25 PM) Summary: RunParameterbuildparameterisnullwhenSCM/pre-SCMphaseisstarted onremote-node . 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-25758) NPE when triggering downstream job (again)
Steffen Sledz created JENKINS-25758 NPE when triggering downstream job (again) Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Nov/14 2:30 PM Description: We've some trigger-only jobs which check for repo changes only without any build step. They are used to trigger some downstream jobs only but fire this NPE: First time build. Skipping changelog. Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered FATAL: null java.lang.NullPointerException at hudson.model.Result.isBetterOrEqualTo(Result.java:125) at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:133) at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:83) at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:140) at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:243) at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:699) at hudson.model.Build$BuildExecution.cleanUp(Build.java:194) at hudson.model.Run.execute(Run.java:1805) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) There are a lot of JENKINS-Issues related to similar problems. But all of them are resolved fixed, cannot reproduce, or duplicated. So this seems to be a new problem. Environment: Jenkins 1.590 Fedora release 20 (Heisenbug) x86_64 OpenJDK Runtime Environment 1.7.0_71-mockbuild_2014_10_15_17_02-b00 Project: Jenkins Priority: Major Reporter: Steffen Sledz 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-25759) FilePath.validateAntFileMask sucks up heap
Jesse Glick created JENKINS-25759 FilePath.validateAntFileMask sucks up heap Issue Type: Bug Assignee: Jesse Glick Components: core Created: 24/Nov/14 2:42 PM Description: Although FilePath.validateAntFileMask is typically bounded to check at most 1 files before giving up and announcing that it cannot find a match, it turns out that DirectoryScanner collects the names of non-matches in filesNotIncluded and dirsNotIncluded in the meantime. In a big workspace, this can cause the JVM (usually a slave agent) to allocate gigabytes of heap, eventually causing the slave to become overwhelmed and crash. Project: Jenkins Labels: performance Priority: Critical Reporter: Jesse Glick 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-25759) FilePath.validateAntFileMask sucks up heap
Jesse Glick started work on JENKINS-25759 FilePath.validateAntFileMask sucks up heap Change By: Jesse Glick (24/Nov/14 2:42 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25737) 'Run Parameter' build parameter is null when SCM/pre-SCM phase is started on remote-node.
Mike Delaney updated JENKINS-25737 Run Parameter build parameter is null when SCM/pre-SCM phase is started on remote-node. Change By: Mike Delaney (24/Nov/14 2:44 PM) Attachment: jenkins-25747-example.tar 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-25737) 'Run Parameter' build parameter is null when SCM/pre-SCM phase is started on remote-node.
Mike Delaney commented on JENKINS-25737 Run Parameter build parameter is null when SCM/pre-SCM phase is started on remote-node. Daniel, (Using Jenkins 1.565.3, and Perforce SCM plug-in 1.3.29) Start Jenkins (I ran hpi:run) Add a dump remote node Configure a job to use as a 'Run Parameter' reference. Configure another job to use as a primry repro job Add a run paramter and point it to the job created in step #3 Add an execution of the Perforce SCM plug-in. You can use 'guest' as your use and workshop.perforce.com:1666 as your server Run job #3 to get at least one entry in the drop down The job will fail with an obscure error that looks to be an issue with Perforce but while debugging the code, I noticed that it was because the 'Run Parameter' variable was NULL when the Perforce SCM plug-in was trying to use it to do substitution. The eactt error that I'm seeing is: Caught exception in perforce-plugin. nulljava.lang.NullPointerException at java.lang.String.replace(String.java:2207) at hudson.plugins.perforce.utils.MacroStringHelper.substituteParametersNoCheck(MacroStringHelper.java:185) at hudson.plugins.perforce.utils.MacroStringHelper.getDefaultSubstitutions(MacroStringHelper.java:341) at hudson.plugins.perforce.utils.MacroStringHelper.substituteParametersNoCheck(MacroStringHelper.java:246) at hudson.plugins.perforce.utils.MacroStringHelper.substituteParametersNoCheck(MacroStringHelper.java:298) at hudson.plugins.perforce.utils.MacroStringHelper.substituteParameters(MacroStringHelper.java:148) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:876) at hudson.model.AbstractProject.checkout(AbstractProject.java:1024) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411) at hudson.model.Run.run(Run.java:1198) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:122) I've attached an example (jenkins-25747-example.tar) of the two jobs that I used to reproduce the error. It contains the two jobs that should be able to reproduce the error for you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25758) NPE when triggering downstream job (again)
Steffen Sledz
updated JENKINS-25758
NPE when triggering downstream job (again)
Change By:
Steffen Sledz
(24/Nov/14 2:54 PM)
Description:
Wevesome
trigger-only
jobswhichcheckforrepochangesonlywithoutanybuildstep.Theyareusedtotriggersomedownstreamjobs
onlybut
.Butinsteadoftriggeringthejobsthey
firethisNPE:
{noformat}Firsttimebuild.Skippingchangelog.Warning:youhavenopluginsprovidingaccesscontrolforbuilds,sofallingbacktolegacybehaviorofpermittinganydownstreambuildstobetriggeredFATAL:nulljava.lang.NullPointerException athudson.model.Result.isBetterOrEqualTo(Result.java:125) atjenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:133) atjenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:83) atjenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:140) athudson.tasks.BuildTrigger.execute(BuildTrigger.java:243) athudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:699) athudson.model.Build$BuildExecution.cleanUp(Build.java:194) athudson.model.Run.execute(Run.java:1805) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240){noformat}TherearealotofJENKINS-Issuesrelatedtosimilarproblems.Butallofthemareresolved*fixed*,*cannotreproduce*,or*duplicated*.Sothisseemstobeanewproblem.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25760) Jenkins maven-plugin cannot deal with mavens advanced reactor options
Jacques Stadler created JENKINS-25760 Jenkins maven-plugin cannot deal with mavens advanced reactor options Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 24/Nov/14 3:21 PM Description: The Jenkins Maven Plugin cannot deal with the advanced reactor options of Maven. See http://blog.sonatype.com/2009/10/maven-tips-and-tricks-advanced-reactor-options When e.g. executing a a maven build with the following maven command in Jenkins: mvn clean install -pl !excludedModule one gets the following error: Executing Maven: -B -f /myworkspace/myproject/pom.xml clean install -pl !excludedModule [INFO] Scanning for projects... [ERROR] Could not find the selected project in the reactor: !excludedModule - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException channel stopped See also the discussion in the Jenkins Google Group: https://groups.google.com/forum/#!topic/jenkinsci-users/8hXjxAB0WSw Environment: Jenkins v1.565.3, Maven-Plugin version 2.7 Project: Jenkins Priority: Major Reporter: Jacques Stadler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25760) Jenkins maven-plugin cannot deal with mavens advanced reactor options
Jacques Stadler
updated JENKINS-25760
Jenkins maven-plugin cannot deal with mavens advanced reactor options
Change By:
Jacques Stadler
(24/Nov/14 3:25 PM)
Description:
TheJenkinsMavenPlugincannotdealwiththeadvancedreactoroptionsofMaven.Seehttp://blog.sonatype.com/2009/10/maven-tips-and-tricks-advanced-reactor-optionsWhene.g.executingaamavenbuildwiththefollowingmavencommandinJenkins:mvncleaninstall-pl!excludedModuleonegetsthefollowingerror:{code}ExecutingMaven:-B-f/myworkspace/myproject/pom.xmlcleaninstall-pl!excludedModule[INFO]Scanningforprojects...[ERROR]Couldnotfindtheselectedprojectinthereactor:!excludedModule-[Help1][ERROR][ERROR]Toseethefullstacktraceoftheerrors,re-runMavenwiththe-eswitch.[ERROR]Re-runMavenusingthe-Xswitchtoenablefulldebuglogging.[ERROR][ERROR]Formoreinformationabouttheerrorsandpossiblesolutions,pleasereadthefollowingarticles:[ERROR][Help1]http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionExceptionchannelstopped{code}
Runningthesamecommandonthesameprojectwiththesamemavenversiononthecommandlineitworksfine.
SeealsothediscussionintheJenkinsGoogleGroup:https://groups.google.com/forum/#!topic/jenkinsci-users/8hXjxAB0WSw
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] [cobertura-plugin] (JENKINS-6094) Allow cobertura coverage report generation for failed builds
Kanstantsin Shautsou resolved JENKINS-6094 as Not A Defect Allow cobertura coverage report generation for failed builds Unset "Consider only stable builds" Change By: Kanstantsin Shautsou (24/Nov/14 3:27 PM) Status: Open Resolved Resolution: NotADefect 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-25759) FilePath.validateAntFileMask sucks up heap
Jesse Glick updated JENKINS-25759 FilePath.validateAntFileMask sucks up heap Change By: Jesse Glick (24/Nov/14 3:29 PM) Labels: lts-candidate performance 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] [cobertura-plugin] (JENKINS-25761) support multiple ant globs
Kanstantsin Shautsou created JENKINS-25761 support multiple ant globs Issue Type: Improvement Assignee: stephenconnolly Components: cobertura-plugin Created: 24/Nov/14 3:31 PM Description: I have project that generates results that are not under one mask. I see no optional group functionality in ANT glob with textinput in plugin configuration. Add functionality to support multiple ant globs with textarea input (one globe per line) Project: Jenkins Priority: Major Reporter: Kanstantsin Shautsou 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-10442) RestartNotSupportedException when trying to do safeRestart
Steve Jansen commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart Daniel Beck: my fix resolved the safeRestart (and restart) issue on my CentOS 6.5 system (which curiously uses the Oracle JDK 1.7.0_65). This resolved the Failed to obtain the command line arguments of the process error seen on my system in both the Jenkins Web UI and the Jenkins SSH/CLI. 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] [teamconcert-git-plugin] (JENKINS-25762) Build Engine going inactive due to no credentials
bbonn created JENKINS-25762 Build Engine going inactive due to no credentials Issue Type: Bug Assignee: Krishna Kishore Components: teamconcert-git-plugin Created: 24/Nov/14 3:38 PM Description: Hi there, We were recently required by our security group to disable anonymous access in Jenkins. This has had a negative effect on our RTC integration. We have never required folks to put in credentials into the build engine. Not many folks have taken to kicking off builds from the Eclipse, and it is one more place to forget to change your password. When we made the change we had a bunch of build engines shut down, i.e. go inactive. Is there any way around this, we don't want to ask developers to put credentials in unless they want the 2 way interaction (kicking off builds from Eclipse). Thanks! Environment: Windows Server 2008 12 Project: Jenkins Labels: teamconcert RTC, Priority: Major Reporter: bbonn 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] [s3-plugin] (JENKINS-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)
Adrian Wilke commented on JENKINS-19725 Unable to unmarshall response (Couldnt initialize a SAX driver to create an XMLReader) Had the same problem with Jenkins 1.5.80. Updated Jenkins to 1.5.90 (Kubuntu upgrade). Works now. 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] [acceptance-test-harness] (JENKINS-25576) Create a new LDAP test that runs with a real LDAP server
Bowen Cheng commented on JENKINS-25576 Create a new LDAP test that runs with a real LDAP server Following is a short summary of this contribution: A new LDAP plugin Selenium test is added (plugins/no_docker/ LdapPluginNoDockerTest.java): • Unlike the existing Selenium test which requires Dock act as a LDAP container, this one runs with real corporate LDAP server. • Necessary information required for running test (server config info, user info) can be set through command line (details is explained in Javadoc). • A new LdapEnv class is introduced to process environment variables passed from terminal. ActiveDirectryTest is refactored since the new LDAP test shares same user story. • A new method “authorizeUserAsAdmin” is extracted after refactoring. It is put in “/org/jenkinsci/test/acceptance/plugins/matrix_auth/ProjectBasedMatrixAuthorizationStrategy.java”. • This methods simply authorizes given user as admin. It is extracted as this process is common to multiple test cases and classes. • It will be cool if in the future we have methods similar to “authorizeUserAsAdmin” but in a higher abstract level (e.g. a method that authorize/ de-authorize user(s) one or multiple roles) 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-plugin] (JENKINS-24323) Could not copy slave.jar into '/users/ccfw73' on slave
John Moses commented on JENKINS-24323 Could not copy slave.jar into /users/ccfw73 on slave I had the same problem with this nonexistant /target/jenkins/WEB-INF/slave.jar file. Upgrading to jenkins 1.590 resolves the issue for me. 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] [teamconcert-plugin] (JENKINS-25762) Build Engine going inactive due to no credentials
Krishna Kishore updated JENKINS-25762 Build Engine going inactive due to no credentials Change By: Krishna Kishore (24/Nov/14 4:10 PM) Component/s: teamconcert-plugin Component/s: teamconcert-git-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep-plugin] (JENKINS-25763) Conditional steps plugin with wrong syntax parameters
Wojciech Hajduczenia created JENKINS-25763 Conditional steps plugin with wrong syntax parameters Issue Type: Bug Assignee: Dominik Bartholdi Attachments: config.PNG, execution.PNG Components: conditional-buildstep-plugin Created: 24/Nov/14 4:11 PM Description: While running the plugin and having the typo/wrong syntax in "token" field (missing " in my case), allows to execute further steps even when in advanced options of this plugin "fail the build" is set on evaluation failure (see config.png for setup example). Execution.png has the steps that are placed after the plugin that is having bad behaviour and they are executed. In my opinion there should be a syntax verification performed there, and when syntax is not correct, should fail the job at this step or at least this situation should be treated as condition evaluation failure. If i can assist with more information please let me know to improve this wonderfull tool. Thank you. Environment: RH 6.5 Project: Jenkins Labels: plugins Priority: Major Reporter: Wojciech Hajduczenia 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] [acceptance-test-harness] (JENKINS-25576) Create a new LDAP test that runs with a real LDAP server
Bowen Cheng edited a comment on JENKINS-25576 Create a new LDAP test that runs with a real LDAP server Following is a short summary of this contribution: A new LDAP plugin Selenium test is added (plugins/no_docker/ LdapPluginNoDockerTest.java): • Unlike the existing Selenium test which requires Dock act as a LDAP container, this one runs with real corporate LDAP server. • Necessary information required for running test (server config info, user info) can be set through command line (details is explained in Javadoc). • A new LdapEnv class is introduced to process environment variables passed from terminal. ActiveDirectryTest is refactored since the new LDAP test shares same user story. • A new method “authorizeUserAsAdmin” is extracted after refactoring. It is put in “/org/jenkinsci/test/acceptance/plugins/matrix_auth/ProjectBasedMatrixAuthorizationStrategy.java”. • This methods simply authorizes given user as admin. It is extracted as this process is common to multiple test cases and classes. • It will be cool if in the future we have methods similar to “authorizeUserAsAdmin” but in a higher abstract level (e.g. a method that authorize/ de-authorize user(s) one or multiple roles) 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] [promoted-builds-plugin] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Charles Mathis updated JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. Change By: Charles Mathis (24/Nov/14 4:15 PM) Description: Mybuildsareforwindowsprojects,butthisissuewouldbethecasewithanyprojectIassume.Ihaveabuildthatisusingalabel,win,whichbothwinbuilda01andwinbuilda02arelabelledwith.Sometimes,thebuildhappensonwinbuilda01:StartedbyuserCharlesMathisBuildingremotelyonwinbuilda01inworkspaced:\jenkins-slave\workspace\DeployerUsingremoteperforceclient:jenkins_deployer--667683261[...successfullybuilds...]NotifyingupstreamprojectsofjobcompletionFinished:SUCCESSButthepromotionhappensonwinbuilda02:StartedbyuserchmathisBuildingremotelyonwinbuilda02inworkspaceD:\jenkins-slave\workspace\DeployerPromotingDeployer#173[Deployer]$cmd/ccallC:\Windows\TEMP\hudson791959618011257982.bat[...unsuccessfullypromotes...]NotifyingupstreamprojectsofjobcompletionFinished:FAILUREIwouldexpectoneoftwothings:1)Ittorunthepromotiononwinbuilda01sinceitbuiltitonwinbuilda01or2)Copydownthebuildartifactstowinbuilda02sothatitcanrunthepromotionthereNeitherseemtohappen.AmImissingsomething?Oristhisabug?-Theobviousworkaroundistosetthebuildtospecificboxinsteadofalabelsothatthebuildandpromotionsjobsdonotroam,butthatdefeatsthepurposeofusingslaves.:( -11/24/2014Edit:IhavealotmoreexperiencewithJenkinsnow,soIrealizethatIshouldnotrelyonworkspacefileswhenpromoting,butratherarchivemyartifacts,andcopyartifactsfromapreviousbuildusingtheCopyArtifactsplugin.Thatway,nomatterwheremypromotionruns,itllalwayscopydowntheartifactstotheboxitrunson.Whilethatistheappropriatethingtodo,forlessexperiencedusersofJenkins,itsnotobvious,soIwouldsuggestthatthisissueisstillrelevant,butunderstandwhyitisalowerpriority.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] [promoted-builds-plugin] (JENKINS-15980) Promotion job doesn't execute on the same machine that the build job executed on.
Daniel Beck commented on JENKINS-15980 Promotion job doesnt execute on the same machine that the build job executed on. I have a lot more experience with Jenkins now, so I realize that I should not rely on workspace files when promoting It's sufficient to read the big yellow warning on https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin it could be rephrased to mention that it could also build on a different node if the original node is busy, but the recommendation is good. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Jordan Spiker commented on JENKINS-25676 Disconnect from XMPP after a few minutes All, I installed the updated Jabber plugin (1.30) and I have not had the disconnect issue since. There are a number of these warnings in the log, however: Nov 24, 2014 10:48:00 AM WARNING org.jivesoftware.smack.util.PacketParserUtils parsePresence Failed to parse extension packet in Presence packet. 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] [conditional-buildstep-plugin] (JENKINS-25763) Conditional steps plugin with wrong syntax parameters
Daniel Beck commented on JENKINS-25763 Conditional steps plugin with wrong syntax parameters The problem is that it doesn't fail to evaluate. It expects a string (to compare to a list of values that are considered to mean "true"), and a string is what it got. It's no different than not building when the value entered is foo or hello world. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Jordan Spiker commented on JENKINS-25676 Disconnect from XMPP after a few minutes Well after a half hour of working OK, Jabber disconnected in the same way as before. Please disregard my previous comment. 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-25758) NPE when triggering downstream job (again)
Daniel Beck commented on JENKINS-25758 NPE when triggering downstream job (again) This looks a lot like JENKINS-23191. Make sure the downstream project (the one with the trigger defined) has one of the result options selected. 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-plugin] (JENKINS-25754) At view overview the link to Jacoco Line Coverage results is wrong
centic resolved JENKINS-25754 as Duplicate At view overview the link to Jacoco Line Coverage results is wrong Should be fixed on master, see JENKINS-23623, will be included in next release. Change By: centic (24/Nov/14 5:20 PM) Status: Open Resolved Assignee: OgnjenBubalo centic 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-25759) FilePath.validateAntFileMask sucks up heap
dogfood commented on JENKINS-25759 FilePath.validateAntFileMask sucks up heap Integrated in jenkins_main_trunk #3833 FIXED JENKINS-25759 Avoid consuming too much memory while running validateAntFileMask. (Revision 534328b264f9338e48418d2bcc0d28daaf48b3a0) Result = SUCCESS jesse glick : 534328b264f9338e48418d2bcc0d28daaf48b3a0 Files : core/src/main/java/hudson/util/FormFieldValidator.java core/src/main/java/hudson/FilePath.java core/src/main/java/hudson/tasks/ArtifactArchiver.java core/src/test/java/hudson/FilePathTest.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ruby-runtime] (JENKINS-18528) ruby plugins cannot work on Jenkins 1.519+
ssbarnea commented on JENKINS-18528 ruby plugins cannot work on Jenkins 1.519+ Something is unclear to me, a bug still present in current release (1.583) is marked as solved with the last commend saying "will be fixed in 0.12",... and that's more than a year old This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [_test] (JENKINS-25764) Grosir Busana Muslim Terbaru Terpercaya Surabaya
obat anda created JENKINS-25764 Grosir Busana Muslim Terbaru Terpercaya Surabaya Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 24/Nov/14 5:34 PM Description: Kami Supplier Busana Muslim Terbaru Harga Grosir Terpercaya Surabaya bisa di jual lagi , dan menerima dropsip ( binis tanpa modal ) Project: Jenkins Labels: yommygrosirfashion,grosir grosir busana muslim terbaru terpercaya Priority: Minor Reporter: obat anda This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [_test] (JENKINS-25764) Grosir Busana Muslim Terbaru Terpercaya Surabaya
obat anda resolved JENKINS-25764 as Fixed Grosir Busana Muslim Terbaru Terpercaya Surabaya Change By: obat anda (24/Nov/14 5:35 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] [hockeyapp-plugin] (JENKINS-25765) Plugin does not appear as post build action or flexible publish action as of 1.2.0
Steven Shipton created JENKINS-25765 Plugin does not appear as post build action or flexible publish action as of 1.2.0 Issue Type: Bug Assignee: Unassigned Components: hockeyapp-plugin Created: 24/Nov/14 5:43 PM Description: After updating I could not find 'Upload to HockeyApp' as an option under the flexible publish action which I am currently using. Also could not find 'Upload to HockeyApp' as an option under post build actions. Downgraded to 1.1.0 and it is back. Environment: Jenkins 1.590 Project: Jenkins Priority: Major Reporter: Steven Shipton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-23594) Support git-new-workdir
Kanstantsin Shautsou commented on JENKINS-23594 Support git-new-workdir Have you tried sparse checkout or subtrees? Do you mirror this repo locally? Local git repo should have good performance. Also build must run from clean env, that means that you should fetch it every time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-23594) Support git-new-workdir
KaibutsuX Mahou commented on JENKINS-23594 Support git-new-workdir Yes, we use sparse checkout. No we do not use subtrees. Yes we mirror it locally. The performance of the repo is not what is in question. The performance is fine, the size of each directory used for the matrix configuration across multiple branches is the problem. Yes, I do not care about fetching the repo every time. Again, the problem is the amount of data being duplicated. The repo is 10GB. For every target platform in the configuration matrix and every branch that I create as a separate Jenkins project, that 10GB is doubled, tripled and so on everytime I add a new project/platform/build target. Please see: http://nuclearsquid.com/writings/git-new-workdir/ for an example of git new-workdir 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] [swarm-plugin] (JENKINS-10215) New swarm client release needed with latest slave.jar classes embedded
Kanstantsin Shautsou resolved JENKINS-10215 as Fixed New swarm client release needed with latest slave.jar classes embedded As i see latest is now included. Closing. Change By: Kanstantsin Shautsou (24/Nov/14 6:23 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] [git-plugin] (JENKINS-21896) Configurable merge message
Kanstantsin Shautsou updated JENKINS-21896 Configurable merge message Change By: Kanstantsin Shautsou (24/Nov/14 6:29 PM) Summary: Howtocustomizecommitcommentsforthepushofmergingresults Configurablemergemessage This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-17915) Tags applied by GitPublisher is not visible/registered in at build summary page (GetTagAction)
Kanstantsin Shautsou updated JENKINS-17915 Tags applied by GitPublisher is not visible/registered in at build summary page (GetTagAction) Change By: Kanstantsin Shautsou (24/Nov/14 6:32 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing-plugin] (JENKINS-21445) Job Disabled Build Slicer do not check project already disabled
Steven Christou resolved JENKINS-21445 as Fixed Job Disabled Build Slicer do not check project already disabled Issue has been fixed as part of PR-12. Change By: Steven Christou (24/Nov/14 6:32 PM) Status: Open Resolved Assignee: mdonohue StevenChristou 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] [git-plugin] (JENKINS-17915) Show applied tags on build page
Kanstantsin Shautsou updated JENKINS-17915 Show applied tags on build page Change By: Kanstantsin Shautsou (24/Nov/14 6:33 PM) Summary: Tags Show applied byGitPublisherisnotvisible/registeredinat tagson build summary page (GetTagAction) Description: TagsappliedbyGitPublisherisnotvisible/registeredinatbuildsummarypage(GetTagAction) 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-22028) HTML in job description does not get rendered (all html tags escaped)
Frank van Gemeren reopened JENKINS-22028 HTML in job description does not get rendered (all html tags escaped) I'm having the same issue on a relatively new installation. The version number is 1.590. There is only the "Escaped HTML" option in Global Security. I can't see "Safe HTML". Any ideas? Change By: Frank van Gemeren (24/Nov/14 6:55 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-25737) 'Run Parameter' build parameter is null when SCM/pre-SCM phase is started on remote-node.
Daniel Beck commented on JENKINS-25737 Run Parameter build parameter is null when SCM/pre-SCM phase is started on remote-node. I guess this needs a Perforce client to work? Unless that's a two click install, that's a bit more effort than I'm willing to spend here. However using NullSCM and breaking in checkout(...), then running build.getEnvironment(TaskListener.NULL) shows no undefined variable value. Using Jenkins ~1.591. Could you try what happens on a recent Jenkins version (current LTS or weekly)? 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-22028) HTML in job description does not get rendered (all html tags escaped)
Daniel Beck resolved JENKINS-22028 as Fixed HTML in job description does not get rendered (all html tags escaped) Make sure Antisamy Markup Formatter plugin is installed and enabled. I think the almost 20 people watching this would have noticed in the last half year if this wasn't actually fixed and mentioned it. So it's likely that, whatever it is, you're experiencing a different issue. Therefore please file a new issue if the above doesn't work for you, following the advice at https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue . Or even better, ask for troubleshooting advice on the jenkinsci-users mailing list or in IRC first. Change By: Daniel Beck (24/Nov/14 7:05 PM) Status: Reopened 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] [conditional-buildstep-plugin] (JENKINS-25763) Conditional steps plugin with wrong syntax parameters
Wojciech Hajduczenia commented on JENKINS-25763 Conditional steps plugin with wrong syntax parameters Any chances that it can evaluate if the syntax is correct or not when the first " is entered? Dont know what are the exact rulles for the syntax there but i think that when " is entered it should expect a second to close like it is in shell unless tehre is an escape character cancelling the propper usage. Sorry if i have opened this issue and took your time but i am teaching a friend from work some tricks and i did a mistake on purpose and i was suprised that the build not failed and stayed "green" and executed the tasks that were later indicated. I though that if tghe condition is not met or something is not correct with that (syntax error) it would behave like the verification failure. and would fail the job as it was indicated in the advanced option. Could use some help with configuring something like that to fail the job in case the condition is not met or syntax is wrong. 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] [jabber-plugin] (JENKINS-25505) jabber-plugin 1.28 cannot resolve host with javax.naming.NameNotFoundException: DNS name not found
Louis-Félix Tessier commented on JENKINS-25505 jabber-plugin 1.28 cannot resolve host with javax.naming.NameNotFoundException: DNS name not found Same problem here with "Jabber notifier 1.30" and "Jenkins 1.590". 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] [svnmerge-plugin] (JENKINS-25217) Do not force automatic rebase upon successfull integration to upstream
slav dok commented on JENKINS-25217 Do not force automatic rebase upon successfull integration to upstream I agree with Hugues that "rebase" after "reintegrate" is absolutely required, as per SVN documentation. However what would be nice here is an option to only do "rebase" on the feature job, without triggering the rest of the build. 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-keeper-plugin] (JENKINS-25293) Build Keeper Plugin functionality does not appear
Stuart Strickland commented on JENKINS-25293 Build Keeper Plugin functionality does not appear No comments in a month? Please tell me someone at least looked at this. Meanwhile, I have confirmed on Firefox v33.1 that this occurs there, too. I still see no way to invoke any aspect of this plugin not in a job config, not in system config, not anywhere else under Manage Jenkins, not in workspaces, dashboard, views. Am I missing something obvious? What should I expect to see, and where? I do have Token Macro 1.10 and Run Condition 1.0 plugins installed. Now Jenkins 1.590. 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-plugin] (JENKINS-25766) Rebase build action does not list/use Promotion permalinks, contrary to documentation
slav dok created JENKINS-25766 Rebase build action does not list/use Promotion permalinks, contrary to documentation Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 24/Nov/14 8:21 PM Description: In the wiki documentation, under "Automatic Rebase" section, it explicitly states ability to rebase to a point created with "Promoted Builds" permalink: Specifying the build to rebase to is a good way to control the frequency of the rebase. For example, imagine using the build promotion plugin on the trunk, and promote a build as "rebase point" about once a day (contingent on passing QA jobs.) However version 2.3 of the plugin does not list (nor let use) any Promoted Builds permalinks, it only show default "last, stable, unstable, etc, and Last Integrated" Environment: Jenkins: 1.565.3 Subversion Plug-in: 2.4.5 svnmerge plugin: 2.3 Project: Jenkins Priority: Minor Reporter: slav dok 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-plugin] (JENKINS-25334) Percentage link does not work in non-default views
centic resolved JENKINS-25334 as Duplicate Percentage link does not work in non-default views Fixed via JENKINS-23623, will be included in next release (likely 1.0.17). Change By: centic (24/Nov/14 8:23 PM) Status: Open Resolved Assignee: OgnjenBubalo centic 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-25767) Build location restrictions are not stored with 1.590
Reinhard Karbas created JENKINS-25767 Build location restrictions are not stored with 1.590 Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Nov/14 8:26 PM Description: After installing the latest version (1.590) whenever I change a job the label / build machine restriction where the job can run is no longer stored in the job definition and the job runs on master instead on the appropriate slave I had to go back to 1.588 to have my build restrictions stored and handled properly again Environment: SLES 11 SP3 Jenkins master server Project: Jenkins Labels: configuration build Priority: Blocker Reporter: Reinhard Karbas 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-25767) Build location restrictions are not stored with 1.590
Daniel Beck resolved JENKINS-25767 as Duplicate Build location restrictions are not stored with 1.590 Change By: Daniel Beck (24/Nov/14 8:29 PM) 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] [jacoco-plugin] (JENKINS-25532) java.util.zip.ZipException: invalid literal/length code in JacocoPublisher
centic commented on JENKINS-25532 java.util.zip.ZipException: invalid literal/length code in JacocoPublisher Sounds like a broken Zip/Jar file in your build-output, but can you first try with the latest version 1.0.16 of JaCoCo-plugin, I think you are running a fairly old version from 2 years ago, it might very well be fixed since then. 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-plugin] (JENKINS-23857) Coverage Breakdown by Maven Module
centic updated JENKINS-23857 Coverage Breakdown by Maven Module Change By: centic (24/Nov/14 8:31 PM) Issue Type: Bug NewFeature 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-plugin] (JENKINS-23822) Wiki page has images in German
centic commented on JENKINS-23822 Wiki page has images in German This is a nice task for someone willing to contribute, any takers? Either just update the images in the wiki or attach some to this bug-entry... 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Reinhard Karbas commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration I see the same issue after upgrading from 1.588 to 1.590 I have the same plugins in both versions and it works with 1.588 and is broken in 1.590 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-plugin] (JENKINS-19929) Code Coverage Trend graph y-axis clipped at latest max, not graph max
centic resolved JENKINS-19929 as Fixed Code Coverage Trend graph y-axis clipped at latest max, not graph max This should be fixed by commit https://github.com/jenkinsci/jacoco-plugin/commit/f685f68f4608f431ee2f39e2fb6d7b8dd8c17bd3 in version 1.0.15 of jacoco-plugin, please reopen this issue if you still see this problem with a recent version. Change By: centic (24/Nov/14 8:36 PM) Status: Open Resolved Assignee: OgnjenBubalo centic 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] [jacoco-plugin] (JENKINS-24081) [Jacoco] license missing from project
centic resolved JENKINS-24081 as Fixed [Jacoco] license missing from project The next release will include the MIT license, see commit https://github.com/jenkinsci/jacoco-plugin/commit/f2e97e90e0d90f1b57460adb0a14262f323d0705 Change By: centic (24/Nov/14 8:50 PM) Status: Open Resolved Assignee: OgnjenBubalo centic 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] [jacoco-plugin] (JENKINS-23708) Unable to view JaCoCo report and history graph
centic commented on JENKINS-23708 Unable to view JaCoCo report and history graph Wouldn't it make more sense to use "logger = System.out" in this case so that the information is at least printed to the console? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25768) Git failed to check out after the upgrade
Siva Masilamani
created JENKINS-25768
Git failed to check out after the upgrade
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git-plugin
Created:
24/Nov/14 9:12 PM
Description:
After upgrade Jenkins and GIT plugin to the latest version,the checkout process failed with the below messages and the only differences I could see is that it adds "," between branch and the commit as below.
{ C:\Softwares\Git\bin\git.exe rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
C:\Softwares\Git\bin\git.exe config remote.origin.url gitolite:testproject.git # timeout=10
Fetching upstream changes from gitolite:testproject.git
C:\Softwares\Git\bin\git.exe --version # timeout=10
C:\Softwares\Git\bin\git.exe fetch --tags --progress gitolite:testproject.git +refs/heads/:refs/remotes/origin/
C:\Softwares\Git\bin\git.exe rev-parse "origin/develop,^{commit}" # timeout=10
C:\Softwares\Git\bin\git.exe rev-parse "develop,^{commit}" # timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.}
Environment:
Jenkins-1.569
Git-Plugin 2.3
Git Client Plugin 1.11.1
Project:
Jenkins
Priority:
Major
Reporter:
Siva Masilamani
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25768) Git failed to check out after the upgrade
Siva Masilamani
updated JENKINS-25768
Git failed to check out after the upgrade
Change By:
Siva Masilamani
(24/Nov/14 9:13 PM)
Description:
After
upgrade
upgraded
JenkinsandGITplugintothelatestversion,thecheckoutprocessfailedwiththebelowmessagesandtheonlydifferencesIcouldseeisthatitadds,betweenbranchandthecommitasbelow.
{
C:\Softwares\Git\bin\git.exerev-parse--is-inside-work-tree#timeout=10FetchingchangesfromtheremoteGitrepository
C:\Softwares\Git\bin\git.execonfigremote.origin.urlgitolite:testproject.git#timeout=10Fetchingupstreamchangesfromgitolite:testproject.git
C:\Softwares\Git\bin\git.exe--version#timeout=10
C:\Softwares\Git\bin\git.exefetch--tags--progressgitolite:testproject.git+refs/heads/*:refs/remotes/origin/*
C:\Softwares\Git\bin\git.exerev-parseorigin/develop,^{commit}#timeout=10C:\Softwares\Git\bin\git.exerev-parsedevelop,^{commit}#timeout=10ERROR:Couldntfindanyrevisiontobuild.Verifytherepositoryandbranchconfigurationforthisjob.}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-25768) Git failed to check out after the upgrade
Siva Masilamani updated JENKINS-25768 Git failed to check out after the upgrade Change By: Siva Masilamani (24/Nov/14 9:14 PM) Environment: Jenkins-1.569 GITVersion:1.9.4 Git-Plugin2.3GitClientPlugin1.11.1 OS:Windows 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-plugin] (JENKINS-25769) Rebase build action cannot be triggered from Promoted Builds
slav dok created JENKINS-25769 Rebase build action cannot be triggered from Promoted Builds Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 24/Nov/14 9:28 PM Description: When executing "Rebase" action from Promoted Builds, it skips with indication that it's not an SVN project Started by user slavd Building on master in workspace D:\jobs\feature-trunk-slav-personal\workspace Promoting feature-trunk-slav-personal #68 Project does not build a Subversion feature branch. Skip rebase action. I understand that Promoted Builds don't appear like normal builds, however the "Rebase from Upstream" manual action always works on latest WORKSPACE anyways, so being able to trigger it from promotions (for reasons for checking tests/QA approval first) would be much appreciated. Environment: Jenkins: 1.565.3 Subversion Plug-in: 2.4.5 Promoted Builds Plugin: 2.18 svnmerge plugin: 2.3 Project: Jenkins Priority: Major Reporter: slav dok 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-plugin] (JENKINS-25766) Rebase build action does not list/use Promotion permalinks, contrary to documentation
slav dok
updated JENKINS-25766
Rebase build action does not list/use Promotion permalinks, contrary to documentation
Change By:
slav dok
(24/Nov/14 9:33 PM)
Description:
Inthewikidocumentation,underAutomaticRebasesection,itexplicitlystatesabilitytorebasetoapointcreatedwithPromotedBuildspermalink:{quote}Specifyingthebuildtorebasetoisagoodwaytocontrolthefrequencyoftherebase.Forexample,imagineusingthebuildpromotionpluginonthetrunk,andpromoteabuildasrebasepointaboutonceaday(contingentonpassingQAjobs.){quote}Howeverversion2.3oftheplugindoesnotlist(norletuse)anyPromotedBuildspermalinks,itonlyshowdefaultlast,stable,unstable,etc,andLastIntegrated
Pleasenotethisproblemis*only*with*BuildAction*thatispartofregularbuildsteps.ThemanualRebasefromUpstreamlinkontheleftofproject_does_showcustom/promotedbuildspermalinks.
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] [disk-usage-plugin] (JENKINS-25770) Run Disk Usage as pre-build step for every project
Manoj Thakkar updated JENKINS-25770 Run Disk Usage as pre-build step for every project Change By: Manoj Thakkar (24/Nov/14 9:32 PM) Summary: RunDiskUsageas per pre -buildstepforeveryproject Issue Type: Bug NewFeature 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] [disk-usage-plugin] (JENKINS-25770) Run Disk Usage as per-build step for every project
Manoj Thakkar created JENKINS-25770 Run Disk Usage as per-build step for every project Issue Type: Bug Assignee: Manoj Thakkar Components: disk-usage-plugin Created: 24/Nov/14 9:31 PM Description: Hi, we have faced this issue of Disk Usage running every hour on a slave, which in our and i think multiple other Project's scenario a little insufficient, We wanted to find a disk usage on a slave before an scm checkout is done and either fail a build or delete the workspace if the disk is too full, Project: Jenkins Priority: Major Reporter: Manoj Thakkar 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-25759) FilePath.validateAntFileMask sucks up heap
Jesse Glick resolved JENKINS-25759 as Fixed FilePath.validateAntFileMask sucks up heap Change By: Jesse Glick (24/Nov/14 9:46 PM) Status: InProgress 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] [jacoco-plugin] (JENKINS-19929) Code Coverage Trend graph y-axis clipped at latest max, not graph max
Mark Waite closed JENKINS-19929 as Fixed Code Coverage Trend graph y-axis clipped at latest max, not graph max Change By: Mark Waite (24/Nov/14 9:49 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
mwebber commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Can I suggest that people who have this problem give a list of the plugins that they have. 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] [core] (JENKINS-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Reinhard Karbas updated JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Change By: Reinhard Karbas (24/Nov/14 10:14 PM) Attachment: Jenkins-plugins-rk.doc 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-25533) Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration
Reinhard Karbas commented on JENKINS-25533 Restrict where this project can be run removed/disabled after Save/Apply of Job Configuration Added my list of plugins as attachment (jenkins-plugins-rk.doc) 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-flow-plugin] (JENKINS-22779) Build-Flow plugin problems in latest version (0.11.1)
Peter Kubryk commented on JENKINS-22779 Build-Flow plugin problems in latest version (0.11.1) Experiencing this issue -CloudBees Build Flow plugin 0.16 -Jenkins 1.583 Trying to use the html report plugins in a post build action 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-25742) Concurrent job rename and edit view results in deadlock that puts Jenkins in a non responsive state
Mujib Wahab commented on JENKINS-25742 Concurrent job rename and edit view results in deadlock that puts Jenkins in a non responsive state we are able to reproduce this with latest LTS 1.580.1 as well. Will test with latest release 1.590 and update the result. 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] [job-restrictions-plugin] (JENKINS-25771) Add started by a member of group JobRestriction
Christopher Suarez created JENKINS-25771 Add started by a member of group JobRestriction Issue Type: New Feature Assignee: Unassigned Components: job-restrictions-plugin Created: 25/Nov/14 12:28 AM Description: Add a job restriction based on group membership for realms that support groups. Project: Jenkins Priority: Minor Reporter: Christopher Suarez 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.
