date:20140109

Gregory B
created JENKINS-21301

Jenkins stops responding to HTTP requests outside builds

Issue Type:

Bug

Assignee:

Unassigned

Attachments:

heap-20140108.7z.001, heap-20140108.7z.002, heap-20140108.7z.003, heap-20140108.7z.004, heap-20140108.7z.005, heap-20140108.7z.006, heap-20140108.7z.007, heap-20140108.7z.008, heap-20140108.7z.009, heap-20140108.7z.010, heap-20140108.7z.011, heap-20140108.7z.012, System Information [Jenkins].pdf, thread-20140108.dump

Components:

core, fitnesse

Created:

09/Jan/14 11:53 AM

Description:

Jenkins stops responding to HTTP requests and must be restarted every morning.
The problem appends when no job is running as all emails are sent.

Enclosed: thread dump, heap dump and system information.

Thank you Awesome Jenkins Team in advance for your help.

Environment:

Red Hat Entreprise 6.3 x64

Project:

Jenkins

Priority:

Major

Reporter:

Gregory B

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

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

[JIRA] [maven] (JENKINS-20209) Maven plugin sends email notification to null address

2014-01-09 Thread dmitry.babur...@db.com (JIRA)















































Dmitry Baburkin
 commented on  JENKINS-20209


Maven plugin sends email notification to null address















Thanks guys, 2.0.1 worked for LTS 1.532.1



























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







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

[JIRA] [core] (JENKINS-21301) Jenkins stops responding to HTTP requests outside builds















































Gregory B
 updated  JENKINS-21301


Jenkins stops responding to HTTP requests outside builds
















Change By:


Gregory B
(09/Jan/14 11:58 AM)




Priority:


Major
Critical



























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







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

[JIRA] [core] (JENKINS-21301) Jenkins stops responding to HTTP requests outside builds















































Gregory B
 updated  JENKINS-21301


Jenkins stops responding to HTTP requests outside builds
















Change By:


Gregory B
(09/Jan/14 11:57 AM)




Description:


JenkinsstopsrespondingtoHTTPrequestsandmustberestartedeverymorning.Theproblemappendswhennojobisrunningasallemailsaresent.
Thethreaddumpindicateslotsofblockedthreads,butIdontread/understandtherelationshiptojobexecutions.
Enclosed:threaddump,heapdumpandsysteminformation.ThankyouAwesomeJenkinsTeaminadvanceforyourhelp.



























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







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

[JIRA] [ldap] (JENKINS-21302) use LDAP information to expose more user details

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















































Nicolas De Loof
 created  JENKINS-21302


use LDAP information to expose more user details















Issue Type:


Improvement



Assignee:


Kohsuke Kawaguchi



Components:


ldap



Created:


09/Jan/14 11:59 AM



Description:


LDAP provide detailed informations on user (full name, phone number, email, etc). Jenkins plugin should expose them a UserProperty so they can be displayed on /user/id.
Could also use the LDAP provided email to populate Mailer.UserProperty




Project:


Jenkins



Priority:


Minor



Reporter:


Nicolas De Loof

























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







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

[JIRA] [core] (JENKINS-18649) Renaming jobs should be a separate permission from configuring

2014-01-09 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-18649


Renaming jobs should be a separate permission from configuring















JENKINS-18678 could be circumvented by just taking away users' permission to rename while keeping the permission to configure jobs.



























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







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

[JIRA] [testng] (JENKINS-20985) TestNG plugin should has a possibility to use thresholds for failed tests

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
















































Gavin Gray
 assigned  JENKINS-20985 to Gavin Gray



TestNG plugin should has a possibility to use thresholds for failed tests
















Change By:


Gavin Gray
(09/Jan/14 12:11 PM)




Assignee:


NalinMakar
GavinGray



























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







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

[JIRA] [config-file-provider] (JENKINS-16706) Configure provided settings.xml at the Maven plugin level, not at the Maven job level

2014-01-09 Thread florian.zscho...@cycos.com (JIRA)















































Florian Zschocke
 commented on  JENKINS-16706


Configure provided settings.xml at the Maven plugin level, not at the Maven job level















This sounds like a duplicate of JENKINS-17723. The latter is marked as resolved but it seems not to be working.
I actually don't get the global Maven Configuration settings to work at all. No matter what I set as default settings providers, only the default maven settings are used, i.e. user settings from ~/.m2 and global settings from the maven installation. No override takes place:

Executing Maven:  -B -f /var/lib/jenkins/jobs/test_maven/workspace/pom.xml help:effective-settings




























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







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

[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542

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















































Yoichi Nakayama
 commented on  JENKINS-20898


SVN post commit hook not working after update to 1.542















I've tried to reproduce it with Jenkins 1.542 and Subversion-PI 1.54 on Ubuntu,
but build is triggered as expected.
There may be some missing conditions. How can I reproduce the issue?



























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







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

[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542

2014-01-09 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-20898


SVN post commit hook not working after update to 1.542















nothing shows up in the log

Try creating a new log for hudson.scm with more verbose logging output.



























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







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

[JIRA] [core] (JENKINS-19246) Configure Project loading overloay not hiding error invalid gitTool selection Default

2014-01-09 Thread rica...@ricardomartins.net.br (JIRA)















































Ricardo Martins
 commented on  JENKINS-19246


Configure Project loading overloay not hiding error invalid gitTool selection Default















Still has the issue on 1.544



























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







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

[JIRA] [core] (JENKINS-21303) NPE in hudson.model.Job.getEnvironment

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















































stephenconnolly
 created  JENKINS-21303


NPE in hudson.model.Job.getEnvironment















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


09/Jan/14 12:46 PM



Description:


If a retention strategy is in the process of decommissioning a node while Job.getEnvironment is called there will be a NPE thrown.




Project:


Jenkins



Priority:


Minor



Reporter:


stephenconnolly

























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







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

[JIRA] [core] (JENKINS-21303) NPE in hudson.model.Job.getEnvironment















































SCM/JIRA link daemon
 commented on  JENKINS-21303


NPE in hudson.model.Job.getEnvironment















Code changed in jenkins
User: Stephen Connolly
Path:
 core/src/main/java/hudson/model/Job.java
http://jenkins-ci.org/commit/jenkins/e998c2a670fbb7f9e32af37218e7076de696455e
Log:
  FIX JENKINS-21303 There is a NPE here that can and does happen for real when an aggresive slave retention strategy interacts with post build triggers that want to do token macro expansion





























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







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

[JIRA] [git] (JENKINS-21277) Job cannot be built with parameters















































Mark Waite
 commented on  JENKINS-21277


Job cannot be built with parameters















I was unable to duplicate this bug.  Can you provide more information about the context where it fails and the cases where the work around resolves the issue?

I tried the following steps using Jenkins 1.532.1, Git plugin 2.0.1, and Git client plugin 1.6.0:


	Create a new job that is a freestyle project
	Configure the job to use a git repository (mine used a local git repo with git:// protocol)
	Configure the job as a parameterized job with a single string parameter (mine was named STRING_PARAMETER)
	Add an XShell build step to echo $STRING_PARAMETER
	Run that job several times with different values for STRING_PARAMETER





























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







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

[JIRA] [git] (JENKINS-21264) inverse build strategy issues

Mark Waite
commented on JENKINS-21264

inverse build strategy issues

I was able to duplicate the behavior reported here.

I assume that the message "No new revisions were found; the most-recently built branch will be built again" is relevant to this case. I assume that since the plugin decided there were no changes on any branches, it built the last branch again, rather than applying the selected inverse branch choosing strategy.

The steps I took:

Create a new freestyle project
Configure it to use Git as SCM with a nearby git:// protocol repository
Add the branch choosing strategy, set it to "Inverse"
Add an SCM poll every two minutes setting to the job
Save the job - Confirm the job ran multiple times, once for each branch not named "master"
Modify the branch choosing strategy to default
Run the job - confirm it builds the master branch
Modify the branch choosing strategy to Inverse
Run the job - confirm it incorrectly builds the master branch again

[JIRA] [reverse-proxy-auth] (JENKINS-21304) NPE - Reverse Proxy Authentication

2014-01-09 Thread mar...@campbellsoftware.co.uk (JIRA)

Martin Campbell
created JENKINS-21304

NPE - Reverse Proxy Authentication

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Attachments:

stacktrace.TXT

Components:

reverse-proxy-auth

Created:

09/Jan/14 1:08 PM

Description:

Our configuration is that users access Jenkins through an Apache2 reverse proxy that provides integrated browser authentication using Kerberos. Our Jenkins server is configured to use the reverse-proxy-auth to read the X-Forwarded-User HTTP header and set that as the Jenkins user identity.

This has ran for over a year without any issues.

Recently I updated to V1.546 of Jenkins. Any attempt to access Jenkins now results in a Null Pointer Exception on a page access, rendering this version of Jenkins totally unusable. I've attached the stack trace as a text file to preserve formatting.

Having a brief look at the code, this is occurring on line 366 of the latest reverse-proxy-auth plugin (V1.3). This is simply calling the HTTPServletRequest.getHeader method to retrieve any user name passed in the HTTP request. This is coded to the API docs which state that if such a header does not exist then NULL will be returned.

In V1.546, the implementation of this getHeader method has now started failing. I suspect this is a bug with the bundled version of the Jetty code rather than being a Jenkins code issue. I'll have a look at the code when I get a chance to trace this back but wanted to raise this in case anyone else experiences a similar issue and hopefully link it to any Jetty related bugs that might be raised.

Environment:

Jenkins V1.546

Ubuntu 12.04 LTS

Project:

Jenkins

Priority:

Blocker

Reporter:

Martin Campbell

[JIRA] [depgraph-view] (JENKINS-17327) Subprojects of the Parameterized trigger plugin are not shown in jsplumb view

2014-01-09 Thread d.schu...@buero-s.de (JIRA)















































Dieter Schüle
 commented on  JENKINS-17327


Subprojects of the Parameterized trigger plugin are not shown in jsplumb view















Same issue here. Not only in jsplumbview but also in graphviz view. Would be great if subproject could be treated like other related projects (dependedencies -- arrows). We use a lot of subprojects, the plugin does not make sense without visualition of dependencies to them.



























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







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

[JIRA] [depgraph-view] (JENKINS-17327) Subprojects of the Parameterized trigger plugin are not shown in jsplumb view

2014-01-09 Thread d.schu...@buero-s.de (JIRA)













































 
Dieter Schüle
 edited a comment on  JENKINS-17327


Subprojects of the Parameterized trigger plugin are not shown in jsplumb view
















Same issue here. Not only in jsplumbview but also in graphviz view. Would be great if subproject could be treated like other related projects (dependedencies -- arrows). We use a lot of subprojects, the plugin does not make sense without visualization of dependencies to them.



























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







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

[JIRA] [core] (JENKINS-21301) Jenkins stops responding to HTTP requests outside builds















































Gregory B
 updated  JENKINS-21301


Jenkins stops responding to HTTP requests outside builds
















Change By:


Gregory B
(09/Jan/14 1:15 PM)




Description:


JenkinsstopsrespondingtoHTTPrequestsandmustberestartedeverymorning.Theproblemappendswhennojobisrunningasallemailsaresent.Thethreaddumpindicateslotsofblockedthreads,butIdontread/understandtherelationshiptojobexecutions.Enclosed:threaddump,heapdumpandsysteminformation.Thankyou
inadvance
AwesomeJenkinsTeam
inadvance
foryourhelp.



























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







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

[JIRA] [core] (JENKINS-21303) NPE in hudson.model.Job.getEnvironment

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
















































stephenconnolly
 resolved  JENKINS-21303 as Fixed


NPE in hudson.model.Job.getEnvironment
















Change By:


stephenconnolly
(09/Jan/14 1:23 PM)




Status:


Open
Resolved





Assignee:


stephenconnolly





Resolution:


Fixed



























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







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

[JIRA] [git] (JENKINS-21264) inverse build strategy issues

Mark Waite
edited a comment on JENKINS-21264

inverse build strategy issues

I was able to duplicate the behavior reported here.

The steps I took:

After that sequence of verification steps, I then submitted a change to the master branch while the inverse choosing strategy was enabled. I did not expect any build, since the change was to the branch which should have been excluded by the "Inverse" choosing strategy. I was surprised. It built and reported that there were no changes so it was buidling the same version again. I assume that is because the fast remote polling does not support the inverse branch choosing strategy.

I added "Force polling with workspace" and submitted another change to the master branch. That did not cause a build. I submitted a change to another branch, and that caused a rebuild. It appears "Force polling with workspace" may need to be implicitly enabled if the inverse branch choosing strategy is enabled.

[JIRA] [configurationslicing] (JENKINS-15612) Configuration Slicer for Jenkins Build Timeout Plugin missing in Version 1.33?

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















































Steven Kitchen
 commented on  JENKINS-15612


Configuration Slicer for Jenkins Build Timeout Plugin missing in Version 1.33?















I am still seeing this issue with 1.38.3  build timeout 1.12.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/groups/opt_out.

[JIRA] [git] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)
















































SCM/JIRA link daemon
 resolved  JENKINS-14026 as Fixed


git plugin doesnt support branch name contains slash (/)
















Change By:


SCM/JIRA link daemon
(09/Jan/14 1:32 PM)




Status:


Reopened
Resolved





Resolution:


Fixed



























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







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

[JIRA] [config-file-provider] (JENKINS-16706) Configure provided settings.xml at the Maven plugin level, not at the Maven job level

2014-01-09 Thread and...@hammar.net (JIRA)















































Anders Hammar
 commented on  JENKINS-16706


Configure provided settings.xml at the Maven plugin level, not at the Maven job level















Yes, this should be closed as a dupe of JENKINS-17723. That fix works in my LTS 1.532.1 installation (at least for settings file, don't use global settings file). It gives a default configuration on the project, which can then be re-configured should it be required.



























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







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

[JIRA] [git] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)















































SCM/JIRA link daemon
 commented on  JENKINS-14026


git plugin doesnt support branch name contains slash (/)















Code changed in jenkins
User: Vincent Latombe
Path:
 src/main/java/hudson/plugins/git/GitSCM.java
 src/test/java/hudson/plugins/git/GitSCMTest.java
http://jenkins-ci.org/commit/git-plugin/12b16252efb7f6ad0cb80ff04f7557b60f7bfaca
Log:
  FIXED JENKINS-14026 git plugin doesn't support branch name contains
slash ("/")

The main issue is to determine whether an input containing a slash is a
qualified branch (remote followed by branch name) or a branch name on
which the remote name needs to be prepended.

When there is only one remote involved, that can be solved by prepending
the remote name to the branch name if the branch name doesn't already
start with the remote name.

Note : This commit doesn't cover cases where the given branch name is a
pattern


Compare: https://github.com/jenkinsci/git-plugin/compare/ab720af8b26b^...12b16252efb7




























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







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

[JIRA] [git] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)















































SCM/JIRA link daemon
 commented on  JENKINS-14026


git plugin doesnt support branch name contains slash (/)















Code changed in jenkins
User: Vincent Latombe
Path:
 src/main/java/hudson/plugins/git/GitSCM.java
 src/test/java/hudson/plugins/git/GitSCMTest.java
http://jenkins-ci.org/commit/git-plugin/13c2b08009fce7273051739acae19cfaa4d76b17
Log:
  FIXED JENKINS-14026 git plugin doesn't support branch name contains
slash ("/")

The main issue is to determine whether an input containing a slash is a
qualified branch (remote followed by branch name) or a branch name on
which the remote name needs to be prepended.

When there is only one remote involved, that can be solved by prepending
the remote name to the branch name if the branch name doesn't already
start with the remote name.

Note : This commit doesn't cover cases where the given branch name is a
pattern





























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







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

[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

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















































dimitkoto
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















+1



























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







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

[JIRA] [elastic-axis] (JENKINS-21305) elastic axis definition cannot contain multiple labels, though helps says that is allowed

Mark Waite
created JENKINS-21305

elastic axis definition cannot contain multiple labels, though helps says that is allowed

Issue Type:

Bug

Assignee:

Unassigned

Components:

elastic-axis

Created:

09/Jan/14 1:51 PM

Description:

If I want to run a multi-configuration job on all windows machines (as identified by the NodeLabeler plugin), elastic axis makes that work very well. All machines with that label are used to execute the job.

If I want to run a multi-configuration job on all Debian machines (as identified by the NodeLabeler plugin), elastic axis makes that work very well. All machines with that label are used to execute the job.

If I want to run a multi-configuration job on all Debian machines and on all windows machines (as identified by the NodeLabeler plugin), the plugin help suggests I can place a space separated list of labels. When I place "Debian windows" in the list of labels, no nodes are selected.

It appears the space separated list of labels is not being evaluated.

Environment:

Jenkins 1.532.1

Elastic axis 1.1

Project:

Jenkins

Priority:

Major

Reporter:

Mark Waite

[JIRA] [core] (JENKINS-18224) TransientActionFactory
















































SCM/JIRA link daemon
 resolved  JENKINS-18224 as Fixed


TransientActionFactory
















Change By:


SCM/JIRA link daemon
(09/Jan/14 1:55 PM)




Status:


InProgress
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-18224) TransientActionFactory















































SCM/JIRA link daemon
 commented on  JENKINS-18224


TransientActionFactory















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/matrix/DefaultMatrixExecutionStrategyImpl.java
 core/src/main/java/hudson/model/AbstractBuild.java
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/hudson/model/Actionable.java
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/Job.java
 core/src/main/java/hudson/model/Queue.java
 core/src/main/java/hudson/model/Run.java
 core/src/main/java/hudson/model/TransientBuildActionFactory.java
 core/src/main/java/hudson/model/TransientComputerActionFactory.java
 core/src/main/java/hudson/model/TransientProjectActionFactory.java
 core/src/main/java/hudson/model/queue/WorkUnitContext.java
 core/src/main/java/jenkins/model/ModelObjectWithContextMenu.java
 core/src/main/java/jenkins/model/TransientActionFactory.java
 core/src/main/resources/hudson/matrix/MatrixProject/index.jelly
 core/src/main/resources/hudson/model/AbstractBuild/index.jelly
 core/src/main/resources/hudson/model/AbstractProject/main.jelly
 core/src/main/resources/lib/hudson/actions.jelly
 core/src/main/resources/lib/hudson/project/projectActionFloatingBox.jelly
 test/src/test/java/jenkins/model/TransientActionFactoryTest.java
http://jenkins-ci.org/commit/jenkins/f1a751f79dfbb975e4c436fd0967323e1ae7b8c6
Log:
  FIXED JENKINS-18224 Introduced TransientActionFactory.





























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







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

[JIRA] [core] (JENKINS-18224) TransientActionFactory















































SCM/JIRA link daemon
 commented on  JENKINS-18224


TransientActionFactory















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/Actionable.java
 core/src/main/java/jenkins/model/TransientActionFactory.java
http://jenkins-ci.org/commit/jenkins/6eb191964b415d7f0a025847d5444db922d6fe49
Log:
  JENKINS-18224 Preparing to merge #1059.





























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







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

[JIRA] [core] (JENKINS-18224) TransientActionFactory















































SCM/JIRA link daemon
 commented on  JENKINS-18224


TransientActionFactory















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/cli/SetBuildParameterCommand.java
 core/src/main/java/hudson/matrix/DefaultMatrixExecutionStrategyImpl.java
 core/src/main/java/hudson/model/AbstractBuild.java
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/hudson/model/Actionable.java
 core/src/main/java/hudson/model/CauseAction.java
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/Job.java
 core/src/main/java/hudson/model/Queue.java
 core/src/main/java/hudson/model/Run.java
 core/src/main/java/hudson/model/TransientBuildActionFactory.java
 core/src/main/java/hudson/model/TransientComputerActionFactory.java
 core/src/main/java/hudson/model/TransientProjectActionFactory.java
 core/src/main/java/hudson/model/labels/LabelAtom.java
 core/src/main/java/hudson/model/queue/WorkUnitContext.java
 core/src/main/java/hudson/tasks/Fingerprinter.java
 core/src/main/java/hudson/triggers/SCMTrigger.java
 core/src/main/java/jenkins/model/ModelObjectWithContextMenu.java
 core/src/main/java/jenkins/model/TransientActionFactory.java
 core/src/main/resources/hudson/matrix/MatrixProject/index.jelly
 core/src/main/resources/hudson/model/AbstractBuild/index.jelly
 core/src/main/resources/hudson/model/AbstractProject/main.jelly
 core/src/main/resources/lib/hudson/actions.jelly
 core/src/main/resources/lib/hudson/project/projectActionFloatingBox.jelly
 core/src/test/java/hudson/model/ActionableTest.java
 test/src/test/java/hudson/model/UserTest.java
 test/src/test/java/jenkins/model/TransientActionFactoryTest.java
http://jenkins-ci.org/commit/jenkins/0f7b144fd32544a872075d58300a53b9abcca5f4
Log:
  Merge pull request #1059 from jglick/TransientActionFactory-JENKINS-18224

JENKINS-18224 TransientActionFactory


Compare: https://github.com/jenkinsci/jenkins/compare/e998c2a670fb...0f7b144fd325




























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







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

[JIRA] [core] (JENKINS-18224) TransientActionFactory















































SCM/JIRA link daemon
 commented on  JENKINS-18224


TransientActionFactory















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/cli/SetBuildParameterCommand.java
 core/src/main/java/hudson/model/AbstractBuild.java
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/hudson/model/Actionable.java
 core/src/main/java/hudson/model/CauseAction.java
 core/src/main/java/hudson/model/Computer.java
 core/src/main/java/hudson/model/labels/LabelAtom.java
 core/src/main/java/hudson/tasks/Fingerprinter.java
 core/src/main/java/hudson/triggers/SCMTrigger.java
 test/src/test/java/hudson/model/UserTest.java
http://jenkins-ci.org/commit/jenkins/a22e9feaaef30b89621ae9ca3f33f862ae99f4c7
Log:
  JENKINS-18224 Introduced Actionable.replaceAction, allowing getActions() to be deprecated except for subclasses.





























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







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

[JIRA] [git] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)















































