pipeline

Automate remote Java and frontend deployments with status checks via SSH.

Updated Jun 19, 2020
One-click install
npx skills add https://github.com/xixiU/yu_config --skill pipeline-xixiu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/xixiU/yu_config/tree/main/claude/skills/pipeline
Command: npx skills add https://github.com/xixiU/yu_config --skill pipeline-xixiu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates remote application deployment and status checks over SSH, enabling reliable management of Java backends and frontend assets across multiple environments.

Core Features & Use Cases

  • Automates deploy (redeploy) and status checks for remote Java (Maven + jar) and frontend (Node build + Nginx) deployments.
  • Supports env/app inference, config-driven environments, and restart flow with optional JAVA_HOME injection.
  • Ideal for teams needing repeatable deployment workflows across multiple servers with minimal manual setup.

Quick Start

Redeploy the target application in the current project directory or specify env and app to control deployment.

Frequently Asked Questions about pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate remote Java application deployment over SSH?

Automating remote Java application deployment over SSH is handled by triggering a redeploy flow that builds Maven jar packages locally and transfers them to the target environment. The pipeline restarts the remote application using configurable restart scripts with optional JAVA_HOME injection.

Can I deploy frontend assets built with Node to a remote Nginx server?

Deploying frontend assets built with Node to a remote Nginx server is supported through the pipeline's automated deployment flow. It executes Node-based frontend builds and deploys the resulting assets to the configured remote environments.

How do I check the status of a remote application after deployment?

Checking the status of a remote application after deployment is performed via SSH status checks. The pipeline automates these status checks across configured environments to verify that the Java backend or frontend assets are running correctly.

Do I need to manually specify the environment and app name for each deployment?

Manually specifying the environment and app name for each deployment is not strictly required. The pipeline supports env/app inference and config-driven environments, allowing you to initiate redeployments from the current project directory with optional explicit overrides.

What is the best way to manage repeatable deployments across multiple servers?

Managing repeatable deployments across multiple servers is achieved using config-driven environments within the pipeline. This approach automates Maven and Node builds alongside remote SSH redeploys, minimizing manual setup and ensuring consistent application state across servers.

Why does my remote Java backend fail to restart after a jar deployment?

A remote Java backend failing to restart after a jar deployment is often due to incorrect JAVA_HOME configuration. The pipeline addresses this by supporting optional JAVA_HOME injection directly into the restart scripts during the automated remote redeploy flow.