tea/.gitlab/pipeline/jobs/build-composer-dependencies.yml

build-composer-dependencies:
  extends: .default
  stage: build
  needs: [ ]
  variables:
    COMPOSER_CACHE_DIR: '.composer'
  script:
    - composer --version
    - COMPOSER_CACHE_DIR=.composer
      composer update --prefer-dist --no-progress --optimize-autoloader
  artifacts:
    when: on_success
    expire_in: 2 weeks
    paths:
      - .Build
  cache:
    paths:
      - .composer
[CLEANUP] Split GitLab jobs (#273) 2021-08-24 10:27:50 +02:00			`build-composer-dependencies:`
			`extends: .default`
			`stage: build`
			`needs: [ ]`
			`variables:`
			`COMPOSER_CACHE_DIR: '.composer'`
			`script:`
			`- composer --version`
			`- COMPOSER_CACHE_DIR=.composer`
[TASK] Prevent composer.lock file (#1161) This is a TYPO3 extension, a library. We do not track the `composer.lock` file for that reason. Composer itself offers an option to prevent generation of the file. This is now configured to prevent the creation of the file. That should prevent issues with local version of the file. One might change the `composer.json` version constraints but updates might fail due to locked version constraints. This no longer happens if no locked version, due to missing lock file, exist. Composer would render warnings when using `composer install` without a lock file. That's why we update the CI commands to use `composer update` instead. That warning was already rendered within CI due to missing file. 2024-02-07 09:54:59 +01:00			`composer update --prefer-dist --no-progress --optimize-autoloader`
[CLEANUP] Split GitLab jobs (#273) 2021-08-24 10:27:50 +02:00			`artifacts:`
			`when: on_success`
			`expire_in: 2 weeks`
			`paths:`
			`- .Build`
			`cache:`
			`paths:`
			`- .composer`