date:20130628















































SCM/JIRA link daemon
 commented on  JENKINS-18014


[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.















Code changed in jenkins
User: Alex Earl
Path:
 src/main/java/org/jenkinsci/plugins/tokenmacro/TokenMacro.java
 src/main/java/org/jenkinsci/plugins/tokenmacro/Tokenizer.java
 src/test/java/org/jenkinsci/plugins/tokenmacro/TokenMacroTest.java
http://jenkins-ci.org/commit/token-macro-plugin/8c10736b54aac32f1590720fa2f843febaf31b32
Log:
  Merge pull request #12 from slide/master

Fix JENKINS-18014


Compare: https://github.com/jenkinsci/token-macro-plugin/compare/766cdb04c67a...8c10736b54aa




























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







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

[JIRA] [email-ext] (JENKINS-18014) [Email-ext plugin] ${ENV, var=FOO} for 2.29 doesn't work anymore.















































SCM/JIRA link daemon
 commented on  JENKINS-18014


[Email-ext plugin] ${ENV, var=FOO} for 2.29 doesnt work anymore.















Code changed in jenkins
User: Alex Earl
Path:
 src/main/java/org/jenkinsci/plugins/tokenmacro/TokenMacro.java
 src/main/java/org/jenkinsci/plugins/tokenmacro/Tokenizer.java
 src/test/java/org/jenkinsci/plugins/tokenmacro/TokenMacroTest.java
http://jenkins-ci.org/commit/token-macro-plugin/e1523eca5fb78fad1112193829ee4782620d9ce5
Log:
  Fix JENKINS-18014

Changed the way that macros are escaped to using something similar to Groovy with two $'s. This required actually looking for the items that matched with two $'s and then handling that case special.





























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] [core] (JENKINS-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow















































Croesus Kall
 commented on  JENKINS-9120


RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow















Same problem:
Jenkins 1.518, RHEL6.4, running behind apache 2.2.15
Happens twice a week - only a restart can fix.



























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] [ssh-slaves] (JENKINS-18214) fail to migrate legacy ssh-slaves private key

2013-06-28 Thread s.sog...@gmail.com (JIRA)
















































sogabe
 resolved  JENKINS-18214 as Fixed


fail to migrate legacy ssh-slaves private key
















Change By:


sogabe
(28/Jun/13 7:32 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow

2013-06-28 Thread sebastian.l...@googlemail.com (JIRA)















































Sebastian Laag
 commented on  JENKINS-9120


RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow















Using 1.516 with Windows Server 2008 R2, JDK 1.7 Update 21 64Bit.

Maybe its a problem of excessive jenkins usage? We currently use a setup of 1 master and 12 slaves. All with the same jdk. We use a jnlp connection to connect slave and master.

This problem occurs nearly every day, although that we restart all master and slave VMs once a day.

Is there a possible fix or workaround?



























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







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

[JIRA] [core] (JENKINS-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow















































Croesus Kall
 updated  JENKINS-9120


RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
















Change By:


Croesus Kall
(28/Jun/13 7:42 AM)




Attachment:


JENKINS-9120-ringbuffer-stacktrace-cr.log



























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] [core] (JENKINS-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow













































 
Croesus Kall
 edited a comment on  JENKINS-9120


RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
















Same problem:
Jenkins 1.518, RHEL6.4, running behind apache 2.2.15
Happens twice a week - only a restart can fix.
(attached stacktrace: JENKINS-9120-ringbuffer-stacktrace-cr.log )



























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] [core] (JENKINS-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow













































 
Croesus Kall
 edited a comment on  JENKINS-9120


RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
















Same problem:
Jenkins 1.518, RHEL6.4, running behind apache 2.2.15
Happens twice a week - only a restart can fix.
(attached stacktrace: JENKINS-9120-ringbuffer-stacktrace-cr.log )



























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] [maven2] (JENKINS-18533) Unable to run Maven3 builds due to InvalidClassException

2013-06-28 Thread t...@tw.de (JIRA)
















































Thomas Letze
 resolved  JENKINS-18533 as Fixed


Unable to run Maven3 builds due to InvalidClassException
















Downgraded to Jenkins 1.518.

That solved this for me.

Thx for the hint,
Thomas





Change By:


Thomas Letze
(28/Jun/13 7:48 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [parameterized-trigger] (JENKINS-18536) Remove downstream job from queue before new triggers

2013-06-28 Thread mabahj (JIRA)

Markus
created JENKINS-18536

Remove downstream job from queue before new triggers

Issue Type:

New Feature

Assignee:

huybrechts

Components:

parameterized-trigger

Created:

28/Jun/13 8:48 AM

Description:

Given two jobs:

Downstream, which has a 60s quiet period
Upstream, which triggers a parameterized build on Downstream

Now, if you quickly trigger Upstream 3 times, then there will be 3 Downstream jobs in the queue. They will then all run.

We would like parameterized triggering in combination with downstream quiet period to behave sort of like the SVN quiet period behaves: If Upstream is triggered multiple times, then only the last triggered Downstream will remain in the queue.

Summary: Before Upstream triggers Downstream, Upstream should remove any instances of Downstream from the queue. This should of course be an option and not the default behavior.

Project:

Jenkins

Priority:

Major

Reporter:

Markus

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] [parameterized-trigger] (JENKINS-18536) Remove downstream job from queue before new triggers

2013-06-28 Thread mabahj (JIRA)















































Markus
 commented on  JENKINS-18536


Remove downstream job from queue before new triggers















For anyone that may need the same feature. Our current work-around is a rather messy groovy script added to Upstream:
CancelDownstreamQueue.groovy
import hudson.model.*

Jenkins = Hudson.instance
def q = Jenkins.instance.queue;

if ( args.length != 2 ) {
  println "ERROR - CancelDownstreamQueue.groovy - Scripts needs two arguments. Own job name and part of downstream job name to search for. Do not know if wildcards are supported." 
} else {
  println("Search for downstream jobs from " + args[0] + " whose name contains " + args[1]);
  def thisjob = Jenkins.getInstance().getItemByFullName(args[0]);
  if (thisjob == null) {
println("ERROR - CancelDownstreamQueue.groovy - Could not find this job");
  }else{  
//println(thisjob.getDownstreamProjects())
ListAbstractProject childs = thisjob.getDownstreamProjects()
if (childs == null) {
 println("ERROR - CancelDownstreamQueue.groovy - childs is null");
}else{
  for (IteratorAbstractProject iterator = childs.iterator(); iterator.hasNext();) {
AbstractProject child = iterator.next();
if (child.getFullName().contains(args[1])) {
  println("  Found downstream job " + child.getFullName() + ". Searching for queued items");
  q.items.findAll { it.task.name.equals(child.getFullName()) }.each {
println("Cancelling queued " + it.task.getDisplayName());
q.cancel(it.task);
  }
} else {
  println("  Skipping " + child.getFullName());
}
  }
}
  }
  println("Done");
}


But the script is not 100% stable. It happens to fail (hangs or generates a java.lang.NegativeArraySizeException).
The script is started like this:

java -jar jenkins-cli.jar -s http://jenkins:8080/ groovy ./CancelDownstreamQueue.groovy $JOB_NAME SearchStringForJobsToCancel




























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] [buckminster] (JENKINS-18531) Allow for installation on Windows slave node

