[JIRA] [subversion] (JENKINS-22199) Jenkins throwing errors in SCM Polling and Updates with Subversion
Cees Bos commented on JENKINS-22199 Jenkins throwing errors in SCM Polling and Updates with Subversion When is the next release of the subversion-plugin expected? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodeofflinenotification] (JENKINS-20720) Jenkins fails to connect to slave via ssh after nodeofflinenotification plugin
Wilder Rodrigues assigned JENKINS-20720 to Wilder Rodrigues Jenkins fails to connect to slave via ssh after nodeofflinenotification plugin Change By: Wilder Rodrigues (01/Apr/14 6:19 AM) Assignee: WilderRodrigues This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodeofflinenotification] (JENKINS-20720) Jenkins fails to connect to slave via ssh after nodeofflinenotification plugin
Wilder Rodrigues commented on JENKINS-20720 Jenkins fails to connect to slave via ssh after nodeofflinenotification plugin I'm suffering of the same problem. Since I'm already maintainer of the reverse proxy auth plugin, I will also take care of this one. The issue is opened since November 2013: it seems the guys are running out of time to fix it. Cheers, Wilder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-16429) ComThread is leaking even when its peer is dead
Dennys Hsieh commented on JENKINS-16429 ComThread is leaking even when its peer is dead I just upgrade to active directory plugin 1.36 with com4j 2.1 It seems the leak issue is not fixed yet. But my groovy script runs every 60mins, I'm not sure will the new com4j clear the leak thread in batch or any dependency? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-21906) NumberFormatException occurs when accessing the JSON api
Moosh Ben
reopened JENKINS-21906
NumberFormatException occurs when accessing the JSON api
NumberFormatException is fixed in 2.0.4 but entry change date is not retrieved.
Using the following groovy code:
def thr = Thread.currentThread();
def currentBuild = thr?.executable;
def changes = currentBuild.getChangeSet();
changes.getItems().each {
ChangeLogSet.Entry lastChange = (ChangeLogSet.Entry)it;
lastChange.getTimestamp();
}
Produces a wrong timestamp (0).
Reverting to git plugin 2.0.1 fixes the issue.
Change By:
Moosh Ben
(01/Apr/14 6:38 AM)
Resolution:
Fixed
Status:
Resolved
Reopened
Assignee:
NicolasDeLoof
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-16732) Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Guy Rozendorn
commented on JENKINS-16732
Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Applying the following patch over v1.7.0 seems to solve it:
diff --git i/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java w/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
index 82598d2..8526e4c 100644
--- i/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
+++ w/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
@@ -152,7 +152,7 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
this.gitExe = gitExe;
this.environment = environment;
-launcher = new LocalLauncher(IGitAPI.verbose?listener:TaskListener.NULL);
+launcher = new LocalLauncher(listener);
}
public GitClient subGit(String subdir) {
@@ -1855,7 +1855,7 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
}
}
if(shouldProxy) {
-final HttpHost proxyHost = new HttpHost(proxy.name, proxy.port);
+final HttpHost proxyHost = new HttpHost(proxy.name, proxy.port);
final HttpRoutePlanner routePlanner = new DefaultProxyRoutePlanner(proxyHost);
clientBuilder.setRoutePlanner(routePlanner);
if (proxy.getUserName() != null proxy.getPassword() != null)
@@ -1896,7 +1896,7 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
try {
for (String candidate : candidates) {
HttpGet get = new HttpGet(candidate);
-
+
final CloseableHttpResponse response = client.execute(get);
try{
status = response.getStatusLine().getStatusCode();
Although we've been running this build only for a day now.
I'll report back if it still happens
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Daniel Just installed https://jenkins.ci.cloudbees.com/job/plugins/job/subversion-plugin/336/org.jenkins-ci.plugins$subversion/ and removed ~/.subversion that contains "static credentials" added by using jsvn. And got the issue again on externals : Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed Re-added credentials by doing a "jsvn info $REPO", and then post-commit works again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vs-code-metrics] (JENKINS-21848) CyclomaticComplexity/LineOfCodes always 0 if library contains enumeration
Kris P commented on JENKINS-21848 CyclomaticComplexity/LineOfCodes always 0 if library contains enumeration Here is the content for one of those Enums: Type Name="SomeEnumType" Metrics Metric Name="MaintainabilityIndex" Value="100" / Metric Name="CyclomaticComplexity" Value="0" / Metric Name="ClassCoupling" Value="0" / Metric Name="DepthOfInheritance" Value="1" / Metric Name="LinesOfCode" Value="0" / /Metrics Members / /Type .pdb file is in the same folder with the dll-file, no warnings or errors while running "Microsoft Visual Studio 10.0\Team Tools\Static Analysis Tools\FxCop\Metrics.exe" Any advices how to produce more possible helpfull logs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21257) up link of downstream job from multiconfig job is going nowhere
Derk-Jan Hartman resolved JENKINS-21257 as Fixed up link of downstream job from multiconfig job is going nowhere Change By: Derk-Jan Hartman (01/Apr/14 7:59 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Richard Bergoin: Not sure how many of the preceding comments you read, but please note that this fix simply adds support for "additional credentials" in some code paths that used no credentials at all. You'll still need to define credentials for the explicitly defined modules, you'll still need to add "additional credentials" in case of externals, even within the same repos as your other modules , and you need to specify the correct realm for those so they are considered at all during authentication. If you read and understood all of the previous comments to this issue, and followed the instructions, but the problem still occurs, please post the entire stack trace, including all the "Caused by" sections. The error message alone is useless. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-22351) Authentication error during assembly.(svn: E200015)
René Charbonneau commented on JENKINS-22351 Authentication error during assembly.(svn: E200015) We are facing this issue too. I also found this thread at stackoverflow: http://stackoverflow.com/questions/22068297/jenkins-subversion-error-e200015-no-credential-to-try-authentication-failed So it seems to be a problem of the svn plugin. Kind Regards René This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Daniel, thanks for reply, here is the log, and the CredentialsSVNAuthenticationProviderImpl logger output make me think that the credentials used for the externals are the one used for the main module (no additional module configured, as you said) : Apr 01, 2014 9:24:45 AM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl Attempting auth for URL: https://svn.company.com/repo/tags/project-1.0; Realm: https://svn.company.com:443 SVN repository Apr 01, 2014 9:24:45 AM WARNING hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl onNotify Failed to handle Subversion commit notification org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /repo/tags/project-1.0 failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getRepositoryUUID(DAVRepository.java:148) at hudson.scm.SubversionSCM$ModuleLocation.getUUID(SubversionSCM.java:2712) at hudson.scm.SubversionRepositoryStatus$JobTriggerListenerImpl.onNotify(SubversionRepositoryStatus.java:202) at hudson.scm.SubversionRepositoryStatus.doNotifyCommit(SubversionRepositoryStatus.java:136) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.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$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$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.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
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck
commented on JENKINS-21785
Check for changes in folders linked via svn:externals fails due to missing credentials
Richard: To clarify, you have one module configured, and no additional credentials? If so, you simply need to do that; externals only have "additional credentials" to work with, even when in the same repo! That log message I added to assist in determining the "realm" to enter, as some users expressed confusion about how that works.
Just add an "additional credential", use {{https://svn.company.com:443 SVN repository}} for the realm, and choose whatever credential is appropriate for that repo, could be the same as for the configured module.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Richard: To clarify, you have one module configured, and no additional credentials? If so, you simply need to do that; externals only have "additional credentials" to work with, even when in the same repo! That log message I added to assist in determining the "realm" to enter, as some users expressed confusion about how that works. Just add an "additional credential", use https://svn.company.com:443 SVN repository for the realm, and choose whatever credential is appropriate for that repo, could be the same as for the configured module. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials To clarify, you have one module configured, and no additional credentials? : yes. The realm for the external is (I think) the same that the realm of the "main" module, for exemple, an app have an external to a library tag : https://svn.company.com/app/trunk have https://svn.company.com/lib/tags/project-1.0 as externals Shouldn't main module credentials be applied, as both realms are "https://svn.company.com:443 SVN 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/d/optout.
Kristian Karl sent you an invitation
Kristian Karl sent you an invitation Twitter helps you stay connected with what's happening right now and with the people and organizations you care about. Accept invitation https://twitter.com/i/ffe2ba34-c8f1-4a2f-97ce-dfb00f37cf16 -- You can unsubscribe from receiving email notifications from Twitter at anytime. For general inquiries, please visit us at Twitter Support. Unsubscribe: https://twitter.com/i/o?t=1iid=09fbc1ea189c431a83d4497be769c16auid=0c=XbvOYkiBHRUMunayh%2FA%2Bi%2B3SnbNiCHROsUofR6FuFVxgKJ5ZXFGd2Q%3D%3Dnid=9+26 Need help? https://support.twitter.com -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fortify360] (JENKINS-21332) Fortify Upload does not work in Jenkins = 1.519
Maurits Rijk commented on JENKINS-21332 Fortify Upload does not work in Jenkins = 1.519 Work-around I used: unpack the classes.jar in WEB-INF/classes chmod 550 ./classes This makes sure that during Jenkins start the classes folder isn't removed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
michael soukup commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Shouldn't main module credentials be applied, as both realms are "https://svn.company.com:443 SVN repository" ? should But ain't: comment-195699 this is why there exists this bug entry after all... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Richard: Should it? Possibly. Does it? No. Which many of the preceding comments mention (e.g. 1 2 3 4). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [javadoc] (JENKINS-22443) Jenkins Linux Master not connecting to Windows Slave using the Fitnesse Plugin
Tony Sidhu created JENKINS-22443 Jenkins Linux Master not connecting to Windows Slave using the Fitnesse Plugin Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: javadoc, windows-slaves Created: 01/Apr/14 10:55 AM Description: The master slave connection is running, but when i try to run a job using the Fitnesse plugin and specify the Fitnesse Host as 'localhost' if fails to connect, even though in the Slave config I have specified a HOST_NAME as the servers FQDN. However if I change the 'localhost' value on the job to the FQDN name it will connect and run the job. I need to use the 'localhost' value so that my job can connect to the next available slave, in my scenario i'm using 4 slaves, so i do not want my jobs to be bound to 1 slave. This was not an issue in JAVA 1.6.0_b45, however i did downgrade to this version but this feature no longer works, any assistance would be appreciated, i have exhausted google for an answer. Due Date: 04/Apr/14 12:00 AM Environment: Ubuntu 12.04 Linux Master Windows 2008 R2 Slaves environment Java 1.7.0_u51 on master and slave Fix Versions: current Project: Jenkins Priority: Major Reporter: Tony Sidhu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [update-center] (JENKINS-22162) no GUI update option for snapshot builds of Jenkins
steve steve resolved JENKINS-22162 as Not A Defect no GUI update option for snapshot builds of Jenkins Ok this is def on our side of things. the button for 1.557 just showed up. Although the manual update check still never finishes. but that is not a jenkins issue then but rather related to our network settings I guess. consider this fixed. Change By: steve steve (01/Apr/14 10:55 AM) Status: Open Resolved Fix Version/s: current Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clover] (JENKINS-22444) Update Clover plugin to use Clover Core 3.3.0
Marek Parfianowicz started work on JENKINS-22444 Update Clover plugin to use Clover Core 3.3.0 Change By: Marek Parfianowicz (01/Apr/14 11:49 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clover] (JENKINS-22444) Update Clover plugin to use Clover Core 3.3.0
Marek Parfianowicz created JENKINS-22444 Update Clover plugin to use Clover Core 3.3.0 Issue Type: Improvement Assignee: Marek Parfianowicz Components: clover Created: 01/Apr/14 11:49 AM Project: Jenkins Priority: Minor Reporter: Marek Parfianowicz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-20273) Aborting the master job should abort all the downstream
Sebastian Schuberth commented on JENKINS-20273 Aborting the master job should abort all the downstream @Nickolay: The symptoms are the same, but I believe the issues need to be solved independently as they appear in different components / plugins, so they are not duplicates in the strict sense. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-11257) Stopping a parent job doesn't stop the triggered child jobs
Sebastian Schuberth commented on JENKINS-11257 Stopping a parent job doesnt stop the triggered child jobs Is there any way to work around this, e.g. by using some Groovy scripting? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clover] (JENKINS-22444) Update Clover plugin to use Clover Core 3.3.0
SCM/JIRA link daemon commented on JENKINS-22444 Update Clover plugin to use Clover Core 3.3.0 Code changed in jenkins User: Marek Parfianowicz Path: pom.xml http://jenkins-ci.org/commit/clover-plugin/573ed2246f37eaba9029c78af6a9ac7a954db0bf Log: JENKINS-22444: updating Clover version number Compare: https://github.com/jenkinsci/clover-plugin/compare/a9861aea4f70...573ed2246f37 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clover] (JENKINS-22444) Update Clover plugin to use Clover Core 3.3.0
SCM/JIRA link daemon commented on JENKINS-22444 Update Clover plugin to use Clover Core 3.3.0 Code changed in jenkins User: mparfianowicz Path: pom.xml http://jenkins-ci.org/commit/clover-plugin/1190fd3f1724c6576e4c7431cdf4f070e2abd618 Log: JENKINS-22444: updating Clover plugin to use Clover Core version 3.3.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I was thinking the PR 70 will solve this issue (I misundertood the log and think that it inform the "realm" which will be used to the connection). I can test this issue (as previously with PR 74), if the "possibly" can be assume to be "yes" (but who can decide of this...). From my point of view, credentials are "server based" for continuous, but it could be "repository based" (subpath of a server). Maybe a "FINE" logging of username used to connect to a repository can be interesting (for debugging purpose). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Jens Rosenthal commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Richard: I believe that the credentials have to be "repository based"... Just think of a huge company with many project teams and a fine grained access control for all the repositories hosted on one (or more) SVN server(s). Matching the URL (of the external) - e.g. https://svn.server.company:443/reporoot/repo/my/external - against a realm string - e.g. https://svn.server.company:443/reporoot/repo - might well suffice for this to work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
davida2009 commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I am running Jenkins 1.552 on a Linux master. I have installed svn plugin '2.3-SNAPSHOT(private-03/31/2-14 18:05-jenkins'. I have a job that runs on a Windows slave that polls a svn repo and does a Visual Studio C++ build if a change is detected. The svn repo has an external link to another svn repo. I have specified an 'additional credential' for the external (I believe correctly). Jenkins gives the following exception when I commit a change to the external repo and run the Jenkins job: Apr 01, 2014 1:36:42 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluateCaught exception evaluating: it.transientActions in /jenkins/job/Zodiac_VS2010_Osiris_TI/110/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
Sebastian Schuberth commented on JENKINS-21547 Add information to console log when a job is aborted by gerrit FYI, I've created a PR 1 about the wording of the "Build Current Patches Only" option. 1 https://github.com/jenkinsci/gerrit-trigger-plugin/pull/140 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-13593) Seems to not handle having builds in seperate folder
Matthew Firtion commented on JENKINS-13593 Seems to not handle having builds in seperate folder This also affects Jenkins 1.520 with SCM Sync Config 0.0.7.3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-16429) ComThread is leaking even when its peer is dead
Frank Seifart edited a comment on JENKINS-16429 ComThread is leaking even when its peer is dead It seems that the issue is not fixed completely. Now the number of threads are ok, but java memory usage is excessively high and rises constantly as before. I think there is a remaining memory leak. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-16429) ComThread is leaking even when its peer is dead
Frank Seifart commented on JENKINS-16429 ComThread is leaking even when its peer is dead It seems that the issue is not fixed completely. Now the number of threads are ok, but java memory usage is excesively high rises constantly as before. I think there is a remaining memory leak. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vs-code-metrics] (JENKINS-21848) CyclomaticComplexity/LineOfCodes always 0 if library contains enumeration
Yasuyuki Saito commented on JENKINS-21848 CyclomaticComplexity/LineOfCodes always 0 if library contains enumeration Do you know the cyclomatic complexity of Module and Namespace that contains the enumeration in the file? if cyclomatic complexity is 0, there is a possibility of failure of Metrics.exe. Otherwise, it is a bug in the plug-in. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22413) Does not work a functionality of job creation , because occurred the ArrayIndexOutOfBoundsException.
Kazuki Shimizu commented on JENKINS-22413 Does not work a functionality of job creation , because occurred the ArrayIndexOutOfBoundsException. Creation of new job succeed on version 1.557. Thank you fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
Sagi Sinai-Glazer commented on JENKINS-21547 Add information to console log when a job is aborted by gerrit @rin_ne - if your pull request was already merged (20.3.2014) - then why is this ticket not yet resolved? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs] (JENKINS-22445) Creating workspace does not work if Update is checked
Karl-Heinz Marbaise created JENKINS-22445 Creating workspace does not work if Update is checked Issue Type: Bug Affects Versions: current Assignee: redsolo Components: tfs Created: 01/Apr/14 1:42 PM Description: The problem arises if i check the checkbox Update for the TFS plugin and let the build run the first time. It will fail cause the workspace has not been created yet. If you uncheck the checkbox and do the first run it will create the workspace. Afterwards i need to check the checkbox back. Project: Jenkins Priority: Major Reporter: Karl-Heinz Marbaise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs] (JENKINS-22446) Get the branch name into environment variable.
Karl-Heinz Marbaise created JENKINS-22446 Get the branch name into environment variable. Issue Type: Improvement Affects Versions: current Assignee: redsolo Components: tfs Created: 01/Apr/14 1:51 PM Description: It would be nice having the branch name be provided into an environment variable. Project: Jenkins Priority: Minor Reporter: Karl-Heinz Marbaise This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-755) Default JDK meaning in project options is confusing.
Vladimir Kralik commented on JENKINS-755 Default JDK meaning in project options is confusing. I think, that the "Default" is good option, because I have a lot of projects with standard configuration and only several project with different JDK requirement. Depending on JDK installed on system is not a good idea, because on different systems ( slaves ) could be different JDK installed, so I could get different results. There should be "rule" which says : "The first one JDK in configuration is default." And would be nice to have possibility change order via drag-n-drop. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Christoph Vogtländer edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Daniel Beck: Using the new snapshot (PR74/Build 336) fixed the problem for me. At least using your script test code posted in 1 and 2. Tested the scripts with the snapshot from PR70 to confirm failure. The test with PR74 now succeedes. Also successfully tested with "real" commit hook notification. There are no trace messages left in the log and jobs are triggered correctly. Thanks a lot for your help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
rin_ne commented on JENKINS-21547 Add information to console log when a job is aborted by gerrit Sagi, I don't know workflow on Jenkins JIRA. You mean issue should be closed by developer? Please tell me the correct flow on this JIRA. In my community, issue reporter can only close issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
rin_ne edited a comment on JENKINS-21547 Add information to console log when a job is aborted by gerrit Sagi, I don't know workflow on Jenkins JIRA. You mean issue should be closed by resolver? If so, who should verify that reporter issue is fixed? Please tell me the correct flow on this JIRA. In my community, issue reporter can only close issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
K Rehman assigned JENKINS-21643 to K Rehman Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Change By: K Rehman (01/Apr/14 2:01 PM) Assignee: GregPeters KRehman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [update-center] (JENKINS-22162) no GUI update option for snapshot builds of Jenkins
Daniel Beck commented on JENKINS-22162 no GUI update option for snapshot builds of Jenkins This pages (oddly) uses your web browser to download the update center. If you have tight control over _javascript_, AJAX, ... or a broken proxy, DNS, ... then this won't work, true. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
K Rehman commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Finally got around to testing this again on 2 different environments - one with WAS on Windows 7 and another with WAS on AIX, but with same result. I can telnet into both the soap connector port and the WAS admin port. It seems to be failing with the api calls Currently get this failure message: Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- XXX-1.0-SNAPSHOT.war --- Generating EAR For New Artifact: XXX-1.0-SNAPSHOT Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Could not determine if artifact XXX-1.0-SNAPSHOT' is installed: ADMA0089E: The AppManagement MBean is not found. at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.isArtifactInstalled(WebSphereDeploymentService.java:204) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.stopArtifact(WebSphereDeployerPlugin.java:211) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.perform(WebSphereDeployerPlugin.java:169) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1007) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1628) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:506) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:247) Build step 'Deploy To IBM WebSphere Application Server' changed build result to FAILURE Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
K Rehman updated JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) Change By: K Rehman (01/Apr/14 2:07 PM) Assignee: KRehman GregPeters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Richard Bergoin commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Jens, Ok for repo base credentials, in fact this is also that we have, I would add a "global credentials" to not have to reconfigure each jobs using this external (more than 30), but the global credentials is domain based (e.g. hostname, so only one global credential for svn.company.com) Note that we also have CI for our internal libraries, so the credentials are already entered in another job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-22190) Changelog only shows changes in externals
Rene Affourtit updated JENKINS-22190 Changelog only shows changes in externals Change By: Rene Affourtit (01/Apr/14 2:06 PM) 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/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
rin_ne resolved JENKINS-21547 as Fixed Add information to console log when a job is aborted by gerrit Sorry, I misunderstand workflow. This issue is fixed. Please verify then close it if OK. Change By: rin_ne (01/Apr/14 2:10 PM) Status: Open Resolved Assignee: JakubCzaplicki Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
Greg Peters commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) @Rehman I had another user have an issue where they were getting this error. If you are using WAS ND, point the plugin the deployment manager and see if that fixes your issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Richard: It may be possible, but it's not currently implemented this way (admittedly, the current solution seems a bit weird). If PR70+PR74 work, then only an issue of convenience / redundancy in configuration is left. David: The error seems to be completely unrelated. I suggest you open a new issue for that. Anyone able to confirm that PR74 works? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
michael soukup commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Richard: you can use the same method that I used to reconfigure our 20+ jobs: edit the xml files directly and restart the server as described in comment-196380 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-16429) ComThread is leaking even when its peer is dead
Jesse Glick updated JENKINS-16429 ComThread is leaking even when its peer is dead Change By: Jesse Glick (01/Apr/14 2:17 PM) Labels: active_directory,comthread outofmemoryerrorthreadswindowswinstone This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clover] (JENKINS-22444) Update Clover plugin to use Clover Core 3.3.0
Marek Parfianowicz resolved JENKINS-22444 as Fixed Update Clover plugin to use Clover Core 3.3.0 Change By: Marek Parfianowicz (01/Apr/14 2:24 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clover] (JENKINS-22444) Update Clover plugin to use Clover Core 3.3.0
Marek Parfianowicz commented on JENKINS-22444 Update Clover plugin to use Clover Core 3.3.0 http://maven.jenkins-ci.org/content/repositories/releases/org/jenkins-ci/plugins/clover/4.3.0/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Mike Penz commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I've also installed the snapshot plugin, i've also set the additional credentials, without any luck. As soon as there's a change in one of the externals it fails. hudson.util.IOException2: revision check failed on http://server/svn/repo/... at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:739) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:900) at hudson.model.AbstractProject.checkout(AbstractProject.java:1320) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1688) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/repo/... failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:177) ... 11 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 29 more we checkout two modules each with their own credentials http://server/svn/repo/folder1... with credentials1 http://server/svn/repo/folder2... with credentials1 and i add additional credentials with realm http://server/svn/repo with credentials1 i've also tried additional credentials with realm http://server/ with credentials1 (the credentials1 are all the same) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] [ivy] (JENKINS-22447) Ivy Job builds don't release workspace lock due to override of cleanup
Kevin Formsma created JENKINS-22447 Ivy Job builds dont release workspace lock due to override of cleanup Issue Type: Bug Assignee: Timothy Bingaman Components: ivy Created: 01/Apr/14 2:27 PM Description: The fix for https://issues.jenkins-ci.org/browse/JENKINS-10615 caused the Ivy plugin to not release workspace locks. This causes an additional workspace to be created for each Ivy job execution until Jenkins is restarted. This is because IvyBuild.java has a AbstractRunner implementation that overrides cleanUp which causes the workspace lease to not be released. Project: Jenkins Labels: ivy Priority: Critical Reporter: Kevin Formsma This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18364) Optimize creation of relative links to jobs
Jesse Glick started work on JENKINS-18364 Optimize creation of relative links to jobs Change By: Jesse Glick (01/Apr/14 2:31 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18364) Optimize creation of relative links to jobs
Jesse Glick assigned JENKINS-18364 to Jesse Glick Optimize creation of relative links to jobs Change By: Jesse Glick (01/Apr/14 2:31 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
michael soukup commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @~Mike Penz make sure you entered the realm as described in comment-197898 and comment-196458, not only the url of the repository - it should work for you, too. https://svn.company.com:443 SVN 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/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-18457) Comment Added gerrit trigger doesn't work
rin_ne resolved JENKINS-18457 as Fixed Comment Added gerrit trigger doesnt work Seems this issue is already fixed. Change default label string Add Tips Tricks to plugin page. Change By: rin_ne (01/Apr/14 2:42 PM) Status: Open Resolved Assignee: rsandell OrgadShaneh Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
michael soukup edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Mike Penz make sure you entered the realm as described in comment-197898 and comment-196458, not only the url of the repository - it should work for you, too. https://svn.company.com:443 SVN 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/d/optout.
[JIRA] [ivy] (JENKINS-22447) Ivy Job builds don't release workspace lock due to override of cleanup
Kevin Formsma updated JENKINS-22447 Ivy Job builds dont release workspace lock due to override of cleanup Change By: Kevin Formsma (01/Apr/14 2:43 PM) Description: Thefixforhttps://issues.jenkins-ci.org/browse/JENKINS-10615causedtheIvyplugintonotreleaseworkspacelocks.ThiscausesanadditionalworkspacetobecreatedforeachIvyjobexecutionuntilJenkinsisrestarted.ThisisbecauseIvyBuild.java andIvyModuleSetBuild.java hasaAbstractRunnerimplementationthatoverridescleanUpwhichcausestheworkspaceleasetonotbereleased. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-18391) Gerrit Version is null after upgrade to 2.10.1
rin_ne resolved JENKINS-18391 as Fixed Gerrit Version is null after upgrade to 2.10.1 This issue is already fixed. Please verify with 2.11.x. Change By: rin_ne (01/Apr/14 2:36 PM) Status: Open Resolved Assignee: rsandell teilo Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Mike Penz edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials I've also installed the snapshot plugin, i've also set the additional credentials, without any luck. As soon as there's a change in one of the externals it fails. hudson.util.IOException2: revision check failed on http://server/svn/repo/... at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:739) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:900) at hudson.model.AbstractProject.checkout(AbstractProject.java:1320) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1688) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /svn/repo/... failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:177) ... 11 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 29 more we checkout two modules each with their own credentials http://server/svn/repo/folder1... with credentials1 http://server/svn/repo/folder2... with credentials1 and i add additional credentials with realm http://server/svn/repo with credentials1 i've also tried additional credentials with realm http://server/ with credentials1 (the credentials1 are all the same) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] [core] (JENKINS-18364) Optimize creation of relative links to jobs
Jesse Glick updated JENKINS-18364 Optimize creation of relative links to jobs Change By: Jesse Glick (01/Apr/14 2:50 PM) Labels: lts-candidate performance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-22346) jenkins cli command with key fails with - java.io.EOFException
Eric Helgeson commented on JENKINS-22346 jenkins cli command with key fails with - java.io.EOFException This worked as recently as 1.555. Broken in 1.556 1.557 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22448) Jenkins Error CA Certificate
TJ Bryant created JENKINS-22448 Jenkins Error CA Certificate Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 01/Apr/14 3:09 PM Description: I am trying to start jenkins using a CA signed certificate but I am getting this error Running from: /usr/lib/jenkins/jenkins.war Apr 01, 2014 9:56:01 AM winstone.Logger logInternal INFO: Winstone shutdown successfully Apr 01, 2014 9:56:01 AM winstone.Logger logInternal SEVERE: Container startup failed java.io.IOException: Failed to start a listener: winstone.HttpsConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.init(Launcher.java:149) at winstone.Launcher.main(Launcher.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at Main._main(Main.java:293) at Main.main(Main.java:98) Caused by: java.io.IOException: DerValue.getBigInteger, not an int 48 at sun.security.util.DerValue.getBigInteger(DerValue.java:511) at winstone.HttpsConnectorFactory.readPEMRSAPrivateKey(HttpsConnectorFactory.java:171) at winstone.HttpsConnectorFactory.start(HttpsConnectorFactory.java:90) at winstone.Launcher.spawnListener(Launcher.java:207) ... 8 more Open ssl was used to generate the key and csr, then the CA gave us back the cert. What could be causing this error? JENKINS_ARGS="--httpsCertificate=/var/lib/jenkins/cert/cci-jenkins_uncc_edu_cert.cer --httpsPrivateKey=/var/lib/jenkins/cert/cci-jenkins.key" Environment: Redhat Linux Project: Jenkins Priority: Major Reporter: TJ Bryant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Mike Penz commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @michael soukup Ok i was now able to solve it too. You were right that you have to define the realm including the brackets and the name. i always thought it should work if you just define https://svn.company.com:443 Thanks for the help any solution how to define this as default? we have 100+ builds and almost each of those has externals. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Mike Penz edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @michael soukup Ok i was now able to solve it too. You were right that you have to define the realm including the brackets and the name. i always thought it should work if you just define https://svn.company.com:443 Thanks for the help any solution how to define this as default? we have 100+ builds and almost each of those has externals. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Mike Penz edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials michael soukup Ok i was now able to solve it too. You were right that you have to define the realm including the brackets and the name. i always thought it should work if you just define https://svn.company.com:443 Thanks for the help any solution how to define this as default? we have 100+ builds and almost each of those has externals. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
davida2009 commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Hi Daniel Sorry, I pasted in the wrong exception. I really am getting one relevant to this issue (see below). I am running your snapshot. The exception is random - sometimes the update succeeds, sometimes it doesn't. This time I used a clean workspace, to clear any cached credentials. David At revision 1231 At revision 5573 no change for https://172.29.68.12/subversion/zodiac/trunk since the previous build hudson.util.IOException2: revision check failed on https://172.29.68.12/subversion/Osiris/trunk/Source/Osiris/include at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:739) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:900) at hudson.model.AbstractProject.checkout(AbstractProject.java:1320) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:518) at hudson.model.Run.execute(Run.java:1688) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /subversion/Osiris/trunk/Source/Osiris/include failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:177) ... 11 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 29 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you
[JIRA] [core] (JENKINS-18364) Optimize creation of relative links to jobs
SCM/JIRA link daemon commented on JENKINS-18364 Optimize creation of relative links to jobs Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/Functions.java core/src/test/java/hudson/FunctionsTest.java http://jenkins-ci.org/commit/jenkins/bcc86148561ad9ab4a0365ff00d28ff7ee71d57c Log: FIXED JENKINS-18364 Functions.getRelativeLinkTo is called many times during rendering, so skip checking View.getItems which is expensive. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18364) Optimize creation of relative links to jobs
SCM/JIRA link daemon resolved JENKINS-18364 as Fixed Optimize creation of relative links to jobs Change By: SCM/JIRA link daemon (01/Apr/14 3:36 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vstestrunner] (JENKINS-22450) Make trx and coverage files paths available to further build steps in VSTestRunner plugin
Alexander Filatov created JENKINS-22450 Make trx and coverage files paths available to further build steps in VSTestRunner plugin Issue Type: Improvement Assignee: Unassigned Components: vstestrunner Created: 01/Apr/14 3:53 PM Description: There is no convenient way to specify output files for vstest.console.exe. The application generates arbitrary output names for every run like: Results File: D:\Projects\Component\TestResults\username_MACHINENAME 2014-03-31 18_27_07.trx Attachments: D:\Projects\Component\TestResults\e78e4dbd-5664-44de-a32b-91c312c1f7ad\username_MACHINENAME 2014-03-31 18_26_52.coverage It will be fine to make those file paths available for next build steps. Project: Jenkins Labels: vstest.console.exe vstestrunner Priority: Major Reporter: Alexander Filatov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Mike Penz commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials davida2009 ok it seems you have the exact same issue we had. Try to add additinal credentials. It's really important that you use the correct realm. The realm in our case is "http://server:port SVN Server Name" -- without " After migrating to the new subversion plugin the name of the old credentials was automatically set to the realm of the svn server try to using this one. our automatically upgraded credentials had a name like "buildmaster/** (http://server:port SVN Server Name)" just remove the stuff before and the brackets. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay] (JENKINS-22449) Stripes in progress bar broken on Chromium 22.x
Bjoern Kimminich created JENKINS-22449 Stripes in progress bar broken on Chromium 22.x Issue Type: Bug Affects Versions: current Assignee: Christian Pelster Attachments: IMG_20140401_174301.jpg Components: walldisplay Created: 01/Apr/14 3:48 PM Description: As seen on attached photo the gradient effect for the progress-stripes of running jobs is broken in Chromium on Raspbian. Environment: Chromium Browser 22.x for Linux (on Raspberry Pi with Raspbian) Project: Jenkins Priority: Minor Reporter: Bjoern Kimminich This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13323) Renaming a node does not update associated projects
evernat resolved JENKINS-13323 as Incomplete Renaming a node does not update associated projects No response from the reporter, so resolving as incomplete. Change By: evernat (01/Apr/14 3:57 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-22199) Jenkins throwing errors in SCM Polling and Updates with Subversion
kutzi commented on JENKINS-22199 Jenkins throwing errors in SCM Polling and Updates with Subversion Whenever someone feels like releasing 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/d/optout.
[JIRA] [core] (JENKINS-17424) SEVERE: Failed Loading plugin nodeofflinenotification and SEVERE: Failed Loading plugin pathignore
evernat resolved JENKINS-17424 as Duplicate SEVERE: Failed Loading plugin nodeofflinenotification and SEVERE: Failed Loading plugin pathignore resolved as duplicate Change By: evernat (01/Apr/14 4:06 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
davida2009 commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Mike, thanks for your help. I have specified 'additional credentials'. However, until today I had specified a realm of: CollabNet Subversion Repository which we got from our server configuration. Today I added the url: https://snip/subversion:443 CollabNet Subversion Repository but that made no difference. I still get the exception. Unfortunately there seems to be no documentation in Jenkins about this. Until recently I was completely unaware of the concept of 'realm' in Subversion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17426) I get a lot of those WARNING: Skipping a non-existent field onlyCopyClaimOnSimilarError
evernat resolved JENKINS-17426 as Not A Defect I get a lot of those WARNING: Skipping a non-existent field onlyCopyClaimOnSimilarError This is just a warning about old data from a previous version of a plugin. You can ignore it. Or you can use Manage old data / Discard old data in the "Administer Jenkins" page. Change By: evernat (01/Apr/14 4:04 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17423) Exception on start up: SEVERE: An exception occurred during processing of the org.apache.wink.server.internal.providers.entity.html.HtmlProvider class. This class is igno
evernat resolved JENKINS-17423 as Duplicate Exception on start up: SEVERE: An exception occurred during processing of the org.apache.wink.server.internal.providers.entity.html.HtmlProvider class. This class is ignored. This is a duplicate of https://marvelution.atlassian.net/browse/MARVJIRAHUDSON-296 Mark Reveld said to ignore it: https://marvelution.atlassian.net/browse/MARVJIRAHUDSON-296?focusedCommentId=13692page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13692 Change By: evernat (01/Apr/14 4:20 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials davida: Skip the local path /subversion. Search through my older comments, there's several ways described how you can find out the realm. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
mike bayer commented on JENKINS-20769 Failed to execute command Pipe.EOF just to update, I'm running "Jenkins ver. 1.558-SNAPSHOT (rc-04/01/2014 04:22 GMT-kohsuke)" which I assume includes this fix, I now see this in my logs: SEVERE: Failed to execute command Pipe.Flush(10) (channel general (i-34cf7b17)) java.lang.ClassCastException: java.io.OutputStreamWriter cannot be cast to java.io.OutputStream at hudson.remoting.ProxyWriter$Flush.execute(ProxyWriter.java:285) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Apr 01, 2014 3:55:54 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Apr 01, 2014 3:57:13 PM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.Flush(10) (channel general (i-6ac87c49)) java.lang.ClassCastException: java.io.OutputStreamWriter cannot be cast to java.io.OutputStream at hudson.remoting.ProxyWriter$Flush.execute(ProxyWriter.java:285) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) not sure if this is related to the fix or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22401) Auto Install jdk 8 from oracle downloads html instead of bin
Jesse Glick resolved JENKINS-22401 as Duplicate Auto Install jdk 8 from oracle downloads html instead of bin Change By: Jesse Glick (01/Apr/14 5:21 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22367) Move JDKInstaller to a plugin
Jesse Glick commented on JENKINS-22367 Move JDKInstaller to a plugin Agreed. We should also consider adding an installer for the JRE, which can be gotten from java.com more easily, I think, and which would suffice for some purposes. Not compiling Java programs, obviously—unless you are using (say) a Maven project requesting the Eclipse compiler. But possibly enough to run many Ant/Maven/Gradle builds. And all that is needed for SSH Slaves and similar slave launchers, since you only need a JRE for the slave agent. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20769) Failed to execute command Pipe.EOF
Jesse Glick reopened JENKINS-20769 Failed to execute command Pipe.EOF @zzzeek added a note to @kohsuke’s commit: https://github.com/jenkinsci/remoting/commit/cdbc40b8980d3ea528473daf7e44475c956a9a03#commitcomment-5870985 Change By: Jesse Glick (01/Apr/14 5:37 PM) Resolution: Fixed Status: Resolved Reopened Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [msbuild] (JENKINS-22451) Backslash is stripped from MSBuild command line argument
Chris McKinnon
created JENKINS-22451
Backslash is stripped from MSBuild command line argument
Issue Type:
Bug
Assignee:
kdsweeney
Components:
msbuild
Created:
01/Apr/14 6:21 PM
Description:
I'm trying to pass in the following command line argument to MSBuild:
/p:SolutionDir="${WORKSPACE}"\trunk\
From my build output, this is passed properly except the "\" at the end of "trunk\" is always removed.
I tried version 1.21 and 1.17 of the MSBuild plugin and neither work.
Project:
Jenkins
Priority:
Minor
Reporter:
Chris McKinnon
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18364) Optimize creation of relative links to jobs
dogfood commented on JENKINS-18364 Optimize creation of relative links to jobs Integrated in jenkins_main_trunk #3272 FIXED JENKINS-18364 Functions.getRelativeLinkTo is called many times during rendering, so skip checking View.getItems which is expensive. (Revision bcc86148561ad9ab4a0365ff00d28ff7ee71d57c) Result = SUCCESS Jesse Glick : bcc86148561ad9ab4a0365ff00d28ff7ee71d57c Files : core/src/test/java/hudson/FunctionsTest.java core/src/main/java/hudson/Functions.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22265) Seemingly random java.lang.InterruptedException in MultiJob plugin
Seth
commented on JENKINS-22265
Seemingly random java.lang.InterruptedException in MultiJob plugin
Our analysis indicates that this is caused by the following faulty Future#cancel implementation in https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/queue/FutureImpl.java :
@Override
public boolean cancel(boolean mayInterruptIfRunning) {
Queue q = Jenkins.getInstance().getQueue();
synchronized (q) {
synchronized (this) {
if(!executors.isEmpty()) {
if(mayInterruptIfRunning)
for (Executor e : executors)
e.interrupt();
return mayInterruptIfRunning;
}
return q.cancel(task);
}
}
}
Specifically, note that a FutureImpl will retain references to its executor(s) long after those executors have finished executing that particular task, and because this method makes no attempt to check its state to determine whether a transition to canceled is possible, it seems that any client code that holds a reference to a FutureImpl will be able to cancel arbitrary future jobs an arbitrary number of times (each invocation of cancel, concurrent or not, will produce another attempt to set the executor thread's interrupted bit).
Unfortunately, the fix is neither simple clear, as the AsyncFutureImpl that this class extends is also an invalid future implementation; it is trivially possible to have a cancelled AsyncFutureImpl with a value and throwable. And that the fact none of the fields are declared volatile suggest there is a race between a notifying thread's write and a waiting thread's read. I would recommend looking at (or, ideally, using) Guava's com.google.common.util.concurrent.AbstractFuture implementation instead.
The way this bug is exercised by the MultiJob plugin is that it, if so configured, will attempt to halt execution of all subtasks on any subtask's failure (from https://github.com/jenkinsci/tikal-multijob-plugin/blob/master/src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuilder.java ):
...
KillPhaseOnJobResultCondition killCondition = subTask.phaseConfig
.getKillPhaseOnJobResultCondition();
if (killCondition.equals(KillPhaseOnJobResultCondition.NEVER))
return false;
if (killCondition.isKillPhase(subTask.result)) {
for (SubTask _subTask : subTasks)
_subTask.future.cancel(true);
}
...
Our workaround has been to configure all our usages of the MultiJob plugin to "Kill the phase on: Never" so that we return from the first if statement and never make it to the second block.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22452) Unable to Specify Git Repo Name
Prasad Pamidi created JENKINS-22452 Unable to Specify Git Repo Name Issue Type: Bug Assignee: Nicolas De Loof Attachments: Screen Shot 2014-04-01 at 3.22.54 PM.png, Screen Shot 2014-04-01 at 3.23.16 PM.png Components: git, git-client Created: 01/Apr/14 7:34 PM Description: Hi, I'm trying to run a build task, which uses the source code mentioned in the git repository. Once the build goes through I want to upload a tag to remote git repo. So, when I'm trying to use git-publisher to do this, it is asking me to specify "Target remote name" under the new tag setup section. But the current version of git client and git doesn't provide me way to specify "Remote Name" for git repository that I've configured under "Source Code Management". I've also attached the screenshots. Can someone help me with this issue. Regards. Project: Jenkins Labels: plugin jenkins git git-publisher git-client Priority: Major Reporter: Prasad Pamidi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-22260) Ideas for other variables to support
Clifford Sanders commented on JENKINS-22260 Ideas for other variables to support I don't think that this plugin is meant for exposing those variables. The description on github states: "... injects name of user started the build into build variables set." Maybe this can be solved by using the EnvInject Plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-9383) mitigate security issues
Jesse Glick resolved JENKINS-9383 as Fixed mitigate security issues Closing since JENKINS-15212 covers the ineffectiveness of the current solution. Change By: Jesse Glick (01/Apr/14 8:01 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-15212) More flexible and effective security for Groovy Postbuild
Jesse Glick assigned JENKINS-15212 to Jesse Glick More flexible and effective security for Groovy Postbuild Change By: Jesse Glick (01/Apr/14 8:01 PM) Assignee: wolfs JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-15212) More flexible and effective security for Groovy Postbuild
Jesse Glick started work on JENKINS-15212 More flexible and effective security for Groovy Postbuild Change By: Jesse Glick (01/Apr/14 8:01 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-15212) More flexible and effective security for Groovy Postbuild
Jesse Glick updated JENKINS-15212 More flexible and effective security for Groovy Postbuild Change By: Jesse Glick (01/Apr/14 8:02 PM) Priority: Major Critical URL: https://github.com/jenkinsci/groovy-postbuild-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/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-9383) mitigate security issues
Daniel Beck commented on JENKINS-9383 mitigate security issues Jesse: Note that 15212 also mentions the need for a more extensive API to make the plugin in a secured environment not just useable, but useful. Maybe use this one for the sandboxing, and keep 15212 for the API changes? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-9383) mitigate security issues
Daniel Beck edited a comment on JENKINS-9383 mitigate security issues Jesse: Note that 15212 also mentions the need for a more extensive API to make the plugin in a secured environment not just useable, but useful too many basic action requires falling back to the manager. Maybe use this one for the sandboxing, and keep 15212 for the API changes? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
