How to send mails automatically when cvs check-in is performed ?
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
How to send mails automatically when cvs check-in is performed ?
Hi, Company network scenario : 2 RHEL servers... First server acts as Proxy,Mail & DHCP...while the second one acts as file server & cvs server. Problem : Till now everyone is able to checkout & checkin the cvs server successfully.Now the company persons has given me a challenge that whenever a person "checks-in" the cvs server a mail should go to a specified person/group automatically
How to send mails(automatically) to a particular person/group whenever a person makes check-in in the cvs server..?????
Sorry if i posted in the wrong section..i thought the problem is more with the mail part ..
Hi kstan,
Through ssh..i'll explain cvs-network in detail..We are currently working on different projects..So we had created different cvs repository for each project(total 3 cvs repositories)..
3 repositories are ..
1. /ic/a
2. /Sw/b
3. /Algo/c
Altogether 30 users are here out of which 5 are windows users & rest linux(RHEL Desktop or Mandriva)..Windows users are using wincvs 1.2 & linux users are using lincvs 1.4.3.Windows users connect to cvs-server through "ssh tunneling".Linux users connect to cvs-server through the port 2401.
At present when a user commits a change in the ic-repository(/ic/a), the other users who belong to that particular repository who get notification mail automatically...
Already we are having the group-id for the ic-team..
Hi kstan,
Through ssh..i'll explain cvs-network in detail..We are currently working on different projects..So we had created different cvs repository for each project(total 3 cvs repositories)..
3 repositories are ..
1. /ic/a
2. /Sw/b
3. /Algo/c
Altogether 30 users are here out of which 5 are windows users & rest linux(RHEL Desktop or Mandriva)..Windows users are using wincvs 1.2 & linux users are using lincvs 1.4.3.Windows users connect to cvs-server through "ssh tunneling".Linux users connect to cvs-server through the port 2401.
At present when a user commits a change in the ic-repository(/ic/a), the other users who belong to that particular repository who get notification mail automatically... If you'd have working solution then congratulation, and please share with us, otherwise I have 1 suggestions.
Already we are having the group-id for the ic-team..
Unfortunately I don't have any immediately solution, but I have is a work around solution (Which can be tricky)
My suggestion is,
Configure a start up script , when any ssh login will trigger the script and run some necessary action you want. (either ~/.bashrc, /etc/environment,/etc/profile,/etc/profile.d/automail or etc kind of way you prefer). The action can be check what current username, check what current cvs version (which is going to update), and etc.
If you want to maintain the server, create a specific username, inside the startup script purposely detect this kind of login won't trigger the email.
I hope you can understand and it is a long story to explain the scenario and logic. Simply plan for you strategy. However, before you ask us the next question tell us your strategy so we can suggestion what is the next step.
Have a look at cvsspam. I use it here to send emails on commits and it works fine. It needs ruby to run, but you don't need to know the ruby syntax to install/configure it.
Have a look at cvsspam. I use it here to send emails on commits and it works fine. It needs ruby to run, but you don't need to know the ruby syntax to install/configure it.
I see, it support svn? Seems like it need to always keep screening the repository to determine whether it have changes or not.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.