SCM/JIRA link daemon
 commented on  JENKINS-14026


git plugin doesnt support branch name contains slash (/)















Code changed in jenkins
User: Nicolas De loof
Path:
 src/main/java/hudson/plugins/git/GitSCM.java
 src/test/java/hudson/plugins/git/GitSCMTest.java
http://jenkins-ci.org/commit/git-plugin/a67bbc0062fa4dd4d27b8113f3a27840b53dded9
Log:
  Merge pull request #187 from jenkinsci/JENKINS-14026

FIXED JENKINS-14026 git plugin doesn't support branch name contains


Compare: https://github.com/jenkinsci/git-plugin/compare/b75d1e21dc75...a67bbc0062fa




























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







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

[JIRA] [core] (JENKINS-21303) NPE in hudson.model.Job.getEnvironment

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















































dogfood
 commented on  JENKINS-21303


NPE in hudson.model.Job.getEnvironment















Integrated in  jenkins_main_trunk #3156
 FIX JENKINS-21303 There is a NPE here that can and does happen for real when an aggresive slave retention strategy interacts with post build triggers that want to do token macro expansion (Revision e998c2a670fbb7f9e32af37218e7076de696455e)

 Result = SUCCESS
Stephen Connolly : e998c2a670fbb7f9e32af37218e7076de696455e
Files : 

	core/src/main/java/hudson/model/Job.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/groups/opt_out.

