[JIRA] [core] (JENKINS-25993) Java 9 completely changes JDK directory layout and drops tools.jar

[mar...@headcrashing.eu (JIRA)]

Markus KARG
 created  JENKINS-25993


Java 9 completely changes JDK directory layout and drops tools.jar















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


10/Dec/14 7:50 AM



Description:


Oracle published plans to drop the existence of tools.jar and totally restructure the directory layout of the JDK beginning with JDK 9, including changes in the extensions mechanism and location of rt.jar. As a side effect, all plugins relying on a particular layout structure and / or the existence of tools.jar won't work on JDK 9.

The intention is to move from a histrically grown infrastructure to a layout which is specified by a JSR standard, hence it can be considered consistent on all future JDKs even from different vendors, which is a positive thing, but imposed problems for many tool vendors.

As this is a cross-plugin concern, all plugins have to be checked and possibly fixed.

For more information see http://openjdk.java.net/jeps/220.

A pre-release of JDK 9 can be downloaded from https://jdk9.java.net/download/.

Oracle is interested to get in touch with projects being currently dependend of the existing pre-9 JDK structure. Such projects shall report on the jigsaw-dev mailing list.

Some effects in short:

•	JRE and JDK images now have identical structures. Previously a JDK image embedded the JRE in a jre subdirectory; now a JDK image is simply a run-time image that happens to contain the full set of development tools and other items historically found in the JDK.

•	User-editable configuration files previously located in the lib directory are now in the new 'conf' directory. The files that remain in the lib directory are private implementation details of the run-time system, and should never be opened or modified.

•	The endorsed-standards override mechanism has been removed. Applications that rely upon this mechanism, either by setting the system property java.endorsed.dirs or by placing jar files into the lib/endorsed directory of a JRE, will not work. We expect to provide similar functionality later in JDK 9 in the form of upgradeable modules.

•	The extension mechanism has been removed. Applications that rely upon this mechanism, either by setting the system property java.ext.dirs or by placing jar files into the lib/ext directory of a JRE, will not work. In most cases, jar files that were previously installed as extensions can simply be placed at the front of the class path.

•	The internal files rt.jar, tools.jar, and dt.jar have been removed. The content of these files is now stored in a more efficient format in implementation-private files in the lib directory. Class and resource files previously in tools.jar and dt.jar are now always visible via the bootstrap or application class loaders in a JDK image.

•	A new, built-in NIO file-system provider can be used to access the class and resource files stored in a run-time image. Tools that previously read rt.jar and other internal jar files directly should be updated to use this file system.

(Source: December Oracle Java CAP Program Newsletter)




Environment:


JDK 9




Project:


Jenkins



Labels:


jdk
plugins
general




Priority:


Blocker



Reporter:


Markus KARG

























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

[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection

[cepn...@java.net (JIRA)]

cepnyci
 commented on  JENKINS-23232


SEVERE: I/O error in channel Chunked connection















Daniel, I am sorry but I have no idea what "ASCII nloa" means. I did google, but could not find anything useful. 



























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] [groovy-plugin] (JENKINS-25992) Groovy script lucks permissions on slave

[dmitrijs.sahl...@accenture.com (JIRA)]

Dmitrijs Sahlovs
 created  JENKINS-25992


Groovy script lucks permissions on slave















Issue Type:


Bug



Assignee:


vjuranek



Components:


groovy-plugin



Created:


10/Dec/14 7:33 AM



Description:


I have a windows slave. On that slave I have a build, which got "Execute system Groovy script" as a buildstep. I am running a simple script there:
def myFile = new File("C:/abc/abc.cmd")
def fileText = myFile.text
fileText = (fileText =~ /aa/).replaceFirst("bb")
myFile.write(fileText)
and I receive:
FATAL: C:/abc/abc.cmd (The system cannot find the path specified)

However, I am able to execute this script from node script console it runs just fine, so I suppose for some reason script is lucking permissions, when is executed as a build step.




Environment:


Jenkins-v1.576 on Windows

Groovy plugin-v1.19

Windows Slaves Plugin-v1.0




Project:


Jenkins



Priority:


Major



Reporter:


Dmitrijs Sahlovs

























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-25991) Tree-like build log

[jiefei.c...@gmail.com (JIRA)]

Jiefei Chen
 created  JENKINS-25991


Tree-like build log















Issue Type:


New Feature



Assignee:


Unassigned


Components:


core



Created:


10/Dec/14 6:13 AM



Description:


In our project, we have tons of messages in each build step. The messages are put to log file in plain text. It is better to display the messages in a tree-view. Then, it is easy to tell exactly, which build step is failed.




Project:


Jenkins



Labels:


jenkins




Priority:


Minor



Reporter:


Jiefei Chen

























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-25990) Discard Old Builds doesn't work on Matrix Job

[pandu_...@yahoo.com (JIRA)]

Pandu Aji
 created  JENKINS-25990


Discard Old Builds doesn't work on Matrix Job















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


10/Dec/14 2:02 AM



Description:


Checked "Discard Old Builds"
Set "Days to keep builds" to 5

Builds in the directories below aren't getting cleanup:

	/var/lib/jenkins/jobs//builds
	/var/lib/jenkins/jobs//configurations//*/builds



The same settings work on non-Matrix job.
It causes jenkins server to run out of disk pretty quickly.




Environment:


Jenkins : 1.593

Matrix Project Plugin : 1.4




Project:


Jenkins



Priority:


Major



Reporter:


Pandu Aji

























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-25990) Discard Old Builds doesn't work on Matrix Job

[pandu_...@yahoo.com (JIRA)]

Pandu Aji
 updated  JENKINS-25990


Discard Old Builds doesn't work on Matrix Job
















Change By:


Pandu Aji
(10/Dec/14 2:03 AM)




Description:


Checked "Discard Old Builds"Set "Days to keep builds" to 5Builds in the directories below aren't getting cleanup:- /var/lib/jenkins/jobs//builds- /var/lib/jenkins/jobs//configurations//
<
*
>
//
<
*
>
//
<
*
>
/buildsThe same settings work on non-Matrix job.It causes jenkins server to run out of disk pretty quickly.



























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-25989) No wrap up(not in multiple lines) of too long list of slaves at label page

[hits...@gmail.com (JIRA)]

hiteswar kumar
 created  JENKINS-25989


No wrap up(not in multiple lines) of too long list of slaves at label page















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


10/Dec/14 2:00 AM



Description:


[BACKGROUND]
At earlier LTS core 1.532.2, too long list of slaves automatically wrap up in multiple line and related project in one page only and no need to scroll right side to see all slaves and related projects.

[ISSUE]
at jenkins core LTS 1.554.2, too long list of slaves NOT wrap up in multipl lines  and related projects needs to scroll right side to see all slaves and related projects.

at jenkins core LTS 1.580.1, too long list of slaves NOT wrap in multiple lines.
but related projects are fit into one view. no need to scroll right side to view related projects.
But need to scroll right side to see all slaves. but ideally 




Environment:


Jenkins core 1.554.2 LTS, 1.580.1 LTS




Project:


Jenkins



Priority:


Major



Reporter:


hiteswar kumar

























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] [selenium-plugin] (JENKINS-25583) Unexpected error in launching a slave. This is probably a bug in Jenkins.

[tkurd...@gmail.com (JIRA)]

Taras Kurdyna
 commented on  JENKINS-25583


Unexpected error in launching a slave. This is probably a bug in Jenkins.















Any idea, when can this be 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] [selenium-plugin] (JENKINS-25987) Selenium Grid fails to start Selenium Server on slaves

[tkurd...@gmail.com (JIRA)]

Taras Kurdyna
 closed  JENKINS-25987 as Duplicate


Selenium Grid fails to start Selenium Server on slaves
















It is dup.





Change By:


Taras Kurdyna
(10/Dec/14 1:37 AM)




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

[JIRA] [core] (JENKINS-25988) Major performance issues on pages with large build queues (100+ items)

[r...@vmware.com (JIRA)]

Ryan Hsu
 created  JENKINS-25988


Major performance issues on pages with large build queues (100+ items)















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


10/Dec/14 1:36 AM



Description:


On job pages (http://.com/job/) that have large build queues, the page loads and handles extremely slow. I have observed this on a machine with 16GB RAM and pretty hefty CPU and reproduced in all major browsers. On Chrome, the task manager shows a consistent > 100% CPU usage on the tab that has the page open.

I have verified that the issue has nothing to do with loading assets from the server. A quick profile [1] of the code execution showed that lots of time is spent in functions "getclientWidth" and "getClientHeight". Looks like these are getting called from "getElementOverflowParams()" in hudson-behavior.js. I believe this is a problem resulting from commit cb9036 [2] from 15 days ago, "Single/Multiline Build History", wherein this code is introduced.

The problem seems to be that there are way too many event handlers listening to window resize events. This is causing the page to essentially hang and be unusable. 


[1] http://i.imgur.com/Rr29SnU.png
[2] https://github.com/jenkinsci/jenkins/commit/cb9036c45527223525cc1b48020a8ed777020c1a




Project:


Jenkins



Labels:


performance




Priority:


Major



Reporter:


Ryan Hsu

























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] [selenium-plugin] (JENKINS-25658) Selenium Node (Jenkins slave) doesn't start

[lavoie.rich...@gmail.com (JIRA)]

Richard Lavoie
 resolved  JENKINS-25658 as Fixed


Selenium Node (Jenkins slave) doesn't start
















duplicate of JENKINS-25583





Change By:


Richard Lavoie
(10/Dec/14 1:31 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/d/optout.

[JIRA] [selenium-plugin] (JENKINS-18806) Selenium grid plugin have the error "Subversion checkout has been canceled" on the slave

[lavoie.rich...@gmail.com (JIRA)]

Richard Lavoie
 commented on  JENKINS-18806


Selenium grid plugin have the error "Subversion checkout has been canceled" on the slave















Just how is this related to the selenium 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] [selenium-plugin] (JENKINS-25987) Selenium Grid fails to start Selenium Server on slaves

[lavoie.rich...@gmail.com (JIRA)]

Richard Lavoie
 resolved  JENKINS-25987 as Duplicate


Selenium Grid fails to start Selenium Server on slaves
















Duplicate of JENKINS-25583





Change By:


Richard Lavoie
(10/Dec/14 1:30 AM)




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] [ec2-plugin] (JENKINS-25963) Jobs tied to EC2 plugin-provisioned slaves via NodeLabel parameter don't provision new slaves

[aba...@java.net (JIRA)]

abayer
 assigned  JENKINS-25963 to Dominik Bartholdi



Jobs tied to EC2 plugin-provisioned slaves via NodeLabel parameter don't provision new slaves
















Change By:


abayer
(10/Dec/14 1:19 AM)




Assignee:


Francis Upton
Dominik Bartholdi



























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] [ec2-plugin] (JENKINS-25963) Jobs tied to EC2 plugin-provisioned slaves via NodeLabel parameter don't provision new slaves

[aba...@java.net (JIRA)]

abayer
 commented on  JENKINS-25963


Jobs tied to EC2 plugin-provisioned slaves via NodeLabel parameter don't provision new slaves















This is the case with anything using NodeProvisioner - i.e., any cloud slave plugin. This is because NodeLabel doesn't actually tell the queue anything about what it needs, exactly - if it had a LabelAssignmentAction, that'd work.



























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] [selenium-plugin] (JENKINS-25987) Selenium Grid fails to start Selenium Server on slaves

[tkurd...@gmail.com (JIRA)]

Taras Kurdyna
 created  JENKINS-25987


Selenium Grid fails to start Selenium Server on slaves















Issue Type:


Bug



Assignee:


Richard Lavoie



Components:


selenium-plugin



Created:


10/Dec/14 1:17 AM



Description:


I am having troubles getting Selenium Grid to start Selenium Server on slaves. When I try manually starting Selenium server on the slaves it works great.

I am getting this error all the time:

[12/09/14 17:15:48] [SSH] Starting slave process: cd "C:\cygwin64\home\$USER\selenium-server" && java  -jar slave.jar
<===[JENKINS REMOTING CAPACITY]===>channel started
Slave.jar version: 2.48
This is a Windows slave
Starting Selenium nodes on Thor IE11 - Win8.1
$ "C:\Program Files\Java\jre1.8.0_25\bin\java" -Dwebdriver.ie.driver=C:\cygwin64\home\$USER\selenium-server\IEDriverServer.exe -cp C:\cygwin64\home\$USER\selenium-server\slave.jar hudson.remoting.Launcher -cp C:\cygwin64\home\$USER\selenium-server\selenium-server-standalone-2.41.0.jar -connectTo localhost:57416
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.
java.lang.NullPointerException
	at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:98)
	at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:24)
	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2677)
	at hudson.remoting.UserRequest.perform(UserRequest.java:121)
	at hudson.remoting.UserRequest.perform(UserRequest.java:49)
	at hudson.remoting.Request$2.run(Request.java:324)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
	at ..remote call to Thor IE11 - Win8.1(Native Method)
	at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)
	at hudson.remoting.UserResponse.retrieve(UserRequest.java:221)
	at hudson.remoting.Channel.call(Channel.java:752)
	at hudson.FilePath.act(FilePath.java:970)
	at hudson.FilePath.act(FilePath.java:959)
	at hudson.plugins.selenium.process.SeleniumJarRunner.start(SeleniumJarRunner.java:46)
	at hudson.plugins.selenium.configuration.global.SeleniumGlobalConfiguration.start(SeleniumGlobalConfiguration.java:55)
	at hudson.plugins.selenium.PluginImpl.startSeleniumNode(PluginImpl.java:444)
	at hudson.plugins.selenium.ComputerListenerImpl.onOnline(ComputerListenerImpl.java:26)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:531)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:366)
	at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:945)
	at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:133)
	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:711)
	at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	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:745)
[12/09/14 17:15:59] Launch failed - cleaning up connection
[12/09/14 17:15:59] [SSH] Connection closed.
ERROR: Connection terminated
java.io.IOException: Unexpected termination of the channel
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
	at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325)
	at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794)
	at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801)
	at java.io.ObjectInputStream.(ObjectInputStream.java:299)
	at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40)
	at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
	at hudson.remoting.SynchronousComman

[JIRA] [cloudformation-plugin] (JENKINS-25752) List of regions should be updates because of a new AWS region. ( eu-center-1 Frankfurt)

[j...@zindello.com.au (JIRA)]

Josh Mesilane
 commented on  JENKINS-25752


List of regions should be updates because of a new AWS region. ( eu-center-1 Frankfurt)















No worries. I've created a pull request with the added line to the Array.



























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] [cloudformation-plugin] (JENKINS-25752) List of regions should be updates because of a new AWS region. ( eu-center-1 Frankfurt)

[ocs...@gmail.com (JIRA)]

Adam Ocsvari
 commented on  JENKINS-25752


List of regions should be updates because of a new AWS region. ( eu-center-1 Frankfurt)















Extending the code with Frankfurt is just extending the array.

At the same time it would be nice to get the regions dynamically from an AWS API call. This solution needs careful planning tough.



























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] [parameterized-trigger-plugin] (JENKINS-25986) Cannot save jenkins job after updating it

[jllo...@us.ibm.com (JIRA)]

jose lopez
 created  JENKINS-25986


Cannot save jenkins job after updating it















Issue Type:


Bug



Assignee:


huybrechts



Components:


parameterized-trigger-plugin



Created:


10/Dec/14 12:27 AM



Description:


I can't save my newly created jenkins job (freestyle of copy from existing item)

Scenario I: Creating job by copying from existing job and execute a shell script.

1) Create a new item and select "Copy existing item"
2) Fill in the blanks and click OK
3) Go to Build section
2) Select "Execute Shell Script"
3) Add the following code to be executed on the shell:

function jsonval {
  temp=`echo $json | sed 's/\//\//g' | sed 's/[{}]//g' | awk -v k="text" '{n=split($0,a,","); for (i=1; i<=n; i++) print a[i]}' | sed 's/\"\:\"/|/g' | sed 's/[\,]/ /g' | grep -w $prop`
  echo ${temp##*|}
}
4) Click Apply

After adding that code and hitting Apply nothing happens. Then, if I click Save nothing happens and I get the following information displayed in my page:

The connection was reset

The connection to the server was reset while the page was loading.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

Scenario II: Create a freestyle project and enable parametrized build

1) Create a new item and select freestyle
2) Check "This build is parameterized"
3) Add a new parameter
4) Click Apply 
5) Add a new parameter
6) Click Apply
7) Click Save

At 4) I can see a green bar at the top of my page with the legend SAVED. Good that is what I am expecting. Sadly on 6) I don't see anything. Nothing happens. On 7) I don't see anything happening and I see the following information displayed in my page:

The connection was reset

The connection to the server was reset while the page was loading.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.







Environment:


Jenkins:

Jenkins ver. 1.59.3



OS:

Linux plague 2.6.32.12-0.7-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux



Browser

Chrome Version 39.0.2171.71

Firefox 31.3.0 ESR

Internet Explorer 8



Java

JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr8ifx-20100609_59383 (JIT enabled, AOT enabled)>J9VM - 20100609_059383>JIT  - r9_20100401_15339ifx2>GC   - 20100308_AA








Project:


Jenkins



Labels:


plugin
jenkins




Priority:


Critical



Reporter:


jose lopez

























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] [github-plugin] (JENKINS-23995) Adding commit status context in github-plugin

[crazy...@gmail.com (JIRA)]

  
Nelson Chen
 edited a comment on  JENKINS-23995


Adding commit status context in github-plugin
