2013-06-28 Thread koti...@gmail.com (JIRA)















































Thanasis Kotisis
 updated  JENKINS-18531


Allow for installation on Windows slave node
















Change By:


Thanasis Kotisis
(28/Jun/13 9:01 AM)




Summary:


Allowfor
installationon
Windows
slave
node
installation



























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] [accurev] (JENKINS-18538) cannot send email in different domain

2013-06-28 Thread 949330...@qq.com (JIRA)















































can youfeel
 created  JENKINS-18538


cannot send email in different domain 















Issue Type:


Bug



Assignee:


Scott Tatum



Components:


accurev



Created:


28/Jun/13 9:57 AM



Description:


only send email which is in AD ,cannot send to qq or gmail .

got error :Failed to send out e-mail

javax.mail.MessagingException: Could not connect to SMTP host: smtp.hp.com, port: 25;
  nested exception is:




Environment:


jenkins server :window 2008  AD and dc








Project:


Jenkins



Priority:


Major



Reporter:


can youfeel

























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] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects

2013-06-28 Thread b.bott...@projectnibble.org (JIRA)















































Benny Bottema
 commented on  JENKINS-18162


Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects















sooo... any chance we can solve this situation 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/groups/opt_out.

[JIRA] [cvs] (JENKINS-18539) CVS-Plugin 2.9 consumes 10x more hard disk usage than 1.6

2013-06-28 Thread skyb...@java.net (JIRA)

Florian Rosenauer
created JENKINS-18539

CVS-Plugin 2.9 consumes 10x more hard disk usage than 1.6

Issue Type:

Bug

Assignee:

Unassigned

Attachments:

cvs-server.PNG, jenkins-server.PNG

Components:

cvs

Created:

28/Jun/13 12:09 PM

Description:

Upgrading from 1.509.1 to 1.516 updated the bundled cvs-plugin from 1.6 to 2.8.
I upgraded to 2.9 but as far as I can remember 2.8 was the same problem:

After the upgrade the disk load on our CVS server increased by about 10 times and user startet complaining why cvs is so slow these days.
I also noticed a few 1000MHz more CPU-Load on our Jenkins Server.

I now did a downgrade from CVS-Plugin 2.9 to 1.6 which fixed the problem.

It can be seen clearly on the attached graphics.
(upgrade was on 13.6.2013, downgrade on 21.6.2013)
(dont get confused by the last day's data, its so many measure points so its getting filled up).

Unfortunatelly the 1.6 plugin seems not to be 100% compatible with Jenkins 1.516 because its startet generating "You have data stored in an older format and/or unreadable data." messages. So I added this bug as Major because at some point I estimate v1.6 it will prevent me from upgrading our Jenkins server.

Environment:

Jenkins 1.516 on Tomcat 6, RedHat 5.6 64 Bit, CVS 1.11.22 (on both build and cvs server), jdk1.6.0_26

Project:

Jenkins

Priority:

Critical

Reporter:

Florian Rosenauer

[JIRA] [cvs] (JENKINS-18539) CVS-Plugin 2.9 consumes 10x more hard disk usage than 1.6

2013-06-28 Thread skyb...@java.net (JIRA)















































Florian Rosenauer
 updated  JENKINS-18539


CVS-Plugin 2.9 consumes 10x more hard disk usage than 1.6
















Change By:


Florian Rosenauer
(28/Jun/13 12:11 PM)




Description:


Upgradingfrom1.509.1to1.516updatedthebundledcvs-pluginfrom1.6to2.8.Iupgradedto2.9butasfarasIcanremember2.8wasthesameproblem:AftertheupgradethediskloadonourCVSserverincreasedbyabout10timesanduserstartetcomplainingwhycvsissoslowthesedays.Ialsonoticedafew1000MHzmoreCPU-LoadonourJenkinsServer.InowdidadowngradefromCVS-Plugin2.9to1.6whichfixedtheproblem.Itcanbeseenclearlyontheattachedgraphics.(upgradewason13.6.2013,downgradeon21.6.2013)(dontgetconfusedbythelastdaysdata,itssomanymeasurepointssoitsgettingfilledup).Unfortunatellythe1.6pluginseemsnottobe100%compatiblewithJenkins1.516becauseitsstartetgeneratingYouhavedatastoredinanolderformatand/orunreadabledata.messages.SoIaddedthisbugas
Major
Critical
becauseatsomepointIestimatev1.6itwillpreventmefromupgradingourJenkinsserver.



























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] [maven2] (JENKINS-9466) Provide maven build.finalName in the downloadable artifacts name

2013-06-28 Thread andrei.ba...@movzx.net (JIRA)















































Andrei Badea
 commented on  JENKINS-9466


Provide maven build.finalName in the downloadable artifacts name















The result of this "disambiguation" results in a Maven command-line build being different from a Maven build done in Jenkins. That's deeply wrong, because users do not expect it. It also makes one think "if this in different in the Jenkins build, what else is different?".



























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] [nodeofflinenotification] (JENKINS-14805) Global property 'Node Offline Email Notification' does not work















































Ben Golding
 updated  JENKINS-14805


Global property Node Offline Email Notification does not work
















Change By:


Ben Golding
(28/Jun/13 1:21 PM)




Description:


GlobalpropertyNodeOfflineEmailNotification(inConfigureSystem)doesnotwork.IhaveselectedthecheckboxNodeOfflineEmailNotificationandenteredmyusername(notfullemailaddress,butthefirstpart,sinceDefaultusere-mailsuffixisset).Thisdidnotwork,soItriedalsoselectingthesamecheckboxintheconfigurationpageforeachnode.Thisstilldidnotwork.ItonlyworksifIentermyusernameindividuallyineachnode.
-AdditionalissuewithJIRAsetupforissues:nodeofflinenotificationisnotavalidcomponentSeehttps://wiki.jenkins-ci.org/display/JENKINS/Node+Offline+Notification+PluginThebugisfiledascoreuntilsomeonefixestheJIRA.



























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] [nodeofflinenotification] (JENKINS-18541) Core 1.520 breaks nodeofflinenotification plugin















































Ben Golding
 created  JENKINS-18541


Core 1.520 breaks nodeofflinenotification plugin















Issue Type:


Bug



Assignee:


Unassigned


Components:


nodeofflinenotification



Created:


28/Jun/13 1:26 PM



Description:


Update core 1.517 -- 1.520 appears to break this plugin.

Excerpt from /log/all below


