Skip to content

Conversation

@HyukjinKwon
Copy link
Member

@HyukjinKwon HyukjinKwon commented Jan 9, 2026

What changes were proposed in this pull request?

This PR proposes to use ASF_NEXUS_TOKEN to release and drop staging repository when finalizing the RC.
While I am here, I made the commands more portable/universal - in practice, I wanted to use the same commands when I test in my local.

Why are the changes needed?

To automatically release/drop the staging repo.

Does this PR introduce any user-facing change?

No, dev-only.

How was this patch tested?

I manually tested.

Was this patch authored or co-authored using generative AI tooling?

No.

@HyukjinKwon HyukjinKwon changed the title [MINOR][BUILD] Use commands that work for more OS and more portable [MINOR][BUILD] Use commands that work for more OS and more portable in release script Jan 9, 2026
@HyukjinKwon HyukjinKwon marked this pull request as draft January 9, 2026 06:29
@HyukjinKwon HyukjinKwon force-pushed the minor-compat-command branch from 59f3fcc to 297db63 Compare January 9, 2026 06:50
@HyukjinKwon HyukjinKwon changed the title [MINOR][BUILD] Use commands that work for more OS and more portable in release script [SPARK-54982][INFRA] Use ASF_NEXUS_TOKEN to release and drop staging repository when finalizing the RC Jan 9, 2026
@github-actions
Copy link

github-actions bot commented Jan 9, 2026

JIRA Issue Information

=== Bug SPARK-54982 ===
Summary: Automatically release and drop the staging repository
Assignee: None
Status: Open
Affected: ["4.0.1","3.5.7","4.1.1"]


This comment was automatically generated by GitHub Actions

@HyukjinKwon HyukjinKwon marked this pull request as ready for review January 9, 2026 06:54
@HyukjinKwon
Copy link
Member Author

cc @dongjoon-hyun @cloud-fan

Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

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

+1, LGTM.

Are you going to document how to get Nexus token in our website after this PR?

Nice, I saw both PRs and approved.

@HyukjinKwon
Copy link
Member Author

Merged to master, branch-4.1, branch-4.0 and branch-3.5.

HyukjinKwon added a commit that referenced this pull request Jan 9, 2026
…repository when finalizing the RC

### What changes were proposed in this pull request?

This PR proposes to use ASF_NEXUS_TOKEN to release and drop staging repository when finalizing the RC.
While I am here, I made the commands more portable/universal - in practice, I wanted to use the same commands when I test in my local.

### Why are the changes needed?

To automatically release/drop the staging repo.

### Does this PR introduce _any_ user-facing change?

No, dev-only.

### How was this patch tested?

I manually tested.

### Was this patch authored or co-authored using generative AI tooling?

No.

Closes #53744 from HyukjinKwon/minor-compat-command.

Authored-by: Hyukjin Kwon <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>
(cherry picked from commit c26a3e4)
Signed-off-by: Hyukjin Kwon <[email protected]>
HyukjinKwon added a commit that referenced this pull request Jan 9, 2026
…repository when finalizing the RC

This PR proposes to use ASF_NEXUS_TOKEN to release and drop staging repository when finalizing the RC.
While I am here, I made the commands more portable/universal - in practice, I wanted to use the same commands when I test in my local.

To automatically release/drop the staging repo.

No, dev-only.

I manually tested.

No.

Closes #53744 from HyukjinKwon/minor-compat-command.

Authored-by: Hyukjin Kwon <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>
(cherry picked from commit c26a3e4)
Signed-off-by: Hyukjin Kwon <[email protected]>
HyukjinKwon added a commit that referenced this pull request Jan 9, 2026
…repository when finalizing the RC

This PR proposes to use ASF_NEXUS_TOKEN to release and drop staging repository when finalizing the RC.
While I am here, I made the commands more portable/universal - in practice, I wanted to use the same commands when I test in my local.

To automatically release/drop the staging repo.

No, dev-only.

I manually tested.

No.

Closes #53744 from HyukjinKwon/minor-compat-command.

Authored-by: Hyukjin Kwon <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>
HyukjinKwon added a commit to apache/spark-website that referenced this pull request Jan 9, 2026
…finalizing the RC

Per apache/spark#53744

Author: Hyukjin Kwon <[email protected]>

Closes #659 from HyukjinKwon/release-automation.
Yicong-Huang pushed a commit to Yicong-Huang/spark that referenced this pull request Jan 9, 2026
…repository when finalizing the RC

### What changes were proposed in this pull request?

This PR proposes to use ASF_NEXUS_TOKEN to release and drop staging repository when finalizing the RC.
While I am here, I made the commands more portable/universal - in practice, I wanted to use the same commands when I test in my local.

### Why are the changes needed?

To automatically release/drop the staging repo.

### Does this PR introduce _any_ user-facing change?

No, dev-only.

### How was this patch tested?

I manually tested.

### Was this patch authored or co-authored using generative AI tooling?

No.

Closes apache#53744 from HyukjinKwon/minor-compat-command.

Authored-by: Hyukjin Kwon <[email protected]>
Signed-off-by: Hyukjin Kwon <[email protected]>

# Release the repository
curl --retry 10 --retry-all-errors -s -u "$APACHE_USERNAME:$APACHE_PASSWORD" \
curl --retry 10 --retry-all-errors -s -u "$ASF_USERNAME:$ASF_NEXUS_TOKEN" \
Copy link
Member

Choose a reason for hiding this comment

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

Hi, @HyukjinKwon .

For me, ASF_NEXUS_TOKEN has two fields, xxx:yyy (Name Code: Pass Code), style. I'm wondering if you change ASF_USERNAME here with Name Code? Nesus repository shows like the following.

<server>
  <id>${server}</id>
  <username>xxx</username>
  <password>yyy</password>
</server>

Copy link
Member

@dongjoon-hyun dongjoon-hyun Jan 11, 2026

Choose a reason for hiding this comment

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

If we change ASF_USERNAME to Name Code, does the other release process work for you? For example, the following seems to be broken.

dev/create-release/release-build.sh:      echo "From: [email protected]"

Copy link
Member Author

Choose a reason for hiding this comment

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

oh yeah password only

Copy link
Member Author

Choose a reason for hiding this comment

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

username is just username as is

Copy link
Member Author

Choose a reason for hiding this comment

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

I think I should clarify it .. let me open a PR to fix. ASF_USERNAME is username (mine is gurwls223 for example). ASF_NEXUS_TOKEN is yyy at password.

Copy link
Member Author

Choose a reason for hiding this comment

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

btw, I tried it with username combination and it did not work for me. in short,

  • -u xxx:yyy did not work for me
  • -u gurwls223:mypassword did not work.
  • -u gurwls223:yyy worked for me.

Copy link
Member

Choose a reason for hiding this comment

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

Got it. Thank you for clarifying. Let me try Spark 3.5.8 with that style . :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants