Return-Path: X-Original-To: apmail-continuum-commits-archive@www.apache.org Delivered-To: apmail-continuum-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BC9ACDCF0 for ; Fri, 28 Dec 2012 07:10:56 +0000 (UTC) Received: (qmail 81210 invoked by uid 500); 28 Dec 2012 07:10:56 -0000 Delivered-To: apmail-continuum-commits-archive@continuum.apache.org Received: (qmail 81156 invoked by uid 500); 28 Dec 2012 07:10:55 -0000 Mailing-List: contact commits-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list commits@continuum.apache.org Received: (qmail 81120 invoked by uid 99); 28 Dec 2012 07:10:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Dec 2012 07:10:54 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_FRT_FOLLOW1 X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Dec 2012 07:10:41 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id AEA4E2388A2C; Fri, 28 Dec 2012 07:10:18 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1426423 [4/15] - in /continuum/site-publish/docs/latest: ./ administrator_guides/ administrator_guides/security/ css/ developer_guides/ images/ installation/ user_guides/ user_guides/building_project/ user_guides/cancelling_build/ user_gui... Date: Fri, 28 Dec 2012 07:10:14 -0000 To: commits@continuum.apache.org From: brett@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20121228071018.AEA4E2388A2C@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: continuum/site-publish/docs/latest/administrator_guides/parallelBuilds.html URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/parallelBuilds.html?rev=1426423&r1=1426422&r2=1426423&view=diff ============================================================================== --- continuum/site-publish/docs/latest/administrator_guides/parallelBuilds.html (original) +++ continuum/site-publish/docs/latest/administrator_guides/parallelBuilds.html Fri Dec 28 07:10:12 2012 @@ -19,7 +19,7 @@ @import url("../css/site.css"); - + @@ -32,7 +32,7 @@ pageTracker._trackPageview();
@@ -71,7 +74,7 @@ pageTracker._trackPageview(); - Last Published: 06 May 2010 + Last Published: 28 Dec 2012
@@ -91,15 +94,15 @@ pageTracker._trackPageview();
-

Managing Parallel Builds

-

Since 1.3.1, Continuum can be configured to checkout and build projects in parallel or concurrently.

-

Configuring Parallel Builds

-

The number of build queues to be used when checking out or building projects can be configured in the Configuration page, via the Number of Allowed Builds in Parallel field (see Managing General Configuration). The value should be greater than one (1) to be able to create a build queue aside from the default.

-

Another thing to note is that if Distributed Builds is enabled, Parallel Builds is automatically disabled. To make it short, you're only allowed to use one of these functionalities at a time in the current implementation.

-

To configure parallel builds:

-
  1. Create a build queue to be used for the projects. Refer to Managing Build Queues
    2. -
  2. Attach the build queue(s) to a build schedule. Refer to Attaching Build Queue to a Schedule
    3. -
  3. Create or edit the project's build definition to use the build schedule configured with the build queue(s). Refer to Managing Build Definitions
    4. -
-

A screen similar to the following is displayed under the Queues page when the project is built (force/sheduled).

-Queues
-

Limitations

-

Below are some feature limitations for the current implementation:

-
  1. Project groups cannot be built multiple times simulateously.
    2. -
  2. Concurrent build of inter-dependent projects in a group is not yet supported.
    3. -
  3. All projects in a project group will be enqueued to the same Build Queue.
    4. -
-
-
- +

Managing Parallel Builds

Since 1.3.1, Continuum can be configured to checkout and build projects in parallel or concurrently.

Configuring Parallel Builds

The number of build queues to be used when checking out or building projects can be configured in the Configuration page, via the Number of Allowed Builds in Parallel field (see Managing General Configuration). The value should be greater than one (1) to be able to create a build queue aside from the default.

Another thing to note is that if Distributed Builds is enabled, Parallel Builds is automatically disabled. To make it short, you're only allowed to use one of these functionalities at a time in the current implementation.

To configure parallel builds:

  1. Create a build queue to be used for the projects. Refer to Managing Build Queues
  2. Attach the build queue(s) to a build schedule. Refer to Attaching Build Queue to a Schedule
  3. Create or edit the project's build definition to use the build schedule configured with the build queue(s). Refer to Managing Build Definitions

