Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Missing release tgz file in v2.0.4 #900

Closed
chenrui333 opened this issue Apr 19, 2020 · 4 comments
Closed

Missing release tgz file in v2.0.4 #900

chenrui333 opened this issue Apr 19, 2020 · 4 comments
Assignees
@ossarga
Labels
packaging and installation

Comments

@chenrui333
Copy link

chenrui333 commented Apr 19, 2020 •
edited
Loading

The release tgz file (cassandra-reaper-2.0.4.tar.gz ) is missing in the latest release
@adejanovski adejanovski added the new Issues requiring triage label Apr 19, 2020
@chenrui333 chenrui333 changed the title Missing release tgz file in v2.0.5 Missing release tgz file in v2.0.4 Apr 19, 2020
@adejanovski adejanovski added packaging and installation and removed new Issues requiring triage labels Apr 21, 2020
@adejanovski
Copy link
Contributor

The new GHA based release process is definitely not pushing the built packages the the GH release.
We need to check this

@ossarga
Copy link
Contributor

ossarga commented May 11, 2020

We might be able to test this by forking the repo and debugging the fork.

The Apache Cassandra project has a "dry run" mode for the release that prints the commands that will run to execute the release. We may want to add functionality to the Reaper project this when we fix this issue.

ossarga added a commit that referenced this issue May 21, 2020
@ossarga
ISSUE #900: CI config updates
2058481 
* Changed upload action to use builtin GITHUB_TOKEN
ossarga added a commit that referenced this issue May 21, 2020
@ossarga
ISSUE #900: CI config updates
7b09e9a 
* Enabled docker push to repository
ossarga added a commit that referenced this issue May 21, 2020
@ossarga
ISSUE #900: Updated documentation
25a3660 
* Updated and added more details on how to cut a release
* Updated README to show GitHub Actions status badge
ossarga added a commit that referenced this issue May 25, 2020
@ossarga
ISSUE #900: CI config updates
d805c29 
* Changed upload action to use builtin GITHUB_TOKEN
* Enabled docker push to repository
adejanovski pushed a commit that referenced this issue May 26, 2020
@ossarga @adejanovski
ISSUE #900: CI config updates
21a993a 
* Changed upload action to use builtin GITHUB_TOKEN
* Enabled docker push to repository
ossarga added a commit that referenced this issue May 26, 2020
@ossarga
ISSUE #900: Updated documentation
dcd6e58 
* Updated and added more details on how to cut a release
* Updated README to show GitHub Actions status badge
ossarga added a commit that referenced this issue Jun 1, 2020
@ossarga
ISSUE #900: CI config updates
db59386 
* Added release event to CI
@ossarga
Copy link
Contributor

ossarga commented Jun 19, 2020

Fixed the issue that was causing this bug on the 2.0 branch. The fix works as the 2.0.5 release build automatically uploaded the binaries to the GitHub release page

In order to fix the issue with Release 2.0.4, I manually attached the binaries that were in Bintray to the release.

@ossarga ossarga closed this as completed Jun 19, 2020
@rzvoncek
Copy link
Contributor

It looks like this issue is no longer present in a recent build (https://github.com/thelastpickle/cassandra-reaper/actions/runs/140601087). Closing this issue.

adejanovski pushed a commit that referenced this issue Aug 21, 2020
@ossarga @adejanovski
ISSUE #900: CI config updates
29c1560 
* Changed upload action to use builtin GITHUB_TOKEN
* Enabled docker push to repository
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ossarga ossarga

Labels
packaging and installation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@chenrui333 @rzvoncek @adejanovski @ossarga