Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI core:update returns exit code 1 #43366

Closed
35grain opened this issue Apr 25, 2024 · 5 comments
Closed

CLI core:update returns exit code 1 #43366

35grain opened this issue Apr 25, 2024 · 5 comments

Comments

@35grain
Copy link

35grain commented Apr 25, 2024

Steps to reproduce the issue

Run the core:update command.

Expected result

If everything goes as intended, exit code 0 is expected.

Actual result

Exit code 1 is returned.

System information (as much as possible)

Joomla 5.x. PHP 8.2.17.

Additional comments

This currently makes automation tasks fail, as anything other than 0 is considered as a failure. Is this intended behavior?

@brianteeman
Copy link
Contributor

What exact version are you updating from

@35grain
Copy link
Author

35grain commented Apr 25, 2024

Initially I updated from 5.0.2 but the same happens with 5.1.

@Hackwar
Copy link
Member

Hackwar commented Apr 26, 2024

What is your complete output of the command? It should display Joomla core updated successfully! as last line in the output and return a 0 exit code. That is the code since 4.4 actually. Are you absolutely sure that the update was 100% successfull?

@alikon
Copy link
Contributor

alikon commented Apr 27, 2024

if you already have the latest Joomla! version then the exit code is 1

@35grain
Copy link
Author

35grain commented Apr 29, 2024

Unfortunately I don't have the output for the update from 5.0.2 to 5.1, however everything seems operational so it is difficult to tell if something went wrong. But

if you already have the latest Joomla! version then the exit code is 1

is more or less what I was hoping to figure out whether or not this is the intended behavior. Will try to work around this then. Thanks!

@35grain 35grain closed this as completed Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants