[JIRA] [conditional-buildstep] (JENKINS-22600) Sub-projects that defined in conditional steps appeared as Static and Other executed recently at job main page
Gosha Frost created JENKINS-22600 Sub-projects that defined in conditional steps appeared as Static and Other executed recently at job main page Issue Type: Bug Assignee: Dominik Bartholdi Attachments: configure.png, jobA.png Components: conditional-buildstep, parameterized-trigger Created: 14/Apr/14 7:02 AM Description: Scenario: The job A launches two sub jobs B and C according to the condition steps. Issue: Main page of job A shows the sub-projects B and C twice as "Static" and "Other executed recently" In case of one sub-project the behavior is correct - only "Static" is appearing. See attached screenshots Environment: Jenkins 1.532.2 Parameterized Trigger plugin 2.24 conditional-buildstep 1.3.3 Project: Jenkins Priority: Minor Reporter: Gosha Frost This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameters] (JENKINS-19560) Parameterized build only takes DEFAULT value
Tom Ghyselinck commented on JENKINS-19560 Parameterized build only takes DEFAULT value It's not during polling, it's during checkout. The variable $VERSION from the "list subversion tags plugin" is not resolved when no default value is configured. ( It is resolved when the default value is filled in! ) But we want the default value to be selected by the "Sort newest first" and "Sort Z to A" configuration item. Note When both are selected, I suggest preference for "Sort newest first". "Sort Z to A" can then be used in second stage when 2 tags have been modified at the same time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-21003) ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading
Lucie Votypkova commented on JENKINS-21003 ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading Hi, I can cashed information about build size, it is not problem. there should be max 3 threads for calculation disk usage (calculation of workspaces, calculation of jobs, calculation of builds). I agree this is a serious bug, I will write tests for it so it will not happen again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-21003) ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading
Lucie Votypkova commented on JENKINS-21003 ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading Oh sorry I read badly your comment recampbell. I checked the code and cashed information about build size is not problem, but the problem will be a filtering. Pluigin provides a filter build disk usage by age of build - this is necessary feature for our instance to identify jobs which old builds take a lot of disk space. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-21003) ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading
Lucie Votypkova edited a comment on JENKINS-21003 ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading Another thing is recalculation threads - they break lazy loading too, it is possible to disable then, but I think that I should do something with them too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-21003) ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading
Lucie Votypkova commented on JENKINS-21003 ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading Another think is recalculation threads - they break lazy loading too, it is possible to disable then, but I think that I should do something with them too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm] (JENKINS-21892) Swarm client fails to create slave if CSRF filter is enabled
neiltingley commented on JENKINS-21892 Swarm client fails to create slave if CSRF filter is enabled Simon, trying your patch with latest LTS version ver. 1.532.3 Am getting the same error as you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22601) Prodive option for -f / force in git push (after tagging)
Steffen Buehl created JENKINS-22601 Prodive option for -f / force in git push (after tagging) Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, git-chooser-alternative Created: 14/Apr/14 9:09 AM Description: If the "create tag" "update new tag" options are checked, git should push the created/updated with -f / force, otherwise the (central) git repository would reject the updated tag and the build fails. i don't know if this is already achievable with some update hook hacking (delete tag on tag-push?) Project: Jenkins Priority: Minor Reporter: Steffen Buehl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit-trail] (JENKINS-22602) NullPointerException in AuditTrailFilter#doFilter() when HttpServletRequest.getPathInfo() is null
Cyrille Le Clerc created JENKINS-22602 NullPointerException in AuditTrailFilter#doFilter() when HttpServletRequest.getPathInfo() is null Issue Type: Bug Affects Versions: current Assignee: Cyrille Le Clerc Components: audit-trail Created: 14/Apr/14 9:16 AM Description: java.lang.NullPointerException java.util.regex.Matcher.getTextLength(Unknown Source) java.util.regex.Matcher.reset(Unknown Source) java.util.regex.Matcher.init(Unknown Source) java.util.regex.Pattern.matcher(Unknown Source) hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:60) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) hudson.plugins.cloudbees.account.EC2CloudListener$2.doFilter(EC2CloudListener.java:57) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) org.jvnet.hudson.plugins.cors.JenkinsCorsFilter.doFilter(JenkinsCorsFilter.java:42) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) com.cloudbees.jenkins.plugins.dacsecurity.auth.VerifyHostFilter.doFilter(VerifyHostFilter.java:33) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) com.cloudbees.jenkins.plugins.dacsecurity.auth.CloudBeesBasicAuthFilter.doFilter(CloudBeesBasicAuthFilter.java:122) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) Project: Jenkins Priority: Major Reporter: Cyrille Le Clerc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from
[JIRA] [audit-trail] (JENKINS-22602) NullPointerException in AuditTrailFilter.doFilter() when HttpServletRequest.getPathInfo() is null
Cyrille Le Clerc
updated JENKINS-22602
NullPointerException in AuditTrailFilter.doFilter() when HttpServletRequest.getPathInfo() is null
Change By:
Cyrille Le Clerc
(14/Apr/14 9:22 AM)
Summary:
NullPointerExceptioninAuditTrailFilter
#
.
doFilter()whenHttpServletRequest.getPathInfo()isnull
Description:
{noformat}java.lang.NullPointerException java.util.regex.Matcher.getTextLength(UnknownSource) java.util.regex.Matcher.reset(UnknownSource) java.util.regex.Matcher.init(UnknownSource) java.util.regex.Pattern.matcher(UnknownSource) hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:60) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) hudson.plugins.cloudbees.account.EC2CloudListener$2.doFilter(EC2CloudListener.java:57) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) org.jvnet.hudson.plugins.cors.JenkinsCorsFilter.doFilter(JenkinsCorsFilter.java:42) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) com.cloudbees.jenkins.plugins.dacsecurity.auth.VerifyHostFilter.doFilter(VerifyHostFilter.java:33) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) com.cloudbees.jenkins.plugins.dacsecurity.auth.CloudBeesBasicAuthFilter.doFilter(CloudBeesBasicAuthFilter.java:122) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164){noformat}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder We used the EnvInject plugin to run some tests before the repo is checked out. When building multiple configurations, there seems to be 3 git repositories, the one in the regular workspace that is checked out by the main job, and then for each configuration, another repo living in workspace/VAR/VALUE, where the project is really built. We suspect those configuration-specific copies are not updated for some reason, and thus origin/pr/XXX/merge points to an old commit that is not present in that particular repo anymore. We wanted to force a git fetch on those repos before the checkout, but the problem is bofore the check those repo don't even exist! It looks like jenkins do a clone for them or something. Another weird thing is after doing this experimentation with EnvInject, the problematic PR got "fixed". We suspect that something might have been cleaned when the pre-checkout commit failed, and the checkout was never done, but all these are just wild guesses. We'll continue to investigate this as much as possible, but all points to some conflict with multiple configuration builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm] (JENKINS-21892) Swarm client fails to create slave if CSRF filter is enabled
neiltingley edited a comment on JENKINS-21892 Swarm client fails to create slave if CSRF filter is enabled Patch works for me on latest LTS. (Make sure you use the patched swarm client jar!). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-22603) Add support Dashboard View
Dmitry Ryltsov created JENKINS-22603 Add support Dashboard View Issue Type: New Feature Assignee: jpiironen Components: robot-plugin Created: 14/Apr/14 11:25 AM Description: Hello! Please add support for Dashboard + View https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View Project: Jenkins Labels: dashboard robot Priority: Major Reporter: Dmitry Ryltsov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-21003) ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading
Lucie Votypkova commented on JENKINS-21003 ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading Moving information into separate xml file diskUsage.xml from build.xml should solve problems with lazy loading. During starting all information will be cashed from diskUsage.xml files of non loaded builds. Recalculation thread will update only diskUsage.xml job and update cashed information from nonloaded builds. I hope tested implementation will be 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/d/optout.
[JIRA] [email-ext] (JENKINS-20384) Please improve triggers UI
Alex Earl resolved JENKINS-20384 as Fixed Please improve triggers UI Completed all the items I agreed with (which is the majority). Change By: Alex Earl (14/Apr/14 12:57 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/d/optout.
[JIRA] [core] (JENKINS-22275) Save of job configuration doesn't work after removing a parameter under 'This build is parameterized'
wbauer commented on JENKINS-22275 Save of job configuration doesnt work after removing a parameter under This build is parameterized Same issue here with Chrome 34.0.1847.45 and Safari 7.0.3 (9537.75.14). It works fine in Firefox 25.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22604) WebSphere-deployer Plugin doesnot work with Security Emnabled WAS
sakshi kataria created JENKINS-22604 WebSphere-deployer Plugin doesnot work with Security Emnabled WAS Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin, security Created: 14/Apr/14 2:02 PM Description: I have configured jenkins with WebSphere-deployer plugin, but its not working with security enabled WebSphere Application Server. Kindly help me to resolve this asap. Due Date: 15/Apr/14 12:00 AM Environment: Windows Fix Versions: current Project: Jenkins Priority: Critical Reporter: sakshi kataria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22601) Prodive option for -f / force in git push (after tagging)
Mark Waite updated JENKINS-22601 Prodive option for -f / force in git push (after tagging) Change By: Mark Waite (14/Apr/14 2:22 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22601) Provide option for -f / force in git push (after tagging)
Mark Waite updated JENKINS-22601 Provide option for -f / force in git push (after tagging) Change By: Mark Waite (14/Apr/14 2:23 PM) Summary: Prodive Provide optionfor-f/forceingitpush(aftertagging) Component/s: 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/d/optout.
[JIRA] [git-client] (JENKINS-22119) Fail to update update git repository with stored credential
Mikkel Larsen
commented on JENKINS-22119
Fail to update update git repository with stored credential
I finally had some time to dig into this.
What caused the problem for me was that when you copy the https address from a private repository on bitbucket it is displayed as:
https://usern...@bitbucket.com/username/repo.git
and for a public repo it is:
https://bitbucket.com/username/repo.git
Removing the `username@` from the url in the jenkins setup, fixes the problem for private repos.
A fix that would allow either format would be to strip the username@ from the url in the `checkCredentials()`: https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1854
e.g something like this:
diff --git a/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java b/src/main/java/org/jenkins
index 9fd48ab..feb95d2 100644
--- a/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
+++ b/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
@@ -1843,6 +1843,7 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
*/
private void checkCredentials(URIish u, StandardCredentials cred) {
String url = ""
+url = "" class="code-quote">"[\\w]+@", "");
final HttpClientBuilder clientBuilder = HttpClients.custom();
final CredentialsProvider credentialsProvider = new BasicCredentialsProvider();
clientBuilder.setDefaultCredentialsProvider(credentialsProvider);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22119) Fail to update update git repository with stored credential
Mikkel Larsen
edited a comment on JENKINS-22119
Fail to update update git repository with stored credential
I finally had some time to dig into this.
What caused the problem for me was that when you copy the https address from a private repository on bitbucket it is displayed as:
https://usern...@bitbucket.org/username/repo.git
and for a public repo it is:
https://bitbucket.org/username/repo.git
Removing the `username@` from the url in the jenkins setup, fixes the problem for private repos.
A fix that would allow either format would be to strip the username@ from the url in the `checkCredentials()`: https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1854
e.g something like this:
diff --git a/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java b/src/main/java/org/jenkins
index 9fd48ab..feb95d2 100644
--- a/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
+++ b/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
@@ -1843,6 +1843,7 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
*/
private void checkCredentials(URIish u, StandardCredentials cred) {
String url = ""
+url = "" class="code-quote">"[\\w]+@", "");
final HttpClientBuilder clientBuilder = HttpClients.custom();
final CredentialsProvider credentialsProvider = new BasicCredentialsProvider();
clientBuilder.setDefaultCredentialsProvider(credentialsProvider);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22119) Fail to update update git repository with stored credential
Mark Waite commented on JENKINS-22119 Fail to update update git repository with stored credential I would expect that change to break several other use cases (like the ssh use case I use to push changes back to a GitHub repository). I think users will need to use the work around for the problem case you described (butbucket https URL's behave better without the username embedded in the URL). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder Also, I think this problem only happens when a PR is being tested and there is a push -f in the same PR, so a new build is queued. After that happens, the build seems to stay broken. Any idea about how this push -f while the PR is being tested can end up in this situation? Is any information about the hash being stored somewhere that is read then by the queued build for the same PR? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22119) Fail to update update git repository with stored credential
Mikkel Larsen commented on JENKINS-22119 Fail to update update git repository with stored credential checkCredentials() seems to only deal with HTTP so I can't see how that would affect ssh? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22605) The Links for the disk-usage plugin are missing a plugin String in the Path
Samir Huremovic created JENKINS-22605 The Links for the disk-usage plugin are missing a plugin String in the Path Issue Type: Bug Assignee: Lucie Votypkova Components: disk-usage Created: 14/Apr/14 2:42 PM Description: In our environment we are using a prefix for the Webapp (I only mention this, because I dont know if the problem occurs only with a prefix enabled). The links/paths generated are not correct, they dont contain "plugin". Example: https://myserver/jenkins10prefix/disk-usage/ does not work. Corrected path: https://myserver/jenkins10prefix/plugin/disk-usage/ does work. It seems that all of the links for the disk-usage plugin in Jenkins are not correct. Environment: RHEL 6.4, Jenkins 1.559, disk-usage 0.23 Project: Jenkins Priority: Major Reporter: Samir Huremovic This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder I can reproduce this easily now, is that, pushing --force to a PR that's being tested already in Jenkins. A simple test is just have a dummy project, which just a build script that is a sleep 60. Then create a PR, wait until jenkins runs the job to build it, while is at it, do a git rebase --force HEAD^ to the project and push --force to the PR branch and boom! If configurations are really a problem or not needs to be confirmed still, I'll do that as soon as possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13314) Remote API does not include downstream/upstream build info
Jim Divine commented on JENKINS-13314 Remote API does not include downstream/upstream build info This would be incredibly useful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Mark Waite commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder Thanks very much for the detailed investigation! I think that means this bug has the same symptoms as JENKINS-21980. Could you construct a Java based test case (in the git-plugin source code) which shows the failure? That would increase the chances of someone who knows the plugin finding a solution for the problem. I think the issue is in the git-plugin handling of the case where a SHA1 was valid for a previous build, but is no longer valid. In that case, I assume the plugin should ignore the bad SHA1 and checkout something else instead. Do you have a recommendation for what should be used instead of the invalid SHA1? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Leandro Lucarella commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder I think the pr builder plugin should just do the git fetch with the pull request references and then just use the symbolic name of the references (origin/pr/N/merge) instead of using any hash. But I don't know exactly how is the interaction between this plugin and the git-plugin, I'm just thinking in terms of plain git commands. I really don't see why any of the plugins should use any numeric old hash. I'll do my best to try to reproduce this with a Java test case, but I can't promise anything because my Java-fu is practically non-existant (even when Java as a language is easy, the thousands layers of libraries are not easy to grasp at all :S). Also, I'll take another look at JENKINS-21980 now that I have a better idea of where the issue is. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-21003) ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading
Jesse Glick commented on JENKINS-21003 ProjectDiskUsageAction.getBuildsDiskUsageAllSubItems breaks lazy-loading Why not keep a single file per job listing disk usage for every build? (Possibly in properties format, if the content is sufficiently simple.) This would be a lot faster to load than hundreds of little XML files. Of course you would need to update it when a new build is created; unnecessary to do so when an old build is deleted, since you can just ignore entries for builds whose directories (Run.id) do not still exist. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-21776) Jenkins jira comment text typo
Tristan Amini assigned JENKINS-21776 to Tristan Amini Jenkins jira comment text typo Change By: Tristan Amini (14/Apr/14 3:25 PM) Assignee: TristanAmini This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22606) People view lists no people when viewed with IE9
davida2009 created JENKINS-22606 People view lists no people when viewed with IE9 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 14/Apr/14 3:31 PM Description: If I view the Jenkins People View using IE9 no people are listed and the IE9 _javascript_ console shows an error: SCRIPT5007: Unable to set value of the property 'innerHTML': object is null or undefined sortable.js, line 209 character 17 The people list is properly populated when viewed with Firefox 28.0. Project: Jenkins Priority: Major Reporter: davida2009 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Jesse Glick updated JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Something similar reported by a user of 1.532.2. Was using Perforce plugin (and others), but not Ivy. Trigger condition as yet unknown. Change By: Jesse Glick (14/Apr/14 4:12 PM) Assignee: NicolasDeLoof Priority: Minor Major Component/s: ivy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-21776) Jenkins jira comment text typo
SCM/JIRA link daemon commented on JENKINS-21776 Jenkins jira comment text typo Code changed in jenkins User: Tristan Amini Path: src/main/java/hudson/plugins/jira/JiraCreateIssueNotifier.java http://jenkins-ci.org/commit/jira-plugin/dac6aad228db514048755b2786fae1c8955c622a Log: JENKINS-21776 Fixed typo in JiraCreateIssueNotifier. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-21776) Jenkins jira comment text typo
SCM/JIRA link daemon commented on JENKINS-21776 Jenkins jira comment text typo Code changed in jenkins User: artkoshelev Path: src/main/java/hudson/plugins/jira/JiraCreateIssueNotifier.java http://jenkins-ci.org/commit/jira-plugin/eaa8760d560029bf1f920ff8eab46053bad2cc13 Log: Merge pull request #40 from Tamini/master JENKINS-21776 Fixed typo in JiraCreateIssueNotifier. Compare: https://github.com/jenkinsci/jira-plugin/compare/9c9e780c0607...eaa8760d5600 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Jesse Glick updated JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Change By: Jesse Glick (14/Apr/14 4:19 PM) Labels: concurrent-buildworkspace This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-21776) Jenkins jira comment text typo
Tristan Amini resolved JENKINS-21776 as Fixed Jenkins jira comment text typo Change By: Tristan Amini (14/Apr/14 4:26 PM) Status: Open Resolved Assignee: TristanAmini Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
David Humeniuk commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I'm still seeing this issue with git client plug-in 1.8.0. Here's the specific message: Started on Apr 14, 2014 12:00:10 PM Using strategy: Default poll Last Built Revision: Revision e28681748de2b634ab6cd68c55dc0ac349e6b872 (origin/master) using .gitcredentials to set credentials Could not remove the credential section from the git configuration FATAL: Command "git config --local credential.helper store --file=\"C:\Users\IDTASK~1\AppData\Local\Temp\git4905599288427248808.credentials\"" returned status code 255: stdout: stderr: error: could not lock config file .git/config: File exists hudson.util.IOException2: Command "git config --local credential.helper store --file=\"C:\Users\IDTASK~1\AppData\Local\Temp\git4905599288427248808.credentials\"" returned status code 255: stdout: stderr: error: could not lock config file .git/config: File exists at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:459) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1567) at hudson.model.AbstractProject.poll(AbstractProject.java:1490) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: hudson.plugins.git.GitException: Command "git config --local credential.helper store --file=\"C:\Users\IDTASK~1\AppData\Local\Temp\git4905599288427248808.credentials\"" returned status code 255: stdout: stderr: error: could not lock config file .git/config: File exists at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1276) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1253) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1249) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1245) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1142) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1091) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1082) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:1739) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:492) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:457) ... 13 more Done. Took 13 sec No changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22607) LogRotator inefficient when number of builds to kept is very large
Jesse Glick created JENKINS-22607 LogRotator inefficient when number of builds to kept is very large Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Apr/14 4:32 PM Description: If you have configured LogRotator to delete all builds older than 30 days, yet you do around 1000 builds a day, then at the end of each build LogRotator.perform will scan backwards from the previous build all the way to the first build (or nearby), loading each build along the way, just to find the (on average) one build which is now older than 30 days so it can be deleted. This forces thousands of builds to be kept in memory, or if they cannot all be held in memory, forces each build to reload thousands of older build records that it does not really need. Would be better to do a binary search through the build history to find the newest build which is suitable for deletion. Project: Jenkins Labels: performance lazy-loading log-rotator Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-22608) Inject variables into success/fail comments
Alex Conrad
created JENKINS-22608
Inject variables into success/fail comments
Issue Type:
Improvement
Assignee:
Honza Brázdil
Components:
ghprb
Created:
14/Apr/14 5:08 PM
Description:
When Jenkins submits a comment to Github whether a test passed or failed, I need more information in the message. I would like to see jobs customize the post-build message by injecting environment variables, such as:
Test PASSed, code coverage is at ${COVERAGE_PERCENTAGE}%.
Project:
Jenkins
Priority:
Major
Reporter:
Alex Conrad
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
SCM/JIRA link daemon commented on JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/slaves/WorkspaceList.java http://jenkins-ci.org/commit/jenkins/3dc0a444068601a61930af4c422ffefdd0928063 Log: JENKINS-21622 Trying to diagnose who is acquiring workspace leases when and why. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Mark Waite commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) David Humeniuk I believe that stack trace is different than the other stack traces reported in this bug report. It seems to be similar to the stack trace in JENKINS-21914. In both cases, the problem is visible on Windows. Can you confirm that there are no "orphan" git.exe processes running on the machine which shows the problem? If there are orphan git processes, can you kill them and see if that resolves your issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core] (JENKINS-22609) Job container statistics omit other top-level items
Jesse Glick commented on JENKINS-22609 Job container statistics omit other top-level items Would also be sensible to just omit mention of types with no instances. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core] (JENKINS-22609) Job container statistics omit other top-level items
Jesse Glick created JENKINS-22609 Job container statistics omit other top-level items Issue Type: Improvement Assignee: Unassigned Components: support-core Created: 14/Apr/14 5:16 PM Description: about.md lists statistics about Job and ItemGroup instances, with some overlap (for example for MavenModuleSet instances), but omitting any mention of other TopLevelItem instances such as update centers. Would be better to just list all TopLevelItem types, and for those which are also a Jpb, show build count statistics, and for those which are also ItemGroup, show item count statistics. Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-template] (JENKINS-22610) Removing (deleting) Email Notification Templates will cause the associated builds to fail.
Matthew Kruer created JENKINS-22610 Removing (deleting) Email Notification Templates will cause the associated builds to fail. Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext-template Created: 14/Apr/14 5:20 PM Description: Removing (deleting) Email Notification Templates will cause the associated builds to fail until the job is updated to reflect the template is no longer to be used. Steps to reproduce: 1. Create two Templates in Email Notification Templates 2. Add both Templates to a job, and run job, see success 3. Edit Email Notification Templates, and remove on of the templates 4. Run job again, See error The Job should not fail because of a missing template, but it still might be good idea to bitch that there is a missing template and then remove it? Project: Jenkins Priority: Minor Reporter: Matthew Kruer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Jesse Glick commented on JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Diagnostic build: http://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-war/1.532.2.JENKINS-21622-diag/jenkins-war-1.532.2.JENKINS-21622-diag.war This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-21362) Multiple (User Defined) Global Templates
Matthew Kruer commented on JENKINS-21362 Multiple (User Defined) Global Templates Testing it out now, found one minor issue https://issues.jenkins-ci.org/browse/JENKINS-22610 I am temped to file another bug on the name of the plugin (email-ext-template or emailext-template or email-ext-template-plugin? seems to be liested three diffrent ways. Going forward I will be reporting bug under email-ext-template. Good work, this should make my life and anyone elases that had to do mass e-mails much easier going forward. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-21362) Multiple (User Defined) Global Templates
Alex Earl commented on JENKINS-21362 Multiple (User Defined) Global Templates Hmmm, where are the different ways it is reported? Please do file an issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-template] (JENKINS-22610) Removing (deleting) Email Notification Templates will cause the associated builds to fail.
Alex Earl commented on JENKINS-22610 Removing (deleting) Email Notification Templates will cause the associated builds to fail. Can you post the build log with the error message? I am thinking you are seeing an NPE or something? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-template] (JENKINS-22610) Removing (deleting) Email Notification Templates will cause the associated builds to fail.
Matthew Kruer commented on JENKINS-22610 Removing (deleting) Email Notification Templates will cause the associated builds to fail. tarted by user anonymous Building on master in workspace /var/lib/jenkins/workspace/Step_1_-_Create_Development_Repository Deleting project workspace... done No emails were triggered. FATAL: null java.lang.NullPointerException at org.jenkinsci.plugins.emailext_template.ExtendedEmailTemplatePublisher.prebuild(ExtendedEmailTemplatePublisher.java:51) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:819) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:814) at hudson.model.Build$BuildExecution.doRun(Build.java:142) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:566) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22611) Triggered by SCM multiple times
Patrik Boström created JENKINS-22611 Triggered by SCM multiple times Issue Type: Bug Assignee: Unassigned Components: delivery-pipeline Created: 14/Apr/14 5:48 PM Description: Triggered by SCM shows multiple times Project: Jenkins Priority: Minor Reporter: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-template] (JENKINS-22610) Removing (deleting) Email Notification Templates will cause the associated builds to fail.
Alex Earl commented on JENKINS-22610 Removing (deleting) Email Notification Templates will cause the associated builds to fail. Just as I thought. Should be an easy fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22611) Triggered by SCM multiple times
Patrik Boström updated JENKINS-22611 Triggered by SCM multiple times Change By: Patrik Boström (14/Apr/14 5:51 PM) Attachment: screenshot.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/d/optout.
[JIRA] [dynamic-axis] (JENKINS-22612) Parametrizeds jobs do not save after to exclude a parameter
Cleber Pereira created JENKINS-22612 Parametrizeds jobs do not save after to exclude a parameter Issue Type: Bug Assignee: Cleber Pereira Components: dynamic-axis, dynamic_extended_choice_parameter, parameterized-trigger, parameters Created: 14/Apr/14 5:54 PM Description: The problem occurs after trying to delete a parameter in a parameterized job. Unable to save this change. Clicking the save button, nothing happens. This may have occurred after the installation of Dynamic Parameter Plug-in. Due Date: 02/Apr/13 12:00 AM Environment: SO: SO Linux, amd64/64 (4 cores) Java: Java(TM) SE Runtime Environment, 1.6.0_43-b01 JVM: Java HotSpot(TM) 64-Bit Server VM, 20.14-b01, mixed mode Jenkins Version: 1.558 Project: Jenkins Labels: plugin parameter parameterized save job dont Priority: Major Reporter: Cleber Pereira This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-15086) Copy artifacts via permalink doesn't work from a promotion action
Jesse Glick updated JENKINS-15086 Copy artifacts via permalink doesnt work from a promotion action Change By: Jesse Glick (14/Apr/14 5:58 PM) Summary: copy Copy artifactsviapermalinkdoesntwork fromapromotionaction This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-19007) copy artifacts via permalink for promoted builds shows wrong link
Jesse Glick commented on JENKINS-19007 copy artifacts via permalink for promoted builds shows wrong link While working on JENKINS-22590 I saw something similar to this but it goes away if you click around a bit; in other words, the problem is related to automatic refreshing of form completions. Probably a Jenkins core bug fixed in later Jenkins versions. Anyway my forthcoming proposed fix of JENKINS-22590 always offers a generic list of permalinks when the upstream job name is not understood, rather than showing permalinks from the current job, which makes no sense. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-template] (JENKINS-22613) email-ext-template plugin has many names
Matthew Kruer created JENKINS-22613 email-ext-template plugin has many names Issue Type: Bug Assignee: Alex Earl Components: email-ext-template Created: 14/Apr/14 6:04 PM Description: Jenkins bug reporting (this site) the label from the plugin is email-ext-template Git Hub uses email-ext-template-plugin https://github.com/jenkinsci/email-ext-template-plugin Jenkins lists the name as emailext-template http://jenkins-ci.org/plugin/emailext-template/ plugin repo uses emailext-template http://updates.jenkins-ci.org/download/plugins/emailext-template/0.1-beta/ To avoid confusion I would think they would all use the same name? Project: Jenkins Priority: Minor Reporter: Matthew Kruer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22590) Promotion permalinks not offered when job name is parameterized
Jesse Glick assigned JENKINS-22590 to Jesse Glick Promotion permalinks not offered when job name is parameterized Change By: Jesse Glick (14/Apr/14 6:05 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22590) Promotion permalinks not offered when job name is parameterized
Jesse Glick updated JENKINS-22590 Promotion permalinks not offered when job name is parameterized Change By: Jesse Glick (14/Apr/14 6:05 PM) URL: https://github.com/jenkinsci/copyartifact-plugin/pull/34 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-21362) Multiple (User Defined) Global Templates
Alex Earl updated JENKINS-21362 Multiple (User Defined) Global Templates Change By: Alex Earl (14/Apr/14 6:07 PM) Component/s: emailext-template Component/s: email-ext-template This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-22590) Promotion permalinks not offered when job name is parameterized
Jesse Glick commented on JENKINS-22590 Promotion permalinks not offered when job name is parameterized Editing config.xml directly (via POST, for example) does work as a workaround in my experiments. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-template] (JENKINS-22613) email-ext-template plugin has many names
Alex Earl commented on JENKINS-22613 email-ext-template plugin has many names Agreed...I'll try and clean this up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [emailext-template] (JENKINS-22610) Removing (deleting) Email Notification Templates will cause the associated builds to fail.
Alex Earl updated JENKINS-22610 Removing (deleting) Email Notification Templates will cause the associated builds to fail. Change By: Alex Earl (14/Apr/14 6:08 PM) Component/s: emailext-template Component/s: email-ext-template This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
dogfood commented on JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Integrated in jenkins_main_trunk #3306 JENKINS-21622 Trying to diagnose who is acquiring workspace leases when and why. (Revision 3dc0a444068601a61930af4c422ffefdd0928063) Result = SUCCESS Jesse Glick : 3dc0a444068601a61930af4c422ffefdd0928063 Files : core/src/main/java/hudson/slaves/WorkspaceList.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/d/optout.
[JIRA] [emailext-template] (JENKINS-22613) email-ext-template plugin has many names
Alex Earl updated JENKINS-22613 email-ext-template plugin has many names Change By: Alex Earl (14/Apr/14 6:09 PM) Component/s: emailext-template Component/s: email-ext-template This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [emailext-template] (JENKINS-22613) email-ext-template plugin has many names
Matthew Kruer commented on JENKINS-22613 email-ext-template plugin has many names No worries, It happens. Catching it early helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-22608) Inject variables into success/fail comments
Marc Abramowitz commented on JENKINS-22608 Inject variables into success/fail comments I agree. This would be super useful for doing custom things on top of ghprb like measuring the change in coverage from a PR, doing lint checks, 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/d/optout.
[JIRA] [emailext-template] (JENKINS-22614) Centralized reporting and configuration of emailext-templates
Matthew Kruer created JENKINS-22614 Centralized reporting and configuration of emailext-templates Issue Type: Improvement Assignee: Alex Earl Components: emailext-template Created: 14/Apr/14 6:26 PM Description: One of the things that I think would go well with the, especially if you are making a new configuration page would be to have the ability to view and possibly edit existing jobs that have the emailext-template enable. This is a quick overview of all the triggers. This could be taken to the next step where one could look at a tabularized data of jobs and templates and edit them on one page without have to go each job itself This might be best added to the email-ext-recipients-column as they are sort of doing it already. Project: Jenkins Priority: Major Reporter: Matthew Kruer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22028) HTML in job description does not get rendered (all html tags escaped)
Edin Mujkanovic commented on JENKINS-22028 HTML in job description does not get rendered (all html tags escaped) We have the same problem with iframes defined in the description fields not being rendered. All other HTML works fine though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22485) Cannot save job configuration after deleting a parameter
Townsend Duong commented on JENKINS-22485 Cannot save job configuration after deleting a parameter It seems to work on Firefox as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22607) LogRotator inefficient when number of builds to kept is very large
Jesse Glick assigned JENKINS-22607 to Jesse Glick LogRotator inefficient when number of builds to kept is very large Change By: Jesse Glick (14/Apr/14 6:47 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22607) LogRotator inefficient when number of builds to kept is very large
Jesse Glick started work on JENKINS-22607 LogRotator inefficient when number of builds to kept is very large Change By: Jesse Glick (14/Apr/14 6:47 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22607) LogRotator inefficient when number of builds to kept is very large
Jesse Glick commented on JENKINS-22607 LogRotator inefficient when number of builds to kept is very large Fixing this when numToKeep is set looks impractical, since AbstractLazyLoadRunMap.idOnDisk is not exposed (not even its size), and so there is no way of knowing which build is the 3th oldest—you cannot rely on this having a particular build number. Fixing it for daysToKeep looks easier since you can simply browse forward from the oldest build and keep on deleting them so long as they are sufficiently old. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22607) LogRotator inefficient when number of builds to kept is very large
Jesse Glick commented on JENKINS-22607 LogRotator inefficient when number of builds to kept is very large Not sure if the fix should be lts-candidate, given that it does not work for numToKeep. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22485) Cannot save job configuration after deleting a parameter
Jeremy Kissell commented on JENKINS-22485 Cannot save job configuration after deleting a parameter Installing firefox on my Mac is a valid workaround, thank you! Note: Clicking APPLY still throws an error in firefox, but clicking SAVE does allow me to delete the parameter strings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-workspace-cleaner] (JENKINS-22331) java exception on svn update and checkout
David Pärsson commented on JENKINS-22331 java exception on svn update and checkout From the stacktrace, this seems to be related to the Subversion plugin and not the svn-workspace-cleaner plugin. I'm therefore closing this issue. Please reopen and assign to the proper component if this is still an issue. Sorry for the late response. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22607) LogRotator inefficient when number of builds to kept is very large
SCM/JIRA link daemon resolved JENKINS-22607 as Fixed LogRotator inefficient when number of builds to kept is very large Change By: SCM/JIRA link daemon (14/Apr/14 7:41 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22607) LogRotator inefficient when number of builds to kept is very large
SCM/JIRA link daemon commented on JENKINS-22607 LogRotator inefficient when number of builds to kept is very large Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/tasks/LogRotator.java http://jenkins-ci.org/commit/jenkins/d9188ce2ad2070eab5ea27cb7f96257b351392a7 Log: FIXED JENKINS-22607 Avoid loading recent builds when deletion of builds older than some date has been requested. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
David Humeniuk commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I'll report my status on the other issue since that seems to be more appropriate. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15604) checkUrl and codemirror-mode do not mix
Jesse Glick updated JENKINS-15604 checkUrl and codemirror-mode do not mix Tried to use the attached patch to add shell syntax highlighting to CommandInstaller in trunk. This seems to cause weird issues when reloading the configuration page; existing scripts are invisible until you start editing them, and with a zero-height textarea. Change By: Jesse Glick (14/Apr/14 8:13 PM) Attachment: x.diff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15604) checkUrl and codemirror-mode do not mix
Jesse Glick commented on JENKINS-15604 checkUrl and codemirror-mode do not mix Cf.: https://github.com/jenkinsci/script-security-plugin/blob/aa0c8b28290b5d77d160684f2ffc3737a1856e1b/src/main/resources/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SecureGroovyScript/config.jelly#L29 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-21914) Intermittent Git(hub) polling errors on Windows
David Humeniuk commented on JENKINS-21914 Intermittent Git(hub) polling errors on Windows I have the same issue. There are no git.exe processes running (I'm assuming that the polling would have to run on the master, that's what I checked). git.exe will show up in the task manager, but quickly disappear. When this happens, it is intermittent. Is it possible that Jenkins is trying to use the same file for multiple jobs or something? I tried installing the File Leak Detector plug-in, but got this error when I tried to activate: javax.servlet.ServletException: java.lang.Error: Failed to activate file leak detector: Connecting to 0 Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.file_leak_detector.Main.run(Main.java:50) at org.kohsuke.file_leak_detector.Main.main(Main.java:35) Caused by: java.io.IOException: no such process at sun.tools.attach.WindowsVirtualMachine.openProcess(Native Method) at sun.tools.attach.WindowsVirtualMachine.init(WindowsVirtualMachine.java:56) at sun.tools.attach.WindowsAttachProvider.attachVirtualMachine(WindowsAttachProvider.java:69) at com.sun.tools.attach.VirtualMachine.attach(VirtualMachine.java:213) ... 6 more It probably also noteworthy that I'm using this with the Stash Webhooks to Jenkins plug-in (https://marketplace.atlassian.com/plugins/com.nerdwin15.stash-stash-webhook-jenkins). That plug-in will trigger Jenkins to check for branches to build and I have several Jenkins jobs, one job for each development branch (plus several jobs for the master). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buildtriggerbadge] (JENKINS-22557) Column should have text in tooltip (like history)
Michael Pailloncy assigned JENKINS-22557 to Michael Pailloncy Column should have text in tooltip (like history) Change By: Michael Pailloncy (14/Apr/14 8:40 PM) Assignee: BaptisteMathus MichaelPailloncy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22607) LogRotator inefficient when number of builds to kept is very large
dogfood commented on JENKINS-22607 LogRotator inefficient when number of builds to kept is very large Integrated in jenkins_main_trunk #3307 FIXED JENKINS-22607 Avoid loading recent builds when deletion of builds older than some date has been requested. (Revision d9188ce2ad2070eab5ea27cb7f96257b351392a7) Result = SUCCESS Jesse Glick : d9188ce2ad2070eab5ea27cb7f96257b351392a7 Files : core/src/main/java/hudson/tasks/LogRotator.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22583) hetero-radio should work with multiple instances of the same ui
SCM/JIRA link daemon commented on JENKINS-22583 hetero-radio should work with multiple instances of the same ui Code changed in jenkins User: Stefan Wolf Path: pom.xml src/main/java/jenkins/plugins/ui_samples/HeteroList.java src/main/resources/jenkins/plugins/ui_samples/HeteroList/HeteroRadioEntry/config.jelly src/test/java/jenkins/plugins/ui_samples/HeteroListTest.java http://jenkins-ci.org/commit/ui-samples-plugin/06ecb947511f89b5d1f5c32c2fb56522f4e3d24b Log: JENKINS-22583 Added hetero-radio to Ui-Samples with roundtrip-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/d/optout.
[JIRA] [core] (JENKINS-22583) hetero-radio should work with multiple instances of the same ui
SCM/JIRA link daemon commented on JENKINS-22583 hetero-radio should work with multiple instances of the same ui Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/jenkins/plugins/ui_samples/HeteroList.java src/main/resources/jenkins/plugins/ui_samples/HeteroList/HeteroRadioEntry/config.jelly src/test/java/jenkins/plugins/ui_samples/HeteroListTest.java http://jenkins-ci.org/commit/ui-samples-plugin/edf3a3af0e71d3f9a8ff233671bfdaa7a8a165d0 Log: Merge pull request #2 from wolfs/hetero-radio JENKINS-22583 Added hetero-radio to Ui-Samples with roundtrip-test Compare: https://github.com/jenkinsci/ui-samples-plugin/compare/29361d447783...edf3a3af0e71 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buildtriggerbadge] (JENKINS-22557) Column should have text in tooltip (like history)
SCM/JIRA link daemon commented on JENKINS-22557 Column should have text in tooltip (like history) Code changed in jenkins User: Michael Pailloncy Path: src/main/resources/org/jenkinsci/plugins/buildtriggerbadge/LastBuildTriggerColumn/column.jelly http://jenkins-ci.org/commit/buildtriggerbadge-plugin/8b0424d0875c70537cdcf9ea5bd7143928a72faf Log: Fixing JENKINS-22557 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22583) hetero-radio should work with multiple instances of the same ui
SCM/JIRA link daemon commented on JENKINS-22583 hetero-radio should work with multiple instances of the same ui Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/lib/form/hetero-radio.jelly http://jenkins-ci.org/commit/jenkins/0faa7b7d2383320fc2357d687a6c535b20c7ef2b Log: Merge branch 'hetero-radio' of github.com:wolfs/jenkins JENKINS-22583 Noting merge of #1182. Conflicts: changelog.html Compare: https://github.com/jenkinsci/jenkins/compare/5789f0c75c37...0faa7b7d2383 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22583) hetero-radio should work with multiple instances of the same ui
SCM/JIRA link daemon commented on JENKINS-22583 hetero-radio should work with multiple instances of the same ui Code changed in jenkins User: Stefan Wolf Path: changelog.html http://jenkins-ci.org/commit/jenkins/b93d77119f0df2c89bc0c50727affe2a6755df76 Log: JENKINS-22583 Changelog This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22583) hetero-radio should work with multiple instances of the same ui
SCM/JIRA link daemon resolved JENKINS-22583 as Fixed hetero-radio should work with multiple instances of the same ui Change By: SCM/JIRA link daemon (14/Apr/14 9:08 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/d/optout.
[JIRA] [core] (JENKINS-22583) hetero-radio should work with multiple instances of the same ui
SCM/JIRA link daemon commented on JENKINS-22583 hetero-radio should work with multiple instances of the same ui Code changed in jenkins User: Stefan Wolf Path: core/src/main/resources/lib/form/hetero-radio.jelly http://jenkins-ci.org/commit/jenkins/0e845b678f7922a009709e113161f74bd6a90af1 Log: FIXED JENKINS-22583 Use unique id to distinguish between multiple included instances of the same 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/d/optout.
[JIRA] [www] (JENKINS-1968) Project or Job?
Martin dAnjou commented on JENKINS-1968 Project or Job? I am writing documentation to explain how to use Jenkins and I find myself having to explain that clicking on "New Job" creates a "Project". Very confusing. I think it is worth cleaning up the HTML. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
SCM/JIRA link daemon resolved JENKINS-21622 as Fixed Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Change By: SCM/JIRA link daemon (14/Apr/14 9:41 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
SCM/JIRA link daemon commented on JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractBuild.java http://jenkins-ci.org/commit/jenkins/decf902ab797b1ef5f5fb8f5c1651520c0fe33f2 Log: FIXED JENKINS-21622 Release workspace leases (and avoid @2) even if post-build actions throw LinkageError. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22196) Validation error when choosing a valid project as manual downstream project
Thomas Carsuzan commented on JENKINS-22196 Validation error when choosing a valid project as manual downstream project Hi, I am currently looking at your pull request. Tetra This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22615) Provide more helpful error message when missing required field
Tianming Zhao created JENKINS-22615 Provide more helpful error message when missing required field Issue Type: Improvement Assignee: Unassigned Components: plugin Created: 14/Apr/14 9:49 PM Description: When using job-dsl-plugin 1.21, I forgot to give the job a name, and I ended up getting error message as below. I would suggest to output a more helpful error message which, in this case, should reveal where exactly the problem was or prompt me more helpful information. As a newbie to Jenkins plugins, the following error message is very difficult for me to figure out the root cause. FATAL: the number of constructors during runtime and compile time for java.lang.RuntimeException do not match. Expected 5 but got 4 java.lang.IncompatibleClassChangeError: the number of constructors during runtime and compile time for java.lang.RuntimeException do not match. Expected 5 but got 4 at groovy.lang.MetaClassImpl.selectConstructorAndTransformArguments(MetaClassImpl.java:1381) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.selectConstructorAndTransformArguments(ScriptBytecodeAdapter.java:234) at javaposse.jobdsl.dsl.NameNotProvidedException.init(NameNotProvidedException.groovy:8) at javaposse.jobdsl.dsl.AbstractJobManagement.validateNameArg(AbstractJobManagement.java:67) at javaposse.jobdsl.dsl.AbstractJobManagement.validateUpdateArgs(AbstractJobManagement.java:58) at javaposse.jobdsl.plugin.JenkinsJobManagement.createOrUpdateConfig(JenkinsJobManagement.java:99) at javaposse.jobdsl.dsl.DslScriptLoader.extractGeneratedJobs(DslScriptLoader.java:122) at javaposse.jobdsl.dsl.DslScriptLoader.runDslEngine(DslScriptLoader.java:98) at javaposse.jobdsl.plugin.ExecuteDslScripts.perform(ExecuteDslScripts.java:159) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1575) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Project: Jenkins Priority: Minor Reporter: Tianming Zhao This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22616) Active Directory Plugin not working with project based authorization matrix
Alan Qian created JENKINS-22616 Active Directory Plugin not working with project based authorization matrix Issue Type: Bug Assignee: Unassigned Components: active-directory Created: 14/Apr/14 9:58 PM Description: We recently installed the Active Directory plugin, and are able to configure it to work when we click the 'Test' button. However, it does not seem to take effect when we try to add AD distribution groups into the project level authorization matrices. The plugin seem to pick up the group names correctly (no red X), but people in the group still don't see things like the 'build' link that they are supposed to have been granted. Project: Jenkins Priority: Minor Reporter: Alan Qian This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
dogfood commented on JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Integrated in jenkins_main_trunk #3309 FIXED JENKINS-21622 Release workspace leases (and avoid @2) even if post-build actions throw LinkageError. (Revision decf902ab797b1ef5f5fb8f5c1651520c0fe33f2) Result = SUCCESS Jesse Glick : decf902ab797b1ef5f5fb8f5c1651520c0fe33f2 Files : core/src/main/java/hudson/model/AbstractBuild.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22583) hetero-radio should work with multiple instances of the same ui
dogfood commented on JENKINS-22583 hetero-radio should work with multiple instances of the same ui Integrated in jenkins_main_trunk #3309 FIXED JENKINS-22583 Use unique id to distinguish between multiple included instances of the same page. (Revision 0e845b678f7922a009709e113161f74bd6a90af1) JENKINS-22583 Changelog (Revision b93d77119f0df2c89bc0c50727affe2a6755df76) Result = SUCCESS Stefan Wolf : 0e845b678f7922a009709e113161f74bd6a90af1 Files : core/src/main/resources/lib/form/hetero-radio.jelly Stefan Wolf : b93d77119f0df2c89bc0c50727affe2a6755df76 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/d/optout.
[JIRA] [batch-task] (JENKINS-21329) Can't do git commands in Jenkins
Mark Waite closed JENKINS-21329 as Cannot Reproduce Cant do git commands in Jenkins Change By: Mark Waite (15/Apr/14 1:58 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
