Composer 2 about gitlab-ci-pipeline-php HOT 6 OPEN

Hello @j3j5

Temporarily, on an existing project, we are testing the following solution:

project:
  services:
    - mariadb:10.3
  image: edbizarro/gitlab-ci-pipeline-php:7.4-alpine
  script:
    - composer -V # Composer version 1.10.15 2020-10-13 15:59:09
    - sudo composer self-update --2 
    - composer -V 
    # The "hirak/prestissimo" plugin (installed globally) was skipped because it requires a Plugin API version ("^1.0.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option. 
    # Composer version 2.0.3 2020-10-28 15:50:55

I think it would be good to be able to switch from V1 to V2 and vice-versa.

from gitlab-ci-pipeline-php.

I see there's an open PR #108, I'm fine with that approach 👍

from gitlab-ci-pipeline-php.

@j3j5 I confirm you before doing my PR, I saw the message from @romainnorberg and i use this to solve my CI

from gitlab-ci-pipeline-php.

Hi @romainnorberg , that exactly has been my approach, to upgrade from the container, but I guess it'd be better if we could choose w/o having to download the upgrade/downgrade every time. Personally, I'd go for using composer2 only and leave the downgrade (as you mention above) as an option, but I guess it's @edbizarro call.

from gitlab-ci-pipeline-php.

@edbizarro Possible that composer 2 is still not working?

from gitlab-ci-pipeline-php.

Is there anything that is being done about this?

Is there a better alternative?

from gitlab-ci-pipeline-php.