Joomla! Issue Tracker - CMS

Download
Launch
Feeling Lucky

[#22338] - [4.0] Nightly build. New installation. "It looks like you are trying to run Joomla! from our git repository."

J4 Issue ?
avatar ReLater
ReLater
23 Sep 2018

Steps to reproduce the issue

  • Several reports and I tried it, too:
    Try to install Nightly Build Sunday, 23 September 2018 02:00:36 UTC
    Joomla_4.0.0-alpha5-dev-Development-Full_Package.zip

Expected result

  • Installation GUI

Actual result

23-09-_2018_13-05-54

avatar ReLater ReLater - open - 23 Sep 2018
avatar joomla-cms-bot joomla-cms-bot - change - 23 Sep 2018
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 23 Sep 2018
avatar ReLater
ReLater - comment - 23 Sep 2018

The whole /media/ folder is missing.

avatar richard67
richard67 - comment - 23 Sep 2018

Yes, and compiled css of the templates are missing, too.

This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22338.

avatar ReLater
ReLater - comment - 23 Sep 2018

Also missing in 4.0 branch of repository

avatar richard67
richard67 - comment - 23 Sep 2018

Nightly build package from yesterday was ok.

This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22338.

avatar richard67
richard67 - comment - 23 Sep 2018

@wilsonge Any idea what could have happened?

avatar richard67
richard67 - comment - 23 Sep 2018

@ReLater Media folder is not in 4.0-dev branch of the repo anymore since PR #21328 , I think. But it should have been created by nmp install before the package was packed. It seems this failed somehow.

This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22338.

avatar richard67
richard67 - comment - 23 Sep 2018

@ReLater Media folder is not in 4.0-dev branch of the repo anymore since PR #21328 , I think. But it should have been created by nmp install before the package was packed. It seems this failed somehow.

This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/22338.

avatar brianteeman brianteeman - change - 23 Sep 2018
Labels Added: J4 Issue
avatar brianteeman brianteeman - labeled - 23 Sep 2018
avatar ReLater
ReLater - comment - 23 Sep 2018

Related: #22325
One should test own commits before committing them blindly into an "official" branch for merging.

Again frustrated "normal" testers/users out there.

avatar wilsonge
wilsonge - comment - 23 Sep 2018

ping @mbabker as I'm not sure where the new jenkins lives. Given git is compiling just fine and the comments on @22325 wondering if the jenkins workspace isn't being cleared down properly

avatar franz-wohlkoenig franz-wohlkoenig - change - 23 Sep 2018
Status New ⇒ Discussion
avatar franz-wohlkoenig franz-wohlkoenig - change - 23 Sep 2018
Category ⇒ com_installer
avatar mbabker
mbabker - comment - 23 Sep 2018

Nightly build regenerated. It had nothing to do with "blindly committing to an official branch", there was a GitHub API hiccup when the build for the 4.0 branch was put together last night and it caused the package to not build correctly. Nothing more, nothing less.

avatar mbabker mbabker - change - 23 Sep 2018
Status Discussion ⇒ Closed
Closed_Date 0000-00-00 00:00:00 ⇒ 2018-09-23 15:29:21
Closed_By ⇒ mbabker
avatar mbabker mbabker - close - 23 Sep 2018
avatar mbabker
mbabker - comment - 23 Sep 2018

FWIW 4e8b304 adds checks to the build script to fail it if composer install or npm install fail (the latter being what actually failed), this should cause the nightly build job to fail over as well and not push a broken package.

avatar ReLater
ReLater - comment - 23 Sep 2018

"blindly committing to an official branch"

Sorry, but there is also #22325 that makes it impossible to recompile scss after build. That is something that I packed also in my angry phrase.

avatar brianteeman
brianteeman - comment - 23 Sep 2018

That is completely unrelated

Add a Comment

Login with GitHub to post a comment