A screen similar to the following is displayed under the Queues page when the project is built (force/sheduled).

Queues

Limitations

Below are some feature limitations for the current implementation:

  1. Project groups cannot be built multiple times simulateously.
  2. Concurrent build of inter-dependent projects in a group is not yet supported.
  3. All projects in a project group will be enqueued to the same Build Queue.
@@ -505,7 +482,7 @@ pageTracker._trackPageview();
- + \ No newline at end of file Modified: continuum/site-publish/docs/latest/administrator_guides/projectgroup.html URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/projectgroup.html?rev=1426423&r1=1426422&r2=1426423&view=diff ============================================================================== --- continuum/site-publish/docs/latest/administrator_guides/projectgroup.html (original) +++ continuum/site-publish/docs/latest/administrator_guides/projectgroup.html Fri Dec 28 07:10:12 2012 @@ -20,7 +20,7 @@ - + @@ -33,7 +33,7 @@ pageTracker._trackPageview();
@@ -72,7 +75,7 @@ pageTracker._trackPageview(); - Last Published: 06 May 2010 + Last Published: 28 Dec 2012
@@ -92,15 +95,15 @@ pageTracker._trackPageview();
-

Managing Project Groups

-Group Summary homepage

Adding a Project Group

-

From the home page (Group Summary) Use the the Add Project Group button

-Add Project Group

Then You will have the project Group detail.

-Edit Project Group detail

Some fields are mandatory :

-
  • Project Group Name
    • -
  • Project Group Id
    • -
-
-

Editing a Project Group

-

From the home page (Group Summary), click the project group name link.

-

The project group information will then be displayed.

-Project Group Summary

Then, click on the Edit button.

-Update Project Group

The following fields can be updated:

-
  • Project Group Name: The name of the project group.
    • -
  • Description: A brief description about the group.
    • -
  • Local Repository: The specific repository used for the project which points to the exact location of the repository in the machine used for building.
    • -
  • Homepage Url: The site of the project.
    • -
-

And, projects can be moved to another project group.

-
-

Deleting a Project Group

-

There are two ways to delete a project group.

-

From the home page (Group Summary), click the Delete icon to the right of the group you wish to delete.

-

From the Project Group Summary page, click the Delete Group button.

-

Confirm the deletion

-

Note that user roles for this project group will not be removed. This is intentional so that if you are sharing a user database among several Continuum instances, users will still be able to access the same group on a different server.

-
-
- +

Managing Project Groups

Group Summary homepage

Adding a Project Group

From the home page (Group Summary) Use the the Add Project Group button

Add Project Group

Then You will have the project Group detail.

Edit Project Group detail

Some fields are mandatory :

  • Project Group Name
  • Project Group Id

Editing a Project Group

From the home page (Group Summary), click the project group name link.

The project group information will then be displayed.

Project Group Summary

Then, click on the Edit button.

Update Project Group

The following fields can be updated:

  • Project Group Name: The name of the project group.
  • Description: A brief description about the group.
  • Local Repository: The specific repository used for the project which points to the exact location of the repository in the machine used for building.
  • Homepage Url: The site of the project.

And, projects can be moved to another project group.

Deleting a Project Group

There are two ways to delete a project group.

From the home page (Group Summary), click the Delete icon to the right of the group you wish to delete.

From the Project Group Summary page, click the Delete Group button.

Confirm the deletion

Note that user roles for th is project group will not be removed. This is intentional so that if you are sharing a user database among several Continuum instances, users will still be able to access the same group on a different server.

@@ -515,7 +483,7 @@ pageTracker._trackPageview();
- + \ No newline at end of file Modified: continuum/site-publish/docs/latest/administrator_guides/purgeConfiguration.html URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/purgeConfiguration.html?rev=1426423&r1=1426422&r2=1426423&view=diff ============================================================================== --- continuum/site-publish/docs/latest/administrator_guides/purgeConfiguration.html (original) +++ continuum/site-publish/docs/latest/administrator_guides/purgeConfiguration.html Fri Dec 28 07:10:12 2012 @@ -19,7 +19,7 @@ @import url("../css/site.css"); - + @@ -32,7 +32,7 @@ pageTracker._trackPageview();
@@ -71,7 +74,7 @@ pageTracker._trackPageview(); - Last Published: 06 May 2010 + Last Published: 28 Dec 2012
@@ -91,15 +94,15 @@ pageTracker._trackPageview();
-

Purge Configuration

-

Click the Purge Configurations link under the Administration section.

-Purge Configurations

You will see all repository purge configurations and all directory purge configurations.

-

Here you can add/edit/delete the purge configuration.

-

You can also purge the repository or directory by clicking the corresponding purge icon of the purge configuration.

-purge now icon

Adding / Editing Repository Purge Configuration

-

Specify the repository to purge.

-
-

Adding / Editing Directory Purge Configuration

-

There are two types of directory purge configuration:

-
  • releases - this will purge the working copies associated with releases.
    • -
  • buildOutput - this will purge the build output of each project.
    • -
-
-

Purging Repository

-
  • Delete all - will delete the entire contents of the repository
    • -
  • Days Old - will delete the artifact if it's older than the number of days old but still satisfies the number of retention count.

    Example:

    -

    Days_Old = 30 days

    -

    Retention_Count = 2

    -

    If I have 5 artifacts that are older than 30 days, only 3 of them will be deleted because I have to retain any 2 artifacts (Retention count).

    -
    • -
  • Retention Count - the number of artifacts to retain; all in excess will be deleted
    • -
  • Delete Released Snapshots - will delete all released snapshots
    • -
-
-

Purging Directory

-
  • Delete all
    • Releases Directory - will delete all releases-* directories
      • -
    • Build Output Directory - will delete all build output of each project
      • -
    -
    • -
  • Days Old - will delete the directory if it's older than the number of days old
    • -
  • Retention Count - number of directories to retain
    • -
-
-

Steps in purging:

-
  • Perform Delete All purging if it is checked.
    • -
  • If delete all is not checked, then is days old has a value greater than 0? If it has then perform days old purging.
    • -
  • If days old is 0 then perform retention count purging.
    • -
  • Delete released snapshots purging will always be performed if it is checked, unless the Delete All is also checked or it's a directory purging.
    • -
-
-
- +

Purge Configuration

Click the Purge Configurations link under the Administration section.

Purge Configurations

You will see all repository purge configurations and all directory purge configurations.

Here you can add/edit/delete the purge configuration.

You can also purge the repository or directory by clicking the corresponding purge icon of the purge configuration.

purge now icon

Adding / Editing Repository Purge Configuration

Specify the repository to purge.

Adding / Editing Directory Purge Configuration

There are two types of directory purge configuration:

  • releases - this will purge the working copies associated with releases.
  • buildOutput - this will purge the build output of each project.

Purging Repository

  • Delete all - will delete the entire contents of the repository
  • Days Old - will delete the artifact if it's older than the number of days old but still satisfies the number of retention count.

    Example:

    Days_Old = 30 days

    Retention_Count = 2

    If I have 5 artifacts that are older than 30 days, only 3 of them will be deleted because I have to retain any 2 artifacts (Retention count).

  • Retention Count - the number of artifacts to retain; all in excess will be deleted
  • Delete Released Snapshots - will delete all re leased snapshots

Purging Directory

  • Delete all
    • Releases Directory - will delete all releases-* directories
    • Build Output Directory - will delete all build output of each project
  • Days Old - will delete the directory if it's older than the number of days old
  • Retention Count - number of directories to retain

Steps in purging:

  • Perform Delete All purging if it is checked.
  • If delete all is not checked, then is days old has a value greater than 0? If it has then perform days old purging.
  • If days old is 0 then perform retention count purging.
  • Delete released snapshots purging will always be performed if it is checked, unless the Delete All is also checked or it's a directory purging.
