mirror of
https://github.com/sourcegraph/sourcegraph.git
synced 2026-02-06 18:51:59 +00:00
* wip * gitserver (mostly) wolfi 4 bazel * the big heck of all things * Add rules_apko lock translation rules to WORKSPACE * Call apko_repositories() more * fix rules_apko to handle our shorter repo urls * fix workspace from rebase, and missing locks * visibility on wolfi_base_image * hand-fix a lock coz apko lock is 🅱️roken * remove chainguard repo+keyring from base * update locks * add chainguard repo+keychain to single server manifest * unrelated fixes, server+grafana still h*cked * fix postgres-exporter * the big fix * aws lib got bumped? * downgrade sso-oidc? idk * ignore wolfi locks from prettier * dynamically do the locks with a reporule * document and make nice :nails: * bazel run @rules_apko//apko patch * Fix .typo.typo * Update tooling for end-to-end Bazel images (#61106) * Update sg wolfi image to build using Bazel * bazel run @rules_apko//apko patch * Fix .typo.typo * Add update-images and implement apko YAML change monitoring * Use bazel apko and add support for additional repos * Refactor sg wolfi * Rework wolfi base image auto-update pipeline * sg bazel configure * [rough] Add --check flag to sg wolfi lock * Refactor sg wolfi lock --check * Simplify check and update apko lock hash operations * Fix resolveImagePath when running in bazel * Fixup logic error in CheckApkoLockHashes * Tweak DoBaseImageBuild output * Remove debug output * Fix sg wolfi lock --check behaviour for all images * Replace base image build step with apko lock --check * Remove debug line * Minor fixups for CI step * Wrap with AnnotatedCmd * Fixup annotation * Update apko lockfiles * Allow additional repos to be passed * Update build-base-image.sh with bazel + add back to pipeline * Ensure that modified base images are rebuilt * Solve bazelception * Remove timestamp for bit-level reproducibility * Skip local keygen when running on buildkite * Add workaround for lack of local repo support in rules_apko * Run apkoOps first as it's quick and might fail * Remove blocking allBaseImagesBuilt step * Remove unused promethus-gcp image * Add special cases to resolveImagePath * Cleanly handle case where no bazel build path exists This could happen in cases where a base image is only used outside of sourcegraph/sourcegraph, or if you've added a new base image config but haven't added the associated Bazel scaffolding * Add debugging around failing docker builds * More debugging * Normalise apko_lockfile to match repo.bzl * Fixup apko docker call * Try passing imageconfigdir differently to docker * Run ls in different container * Soft-fail when using legacy build in Buildkite * Add missing include * Workaround for building sourcegraph and sourcegraph-dev * Add postgresql-client package to server This contains createdb, which was recently moved from postgresql * Inflate postgres-12-codeinsights image to avoid rules_apko errors * Remove update line from yaml files * Fix issue caused by moving base sourcegraph image * Remove apk-tools from server * Update lockfiles * Address review feedback * Remove debug lines * fix unbound var --------- Co-authored-by: Noah Santschi-Cooney <noah@santschi-cooney.ch> * go mod tidy + gazelle-update-repos after merging main * Use aspect bazel cache * Use Aspect bazel caching when calling bazel in bash and sg * Append annotation * Run apko lock on aspect agent * Remove base image builds Discussion in https://sourcegraph.slack.com/archives/C05EVRLQEUR/p1712307465660509 * Remove unused functionality * Update BaseImageConfig comments * Rewrite wolfi-images/README.md * Add .apko/range.sh to .gitattributes * Remove "wolfi" from :base_image and :base_tarball targets * remove allowlist extras from debugging * Tweak user instructions around package testing * Add agent healthcheck to buildkite scripts * prettier * sg bazel configure * bazel run //:gazelle-update-repos --------- Co-authored-by: Noah Santschi-Cooney <noah@santschi-cooney.ch> Co-authored-by: Noah S-C <noah@sourcegraph.com> |
||
|---|---|---|
| .. | ||
| BUILD.bazel | ||
| image_test.yaml | ||
| README.md | ||
Bundled Executor
The bundled executor is a simple executor that runs commands on the container instead of delegating to spawned containers.
The runtime of this executor is shell.
Configuration
Since the bundled executor does not spawn Docker Containers to run Jobs, src cannot be used for Batch Changes. To run
Batch Changes, Native Execution must be enabled.
Native Execution
See Documentation on how to enable Native Execution.
Clean Workspace
To ensure a clean workspace, the executor will exit with code 0 once a Job is complete. It depends on the Platform to
create a new instance when it exits.
Available Commands
batcheshelperxmlstarlet- Python 3
pip- Java 11 (OpenJDK)
- Maven 3.6.3
yq