| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Import sshkeys module from git://github.com/boklm/puppet-sshkeys.git
at commit 3fb4c1ee17d983dfa8fbc4ad3eed47e0e5712e30.
|
|
|
|
|
|
|
|
|
|
| |
The host.conf config file for youri contains the hostnames of the nodes
that are building packages for each architecture. The variable
$build_src_node has been added to buildsystem::var::scheduler to contain
the hostname of the server building the initial src.rpm. The variable
$build_nodes_aliases has been added to buildsystem::var::scheduler to be
used to find the real hostnames of the nodes building the packages for
each architecture.
|
| |
|
|
|
|
| |
Create SRPMS directories for medias.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The youri submit configuration has been changed. The following two
template files :
- youri/submit-todo.conf
- youri/submit-upload.conf
have been replaced by a common template file for youri submit-todo and
youri submit-upload :
- youri/submit.conf
This new template file does not contain any specific configuration.
Instead the youri configuration is now created using informations from
the following hash variables :
- the $youri_conf_default hash from buildsystem::var::youri, containing
default configuration for the repository, the checks, actions and
posts.
- the $youri_conf parameter from buildsystem::var::youri, overriding
infos from the default configuration defined in $youri_conf_default.
- the distros specific configuration is defined in the $distros
parameter from buildsystem::var::distros.
All those variables contain configuration for both youri submit-todo
and youri submit-upload.
This change allows moving all Mageia specific configuration outside the
buildsystem module to the class mga_buildsystem::config, while still
keeping common configuration in the buildsystem module.
The following checks definitions have also been removed from youri
submit-todo configuration, because they are not used in the current
configuration :
- history
- precedence
- section
- svn
The 'version' check options for infra_1 and infra_2 have been moved from
youri submit-upload to submit-todo configuration.
|
|
|
|
| |
A function to join elements from an array to create a string.
|
| |
|
|
|
|
|
| |
The group_members function currently defined in buildsystem module could
be used outside of this module, so move it to mga-common.
|
|
|
|
|
| |
Add options in buildsystem::var::signbot to select GPG key email and
name.
|
|
|
|
|
| |
Add build_nodes parameter in buildsystem::var::scheduler. This parameter
is a hash containing the build nodes available indexed by architecture.
|
|
|
|
|
| |
The admin_mail parameter is used to select the email address sending the
build failure notifications.
|
|
|
|
|
| |
In upload.conf template for ulri config use the dependencies between
medias defined in buildsystem::var::distros.
|
|
|
|
|
|
|
|
| |
Replace infra_*/release with infra_*/updates. The infra media is using
core/updates, so we have a 'release' repository requiring an 'updates'
repository. For more simplicity in media dependencies, it is replaced
with an updates repository so that we have instead an 'updates' ->
'updates' medias dependency.
|
| |
|
| |
|
|
|
|
|
| |
Update repoctl config to use infos from buildsystem::var::distros
instead of buildsystem::config.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove use of "each" methods on hashes in template files. With ruby 1.8,
the order in which the hash is enumerated is random. When using the each
method to scan all hash keys and elements in template files, puppet will
do unnecessary changes in files installed on the server, making it more
difficult to see the real changes. In order to avoid this, we stop using
the "each" method on hashes and instead use the "keys" method to get an
array of all keys and sort it alphabetically.
With ruby 1.9 the hashes enumerate their values in the order that the
corresponding keys were inserted, but we are still using ruby 1.8 with
Mageia 2.
|
|
|
|
|
|
|
|
|
| |
It is now possible to add the option 'based_on' to a distribution
defined in buildystem::var::distros. This is useful for distributions
like infra_1 or infra_2 which provide a new repository for an existing
distribution. When repositories from an other distribution are defined
in 'based_on', the repositories are linked with a symbolic link, and
defined in media.cfg.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use buildsystem::var::distros settings in vhost_repository.conf
template.
The URLs for the infra_1 and infra_2 repositories have been changed, and
will need to be updated in urpmi configuration on servers using those
repositories.
The old URLs were :
- http://repository.mageia.org/distrib/infra_1/
- http://repository.mageia.org/distrib/infra_2/
The new URLs are now :
- http://repository.mageia.org/bootstrap/infra_1/
- http://repository.mageia.org/bootstrap/infra_2/
|
| |
|
| |
|
|
|
|
|
| |
Use $buildsystem::var::repository::hostname to store repository
hostname.
|
| |
|
|
|
|
|
| |
Use list of distribution from buildsystem::var::distros to generate list
of configs for iurt.
|
|
|
|
| |
Use settings from buildsystem::var::distros to create mgarep.conf.
|
|
|
|
|
|
|
| |
Remove %mgaversion macro definition, as it doesn't seem to be used by
packages during srpm generation. Also the value defined by mgarepo.conf
is incorrect as it doesn't correspond to the value defined by
rpm-mageia-setup-build package.
|
|
|
|
|
|
| |
The %mageia_branch macro does not seem to be used, according to a search
on "site:mageia.org %mageia_branch" on google. So remove it from
mgarepo.conf to simplify the configuration.
|
|
|
|
|
| |
The mgarepo.conf template is now using settings from
buildsystem::var::mgarepo.
|
|
|
|
|
|
|
| |
The media.cfg file is now generated for all distributions now (it was
only done for cauldron before). The media.cfg file is generated using
the infos about the distributions and medias from the $distro parameter
in buildsystem::var::distros.
|
|
|
|
| |
Create distributions trees.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The $distros variable is hash containing settings about the
distributions.
It was something like this :
$distro = {
'cauldron' => {
'arch' => [ 'i586', 'x86_64' ],
'medias' => {
'core' => [ 'release' ],
},
'base_medias' => [ 'core/release' ],
},
}
It is now something like this :
$distro = {
'cauldron' => {
'arch' => [ 'i586', 'x86_64' ],
'medias' => {
'core' => {
'repos' => {
'release' => {},
},
},
},
'base_medias' => [ 'core/release' ],
},
}
This should allow setting more infos about each medias / repos, that can
be used in order to generate media.cfg config files.
|
|
|
|
| |
Add an option to select supported arch of a distribution.
|
| |
|
|
|
|
|
|
| |
Move templates/iurt/sudoers.iurt to templates/sudoers.iurt. This file
was the only file in the iurt directory, so it is not needed to keep a
iurt directory.
|
|
|
|
|
|
|
|
|
|
|
| |
All distributions now use the same template file for their iurt
configuration file. The 'base_media' value has been added in the
distributions configuration in buildsystem::var::distros to allow
setting in iurt configuration the base_media that will be used to
generate chroots.
The iurt configuration now also contains all the medias in 'all_media',
instead of only the 'release' medias previously.
|
| |
|
|
|
|
|
| |
Iurt config for Mandriva 2010.1 was used when the servers were running
Mandriva 2010.1, but it is no longer used.
|
|
|
|
|
| |
Use the variable from webstatus configuration to set URL in upload.conf
instead of hardcoding pkgsubmit.$domain.
|
|
|
|
|
|
|
| |
buildsystem::var::distros will be used to store the list of
distributions and their configuration, medias, etc ... The list of
distributions and medias has been removed from buildsystem::mgarepo and
moved to mga_buildsystem::config.
|
|
|
|
|
| |
buildsystem::create_upload_dir is used only once, so it should be a
class and not a define.
|
|
|
|
|
| |
Remove parameters for buildsystem::create_upload_dir. Instead access
configuration variables directly.
|
| |
|
| |
|
|
|
|
|
| |
This function takes two hashes as argument and return a new hash containing
the content of the two hashes.
|
|
|
|
|
| |
This function takes a hash as argument and return the hash keys as a
list.
|
| |
|
|
|
|
| |
buildsystem::var::maintdb is used to store maintdb configuration.
|
| |
|
| |
|