[JIRA] [htmlpublisher] (JENKINS-19403) Unable to Open Report Created by HTML Publisher Plugin

2014-01-09 Thread john.arme...@sage.com (JIRA)















































John Armenia
 reopened  JENKINS-19403


Unable to Open Report Created by HTML Publisher Plugin
















This is happening again on Jenkins 1.544 Publisher version 1.3.





Change By:


John Armenia
(09/Jan/14 2:06 PM)




Resolution:


Duplicate





Status:


Resolved
Reopened



























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







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

[JIRA] [integrity-plugin] (JENKINS-21300) PTC integrity plugin: after update to version 1.20 the error Null value not allowed as an environment variable: MKSSI_HOST is thrown

2014-01-09 Thread cletusdso...@hotmail.com (JIRA)















































Cletus DSouza
 commented on  JENKINS-21300


PTC integrity plugin: after update to version 1.20 the error Null value not allowed as an environment variable: MKSSI_HOST is thrown















Unfortunately, due to a new parameter added in v1.19, you are required to enter a 'Configuration Name' for each Job.  This will allow you to use the Integrity plugin with the Multiple SCMs 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/groups/opt_out.

[JIRA] [htmlpublisher] (JENKINS-19403) Unable to Open Report Created by HTML Publisher Plugin

2014-01-09 Thread john.arme...@sage.com (JIRA)















































John Armenia
 updated  JENKINS-19403


Unable to Open Report Created by HTML Publisher Plugin
















You can see the publisher is correctly copying the reports.





Change By:


John Armenia
(09/Jan/14 2:12 PM)




Attachment:


screenshot-1.jpg



























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







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

[JIRA] [htmlpublisher] (JENKINS-19403) Unable to Open Report Created by HTML Publisher Plugin

2014-01-09 Thread john.arme...@sage.com (JIRA)















































John Armenia
 updated  JENKINS-19403


Unable to Open Report Created by HTML Publisher Plugin
















Here is the error trying to access the report.





Change By:


John Armenia
(09/Jan/14 2:13 PM)




Attachment:


screenshot-2.jpg



























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







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

[JIRA] [config-file-provider] (JENKINS-16706) Configure provided settings.xml at the Maven plugin level, not at the Maven job level

2014-01-09 Thread florian.zscho...@cycos.com (JIRA)















































Florian Zschocke
 commented on  JENKINS-16706


Configure provided settings.xml at the Maven plugin level, not at the Maven job level















I am trying this with 1.539 and can not get it to work at all. Not with a path to a file nor with a provided config file.



























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







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

[JIRA] [config-file-provider] (JENKINS-16706) Configure provided settings.xml at the Maven plugin level, not at the Maven job level

2014-01-09 Thread florian.zscho...@cycos.com (JIRA)













































 
Florian Zschocke
 edited a comment on  JENKINS-16706


Configure provided settings.xml at the Maven plugin level, not at the Maven job level
















I am trying this with 1.539 and can not get it to work at all. Not with a path to a file nor with a provided config file.
Config File Provider plugin version 2.7.1
Platform is Linux.



























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







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

[JIRA] [config-file-provider] (JENKINS-16706) Configure provided settings.xml at the Maven plugin level, not at the Maven job level

2014-01-09 Thread florian.zscho...@cycos.com (JIRA)













































 
Florian Zschocke
 edited a comment on  JENKINS-16706


Configure provided settings.xml at the Maven plugin level, not at the Maven job level
















I am trying this with 1.539 and can not get it to work at all. Not with a path to a file nor with a provided config file.
Config File Provider plugin version 2.7.1
Platform is Windows.



























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







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

[JIRA] [git] (JENKINS-21277) Job cannot be built with parameters

2014-01-09 Thread tom...@martos.bme.hu (JIRA)
















































Tamas Papp
 resolved  JENKINS-21277 as Wont Fix


Job cannot be built with parameters
















The issue can be applied only for existing jobs, therefore hard to reproduce.
There is an existing workaround available.





Change By:


Tamas Papp
(09/Jan/14 2:41 PM)




Status:


Open
Resolved





Resolution:


WontFix



























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







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

[JIRA] [git] (JENKINS-21277) Job cannot be built with parameters

2014-01-09 Thread tom...@martos.bme.hu (JIRA)















































Tamas Papp
 commented on  JENKINS-21277


Job cannot be built with parameters















hi Mark,

I also cannot reproduce it.
As I wrote it's true only for existing jobs.
I think it's cannot be fixed this way..



























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







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

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

2014-01-09 Thread jb-jenk...@bauer-kirch.de (JIRA)















































Jan Busch
 created  JENKINS-21306


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















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


09/Jan/14 2:46 PM



Description:


Option "Execute concurrent builds if necessary" is not selected.
With every build another directory with suffix "@X" and incremented "X" is created. There is no concurrent build running. With former versions (running 1.539 now) this does not happen. I.e. no suffix is appended.
This bothers me because the "@X"-directories will become more and more and will never be deleted.




Environment:


Debian squeeze




Project:


Jenkins



Priority:


Major



Reporter:


Jan Busch

























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







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

[JIRA] [jiratestresultreporter] (JENKINS-21307) Hard coded rest API version should be parameterized

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















































george dma
 created  JENKINS-21307


Hard coded rest API version should be parameterized















Issue Type:


Bug



Assignee:


Unassigned


Components:


jiratestresultreporter



Created:


09/Jan/14 2:47 PM



Description:


When using this plugin on an old version of JIRA like v4.4.4 the rest API url is  http://localhost:8080/rest/api/2.0.alpha1/issue  and not /rest/api/2/issue/.

In the code I saw on line 151
String url = "" + "rest/api/2/issue/";

Please make it so that this string is parametrized so that we can define it ourselves due to different JIRA versions.




Project:


Jenkins



Labels:


plugin
jira




Priority:


Major



Reporter:


george dma

























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







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

[JIRA] [core] (JENKINS-19550) Jenkins doesn''t show update for 1.509.3

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















































Nick Jones
 commented on  JENKINS-19550


Jenkins doesnt show update for 1.509.3















I determined the issue, at least in my case: the "Update Site" URL for LTS was set to http://updates.jenkins-ci.org/stable/update-center.json; however, our Jenkins installation uses https, and Chrome was blocking the update check. Changing the Update Site URL to use https solved the problem, and Jenkins and plugin updates started appearing again. This presumably occurred due to a Chrome update at some point.



























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







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

[JIRA] [core] (JENKINS-18224) TransientActionFactory

SCM/JIRA link daemon
commented on JENKINS-18224

TransientActionFactory

