Skip to content

CI: add build-args#36947

Merged
sagudev merged 1 commit intoservo:mainfrom
sagudev:build_args_ci
May 12, 2025
Merged

CI: add build-args#36947
sagudev merged 1 commit intoservo:mainfrom
sagudev:build_args_ci

Conversation

@sagudev
Copy link
Member

@sagudev sagudev commented May 10, 2025

Add build-args input in CI and try_parser job definition so we can pass own build args to ./mach build

Testing: There are tests for try parser and I tested CI in my fork.
Fixes: partial fix #36823

Signed-off-by: sagudev <16504129+sagudev@users.noreply.github.com>
@sagudev sagudev marked this pull request as ready for review May 10, 2025 07:41
@sagudev sagudev requested a review from mrobinson May 10, 2025 07:41
- name: Build (${{ inputs.profile }})
run: |
./mach build --use-crown --locked --${{ inputs.profile }}
./mach build --use-crown --locked --${{ inputs.profile }} ${{ inputs.build-args }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where are the build args going to come from? Are they just going to be statically defined in the workflows and this is just setting up the interesting for that? Im concerned about the risk of template injection here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

like all inputs, they will come from workflow call which populates args based on try_parser.py output. No injection should be possible (at least from non servo org members). But if it is possible it's already possible via other inputs (here it would be possible to abuse profile to get functionality of build-args).

@sagudev sagudev added this pull request to the merge queue May 12, 2025
Merged via the queue into servo:main with commit c0339dd May 12, 2025
23 checks passed
@sagudev sagudev deleted the build_args_ci branch May 12, 2025 08:11
@sagudev sagudev self-assigned this Aug 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support running vello in CI

3 participants