GitHub just released the UI yesterday. The commit status contexts are now shown in the web interface. However, it looks like there's nothing in the Jenkins ecosystem that supports this at the moment.

https://github.com/blog/1935-see-results-from-all-pull-request-status-checks



























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] [github-plugin] (JENKINS-23995) Adding commit status context in github-plugin

[crazy...@gmail.com (JIRA)]

Nelson Chen
 commented on  JENKINS-23995


Adding commit status context in github-plugin















GitHub just released the UI yesterday. The commit status contexts are now shown in the web interface.

https://github.com/blog/1935-see-results-from-all-pull-request-status-checks



























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] [cloudformation-plugin] (JENKINS-11833) Add a Post-build action to create AMI

[j...@zindello.com.au (JIRA)]

  
Josh Mesilane
 edited a comment on  JENKINS-11833


Add a Post-build action to create AMI
















You can already do this using an "Execute Shell" script. You need to use the Cloudformation outputs to spit out the InstanceID and the Region. I'm doing this using the following



export AWS_ACCESS_KEY_ID=xxx
export AWS_SECRET_ACCESS_KEY=xxx
aws ec2 create-image --instance-id $amibuilder_InstanceID --name some_ami_`date +%y%m%d-%H%M` --description "Some AMI Image `date +%y%m%d-%H%M`" --region $amibuilder_AWSRegion --debug






























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] [cloudformation-plugin] (JENKINS-11833) Add a Post-build action to create AMI

[j...@zindello.com.au (JIRA)]

Josh Mesilane
 commented on  JENKINS-11833


Add a Post-build action to create AMI















You can already do this using an "Execute Shell" script. You need to use the Cloudformation outputs to spit out the InstanceID and the Region. I'm doing this using the following

export AWS_ACCESS_KEY_ID=xxx
export AWS_SECRET_ACCESS_KEY=xxx
aws ec2 create-image -instance-id $amibuilder_InstanceID --name some_ami_`date +%y%m%d%H%M` -description "Some AMI Image `date +%y%m%d%H%M`" --region $amibuilder_AWSRegion --debug



























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] [cloudformation-plugin] (JENKINS-25752) List of regions should be updates because of a new AWS region. ( eu-center-1 Frankfurt)

[j...@zindello.com.au (JIRA)]

Josh Mesilane
 commented on  JENKINS-25752


List of regions should be updates because of a new AWS region. ( eu-center-1 Frankfurt)















I'd too like to see this updated. If you're happy I could look at the codebase and see what's involved in adding this if you've not got the 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/d/optout.

[JIRA] [artifactory-plugin] (JENKINS-25985) maven-artifcatory deployment doesn't work

[jenk...@richardlee.name (JIRA)]

Richard Lee
 created  JENKINS-25985


maven-artifcatory deployment doesn't work















Issue Type:


Bug



Assignee:


yossis



Components:


artifactory-plugin



Created:


09/Dec/14 11:36 PM



Description:


I have my maven-artifactory project set up to deploy to artifactory, but after the build completes, it doesn't actually do anything.  It puts an artifactory link in the build status page, but clicking on that shows that nothing was actually uploaded.  I've tested the connection in the global settings, and the jenkins machine can talk to artifactory.  There's nothing in the build log that makes be believe it is actually trying to upload artifacts after a successful build.  Seems that this plugin is missing some configuration diagnostics.




Project:


Jenkins



Priority:


Major



Reporter:


Richard Lee

























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-plugin] (JENKINS-25340) lost trend history after skipping build

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 commented on  JENKINS-25340


lost trend history after skipping build















1. Not definite, but I hope soon. 2. No, matching changes would also be needed in the JUnit plugin. Anyway this is just one possible avenue to 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] [subversion-plugin] (JENKINS-23573) Set an umask

[lyle2.0+jenk...@gmail.com (JIRA)]

Lyle Hanson
 commented on  JENKINS-23573


Set an umask















I've run into the same problem with the local Maven repository; files created by the Jenkins process don't have group write permissions, which is problematic because other users on the machine need to share the same repo.



























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] [weblogic-deployer-plugin] (JENKINS-21244) Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer

[r...@orange.fr (JIRA)]

Raphael CHAUMIER
 updated  JENKINS-21244


Un-escaped $ in module file name passed in command line to weblogic.jar results in the input file not found deployer
















Change By:


Raphael CHAUMIER
(09/Dec/14 10:22 PM)




Labels:


weblogic-deployer-plugin-2.10



























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







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

[JIRA] [subversion-plugin] (JENKINS-25984) Jenkins subversion plugin does not handle git-flow style branch names

[justin.gor...@gmail.com (JIRA)]

Justin Gordon
 created  JENKINS-25984


Jenkins subversion plugin does not handle git-flow style branch names















Issue Type:


Bug



Assignee:


Unassigned


Components:


subversion-plugin



Created:


09/Dec/14 10:33 PM



Description:


I think many people use the SVN plugin, but that one does not handle git-flow style branch names.

Like

feature/some-great-feature





Project:


Jenkins



Priority:


Minor



Reporter:


Justin Gordon

























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-parameter-plugin] (JENKINS-20958) Allow to choose from branches and not only shas and tags

[justin.gor...@gmail.com (JIRA)]

Justin Gordon
 commented on  JENKINS-20958


Allow to choose from branches and not only shas and tags















+1 for this item. I think many people use the SVN plugin, but that one does not handle git-flow style branch names.



























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-plugin] (JENKINS-7711) Git branch names don't handle / right

[justin.gor...@gmail.com (JIRA)]

Justin Gordon
 commented on  JENKINS-7711


Git branch names don't handle / right















I seeing this issue with the svn plugin which allows picking git branches



























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] [weblogic-deployer-plugin] (JENKINS-19862) NPE when copying job with deployer plugin

[r...@orange.fr (JIRA)]

Raphael CHAUMIER
 commented on  JENKINS-19862


NPE when copying job with deployer plugin















Stack trace : 
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.

C:\Users\MRC>cd C:\Documents\Raphael\workspace\weblogic-deployer-plugin

C:\Documents\Raphael\workspace\weblogic-deployer-plugin>mvn hpi:run -Pjenkins
[INFO] Scanning for projects...
Downloading: http://repo.jenkins-ci.org/public/org/kohsuke/access-modifier-check
er/maven-metadata.xml
Downloaded: http://repo.jenkins-ci.org/public/org/kohsuke/access-modifier-checke
r/maven-metadata.xml (418 B at 0.4 KB/sec)
[INFO]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethrea
ded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] 
[INFO] Building Deploy WebLogic Plugin 2.11-SNAPSHOT
[INFO] 
[INFO]
[INFO] >>> maven-hpi-plugin:1.95:run (default-cli) @ weblogic-deployer-plugin >>
>
Downloading: https://oss.sonatype.org/service/local/staging/deploy/maven2/org/ko
hsuke/stapler/stapler/maven-metadata.xml
Downloading: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/maven
-metadata.xml
Downloading: http://uk.maven.org/maven2/org/kohsuke/stapler/stapler/maven-metada
ta.xml
Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/kohsuke
/stapler/stapler/maven-metadata.xml
Downloaded: http://uk.maven.org/maven2/org/kohsuke/stapler/stapler/maven-metadat
a.xml (1015 B at 4.5 KB/sec)
Downloaded: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/maven-
metadata.xml (7 KB at 15.6 KB/sec)
[WARNING] Could not transfer metadata org.kohsuke.stapler:stapler/maven-metadata
.xml from/to sonatype-nexus-staging (https://oss.sonatype.org/service/local/stag
ing/deploy/maven2/): Failed to transfer file: https://oss.sonatype.org/service/l
ocal/staging/deploy/maven2/org/kohsuke/stapler/stapler/maven-metadata.xml. Retur
n code is: 400 , ReasonPhrase:Bad Request.
Downloading: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/1.208
-SNAPSHOT/maven-metadata.xml
Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/kohsuke
/stapler/stapler/1.208-SNAPSHOT/maven-metadata.xml
Downloaded: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/1.208-
SNAPSHOT/maven-metadata.xml (2 KB at 3.9 KB/sec)
Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/kohsuke
/stapler/stapler-parent/1.208-SNAPSHOT/maven-metadata.xml
Downloading: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler-paren
t/1.208-SNAPSHOT/maven-metadata.xml
Downloaded: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler-parent
/1.208-SNAPSHOT/maven-metadata.xml (598 B at 2.0 KB/sec)
Downloading: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/1.232
-SNAPSHOT/maven-metadata.xml
Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/kohsuke
/stapler/stapler/1.232-SNAPSHOT/maven-metadata.xml
Downloaded: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/1.232-
SNAPSHOT/maven-metadata.xml (3 KB at 7.9 KB/sec)
Downloading: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler-paren
t/1.232-SNAPSHOT/maven-metadata.xml
Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/kohsuke
/stapler/stapler-parent/1.232-SNAPSHOT/maven-metadata.xml
Downloaded: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler-parent
/1.232-SNAPSHOT/maven-metadata.xml (775 B at 2.4 KB/sec)
[INFO]
[INFO] — maven-hpi-plugin:1.95:validate (default-validate) @ weblogic-deployer
-plugin —
[INFO]
[INFO] — maven-enforcer-plugin:1.0.1:enforce (enforce-maven) @ weblogic-deploy
er-plugin —
[INFO]
[INFO] — maven-enforcer-plugin:1.0.1:display-info (display-info) @ weblogic-de
ployer-plugin —
[INFO] Maven Version: 3.2.1
[INFO] JDK Version: 1.6.0_43 normalized as: 1.6.0-43
[INFO] OS Info: Arch: amd64 Family: windows Name: windows 7 Version: 6.1
[INFO]
[INFO] — maven-localizer-plugin:1.14:generate (default) @ weblogic-deployer-pl
ugin —
[INFO]
[INFO] — maven-resources-plugin:2.5:resources (default-resources) @ weblogic-d
eployer-plugin —
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 71 resources
[INFO]
[INFO] — maven-compiler-plugin:2.5:compile (default-compile) @ weblogic-deploy
er-plugin —
[INFO] Nothing to com