Jun 28, 2013 1:51:08 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin nodeofflinenotification
hudson.util.IOException2: Failed to initialize
	at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:379)
	at hudson.PluginManager$2$1$1.run(PluginManager.java:334)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:893)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.Exception: unable to locate gem bundle for nodeofflinenotification at /localdev/bl/jenkins/plugins/nodeofflinenotification/WEB-INF/classes/vendor/gems
	at ruby.RubyPlugin.initRubyLoadPaths(RubyPlugin.java:202)
	at ruby.RubyPlugin.start(RubyPlugin.java:158)
	at hudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:387)
	at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:376)
	... 9 more





Environment:


Jenkins 1.520

Node Offline Notification Plugin 1.0.3




Project:


Jenkins



Priority:


Critical



Reporter:


Ben Golding

























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] [nodeofflinenotification] (JENKINS-18541) Core 1.520 breaks nodeofflinenotification plugin















































Ben Golding
 updated  JENKINS-18541


Core 1.520 breaks nodeofflinenotification plugin
















Change By:


Ben Golding
(28/Jun/13 1:32 PM)




Description:


Updatecore1.517--1.520appearstobreakthisplugin.
Excerptfrom
From
/log/all
below
{code}Jun28,20131:51:08PMjenkins.InitReactorRunner$1onTaskFailedSEVERE:FailedLoadingpluginnodeofflinenotificationhudson.util.IOException2:Failedtoinitialize	athudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:379)	athudson.PluginManager$2$1$1.run(PluginManager.java:334)	atorg.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)	atorg.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)	atjenkins.model.Jenkins$7.runTask(Jenkins.java:893)	atorg.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)	atorg.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)	atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)	atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)	atjava.lang.Thread.run(Thread.java:619)Causedby:java.lang.Exception:unabletolocategembundlefornodeofflinenotificationat/localdev/bl/jenkins/plugins/nodeofflinenotification/WEB-INF/classes/vendor/gems	atruby.RubyPlugin.initRubyLoadPaths(RubyPlugin.java:202)	atruby.RubyPlugin.start(RubyPlugin.java:158)	athudson.ClassicPluginStrategy.startPlugin(ClassicPluginStrategy.java:387)	athudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:376)	...9more{code}
Moreinfo:indeedthepath{code}/localdev/bl/jenkins/plugins/nodeofflinenotification/WEB-INF/classes/vendor/gems{code}doesnotexist.Thesearetheonlyfilesintheplugindirectory:{code}%find/localdev/bl/jenkins/plugins/nodeofflinenotification/localdev/bl/jenkins/plugins/nodeofflinenotification/localdev/bl/jenkins/plugins/nodeofflinenotification/WEB-INF/localdev/bl/jenkins/plugins/nodeofflinenotification/WEB-INF/lib/localdev/bl/jenkins/plugins/nodeofflinenotification/WEB-INF/lib/classes.jar/localdev/bl/jenkins/plugins/nodeofflinenotification/.timestamp2/localdev/bl/jenkins/plugins/nodeofflinenotification/META-INF/localdev/bl/jenkins/plugins/nodeofflinenotification/META-INF/MANIFEST.MF{code}TherequiredclassesappeartoexistinsidetheJAR-file:{code}%jar-tf/localdev/bl/jenkins/plugins/nodeofflinenotification/WEB-INF/lib/classes.jaremail_node_property/config.erbmodels/emailnodeproperty.rbmodels/java_emailcomputerlistener.rbmodels/src/emailcomputerlistener.rbmodels/src/java_wrapper.rbvendor/bundle/configvendor/gems/bundler/gems/jenkins-plugin-runtime-39cc789729c0/Gemfilevendor/gems/bundler/gems/jenkins-plugin-runtime-39cc789729c0/README.md...{code}



























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.

XCOPY command/ArtifactDeployer Plugin

2013-06-28 Thread tushanka

Hello Everyone,

I want to copy files on shared drive through jenkins.
and also on the remote server

For copying files on shared drive i used XCOPY E:/foldername/name.war
Z:/testfolder
Z is the mapped drive. when i run the bat file with these contents through
cmd it works fine..but when it is configured in jenkins it gives the
following error:
*Invalid drive specification
0 File(s) copied
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE*
I tried following steps for copying files to remote server

installed copy artifact plugin
in the job configuration i get following
Files to deploy:-
Remote directory:-

For files to deploy i specify the .war files which is fine
For Remote directory ,i dnt seem to make anything work. i tried //machine
name/folder and many other combinations. however ,nothing seems to work.
below is the error for the same

[ArtifactDeployer] - Starting deployment from the build step ...
[ArtifactDeployer] - [ERROR] - Failed to deploy. Can't create the directory
'Z:/test'
[ArtifactDeployer] - [ERROR] - Failed to mkdirs: Z:/test
Build step '[ArtifactDeployer] - Deploy artifacts from workspace to remote
directories' changed build result to FAILURE
Build step '[ArtifactDeployer] - Deploy artifacts from workspace to remote
directories' marked build as failure
Finished: FAILURE

Can anyone please help me.

--
View this message in context:
http://jenkins-ci.361315.n4.nabble.com/XCOPY-command-ArtifactDeployer-Plugin-tp4671091.html
Sent from the Jenkins issues mailing list archive at Nabble.com.

--
You received this message because you are subscribed to the Google Groups
Jenkins Issues group.
To unsubscribe from this 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] [build-failure-analyzer] (JENKINS-18542) Make dependency to git plugin optional















































Ben Golding
 created  JENKINS-18542


Make dependency to git plugin optional 















Issue Type:


Improvement



Assignee:


Tomas Westling



Components:


build-failure-analyzer



Created:


28/Jun/13 1:40 PM



Description:


Please make dependency from build-failure-analyzer to git optional.

We don't use Git in our Jenkins. I prefer to keep the installed plugins UI list manageable, reduce startup time, etc...




Environment:


Core 1.520

Build Failure Analyzer 1.5.0




Project:


Jenkins



Priority:


Minor



Reporter:


Ben Golding

























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] [ant] (JENKINS-14245) I have lost all ant targets in all jobs of my Jenkins server when i have enabled Check-out Strategy to emulate a clean checkout by first deleting unversioned/ignored file

2013-06-28 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-14245


I have lost all ant targets in all jobs of my Jenkins server when i have enabled Check-out Strategy to emulate a clean checkout by first deleting unversioned/ignored files, then svn update















Is this still an issue?



























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] [build-failure-analyzer] (JENKINS-18544) Missing dependency to git















































Ben Golding
 created  JENKINS-18544


Missing dependency to git















Issue Type:


Bug



Assignee:


Tomas Westling



Components:


build-failure-analyzer



Created:


28/Jun/13 1:58 PM



Description:


Dependency from build-failure-analyzer to git seems to be missing from the metadata.

Workaround seems OK (manually select "Git Plugin" checkbox when installing)

From /log/all:

SEVERE: Failed Loading plugin build-failure-analyzer
java.io.IOException: Dependency git (1.1.10) doesn't exist
	at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:479)
	at hudson.PluginManager$2$1$1.run(PluginManager.java:333)
	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:893)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:619)





