- Nov 17, 2020
-
-
Georges Racinet authored
-
- Nov 16, 2020
-
-
Georges Racinet authored
Part of heptapod#368: the Rails app will be able to set this environment variable and we're now sending it back as the `accept_mr_iid` key to the listener for the pre-receive hook, so that the Rails app may apply merge permissions instead of (direct) push permissions. Using the (project-local) iid is better than the id, because the receiving end won't have to check that someone is trying to cheat with a MR on another project and is anyway fast compared to the overall amount of process on its side.
-
- Nov 15, 2020
-
-
Georges Racinet authored
This is part of heptapod#364. Heptapod Workhorse will pass the `X-HEPTAPOD-HG-NATIVE` header with the appropriate value, and we use it to set configuration on the wished repository accordingly. We could have made the `env` argument of the `load_repo()` method optional (and hence hadn't needed to adapt existing tests), but nothing would then prove that it wasn't forgotten, even with coverage proving that `load_repo()` is indeed called (which it does).
-
Georges Racinet authored
This is part of heptapod#364. Heptapod Shell cannot pass `--config` command-line arguments, because that is rightfully considered a potential security breach (it would allow to register a hook, hence for arbitrary code execution). So we resort to an environment variable. It will actually also be more practical for the Rails app (only one method, the env creator, to patch)
-
- Nov 14, 2020
-
-
Georges Racinet authored
This is the first part of heptapod#364 If the new `heptapod.native` config flag is set, payloads of GitLab hooks will be made of Mercurial SHAs instead of Git SHAs. This will be used for native Mercurial projects, for which obviously GitLab notification hooks must contain Mercurial SHAs, since these are the only ones the Rails app is supposed to be aware of. For now, there's no facility to set this flag automatically but it can be used for testing in developer setups (by putting it in `hdk.hgrc`). ## Implementation details: Instead of going over all the places were a SHA is recorded that will end up in a hook call, we convert back to Mercurial right before we send the hook. This is perhaps good enough, while we are in the transitional way of operation of still converting to Git. Things will be very different anyway when we don't do that any more.
-
Georges Racinet authored
This was forgotten in the big refactor of the CI setup. (the tests are currently not passing with hg-default, seems to be quite normal, an API change)
-
- Nov 10, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- Nov 01, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
That was long overdue
-
Georges Racinet authored
See also heptapod#352
-
- Oct 26, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- Oct 16, 2020
-
-
Georges Racinet authored
Since py-heptapod also serves as a common library for HGitaly, it makes sense to check the impact of landed changes on HGitaly. This will also propagate scheduler or trigger builds. For example if there's a rebuild of hg-default, it should trigger the rebuild of py-heptapod, which will trigger that of HGitaly. We'll have a few redundant buils along the way (hg-current didn't change in that example), but that's tolerable for the time being and could probably be further optimized.
-
Georges Racinet authored
The install job is expected now to be slower than the other, at least if all Docker images are already downloaded.
-
- Oct 15, 2020
-
-
Georges Racinet authored
-
- Oct 14, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- Sep 30, 2020
-
-
Georges Racinet authored
In particular this brings the enforcement of the 100% coverage policy.
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-
- Sep 28, 2020
-
-
Sushil Khanchi authored
This patch initiate a tag module which aims to provide utilities and conventions for gitlab/heptapod tags. Also, adds a method `gitlab_tag_ref`.
-
- Sep 30, 2020
-
-
Georges Racinet authored
Actually this is done in run-all-tests, but it shouldn't be a problem for local runs.
-
- Sep 22, 2020
-
-
Georges Racinet authored
-
- Sep 21, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- Sep 10, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-
- Sep 04, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
The recently added group-level environment variables for heptapod#339 end up in the message produced by this test, making the assertion too strict.
-
Georges Racinet authored
-
- Aug 24, 2020
-
-
Georges Racinet authored
-
- Aug 25, 2020
-
-
Georges Racinet authored
For the record, dulwich 0.20 dropped Python 2 support.
-
Georges Racinet authored
We need a marker right now so that the requirements file shipping with the Rails application can refer to it.
-
- Aug 04, 2020
-
-
Georges Racinet authored
-