@@ -527,7 +482,7 @@ pageTracker._trackPageview();
- + \ No newline at end of file Modified: continuum/site-publish/docs/latest/administrator_guides/queues.html URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/queues.html?rev=1426423&r1=1426422&r2=1426423&view=diff ============================================================================== --- continuum/site-publish/docs/latest/administrator_guides/queues.html (original) +++ continuum/site-publish/docs/latest/administrator_guides/queues.html Fri Dec 28 07:10:12 2012 @@ -20,7 +20,7 @@ - + @@ -33,7 +33,7 @@ pageTracker._trackPageview();
@@ -72,7 +75,7 @@ pageTracker._trackPageview(); - Last Published: 06 May 2010 + Last Published: 28 Dec 2012
@@ -92,15 +95,15 @@ pageTracker._trackPageview();
-

Managing Queues

-

Current checkouts and builds, and all other projects queued in the checkout, build, and prepare build queues can be viewed in the Queues page.

-Queues

Prepare Build Queue

-Prepare Build Queue

Build Queues

-Queues View

Checkout Queue

-Checkout Queue

You must have a Manage Continuum Queues role for you to:

-
  1. Cancel current checkouts, current builds, queued prepare builds, queued checkouts and queued builds by clicking the cancel build icon.
    2. -
  2. Cancel multiple queued tasks by selecting the corresponding checkboxes of the checkouts, builds, or project updates you want to cancel and then click the Cancel Entries button.

    Note: Cancelling current prepare build is not allowed to prevent data corruption.

    -
    3. -
-
- +

Managing Queues

Current checkouts and builds, and all other projects queued in the checkout, build, and prepare build queues can be viewed in the Queues page.

Queues

Prepare Build Queue

Prepare Build Queue

Build Queues

Queues View

Checkout Queue

Checkout Queue

You must have a Manage Continuum Queues role for you to:

  1. Cancel current checkouts, current builds, queued prepare builds, queued checkouts and queued builds by clicking the cancel build icon.
  2. Cancel multiple queued tasks by selecting the corresponding checkboxes of the checkouts, builds, or project updates you want to cancel and then cli ck the Cancel Entries button.

    Note: Cancelling current prepare build is not allowed to prevent data corruption.

@@ -497,7 +483,7 @@ pageTracker._trackPageview();
- + \ No newline at end of file Modified: continuum/site-publish/docs/latest/administrator_guides/schedules.html URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/schedules.html?rev=1426423&r1=1426422&r2=1426423&view=diff ============================================================================== --- continuum/site-publish/docs/latest/administrator_guides/schedules.html (original) +++ continuum/site-publish/docs/latest/administrator_guides/schedules.html Fri Dec 28 07:10:12 2012 @@ -20,7 +20,7 @@ - + @@ -33,7 +33,7 @@ pageTracker._trackPageview();
@@ -72,7 +75,7 @@ pageTracker._trackPageview(); - Last Published: 06 May 2010 + Last Published: 28 Dec 2012
@@ -92,15 +95,15 @@ pageTracker._trackPageview();
-

Managing Schedules

-

Schedules initiates the building of projects continuously. In this section, adding, modifying, and deleting of schedules are discussed.

-

Clicking the Schedules link from the menu on the left will display the following page:

-List of schedules page

Adding Schedules

-

To add a schedule, follow these steps:

-
  1. Click the Add button below the list of schedules.
    2. -
  2. Fill in the needed information in the Edit Schedules page shown below.Adding a build schedule
    • Name The unique identifier of the schedule. This is a required field.
      • -
    • Description Brief description of the configured schedule. This is a required field.
      • -
    • Cron Expression Determines the exact time interval that the build schedule executes.
      • -
    • Maximum job execution time (seconds) This sets the maximum time for a job to be executed. This is a required field.
      • -
    • Quiet Period (seconds) This a setting that delays the build if there has been a commit in the defined number of seconds prior. This is useful when using CVS, since commits are not atomic and a developer might be committing midway through an update. It is not typically needed if using Subversion.
      • -
    • Add Build Queue Move build queues from the left hand list box to the right hand list box by clicking the appropriate buttons in between the two list boxes. All build queues on the right hand list box will be attached to the schedule.
      • -
    • Enabled When selected, scheduled build will be executed. []
      • -
    -
    3. -
  3. Click Save.
    4. -
-
-

Editing Schedules

-