Environment:


Core 1.520

Build Failure Analyzer 1.5.0




Project:


Jenkins



Priority:


Major



Reporter:


Ben Golding

























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] [parameters] (JENKINS-18534) Cannot add new build to queue from same project with different parameters















































Shannon Kerr
 updated  JENKINS-18534


Cannot add new build to queue from same project with different parameters
















Change By:


Shannon Kerr
(28/Jun/13 2:08 PM)




Summary:


Cannotaddnewbuildtoqueuefromsameproject
using
with
differentparameters



























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] [core] (JENKINS-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'

2013-06-28 Thread bertold.kol...@unboundid.com (JIRA)















































Bertold Kolics
 commented on  JENKINS-7695


archiving throws hudson.util.IOException2: java.io.IOException: request to write 3977 bytes exceeds size in header of 41955006















I also see this issue on 1.514:


Archiving artifacts
ERROR: Failed to archive artifacts: target/test.log
hudson.util.IOException2: java.io.IOException: request to write '8192' bytes exceeds size in header of '9830918' bytes for entry 'target/test.log'
	at hudson.FilePath.copyRecursiveTo(FilePath.java:1942)
	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:137)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
	at hudson.model.Run.execute(Run.java:1600)
	at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:241)
Caused by: java.util.concurrent.ExecutionException: java.io.IOException: request to write '8192' bytes exceeds size in header of '9830918' bytes for entry 'target/test.log'
	at hudson.remoting.Channel$4.adapt(Channel.java:705)
	at hudson.remoting.Channel$4.adapt(Channel.java:700)
	at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:1940)
	... 10 more
Caused by: java.io.IOException: request to write '8192' bytes exceeds size in header of '9830918' bytes for entry 'target/test.log'
	at hudson.org.apache.tools.tar.TarOutputStream.write(TarOutputStream.java:284)
	at hudson.util.io.TarArchiver.visit(TarArchiver.java:115)
	at hudson.util.DirScanner$Glob.scan(DirScanner.java:133)
	at hudson.FilePath.writeToTar(FilePath.java:1978)
	at hudson.FilePath.access$1000(FilePath.java:168)
	at hudson.FilePath$36.invoke(FilePath.java:1919)
	at hudson.FilePath$36.invoke(FilePath.java:1915)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2387)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)





























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] [core] (JENKINS-18276) Archiving artifacts from a slave node is extremely slow even with 1.509.1+

2013-06-28 Thread jakub.stil...@bsc-ideas.com (JIRA)















































Jakub Štiller
 commented on  JENKINS-18276


Archiving artifacts from a slave node is extremely slow even with 1.509.1+















I can confirm it. When copy 150MB WAR using scp the copy speed is 30MB/s, when archiving by Jenkins the rate is only about 3MB/s. I have tried steps described in JENKINS-3922 but no success. Running Jenkins v1.513 with slave v2.23. 



























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] [core] (JENKINS-18191) After upgrading to 1.517 fingerprinting seems to hang

2013-06-28 Thread kuypers.d...@googlemail.com (JIRA)
















































Dirk Kuypers
 resolved  JENKINS-18191 as Cannot Reproduce


After upgrading to 1.517 fingerprinting seems to hang
















After upgrading to 1.520 I cannot reproduce the problem anymore. Maybe it was fixed by all the fingerprinting changes since then, maybe my problem was only a problem at my site...





Change By:


Dirk Kuypers
(28/Jun/13 2:31 PM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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] [core] (JENKINS-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'

2013-06-28 Thread bertold.kol...@unboundid.com (JIRA)















































Bertold Kolics
 commented on  JENKINS-7695


archiving throws hudson.util.IOException2: java.io.IOException: request to write 3977 bytes exceeds size in header of 41955006















Hi everyone. 
This issue is a big deal for me, so I'm willing to pay USD 20.00 for it.
This offer is registered on FreedomSponsors (http://www.freedomsponsors.org/core/issue/284/archiving-throws-hudsonutilioexception2-javaioioexception-request-to-write-3977-bytes-exceeds-size-in-header-of-41955006).
If you solve it (according to the acceptance criteria described there), please register on FreedomSponsors and mark it as resolved there
I'll then check it out and gladly pay up!

Oh, and if anyone else also wants throw in a few bucks on this, you should check out FreedomSponsors!



























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] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters















































Shannon Kerr
 updated  JENKINS-18534


Cannot add new build to queue from same project with different parameters
















Change By:


Shannon Kerr
(28/Jun/13 3:08 PM)




Component/s:


parameterized-trigger





Component/s:


parameters



























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] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters















































Shannon Kerr
 commented on  JENKINS-18534


Cannot add new build to queue from same project with different parameters















I just attempted to start multiple instance of the same build, all with unique parameters and it was a mess.

Here is what I see:

1. Sometimes it created a new unique job
2. Sometimes it "merged" with the next job in the queue, replacing the parameters

In my testing I used the following parameters:

1. Branch (drop down list box of the available branches)
2. Build type (choice between -D and -R)
3. Check box for Test build (is this a test build?)

I tried different combinations of each of these and could not get consistent behavior.

We're just getting ready to roll out Jenkins and this kind of bug is really throwing off the plan to roll out.  Hope to see it fixed soon, or someone can educate me on what I'm not doing right.

Thanks!



























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







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

[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters















































Shannon Kerr
 updated  JENKINS-18534


Cannot add new build to queue from same project with different parameters
















Change By:


Shannon Kerr
(28/Jun/13 3:44 PM)




Priority:


Major
Blocker





Description:


(ChangedtoBlockerasthisbugispreventingusfromrollingoutJenkinstoproductionrightnow,but
I
couldcompletelychangeourimplementationandreducethistoCriticalorMajorIsuppose,butthatwouldbequiteabitofwork)I
startaparameterizedbuildfromprojectAviathebuildbutton.Asecondparameterizedbuildfromthesameprojectwasthenstartedviathebuildbutton,butwithdifferentparametervalues.Insteadofhavingtwojobsinthequeue,thesecondjobisnotaddedandinsteadtakesoverthefirstjobinthequeue.Ifthejobswerestartedbydifferentusers,bothusersnamesshowupastheStartedbyusers.Onlythesecondusersparametersareusedandretained.Thefirstusersjobisjustlost.Imgoingtoseeifthiseverworked,butImprettysureitdid.ImstillprettynewtoJenkins,butIthoughtIhadtestedthisoutbeforeandhadseentwoinstancesofthesamejobsittinginthequeue.



























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] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters
















































Shannon Kerr
 assigned  JENKINS-18534 to huybrechts



Cannot add new build to queue from same project with different parameters
















Change By:


Shannon Kerr
(28/Jun/13 3:50 PM)




Assignee:


huybrechts



























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] [core] (JENKINS-4409) Hudson test case leaks temp folders

