date:20140202

[JIRA] [ant] (JENKINS-16549) When using ant build step, artifact links in build properties are broken

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
















































evernat
 resolved  JENKINS-16549 as Cannot Reproduce


When using ant build step, artifact links in build properties are broken
















ok, thanks





Change By:


evernat
(03/Feb/14 7:54 AM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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







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

[JIRA] [ant] (JENKINS-16549) When using ant build step, artifact links in build properties are broken

2014-02-02 Thread asid...@gmail.com (JIRA)















































Denis Syrokvash
 commented on  JENKINS-16549


When using ant build step, artifact links in build properties are broken















looks, like i can't reproduce it any more (using jenkinks v1.549, ant plugin v1.2)



























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







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

[JIRA] [integrity-plugin] (JENKINS-21587) memory leak in Plugin 1.22 -orphaned Logger Threads

2014-02-02 Thread matthias.r...@miele.de (JIRA)















































Matthias Rump
 reopened  JENKINS-21587


memory leak in Plugin 1.22 -orphaned Logger Threads
















see last comment





Change By:


Matthias Rump
(03/Feb/14 7:38 AM)




Resolution:


Won't Fix





Status:


Resolved
Reopened



























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







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

[JIRA] [integrity-plugin] (JENKINS-21587) memory leak in Plugin 1.22 -orphaned Logger Threads

2014-02-02 Thread matthias.r...@miele.de (JIRA)















































Matthias Rump
 commented on  JENKINS-21587


memory leak in Plugin 1.22 -orphaned Logger Threads















Hi Cletus,

Yes, the threads are are in the integrity client's VM, NOT in Jenkins, so you're right, the plugin itself does not have the problem. 
But nevertheless the plugin seems to be the course of this issue, as we did not see this number of daemon threads on the same client, same API, with plugin version 1.18.

So what's you proposal?

	connecting the plugin directly to the Server and keeping my fingers crossed it won't kill my production system?




	schedule a restart of my integration server client every hour?




	stepping back to plugin version 1.18 (with all other known issues)?





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)

2014-02-02 Thread roge...@java.net (JIRA)

rogerhu
commented on JENKINS-21016

Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)

The problem is upon configuring a job using an HTTP-based URL with Git credentials, the plug-in attempts to do form validation and verify whether the HTTP authentication succeeded. Because of the recent updates to store this info as a temporary store so that subsequent Git commands will succeed with these credentials, the validation can fail in the absence of a workspace directory.

In other words, the warning message "Failed to connect to repository : Command "git config --local credential.helper store" appears and can be ignored, but it's a false alarm. The job will fetch correctly if ran.

For instance, if Jenkins was started from the / dir, then git will attempt to access .git/config from the root directory, resulting in permissions denied.

Should the creation of the local credential simply just not be done in the absence of a workspace directory? See:

https://github.com/jenkinsci/git-client-plugin/pull/97

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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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.

62 matches

Mail list logo