Hello Kritis
With reference to ur mail i am able to configure scmbug daemon, its up
and running, iam attatching my daemon.conf and glue.conf for ur info.
where i will get the result, in bugzilla where the result will be getting
appended, is it under comment fields that r getting appened,
with the conf in this two files till now iam unable to submit a commit ..
with the valid bug id, what ever the bugid i will give its saying error,
pl see my system conf files and sugges me.
--
D.Chandra Shaker
REDHAT CERTIFIED ENGINEER
#
# This is a template configuration file for the
# scmbug-server daemon
#
$daemon_configuration = {
# Logging configuration
logs => { error => '/var/log/scmbug/error.log' ,
activity => '/var/log/scmbug/activity.log' },
# Port the daemon will start on
daemon_port => 3872,
#
# Execution mode of the daemon. There are 3 options:
#
# - 'threaded'. Multiple threads are created to handle incoming
# connections. This was observed to work well under Windows but
# cause a 3-fold slowdown under UNIX.
#
# - 'forked'. Multiple processes are created to handle incoming
# connections. This was observed to work well under UNIX
# and most Windows systems.
#
# - 'auto'. Automatically chooses between a 'threaded' or 'forked'
# mode.
daemon_mode => "auto",
# Configuration information of the bug tracking
# system
bugtracker => {
# The possible options are:
# - 'Bugzilla'
# - 'Mantis'
# - 'RequestTracker'
# - 'TestDirector'
type => 'Bugzilla',
# This MUST be in the format x.y.z, where x,y,z
# are integers
version => '2.22.2',
database_location => '127.0.0.1',
database_port => '3306',
# Valid values are the ones accepted by the Perl DBI.
#
# For Bugzilla and RequestTracker, this value is ignored
#
# For Mantis, *some* valid values (there are others) are:
# - 'mysql'
# - 'Pg'
database_vendor => 'mysql',
# For RequestTracker these values are ignored
database_name => 'bugs',
database_username => 'educeit',
database_password => 'educeit',
# Used only for Bugzilla.
#
# Flags whether the live bugtracker instance is installed
# locally on the same machine the daemon is running
installed_locally => 1,
# Used for Bugzilla and RequestTracker.
#
# Path to the directory of the bugtracker sources providing an
# API that the daemon can use
installation_directory => '/bugzilla/htdocs/bugzilla',
# Prefix used to display a bug
bug_url_prefix => 'http://127.0.0.1/show_bug.cgi?id=' },
# Translation list of SCM usernames to bug-tracking
# usernames. Mappings based on mapping_ldap are applied
# first. Mappings based on mapping_regexes are applied second and
# can override a mapping based on mapping_ldap. Mappings based on
# mapping_values are applied last and can override all other
# mappings.
userlist => {
# Apply a case sensitive username verification
case_sensitive_username_verification => 1,
mappings => {
# Enable SCM username translation. This flag must be
# turned on for any of the mappings that follow to apply.
enabled => 1,
# This is a mapping based on
# LDAP. ldap_scm_username_attribute defines the LDAP
# attribute that will be used to match the SCM
# username. The SCM username will be mapped into the
# bug-tracking username defined by
# ldap_bugtracking_username_attribute.
mapping_ldap => {
enabled => 0,
ldap_server => '127.0.0.1',
ldap_port => '389',
# A binddn (e.g. cn=default) that has access to read
# all attributes
ldap_binddn => 'replace_with_binddn',
# The password of the binddn that has access to read
# all attributes
ldap_binddn_password => 'replace_with_binddn_password',
# The BaseDN in which to search for the
# ldap_scm_username_attribute
# (e.g. "ou=People,o=Company")
ldap_basedn => 'replace_with_basedn',
# The name of the attribute containing the user's SCM
# username
ldap_scm_username_attribute => 'uid',
# The name of the attribute containing the user's
# bug-tracking username
ldap_bugtracking_username_attribute => 'mail',
# LDAP filter to AND with the
# ldap_scm_username_attribute for filtering the list
# of valid SCM users.
ldap_filter => ''
},
# This is a mapping based on regular expressions. The
# first expression defines how the SCM username will be
# matched. The second defines how it will be transformed,
# and uses the unnamed variable $1 that was described by
# the first expression. The mapping is checked for a match
# as:
# m/$first_regex/
# and is applied as: s/$first_regex/$second_regex/
mapping_regexes => {
enabled => 0,
values => {
# This is an example of mapping a Windows Domain
# user from 'DOMAIN\user' to
# '[EMAIL PROTECTED]'
'^DOMAIN\\\\(\w+)$' => '[EMAIL PROTECTED]',
# This is an example of mapping a UNIX user from
# 'example_user' to
# '[EMAIL PROTECTED]'
'^(\w+)$' => '[EMAIL PROTECTED]'
}
},
# This is a one-to-one mapping of SCM usernames to
# bugtracking usernames. Mappings in this list override
# mappings from mapping_regexes.
mapping_values => {
enabled => 1,
values => {
'educeit' => '[EMAIL PROTECTED]',
'example_user2' => '[EMAIL PROTECTED]'
}
}
}
}
};
#
# This is a template configuration file for the Scmbug glue.
#
$glue_configuration = {
#
# Flags whether the glue is active
#
enabled => 1,
#
# Describes the SCM system integrated with bug-tracking
#
scm => {
name => 'CVS',
# Comma(,)-separated list of paths to any binaries the SCM
# tool may need to use
binary_paths => '/usr/bin',
# This applies only to Subversion. It is recommended that tags
# are stored in the 'tags' directory, and branches in the
# 'branches' directory.
label_directories => [
'tags',
'branches'
],
# This applies only to Subversion. It is recommended that the
# main trunk work is stored in the 'trunk' directory.
main_trunk_directories => [
'trunk'
]
},
#
# Describes the daemon that will process the integration requests
#
daemon => {
location => '10.0.1.113',
port => 3872,
},
#
# List of policies the glue can enforce
#
policies => {
# Log template.
#
# Regular expressions that describe how the bug id and log
# comment will be identified must be defined.
#
# This policy is ALWAYS enabled
log_template => {
# The bugid_regex is a regular expression that must set
# the unnamed variable $1 to the bug number, or list of
# bug numbers. It is checked for a match as: m/$regex/s
bugid_regex => 'bug\s*([\d|\s|,|#]*?):',
# The bugid_split_regex is a regular expression describing
# how a list of bug ids will be split in individual bug
# numbers. It is split as: /$regex/
bugid_split_regex => ',\s?#|\s?#|,|\s+',
# The log_regex is a regular expression that must set the
# unnamed variable $1 to the log comment. It is checked
# for a match as: m/$regex/s
log_regex => 'bug.*?:\s*(.*)'
},
#
# Presence of bug ids. There are 3 options:
#
# - 'required'. A bug id must be specified during each
# activity. Activities without a bug id will not be permitted.
#
# - 'optional'. If a bug id is supplied, the activity will be
# integrated. If not the activity will be permitted to go
# through in the SCM system, but without bug-tracking
# integration.
#
# - 'none'. Never integrate activities regardless. This is
# different than flagging the glue inactive. The remaining
# policies are still enforced were applicable.
# (e.g. policy minimum_log_message_size).
#
# This policy is ALWAYS enabled
presence_of_bug_ids => {
value => 'required'
},
# The SCM user issuing an activity must be the user to which
# the bug is assigned
valid_bug_owner => {
enabled => 1
},
# The bug against which an activity is issued must be in an
# open state
open_bug_state => {
enabled => 1
},
# Minimum number of characters log message.
minimum_log_message_size => {
enabled => 1,
size => 5
},
# Format of label names (tag or branch names) defined as
# regular expressions.
label_name => {
enabled => 1,
names => [
# Convention for official releases.
# For example:
# SCMBUG_RELEASE_0-2-7
'^.+?__[0-99]+_[0-999]+_[0-999]+$',
# Convention for development builds.
# For example:
# SCMBUG_BUILD_28_added_a_policies_mechanism
'^.+?_BUILD_[0-9]+_.+$',
# Convention for branches.
# For example:
# b_experimenting_with_policies_on_glue_side
'^b_.+$',
# Convention for private developer tags. Uses
# the developer's initials (either 2 or 3).
# For example:
# p_kpm_prior_to_bug353_stabilization_fixes
'^p_[a-zA-Z][a-zA-Z]?[a-zA-Z]_.+$'
]
},
# Valid product name. There are 2 options:
#
# - type is 'manual'. Each bug id supplied during commit
# messages must be filed against the product name
# specified in value.
#
# - type is 'auto'. The product name will be
# autodetected. Value must be a comma(,)-separated list of
# regular expressions. Each regular expression must set the
# unnamed variable $1 to the product name.
valid_product_name => {
enabled => 1,
type => 'manual',
value => 'AKKPRODUCT'
},
# Send an email after a successful activity (both committing
# and labeling).
mail_on_success => {
enabled => 0,
# Sending email when a tag is moved or deleted in CVS can
# be annoying, since multiple emails are sent per
# directory(but not when a tag is added). mail_on_label
# can disable that behavior.
mail_on_label => 1,
values => {
# Must be a valid email address. Can remain empty if
# other users should be notified.
To => '[EMAIL PROTECTED]',
# Must be a valid email address. Can remain empty if
# mail_also_appears_from_scm_user is enabled.
From => 'Scmbug <[EMAIL PROTECTED]>',
# Defaults to localhost if left empty
Smtp => '10.0.1.116'
},
# Make the email also appear to have been sent by the SCM
# user.
mail_also_appears_from_scm_user => 1,
# List of users that will be notified
mail_scm_user => 1,
mail_bug_owner => 1,
mail_bug_reporter => 1,
mail_bug_monitors => 1,
mail_product_owners => 1
}
}
};
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
