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.

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

malilib/4fcf40f60b build #6897

Open
sakura-ryoko opened this issue Feb 16, 2025 · 4 comments
Open

malilib/4fcf40f60b build #6897

sakura-ryoko opened this issue Feb 16, 2025 · 4 comments
Labels
build Report a failed build

Comments

@sakura-ryoko
Copy link

sakura-ryoko commented Feb 16, 2025

Please provide:

https://jitpack.io/com/github/sakura-ryoko/malilib/4fcf40f60b/build.log
  • Does the project build on your machine with the same commands as in the log (e.g. gradle install) ?
Yes, of course.  You can see the build.yml runs successfully also.
  • What error are you seeing?
Git error. Retrying.
Git error. Remote branch 'master' not found in upstream origin

I use Jitpack all the time using the same repos over and over, and it suddenly decided to not work. I tried removing Jitpack's Application OAuth, and re-creating it; and no changes. There is no 'master' branch, as the default branch is the 'master'.

@sakura-ryoko sakura-ryoko added the build Report a failed build label Feb 16, 2025
@sakura-ryoko
Copy link
Author

sakura-ryoko commented Feb 16, 2025

New Information:

Apparently your system broke using / in the Repo Branch names; it fails to read it; and then fails to build if there is no master branch because it can't read the branch name.

@jitpack-io
Copy link
Member

Hi

Thank you for reporting this!
That build is now successful and we will be rolling out the fix throughout the day.

Which build with / in branch name is not working for you?

@sakura-ryoko
Copy link
Author

Which build with / in branch name is not working for you?

The one I posted. I have since renamed all of my Repo branches without the / so I could continue working.

@jitpack-io
Copy link
Member

Looks like the / issue was caused by the same bug and should be fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Report a failed build
Projects
None yet
Development

No branches or pull requests

2 participants