[JIRA] (JENKINS-14273) Matrix jobs don't get loaded
Randall Hunt commented on JENKINS-14273 Matrix jobs dont get loaded Can't believe this made it into a release and out to package managers, awful bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14408) URLTrigger deletes schedule from config, then does not trigger
Michiel Koster resolved JENKINS-14408 as Cannot Reproduce URLTrigger deletes schedule from config, then does not trigger Change By: Michiel Koster (13/Jul/12 6:54 AM) Status: InProgress Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14422) Create a page for editing your oracle download credentials
carlspring created JENKINS-14422 Create a page for editing your oracle download credentials Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: core Created: 13/Jul/12 8:44 AM Description: It is currently not possible to edit your Oracle download credentials. This tickets is related to JENKINS-571. I think there should be a central place under Manage Jenkins/Configure System where one could change their various types of credentials, such as svn, etc. Project: Jenkins Priority: Major Reporter: carlspring This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13442) Default icon size should be configurable
Steffen Sledz commented on JENKINS-13442 Default icon size should be configurable Such an improvement would be great. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7495) Make POM parser aware of alternate settings.xml
sslavic commented on JENKINS-7495 Make POM parser aware of alternate settings.xml @Yves That plugin states it supports "Ability to provide configuration files (e.g. settings.xml for maven, XML, groovy, custom files,...) loaded trough the UI which will be copy to the job workspace", and that it works in a way that "It will prevents you to copy various similar configuration files to all your nodes. And the capability to edit those files trough the Jenkins UI !" This is not a solution for case where alternate settings.xml is already provided in project sources, and each project has its own very project specific alternate settings.xml file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10945) Latest changes should include merged revisions (like svn log -g)
Grigory Entin commented on JENKINS-10945 Latest changes should include merged revisions (like svn log -g) We miss this feature very much. At this very moment, change logs provide little in case of merges, and if you ever use branches, that is essential. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10945) Latest changes should include merged revisions (like svn log -g)
Grigory Entin edited a comment on JENKINS-10945 Latest changes should include merged revisions (like svn log -g) We miss this feature very much. At this very moment, change logs provide little info in case of merges, and if you ever use branches, that is essential. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14415) 500 when using Google SSO
Julien Duponchelle commented on JENKINS-14415 500 when using Google SSO After clearing all my cookies it's work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
jglick created JENKINS-14423 Declare direct deps on all Aether artifacts Issue Type: Bug Assignee: olamy Attachments: x.diff Components: maven Created: 13/Jul/12 2:13 PM Description: I have a project which declares a dependency on org.jenkins-ci.lib:lib-jenkins-maven-embedder. With 3.7 it worked fine. Changing the version to 3.9 makes it not work: NoClassDefFoundError on ConfigUtils, a newer aether-utils class. Turns out that aether-utils 1.11 was being used, via dep from maven-core 3.0.3, whereas 1.13 was really needed for use from aether-connector-wagon. lib-jenkins-maven-embedder declared the correct versions in dependencyManagement, but since this is a jar project, that only affected its own version of Aether, not that of projects depending on it. Suggested patch just makes these simple dependencies. Workaround from client of 3.9 is to explicitly request aether-spi and aether-util in 1.13, though there is still some problem with the version of AbstractHttpClientWagon I am trying to diagnose. Project: Jenkins Priority: Minor Reporter: jglick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
olamy commented on JENKINS-14423 Declare direct deps on all Aether artifacts I agree it was a issue to have such declaration and I have applied you patch. Thanks! BTW if your project depends on aether declare those dependencies. Never rely on transitive dependencies !!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
SCM/JIRA link daemon commented on JENKINS-14423 Declare direct deps on all Aether artifacts Code changed in jenkins User: olivier lamy Path: pom.xml http://jenkins-ci.org/commit/lib-jenkins-maven-embedder/82b63f7cd7e8841993fd8ec452ad4894a5334ed9 Log: JENKINS-14423 Declare direct deps on all Aether artifacts Submiited by 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
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
jglick commented on JENKINS-14423 Declare direct deps on all Aether artifacts Client must also apparently depend on wagon-provider-api:org.apache.maven.wagon:2.2 to get AbstractWagon.getTimeout, though I am still unclear on 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
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
jglick commented on JENKINS-14423 Declare direct deps on all Aether artifacts The project does not explicitly depend on Aether; just calls MavenEmbedder.buildProjects. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
olamy commented on JENKINS-14423 Declare direct deps on all Aether artifacts Maybe aether read this property ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13403) Trigger Build for Drafts
David Pursehouse resolved JENKINS-13403 as Fixed Trigger Build for Drafts This is fixed by the following commits: https://github.com/jenkinsci/gerrit-trigger-plugin/commit/d55636a3e27106f904effb7a78da992c1bca80b0 https://github.com/jenkinsci/gerrit-trigger-plugin/commit/cda1755d62de2c302cc2ea0c7ddec176d934316f https://github.com/jenkinsci/gerrit-trigger-plugin/commit/a7a7a3f9a982750cb784325b47250815cb17ff65 Change By: David Pursehouse (13/Jul/12 2:30 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
[JIRA] (JENKINS-10055) NullPointerException when manually triggering build
David Pursehouse resolved JENKINS-10055 as Fixed NullPointerException when manually triggering build Fixed by the commit mentioned in the previous comment. Change By: David Pursehouse (13/Jul/12 2:31 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
olamy commented on JENKINS-14423 Declare direct deps on all Aether artifacts Do you need a release ? As I will be on holidays this evening for 2 weeks and limited network, I can do it now but not tomorrow BTW feel free to release it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13117) Allow triggering on the change-merged event too
David Pursehouse resolved JENKINS-13117 as Fixed Allow triggering on the change-merged event too This is implemented in the latest master. Several commits starting with this one: https://github.com/jenkinsci/gerrit-trigger-plugin/commit/f10925ee0b7725727b6e9a4a104016fe4619deac Change By: David Pursehouse (13/Jul/12 2:36 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
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
jglick edited a comment on JENKINS-14423 Declare direct deps on all Aether artifacts Client must also apparently depend on org.apache.maven.wagon:wagon-provider-api:2.2 to get AbstractWagon.getTimeout, though I am still unclear on 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
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
jglick
commented on JENKINS-14423
Declare direct deps on all Aether artifacts
Thanks but I do not think I need a release; explicit deps from client project work fine for now. I would anyway first want to figure out what was going on with AbstractWagon.getTimeout - trying to use 2.1 (the default by transitivity) throws {{NoSuchMethodError}}s.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
jglick edited a comment on JENKINS-14423 Declare direct deps on all Aether artifacts Thanks but I do not think I need a release; explicit deps from client project work fine for now. I would anyway first want to figure out what was going on with AbstractWagon.getTimeout - trying to use 2.1 (the default by transitivity) throws NoSuchMethodError. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
jglick commented on JENKINS-14423 Declare direct deps on all Aether artifacts Oh, looks like you already updated wagonVersion in 3.10-SNAPSHOT, so the problem I had was probably limited to 3.9. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12836) Gerrit-Trigger spams log with class ....Branch is missing its descriptor in ... ....GerritProject.getBranches()
David Pursehouse resolved JENKINS-12836 as Fixed Gerrit-Trigger spams log with class Branch is missing its descriptor in ... GerritProject.getBranches() Change By: David Pursehouse (13/Jul/12 2:47 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
[JIRA] (JENKINS-12881) Allow reading custom build message from a workspace file, in case of non-success
David Pursehouse resolved JENKINS-12881 as Fixed Allow reading custom build message from a workspace file, in case of non-success Change By: David Pursehouse (13/Jul/12 2:49 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
[JIRA] (JENKINS-14423) Declare direct deps on all Aether artifacts
dogfood commented on JENKINS-14423 Declare direct deps on all Aether artifacts Integrated in lib-jenkins-maven-embedder #33 JENKINS-14423 Declare direct deps on all Aether artifacts (Revision 82b63f7cd7e8841993fd8ec452ad4894a5334ed9) Result = SUCCESS Olivier Lamy : Files : pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14410) Xvnc does not set DISPLAY variable
jglick commented on JENKINS-14410 Xvnc does not set DISPLAY variable Odd. Does the build log claim to be setting DISPLAY? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14402) Don't show up Invoke ANT Advanced value in Job Configuration
jglick resolved JENKINS-14402 as Duplicate Dont show up Invoke ANT Advanced value in Job Configuration Change By: jglick (13/Jul/12 3:51 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14425) Jenkins crashes every 2 hours eith GLIB error
Shashinandan Ks created JENKINS-14425 Jenkins crashes every 2 hours eith GLIB error Issue Type: Task Assignee: Unassigned Components: javanet Created: 13/Jul/12 3:56 PM Description: Jenkins is crashing every 2 hours with below error in jenkins.log GLib-ERROR **: file gmain.c: line 2008 (g_main_dispatch): assertion failed: (source) aborting.. Is it a problem with RHEL or Jenkins configuration? Environment: Red Hat Linux 5.6 Project: Jenkins Labels: jenkins Priority: Major Reporter: Shashinandan Ks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14426) Can't install more than one JNLP windows slave
Nicolas De Loof created JENKINS-14426 Cant install more than one JNLP windows slave Issue Type: Bug Assignee: Unassigned Components: core Created: 13/Jul/12 4:02 PM Description: JNLP slave, when installed as a service, is created as "Jenkins Slave" service. Trying to add a second slave on same host fail with WMI.WmiException:UnknownFailure (thanks to WMI API not to let us know this is just a f... name conflict) renaming the first installed service as "Jenkins Slave 1", rebooting second JNLP slave now can be installed successfully. Project: Jenkins Priority: Minor Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10912) Memory leak (?) in dashboard
Anoop Karollil commented on JENKINS-10912 Memory leak (?) in dashboard Please disregard all my comments - our leak is on the server side not browser/client side. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14107) Unable to monitor external job in 1.470 (IllegalAccessError)
Dave Kelsey commented on JENKINS-14107 Unable to monitor external job in 1.470 (IllegalAccessError) Aaron, thanks that worked. I downgraded to 1.464 and re-ran the ls -l example and it worked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14107) Unable to monitor external job in 1.470 (IllegalAccessError)
Dave Kelsey edited a comment on JENKINS-14107 Unable to monitor external job in 1.470 (IllegalAccessError) Aaron, thanks that worked. I downgraded to 1.464 and re-ran the ls -l example and it worked. So newer versions have broken the ability to monitor external jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14427) Wrong down/upstream jobs relationship from manual build pipeline trigger on multi-modules
Sylvain Veyrié created JENKINS-14427 Wrong down/upstream jobs relationship from manual build pipeline trigger on multi-modules Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-pipeline Created: 13/Jul/12 6:38 PM Description: I don't know if this is a Build Pipeline Plugin bug or a Fingerprint bug, or a Maven Plugin bug, but it is more in the way when using the BP Plugin. Or a feature. I have a multi-module Maven3 project: foo-parent /foo (war module) /foo-integration with a dep on "foo" (will contain Selenium tests in the future) I have 3 Jenkins jobs: Foo (mvn clean install, restricted to /foo) Foo-Checks (mvn some:checks foo-parent, restricted to /foo) Foo-Integration (mvn some:things foo-parent, restricted to /foo-integration) Everything is run against foo-parent. "restricted to /foo" means "-pl foo -am" mvn option. Foo is triggered by SCM Foo has a post build action: it triggers Foo-Checks Foo has a post build action: Build Pipeline downstream job (allow to trigger Foo-Integration) At this point, everything is perfect: Foo-Checks is a downstream job of Foo Foo-Integration is a downstream job of Foo-Checks The build pipeline view shows: Foo = Foo-Checks = Foo-Integration If Foo is triggered, still OK. But, if I manually trigger Foo-Integration in the Build Pipeline view: Foo-Integration becomes a downstream project of Foo The build pipeline view shows: Foo = Foo-Checks = Foo-Integration = Foo-Integration I tried to delete some fingerprints, but I have the feeling there is some "magical" in the job tree algorithm using Maven dependencies. Is this really a bug? If not a bug, would it be possible to have an option to set the "upstream/downstream" tree ignore maven dependencies/modules? Or just in the Build Pipeline tree? Project: Jenkins Priority: Major Reporter: Sylvain Veyrié This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10025) Calling rebuildDependencyGraph() in cycle
eguess74 commented on JENKINS-10025 Calling rebuildDependencyGraph() in cycle Any progress on that one, please? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14428) Provide group operations for Disable build slicer
eguess74 created JENKINS-14428 Provide group operations for Disable build slicer Issue Type: Improvement Assignee: mdonohue Components: configurationslicing Created: 13/Jul/12 7:44 PM Description: Please take a look at adding three buttons to the disable build slicer configuration page: Check all, Uncheck all, Invert Selection + provide a regexp based configuration the same way as it is done to specify the jobs for the view. We have 700+ jobs - clicking through them is pain. Project: Jenkins Priority: Minor Reporter: eguess74 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14429) LDAPS gives Administrative Limit Exceeded error, the recommended steps not applicable
hab 278 created JENKINS-14429 LDAPS gives Administrative Limit Exceeded error, the recommended steps not applicable Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: security Created: 13/Jul/12 7:57 PM Description: Upon configuring Jenkins with an LDAPS server, jenkins seems to constantly give an "Administrative Limit Exceeded" error. However, it only does this once the user provides the correct credentials. If the user provides improper credentials, it gives "Bad Credentials". If using an unsecure LDAP server, jenkins constantly gives "Bad Credentials" Jenkins logs: Red Hat 6.2 LDAPS Correct Credentials Jul 13, 2012 3:49:11 PM hudson.security.AuthenticationProcessingFilter2 onUnsuccessfulAuthentication INFO: Login attempt failed org.acegisecurity.AuthenticationServiceException: LdapCallback;LDAP: error code 11 - Administrative Limit Exceeded; nested exception is javax.naming.LimitExceededException: LDAP: error code 11 - Administrative Limit Exceeded; remaining name ''; nested exception is org.acegisecurity.ldap.LdapDataAccessException: LdapCallback;LDAP: error code 11 - Administrative Limit Exceeded; nested exception is javax.naming.LimitExceededException: LDAP: error code 11 - Administrative Limit Exceeded; remaining name '' at org.acegisecurity.providers.ldap.LdapAuthenticationProvider.retrieveUser(LdapAuthenticationProvider.java:238) at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:119) at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:195) at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:45) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:71) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at
[JIRA] (JENKINS-14429) LDAPS gives Administrative Limit Exceeded error, the recommended steps not applicable
hab 278 updated JENKINS-14429 LDAPS gives Administrative Limit Exceeded error, the recommended steps not applicable Change By: hab 278 (13/Jul/12 7:59 PM) Description: UponconfiguringJenkinswithanLDAPSserver,jenkinsseemstoconstantlygiveanAdministrativeLimitExceedederror.However,itonlydoesthisoncetheuserprovidesthecorrectcredentials.Iftheuserprovidesimpropercredentials,itgivesBadCredentials.IfusinganunsecureLDAPserver,jenkinsconstantlygivesBadCredentials TherecommendedstepsistospecifygrouptoreducescopeorchangeLDAPBindSecurityRealm.groovyinWEB-INF/security/howeverthisfileisnotpresent. Jenkinslogs:RedHat6.2LDAPSCorrectCredentialsJul13,20123:49:11PMhudson.security.AuthenticationProcessingFilter2onUnsuccessfulAuthenticationINFO:Loginattemptfailedorg.acegisecurity.AuthenticationServiceException:LdapCallback;[LDAP:errorcode11-AdministrativeLimitExceeded];nestedexceptionisjavax.naming.LimitExceededException:[LDAP:errorcode11-AdministrativeLimitExceeded];remainingname;nestedexceptionisorg.acegisecurity.ldap.LdapDataAccessException:LdapCallback;[LDAP:errorcode11-AdministrativeLimitExceeded];nestedexceptionisjavax.naming.LimitExceededException:[LDAP:errorcode11-AdministrativeLimitExceeded];remainingname atorg.acegisecurity.providers.ldap.LdapAuthenticationProvider.retrieveUser(LdapAuthenticationProvider.java:238) atorg.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:119) atorg.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:195) atorg.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:45) atorg.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:71) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) atorg.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:225) atorg.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) atorg.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) atorg.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) atorg.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) atorg.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:927) atorg.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) atorg.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) atorg.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1001)
[JIRA] (JENKINS-14430) Teach cli commands disable-job and enable-job to perform group operations
eguess74 updated JENKINS-14430 Teach cli commands disable-job and enable-job to perform group operations Change By: eguess74 (13/Jul/12 8:02 PM) Description: Pleaseaddtheabilitytospecifyagroupofjobstobedisabled/enabled.wouldbeniceifitcouldunderstand * asallandfilteroutbypartofthenamemyjobmyj*+mayberegexp? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14430) Teach cli commands disable-job and enable-job to perform group operations
eguess74 created JENKINS-14430 Teach cli commands disable-job and enable-job to perform group operations Issue Type: Improvement Assignee: Unassigned Components: cli Created: 13/Jul/12 8:01 PM Description: Please add the ability to specify a group of jobs to be disabled/enabled. would be nice if it could understand "" as "all" and filter out by part of the name myjob myj + may be regexp? Project: Jenkins Priority: Minor Reporter: eguess74 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14430) Teach cli commands disable-job and enable-job to perform group operations
eguess74 updated JENKINS-14430 Teach cli commands disable-job and enable-job to perform group operations Change By: eguess74 (13/Jul/12 8:02 PM) Description: Pleaseaddtheabilitytospecifyagroupofjobstobedisabled/enabled.wouldbeniceifitcouldunderstand * asterisk asallandfilteroutbypartofthename myjobmyj* +mayberegexp? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14430) Teach cli commands disable-job and enable-job to perform group operations
eguess74 updated JENKINS-14430 Teach cli commands disable-job and enable-job to perform group operations Change By: eguess74 (13/Jul/12 8:03 PM) Description: Pleaseaddtheabilitytospecifyagroupofjobstobedisabled/enabled.wouldbeniceifitcouldunderstandasterisk (*) asallandfilteroutbypartofthenamemyjobmyj*+mayberegexp? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14430) Teach cli commands disable-job and enable-job to perform group operations
eguess74 updated JENKINS-14430 Teach cli commands disable-job and enable-job to perform group operations Change By: eguess74 (13/Jul/12 8:03 PM) Description: Pleaseaddtheabilitytospecifyagroupofjobstobedisabled/enabled.wouldbeniceifitcouldunderstandasterisk (*) asallandfilteroutbypartofthenamemyjobmyj*+mayberegexp? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13246) disk usage peridocity should be configurable
Shawn Baker commented on JENKINS-13246 disk usage peridocity should be configurable Instead of a set time period, how about a trigger to initiate a disk usage check for a specific project. I could see a checkbox option in each project that, if checked, would trigger disk usage check after that project has completed successfully. Or maybe provided a post-build step to do so. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14371) NullPointerException in EnvInjectBuilderContributionAction.buildEnvVars during SCM poll
SCM/JIRA link daemon commented on JENKINS-14371 NullPointerException in EnvInjectBuilderContributionAction.buildEnvVars during SCM poll Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuilderContributionAction.java http://jenkins-ci.org/commit/envinject-plugin/4282ddca174519d902ceb676237a7edbfdc20a8f Log: Fix JENKINS-14371 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14431) NullPointerException if no sites are configured
Christopher Orr created JENKINS-14431 NullPointerException if no sites are configured Issue Type: Bug Assignee: simoneardissone Components: assembla Created: 13/Jul/12 8:49 PM Description: According to this Stack Overflow question (http://stackoverflow.com/questions/11443748/builds-from-github-failing), there is a NullPointerException during checkout. Building in workspace /var/lib/jenkins/jobs/SweetyHigh-Staging/workspace Checkout:workspace / /var/lib/jenkins/jobs/SweetyHigh-Staging/workspace - hudson.remoting.LocalChannel@46ffed1d Using strategy: Default Last Built Revision: Revision a40cbe653169bc73c445f39e09dcd8cfe66e5fe7 (origin/master) Fetching changes from 1 remote Git repository Fetching upstream changes from g...@github.com:Sweety-High/sweetyhigh.git Commencing build of Revision a40cbe653169bc73c445f39e09dcd8cfe66e5fe7 (origin/master) Checking out Revision a40cbe653169bc73c445f39e09dcd8cfe66e5fe7 (origin/master) hudson.util.IOException2: Failed to parse changelog at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:600) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1488) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.lang.NullPointerException at jenkins.plugin.assembla.AssemblaSCMListener.onChangeLogParsed(AssemblaSCMListener.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:598) ... 6 more From a brief look at the code, it appears that this occurs because the "site" chosen is null: https://github.com/jenkinsci/assembla-plugin/blob/master/src/main/java/jenkins/plugin/assembla/AssemblaSCMListener.java#L32 I don't use the plugin, but I imagine that this happens if the plugin has been installed but no sites have been configured in the global settings. Project: Jenkins Priority: Major Reporter: Christopher Orr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
