Skip to content

CASSANALYTICS-198: Add publish script and workflow - #245

Merged
bbotella merged 2 commits into
apache:trunkfrom
bbotella:CASSANALYTICS-198
Sep 18, 2026
Merged

bbotella merged 2 commits into
apache:trunkfrom
bbotella:CASSANALYTICS-198

Conversation

@bbotella

Copy link
Copy Markdown
Contributor

CASSANALYTICS-198

Adds cancels

Remove comments

Remove comments
@jyothsnakonisa

Copy link
Copy Markdown
Contributor

Thanks @bbotella for the patch, does each snapshot publishing after a commit overrides existing artifact for that version in the repository or does it create a new artifact?

@bbotella

Copy link
Copy Markdown
Contributor Author

The only thing that should be overwritten is the -SNAPSHOT pointer, but the artifact itself will not be overwritten. That should allow others to point to snapshot artifact and always get the latest commit to trunk.

@jyothsnakonisa

Copy link
Copy Markdown
Contributor

Since each commit creates a new artifact, I am wondering if it creates any storage space issues in the artifactory

@bbotella

Copy link
Copy Markdown
Contributor Author

I've seen a similar pattern on other Apache projects. We can start with this and fix it if it becomes an issue

@michaelsembwever

Copy link
Copy Markdown
Member

you can use SNAPSHOT or the timestamped snapshot version.

I am wondering if it creates any storage space issues in the artifactory

we will get pinged if it becomes a problem

Comment thread CHANGES.txt Outdated
@@ -1,5 +1,6 @@
0.5.0
-----
* Publish a snapshot artifact for every trunk commit (CASSANALYTICS-198)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

nit: this isn't user-facing and shouldn't be in CHANGES.txt

@bbotella
bbotella merged commit 03040d2 into apache:trunk Sep 18, 2026
24 of 26 checks passed
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.

3 participants