frappe / frappe/press

[Enhancement]: Do all pre-build validations and show them upfront for deploys

Open
#4,864 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
562
Forks
410
Avg merge
22h 15m
Merged PRs (30d)
197

Description

### Affected Area

Dashboard/UI

### Problem Statement

When I tried to update a bench group that had an outdated node and Python dependency, it threw an error for one of them per deploy (as we throw an exception once we find a validation is false).

Maybe do all validations and send them as a batch to show them on the frontend?

Had to do 2 deploys to realise I had 2 different issues

Image

Image

### Proposed Solution

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the deploy pre-build validation flow in the Dashboard/UI area, focusing on where node and Python dependency checks are surfaced. Determine how multiple failed validations are currently stopped and reported. Done means a deploy reports all relevant validation failures together upfront instead of requiring separate deploys.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cloud, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.