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

[tnikolova82]

Summary

Fixes continued failures in build #23+ where the nodejs multibuildpack test still fails with failed to start: exit status 1 even after PR #1178 (Eventually timeout fix) was merged.

Problem Analysis

The Two-Layer Timeout Issue

Build #23 shows that PR #1178 fixed only one layer of the timeout problem:

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: Still using CF default of 60s - THIS PR FIXES THIS

What's Actually Failing

The error failed to start: exit status 1 comes from:

vendor/github.com/cloudfoundry/switchblade/internal/cloudfoundry/stage.go:47
return "", fmt.Errorf("failed to start: %w\n\nOutput:\n%s", err, logs)

This happens when the cf start <appname> command fails, which occurs before the test's Eventually checks even run.

Timeline

Step	Duration	Status
1. cf push (staging)	4-5 minutes	✅ Succeeds
2. cf start (boot app)	>60 seconds	❌ CF TIMES OUT HERE
3. Test Eventually checks	90s available	⏸️ Never reached

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 kills the app before it finishes starting.

Solution

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

---
applications:
- name: ((name))
  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
• name: ((name)): Template variable filled by switchblade

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.

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 characteristics
• Modified default timeouts or health check behavior
• Affected resource allocation under parallel load

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:

• ✅ 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 start waits up to 180s for app boot ✅ Fixed by this PR
3. App successfully starts and binds port ✅ Should succeed now
4. Test Eventually checks pass (90s available) ✅ PR Fix multibuildpack integration test timeouts (builds #19-22 failures) #1178
5. Test succeeds ✅✅✅

Verification

To verify this fix works:

1. Check that build Can't push new app with ruby-buildpack v1.1.3 #24 uses this commit
2. Monitor cf start command in logs - should succeed instead of timing out
3. Test should reach the Eventually checks (not fail during deployment)
4. Overall test should pass

Related

• Fixes: Build Can not run the tests #23 failure
• 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 same issue)
• CF Docs: App Manifest Attributes - timeout