date:20140220















































Kishore Redlapalli
 commented on  JENKINS-20913


[jar caching] - winp.x64.dll access conflicts















We are seeing this on win8/8.1 slaves once in a week!Unable to render embedded object: File (..can this be fixed please) not found.!
we are on Jenkins LTS 1.532.1 running on CentOs6.5



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-20913) [jar caching] - winp.x64.dll access conflicts













































  
Kishore Redlapalli
 edited a comment on  JENKINS-20913


[jar caching] - winp.x64.dll access conflicts
















We are seeing this on win8/8.1 slaves once in a week!Unable to render embedded object: File (..can this be fixed please) not found.!
slave.jar crashes with the above error
we are on Jenkins LTS 1.532.1 running on CentOs6.5



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-20913) [jar caching] - winp.x64.dll access conflicts













































  
Kishore Redlapalli
 edited a comment on  JENKINS-20913


[jar caching] - winp.x64.dll access conflicts
















We are seeing this on win8/8.1 slaves once in a week!Unable to render embedded object: File (..can this be fixed please) not found.!
slave.jar crashes with the above error
we are on Jenkins LTS 1.532.1 running on CentOs6.5
also, at the end of each job, the above issue occurs everytime!!



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21797) Subversion-Tagging Plugin can't create tag because of missing credentials

2014-02-20 Thread e598...@drdrb.com (JIRA)















































Branz Frandwein
 commented on  JENKINS-21797


Subversion-Tagging Plugin can't create tag because of missing credentials















@Joe Shomphe
To which version (Jenkins, plugins) did you roll back to fix it? 



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-20913) [jar caching] - winp.x64.dll access conflicts

2014-02-20 Thread alex.toml...@digital.cabinet-office.gov.uk (JIRA)















































Oleg Nenashev
 commented on  JENKINS-20913


[jar caching] - winp.x64.dll access conflicts















@Kishore

If I understand toy correctly, you see the following issue:

Unable to render embedded object: File (..can this be fixed please) not found.

If yes, I suppose that this is an another issue. Please create ticket for it 



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [swarm] (JENKINS-21892) Swarm client fails to create slave if CSRF filter is enabled

2014-02-20 Thread simon....@gmail.com (JIRA)















































Simon Kaufmann
 created  JENKINS-21892


Swarm client fails to create slave if CSRF filter is enabled















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


swarm



Created:


20/Feb/14 10:27 AM



Description:


When having the "Prevent Cross Site Request Forgery exploits" flag enabled, the swarm client fails to create the slave with Failed to create a slave on Jenkins CODE: 403.

This is the relevant excerpt from the Jenkins server log:

←[33mFeb 20, 2014 11:17:08 AM hudson.security.csrf.CrumbFilter doFilter
WARNING: No valid crumb was included in request for /plugin/swarm/createSlave. Returning 403.





Project:


Jenkins



Priority:


Major



Reporter:


Simon Kaufmann

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21893) Maven Build gets slow after update to Jenkins ver. 1.532.2

2014-02-20 Thread martin.nattr...@logicals.com (JIRA)















































Martin Nattrodt
 created  JENKINS-21893


Maven Build gets slow after update to Jenkins ver. 1.532.2















Issue Type:


Bug



Assignee:


Unassigned


Components:


maven



Created:


20/Feb/14 10:49 AM



Description:


After Update of Jenkins to 1.532.2 LTS the build performace gots slow. It needs more than twice of the build time. 

I found two things in the Maven log what was different between before and after the Update:

The first it waits sometimes 30-40 secounds 
at a line like 
00:13:26.710 [JENKINS] Archiving disabled
00:14:55.462 [INFO]

This log Line was not before the  update.

The download Speed from the artifactory was about the half





Environment:


Debian 6




Project:


Jenkins



Priority:


Major



Reporter:


Martin Nattrodt

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [xunit] (JENKINS-21883) [xUnit] message not shown for QtTestLib

2014-02-20 Thread sahum...@gmail.com (JIRA)















































sahumada
 updated  JENKINS-21883


[xUnit]  message not shown for QtTestLib
















new version that also updates the tests so they pass





Change By:


sahumada
(20/Feb/14 10:57 AM)




Attachment:


0001-qtestlib-Fix-reporting-skip-messages.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] [xunit] (JENKINS-21883) [xUnit] message not shown for QtTestLib

2014-02-20 Thread sahum...@gmail.com (JIRA)













































  
sahumada
 edited a comment on  JENKINS-21883


[xUnit]  message not shown for QtTestLib
















new version that also updates the tests so they pass here



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [matrix-reloaded] (JENKINS-19970) ( Praqma case 10162 ) Matrix-reloaded does not adhere to build permissions in the same way that normal manual build triggering does.

2014-02-20 Thread oliver.b...@aei.mpg.de (JIRA)















































Oliver Bock
 commented on  JENKINS-19970


( Praqma case 10162 ) Matrix-reloaded does not adhere to build permissions in the same way that normal manual build triggering does. 















FWIW, we experience the same error: using project-based security (which is vital) doesn't work with Matrix Reloaded. It doesn't allow to trigger matrix rebuilds by users who don't have global build permissions, as described by the original reporter.

Is there any update on this?

Thanks.



























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







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

[JIRA] [codahale-metrics-librato] (JENKINS-21894) Codahale Metrics Librato plugin doesn't work

2014-02-20 Thread stephenconno...@java.net (JIRA)















































stephenconnolly
 created  JENKINS-21894


Codahale Metrics Librato plugin doesn't work















Issue Type:


Bug



Assignee:


Cyrille Le Clerc



Components:


codahale-metrics-librato



Created:


20/Feb/14 11:09 AM



Description:


This plugin seems to do nothing. I installed it and there was no options for export added




Project:


Jenkins



Priority:


Major



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] [swarm] (JENKINS-21892) Swarm client fails to create slave if CSRF filter is enabled

2014-02-20 Thread simon....@gmail.com (JIRA)















































Simon Kaufmann
 commented on  JENKINS-21892


Swarm client fails to create slave if CSRF filter is enabled















I have proposed a fix here: https://github.com/jenkinsci/swarm-plugin/pull/11 



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [github-oauth] (JENKINS-21895) Latest LTS causes swarm clients fail to authenticate when using github-oauth

Alex Tomlins
created JENKINS-21895

Latest LTS causes swarm clients fail to authenticate when using github-oauth

Issue Type:

Bug

Affects Versions:

current

Assignee:

Sam Kottler

Components:

github-oauth, swarm

Created:

20/Feb/14 11:54 AM

Description:

