Website deployment not reflecting changes from main

[tabathad]

Summary

The deployed website at https://git-proxy.finos.org does not reflect the current state of the main branch. Netlify deployments appear to run, but the site content is stale.

Root Cause

The netlify.toml file is missing critical build configuration. It currently only contains an ignore directive:

[build]
  ignore = "git diff --quiet $CACHED_COMMIT_REF $COMMIT_REF . ../website/"

This is missing:

• base — Netlify doesn't know the website source is in website/
• command — Netlify doesn't know to run npm run build (Docusaurus)
• publish — Netlify doesn't know the built output is in website/build/

Without these, Netlify either skips the build entirely (the ignore command succeeds because the paths resolve incorrectly without a base) or has no instructions to actually build and publish the site.

History

The configuration was originally correct (commit 0da90fb):

[build]
  base = "./website"

It was then replaced with the ignore-only approach (commit a1af8e7 and subsequent iterations), which removed base, command, and publish. The build/publish settings may have been configured directly in the Netlify dashboard at some point, but the ignore path ../website/ is relative to the repo root (since no base is set), which likely doesn't resolve correctly.

Proposed Fix

Update netlify.toml to include the full build configuration:

[build]
  base = "website/"
  command = "npm run build"
  publish = "build/"
  ignore = "git diff --quiet $CACHED_COMMIT_REF $COMMIT_REF . ../website/"

Note: publish is relative to base, so build/ resolves to website/build/. The ignore command should also be validated — if base is set to website/, then ../website/ may need adjustment since ignore runs from the base directory.

Verification

After the fix:

1. Push a change to main (even a docs-only change)
2. Confirm Netlify triggers a build (not skipped)
3. Confirm the build succeeds and the site updates
4. Verify https://git-proxy.finos.org reflects the latest content

[tabathad]

@kriswest @jescalada - the netlify deployment preview for #1417 shows the correct version, updated linkedin, docs, and correct titles for maintainers (except for Andy who is added in ##1413)

[kriswest]

I'm not entirely convinced that the netlify.toml file is the cause of the deployment issue. It doesn't look like its changed in 2 years: https://github.com/finos/git-proxy/commits/main/netlify.toml
and we've definitely deployed in that time period.

I suspect the issue actually lies with the config in the netlify platform itself OR there was some problem building the website during the last release or recent merges to main. Previews are definitely building fine (e.g. #1413 https://deploy-preview-1413.git-proxy.preview.finos.org/) so we've probably changed something thats causing an issue.

We'll need to seek help from @TheJuanAndOnly99 or help@finos.org as we don't have access to netlify. @TheJuanAndOnly99 our last release was 14th Jan, although I believe we've been releasing docs on merge to main. The last time that happened successfully would have been between 29th September and 13th December 2025 (which is the period during which the version number was 2.0.0-rc3 as currently shown on the deployed site).

[kriswest]

I've dropped an email to help@finos.org pointing to this issue

[kriswest]

@tabathad I have no idea why, but it just deployed successfully on merge of #1413 !

The previous deployment for your changes failed, but netlify won't tell me why at the moment ():
1:55:05 PM: [ERROR] Deploy logs are currently unavailable. We are working on resolving the issue.

https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/699b9bde4acc9e0008c4b414

[tabathad]

huzzah for the successful deployment! When I clicked through on the previous deployment, it showed me these logs, in case it's helpful for troubleshooting https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/699b9bde4acc9e0008c4b414

7:14:22 PM: Build ready to start
7:14:23 PM: build-image version: 61439bcb1c7da9fe83a0d0117412601aca53908b (noble-new-builds)
7:14:23 PM: buildbot version: 61439bcb1c7da9fe83a0d0117412601aca53908b
7:14:23 PM: Fetching cached dependencies
7:14:23 PM: Failed to fetch cache, continuing with build
7:14:23 PM: Starting to prepare the repo for build
7:14:23 PM: No cached dependencies found. Cloning fresh repo
7:14:23 PM: git clone --filter=blob:none https://github.com/finos/git-proxy
7:14:23 PM: Preparing Git Reference refs/heads/main
7:14:24 PM: Custom publish path detected. Proceeding with the specified path: 'website/build'
7:14:24 PM: Custom ignore command detected. Proceeding with the specified command: 'git diff --quiet $CACHED_COMMIT_REF $COMMIT_REF . ../website/'
7:14:25 PM: Failed during stage 'checking build content for changes': Canceled build due to no content change
7:14:25 PM: User-specified ignore command returned exit code 0. Returning early from build.```

[kriswest]

It is helpful to know you can retrieve them @tabathad - my org probably has the domain blocked (netlify can be used to statically host arbitrary content used for nefarious purposes).

The particular log you quote above is showing that there were no changes to deploy so it cancelled. There can be multiple deployment runs for an PR and PRs might contain no changes to the website, so the ignore config enables it to cancel early to save pointlessly repeating the build.

However the production deploy should only run once, here's one that failed (after your homepage changes): https://app.netlify.com/projects/endearing-brigadeiros-63f9d0/deploys/699b9bde4acc9e0008c4b414

I'd be interested to know why that one failed.