- 24 Nov, 2020 5 commits
-
-
Georges Racinet authored
Now it's really basic again.
-
Georges Racinet authored
it will be reused
-
Georges Racinet authored
It's a bit cleaner: we can have the tear down, without the extra indention that the `with` statement would need.
-
Georges Racinet authored
This reproduces the problems encountered with the Mercurial native mode, see hgitaly#23.
-
Georges Racinet authored
This is just convenient and would also mean a fixture would be very easy to create.
-
- 25 Nov, 2020 1 commit
-
-
Georges Racinet authored
which I've been doing manually on my development workspaces. Of course the hg-native mode hadn't a chance to pass on CI before this.
-
- 24 Nov, 2020 2 commits
-
-
Georges Racinet authored
The stable branch is still for Heptapod 0.16, but there probably won't be any release on it, now.
-
Georges Racinet authored
-
- 19 Nov, 2020 5 commits
-
-
Georges Racinet authored
-
Georges Racinet authored
With the native mode, something pushed is pushed. In that case if we don't want a closing changeset of the GitLab branch, we have to prevent pushing it in the first place. People can always change the default branch setting if needed
-
Georges Racinet authored
For native repos, the shadowing happens at read time, so we can't make a difference between sliding (not a new bookmark) or not. Also, we cannot just let the bookmark at a previous position for the non-shadowed case of the default GitLab branch. This latter case is done identically for non-native repos because it was arguably a logical discrepancy.
-
Georges Racinet authored
The branchmap rules make it so that if it's useful for visualisation of instabilities, in stack topics case, the older one is still visible after publication (because it's base of the one that now has to be rebased). Hoping this can change at some point in the future, though.
-
Georges Racinet authored
For the very few tests that need to make a difference, it's best not to assume we will use a global flag available on the Heptapod project forever. It could very well depend on the given project.
-
- 17 Nov, 2020 1 commit
-
-
Georges Racinet authored
This one wasn't absorbed. Doesn't seem worth it to make it fit inside that series that predates the flake8 version bump.
-
- 14 Nov, 2020 1 commit
-
-
Georges Racinet authored
See heptapod#368 Now with two sets of scenarios with various refusals, and the check that accepting Merge Requests is recognized to go through another set of permissions (very important to avoid locking situations) --HG-- branch : stable
-
- 03 Nov, 2020 12 commits
-
-
Georges Racinet authored
This is again cleaner, and ultimately the reason why we've put a long timeout and `cleanup_teardown()` in `Project.__exit__()`, even though it's much less necessary now than it was before we made Project names unique.
-
Georges Racinet authored
Less pollution, even though try…finally wasn't so bad.
-
Georges Racinet authored
-
Georges Racinet authored
This works, but we still have uncertainties about MR creation prompt on push and the expected pipelines, so we don't test these.
-
Georges Racinet authored
This will allow for nicer cleanups, especially for those created in tests. We're adopting the strong cleanup capability and the larger timeout in `Project.__exit__()` to mimic what the Project fixtures do, in the hope to have them simply use the new Context Managers.
-
Georges Racinet authored
We chose to pass a whole Project instance, because it's seem very unlikely we'd have a use case for passing an id (caller would have created the target Project or would use a fixture), and therefore it makes things simpler on the average for the caller.
-
Georges Racinet authored
We already had a persistent normal user and the `external_user` fixture. This one is not external.
-
Georges Racinet authored
Proper testing of Git operation will need this.
-
Georges Racinet authored
A bit cleaner this way. One day, we may reduce the duplication by introducing a proper MergeRequest object.
-
Georges Racinet authored
Amazingly, the `owner_api_request()` shortcut was all we needed for a long time, but we'll now will need to be able to pass the user explicitely.
-
Georges Racinet authored
-
Georges Racinet authored
This will help reducing the boiler plate and over long statements. Leveraging in test_import for immediate testing.
-
- 17 Nov, 2020 5 commits
-
-
Georges Racinet authored
The good thing is that we finally get back to sanity with boolean operators. This is now legit: if something and othercondition:
-
Georges Racinet authored
Notably, we're using `l` as a variable in short list comprehensions only (ambiguity with 1 is not a problem with any decent terminal font). This is just fine, E741 is a pain.
-
Georges Racinet authored
This way, we won't depend from Docker Hub rate limiting.
-
Georges Racinet authored
It's time to get rolling.
-
Georges Racinet authored
In the case where several jobs happen to run on the same Docker host, it's important to avoid that they use the same services. Otherwise, the first completion breaks the ones still running, because it shuts down the services they rely on. Of course, it's better not to have such voracious jobs in parallel, but that's a different issue.
-
- 31 Oct, 2020 1 commit
-
-
Georges Racinet authored
It's still far from being comprehensive, but it did catch something to be fixed.
-
- 29 Oct, 2020 3 commits
-
-
Both SHA and repo_type had to be corrected, being still hardcoded for Mercurial.
-
-
-
- 08 Nov, 2020 1 commit
-
-
Georges Racinet authored
Had forgotten that the logs are located in subdirectories. It would be tempting do just take the whole /var/log/gitlab directory, but then I'd be wary it could be too big. I expect the artifacts system to perform compression (IIRC it's artifacts are wrapped in a zip file). We do have some random failures in the nightly builds that I'd like to investigate. We'll see if that is enough.
-
- 18 Oct, 2020 2 commits
-
-
Georges Racinet authored
This spares us refreshing APT sources and installing tox, better for latency, bandwidth, given that the chances the base image is already available are high, and about the same as the octobus image meant for classical Mercurial extensions testing that's been replaced.
-
Georges Racinet authored
This parallels what's been done in omnibus-heptapod, except that we still allow manual triggering. The simplest case remains to make a MR for tests expected to pass on the latest testing Heptapod Docker image.
-
- 15 Oct, 2020 1 commit
-
-
Georges Racinet authored
This will give us the means to test heptapod#204, hence also omnibus-heptapod#12, since archive production will be done by HGitaly.
-