Wishes and Messages

Notification format sample

  1. Home
  2. Anniversary Wishes
  3. Notification format sample
Notification format sample
February 06, 2019 Anniversary Wishes 2 comments

Sample Format, Notification WITH an Administrative Separation Board. ( Letterhead). From: Commanding Officer. To: (Individual Marine). Subj: NOTIFICATION.

Decision I/4 (of the first Meeting of the Parties)
FORMAT FOR NOTIFICATION
  • Section I: Background
  • Section II: Specific Information Requirements
  • Section III: Form of Notification
  • Table 1: Notification to an Affected Party of a Proposed Activity under Article 3 of the Convention
  • Table 2: Reply to a Notification of a Proposed Activity under Article 3 of the Convention
  • Table 3: Public Notification of the Proposed Activity, EIA Process, and Participation and Consultation Process

The Meeting,

Recalling Article 3 of the Convention stipulating that a notification on a proposed project likely to have transboundary impact shall be transmitted to the affected Parties,

Having considered document CEP/WG.3/R.26 on the format for notification prepared by the delegation of Canada,

1. Expresses its appreciation to the delegation of Canada for the work undertaken;

2. Adopts the format for notification as appended to this decision; and

3. Recommends Parties to use the format to the extent possible when transmitting a notification according to Article 3 of the Convention.

Appendix
FORMAT FOR NOTIFICATION UNDER ARTICLE 3 OF THE ECE CONVENTION ON ENVIRONMENTAL IMPACT ASSESSMENT IN A TRANSBOUNDARY CONTEXT
 I. BACKGROUND []

1. The scope of information required in the notification process goes well beyond the minimum information requirements set out in Article 3 of the Convention. The information requirements fall into three main categories:

(i) Information needed for the affected Party to make a decision on its participation in the EIA process;

(ii) Information needed from the affected Party to assist in the assessment of transboundary environmental impacts and information needed to facilitate its participation and input to the EIA process; and

(iii) Information needed by the public and authorities in the potentially affected country to participate in the process.

2. Given these types of information, a three-stage notification procedure may be appropriate to ensure all of the information needed by each Party is conveyed to that Party. The notification procedure can be divided into three stages:

(i) Stage one: Notification of the proposed activity to the affected Party;

(ii) Stage two: Request for and transfer of information from the affected Party;

(iii) Stage three: Public notification of the proposed activity, EIA process and opportunities for public participation and consultation.

3. These stages correspond to the procedural steps of the Convention set out in the report on Bilateral and multilateral cooperation on environmental impact assessment in a transboundary context (CEP/WG.3/R.4, annex, figure 1) with the exception of "confirmation of participation". The format for the response to a request is included below.

4. The Party of origin initiates each of the stages either by providing or requesting information and may combine the stages to expedite the process. The request for information from the affected Party does not have to be delayed until a decision is made on whether or not it will participate. However, some of the information provided by the affected Party is needed prior to notifying the public in stage three, such as the affected Party's decision on whether it intends to participate and an agreed upon method of carrying out the public notification.

5. One option is to proceed with stages one and two concurrently. The request for information may be a part of stage one and assumes that the affected Party wishes to participate in the EIA process. The time period designated for providing information requested in stage two may be extended beyond the time-frame for response to stage one.

6. Given the time-frames for response suggested in the final report of the Task Force on Legal and Administrative Aspects (ENVWA/WG.3/R.12), it may be appropriate for stages one and two to proceed at the same time. The time-frame for stage two may commence after the response for stage one is given. This would allow affected Parties more time to gather the information requested in stage two.

 II. SPECIFIC INFORMATION REQUIREMENTS []

A. Stage one: Notification of the proposed activity to the affected Party

7. The first stage of notification is prepared by the designated authority in the country where the activity is proposed. The notification should contain sufficient specific information to enable the affected Party to make an informed decision on its participation.

1. Information on the proposed activity

8. The information requirements suggested in the Convention pointed to the idea that specific details of the activity, not just a brief description, were needed in the initial notification to enable the affected Party to make an informed decision on whether or not to participate in the EIA process. This has resulted in information requirements for the proposed activity which are quite detailed. The information elements (i.e. notification documentation) are:

(i) Information on the nature of the proposed activity:

  • Whether the activity is listed in Appendix I to the Convention;
  • Type of activity;
  • Scope of activity (e.g. main activity and any/all peripheral activities requiring assessment);
  • Scale of activity (e.g. size, production capacity, etc.);
  • Description of the activity (e.g. technology used);
  • Description of the purpose of the activity;
  • Rationale for proposed activity (e.g. socio-economic, physical-geographic basis);

(ii) Information on the spatial and temporal boundaries of the proposed activity:

  • Location and description of the location (e.g. physical-geographic, socio-economic characteristics);
  • Rationale for location of proposed activity (e.g. socio-economic, physical-geographic basis);
  • Maps and other pictorial documents connected with the information on the proposed activity;
  • Time-frame for proposed activity (e.g. start and duration of construction and operation);

(iii) Information on expected environmental impacts and proposed mitigation measures:

  • Scope of assessment (e.g. consideration of cumulative impacts, alternatives, sustainable development, associated activities, etc.);
  • Expected environmental impacts of the activity (e.g. types, locations, magnitudes);
  • Inputs (e.g. land, water, raw materials, power sources);
  • Outputs (e.g. amounts and types of: emissions into the atmosphere, discharges into the water system, solid waste);
  • Available information on the activity's possible significant transboundary environmental impacts (e.g. types, locations, magnitudes);
  • Measures to prevent, eliminate, minimize or compensate for environmental effects;

(iv) Name, address and telephone/fax numbers of proponent (developer);

(v) EIA documentation (e.g. EIA report or environmental impact statement (EIS)), if available.

9. The type of information included in the notification will vary from one proposed activity to the next and from country to country depending on the information available at the time of notification and the EIA process in each country. In some cases, EIA documentation (e.g. an EIA report or EIS) is required at the time when a proponent seeks government approval for an activity. If this information is available at the time of notification, it should be included with the initial notification.

2. Points of contact for the Party of origin

10. The name, address and telephone/fax numbers of the authority responsible for coordinating activities relating to the EIA should be provided (see decision I/3) together with a name, address and telephone/fax numbers for further information.

11. The name, address and telephone/fax numbers of the decision-making authority for the proposed activity (i.e. competent authority) should also be provided, if different from the above authority.

3. Points of contact for the possible affected Party or Parties

12. The name, address, and telephone/fax numbers of the authority responsible for coordinating activities relating to the EIA should be provided (see decision I/3, appendix, for points of contact).

13. The list of affected Parties to which notification is being sent should also be provided.

4. Information on the EIA process in the country where the proposed activity is located

14. The following should be provided:

- Information on the EIA process that will be applied to the proposed activity, including an indication of the time schedule, and opportunities for the affected Party or Parties to be involved in the EIA process and to review and comment on the notification and the EIA documentation;

  • The nature and timing of the decision that may be applied to the proposed activity;
  • Process for approval of the proposed activity.

5. Information on the public participation process

15. Information on the Party of origin's public participation process and the anticipated schedule for public consultation should be included.

6. Request for a response

16. A deadline should be included for providing a response as to whether or not the affected Party will participate.

17. The time-frame for a response on whether an affected Party would participate must be long enough to allow the affected Party to inform decision makers, consult with experts on the type of proposed activity, discuss the potential effects of the proposed activity and take a decision on its participation.

18. Short response times have led to problems and a minimum of six weeks for a response has been suggested. A time-frame of one to four months was suggested in the final report of the Task Force on Legal and Administrative Aspects (ENVWA/WG.3/R.12, para. 15). Given previous findings, the minimum time-frame for response could be one month and a half with a maximum of four months from the date of notification.

B. Stage two: Request for and transfer of information from the affected Party

19. The second stage of notification is the request for information from the affected Party assuming that the response by the affected Party is such that it intends to participate in the EIA.

1. Information on the potentially affected environment

20. The Party of origin may request:

  • Reasonably obtainable information from the affected country relating to the potentially affected environment;
  • Reasonably obtainable information on the activities within the potentially affected environment which may influence the potential transboundary environmental effects caused by the proposed activity;
  • Points of contact for this information.

The Party of origin will indicate the deadline for the submission of this information.

21. The quality of information provided by the affected Party is dependent on the information on the proposed activity that was provided by the Party of origin in stage one. If the Party of origin has provided sufficient information in stage one, the affected Party will be in a better position to know which information that it should provide.

22. The time-frame for the provision of this information has been addressed in the final report of the Task Force on Legal and Administrative Aspects (ENVWA/WG.3/R.12, para. 18), which suggests that up to four months might be sufficient for the provision of this information. If the request for information is included in stage one, the time-frame for response may be adjusted to reflect this early request or to reflect the date on which the affected Party responded to the notification. For example, the time-frame for providing stage two information may not start until a positive response from the affected Party is received.

2. Request for a proposal to solicit public participation in the EIA

23. The Convention requires that the public of the affected Party should be informed of the proposed activity and the EIA process that will be applied to it, and be given an opportunity to participate in the EIA process and make comments on or raise objections to the proposed activity. It was suggested in the report on Bilateral and multilateral cooperation on environmental impact assessment in a transboundary context (CEP/WG.3/R.4, annex, para. 40) that the notification of the public should be given as a public advertisement or a special information brochure. This document also suggested that the detailed arrangements to inform the public of the affected Party may be made through bilateral or multilateral agreements.

24. In the absence of such an agreement, the Party of origin may request a proposal from the affected Party to arrange for the publication of the notice and make copies of the EIA documentation available to the public. The Party of origin may request information on the procedure for making documents available to the public of the affected country, the language in which the affected Party prefers the notification and documents, and the location where they should be made available. In this request, the Party of origin could again state the public participation process in the country of origin. Such information could assist the affected Party to tailor its proposal so that its own public participation process, when appropriate, can be harmonized with that of the Party of origin's. Such coordination could help enhance and facilitate the overall public participation process for a proposed activity.

25. Details which need to be decided on include:

  • Who will notify the public and/or distribute the EIA documentation?
  • Who will conduct the public participation process and receive comments from the public?
  • The names, addresses and telephone/fax numbers of the newspapers and/or other news media in which the public notices should appear;
  • Details to be included in the advertisement including where, and in what language(s), the EIA documentation may be inspected;
  • The names, addresses and telephone/fax numbers of the authorities to which the EIA documentation should be sent and the number of copies required for each;
  • Public locations where EIA documentation should be sent and the number of copies required at each location.

26. It may be beneficial to request a proposal at the time of stage one, assuming that a positive response is expected from the affected Party on its participation in the EIA.

27. The final report of the Task Force on Legal and Administrative Aspects (ENVWA/WG.3/R.12, para. 36) concluded that "... translation is required in any case where language differences exist and where the language in a document ... may not be understood by those who read it". This report also concluded that "... the Party of origin should be responsible for translations and bear the related costs, unless the concerned Parties have agreed otherwise" (ENVWA/WG.3/R.12, para. 41). This leaves the option of bilateral agreements on the issue of translation open to the Parties.

C. Stage three: Public notification of the proposed activity, EIA process and opportunities for public participation and consultation

28. Once the Party of origin has received the proposal from the affected Party to solicit participation from the public and authorities, the notification is published in the affected country.

1. Information on the proposed activity

29. The public notification should include a brief description of the proposed activity, including its location, the time-frame for the proposed activity, potential transboundary impacts, and brief information on the EIA process that will be applied to the proposal.

2. Point of contact for public participation/consultation

30. The Party of origin should ensure that this notification contains the name, address and telephone/fax numbers of the authority to which members of the public are invited to submit comments.

3. Information on the participation process

31. The notification should also:

  • Give a timetable for participation, consultation, comments;
  • Specify where, and in which language(s), the EIA documentation may be inspected.
III. FORM OF NOTIFICATION []

32. Notification samples can exist in two forms, letter and tabular/list. The predominant form is the tabular or list form. This form has an advantage since it may be scanned quickly to ensure all information requirements have been included. Specific information is easily retrieved since the information in each box is clearly identified by a heading.

33. The tabular or list format also lends itself to being made available electronically. For example, a registry system for the Convention may be established as part of the ECE database on EIA, in which all notifications are filed electronically and made available through the Internet.

34. The letter form of notification is less clear and requires closer scrutiny to retrieve specific information, but is more suitable when a request for information is being made.

35. A combination of these two forms may be appropriate in stage one. A brief cover note may be written indicating that an activity with significant transboundary effects is being proposed in a specific country and this is the notification specified under Article 3 of the Convention. The note would then refer to the attached table or list that contains the specific information for the notification. The response to the stage one notification from the affected Party could be in the form of a letter. An example of a table that may be used in stage one is given in table 1 below.

36. The request for information for stage two may be made in letter form. The Party of origin may choose to provide a table for the affected Party to complete. The response from the affected Party could take a tabular form to ensure that all of the components of the request have been considered. A sample response table is provided in table 2 below.

37. The notification of the public (stage three) could also be in tabular form. A sample tabular form for stage three is given in table 3 below.

 Table 1 []

NOTIFICATION TO AN AFFECTED PARTY OF A PROPOSED ACTIVITY UNDER ARTICLE 3 OF THE CONVENTION
1. INFORMATION ON THE PROPOSED ACTIVITY
(i) Information on the nature of the proposed activity
Type of activity proposed 
Is the proposed activity listed in Appendix I to the Convention?

Yes No

Scope of proposed activity
(e.g. main activity and any/all peripheral activities requiring assessment)
 
Scale of proposed activity
(e.g. size, production capacity, etc.)
 
Description of proposed activity
(e.g. technology used)
 
Description of purpose of proposed activity 
Rationale for proposed activity
(e.g. socio-economic, physical geographic basis)
 
Additional information/comments 
(ii) Information on the spatial and temporal boundaries of the proposed activity
Location+ 
Description of the location (e.g. physical-geographic, socio-economic characteristics) 
Rationale for location of proposed activity (e.g. socio-economic, physical-geographic basis) 
Time-frame for proposed activity (e.g. start and duration of construction and operation) 
Maps and other pictorial documents connected with the information on the proposed activity 
Additional information/comments 

(iii) Information on expected environmental impacts and proposed mitigation measures

Scope of assessment (e.g. consideration of: cumulative impacts, evaluation of alternatives, sustainable development issues, impact of peripheral activities, etc.)

 

Expected environmental impacts of proposed activity (e.g. types, locations, magnitudes)

 

Inputs (e.g. raw material, power sources, etc.)

 

Outputs (e.g. amounts and types of: emissions into the atmosphere, discharges into the water system, solid waste)

 

Transboundary impacts (e.g. types, locations, magnitudes)

 

Proposed mitigation measures (e.g. if known, mitigation measures to prevent, eliminate, minimize, compensate for environmental effects)

 

Additional information/comments

 

(iv) Proponent/developer

Name, address, telephone and fax numbers

 

(v) EIA documentation

Is the EIA documentation (e.g. EIA report or EIS) included in the notification?

Yes No Partial

If no/partial, description of additional documentation to be forwarded and (approximate) date(s) when documentation will be available

 

Additional information/comments

 

2. POINTS OF CONTACT
(i) Points of contact for the possible affected Party or Parties
Authority responsible for coordinating activities relating to the EIA (refer to decision I/3, appendix)

- Name, address, telephone and fax numbers

 
List of affected Parties to which notification is being sent 
(ii) Points of contact for the Party of origin
Authority responsible for coordinating activities relating to the EIA (refer to decision I/3, appendix)
- Name, address, telephone and fax numbers
 
Decision-making authority if different than authority responsible for coordinating activities relating to the EIA
- Name, address, telephone and fax numbers
 
3. INFORMATION ON THE EIA PROCESS IN THE COUNTRY WHERE THE PROPOSED ACTIVITY IS LOCATED
(i) Information on the EIA process that will be applied to the proposed activity
Time schedule 
Opportunities for the affected Party or Parties to be involved in the EIA process 
Opportunities for the affected Party or Parties to review and comment on the notification and the EIA documentation 
Nature and timing of the possible decision 
Process for approval of the proposed activity 
Additional information/comments 
4. INFORMATION ON THE PUBLIC PARTICIPATION PROCESS IN THE COUNTRY OF ORIGIN
Public participation procedures 
Expected start and duration of public consultation 
Additional information/comments 
5. DEADLINE FOR RESPONSE
Date 
 
 Table 2 []
REPLY TO A NOTIFICATION OF A PROPOSED ACTIVITY UNDER ARTICLE 3 OF THE CONVENTION
1. INFORMATION ON THE POTENTIALLY AFFECTED ENVIRONMENT
(i) Information relating to the potentially affected environment
Protected areas 
Geographic features 
Archaeologically sensitive areas 
Ecology of the region 
Additional information/comments 
(ii) Information on activities within the potentially affected region

Activities which may influence the transboundary environmental effects caused by the proposed activity

 
Additional information/comments 
(iii) Points of contact
Points of contact where above information may be obtained
- Names, addresses, telephone and fax numbers
 
2. RESPONSE TO REQUEST FOR A PROPOSAL FOR PUBLIC PARTICIPATION
(i) Language(s) 
Language(s) of the EIA documentation 
Language(s) of the publications 
(ii) Responsible Parties
Party responsible for public notification and/or distribution of EIA documentation 
If different than above, Party responsible for conducting the public participation process and for receiving comments from the public 
(iii) Advertisements
Names, addresses, telephone and fax numbers of the newspapers or other media in which the public notices should appear 

2. RESPONSE TO REQUEST FOR A PROPOSAL FOR PUBLIC PARTICIPATION

Details to be included in the advertisements (e.g. brief description of proposed activity, where comments can be forwarded, time-table for public participation, where EIA documentation can be inspected, language of EIA documentation, etc.)

 

(iv) Distribution of EIA documentation

Public locations where EIA documentation should be sent (e.g. libraries) including the number of copies required at each location

 

Authorities (i.e. governmental, scientific, etc.) to which the EIA documentation should be sent, including the number of copies for each authority

 
(v) Additional information regarding proposal for public participation
Additional information/comments/suggestions
 Table 3 []
PUBLIC NOTIFICATION OF THE PROPOSED ACTIVITY, EIA PROCESS, AND PARTICIPATION AND CONSULTATION PROCESS
1. INFORMATION ON THE PROPOSED ACTIVITY
(i) Brief description of the proposed activity
Location 
Potential transboundary impacts 
Time-frame for proposed activity 
Information on the EIA process that will be applied to the proposal 
Additional information/comments 
2. POINT OF CONTACT FOR PUBLIC PARTICIPATION/CONSULTATION
Authority to which members of the public are invited to submit comments
- Name, address, telephone and fax numbers
 
3. INFORMATION ON THE PARTICIPATION PROCESS
Time-table for participation, consultation, comments 
Where, and in which language(s), the EIA documentation may be inspected 

Describes the message and JSON formats that Amazon SNS supports. header is an example of a header for a Notification message to an HTTP endpoint.

Bootstrap Notify

notification format sample

Notification letters are business letters that are used to notify someone about something. Since sometimes, the letter is not meant to warn the recipient but only to inform or notify him, they are different than the warning letters. Notification letters can be used by employers to notify their employees, by courts to notify the relevant parties involved in a case, by landlords to their tenants, by businesses to their customers etc. They are used for different purposes. For example, discipline notification, absence in court hearing notification, truancy notification, eviction notification etc. Usually, the format of all notification letters is the same. Here is a little about notification letters.

  • Notification letters are usually written in business letter format
  • Sometimes, the notification letters are also written in email format
  • Unlike many other letters, notification letters are short and concise.
  • The notified should add his signature or stamp in a notification letter.
  • One should avoid using harsh language in notification if it is serious or continuous notice
  • If a response is required, the recipient should be told within the letter to submit response by the given date
  • If the notification is an official notification it usually contains the company’s logo on the head of the letter.
  • A notification letter should end up with decent salutations, requesting the recipient to consider it.

If you don’t know how to write notification letters, no problem; it is never bad to learn from examples. We are here to assist you to learn some notification letter formats and styles. Check out our samples and by looking at a few, you’ll be able to make your own. If you find it difficult to make a full-fledged letter, just modify our given samples and use them. Eureka!

Below is the sample text for the letter

I, Mr. [enter name], your landlord, am writing this letter to you in order to notify you regarding the rental agreement that took effect between us on [enter date]. As per the agreement, the agreement was supposed to end on [enter year/month/date]. It is [enter month] and as I was bound to notify you two months before the end of the agreement, I am writing to you to remind you about it. The agreement is ending on [enter month/date] so you are requested to vacate the land/house before the end of [enter month]. In the case that you want to renew the agreement, please inform me as soon as you receive this notification. Thank you! 

 

Preview and Details of Template

Notification Letter Template

File: Word (.doc) 2007+ and iPad 
Size 28 Kb   | Download

File: OpenOffice (.odt) Writer [Writer]
Size 11 Kb   |  Download

License: ENERGY  (Personal Use Only)
(Distribution) by Kate Elizabeth(CEO)

best confession of love
I am nothing
order confirmation examples
When to use faithfully or sincerely in a letter
extend an invitation to attend a trade show
A letter of accomplishment
how to take things slow in a new relationship
Letter to government official template

Looking for other ways to read this?

notification format sample

NOOOOOOO. You are talking to a military romance scammer. I received an email from the US Army that directly answers your question that is pasted below please keep reading.I believe you are the victim of a military Romance Scam whereas the person you are talking to is a foreign national posing as an American Soldier claiming to be stationed overseas on a peacekeeping mission. That's the key to the scam they always claim to be on a peacekeeping mission.Part of their scam is saying that they have no access to their money that their mission is highly dangerous.If your boyfriend girlfriend/future husband/wife is asking you to do the following or has exhibited this behavior, it is a most likely a scam:Moves to private messaging site immediately after meeting you on Facebook or SnapChat or Instagram or some dating or social media site. Often times they delete the site you met them on right after they asked you to move to a more private messaging siteProfesses love to you very quickly & seems to quote poems and song lyrics along with using their own sort of broken language, as they profess their love and devotion quickly. They also showed concern for your health and love for your family.Promises marriage as soon as he/she gets to state for leave that they asked you to pay for.They Requests money (wire transfers) and Amazon, iTune ,Verizon, etc gift cards, for medicine, religious practices, and leaves to come home, internet access, complete job assignments, help sick friend, get him out of trouble, or anything that sounds fishy.The military does provide all the soldier needs including food medical Care and transportation for leave. Trust me, I lived it, you are probably being scammed. I am just trying to show you examples that you are most likely being connned.Below is an email response I received after I sent an inquiry to the US government when I discovered I was scammed. I received this wonderful response back with lots of useful links on how to find and report your scammer. And how to learn more about Romance Scams.Right now you can also copy the picture he gave you and do a google image search and you will hopefully see the pictures of the real person he is impersonating. this doesn't always work and take some digging. if you find the real person you can direct message them and alert them that their image is being used for scamming.Good Luck to you and I'm sorry this may be happening to you. please continue reading the government response I received below it's very informative.   You have contacted an email that is monitored by the U.S. Army Criminal Investigation Command. Unfortunately, this is a common concern. We assure you there is never any reason to send money to anyone claiming to be a Soldier online. If you have only spoken with this person online, it is likely they are not a U.S. Soldier at all. If this is a suspected imposter social media profile, we urge you to report it to that platform as soon as possible. Please continue reading for more resources and answers to other frequently asked questions:  How to report an imposter Facebook profile: Caution-https://www.facebook.com/help/16... < Caution-https://www.facebook.com/help/16... >   Answers to frequently asked questions:  - Soldiers and their loved ones are not charged money so that the Soldier can go on leave.  - Soldiers are not charged money for secure communications or leave.  - Soldiers do not need permission to get married.  - Soldiers emails are in this format: [email protected] < Caution-mailto: [email protected] > anything ending in .us or .com is not an official email account.  - Soldiers have medical insurance, which pays for their medical costs when treated at civilian health care facilities worldwide – family and friends do not need to pay their medical expenses.  - Military aircraft are not used to transport Privately Owned Vehicles.  - Army financial offices are not used to help Soldiers buy or sell items of any kind.  - Soldiers deployed to Combat Zones do not need to solicit money from the public to feed or house themselves or their troops.  - Deployed Soldiers do not find large unclaimed sums of money and need your help to get that money out of the country.  Anyone who tells you one of the above-listed conditions/circumstances is true is likely posing as a Soldier and trying to steal money from you.  We would urge you to immediately cease all contact with this individual.  For more information on avoiding online scams and to report this crime, please see the following sites and articles:   This article may help clarify some of the tricks social media scammers try to use to take advantage of people: Caution-https://www.army.mil/article/61432/< Caution-https://www.army.mil/article/61432/>   CID advises vigilance against 'romance scams,' scammers impersonating Soldiers  Caution-https://www.army.mil/article/180749 < Caution-https://www.army.mil/article/180749 >   FBI Internet Crime Complaint Center: Caution-http://www.ic3.gov/default.aspx< Caution-http://www.ic3.gov/default.aspx>   U.S. Army investigators warn public against romance scams: Caution-https://www.army.mil/article/130...< Caution-https://www.army.mil/article/130...>   DOD warns troops, families to be cybercrime smart -Caution-http://www.army.mil/article/1450...< Caution-http://www.army.mil/article/1450...>   Use caution with social networking  Caution-https://www.army.mil/article/146...< Caution-https://www.army.mil/article/146...>    Please see our frequently asked questions section under scams and legal issues. Caution-http://www.army.mil/faq/ < Caution-http://www.army.mil/faq/ > or visit Caution-http://www.cid.army.mil/ < Caution-http://www.cid.army.mil/ >.  The challenge with most scams is determining if an individual is a legitimate member of the US Army. Based on the Privacy Act of 1974, we cannot provide this information. If concerned about a scam you may contact the Better Business Bureau (if it involves a solicitation for money), or local law enforcement. If you're involved in a Facebook or dating site scam, you are free to contact us direct; (571) 305-4056.   If you have a social security number, you can find information about Soldiers online at Caution-https://www.dmdc.osd.mil/appj/sc... < Caution-https://www.dmdc.osd.mil/appj/sc... > . While this is a free search, it does not help you locate a retiree, but it can tell you if the Soldier is active duty or not.  If more information is needed such as current duty station or location, you can contact the Commander Soldier's Records Data Center (SRDC) by phone or mail and they will help you locate individuals on active duty only, not retirees. There is a fee of $3.50 for businesses to use this service. The check or money order must be made out to the U.S. Treasury. It is not refundable. The address is:  Commander Soldier's Records Data Center (SRDC) 8899 East 56th Street Indianapolis, IN 46249-5301 Phone: 1-866-771-6357  In addition, it is not possible to remove social networking site profiles without legitimate proof of identity theft or a scam. If you suspect fraud on this site, take a screenshot of any advances for money or impersonations and report the account on the social networking platform immediately.  Please submit all information you have on this incident to Caution-www.ic3.gov < Caution-http://www.ic3.gov > (FBI website, Internet Criminal Complaint Center), immediately stop contact with the scammer (you are potentially providing them more information which can be used to scam you), and learn how to protect yourself against these scams at Caution-http://www.ftc.gov < Caution-http://www.ftc.gov > (Federal Trade Commission's website)

For example, this will send Slack notifications only on builds on the master all relevant data to do so at the receiving end (see Webhooks Delivery Format).

Notification Emails

notification format sample

Improve this page on GitHub

Configuring Build Notifications

Note that if you’re still using travis-ci.org you need to use instead of in all of the commands shown on this page.

Travis CI can notify you about your build results through email, IRC, chat or custom webhooks.

Default notification settings #

By default, email notifications are sent to the committer and the commit author when they are members of the repository, that is they have

  • push or admin permissions for public repositories.
  • pull, push or admin permissions for private repositories.

Emails are sent when, on the given branch:

  • a build was just broken or still is broken.
  • a previously broken build was just fixed.

For more information, please read default email addresses, changing the email address or troubleshooting email notification.

If you add another notification channel, e.g. HipChat or Slack, the default is to send a notification on every build.

Conditional notifications #

You can filter out and reject notifications by specifying a condition in your build configuration (your file) using .

For example, this will send Slack notifications only on builds on the branch:

See Conditions for details on specifying conditions.

Changing notification frequency #

You can change the conditions for any notification channels by setting the or flag to one of:

  • : always send a notification.
  • : never send a notification.
  • : send a notification when the build status changes.

For example, to always send slack notifications on successful builds:

Note: These webhooks are executed at the end of a build, and not by individual jobs (see builds vs jobs). This means that environment variables from the build are not available in this section.

There is currently no way of limiting the notification to a specific branch, but the payload will contain all relevant data to do so at the receiving end (see Webhooks Delivery Format).

Note on SSL/TLS Ciphers #

When posting notifications over SSL/TLS, be mindful of what ciphers are accepted by the receiving server. Notifications will fail if none of the server’s ciphers work.

Currently, the following ciphers (as defined by the openssl gem) are known to work:

Also, consult cipher suite names mapping.

If none of the ciphers listed above works, please open a GitHub issue.

Note on IP addresses #

All notifications that use HTTP are sent through a proxy with static IP addresess to ensure safelist and firewall rule stability. The current IP addresses are:

Configuring email notifications #

Specify recipients that will be notified about build results:

Turn off email notifications entirely:

Specify when you want to get notified:

Pull Request builds do not trigger email notifications.

How is the build email receiver determined? #

By default, a build email is sent to the committer and the author, but only if they have access to the repository the commit was pushed to. This prevents forks active on Travis CI from notifying the upstream repository’s owners when they’re pushing any upstream changes to their fork. It also prevents build notifications from going to folks not registered on Travis CI.

The email address is then determined based on the email address in the commit, but only if it matches one of the email addresses in our database. We synchronize all your email addresses from GitHub, solely for the purpose of build notifications.

The default can be overridden in the as shown above. If there’s a setting specified, Travis CI only sends an emails to the addresses specified there, rather than to the committer and author.

Changing the email address for build notifications #

Travis CI only sends build notifications to email addresses registered on GitHub. If you have multiple addresses registered you can set the email address for a specific repository using :

Note that this also changes the commit email address, not just the Travis CI notification settings.

Or set the email for all of your git repositories:

Note that we currently don’t respect the detailed notifications settings on GitHub, as they’re not exposed via an API at this point.

Missing build notifications #

The most common cause for not receiving build notifications, beyond not having a user account on Travis CI, is the use of an email address that’s not registered and verified on GitHub. See above on how to change the email address to one that’s registered or make sure to add the email address used in this repository to your verified email addresses on GitHub.

Configuring IRC notifications #

You can also send notifications to an IRC channel. Notifications are sent from , which auto-authenticates on Freenode.

Or multiple channels:

As with other notification types you can specify when IRC notifications will be sent:

Customize the message that will be sent to the channel(s) with a template:

You can interpolate the following variables:

  • repository_slug: your GitHub repo identifier (like )
  • repository_name: the slug without the username
  • repository: same as repository_slug [Deprecated]
  • build_number: build number
  • build_id: build id
  • branch: branch build name
  • commit: shortened commit SHA
  • author: commit author name
  • commit_message: commit message of build
  • commit_subject: first line of the commit message
  • result: result of build
  • message: travis message to the build
  • duration: total duration of all builds in the matrix
  • elapsed_time: time between build start and finish
  • compare_url: commit change view URL
  • build_url: URL of the build detail

The default template is:

If you want the bot to use notices instead of regular messages the flag can be used:

and if you want the bot not to join before sending the messages, use the flag:

If you enable , remember to remove the flag (n) on the IRC channel(s) the bot notifies.

Pull Request builds do not trigger IRC notifications.

Channel key #

If you want the bot to send messages to channels protected with a channel key (ie, set with ), use the variable:

Note: We highly recommend you encrypt this value if your .travis.yml is stored in a public repository.

Password protected servers #

You may also authenticate to an IRC server with user:

Note: We highly recommend you encrypt this value if your .travis.yml is stored in a public repository.

Configuring campfire notifications #

Notifications can also be sent to Campfire chat rooms, using the following format:

  • subdomain: is your campfire subdomain (i.e. if you visit )
  • api token: is the token of the user you want to use to post the notifications.
  • room id: this is the room id, not the name.

Note: We highly recommend you encrypt this value if your .travis.yml is stored in a public repository:

You can also customise the notifications, like with IRC notifications:

Other flags, such as and also work like they do in IRC notification configuration.

Pull Request builds do not trigger Campfire notifications.

Configuring flowdock notifications #

Notifications can be sent to your Flowdock Team Inbox using the following format:

  • api token: is your API Token for the Team Inbox you wish to notify. You may pass multiple tokens as a comma separated string or an array.

Note: We highly recommend you encrypt this value if your .travis.yml is stored in a public repository:

Pull Request builds do not trigger Flowdock notifications.

Configuring HipChat notifications #

Send notifications to your HipChat rooms using the following key in your :

  • : token of the user you want to post the notifications as. One of
    • API v1 token your group administrator gives you.
    • API v2 token you manage.
  • : optional, defaults to api.hipchat.com, but can be specified for HipChat Server instances.
  • or : id or name (case-sensitive) of the room you want to notify. If your room name contains spaces then use room id.

Always encrypt this value if your is stored in a public repository:

If you are running HipChat Server, specify the hostname like this instead:

HipChat notifications support templates too, so you can customize the appearance of the notifications, e.g. reduce it to a single line:

If you want to send HTML notifications you need to add like this (note that this is not compatible with some features like @mentions and autolinking):

With the V2 API, you can trigger a user notification by setting :

Setting the From value in notifications #

When a V1 token is used, the notification is posted by “Travis CI”.

With a V2 token, this value is set by the token’s Label. Create a special-purpose room notification token (“Tokens” under the room’s “Administration” section) with a desired label, and use this token.

Notifications of PR builds #

By default, Hipchat will be notified both for push builds and pull request builds.

Turn pull request notifications off by adding to the section of your :

Configuring Pushover notifications #

Notifications can also be sent via Pushover via the following format:

  • api token: API Token/Key for a Pushover Application (create this under “Your Applications” after logging in to Pushover; it’s recommended to create one specific to Travis CI).
  • user key: The User Key for a user to be notified (this can be seen after logging in to Pushover). A list of multiple users is supported.

Note: We highly recommend you encrypt these values if your .travis.yml is stored in a public repository; this will add (or overwrite) your api_token, and append the specified user_key to the list of users.

You can also customise the notifications, like with IRC notifications:

Other flags, such as and also work like the IRC notification config.

Pull Request builds do not trigger Pushover notifications.

Configuring Slack notifications #

Travis CI can send notifications to your Slack channels about build results.

On Slack, set up a new Travis CI integration.

Copy and paste the settings, which already include the proper token, into your , and you’re good to go.

Note: We highly recommend you encrypt this value if your .travis.yml is stored in a public repository:

The simplest configuration requires your account name and the token you just generated.

To specify a different channel, add it to the configuration with a separating the channel from the account and token:

To specify a different channel when using with encrypted credentials use:

You can specify multiple channels as well.

Similarly, you can use the channel override syntax with encrypted credentials as well.

This is how a setup with encrypted credentials could look like:

Once everything’s set up, push a new commit and you’ll get a message in the slack channel.

Notifications of PR builds #

Turn pull request notifications off by adding to the section of your :

Customizing slack notifications #

Customize the notification message by editing the template, as in this example:

The default template for push builds is:

while the default template for pull request builds is:

You can also use Slack-style markup using , , , , . See Slack documentation for more information on message formatting.

Configuring webhook notifications #

You can define webhooks to be notified about build results:

Or multiple URLs:

As with other notifications types you can specify when webhook payloads will be sent:

Webhooks Delivery Format #

Webhooks are delivered with a content type using HTTP POST, with the body including a parameter that contains the JSON webhook payload in a URL-encoded format.

Here is the payload sent to the Travis CI documentation application:

You will see one of the following values in the / fields that represent the state of the build.

  • 0: Represents a build that has completed successfully
  • 1: Represents a build that has not yet completed or has completed and failed

Additionally a message will be present in the / fields that further describe the status of the build.

  • Pending: A build has been requested
  • Passed: The build completed successfully
  • Fixed: The build completed successfully after a previously failed build
  • Broken: The build completed in failure after a previously successful build
  • Failed: The build is the first build for a new branch and has failed
  • Still Failing: The build completed in failure after a previously failed build
  • Canceled: The build was canceled
  • Errored: The build has errored

The field can be used to find the event type that caused this build to run. Its value is one of , , , or . For pull requests, the field will have the value , and a field is included too, pointing to the pull request’s issue number on GitHub.

To quickly identify the repository involved, we include a header, with a format of , so for instance .

Verifying Webhook requests #

To ensure the integrity of your workflow, we strongly encourage you to verify the POST request before acting on it.

The POST request comes with the custom HTTP header . Using the published SSL public key, you can verify the signature of the payload.

  1. Pick up the data from the HTTP request’s body.
  2. Obtain the header value, and base64-decode it.
  3. Obtain the public key corresponding to the private key that signed the payload. This is available at the endpoint’s on the relevant API server. (e.g., https://api.travis-ci.com/config)
  4. Verify the signature using the public key and SHA1 digest.

Examples #

  1. WebhookSignatureVerifier is a small Sinatra app which shows you how this works.

  2. This documentation site receives a webhook notification, verifies the request and updates the Gist showing the payload example above. See the code.

  3. Travis Webhook Checker is an example Django view which implements this in Python.

  4. Travis Golang Hooks Verification is a small webapp in Go which verifies the hook.

  5. travis-webhook-verification-nodejs contains two examples for verifying webhooks in Node.js using express and hapi.js

Configuring OpsGenie notifications #

By using OpsGenie Travis CI Integration, you can forward Travis CI alerts to OpsGenie. OpsGenie can determine the right people to notify based on on-call schedules, using email, text messages (SMS), phone calls and iPhone & Android push notifications, and escalating alerts until the alert is acknowledged or closed.

Functionality of the integration #

  • When the status of a project is failing, broken or errored on Travis CI, an alert is created in OpsGenie automatically through the integration.
  • When the status is passed or fixed on Travis CI, the alert is closed in OpsGenie.

Add Travis CI Integration in OpsGenie #

  1. Please create an OpsGenie account if you haven’t already
  2. Go to OpsGenie Travis CI Integration page,
  3. Specify who should be notified for Travis CI alerts using the “Teams” field. Auto-complete suggestions will be provided as you type.
  4. Copy the Webhook URL by clicking on the copy button or selecting.
  5. Click on “Save Integration”.

Configuration in Travis CI #

  1. Activate your Github repositories that you want to monitor by enabling the service hook for Travis CI on Github.
  2. Add .travis.yml file to your repository.
  3. Add the following configuration to your .travis.yml file. notifications: _webhooks:
  4. Commit the .travis.yml file to the root of your repository.

Configuring multiple notification targets with different configurations #

Each of the notifiers described above can also take an array of hashes as configurations, each element being a configuration of that notifier as described above. This is useful when you want different notification behaviors based on build results.

For example, you might have separate Slack channels for notifying successful builds and failing builds, using non-default templates:

WATCH THE VIDEO ON THEME: How to write Notice - Tips of Notice Writing with format and a sample

Having considered document CEP/WG.3/R on the format for notification prepared by the . Notification samples can exist in two forms, letter and tabular/ list.

notification format sample
Written by Zolotaxe
Write a comment