makiolaj/calendula
1
0
Fork 1
Code Actions Releases 37 Activity
35 Commits 23 Branches 52 Tags
ffc7ed414fc07cb4a1a54c67f38155e0281f8f71
Commit Graph
4 Commits
Author SHA1 Message Date
Jean-Luc MakiolaandClaude Opus 4.7 6ebe8d69e9 ci(cleanup): trim lint+test scope for faster pipelines
CI / ci (push) Successful in 9m1s
Details
Build and Release to F-Droid / ci (push) Successful in 5m21s
Details
Build and Release to F-Droid / build-and-deploy (push) Successful in 7m28s
Details 
- ci.yaml: ./gradlew lint -> lintDebug, test -> testDebugUnitTest.
  Default lint task runs for BOTH debug and release variants which
  doubles the scan work; AGP's lint catalog is identical between
  variants for our scope so debug-only is sufficient. Same for test:
  testDebugUnitTest avoids running release-variant test compilation.

- release.yaml: drop lint step from ci-sanity job. Lint is enforced
  on every push to main via ci.yaml; by the time a tag exists at a
  main commit, lint has already passed. Release-sanity keeps test +
  assembleDebug to catch any tag-resolved drift (e.g. version code
  substitution issues).

Expected CI run time reduction: ~30% (lint accounts for the largest
single block of cold-cache work).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-06-08 17:03:08 +02:00
Jean-Luc MakiolaandClaude Opus 4.7 0508ea9de5 fix(ci): split release.yaml sanity gradle calls to avoid OOM
Build and Release to F-Droid / build-and-deploy (push) Has been cancelled
Details
CI / ci (push) Has been cancelled
Details
Build and Release to F-Droid / ci (push) Has been cancelled
Details 
The release workflow's ci-sanity job ran 'lint test assembleDebug' as
a single gradle invocation, which combined all three phases in one
JVM and exceeded the 2GB heap inside the gitea-actions docker
container ("Gradle build daemon disappeared unexpectedly"). Split
into three separate invocations matching ci.yaml - each gradle call
gets its own fresh 2GB JVM, well under the container's memory ceiling.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-06-08 16:53:30 +02:00
Jean-Luc MakiolaandClaude Opus 4.7 bfa7757d88 ci: add gitea release workflow with F-Droid pipeline 
Triggers on git tags. Runs CI sanity (lint+test+assembleDebug), then
in build-and-deploy job: writes version from tag into app/build.gradle.kts
(versionCode = MAJOR*10000 + MINOR*100 + PATCH, HouseHoldKeaper
convention), drops keystore + key.properties from secrets, runs
assembleRelease, pulls existing F-Droid repo from Hetzner, drops the
new APK + metadata, regenerates index with 'fdroid update -c', and
SCPs the whole tree back to Hetzner.

Required secrets: KEYSTORE_BASE64, KEY_PASSWORD, KEY_ALIAS,
HETZNER_HOST, HETZNER_USER, HETZNER_PASS. Configure these in Gitea
repo settings before pushing the first tag.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-06-08 15:49:01 +02:00
Jean-Luc MakiolaandClaude Opus 4.7 fb7f2ad1f3 ci: add gitea CI workflow (lint, test, assemble, trivy) 
Runs on every push to any branch (tags excluded) and on pull requests.
Installs JDK 17 + Android SDK 36 + 37.0-preview (needed because the
Material 3 Expressive alpha transitively requires compileSdk 37).
Gradle dependency cache keyed on libs.versions.toml. Trivy scan runs
with continue-on-error like HouseHoldKeaper - we report findings but
don't block.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
 2026-06-08 15:46:57 +02:00