Skip to content

Conversation

nejch
Copy link
Member

@nejch nejch commented Feb 19, 2020

I had really weird behavior (tests failing, omnibus config wouldn't load properly) until I realized I had a super old gitlab image locally that wasn't being pulled for tests.

This does an explicit docker pull instead of --pull since that's only been added recently and might not work for everyone, and it should only be a tiny penalty anyway.

I added a CLI flag so this should make it easy to build a CI matrix with tox that tests against several GitLab versions (e.g. latest + 3 last minor releases etc) or to explicitly test against a version reported in an issue. (Although I see currently Travis is excruciatingly slow so not sure if that's desired :D)

@max-wittig
Copy link
Member

max-wittig commented Feb 19, 2020

@nejch Thanks for the MR! I like the idea that we always pull the latest image, but I don't think we should test older versions. I'm sadly the only maintainer of this library and I don't think it's worth the time to spend on older GitLab versions.

@nejch
Copy link
Member Author

nejch commented Feb 19, 2020

Ok sure! If you think the flag for explicit tags is helpful I can leave it, e.g. to manually run tests to check an issue is only with an old gitlab version or so (it doesn't do anything by default); otherwise I can remove it.

@max-wittig
Copy link
Member

You're right. It does make sense that it's configurable and the default is the latest! Thanks!

@max-wittig max-wittig merged commit 745bdf7 into python-gitlab:master Feb 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants