date:20140901















































Craig Rodrigues
 commented on  JENKINS-24521


Update jna from 3.3.0-jenkins to 4.1.0 (or newer)















I submitted this pull request to update Jenkins to JNA 4.1.0:

https://github.com/jenkinsci/jenkins/pull/1387

It is similar to:

https://github.com/jenkinsci/jenkins/pull/1181

but follows the pattern here: 

http://twall.github.io/jna/4.1.0/com/sun/jna/Structure.html#getFieldOrder%28%29



























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







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

[JIRA] [read-only-configurations] (JENKINS-24458) JobConfiguration doesn't have @ExportedBean so cannot write hudson.model.Actionable.actions

2014-09-01 Thread florent.fie...@siemens.com (JIRA)















































Florent Fievez
 commented on  JENKINS-24458


JobConfiguration doesnt have @ExportedBean so cannot write hudson.model.Actionable.actions















The only workaround I found is to change default log level to SEVERE (/log/levels)



























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







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

[JIRA] [junit] (JENKINS-12869) Maven Build fails when integration/system test executed with failsafe fails.

2014-09-01 Thread t...@gundmann.dk (JIRA)















































Tim Gundmann
 commented on  JENKINS-12869


Maven Build fails when integration/system test executed with failsafe fails.















Any news?



























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







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

[JIRA] [windows-slaves] (JENKINS-24523) Update windows-slave-installer-module to use JNA 4.1.0















































Craig Rodrigues
 created  JENKINS-24523


Update windows-slave-installer-module to use JNA 4.1.0















Issue Type:


Improvement



Assignee:


Kohsuke Kawaguchi



Components:


windows-slaves



Created:


01/Sep/14 9:34 AM



Description:


windows-slave-installer-module needs to be updated to use JNA 4.1.0




Project:


Jenkins



Priority:


Major



Reporter:


Craig Rodrigues

























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







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

[JIRA] [windows-slaves] (JENKINS-24523) Update windows-slave-installer-module to use JNA 4.1.0
















































Craig Rodrigues
 resolved  JENKINS-24523 as Not A Defect


Update windows-slave-installer-module to use JNA 4.1.0
















windows-slave-installer-module does not have jna in it's POM file,
and it does not reference the com.sun.jna.Structure class,
so no code modifications need to be done.





Change By:


Craig Rodrigues
(01/Sep/14 9:41 AM)




Status:


Open
Resolved





Resolution:


NotADefect



























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







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

