Skip to content

deploy:check_composer_install fails #10

Closed

Description

@surphil

Complete deployer-extended-typo3 setup works nicely, but only if we remove deploy:check_composer_install.

# Working run without deploy:check_composer_install 
➜  git:(master) ddev exec dep deploy staging 
✈︎ Deploying master on staging
✔ Executing task deploy:check_lock
✔ Executing task deploy:check_branch_local
✔ Executing task deploy:check_branch
✔ Executing task deploy:prepare
✔ Executing task deploy:lock
✔ Executing task deploy:release
✔ Executing task deploy:update_code
✔ Executing task deploy:shared
✔ Executing task deploy:writable
✔ Executing task deploy:vendors
✔ Executing task deploy:clear_paths
✔ Executing task db:backup
✔ Executing task buffer:start
✔ Executing task db:truncate
✔ Executing task typo3cms:database:updateschema
✔ Executing task deploy:symlink
✔ Executing task cache:clear_php_cli
✔ Executing task cache:clear_php_http
✔ Executing task buffer:stop
✔ Executing task deploy:unlock
✔ Executing task cleanup
✔ Executing task deploy:extend_log
Successfully deployed!
 
# Breaking run with deploy:check_composer_install 
➜ git:(master) ✗ ddev exec dep deploy staging
✈︎ Deploying master on staging
✔ Executing task deploy:check_lock
➤ Executing task deploy:check_composer_install
✔ Executing task deploy:failed
✔ Executing task deploy:unlock
✔ Executing task deploy:unlock
✔ Executing task deploy:unlock

In deploy_check_composer_install.php line 10:
                                                                                                                                                                                            
  A composer.lock changes has been detected but you did not run "composer install". Please run composer install, then check if everything is working on your instance and do deploy after.  
                                                                                                                                                                                            

deploy [-p|--parallel] [-l|--limit LIMIT] [--no-hooks] [--log LOG] [--roles ROLES] [--hosts HOSTS] [-o|--option OPTION] [--] [<stage>]

Failed to execute command dep deploy staging: exit status 1

Local composer --dry-run output:

# ddev
➜ git:(master) ddev composer install --dry-run
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Nothing to install, update or remove
49 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

# local without ddev (not really preferred way to work)
➜ git:(master) composer install --dry-run
Installing dependencies from lock file (including require-dev)
Verifying lock file contents can be installed on current platform.
Nothing to install, update or remove
49 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

We are using composer 2.0.7.

Any idea?

Activity

  1. kszymukowicz commented on Dec 4, 2020

    @kszymukowicz
    Contributor

    Yes. This is because the info about "no need to install anything" has changed a bit in composer2.
    I am working on composer2 issues. This will be fixed soon.

  2. kszymukowicz commented on Dec 30, 2020

    @kszymukowicz
    Contributor

    @surphil
    Plz try deployer-extended-typo3 16.0.0. The check for deploy:check_composer_install is fixed and additionally you can set composer version with set('composer_channel', 2)

  3. locked and limited conversation to collaborators on Jun 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions