GitLab

Execute git while making sure it answers in English

This way, regardless of the default language in the environment,
our task will complete as expected.

See merge request !31

This way, regardless of the default language in the environment,
our task will complete as expected.

Remove untouched repositories from git.check_status to reduce noise

Fix Redmine#102624

Untouched repositories: 

* "master repository" (the actual solution using Drupalizer)
* Drupalizer's repository

See merge request !30

Fix Redmine#102624

Remove drush option <contrib-destination> from "prepare install" command

We should parametrize this option through drush's make/yml files.

This will avoid an error that occurs in some situations where the folder
to specified in contrib-destination gets overwritten by a git clone.

e.g. : profiles/<my-profile> gets overwritten by a git clone while it might
have been parent folder of contrib modules previously downloaded.

This depends on the order a drush make/yml file has been written as far as
I can understand the issue.

See merge request !29

We should parametrize this option through drush's make/yml files.

This will avoid an error that occurs in some situations where the folder
to specified in contrib-destination gets overwritten by a git clone.

e.g. : profiles/<my-profile> gets overwritten by a git clone while it might
have been parent folder of contrib modules previously downloaded.

This depends on the order a drush make/yml file has been written as far as
I can understand the issue.

Rewrite rsync exclude rules in deploy task

Exclude `files/` directories and `settings.php` files from rsyncing.

See merge request !28

Exclude `files/` directories and `settings.php` files from rsyncing.

Use of always_use_pty variable

Import missing lcd() from fabric api into deploy.py



See merge request !27

Import missing execute() from fabric api into deploy.py



See merge request !26

Use fabric API to execute subtasks in docker.clean



See merge request !25

Feature/docker.clean

Removes container and images for a fresh workspace

See merge request !24

Do not use `fab_run()` helper for local tasks

Le `fab_run()` helper n'ajoute aucun fonctionnalité à l'exécution des commandes locales, mais il fair plus difficile à comprendre où un commande sera exécuter.

Si on minimalise utilisation de `fab_run()`, le	workflow de Drupalizer deviens plus transparent.

See merge request !22

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

The `provision` task specifically targets Jenkins platform that can only exist
in local environment. Direct usage of `local()` operation prevents accidental
manipulation of build artifacts in other environments.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

This argument is valid only in combination with `local` role parameter, and it
is not being called in this combination anymore.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

It makes sense (and even possible at all) to controll Docker containers from
local environment. Replacing `fab_run()` directly with `local()` calls ensures
that container management will not be performed inside of Docker instance or on
remote server because of a configuration error.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

The `fab_run()` function does not add any behavior for local calls, only
ambiguity of the command execution environment.

Inlining `local()` calls contributes to a clear separation of enrivonments.

Regularize usage of locale and site_languages config

On n'a pas de besoin d'avoir deux parameters qui configure la locale d'installation. Seulement site_languages is suffisant.

See merge request !23

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

The `site_languages` parameter can receive multiple language codes separated by
commas. Thus its value cannot be reused as-is as a value of `locale` parameter
which is passed to Drush during site installation.

The value of `site_languages` must be split, and the first element in the list
of languages will be used as a site locale during installation.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

Locale configuration during installation is done with two config parameters:
`locale` and `site_languages`, which is excessive. Given that the `locale`
parameter is a simple boolean, its value can be inferred from the value of
`site_languages` parameter.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

Do not try to download translation if no languages were set in site
configuration. Otherwise, Drush will try to download translations, will be able
to find anything, and ultimately fail environment initialization.

Do not update /etc/hosts file if target hostname is not set



See merge request !21

Change default vars values to something that does not crash Drupalizer



See merge request !20

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

It is better to use the most common IP address assigned to Docker containers
than to use a network broadcast address.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

If configured host name is empty, Drupalizer will construct an invalid `sed`
invocation to modify `/etc/hosts` file. As the result, environment
initialization will fail.

Reformat code to match Python coding standards



See merge request !17