[JIRA] [publish-over-ssh-plugin] (JENKINS-26215) Add option to recursively copy a tree, as per scp -r.

2014-12-23 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 created  JENKINS-26215


Add option to recursively copy a tree, as per scp -r.















Issue Type:


Improvement



Assignee:


bap



Components:


publish-over-ssh-plugin



Created:


23/Dec/14 2:18 PM



Description:


I don't see the equivalent of the "-r" option to recursively copy a directory over scp/sftp. This would be extremely useful to me, an is almost a blocker. Thanks.




Environment:


Jenkins 1.594, Publish Over SSH v1.12




Project:


Jenkins



Priority:


Major



Reporter:


J McG

























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] [scp-plugin] (JENKINS-26216) Add option to recursively copy a tree, as per scp -r.

2014-12-23 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 created  JENKINS-26216


Add option to recursively copy a tree, as per scp -r.















Issue Type:


Improvement



Assignee:


ramazanyich2



Components:


scp-plugin



Created:


23/Dec/14 2:26 PM



Description:


I don't see the equivalent of the "-r" option to recursively copy a directory over scp/sftp. This would be extremely useful to me, an is almost a blocker. Thanks.




Environment:


Jenkins 1.594, Hudson SCP pulisher plugin: v1.8




Project:


Jenkins



Priority:


Minor



Reporter:


J McG

























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] [fogbugz-plugin] (JENKINS-24972) FogBugz does not always use CASE_ID, for example BugzID is used too (for svn integration).

2014-12-23 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 updated  JENKINS-24972


FogBugz does not always use CASE_ID, for example BugzID is used too (for svn integration).
















Change By:


J McG
(23/Dec/14 2:28 PM)




Description:


IntheBuildEnvironmentsettingstheCopycustomfieldsfromFogbugzcaseretrievedbyCASE_IDenvironmentvariableintoenvironmentvariablesavailabletootherbuildsteps.specifiesCASE_IDyetweuseBugzIDtoensureoursubversionintegrationwithFogBugzworks.CantthispartofJenkinsbemodifiedtousetheBugIDRegexfromtheFogbugzAPIcommunicationsettings?
Asweusesvn,IbelievethisisstoppingusfromhavingJenkinsautomaticallyupdateourFogBugzentries,becausewecantuseCASE_ID,buthavetouseBugzID.





Priority:


Minor
Major



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [scp-plugin] (JENKINS-26216) Add option to recursively copy a tree, as per scp -r.

2014-12-23 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 commented on  JENKINS-26216


Add option to recursively copy a tree, as per scp -r.















Having previously read the plugin documentation multiple times, far as I could tell in the plugin documentation, using the ant-style selection did not replicate hierarchies, but flattened them. I not only want to read a tree of files in, but want that tree, with sub-directories and all, replicated to the target, as per "scp -r". Does the ant-style selection do this?

Previous comments by: Jul 21, 2009, Dan Morrow and Aug 12, 2010, Andrei Pozolotin have gone unanswered.

The comment in the documentation " You can use ant includes syntax, eg. folder/dist/*.jar. " does not clearly imply that directory hierarchies will be replicated, and the previous comments imply I am correct.



























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] [scp-plugin] (JENKINS-26216) Add option to recursively copy a tree, as per scp -r.

2014-12-23 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 updated  JENKINS-26216


Add option to recursively copy a tree, as per scp -r.
















Change By:


J McG
(23/Dec/14 4:21 PM)




Description:


Idontseetheequivalentofthe-roptiontorecursivelycopyadirectoryoverscp/sftp.Thiswouldbeextremelyusefultome,
an
and
isalmostablocker.Thanks.





Priority:


Minor
Major



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [svn-tag-plugin] (JENKINS-26217) Enable support for HEAD (v2.5) Subversion plugin.

2014-12-23 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 created  JENKINS-26217


Enable support for HEAD (v2.5) Subversion plugin.















Issue Type:


Bug



Assignee:


k2nakamura



Components:


svn-tag-plugin



Created:


23/Dec/14 4:33 PM



