Add manifest.yml with increased timeout for Rails72 multibuildpack test fixture

[tnikolova82]

Summary

Fixes continued failures in builds #23-25 where the nodejs multibuildpack test fails with manifest variable substitution errors and app start timeouts.

Problem Analysis

The Two Issues

Build #25 revealed a manifest variable substitution error on top of the timeout issue:

Expected to find variables: name
FAILED

This error occurs because cf push with name: ((name)) expects a variable definition that doesn't exist.

Root Cause

Switchblade provides the app name via command-line arguments (-n flag), not through manifest variable substitution:

// vendor/github.com/cloudfoundry/switchblade/internal/cloudfoundry/setup.go
args = append(args, "-n", appName)  // Name via CLI flag
args = append(args, "-f", filepath.Join(source, "manifest.yml"))  // Manifest used for other settings

The manifest should not specify a name attribute at all.

The Two-Layer Timeout Issue

Even with the variable error fixed, we still need extended timeouts:

1. ✅ Test timeout (Gomega Eventually): Fixed in PR Fix multibuildpack integration test timeouts (builds #19-22 failures) #1178 - extended to 90s
2. ✅ CF app start timeout: Fixed in this PR - extended to 180s via manifest

The Rails 7.2 + Webpacker app takes longer than 60 seconds to boot:

• Rails framework initialization
• Webpacker asset loading
• Database connections
• Multi-buildpack overhead

Cloud Foundry's default 60-second timeout would kill the app before it finishes starting.

Solution

Add manifest.yml to the fixtures/multibuildpack/rails72/ directory:

---
applications:
- memory: 1G
  timeout: 180
  health-check-type: port

Key Settings

• timeout: 180: Allows 3 minutes for app to start (vs default 60s)
• health-check-type: port: CF waits for app to bind its port (default, explicit here)
• memory: 1G: Explicit memory allocation for the heavy Rails app
• NO name attribute: Switchblade provides name via -n flag

How Switchblade Uses This

Verified in the switchblade source code:

// vendor/github.com/cloudfoundry/switchblade/internal/cloudfoundry/setup.go:346-348
_, err = os.Stat(filepath.Join(source, "manifest.yml"))
if err == nil {
    args = append(args, "-f", filepath.Join(source, "manifest.yml"))
}

Switchblade automatically uses manifest.yml if present when running cf push.

Timeline

Build	Status	Issue
#18	✅ Succeeded	Before timeout issues
#19-22	❌ Failed	Insufficient timeouts
#23	❌ Failed	Only test timeout fixed (PR #1178)
#24	🔴 Errored	Docker Hub infrastructure issue
#25	❌ Failed	Manifest variable substitution error

Why This Wasn't Caught Before

Build #18 (Oct 2-3, last success) likely succeeded due to:

• Better CF platform performance on that day
• More available Diego cell resources
• Faster app boot time on that specific run

What changed around Oct 3 (between builds #18 and #19):

• bosh-deployment: 0fa63999 → 9a789787
• cf-deployment-concourse-tasks: f5a26a00 → 6e5a4bfb

These infrastructure updates may have changed Diego cell performance or timeout behaviors.

Precedent

Similar approaches in this codebase:

• JRuby tests use extended timeouts for slow-booting apps
• PR Increase JRuby test polling timeout for cflinuxfs5 stability #1140: Extended test timeouts for JRuby
• PR Fix multibuildpack integration test timeouts (builds #19-22 failures) #1178: Extended Eventually timeouts for all multibuildpack tests
• Commit d5294b6: Extended timeouts for Docker backend racing issues

Heavy apps consistently need more time across the board.

Testing

This fix:

• ✅ Resolves manifest variable substitution error
• ✅ Targets the actual root cause (CF app start timeout)
• ✅ Works together with PR Fix multibuildpack integration test timeouts (builds #19-22 failures) #1178 (test timeout fix)
• ✅ Only affects the rails72 multibuildpack fixture
• ✅ No changes to test code required
• ✅ No impact on other test fixtures
• ✅ Low risk - standard CF manifest pattern

Expected Outcome

After this PR:

1. Rails72 app staging completes (4-5 min) ✅ Already working
2. cf push succeeds without variable errors ✅ Fixed by this PR
3. cf start waits up to 180s for app boot ✅ Fixed by this PR
4. App successfully starts and binds port ✅ Should succeed now
5. Test Eventually checks pass (90s available) ✅ PR Fix multibuildpack integration test timeouts (builds #19-22 failures) #1178
6. Test succeeds ✅✅✅

Verification

To verify this fix works:

1. Check that next build uses this commit
2. Monitor for absence of "Expected to find variables: name" error
3. Monitor cf start command in logs - should succeed instead of timing out
4. Test should reach the Eventually checks (not fail during deployment)
5. Overall test should pass

Related

• Fixes: Build Can not run the tests #23, Added database migrations #25 failures
• Depends on: PR Fix multibuildpack integration test timeouts (builds #19-22 failures) #1178 (Eventually timeout fix - both are needed)
• Related to: builds Gitbot testing continues. #19-22 (all failed with timeout issues)
• CF Docs: App Manifest Attributes - timeout