Thursday, December 22, 2011

Jenkins Community Survey Results: 82% Consider Jenkins Mission Critical

The results from the first Jenkins Community Survey are in! 624 people took the time to share how they use Jenkins and tell us what capabilities matter most to them.

Highlights:
  • 82% of respondents said Jenkins is mission critical to their development process
  • 71% use Jenkins as their only CI tool
  • Jenkins is useful for companies of any size, but 76% work for organizations with > 10 developers
  • 80% of respondents have 3 or fewer masters and 10 or fewer build agents
  • 65% of companies have 10 or fewer executors
  • 76% have between 2 and 50 projects
  • Additional reporting capabilities and high availability were the highest-prioritized features

Check out the full survey results here (minimal registration required). You’ll learn which features users thought were most important to develop, which factors are most influential in making Jenkins easier to adopt, and many other insights into a typical Jenkins installation.

Many, many thanks to everyone who took the survey. You have been instrumental in helping the Jenkins community focus on the most needed features! And congratulations to Chris Dolan, who won the drawing for the AppleTV.

CloudBees
www.cloudbees.com
 
Follow CloudBees:
Facebook Twitter

2 comments:

  1. Hello,
    i have a question.I try to establish a connection from a jenkins-UI
    to a JBoss-Server(JBoss-5.1.0-default), but i have this Error-
    message:
    log4j:WARN No appenders could be found for logger
    (org.nabucco.testautomation.mgmt.launcher.TestautomationLauncher).
    log4j:WARN Please initialize the log4j system properly.
    org.nabucco.testautomation.mgmt.launcher.LauncherException: Could not
    connect to Server
    at
    org.nabucco.testautomation.mgmt.launcher.RemoteTestConfigurationLauncher.(RemoteTestConfigurationLauncher.java:
    191)
    at
    org.nabucco.testautomation.mgmt.launcher.TestautomationLauncher.execute(TestautomationLauncher.java:
    103)
    at
    org.nabucco.testautomation.jenkins.plugin.TestautomationBuilder.perform(TestautomationBuilder.java:
    202)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:
    19)
    at hudson.model.AbstractBuild
    $AbstractRunner.perform(AbstractBuild.java:703)
    at hudson.model.Build$RunnerImpl.build(Build.java:178)
    at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
    at hudson.model.AbstractBuild
    $AbstractRunner.run(AbstractBuild.java:473)
    at hudson.model.Run.run(Run.java:1410)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
    at hudson.model.ResourceController.execute(ResourceController.java:
    88)
    at hudson.model.Executor.run(Executor.java:238)
    Caused by:
    org.nabucco.framework.base.facade.component.connection.ConnectionException:
    Error creating JBoss connection.
    at
    org.nabucco.framework.base.facade.component.connection.JBossConnection.initContext(JBossConnection.java:
    57)
    at
    org.nabucco.framework.base.facade.component.connection.Connection.(Connection.java:
    58)
    at
    org.nabucco.framework.base.facade.component.connection.JBossConnection.(JBossConnection.java:
    41)
    at
    org.nabucco.framework.base.facade.component.connection.ConnectionFactory.createConnection(ConnectionFactory.java:
    105)
    at
    org.nabucco.testautomation.mgmt.launcher.RemoteTestConfigurationLauncher.(RemoteTestConfigurationLauncher.java:
    171)
    ... 11 more
    Caused by: javax.naming.NoInitialContextException: Cannot instantiate
    class: org.jnp.interfaces.NamingContextFactory
    at
    javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:
    657)
    at
    javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.(InitialContext.java:197)
    at
    org.nabucco.framework.base.facade.component.connection.JBossConnection.initContext(JBossConnection.java:
    55)
    ... 15 more
    Caused by: java.lang.ClassNotFoundException:
    org.jnp.interfaces.NamingContextFactory
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
    at
    winstone.classLoader.WebappClassLoader.loadClass(WebappClassLoader.java:
    83)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at
    com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:
    46)
    at
    javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:
    654)
    ... 19 more
    19.03.2012 11:24:24 hudson.model.Run run
    INFO: org.nabucco.framework.base.test #18 main build action completed:
    SUCCESS
    ^C19.03.2012 11:39:47 winstone.Logger logInternal
    INFO: JVM is terminating. Shutting down Winstone

    Although i have put the jnp-client in the Lib.
    What can i do to solve this problem?

    ReplyDelete
  2. This appears to be a question for the Jenkins Community. You can file an issue with the Jenkins Community at: https://wiki.jenkins-ci.org/display/JENKINS/Issue+Tracking.

    Alternatively, CloudBees offers a supported version of Jenkins called Jenkins Enterprise by CloudBees. This is the same open source Jenkins that you know and love, but with technical support provided by CloudBees. You can read more about it here: http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-overview.cb. Jenkins Enterprise by CloudBees also comes with some additional plugins (http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-available-plugins.cb). For more information about Jenkins Enterprise by CloudBees, please feel free to contact CloudBees sales at: sales@cloudbees.com.

    Thanks for your comment!

    ReplyDelete