Description:


See case https://issues.jenkins-ci.org/browse/JENKINS-18935

I am attempting to tag a project I host on Sourceforge using this plugin. I have, as far as I am aware, configured my credentials (as much as I can in the ) including the ssh agent plugin. Yet still I get a java exception:

java.lang.NoSuchMethodError:

hudson.scm.SubversionSCM.getRevisionFile(...)

XXXsnipXXX

I am using the Subversion plugin v2.5-SNAPSHOT (private-12/17/2014 10:23-jenkins)

https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/org.jenkins-ci.plugins$subversion/lastSuccessfulBuild/artifact/org.jenkins-ci.plugins/subversion/2.5-SNAPSHOT/subversion-2.5-SNAPSHOT.hpi

(I require svn v1.8 support), so I suspect this is the issue. Might it be possible to update this plugin, and confirm if it can work with Sourceforge?




Environment:


Jenkins 1.594, Subversion Tag v1.17




Project:


Jenkins



Priority:


Major



Reporter:


J McG

























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-18935) Make Subversion plugin support Subversion 1.8

2014-12-22 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















I hope the update will be officially released soon!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [valgrind-plugin] (JENKINS-24971) valgrind not run if working directory set.

2014-11-24 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 commented on  JENKINS-24971


valgrind not run if working directory set.















Thanks for the advice. I note that the download page for the plugin lists 0.22 as the latest version:

https://wiki.jenkins-ci.org/display/JENKINS/Valgrind+Plugin

I quote:

"Latest Release 	0.22 (archives)
Latest Release Date Sep 16, 2014
Required Core   1.424"

We use Jenkins v1.577. I also note that the changelog lists v0.24, which appears to be unavailable, and I can't find a link to it anywhere. Please can you advise?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [valgrind-plugin] (JENKINS-24971) valgrind not run if working directory set.

2014-11-24 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 commented on  JENKINS-24971


valgrind not run if working directory set.















Thank you very much for your incredibly prompt, clear and helpful response! Thanks again.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [valgrind-plugin] (JENKINS-24971) valgrind not run if working directory set.

2014-11-24 Thread jason.mcguin...@instinet.co.uk (JIRA)












































 
J McG
 edited a comment on  JENKINS-24971


valgrind not run if working directory set.
















