New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
processing archived projects (and failing) #157
Comments
P.S. Re-tested againsta the latest (1.18.3.2) and I can still reproduce it. |
Fixed in v1.20.2, released today. |
Hello, Just re-tested it on the latest 1.20.2 and I'm afraid it's still an issue - gitlabform continues to process archived projects (and fails). |
Hi @gdubicki and @weakcamel , This wasn't working for me on 1.21 either. Gitlab 13.9.5-ee But, I think that may be because there is an assumption that gitlabform will skip projects that are set to archived manually, not via gitlabform :) Once I set it via gitlabform it was fine :)
|
Now it works like @jocado wrote. But I think that we could add a feature flag to skip all the projects that are archived, not only if we archived them. I am not sure why I didn’t propose it before.. 🤔 |
Ah, I see - thank you, that kind of makes sense. Yet I support the idea of a flag to skip archived projects while processing - this would be great! On a big Gitlab instance with archived projects all over the place (in multiple groups), specifying all of them in gitlabform config does not scale well. |
@gdubicki We're also interested in such a flag, if you tell me where should I put it I can work in a PR. |
I was thinking about a global flag passed as cli parameter, f.e. What do you think? |
Sounds good to me |
Please check out version 1.23.0rc1 (it was supposed to be 1.22.0rc1 but my finger slipped 😓 ), @Pigueiras and @weakcamel . :) Note that there is only o PyPI build with this version. Anyone interested in implementing #201 ? ;) |
Fixes #157 (in an even better way ;).
Since there's already 1.23.0, I tested it a bit and it looks great 👍 No more exceptions and thanks to the reduced number of projects to process, running gitlabform is now 30% faster. Thank you! |
When running
gitlabform
against ALL projects, gitlabform is attempting to apply configuration also to archived ones. This doesn't work since they're read-only and results in the following exception (in this case, on attempting to set MR approvals):Note: I'm using 1.17.0.1 (soon to be upgraded) but release notes of more current releases don't indicate any changes in this area.
The text was updated successfully, but these errors were encountered: