[JIRA] [core] (JENKINS-30655) Remoting blocks when the slave disconnects during copying files
Title: Message Title
ikedam commented on JENKINS-30655
Re: Remoting blocks when the slave disconnects during copying files
Does that mean no additional logs are output even after click the abort button ("x" button) ?
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-30655) Remoting blocks when the slave disconnects during copying files
Title: Message Title JY Hsu commented on JENKINS-30655 Re: Remoting blocks when the slave disconnects during copying files I don't see the problem if I manually disconnect the slave. It looks like the problem happens when the slave doesn't disconnect, but instead have network problem. Or it is not related to network at all, just that the copy somehow went into a deadlock. 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] [copyartifact-plugin] (JENKINS-30357) CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build
Title: Message Title ikedam closed an issue as Fixed Fixed in copyartifact-1.36.1. It will be available in the update center in a day. Please try that. Jenkins / JENKINS-30357 CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build Change By: ikedam Status: Resolved Closed 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-30655) Remoting blocks when the slave disconnects during copying files
Title: Message Title ikedam commented on JENKINS-30655 Re: Remoting blocks when the slave disconnects during copying files Jenkins CopyArtifact remoting Disconnect the slave 1.554.3 1.33 2.36 Build fails 1.565.3 1.33 2.46 Build sometimes hangs 1.580.3 1.33 2.47 Build always hangs
[JIRA] [core] (JENKINS-30655) Remoting blocks when the slave disconnects during copying files
Title: Message Title JY Hsu commented on JENKINS-30655 Re: Remoting blocks when the slave disconnects during copying files Started by upstream project "LCMI20.0 Test Step" build number 69 originally caused by: Started by upstream project "LCMI20.0 Pipeline" build number 85 originally caused by: Started by upstream project "LCMI20.0 Start Pipeline" build number 105 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on IC_Mac_01 in workspace /Users/Automation/Jenkins/workspace/LCMI_UnitTest Deleting project workspace... done [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Injecting as environment variables the properties content XCTOOL=/Users/automation/xctool BUILD_HOME=/Users/automation/Jenkins/workspace/LCMI_UnitTest/B_LCMI20.0_Connections.test/buildartifacts [EnvInject] - Variables injected successfully. Build timed out (after 10 minutes). Marking the build as aborted. Build timed out (after 10 minutes). Marking the build as failed. I have no access to the master machine, so I can only provide the job log 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] [copyartifact-plugin] (JENKINS-29488) Fix findbugs issue in copyartifact-plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29488 Re: Fix findbugs issue in copyartifact-plugin Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/BuildSelectorParameter.java http://jenkins-ci.org/commit/copyartifact-plugin/a495c486c3d2f8ed2d931db64e90b4f69c11fcc2 Log: JENKINS-29488 Fixed findbugs issues. 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] [copyartifact-plugin] (JENKINS-30357) CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30357 Re: CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/ParameterizedBuildSelectorTest.java http://jenkins-ci.org/commit/copyartifact-plugin/d7df521bde6fe4dae57ad16c962e1957435b70e1 Log: JENKINS-30357 Fixed failing tests. 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] [copyartifact-plugin] (JENKINS-30357) CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30357 CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-30357) CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30357 Re: CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/ParameterizedBuildSelector.java src/test/java/hudson/plugins/copyartifact/ParameterizedBuildSelectorTest.java http://jenkins-ci.org/commit/copyartifact-plugin/4e6cb78a2226ffe238a25ddfa788866c8cb4f131 Log: [FIXED JENKINS-30357] Improved error handlings in ParameterizedBuildSelector. 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] [copyartifact-plugin] (JENKINS-30357) CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30357 Re: CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build Code changed in jenkins User: ikedam Path: src/test/java/hudson/plugins/copyartifact/ParameterizedBuildSelectorTest.java http://jenkins-ci.org/commit/copyartifact-plugin/bab56aae014bf259755fdb3d966dac0be35382b3 Log: JENKINS-30357 Added tests to reproduce JENKINS-30357 , NPE when ParameterizedBuildSelector in workflow, or using an undefined variable. 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] [copyartifact-plugin] (JENKINS-30357) CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30357 Re: CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java src/main/java/hudson/plugins/copyartifact/ParameterizedBuildSelector.java http://jenkins-ci.org/commit/copyartifact-plugin/6ddc88a0e0609bde83d8aecbd90170f254cc8fcf Log: JENKINS-30357 Fixed NPE when using ParameterizedBuildSelector in Workflow or using undefined variables in ParameterizedBuildSelector. 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] [copyartifact-plugin] (JENKINS-30357) CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30357 Re: CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/CopyArtifact.java src/main/java/hudson/plugins/copyartifact/ParameterizedBuildSelector.java src/main/resources/hudson/plugins/copyartifact/ParameterizedBuildSelector/help-parameterName.html src/test/java/hudson/plugins/copyartifact/ParameterizedBuildSelectorTest.java http://jenkins-ci.org/commit/copyartifact-plugin/b72f3f9c95d656ff72ead97ffce7e94684d38571 Log: Merge pull request #70 from ikedam/feature/ JENKINS-30357 _NpeInParameterizedBuildSelector JENKINS-30357 Fixed NPE and other improvements in ParameterizedBuildSelector Compare: https://github.com/jenkinsci/copyartifact-plugin/compare/f4946461e5f4...b72f3f9c95d6 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] [copyartifact-plugin] (JENKINS-30357) CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-30357
Re: CopyArtifact step fails when using ParameterizedBuildSelector class for selecting build
Code changed in jenkins User: ikedam Path: src/main/java/hudson/plugins/copyartifact/ParameterizedBuildSelector.java src/main/resources/hudson/plugins/copyartifact/ParameterizedBuildSelector/help-parameterName.html src/test/java/hudson/plugins/copyartifact/ParameterizedBuildSelectorTest.java http://jenkins-ci.org/commit/copyartifact-plugin/43699c2f605172202f228d627a4cb329dc95f984 Log:
JENKINS-30357
Extends ParameterizedBuildSelector to also accepts immediate values () and variable expressions ($ {SELECTOR}
).
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-29876) NPE when triggering downstream job
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-29876 NPE when triggering downstream job Change By: Kanstantsin Shautsou Labels: lts-candidate trigger 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-29876) NPE when triggering downstream job
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-29876 NPE when triggering downstream job Change By: Oleg Nenashev Labels: lts-candidate trigger 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] [remoting] (JENKINS-5703) Exception leaves zombie processes for slaves started by command on master
Title: Message Title
Ben Walding edited a comment on JENKINS-5703
Re: Exception leaves zombie processes for slaves started by command on master
Even though I've done zero investigation into this - my initial thought would be that the slave *should* actually be launched with an exec in there:{noformat}bash -c 'ssh localhost "cd ~/localhost; exec java -jar ~/localhost/slave.jar"'{noformat}This can be tested by setting the advanced "JavaPath" setting to "exec java" (or whatever java executable you are using).!javapath. jpg png |thumbnail!{noformat:title=Process list without exec}ubuntu 22426 bash -c cd "/home/jenkins-slave" && java -jar slave.jarubuntu 22427 java -jar slave.jar{noformat}{noformat:title=Process list with exec}ubuntu 22905 java -jar slave.jar{noformat}Will this fix it? No idea, but having extra processes in the process chain is often a cause for failed signal handling and zombie processes.
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] [remoting] (JENKINS-5703) Exception leaves zombie processes for slaves started by command on master
Title: Message Title
Ben Walding edited a comment on JENKINS-5703
Re: Exception leaves zombie processes for slaves started by command on master
Even though I've done zero investigation into this - my initial thought would be that the slave *should* actually be launched with an exec in there:{noformat}bash -c 'ssh localhost "cd ~/localhost; exec java -jar ~/localhost/slave.jar"'{noformat}This can be tested by setting the advanced "JavaPath" setting to "exec java" (or whatever java executable you are using).!javapath.png |thumbnail !{noformat:title=Process list without exec}ubuntu 22426 bash -c cd "/home/jenkins-slave" && java -jar slave.jarubuntu 22427 java -jar slave.jar{noformat}{noformat:title=Process list with exec}ubuntu 22905 java -jar slave.jar{noformat}Will this fix it? No idea, but having extra processes in the process chain is often a cause for failed signal handling and zombie processes.
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] [remoting] (JENKINS-5703) Exception leaves zombie processes for slaves started by command on master
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-5703 Exception leaves zombie processes for slaves started by command on master Change By: Ben Walding Attachment: javapath.png 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] [remoting] (JENKINS-5703) Exception leaves zombie processes for slaves started by command on master
Title: Message Title
Ben Walding edited a comment on JENKINS-5703
Re: Exception leaves zombie processes for slaves started by command on master
Even though I've done zero investigation into this - my initial thought would be that the slave *should* actually be launched with an exec in there:{noformat}bash -c 'ssh localhost "cd ~/localhost; exec java -jar ~/localhost/slave.jar"'{noformat}This can be tested by setting the advanced " java JavaPath " config setting to "exec java" (or whatever java executable you are using). !javapath.jpg|thumbnail! {noformat:title=Process list without exec}ubuntu 22426 bash -c cd "/home/jenkins-slave" && java -jar slave.jarubuntu 22427 java -jar slave.jar{noformat}{noformat:title=Process list with exec}ubuntu 22905 java -jar slave.jar{noformat}Will this fix it? No idea, but having extra processes in the process chain is often a cause for failed signal handling and zombie processes.
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] [remoting] (JENKINS-5703) Exception leaves zombie processes for slaves started by command on master
Title: Message Title Ben Walding commented on JENKINS-5703 Re: Exception leaves zombie processes for slaves started by command on master Even though I've done zero investigation into this - my initial thought would be that the slave should actually be launched with an exec in there: bash -c 'ssh localhost "cd ~/localhost; exec java -jar ~/localhost/slave.jar"' This can be tested by setting the advanced "java" config to "exec java" (or whatever java executable you are using). Process list without exec ubuntu 22426 bash -c cd "/home/jenkins-slave" && java -jar slave.jar ubuntu 22427 java -jar slave.jar Process list with exec ubuntu 22905 java -jar slave.jar Will this fix it? No idea, but having extra processes in the process chain is often a cause for failed signal handling and zombie processes. 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] [multiple-scms-plugin] (JENKINS-30145) NPE on rendering a job page that uses MultipleSCM for "Polling Log" action
Title: Message Title Kanstantsin Shautsou resolved as Fixed Should be fixed on newest cores. Jenkins / JENKINS-30145 NPE on rendering a job page that uses MultipleSCM for "Polling Log" action Change By: Kanstantsin Shautsou Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [literate] (JENKINS-30780) Natively support project embedded plugin, build, continuous delivery configuration
Title: Message Title Levon Karayan created an issue Jenkins / JENKINS-30780 Natively support project embedded plugin, build, continuous delivery configuration Issue Type: Improvement Assignee: stephenconnolly Components: literate Created: 03/Oct/15 9:40 PM Labels: 2.0 Priority: Minor Reporter: Levon Karayan Jenkin's is primarily configured via web ui. an evolved approach is to bundle the instructions/configurations with the project. Similar to: https://docs.saucelabs.com/ci-integrations/travis-ci/ https://wiki.jenkins-ci.org/display/JENKINS/Literate+Plugin http://www.yegor256.com/2014/07/24/rultor-automated-merging.html Once the build is configured, there should be an oportuntiy to supplement & override any functionality from the project embedded config file for additional features or for purposes of secu
[JIRA] [core] (JENKINS-29078) hudson.triggers.Trigger$Cron doRun throwing a NullPointerException
Title: Message Title Kanstantsin Shautsou commented on JENKINS-29078 Re: hudson.triggers.Trigger$Cron doRun throwing a NullPointerException Tony Finn what you describe sounds like other issue that already fixed. Chin Boon Oh without knowing what/when/who inserted null in triggers it impossible to reproduce. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-30779) I need a way to configure blocking behavior for different jobs
Title: Message Title rlagoue updated an issue Jenkins / JENKINS-30779 I need a way to configure blocking behavior for different jobs Change By: rlagoue Summary: I need a way to configure blocking behavior for different job jobs 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] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Stéphane Este-Gracias commented on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error Issue fixed by following this article: i.e. adding a "/" at the end of the webhook definition in Bitbucket console. https://confluence.atlassian.com/display/BBKB/Webhooks+return+error+code+500+with+Jenkins 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] [jclouds-jenkins] (JENKINS-28815) Providing nodes by "Image name" always works as by "Image ID"
Title: Message Title Fritz Elfert commented on JENKINS-28815 Re: Providing nodes by "Image name" always works as by "Image ID" Hi, Actually, this is a caching bug in jclouds. I just issued https://github.com/jenkinsci/jclouds-plugin/pull/104 which circumvents jcloud's image cache. Cheers -Fritz 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-29876) NPE when triggering downstream job
Title: Message Title dogfood commented on JENKINS-29876 Re: NPE when triggering downstream job Integrated in jenkins_main_trunk #4300 [FIXED JENKINS-29876] CheckForNull job in ReverseBuildTrigger (Revision 45e4e990269325ba1f8bca25959ff8dcaa21f398) Result = SUCCESS kanstantsin.sha : 45e4e990269325ba1f8bca25959ff8dcaa21f398 Files : test/src/test/java/jenkins/triggers/ReverseBuildTriggerTest.java core/src/main/java/jenkins/triggers/ReverseBuildTrigger.java 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] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title
Stéphane Este-Gracias edited a comment on JENKINS-29096
Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
I'm using Git repository. I just pushed a single commit.I've created a logger dedicated to "com.cloudbees.jenkins.plugins.BitbucketHookReceiver" and the only log I have is following{noformat}Oct 03, 2015 8:09:08 PM FINE com.cloudbees.jenkins.plugins.BitbucketHookReceiver Received commit hook notification : {noformat}The full log is following{noformat}Oct 03, 2015 8:09:08 PM org.eclipse.jetty.util.log.JavaUtilLog warnWARNING: Error while serving https:// jenkins.bikemike.mobi /bitbucket-hook/java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:165) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.Http
[JIRA] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title
Stéphane Este-Gracias edited a comment on JENKINS-29096
Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
I had a look on the plugin repository, the log that I found is here :{noformat}LOGGER.fine("Received commit hook notification : " + body);{noformat}It seems that the plugin only receives an empty body.After doing a tcpdump on my server, I found that the received payload is a valid JSON (trace logs are behind nginx with SSL support).{noformat}POST /bitbucket-hook HTTP/1.1Host: jenkins.bikemike.mobi X-Real-IP: 131.103.20.165X-Forwarded-For: 131.103.20.165X-Forwarded-Proto: httpsConnection: closeContent-Length: 5586Accept-Encoding: gzip, deflateAccept: */*X-Event-Key: repo:pushUser-Agent: Bitbucket-Webhooks/2.0X-Hook-UUID: 502882a9-696b-40ac-a75d-ed8ccc564794Content-Type: application/json{ }{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, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title
Stéphane Este-Gracias commented on JENKINS-29096
Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
I had a look on the plugin repository, the log that I found is here :
LOGGER.fine("Received commit hook notification : " + body);
It seems that the plugin only receives an empty body.
After doing a tcpdump on my server, I found that the received payload is a valid JSON (trace logs are behind nginx with SSL support).
POST /bitbucket-hook HTTP/1.1
Host: jenkins.bikemike.mobi
X-Real-IP: 131.103.20.165
X-Forwarded-For: 131.103.20.165
X-Forwarded-Proto: https
Connection: close
Content-Length: 5586
Accept-Encoding: gzip, deflate
Accept: */*
X-Event-Key: repo:push
User-Agent: Bitbucket-Webhooks/2.0
X-Hook-UUID: 502882a9-696b-40ac-a75d-ed8ccc564794
Content-Type: application/json
{ }
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] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Stéphane Este-Gracias commented on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error See corresponding nginx logs 131.103.20.165 - - [03/Oct/2015:20:09:08 +] "POST /bitbucket-hook HTTP/1.1" 302 5 "-" "Bitbucket-Webhooks/2.0" 131.103.20.165 - - [03/Oct/2015:20:09:08 +] "GET /bitbucket-hook/ HTTP/1.1" 500 3892 "-" "Bitbucket-Webhooks/2.0" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Stéphane Este-Gracias commented on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error I'm using Git repository. I just pushed a single commit. I've created a logger dedicated to "com.cloudbees.jenkins.plugins.BitbucketHookReceiver" and the only log I have is following Oct 03, 2015 8:09:08 PM FINE com.cloudbees.jenkins.plugins.BitbucketHookReceiver Received commit hook notification : The full log is following Oct 03, 2015 8:09:08 PM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: Error while serving https://jenkins.bikemike.mobi/bitbucket-hook/ java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:165) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(Rem
[JIRA] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Félix Belzunce Arcos edited a comment on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error [~seenukarthi] [~sestegra] Would you mind to post the exactly stacktrace you are getting? Are you just pushing to BitBucket? Maybe you are doing something special like merging branches?* Can you activate the logger for com.cloudbees.jenkins.plugins.BitbucketHookReceiver? You can do this in http:///jenkins/log/ * Are you using a mercurial repo? 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-29876) NPE when triggering downstream job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29876 Re: NPE when triggering downstream job Code changed in jenkins User: Kanstantsin Shautsou Path: core/src/main/java/jenkins/triggers/ReverseBuildTrigger.java test/src/test/java/jenkins/triggers/ReverseBuildTriggerTest.java http://jenkins-ci.org/commit/jenkins/45e4e990269325ba1f8bca25959ff8dcaa21f398 Log: [FIXED JENKINS-29876] CheckForNull job in ReverseBuildTrigger 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-29876) NPE when triggering downstream job
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-29876 NPE when triggering downstream job Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29876 Re: NPE when triggering downstream job Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/jenkins/triggers/ReverseBuildTrigger.java test/src/test/java/jenkins/triggers/ReverseBuildTriggerTest.java http://jenkins-ci.org/commit/jenkins/339dd4ace545187d04a65bedea44b215fd11ba39 Log: Merge pull request #1842 from KostyaSha/patch-3 [FIXED JENKINS-29876] CheckForNull job in ReverseBuildTrigger Compare: https://github.com/jenkinsci/jenkins/compare/5e2b15426118...339dd4ace545 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-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-30502 Unable to delete project with trailing whitespace in name Change By: Christopher Simons Assignee: Christopher Simons 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] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Félix Belzunce Arcos edited a comment on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error [~seenukarthi] [~sestegra] Would you mind to post the exactly stacktrace you are getting? Are you just pushing to BitBucket? Maybe you are doing something special like merging branches? * Can you activate the logger for com.cloudbees.jenkins.plugins.BitbucketHookReceiver? You can do this in http:///jenkins/log/ 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] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Félix Belzunce Arcos commented on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error Karthikeyan Vaithilingam Stéphane Este-Gracias Would you mind to post the exactly stacktrace you are getting? Are you just pushing to BitBucket? Maybe you are doing something special like merging branches? 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] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Stéphane Este-Gracias commented on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error My first installation of the Bitbucket plugin was the version 1.1.2. I've never installed this plugin before. I deleted the folder and restarted the jenkins instance. Unfortunately, the same issue still occurs. 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] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Karthikeyan Vaithilingam commented on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error Deleted the folder FOLDER $JENKINS_HOME/plugins/bitbucket and restarted the jenkins instance still the issue persists. 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] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Félix Belzunce Arcos edited a comment on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error [~ nde sestegra ] This issue should be fixed in 1.1.2Please, delete the FOLDER $JENKINS_HOME/plugins/bitbucket and restart the instance so the plugin can be re-extracted 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] [bitbucket-plugin] (JENKINS-29096) Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error
Title: Message Title Félix Belzunce Arcos commented on JENKINS-29096 Re: Bitbucket Plugin unable to parse Bitbucket webhook JSONObject error Andreas Esterle This issue should be fixed in 1.1.2 Please, delete the FOLDER $JENKINS_HOME/plugins/bitbucket and restart the instance so the plugin can be re-extracted 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-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov edited a comment on JENKINS-30719
Re: cannot specify ${something} string in parameters
Excuse me for stupid explanation. Here's the hypothetical scenario:1. you have a parameter `VERSION` in the job config2. you want to also configure in a parameter that will have as a value literal {noformat} `something_${VERSION}_something` {noformat} How is it possible to prevent the string in the second parameter to be expanded? I don't currently have that exact use case. But I thought it is possible to escape the `$` character such that variables are not expanded.
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-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov edited a comment on JENKINS-30719
Re: cannot specify ${something} string in parameters
Excuse me for stupid explanation. Here's the hypothetical scenario:1. you have a parameter `VERSION` in the job config2. you want to also configure in a parameter that will have as a value literal `something_${VERSION}_something`How is it possible to prevent the {code}${VERSION}{code} string in the second parameter to be expanded? I don't currently have that exact use case. But I thought it is possible to escape the `$` character such that variables are not expanded.
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-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov edited a comment on JENKINS-30719
Re: cannot specify ${something} string in parameters
Excuse me for stupid explanation. Here's the hypothetical scenario:1. you have a parameter `VERSION` in the job config2. you want to also configure in a parameter that will have as a value literal `something_${VERSION}_something`How is it possible to prevent the ` {code:java} ${VERSION} ` {code} string in the second parameter to be expanded? I don't currently have that exact use case. But I thought it is possible to escape the `$` character such that variables are not expanded.
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-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov edited a comment on JENKINS-30719
Re: cannot specify ${something} string in parameters
Excuse me for stupid explanation. Here's the hypothetical scenario:1. you have a parameter `VERSION` in the job config2. you want to also configure in a parameter that will have as a value literal `something_${VERSION}_something`How is it possible to prevent the{code :java }${VERSION}{code}string in the second parameter to be expanded? I don't currently have that exact use case. But I thought it is possible to escape the `$` character such that variables are not expanded.
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-30719) cannot specify ${something} string in parameters
Title: Message Title
akostadinov commented on JENKINS-30719
Re: cannot specify ${something} string in parameters
Excuse me for stupid explanation. Here's the hypothetical scenario: 1. you have a parameter `VERSION` in the job config 2. you want to also configure in a parameter that will have as a value literal `something_$ {VERSION}_something` How is it possible to prevent the `${VERSION}
` string in the second parameter to be expanded? I don't currently have that exact use case. But I thought it is possible to escape the `$` character such that variables are not expanded.
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] [build-blocker-plugin] (JENKINS-30779) I need a way to configure blocking behavior for different job
Title: Message Title rlagoue created an issue Jenkins / JENKINS-30779 I need a way to configure blocking behavior for different job Issue Type: New Feature Assignee: Unassigned Components: build-blocker-plugin Created: 03/Oct/15 4:39 PM Priority: Major Reporter: rlagoue Let's assume I have a job A, that needs to be blocked when 2 jobs (B and C) are running. for B: the blocking should be global for C: the blocking should be node based. It would be nice to configure it with your plugin. Thank you Add Comment
[JIRA] [sauce-ondemand-plugin] (JENKINS-30778) Sauce Labs Test Publisher Configuration
Title: Message Title
Alex G. updated an issue
Jenkins / JENKINS-30778
Sauce Labs Test Publisher Configuration
Change By:
Alex G.
I'm using TestNG (also tried JUnit) to run tests in Sauce Labs cloud. In order to update the pass/fail status of those tests in Sauce Labs once they done, I added the "Run Sauce Labs Test Publisher" post-build action to my Jenkins build.First of all, the documentation isn't even clear about how this integration must be configured. This is what it says: "In addition, you will need to output the following line *{color:red}to your {color}* for each test that is run using Sauce Labs: SauceOnDemandSessionID=YOUR_SESSION_ID job-name=YOUR_JOB_NAME." What does that mean? *To your what?*Based on source code, I figured there has to be tag in the Surefire XML Report, the content of which must be that line. But that doesn't make much sense, because those tags are only generated when an error happens. Also no matter what I've tried, I just could couldn't make Surefire/TestNG output that tag into the report at all. Not even when test failed.I'm either not understanding something (probably) or this way of configuring things is messed up.Last few lines of my log:Starting post-build for Sauce Labs pluginFinished post-build for Sauce Labs pluginRecording test resultsStarting Sauce Labs test publisherFinished Sauce Labs test publisherStarting Sauce Labs test publisherFinished Sauce Labs test publisher
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 "Jenk
[JIRA] [sauce-ondemand-plugin] (JENKINS-30778) Sauce Labs Test Publisher Configuration
Title: Message Title Alex G. created an issue Jenkins / JENKINS-30778 Sauce Labs Test Publisher Configuration Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 03/Oct/15 4:00 PM Labels: plugin configuration Priority: Major Reporter: Alex G. I'm using TestNG (also tried JUnit) to run tests in Sauce Labs cloud. In order to update the pass/fail status of those tests in Sauce Labs once they done, I added the "Run Sauce Labs Test Publisher" post-build action to my Jenkins build. First of all, the documentation isn't even clear about how this integration must be configured. This is what it says: "In addition, you will need to output the following line to your for each test that is run using Sauce Labs: SauceOnDemandSessionID=YOUR_SESSION_ID job-name=YOUR_JOB_NAME." What does that mean? To your what? Based on source code, I figured there has to be tag in the Surefire XML Report, the content of which must be that line. But that doesn't make much sense, because those tags are only generated when an error happens. Also no matter what I've tried, I just could make Surefire/TestNG output that tag into the report at all. Not even when test failed. I'm either not understanding something (probably) or this way of configuring th
[JIRA] [git-plugin] (JENKINS-27998) Git plugin fails to clone with ssh protected passphrase
Title: Message Title Mark Waite resolved as Duplicate Dejay Clayton comments on his investigation are in JENKINS-20879 Jenkins / JENKINS-27998 Git plugin fails to clone with ssh protected passphrase Change By: Mark Waite Status: Reopened Resolved 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] [ssh-credentials-plugin] (JENKINS-20638) SSH key credential doesn't work with key passphrase
Title: Message Title Mark Waite resolved as Duplicate Dejay Clayton comments on his investigation are in JENKINS-20879 Jenkins / JENKINS-20638 SSH key credential doesn't work with key passphrase Change By: Mark Waite Status: Reopened Resolved 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] [git-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Mark Waite commented on JENKINS-20879 Re: SSH Credentials (private key with passphrase) do not work Dejay Clayton Thanks for reporting your further results. I'm glad it started working for you. I suspect there may be some ordering dependencies which are made visible on the first connection between a slave and the ssh process of the server repository. At least that's why I think my Docker instance fails and my main Ubuntu machine succeeds. My main Ubuntu machine has already communicated with the ssh daemon on each of my internal slaves that I use for tests, while the Docker instance is seeing the ssh connection for the very first time. I won't be able to investigate further this weekend, but hope to continue studying this further in the future. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-30755) GIT Plugin doesn't respect GIT_HOME or PATH
Title: Message Title Mark Waite edited a comment on JENKINS-30755 Re: GIT Plugin doesn't respect GIT_HOME or PATH I compiled and installed git 2.6.0 on my Debian 6 machine (with --prefix=/usr/local) and on my CentOS 6 machine (with --prefix=/opt/git-2.6.0) and then inserted those git locations into the "Tool Locations" for each of those nodes. Then I ran tests which required at least git 1.7.10. The tests passed and the console log showed that the git executable I had declared was being used in the job.Screen shots of my configuration of the two machines are attached in case they help you see where I configured the git location. I think the way I've configured it is closer to the way the original support for non-standard locations was intended to be used. Can you try that configuration method instead of attempting to adjust the PATH environment variable? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-30755) GIT Plugin doesn't respect GIT_HOME or PATH
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-30755 GIT Plugin doesn't respect GIT_HOME or PATH Change By: Mark Waite Attachment: debian-6-non-standard-git-location.png Attachment: CentOS-non-standard-git-location.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-30755) GIT Plugin doesn't respect GIT_HOME or PATH
Title: Message Title Mark Waite commented on JENKINS-30755 Re: GIT Plugin doesn't respect GIT_HOME or PATH I compiled and installed git 2.6.0 on my Debian 6 machine (with --prefix=/usr/local) and on my CentOS 6 machine (with --prefix=/opt/git-2.6.0) and then inserted those git locations into the "Tool Locations" for each of those nodes. Then I ran tests which required at least git 1.7.10. The tests passed and the console log showed that the git executable I had declared was being used in the job. Screen shots of my configuration of the two machines are attached in case they help you see where I configured the git location. 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] [tap-plugin] (JENKINS-24843) TAP Test Results Summary page shows 0ms for total even though there are non-zero durations
Title: Message Title Bruno P. Kinoshita commented on JENKINS-24843 Re: TAP Test Results Summary page shows 0ms for total even though there are non-zero durations Actually, I was looking at an older job I think. Investigating why the total is not the sum of the time of all the tests. 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] [svnmerge-plugin] (JENKINS-30769) Rebase commit message should be configurable
Title: Message Title Andre Lopes commented on JENKINS-30769 Re: Rebase commit message should be configurable I will try to contribute this change. Just wanted to open the improvement so that others can provide their insights. 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-30719) cannot specify ${something} string in parameters
Title: Message Title
Oliver Gondža commented on JENKINS-30719
Re: cannot specify ${something} string in parameters
I am not sure I follow. When do you want it to be replaced, if ever? When it is being replaced? If you do not escape at all.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [stashnotifier-plugin] (JENKINS-28480) Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)
Title: Message Title Pavel Batanov commented on JENKINS-28480 Re: Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge) Looks like you unchecked "Keep repeated builds in Stash" after the first build has happen. Unfortunately this will not remove builds performed while option was checked. For now you have to options. First is manually mark first build as successfull via the same REST API. Second is just make a dummy commit which will reset builds. "Keep repeated builds in Stash" internally just adds the build number from the build key, so then unchecked new bulds overwrite each other and then cheked new build state is created each time instead. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