(BTW: I think your considering the path relative to the working dir as a bug is what I thought too. Relative to the workspace like most of the other settings in Jenkins seems much more sensible!  Thank you very much for your incredibly prompt, clear and helpful response! Thanks again.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [valgrind] (JENKINS-24971) valgrind not run if working directory set.

2014-10-02 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 created  JENKINS-24971


valgrind not run if working directory set.















Issue Type:


Bug



Assignee:


Johannes Ohlemacher



Components:


valgrind



Created:


02/Oct/14 5:06 PM



Description:


When I set the working directory and I attempt to build the prohject in Jenkins using the valgrind plugin to run valgrind (valgrind-3.8.1) all I get in the log is:

Valgrind includes files: 
$ valgrind --version
Valgrind detected valgrind version (valgrind): 3.8.1
FINDBUGS Collecting findbugs analysis files...

If I delete the setting in the working directory and build again I see:

(I have tried both "BasicStartExitSendOrders*" and "BasicStartExitSendOrdersTest" and get the same result.)

Valgrind includes files: BasicStartExitSendOrdersTest
$ valgrind --version
Valgrind detected valgrind version (valgrind): 3.8.1
Valgrind working dir: /home/jenkins/workspace/NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender
NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender $ valgrind --tool=memcheck --leak-check=full --show-reachable=no --undef-value-errors=no --track-origins=no --child-silent-after-fork=no --trace-children=no --xml=yes --xml-file=/home/jenkins/workspace/NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender/sender/reports/valgrind/BasicStartExitSendOrdersTest.%p.xml /home/jenkins/workspace/NxtGateway_Centos_v6_4_SNAPSHOT_HEAD_Sender/sender/build/cpp/src/Test/BasicStartExitSendOrdersTest

Valgrind valgrind exit code: 201
Valgrind valgrind standard out: 
ERROR: Unable to initialize logger - configuration file is not specified. Please set environment variable LOG4CXX_CONFIG_FILE
Running 8 test cases...
unknown location(0): fatal error in "SenderCtor": std::runtime_error: Required parameter 'MSG_SIZE' has no specified value.
unknown location(0): fatal error in "SenderInit": std::runtime_error: Required parameter 'MSG_SIZE' has no specified value.
unknown location(0): fatal error in "SenderInitWithMITSim": std::exception: Error loading NXTG configuration file mit.xml: Failed to open file.
unknown location(0): fatal error in "SenderInitWithMITSimAndRunner": std::exception: Error loading NXTG configuration file mit.xml: Failed to open file.
unknown location(0): fatal error in "SenderProcessANewOrderMsg": std::exception: Error loading NXTG configuration file mit.xml: Failed to open file.
unknown location(0): fatal error in "SenderProcessACancelOrderMsg": std::exception: Error loading NXTG configuration file mit.xml: Failed to open file.
unknown location(0): fatal error in "SenderProcessAReplaceOrderMsg": std::exception: Error loading NXTG configuration file mit.xml: Failed to open file.
unknown location(0): fatal error in "SenderSoakTestNewOrderParallel": std::exception: Error loading NXTG configuration file mit.xml: Failed to open file.
Valgrind valgrind error out: 
log4cxx: No appender could be found for logger (com.nomura.nxtdirect.nxt-direct-user.NxtDirectSender).
log4cxx: Please initialize the log4cxx system properly.


	
	
		
		
			8 failures detected in test suite "Master Test Suite"
Build step 'Run Valgrind' marked build as failure
FINDBUGS Skipping publisher since build result is FAILURE
		
		
	
	



Also please clarify the help text on the "Executable Include Pattern" edit box to indicate if it is relative to the entry in the "Working Directory" edit box. Thank you.




Environment:


CentOS v6.5



System Properties

Name  ↓	Value   

com.sun.akuma.Daemon	daemonized

executable-war	/usr/lib/jenkins/jenkins.war

file.encoding	UTF-8

file.encoding.pkg	sun.io

file.separator	/

hudson.diyChunking	true

java.awt.graphicsenv	sun.awt.X11GraphicsEnvironment

java.awt.headless	true

java.awt.printerjob	sun.print.PSPrinterJob

java.class.path	/usr/lib/jenkins/jenkins.war

java.class.version	50.0

java.endorsed.dirs	/usr/java/jdk1.6.0_35/jre/lib/endorsed

java.ext.dirs	/usr/java/jdk1.6.0_35/jre/lib/ext:/usr/java/packages/lib/ext

java.home	/usr/java/jdk1.6.0_35/jre

java.io.tmpdir	/tmp

java.library.path	

[JIRA] [core] (JENKINS-24972) FogBugz does not always use CASE_ID, for example BugzID is used too (for svn integration).

2014-10-02 Thread jason.mcguin...@instinet.co.uk (JIRA)














































J McG
 created  JENKINS-24972


FogBugz does not always use CASE_ID, for example BugzID is used too (for svn integration).















Issue Type:


Bug



Assignee:


Unassigned


Components:


core, fogbugz



Created:


02/Oct/14 5:18 PM



Description:


In the "Build Environment" settings the "Copy custom fields from Fogbugz case retrieved by 'CASE_ID' environment variable into environment variables available to other build steps." specifies "CASE_ID" yet we use "BugzID" to ensure our subversion integration with FogBugz works. Can't this part of Jenkins be modified to use the "Bug ID Regex" from the "Fogbugz API communication settings"?




Environment:


CentOS v6.5



System Properties

Name  ↓	Value   

com.sun.akuma.Daemon	daemonized

executable-war	/usr/lib/jenkins/jenkins.war

file.encoding	UTF-8

file.encoding.pkg	sun.io

file.separator	/

hudson.diyChunking	true

java.awt.graphicsenv	sun.awt.X11GraphicsEnvironment

java.awt.headless	true

java.awt.printerjob	sun.print.PSPrinterJob

java.class.path	/usr/lib/jenkins/jenkins.war

java.class.version	50.0

java.endorsed.dirs	/usr/java/jdk1.6.0_35/jre/lib/endorsed

java.ext.dirs	/usr/java/jdk1.6.0_35/jre/lib/ext:/usr/java/packages/lib/ext

java.home	/usr/java/jdk1.6.0_35/jre

java.io.tmpdir	/tmp

java.library.path	/usr/java/jdk1.6.0_35/jre/lib/amd64/server:/usr/java/jdk1.6.0_35/jre/lib/amd64:/usr/java/jdk1.6.0_35/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib

java.runtime.name	Java(TM) SE Runtime Environment

java.runtime.version	1.6.0_35-b10

java.specification.name	Java Platform API Specification

java.specification.vendor	Sun Microsystems Inc.

java.specification.version	1.6

java.vendor	Sun Microsystems Inc.

java.vendor.url	http://java.sun.com/

java.vendor.url.bug	http://java.sun.com/cgi-bin/bugreport.cgi

java.version	1.6.0_35

java.vm.info	mixed mode

java.vm.name	Java HotSpot(TM) 64-Bit Server VM

java.vm.specification.name	Java Virtual Machine Specification

java.vm.specification.vendor	Sun Microsystems Inc.

java.vm.specification.version	1.0

java.vm.vendor	Sun Microsystems Inc.

java.vm.version	20.10-b01

javamelody.About Monitoring	https://wiki.jenkins-ci.org/display/JENKINS/Monitoring

javamelody.analytics-id	UA-1335263-7

javamelody.custom-reports	Jenkins Info,About Monitoring

javamelody.gzip-compression-disabled	true

javamelody.http-transform-pattern	/\d+/|/site/.+|avadoc/.+|/ws/.+|obertura/.+|estReport/.+|iolations/file/.+|/user/.+|/static/\w+/|/adjuncts/\w+/|/bound/[\w\-]+

javamelody.Jenkins Info	/systemInfo

javamelody.no-database	true

javamelody.storage-directory	//home/jenkins/monitoring

javamelody.system-actions-enabled	true

JENKINS_HOME	/home/jenkins

jna.platform.library.path	/usr/lib64:/lib64:/usr/lib:/lib

line.separator	

mail.smtp.sendpartial	true

mail.smtps.sendpartial	true

os.arch	amd64

os.name	Linux

os.version	2.6.18-308.11.1.el5

path.separator	:

pid	17058

sun.arch.data.model	64

sun.boot.class.path	/usr/java/jdk1.6.0_35/jre/lib/resources.jar:/usr/java/jdk1.6.0_35/jre/lib/rt.jar:/usr/java/jdk1.6.0_35/jre/lib/sunrsasign.jar:/usr/java/jdk1.6.0_35/jre/lib/jsse.jar:/usr/java/jdk1.6.0_35/jre/lib/jce.jar:/usr/java/jdk1.6.0_35/jre/lib/charsets.jar:/usr/java/jdk1.6.0_35/jre/lib/modules/jdk.boot.jar:/usr/java/jdk1.6.0_35/jre/classes

sun.boot.library.path	/usr/java/jdk1.6.0_35/jre/lib/amd64

sun.cpu.endian	little

sun.cpu.isalist	

sun.io.unicode.encoding	UnicodeLittle

sun.java.command	/usr/lib/jenkins/jenkins.war --logfile=/home/jenkins/logs/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20

sun.java.launcher	SUN_STANDARD

sun.jnu.encoding	UTF-8

sun.management.compiler	HotSpot 64-Bit Tiered Compilers

sun.os.patch.level	unknown

svnkit.http.methods	Digest,Basic,NTLM,Negotiate

svnkit.ssh2.persistent	false

user.country	US

user.dir	/

user.home	/home/jenkins

user.language	en

user.name	jenkins

user.timezone	US/Eastern

Environment Variables

Name  ↓	Value