I'm using gcloud's 'Source Repository' to link to a GitHub repo to trigger automated container builds. Unfortunately the Source Code shown in gcloud seems to get out of sync with the GitHub Repo. The example below shows that gcloud is missing the last 7 commits.
This seems to be fixed by removing the code from Google 'Source Repository' and relinking to GitHub but this is a major annoyance. This has happened several times to several different repos over the past couple of months.
Any idea what is causing this and if there is any fix?
Seeing this issue today, anyone else experiencing this? There's no service status for cloud repos or github sync so hard to tell, but all my repositories stay in a constant state of "Syncing"
Related
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 setup a local Jekyll site that is configured to deploy to Github pages. I used the "Chirpy" theme (see https://github.com/cotes2020/jekyll-theme-chirpy) and followed the instructions successfully to get it to deploy the first time.
I am trying to get my 2nd commit w/ updates to deploy but the process is failing when the Github action runs. I see this output:
This is my first attempt at any of this so don't have any perspective on what is going on w/ any of these technologies.
Thanks for any help and LMK what else might make things clearer!
It seems like after you run test.sh, you tried to switch branches. I suspect that is the problem because it doesn't appear that you tried to git reset or anything like that. I believe your test.sh ran (see these lines) so there are unstaged changes.
If you don't want those changes, you might try a git stash to easily reset. Just a thought.
So the issue was that I checked in the _site and .jekyll-cache directories. Here is the proper .gitignore entries to have the standard gh-pages branch build w/o this problem.
https://github.com/github/gitignore/blob/master/Jekyll.gitignore
This has been asked before, but none of the answers seem to help. I'm using Git Pages to publish materials for a course, and the Github app to push the changes. I'm creating the website in RStudio (Index file is an .Rmd file which saves to index.html). This was working fine until today, when it suddenly stopped. None of my changes are being updated to git pages website (ending 'github.io', even though the changes are being successfully pushed to the Github Repo. None of the Github pages options has changed (index.html is saved in master/docs). There is only one branch (the 'master'), as this is a single author project. I've tried in multiple browsers. Any pointers greatly welcome!
This is because GitHub is down all over the world.
Please find the latest status at https://status.github.com/messages and try again when the issues are resolved.
I have configured a multibranch pipeline job in Jenkins linked to our GitHub repo which is working nicely, feeding back the status of checks to the pull request in our GitHub so we know if the branch is good for merging in.
What I don't see are any open pull requests listed against the Job in Jenkins:
We also have the Blue Ocean plugin in installed and no PR's are shown there either.
Anyone know why this is the case? Am I missing another plugin\config?
I had this issue as well. I tried what joey suggested, but that did not work. I found out that if you add PR-.+ (or PR-* as a wildcard) to your regex filter for branches to include, the pull requests "magically" appear. The documentation of this was found here. It's very frustrating that the "official" documentation for this plugin does not explain this (at least from what sparse documentation I could find). The configuration for my project, which works, is here:
I'm not sure if this is a recommended way to use this plugin for this use case, but Jenkins never seems to have ample documentation.
I was getting the same issue. But this time within Blue Ocean UI as shown below
The fix was to switch from using Git to GitHub Branch Source at the job level and configure GitHub Branch Source. The job type was Multibranch pipeline.
One possible cause could be that GitHub is unable to connect to Jenkins directly due to a firewall. This is likely the case if GitHub never reports the status check as completed, in other words, it hangs forever.
In this case, polling is an easy solution. Go to http://_jenkins_ip_:8080/job/_job_name_/configure and select the "Scan Repository Triggers" tab. Tick the "Periodically if not otherwise run" checkbox and select an interval. I have 15 minutes on mine.
The first time this is done, there should be an immediate scan and it should detect the pull request, otherwise, there might be something else going on. Check the "Scan Repository Log" page on the job, as it might have useful info.
By the way, I did not install the "GitHub Pull Request Builder Plugin" as the page says that it has a security issue. Instead, the "GitHub Branch Source Plugin" is being used. Some other related plugins installed:
Git client plugin
Git plugin
GitHub API Plugin
GitHub Authentication plugin
GitHub Integration Plugin
GitHub plugin
I'm also using Blue Ocean, but this is not required, it simply provides a different UI.
I know that this is an old topic, but I had the same issue while I was trying to visualize my Pull Requests from Bitbucket and I hope this answer will help other people in need. In my case, I was using Bitbucket Push and Pull Request Plugin, which is pretty similar to other GitHub Plugins for Jenkins.
My problem came from the fact that I selected Git instead of Bitbucket in Branch Sources >> Add Source section. I suspect the same thing happened in this case, where the two options Git and GitHub are even easier to confuse.
I'm very new to github and I started using it a few weeks ago for my uni group project.
The problem that I'm having is:
There is a remote repo on github where everyone in the group is using.
I do have a local repo on my laptop, where I've worked my part of the project.
I recently committed and synced the updates that I made to github using desktop app for mac.
I got a few errors and the sync failed.
After that when I looked at the files that I have locally, they got overwritten by the ones from the git(non-updated version) and all of my work are gone.
Can you please help me on what I should do to receive the files that I had locally? Is there any way that I can undo that last sync. I found a few suggestions online, but since I'm not sure which one to use, I don't really want to mess up the files anymore.
Thanks
(Nearly) All changes made to git repositories can be undo. We don't know the commands you entered but enter it at Google for a specific solution.
You proberly have to use something like:
$git rebase