[JIRA] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with

[dogf...@java.net (JIRA)]

dogfood
 commented on  JENKINS-25788


WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with















Integrated in  jenkins_main_trunk #3861
 [FIXED JENKINS-25788] RunMap.remove was always returning false, even when the Run was in fact removed. (Revision ce94579c50621990517c86120236ee9a1d0490da)

 Result = SUCCESS
Jesse Glick : ce94579c50621990517c86120236ee9a1d0490da
Files : 

	test/src/test/java/hudson/model/RunMapTest.java
	core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
	changelog.html





























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-plugin] (JENKINS-25340) lost trend history after skipping build

[wink...@dresearch-fe.de (JIRA)]

Peter Winkler
 commented on  JENKINS-25340


lost trend history after skipping build















So I've a last two questions:
1. Is there any timeline where it is planned to start with JENKINS-24380?
2. Is it guaranteed that after JENKINS-24380 is fulfilled trend history comes back to old behavior?



























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-trigger-plugin] (JENKINS-25983) Provide link or variable to dependent triggered job

[rol...@utk.edu (JIRA)]

Roland Schulz
 created  JENKINS-25983


Provide link or variable to dependent triggered job















Issue Type:


Improvement



Assignee:


rsandell



Components:


gerrit-trigger-plugin



Created:


09/Dec/14 9:53 PM



Description:


2.12 added the "Other jobs on which this job depends" feature. The triggering works well. But our dependent job also needs files from the upstream/producer job. Copying those can be done with the copy-artifact plugin. But for it to be able to copy it from the correct job it needs to know the job number of the upstream/producer job. Thus it would be nice if the gerrit-trigger-plugin would provide a variable or permalink which contained the job(id) of the upstream job. Given that there could be multiple upstream jobs this variable could be called GERRIT_UPSTREAM_{upstream-job-name}. If instead of a variable this information is provided by a link, the link would need to contain the change-id, patcheset-revision or refspec so that one could get the job id as a function of either of those informations. I tried to look whether there is already some remote API like this but I could find whether anything like this is already there. Sorry if I missed it.




Project:


Jenkins



Priority:


Major



Reporter:


Roland Schulz

























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-23966) Master labels is disappeared in case system configuration has been changed

[dogf...@java.net (JIRA)]

dogfood
 commented on  JENKINS-23966


Master labels is disappeared in case system configuration has been changed















Integrated in  jenkins_main_trunk #3860
 JENKINS-23966 Master labels disappear when system configuration is updated (Revision 60c2071a301ec6310e6e71b2c98df1b6cade9c90)

 Result = SUCCESS
dominiquebrice : 60c2071a301ec6310e6e71b2c98df1b6cade9c90
Files : 

	core/src/main/resources/jenkins/model/MasterBuildConfiguration/config.groovy
	test/src/test/java/jenkins/model/MasterBuildConfigurationTest.java





























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-25982) JobProperty.getJobActions should be interpreted by Job, not AbstractProject

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 created  JENKINS-25982


JobProperty.getJobActions should be interpreted by Job, not AbstractProject















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


09/Dec/14 9:04 PM



Description:


transientActions should be pulled up from AbstractProject to Job.




Project:


Jenkins



Labels:


api
workflow




Priority:


Minor



Reporter:


Jesse Glick

























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-plugin] (JENKINS-25340) lost trend history after skipping build

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 commented on  JENKINS-25340


lost trend history after skipping build















Release notes for 1.576 mention the fix of JENKINS-23945.

A new configuration option is not desirable; rather better tuning of the standard behavior.



























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] [teamconcert-plugin] (JENKINS-25981) RTC plugin errors with parallel builds

[mst...@java.net (JIRA)]

mstave
 created  JENKINS-25981


RTC plugin errors with parallel builds















Issue Type:


Bug



Assignee:


Unassigned


Components:


teamconcert-plugin



Created:


09/Dec/14 8:47 PM



Description:


If a job runs before the previous run has completed its RTC checkout phase
the previous job reports an error, and the change information for the first job is lost.  Enabling a "quiet time" helps avoid the problem, but that adds a long fixed delay in all cases - not just when the actual checkout phase would overlap. 

Limiting the overlap exposure to just the "accepting changes" portion rather than the entire checkout duration would help some. 

If it would help, I work at IBM and could help reproduce this or test a fix, reach out to mst...@us.ibm.com

RTC : checkout...
12:35:09 RTC Checkout : Source control setup
12:35:10 RTC Checkout : Accepting changes into workspace "myWorkspaceName" ...
12:36:03 RTC Checkout : Fetching files to fetch destination "/tmp/slavePath/workspace/myProjectName" ...
12:37:27 FATAL: RTC : checkout failure: The configuration of the build workspace changed (possibly by a concurrent build) during the load.
12:37:28 com.ibm.team.build.common.TeamBuildException: The configuration of the build workspace changed (possibly by a concurrent build) during the load.
12:37:28 	at com.ibm.team.build.internal.scm.SourceControlUtility.updateFileCopyArea(SourceControlUtility.java:704)
12:37:28 	at com.ibm.team.build.internal.hjplugin.rtc.RepositoryConnection.checkout(RepositoryConnection.java:436)
12:37:28 	at com.ibm.team.build.internal.hjplugin.rtc.RTCFacade.checkout(RTCFacade.java:390)
12:37:28 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
12:37:28 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:94)
12:37:28 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
12:37:28 	at java.lang.reflect.Method.invoke(Method.java:619)
12:37:28 	at com.ibm.team.build.internal.hjplugin.RTCFacadeFactory$RTCFacadeWrapper.invoke(RTCFacadeFactory.java:115)
12:37:28 	at com.ibm.team.build.internal.hjplugin.RTCCheckoutTask.invoke(RTCCheckoutTask.java:166)
12:37:28 	at com.ibm.team.build.internal.hjplugin.RTCCheckoutTask.invoke(RTCCheckoutTask.java:32)
12:37:28 	at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2484)
12:37:28 	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
12:37:28 	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
12:37:28 	at hudson.remoting.Request$2.run(Request.java:328)
12:37:28 	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
12:37:28 	at java.util.concurrent.FutureTask.run(FutureTask.java:273)
12:37:28 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1170)
12:37:28 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:640)
12:37:28 	at java.lang.Thread.run(Thread.java:853)
12:37:28 Caused by: com.ibm.team.repository.common.StaleDataException: The configuration for 'Workspace 'myWorkspaceName':Component 'myComponentA'' is more recent in the repository than the version you have. This usually means that another client has modified it first. Please refresh and try again.
12:37:28 	at com.ibm.team.scm.service.internal.ScmServiceInternal.validateSync(ScmServiceInternal.java:980)
12:37:28 	at com.ibm.team.scm.service.internal.ScmServiceInternal.validateSyncTimes(ScmServiceInternal.java:890)
12:37:28 	at com.ibm.team.scm.service.internal.ScmService$65.run(ScmService.java:2958)
12:37:28 	at com.ibm.team.scm.service.internal.AbstractScmService$5.run(AbstractScmService.java:743)
12:37:28 	at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runTransaction(RepositoryDatabase.java:347)
12:37:28 	at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runInTransaction(RepositoryDatabase.java:271)
12:37:28 	at com.ibm.team.repository.service.internal.PrimitiveTransactionService.runInTransaction(PrimitiveTransactionService.java:96)
12:37:28 	at sun.reflect.GeneratedMethodAccessor172.invoke(null)
12:37:28 	at sun.reflect.DelegatingMethod

[JIRA] [junit-plugin] (JENKINS-9980) Add the "Publish JUnit test result report" option to maven job configuration page

