CommunityRule/community-rule
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update ci.yaml
CI Pipeline / test (20) (pull_request) Successful in 5m17s
Details
CI Pipeline / test (18) (pull_request) Successful in 6m36s
Details
CI Pipeline / e2e (chromium) (pull_request) Failing after 4m48s
Details
CI Pipeline / e2e (firefox) (pull_request) Failing after 3m40s
Details
CI Pipeline / performance (pull_request) Has been cancelled
Details
CI Pipeline / storybook (pull_request) Has been cancelled
Details
CI Pipeline / lint (pull_request) Has been cancelled
Details
CI Pipeline / build (pull_request) Has been cancelled
Details
CI Pipeline / e2e (webkit) (pull_request) Has been cancelled
Details
CI Pipeline / visual-regression (pull_request) Has been cancelled
Details

Browse Source
This commit is contained in:
adilallo
2025-09-02 21:28:32 -06:00
parent e071449ce9
commit 1253779c00
1 changed files with 30 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/ci.yaml
+30 -3
View File
@@ -64,7 +64,16 @@ jobs:
# start and detach with logs
mkdir -p .next
# Use production server with enhanced stability for CI
nohup npm run start -- -p "$PORT" -H "$HOST" > .next/runner.log 2>&1 &
# Start server in background but keep it alive with proper signal handling
(
# Create a new process group to isolate from CI cleanup
setsid bash -c '
# Set up signal handlers to prevent premature termination
trap "echo \"🛑 Received signal, shutting down gracefully...\"; exit 0" TERM INT
# Start the server
npm run start -- -p "'$PORT'" -H "'$HOST'" 2>&1 | tee .next/runner.log
' &
) &
echo $! > .next/runner.pid
echo "🌐 PID $(cat .next/runner.pid) listening on http://$HOST:$PORT"
@@ -212,7 +221,16 @@ jobs:
test -d .next || { echo "❌ Missing .next build output"; exit 1; }
mkdir -p .next
# Use production server with enhanced stability for CI
nohup npm run start -- -p "$PORT" -H "$HOST" > .next/runner.log 2>&1 &
# Start server in background but keep it alive with proper signal handling
(
# Create a new process group to isolate from CI cleanup
setsid bash -c '
# Set up signal handlers to prevent premature termination
trap "echo \"🛑 Received signal, shutting down gracefully...\"; exit 0" TERM INT
# Start the server
npm run start -- -p "'$PORT'" -H "'$HOST'" 2>&1 | tee .next/runner.log
' &
) &
echo $! > .next/runner.pid
echo "🌐 PID $(cat .next/runner.pid) listening on http://$HOST:$PORT"
@@ -312,7 +330,16 @@ jobs:
test -d .next || { echo "❌ Missing .next build output"; exit 1; }
mkdir -p .next
# Use production server with enhanced stability for CI
nohup npm run start -- -p "$PORT" -H "$HOST" > .next/runner.log 2>&1 &
# Start server in background but keep it alive with proper signal handling
(
# Create a new process group to isolate from CI cleanup
setsid bash -c '
# Set up signal handlers to prevent premature termination
trap "echo \"🛑 Received signal, shutting down gracefully...\"; exit 0" TERM INT
# Start the server
npm run start -- -p "'$PORT'" -H "'$HOST'" 2>&1 | tee .next/runner.log
' &
) &
echo $! > .next/runner.pid
echo "🌐 PID $(cat .next/runner.pid) listening on http://$HOST:$PORT"