Code changed in jenkins
User: Jesse Glick
Path:
src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java
src/main/java/com/cloudbees/hudson/plugins/folder/TransientFolderActionFactory.java
src/main/java/com/cloudbees/hudson/plugins/folder/relocate/RelocateAction.java
src/main/resources/com/cloudbees/hudson/plugins/folder/Folder/configure.jelly
src/test/java/com/cloudbees/hudson/plugins/folder/FolderTest.java
http://jenkins-ci.org/commit/cloudbees-folder-plugin/c006194cec064331b273050177d67c883b6e6d27
Log:
Taking advantage of APIs available with newer Jenkins cores.
· JENKINS-18224 TransientActionFactory simplifies adding the Move action and makes it available more broadly.
Can therefore deprecate TransientFolderActionFactory.
· Expanding the search index to look for jobs in subfolders (matches #848 in Jenkins root).
· testReloadJenkinsAndFindBuildInProgress can now pass unconditionally.
· ListView.setIncludeRegex avoids the need for reflection.
· f:bottomButtonBar convenient in Jelly.
As yet unimplemented:
· AutoCompletionCandidates.ofJobNames could be used, though it does not filter by permitted children.
(Nor, generally, should it, since this method is typically used for existing items, which might violate this restriction.)
Might be feasible to call ofJobNames and then filter the result; or perhaps this method should accept an Item filter.

[JIRA] [email-ext] (JENKINS-21308) java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport

2014-01-09 Thread aherit...@apache.org (JIRA)















































Arnaud Héritier
 created  JENKINS-21308


java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport















Issue Type:


Bug



Assignee:


Alex Earl



Components:


email-ext



Created:


09/Jan/14 2:58 PM



Description:


I tried to upgrade the email-ext plugin from 2.36 to 2.37 and after that I started to have exceptions in logs (https://gist.github.com/aheritier/8332104) and no tests failures results in emails
It seems to be similar to JENKINS-20355 and JENKINS-16990
I downgraded to 2.36 and it works
Here is my list of installed plugins :


Name  Version   Enabled   Pinned   
android-emulator		2.10	false	false
ansicolor			0.3.1	true	false
ant1.2	true	true
appaloosa-plugin		1.4.0	true	false
async-http-client		1.7.8	true	false
beer1.2	false	false
build-pipeline-plugin		1.4.2	true	false
build-timeout			1.12.2	true	false
buildresult-trigger		0.16	true	false
buildtriggerbadge		1.1	true	false
claim2.3	true	false
clang-scanbuild-plugin		1.4	true	false
compact-columns			1.10	true	false
conditional-buildstep		1.3.3	true	false
config-file-provider		2.7.1	true	false
configurationslicing		1.38.3	true	false
console-column-plugin		1.5	true	false
credentials			1.9.4	true	true
crowd21.6	true	false
custom-job-icon			0.2	false	false
cvs2.11	false	true
dashboard-view			2.9.2	true	false
depgraph-view			0.11	false	false
disk-usage			0.23	true	false
email-ext			2.36	true	false
embeddable-build-status		1.4	true	false
envinject			1.89	true	false
extended-read-permission	1.0	true	false
external-monitor-job		1.2	false	true
fstrigger			0.38	true	false
git1.5.0	true	false
git-client			1.6.0	true	false
git-notes			0.0.4	false	false
git-server			1.2	true	false
github1.8	true	false
github-api			1.44	true	false
global-build-stats		1.3	true	false
googlecode			1.7	true	false
gradle1.23	true	false
greenballs			1.13	true	false
ivytrigger			0.32	true	false
javadoc1.1	true	true
jenkins-multijob-plugin		1.10	true	false
jira1.38	true	false
jquery1.7.2-1	true	false
jquery-ui			1.0.2	true	false
keyboard-shortcuts-plugin	1.2	true	false
ldap1.7	false	true
m2release			0.13.0	true	false
mailer1.8	true	true
maven-deployment-linker		1.5.1	true	false
maven-plugin			2.0.1	true	true
maven-repo-cleaner		1.2	true	false
multiple-scms			0.3	true	false
nested-view			1.14	true	false
nodelabelparameter		1.4	true	false
pam-auth			1.1	false	true
parameterized-trigger		2.22	true	false
play-autotest-plugin		0.0.12	true	false
port-allocator			1.8	true	false
postbuild-task			1.8	true	false
PrioritySorter			2.5	true	false
project-stats-plugin		0.4	true	false
promoted-builds			2.14	true	false
radiatorviewplugin		1.17	true	false
rebuild1.20	true	false
ruby1.2	true	false
ruby-runtime			0.12	false	false
run-condition			1.0	true	false
scm-api0.2	true	false
scm-sync-configuration		0.0.7.3	true	false
scriptler			2.6.1	true	false
scripttrigger			0.31	true	false
sonar2.1	true	false
ssh-agent			1.4.1	true	false
ssh-credentials			1.6	true	true
ssh-slaves			1.5	true	true
subversion			1.54	true	true
tmpcleaner			1.1	true	false
token-macro			1.9	true	false
translation			1.11	true	true
urltrigger			0.37	true	false
ws-cleanup			0.19	true	false
xcode-plugin			1.4.2	true	false
xtrigger			0.54	true	false





Environment:


Jenkins ver. 1.532.1




Project:


Jenkins



Priority:


Major



Reporter:


Arnaud Héritier

























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:

[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect

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















































John Dyer
 created  JENKINS-21309


Git plugins changes URL for Bitbucket is incorrect















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git, git-client



Created:


09/Jan/14 3:12 PM



Description:


When I have the repository browser for a project set to auto, or bitbucketweb, I get a 404 when going to any of the changes in a build.

The problem is the URL is going to 


http://bitbucket.org/projectname/commit/1234


when it should be going to 


http://bitbucket.org/projectname/commits/1234


Notice commit vs commits

I thought this worked at some point, but I may be making that up. 




Environment:


Gitplugin 1.5.0

Jenkins 1.544




Project:


Jenkins



Priority:


Major



Reporter:


John Dyer

























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







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

[JIRA] [core] (JENKINS-18224) TransientActionFactory

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















































dogfood
 commented on  JENKINS-18224


TransientActionFactory















Integrated in  jenkins_main_trunk #3157
 FIXED JENKINS-18224 Introduced TransientActionFactory. (Revision f1a751f79dfbb975e4c436fd0967323e1ae7b8c6)
JENKINS-18224 Introduced Actionable.replaceAction, allowing getActions() to be deprecated except for subclasses. (Revision a22e9feaaef30b89621ae9ca3f33f862ae99f4c7)
JENKINS-18224 Preparing to merge #1059. (Revision 6eb191964b415d7f0a025847d5444db922d6fe49)

 Result = SUCCESS
Jesse Glick : f1a751f79dfbb975e4c436fd0967323e1ae7b8c6
Files : 

	core/src/main/java/hudson/model/Job.java
	core/src/main/resources/hudson/matrix/MatrixProject/index.jelly
	core/src/main/java/hudson/model/queue/WorkUnitContext.java
	core/src/main/resources/lib/hudson/actions.jelly
	core/src/main/java/hudson/model/Computer.java
	core/src/main/java/hudson/matrix/DefaultMatrixExecutionStrategyImpl.java
	core/src/main/java/hudson/model/AbstractProject.java
	core/src/main/java/hudson/model/TransientComputerActionFactory.java
	core/src/main/java/jenkins/model/TransientActionFactory.java
	core/src/main/resources/lib/hudson/project/projectActionFloatingBox.jelly
	core/src/main/java/hudson/model/Run.java
	core/src/main/resources/hudson/model/AbstractBuild/index.jelly
	core/src/main/java/hudson/model/AbstractBuild.java
	core/src/main/java/hudson/model/Actionable.java
	core/src/main/java/hudson/model/Queue.java
	core/src/main/java/hudson/model/TransientBuildActionFactory.java
	core/src/main/java/hudson/model/TransientProjectActionFactory.java
	test/src/test/java/jenkins/model/TransientActionFactoryTest.java
	core/src/main/java/jenkins/model/ModelObjectWithContextMenu.java
	core/src/main/resources/hudson/model/AbstractProject/main.jelly



Jesse Glick : a22e9feaaef30b89621ae9ca3f33f862ae99f4c7
Files : 

	core/src/main/java/hudson/model/CauseAction.java
	core/src/main/java/hudson/model/Computer.java
	core/src/main/java/hudson/model/labels/LabelAtom.java
	core/src/main/java/hudson/model/Actionable.java
	core/src/main/java/hudson/cli/SetBuildParameterCommand.java
	core/src/main/java/hudson/triggers/SCMTrigger.java
	test/src/test/java/hudson/model/UserTest.java
	core/src/main/java/hudson/tasks/Fingerprinter.java
	core/src/main/java/hudson/model/AbstractProject.java
	core/src/main/java/hudson/model/AbstractBuild.java



Jesse Glick : 6eb191964b415d7f0a025847d5444db922d6fe49
Files : 

	core/src/main/java/jenkins/model/TransientActionFactory.java
	changelog.html
	core/src/main/java/hudson/model/Actionable.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/groups/opt_out.

[JIRA] [email-ext] (JENKINS-21308) java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport

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















































Alex Earl
 commented on  JENKINS-21308


java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport















My guess is that this has something to do with the upgrade from 1.509.4 to 1.532.1 for the parent pom.xml. I'm not sure why, but there weren't any other changes that might have caused something like this.



























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







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

[JIRA] [core] (JENKINS-18224) TransientActionFactory















































SCM/JIRA link daemon
 commented on  JENKINS-18224


TransientActionFactory















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/Actionable.java
 core/src/main/java/jenkins/model/TransientActionFactory.java
http://jenkins-ci.org/commit/jenkins/c21b209ba383e5e4f6522ec866d03fb9ca5745a4
Log:
  JENKINS-18224 Relaxing type parameter restriction on TransientActionFactory since useful mixin interfaces like Item do not extend Actionable.





























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







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

[JIRA] [email-ext] (JENKINS-21308) java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport

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















































Alex Earl
 commented on  JENKINS-21308


java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport















Also, it looks like there is a maven-integration-plugin that is required for that stuff to work (from JENKINS-20355) can you try that?



























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







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

[JIRA] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend

2014-01-09 Thread m...@objectxp.com (JIRA)















































Michel Marti
 updated  JENKINS-9031


Performance plugin lock out Jenkins while running Performance Trend
















I have attached a patch which implements a caching mechanism for JMeter reports. Processed reports get serialized to disk for later reuse and are also added to a memory-backed cache (holding max 100 entries) for even faster access.





Change By:


Michel Marti
(09/Jan/14 3:33 PM)




Attachment:


0001-Cache-preprocessed-JMeter-Reports-JENKINS-9031.patch



























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







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

[JIRA] [configurationslicing] (JENKINS-11774) Mass-configure triggers in Email-Ext-plugin

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















































Idan Bidani
 commented on  JENKINS-11774


Mass-configure triggers in Email-Ext-plugin















I've applied the patch and compiled successfully on the branch "with_triggers"
you may find only the compilation fix without the error under branch "master"
https://github.com/iplaman/configurationslicing-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/groups/opt_out.

[JIRA] [prioritysorter] (JENKINS-21310) Queue broken by CCE from PriorityConfiguration.getPriorityInternal















































Jesse Glick
 created  JENKINS-21310


Queue broken by CCE from PriorityConfiguration.getPriorityInternal















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


prioritysorter



Created:


09/Jan/14 3:50 PM



Description:


A user of cloudbees-folders-plus (from Jenkins Enterprise) reports that moving a job from folder to Jenkins root is broken with


java.lang.ClassCastException: com.cloudbees.hudson.plugins.folder.relocate.RelocateTask cannot be cast to hudson.model.Job
	at jenkins.advancedqueue.PriorityConfiguration.getPriorityInternal(PriorityConfiguration.java:207)
	at jenkins.advancedqueue.PriorityConfiguration.getPriority(PriorityConfiguration.java:199)
	at jenkins.advancedqueue.sorter.AdvancedQueueSorter.onNewItem(AdvancedQueueSorter.java:111)
	at jenkins.advancedqueue.sorter.AdvancedQueueSorter.getCalculatedWeight(AdvancedQueueSorter.java:103)
	at jenkins.advancedqueue.sorter.AdvancedQueueSorter.access$000(AdvancedQueueSorter.java:47)
	at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:78)
	at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:76)
	at java.util.TimSort.countRunAndMakeAscending(Unknown Source)
	at java.util.TimSort.sort(Unknown Source)
	at java.util.TimSort.sort(Unknown Source)
	at java.util.Arrays.sort(Unknown Source)
	at java.util.Collections.sort(Unknown Source)
	at jenkins.advancedqueue.sorter.AdvancedQueueSorter.sortBuildableItems(AdvancedQueueSorter.java:76)
	at hudson.model.Queue.maintain(Queue.java:1092)
	at hudson.model.Queue$MaintainTask.doRun(Queue.java:2084)
	at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
	at java.util.TimerThread.mainLoop(Unknown Source)
	at java.util.TimerThread.run(Unknown Source)


Probably other special queue tasks would also be broken by this plugin, which assumes without checking that every Task is a Job.




Environment:


2.4, 1.532.1




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/groups/opt_out.

[JIRA] [prioritysorter] (JENKINS-21310) Queue broken by CCE from PriorityConfiguration.getPriorityInternal















































Jesse Glick
 started work on  JENKINS-21310


Queue broken by CCE from PriorityConfiguration.getPriorityInternal
















Change By:


Jesse Glick
(09/Jan/14 3:50 PM)




Status:


Open
InProgress



























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







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

[JIRA] [http_request] (JENKINS-21311) Queue item cancellation via REST api works but returns a 404

2014-01-09 Thread barthelemy.von.hal...@cern.ch (JIRA)















































Barthélémy von Haller
 created  JENKINS-21311


Queue item cancellation via REST api works but returns a 404















Issue Type:


Bug



Assignee:


Unassigned


Components:


http_request



Created:


09/Jan/14 3:52 PM



Description:


When I call http://Jenkins_URL/queue/cancelItem?id=queueItem it does cancel the item but it returns a 404. It must return a 200 instead.




Environment:


jenkins 1.546




Project:


Jenkins



Priority:


Major



Reporter:


Barthélémy von Haller

























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







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

[JIRA] [prioritysorter] (JENKINS-21310) Queue broken by CCE from PriorityConfiguration.getPriorityInternal















































Jesse Glick
 updated  JENKINS-21310


Queue broken by CCE from PriorityConfiguration.getPriorityInternal
















Change By:


Jesse Glick
(09/Jan/14 3:53 PM)




URL:


https://github.com/jenkinsci/priority-sorter-plugin/pull/14



























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







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

[JIRA] [testflight] (JENKINS-20503) Appending changlog says no changes if a build failed

2014-01-09 Thread ricardo_ruiz_lo...@yahoo.es (JIRA)















































Ricardo Ruiz
 commented on  JENKINS-20503


Appending changlog says no changes if a build failed















Hello!
I have exactly the same problem with the current version, 1.3.9
I tried to write this in the notes box (as I have in the email):
${CHANGES_SINCE_LAST_SUCCESS, reverse="true", showPaths="true"}
But it didn't work.
Any idea?



























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







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

[JIRA] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend

2014-01-09 Thread m...@objectxp.com (JIRA)















































Michel Marti
 updated  JENKINS-9031


Performance plugin lock out Jenkins while running Performance Trend
















I just attached an improved version of the patch where the caching code is located in PerformanceReportParser. This allows reuse of the caching code in other report parser implementations.





Change By:


Michel Marti
(09/Jan/14 4:12 PM)




Attachment:


0001-Cache-preprocessed-JMeter-Reports-JENKINS-9031.patch



























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







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

[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start

2014-01-09 Thread deevan...@live.com (JIRA)















































Devsh sharma
 created  JENKINS-21312


Vsphere plugin keeps reseting the slave when slave is configured for on demand start















Issue Type:


Bug



Assignee:


Unassigned


Components:


vsphere-cloud



Created:


09/Jan/14 4:33 PM



Description:



i am facing this problem with vsphere cloud plugin , where i have configured my slaves (vsphere images) to be turned on on demand, the problem is when i submit the job it goes in waiting queue , after a while Jenkins turn on the corresponding slave , now while the process of turning on the slave is in progress a poll operation is performed by jenkins and restarts the slave , so this operation keeps on going endlessly.

log-Jan 09, 2014 7:30:45 PM INFO hudson.slaves.RetentionStrategy$Demand check
Launching computer Vistax64_sp1 as it has been in demand for 10 min

Jan 09, 2014 7:30:45 PM INFO hudson.slaves.RetentionStrategy$Demand check
Launching computer Vistax64_sp2 as it has been in demand for 10 min

Jan 09, 2014 7:30:45 PM INFO org.jenkinsci.plugins.vSphereCloud InternalLog
Vistax86_sp2 Starting Virtual Machine...

Jan 09, 2014 7:30:45 PM INFO org.jenkinsci.plugins.vSphereCloud InternalLog
Vistax64_sp1 Starting Virtual Machine...

http://javadoc.jenkins-ci.org/hudson/slaves/CloudSlaveRetentionStrategy.html

Retention strategy polls after every two minutes and resets the slave , is there any way to increase this polling period ?


Jenkins Version - 1.544

VSphere Plugin - 1.1.2





Project:


Jenkins



Priority:


Critical



Reporter:


Devsh sharma

























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







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

[JIRA] [core] (JENKINS-18224) TransientActionFactory

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















































dogfood
 commented on  JENKINS-18224


TransientActionFactory















Integrated in  jenkins_main_trunk #3158
 JENKINS-18224 Relaxing type parameter restriction on TransientActionFactory since useful mixin interfaces like Item do not extend Actionable. (Revision c21b209ba383e5e4f6522ec866d03fb9ca5745a4)

 Result = SUCCESS
Jesse Glick : c21b209ba383e5e4f6522ec866d03fb9ca5745a4
Files : 

	core/src/main/java/jenkins/model/TransientActionFactory.java
	core/src/main/java/hudson/model/Actionable.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/groups/opt_out.

[JIRA] [git] (JENKINS-18303) Cannot do checkout of a git repository in BitBucket in Jenkins

2014-01-09 Thread j...@stimulant.io (JIRA)















































Josh Santangelo
 commented on  JENKINS-18303


Cannot do checkout of a git repository in BitBucket in Jenkins















I'm having this problem with a different host. The frustrating part is that sometimes it hangs and sometimes it doesn't  so everything is configured correctly, but it just randomly fails.



























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







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

[JIRA] [prioritysorter] (JENKINS-21313) Anonymous users can configure and delete PrioritySorter JobGroups

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















































mwebber
 created  JENKINS-21313


Anonymous users can configure and delete PrioritySorter JobGroups















Issue Type:


Bug



Assignee:


bklarson



Components:


prioritysorter



Created:


09/Jan/14 4:50 PM



Description:


I am running:
Jenkins 1.545
CAS plugin 1.1.1 for authentication
Role Strategy Plugin 2.1.0 for authorization
Priority Sorter plugin 2.5
(these are the latest available at the time of writing)

The only security granted to anonymous users is "overall - read" and "job - read". However, if an anonymous user views Jenkins, the link to the management function "Job Priorities" remains visible in the top left hand corner of the Jenkins main page, and can be clicked. You can then create / edit / delete job priority groups.

The function should only be available to administrations. I suspect that the Priority Sorter plugin simply does not check for authorisation.




Project:


Jenkins



Priority:


Major



Reporter:


mwebber

























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







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

[JIRA] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend

2014-01-09 Thread man...@apache.org (JIRA)















































Manuel Carrasco
 commented on  JENKINS-9031


Performance plugin lock out Jenkins while running Performance Trend















Could you please send a pull-request in github, so as I can merge your contribution easily.

Thank you.



























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







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

[JIRA] [prioritysorter] (JENKINS-21313) Anonymous users can configure and delete PrioritySorter JobGroups

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















































mwebber
 commented on  JENKINS-21313


Anonymous users can configure and delete PrioritySorter JobGroups















I only just noticed an option on the main Jenkins configuration page "Only Admins can edit Job Priorities", which has associated help text "Check if only Administrators should be allowed to view and edit the Job Priorities".

Checking this option fixes the problem. However, the option description does not make it clear that leaving this unchecked (the default value!) means that anonymous users can change priority groups, as well as the priority on individual jobs.

It seems to me the default value is wrong for Jenkins installations where securtity is otherwise enabled.



























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







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

[JIRA] [core] (JENKINS-19720) Jenkins Loses Build History

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















































Gavin Gray
 commented on  JENKINS-19720


Jenkins Loses Build History















Just saw this on 1.532.1.



























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







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

[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start

2014-01-09 Thread jswa...@alohaoi.com (JIRA)
















































Jason Swager
 assigned  JENKINS-21312 to Jason Swager



Vsphere plugin keeps reseting the slave when slave is configured for on demand start
















Change By:


Jason Swager
(09/Jan/14 5:22 PM)




Assignee:


JasonSwager



























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







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

[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification















































Jesse Glick
 commented on  JENKINS-16332


Leading and trailing underscores are added to commiters email address, unable to send build notification















@cowwoc so something called 
User.get("First Last _first.last@gmail.com_")
 which is OK, but there was already a User which had that not only as an id but also as a fullName, which is wrong. The question is how and when that User got created, which this log snippet does not indicate. To learn that, we would need an (earlier) log message starting with 
[JENKINS-16332] Suspicious fullName being stored: First Last _first.last@gmail.com_
 which includes a stack trace possibly indicating the culprit.



























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







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

[JIRA] [prioritysorter] (JENKINS-21314) Stack trace displayed on web page when attempting to configure PrioritySorter plugin

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















































mwebber
 created  JENKINS-21314


Stack trace displayed on web page when attempting to configure PrioritySorter plugin















Issue Type:


Bug



Assignee:


bklarson



Components:


prioritysorter



Created:


09/Jan/14 5:20 PM



Description:


I am running jenkins 1.545 with PrioritySorter plugin 2.5 (not in legacy mode).

Previously, I did not have any priority groups defined. I defined some, and saved the result. I then clicked on "Job Priorities" from the main page in order to add some more groups, but instead I got a stack trace, as below. This happens every time I click "Job Priorities".


A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.
Stack trace

javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/exports/jenkins_home/plugins/PrioritySorter/WEB-INF/lib/classes.jar!/jenkins/advancedqueue/PriorityConfiguration/index.jelly:67:60: st:include The page attribute is not specified
	at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)
	at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	at

[JIRA] [backup] (JENKINS-21076) Workspace zip from windows host wrong

2014-01-09 Thread nicholas.yo...@microfocus.com (JIRA)















































nyoung02
 commented on  JENKINS-21076


Workspace zip from windows host wrong















Yes, it's very annoying!

We've done a workaround for this by zipping up the files we need as part of the job configuration and just archiving those zip files.



























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







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

[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start

2014-01-09 Thread jswa...@alohaoi.com (JIRA)















































Jason Swager
 commented on  JENKINS-21312


Vsphere plugin keeps reseting the slave when slave is configured for on demand start















According to this log, Jenkins is trying to launch TWO different slaves: Vistax86_sp2 and Vistax64_sp1.  The log shows that Jenkins was starting those two slaves.  Are those slaves the SAME VM (ie, different snapshots, or perhaps just misconfiguration) or DIFFERENT VMs?

From this log, I don't see any attempt to reset the same slave.



























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







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

[JIRA] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend

2014-01-09 Thread m...@objectxp.com (JIRA)















































Michel Marti
 commented on  JENKINS-9031


Performance plugin lock out Jenkins while running Performance Trend















Could you please send a pull-request in github, so as I can merge your contribution easily.
I'd rather not. What's so difficult in saving the attached patch and then doing a 'git am -3 ...'?



























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







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

[JIRA] [core] (JENKINS-18694) Builds forgotten after containing folder renamed















































Jesse Glick
 started work on  JENKINS-18694


Builds forgotten after containing folder renamed
















Change By:


Jesse Glick
(09/Jan/14 5:33 PM)




Status:


Open
InProgress



























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







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

[JIRA] [core] (JENKINS-18694) Builds forgotten after containing folder renamed















































Jesse Glick
 updated  JENKINS-18694


Builds forgotten after containing folder renamed
















Change By:


Jesse Glick
(09/Jan/14 5:32 PM)




Component/s:


cloudbees-folder



























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







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

[JIRA] [core] (JENKINS-21315) NPE when collection JUnit test results















































Vincent Massol
 created  JENKINS-21315


NPE when collection JUnit test results















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


09/Jan/14 5:38 PM



Description:


I was on 1.544, I upgraded to 1.546 found some blocker (see JENKINS-21250) and rolled-back to 1.546 and then it started failing (I don't remember it failing before).

The error I get now is:


...
[INFO] 
[INFO] Building XWiki Commons - XML 5.4-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ xwiki-commons-xml ---
[INFO] Deleting /home/hudsonagent/hudson_root/workspace/xwiki-commons/xwiki-commons-core/xwiki-commons-xml/target
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-plugins) @ xwiki-commons-xml ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-jcl-log4j-isolation) @ xwiki-commons-xml ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-commons-lang3) @ xwiki-commons-xml ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-upper-bounds) @ xwiki-commons-xml ---
[INFO] Skipping Rule Enforcement.
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-no-legacy-dependencies) @ xwiki-commons-xml ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-platform-rendering-isolation) @ xwiki-commons-xml ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (check-dependency-version) @ xwiki-commons-xml ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.4:process (xwiki-license-resources) @ xwiki-commons-xml ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ xwiki-commons-xml ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 6 resources
[INFO] Copying 2 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ xwiki-commons-xml ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 25 source files to /home/hudsonagent/hudson_root/workspace/xwiki-commons/xwiki-commons-core/xwiki-commons-xml/target/classes
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:manifest (bundle-manifest) @ xwiki-commons-xml ---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ xwiki-commons-xml ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/hudsonagent/hudson_root/workspace/xwiki-commons/xwiki-commons-core/xwiki-commons-xml/src/test/resources
[INFO] Copying 2 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ xwiki-commons-xml ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 4 source files to /home/hudsonagent/hudson_root/workspace/xwiki-commons/xwiki-commons-core/xwiki-commons-xml/target/test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.16:test (default-test) @ xwiki-commons-xml ---
[INFO] Surefire report directory: /home/hudsonagent/hudson_root/workspace/xwiki-commons/xwiki-commons-core/xwiki-commons-xml/target/surefire-reports

---
 T E S T S
---
Running org.xwiki.xml.XMLUtilsTest
Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.246 sec - in org.xwiki.xml.XMLUtilsTest
Running org.xwiki.xml.html.HTMLUtilsTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.102 sec - in org.xwiki.xml.html.HTMLUtilsTest
Running org.xwiki.xml.internal.html.DefaultHTMLCleanerTest
Tests run: 14, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.252 sec - in org.xwiki.xml.internal.html.DefaultHTMLCleanerTest

Results :

Tests run: 37, Failures: 0, Errors: 0, Skipped: 1

[JENKINS] Recording test results
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] XWiki Commons - Parent POM  SUCCESS

[JIRA] [core] (JENKINS-18694) Builds forgotten after containing folder renamed















































Jesse Glick
 updated  JENKINS-18694


Builds forgotten after containing folder renamed
















Not an lts-candidate since fix requires APIs not expected to be backported to the current LTS line.





Change By:


Jesse Glick
(09/Jan/14 5:38 PM)




Labels:


folderslazy-loading
lts-candidate



























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







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

[JIRA] [junit] (JENKINS-18672) NPE when reading JUnit reports















































Vincent Massol
 updated  JENKINS-18672


NPE when reading JUnit reports
















Change By:


Vincent Massol
(09/Jan/14 5:41 PM)




Affects Version/s:


current



























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







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

[JIRA] [junit] (JENKINS-18672) NPE when reading JUnit reports















































Vincent Massol
 updated  JENKINS-18672


NPE when reading JUnit reports
















Change By:


Vincent Massol
(09/Jan/14 5:40 PM)




Affects Version/s:


current



























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







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

[JIRA] [core] (JENKINS-21315) NPE when collection JUnit test results















































Vincent Massol
 updated  JENKINS-21315


NPE when collection JUnit test results
















Change By:


Vincent Massol
(09/Jan/14 5:41 PM)




Affects Version/s:


current



























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







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

[JIRA] [email-ext] (JENKINS-21308) java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport

2014-01-09 Thread aherit...@apache.org (JIRA)















































Arnaud Héritier
 commented on  JENKINS-21308


java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport















I already have the Maven Integration Plugin in version 2.0.1



























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







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

[JIRA] [prioritysorter] (JENKINS-21316) PrioritySorter wrongly assumes Queue.Task is Job

2014-01-09 Thread e...@switchbeat.com (JIRA)















































Magnus Sandberg
 created  JENKINS-21316


PrioritySorter wrongly assumes Queue.Task is Job















Issue Type:


Bug



Assignee:


bklarson



Components:


prioritysorter



Created:


09/Jan/14 6:02 PM



Description:


PrioritySorter wrongly assumes Queue.Task is Job in various places. 




Project:


Jenkins



Priority:


Major



Reporter:


Magnus Sandberg

























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







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

[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification

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















































cowwoc
 commented on  JENKINS-16332


Leading and trailing underscores are added to commiters email address, unable to send build notification















I didn't see such a log entry but I will keep my eye open if this happens again.

Mail-Ext just committed an interesting bugfix: https://issues.jenkins-ci.org/browse/JENKINS-20215

Do you think this could have been at fault?



























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







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

[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification

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













































 
cowwoc
 edited a comment on  JENKINS-16332


Leading and trailing underscores are added to commiters email address, unable to send build notification
















I didn't see such a log entry but I will keep my eye open if this happens again.

The EMail-ext plugin just fixed an interesting bug: https://issues.jenkins-ci.org/browse/JENKINS-20215

Do you think this could have been at fault?



























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







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

[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job















































SCM/JIRA link daemon
 commented on  JENKINS-18678


Builds disappear some time after renaming job















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/AbstractProject.java
 test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
http://jenkins-ci.org/commit/jenkins/cb623640ccd820ad0540efc3b50cc596626e43a2
Log:
  FIXED JENKINS-18694 Generalizing fix of JENKINS-18678 to include also rename of parent folders, taking advantage of JENKINS-18028 API.





























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







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

[JIRA] [core] (JENKINS-18694) Builds forgotten after containing folder renamed















































SCM/JIRA link daemon
 commented on  JENKINS-18694


Builds forgotten after containing folder renamed















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/AbstractProject.java
 test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
http://jenkins-ci.org/commit/jenkins/cb623640ccd820ad0540efc3b50cc596626e43a2
Log:
  FIXED JENKINS-18694 Generalizing fix of JENKINS-18678 to include also rename of parent folders, taking advantage of JENKINS-18028 API.





























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







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

[JIRA] [cloudbees-folder] (JENKINS-18028) ItemListener.onMoved















































SCM/JIRA link daemon
 commented on  JENKINS-18028


ItemListener.onMoved















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/AbstractProject.java
 test/src/test/groovy/hudson/model/AbstractProjectTest.groovy
http://jenkins-ci.org/commit/jenkins/cb623640ccd820ad0540efc3b50cc596626e43a2
Log:
  FIXED JENKINS-18694 Generalizing fix of JENKINS-18678 to include also rename of parent folders, taking advantage of JENKINS-18028 API.





























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







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

[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification