- Mar 27, 2025
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
The base image is now on Debian 12 with Python 3.11, and all our Python libraries and executables (`hg`) are installed in the `/opt/heptapod` virtualenv. The symptom is the hard error for lack of `yaml` library, but it would have failed later on anyway for not having Mercurial etc. With the base image now having Python 3.11, hardcoding 3.9 could not work anymore.
-
- Mar 16, 2025
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
As of heptapod/ci-images/fixed_pydeps@0dc8e065f8e8, tox is available in the Heptapod virtualenv only. Also switching to the Mercurial of the virtualenv, because it also has `hg-evolve`.
-
- Mar 15, 2025
-
-
Georges Racinet authored
-
- Mar 13, 2025
-
-
Georges Racinet authored
The Minio client lib is not installed with py-heptapod as of 5.1.2 (it depends on `boto3` instead), so we add it manually to quickly fix the build.
-
Georges Racinet authored
Given how it works, it hardly comes at a surprise that having clone bundles does not open up the repositories to the wild, yet still needs to be tested.
-
Georges Racinet authored
This is somewhat inelegant (large duplication) but it does the job and it is better for clarity.
-
- Mar 11, 2025
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- Mar 09, 2025
-
-
Georges Racinet authored
Good riddance
-
- Mar 07, 2025
-
-
Georges Racinet authored
and especially on the result of merges, which are just duplicates most of the time since we are usually just publishing a linear piece of history.
-
Georges Racinet authored
The noticeabile fact about MinIO compared to various online resources is that service-level environment variables do not work (perhaps just because our Runner does not feature them)
-
Georges Racinet authored
These `None` values will not be there in Heptapod 17.8.0 final
-
- Mar 04, 2025
-
-
Georges Racinet authored
These tests go with heptapod#189, but they will need a MinIO service to run in CI/CD.
-
Georges Racinet authored
Better than making a subsequent request (e.g., for visibility)
-
- Mar 01, 2025
-
-
Georges Racinet authored
-
Georges Racinet authored
Heptapod 17.9 will have the "finalization" of the native migration, hence there should not be any single remaining hg-git based project, except if the finalization failed and the instance is started with the option of running post_deployment migrations only after deployment. Of course people should not proceed in this case, but they might notice only at the next migration landmark version, which is 17.11 With this, we trim down the functional tests in the hg-git case to - backup tests - tests that require hg-git explicitly (mostly native migration)
-
Georges Racinet authored
Perhaps was it working in a previous version, but nowadays the positional argument would be the DB user name, not the DB name.
-
- Feb 28, 2025
-
-
Georges Racinet authored
-
- Feb 23, 2025
-
-
Georges Racinet authored
-
- Feb 20, 2025
-
-
Georges Racinet authored
-
- Feb 17, 2025
-
-
Georges Racinet authored
These should be carried over by the export/import sequence, even though the mirror definitions apparently are not. We need FS access, because there is no other way to access the auxiliary Git repository for checks - barring setting up yet another mirror, which would be vastly overdone. Final validation for heptapod#2052
-
- Feb 11, 2025
-
-
Georges Racinet authored
This Project field is now unnecessary to test mirrors and is not exposed in the APIs anymore. This is the functional tests counterpart of heptapod#2041
-
- Feb 05, 2025
-
-
Georges Racinet authored
In heptapod!997, we stopped using the Heptapod SHA display methods that replace Git hashes by Mercurial hashes from the web app, so of course we have to stop testing the hashes in the `hg-git` case (which is on life support, with the finalization of the general migration due for this cycle). On top of that, there was a side effect for native Projects: Mercurial SHAs are now truncated according to the GitLab standard (8 nybbles instead of previously 11). We adapt the tests accordingly, by introducing a `short_node` method on `hg.LocalRepo` to make later changes easier if needed.
-
Georges Racinet authored
The layout changed for GitLab 17.9, and is actually easier to query.
-
- Jan 28, 2025
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- Jan 26, 2025
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- Jan 25, 2025
-
-
Georges Racinet authored
Necessary for the tests to pass with the `heptapod` branch of the Rails app already merged in `heptapod-future`.
-
- Jan 24, 2025
-
-
Georges Racinet authored
The `manual-ssh` variant is very flaky, needing usually 3 retries to pass in CI. Since we are after heptapod#1964, it is ok to stop testing some features for hg-git projects (remaining support being there so that they can be migrated), so we stop wasting time with this.
-
- Jan 23, 2025
-
-
Georges Racinet authored
-
Georges Racinet authored
Heptapod 17.7 prevents creating legacy, hg-git based Mercurial projects. However it still has a feature flag, meant explicitly for these tests. We have to do the feature flags update before the application setting update, of course.
-
Georges Racinet authored
With the typical invocation by tox, it was already displayed, but it was buried with other options. This gives it better visibility.
-
- Nov 07, 2024
-
-
Georges Racinet authored
Meant to reproduce heptapod#1876, but actually passing in HDK context.
-
- Jan 21, 2025
-
-
Georges Racinet authored
The test for backup of Git repositories used internally for mirroring is brought by this merge, and had to be modified because the Git repository is not filled at push time in the 17.7 version, but upon mirroring. Hence we needed to setup a mirror.
-