2013-06-28 Thread de...@ikedam.jp (JIRA)















































ikedam
 commented on  JENKINS-4409


Hudson test case leaks temp folders















It should be fixed in 1.520, in https://github.com/jenkinsci/jenkins/pull/791, but still happens.

java.io.IOException: Unable to delete C:\Users\ikedam\AppData\Local\Temp\hudson1720733180692388407tmp\credentials\WEB-INF\lib\classes.jar
at hudson.Util.deleteFile(Util.java:253)
at hudson.Util.deleteRecursive(Util.java:305)
at hudson.Util.deleteContentsRecursive(Util.java:202)
at hudson.Util.deleteRecursive(Util.java:296)
at hudson.Util.deleteContentsRecursive(Util.java:202)
at hudson.Util.deleteRecursive(Util.java:296)
at hudson.Util.deleteContentsRecursive(Util.java:202)
at hudson.Util.deleteRecursive(Util.java:296)
at hudson.Util.deleteContentsRecursive(Util.java:202)
at hudson.Util.deleteRecursive(Util.java:296)
at org.jvnet.hudson.test.TestPluginManager$1.run(TestPluginManager.java:146)


Hmm



























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] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine

2013-06-28 Thread ljader...@gmail.com (JIRA)















































Łukasz Jąder
 commented on  JENKINS-18312


changelog browsing uses the wrong path to Redmine















Probably this PR https://github.com/jenkinsci/redmine-plugin/pull/10 could fix this issue, but merging into main repo and releasing it could take some time.



























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







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

[JIRA] [core] (JENKINS-18262) @TestExtension works only when the enclosing class is exactly the test case class

2013-06-28 Thread de...@ikedam.jp (JIRA)
















































ikedam
 resolved  JENKINS-18262 as Fixed


@TestExtension works only when the enclosing class is exactly the test case class
















Fixed in 1.520, 80cf490.





Change By:


ikedam
(28/Jun/13 4:07 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [redmine] (JENKINS-18312) changelog browsing uses the wrong path to Redmine

2013-06-28 Thread ljader...@gmail.com (JIRA)













































 
Łukasz Jąder
 edited a comment on  JENKINS-18312


changelog browsing uses the wrong path to Redmine
















Probably this PR https://github.com/jenkinsci/redmine-plugin/pull/10 could fix this issue, but merging it into main repo and releasing it could take some time.



























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







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

[JIRA] [core] (JENKINS-18259) Unable to delete slave.log in plugin tests

2013-06-28 Thread de...@ikedam.jp (JIRA)
















































ikedam
 closed  JENKINS-18259 as Fixed


Unable to delete slave.log in plugin tests
















Fixed in 1.520.





Change By:


ikedam
(28/Jun/13 4:06 PM)




Status:


Resolved
Closed



























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







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

[JIRA] [perforce] (JENKINS-7436) Add support for perforce shelve builds

2013-06-28 Thread john.mcgo...@openwave.com (JIRA)















































John McGowan
 commented on  JENKINS-7436


Add support for perforce shelve builds















We've been doing precommit/shelved builds for a good while in a build step prior to the main job. Parameterized build with the p4 shelve number as input. I "Run buildstep before SCM":

#!/bin/bash -ex

p4 revert ...

The before the main build task I run this (this is on a clean and new workspace everytime btw): 

if [ $SHELVE != 0 ]; then

	Unshelve the p4 shelve list supplied in the parameter 'SHELVE'
p4 unshelve -s $SHELVE
if [ $? -ne 0 ]; then
echo "Unshelving change $SHELVE hasn't worked, aborting"
exit 1
fi
else
echo "Input a value for the P4 shelve command or else you're just building the latest nightly code, which is covered in another job"
exit 1
fi





























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] [perforce] (JENKINS-7436) Add support for perforce shelve builds

2013-06-28 Thread john.mcgo...@openwave.com (JIRA)













































 
John McGowan
 edited a comment on  JENKINS-7436


Add support for perforce shelve builds
















We've been doing precommit/shelved builds for a good while in a build step prior to the main job. Parameterized build with the p4 shelve number as input. I run "Run buildstep before SCM":

#!/bin/bash -ex

p4 revert ...

Then before the main build task I run this (this is on a clean and new workspace everytime btw): 

if [ $SHELVE != 0 ]; then

	Unshelve the p4 shelve list supplied in the parameter 'SHELVE'
p4 unshelve -s $SHELVE
if [ $? -ne 0 ]; then
echo "Unshelving change $SHELVE hasn't worked, aborting"
exit 1
fi
else
echo "Input a value for the P4 shelve command or else you're just building the latest nightly code, which is covered in another job"
exit 1
fi





























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] [warnings] (JENKINS-18545) Output Escaping / ANSI coloring

2013-06-28 Thread tho...@thomasfischer.biz (JIRA)















































Thomas Fischer
 created  JENKINS-18545


Output Escaping / ANSI coloring















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Ulli Hafner



Components:


warnings



Created:


28/Jun/13 4:13 PM



Description:


it seems that the warnings plugin does not strip escape codes (http://en.wikipedia.org/wiki/ANSI_escape_code) before its parsing the output?

Could this please be improved, that would be awesome to have it working together with the rest of the system running with colors correctly.

Some possible quick starts:

	http://serverfault.com/questions/71285/in-centos-4-4-how-can-i-strip-escape-sequences-from-a-text-file
	http://stackoverflow.com/questions/14652538/remove-ascii-color-codes



Thank you very much, awesome plugin otherwise 




Environment:


- colorgcc

- GNU Make + GNU Compiler (gcc) Warnings

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




Project:


Jenkins



Labels:


warnings
ansicolor




Priority:


Minor



Reporter:


Thomas Fischer

























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] [publish-over-ssh] (JENKINS-18546) Provide a possibility to run post build action manually

2013-06-28 Thread ms-jenk...@256bit.org (JIRA)















































Marc Schoechlin
 created  JENKINS-18546


Provide a possibility to run post build action manually















Issue Type:


New Feature



Assignee:


bap



Components:


publish-over-ssh



Created:


28/Jun/13 4:14 PM



Description:


I would like to have a possibility to publish the build artifacts and to execute a command on the remote host manually.

Please provide a config option "Run post-build action manually" and a text-input for the menu label.
The defined menulabel should appear with the defined text as a link in the job menu which can be used to trigger this action manually.






Project:


Jenkins



Priority:


Major



Reporter:


Marc Schoechlin

























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] [build-flow] (JENKINS-18547) Definition of flow appears in BuildTriggers section

2013-06-28 Thread te...@java.net (JIRA)















































teilo
 created  JENKINS-18547


Definition of flow appears in BuildTriggers section















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


build-flow



Created:


28/Jun/13 4:21 PM



Description:


IN the job configuration for a new build flow the "define build flow" is in the "Build Triggers" section.

This is presumably as there is no "Build" section header which is expected and present in Maven2/3 and freestyle jobs.




