ci(buildkite): add a repo script for pipeline upload
User description
What was added
.buildkite/upload.sh (git mode 100755). FPC agents run --no-command-eval, so the pipeline-upload step has to be this checked-in script rather than an inline buildkite-agent pipeline upload. The script re-uploads .buildkite/pipeline.yml.
No other files were changed. .buildkite/pipeline.yml and .buildkite/scripts/upload.sh are untouched.
git ls-files -s .buildkite
100644 12294e852eaa2cedc6760df812b5e71b40a49a32 0 .buildkite/README.md
100644 a609fdea6c58fda7eff6f11302395dc1ec3be83d 0 .buildkite/pipeline.yml
100755 6722e8cd1b81338ece91ba50447138c22dd55f0d 0 .buildkite/scripts/governance-enforce.sh
100755 f2185008a535a1693c46031cf71b61989d6927fe 0 .buildkite/scripts/lib/common.sh
100755 e024e80926b30b5a6c788e62349cad2058a6baae 0 .buildkite/scripts/lib/npm-install.sh
100755 0e6f0185ca23f31c45acf002be859e9e7571007f 0 .buildkite/scripts/license-truth.sh
100755 f40f4d6230204bde4581355499d05de39f35a655 0 .buildkite/scripts/smoke.sh
100755 95a61567d19198b419de8ff963a351b7718aefb0 0 .buildkite/scripts/unit.sh
100755 555885e7ae7bd163db78ed3b7e9ba3933ea4d0a7 0 .buildkite/scripts/upload.sh
100755 6d5483c8f4574c06905ae2f27fc63b3ea106d58e 0 .buildkite/upload.sh
Secrets audit (read-only)
.buildkite/pipeline.yml was not modified. Every step inherits the top-level queue fpc-isolated. There is no secrets: block. The only env keys are CI, NPM_CONFIG_AUDIT, NPM_CONFIG_FUND, and NPM_CONFIG_UPDATE_NOTIFIER (all non-secret literals).
No step targets fpc-isolated-secrets or master-pc-isolated, and no step has secrets: or secret env. The if: check (default branch, no pull request, no tag) therefore applies to no step:
| step key | queue | secrets: / secret env | if: limited to default branch, no PR, no tag |
|---|---|---|---|
governance-enforce | fpc-isolated (inherited) | no | n/a — not a secrets step |
unit | fpc-isolated (inherited) | no | n/a — not a secrets step |
smoke | fpc-isolated (inherited) | no | n/a — not a secrets step |
license-truth | fpc-isolated (inherited) | no | n/a — not a secrets step |
Script paths referenced by pipeline.yml
Report only. None are missing, and none are a mode other than 100755:
| path | git mode |
|---|---|
.buildkite/scripts/governance-enforce.sh | 100755 |
.buildkite/scripts/unit.sh | 100755 |
.buildkite/scripts/smoke.sh | 100755 |
.buildkite/scripts/license-truth.sh | 100755 |
The file header comment also names .buildkite/scripts/upload.sh, which is present at 100755. That path is not a step command.
Refs WAVE-28251
CodeAnt-AI Description
Allow pipeline uploads on restricted Buildkite agents
What Changed
- Pipeline uploads can now run on agents that reject inline commands, allowing the repository pipeline to be uploaded again.
Impact
✅ Pipeline uploads work with command evaluation disabled
💡 Usage Guide
Checking Your Pull Request
Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.
Talking to CodeAnt AI
Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:
@codeant-ai ask: Your question here
This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.
Example
@codeant-ai ask: Can you suggest a safer alternative to storing this secret?
Preserve Org Learnings with CodeAnt
You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:
@codeant-ai: Your feedback here
This helps CodeAnt AI learn and adapt to your team's coding style and standards.
Example
@codeant-ai: Do not flag unused imports.
Retrigger review
Ask CodeAnt AI to review the PR again, by typing:
@codeant-ai: review
Check Your Repository Health
To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.