[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death

2014-09-01 Thread sharon....@emc.com (JIRA)















































sharon xia
 commented on  JENKINS-24453


Jenkins server got blue screen to death















Still see this issue on Jenkins ver. 1.532.3



























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







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

[JIRA] [core] (JENKINS-24353) UI Themes plugin

2014-09-01 Thread sven.appenr...@iav.de (JIRA)













































 
Sven Appenrodt
 edited a comment on  JENKINS-24353


UI Themes plugin
















One of the topics: 
overlapping vs. line wrap in build history. May can be configured as "no wrap and clipped" (see JENKINS-23999)



























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







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

[JIRA] [gerrit] (JENKINS-24445) Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification

2014-09-01 Thread rinrin...@gmail.com (JIRA)















































rin_ne
 updated  JENKINS-24445


Retriggering builds via the Manual Trigger feature of the Gerrit Trigger Plugin causes wrong verification
















Change By:


rin_ne
(01/Sep/14 9:46 AM)




URL:


https://github.com/jenkinsci/gerrit-trigger-plugin/pull/172



























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







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

[JIRA] [windows-slaves] (JENKINS-24524) Update memory-monitor plugin to JNA 4.1.0















































Craig Rodrigues
 created  JENKINS-24524


Update memory-monitor plugin to JNA 4.1.0















Issue Type:


Improvement



Assignee:


Kohsuke Kawaguchi



Components:


windows-slaves



Created:


01/Sep/14 9:51 AM



Description:


The memory-monitor plugin needs to be updated to JNA 4.1.0.

I created this pull request:
https://github.com/jenkinsci/extras-memory-monitor/pull/5




Project:


Jenkins



Priority:


Major



Reporter:


Craig Rodrigues

























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







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

[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death

2014-09-01 Thread sharon....@emc.com (JIRA)















































sharon xia
 commented on  JENKINS-24453


Jenkins server got blue screen to death















Could you please let me know how to run a normal user(not administrator)run jenkins? I followed the guide but it failed: http://technet.microsoft.com/en-us/library/cc787533%28v=WS.10%29.aspx

Currently this crash issue happens more than once a day...



























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







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

[JIRA] [repository] (JENKINS-24525) Yum repo for LTS points to wronng version which is not in the repository

2014-09-01 Thread vittorio.bocc...@dectris.com (JIRA)















































Vittorio Boccone
 created  JENKINS-24525


Yum repo for LTS  points to wronng version which is not in the repository















Issue Type:


Bug



Affects Versions:


current



Assignee:


magnayn



Components:


repository



Created:


01/Sep/14 10:02 AM



Description:


root@localhost yum.repos.d# yum update jenkins
Resolving Dependencies
-- Running transaction check
--- Package jenkins.noarch 0:1.554.1-1.1 will be updated
--- Package jenkins.noarch 0:1.562-1.1 will be an update
-- Finished Dependency Resolution

Dependencies Resolved


 Package Arch   Version   Repository   Size

Updating:
 jenkins noarch 1.562-1.1 jenkins  59 M

Transaction Summary

Upgrade  1 Package

Total download size: 59 M
Is this ok y/d/N: y
Downloading packages:


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

 1. Contact the upstream for the repository and get them to fix the problem.

 2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

 3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:

yum-config-manager --disable repoid

 4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=repoid.skip_if_unavailable=true

Cannot find a valid baseurl for repo: jenkins




Environment:


Fedora 19 on a x86_64




Project:


Jenkins



Priority:


Minor



Reporter:


Vittorio Boccone

























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







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

[JIRA] [pam-auth] (JENKINS-24526) Update libpam4j to use JNA 4.1.0















































Craig Rodrigues
 created  JENKINS-24526


Update libpam4j to use JNA 4.1.0















Issue Type:


Improvement



Assignee:


Unassigned


Components:


pam-auth



Created:


01/Sep/14 10:07 AM



Description:


libpam4j needs to be updated to use JNA 4.1.0

I have submitted a pull request here:

https://github.com/kohsuke/libpam4j/pull/10




Project:


Jenkins



Priority:


Major



Reporter:


Craig Rodrigues

























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







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

[JIRA] [subversion] (JENKINS-17900) subversion credentials are not stored in hudson.scm.SubversionSCM.xml

2014-09-01 Thread schristo...@gmail.com (JIRA)
















































Steven Christou
 resolved  JENKINS-17900 as Wont Fix


subversion credentials are not stored in hudson.scm.SubversionSCM.xml
















Motonori IWAMURO, 2.0+ version of the subversion plugin does not use the https://JENKINS_URL/scm/SubversionSCM/enterCredentials or the SubversionSCM.xml for authentication anymore. Instead the plugin uses the Credentials Plugin





Change By:


Steven Christou
(01/Sep/14 10:29 AM)




Status:


Reopened
Resolved





Assignee:


StevenChristou





Resolution:


WontFix



























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







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

[JIRA] [core] (JENKINS-21621) bad path environment set by Jenkins

2014-09-01 Thread ilie.danielste...@gmail.com (JIRA)















































ilie daniel
 commented on  JENKINS-21621


bad path environment set by Jenkins















1577 jenkins version
Running a batch from jenknins with content:
@echo on
set a
set b
set c
set d
set e
set f
set g
set h
set i
set j
set k
set l
set m
set n
set o
set p
set r
set s
set t
set q
set u
set v
set w
set x
set y
set z

setoutputEnvironment.txt

will lead to the same problem with Path variable



























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







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

[JIRA] [core] (JENKINS-21621) bad path environment set by Jenkins

2014-09-01 Thread ilie.danielste...@gmail.com (JIRA)













































 
ilie daniel
 edited a comment on  JENKINS-21621


bad path environment set by Jenkins
















1577 jenkins version
Running a batch file from jenknins with content:
@echo on
set a
set b
set c
set d
set e
set f
set g
set h
set i
set j
set k
set l
set m
set n
set o
set p
set r
set s
set t
set q
set u
set v
set w
set x
set y
set z

setoutputEnvironment.txt

will lead to the same problem with Path variable



























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







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

[JIRA] [core] (JENKINS-24527) Update jna-posix so that it can compile with JNA 4.1.0















































Craig Rodrigues
 created  JENKINS-24527


Update jna-posix so that it can compile with JNA 4.1.0















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


01/Sep/14 10:55 AM



Description:


jna-posix does not compile with JNA 4.1.0.  It needs to be updated.
I filed this bug against jna-posix: https://kenai.com/jira/browse/JNA_POSIX-2
but it looks like that project is not very active.




Project:


Jenkins



Priority:


Major



Reporter:


Craig Rodrigues

























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







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

[JIRA] [core] (JENKINS-24527) Update jna-posix so that it can compile with JNA 4.1.0















































Craig Rodrigues
 commented on  JENKINS-24527


Update jna-posix so that it can compile with JNA 4.1.0















This patch fixes the problem and works with JNA 4.1.0:

https://github.com/rodrigc/jna-posix/commit/cb8c9f1ce7aff65ca54f61b4404cffba3d55852e



























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







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

[JIRA] [core] (JENKINS-23271) Intermittent Ivalid Object ID in remoting module

2014-09-01 Thread vinc...@latombe.net (JIRA)
















































Vincent Latombe
 assigned  JENKINS-23271 to Unassigned



Intermittent Ivalid Object ID in remoting module
















Change By:


Vincent Latombe
(01/Sep/14 11:47 AM)




Assignee:


VincentLatombe



























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







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

[JIRA] [core] (JENKINS-21621) bad path environment set by Jenkins

2014-09-01 Thread ilie.danielste...@gmail.com (JIRA)













































 
ilie daniel
 edited a comment on  JENKINS-21621


bad path environment set by Jenkins
















I think that is the same issue :https://issues.jenkins-ci.org/browse/JENKINS-11992 



























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







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

[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death

2014-09-01 Thread sharon....@emc.com (JIRA)

sharon xia
commented on JENKINS-24453

Jenkins server got blue screen to death

I took a look at the windows dump file, the blue screen is caused by java.exe which called jenkins.

GetPointerFromAddress: unable to read from f800018be000
PROCESS fa804b96db30
SessionId: none Cid: 053cPeb: 7fd5000 ParentCid: 04f8
DirBase: 82c93e000 ObjectTable: f8a001823860 HandleCount: Data Not Accessible
Image: java.exe
VadRoot fa804bdb6680 Vads 972 Clone 0 Private 744164. Modified 258616. Locked 58.
DeviceMap f8a0019d4cc0
Token f8a001c0da30
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
f780: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime00:00:00.000
QuotaPoolUsagePagedPool 0
QuotaPoolUsageNonPagedPool 0
Working Set Sizes (now,min,max) (746794, 50, 345) (2987176KB, 200KB, 1380KB)
PeakWorkingSetSize747257
VirtualSize 20052 Mb
PeakVirtualSize 20075 Mb
PageFaultCount1577231
MemoryPriorityBACKGROUND
BasePriority 8
CommitCharge 1015778

Error in reading nt!_ETHREAD @ fa804b971a30

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

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

[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)

2014-09-01 Thread romuald.ginh...@axilumrobotics.com (JIRA)
















































Daniel Beck
 resolved  JENKINS-22750 as Fixed


Polling no longer triggers builds (regression 1.560)
















Kirill Peskov: Please file a new issue. Yours is only superficially similar to this one, and we don't need to keep the ~80 people watching this one informed about the investigation related to your (different) issue.





Change By:


Daniel Beck
(01/Sep/14 12:49 PM)




Status:


Reopened
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/d/optout.

[JIRA] [master-slave] (JENKINS-11992) Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing ' \Java\jre6\bin was unexpected at this time.' error

2014-09-01 Thread ilie.danielste...@gmail.com (JIRA)















































ilie daniel
 commented on  JENKINS-11992


Win7 x64: x86 Java runtime creates bad PATH on x64 OS causing  \Java\jre6\bin was unexpected at this time. error















Workaround for my ant script:
	target name="runBat"

		!-- Remove quotes from Path: https://issues.jenkins-ci.org/browse/JENKINS-11992 --
		loadresource property="clean.Path"
			propertyresource name="env.Path" /
			filterchain
tokenfilter
	filetokenizer /
	replacestring from="" to="" /
/tokenfilter
			/filterchain
		/loadresource

		exec executable="cmd.exe" spawn="yes" vmlauncher="false" dir="./${run.dir}"
			env key="BUILD_ID" value="dontKillMe" /
			env key="Path" value="${clean.Path}" /
			arg line="/k call ${bat.file}" /
		/exec
	/target



























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







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

[JIRA] [mstestrunner] (JENKINS-24528) Test Category Field does not accept environnement variables















































Romuald Ginhoux
 created  JENKINS-24528


Test Category Field does not accept environnement variables















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


Capture.PNG



Components:


mstestrunner



Created:


01/Sep/14 1:16 PM



Description:


I use MSTestRunner in a parameterized build to define the test category I want to run from the user interactively choosing the name of category in a dropdown list when starting the build. According to the parameterized build plugin, the variable is defined as an environment variable. I can access to its value successufully using %UserChoice% from a batch command inside the job. However, the MSTestRunner plugin does not accept to read %UserChoice% when I type it in in the TestCategory field. I get an error (see attached screenshot): "the model of the chain is not valid"




Project:


Jenkins



Priority:


Major



Reporter:


Romuald Ginhoux

























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







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

[JIRA] [subversion] (JENKINS-17900) subversion credentials are not stored in hudson.scm.SubversionSCM.xml















































Daniel Beck
 commented on  JENKINS-17900


subversion credentials are not stored in hudson.scm.SubversionSCM.xml















Steven Christou:
Still some cleanup left as I stated above:
https://github.com/jenkinsci/subversion-plugin/blob/master/src/main/resources/hudson/scm/SubversionSCM/DescriptorImpl/url-help.properties#L33



























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







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

[JIRA] [git] (JENKINS-24467) ssh not found by git because PATH has been unexpectedly changed

2014-09-01 Thread langer...@gmail.com (JIRA)















































Rob Langley
 commented on  JENKINS-24467


ssh not found by git because PATH has been unexpectedly changed















Having spent a little more time looking at this, the above will cause JENKINS-22009 to reoccur, I think a better solution would be the following:


diff --git a/src/main/java/hudson/plugins/git/util/GitUtils.java b/src/main/java/hudson/plugins/git/util/GitUtils.java
index 3d41ad3..d770209 100644
--- a/src/main/java/hudson/plugins/git/util/GitUtils.java
+++ b/src/main/java/hudson/plugins/git/util/GitUtils.java
@@ -266,8 +266,8 @@ public class GitUtils implements Serializable {
 if (buildActions != null) {
 for (Action action : buildActions) {
 // most importantly, ParametersAction will be processed here (for parameterized builds)
-if (action instanceof EnvironmentContributingAction) {
-EnvironmentContributingAction envAction = (EnvironmentContributingAction) action;
+if (action instanceof ParametersAction) {
+ParametersAction envAction = (ParametersAction) action;
 envAction.buildEnvVars(b, env);
 }
 }



EnvironmentContributingAction is too wider net where are I believe ParametersAction will be much better. At least with my testing it looks to do the right thing with or without EnvInject installe. @danielbeck - it should only add parameters rather then environment variables which should avoid any instance of copying of node specific environments. It also passes the test case added for JENKINS-22009.

As for a test case, I'm not sure. EnvInject hit this as EnvInjectPluginAction implements EnvironmentContributingAction, is it possible to set something in a test to create some thing similar?



























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







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

[JIRA] [git] (JENKINS-24529) Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes

2014-09-01 Thread kirill...@gmail.com (JIRA)















































Kirill Peskov
 created  JENKINS-24529


Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git, virtualbox



Created:


01/Sep/14 1:46 PM



Description:


The bug is similar to 22750 but according to developer's request is filed here as separate issue.

It's easily reproducible in following configuration:

Server: most recent Bitnami Appliance (Ubuntu-based), jenkins.war manually upgraded to 1.577
Slaves: 1 'cloud' in-demand slave, managed by virtualbox plugin, Ubuntu 14.04 LTS x86_64 with OS 'native' LAMP stack.
SCM: git in local network on a separate server, accessible by ssh  git protocols
Job: default 'free-style job', with Build Trigger set to 'Poll SCM' once per hour (doesn't matter fixed or randomized), tied by node name to the particular slave (in-demand cloud VB slave)

Manual job triggering brings the node online and after the configured delay (3 min in my case) jenkins proceeds with the rest of the job. Changes in SCM cannot trigger the build, git polling log shows the message: "We need to schedule a new build to get a workspace, but deferring in the hope that one will become available soon (all_suitable_nodes_are_offline)".

This is not just a bug, it's a sort of logical trap. Jenkins has to make the decision to power up slave node(s) based on the results of SCM Polling, but unable to do that, because the very SCM Polling can be done only on the node(s) which are currently offline.




Environment:


Server: most recent Bitnami Appliance (Ubuntu-based), jenkins.war manually upgraded to 1.577

Slaves: 1 cloud in-demand slave, managed by virtualbox plugin, Ubuntu 14.04 LTS x86_64 with OS native LAMP stack.

Hypervisor: Virtualbox 4.3.14 on Ubuntu 14.04 LTS x86_64 




Project:


Jenkins



Labels:


plugin
git
jenkins
slave
scm
trigger
virtualbox




Priority:


Major



Reporter:


Kirill Peskov

























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







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

[JIRA] [subversion] (JENKINS-17900) subversion credentials are not stored in hudson.scm.SubversionSCM.xml

2014-09-01 Thread schristo...@gmail.com (JIRA)















































Steven Christou
 commented on  JENKINS-17900


subversion credentials are not stored in hudson.scm.SubversionSCM.xml















Daniel Beck I believe this is kept in for legacy plugins like the SCM Sync Plugin, and others that have not migrated to the new credentials plugin.



























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







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

[JIRA] [git] (JENKINS-24529) Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes















































Daniel Beck
 commented on  JENKINS-24529


Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes















Did you configure Git SCM in a way that requires a workspace to poll, e.g. include/exclude paths? The very basic "only a repository" should work without requiring a workspace.



























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







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

[JIRA] [core] (JENKINS-16018) Not all builds show in the build history dashboard on job

Daniel Beck
resolved JENKINS-16018 as Cannot Reproduce

Not all builds show in the build history dashboard on job

Since nobody watching this provided additional information since I posted the previous comment, I'm resolving this as cannot reproduce.

If you experience this issue on a Jenkins release no older than eight weeks (LTS or latestgreatest), please file a new bug against core and include ALL the information asked for in the preceding comment.

In the preceding comment I also explain why this issue description and the comments are not useful in getting this issue resolved. In essence, too little real information is provided here, and comments seem to contradict, indicating different causes. Newly filed issues won't have this problem.

If you're using a version older than eight weeks, and cannot reproduce the problem (or did not try to do so) on a current Jenkins version, please refrain from filing a new issue. Many issues in Jenkins get fixed during normal development and it's a waste of time trying to investigate long resolved issues.

Change By:

Daniel Beck
(01/Sep/14 2:35 PM)

Status:

Open
Resolved

Resolution:

CannotReproduce

[JIRA] [core] (JENKINS-16775) Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpl's signer information does not match signer information of other clas
















































Daniel Beck
 resolved  JENKINS-16775 as Cannot Reproduce


Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpls signer information does not match signer information of other classes in the same package
















No response to comment asking for updated information in three weeks, so resolving as Cannot Reproduce.





Change By:


Daniel Beck
(01/Sep/14 2:36 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/d/optout.

[JIRA] [core] (JENKINS-18756) All builds fail with NoSuchElementException from Treemap.putAll
















































Daniel Beck
 resolved  JENKINS-18756 as Incomplete


All builds fail with NoSuchElementException from Treemap.putAll
















No response to comment asking for additional information in months, so resolving as Incomplete.

Please file a new issue if you experience this problem during normal Jenkins operation with a version no older than eight weeks.





Change By:


Daniel Beck
(01/Sep/14 2:38 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























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







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

[JIRA] [git] (JENKINS-24529) Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes

2014-09-01 Thread kirill...@gmail.com (JIRA)















































Kirill Peskov
 commented on  JENKINS-24529


Poll SCM Job Trigger (git) does not wake up VirtualBox on-demand slave nodes















Only a repository. Via native git protocol, e.g. 

Repository URL: git://hostname/repo-name.git
Branch specifier: left blank, but has been replaced by Jenkins with '**'
Repository browser: (Auto)



























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







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

[JIRA] [core] (JENKINS-17003) JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect















































Daniel Beck
 updated  JENKINS-17003


JNLP Slave on Windows Server 2012 will not reconnect to master after network disconnect/reconnect
















Change By:


Daniel Beck
(01/Sep/14 2:43 PM)




Labels:


jnlp
remoting
serviceslavewindows



























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







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

[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456















































Daniel Beck
 updated  JENKINS-13253


Slave connection reset issues since 1.456
















Change By:


Daniel Beck
(01/Sep/14 2:43 PM)




Labels:


remoting



























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







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

[JIRA] [core] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave















































Daniel Beck
 updated  JENKINS-14332


Repeated channel/timeout errors from Jenkins slave
















Change By:


Daniel Beck
(01/Sep/14 2:43 PM)




Labels:


remoting



























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







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

[JIRA] [core] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel















































Daniel Beck
 updated  JENKINS-6817


FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
















Change By:


Daniel Beck
(01/Sep/14 2:43 PM)




Labels:


remoting



























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







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

[JIRA] [crowd] (JENKINS-17288) Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly















































Daniel Beck
 updated  JENKINS-17288


Packaging of spring-context-support causes crowd plugin to prevent Jenkins starting properly
















Removing core component. Issues like these are what PluginFirstClassloader is designed for, and if not using that, it's no surprise this breaks.





Change By:


Daniel Beck
(01/Sep/14 2:45 PM)




Component/s:


core



























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







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

[JIRA] [core] (JENKINS-19758) Jenkins: [reproducible] ssh slave log not available, spinning wheel after upgrading to SSH Credentials 1.4, SSH Slaves 1.2 and disconnecting/reconnecting















































Daniel Beck
 commented on  JENKINS-19758


Jenkins: [reproducible] ssh slave log not available, spinning wheel after upgrading to SSH Credentials 1.4, SSH Slaves 1.2 and disconnecting/reconnecting















Costin Caraivan: Are you still experiencing this issue on recent Jenkins + plugin versions?



























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







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

[JIRA] [p4] (JENKINS-23890) Error on Maven build with SCM changes















































Paul Allen
 commented on  JENKINS-23890


Error on Maven build with SCM changes 















Very strange?  I have setup a Windows + Maven environment; I did get some other Web/Jelly errors, due to XStream on Java 8.  I upgraded Jenkins to 1.558 and all the errors vanished.  

What version of Jenkins are you using?



























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







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

[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service















































Jan Klass
 commented on  JENKINS-22685


Jenkins cannot restart Windows service















I also have the issue on a 1.565.1 installation.

Jenkins.exe is running as user SYSTEM. I guess it should be able to restart services then!? (Not sure where to find WMI and its service permissions).



























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







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

[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service















































Jan Klass
 commented on  JENKINS-22685


Jenkins cannot restart Windows service















Is the Jenkins auto-war-update sufficient? Or do I need to download and install Jenkins again (where I guess I would get a new Jenkins.exe)?



























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







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

[JIRA] [p4] (JENKINS-24490) 'Poll Only' or 'Disable Sync' option















































Paul Allen
 commented on  JENKINS-24490


Poll Only or Disable Sync option















I had been looking at this issue a few weeks back for another customer.  Frustratingly the code is quite simple to detect/disable the triggering for the parent/children.  The harder part has been adding the option to the UX, so that it appears within the context of Matrix builds.



























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







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

[JIRA] [core] (JENKINS-11543) UTF-8 encoding issue of build parameters as soon as including File parameter

2014-09-01 Thread krizleeb...@java.net (JIRA)















































krizleebear
 commented on  JENKINS-11543


UTF-8 encoding issue of build parameters as soon as including File parameter 















Thanks for the quick reply! 
To be honest I didn't expect to get an update on a topic this old. 
I'm looking forward to see further updates to this issue and of course a 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/d/optout.

[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service















































Jan Klass
 commented on  JENKINS-22685


Jenkins cannot restart Windows service















Indeed; replacing just the jenkins.exe with the one inside the 1.565.1 distribution zip makes the restart work again.
I guess the other reports here likely come from the same misunderstanding. Merely (auto-)upgrading Jenkins (=replacing the war) is not enough.



























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







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

[JIRA] [p4] (JENKINS-24493) P4 Plugin cannot sync symlinks















































Paul Allen
 commented on  JENKINS-24493


P4 Plugin cannot sync symlinks















You need to be running Java 7 or later (symlinks were only recently supported in Java nio).



























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







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

[JIRA] [core] (JENKINS-11543) UTF-8 encoding issue of build parameters as soon as including File parameter















































Daniel Beck
 commented on  JENKINS-11543


UTF-8 encoding issue of build parameters as soon as including File parameter 















krizleebear: It was easy to reproduce and someone confirmed it's still a problem. What's not to love?



Possibly related library issue: https://issues.apache.org/jira/browse/FILEUPLOAD-206

FileUpload fails to handle requests with a form enctype of multipart/form-data;charset=UTF-8, so I doubt this can be resolved client-side (happy to be proven wrong!), so the Stapler fix above seems to be the correct solution for now.



























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







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

[JIRA] [p4] (JENKINS-24512) Add option to lock the created workspace to a host















































Paul Allen
 commented on  JENKINS-24512


Add option to lock the created workspace to a host















Initially I did set the host field, but Jenkins did not reliably give me the correct host (master vs remote slave builds).  I'll look into this again and see if I can extract it from another location.



























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







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

[JIRA] [build-keeper-plugin] (JENKINS-24530) Feature Request: Be able to Combine conditions















































Jan Klass
 created  JENKINS-24530


Feature Request: Be able to Combine conditions















Issue Type:


Bug



Assignee:


bap



Components:


build-keeper-plugin



Created:


01/Sep/14 3:26 PM



Description:


In order to keep a successful build every 30 days but also (first) failure in between, it would be great to be able to combine multiple conditions.




Project:


Jenkins



Priority:


Major



Reporter:


Jan Klass

























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







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

[JIRA] [build-keeper-plugin] (JENKINS-24530) Feature Request: Be able to Combine conditions















































Jan Klass
 updated  JENKINS-24530


Feature Request: Be able to Combine conditions
















Change By:


Jan Klass
(01/Sep/14 3:28 PM)




Issue Type:


Bug
NewFeature



























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







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

[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service

2014-09-01 Thread sschube...@gmail.com (JIRA)















































Sebastian Schuberth
 commented on  JENKINS-22685


Jenkins cannot restart Windows service















 Merely (auto-)upgrading Jenkins (=replacing the war) is not enough.

Thanks for the clarification!



























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







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

[JIRA] [robot-plugin] (JENKINS-24531) There should be high resolution versions of graphs available

2014-09-01 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 created  JENKINS-24531


There should be high resolution versions of graphs available















Issue Type:


Bug



Assignee:


Jussi Malinen



Components:


robot-plugin



Created:


01/Sep/14 4:01 PM



Description:


It would be nice if there was a high resolution version of the graphs available. These could be used in for example slides.




Project:


Jenkins



Priority:


Minor



Reporter:


Jussi Malinen

























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







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

[JIRA] [robot-plugin] (JENKINS-24531) There should be high resolution versions of graphs available

2014-09-01 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 started work on  JENKINS-24531


There should be high resolution versions of graphs available
















Change By:


Jussi Malinen
(01/Sep/14 4:02 PM)




Status:


Open
InProgress



























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







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

[JIRA] [robot-plugin] (JENKINS-24531) There should be high resolution versions of graphs available

2014-09-01 Thread jussi.ao.mali...@gmail.com (JIRA)
















































Jussi Malinen
 resolved  JENKINS-24531 as Fixed


There should be high resolution versions of graphs available
















Implemented.





Change By:


Jussi Malinen
(01/Sep/14 4:03 PM)




Status:


InProgress
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/d/optout.

[JIRA] [p4] (JENKINS-24512) Add option to lock the created workspace to a host















































Paul Allen
 commented on  JENKINS-24512


Add option to lock the created workspace to a host















I can set the host using InetAddress.getLocalHost().getHostName(); however should I set the workspace before every build? Or just at creation?
The issue is at creation you don't necessarily know which Slaves the workspace will run on?




























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







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

[JIRA] [robot-plugin] (JENKINS-22406) Show tags for test cases

2014-09-01 Thread jussi.ao.mali...@gmail.com (JIRA)
















































Jussi Malinen
 resolved  JENKINS-22406 as Fixed


Show tags for test cases
















Change By:


Jussi Malinen
(01/Sep/14 4:32 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/d/optout.

[JIRA] [robot-plugin] (JENKINS-21644) Aggregated results in a multimodule maven project displays only values of the last submodule

2014-09-01 Thread jussi.ao.mali...@gmail.com (JIRA)
















































Jussi Malinen
 resolved  JENKINS-21644 as Fixed


Aggregated results in a multimodule maven project displays only values of the last submodule
















Change By:


Jussi Malinen
(01/Sep/14 4:43 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/d/optout.

[JIRA] [p4] (JENKINS-24493) P4 Plugin cannot sync symlinks

2014-09-01 Thread tsack...@adobe.com (JIRA)















































Tom Sackett
 commented on  JENKINS-24493


P4 Plugin cannot sync symlinks















Ah. That makes sense. I had installed jre 7u67, but from the command-line (and Jenkins) I still get version 1.6. I had noticed the 1.6 number of the java-runtime.version above, but had assumed it must be part of another confusing version numbering scheme similar to what Sun did with Solaris.

My Macs seem perfectly happy to run 1.7 in the browser, but can't find it on the command line. I'll keep trying.



























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







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

[JIRA] [jenkinswalldisplay] (JENKINS-24522) additional-identities-plugin Configurer Link not getting displayed in Jenkins dashboad GUI
















































Daniel Beck
 resolved  JENKINS-24522 as Not A Defect


additional-identities-plugin Configurer Link not getting displayed in Jenkins dashboad GUI
















This is a bug tracker, not a support website.

For requests for assistance, please ask on jenkinsci-users mailing list, or in #jenkins on Freenode.





Change By:


Daniel Beck
(01/Sep/14 6:00 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























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







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

[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression

2014-09-01 Thread domi.br...@free.fr (JIRA)















































Dominique Brice
 updated  JENKINS-2


Label display wrong when using operators in _expression_
















screenshot of new plugin





Change By:


Dominique Brice
(01/Sep/14 6:02 PM)




Attachment:


LJPa_jdk7.png





Attachment:


LJPa_macos.png





Attachment:


LJPa_unassigned.png



























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







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

[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression

2014-09-01 Thread domi.br...@free.fr (JIRA)

Dominique Brice
commented on JENKINS-2

Label display wrong when using operators in _expression_

I have a functional version of a new plugin that covers this requirement. See attached screenshot.
A couple of remarks:

labels assigned to jobs are not normalized by Jenkins: if the user enters “jdk7master” in one job and “masterjdk7” in another one, they will be seen as two different labels. The plugin follows this behavior, and puts these jobs in two distinct categories
the new page lists all jobs that reference the specific label, regardless of the meaning of the full label. So “windows!msbuild” jobs will be shown on the page for label “msbuild”. As a user I think it makes sense functionally, and the reason why a job is shown on the page is clearly stated (“Job(s) configured with label_something”)
while I was testing that I noticed that it’s possible to assign labels to a node starting with !. This leads to unexpected behavior. Not sure if it’s worth reporting it (maybe it’s already reported?)
for the display of each group of jobs I used the standard projects’ list view

Feedback and comments are welcome.

[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression

Daniel Beck
commented on JENKINS-2

Label display wrong when using operators in _expression_

Looks great!

Makes sense. Jenkins doesn't consider them equal either despite Label implementing Comparable.

the new page lists all jobs that reference the specific label, regardless of the meaning of the full label. So “windows!msbuild” jobs will be shown on the page for label “msbuild”. As a user I think it makes sense functionally, and the reason why a job is shown on the page is clearly stated (“Job(s) configured with label_something”)

Makes sense. Since it groups by label, it's clear that labels may be inverted (only those "NOT something"), or even useless (label||!label and similar, less obvious rules).

while I was testing that I noticed that it’s possible to assign labels to a node starting with !. This leads to unexpected behavior. Not sure if it’s worth reporting it (maybe it’s already reported?)

Not sure what you mean. If the node is called 'foo' and you specify '!foo' as label, it'll run on any other node (!windows could be a shortcut for e.g. osx||linux||solaris in a particular setup). If OTOH the node is called '!foo' because the naming conventions don't take label expressions into account (didn't check whether that's possible though), reporting that would be useful. Seems related to similar reports of brokenness related to labels.

for the display of each group of jobs I used the standard projects’ list view

Personally I find these list view lists very noisy and would prefer a minimal view similar to what is shown on the label index page for exact matches, but I recognize that's subjective and your use case may even require it to look like that.

[JIRA] [p4] (JENKINS-24512) Add option to lock the created workspace to a host

2014-09-01 Thread dant...@gmail.com (JIRA)















































dan tran
 commented on  JENKINS-24512


Add option to lock the created workspace to a host















I am clueless on Jenkins development so I cant recommend which method to use. However the following is my use case

1. Able to run mvn -B release:prepare release:perform on both master and slave. Very likely on slave. I build snapshot at Jenkins slave and use jenkins maven release plugin to run cut the release using the same workspace

2. release:prepare at master and then fan out/in to all slaves to the rest ( ie viewable using jenkins build pipeline plugin).  This is our java+native mulitplatform build

for both cases, I am using manual view workspace

So it is important for me have current workspace with a known hostname for fast client workspace discovery

Perhaps we can do some experiment to add this as an option?  

Thank you for looking into this




























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







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

[JIRA] [p4] (JENKINS-23890) Error on Maven build with SCM changes

2014-09-01 Thread dant...@gmail.com (JIRA)















































dan tran
 commented on  JENKINS-23890


Error on Maven build with SCM changes 















I always use latest jenkins



























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







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

[JIRA] [core] (JENKINS-16451) Workspace cleanup chmods the top-level directory to complete crap















































Daniel Beck
 commented on  JENKINS-16451


Workspace cleanup chmods the top-level directory to complete crap















Another option would be that SCM's processWorkspaceBeforeDeletion(...) breaks things. What SCMs (Subversion, Git, Mercurial, ...) are used on the affected jobs? Does it also affect jobs that don't use any SCM?

What workspace listeners are in use when this occurs? Run WorkspaceListener.all() in Manage Jenkins » Script Console and report the output.

Re Workspace Cleanup plugin, maybe this should be changed to report failure to delete in one of the tries at least to the system log:
https://github.com/jenkinsci/ws-cleanup-plugin/blob/267f3/src/main/java/hudson/plugins/ws_cleanup/PreBuildCleanup.java#L103



























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







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

[JIRA] [core] (JENKINS-16962) Linux slave on different timezone - immediate ping timeout exception
















































Daniel Beck
 resolved  JENKINS-16962 as Cannot Reproduce


Linux slave on different timezone - immediate ping timeout exception
















Resolving as Cannot Reproduce after a few weeks without response to a comment asking for updated information by the reporter.

Please file a new issue if this still occurs in recent (no older than 8 weeks) Jenkins versions.





Change By:


Daniel Beck
(01/Sep/14 6:54 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/d/optout.

[JIRA] [mstestrunner] (JENKINS-24528) Test Category Field does not accept environnement variables















































Daniel Beck
 updated  JENKINS-24528


Test Category Field does not accept environnement variables
















I'm not sure about this specific plugin, but in Jenkins configuration variables are usually referenced as $NAME or ${NAME}, like in shell scripts. Try that.





Change By:


Daniel Beck
(01/Sep/14 7:08 PM)




Issue Type:


Bug
NewFeature



























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







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

[JIRA] [build-blocker] (JENKINS-20255) jenkins master crashes on deletetion of a node, both from command line and UI

2014-09-01 Thread o.v.nenas...@gmail.com (JIRA)
















































Oleg Nenashev
 resolved  JENKINS-20255 as Cannot Reproduce


jenkins master crashes on deletetion of a node, both from command line and UI
















Agreed.
The issue should be reproduced on LTS and/or latest versions





Change By:


Oleg Nenashev
(01/Sep/14 7:09 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/d/optout.

[JIRA] [core] (JENKINS-12219) Missing builds after restart due to error loading FileParameters















































Daniel Beck
 commented on  JENKINS-12219


Missing builds after restart due to error loading FileParameters















Is this still the path referenced in recent versions of Jenkins when using Tomcat?



























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







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

[JIRA] [core] (JENKINS-11543) UTF-8 encoding issue of build parameters as soon as including File parameter

2014-09-01 Thread krizleeb...@java.net (JIRA)















































krizleebear
 commented on  JENKINS-11543


UTF-8 encoding issue of build parameters as soon as including File parameter 















Well - thanks a lot, I'm really thrilled about your fast response and take of direct action! 
I'm a fan of hard-to-guess issues. I even browsed github and had a swift look at two classes (FileParameterDefinition and FileParameterValue) in Jenkins source code on my own... but as complete stranger to the code I didn't realize where the error had its origin.



























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







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

[JIRA] [core] (JENKINS-19786) Configuration page is stuck at loading
















































Daniel Beck
 resolved  JENKINS-19786 as Duplicate


Configuration page is stuck at loading
















Appears to be a duplicate caused by SSH publisher, so closing as such.

Similar issues should be filed independently as these are likely caused by different plugins. Your browser's error console may help determine the culprit.





Change By:


Daniel Beck
(01/Sep/14 7:54 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/d/optout.

[JIRA] [metrics] (JENKINS-23933) Expose build successful/unstable/failed metrics

2014-09-01 Thread mfriedenha...@gmail.com (JIRA)















































Mirko Friedenhagen
 commented on  JENKINS-23933


Expose build successful/unstable/failed metrics















Any feedback?



























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







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

[JIRA] [core] (JENKINS-21306) Whith option Execute concurrent builds if necessary not enabled @X is added to workspace name
















































Daniel Beck
 resolved  JENKINS-21306 as Incomplete


Whith option Execute concurrent builds if necessary not enabled @X is added to workspace name
















Too little information provided to investigate further. Please file a new issue if this happens again on a recent release (no older than eight weeks or so). A related issue was resolved in JENKINS-21622.

Include the output of the following script run in Manage Jenkins » Script Console, and include which node this happens on:


( [] + Jenkins.instance + Jenkins.instance.nodes ).each {
  println it.displayName
  println it.toComputer()?.workspaceList?.inUse
}






Change By:


Daniel Beck
(01/Sep/14 8:04 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























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







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

[JIRA] [core] (JENKINS-21384) 100% CPU on NioSocketAcceptor















































Daniel Beck
 commented on  JENKINS-21384


100% CPU on NioSocketAcceptor















Does this issue still occur? Did you update Jenkins since reporting this, and if so, what's the current version?



























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







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

[JIRA] [core] (JENKINS-21395) Jenkins does not reuse created workspace but creates a new
















































Daniel Beck
 resolved  JENKINS-21395 as Duplicate


Jenkins does not reuse created workspace but creates a new
















Seems to duplicate JENKINS-21622. If this occurs on recent Jenkins versions (no older than eight weeks), please fine a new issue and provide the information requested here:

https://issues.jenkins-ci.org/browse/JENKINS-21306?focusedCommentId=209499page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-209499





Change By:


Daniel Beck
(01/Sep/14 8:07 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/d/optout.

[JIRA] [core] (JENKINS-19145) Builds fail because of slave went offline during the build















































Daniel Beck
 commented on  JENKINS-19145


Builds fail because of slave went offline during the build















These look like different problems, as the original report shows the slave to be named 'null'. Probably because there's no hudson.model.Computer for the hudson.model.Node, but needs further investigation.

Do these issues still occur on more recent Jenkins versions (no older than eight weeks)?



























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







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

[JIRA] [core] (JENKINS-22072) Multi-configuration parent consumes an executor when build is queued with slave offline
















































Daniel Beck
 resolved  JENKINS-22072 as Duplicate


Multi-configuration parent consumes an executor when build is queued with slave offline
















Analysis in the newer issue, so resolving this one.





Change By:


Daniel Beck
(01/Sep/14 8:11 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/d/optout.

[JIRA] [core] (JENKINS-21913) java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.















































Daniel Beck
 commented on  JENKINS-21913


java.io.StreamCorruptedException: invalid type code: 41 occured at end of build.















Jenkins slaves communicate via stdout with the master. Regular standard output is redirected to not interfere. Slave VM crash messages still write to stdout, as may this output.



























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







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

[JIRA] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart















































Daniel Beck
 commented on  JENKINS-10442


RestartNotSupportedException when trying to do safeRestart















Is anyone still experiencing this issue on recent Jenkins versions? If so, please post a comment mentioning your Jenkins version, JRE vendor and version, OS, and exact error message. If you use Oracle JRE instead of OpenJDK, does that resolve the 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/d/optout.

[JIRA] [core] (JENKINS-13905) install IPS jenkins package failed















































Daniel Beck
 updated  JENKINS-13905


install IPS jenkins package failed
















Change By:


Daniel Beck
(01/Sep/14 8:22 PM)




Labels:


solaris



























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







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

[JIRA] [core] (JENKINS-7976) Aggregate downstream test results does not work for Matrix projects















































Daniel Beck
 commented on  JENKINS-7976


Aggregate downstream test results does not work for Matrix projects















If this still occurs on recent Jenkins versions (no older than eight weeks), please specify your Jenkins version, Matrix Project version, and JUnit plugin version (if Jenkins 1.577+).



























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







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

[JIRA] [core] (JENKINS-11586) Regression introduced with Slave Side ChannelPinger















































Daniel Beck
 commented on  JENKINS-11586


Regression introduced with Slave Side ChannelPinger















Is anyone still experiencing this issue on recent (no older than eight weeks) versions of Jenkins? If so, please specify the Jenkins version and exact behavior you're seeing.



























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







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

[JIRA] [core] (JENKINS-21353) Cannot delete workspace