Upgrading to the latest LTS version (1.532.2) caused all our swarm clients to fail to connect. Reverting to the previous version (1.532.1) resolved the issue.

They all failed with an authentication failure. We're using the github-oauth plugin. The slave user below has been manually created on the server, and given an API token, which is being used as the password. I've managed to reproduce this using curl as follows.

Against 1.532.2:

$ curl --user slave https://jenkins.example.com/plugin/swarm/slaveInfo
Enter host password for user 'slave':
Error 401
Status Code: 401Exception: Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@661c7182: Username: slave; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@0: RemoteIpAddress: 192.168.0.3; SessionId: null; Not granted any authorities
Stacktrace: (none)

Generated by Winstone Servlet Engine v0.9.10 at Thu Feb 20 10:48:18 UTC 2014

Same command against 1.532.1:

$ curl --user slave https://jenkins.example.com/plugin/swarm/slaveInfo
Enter host password for user 'slave':
12345678-1234-1234-1234-123456789abc

This may be a duplicate of JENKINS-17539, but the symptoms are different.

Project:

Jenkins

Labels:

jenkins
slave

Priority:

Major

Reporter:

Alex Tomlins

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21521) Submodules are disabled by default as of git plugin 2.0.1

2014-02-20 Thread mikhail.kal...@gmail.com (JIRA)















































Mikhail Kalkov
 commented on  JENKINS-21521


Submodules are disabled by default as of git plugin 2.0.1















I agree that this defect breaks existing products. However, I was able to work around it by enabling recursive submodule checkout. I can imagine a case when a non-recursive checkout is necessary and then it would be a blocker. Since this issue is not critical for me, I set it to "Minor" on submission. I don't think Niklas De Loof has actually reviewed it yet.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-19591) Pathological branch rename causes git fetch to fail

SCM/JIRA link daemon
commented on JENKINS-19591

Pathological branch rename causes git fetch to fail

Code changed in jenkins
User: Mark Waite
Path:
src/test/java/org/jenkinsci/plugins/gitclient/GitAPITestCase.java
http://jenkins-ci.org/commit/git-client-plugin/637ae514811e381ab1b0294164594cce5849a7e1
Log:
Test prune with pathologically named branches

If a branch is created and pushed to a remote repository (for example,
a branch named "branch1"), then that branch is deleted, and a new
branch is created and pushed which uses the first branch name as a
parent (for example, a branch named "branch1/a"), the fetch will fail
until a "git remote prune origin" has been performed to remove the
originally created remote branch name from the working repository.

Refer to https://issues.jenkins-ci.org/browse/JENKINS-19591 for a more
detailed description.

This is another case where the JGit implementation differs from the
command line git implementation. The JGit implementation does not
seem to require the "git remote prune origin" command. I assume it
performs that operation happens implicitly inside JGit.

[JIRA] [git] (JENKINS-21896) How to customize commit comments for the push of merging results

2014-02-20 Thread m...@protel.net (JIRA)















































m r
 created  JENKINS-21896


How to customize commit comments for the push of merging results















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git



Created:


20/Feb/14 1:33 PM



Description:


I wanted to use the "automatic merging" functionality as described here: "Using Git, Jenkins and pre-build branch merging" ( https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-AdvancedFeatures ). I configured my job a described with the integration branch (Branch to merge to) configured to "developAutoMerge" and leaved the 'branch' field in the Git SCM blank.

When I "Build now" I get following exception:

Fetching changes from the remote Git repository
Fetching upstream changes from g...@repository.git
Seen branch in repository origin/develop
Seen branch in repository origin/developAutoMerge
Seen branch in repository origin/feature/blabla
[...]
Seen branch in repository origin/master
Seen branch in repository origin/release/2.6.1
Seen branch in repository origin/release/2.6.2
Seen 13 remote branches
Multiple candidate revisions
Scheduling another build to catch up with blaServerBuild_developAutoMerge
Merging Revision 6474f8ef91822e58edc55aad707d2725ff5a8431 (origin/feature/blabla) onto /developAutoMerge using resolve strategy
FATAL: Command "git rev-parse /developAutoMerge^{commit}" returned status code 128:
stdout: /developAutoMerge^{commit}

stderr: fatal: ambiguous argument '/developAutoMerge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions

hudson.plugins.git.GitException: Command "git rev-parse /developAutoMerge^{commit}" returned status code 128:
stdout: /developAutoMerge^{commit}

stderr: fatal: ambiguous argument '/developAutoMerge^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions

	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1148)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1125)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1121)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:937)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:947)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:401)
	at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257)
	at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:62)
	at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:795)
	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:862)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1415)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)
	at hudson.model.Run.execute(Run.java:1678)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)

I found a similar problem by googling: https://groups.google.com/forum/#!topic/jenkinsci-dev/ek4hYR-z08k
The proposed solution there was downgrading the Jenkins Git plugin from 2.0 to 1.4.0.




Environment:


Linux Ubuntu 3.2.0-58-generic x86_64

Jenkins ver. 1.546

Git Plugin 2.0 (also with 2.0.1 not working)

Git server plugin 1.3

Jenkins GIT client plugin 1.6.2




Project:


Jenkins



Labels:


exception
git
plugin




Priority:


Major



Reporter:


m r

[JIRA] [core] (JENKINS-16514) Jenkins slow to not responding when auto refresh is enabled

2014-02-20 Thread ever...@free.fr (JIRA)
















































evernat
 resolved  JENKINS-16514 as Incomplete


Jenkins slow to not responding when auto refresh is enabled 
















There is not enough information in this issue to find a fix.
For example, I suggest to take thread dumps in this case, to find what is going on:
http://host:port/threadDump





Change By:


evernat
(20/Feb/14 1:34 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























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







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

[JIRA] [git] (JENKINS-21896) How to customize commit comments for the push of merging results

2014-02-20 Thread m...@protel.net (JIRA)















































m r
 updated  JENKINS-21896


How to customize commit comments for the push of merging results
















Change By:


m r
(20/Feb/14 1:40 PM)




Issue Type:


Bug
Improvement





Labels:


exception
 git plugin
 publisher





Environment:


Linux Ubuntu 3.2.0-58-generic x86_64Jenkins ver. 1.546Git Plugin 2.0
 (also with 2.0.1 not working)
Git server plugin 1.3Jenkins GIT client plugin 1.6.2





Priority:


Major
Minor





Description:


I
 wanted to use
 am using
 the "automatic merging" functionality as described here: "Using Git, Jenkins and pre-build branch merging" ( https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-AdvancedFeatures ).
 The merging is working well. What
 I
 configured my job a described with the integration branch (Branch
 wanted is
 to
 have some readable information about which two branches are integratet within a commited
 merge
 to) configured to "developAutoMerge" and leaved the 'branch' field in the Git SCM blank
 result
.
 The current comments look like:

When I
 "
Build now
Merge commit '6cb5a448d66ab30aca2257123e7c0396fa9fddac' into HEAD
"
 I get following exception:

Fetching changes from the remote Git repositoryFetching upstream changes from g...@repository.gitSeen branch in repository origin
I would be very useful if more informative commit
/
develop
push comments could be written like:

Seen branch in repository origin/developAutoMerge

Seen
"Merged
 branch
 in repository origin/feature/blabla[...]Seen branch in repository origin/masterSeen branch in repository origin/
 '
release/2.
6
4
.
1Seen
7' into
 branch
 in repository origin/release/2.6.2Seen 13 remote branchesMultiple candidate revisionsScheduling another build to catch up with blaServerBuild_developAutoMergeMerging Revision 6474f8ef91822e58edc55aad707d2725ff5a8431 (origin/feature/blabla) onto /developAutoMerge using resolve strategyFATAL: Command "git rev-parse /developAutoMerge^{commit}" returned status code 128:stdout: /developAutoMerge^{commit}stderr: fatal: ambiguous argument
 '
/developAutoMerge^{commit}
develop
'
: unknown revision or path not in the working tree
.
Use
 Merge commit
 '
--
6cb5a448d66ab30aca2257123e7c0396fa9f8dac
'
 to separate paths from revisionshudson.plugins.git.GitException: Command
 into HEAD
 "
git rev-parse /developAutoMerge^{commit}" returned status code 128:

stdout: /developAutoMerge^{commit}

stderr: fatal: ambiguous argument '/developAutoMerge^{commit}': unknown revision or path not in the working tree.Use '--' to separate paths from revisions	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1148)	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1125)	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1121)	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:937)	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:947)	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.revParse(CliGitAPIImpl.java:401)	at hudson.plugins.git.GitAPI.revParse(GitAPI.java:257)	at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:62)	at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:795)	at hudson.plugins.git.GitSCM.checkout(GitSCM.java:862)	at hudson.model.AbstractProject.checkout(AbstractProject.java:1415)	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652)	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561)	at hudson.model.Run.execute(Run.java:1678)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)	at hudson.model.ResourceController.execute(ResourceController.java:88)	at hudson.model.Executor.run(Executor.jav

[JIRA] [extra-columns] (JENKINS-21740) Columns with value of a variable from script

2014-02-20 Thread d.marom...@lantiq.com (JIRA)















































dor cohen
 stopped work on  JENKINS-21740


Columns with value of a variable from script
















Change By:


dor cohen
(20/Feb/14 1:42 PM)




Status:


In Progress
Open



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [extra-columns] (JENKINS-21740) Columns with value of a variable from script

2014-02-20 Thread d.marom...@lantiq.com (JIRA)















































dor cohen
 started work on  JENKINS-21740


Columns with value of a variable from script
















Change By:


dor cohen
(20/Feb/14 1:42 PM)




Status:


Open
In Progress



























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







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

[JIRA] [ssh-credentials] (JENKINS-20638) SSH key credential doesn't work with key passphrase

2014-02-20 Thread ide...@gmail.com (JIRA)















































Marcelo Filho
 commented on  JENKINS-20638


SSH key credential doesn't work with key passphrase















Are the same?


stderr: Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password).
fatal: Could not read from remote repository.




























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-11989) Build history time line chart doesn't render in Internet Explorer 8.0.6001

2014-02-20 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-11989


Build history time line chart doesn't render in Internet Explorer 8.0.6001















Is it reproduced with a recent Jenkins version?



























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







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

[JIRA] [all-changes] (JENKINS-21808) Error on Save Projet Modification

2014-02-20 Thread lmari...@gmail.com (JIRA)















































LeMar Davidson
 commented on  JENKINS-21808


Error on Save Projet Modification 















I think I am also facing this issue:




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: Failed to parse JSON:{  }
	at org.kohsuke.stapler.RequestImpl.getSubmittedForm(RequestImpl.java:878)
	at hudson.model.ListView.submit(ListView.java:318)
	at hudson.model.View.doConfigSubmit(View.java:945)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
	at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46)
	at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	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:722)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	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.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	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:79)
	at hudson.security.ChainedServ

[JIRA] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly















































Olivier Trempe
 commented on  JENKINS-15163


Mercurial plugin cloning not resolving environment variables correctly















@jglick I upgraded to 1.50-beta-2. From what I understand, this does not solve my issue as environment variables set in slave configuration are still not used by the mercurial plugin. Thus I cannot rely on setting HGRCPATH in slaves configuration to use a specific hgrc on each slave machine.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [hp-application-automation-tools-plugin] (JENKINS-21897) Execution status: Error, Message: Access is denied

2014-02-20 Thread daniel.glu...@de.bosch.com (JIRA)















































Daniel Glueck
 created  JENKINS-21897


Execution status: Error, Message: Access is denied















Issue Type:


Bug



Assignee:


Ofir Shaked



Components:


hp-application-automation-tools-plugin



Created:


20/Feb/14 2:32 PM



Description:


I currently face the problem that my HP ALM test automations are not running when executed with the HP Application Automation Tools. They are running fine when I trigger them from within HP ALM.

This is the output of the job:
Does anybody know what "Execution status: Error, Message: Access is denied" means. Is there maybe some permission configuration missing in HP ALM?


Building in workspace D:\Tools\Jenkins\workspace\Dani-JenkinsWithQC
[Dani-JenkinsWithQC] $ D:\Tools\Jenkins\workspace\Dani-JenkinsWithQC\HpToolsLauncher.exe -paramfile props20022014150821066.txt
"Started..."
Timeout is set to: 5
Run mode is set to: RUN_REMOTE

Starting test set execution
Test set name: JenkinsIntegartionTest, Test set id: 2457
"Number of tests in set: "2
Test 1: [1]Login will run on host: si0vm839
Test 2: [1]Logout will run on host: si0vm839
"Scheduler started at:20.02.2014 15:08:28
---
20.02.2014 15:08:29 Running: [1]Login
20.02.2014 15:08:29 Running test: [1]Login, Test id: 938, Test instance id: 1412
Test: [1]Login, Id: 1412, Execution status: Running
Test: [1]Login, Id: 1412, Execution status: Error, Message: Access is denied
20.02.2014 15:08:33 Test complete: [1]Login
---
20.02.2014 15:08:33 Running: [1]Logout
20.02.2014 15:08:33 Running test: [1]Logout, Test id: 939, Test instance id: 1413
Test: [1]Logout, Id: 1413, Execution status: Running
Test: [1]Logout, Id: 1413, Execution status: Error, Message: Access is denied
==\nJob timed out!\n==

Run status: Job failed, total tests: 2, succeeded: 0, failures: 0, errors: 2
Build step 'Execute HP tests from HP ALM' changed build result to FAILURE
Finished: FAILURE





Environment:


HP Application Automation Tools: 2.0.2

HP ALM Server: 11.52

Jenkins on Windows: 1.537




Project:


Jenkins



Priority:


Major



Reporter:


Daniel Glueck

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec

2014-02-20 Thread vinc...@latombe.net (JIRA)













































  
Vincent Latombe
 edited a comment on  JENKINS-21626


Permanent build due to the use of an environment variable in config spec
















Released in 1.5



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec

2014-02-20 Thread vinc...@latombe.net (JIRA)















































Vincent Latombe
 commented on  JENKINS-21626


Permanent build due to the use of an environment variable in config spec















Releases in 1.5



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec

2014-02-20 Thread vinc...@latombe.net (JIRA)
















































Vincent Latombe
 closed  JENKINS-21626 as Fixed


Permanent build due to the use of an environment variable in config spec
















Change By:


Vincent Latombe
(20/Feb/14 2:35 PM)




Status:


Open
Closed





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] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly

2014-02-20 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 commented on  JENKINS-15163


Mercurial plugin cloning not resolving environment variables correctly















I guess that would matter if you used a custom version of the largefiles extension, and this was in a different location on each slave. Normally to enable it you would simply use


[extensions]
largefiles =


since it is a bundled extension.

(%include syntax is not currently supported for the configuration field, though I think it could be with a bit of work.)



























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







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

[JIRA] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly

2014-02-20 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 commented on  JENKINS-15163


Mercurial plugin cloning not resolving environment variables correctly















Oh and even if you do have a custom extension, you could always create a ZIP of a Mercurial installation containing it in the hgext directory and specify a ZIP download tool installer for the Jenkins definition of the installation. More cumbersome but would work.



























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







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

[JIRA] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly















































Olivier Trempe
 commented on  JENKINS-15163


Mercurial plugin cloning not resolving environment variables correctly















The use of largefiles extension was just an example to illustrate the problem.

The actual hgrc file I want to use contains many other things: hooks, extensions, auth, many subpaths



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly















































Olivier Trempe
 commented on  JENKINS-15163


Mercurial plugin cloning not resolving environment variables correctly















The hgrc files are managed on every slaves with a configuration management tool. It is very easy to customize the content and its location. So being able to use HGRCPATH environment variable would help a lot for that matter.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21225) Configuration Slicing for Editable Email Notification not working anymore with latest versions

2014-02-20 Thread bat...@batmat.net (JIRA)















































Baptiste Mathus
 commented on  JENKINS-21225


Configuration Slicing for Editable Email Notification not working anymore with latest versions















For the record, just reproduced with :

	Jenkins 1.531
	Configuration Slicing Plugin : 1.37
	Email-Ext plugin : 2.34





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [thinBackup] (JENKINS-21898) ThinBackup can not restore ZIP saved in in Linux onto a Windows Machine

2014-02-20 Thread forward.my.mai...@gmail.com (JIRA)















































John Smith
 created  JENKINS-21898


ThinBackup can not restore ZIP saved in in Linux onto a Windows Machine















Issue Type:


Bug



Assignee:


Thomas Fürer



Components:


thinBackup



Created:


20/Feb/14 3:04 PM



Description:


Log file contains the following:

Caught exception evaluating: it.availableBackups in /jenkins/thinBackup/restoreOptions. Reason: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)

Caused by: java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	at java.lang.String.substring(String.java:1911)
	at org.jvnet.hudson.plugins.thinbackup.backup.BackupSet.initializeFromZipFile(BackupSet.java:129)
	at org.jvnet.hudson.plugins.thinbackup.backup.BackupSet.initialize(BackupSet.java:93)
	at org.jvnet.hudson.plugins.thinbackup.backup.BackupSet.(BackupSet.java:79)
	at org.jvnet.hudson.plugins.thinbackup.utils.Utils.getValidBackupSetsFromZips(Utils.java:352)
	at org.jvnet.hudson.plugins.thinbackup.utils.Utils.getValidBackupSets(Utils.java:371)
	at org.jvnet.hudson.plugins.thinbackup.utils.Utils.getBackupsAsDates(Utils.java:284)
	at org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink.getAvailableBackups(ThinBackupMgmtLink.java:159)
	... 129 more


Looking at source I see

tmpName = tmpName.substring(0, tmpName.indexOf(File.separator));

I suspect File.separator is the Windows character, but the version used to save the archive is the Linux version.




Due Date:


20/Feb/14 12:00 AM




Environment:


Archive saved by ThinBackup v1.7.4 in Linux Server

Archive failed to restore on ThinBackup v1.7.4 in Windows 2008 Server

Jenkins version 1.551




Project:


Jenkins



Priority:


Major



Reporter:


John Smith

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly

2014-02-20 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 commented on  JENKINS-15163


Mercurial plugin cloning not resolving environment variables correctly















So support for %include $HGRCPATH would be helpful in your case.

Anyway it sounds like your issue has nothing whatsoever to do with the issue originally reported here, which is about expansion of variables in a clone URL and the comparison done by the plugin between the attempted clone URL and the path reported in the workspace (which is done to ensure that you get a clean clone after switching repository location).



























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







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

[JIRA] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly

2014-02-20 Thread robert.kozlow...@morganstanley.com (JIRA)















































Olivier Trempe
 commented on  JENKINS-15163


Mercurial plugin cloning not resolving environment variables correctly















Yes it would be useful.

Sorry for spamming this 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] [jenkins-tracker] (JENKINS-21765) Jenkins occasionally crashing on start up

2014-02-20 Thread chris.we...@jdsu.com (JIRA)















































Chris Welch
 updated  JENKINS-21765


Jenkins occasionally crashing on start up
















Two more crashes since the initial report.  Logs attached





Change By:


Chris Welch
(20/Feb/14 3:16 PM)




Attachment:


hs_err_pid2041.log





Attachment:


hs_err_pid5959.log



























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







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

[JIRA] [master-slave] (JENKINS-21875) NullPointerException when trying to mark slave temporarily offline

2014-02-20 Thread a...@wilken.de (JIRA)















































Andreas tS
 commented on  JENKINS-21875


NullPointerException when trying to mark slave temporarily offline















The same error occurs, when setting the master offline.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [jira] (JENKINS-21766) Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'

2014-02-20 Thread cvecchi...@ebay.com (JIRA)















































chris vecchione
 commented on  JENKINS-21766


Jenkins create jira issue plugin does not allow configurable jira issue type: defaults to 'bug'















Also (this should not need to be stated but in case): the 'Create jira issue' UI should add this new field ("Issue Type") allowing user input.



























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







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

[JIRA] [teamconcert] (JENKINS-21857) com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF

2014-02-20 Thread heath...@ca.ibm.com (JIRA)
















































Heather Fraser-Dube
 resolved  JENKINS-21857 as Fixed


com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF
















Change By:


Heather Fraser-Dube
(20/Feb/14 4:31 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [teamconcert] (JENKINS-21857) com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF

2014-02-20 Thread heath...@ca.ibm.com (JIRA)















































Heather Fraser-Dube
 commented on  JENKINS-21857


com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF















Pushed the missing files.

When developing within Eclipse we also install the -rtc jars into the hjplugin repo.



























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







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

[JIRA] [mstest] (JENKINS-21899) tests that return a status of Error are not being reported as such















































Robert Kozlowski
 created  JENKINS-21899


tests that return a status of Error are not being reported as such















Issue Type:


Bug



Affects Versions:


current



Assignee:


acmarques



Components:


mstest



Created:


20/Feb/14 5:08 PM



Description:


Tests that return a status of Error are not being reported as such.




Project:


Jenkins



Priority:


Minor



Reporter:


Robert Kozlowski

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira

2014-02-20 Thread pat...@diabol.se (JIRA)















































Patrik Boström
 commented on  JENKINS-13279


Interface with Crowd embedded that runs in Jira















CrowdRememberMeServices implements the some parts of the SSO functionality.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [jenkinswalldisplay] (JENKINS-21900) Progress indicator does not function properly in certain conditions

2014-02-20 Thread otta...@ottawan.kicks-ass.net (JIRA)















































Ivan Mounitsyn
 created  JENKINS-21900


Progress indicator does not function properly in certain conditions















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


jenkinswalldisplay



Created:


20/Feb/14 6:30 PM



Description:


jenkinswalldisplay.js lines 633-635:
var dateHeader = jqXHR.getResponseHeader("Date");
var date = new Date(dateHeader);
serverTime = date.getTime();

If response headers do not contain Date header (standalone Jenkins?) all currently building jobs progress show 100% complete.


Also noticed jenkinswalldisplay.js line 813: if (customTheme != null) 

If customTheme is not defined generates an error




Project:


Jenkins



Priority:


Minor



Reporter:


Ivan Mounitsyn

























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







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

[JIRA] [build-flow] (JENKINS-21901) Started by [buildflow-build#] message is not linked

2014-02-20 Thread mr...@sjm.com (JIRA)















































Michael Rose
 created  JENKINS-21901


Started by [buildflow-build#] message is not linked















Issue Type:


Bug



Assignee:


Nicolas De Loof



Attachments:


build-flow-unlinked.png



Components:


build-flow



Created:


20/Feb/14 6:47 PM



Description:


It would really improve usability if the "started by" message was a link instead of plain text (see attachment).




Project:


Jenkins



Priority:


Trivial



Reporter:


Michael Rose

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [monitoring] (JENKINS-21902) Add Waiting / Blocked on information in textual thread dump

2014-02-20 Thread sagi.sinai-gla...@ericsson.com (JIRA)















































Sagi Sinai-Glazer
 created  JENKINS-21902


Add Waiting / Blocked on information in textual thread dump















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


monitoring



Created:


20/Feb/14 6:54 PM



Description:


A waiting thread will show in the Monitoring plugin like this:
"http-bio-9029-exec-3493" daemon prio=5 TIMED_WAITING
But on host-url/threadDump screen it'll give more information on the object that is being waited for:
"http-bio-9029-exec-3493" Id=194353 Group=main TIMED_WAITING on com.sun.jndi.ldap.LdapRequest@10f324c

This goes the same for Blocked state.
Without this information the thread-dump feature becomes kind of useless in these situations.




Project:


Jenkins



Priority:


Major



Reporter:


Sagi Sinai-Glazer

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-13765) PTC Integrity Plugin - Restore Timestamp Not Working
















































Cletus D'Souza
 resolved  JENKINS-13765 as Won't Fix


PTC Integrity Plugin - Restore Timestamp Not Working
















This is an Integrity API issue cannot be resolved in the plugin





Change By:


Cletus D'Souza
(20/Feb/14 6:59 PM)




Status:


Open
Resolved





Resolution:


Won't Fix



























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







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

[JIRA] [integrity-plugin] (JENKINS-9477) [integrity-plugin] MKS plugin consumes 1 file descriptor on MKS server per file in project to check-out
















































Cletus D'Souza
 resolved  JENKINS-9477 as Won't Fix


[integrity-plugin] MKS plugin consumes 1 file descriptor on MKS server per file in project to check-out
















This is an Integrity API issue.  Cannot be resolved in the plugin.





Change By:


Cletus D'Souza
(20/Feb/14 6:59 PM)




Status:


Open
Resolved





Resolution:


Won't Fix



























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







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

[JIRA] [integrity-plugin] (JENKINS-18579) PTC Plugin does not restore symbolic links in filesystem
















































Cletus D'Souza
 resolved  JENKINS-18579 as Won't Fix


PTC Plugin does not restore symbolic links in filesystem
















This is an Integrity API issue, cannot be fixed in the plugin





Change By:


Cletus D'Souza
(20/Feb/14 7:01 PM)




Status:


Open
Resolved





Resolution:


Won't Fix



























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







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

[JIRA] [integrity-plugin] (JENKINS-21826) Integrity Plugin does not work with parameterized builds
















































Cletus D'Souza
 resolved  JENKINS-21826 as Not A Defect


Integrity Plugin does not work with parameterized builds
















Incorrect syntax used...  Use ${env['VARIABLE_NAME']}





Change By:


Cletus D'Souza
(20/Feb/14 7:03 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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







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

[JIRA] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue

2014-02-20 Thread aba...@java.net (JIRA)















































abayer
 commented on  JENKINS-21044


Throttle Concurrent Builds blocking Jenkins queue















Jesse, Oleg, are you guys working on this? If not, I think we should probably do a rollback and re-release the old 1.8.0 again as 1.8.2 to trump the broken 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] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue















































Oleg Nenashev
 commented on  JENKINS-21044


Throttle Concurrent Builds blocking Jenkins queue















@abayer
I've started working on the issue. 
BTW, I cannot re-test the fix now due to the vacation. 

If somebody has a relevant dev. system, I can provide a test build.



























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







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

[JIRA] [maven] (JENKINS-21903) Not all maven downstream jobs get triggered

2014-02-20 Thread steph...@odul.com (JIRA)















































Stephane Odul
 created  JENKINS-21903


Not all maven downstream jobs get triggered















Issue Type:


Bug



Assignee:


olamy



Components:


maven, maven-dependency-update-trigger



Created:


20/Feb/14 7:56 PM



Description:


We have a maven job Foo with 10 downstream dependencies. In the Job page all the dependencies are noted clearly as well as on the the actual build page. Hower some of the downstream Jobs show with "(none)" instead of their build number and the log of the Foo build shows the "Triggering a new build of " lines, but only for 7 out of the 10 that should be triggered.

Jenkins clearly knows about the SNAPSHOT dependency and shows the downstream relationship correctly, yet it 'forgets' to trigger some of the jobs.

Confirmed with 1.550 and 1.551.




Project:


Jenkins



Priority:


Major



Reporter:


Stephane Odul

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git

2014-02-20 Thread bpodgur...@gmail.com (JIRA)















































Benjamin Podgursky
 commented on  JENKINS-15128


Renaming job doesn't work with Git















Any hope of seeing a fix for this?  The plugin looked to be really useful when we first installed it, but this makes it unusable unfortunately (we have too many projects and developers to rely on manual fixes every time a project is deleted/renamed...)



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ownership] (JENKINS-20313) Keep ownership information on duplicated job















































Oleg Nenashev
 started work on  JENKINS-20313


Keep ownership information on duplicated job
















Change By:


Oleg Nenashev
(20/Feb/14 8:47 PM)




Status:


Open
In Progress



























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







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

[JIRA] [ownership] (JENKINS-21904) Add a ItemOwnershipPolicy extension point















































Oleg Nenashev
 created  JENKINS-21904


Add a ItemOwnershipPolicy extension point















Issue Type:


New Feature



Assignee:


Oleg Nenashev



Components:


ownership



Created:


20/Feb/14 8:49 PM



Description:


Use-case:

	Allow to create custom ownership setup on job's creation or copying






Project:


Jenkins



Labels:


extension




Priority:


Major



Reporter:


Oleg Nenashev

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ownership] (JENKINS-21904) Add a ItemOwnershipPolicy extension point















































Oleg Nenashev
 started work on  JENKINS-21904


Add a ItemOwnershipPolicy extension point
















Change By:


Oleg Nenashev
(20/Feb/14 8:54 PM)




Status:


Open
In Progress



























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







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

[JIRA] [authorize-project] (JENKINS-21117) Plugin does not load AuthorizeProjectStrategy global configurations on Jenkins start
















































Oleg Nenashev
 resolved  JENKINS-21117 as Not A Defect


Plugin does not load AuthorizeProjectStrategy global configurations on Jenkins start
















Change By:


Oleg Nenashev
(20/Feb/14 8:58 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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







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

[JIRA] [authorize-project] (JENKINS-21117) Plugin does not load AuthorizeProjectStrategy global configurations on Jenkins start















































Oleg Nenashev
 commented on  JENKINS-21117


Plugin does not load AuthorizeProjectStrategy global configurations on Jenkins start















Agreed. The issue is invalid



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [authorize-project] (JENKINS-21117) Plugin does not load AuthorizeProjectStrategy global configurations on Jenkins start
















































Oleg Nenashev
 closed  JENKINS-21117 as Not A Defect


Plugin does not load AuthorizeProjectStrategy global configurations on Jenkins start
















Change By:


Oleg Nenashev
(20/Feb/14 8:58 PM)




Status:


Resolved
Closed



























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







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

[JIRA] [ownership] (JENKINS-18976) Send e-mail notifications in case of the ownership changes















































Oleg Nenashev
 updated  JENKINS-18976


Send e-mail notifications in case of the ownership changes
















Workaround: use Mail Watcher Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Mail+Watcher+Plugin





Change By:


Oleg Nenashev
(20/Feb/14 8:56 PM)




Assignee:


Oleg Nenashev





Priority:


Major
Minor



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [role-strategy] (JENKINS-16415) Unable to add project roles using Role stratedy plugin















































Oleg Nenashev
 commented on  JENKINS-16415


Unable to add project roles using Role stratedy plugin















Sorry for the long delay...
The issue occurs in IE 9/10 Compat Views only. 
We have discovered many issues with Compat Views during last months.

I'm almost sure that JENKINS-19826 addressees this issue as well, so the submission should work in 1.548+



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [role-strategy] (JENKINS-16415) Unable to add project roles using Role stratedy plugin















































Oleg Nenashev
 updated  JENKINS-16415


Unable to add project roles using Role stratedy plugin
















Change By:


Oleg Nenashev
(20/Feb/14 9:07 PM)




Labels:


_javascript_





Environment:


Windows, IE 9.0
 Compat View



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [concurrent-build] (JENKINS-15098) svnexternals causing issues with concurrent builds
















































Oleg Nenashev
 assigned  JENKINS-15098 to kutzi



svnexternals causing issues with concurrent builds
















The PR is still waiting for Kutzi's review...





Change By:


Oleg Nenashev
(20/Feb/14 9:12 PM)




Assignee:


Oleg Nenashev
kutzi



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21260) PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!















































SCM/JIRA link daemon
 commented on  JENKINS-21260


PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!















Code changed in jenkins
User: Cletus D'Souza
Path:
 src/main/java/hudson/scm/APISession.java
 src/main/java/hudson/scm/IntegrityCMProject.java
 src/main/java/hudson/scm/IntegrityCheckoutTask.java
 src/main/java/hudson/scm/IntegritySCM.java
http://jenkins-ci.org/commit/integrity-plugin/9c4605abb92d6adebd8618828bd8c49e3d0cb526
Log:
  Resolved the following issues:
JENKINS-21587: memory leak in Plugin 1.22 -orphaned Logger Threads (accepted patch from Matthias Rump - thank you!)
JENKINS-21479: Poll SCM trigger no functioning during the first execution
JENKINS-21260: PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21479) Poll SCM trigger no functioning during the first execution















































SCM/JIRA link daemon
 commented on  JENKINS-21479


Poll SCM trigger no functioning during the first execution















Code changed in jenkins
User: Cletus D'Souza
Path:
 src/main/java/hudson/scm/APISession.java
 src/main/java/hudson/scm/IntegrityCMProject.java
 src/main/java/hudson/scm/IntegrityCheckoutTask.java
 src/main/java/hudson/scm/IntegritySCM.java
