I am using Gerrit2.4.2. My account is an administrator, also in Reviewer and Verifier groups(I created these two groups manually).
In All-Projects, I allow Reviewer group to review /ref/* and Verifier to submit /ref/*.
See my diagram below:
We have a project named as appengine. Also have a group called 'appengine team'. This group has two memebers: another developer and me.
Now another developer added a test file and pushed it to HEAD:refs/for/master. But I didn't get any email notification. After he logged into the Gerrit web site and found his change issue.
And added my email manually, I could see the email notification and also could see the change issue in web site.
My project's settings look like so:
Gerrit doesn't send email notifications when a change is uploaded, unless you are watching that project (Settings->Watched Projects). You will also get an email notification if somebody adds you as a reviewer to a change.
My current way is to use one parameter for receive-pack command. I added to my .git/config file:
[remote "review"]
pushurl = ssh://username#IP:29418/myproject.git
push = HEAD:refs/for/master
receivepack = git receive-pack --reviewer csfreebird
Each time a developer uses git push review, I get an email.
Not perfect, Gerrit server should take the responsibility.
Related
Issue watchers not receiving email notifications on JIRA software : I have watched several issue on our JIRA software, However I am not receiving any email when there is an update going on. What am I missing?
Please check the notification scheme applied to your project. As a project admin, you're capable to see the notification rules. For Jira Server, you can check this link: https://jira_domain/plugins/servlet/project-config/PROJECTKEY/notifications
You might need to check with your Jira administrator to adjust the notification scheme.
Also bear in mind, if you update a Jira issue by yourself, you might not be getting notifications by default. See your Preferences under your profile:
https://jira_domain/secure/ViewProfile.jspa
(My Changes: Do not notify me)
Another potential problem might be watchers' e-mail addresses - are they correct? Is your SMTP server able to send e-mails to these watchers' addresses? Problems might typicallly happen if recipients' e-mail addresses are in different domain and your SMTP is not configured properly to send e-mails to external domains.
I am using tfs 2017. In the alert settings I have configured gmail smtp and when I try send test mail it works, mails are sent to the email address. I have configured notifications and set the delivery settings for the same. But the emails are not getting sent when ever I make any changes in any work item.
Could any one help out to resolve this issue?
First, for on-premises TFS, you must configure an SMTP sever in order for team members to see the Notifications option from their account menu and to receive notifications. Double this setting and make sure your SMTP server worked
According to your screenshot you are trying to manage notifications for a team:
Deliver to Specific team members
Roles Assigned To(New) Assigned
To(Previous ), Previous Assignee, Current Assignee
Make sure your account is applied to those roles for the changed work item.
And in this case,
by default, email notifications will be sent to your preferred email address: xxx#xxx.com. You could check and update your address in your user profile, check if the E-Mail address is the one you would like to use.
Besides, also try to change the Deliver to Team email address and directly input your E-Mail Address. Then test again.
I have a project in TFS. The last two pull requests, we got emails for "xxx has approved the code" but not the subsequent emails for "xxx marked the pull request as completed" The pull requests in question were both approved and completed. The emails do not appear to have been caught in Outlook's spam filter.
The subscription for all projects is "A pull request I created or am a reviewer on is updated"
Version: 15.117.26714.0
Is there a way to diagnose why TFS email notifications are so flaky? This isn't the first complaint I've gotten about TFS email notifications being unreliable.
Have tested TFS 2017.2 instance but could not reproduce the issue on my side. Both approved and completed E-mail sent correctly.
So the issue seems not be able to stable reproduce. For now, there is no way to trouble shoot this directly. You could check the event log in TFS sever to see if you got any error or warning info there.
To narrow down the issue, you could analysis both address the E-mail achieved and sent.
Notifications are sent to your preferred email address, which you can
change from your account preferences. Change the preferred one
and use another to see if issue still exists.
The received notifications are sent by the configured SMTP
server. Try to specify another SMTP Server and the email address
to use for sending emails.
One possibility for this issue, the action of approved and completed pull request were too closely. This may cause TFS only trigger one E-Mail. Do it slowly and try again. Based on my testing, in this case, the E-Mail are sent not in sequence, the completed came first then the approved one.
Moreover, you could also explicitly add a subscription with "A pull request I created or am a reviewer on is updated" just for the project you are working on, which may do the trick.
I have been working on a new TFS 2018 install and I have everything setup with the exception of email notifications. I setup in the admin console the SMTP relay information and when i click test and enter in my email, I get the test notification. Now when i switch to the TFS web console and I create a new work item and assign it to a user the user never gets an email. I have verified that the team notification are on and there is a notification setup for when a work item is assigned. Is there something Im missing, is there a log I need to enable to show if there are errors sending emails out?
any help would be great.
Firstly, please make sure you have created the subscriptions correctly and the SMTP server is OK. See Manage notifications for a team.
Based on my test, teams who are not part of Contributors group are not able to receive email notifications.
So, if your project team is not a member of the Contributors group, just add the team to the group. Then try it again.
Another workaround is using the email address directly when creating the subscriptions. This should be related to the AD sync issue. Refer to this thread for details: .
Without Active Directory, TFS will not send team alerts. Users can set
their preferred email address, which TFS will then sync to Active
Directory as the "[Member's default email address]". If no Active
Directory is found, that sync won't work, which means their default
email is blank. Blank email means no alert sent (which means no error
about the sending failing either).
I have this error when I push my code to Github repository by Xcode
Before answering the question you must know:
Although everyone can make a pull request, you can't just push to a repository. ِِYou need permission.
So this happened for me because in my Xcode, I was pushing to a remote that belonged to one of the other members ie I didn't have permission to push to.
You have two options:
Ask for permission from the owner of that remote repo/fork and have them include into one of its collaborators
Or Simply push to a repo that you have permission like your own repo,
using the dropdown menu encircled below (and perhaps then make a pull request from there to that branch you wanted to push to)
I usually run into this issue when I checkout directly from a remote branch ie I do something like:
git checkout -b localFromUpstream upstream/someBranch
And then when I commit, Xcode assumes that I want to push back to upstream/someBranch. But I don't permission to push to upstream/someBranch.
HTTP code 403 means forbidden, so it is most probably incorrect credentials. So double check your username and password etc.
https://en.wikipedia.org/wiki/HTTP_403
Even you can make a pull request, but can't just push to a repository. ِِYou need permission.
Inviting collaborators to a personal repository
Ask for the username of the person you're inviting as a collaborator. If they don't have a username yet, they can sign up for GitHub.
On GitHub, navigate to the main page of the repository.
Under your repository name, click Settings.
In the left sidebar, click Collaborators.
Under "Collaborators", start typing the collaborator's username.
Select the collaborator's username from the drop-down menu.
Click Add collaborator.
The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.