▸case-22 I am getting an error when running docker build locally: 'failed to solve: process /bin/sh -c npm install did not complete successfully: exit code 1'. How do I inspect the build logs or run an interactive shell inside a failed container build step? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 We are migrating a .NET 8 Web API service from manual IIS deployments to an automated containerized pipeline deploying to Azure App Service. Generate the pipeline overview, workflow code, environment secrets, and rollback notes. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 We want an automated build pipeline that compiles an Electron desktop app for Linux and Windows on every release tag. Outline the pipeline stages, GitHub Actions workflow file, environment variables, and rollback plan. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 We need a CI/CD pipeline for a Laravel application running in Docker. On PR open, run PHPUnit tests and Pint style checks. On merge to main, deploy to ECS. Provide the pipeline design, workflow file, secrets required, and deployment risk assessment with rollback plan. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 Our team wants to establish a CI/CD pipeline for a Java Spring Boot service built with Maven. We need automated unit testing, SonarQube quality analysis, and deployment to staging. Provide the pipeline plan, workflow file, secret inventory, and risk management notes. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 Our team builds a Flutter mobile app and wants to automate linting, unit testing, and building Android APK artifacts on pull requests. Provide the automation architecture, workflow config, environment requirements, and failure recovery plan. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 We are moving our Kubernetes manifest deployments from local kubectl applies to a CI/CD pipeline targeting development, staging, and production clusters. Provide an automation plan including stage triggers, YAML config, required credentials, and risk mitigations. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 We need a CI/CD workflow for an Elixir Phoenix web service that includes running database migrations safely before updating application instances. Outline the stage pipeline, workflow file content, secrets needed, and rollback steps. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 We have a Serverless Framework application using AWS Lambda and Node.js. We need an automated pipeline triggered on push to main to run tests, deploy to staging, and run integration tests. Generate the workflow specification, configuration file, credentials list, and rollback plan. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 We are building an internal developer portal and need a mockup/layout description for the deployment status dashboard UI, specifically showing component layout, color schemes for status badges, and grid navigation for developers. Can you provide a UI visual layout design? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 We want to automate testing and packaging for a Python machine learning inference API that uses ONNX Runtime. Create a pipeline design with workflow config, required secrets, and deployment risk management. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 We want to automate our Terraform deployment workflow using CI/CD. When PRs are opened, it should run terraform fmt and terraform plan; when merged to main, it should run terraform apply. Provide the full workflow plan, configuration file, secrets list, and rollback notes. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 We want to set up an automated CI/CD pipeline for our Python FastAPI backend service running on AWS ECS. We currently run pytest and flake8 manually before pushing Docker images. Model a full automation workflow including stage summaries, workflow configuration, environment variables, and rollback steps. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 We are setting up CI/CD to replace our manual deployment scripts for a Next.js web app, deploying automatically to staging and requiring manual approval for production. Please generate an automation plan detailing the pipeline stages and triggers, the exact workflow configuration code, the necessary credentials and environment setup, as well as an assessment of risks, assumptions, and rollback steps. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 We want to automate testing and deployment for a Rails application using Docker and GitHub Actions. Currently devs run rspec locally and deploy via SSH scripts. Outline the automated pipeline stages, full workflow definition, secret requirements, and rollback instructions. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 Our repository contains both a React frontend and a Go microservice. Developers currently manually test and build both before creating releases. Create an automated CI/CD design with triggers, workflow files, secrets list, and failure recovery notes. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 We need an automated release pipeline for our Go CLI tool that cross-compiles binaries and drafts GitHub releases when a git tag is pushed. Provide the workflow structure, workflow configuration, environment variable definitions, and rollback strategy. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 We want an automated pipeline that builds a static Hugo site on main pushes and deploys it to Cloudflare Pages, with preview deployments for pull requests. Provide the workflow stage breakdown, config code, required tokens, and rollback strategy. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 We want to fully automate the delivery process for our Node.js microservice whenever code lands on main or a pull request is opened. Can you put together a complete pipeline design for us? Please outline the overall pipeline stages and triggers, provide the GitHub Actions workflow file content, list all required secrets and environment variables, and highlight key deployment risks along with rollback procedures. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 We need a CI/CD pipeline for a Rust microservice that runs cargo test, cargo clippy, builds a container image, and deploys to AWS EKS. Provide the pipeline summary, workflow file, secret definitions, and rollback procedures. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 We build internal Kubernetes Helm charts and want an automated CI workflow that lints charts on pull requests and packages/publishes charts to an OCI registry when tagged. Outline the stage breakdown, workflow code, secrets, and risk handling. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 I am trying to run git push origin main from my terminal, but I get 'error: failed to push some refs ... updates were rejected because the remote contains work that you do not have locally'. What single git command should I run to resolve this push rejection? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |