- May 13, 2020
-
-
Georges Racinet authored
It's just not reasonable to expect that our tests would always pass with Mercurial default (unstable) branch, since this is precisely our alert mechanism.
-
- May 08, 2020
-
-
Georges Racinet authored
-
- May 03, 2020
-
-
Manuel Jacob authored
-
Manuel Jacob authored
-
Manuel Jacob authored
-
Manuel Jacob authored
-
- Mar 10, 2020
-
-
Georges Racinet authored
with the newly created ci-py2-hg-git images, we'll get slightly faster builds, using less bandwidth and power.
-
Georges Racinet authored
The 'current' stage will run the tests against the latest released Mercurial version available in our base Docker images, while the 'compat' stage will run against all other versions. This way, most failures in ordinary development will be detected early and the full compatibility jobs won't be launched (they will eventually, once the failures against the current version are resolved)
-
Georges Racinet authored
As usual, this is the latest released version.
-
- Jan 11, 2020
-
-
Georges Racinet authored
This is the same as what's been done earlier for heptapod/hg-git: `/usr/bin/ssh` is no longer installed with `git-core` because the base image skips install of `Recommends` dependencies.
-
- Dec 22, 2019
-
-
Georges Racinet authored
Currently, the tests fail for this version of Mercurial, hence we'll add the job once they are fixed. Ideally, this changeset should be rebased on top of a revision that fixes hg-git for Mercurial default, hence validating the fix.
-
Georges Racinet authored
All commands that make use of Python and are meant to retrieve or prebuild code should not themselves use potentially incompatible stuff from /ci/repos/mercurial. For instance, updating Mercurial to 'stable' should not risk using a random version of the mercurial Python package. It must instead use the one provided system-wide, that is consistent with the `hg` command.
-
- Dec 08, 2019
-
-
Georges Racinet authored
Without these two flags, we get the following: ``` devel-warn: changectx.__init__ is getting more limited, see context.changectxdeprecwarn() for details (compatibility will be dropped after Mercurial-4.6, update your code.) at: /tmp/hgtests.ShCiwV/install/lib/python/mercurial/localrepo.py:849 (__contains__) ``` after inspection of the code paths, it turns out that these are self-inflicted Mercurial warnings. This can be seen with test-clone.t, the whole traceback does not involve hg-git at all. So the only practical solution we have is to silence the warnings. I think it's acceptable as long as it's for this single version and in particulary not for any version under active development or maintenance.
-
- Dec 07, 2019
-
-
Georges Racinet authored
Noticed that some tests don't pass while working on the CI configuration. Ideally, this changeset should be rebased on top of a revision that fixes hg-git for Mercurial default, hence validating the fix.
-
- Dec 22, 2019
-
-
Georges Racinet authored
Now that Octobus images for CI of Mercurial extensions against a fixed Mercurial version have a prebuilt Mercurial, we can just use it, saving some computing resources and waiting time. Also, this makes sure that the CI will use the test runner provided with hg-git, which will avoid problems on older versions (seen one with a new skip rule). To avoid inconsistencies (hg executable importing the system wide mercurial Python package), we need to also set PYTHONPATH, and conversely unset it to run pip in before_script
-
- Dec 08, 2019
-
-
Georges Racinet authored
Currently, hg-git does not pass the tests for - Mercurial 4.6 - the head of Mercurial default branch In order to start benefit of the CI and enforcing that contributions must pass it, we will therefore add jobs for these two versions in separate topics and Merge Requests. Also worth of note is that 5.2 can have new point releases that will be provided in the base Docker image. Hence we don't exclude it from nightly runs.
-
Georges Racinet authored
This Gitlab CI configuration launches the tests of the target hg-git revision against: - the current head of Mercurial `stable` branch - a fixed Mercurial version, assumed not to change anymore We'll add more versions in a follow-up. ## `image` All operations after cloning of the tested `hg-git` revision happen in a fresh container started on this Docker image. The ones we use are available on Docker Hub, with definitions in https://dev.heptapod.net/octobus/ci-dockerfiles ## `before_script` The `before_script` at toplevel will be executed for each job. In later GitLab versions, we'll also have a `default` toplevel key that will allow to specifiy a common value for `script` (and `before_script`, deprecating its use at toplevel). The installations performed by this `before_script` would be better provided by a dedicated series of base Docker images, saving resources and execution time. If that is done, we are able to remove this `before_script` altogether. ## `except` In a first installment, we'll add a nightly scheduler after landing of this configuration. We don't want it to relaunch tests against Mercurial versions that don't change ## `script` This form has the tests launcher build and use the appropriate Mercurial revision (information about it displayed first).
-