[SPARK-56415][INFRA] Simplify create_spark_jira.py for LLM-driven JIRA ticket creation#55281
[SPARK-56415][INFRA] Simplify create_spark_jira.py for LLM-driven JIRA ticket creation#55281cloud-fan wants to merge 9 commits intoapache:masterfrom
Conversation
…A ticket creation Co-authored-by: Isaac
- Remove CLI version flag; auto-detect latest unreleased version instead - Split preflight into check_jira_access() and detect_affected_version() - Hint in AGENTS.md to review versions after ticket creation Co-authored-by: Isaac
…ssues only Co-authored-by: Isaac
There was a problem hiding this comment.
I can add back the old script if people still need it, but with a different name, as create_spark_jira.py should only create ticket.
Co-authored-by: Isaac
Co-authored-by: Isaac
Co-authored-by: Isaac
|
Thank you for pinging me. Let me try today. |
|
|
||
| parser = argparse.ArgumentParser(description="Create a Spark JIRA issue.") | ||
| parser.add_argument("title", nargs="?", help="Title of the JIRA issue") | ||
| parser.add_argument("-p", "--parent", help="Parent JIRA ID for subtasks") |
There was a problem hiding this comment.
I'm alway using this parent JIRA ID feature. Please recover this, @cloud-fan .
Co-authored-by: Isaac
…xclusive Co-authored-by: Isaac
Co-authored-by: Isaac
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
There was a problem hiding this comment.
I've been considering this improvement. It would be great to preserve all existing features because it's a fallback for non-LLM-installed environment or users, @cloud-fan .
I can add back the old script if people still need it, but with a different name, as create_spark_jira.py should only create ticket.
In addition, it would be great if we can keep the existing file name because create_spark_jira.py is used conventionally by multiple committers across multiple Spark sub-projects already.
- https://github.com/apache/spark/blob/master/dev/create_spark_jira.py
- https://github.com/apache/spark-kubernetes-operator/blob/main/dev/create_spark_jira.py
- https://github.com/apache/spark-connect-swift/blob/main/dev/create_spark_jira.py
It's the same for merge_spark_pr.py:
- https://github.com/apache/spark/blob/master/dev/merge_spark_pr.py
- https://github.com/apache/spark-kubernetes-operator/blob/main/dev/merge_spark_pr.py
- https://github.com/apache/spark-connect-swift/blob/main/dev/merge_spark_pr.py
This PR had better narrow down toward teaching LLMs to skip some existing human-oriented features which is not required for LLM-environment.
|
I'm fine to create a new script for this llm use case dedicatedly. But I'm confused about the naming suggestion. This simply creates Spark JIRA ticket but we can't name it |
2 participants
What changes were proposed in this pull request?
Simplifies
dev/create_spark_jira.pyto focus on JIRA ticket creation only, making it suitable for use by LLM agents. Also updatesAGENTS.mdwith instructions for automated ticket creation.Changes to the script:
create_and_checkout_branch(),create_commit(),run_cmd(), and interactivechoose_components()— the script now only creates a JIRA ticket and prints the ticket key.-c(component) required instead of falling back to an interactive prompt.--list-componentsflag to query valid component names from JIRA.jiralibrary orJIRA_ACCESS_TOKENis missing, the script prints a helpful message directing the user to create the ticket manually, instead of a raw error.Changes to
AGENTS.md:Why are the changes needed?
Previously,
AGENTS.mdtold LLM agents to ask the user to create JIRA tickets manually. Thecreate_spark_jira.pyscript existed but included interactive prompts and git side effects (branch creation, committing) that made it unsuitable for automated use. This change makes the script LLM-friendly so agents can create tickets as part of the PR workflow.Does this PR introduce any user-facing change?
No. The script's CLI interface is simplified but the core JIRA creation functionality is preserved.
How was this patch tested?
#55280 was created with this new prompt.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code