GitLab

Attempt to save the situation by reading GITLAB environment variables

These where detected by github

The issue has been seen with thin 1.7 in users-api-ror, but to keep both
application as close as possible as far as packaging and installation is
concerned, change this here

They cannot be avoided easily because bundler will change Gemfile.lock
to include version used to build bundle, and this will change between
debian versions

Packaging attempts to make sure git state is clean before packaging. If
it is not, output a more helpfull message

This enables the same debian/control file for jessie and stretch
variants, and removes the need for live patching using sed in the
.gitlab-ci.yml file

This version is the first that support prepared statements properly, at
least for the script/generate_prepared_statement_bug.sh test

With this new logger, it becomes easy to prepend to all entries of the
log file a timestamp, thread_id and fiber_id before each log line

In this version, package deployment is a manual step in all branch based
deployments, that will fail if attempted on an untagged release

Jonathan Pastor authored Oct 03, 2018 and MARGERY David committed Oct 18, 2018

delete jabber.rb and remove blather from gem dependencies in the process

Merge branch 'remove-jabber-connection' into 'master'

See merge request !58

comment the connection to jabber.grid5000.fr, and all event handlers related to this connection

See merge request !57

(cherry picked from commit 6feba383)

ef273025 delete jabber.rb and remove blather from gem dependencies
965edc16 [jabber] remove any mention to xmpp and jabber

For stretch, this seems required to avoid "Encryption not available on
this event-machine" errors when running tests

By design, conditions in 'only' are alternatives. To have a job only
built on a given branch and if a tag matches a given pattern use except
wiith a negative condition