[JIRA] (JENKINS-50287) Make as-it-is checkout only files initally
Title: Message Title Slawomir Czarko commented on JENKINS-50287 Re: Make as-it-is checkout only files initally The way I have been using as-it-is so far is by doing a full checkout first then running my own script which was pruning the working copy using svn up --set-depth. Starting with 'files' as depth is not good enough for that case since the script I use for pruning the working copy is in a subdirectory. What is the reason for this change in behaviour of as-it-is? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-50839) Repository depth 'as-it-is' is broken in 2.10.5, it works as depth 'files'
Title: Message Title Slawomir Czarko created an issue Jenkins / JENKINS-50839 Repository depth 'as-it-is' is broken in 2.10.5, it works as depth 'files' Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: subversion-plugin Created: 2018-04-17 09:34 Environment: Jenkins version 2.107.2 LTS Subversion plugin 2.10.5 Priority: Blocker Reporter: Slawomir Czarko After upgrading subversion-plugin from 2.10.3 to 2.10.5 all my builds broke. I'm using depth 'as-it-is' and now the builds behave as if depth was set to 'files' which results in a very incomplete checkout. Downgrading back to 2.10.3 restores the previous, correct behaviour. Add Comment
[JIRA] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems
Title: Message Title Slawomir Czarko commented on JENKINS-26318 Re: Subversion Plug in 2.5 causes sporadic problems .hpi file works with Jenkins as well. Btw, I stopped using this plug-in altogether about half a year ago. I don't remember what was the exact reason but it was still causing problems even with the patches. 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] [slave-squatter-plugin] (JENKINS-7667) Build waits for next available executor even if several are available
Title: Message Title Slawomir Czarko commented on JENKINS-7667 Re: Build waits for next available executor even if several are available It is still happening with fully updated LTS version. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-33095) Upgrade to folder 5.2.1 + matrix-auth 1.3 results in dead Jenkins
Title: Message Title Slawomir Czarko commented on JENKINS-33095 Re: Upgrade to folder 5.2.1 + matrix-auth 1.3 results in dead Jenkins Matrix Auth 1.3.2 does NOT automatically pull in CloudBees Folders Plugin. Installing CloudBees Folders Plugin manually solves the problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-32970) groovy templates do not work after upgrading from 2.40.5 to 2.41
Title: Message Title Slawomir Czarko commented on JENKINS-32970 Re: groovy templates do not work after upgrading from 2.40.5 to 2.41 Downgrading plugin to 2.40.5 makes it work again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-32970) groovy templates do not work after upgrading from 2.40.5 to 2.41
Title: Message Title
Slawomir Czarko created an issue
Jenkins / JENKINS-32970
groovy templates do not work after upgrading from 2.40.5 to 2.41
Issue Type:
Bug
Assignee:
Alex Earl
Components:
email-ext-plugin
Created:
16/Feb/16 8:34 AM
Environment:
Jenkins LTS 1.642.1 Email Extension Plugin 2.41
Priority:
Major
Reporter:
Slawomir Czarko
After upgrading to 2.41 version of the plugin, I get this error (in the mail body):
Groovy Template file [groovy-html.template] was not found in $JENKINS_HOME/email-templates.
I have in the default content:
$ {SCRIPT, template="groovy-html.template"}
$ {BUILD_LOG_EXCERPT,start="^--BEGIN--$",end="^--END--$"}
[JIRA] [blamesubversion-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems
Title: Message Title Slawomir Czarko commented on JENKINS-26318 Re: Subversion Plug in 2.5 causes sporadic problems pull request Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-label-assignment-plugin] (JENKINS-32175) Add option to run groovy script from a file
Title: Message Title Slawomir Czarko created an issue Jenkins / JENKINS-32175 Add option to run groovy script from a file Issue Type: Improvement Assignee: Unassigned Components: groovy-label-assignment-plugin Created: 22/Dec/15 6:11 PM Priority: Minor Reporter: Slawomir Czarko It would be good to have an option to use a groovy script saved in a file. Add Comment This message was sent by Atlassian
[JIRA] [doxygen-plugin] (JENKINS-29938) Unable to serialize is reported when publishing doxygen generate html files
Title: Message Title Slawomir Czarko resolved as Fixed Fixed in Doxygen-plugin 0.18 Jenkins / JENKINS-29938 Unable to serialize is reported when publishing doxygen generate html files Change By: Slawomir Czarko 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] [subversion-plugin] (JENKINS-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title Slawomir Czarko commented on JENKINS-31520 Re: SVN_* variables are not available in build script if variable is used in SVN url @recena config.xml is configured using the option which does work: "Prepare an environment for the run" option from EnvInject Plugin What does not work is this one: "Inject environment variables" option from EnvInject Plugin with "Run buildstep before SCM runs" option from Pre SCM BuildStep Plugin In both cases Subversion Plugin is able to checkout code correctly but in one case SVN_* variables are set and in the other one they're not. 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-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title Slawomir Czarko commented on JENKINS-31520 Re: SVN_* variables are not available in build script if variable is used in SVN url Manuel Jesús Recena Soto I don't know in which plugin there's a bug. What confuses me is that Subversion Plugin resolves USE_VER variable when a job runs more than once and results change in the middle of the run. When checking out code the variable is resolved correctly regardless if Pre SCM BuildStep Plugin is used or not. But when creating SVN_* variables the results depend on whether Pre SCM BuildStep Plugin is used. In my opinion it would be less confusing if resolving USE_VER variable failed or succeeded consistently in a given build. 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-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title
Slawomir Czarko commented on JENKINS-31520
Re: SVN_* variables are not available in build script if variable is used in SVN url
Manuel Jesús Recena Soto I'm using SVN URL http://svn.apache.org/repos/asf/pivot/trunk@$USE_VER
Instructions follow.
Jenkins configuration:
Jenkins LTS Jenkins LTS 1.625.2
Subversion Plugin - 2.5.4
Environment Injector Plugin - 1.92.1
Pre SCM BuildStep Plugin - 0.3
Setting up job:
add SVN module with:
Repository URL http://svn.apache.org/repos/asf/pivot/trunk@$USE_VER
Repository depth: empty
Local module directory: trunk
Ignore externals: selected
in Build Environment section tick "Run buildstep before SCM runs" then click "Add Build Step" in this section and select "Inject environment variables", in "Properties Content" enter: USE_VER=1713807
in Build section click "Add Build Step" and select "Execute shell", in "Command" enter: #!/bin/bash { set | grep -e SVN -e USE_VER ; }
|| true
Run job and check the Console Output. The relevant output starts with SVN checkout:
Checking out a fresh workspace because /jenkins/workspace/problem/trunk doesn't exist Cleaning local Directory trunk Checking out http://svn.apache.org/repos/asf/pivot/trunk@1713807 at revision 1713807 U . At revision 1713807 no change for http://svn.apache.org/repos/asf/pivot/trunk since the previous build [problem] $ /bin/bash /tmp/hudson1386748194641801585.sh USE_VER=1713807 Notifying upstream projects of job completion Finished: SUCCESS
What I expect though is this output (lines starting with SVN_ are missing from the above output):
Checking out a fresh workspace because /jenkins/workspace/problem/trunk doesn't exist Cleaning local
[JIRA] [subversion-plugin] (JENKINS-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title
Slawomir Czarko edited a comment on JENKINS-31520
Re: SVN_* variables are not available in build script if variable is used in SVN url
[~recena] {noformat} http://svn.apache.org/repos/asf/pivot/trunk/@${USE_VER} {noformat} also works
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-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title
Slawomir Czarko commented on JENKINS-31520
Re: SVN_* variables are not available in build script if variable is used in SVN url
Manuel Jesús Recena Soto
http://svn.apache.org/repos/asf/pivot/trunk/@${USE_VER}
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-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title Slawomir Czarko edited a comment on JENKINS-31520 Re: SVN_* variables are not available in build script if variable is used in SVN url @ [~ recena ] config.xml is configured using the option which does work:* "Prepare an environment for the run" option from EnvInject PluginWhat does not work is this one:* "Inject environment variables" option from EnvInject Plugin with "Run buildstep before SCM runs" option from Pre SCM BuildStep PluginIn both cases Subversion Plugin is able to checkout code correctly but in one case SVN_* variables are set and in the other one they're not. 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-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title Slawomir Czarko commented on JENKINS-31520 Re: SVN_* variables are not available in build script if variable is used in SVN url Manuel Jesús Recena Soto Can you attach/paste config.xml? 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-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title Slawomir Czarko commented on JENKINS-31520 Re: SVN_* variables are not available in build script if variable is used in SVN url Manuel Jesús Recena Soto I need Pre SCM BuildStep Plugin since in my actual job I'm running a system groovy script (on master) to determine the value of USE_VER. I can try to convert the script so it doesn't need to run as system groovy script. 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-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title Slawomir Czarko commented on JENKINS-31520 Re: SVN_* variables are not available in build script if variable is used in SVN url Manuel Jesús Recena Soto I've found a configuration which works with Pre SCM BuildStep Plugin If you set USE_VAR as node environment variable to 1 then you can set USE_VER to the correct value using Pre SCM BuildStep Plugin and SVN_* variables will be set correctly. Console output: [EnvInject] - Loading node environment variables. Building remotely on slave in workspace /jenkins/workspace/problem Running Prebuild steps [problem] $ /bin/sh -xe /tmp/hudson3358871213827210249.sh + echo 'Node environment variable USE_VER=1' Node environment variable USE_VER=1 Success build forhudson.tasks.Shell@70916cc9 [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties content USE_VER=1712454 [EnvInject] - Variables injected successfully. Success build fororg.jenkinsci.plugins.envinject.EnvInjectBuilder@5b7d39db Updating http://svn.apache.org/repos/asf/pivot/trunk@1712454 at revision 1712454 At revision 1712454 no change for http://svn.apache.org/repos/asf/pivot/trunk since the previous build [problem] $ /bin/bash /tmp/hudson989831158393201234.sh SVN_REVISION=1712454 SVN_REVISION_1=1712454 SVN_URL=http://svn.apache.org/repos/asf/pivot/trunk SVN_URL_1=http://svn.apache.org/repos/asf/pivot/trunk USE_VER=1712454 Notifying upstream projects of job completion Finished: SUCCESS If USE_VER is set as node environment variable with non-numeric value it doesn't work as before. This makes me think this might be a problem with EnvInject 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
[JIRA] [envinject-plugin] (JENKINS-31602) EnvInject Plugin doesn't work correctly with combination of Subversion Plugin and Pre SCM BuildStep Plugin
Title: Message Title Slawomir Czarko created an issue Jenkins / JENKINS-31602 EnvInject Plugin doesn't work correctly with combination of Subversion Plugin and Pre SCM BuildStep Plugin Issue Type: Bug Assignee: Oleg Nenashev Attachments: config.xml-bad, config.xml-good, consoleText-bad, consoleText-good Components: envinject-plugin Created: 17/Nov/15 3:21 PM Environment: Jenkins LTS 1.625.2 OS - CentOS 7.1 Subversion Plugin - 2.5.4 EnvInject Plugin - 1.92.1 Pre SCM BuildStep Plugin - 0.3 Priority: Minor Reporter: Slawomir Czarko If I add a Build Step "Inject environment variables" in the section which appears after clicking "Run buildstep before SCM runs" in order to inject environment variable USE_VER then "Subversion plugin" will not set SVN_* environment variables. Job configuration config.xml-bad Console output consoleText-bad This works fine also if instead of "Inject environment variables" I use "Execute system Groovy script" Build Step from Groovy Plugin
[JIRA] [subversion-plugin] (JENKINS-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title Slawomir Czarko commented on JENKINS-31520 Re: SVN_* variables are not available in build script if variable is used in SVN url Manuel Jesús Recena Soto When problem occurs I can see this message repeated 8 times in the log: Nov 17, 2015 1:01:32 PM WARNING hudson.scm.SubversionSCM buildEnvVars no revision found corresponding to http://svn.apache.org/repos/asf/pivot/trunk@$USE_VER; known: http://svn.apache.org/repos/asf/pivot/trunk Nothing is logged if problem does not happen. 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-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title Slawomir Czarko commented on JENKINS-31520 Re: SVN_* variables are not available in build script if variable is used in SVN url Manuel Jesús Recena Soto Yes. I've tried different options for setting USE_VAR variable and I got this. Does not work: "Inject environment variables" option from EnvInject Plugin with "Run buildstep before SCM runs" option from Pre SCM BuildStep Plugin Does work: "Prepare an environment for the run" option from EnvInject Plugin use a groovy system script with "Run buildstep before SCM runs" option from Pre SCM BuildStep Plugin Parameterized Build plugin I don't understand how in all cases Subversion Plugin is able to checkout the files correctly (which indicates it has access to USE_VER variable) but SVN_* variables are not set in one of the cases. 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] [doxygen-plugin] (JENKINS-29938) Unable to serialize is reported when publishing doxygen generate html files
Title: Message Title Slawomir Czarko commented on JENKINS-29938 Re: Unable to serialize is reported when publishing doxygen generate html files Fix for this problem - https://github.com/jenkinsci/doxygen-plugin/pull/13 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-31520) SVN_* variables are not available in build script if variable is used in SVN url
Title: Message Title Slawomir Czarko created an issue Jenkins / JENKINS-31520 SVN_* variables are not available in build script if variable is used in SVN url Issue Type: Bug Assignee: Unassigned Attachments: no-problem.xml, problem.xml Components: subversion-plugin Created: 12/Nov/15 11:06 AM Environment: Jenkins LTS 1.625.1 OS - CentOS 7.1 subversion-plugin - 2.5.4 Labels: scm subversion Priority: Major Reporter: Slawomir Czarko Attached job in problem.xml can be used to reproduce this. By comparison no-problem.xml doesn't use variables in SVN URL and works as expected. In both cases the
[JIRA] [subversion-plugin] (JENKINS-11148) SVN_REVISION not available in build script
Title: Message Title Slawomir Czarko commented on JENKINS-11148 Re: SVN_REVISION not available in build script Manuel Jesús Recena Soto Done - https://issues.jenkins-ci.org/browse/JENKINS-31520 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-11148) SVN_REVISION not available in build script
Title: Message Title Slawomir Czarko commented on JENKINS-11148 Re: SVN_REVISION not available in build script This job can be used to reproduce this: http://pastebin.com/raw.php?i=eUR1gLNx By comparison this one doesn't use variables in SVN URL and works as expected: http://pastebin.com/raw.php?i=T2E1H9mg In both cases the expected output is the same: SVN_REVISION=1712454 SVN_REVISION_1=1712454 SVN_URL=http://svn.apache.org/repos/asf/pivot/trunk SVN_URL_1=http://svn.apache.org/repos/asf/pivot/trunk 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-20546) Preserve symlinks when copying artifacts
Title: Message Title Slawomir Czarko commented on JENKINS-20546 Re: Preserve symlinks when copying artifacts Jesse Glick ikedam Sorry for reopening the bug. My problem turned out to have nothing to do with Copy Artifacts 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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Title: Message Title Slawomir Czarko commented on JENKINS-23232 Re: SEVERE: I/O error in channel Chunked connection Still happens randomly with 1.625.1 LTS when using jenkins-cli.jar to upload job config.xml file. Sometimes it fails after couple of requests sometimes after 20+. Server and client are running on CentOS 7.1 I have -Dhudson.diyChunking=false in /etc/sysconfig/jenkins Enabling TCP port for JNLP slave agents seems to fix this or at least reduce the frequency. 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-20546) Preserve symlinks when copying artifacts
Title: Message Title Slawomir Czarko reopened an issue This is still broken in 1.36.1 if fingerprinting of artifacts is not enabled. Jenkins / JENKINS-20546 Preserve symlinks when copying artifacts Change By: Slawomir Czarko Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [blamesubversion-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems
Title: Message Title
Slawomir Czarko edited a comment on JENKINS-26318
Re: Subversion Plug in 2.5 causes sporadic problems
{quote}Why do you think this issue has anything to do with the BlameSubversion plugin? If GitHub is right, the BlameSubversion project has no changes for 3 years. BlameSubversion also does not seem to do any custom class loading.{quote}Because the problem doesn't appear with a custom version of BlameSubversion plugin where I've renamed SVNRevisionState class from BlameSubversion plugin to BlameSVNRevisionState.If anybody's interested the modified version of the plugin is here - https://github.com/ezjenkins/BlameSubversion-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] [blamesubversion-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems
Title: Message Title Slawomir Czarko commented on JENKINS-26318 Re: Subversion Plug in 2.5 causes sporadic problems Why do you think this issue has anything to do with the BlameSubversion plugin? If GitHub is right, the BlameSubversion project has no changes for 3 years. BlameSubversion also does not seem to do any custom class loading. Because the problem doesn't appear with a custom version of BlameSubversion plugin where I've SVNRevisionState from BlameSubversion plugin to BlameSVNRevisionState. If anybody's interested the modified version of the plugin is here - https://github.com/ezjenkins/BlameSubversion-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] [blamesubversion-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems
Title: Message Title Slawomir Czarko commented on JENKINS-26318 Re: Subversion Plug in 2.5 causes sporadic problems Maybe some other plugin contains conflicting SVNRevisionState class? On Linux you can run this to check if you have such a plugin (assuming Jenkins is in /var/lib/jenkins/): for i in $(find /var/lib/jenkins/plugins/ -name '*.jar') ; do ( unzip -l $i | grep -q SVNRevisionState ) && echo $i ; done 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] [envinject-plugin] (JENKINS-18714) SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable
Title: Message Title Slawomir Czarko edited a comment on JENKINS-18714 Re: SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable - Still happens with Subversion Plugin 2.5.3 and EnvInject Plugin 1.92.1 - I take it back. I had a problem yesterday with missing SVN_URL and SVN_REVISION variables but it had nothing to do with this bug. The problem was in my scripts. 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] [envinject-plugin] (JENKINS-18714) SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable
Title: Message Title Slawomir Czarko commented on JENKINS-18714 Re: SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable Still happens with Subversion Plugin 2.5.3 and EnvInject Plugin 1.92.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [doxygen-plugin] (JENKINS-29938) Unable to serialize is reported when publishing doxygen generate html files
Title: Message Title Slawomir Czarko commented on JENKINS-29938 Re: Unable to serialize is reported when publishing doxygen generate html files Happens also on LTS Jenkins 1.609.2 with Linux server and clients. Doxygen plugin 0.17. Downgrade to Doxygen plugin 0.16 fixes the problem. 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-26318) Subversion Plug in 2.5 causes sporadic problems
Title: Message Title Slawomir Czarko commented on JENKINS-26318 Re: Subversion Plug in 2.5 causes sporadic problems hudson.scm.SVNRevisionState in subversion-plugin used to be a private class but that was changed in this commit: commit 75080db63a30d42ac66d5ff46f8fbf49bab6b637 Author: Nicolas De loof nicolas.del...@gmail.com Date: Thu Oct 30 09:41:43 2014 +0100 Make SVNRevisionState public Required so another plugin can retrieve the built revision. Typical use case is svnmerge-plugin which has to merge built revision to upstream branch 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-26318) Subversion Plug in 2.5 causes sporadic problems
Title: Message Title Slawomir Czarko commented on JENKINS-26318 Re: Subversion Plug in 2.5 causes sporadic problems This can be caused by duplicate class name (hudson.scm.SVNRevisionState) between subversion-plugin and other plugins, for example BlameSubversion-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] [subversion-plugin] (JENKINS-26458) E155021: This client is too old to work with the working copy
Title: Message Title Slawomir Czarko commented on JENKINS-26458 Re: E155021: This client is too old to work with the working copy I just noticed that in hudson.scm.SubversionSCM.xml I had this line: workspaceFormat100/workspaceFormat It should have been 29. This got fixed after I changed subversion version in global Jenkins settings from 1.7 to 1.8 and then back to 1.7. Now it sometimes works, and sometimes I get this: FATAL: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState java.lang.ClassCastException: hudson.scm.SVNRevisionState cannot be cast to hudson.scm.SVNRevisionState at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1758) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) This was reported as JENKINS-27079 and JENKINS-26318 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-26458) E155021: This client is too old to work with the working copy
Title: Message Title Slawomir Czarko commented on JENKINS-26458 Re: E155021: This client is too old to work with the working copy I have BlameSubversion plugin installed. Both subversion and BlameSubversion provide class SVNRevisionState - classloader conflict? 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-26458) E155021: This client is too old to work with the working copy
Title: Message Title Slawomir Czarko edited a comment on JENKINS-26458 Re: E155021: This client is too old to work with the working copy Ijustnoticedthatinhudson.scm.SubversionSCM.xmlIhadthisline:workspaceFormat100/workspaceFormatItshouldhavebeen29.ThisgotfixedafterIchangedsubversionversioninglobalJenkinssettingsfrom1.7to1.8andthenbackto1.7.Nowitsometimesworks,andsometimesIgetthis:FATAL:hudson.scm.SVNRevisionStatecannotbecasttohudson.scm.SVNRevisionStatejava.lang.ClassCastException:hudson.scm.SVNRevisionStatecannotbecasttohudson.scm.SVNRevisionState athudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) athudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) athudson.scm.SCM.checkout(SCM.java:484) athudson.model.AbstractProject.checkout(AbstractProject.java:1270) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) athudson.model.Run.execute(Run.java:1758) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240)Thiswasreportedas[JENKINS- 27079 26734 ]and[JENKINS-26318] 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-26458) E155021: This client is too old to work with the working copy
Title: Message Title Slawomir Czarko edited a comment on JENKINS-26458 Re: E155021: This client is too old to work with the working copy Ijustnoticedthatinhudson.scm.SubversionSCM.xmlIhadthisline:workspaceFormat100/workspaceFormatItshouldhavebeen29.ThisgotfixedafterIchangedsubversionversioninglobalJenkinssettingsfrom1.7to1.8andthenbackto1.7.Nowitsometimesworks,andsometimesIgetthis:FATAL:hudson.scm.SVNRevisionStatecannotbecasttohudson.scm.SVNRevisionStatejava.lang.ClassCastException:hudson.scm.SVNRevisionStatecannotbecasttohudson.scm.SVNRevisionState athudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) athudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) athudson.scm.SCM.checkout(SCM.java:484) athudson.model.AbstractProject.checkout(AbstractProject.java:1270) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) athudson.model.Run.execute(Run.java:1758) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240)Thiswasreportedas[JENKINS- 26734 27079 ]and[JENKINS-26318] butIdonothaveMultipleSCMplugininstalledwhichismentionedinthesebugs. 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-26458) E155021: This client is too old to work with the working copy
Title: Message Title Slawomir Czarko edited a comment on JENKINS-26458 Re: E155021: This client is too old to work with the working copy IhaveBlameSubversionplugininstalled.BothsubversionandBlameSubversionprovideclassSVNRevisionState-classloaderconflict? Insubversion-plugin2.4.xSVNRevisionStateclasswasidenticalasinBlameSubversionbutin2.5thereweresomechanges. 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-26458) E155021: This client is too old to work with the working copy
Title: Message Title Slawomir Czarko commented on JENKINS-26458 Re: E155021: This client is too old to work with the working copy Subversion Plugin doesn't support all the subversion operations so it's not always possible to avoid using subversion CLI. For me this problem happens when subversion CLI is version 1.7 so I cannot SVN version from 1.7 to 1.8 in the Jenkins configuration because then the subversion CLI client doesn't work. 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-26458) E155021: This client is too old to work with the working copy
Title: Message Title Slawomir Czarko updated an issue Jenkins / JENKINS-26458 E155021: This client is too old to work with the working copy Build output with failure. Change By: Slawomir Czarko Attachment: test-subversion-consoleText 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-26458) E155021: This client is too old to work with the working copy
Title: Message Title Slawomir Czarko commented on JENKINS-26458 Re: E155021: This client is too old to work with the working copy In my build scripts I need to execute various SVN commands - add, delete, status, commit. But that's not really relevant to this problem. I was replying to the comment that It is very important that the workspace is managed by Subversion Plugin. and explaining why I need to use subversion CLI and why I cannot update SVN version from 1.7 to 1.8 in the Jenkins configuration. I can reproduce this bug with a basic job which has one SVN module defined - test-subversion.xml. It fails every time if in global Jenkins settings subversion version is set to 1.7. With 1.8 it works. I'm not sure but I think when it fails the SVN working copy seems to be corrupted. Normally with 1.7 SVN working copy if you run this command : sqlite3 .svn/wc.db PRAGMA user_version you get 29. With 1.8 you get 31. But when this error happens I get 100 which is the value mentioned in the error message. This would explain why the plugin is unable to checkout the code. Jenkins build output when it fails - test-subversion-consoleText 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-26458) E155021: This client is too old to work with the working copy
Title: Message Title Slawomir Czarko updated an issue Jenkins / JENKINS-26458 E155021: This client is too old to work with the working copy Jenkins job definition to reproduce this problem. Change By: Slawomir Czarko Attachment: test-subversion.xml 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] [envinject-plugin] (JENKINS-27665) NPE after updating EnvInject Plugin from 1.90 to 1.91.1
Slawomir Czarko created JENKINS-27665 NPE after updating EnvInject Plugin from 1.90 to 1.91.1 Issue Type: Bug Assignee: Gregory Boissinot Components: envinject-plugin Created: 30/Mar/15 10:20 AM Description: java.lang.NullPointerException at org.jenkinsci.lib.envinject.EnvInjectAction$1.transformEntry(EnvInjectAction.java:94) at org.jenkinsci.lib.envinject.EnvInjectAction$1.transformEntry(EnvInjectAction.java:92) at com.google.common.collect.Maps$TransformedEntriesMap$1$1.apply(Maps.java:1218) at com.google.common.collect.Maps$TransformedEntriesMap$1$1.apply(Maps.java:1216) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at java.util.AbstractMap.putAll(AbstractMap.java:272) at java.util.TreeMap.putAll(TreeMap.java:321) at org.jenkinsci.lib.envinject.service.EnvInjectSavable.saveEnvironment(EnvInjectSavable.java:54) at org.jenkinsci.lib.envinject.EnvInjectAction.writeReplace(EnvInjectAction.java:91) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:89) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:99) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:223) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:210) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:182) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:167) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:108) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:178) at hudson.model.Run.save(Run.java:1929) at hudson.plugins.changelog_history.ChangeLogHistoryRunListener.copyChangeLogs(ChangeLogHistoryRunListener.java:82) at hudson.plugins.changelog_history.ChangeLogHistoryRunListener.onDeleted(ChangeLogHistoryRunListener.java:50) at hudson.plugins.changelog_history.ChangeLogHistoryRunListener.onDeleted(ChangeLogHistoryRunListener.java:40) at
[JIRA] [build-flow-extensions] (JENKINS-27666) Some jobs can't be started after updating Build Blocker Plugin from 1.4.1 to 1.6
Slawomir Czarko created JENKINS-27666 Some jobs cant be started after updating Build Blocker Plugin from 1.4.1 to 1.6 Issue Type: Bug Assignee: Unassigned Components: build-flow-extensions Created: 30/Mar/15 10:35 AM Description: Nothing in the log. Downgrading back to 1.4.1 fixes the problem. Environment: Jenkins LTS 1.596.2 Project: Jenkins Priority: Major Reporter: Slawomir Czarko This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Slawomir Czarko commented on JENKINS-26458 org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy With the plugin 2.5, in our case, when setting SVN version to 1.8 (instead of 1.7) in the Jenkins settings, it solves the problem. Will this work if the SVN client on the slaves is 1.7? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy
Slawomir Czarko commented on JENKINS-26458 org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy For me this started happening after updating subversion plugin from version 2.4.5 to 2.5. Downgrading subversion plugin back to 2.4.5 fixes the problem. 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] [mailer] (JENKINS-9939) Publisher hudson.tasks.Mailer aborted due to exception
Slawomir Czarko commented on JENKINS-9939 Publisher hudson.tasks.Mailer aborted due to exception I got the same error on the current LTS version of Jenkins - 1.532.2 ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.FilePath.act(FilePath.java:900) at hudson.FilePath.act(FilePath.java:884) at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:114) at org.jenkinsci.plugins.xunit.XUnitProcessor.performXUnit(XUnitProcessor.java:57) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:88) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1690) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) ERROR: Publisher hudson.tasks.Mailer aborted due to exception java.lang.NullPointerException at hudson.tasks.MailSender.createFailureMail(MailSender.java:278) at hudson.tasks.MailSender.getMail(MailSender.java:153) at hudson.tasks.MailSender.execute(MailSender.java:101) at hudson.tasks.Mailer.perform(Mailer.java:137) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1690) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-prerequisites] (JENKINS-18688) Jobs don't start if Slave Prerequisite script is defined and job weight 1
Slawomir Czarko created JENKINS-18688 Jobs dont start if Slave Prerequisite script is defined and job weight 1 Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: slave-prerequisites Created: 10/Jul/13 8:50 AM Description: I'm using two plugins: 'Slave Prerequisite plugin' and 'Jenkins heavy job plugin' https://wiki.jenkins-ci.org/display/JENKINS/Slave+Prerequisites+Plugin http://wiki.hudson-ci.org/display/HUDSON/Heavy+Job+Plugin If job is configured with a 'Job weight' greater than 1 and a script is defined for 'Check job prerequisites' then the job never starts. Changing 'Job weight' to 1 or unselecting 'Check job prerequisites' checkbox allows the job to start. Project: Jenkins Labels: plugin Priority: Major Reporter: Slawomir Czarko 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] [heavy-job] (JENKINS-18688) Jobs don't start if Slave Prerequisite script is defined and job weight 1
Slawomir Czarko updated JENKINS-18688 Jobs dont start if Slave Prerequisite script is defined and job weight 1 Change By: Slawomir Czarko (10/Jul/13 9:21 AM) Component/s: heavy-job 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] [svncompat13] (JENKINS-17974) SVN plugin ignores --depth parameters
Slawomir Czarko commented on JENKINS-17974 SVN plugin ignores --depth parameters Is the component here correct? I'm working on a fix for this issue but for subversion-plugin not for svncompat13. 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] [svncompat13] (JENKINS-17974) SVN plugin ignores --depth parameters
Slawomir Czarko commented on JENKINS-17974 SVN plugin ignores --depth parameters Which SVN version are you using? 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.
