Skip to content

Conversation

@adunsulag
Copy link

Testing this PR to see if it fixes the inferno caching issue.

@adunsulag
Copy link
Author

@kojiromike Sorry it took me a while to execute this, but it looks like the cache is continuing to have issues with inferno.

@kojiromike
Copy link

@adunsulag I'm still confused how to handle composer, since nothing explicitly calls composer install -- I guess it happens inside openemr.sh?

@kojiromike
Copy link

@adunsulag in any case, I've pushed one more effort if you want to try.

@adunsulag adunsulag force-pushed the openemr-pr-external-8673-actions-cache-2 branch from 8ba31f6 to bc067ff Compare July 24, 2025 00:49
@adunsulag
Copy link
Author

@kojiromike thanks giving it a try.

So the Inferno ci/inferno/run.sh script calls the /ci/ciLibrary.source::main_build which does call composer install command.

main_build() {
    actions_chmod -R 0777 .
    local composer_home
    composer_home=$(composer --no-interaction config --global --absolute home) 2> /dev/null
    composer install --prefer-dist --no-progress
    npm ci
    npm run build
    composer global require phing/phing
    "${composer_home}/vendor/bin/phing" vendor-clean
    "${composer_home}/vendor/bin/phing" assets-clean
    composer global remove phing/phing
    composer dump-autoload -o
    rm -fr node_modules
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants