I am using the amazing plugin sbt-ci-release but I think I am doing something wrong. I posted the whole details of all my experimentation and steps and attempt as an issue in their repo which can be find here.
To do it short, when travis is calling +publishSigned it is yelling about
java.lang.IllegalStateException: No staging repository is found. Run publishSigned first
When I tried to manually create a staging folder, it succeed without exception but did not deploy any binary and deleted the folder.
I am not sure what to try next.
Thanks.
The issue was that my branch tag was 0.1 instead of v0.1 , adding the heading v solve the problem.
See https://github.com/olafurpg/sbt-ci-release/issues/44#issuecomment-503087541
Related
I have a blog project in production. If I check the deployment source under output tab, some files are missing in pages folder. It shows "no output files."
This is not affecting surfing the blog, everything works fine. The build log is perfect as well, no errors or warnings. What I realized is that all the missing pages in the Vercel output folder can't be crawled by search engines, so they suffer SEO.
Vercel is picking the files from my git commit so it's automatic once I commit to main. The deployment settings wasn't tampered with so it's the default for a NextJS project as set by Vercel, and the build log shows that all these missing files were successfully generated.
I've searched everywhere online, I saw someone with similar problem on one blog like that but no solution to it yet. I contacted Vercel, they said maybe it's NextJS specific issue which I strongly doubt, still no solution provided.
I wonder why pages will be successfully generated yet they won't appear in the Vercel output folder.
After days of no solution, I opened another complaint with Vercel and another agent was assigned to me. I was told that the 'missing files' in Source folder is not missing exactly, but there was a bug in their File Tree component. I can confirm now that the files are now visible in in Vercel source folder, perhaps, this bug has been attended to.
EDIT
After another commit, the No source files error still showed but got fixed after re-deploying the commit from Vercel.
I've been using Google Cloud Build with GitHub triggers without issue for a while now; all of a sudden today, something changed. Somehow the hashes that are showing up in Cloud Build do not correspond to any commits in any of my repositories...
I've tried searching for documentation, or other folks who've encountered this problem, but found nothing. I uninstalled and reinstalled the GitHub app to no avail.
Has anyone encountered this, and if so, how do you fix it?
EDIT
I found a workaround, looks like builds can be manually run
Notice in the build history, the manual run has found a real commit, whereas the build triggered by a push to GitHub is coming up with bogus commits...
Check if the issue persists (especially after you trigger a manual run and find back normal existing SHA).
There was an incident affecting Cloud Tasks scheduler jobs which might have a side-effect on your build status. Considering the incident is resolved, you should not see such an issue again.
The OP quickshiftin confirms in the comments it was more a GitHub issue than a Google Cloud one:
[It] looks like that incident was in us-central1, my servers are in us-west1.
Also, I got a response from a GitHub ticket I filed, where they said it appears to relate to changes they made "very recently" and reverted last night.
As of this morning, the build is working again (nothing changed on my side). >
Presumably the issue was from either Google or GitHub.
I don't know if it's related to this issue, git tag generates an another ref id than the commit id when created with a comment (git tag -a YOUR_TAG -m YOUR_COMMENT), so the following command results may have been displayed.
git show-ref --abbrev=7 --hash refs/tags/YOUR_TAG
or
git rev-parse --short refs/tags/YOUR_TAG
I have been trying to push my first project to github, but no success whatsoever. I have two errors:
When I specify the path of the folder (cd Desktop/folder), I get yhe message:no path found. The name is correct, so how can I overcome this? Also,I am not sure how critical this error is.
Following the steps in the github tutorial on the freecodecamp website, after push command I get the error: everything is up to date but,in fact, no changes are done to the repository and nothing is uploaded.
I appreciate clear answers because I am not too technical myself and this is my first project to upload.
Many thanks!
please find below link which will help you from the very beginning how all process done you will know through conceptually
https://product.hubspot.com/blog/git-and-github-tutorial-for-beginners
I've multiple projects configured exactly the same way using the same VCS root. All that changes for the projects is the project name, so to keep things DRY I share the root with the following fetch url:
git#github.com:<myorg>/%conf.GitProjectName%.git
For one single project this fails with:
List remote refs failed: cannot locate repository at git#github.com:<myorg>/<My project>.git: ERROR: Repository not found.
This is really weird and I can clone the git repo using git#github.com:<myorg>/<My project>.git without any problem. Any idea about how to debug this?
This was not due to teamcity, it was because of github's new way to give teams rights to a repository which wasn't there before I think. Didn't delete the question to help other that might have the problem.
I've failed to add two or more github reps to teamcity using the same private key. I've generated another private/public pair, added public key to github for new repo, then added private key into teamcity. This worked for me. Hope it helps.
[SOLVED] Somehow, I managed to not have "write" permissions to the .git directory. So was trying to write the commit and getting bounced.
I've been using Eclipse for a few months, but had been just running git from the CLI. I decided that was inefficient and that I wanted to use eGit, so I started following this tutorial (http://www.slideshare.net/loianeg/using-the-egit-eclipse-plugin-with-git-hub-2578587?from=embed).
I'm trying to add an existing project, so I did Team-->Share Project-->Git and selected the .git corresponding to my project. Eclipse seems to have picked it up, okay, but when I try to commit, I get a popup saying
"Committing changes has encountered a problem' -- an internal error occured.
When I click details, it say "An internal error occurred
Exception caught during execution of commit command"
...I don't even know where to start on this one. I googled the error and didn't get anything useful.
Anyone know how to fix this, or at least how to start debugging?
I've solved my case removing index.lock file from the git folder of the project.
start debugging?
Check the "Errors" Eclipse view for a full Stack Trace associate with that error message
Example of an Error View:
fix it?
If the Exception is a NPE one (NullPointerException), like shown in bug 329611, then you can try a git commit -m "a message" in a shell, in order to get past that initial first commit with a GUI.
As the OP rogueleaderr mentions, the error view and the exact stack trace behind the exception was enough:
Somehow, I managed to not have "write" permissions to the .git directory.
So was trying to write the commit and getting bounced.
I face this problem too, Error tab doesn't show anything more.
So I use GitExtension to commit instead, problem solved.
Using parallel eGit and GitExtension to keep tracking a local git repo is a good idea. It's update runtime on both Eclipse and GitExtension when we make change on each.
I faced this problem. I delete the .git folder and .gitignore file push to upstream it works correctly.
I had this same issue. I resolved it by committing manually from terminal using (in this order):
git add . then git commit and lastly, git push from the local repo directory.
I faced similar problem, It was resolved after deleting index.lock file in .git\ folder.