Project:


Jenkins



Priority:


Minor



Reporter:


teilo

























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] [teamconcert] (JENKINS-18548) Release build runs different than manual build

2013-06-28 Thread sco...@ca.ibm.com (JIRA)















































Scott Cowan
 created  JENKINS-18548


Release build runs different than manual build















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


teamconcert



Created:


28/Jun/13 4:37 PM



Description:


I just tried to release teamconcert 1.0.6, and the release ran fine on my client machine, but the build failed,
https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/31

Then I manually requested a build with no changes and it succeeded,
https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/32

I did a diff of the logs and found some additional logged entries in the successful build that seem related to the error reported in the failed build.  They are at the bottom.

This all seems related to the special requirements of our plugin that lead us to using a file repo, https://github.com/jenkinsci/teamconcert-plugin/tree/master/com.ibm.team.build.hjplugin/repo

See history of our plugin requirements for reference here, https://groups.google.com/forum/?fromgroups#!searchin/jenkinsci-dev/cowan/jenkinsci-dev/aFN3wcTt2Sw/hB8nDczGU14J

CONSOLE LOG:

DEBUG Using connector WagonRepositoryConnector with priority 0 for http://repo.cloudbees.com/content/repositories/central
DEBUG Using connector WagonRepositoryConnector with priority 0 for file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo
Downloading: http://repo.cloudbees.com/content/repositories/central/org/kohsuke/stapler/stapler/maven-metadata.xml
DEBUG Using connector WagonRepositoryConnector with priority 0 for http://repo.jenkins-ci.org/public/
Downloading: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/maven-metadata.xml
Downloading: file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo/org/kohsuke/stapler/stapler/maven-metadata.xml

DEBUG Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties
457/457 B  
457/457 B   4/6 KB  
457/457 B   6/6 KB  

Downloaded: http://repo.cloudbees.com/content/repositories/central/org/kohsuke/stapler/stapler/maven-metadata.xml (457 B at 4.7 KB/sec)
DEBUG Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties

Downloaded: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/maven-metadata.xml (6 KB at 38.4 KB/sec)
DEBUG Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties
DEBUG Could not find metadata org.kohsuke.stapler:stapler/maven-metadata.xml in hjplugin-rtc-repo (file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo)
DEBUG Could not find metadata org.kohsuke.stapler:stapler/maven-metadata.xml in local (/home/jenkins/.m2/repository)
DEBUG Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session.
DEBUG Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session.
DEBUG Failure to find org.kohsuke.stapler:stapler/maven-metadata.xml in file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo was cached in the local repository, resolution will not be reattempted until the update interval of hjplugin-rtc-repo has elapsed or updates are forced
DEBUG Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session.
DEBUG Using connector WagonRepositoryConnector with priority 0 for http://download.java.net/maven/2/
Downloading: http://download.java.net/maven/2/org/kohsuke/stapler/stapler/maven-metadata.xml
4/5 KB  
5/5 KB  
5/5 KB  






Fix Versions:


current



Project:


Jenkins



Labels:

[JIRA] [grails] (JENKINS-8535) Build should not be marked as failed when tests do not pass

2013-06-28 Thread g...@thepinkhams6.com (JIRA)















































Gary Pinkham
 commented on  JENKINS-8535


Build should not be marked as failed when tests do not pass















@Alex..forgive me for muddying Jira with the question but seems like the one that gets installed via the plugins interface in jenkins is quite old.. how does one get the version with your changes..just clone from github and build myself?  (I should probably RTFM eh?)



























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] [grails] (JENKINS-8535) Build should not be marked as failed when tests do not pass

2013-06-28 Thread agander...@cantab.net (JIRA)















































Alex Anderson
 commented on  JENKINS-8535


Build should not be marked as failed when tests do not pass















IIRC (it's been a few months), `git clone ___ jenkins-grails; cd jenkins-grails; mvn package`.

This should make an hpi file in ./target/, which you can then install via the Jenkins management GUI.



























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] [perforce] (JENKINS-18549) No timeout on polling threads

2013-06-28 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 created  JENKINS-18549


No timeout on polling threads















Issue Type:


Bug



Assignee:


Rob Petti



Components:


perforce



Created:


28/Jun/13 4:55 PM



Description:


A couple of days ago there was a brief outage on my perforce connection (no longer than an hour). However I now have a list (https://hostname/descriptor/hudson.triggers.SCMTrigger/) of 9 threads that have been running for 2 days 3 hr.
This is not good.




Environment:


Jenkins 1.518, Perforce plugin 1.3.24




Project:


Jenkins



Priority:


Major



Reporter:


James Howe

























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] [android-emulator] (JENKINS-13785) Use Google Apis SDK Add-on via Target ID fails

2013-06-28 Thread david.muel...@visionera.de (JIRA)

David Müller
commented on JENKINS-13785

Use Google Apis SDK Add-on via Target ID fails

Sorry for the delay in responding - with actual Versions of the jenkins android emulator plugin it now works.
I'm not sure what else I changed, I might have simply forgotten to put the target in quotes, like

Google Inc.:Google APIs:7

instead of

"Google Inc.:Google APIs:7".
That part of the jenkins job history is lost, so I can't be sure.

The build problems I meant where: the sdk could not be downloaded, or the integration tests failed to run on the emulator like this:

ERROR Failed to execute goal com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.1.1:internal-integration-test (default-internal-integration-test)

I remember this happened always when I configured the android emulator plugin for "Run emulator with properties". I worked around the problem by manually updateing the sdks, and starting the matrix build once with "Run emulator with properties", thereby creating the avds, and then changing the configuration to "Run existing emulator".

As stated above, this is not neccessary anymore with the actual versions of maven android and Jenkins android Emulator plugins.

Thanks a lot for the plugin!

[JIRA] [perforce] (JENKINS-18549) No timeout on polling threads

2013-06-28 Thread rob.pe...@gmail.com (JIRA)
















































Rob Petti
 resolved  JENKINS-18549 as Duplicate


No timeout on polling threads
















Change By:


Rob Petti
(28/Jun/13 5:00 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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







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

[JIRA] [warnings] (JENKINS-18290) cpplint.py outputs not handled by Warnings plugin















































SCM/JIRA link daemon
 commented on  JENKINS-18290


cpplint.py outputs not handled by Warnings plugin















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/warnings/parser/CppLintParser.java
 src/test/java/hudson/plugins/warnings/parser/CppLintParserTest.java
 src/test/resources/hudson/plugins/warnings/parser/issue18290.txt
http://jenkins-ci.org/commit/warnings-plugin/1248c6e958d5ad2c58906043e522f337c813d947
Log:
  FIXED JENKINS-18290 Improved regexp of CPPLint parser.
Now old and new formats could be parsed.






























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] [warnings] (JENKINS-18290) cpplint.py outputs not handled by Warnings plugin
















































SCM/JIRA link daemon
 resolved  JENKINS-18290 as Fixed