[spencer.cros...@gmail.com (JIRA)]

Spencer Crosswy
 commented on  JENKINS-9980


Add the "Publish JUnit test result report" option to maven job configuration page















Also interested in an update here.

A workaround we've identified is to have a second freestyle build solely for publishing test results, but you lose the benefit of informing downstream builds that upstream tests have failed.



























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-plugin] (JENKINS-25340) lost trend history after skipping build

[wink...@dresearch-fe.de (JIRA)]

Peter Winkler
 commented on  JENKINS-25340


lost trend history after skipping build















The suggestion to use “skipping” would only solve a small part of our problems. A problem which leads to a build failure before the first test case is started disturbs the statistics because the firmware to be tested wasn’t responsible for that. Moreover “skipping” is already used for test cases which meet hardware where they have to skip. We couldn’t differentiate these two things. 

But nevertheless I wonder that a well-established behavior of JENKINS is changed that restrictively kind without unease that the customers could have a problem with that change.
I expected at least two things:

	a configuration item to give the customer the control to switch back to the old behavior
	a warning in the release notes about the new behavior (anyhow this would have spared the analysis time to find out the really reason of the new behavior, may be I’m wrong, but I haven’t seen such a warning)



With respect to the fact that the change in https://github.com/jenkinsci/jenkins/commit/8d8102036f4e52aada39db37c05025b9bb31516d seems more like a work around than a solution of  JENKINS-23945 (may be JENKINS-24380 is one) it is questionable whether a lost of a well-established functionality can be accepted.



























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-25953) Layout - Tabs in job view are layouted in wrong way

[pwielgola...@gmail.com (JIRA)]

Piotr Wielgołaski
 commented on  JENKINS-25953


Layout - Tabs in job view are layouted in wrong way















Fix in pull request https://github.com/jenkinsci/jenkins/pull/1483



























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-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 resolved  JENKINS-25788 as Fixed


WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
















Fixing in ce94579c50621990517c86120236ee9a1d0490da. (JIRA link daemon dead.)





Change By:


Jesse Glick
(09/Dec/14 8:25 PM)




Status:


In Progress
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] [core] (JENKINS-23966) Master labels is disappeared in case system configuration has been changed

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 resolved  JENKINS-23966 as Fixed


Master labels is disappeared in case system configuration has been changed
















Change By:


Jesse Glick
(09/Dec/14 8:20 PM)




Status:


In Progress
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] [core] (JENKINS-25742) Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state

[bitingspar...@gmail.com (JIRA)]

Manav Chimakurthi
 updated  JENKINS-25742


Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state
















Change By:


Manav Chimakurthi
(09/Dec/14 8:20 PM)




Description:


When there are multiple users using Jenkins:One user has clicked on "Yes" confirmation to rename a job.Another user has clicked on "OK" on the "Edit View" screen at the same time.Results in a race condition that
 results in
 leads to
 a deadlock. Immediately after this deadlock occurs, Jenkins "create new job" and other operations are unresponsive. And after some more time Jenkins goes down.{noformat}Name: Handling GET /jenkins/view/ABCDEF/api/json : qtp817406040-243035State: BLOCKED on hudson.model.ListView@57affa54 owned by: Handling POST /jenkins/view/ABCDEF/configSubmit : qtp817406040-42Total blocked: 9  Total waited: 189Stack trace: hudson.model.ListView.getItems(ListView.java:164)hudson.model.ListView.getItems(ListView.java:66)sun.reflect.GeneratedMethodAccessor1929.invoke(Unknown Source)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:483)org.kohsuke.stapler.export.MethodProperty.getValue(MethodProperty.java:66)org.kohsuke.stapler.export.Property.writeTo(Property.java:116)org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190)org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)org.kohsuke.stapler.export.Model.writeTo(Model.java:157)org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267)hudson.model.Api.doJson(Api.java:204)sun.reflect.GeneratedMethodAccessor771.invoke(Unknown Source)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:483)org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210)org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)org.kohsuke.stapler.Stapler.invoke(Stapler.java:636)org.kohsuke.stapler.Stapler.service(Stapler.java:225)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1667)hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:91)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)hudson.security.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:1

[JIRA] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 updated  JENKINS-25788


WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
















Change By:


Jesse Glick
(09/Dec/14 8:18 PM)




Labels:


lazy-loading
 lts-candidate
 regression



























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-25742) Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state

[bitingspar...@gmail.com (JIRA)]

Manav Chimakurthi
 updated  JENKINS-25742


Concurrent "job rename" and "edit view" results in deadlock that puts Jenkins in a non responsive state
















Change By:


Manav Chimakurthi
(09/Dec/14 7:54 PM)




Description:


When there are multiple users using Jenkins:One user has clicked on "Yes" confirmation to rename a job.Another user has clicked on "OK" on the "Edit View" screen at the same time.Results in a race condition that results in a deadlock. Immediately after this deadlock occurs, Jenkins "create new job" and other operations are unresponsive. And after some more time Jenkins goes down.
{noformat}
Name: Handling GET /jenkins/view/ABCDEF/api/json : qtp817406040-243035State: BLOCKED on hudson.model.ListView@57affa54 owned by: Handling POST /jenkins/view/ABCDEF/configSubmit : qtp817406040-42Total blocked: 9  Total waited: 189Stack trace: hudson.model.ListView.getItems(ListView.java:164)hudson.model.ListView.getItems(ListView.java:66)sun.reflect.GeneratedMethodAccessor1929.invoke(Unknown Source)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:483)org.kohsuke.stapler.export.MethodProperty.getValue(MethodProperty.java:66)org.kohsuke.stapler.export.Property.writeTo(Property.java:116)org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190)org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185)org.kohsuke.stapler.export.Model.writeTo(Model.java:157)org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267)hudson.model.Api.doJson(Api.java:204)sun.reflect.GeneratedMethodAccessor771.invoke(Unknown Source)sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke(Method.java:483)org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210)org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733)org.kohsuke.stapler.Stapler.invoke(Stapler.java:863)org.kohsuke.stapler.Stapler.invoke(Stapler.java:636)org.kohsuke.stapler.Stapler.service(Stapler.java:225)javax.servlet.http.HttpServlet.service(HttpServlet.java:790)org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1667)hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:91)org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)hudson.security.BasicAuthenticationFilter.doFilter(BasicAuthenticationFilter.java:114)hudson.

[JIRA] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 updated  JENKINS-25788


WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
















Change By:


Jesse Glick
(09/Dec/14 7:45 PM)




Labels:


free-style
 lazy-loading regression
 warnings



























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-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 updated  JENKINS-25788


WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
















Change By:


Jesse Glick
(09/Dec/14 7:45 PM)




Labels:


free-style
 lazy-loading regression
 warnings



























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-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 started work on  JENKINS-25788


WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
















Change By:


Jesse Glick
(09/Dec/14 7:34 PM)




Status:


Open
In Progress



























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] [job-dsl-plugin] (JENKINS-25922) Add support for Publish Over SSH

[wi...@ceilfors.com (JIRA)]

Wisen Tanasa
 started work on  JENKINS-25922


Add support for Publish Over SSH
















Change By:


Wisen Tanasa
(09/Dec/14 7:26 PM)




Status:


Open
In Progress



























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-15604) checkUrl and codemirror-mode do not mix

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 updated  JENKINS-15604


checkUrl and codemirror-mode do not mix
















Change By:


Jesse Glick
(09/Dec/14 6:39 PM)




Labels:


codemirror _javascript_
 workflow



























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-23148) Accessibility problem when editing shell script in the configuration of a job

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 updated  JENKINS-23148


Accessibility problem when editing shell script in the configuration of a job
















Change By:


Jesse Glick
(09/Dec/14 6:39 PM)




Labels:


accessibility codemirror
 workflow



























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-23151) codemirror-mode on f:textarea broken (was: Execute shell build step text not saved properly)

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 updated  JENKINS-23151


codemirror-mode on f:textarea broken (was: Execute shell build step text not saved properly)
















Change By:


Jesse Glick
(09/Dec/14 6:39 PM)




Labels:


codemirror
 workflow



























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] [integrity-plugin] (JENKINS-25980) How to checkin report summary file on post build using Integrity plugin

[shankar_k_...@usa.com (JIRA)]

Shankar k
 created  JENKINS-25980


How to checkin report summary file on post build using Integrity plugin















Issue Type:


Task



Assignee:


Cletus D'Souza



Components:


integrity-plugin



Created:


09/Dec/14 6:27 PM



Description:


Hi,

I am currently working on Jenkins with PTC Integrity, As I want to checkin the result back to integrity after the build, I hope jenkins allows to checkin the whole project instead of single file. Let me know is there is any patch can do this activity?

Thanks,
Shankar




Project:


Jenkins



Priority:


Minor



Reporter:


