The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

SSL connection timeout in all packages composer

Ricardo Frederico Cambe Ribeiro
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 13, 2024

The pipeline has been working well for quite some time, until yesterday out of the blue started having 2 problems in all branches and pipelines (including the ones that had been successful, we rerun it and the problem continues), when running either (composer install) or (composer update).


Pipeline:

 

image: maven:3.3.9
definitions:
  variables:
    ...
  steps:
    - step: &build
        image: bitnami/laravel
        runs-on:
          - 'self.hosted'
          - 'linux'
        name: 'Build'
        caches:
          - composer
        script:
          - apt-get update && apt-get install -y zip
          - ls -la
          - rm -r .history .idea .vscode dockerfiles
          - rm docker-compose.yml
          - cd src/
          - rm -r .history __mock
          - composer clear-cache
          - composer update --no-interaction --no-progress #problem here
          - composer install --no-interaction --no-progress #or here if the one before is removed
          - php artisan optimize:clear
          - npm install --quiet
          - npm run build
          #- rm -r .git
          - cd ..
          - zip -r app-build-$BITBUCKET_BUILD_NUMBER.zip .
        artifacts:
          - "*.zip"
pipelines:
  branches:
    release/*:
      - step: *build
#      - step: *deploy





Problem 1: SSL connection timeout in all the packages:

 

  • composer update --no-interaction --no-progress

 

581
Now trying to download from source
582
Failed to download spatie/laravel-ignition from dist: curl error 28 while downloading https://api.github.com/repos/spatie/laravel-ignition/zipball/3c067b75bfb50574db8f7e2c3978c65eed71126c: SSL connection timeout
583
Now trying to download from source
584
Failed to download microsoft/azure-storage-queue from dist: curl error 28 while downloading https://api.github.com/repos/Azure/azure-storage-queue-php/zipball/750974f7a888bb7a93cacb873b3280c45e970a23: SSL connection timeout
585
Now trying to download from source
586
Failed to download squigg/azure-queue-laravel from dist: curl error 28 while downloading https://api.github.com/repos/squigg/azure-queue-laravel/zipball/e579e02e7b0828c2e8bb1842c12b1a7061ee6d29: SSL connection timeout
587
Now trying to download from source
588
Failed to download tightenco/ziggy from dist: curl error 28 while downloading https://api.github.com/repos/tighten/ziggy/zipball/939576ad0f3d3e633a9401c8c377bc7bc873ff35: SSL connection timeout
589
Now trying to download from source

 


Problem 2 (fail pipeline): 

 

 

In GitDownloader.php line 82:
git was not found in your PATH, skipping source download
update [--with WITH] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--dry-run] [--dev] [--no-dev] [--lock] [--no-install] [--no-audit] [--audit-format AUDIT-FORMAT] [--no-autoloader] [--no-suggest] [--no-progress] [-w|--with-dependencies] [-W|--with-all-dependencies] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [-m|--minimal-changes] [-i|--interactive] [--root-reqs] [--] [<packages>...]
597

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 14, 2024

Hi @Ricardo Frederico Cambe Ribeiro

Welcome to the community.

Based on your YAML configuration, I can see you are using Linux Docker Runners.

Would it be possible for you to run your build from Pipelines infrastructure by commenting out the runners configuration?

This is for us to see if the same behaviour is happening from different environment.

Let me know how it goes.

Regards,
Mark C

DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events