To edit a schedule, follow these steps:

-
  1. Click the edit icon which can be found to the right of the schedule.
    2. -
  2. Modify the fields in the Edit Schedules page.
    3. -
  3. Click Save.
    4. -
-
-

Deleting Schedules

-

To delete a schedule, click the delete icon, the rightmost icon inline with the schedule to be deleted.

-
-
- +

Managing Schedules

Schedules initiates the building of projects continuously. In this section, adding, modifying, and deleting of schedules are discussed.

Clicking the Schedules link from the menu on the left will display the following page:

List of schedules page

Adding Schedules

To add a schedule, follow these steps:

  1. Click the Add button below the list of schedules.
  2. Fill in the needed information in the Edit Schedules page shown below.Adding a build schedule
    • Name The unique identifier of the schedule. This is a required field.
    • Description Brief description of the configured schedule. This is a required field.
    • Cron Expression De termines the exact time interval that the build schedule executes.
    • Maximum job execution time (seconds) This sets the maximum time for a job to be executed. This is a required field.
    • Quiet Period (seconds) This a setting that delays the build if there has been a commit in the defined number of seconds prior. This is useful when using CVS, since commits are not atomic and a developer might be committing midway through an update. It is not typically needed if using Subversion.
    • Add Build Queue Move build queues from the left hand list box to the right hand list box by clicking the appropriate buttons in between the two list boxes. All build queues on the right hand list box will be attached to the schedule.
    • Enabled When selected, scheduled build will be executed. []
  3. Click Save.

Editing Schedules

To edit a schedule, f ollow these steps:

  1. Click the edit icon which can be found to the right of the schedule.
  2. Modify the fields in the Edit Schedules page.
  3. Click Save.

Deleting Schedules

To delete a schedule, click the delete icon, the rightmost icon inline with the schedule to be deleted.

@@ -515,7 +483,7 @@ pageTracker._trackPageview();
- + \ No newline at end of file Modified: continuum/site-publish/docs/latest/administrator_guides/security-logs.html URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/security-logs.html?rev=1426423&r1=1426422&r2=1426423&view=diff ============================================================================== --- continuum/site-publish/docs/latest/administrator_guides/security-logs.html (original) +++ continuum/site-publish/docs/latest/administrator_guides/security-logs.html Fri Dec 28 07:10:12 2012 @@ -20,7 +20,7 @@ - + @@ -33,7 +33,7 @@ pageTracker._trackPageview();
@@ -72,7 +75,7 @@ pageTracker._trackPageview(); - Last Published: 06 May 2010 + Last Published: 28 Dec 2012
@@ -92,15 +95,15 @@ pageTracker._trackPageview();
-

Security Logs

-

Continuum's logs directory contains a security log file named continuum-security-audit.log, which keeps track of all the security operations.

-

A typical record looks like this:

-
2009-07-22 12:32:00 - admin - User Created: continuum
+        
Security Logs
Continuum's logs directory contains a security log file named continuum-security-audit.log, which keeps track of all the security operations.
A typical record looks like this:
2009-07-22 12:32:00 - admin - User Created: continuum
 2009-07-22 12:32:10 - admin - Role Assigned to user continuum: Continuum Group Project Administrator
 2009-07-22 12:32:17 - admin - User Modified: continuum
 2009-07-22 12:32:34 -  - Logged Out user admin
-2009-07-22 12:32:47 -  - Successful Login for user continuum

-

-
The hyphen delimited records are:

-
  • date and time (server local time)
    • 
-
  • current user performing the operation
    • 
-
  • the operation performed
    • 
-

-
Currently, the following events are logged:

-
  • user creation/modification/deletion
    • 
-
  • user log in/out
    • 
-
  • assigning roles to a user
    • 
-

-

-
+2009-07-22 12:32:47 -  - Successful Login for user continuum

The hyphen delimited records are:

  • date and time (server local time)
  • current user performing the operation
  • the operation performed

Currently, the following events are logged:

  • user creation/modification/deletion
  • user log in/out
  • assigning roles to a user
@@ -520,7 +501,7 @@ pageTracker._trackPageview();
- + \ No newline at end of file