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

Artifacts suddenly no longer available #5741

Closed
Stephan202 opened this issue Jul 16, 2023 · 6 comments
Closed

Artifacts suddenly no longer available #5741

Stephan202 opened this issue Jul 16, 2023 · 6 comments
Labels
stale

Comments

@Stephan202
Copy link

Two artifacts (and maybe others...) produced by this build are suddenly no longer available, yielding HTTP 404 responses:

This happened recently: the GitHub actions build for this commit still passed (meaning the artifacts were still available), build new builds such as for this PR fail.

Can these files (and any others that may be missing) be reinstated somehow? The build is too old to be retriggered, so I don't see how we can fix this without your help.
@Stephan202 Stephan202 changed the title Artifact suddenly no longer available Artifacts suddenly no longer available Jul 16, 2023
@Stephan202 Stephan202 mentioned this issue Jul 16, 2023
Merged
1 task
Stephan202 added a commit to PicnicSupermarket/error-prone that referenced this issue Jul 18, 2023
@Stephan202
Create new tag to work around jitpack/jitpack.io#5741
aca511d
Stephan202 added a commit to PicnicSupermarket/error-prone-support that referenced this issue Jul 19, 2023
@Stephan202
Upgrade Error Prone fork v2.20.0-picnic-1 -> v2.20.0-picnic-2
2086e2d 
This new release is a workaround for jitpack/jitpack.io#5741.

See PicnicSupermarket/error-prone@v2.20.0-picnic-1...v2.20.0-picnic-2
Stephan202 added a commit to PicnicSupermarket/error-prone-support that referenced this issue Jul 19, 2023
@Stephan202
Upgrade Error Prone fork v2.20.0-picnic-1 -> v2.20.0-picnic-2 (#725)
38554be 
This new release is a workaround for jitpack/jitpack.io#5741.

See PicnicSupermarket/error-prone@v2.20.0-picnic-1...v2.20.0-picnic-2
@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Aug 16, 2023
@Stephan202
Copy link
Author

We have since worked around this issue, simply by tagging a new empty commit. But the issue described here still indicates a bug; would be good to better understand it.

@github-actions github-actions bot removed the stale label Aug 17, 2023
@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Sep 16, 2023
@github-actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@miarevalo10 miarevalo10 mentioned this issue Nov 2, 2023
Closed
@Stephan202
Copy link
Author

This happened again for a number of resources, such as this one.

@Stephan202
Copy link
Author

Happened again, e.g. with this reference.

@jitpack-io we really appreciate the free service you provide for open source software. Anything we can do to make this service more robust?

@Stephan202 Stephan202 mentioned this issue Oct 13, 2024
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Stephan202