Closed herreralv-dev closed 3 years ago
hi @herreralv-dev have you tried to clear the cache gitlab cache?
Hi @edbizarro,
A bit hesitant on clearing the cache if you are talking on this: https://gitlab.com/gitlab-org/gitlab-foss/-/issues/41369
We've opted to downgrade the composer to version 1.x and force xdebug to check on coverage instead, here's a little snippet on what we did:
I think this is just a workaround and dependencies will be stale in the long run, our long term solution would be update our Laravel framework and some affected dependencies.
Thank you so much for your reply.
Cheers!
Hi all, @edbizarro just to say that clearing the GitLab cache does nothing... Some older versions of Laravel are just not compatibles with Composer 2. As the OP said the only solution is to force the use of Composer 1 or to update the used version of Laravel (which is a bit complicated for complex projects...)
Yeah, i think because of this old Laravel thing i'll change back to composer 1 and wait a little longer or perhaps make 2 versions with composer 1 and 2
Good Day!
We are having issues after the update of Composer 2 release. It works fine the last few days, but when our developers started to commit and the pipeline starts.
Here's our gitlab-ci.yml:
Looking forward to the resolution for this.
Thank you so much and have a good day!