Shankar k

























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] [workflow-plugin] (JENKINS-25979) Finish Groovy CPS coverage

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 created  JENKINS-25979


Finish Groovy CPS coverage















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


workflow-plugin



Created:


09/Dec/14 5:58 PM



Description:


Full language coverage.

The remaining tasks should be driven by throw new UnsupportedOperationException in CpsTransformer.


	synchronized statements (maybe warn and ignore?)
	Method pointer _expression_
	List spread _expression_ x=[2,3]; y=[1,*x,4]; assert y=[1,2,3,4]
	Map spread _expression_
	Spread method call: x = [1,2,3]; assert x*.toString() = ["1","2","3"]
	Safe method call: x=null; assert x?.foo()==null



See also comment in localMethodCallWithinLotsOfBranches.groovy.

Must also ensure that any exception in this area is properly reported as an error in the log, rather than simply killing the VM thread.




Project:


Jenkins



Priority:


Major



Reporter:


Jesse Glick

























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] [elasticbox-plugin] (JENKINS-25978) Workflow integration

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 created  JENKINS-25978


Workflow integration















Issue Type:


New Feature



Assignee:


Unassigned


Components:


elasticbox-plugin



Created:


09/Dec/14 5:51 PM



Description:


This might be an interesting integration that highlights the ability of the workflow to utilize temporary servers.




Project:


Jenkins



Labels:


workflow




Priority:


Major



Reporter:


Jesse Glick

























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] [findbugs-plugin] (JENKINS-25977) Make FindBugsPublisher a SimpleBuildStep

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 created  JENKINS-25977


Make FindBugsPublisher a SimpleBuildStep















Issue Type:


New Feature



Assignee:


Ulli Hafner



Components:


findbugs-plugin



Created:


09/Dec/14 5:41 PM



Description:


Would allow for use from workflows. (Similarly for any other publishers in this plugin suite.) analysis-core apparently needs some refactoring to work with Run (+ FilePath workspace) in place of AbstractBuild.




Project:


Jenkins



Labels:


workflow




Priority:


Major



Reporter:


Jesse Glick

























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] [deployer-framework-plugin] (JENKINS-25976) Make DeployPublisher a SimpleBuildStep

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 created  JENKINS-25976


Make DeployPublisher a SimpleBuildStep















Issue Type:


New Feature



Assignee:


stephenconnolly



Components:


deployer-framework-plugin



Created:


09/Dec/14 5:38 PM



Description:


Would allow for use from workflows.




Project:


Jenkins



Labels:


workflow




Priority:


Major



Reporter:


Jesse Glick

























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] [workflow-plugin] (JENKINS-25975) More reliable test infrastructure

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 created  JENKINS-25975


More reliable test infrastructure















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


workflow-plugin



Created:


09/Dec/14 5:31 PM



Description:


There are too many @RandomlyFails tests. SemaphoreStep should be used more consistently in place of WatchYourStep and waiting for the execution to suspend. (Already prototyped in WorkflowTest.env.)

Also any build logs should be streamed immediately to stderr, rather than forcing the test to include the current log in every assertion message observed to fail. (In combination with SemaphoreStep, this should also more reliably flush recent output: WorkflowRun flushes logs when new steps are run.)




Project:


Jenkins



Labels:


testing




Priority:


Major



Reporter:


Jesse Glick

























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] [workflow-plugin] (JENKINS-25974) RetryStep and CatchErrorStep should use new API to send output to end of block

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 created  JENKINS-25974


RetryStep and CatchErrorStep should use new API to send output to end of block















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


workflow-plugin



Created:


09/Dec/14 5:27 PM



Description:


https://github.com/jenkinsci/workflow-plugin/pull/27 introduced a new API but did not use it in the originally envisioned use cases.




Project:


Jenkins



Priority:


Major



Reporter:


Jesse Glick

























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-25973) Provide an option to exclude disabled projects from a view

[heinrichmar...@hotmail.com (JIRA)]

Martin Heinrich
 created  JENKINS-25973


Provide an option to exclude disabled projects from a view















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


09/Dec/14 4:58 PM



Description:


Views allow to select projects using a regex. Please provide a filter option to exclude disabled projects.




Environment:


1.589




Project:


Jenkins



Labels:


user-experience
gui




Priority:


Minor



Reporter:


Martin Heinrich

























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-25972) Add disable/enable project to drop down menu

[heinrichmar...@hotmail.com (JIRA)]

Martin Heinrich
 created  JENKINS-25972


Add disable/enable project to drop down menu















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


09/Dec/14 4:56 PM



Description:


Every project has a drop down menu in the name's column of the dashboard view (and in the breadcrumbs and probably elsewhere too). This drop down menu contains "Delete Project", but not "Disable Project".

Please add "Disable Project"/"Enable Project" to the project's drop down menu.




Environment:


1.589




Project:


Jenkins



Labels:


user-experience




Priority:


Minor



Reporter:


Martin Heinrich

























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-25971) Job list and console output are not properly aligned in the new UI

[n...@apache.org (JIRA)]

Ignasi Barrera
 commented on  JENKINS-25971


Job list and console output are not properly aligned in the new UI















Although The environment description says it happens in Chrome, the console alignment also is wrong in Firefox (version 34.0).



























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-25971) Job list and console output are not properly aligned in the new UI

[n...@apache.org (JIRA)]

  
Ignasi Barrera
 edited a comment on  JENKINS-25971


Job list and console output are not properly aligned in the new UI
















Although the environment description says it happens in Chrome, the console alignment also is wrong in Firefox (version 34.0).



























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-25971) Job list and console output are not properly aligned in the new UI

[n...@apache.org (JIRA)]

Ignasi Barrera
 created  JENKINS-25971


Job list and console output are not properly aligned in the new UI















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


09/Dec/14 4:36 PM



Description:


When a view that is not the "All" one is selected as the default view, the job list appears at the bottom of the page, just after the executors box, instead of being near the task menu. This also happens to the Console Output view; it is always displayed at the bottom, after the menu.

The job list appears OK after resizing the window, or if the "All" view is configured as the default one, but the Console Output view always appears in the wrong place.

I've installed the Simple Theme plugin to see if the components are aligned properly in other themes and they work, so it seems something wrong in the default CSS. I've provided my screen resolution and other details in the environment details of the issue.




Environment:


Jenkins v1.593

Ubuntu 14.04.1 LTS

Screen resolution: 1680x1050

Chrome version 40.0.2214.28 beta (64-bit)




Project:


Jenkins



Labels:


gui




Priority:


Major



Reporter:


Ignasi Barrera

























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] [veracode-scanner-plugin] (JENKINS-25823) Sandbox and Scan Name

[boc...@gmail.com (JIRA)]

Mike Bockus
 commented on  JENKINS-25823


Sandbox and Scan Name















Thanks for the recommendation Matteo. Do you think the scan name should be tied back to the Jenkins build? It may be a while before I can update the plugin. I've put this plugin on the back burner now that Veracode has an officially supported Jenkins 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] [mask-passwords-plugin] (JENKINS-19528) Mask Password Plugin should support Maven Style Projects

[misterca...@gmail.com (JIRA)]

Matteo Castellarin
 updated  JENKINS-19528


Mask Password Plugin should support Maven Style Projects
















Change By:


Matteo Castellarin
(09/Dec/14 4:22 PM)




Priority:


Major
Blocker



























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-client-plugin] (JENKINS-25970) Use proxy from http.proxy{Host|Port} JVM properties

[ogon...@gmail.com (JIRA)]

Oliver Gondža
 created  JENKINS-25970


Use proxy from http.proxy{Host|Port} JVM properties















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-client-plugin



Created:


09/Dec/14 4:22 PM



Description:


Git client plugin 1.8.0 does not use proxy from http.proxyHost property nor http_proxy environment variable. I consider this to be a regression upgrading from 1.1.2 as CliGitAPIImpl#checkCredentials was not called before and git client handled http_proxy variable as expected.


FATAL: Failed to fetch from  [Open URL]
hudson.plugins.git.GitException: Failed to fetch from  [Open URL]
 at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:624)
 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:856)
 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:881)
 at hudson.model.AbstractProject.checkout(AbstractProject.java:1411)
 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)
 at hudson.model.Run.execute(Run.java:1665)
 at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
 at hudson.model.ResourceController.execute(ResourceController.java:88)
 at hudson.model.Executor.run(Executor.java:246)
Caused by: hudson.plugins.git.GitException: Failed to connect to  [Open URL] (exception: java.net.SocketException: Network is unreachable)
 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:1935)
 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1123)
 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:87)
 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:254)
 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
 at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
 at hudson.remoting.UserRequest.perform(UserRequest.java:118)
 at hudson.remoting.UserRequest.perform(UserRequest.java:48)
 at hudson.remoting.Request$2.run(Request.java:328)
 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
 at java.lang.Thread.run(Thread.java:662)






Project:


Jenkins



Priority:


Minor



Reporter:


Oliver Gondža

























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] [mask-passwords-plugin] (JENKINS-19528) Mask Password Plugin should support Maven Style Projects

[misterca...@gmail.com (JIRA)]

Matteo Castellarin
 commented on  JENKINS-19528


Mask Password Plugin should support Maven Style Projects















Last activity on this one is dated 2013. Any improvement? I am still experiencing the issue (plugin version 2.7.2).



























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] [_test] (JENKINS-25881) The Jenkins homepage crashes

[ciprian_vin...@yahoo.com (JIRA)]

Ciprian Vintea
 closed  JENKINS-25881 as Not A Defect


The Jenkins homepage crashes
















It wasn't a defect from Jenkins. An incomplete or wrong configuration for a build pipeline view has generated this error for me. Sorry for this ticket.





Change By:


Ciprian Vintea
(09/Dec/14 4:09 PM)




Status:


Open
Closed





Resolution:


Not A Defect



























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] [_test] (JENKINS-25881) The Jenkins homepage crashes

[ciprian_vin...@yahoo.com (JIRA)]

Ciprian Vintea
 commented on  JENKINS-25881


The Jenkins homepage crashes















Wrong or incomplete configuration in build pipeline view has generated this issue, for me. I have removed that view (jenkins_home/view/view-name/delete) and now it's working fine.



























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] [xunit-plugin] (JENKINS-25969) Reduce verbosity of log output (or make it configurable)

[lars.mallinckr...@1und1.de (JIRA)]

Lars Mallinckrodt
 created  JENKINS-25969


Reduce verbosity of log output (or make it configurable)















Issue Type:


Improvement



Assignee:


Gregory Boissinot



Components:


xunit-plugin



Created:


09/Dec/14 4:06 PM



Description:


Depending on the amount of files to be converted, XUnitConversionService::convert produces A LOT of INFO output on the build console (in our case: several megabytes of "[xUnit] [INFO] Converting {some xml file}"), which is a PITA when taking a peek at the logs. 

It would be very welcomed if the verbosity of the output could be somewhat reduced, or perhaps made configurable (e.g. log only WARN and worse, or log only ERROR and worse, and so on).




Project:


Jenkins



Priority:


Minor



Reporter:


Lars Mallinckrodt

























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] [veracode-scanner-plugin] (JENKINS-25823) Sandbox and Scan Name

[misterca...@gmail.com (JIRA)]

Matteo Castellarin
 commented on  JENKINS-25823


Sandbox and Scan Name















ping



























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] [xcode-plugin] (JENKINS-22130) "keychain with the same name already exists" error with developer profile import

[lacos...@java.net (JIRA)]

lacostej
 commented on  JENKINS-22130


"keychain with the same name already exists" error with developer profile import















The cause of the issue is that we use list-keychains incorrectly. list-keychains is used to manage it's own list of keychains not to list the existing ones.
I have a fix for the issue. I will push it later today.



























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-plugin] (JENKINS-25968) False positive changes trigger builds

[nbon...@valipost.com (JIRA)]

valipost nicolas
 created  JENKINS-25968


False positive changes trigger builds















Issue Type:


Bug



Assignee:


Unassigned


Components:


p4-plugin



Created:


09/Dec/14 3:30 PM



Description:


So I discovered recently that there is an official Jenkins plugin now. I started using it 2 weeks ago, and I have a lot of false positives on "code changes" (Already 1000 builds with 0 commit on perforce for this product).
I have ~20 different builds checking every 20 min for new changes. My view is configured like this :

//depot/product1/current/... //jenkins_ESXi_2/product1/current/...

For every false positive, this is the log scrutation jenkins gives me. It's exactly the same for every build. (and it says there are changes but of course there aren't):

Started on 9 déc. 2014 15:43:42
Polling SCM changes on master
P4: Polling with client: jenkins_ESXi_2
... found change: 77
... found change: 91
... found change: 273
... found change: 499
... found change: 511
... found change: 621
... found change: 655
... found change: 709
... found change: 733
... found change: 734
... found change: 780
... found change: 892
... found change: 903
... found change: 920
... found change: 938
... found change: 1038
... found change: 1066
... found change: 1112
... found change: 1117
... found change: 1118
... found change: 1415
... found change: 2107
... found change: 2254
... found change: 2278
... found change: 2764
... found change: 3062
... found change: 3166
... found change: 3416
... found change: 3446
... found change: 3489
... found change: 3551
... found change: 3754
... found change: 3824
... found change: 3829
... found change: 3832
... found change: 4029
... found change: 4122
... found change: 4617
... found change: 4769
... found change: 4812
... found change: 4922
... found change: 5101
... found change: 5136
... found change: 5159
... found change: 5222
... found change: 5325
... found change: 5372
Done. Took 5,1 s
Changes found




Project:


Jenkins



Priority:


Minor



Reporter:


valipost nicolas

























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-plugin] (JENKINS-25340) lost trend history after skipping build

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 commented on  JENKINS-25340


lost trend history after skipping build















There is no argument about the desirability of showing a trend past a few deleted builds, only the best way to implement that without regressing performance. Someone (perhaps myself) needs to spend a couple hours creating a test asserting that the number of additional build records loaded by virtue of displaying the trend graph (relative to what is shown in the Build History widget anyway) is zero or small, so that an alternate algorithm can be picked to decide which builds to include.

(JENKINS-24380 may make it possible to introduce a core API for cheaply determining whether a build of a given number is supposed to exist without actually loading it; if so, this would be an attractive choice, though it would require a dependency on a post-LTS core release. TBD.)

As an aside, Peter Winkler I think your use case would be better served by using the “skipped” status of test cases/suites. This records the fact that the build did run (at a certain time, with a certain changelog, etc.), and records what tests did run to completion—passing or failing—as well as recording which tests were omitted from the suite, or started to run but were killed due to some transient problem with the environment.



























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-19447) JDK installation hangs forever

[dogf...@java.net (JIRA)]

dogfood
 commented on  JENKINS-19447


JDK installation hangs forever















Integrated in  jenkins_main_trunk #3858
 JENKINS-19447 use standard arguments to set installer log file. (Revision a98ccdff0f074b10907ac1b41d3c26bf33e878b0)

 Result = SUCCESS
nicolas de loof : a98ccdff0f074b10907ac1b41d3c26bf33e878b0
Files : 

	core/src/main/java/hudson/tools/JDKInstaller.java





























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-25967) Job rename does not update reference to new workspace

[stefan.stro...@hp.com (JIRA)]

Stefan Strobel
 created  JENKINS-25967


Job rename does not update reference to new workspace















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


Capture.PNG



Components:


core



Created:


09/Dec/14 1:45 PM



Description:


Hi team,

I am experiencing a nasty behavior when renaming a job.
The job itself is properly renamed, as well as the directory names on file system level.
However, the reference to the workspace is not updated. This has a side effect as we are using the git polling mechanism which is dependent on the .git folder within the workspace. As the job assumes no workspace is available it triggers a new build which is NOT what we want.
I know that there is the proposal to specify a custom workspace folder, see http://stackoverflow.com/questions/21682413/renaming-a-jenkins-job

But this is not what we want.

So I ask the team to modify the renaming function to also update the reference to the new workspace. is this possible?

Thanks a lot!
Stefan




Environment:


Jenkins 1.584, RHEL 6




Project:


Jenkins



Labels:


git
polling
jenkins
workspace
reference
rename
update




Priority:


Major



Reporter:


Stefan Strobel

























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] [configurationslicing-plugin] (JENKINS-25964) NullPointerExcpetion when try to slice parameters

[thomas.wab...@siemens.com (JIRA)]

Thomas Wabner
 commented on  JENKINS-25964


NullPointerExcpetion when try to slice parameters















I have found the root cause of this error:

I have a project with a parameter definition like this:


  deployment_reason  
 

It is missing the  and  tags. It should look like this



  deployment_reason 
   
   
 

I have changed the code in UnorderedStringSlice for the method addLineWithSets to following:


private static void addLineWithSets(Map> map, String s, String name) {
			  if (null == s) {
	LOGGER.severe("found illegal line with null value for name: "+name);
	// do nothing
	return;
}
if(!map.containsKey(s)) {
map.put(s, new HashSet());
}
Set list= map.get(s);
list.add(name);
}




























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] [view-job-filters-plugin] (JENKINS-25966) Filter on 'raw' job configuration (RegEx)

[jank...@gmail.com (JIRA)]

Jan Krag
 created  JENKINS-25966


Filter on 'raw' job configuration (RegEx)















Issue Type:


New Feature



Assignee:


Jacob Robertson



Components:


view-job-filters-plugin



Created:


09/Dec/14 12:59 PM



Description:


It would be nice to have the option to RegEx match on the full job configuration xml. This would allow us to create filters for cases that are too specific to add as a full-blown option in the plugin.

