[JIRA] [git-client] (JENKINS-21127) incorrect parameter is set for credential-store
Dmitry Skorbovenko
created JENKINS-21127
incorrect parameter is set for credential-store
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git-client
Created:
23/Dec/13 8:00 AM
Description:
I have fixed it please apply the patch
@@ -974,10 +974,10 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
if (credentials != null) {
listener.getLogger().println("using .gitcredentials to set credentials");
-
+
String urlWithCrendentials = getGitCrendentialsURL(url, credentials);
store = createGitCrendetialsStore(urlWithCrendentials);
-launchCommandIn(workDir, "config", "--local", "credential.helper", "store --store=\"" + store.getAbsolutePath() + "\"");
+launchCommandIn(workDir, "config", "--local", "credential.helper", "store --file=\"" + store.getAbsolutePath() + "\"");
}
}
Project:
Jenkins
Priority:
Blocker
Reporter:
Dmitry Skorbovenko
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [findbugs] (JENKINS-21102) Findbugs throws FileNotFoundException
Ray Lupus edited a comment on JENKINS-21102 Findbugs throws FileNotFoundException mvn findbugs:findbugs pom.xml org.codehaus.mojo findbugs-maven-plugin 2.5.2 findbugs.xml findbugsXml.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21128) password is not stored in credential-store file
Dmitry Skorbovenko
created JENKINS-21128
password is not stored in credential-store file
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git-client
Created:
23/Dec/13 8:01 AM
Description:
I have fixed it please apply the patch
@@ -1537,7 +1537,7 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
.setPass(Secret.toString(up.getPassword()));
}
return uri.toString();
+return uri.toPrivateString();
}
Project:
Jenkins
Priority:
Blocker
Reporter:
Dmitry Skorbovenko
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [findbugs] (JENKINS-21102) Findbugs throws FileNotFoundException
Ray Lupus edited a comment on JENKINS-21102 Findbugs throws FileNotFoundException jenkins maven style template goals is "findbugs:findbugs" pom.xml org.codehaus.mojo findbugs-maven-plugin 2.5.2 generated 2 files in workspace target/ findbugs.xml findbugsXml.xml jenkins plugin version is 4.48，jenkins version 5.10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [findbugs] (JENKINS-21102) Findbugs throws FileNotFoundException
Ray Lupus updated JENKINS-21102 Findbugs throws FileNotFoundException Change By: Ray Lupus (23/Dec/13 8:04 AM) Attachment: findbugs.xml Attachment: findbugsXml.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [findbugs] (JENKINS-21102) Findbugs throws FileNotFoundException
Ray Lupus edited a comment on JENKINS-21102 Findbugs throws FileNotFoundException jenkins maven style template goals is "findbugs:findbugs" pom.xml org.codehaus.mojo findbugs-maven-plugin 2.5.2 generated 2 files in workspace target/ findbugs.xml findbugsXml.xml already attached jenkins plugin version is 4.48，jenkins version 5.10 build on slave This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21127) incorrect parameter is set for credential-store
Dmitry Skorbovenko closed JENKINS-21127 as Fixed incorrect parameter is set for credential-store I have noticed it had been already fixed in master Change By: Dmitry Skorbovenko (23/Dec/13 8:16 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21128) password is not stored in credential-store file
Dmitry Skorbovenko closed JENKINS-21128 as Fixed password is not stored in credential-store file I have noticed it had been already fixed in master Change By: Dmitry Skorbovenko (23/Dec/13 8:16 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21126) it is not possible to make checkout
Dmitry Skorbovenko closed JENKINS-21126 as Fixed it is not possible to make checkout I have noticed it had been already fixed in master Change By: Dmitry Skorbovenko (23/Dec/13 8:17 AM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21082) Build with parameters doesn't work within a multi-job view
hagzag resolved JENKINS-21082 as Duplicate Build with parameters doesn't work within a multi-job view JENKINS-20080 Change By: hagzag (23/Dec/13 9:00 AM) Status: Open Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [core] (JENKINS-20080) Build Button fails for jobs that require "Build with Parameters"
hagzag reopened JENKINS-20080 Build Button fails for jobs that require "Build with Parameters" Change By: hagzag (23/Dec/13 9:15 AM) Resolution: Fixed Status: Resolved Reopened Assignee: Oliver Gondža benza This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Artem Belov commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails Have the same issue with git 2.0 and git-client 1.6 plugins I was trying to fix it using previous versions. In all these versions auth was broken due to some reasons, Caused by: hudson.plugins.git.GitException: Failed to connect to https://stash.***/***.git using credentials YYY (status = 403) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:1610) hudson.plugins.git.GitException: Failed to connect to https://login@stash.***/***.git (status = 403) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getURLWithCrendentials(CliGitAPIImpl.java:1437) hudson.plugins.git.GitException: Failed to connect to https://login@stash.***/***.git (status = 403) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:1597) hudson.plugins.git.GitException: Failed to connect to https://login@stash.***/***.git (status = 403) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:1610) and so on. Sorry, couldn't map these messages to versions now. It was both versions with integrated credentials plugin and without it. The only working solution was roll back to git 1.5 and git-client 1.0.7. I guess one of the possible causes of the bug is that my git login contains @ sign which should be replaced by %40 to be put into connection string correctly. And it's not clear should I use it when define login/password pair in credentials password. Anyway, it's just a guess, because neither @ nor %40 worked Some info about enviroment: Git server is internal Atlassian Stash We have to use https instead of SSL because of firewall issues To force it we use sslVerify = false in git config It properly works using CLI directly and from Jenkins with plugins git 1.5 and git-client 1.0.7 but not later ones. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21103) "Priorities are assigned top down by first match" does not work correctly
Adam Gabryś updated JENKINS-21103 "Priorities are assigned top down by first match" does not work correctly Change By: Adam Gabryś (23/Dec/13 9:43 AM) Attachment: jenkins-configure-priority-sorter.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
evernat commented on JENKINS-20935 Provide separate monitoring pages for each slave node Yes, we can try that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job
Oleg Nenashev assigned JENKINS-18678 to Oleg Nenashev Builds disappear some time after renaming job Change By: Oleg Nenashev (23/Dec/13 9:48 AM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21103) "Priorities are assigned top down by first match" does not work correctly
Adam Gabryś commented on JENKINS-21103 "Priorities are assigned top down by first match" does not work correctly I use "Absolute" sorting strategy (screen jenkins-configure-priority-sorter). Today: I have six free executors. The job (which is in both groups) has been started by scm change. In column "Job Priority" I see 3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job
Oleg Nenashev commented on JENKINS-18678 Builds disappear some time after renaming job Finally, the issue has not been solved in the new LTS. The issue's cause: Builds cache (RunMap.java) has its own reference to builds directory This directory is being set upon job's creation, but AbstractProject don't modify the location on renaming I've created a PR with a draft fix, but we need to implement a unit test (see Daniel's reproduction step in JENKINS-19650) https://github.com/jenkinsci/jenkins/pull/1075 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
KrishnaKanth B N commented on JENKINS-20891 Websphere Deployer fails to deploy to remote server Hi, We are facing the same issue too. We have tried on Windows 7 and Windows 2003 Server. The latest suggestion from Greg on 20th December 2013 did not help us. Please help. Also, we are observing other issues which I will raise as a separate bugs. Below is the summary of them. SOAP Connector Port value not getting persisted in the configuration after Save operation on the Job. (Updated value does not show up on the form but Test Connection picks up the updated value) Once the Test Connection is successful for a server, we cannot establish connection to another server EVEN in other job. It says 'Already Exists!' when we provide other server details and use Test connection. Thanks in advance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21129) Unable to test multiple connections without restarting Jenkins server
KrishnaKanth B N created JENKINS-21129 Unable to test multiple connections without restarting Jenkins server Issue Type: Bug Assignee: Unassigned Components: websphere-deployer Created: 23/Dec/13 10:24 AM Description: Once the Test Connection is successful for a server, we cannot establish connection to another server EVEN in other job. It says 'Already Exists!' when we provide other server details and use Test Connection in the same or any other job. The only solution seems to be to restart Jenkins server! Please help in resolving this. Thanks in advance. Due Date: 30/Dec/13 12:00 AM Environment: Windows 2003 Server, Windows 7, Jenkins 1.522, 1.542 IE 8 Project: Jenkins Labels: Concurrent WAS, Connections Priority: Major Reporter: KrishnaKanth B N This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-remote-trigger] (JENKINS-20826) Integrate credentials plugin
Maurice W. started work on JENKINS-20826 Integrate credentials plugin Change By: Maurice W. (23/Dec/13 10:26 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-remote-trigger] (JENKINS-20827) Integrate token macro plugin
Maurice W. started work on JENKINS-20827 Integrate token macro plugin Change By: Maurice W. (23/Dec/13 10:26 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-remote-trigger] (JENKINS-20829) Allow credentials definition on job level
Maurice W. started work on JENKINS-20829 Allow credentials definition on job level Change By: Maurice W. (23/Dec/13 10:27 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [findbugs] (JENKINS-21102) Findbugs throws FileNotFoundException
Ray Lupus edited a comment on JENKINS-21102 Findbugs throws FileNotFoundException jenkins maven style template goals is "findbugs:findbugs" pom.xml org.codehaus.mojo findbugs-maven-plugin 2.5.2 generated 2 files in workspace target/ findbugs.xml findbugsXml.xml already attached jenkins findbugs plugin version is 4.48，jenkins version 5.10 build on slave This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21103) "Priorities are assigned top down by first match" does not work correctly
Magnus Sandberg commented on JENKINS-21103 "Priorities are assigned top down by first match" does not work correctly Just to clarify: Job Priority column will show you the priority of the latest start of the job, so if the Jobs gets triggered by two different causes you will only see the value of the last. From what I understand from this should however not be the issue in this case. In the Jenkins root directory you will find a file called "jenkins.advancedqueue.PriorityConfiguration.xml" can you attach that file for verification? Would it be possible for you to try a pre-release of the next version with some extended logging (JENKINS-21119)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20080) Build Button fails for jobs that require "Build with Parameters"
benza resolved JENKINS-20080 as Fixed Build Button fails for jobs that require "Build with Parameters" This issue was fixed, you need to upgrade "Jenkins Parameterized Trigger plugin" to 2.22 with jenkins > 1.537 Change By: benza (23/Dec/13 11:19 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21103) "Priorities are assigned top down by first match" does not work correctly
Adam Gabryś updated JENKINS-21103 "Priorities are assigned top down by first match" does not work correctly Change By: Adam Gabryś (23/Dec/13 11:39 AM) Attachment: jenkins.advancedqueue.PriorityConfiguration.xml Attachment: jenkins.advancedqueue.PrioritySorterConfiguration.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21103) "Priorities are assigned top down by first match" does not work correctly
Adam Gabryś commented on JENKINS-21103 "Priorities are assigned top down by first match" does not work correctly "Just to clarify: Job Priority column will show you the priority of the latest start of the job, so if the Jobs gets triggered by two different causes you will only see the value of the last. From what I understand from this should however not be the issue in this case." I know But in my case, it should show 4 (not 3). "Would it be possible for you to try a pre-release of the next version with some extended logging (JENKINS-21119)?" Yes. Today, I upgraded plugin to version 2.3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [patch-parameter] (JENKINS-21130) Patch application failed when no SCM is used
Barak Weiss created JENKINS-21130 Patch application failed when no SCM is used Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: patch-parameter Created: 23/Dec/13 11:42 AM Description: Patch is applied even if SVN is not set as SCM. This forces us to add SVN to a "master" job that calls other jobs that need the patch. I expect the plugin to not apply the patch when SVM in not used, or at least give the option not to fail is SVN is not used. Environment: Windows 7 Project: Jenkins Labels: plugin Priority: Major Reporter: Barak Weiss This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21103) "Priorities are assigned top down by first match" does not work correctly
Adam Gabryś edited a comment on JENKINS-21103 "Priorities are assigned top down by first match" does not work correctly "Just to clarify: Job Priority column will show you the priority of the latest start of the job, so if the Jobs gets triggered by two different causes you will only see the value of the last. From what I understand from this should however not be the issue in this case." I know But in my case, it should show 4 (run by scm change), not 3 (run by user). "Would it be possible for you to try a pre-release of the next version with some extended logging (JENKINS-21119)?" Yes. Today, I upgraded plugin to version 2.3. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Angelo Schneider commented on JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm Can you please clarify on this: C:\gnuwin32\bin> .\wget.exe --auth-no-challenge --http-user=user --http-password=_apiToken_ http://myserver.com:8080/job/Experiment-Main-Build/build?token=1715b88bfba6717fadee72f5d5ecd17a The word "apiToken", is that ment as a keyword so that the final "?token=1715b88bfba6717fadee72f5d5ecd17a" is interpreted correctly or is that a placeholder for the users api token?? @Jeff imho no AD/LDAP request is needed at all. Jenkins should bypass what ever auth scheme it has as long as the user and his apikey is correct. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [status-view] (JENKINS-21131) Ability to customize the summary page for builds/jobs
Inbar Rose created JENKINS-21131 Ability to customize the summary page for builds/jobs Issue Type: Improvement Assignee: Unassigned Components: status-view Created: 23/Dec/13 12:41 PM Description: I would like to be able to customize the display of summaries in the status view. Specifically the changes summary that is derived from git. We use a complex git-setup and the automatic changes are wrong. I would like to be able to remove their display from the status page. I know that the groovy postbuild script grants tools for dealing with summaries, but I have not managed to remove these, perhaps it can only remove those which are not added there by Jenkins. I do not think this is too complex of a request, I am active and can respond to any questions. Project: Jenkins Labels: jenkins configuration job status summary Priority: Major Reporter: Inbar Rose This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [status-view] (JENKINS-21131) Ability to customize the summary page for builds/jobs
Inbar Rose updated JENKINS-21131 Ability to customize the summary page for builds/jobs Change By: Inbar Rose (23/Dec/13 12:45 PM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21132) Stapler returns 200 OK for an internal server error instead of 500
Jan Molak
created JENKINS-21132
Stapler returns 200 OK for an internal server error instead of 500
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
23/Dec/13 12:55 PM
Description:
Install Build Monitor Plugin as it will make triggering the error easier: https://wiki.jenkins-ci.org/display/JENKINS/Build+Monitor+Plugin
To replicate the problem first make Jenkins throw a NullPointerException.
On Jenkins 1.480 this can be easily done by triggering JENKINS-15309 (https://issues.jenkins-ci.org/browse/JENKINS-15309)
create a new Build Monitor view and add some jobs to it. Shut down Jenkins.
edit the config.xml file and make sure that instead of you have (no class specified) as this will cause an unhandled NullPointerException
start up Jenkins and navigate to the Build Monitor view tab
open Google Chrome developer console, go to Network Tab and view the response returned by Jenkins to a fetchJobViews request. It will be something like the following:
HEADERS:
Request URL:http://localhost:8080/$stapler/bound/c9717585-a435-44f6-84fc-732ac9460461/fetchJobViews
Request Method:POST
Status Code:200 OK
Request Headersview source
BODY:
cause: null
localizedMessage: ""
message: ""
stackTrace: [{className:java.util.TreeSet, fileName:TreeSet.java, lineNumber:154, methodName:,…},…]
Please note the "200 OK" part. If there is an internal server error, Jenkins should never return a 200 OK, but something more appropriate such as 500.
Returning a correct HTTP error code will make it easier for plugin developers to correctly react the the problem.
Environment:
Jenkins 1.480 and 1.539
Mac OsX Maverics
Google Chrome
Project:
Jenkins
Labels:
jenkins
exception
nullpointer
stapler
api
Priority:
Major
Reporter:
Jan Molak
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Update: I checked the release version: 1.539 that on JoJ, this version is memory leaks free but this version suffers from other bugs such as problem when using Build multi-configuration project (Matrix job) + Builds of a concurrently executable 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-21133) Periodical crashes of jenkins with loss css-styles.
Jussan Asanov created JENKINS-21133 Periodical crashes of jenkins with loss css-styles. Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: after_first_crash.jpg, loss_css-1.jpg Components: build-flow Created: 23/Dec/13 1:30 PM Description: Problems appeared after update to 1.539 version. (Update to 1.543 have not change this behavior.) Periodically (usually after some inactivity) jenkins crashes on build-starting with loss css styles and with loss controllability (see atachments). Only jenkins-restart resolve this problem. In jenkins log: 23.12.2013 9:27:54 org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: Error while serving http://dev.orgname.local/job/demo1/build java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor348.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java: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 org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(Api
[JIRA] [websphere-deployer] (JENKINS-21129) Unable to test multiple connections without restarting Jenkins server
Greg Peters assigned JENKINS-21129 to Greg Peters Unable to test multiple connections without restarting Jenkins server Change By: Greg Peters (23/Dec/13 1:50 PM) Assignee: Greg Peters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21129) Unable to test multiple connections without restarting Jenkins server
Greg Peters updated JENKINS-21129 Unable to test multiple connections without restarting Jenkins server Change By: Greg Peters (23/Dec/13 1:52 PM) Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-15103) jenkins slave process does not let go of .git\objects\pack\*.pack file causeing "Unable to delete" when wiping workspace
Mark Waite edited a comment on JENKINS-15103 jenkins slave process does not let go of .git\objects\pack\*.pack file causeing "Unable to delete" when wiping workspace The automated tests executed by "mvn install" on the git-client-plugin repository seem to show the same problem. When those tests are run on Linux, they pass. When the same tests are run on Windows, several of the tests fail with the message "Failed to clean up temp dirs" The tests which are failing include: test_checkoutBranchFailure(org.jenkinsci.plugins.gitclient.JGitAPIImplTest): Failed to clean up temp dirs test_setSubmoduleUrl(org.jenkinsci.plugins.gitclient.JGitAPIImplTest): Failed to clean up temp dirs test_show_revision_for_single_commit(org.jenkinsci.plugins.gitclient.JGitAPIImplTest): Failed to clean up temp dirs test_getAllLogEntries(org.jenkinsci.plugins.gitclient.JGitAPIImplTest): Failed to clean up temp dirs test_revListAll(org.jenkinsci.plugins.gitclient.JGitAPIImplTest): Failed to clean up temp dirs test_fetch_with_updated_tag(org.jenkinsci.plugins.gitclient.JGitAPIImplTest): Failed to clean up temp dirs Within the failure details, the message "IOException: Unable to delete ... pack" is listed. Note that the same unit tests pass for the command line implementation. I think that makes the current behavior different from the originally reported behavior. The original report required that there was a certain format for the branch to build, while the unit test failure shows that it will fail for any case which uses JGit as the git executable instead of using the command line as the git executable. Unfortunately, those test failures only happen in the JGit implementation, not in the CLI implementation. This bug report was submitted confirmed as a problem with both the JGit and the CLI implementations, so fixing the JGit specific test failures will not be enough. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21134) SOAP Connector Port Not Updating
Greg Peters created JENKINS-21134 SOAP Connector Port Not Updating Issue Type: Bug Affects Versions: current Assignee: Greg Peters Components: websphere-deployer Created: 23/Dec/13 1:57 PM Description: The SOAP connector port on the configuration page always shows 8880 even though the port is updated. While the backend port the service used is updated the configuration page doesn't reflect it. Due Date: 30/Dec/13 12:00 AM Environment: All environments Project: Jenkins Priority: Major Reporter: Greg Peters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21134) SOAP Connector Port Not Updating
Greg Peters commented on JENKINS-21134 SOAP Connector Port Not Updating Fixed in version 1.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21114) Cannot use reference clone option against a bare repository
Mark Waite commented on JENKINS-21114 Cannot use reference clone option against a bare repository Will, thanks for the proposed patch. Would you be willing to submit the change as a pull request on GitHub so that the git plugin maintainer can consider it for inclusion in a future release of the Git client plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-20937) SCM password should not be recorded in build.xml in job's builds storage
teilo resolved JENKINS-20937 as Fixed SCM password should not be recorded in build.xml in job's builds storage Change By: teilo (23/Dec/13 2:16 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job
Jesse Glick started work on JENKINS-18678 Builds disappear some time after renaming job Change By: Jesse Glick (23/Dec/13 2:48 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shiningpanda] (JENKINS-21090) virtualenv task creating a new virtualenv without the clean flag set
Mobpro Mobpro commented on JENKINS-21090 virtualenv task creating a new virtualenv without the clean flag set It keeps on failing Every time we change something in the build steps this goes wrong 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/groups/opt_out.
[JIRA] [core] (JENKINS-20080) Build Button fails for jobs that require "Build with Parameters"
Jesse Glick assigned JENKINS-20080 to Oliver Gondža Build Button fails for jobs that require "Build with Parameters" Change By: Jesse Glick (23/Dec/13 3:44 PM) Assignee: benza Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-21014) Include verify lifecycle to calculate the more relevant build for "Build whenever a SNAPSHOT dependency is built" when there is more than one upstream candidate
Jesse Glick assigned JENKINS-21014 to Unassigned Include verify lifecycle to calculate the more relevant build for "Build whenever a SNAPSHOT dependency is built" when there is more than one upstream candidate Not sure why this was assigned to me. Change By: Jesse Glick (23/Dec/13 3:45 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Marc Harter commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Being a Jenkins noob, how do I go about applying patches to plugins? Or is it better to wait for a new release? My build system is also down and was hoping to get it up soon. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Chris Tacke commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I'm fairly sure you have to rebuild from the source. I don't have a Java environment set up, so that's really difficult for me to do with any sort of speed. I'm using a Windows system and I'll put my money where my mouth is - I'm willing to pay/donate to the dev team to get this fix released. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [confluence-publisher] (JENKINS-21104) Confluence Publisher Plugin ignores Jenkins proxy settings
Joe Hansche commented on JENKINS-21104 Confluence Publisher Plugin ignores Jenkins proxy settings Thanks for the report! I hadn't considered proxy requirements initially. I'll see what I can do to add this in the next release. (Note to self, for similar implementation details: https://github.com/jenkinsci/stashnotifier-plugin/commit/bf0ee1981348a7cbaefd37b2bed27cdc6e30d50e) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-20146) ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory
Abhishek Chikane commented on JENKINS-20146 ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory I could not upgrade it as the Jenkins upgrade on Windows it self broke my server. I am working on one critical project so thought to upgrade after that. Sorry for not replying. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
emanuelez commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Maybe the hpi you can find here? https://jenkins.ci.cloudbees.com/job/plugins/job/git-client-plugin/194/org.jenkins-ci.plugins$git-client/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21132) Stapler returns 200 OK instead of 500 when an internal server error happens
Jan Molak updated JENKINS-21132 Stapler returns 200 OK instead of 500 when an internal server error happens Change By: Jan Molak (23/Dec/13 4:44 PM) Summary: Stapler returns 200 OK for instead of 500 when an internal server error instead of 500 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/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Jesse Glick commented on JENKINS-20772 'Apply' error screens don't work By the way the actual exception in this case is fixed in the 4.2 release of the Templates plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21114) Cannot use reference clone option against a bare repository
Will Saxon commented on JENKINS-21114 Cannot use reference clone option against a bare repository Yes, I'll try to get that done today. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job
SCM/JIRA link daemon commented on JENKINS-18678 Builds disappear some time after renaming job Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java http://jenkins-ci.org/commit/jenkins/568ccba8187cfa859deeefb397983e049a9d942b Log: [FIXED JENKINS-18678] - Update builds location in RunMap after the job's renaming This change resolve the issue with missing builds after the jobs renaming and further cleanup of cache. Finally, the cache's directory location will be updated after the each job renaming. https://issues.jenkins-ci.org/browse/JENKINS-18678 Signed-off-by: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job
SCM/JIRA link daemon commented on JENKINS-18678 Builds disappear some time after renaming job Code changed in jenkins User: Jesse Glick Path: test/src/test/groovy/hudson/model/AbstractProjectTest.groovy http://jenkins-ci.org/commit/jenkins/1943801ba725bff83e1afaea5f4c7670754c5c61 Log: JENKINS-18678 Reproduced problem in test. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job
SCM/JIRA link daemon resolved JENKINS-18678 as Fixed Builds disappear some time after renaming job Change By: SCM/JIRA link daemon (23/Dec/13 5:21 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job
SCM/JIRA link daemon commented on JENKINS-18678 Builds disappear some time after renaming job Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java http://jenkins-ci.org/commit/jenkins/833c423268635ba79672ccdf6d17977a2a4d4181 Log: JENKINS-18678 Tweaking API, adding @since & changelog for #1075, fixing purgeCache so that test can pass. Compare: https://github.com/jenkinsci/jenkins/compare/7b83852b6685...833c42326863 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17401) Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window
Jesse Glick started work on JENKINS-17401 Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window Change By: Jesse Glick (23/Dec/13 5:28 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17401) Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window
Jesse Glick assigned JENKINS-17401 to Jesse Glick Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window Change By: Jesse Glick (23/Dec/13 5:28 PM) Assignee: Kohsuke Kawaguchi Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Marc Harter commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I tried that hpi but didn't work for me, I'm getting this error in Configuration -> Source Code Management -> Git -> Repository Url with Credentials: Failed to connect to repository : Command "git config --local credential.helper store --file=\"/tmp/git3351626511932244072.credentials\"" returned status code 255: stdout: stderr: error: could not lock config file .git/config: No such file or directory I also get this error when attempting to build (actual repo is masked): Started by user Marc Harter Building in workspace /var/lib/jenkins/jobs/REDI Comps/workspace Wiping out workspace first. Cloning the remote Git repository Cloning repository https://github.com/my-company/my-project.git Fetching upstream changes from https://github.com/my-company/my-project.git using .gitcredentials to set credentials ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress https://github.com/my-company/my-project.git +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: error: cannot run /bin/echo : No such file or directory fatal: could not read Username for 'https://github.com': No such device or address at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1103) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:985) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:69) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:218) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:350) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:828) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) ERROR: null This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21114) Cannot use reference clone option against a bare repository
Mark Waite commented on JENKINS-21114 Cannot use reference clone option against a bare repository Also, is there a way to write a unit test which would show the problem (as you discovered it) and which would confirm that the problem is fixed (and stays fixed, and runs on all platforms, etc.)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Jesse Glick assigned JENKINS-20772 to Kohsuke Kawaguchi 'Apply' error screens don't work Change By: Jesse Glick (23/Dec/13 5:48 PM) Assignee: Steven Christou Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Jesse Glick commented on JENKINS-20772 'Apply' error screens don't work The originally reported issue is actually a bug in the Templates plugin, and very similar to JENKINS-17401. Jenkins is sending a redirect and the Apply handler does not expect this. The fix is just to send a warning in that case, not a redirect. The more general issue is that if an exception is actually thrown, you get a blank error dialog. This is trivially reproduced (in Chrome at least) by configuring a freestyle project, checking Build periodically, and typing some junk into the Schedule field. In apply.js, the error-handling code using responseDialog is triggered, but it does not work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Jesse Glick commented on JENKINS-20772 'Apply' error screens don't work Commenting out $(containerId).appendChild(target); fixes the problem to the extent that the error is shown in a new browser window. But then regular Apply button handling is broken. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Jesse Glick started work on JENKINS-20772 'Apply' error screens don't work Change By: Jesse Glick (23/Dec/13 6:21 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18678) Builds disappear some time after renaming job
dogfood commented on JENKINS-18678 Builds disappear some time after renaming job Integrated in jenkins_main_trunk #3132 [FIXED JENKINS-18678] - Update builds location in RunMap after the job's renaming (Revision 568ccba8187cfa859deeefb397983e049a9d942b) JENKINS-18678 Reproduced problem in test. (Revision 1943801ba725bff83e1afaea5f4c7670754c5c61) JENKINS-18678 Tweaking API, adding @since & changelog for #1075, fixing purgeCache so that test can pass. (Revision 833c423268635ba79672ccdf6d17977a2a4d4181) Result = SUCCESS nenashev : 568ccba8187cfa859deeefb397983e049a9d942b Files : core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java core/src/main/java/hudson/model/AbstractProject.java Jesse Glick : 1943801ba725bff83e1afaea5f4c7670754c5c61 Files : test/src/test/groovy/hudson/model/AbstractProjectTest.groovy Jesse Glick : 833c423268635ba79672ccdf6d17977a2a4d4181 Files : core/src/main/java/hudson/model/AbstractProject.java changelog.html core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-21135) yum repository appears to be stale (1.534) not current (1.544)
Ian Young created JENKINS-21135 yum repository appears to be stale (1.534) not current (1.544) Issue Type: Bug Assignee: Unassigned Components: other Created: 23/Dec/13 6:26 PM Description: If you look at http://pkg.jenkins-ci.org/redhat/ it indicates that 1.544 should be available. However, if you're actually using that yum repository, the most recent you are offered appears to be 1.534 (three months old). I'm guessing that someone has forgotten to run createrepo for a while. Project: Jenkins Priority: Major Reporter: Ian Young This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Jesse Glick edited a comment on JENKINS-20772 'Apply' error screens don't work The originally reported issue is actually a bug in the Templates plugin, and very similar to JENKINS-17401. Jenkins is sending a redirect and the Apply handler does not expect this. The fix is just to send a warning in that case, not a redirect. Update: actually there seems to be no such redirect in the Templates plugin, so that issue probably really is what is reported here: failure to display a stack trace. The more general issue is that if an exception is actually thrown, you get a blank error dialog. This is trivially reproduced (in Chrome at least) by configuring a freestyle project, checking Build periodically, and typing some junk into the Schedule field. In apply.js, the error-handling code using responseDialog is triggered, but it does not work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Jesse Glick assigned JENKINS-20772 to Jesse Glick 'Apply' error screens don't work Change By: Jesse Glick (23/Dec/13 6:21 PM) Assignee: Kohsuke Kawaguchi Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Jeff Burke commented on JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm @angelo, take a look at https://wiki.jenkins-ci.org/display/JENKINS/Authenticating+scripted+clients. It shows how the apitoken is supplied. apitoken is being used as a keyword to tell the CLI/SSH to use the token as an account lookup. On the topic of whether CLI w/API token should verify the account is active w/the underlying security realm... I standby that it needs to do this. It doesn't need to authenticate the credentials, but it does need to verify that the user account hasn't been disabled. Not performing this would, for example, allow previous employees of a company a backdoor into internal Jenkins systems. Long after their AD, LDAP, or PAM account has been disabled, Jenkins SSH would continue to give them access to resources that administrators clearly didn't want them to continue to have. I'd be fine w/it being a configurable option w/in the SSH CLI. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
SCM/JIRA link daemon commented on JENKINS-20772 'Apply' error screens don't work Code changed in jenkins User: Jesse Glick Path: core/src/main/resources/lib/form/apply/apply.js http://jenkins-ci.org/commit/jenkins/0e8195c43d744b65e46ce5d66262e29fbdb9fb35 Log: [FIXED JENKINS-20772] Properly render response in case Apply results in an error page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
SCM/JIRA link daemon commented on JENKINS-20772 'Apply' error screens don't work Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Descriptor.java http://jenkins-ci.org/commit/jenkins/9f23c0bdb3a3ed6485e161ff5c57ebba64f88035 Log: _javascript_ error when showing a FormException after Apply is clicked. Related to JENKINS-20772 but probably not 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17401) Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window
SCM/JIRA link daemon commented on JENKINS-17401 Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/c7dcb99290548f82b39846f4db431ab2ceb326ae Log: JENKINS-17401 JENKINS-20772 Noting. Compare: https://github.com/jenkinsci/jenkins/compare/833c42326863...c7dcb9929054 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
SCM/JIRA link daemon commented on JENKINS-20772 'Apply' error screens don't work Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/c7dcb99290548f82b39846f4db431ab2ceb326ae Log: JENKINS-17401 JENKINS-20772 Noting. Compare: https://github.com/jenkinsci/jenkins/compare/833c42326863...c7dcb9929054 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17401) Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window
SCM/JIRA link daemon commented on JENKINS-17401 Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Job.java core/src/main/resources/hudson/model/Messages.properties http://jenkins-ci.org/commit/jenkins/9e5817adbbf1b8c258c24281d0f61b40b7507cb3 Log: [FIXED JENKINS-17401] Behave gracefully if the user tries to rename a job using the Apply button. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
SCM/JIRA link daemon resolved JENKINS-20772 as Fixed 'Apply' error screens don't work Change By: SCM/JIRA link daemon (23/Dec/13 7:33 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17401) Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window
SCM/JIRA link daemon resolved JENKINS-17401 as Fixed Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window Change By: SCM/JIRA link daemon (23/Dec/13 7:33 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17401) Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window
dogfood commented on JENKINS-17401 Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window Integrated in jenkins_main_trunk #3133 [FIXED JENKINS-17401] Behave gracefully if the user tries to rename a job using the Apply button. (Revision 9e5817adbbf1b8c258c24281d0f61b40b7507cb3) JENKINS-17401 JENKINS-20772 Noting. (Revision c7dcb99290548f82b39846f4db431ab2ceb326ae) Result = SUCCESS Jesse Glick : 9e5817adbbf1b8c258c24281d0f61b40b7507cb3 Files : core/src/main/java/hudson/model/Job.java core/src/main/resources/hudson/model/Messages.properties Jesse Glick : c7dcb99290548f82b39846f4db431ab2ceb326ae Files : 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/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
dogfood commented on JENKINS-20772 'Apply' error screens don't work Integrated in jenkins_main_trunk #3133 _javascript_ error when showing a FormException after Apply is clicked. Related to JENKINS-20772 but probably not the same. (Revision 9f23c0bdb3a3ed6485e161ff5c57ebba64f88035) [FIXED JENKINS-20772] Properly render response in case Apply results in an error page. (Revision 0e8195c43d744b65e46ce5d66262e29fbdb9fb35) JENKINS-17401 JENKINS-20772 Noting. (Revision c7dcb99290548f82b39846f4db431ab2ceb326ae) Result = SUCCESS Jesse Glick : 9f23c0bdb3a3ed6485e161ff5c57ebba64f88035 Files : core/src/main/java/hudson/model/Descriptor.java Jesse Glick : 0e8195c43d744b65e46ce5d66262e29fbdb9fb35 Files : core/src/main/resources/lib/form/apply/apply.js Jesse Glick : c7dcb99290548f82b39846f4db431ab2ceb326ae Files : 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/groups/opt_out.
[JIRA] [role-strategy] (JENKINS-20328) Define project patterns an use them for defining project roles
Oleg Nenashev commented on JENKINS-20328 Define project patterns an use them for defining project roles Probably, role macros or Folder Plugin could resolve your case in a better way. Role-strategy plugin has significant performance issues in the case of big roles number, so I don't think that such improvement will be useful enough. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21136) ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 & Jenkins 1.544
karianna created JENKINS-21136 ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 & Jenkins 1.544 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 23/Dec/13 9:02 PM Description: javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) 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.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at com.thoughtworks.xstream.core.util.OrderRetainingMap.entrySet(OrderRetainingMap.java:77)
[JIRA] [core] (JENKINS-21136) ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 & Jenkins 1.544
Jesse Glick commented on JENKINS-21136 ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 & Jenkins 1.544 Check whether you can reproduce with a fresh $JENKINS_HOME, and if not, make a copy of your real home dir and try progressively removing half of its contents (while you can still reproduce), or restoring half (when not), until you have bisected the problem to a particular plugin, configuration setting, etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
SCM/JIRA link daemon commented on JENKINS-20772 'Apply' error screens don't work Code changed in jenkins User: Jesse Glick Path: core/src/main/resources/jenkins/model/Jenkins/oops.jelly core/src/main/resources/lib/form/apply/apply.js http://jenkins-ci.org/commit/jenkins/f8a73006e955a15ac8491301f8d2f0a6e8e4e17c Log: Merge pull request #1076 from daniel-beck/better-apply-dialog JENKINS-20772 Only show error message in dialog Compare: https://github.com/jenkinsci/jenkins/compare/28e403ac055f...f8a73006e955 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
SCM/JIRA link daemon commented on JENKINS-20772 'Apply' error screens don't work Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/jenkins/model/Jenkins/oops.jelly core/src/main/resources/lib/form/apply/apply.js http://jenkins-ci.org/commit/jenkins/b856cc2434b33ed7fec3492223e141747369bba3 Log: JENKINS-20772 Only show error message in dialog This change removes the superfluous UI elements around the error message if possible. Otherwise, fall back to existing behavior of adding entire page to iframe. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21136) ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 & Jenkins 1.544
karianna commented on JENKINS-21136 ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 & Jenkins 1.544 This was from a fresh install - no changes made. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21136) ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 & Jenkins 1.544
Jesse Glick commented on JENKINS-21136 ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 & Jenkins 1.544 Hmm, not happening for me in 1.546-SNAPSHOT on Linux with Java 7u45. If you know how to run Jenkins in a debugger, check what PureJavaReflectionProvider is working on. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21136) ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 & Jenkins 1.544
karianna commented on JENKINS-21136 ArrayOutOfBounds on almost any admin function - Mac OS X 10.9.1 & Jenkins 1.544 Will dig in if I get a little time after Xmas - to be fair Mac OS X is increasingly becoming a PITA as a development platform so I'm just likely to dump it and go with Linux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-1304) Add a "Use Export" option to the Subversion config section of a job
elygre commented on JENKINS-1304 Add a "Use Export" option to the Subversion config section of a job I would love this. We use "Always check out a clean copy" for a nightly build, and for that build this would be very useful. This build don't use the "poll for changes" functionality, so this is not a loss. Also, since this is always a clean copy, the pristine svn-files are absolutely wasteful. Reading old mailing list threads (such as https://groups.google.com/forum/#!topic/jenkinsci-users/1eN74vwtpcs), there seem to be an understanding that an "export" option is less good than an "update". That is probably true. However, compared to an "Always check out a clean copy", "export" is plain better This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
SCM/JIRA link daemon commented on JENKINS-20772 'Apply' error screens don't work Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/lib/form/apply/apply.js http://jenkins-ci.org/commit/jenkins/9b947ae8a239023482b8dcdec97d37425c42be8c Log: JENKINS-20772 Fix scrolling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
SCM/JIRA link daemon commented on JENKINS-20772 'Apply' error screens don't work Code changed in jenkins User: Jesse Glick Path: core/src/main/resources/lib/form/apply/apply.js http://jenkins-ci.org/commit/jenkins/e292366f62e511323442a03abdcf020396cbc407 Log: Merge pull request #1077 from daniel-beck/better-apply-dialog JENKINS-20772 Fix scrolling Compare: https://github.com/jenkinsci/jenkins/compare/f2e2cbeca421...e292366f62e5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-21133) Periodical crashes of jenkins with loss css-styles.
Will D commented on JENKINS-21133 Periodical crashes of jenkins with loss css-styles. I'm having the same problem – CentOS 6.4, Java 1.6, Jenkins 1.541. Attempting builds/restarts via post request results in 403 errors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
dogfood commented on JENKINS-20772 'Apply' error screens don't work Integrated in jenkins_main_trunk #3135 JENKINS-20772 Only show error message in dialog (Revision b856cc2434b33ed7fec3492223e141747369bba3) Result = SUCCESS daniel-beck : b856cc2434b33ed7fec3492223e141747369bba3 Files : core/src/main/resources/lib/form/apply/apply.js core/src/main/resources/jenkins/model/Jenkins/oops.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
dogfood commented on JENKINS-20772 'Apply' error screens don't work Integrated in jenkins_main_trunk #3136 JENKINS-20772 Fix scrolling (Revision 9b947ae8a239023482b8dcdec97d37425c42be8c) Result = SUCCESS daniel-beck : 9b947ae8a239023482b8dcdec97d37425c42be8c Files : core/src/main/resources/lib/form/apply/apply.js This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for "--progress" option in 1.7.x version of git client binary
dev @ doxo.com created JENKINS-21137 git fetch does not have support for "--progress" option in 1.7.x version of git client binary Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git-client Created: 24/Dec/13 1:54 AM Description: I'm not precisely sure when the "--progress" option was added to the "git fetch" command, but I know that it was not supported in version 1.7.0.4. I know it is supported in version 1.8.5.2, so I wouldn't be surprised if it was added to version 1.8 of the git client binary. My preference would be a workaround similar to what was added when "git clone" started specifying the "-progress" option. Namely a check for the git binary version prior to attempting to use the "-progress" option. See JENKINS-9635. Project: Jenkins Priority: Critical Reporter: dev @ doxo.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Takayuki Hirota edited a comment on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I encountered related issue on Linux and Mac OS X with Atlassian Stash 2.10.0 repos(via https). I fixed this problem on my branch and tested. It works for me. https://github.com/thirota/git-client-plugin/tree/fix-credential-store-path CentOS 6.4, git 1.8.5.2 and Jenkins 1.544 Mac OS X 10.9, git 1.8.3.4 (Apple Git-47) and Jenkins 1.544 Sorry, I could not test on Windows. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Takayuki Hirota commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I had same error too. I think git cannot read credential temp file(/tmp/git3351626511932244072.credentials) in.git/config. fatal: could not read Username for 'https://github.com': No such device or address This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-remote-trigger] (JENKINS-20827) Integrate token macro plugin
Tyrel Alastair Hunter commented on JENKINS-20827 Integrate token macro plugin Submitted a pull request for this feature. https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scp] (JENKINS-21138) scp plugin throws exception while uploading console log
Khai Do created JENKINS-21138 scp plugin throws exception while uploading console log Issue Type: Bug Assignee: Khai Do Components: scp Created: 24/Dec/13 5:36 AM Description: During upload of console log an exception is thrown and the connection pipe gets closed which results in copying only a portion of the console log to the remote server. This feature was working when used with Jenkins 1.525, but started to fail when I upgraded to Jenkins 1.540. The exception occurs when writer.flush() is called in ConsoleRunnable thread. steps to repro: 1. get and install the latest version of the scp plugin 2. goto jenkins global config page and configure an scp server 3. create a new job 4. add a 'Publish artifacts to SCP Repository' build step 5. select to copy console log 6. run a build (with a relatively large log maybe ~5 MB) 7. verify that entire console log is copied to the remote server. Environment: Ubuntu precise Java 1.7 Maven 3.1 Project: Jenkins Labels: log consoleoutput plugin scp Priority: Major Reporter: Khai Do This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Update: I checked also the 1.54X versions (1.541, 1.542, 1.543, 1.544) and the memory leak issue is also on all release 1.54X versions! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