cpplint.py outputs not handled by Warnings plugin
















Change By:


SCM/JIRA link daemon
(28/Jun/13 5:09 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [parameterized-trigger] (JENKINS-18534) Cannot add new build to queue from same project with different parameters















































Shannon Kerr
 commented on  JENKINS-18534


Cannot add new build to queue from same project with different parameters















OK, I think I've isolated the root of this issue.  It appears that the plugin is not honoring unique values for "List Subversion Tags" type parameter.  So, if the only parameter value that is different between two build executions is the Tag or Branch selected by the user, Jenkins will combine the two and user the branch or tag selected by the second build request.

To help my team get around this for now, I've added a new parameter requesting the user type in their name.  This will keep Jim from clobbering Suzy etc.  It won't keep Jim from clobbering Jim's other branch build though.



























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] [nunit] (JENKINS-17521) javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.

Charles Forcey
commented on JENKINS-17521

javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.

We have what might be a related issue. Several of our Rspec tests contain UTF-8 characters. These are stored as UTF-8 text files, have the comment #encoding: utf-8 at the top which hints to Ruby that the source code is not ascii, and perform perfectly in our test suite. When the Jenkins job is complete, a gem called ci_reporter compiles our test results into a reports directory. Somewhere in that after(:all) hook the following error is thrown:

{{ An error occurred in an after(:all) hook. Errno::EPERM: Operation not permitted - Operation not permitted - some/ç?¾å¤‡çŽ¯/coolå¢ƒåº”/path/ç”¨å?¯åŠ¨ occurred at org/jruby/RubyFile.java:1063:in `unlink' }}

The build goes on to succeed, but I think processing this unicode in the XML is causing either an issue. The RubyFile.java reference makes me think this might be our version of jruby (locked at 1.7.1 might be the villain). But I wanted to add this here in case a piece of the Jenkins stack has UTF sensitivities in XML. I think that is unlikely but more information may help us all track this to the root cause. Cheers! C

[JIRA] [nunit] (JENKINS-17521) javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.

Charles Forcey
edited a comment on JENKINS-17521

javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.

NOTE: This is NOT related! We had a real error messaging being fired off by one of our tests and Jenkins was just passing it along. Apologies for the distraction! That said, the actual UTF does not make it into the error report (Chinese characters in this case) so at some point in the chain the UTF is lost. On a terminal, the same test displays the error message and the original UTF.

[JIRA] [nunit] (JENKINS-17521) javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.

Charles Forcey
edited a comment on JENKINS-17521

javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.

UPDATE: This is probably not related to the issue above! We had a real error messaging being fired off by one of our tests and Jenkins was just passing it along, though admittedly turning a UTF error message into scrambled ascii at some point along the way. That said, the actual UTF does not make it into the error report (Chinese characters in this case) so at some point in the chain the UTF is lost. On a terminal, the same test displays the error message and the original UTF.

{{An error occurred in an after(:all) hook. Errno::EPERM: Operation not permitted - Operation not permitted - some/ç?¾å¤‡çŽ¯/coolå¢ƒåº”/path/ç”¨å?¯åŠ¨ occurred at org/jruby/RubyFile.java:1063:in `unlink'}}

[JIRA] [nunit] (JENKINS-17521) javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.

Charles Forcey
edited a comment on JENKINS-17521

javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.

[JIRA] [nunit] (JENKINS-17521) javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.

Charles Forcey
edited a comment on JENKINS-17521

javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.

This is probably not related to the issue above! We have real error messaging being fired off by one of our tests around UTF characters. Jenkins is passing it along, but it or one of our reporting tools in between is turning a UTF error message into scrambled ascii at some point along the way. On a terminal, the same test displays the error message and the original UTF.

Original error message:

An error occurred in an after(:all) hook.
Errno::EPERM: Operation not permitted - Operation not permitted - some/灾备环/cool境应/path/用启动
occurred at org/jruby/RubyFile.java:1063:in `unlink'

Jenkins reported error:

An error occurred in an after(:all) hook.
Errno::EPERM: Operation not permitted - Operation not permitted - some/ç?¾å¤‡çŽ¯/coolå¢ƒåº”/path/ç”¨å?¯åŠ¨ occurred at org/jruby/RubyFile.java:1063:in
`unlink'}}

The build goes on to succeed, but I think Jenkins or one of our tools is mangling the UTF of the error output by the time it ends up in the job log. Cheers! C

[JIRA] [coverity] (JENKINS-18551) Coverity Plugin Is Incompatible with MSBuild Plugin

2013-06-28 Thread cwo...@gmail.com (JIRA)















































Chris Wozny
 created  JENKINS-18551


Coverity Plugin Is Incompatible with MSBuild Plugin















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


coverity



Created:


28/Jun/13 7:48 PM



Description:


Coverity works with MSBuild only when the user creates their own MSBuild script via a "Execute Windows batch command" build step and executes the following command:

Builds $ C:\Coverity\CIC\static-analysis\bin\cov-build --dir C:\CoverityAnalyzeDir cmd /c call C:\Temp\hudson56334.bat

However, if someone attempts to run Coverity with the MSBuild plugin, the following command gets executed and an error occurs:

JENKINS_COVERITY_TEST $ C:\Coverity\CIC\static-analysis\bin\cov-build --dir C:\CoverityAnalyzeDir cmd.exe /C C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /t:Clean;Build /nologo /p:Configuration=Release %BUILD_DIRECTORY%\Project.sln  EXIT %%ERRORLEVEL%%
The filename, directory name, or volume label syntax is incorrect.




Environment:


Windows Server 2008, Java 1.6.0_43, Jenkins 1.517, Coverity Plugin 1.2.3, MSBuild Plugin 1.16




Fix Versions:


current



Project:


Jenkins



Labels:


coverity
msbuild
jenkins




Priority:


Minor



Reporter:


Chris Wozny

























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] [coverity] (JENKINS-18551) Coverity Plugin Is Incompatible with MSBuild Plugin

2013-06-28 Thread cwo...@gmail.com (JIRA)















































Chris Wozny
 commented on  JENKINS-18551


Coverity Plugin Is Incompatible with MSBuild Plugin















This issue probably is linked to the use of the Windows environment variables. Linking to issue 14833.



























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] [clover] (JENKINS-18552) Update Clover Plugin to version 3.1.12

2013-06-28 Thread mparfianow...@atlassian.com (JIRA)















































Marek Parfianowicz
 created  JENKINS-18552


Update Clover Plugin to version 3.1.12















Issue Type:


Improvement



Affects Versions:


current



Assignee:


stephenconnolly



Components:


clover



Created:


28/Jun/13 8:49 PM



Description:


Clover 3.1.12 has been released. Jenkins Clover Plugin can use newer version. 
(currently it uses 3.1.7, which is nearly 1 year old)




Project:


Jenkins



Priority:


Trivial



Reporter:


Marek Parfianowicz

























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] [coverity] (JENKINS-18551) Coverity Plugin Is Incompatible with MSBuild Plugin

2013-06-28 Thread cwo...@gmail.com (JIRA)















































Chris Wozny
 updated  JENKINS-18551


Coverity Plugin Is Incompatible with MSBuild Plugin
















Change By:


Chris Wozny
(28/Jun/13 9:16 PM)




Description:


CoverityworkswithMSBuildonlywhentheusercreatestheirownMSBuildscriptviaaExecuteWindowsbatchcommandbuildstepandexecutesthefollowingcommand:[Builds]$C:\Coverity\CIC\static-analysis\bin\cov-build--dirC:\CoverityAnalyzeDircmd/ccallC:\Temp\hudson56334.batHowever,ifsomeoneattemptstorunCoveritywiththeMSBuildplugin
whichhasenvironmentvariablesinit
,thefollowingcommandgetsexecutedandanerroroccurs:[JENKINS_COVERITY_TEST]$C:\Coverity\CIC\static-analysis\bin\cov-build--dirC:\CoverityAnalyzeDircmd.exe/CC:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe/t:Clean;Build/nologo/p:Configuration=Release%BUILD_DIRECTORY%\Project.slnEXIT%%ERRORLEVEL%%Thefilename,directoryname,orvolumelabelsyntaxisincorrect.



























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] [gerrit-trigger] (JENKINS-10709) multiple builds are triggered for one change in Gerrit

2013-06-28 Thread aerick...@gmail.com (JIRA)















































Andrew Erickson
 commented on  JENKINS-10709


multiple builds are triggered for one change in Gerrit















Seeing this on Jenkins 1.520 with Gerrit Trigger 2.10.0. We never had the problem before, but recently started generating configs from templates and reloading from disk.

Paul, could you post a diff? Robert, any opinions thoughts on Paul's approach?

Thanks,
Andy



























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] [testng] (JENKINS-18498) TestNG reports not working on specific build.

2013-06-28 Thread nul...@nullin.com (JIRA)















































Nalin Makar
 commented on  JENKINS-18498


TestNG reports not working on specific build.















Do you also have Junit Test Reports enabled on the same build at the same time as having TestNG Test Reports enabled?



























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] [testng] (JENKINS-18498) TestNG reports not working on specific build.

2013-06-28 Thread nul...@nullin.com (JIRA)













































 
Nalin Makar
 edited a comment on  JENKINS-18498


TestNG reports not working on specific build.
















Do you also have Junit Test Reports enabled on the same build at the same time as having TestNG Test Reports enabled?

Also, is the job a Maven build or a Free Style build?



























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







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

[JIRA] [clover] (JENKINS-18552) Update Clover Plugin to version 3.1.12

2013-06-28 Thread mparfianow...@atlassian.com (JIRA)















































Marek Parfianowicz
 commented on  JENKINS-18552


Update Clover Plugin to version 3.1.12















https://github.com/jenkinsci/clover-plugin/pull/8



























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] [view-job-filters] (JENKINS-18386) more flexible job filter by parameter















































SCM/JIRA link daemon
 commented on  JENKINS-18386


more flexible job filter by parameter















Code changed in jenkins
User: jacob_robertson
Path:
 src/main/java/hudson/views/MostRecentJobsFilter.java
 src/main/java/hudson/views/ParameterFilter.java
 src/main/java/hudson/views/RegExJobFilter.java
 src/main/resources/hudson/views/MostRecentJobsFilter/config.jelly
 src/main/resources/hudson/views/ParameterFilter/config.jelly
 src/main/resources/hudson/views/RegExJobFilter/config.jelly
 src/test/java/hudson/views/ParameterFilterTest.java
http://jenkins-ci.org/commit/view-job-filters-plugin/b10005a320585ed2fa03d6b06064fdb53fa0019c
Log:
  fixed JENKINS-18386, JENKINS-17597, JENKINS-17093, JENKINS-18399






























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] [view-job-filters] (JENKINS-17597) Poor performance using ParameterFilter















































SCM/JIRA link daemon
 commented on  JENKINS-17597


Poor performance using ParameterFilter















Code changed in jenkins
User: jacob_robertson
Path:
 src/main/java/hudson/views/MostRecentJobsFilter.java
 src/main/java/hudson/views/ParameterFilter.java
 src/main/java/hudson/views/RegExJobFilter.java
 src/main/resources/hudson/views/MostRecentJobsFilter/config.jelly
 src/main/resources/hudson/views/ParameterFilter/config.jelly
 src/main/resources/hudson/views/RegExJobFilter/config.jelly
 src/test/java/hudson/views/ParameterFilterTest.java
http://jenkins-ci.org/commit/view-job-filters-plugin/b10005a320585ed2fa03d6b06064fdb53fa0019c
Log:
  fixed JENKINS-18386, JENKINS-17597, JENKINS-17093, JENKINS-18399






























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] [view-job-filters] (JENKINS-17093) Filter to show N jobs sorted by most recently completed















































SCM/JIRA link daemon
 commented on  JENKINS-17093


Filter to show N jobs sorted by most recently completed















Code changed in jenkins
User: jacob_robertson
Path:
 src/main/java/hudson/views/MostRecentJobsFilter.java
 src/main/java/hudson/views/ParameterFilter.java
 src/main/java/hudson/views/RegExJobFilter.java
 src/main/resources/hudson/views/MostRecentJobsFilter/config.jelly
 src/main/resources/hudson/views/ParameterFilter/config.jelly
 src/main/resources/hudson/views/RegExJobFilter/config.jelly
 src/test/java/hudson/views/ParameterFilterTest.java
http://jenkins-ci.org/commit/view-job-filters-plugin/b10005a320585ed2fa03d6b06064fdb53fa0019c
Log:
  fixed JENKINS-18386, JENKINS-17597, JENKINS-17093, JENKINS-18399






























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] [view-job-filters] (JENKINS-18399) possibility to filter jobs by Restrict where this project can be run















































SCM/JIRA link daemon
 commented on  JENKINS-18399


possibility to filter jobs by Restrict where this project can be run















Code changed in jenkins
User: jacob_robertson
Path:
 src/main/java/hudson/views/MostRecentJobsFilter.java
 src/main/java/hudson/views/ParameterFilter.java
 src/main/java/hudson/views/RegExJobFilter.java
 src/main/resources/hudson/views/MostRecentJobsFilter/config.jelly
 src/main/resources/hudson/views/ParameterFilter/config.jelly
 src/main/resources/hudson/views/RegExJobFilter/config.jelly
 src/test/java/hudson/views/ParameterFilterTest.java
http://jenkins-ci.org/commit/view-job-filters-plugin/b10005a320585ed2fa03d6b06064fdb53fa0019c
Log:
  fixed JENKINS-18386, JENKINS-17597, JENKINS-17093, JENKINS-18399






























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] [view-job-filters] (JENKINS-17093) Filter to show N jobs sorted by most recently completed