In my current case, I needed to show (in order to update) all jobs that use the submodule feature of git, and therefore wanted a view that showed all of these. Specifically finding all jobs with: true in the configuration.

I don't consider this specific case worth adding as a feature, but using RegEx on the entire configuration (or something similar) would allow me to "build my own" view on a case-by-case basis.

(after that, I just need a way to RegEx select any other configured option and display it in a column , but I guess this is not in scope for the view filter plugin. )





Environment:


Using Plugin version 1.26 on Jenkins LTS 1.580.1




Project:


Jenkins



Priority:


Minor



Reporter:


Jan Krag

























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-plugin] (JENKINS-25340) lost trend history after skipping build

[wink...@dresearch-fe.de (JIRA)]

Peter Winkler
 commented on  JENKINS-25340


lost trend history after skipping build















In our opinion the assumption that there is no gap in the number of history builds is a bad assumption.
It is comparable with the assumption that the offered feature to delete builds is no longer a valid feature.
Besides building our firmware we use JENKINS to test our firmware in several test suites in the hours of the night. In this topic means FAILED (red) that a firmware error avoids the complete test suite, UNSTABLE (yellow) that the suite has found firmware errors and STABLE (green) that the suite passed without finding firmware errors. To keep this meaning we delete test builds on following conditions:

	Not our firmware raised a FAILED build (e.g. network problems or github server problems)
	The test build was interrupted due to any reason (test developer want to change versions to be tested, forgotten configuration etc.)
	For developing purpose (to test the test in the JENKINS environment) only a subset of test cases was started in the suite (because the whole suite would be taken hours)



May be there are more reasons to use the “delete build” feature.  In formerly JENKINS versions this procedure was possible without influence to the history graph. With the change due to JENKINS-23945 such a delete of a build disturbs the history graph that kind that deletion of builds is out of usability.
We hope that there is another possibility to be aware JENKINS-23945 on the one hand and keep the history graph independent of gaps in the build list raised by deletion on the other hand.



























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-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582

[w.male...@gmail.com (JIRA)]

  
Waldek M
 edited a comment on  JENKINS-24946


JUnit Tests Results fail to archive in V1.582
















Similar issue with 1.3 Junit plugin, Jenkins 1.586.
Reverting to Junit 1.1 solved it.



Recording test results
ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
java.lang.NoClassDefFoundError: hudson/tasks/junit/JUnitParser$ParseResultCallable
	at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:90)
	at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:120)
	at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:137)
	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
	at hudson.model.Run.execute(Run.java:1784)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)





























This 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-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582

[w.male...@gmail.com (JIRA)]

Waldek M
 commented on  JENKINS-24946


JUnit Tests Results fail to archive in V1.582















Similar issue with 1.3 Junit plugin, Jenkins 1.586.
Reverting to Junit 1.1 solved it.


Recording test results
ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception
java.lang.NoClassDefFoundError: hudson/tasks/junit/JUnitParser$ParseResultCallable
	at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:90)
	at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:120)
	at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:137)
	at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
	at hudson.model.Run.execute(Run.java:1784)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)





























This 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] [configurationslicing-plugin] (JENKINS-25964) NullPointerExcpetion when try to slice parameters

[thomas.wab...@siemens.com (JIRA)]

Thomas Wabner
 commented on  JENKINS-25964


NullPointerExcpetion when try to slice parameters















Found one missed piece in the log:
Caused by: java.lang.NullPointerException
	at java.lang.String$CaseInsensitiveComparator.compare(String.java:1177)
	at java.lang.String$CaseInsensitiveComparator.compare(String.java:1170)
	at java.util.TimSort.countRunAndMakeAscending(TimSort.java:324)
	at java.util.TimSort.sort(TimSort.java:189)
	at java.util.TimSort.sort(TimSort.java:173)
	at java.util.Arrays.sort(Arrays.java:659)
	at java.util.Collections.sort(Collections.java:217)
	at configurationslicing.UnorderedStringSlice.getConfiguredValues(UnorderedStringSlice.java:110)
	... 130 more



























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-parameter-plugin] (JENKINS-23473) empty tags / revisions list when using Folders - NullPointerException - getParentProject()

[shiry...@gmail.com (JIRA)]

Roman Shiryaev
 commented on  JENKINS-23473


empty tags  / revisions list  when using Folders - NullPointerException - getParentProject() 















I can also confirm the issue. Moving job from folder to root directory helps.



























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-25962) Using Jenkins Job Builder to create triggers based on comment regex fails to trigger

[rsand...@cloudbees.com (JIRA)]

rsandell
 commented on  JENKINS-25962


Using Jenkins Job Builder to create triggers based on comment regex fails to trigger















This is related to JENKINS-23152 that I'm currently working on.
The issue is that Jenkins Job Builder is using http post of config.xml and in that scenario core isn't calling trigger.stop/start in the same way as when saving config via UI, or it's using CLI which behaves even worse, so the old configuration from the previous trigger config hangs around and the new one isn't activated correctly.



























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] [jclouds-plugin] (JENKINS-23173) "userData cannot be empty" exception when trying to provision EC2 slaves

[h...@univention.de (JIRA)]

Philipp Hahn
 commented on  JENKINS-23173


"userData cannot be empty" exception when trying to provision EC2 slaves















This happens when the userData is empty, as  creates an empty Byte[] array from that, which  refuses.

Go to "Manage Jenkins -> Configure System -> Cloud -> Cloud (JCloud) -> Cloud Instance Templates -> Extended... -> User Data" and enter some non-empty text, for example some "#cloud-config".



























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] [jacoco-plugin] (JENKINS-25616) Support for coverage.xml generated by Android tools

[sschube...@gmail.com (JIRA)]

Sebastian Schuberth
 commented on  JENKINS-25616


Support for coverage.xml generated by Android tools















Just for the record, the "createDebugCoverageReport" gets dynamically created by the Gradle Android plugin only if the "debug" build type's "testCoverageEnabled" property is set to "true".



























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] [matrix-project-plugin] (JENKINS-23902) Matrix parent takes executor slot and blocks children

[ja...@howeswho.co.uk (JIRA)]

James Howe
 commented on  JENKINS-23902


Matrix parent takes executor slot and blocks children















Odd. With no apparent changes to config or plugins, they started using flyweight executors again.



























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







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

[JIRA] [jacoco-plugin] (JENKINS-25616) Support for coverage.xml generated by Android tools

[martin.nonnenmac...@gmail.com (JIRA)]

  
Martin Nonnenmacher
 edited a comment on  JENKINS-25616


Support for coverage.xml generated by Android tools
















+1 from me. It would be great if the plugin would support using existing xml reports.
I have a script that generates XML and HTML coverage reports and is integrated with the build environment, so it would be much easier to use the reports generated by the script than to keep the configuration of the Jacoco plugin up to date.



























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] [jobgenerator-plugin] (JENKINS-25965) Job Generator + Dynamic parameter choice

[arnaud.sengm...@gmail.com (JIRA)]

Arnaud Sengmany
 created  JENKINS-25965


Job Generator + Dynamic parameter choice















Issue Type:


Bug



Assignee:


Unassigned


Components:


jobgenerator-plugin



Created:


09/Dec/14 9:21 AM



Description:


Hi,

I tried to create a job generator item then set a dynamic parameter choice within this item but it didn't work. When I try to create a simple project, dynamic parameter choice does work. So the problem seems to be related to the job generator plugin.




Project:


Jenkins



Priority:


Minor



Reporter:


Arnaud Sengmany

























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-24895) An existing connection was forcibly closed by the remote host

[ganc...@libero.it (JIRA)]

Graziano Ancona
 commented on  JENKINS-24895


An existing connection was forcibly closed by the remote host















You can have it even if the Slave is not launched as a service: I made a test launching an infinite loop always with the same job (approx 1.5hrs), after some loops I took the error. 
At the same time ping works perfectly (so it's not a network problem), and all the process where alive (no trace of crash/restart/etc in logs).
I got all the logs if you need.



























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] [configurationslicing-plugin] (JENKINS-25964) NullPointerExcpetion when try to slice parameters

[thomas.wab...@siemens.com (JIRA)]

Thomas Wabner
 created  JENKINS-25964


NullPointerExcpetion when try to slice parameters















Issue Type:


Bug



Assignee:


mdonohue



Components:


configurationslicing-plugin



Created:


09/Dec/14 8:16 AM



Description:


If I try to "slice" parameters for my projects I get a empty page. After taking a look into the log files I see the following stack trace:

INFO: Loaded: class configurationslicing.tools.GroovySlicer
Dec 09, 2014 9:08:27 AM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: it.configuredValues in /jenkins/slicing/parameters/. Reason: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
	at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
	at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
	at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
	at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
	at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
	at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
	at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
	at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
	at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61)
	at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:94)
	at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
	at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
	at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
	at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
	at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
	at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
	at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
	at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
	at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
	at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
	at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(Cal