Latest merge does not build #6

New issue

Closed

opened 2022-06-03 16:41:44 +00:00 by emacsen · 5 comments

emacsen commented

2022-06-03 16:41:44 +00:00

(Migrated from gitlab.com)

As seen in the Cloudflare logs:

babka-social-blog.0a16de1c-e37c-45d5-9c8a-209de0eee4d1.log

The problem with the build is that the production build does not complete due to what appears to be missing PostCSS, despite the fact that JEKYLL_ENV is set to production

As seen in the Cloudflare logs: [babka-social-blog.0a16de1c-e37c-45d5-9c8a-209de0eee4d1.log](/uploads/8d2259bb0af09f5b8bb3700b36ba285a/babka-social-blog.0a16de1c-e37c-45d5-9c8a-209de0eee4d1.log) The problem with the build is that the production build does not complete due to what appears to be missing PostCSS, despite the fact that `JEKYLL_ENV` is set to `production`

emacsen commented

2022-06-03 16:41:44 +00:00

(Migrated from gitlab.com)

assigned to @vosaul

vosaul commented

2022-06-04 09:04:24 +00:00

(Migrated from gitlab.com)

I even tried to return the old name, but it didn't fix anything.

Everything works locally, something is going wrong on the Cloudflare side. I noticed that it started on May 23. The only change made then is to replace "name": "fedi-foundation" with Babka Social Blog ![image](/uploads/de9275e96f4a7e04ff70c781fe6a86e0/image.png) I even tried to return the old name, but it didn't fix anything.

emacsen commented

2022-06-05 01:02:01 +00:00

(Migrated from gitlab.com)

You changed the destination folder in commit c1cce8dc, which explains why Cloudflare says the _site directory is missing and it can't grab the build artifacts.

I had it building in both Gitlab by manually specifying the output directory and Cloudflare pages by using _site, which is the default directory.

What was the reason for this change?

You changed the destination folder in commit c1cce8dc, which explains why Cloudflare says the `_site` directory is missing and it can't grab the build artifacts. I had it building in both Gitlab by manually specifying the output directory and Cloudflare pages by using `_site`, which is the default directory. What was the reason for this change?

vosaul commented

2022-06-06 06:30:24 +00:00

(Migrated from gitlab.com)

I noticed that the .gitlab.ci.yml destination folder is public, so I did the same in _config.yml.

But I did it in commit c1cce8dc, and the deployment broke before this edit, on commit b3dc2266

Is it possible for me to see the deployment logs on Cloudflare?

![image](/uploads/b07a8af71659a685c105380122ac47d8/image.png) I noticed that the .gitlab.ci.yml destination folder is `public`, so I did the same in `_config.yml`. But I did it in commit c1cce8dc, and the deployment broke before this edit, on commit b3dc2266 Is it possible for me to see the deployment logs on Cloudflare?

emacsen commented

2022-06-07 16:44:41 +00:00

(Migrated from gitlab.com)

I've changed the Cloudflare build process so it uses public for its artifacts too.

The thing is that you said it was something at CF that changed, but it was actually this change that broke the builds.

Anyway, now the site builds again and we can get to the fixes on the visual side.

I've changed the Cloudflare build process so it uses public for its artifacts too. The thing is that you said it was something at CF that changed, but it was actually this change that broke the builds. Anyway, now the site builds again and we can get to the fixes on the visual side.

emacsen (Migrated from gitlab.com) closed this issue

2022-06-07 16:44:42 +00:00