+
+
+
+
+ 
+
+
+
+
+
+ +
+
+
+
+
+
+
+
+
+
+ wrapper.java.additional.9=-Dcom.sun.management.jmxremote+
The following image shows starting Continuum 1.1, adding a project group, then adding and building the trunk of the Shale Framework (14 modules):
+
The following image shows the same Continuum instance running for several hours:
+
Edit $CONTINUUM_HOME/bin/[platform]/wrapper.conf to add:
+wrapper.java.additional.10=-verbose:gc + or +wrapper.java.additional.10=-Xloggc:gc.txt+
The first sends to the console (and wrapper log) while the second sends to the filename that you tell it to.
+Example output:
+420.568: [GC 62459K->58474K(65104K), 0.0074933 secs] +420.778: [GC 62634K->58733K(65104K), 0.0060762 secs] +420.919: [GC 62893K->58832K(65104K), 0.0034433 secs] +421.015: [GC 62992K->58723K(65104K), 0.0026420 secs] +421.067: [GC 62883K->60885K(65104K), 0.0107248 secs] +421.140: [GC 65045K->62114K(66384K), 0.0122194 secs] +421.153: [Full GC 62114K->32136K(66384K), 0.3591207 secs] +421.655: [GC 36296K->32242K(65104K), 0.0037377 secs] +421.754: [GC 36402K->33061K(65104K), 0.0037182 secs] +421.835: [GC 37221K->33120K(65104K), 0.0028722 secs] +421.930: [GC 37280K->34582K(65104K), 0.0056601 secs] +422.074: [GC 38742K->35150K(65104K), 0.0072451 secs] + + before->after (total), time+
This shows the heap size before and after garbage collection as well as the total heap size and the time for the GC run.
+
+
+
+
+
+
+
+
+
+
+ The main goal is to compile/test sources against the targeted jvm, mvn/maven version, ant version and to add defined envvar (MAVEN_OPTS, ANT_OPTS ...). This is now possible at the build definition level (in 1.1).
+From the menu, choose the 'Profiles' entry
+
Enter a profile name (the name is free)
+
The list box contains all availables installations (jdk, mvn etc..). The installation's type is automatically recognized. In the modification mode of a profile, adding an already attached type will override the existing one.
+
The list box contains all availables installations (jdk, mvn etc..). The installation's type is automatically recognized. In the modification mode of a profile, adding an already attached type will override the existing one.
+
The notification mail contains the following informations :
+Java Home version : + java version "1.4.2_06" + Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_06-b03) + Java HotSpot(TM) Client VM (build 1.4.2_06-b03, mixed mode) + + Builder version : + Maven version: 2.0.5+
+
+
+
+
+
+
+
+
+
+ From the home page (Group Summary) Use the the 'Add Project Group' button
+
Then You will have the project Group detail.
+
Some fields are mandatory :
+
+
+
+
+
+
+
+
+
+
+ Coming Soon
+
+
+
+
+
+
+
+
+
+
+ To write
+
+
+
+
+
+
+
+
+
+
+ Continuum support LDAP for authentication. To configure it, you should follow these steps:
+<!-- + Ldap Authentication can be enabled by setting enabling these components and setting the following configuration options in your security.properties file + + user.manager.impl=ldap + ldap.bind.authenticator.enabled=true + redback.default.admin=admin + redback.default.guest=guest + security.policy.password.expiration.enabled=false + + until this process is better documented, the following is the document for configuration ldap with redback + + http://redback.codehaus.org/integration/ldap.html + --> + + <!-- + + this component manages the connection to the ldap server + + * hostname - The hostname of the ldap server + * port - The port of the ldap server + * baseDn - The baseDn of the ldap system + * contextFactory - context factory for ldap connections + * password - password for the bindDn for the root ldap connection + * bindDn - the core user used for authentication the ldap server, must be able to perform the necessary searches, etc. + --> + + <!-- component> + <role>org.codehaus.plexus.redback.common.ldap.connection.LdapConnectionFactory</role> + <role-hint>configurable</role-hint> + <implementation>org.codehaus.plexus.redback.common.ldap.connection.ConfigurableLdapConnectionFactory</implementation> + <description></description> + <configuration> + <hostname></hostname> + <port></port> + <baseDn></baseDn> + <contextFactory>com.sun.jndi.ldap.LdapCtxFactory</contextFactory> + <password></password> + <bindDn></bindDn> + </configuration> + </component--> + + <!-- + + this component manages the mapping of attributes in ldap to user information in redback + + * email-attribute - The name of the attribute on a user that contains the email address + * full-name-attribute - The name of the attribute on a user that contains the users fullName + * password-attribute - The name of the attribute containing the users password, used for the authentiction using the user manager and not the ldap bind authenticator + * user-id-attribute - The name of the attribute containing the users userId, most commonly cn or sn. + * user-base-dn - The base dn that will be subtree searched for users. + * user-object-class - the objectClass used in the ldap server for indentifying users, most commonly inetOrgPerson. + --> + + <!-- component> + <role>org.codehaus.plexus.redback.common.ldap.UserMapper</role> + <role-hint>ldap</role-hint> + <implementation>org.codehaus.plexus.redback.common.ldap.LdapUserMapper</implementation> + <description></description> + <configuration> + <email-attribute>email</email-attribute> + <full-name-attribute>givenName</full-name-attribute> + <password-attribute>userPassword</password-attribute> + <user-id-attribute>cn</user-id-attribute> + <user-base-dn>o=com</user-base-dn> + <user-object-class>inetOrgPerson</user-object-class> + </configuration> + </component--> + + <!-- + + If caching is desired then make uncomment this and make sure the following configuration parameter is in the security.properties + + user.manager.impl=cached + --> + + <!-- component> + <role>org.codehaus.plexus.redback.users.UserManager</role> + <role-hint>cached</role-hint> + <implementation>org.codehaus.plexus.redback.users.cached.CachedUserManager</implementation> + <description>CachedUserManager</description> + <requirements> + <requirement> + <role>org.codehaus.plexus.redback.users.UserManager</role> + <role-hint>ldap</role-hint> + <field-name>userImpl</field-name> + </requirement> + <requirement> + <role>org.codehaus.plexus.ehcache.EhcacheComponent</role> + <role-hint>users</role-hint> + <field-name>usersCache</field-name> + </requirement> + </requirements> + </component--> + + <!-- + + if using the user manager authenticator to authenticate the user and not the ldap bind authenticator make sure + this definition has the correct password encoder + + Note: you should probably just use the ldap bind authenticator which is enabled by putting + + ldap.bind.authenticator.enabled=true + + in the security.properties + --> + + <!-- component> + <role>org.codehaus.plexus.redback.policy.UserSecurityPolicy</role> + <role-hint>default</role-hint> + <implementation>org.codehaus.plexus.redback.policy.DefaultUserSecurityPolicy</implementation> + <description>User Security Policy.</description> + <requirements> + <requirement> + <role>org.codehaus.plexus.redback.configuration.UserConfiguration</role> + <field-name>config</field-name> + </requirement> + <requirement> + <role>org.codehaus.plexus.redback.policy.PasswordEncoder</role> + <role-hint>sha1</role-hint> + <field-name>passwordEncoder</field-name> + </requirement> + <requirement> + <role>org.codehaus.plexus.redback.policy.UserValidationSettings</role> + <field-name>userValidationSettings</field-name> + </requirement> + <requirement> + <role>org.codehaus.plexus.redback.policy.CookieSettings</role> + <role-hint>rememberMe</role-hint> + <field-name>rememberMeCookieSettings</field-name> + </requirement> + <requirement> + <role>org.codehaus.plexus.redback.policy.CookieSettings</role> + <role-hint>signon</role-hint> + <field-name>signonCookieSettings</field-name> + </requirement> + <requirement> + <role>org.codehaus.plexus.redback.policy.PasswordRule</role> + <field-name>rules</field-name> + </requirement> + </requirements> + </component--> ++
All you need to configure is the ConfigurableLdapConnectionFactory and LdapUserMapper components
+user.manager.impl=ldap +ldap.bind.authenticator.enabled=true +redback.default.admin=adminuser +redback.default.guest=guestuser +security.policy.password.expiration.enabled=false +user.manager.impl=cached +ldap.bind.authenticator.enabled=true+
adminuser + is a LDAP user and will be the default Continuum admin. guestuser + is a LDAP user and will be used for the guest + role, generally, it is an utility LDAP account.
+
+
+
+
+
+
+
+
+
+
+ To Shutdown correctly Continuum, you should look at the build queue. It isn't recommended to shutdown Continuum when a project is building or in the queue.
+From the menu, choose the 'Queues' link
+
Then you'll get the Queues page
+
In this page you can see the current build, projects in the build queue, the current checkout and projects in the checkout queue. For each line, you can cancel the process
+To shutdown Continuum, the queue must be empty, so when you want to shutdown it, you can wait the end of all processes or cancel them.
+If you don't want to have new projects added in the build queue before you shutdown Continuum, you can disable all schedules (Note: You'll need to enable them on the next startup). In future, you'll have an action to automate the disable/enable schedules process.
+
+
+ 
+
+