No description
- Shell 75.1%
- Python 11.4%
- R 6%
- Makefile 3%
- Just 1.7%
- Other 2.8%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
pat-s
637a321bccFollow-up to #11, which landed the trigger-form handling but not the rest. Three things still stood between FORCE_REBUILD and an actual republish. Declare FORCE_REBUILD as a top-level variable so the UI offers it as a dropdown on a manual run, rather than requiring a hand-typed key. Test the value rather than emptiness. A declared variable substitutes its default, so the `[ -n ... ]` check from #11 would have seen the literal string "false" and rebuilt every platform on every cron run. Set overwrite: true on the upload. plugin-s3 skips an object that already exists when overwrite is false, logging "File already exists, skipping upload" and still exiting green, so a forced rebuild would have recompiled every package and published none of them. Normal runs are unaffected, since dedup means only not-yet-published versions are ever built. Also drop the Net debug step, the commented-out Pull upstream step and a stray `# docker info`. The MTU workaround the debug step was diagnosing stays, as does the commented-out alpine-320 matrix entry, which records a deliberately disabled platform rather than dead scaffolding. |
||
| .crow | ||
| .github | ||
| builder | ||
| jenkins | ||
| test | ||
| .gitignore | ||
| build.sh | ||
| CLAUDE.md | ||
| deploy.Jenkinsfile | ||
| handler.py | ||
| install.sh | ||
| Jenkinsfile | ||
| Justfile | ||
| LICENSE | ||
| Makefile | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| renovate.json | ||
| requirements.txt | ||
| serverless-resources.yml | ||
| serverless-stepf.yml | ||
| serverless.yml | ||
r-builds
Builds R interpreter binaries for Linux.
- No changes to upstream code (rstudio/r-builds) is made
- Binaries are only built if they do not yet exist in the S3 bucket