[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title Andrei Costescu commented on JENKINS-33843 Re: It's not possible to disable/uninstall optional dependencies Great news that this is resolved. Which version will have this fixed? (I see it in Jenkins ver. 2.164.2 where I can't uninstall Static Analysis Utilities 1.96 (which has a security warning and is end-of-life) due to an optional dependency to it from Email Extension Plugin 2.66 which I still use) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41705) Unable to install bitbucket-branch-source 2.0.2 due to broken dependency
Title: Message Title Andrei Costescu commented on JENKINS-41705 Re: Unable to install bitbucket-branch-source 2.0.2 due to broken dependency Thanks. I will try that. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41705) Unable to install bitbucket-branch-source 2.0.2 due to broken dependency
Title: Message Title
Andrei Costescu edited a comment on JENKINS-41705
Re: Unable to install bitbucket-branch-source 2.0.2 due to broken dependency
I got the same problem after doing a routine upgrade last week on the standard stable jenkins 2.x build. Now it always complains in "Manage Jenkins" that:{noformat}There are dependency errors loading some plugins: GitHub Branch Source Plugin v2.0.1 SCM API Plugin v1.3 is older than required. To fix, install v2.0.2 or later.GitHub Organization Folder Plugin v1.5 GitHub Branch Source Plugin v1.9 failed to load. Fix this plugin first.{noformat}And indeed le the plugin's page lists 1.3 as latest. I can't upgrade the plugin. And can't downgrade the other plugins either nicely because they fail to load. I could manually remove the plugins from disk but I prefer waiting for a compatible version of SCM API plugin.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41705) Unable to install bitbucket-branch-source 2.0.2 due to broken dependency
Title: Message Title Andrei Costescu commented on JENKINS-41705 Re: Unable to install bitbucket-branch-source 2.0.2 due to broken dependency I got the same problem after doing a routine upgrade last week on the standard stable jenkins 2.x build. Now it always complains in "Manage Jenkins" that: There are dependency errors loading some plugins: GitHub Branch Source Plugin v2.0.1 SCM API Plugin v1.3 is older than required. To fix, install v2.0.2 or later. GitHub Organization Folder Plugin v1.5 GitHub Branch Source Plugin v1.9 failed to load. Fix this plugin first. And indeed le plugin's page lists 1.3 as latest. I can't upgrade the plugin. And can't downgrade the other plugins either nicely because they fail to load. I could manually remove the plugins from disk but I prefer waiting for a compatible version of SCM API plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13707) Job disables itself during execution, when using environment variables in repository url
Title: Message Title
Andrei Costescu edited a comment on JENKINS-13707
Re: Job disables itself during execution, when using environment variables in repository url
I got the same thing with latest 2.x Jenkins and latest SVN plugin. And yes it happens due to the fact that when checking for updates those metadata values are not defined it seems.If I look at *scm-polling.log* from my job's dir I see:{code}Location 'https://...{MD_MY_METADATA_VALUE}/...@...' does not existOne or more repository locations do not exist anymore for hudson.model.FreeStyleProject@71687255[...], project will be disabled.The project has been disabled{code}But when starting the job manually it gets updates as expected - so when starting a build it is properly defined.This happened when I was using simple metadata preset string values (exported to environment with MD_ prefix) in my job config. I fixed it by installing evnInject plugin and using *"Prepare an environment for the run"* option that I think is contributed by that plugin in the metadata section of the job config. Hope this helps other ppl. that bump into this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13707) Job disables itself during execution, when using environment variables in repository url
Title: Message Title
Andrei Costescu commented on JENKINS-13707
Re: Job disables itself during execution, when using environment variables in repository url
I got the same thing with latest 2.x Jenkins and latest SVN plugin. And yes it happens due to the fact that when checking for updates those metadata values are not defined it seems. If I look at scm-polling.log from my job's dir I see:
Location 'https://...{MD_MY_METADATA_VALUE}/...@...' does not exist
One or more repository locations do not exist anymore for hudson.model.FreeStyleProject@71687255[...], project will be disabled.
The project has been disabled
This happened when I was using simple metadata preset string values in my job config. I fixed it by installing evnInject plugin and using "Prepare an environment for the run" option that I think is contributed by that plugin in the metadata section of the job config. Hope this helps other ppl. that bump into this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13707) Job disables itself during execution, when using environment variables in repository url
Title: Message Title
Andrei Costescu edited a comment on JENKINS-13707
Re: Job disables itself during execution, when using environment variables in repository url
I got the same thing with latest 2.x Jenkins and latest SVN plugin. And yes it happens due to the fact that when checking for updates those metadata values are not defined it seems.If I look at *scm-polling.log* from my job's dir I see:{code}Location 'https://...{MD_MY_METADATA_VALUE}/...@...' does not existOne or more repository locations do not exist anymore for hudson.model.FreeStyleProject@71687255[...], project will be disabled.The project has been disabled{code} But when starting the job manually it gets updates as expected - so when starting a build it is properly defined. This happened when I was using simple metadata preset string values in my job config. I fixed it by installing evnInject plugin and using *"Prepare an environment for the run"* option that I think is contributed by that plugin in the metadata section of the job config. Hope this helps other ppl. that bump into this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27668) Add support for multiple git repositories in a single workspace
Title: Message Title Andrei Costescu commented on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace Thanks for the hint. So the pipeline basically skips all the UI for building jobs and configuring them and replaces that by using groovy scripts right? We will not move to that right now I but we might in the future. Is this ability to support multiple repos. a pipeline plugin ability or is it just based on some underlying API that the UI for configuring jobs uses as well? Cause in that case it might not be hard to add that ability there as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27668) Add support for multiple git repositories in a single workspace
Title: Message Title Andrei Costescu commented on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace Yes, but Multiple SCM plugin does need more work to not cause trouble... In some cases it doesn't work at all (generates exceptions in the defined child SCM entry plugins), in some cases it works incorrectly, in some scenarios it doesn't report changes correctly; see cases related to that plugin. I like that it exists though and I did use it for a while when I needed to combine multiple types of repos into one job (but I also did bump into these problems from time to time when using it). I still think that what MultipleSCM plugin does should be a core Jenkins feature (complete/fully operational of course) - is there a place where I can suggest this in a more official way? And then this case is no longer relevant as you could do it that way. And any other SCM plugin would only need to be implemented to handle one repo. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27668) Add support for multiple git repositories in a single workspace
Title: Message Title Andrei Costescu commented on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace I have the same problem. I need to use 3 Git repos and I don't want to configure git modules. The multiSCM plugin as it says in it's own wiki page is more a proof-of-concept currently then a fully implemented plugin. It has it's shortcommings (although I think the idea behind it should be a core feature of Jenkins) which we did hit in the past even when using SVN. Voted up. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-32728) NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)
Title: Message Title Andrei Costescu commented on JENKINS-32728 Re: NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName) I think I found an explanation. Builds that failed took > 40 min (42 min for example). And the build timeout plugin is configured at 40 min. I noticed that the builds that pass are 39m, 38m, or even some of the 40m ... (others with 40m fail) So it times out close to job's normal end time. Maybe right when sauce plugin does it's cleanup. But it's strange that I don't get notified that it timed out in the console or somewhere (in job history as usual for example). Maybe that is caused by this NPE. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-32728) NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)
Title: Message Title
Andrei Costescu updated an issue
Jenkins / JENKINS-32728
NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)
Change By:
Andrei Costescu
The job runs, all tests pass, sauce job also looks normal/success..Jenkins job reports Build Success in console and the tests reports show all passed.Even so the job is marked as a failure.I looked in the logs an I noticed this - which might be the culprit.{code}Feb 01, 2016 8:09:40 PM hudson.triggers.SafeTimerTask runSEVERE: Timer task hudson.plugins.build_timeout.BuildTimeoutWrapper$EnvironmentImpl$TimeoutTimerTask@68416dbd failedjava.lang.NullPointerExceptionat hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.getCurrentHostName(SauceOnDemandBuildWrapper.java:466)at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.access$600(SauceOnDemandBuildWrapper.java:78)at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.getHostName(SauceOnDemandBuildWrapper.java:340)at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.buildEnvVars(SauceOnDemandBuildWrapper.java:317)at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:944)at hudson.plugins.build_timeout.operations.WriteDescriptionOperation.perform(WriteDescriptionOperation.java:65)at hudson.plugins.build_timeout.BuildTimeoutWrapper$EnvironmentImpl$TimeoutTimerTask.doRun(BuildTimeoutWrapper.java:142)at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51)at java.util.TimerThread.mainLoop(Timer.java:555)at java.util.TimerThread.run(Timer.java:505)Feb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessageINFO: Decremented process count for ..., now 0Feb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessageINFO: Flushing Sauce Connect Input StreamFeb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessageINFO: Flushing Sauce Connect Error StreamFeb 01, 2016 8:12:02 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessageINFO: Closing Sauce Connect processFeb 01, 2016 8:12:06 PM com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager logMessageINFO: Sauce Connect stopped for: ...Feb 01, 2016 8:12:06 PM hudson.model.Run executeINFO: my_job #1118 main build action completed: FAILURE{code}I noticed there are newer versions which I might test, but I didn't see anything like this mentioned as fixed in the changelogs.
Add Comment
[JIRA] [sauce-ondemand-plugin] (JENKINS-32728) NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName)
Title: Message Title Andrei Costescu created an issue Jenkins / JENKINS-32728 NPE that makes a successful build get marked as failure (SauceOnDemandBuildWrapper.getCurrentHostName) Issue Type: Bug Assignee: Jack Moxon Components: sauce-ondemand-plugin Created: 02/Feb/16 1:33 PM Environment: Jenkins ver. 1.619 Sauce plugin 1.129 Priority: Minor Reporter: Andrei Costescu The job runs, all tests pass, sauce job also looks normal/success.. Jenkins job reports Build Success and the tests reports show all passed. Even so the job is marked as a failure. I looked in the logs an I noticed this - which might be the culprit. Feb 01, 2016 8:09:40 PM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.plugins.build_timeout.BuildTimeoutWrapper$EnvironmentImpl$TimeoutTimerTask@68416dbd failed java.lang.NullPointerException at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.getCurrentHostName(SauceOnDemandBuildWrapper.java:466) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.access$600(SauceOnDemandBuildWrapper.java:78) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.getHostName(SauceOnDemandBuildWrapper.java:340) at hudson.plugins.sauce_
[JIRA] [sauce-ondemand-plugin] (JENKINS-29421) NullPointerException in latest version of SauceLabs plugin
Title: Message Title Andrei Costescu commented on JENKINS-29421 Re: NullPointerException in latest version of SauceLabs plugin Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-29421) NullPointerException in latest version of SauceLabs plugin
Title: Message Title Andrei Costescu commented on JENKINS-29421 Re: NullPointerException in latest version of SauceLabs plugin Thanks for the workaround. But still I would like to leave the verbose logging on. It still happens with plugin version 1.132. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-29437) SVN no longer shows entries when used with multipleSCM plugin
Title: Message Title Andrei Costescu closed an issue as Duplicate Jenkins / JENKINS-29437 SVN no longer shows entries when used with multipleSCM plugin Change By: Andrei Costescu Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-29435) SVN no longer shows entries when used with multipleSCM plugin
Title: Message Title Andrei Costescu closed an issue as Duplicate Jenkins / JENKINS-29435 SVN no longer shows entries when used with multipleSCM plugin Change By: Andrei Costescu Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-29437) SVN no longer shows entries when used with multipleSCM plugin
Title: Message Title Andrei Costescu created an issue Jenkins / JENKINS-29437 SVN no longer shows entries when used with multipleSCM plugin Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 15/Jul/15 1:21 PM Priority: Major Reporter: Andrei Costescu See JENKINS-27674. I created this case just in case the other one doesn't get attention from the right person. Add Comment This
[JIRA] [subversion-plugin] (JENKINS-29434) SVN no longer shows entries when used with multipleSCM plugin
Title: Message Title Andrei Costescu closed an issue as Duplicate Jenkins / JENKINS-29434 SVN no longer shows entries when used with multipleSCM plugin Change By: Andrei Costescu Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-29435) SVN no longer shows entries when used with multipleSCM plugin
Title: Message Title Andrei Costescu created an issue Jenkins / JENKINS-29435 SVN no longer shows entries when used with multipleSCM plugin Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 15/Jul/15 1:18 PM Environment: Jenkins 1.619 Subversion Plug-in 2.5 Multiple SCMs plugin 0.4 Priority: Major Reporter: Andrei Costescu See JENKINS-27674. I created this case just in case the other one doesn't get attention from the right person. Add Comment
[JIRA] [subversion-plugin] (JENKINS-29434) SVN no longer shows entries when used with multipleSCM plugin
Title: Message Title Andrei Costescu updated an issue Jenkins / JENKINS-29434 SVN no longer shows entries when used with multipleSCM plugin Change By: Andrei Costescu Environment: Jenkins 1.619Subversion Plug-in 2.5Multiple SCMs plugin 0.4 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-29434) SVN no longer shows entries when used with multipleSCM plugin
Title: Message Title Andrei Costescu created an issue Jenkins / JENKINS-29434 SVN no longer shows entries when used with multipleSCM plugin Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 15/Jul/15 1:16 PM Priority: Major Reporter: Andrei Costescu See JENKINS-27674. I created this case just in case the other one doesn't get attention from the right person. Add Comment This
[JIRA] [sauce-ondemand-plugin] (JENKINS-29421) NullPointerException in latest version of SauceLabs plugin
Title: Message Title Andrei Costescu commented on JENKINS-29421 Re: NullPointerException in latest version of SauceLabs plugin What do you use? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-29421) NullPointerException in latest version of SauceLabs plugin
Title: Message Title
Andrei Costescu updated an issue
Jenkins / JENKINS-29421
NullPointerException in latest version of SauceLabs plugin
Change By:
Andrei Costescu
The plugin is unuseable after update :{noformat}Starting pre-build for Sauce Labs pluginStarting Sauce Connect on master node using identifier: defaultLaunching Sauce Connect on ip-10-197-79-50Sauce Connect 4.3.9 now launched for: xyzIncremented process count for xyz, now 1Finished pre-build for Sauce Labs pluginERROR: Build step failed with exceptionjava.lang.NullPointerException at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.buildEnvVars(SauceOnDemandBuildWrapper.java:367) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:944) at hudson.tasks.Ant.perform(Ant.java:144) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381){noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it
[JIRA] [sauce-ondemand-plugin] (JENKINS-29421) NullPointerException in latest version of SauceLabs plugin
Title: Message Title Andrei Costescu updated an issue Jenkins / JENKINS-29421 NullPointerException in latest version of SauceLabs plugin Change By: Andrei Costescu Environment: Jenkins 1.619 Sauce OnDemand plugin 1.130 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-29421) NullPointerException in latest version of SauceLabs plugin
Title: Message Title Andrei Costescu updated an issue Jenkins / JENKINS-29421 NullPointerException in latest version of SauceLabs plugin Change By: Andrei Costescu Environment: Jenkins 1.619 Sauce OnDemand plugin 1.130 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-29421) NullPointerException in latest version of SauceLabs plugin
Title: Message Title
Andrei Costescu updated an issue
Jenkins / JENKINS-29421
NullPointerException in latest version of SauceLabs plugin
Change By:
Andrei Costescu
The plugin is unuseable:{noformat}Starting pre-build for Sauce Labs pluginStarting Sauce Connect on master node using identifier: defaultLaunching Sauce Connect on ip-10-197-79-50Sauce Connect 4.3.9 now launched for: jblok xyz Incremented process count for jblok xyz , now 1Finished pre-build for Sauce Labs pluginERROR: Build step failed with exceptionjava.lang.NullPointerException at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.buildEnvVars(SauceOnDemandBuildWrapper.java:367) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:944) at hudson.tasks.Ant.perform(Ant.java:144) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381){noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from
[JIRA] [sauce-ondemand-plugin] (JENKINS-29421) NullPointerException in latest version of SauceLabs plugin
Title: Message Title Andrei Costescu created an issue Jenkins / JENKINS-29421 NullPointerException in latest version of SauceLabs plugin Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 14/Jul/15 11:37 AM Priority: Major Reporter: Andrei Costescu The plugin is unuseable: Starting pre-build for Sauce Labs plugin Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ip-10-197-79-50 Sauce Connect 4.3.9 now launched for: jblok Incremented process count for jblok, now 1 Finished pre-build for Sauce Labs plugin ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$1.buildEnvVars(SauceOnDemandBuildWrapper.java:367) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:944) at hudson.tasks.Ant.perform(Ant.java:144) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381)
[JIRA] [multiple-scms-plugin] (JENKINS-27674) Build change history is no longer displayed
Title: Message Title Andrei Costescu commented on JENKINS-27674 Re: Build change history is no longer displayed Should this be assigned to the subversion plugin or are you looking at it Kevin? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-27674) Build change history is no longer displayed
Title: Message Title Andrei Costescu updated an issue Jenkins / JENKINS-27674 Build change history is no longer displayed Change By: Andrei Costescu Component/s: subversion-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-27674) Build change history is no longer displayed
Title: Message Title Andrei Costescu commented on JENKINS-27674 Re: Build change history is no longer displayed I also have the exact same problem. Updated SVN plugin 6 days ago (had an older version), wiped out workspaces and since then everything works fine except that there are no more changes shown at all. I do not even get the exception from case description. I can send more info if needed. So: pooling log file does show a file changed job console/log does show that that file has been updated localy change log file only lists multiple SCM & all the SVN repos with no additional info so in UI it is empty: Please fix this cause it is now harder to pinpoint commits that generated regressions. (we have to correlate timestamps of build against SCM history) or look in console for each build then check history in SVN and see who committed something. Jenkins 1.619 Subversion Plug-in 2.5 Multiple SCMs plugin 0.4 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...
[JIRA] [multiple-scms-plugin] (JENKINS-26303) Not compatible with Subversion plugin 2.5
Title: Message Title Andrei Costescu commented on JENKINS-26303 Re: Not compatible with Subversion plugin 2.5 Should I reopen the issue? As far as I understand the configuration I tried should have worked (contains the fix) right? (I see all linked duplicate cases are closed now as well) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title Andrei Costescu commented on JENKINS-27708 Re: Concurrent build limits not honored on Jenkins 1.607 Dirk already created JENKINS-28376 for the new problem. Don't know how related it is in code to the current one. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title Andrei Costescu commented on JENKINS-27708 Re: Concurrent build limits not honored on Jenkins 1.607 I added my vote to it. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title Andrei Costescu commented on JENKINS-27708 Re: Concurrent build limits not honored on Jenkins 1.607 Dirk, did you find a solution to the new problem - builds not starting when they should? I didn't update Jenkins recently to avoid hitting new bugs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27708) Concurrent build limits not honored on Jenkins 1.607
Title: Message Title
Andrei Costescu commented on JENKINS-27708
Re: Concurrent build limits not honored on Jenkins 1.607
It seems to be fixed for me as well (I reported duplicate
JENKINS-28084
).
But now the same (as in above comment) happened to me multiple times: jobs get stuck from time to time in queue. Nothing else running, but they just won't start. If I cancel ('x' button) them from queue and start them again manually they do start.
I don't have a Build Blocker Plugin installed.
Can I check something more when I see this happening again to pinpoint the cause? Should we reopen or create separate bug report?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Yes, the job ran (sauce connect worked although job failed due to a test) and produced those 4.3.8 folders: (...) -rw-r--r-- 1 tomcat tomcat 3596050 Apr 30 12:17 sc-4.3-linux.tar.gz drwxr-xr-x 5 tomcat tomcat4096 Apr 30 12:17 sc-4.3.8-linux (...) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 I will. Currently some other job is running, so I'm waiting for it to run again. But the thing above is not new - I also mentioned it in case description. So you didn't introduce it now. If it behaves as in the past the /usr/share/tomcat7/sc-4.3.8-linux will appear when next sauce-using job runs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 That folder contains only: (...) -rw-r--r-- 1 tomcat tomcat 3587099 Apr 30 10:54 sc-4.3-linux.tar.gz drwxr-xr-x 5 tomcat tomcat4096 Dec 19 17:13 sc-4.3.6-linux (...) I will delete those manually - as I noticed that the plugin will then generate the sc-4.3.8-linux it needs. Will you please fix this problem as well? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 I updated to 1.128. I get this error now: Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ip-10-197-79-50 FATAL: java.io.IOException: Cannot run program "/usr/share/tomcat7/sc-4.3.8-linux/bin/sc" (in directory "/usr/share/tomcat7/sc-4.3.8-linux"): error=2, No such file or directory com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectException: java.io.IOException: Cannot run program "/usr/share/tomcat7/sc-4.3.8-linux/bin/sc" (in directory "/usr/share/tomcat7/sc-4.3.8-linux"): error=2, No such file or directory at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:358) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:819) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279) at hudson.model.Build$BuildExecution.doRun(Build.java:156) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1744) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.io.IOException: Cannot run program "/usr/share/tomcat7/sc-4.3.8-linux/bin/sc" (in directory "/usr/share/tomcat7/sc-4.3.8-linux"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:286) ... 8 more Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:135) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022) ... 9 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu edited a comment on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Thank you. I will update and let you know in case I still see it (hopefully not). How long does it take for me to see the new version? (still 1.127 is latest on plugin wiki page and in Jenkins config) I think the plugin's build itself is failing. Maybe that's why Jenkins doesn't show the update. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu edited a comment on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Thank you. I will update and let you know in case I still see it (hopefully not). How long does it take for me to see the new version? (still 1.127 is latest on plugin wiki page and in Jenkins config) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Thank you. I will update and let you know in case I still see it (hopefully not). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-28084) One per node / One per total Category still allows multiple concurrent builds (regression)
Andrei Costescu commented on JENKINS-28084 One per node / One per total Category still allows multiple concurrent builds (regression) I just updated. I will reopen if I notice it again. 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] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Meanwhile I found out why my two jobs were starting at the same time: https://issues.jenkins-ci.org/browse/JENKINS-28084 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu edited a comment on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Meanwhile I found out why my two jobs were starting at the same time: https://issues.jenkins-ci.org/browse/JENKINS-28084 It seems Jenkins core had a problem that affected the Throttle Concurrent Builds 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] [throttle-concurrent-builds-plugin] (JENKINS-28084) One per node / One per total Category still allows multiple concurrent builds (regression)
Andrei Costescu created JENKINS-28084 One per node / One per total Category still allows multiple concurrent builds (regression) Issue Type: Bug Assignee: Oleg Nenashev Components: throttle-concurrent-builds-plugin Created: 24/Apr/15 11:45 AM Description: Many times when someone manually schedules a job to execute it will end up executing multiple builds of jobs that are in the same Category (limited to 1 per node and 1 in total) concurrently. I have a single Jenkins server, no slaves, and a setup like this: Job A - triggered by Git updates, part of category X Job B - triggered by A on success, part of category X Job C,D - triggered by A on success, part of category Y Job E - triggered by timer, part of category X When Git updates trigger Job A and while A is running I manually schedule Job E to run (both are part of category X that allows only 1 concurrent build), then Job E waits for A to finish as expected. But when A is done successfully then Jobs B, C, D and E start all at the same time. Problem is the B and E are part of category X as well so they should never run at the same time. I didn't see this before recently upgrading all plugins and Jenkins. Environment: Jenkins 1.608 Throttle Concurrent Builds Plugin 1.8.4 Project: Jenkins Priority: Major Reporter: Andrei Costescu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu edited a comment on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 I had no browser selected. Explained in description why. Indeed the above were from version 1.113 where it also happened once immediately after downgrade (probably because of a 'sc ' process). Anyway here it is from when I had it running with 1.125, then it started to fail again: At 16:34 there was a successful run of the job. At 18:34 the tests failed because of a problem with our app. server not starting and thus the unit tests could not connect to it; unit tests connect of 2 min timed out and the job failed. At 19:14:35 I now see two jobs started simultaneously (one by a timer the other by a colleague manually starting it in the same second)! One succeeded and one failed with that error in console "Process count non-zero, but no active tunnels found - Process count reset to zero - FATAL: Unable to start Sauce Connect, please see the Sauce Connect log" That should not have been possible as the 2 jobs are configured to be mutually exclusive (using another plugin for that) and never saw them run at the same time before even if I started them both manually one after the other. But anyway it still shouldn't make sauce plugin non-functional for all future jobs... All future jobs failed until I downgraded and killed processes. 20150410 163455.234 [01966] Sauce Connect 4.3.8, build 1671 0fa40e2 20150410 163455.235 [01966] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt. 20150410 163455.235 [01966] *** WARNING: open file limit 4096 is too low! 20150410 163455.235 [01966] *** Sauce Labs recommends setting it to at least 8000. 20150410 163455.235 [01966] Trying to autodetect proxy settings 20150410 163455.235 [01966] Starting up; pid 1966 20150410 163455.235 [01966] Command line arguments: /usr/share/tomcat7/sc-4.3.8-linux/bin/sc -u *** -k -P 4445 20150410 163455.236 [01966] Using no proxy for connecting to Sauce Labs REST API. 20150410 163455.237 [01966] Resolving saucelabs.com to 162.222.73.28 took 1 ms. 20150410 163456.140 [01966] PROXY *** scproxy started *** 20150410 163456.141 [01966] PROXY found DNS server 172.16.0.23 20150410 163456.190 [01966] Started scproxy on port 46880. 20150410 163456.190 [01966] Please wait for 'you may start your tests' to start your tests. 20150410 163456.190 [01966] Starting secure remote tunnel VM... 20150410 163502.660 [01966] Secure remote tunnel VM provisioned. 20150410 163502.660 [01966] Tunnel ID: fa3516d6947745628480895860b3bb18 20150410 163503.576 [01966] Secure remote tunnel VM is now: booting 20150410 163513.145 [01966] Secure remote tunnel VM is now: running 20150410 163513.145 [01966] Remote tunnel host is: maki77078.miso.saucelabs.com 20150410 163513.145 [01966] Using no proxy for connecting to tunnel VM. 20150410 163513.166 [01966] Resolving maki77078.miso.saucelabs.com to 162.222.77.78 took 21 ms. 20150410 163513.166 [01966] Starting Selenium listener... 20150410 163513.167 [01966] Establishing secure TLS connection to tunnel... 20150410 163513.167 [01966] [EVDNS] Added nameserver 172.16.0.23:53 as 0x7f44b0004c70 20150410 163513.168 [01966] Selenium listener started on port 4445. 20150410 163513.363 [01966] MAIN connecting to KGP server 162.222.77.78 took 195 ms 20150410 163513.365 [01966] MAIN warning, failed to set KGP bufferevent priority to 0 20150410 163516.378 [01966] Sauce Connect is up, you may start your tests. 20150410 163516.378 [01966] Connection established. 20150410 163724.106 [01966] PROXY resolved 'localhost' to '127.0.0.1' (...) many many PROXY lines when running tests (...) 20150410 164056.602 [01966] PROXY 127.0.0.1:48955 <- 200 localhost:8089 (196 bytes) 20150410 164101.193 [01966] Cleaning up. 20150410 164102.171 [01966] Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy 20150410 164102.171 [01966] Overlapping domain: sauce-connect.proxy, shutting down tunnel fa3516d6947745628480895860b3bb18. 20150410 164109.020 [01966] KGP warning: no keepalive ack for > 5s 20150410 164109.424 [01966] Goodbye. 20150410 183415.744 [09736] Sauce Connect 4.3.8, build 1671 0fa40e2 20150410 183415.745 [09736] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt. 20150410 183415.745 [09736] *** WARNING: open file limit 4096 is too low! 20150410 183415.745 [09736] *** Sauce Labs recommends setting it to at least 8000. 20150410 183415.745 [09736] Trying to autodetect proxy settings 2015
[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Np. I'm glad you are looking at it . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 I had no browser selected. Explained in description why. Indeed the above were from version 1.113 where it also happened once immediately after downgrade (probably because of a 'sc ' process). Anyway here it is from when I had it running with 1.125, then it started to fail again: At 16:34 there was a successful run of the job. At 18:34 the tests failed because of a problem with our app. server not starting and thus the unit tests could not connect to it; unit tests connect of 2 min timed out and the job failed. At 19:14:35 I now see two jobs started simultaneously (one by a timer the other by a colleague manually starting it in the same second)! One succeeded and one failed with that error in console "Process count non-zero, but no active tunnels found - Process count reset to zero - FATAL: Unable to start Sauce Connect, please see the Sauce Connect log" That should have been possible as the 2 jobs are configured to be mutually exclusive (using another plugin for that) and never saw them run at the same time before even if I started them both manually one after the other. But anyway it still shouldn't make sauce plugin non-functional for all future jobs... All future jobs failed until I downgraded and killed processes. 20150410 163455.234 [01966] Sauce Connect 4.3.8, build 1671 0fa40e2 20150410 163455.235 [01966] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt. 20150410 163455.235 [01966] *** WARNING: open file limit 4096 is too low! 20150410 163455.235 [01966] *** Sauce Labs recommends setting it to at least 8000. 20150410 163455.235 [01966] Trying to autodetect proxy settings 20150410 163455.235 [01966] Starting up; pid 1966 20150410 163455.235 [01966] Command line arguments: /usr/share/tomcat7/sc-4.3.8-linux/bin/sc -u *** -k -P 4445 20150410 163455.236 [01966] Using no proxy for connecting to Sauce Labs REST API. 20150410 163455.237 [01966] Resolving saucelabs.com to 162.222.73.28 took 1 ms. 20150410 163456.140 [01966] PROXY *** scproxy started *** 20150410 163456.141 [01966] PROXY found DNS server 172.16.0.23 20150410 163456.190 [01966] Started scproxy on port 46880. 20150410 163456.190 [01966] Please wait for 'you may start your tests' to start your tests. 20150410 163456.190 [01966] Starting secure remote tunnel VM... 20150410 163502.660 [01966] Secure remote tunnel VM provisioned. 20150410 163502.660 [01966] Tunnel ID: fa3516d6947745628480895860b3bb18 20150410 163503.576 [01966] Secure remote tunnel VM is now: booting 20150410 163513.145 [01966] Secure remote tunnel VM is now: running 20150410 163513.145 [01966] Remote tunnel host is: maki77078.miso.saucelabs.com 20150410 163513.145 [01966] Using no proxy for connecting to tunnel VM. 20150410 163513.166 [01966] Resolving maki77078.miso.saucelabs.com to 162.222.77.78 took 21 ms. 20150410 163513.166 [01966] Starting Selenium listener... 20150410 163513.167 [01966] Establishing secure TLS connection to tunnel... 20150410 163513.167 [01966] [EVDNS] Added nameserver 172.16.0.23:53 as 0x7f44b0004c70 20150410 163513.168 [01966] Selenium listener started on port 4445. 20150410 163513.363 [01966] MAIN connecting to KGP server 162.222.77.78 took 195 ms 20150410 163513.365 [01966] MAIN warning, failed to set KGP bufferevent priority to 0 20150410 163516.378 [01966] Sauce Connect is up, you may start your tests. 20150410 163516.378 [01966] Connection established. 20150410 163724.106 [01966] PROXY resolved 'localhost' to '127.0.0.1' (...) many many PROXY lines when running tests (...) 20150410 164056.602 [01966] PROXY 127.0.0.1:48955 <- 200 localhost:8089 (196 bytes) 20150410 164101.193 [01966] Cleaning up. 20150410 164102.171 [01966] Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy 20150410 164102.171 [01966] Overlapping domain: sauce-connect.proxy, shutting down tunnel fa3516d6947745628480895860b3bb18. 20150410 164109.020 [01966] KGP warning: no keepalive ack for > 5s 20150410 164109.424 [01966] Goodbye. 20150410 183415.744 [09736] Sauce Connect 4.3.8, build 1671 0fa40e2 20150410 183415.745 [09736] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt. 20150410 183415.745 [09736] *** WARNING: open file limit 4096 is too low! 20150410 183415.745 [09736] *** Sauce Labs recommends setting it to at least 8000. 20150410 183415.745 [09736] Trying to autodetect proxy settings 20150410 1834
[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 /tmp/sc.log confirms what I though This is the content when a job that doesn't leave hanging sc processes ends: (...) 20150415 221730.677 [19514] PROXY 127.0.0.1:33135 <- 200 localhost:8081 (196 bytes) 20150415 221736.064 [19514] Cleaning up. 20150415 221741.999 [19514] Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy 20150415 221741.999 [19514] Overlapping domain: sauce-connect.proxy, shutting down tunnel e66ea3aead4a4656b725fd4b99ccc66c. 20150415 221746.686 [19514] Goodbye. (...) This is the content when a job that does leave hanging sc processes ends (any following job using sauce plugin will fail): (...) 20150416 113808.029 [00744] PROXY 127.0.0.1:51525 <- 200 localhost:8081 (196 bytes) 20150416 113816.646 [00744] Cleaning up. (...) So I think that is what causes the whole problem - no Goodbye.. The following jobs will fail with: (...) 20150416 121716.618 [07153] Sauce Connect 4.3.6, build 1628 8a5c837 20150416 121716.618 [07153] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt. 20150416 121716.618 [07153] Warning, open file limit 4096 is too low. 20150416 121716.618 [07153] Sauce Labs recommends setting it to at least 8000. 20150416 121716.618 [07153] Trying to autodetect proxy settings 20150416 121716.618 [07153] can't lock pidfile /tmp/sc_client.pid. Please check if Sauce Connect is already running. 20150416 121716.618 [07153] Error creating pidfile /tmp/sc_client.pid. (...) All jobs that pass show in console the same (so both the job that leaves processes behind and the one that is ok): (...) Shutting down Sauce Connect Decremented process count for ***, now 0 Flushing Sauce Connect Input Stream Flushing Sauce Connect Error Stream Closing Sauce Connect process Sauce Connect stopped for: *** (...) We fixed meanwhile the open file limit warning and we will try to run Jenkins with newer java version (1.6.x was used before). Although those are probably not the causes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu updated JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Change By: Andrei Costescu (16/Apr/15 9:00 AM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu edited a comment on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Each time I kill the hanging processes, first job succeeds then the following ones fail and 'sc' processes linger around. I restarted the server completely, then asked 3 sauce jobs to run (which ended up in the build queue waiting to finish one by one). Even though only the first job was running there were two 'sc' processes running. Second and third job failed as above and now Jenkins is stale - but 'sc' processes still linger around. Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on *** Process count non-zero, but no active tunnels found Process count reset to zero FATAL: Unable to start Sauce Connect, please see the Sauce Connect log com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Unable to start Sauce Connect, please see the Sauce Connect log at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:308) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:819) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279) at hudson.model.Build$BuildExecution.doRun(Build.java:154) (...) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125
Andrei Costescu commented on JENKINS-27884 Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125 Each time I kill the hanging processes, first job succeeds then the following ones fail and 'sc' progesses linger around. I restarted the server completely, then asked 3 sauce jobs to run (which ended up in the build queue waiting to finish one by one). Even though only the first job was running there were two 'sc' processes running. Second and third job failed as above and now Jenkins is stale - but 'sc' processes still linger around. Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on *** Process count non-zero, but no active tunnels found Process count reset to zero FATAL: Unable to start Sauce Connect, please see the Sauce Connect log com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Unable to start Sauce Connect, please see the Sauce Connect log at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:308) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:819) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279) at hudson.model.Build$BuildExecution.doRun(Build.java:154) (...) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25411) With latest updates, sauce-ondemand no longer works; gives an error
Andrei Costescu commented on JENKINS-25411 With latest updates, sauce-ondemand no longer works; gives an error Yw. And thanks for fixing it . I will try the new version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25411) With latest updates, sauce-ondemand no longer works; gives an error
Andrei Costescu commented on JENKINS-25411 With latest updates, sauce-ondemand no longer works; gives an error Update: the same thing happened, it runs once then that 0 byte file re-appears magically. And the second time the job runs the exception is back. I added for now a job that just deletes that file after the main job runs for now as a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25411) With latest updates, sauce-ondemand no longer works; gives an error
Andrei Costescu commented on JENKINS-25411 With latest updates, sauce-ondemand no longer works; gives an error Update: since sauce connect plugin was emptying the file, I thought - why don't I delete it? Maybe it tries to do that and fails somehow. After I manually deleted /usr/share/tomcat7/sc-4.3-linux.tar.gz, exception went away and now it says 'connected'. Tests still fail because of a timeout but we will have to see if it's still a sauce connect tunnel problem or not, cause it can also be caused by our app. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25411) With latest updates, sauce-ondemand no longer works; gives an error
Andrei Costescu updated JENKINS-25411 With latest updates, sauce-ondemand no longer works; gives an error Change By: Andrei Costescu (03/Nov/14 10:28 AM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25411) With latest updates, sauce-ondemand no longer works; gives an error
Andrei Costescu created JENKINS-25411 With latest updates, sauce-ondemand no longer works; gives an error Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 03/Nov/14 10:26 AM Description: We also tried downloading and putting correct tar.gz file in that location but the first time the plugin tries to start sauce connect it will overwrite it and set it back to size 0. Btw. problem seems to be that the file exists but with size 0. Starting Sauce Connect on master node using identifier: default Launching Sauce Connect on ip-10-74-140-248 FATAL: Error while expanding /usr/share/tomcat7/sc-4.3-linux.tar.gz org.codehaus.plexus.archiver.ArchiverException: Error while expanding /usr/share/tomcat7/sc-4.3-linux.tar.gz at org.codehaus.plexus.archiver.tar.TarUnArchiver.execute(TarUnArchiver.java:101) at org.codehaus.plexus.archiver.AbstractUnArchiver.extract(AbstractUnArchiver.java:120) at com.saucelabs.ci.sauceconnect.SauceConnectFourManager.untarGzFile(SauceConnectFourManager.java:209) at com.saucelabs.ci.sauceconnect.SauceConnectFourManager.extractZipFile(SauceConnectFourManager.java:194) at com.saucelabs.ci.sauceconnect.SauceConnectFourManager.createProcessBuilder(SauceConnectFourManager.java:142) at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:266) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:710) at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:236) at hudson.model.Build$BuildExecution.doRun(Build.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.io.EOFException at java.util.zip.GZIPInputStream.readUByte(GZIPInputStream.java:246) at java.util.zip.GZIPInputStream.readUShort(GZIPInputStream.java:236) at java.util.zip.GZIPInputStream.readHeader(GZIPInputStream.java:140) at java.util.zip.GZIPInputStream.(GZIPInputStream.java:56) at java.util.zip.GZIPInputStream.(GZIPInputStream.java:65) at org.codehaus.plexus.archiver.tar.TarUnArchiver$UntarCompressionMethod.decompress(TarUnArchiver.java:191) at org.codehaus.plexus.archiver.tar.TarUnArchiver$UntarCompressionMethod.access$000(TarUnArchiver.java:112) at org.codehaus.plexus.archiver.tar.TarUnArchiver.execute(TarUnArchiver.java:86) ... 13 more Unfortunately we cannot downgrade further to avoid this. (maybe it would work if we also downgraded Jenkins, don't know) Environment: Sauce OnDemand plugin 1.104 Jenkins 1.587 Project: Jenkins Priority: Minor Reporter: Andrei Costescu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-25179) Starting with OpenID 2.1.1, Google auth. requires you to accept jenkins to access your data at each login
Andrei Costescu created JENKINS-25179 Starting with OpenID 2.1.1, Google auth. requires you to accept jenkins to access your data at each login Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: openid Created: 16/Oct/14 9:29 AM Description: When I installed openID 2.1.1, after Google login screen, Google asks if it should allow Jenkins to access your account data - each time. It should only as once. After downgrading to openID plugin to 2.1, it started to work again as expected. Login just logs in, doesn't require extra steps each time. Environment: Jenkins 1.584 but the same happened with earlier version Project: Jenkins Priority: Minor Reporter: Andrei Costescu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-25179) Starting with OpenID 2.1.1, Google auth. requires you to accept jenkins to access your data at each login
Andrei Costescu commented on JENKINS-25179 Starting with OpenID 2.1.1, Google auth. requires you to accept jenkins to access your data at each login Jenkins is deployed as war inside a Tomcat server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-6545) JUnit report parsing cannot handle nested suites
Andrei Costescu commented on JENKINS-6545 JUnit report parsing cannot handle nested suites Actually I found one but not very useful for Jenkins (the eclipse jUnit results view has an Export in a menu that will generate such xml). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-6545) JUnit report parsing cannot handle nested suites
Andrei Costescu edited a comment on JENKINS-6545 JUnit report parsing cannot handle nested suites Actually I found one but not very useful for Jenkins (the eclipse jUnit results view has an Export in a menu that will generate such xml). So I need one that can be used in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-6545) JUnit report parsing cannot handle nested suites
Andrei Costescu edited a comment on JENKINS-6545 JUnit report parsing cannot handle nested suites Actually I found one but not very useful for Jenkins (the eclipse jUnit results view has an Export in a menu that will generate such xml). So I need on that can be used in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-6545) JUnit report parsing cannot handle nested suites
Andrei Costescu commented on JENKINS-6545 JUnit report parsing cannot handle nested suites I've been searching for a while for a tool that would generate this kind of nested report for JUnit. Did any of you actually have such a nested report xml generated from nested JUnit tests suites (either 3.x or 4.x)? Or it it only generated by other testing frameworks? For example ant xml formatter flattens test suites, doesn't keep nesting. Maven surefire does the same. Even tried TestNG wrapped around JUnit with the same result. (junit 4.11 (used 3 like style and 4 like style), testNG 6.8, ant 1.9.4, maven-surefire-plugin 2.17) So which is the test runner that would generate such a nested report for a nested JUnit suite? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20804) showDependencies for ${CHANGES} doesn't seem to work
Andrei Costescu
commented on JENKINS-20804
showDependencies for ${CHANGES} doesn't seem to work
Ok, I'll try it out.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20804) [Email ext plugin] showDependencies for ${CHANGES} doesn't seem to work
Andrei Costescu
commented on JENKINS-20804
[Email ext plugin] showDependencies for ${CHANGES} doesn't seem to work
Thanks for checking.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20804) [Email ext plugin] showDependencies for ${CHANGES} doesn't seem to work
Andrei Costescu
updated JENKINS-20804
[Email ext plugin] showDependencies for ${CHANGES} doesn't seem to work
Change By:
Andrei Costescu
(28/Nov/13 9:26 AM)
Description:
I'm using the email-ext plugin and it works great except for this problem with "showDependencies".This is how I use it (I only use global configs for all jobs in email-ext, just triggers are set per job):${CHANGES, showPaths=true, showDependencies=true}I have a 'build' project A that triggers 'unit test' project B, C and D. B, C and D are shown as "Downstream Projects" on project A's "Status" page.B and C are started by standard "Build other projects" post-build action of A.D is started by "Build other projects (extended)" post-build action of A if Build result is "Equal or over SUCCESS" and with "Trigger only if downstream project has SCM changes" - that is available due to https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, version 2.21.When project B fails due to a change in project A's SCM, in the email I don't see the commits from project A that resulted in this failure, although "showDependencies" is true.Did I misunderstand what "showDependencies"
it's mean
is meant
for or misused it? If that's not its purpose, then please consider this a feature req. to add the ability to have the changes from A above in email.Thanks.BTW: from token docs, it seems to me that you can't use "showDependencies" with ${CHANGES_SINCE_LAST_SUCCESS}, just with ${CHANGES}. Is that true? Cause that would be exactly what I 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20804) [Email ext plugin] showDependencies for ${CHANGES} doesn't seem to work
Andrei Costescu
updated JENKINS-20804
[Email ext plugin] showDependencies for ${CHANGES} doesn't seem to work
Change By:
Andrei Costescu
(28/Nov/13 9:25 AM)
Description:
I'm using the email-ext plugin and it works great except for this problem with "showDependencies".This is how I use it (I only use global configs for all jobs in email-ext, just triggers are set per job):${CHANGES, showPaths=true, showDependencies=true}I have a 'build' project A that triggers 'unit test' project B, C and D. B, C and D are shown as "Downstream Projects" on project A's "Status" page.B and C are started by standard "Build other projects" post-build action of A.D is started by "Build other projects (extended)" post-build action of A if Build result is "Equal or over SUCCESS" and with "Trigger only if downstream project has SCM changes" - that is available due to https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, version 2.21.When project B fails due to a change in project A's SCM, in the email I don't see the commits from project A that resulted in this failure, although "showDependencies" is true.Did I misunderstand what "showDependencies" it's mean for or misused it? If that's not
it
its
purpose, then please consider this a feature req. to add the ability to have the changes from A above in email.Thanks.BTW: from token docs, it seems to me that you can't use "showDependencies" with ${CHANGES_SINCE_LAST_SUCCESS}, just with ${CHANGES}. Is that true? Cause that would be exactly what I 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20804) [Email ext plugin] showDependencies for ${CHANGES} doesn't seem to work
Andrei Costescu
created JENKINS-20804
[Email ext plugin] showDependencies for ${CHANGES} doesn't seem to work
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Components:
email-ext
Created:
28/Nov/13 9:23 AM
Description:
I'm using the email-ext plugin and it works great except for this problem with "showDependencies".
This is how I use it (I only use global configs for all jobs in email-ext, just triggers are set per job):
${CHANGES, showPaths=true, showDependencies=true}
I have a 'build' project A that triggers 'unit test' project B, C and D. B, C and D are shown as "Downstream Projects" on project A's "Status" page.
B and C are started by standard "Build other projects" post-build action of A.
D is started by "Build other projects (extended)" post-build action of A if Build result is "Equal or over SUCCESS" and with "Trigger only if downstream project has SCM changes" - that is available due to https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, version 2.21.
When project B fails due to a change in project A's SCM, in the email I don't see the commits from project A that resulted in this failure, although "showDependencies" is true.
Did I misunderstand what "showDependencies" it's mean for or misused it? If that's not it purpose, then please consider this a feature req. to add the ability to have the changes from A above in email.
Thanks.
BTW: from token docs, it seems to me that you can't use "showDependencies" with ${CHANGES_SINCE_LAST_SUCCESS}, just with ${CHANGES}. Is that true? Cause that would be exactly what I want.
Environment:
Jenkins 1.541
email-ext 2.36
Project:
Jenkins
Labels:
email-ext
plugin
scm
Priority:
Major
Reporter:
Andrei Costescu
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
