Introduction

Jenkins Blue Ocean provides a modern, visual representation of Pipeline stages and their execution status. When Blue Ocean fails to render pipeline stages -- showing blank cards, missing stage names, or incomplete flow diagrams -- developers lose visibility into build progress and failure points. This is often caused by plugin version mismatches, browser compatibility issues, or malformed pipeline syntax.

Symptoms

  • Blue Ocean pipeline view shows empty or blank stage cards
  • Stage names display as undefined or are missing entirely
  • Pipeline runs successfully but Blue Ocean shows no visualization
  • Browser console shows JavaScript errors when loading Blue Ocean
  • Classic Jenkins pipeline view works but Blue Ocean view is broken

Common Causes

  • Blue Ocean plugin version incompatible with the Jenkins core version
  • Pipeline syntax using features not supported by Blue Ocean's stage parser
  • Browser cache serving outdated Blue Ocean JavaScript assets
  • Parallel stages in the pipeline causing rendering layout issues
  • Missing or corrupted Blue Ocean plugin dependencies

Step-by-Step Fix

  1. 1.Check Blue Ocean plugin version compatibility: Verify the plugin is compatible.
  2. 2.`
  3. 3.# Jenkins UI: Manage Jenkins > Manage Plugins > Installed
  4. 4.# Check Blue Ocean version
  5. 5.# Visit https://plugins.jenkins.io/blueocean/ for compatibility info
  6. 6.`
  7. 7.Clear browser cache and hard reload: Eliminate cached asset issues.
  8. 8.`
  9. 9.# In browser: Ctrl+Shift+Delete to clear cache
  10. 10.# Or hard reload: Ctrl+F5 (Windows) / Cmd+Shift+R (Mac)
  11. 11.# Check browser console for errors: F12 > Console
  12. 12.`
  13. 13.Update Blue Ocean and dependent plugins: Ensure all plugins are current.
  14. 14.`
  15. 15.# Jenkins UI: Manage Jenkins > Manage Plugins > Updates
  16. 16.# Update Blue Ocean and all plugins marked as dependent
  17. 17.# Restart Jenkins after updates
  18. 18.`
  19. 19.Simplify pipeline syntax for Blue Ocean compatibility: Fix complex stage definitions.
  20. 20.```groovy
  21. 21.// BEFORE: Complex parallel stages that may confuse Blue Ocean
  22. 22.stage('Build and Test') {
  23. 23.parallel {
  24. 24.stage('Build') { steps { sh 'make' } }
  25. 25.stage('Test') { steps { sh 'make test' } }
  26. 26.}
  27. 27.}

// AFTER: Explicit stage structure stage('Build') { steps { sh 'make' } } stage('Test') { steps { sh 'make test' } } ```

  1. 1.Verify Blue Ocean API endpoint returns valid data: Check the REST API.
  2. 2.```bash
  3. 3.curl -s https://jenkins.example.com/blue/rest/organizations/jenkins/pipelines/my-pipeline/runs/ | jq '.'
  4. 4.# Should return valid JSON with stage information
  5. 5.`

Prevention

  • Keep Blue Ocean plugin updated alongside Jenkins core version
  • Test pipeline visualization in Blue Ocean after adding new stage patterns
  • Use standard Pipeline syntax that is well-supported by Blue Ocean's parser
  • Include Blue Ocean UI verification in CI/CD pipeline acceptance tests
  • Monitor Jenkins plugin compatibility matrix before upgrading any plugin
  • Provide fallback to classic Jenkins UI when Blue Ocean rendering issues occur