http://jenkins-ci.org/commit/integrity-plugin/9c4605abb92d6adebd8618828bd8c49e3d0cb526
Log:
  Resolved the following issues:
JENKINS-21587: memory leak in Plugin 1.22 -orphaned Logger Threads (accepted patch from Matthias Rump - thank you!)
JENKINS-21479: Poll SCM trigger no functioning during the first execution
JENKINS-21260: PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21587) memory leak in Plugin 1.22 -orphaned Logger Threads















































SCM/JIRA link daemon
 commented on  JENKINS-21587


memory leak in Plugin 1.22 -orphaned Logger Threads















Code changed in jenkins
User: Cletus D'Souza
Path:
 src/main/java/hudson/scm/APISession.java
 src/main/java/hudson/scm/IntegrityCMProject.java
 src/main/java/hudson/scm/IntegrityCheckoutTask.java
 src/main/java/hudson/scm/IntegritySCM.java
http://jenkins-ci.org/commit/integrity-plugin/9c4605abb92d6adebd8618828bd8c49e3d0cb526
Log:
  Resolved the following issues:
JENKINS-21587: memory leak in Plugin 1.22 -orphaned Logger Threads (accepted patch from Matthias Rump - thank you!)
JENKINS-21479: Poll SCM trigger no functioning during the first execution
JENKINS-21260: PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21587) memory leak in Plugin 1.22 -orphaned Logger Threads
















































Cletus D'Souza
 resolved  JENKINS-21587 as Fixed


memory leak in Plugin 1.22 -orphaned Logger Threads
















Patch accepted and released!





Change By:


Cletus D'Souza
(20/Feb/14 9:40 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] [integrity-plugin] (JENKINS-21479) Poll SCM trigger no functioning during the first execution
















































Cletus D'Souza
 resolved  JENKINS-21479 as Fixed


Poll SCM trigger no functioning during the first execution
















Suggestion incorporated!  Thanks!





Change By:


Cletus D'Souza
(20/Feb/14 9:41 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [integrity-plugin] (JENKINS-21260) PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!















































Cletus D'Souza
 commented on  JENKINS-21260


PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!















This issue is related to Jenkins-21479.  This should be resolved now!



























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







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

[JIRA] [integrity-plugin] (JENKINS-21260) PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!
















































Cletus D'Souza
 resolved  JENKINS-21260 as Fixed


PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!
















Resolved in 1.23





Change By:


Cletus D'Souza
(20/Feb/14 9:42 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git

2014-02-20 Thread jenk...@ericlong.com (JIRA)















































Eric Long
 commented on  JENKINS-15128


Renaming job doesn't work with Git















Richard Raseley
This fix did not appear to work for me either.  My job names have spaces in them but not parenthesis.  I am still having problems. Unfortunately we are likely to remove this plug in and manage configurations a different way until this is 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] [extra-columns] (JENKINS-21740) Columns with value of a variable from script















































Fred G
 commented on  JENKINS-21740


Columns with value of a variable from script















Hi,

Can you give an example of what kind of value you would like to see in such a column?
Please also keep in mind, that without additional work such a value would only be displayed as long as the job is executed.
So most of the time the column would be empty.

Regards,

Fred



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [extra-columns] (JENKINS-21740) Columns with value of a variable from script
















































Fred G
 assigned  JENKINS-21740 to dor cohen



Columns with value of a variable from script
















Change By:


Fred G
(20/Feb/14 10:11 PM)




Assignee:


Fred G
dor cohen



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [extra-columns] (JENKINS-21630) Add Column : Test sparkline
















































Fred G
 assigned  JENKINS-21630 to Bruno Perel



Add Column : Test sparkline
















Change By:


Fred G
(20/Feb/14 10:26 PM)




Assignee:


Fred G
Bruno Perel



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [extra-columns] (JENKINS-21630) Add Column : Test sparkline















































Fred G
 commented on  JENKINS-21630


Add Column : Test sparkline















I had a look around for lightweight _javascript_ framework that shows such a sparkline. Sparklines.js seems to go in the right direction, for example.
Nevertheless I think this will have a major impact on the performance of displaying the job list, especially if you have a few dozen or even hundreds of jobs on a page.
One alternative could be to generate such sparklines as graphics, but this would involve server-side graphic generation which is also not trivial.
So the question is, what information does a sparkline give you compared to simple icons (like the weather symbols) that show the current trend of success?




























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [extra-columns] (JENKINS-21295) Project Description column configs for trim and width not correctly redisplaying















































Fred G
 commented on  JENKINS-21295


Project Description column configs for trim and width not correctly redisplaying















There is some additional padding, so it might not be pixel perfect.
I can't reproduce such big difference though.

Which browser are you using? Can you attach a screenshot?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [extra-columns] (JENKINS-21630) Add Column : Test sparkline













































  
Fred G
 edited a comment on  JENKINS-21630


Add Column : Test sparkline
















I had a look around for a lightweight _javascript_ framework that shows such a sparkline. Sparklines.js seems to go in the right direction, for example.
Nevertheless I think this will have a major impact on the performance of displaying the job list, especially if you have a few dozen or even hundreds of jobs on a page.
One alternative could be to generate such sparklines as graphics, but this would involve server-side graphic generation which is also not trivial.
So the question is, what information does a sparkline give you compared to simple icons (like the weather symbols) that show the current trend of success?




























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream















































Steve Roth
 created  JENKINS-21905


intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


21/Feb/14 12:39 AM



Description:


Since approximately 1/30 we have seen 15 very intermittent archiving failures in Jenkins, of the form:


Archiving artifacts
ERROR: Failed to archive artifacts: versions/**, archive/**
java.io.IOException: Failed to extract /foo/bar/slave/workspace/someJob/transfer of 7 files
	at hudson.FilePath.readFromTar(FilePath.java:2088)
	at hudson.FilePath.copyRecursiveTo(FilePath.java:2000)
	at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57)
	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705)
	at hudson.model.Run.execute(Run.java:1695)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:231)
Caused by: java.io.EOFException: Unexpected end of ZLIB input stream
	at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:186)
	at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106)
	at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257)
	at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223)
	at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228)
	at hudson.FilePath.readFromTar(FilePath.java:2066)
	... 12 more
Build step 'Archive the artifacts' changed build result to FAILURE



We definitely have seen this running 1.549 and later.  I cannot confirm if we saw it with 1.548 or earlier, but I think it was less frequent.  It seems to be a relatively new issue we are seeing.




Project:


Jenkins



Priority:


Major



Reporter:


Steve Roth

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [copyartifact] (JENKINS-19473) failed to archive slave artifacts. Unexpected end of ZLIB input stream















































Steve Roth
 commented on  JENKINS-19473


failed to archive slave artifacts. Unexpected end of ZLIB input stream















@fommil – I am seeing the same thing, and have created bug JENKINS-21905 for that 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] [core] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream















































Steve Roth
 commented on  JENKINS-21905


intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream















I saw JENKINS-19473, but this seems to be a different issue.  The caused by clause is different.  [in that case, it was a java.lang.ArrayIndexOutOfBoundsException]



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream















































Steve Roth
 updated  JENKINS-21905


intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
















Change By:


Steve Roth
(21/Feb/14 12:42 AM)




Description:


Since approximately 1/30 we have seen 15 very intermittent archiving failures in Jenkins, of the form:{noformat}Archiving artifactsERROR: Failed to archive artifacts: versions/**, archive/**java.io.IOException: Failed to extract /foo/bar/slave/workspace/someJob/transfer of 7 files	at hudson.FilePath.readFromTar(FilePath.java:2088)	at hudson.FilePath.copyRecursiveTo(FilePath.java:2000)	at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57)	at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140)	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784)	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756)	at hudson.model.Build$BuildExecution.post2(Build.java:183)	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705)	at hudson.model.Run.execute(Run.java:1695)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)	at hudson.model.ResourceController.execute(ResourceController.java:88)	at hudson.model.Executor.run(Executor.java:231)Caused by: java.io.EOFException: Unexpected end of ZLIB input stream	at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:186)	at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106)	at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257)	at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223)	at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228)	at hudson.FilePath.readFromTar(FilePath.java:2066)	... 12 moreBuild step 'Archive the artifacts' changed build result to FAILURE{noformat}We definitely have seen this running 1.
549
548
 and later
, especially with 1
.
549.
  I cannot confirm if we saw it with 1.
548
547
 or earlier, but
 if so,
 I think it was less frequent.  It seems to be a relatively new issue we are seeing.



























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







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

[JIRA] [core] (JENKINS-21906) NumberFormatException occurs when accessing the JSON api

2014-02-20 Thread uw...@java.net (JIRA)















































uwodi
 created  JENKINS-21906


NumberFormatException occurs when accessing the JSON api















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


21/Feb/14 12:47 AM



Description:


When accessing the http://.../api/json url we get the following exception in build 1.551


java.io.IOException: Failed to write timestamp
	at org.kohsuke.stapler.export.Property.writeTo(Property.java:120)
	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187)
	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182)
	at org.kohsuke.stapler.export.Property.writeValue(Property.java:232)
	at org.kohsuke.stapler.export.Property.writeValue(Property.java:169)
	at org.kohsuke.stapler.export.Property.writeValue(Property.java:137)
	at org.kohsuke.stapler.export.Property.writeTo(Property.java:114)
	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187)
	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182)
	at org.kohsuke.stapler.export.Property.writeValue(Property.java:232)
	at org.kohsuke.stapler.export.Property.writeValue(Property.java:137)
	at org.kohsuke.stapler.export.Property.writeTo(Property.java:114)
	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187)
	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182)
	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182)
	at org.kohsuke.stapler.export.Model.writeTo(Model.java:154)
	at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267)
	at hudson.model.Api.doJson(Api.java:195)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	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.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	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:728)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:2

[JIRA] [core] (JENKINS-21906) NumberFormatException occurs when accessing the JSON api

2014-02-20 Thread uw...@java.net (JIRA)















































uwodi
 updated  JENKINS-21906


NumberFormatException occurs when accessing the JSON api
















Change By:


uwodi
(21/Feb/14 1:01 AM)




Description:


When accessing the http://.../api/json url we get the following exception in build 1.551
.  The functionality works in 1.549.
java.io.IOException: Failed to write timestamp	at org.kohsuke.stapler.export.Property.writeTo(Property.java:120)	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187)	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182)	at org.kohsuke.stapler.export.Property.writeValue(Property.java:232)	at org.kohsuke.stapler.export.Property.writeValue(Property.java:169)	at org.kohsuke.stapler.export.Property.writeValue(Property.java:137)	at org.kohsuke.stapler.export.Property.writeTo(Property.java:114)	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187)	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182)	at org.kohsuke.stapler.export.Property.writeValue(Property.java:232)	at org.kohsuke.stapler.export.Property.writeValue(Property.java:137)	at org.kohsuke.stapler.export.Property.writeTo(Property.java:114)	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187)	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182)	at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182)	at org.kohsuke.stapler.export.Model.writeTo(Model.java:154)	at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267)	at hudson.model.Api.doJson(Api.java:195)	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)	at java.lang.reflect.Method.invoke(Method.java:601)	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)	at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210)	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)	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.MetaClass$6.doDispatch(MetaClass.java:248)	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)	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:728)	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)	at org.apache.catalina.core.ApplicationFilterChai

[JIRA] [extra-columns] (JENKINS-21295) Project Description column configs for trim and width not correctly redisplaying















































SCM/JIRA link daemon
 commented on  JENKINS-21295


Project Description column configs for trim and width not correctly redisplaying















Code changed in jenkins
User: Fred G
Path:
 src/main/java/jenkins/plugins/extracolumns/BuildDescriptionColumn.java
 src/main/java/jenkins/plugins/extracolumns/BuildDurationColumn.java
 src/main/java/jenkins/plugins/extracolumns/DescriptionColumn.java
 src/main/resources/jenkins/plugins/extracolumns/BuildDescriptionColumn/config.jelly
 src/main/resources/jenkins/plugins/extracolumns/DescriptionColumn/config.jelly
http://jenkins-ci.org/commit/extra-columns-plugin/17388893c69bee63f1002f6ba7550d922dbec06e
Log:
  JENKINS-21295 - Project Description column configs for trim and width
not correctly redisplaying





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream















































Steve Roth
 commented on  JENKINS-21905


intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream















Forgot to mention, we are seeing this even in the latest Jenkins version (1.551)



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-20913) [jar caching] - winp.x64.dll access conflicts













































  
Kishore Redlapalli
 edited a comment on  JENKINS-20913


[jar caching] - winp.x64.dll access conflicts
















We are seeing this on win8/8.1 slaves once in a week!!
slave.jar crashes with the above error
we are on Jenkins LTS 1.532.1 running on CentOs6.5
also, at the end of each job, the above issue occurs everytime!!



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-20913) [jar caching] - winp.x64.dll access conflicts