It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×1,192

question asked: Jun 21 '11, 8:04 a.m.
question was seen: 5,362 times
last updated: Jun 21 '11, 8:04 a.m.

Related questions

Step fail notify failed to send email notification.

0
John Wang (101●16●12) | asked Jun 21 '11, 8:04 a.m.
Hi,

At the Project level, the Fail Notify is set to NONE. At the step leve, the Fail Notify is set to an ACCESS GROUP. However, Step's "on Fail" is set to "Continue". When the step failed, it didn't send email notification. Looking at the log, the step is marked with

, and the overall job status is set to "Failed but continue". We want to get the email notification if one of the steps failed and we don't want halt the job on failed steps. And the error condition is determined using Log filter. 


Tue Jun 21 00:30:20 EDT 2011: Step: 6684722: CRRBF1595I: Job [JOB_28_IFSE_Validate_Logon_Logoff] Step [validate HE70] starting command part 1 of 2.

Tue Jun 21 00:30:20 EDT 2011: Step: 6684722: CRRBF1597I: Job [JOB_28_IFSE_Validate_Logon_Logoff] Step [validate HE70] completed command part 1 of 2 [P].

Tue Jun 21 00:30:21 EDT 2011: Step: 6684722: CRRBF1595I: Job [JOB_28_IFSE_Validate_Logon_Logoff] Step [validate HE70] starting command part 2 of 2.

Tue Jun 21 00:30:22 EDT 2011: Step: 6684722: CRRBF1597I: Job [JOB_28_IFSE_Validate_Logon_Logoff] Step [validate HE70] completed command part 2 of 2 [P].

Tue Jun 21 00:30:22 EDT 2011: Event: 6684722: CRRBF1384I: Services queued event 'step.completed' [WAITING].

Tue Jun 21 00:30:26 EDT 2011: Event: 6684722: CRRBF1384I: Services queued event 'job.completed' [WAITING].

Tue Jun 21 00:30:28 EDT 2011: BuildForge: 7012426: CRRBF0926I: Job [9fd5e4750c531000f81c9f2b77527752] [6684722] completed.

4 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Brent Ulbricht (2.5k●1●1) | answered Jun 21 '11, 11:41 a.m.
JAZZ DEVELOPER
Hi,

At the Project level, the Fail Notify is set to NONE. At the step leve, the Fail Notify is set to an ACCESS GROUP. However, Step's "on Fail" is set to "Continue". When the step failed, it didn't send email notification. Looking at the log, the step is marked with

, and the overall job status is set to "Failed but continue". We want to get the email notification if one of the steps failed and we don't want halt the job on failed steps. And the error condition is determined using Log filter. 


Tue Jun 21 00:30:20 EDT 2011: Step: 6684722: CRRBF1595I: Job [JOB_28_IFSE_Validate_Logon_Logoff] Step [validate HE70] starting command part 1 of 2.

Tue Jun 21 00:30:20 EDT 2011: Step: 6684722: CRRBF1597I: Job [JOB_28_IFSE_Validate_Logon_Logoff] Step [validate HE70] completed command part 1 of 2 [P].

Tue Jun 21 00:30:21 EDT 2011: Step: 6684722: CRRBF1595I: Job [JOB_28_IFSE_Validate_Logon_Logoff] Step [validate HE70] starting command part 2 of 2.

Tue Jun 21 00:30:22 EDT 2011: Step: 6684722: CRRBF1597I: Job [JOB_28_IFSE_Validate_Logon_Logoff] Step [validate HE70] completed command part 2 of 2 [P].

Tue Jun 21 00:30:22 EDT 2011: Event: 6684722: CRRBF1384I: Services queued event 'step.completed' [WAITING].

Tue Jun 21 00:30:26 EDT 2011: Event: 6684722: CRRBF1384I: Services queued event 'job.completed' [WAITING].

Tue Jun 21 00:30:28 EDT 2011: BuildForge: 7012426: CRRBF0926I: Job [9fd5e4750c531000f81c9f2b77527752] [6684722] completed.



Hi,

What release/build are you using? I've noticed that in the early release 7.1.3 milestone build it works as you expect. Would it work for your project build to set an access group on your filter?

Brent Ulbricht
RTC Build Lead
0
permanent link
John Wang (101●16●12) | answered Jun 21 '11, 11:45 a.m.
Hi Brent,

Thank you for the reply.. We are currently running on 7.1.2... So you are saying this is fixed in 7.1.3.

I'll work with my AVP assess the implications of migrating from 7.1.2 to 7.1.3.
0
permanent link
Robert haig (1.0k●1●6) | answered Jun 21 '11, 12:59 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi Brent,

Thank you for the reply.. We are currently running on 7.1.2... So you are saying this is fixed in 7.1.3.

I'll work with my AVP assess the implications of migrating from 7.1.2 to 7.1.3.


that word "migrate" implies all the complicated things involved in the 7.0.x -> 7.1.x upgrade. We don't like that word :)

I've done several 7.1.2->7.1.3 upgrades here as part of build test. Some with rather large DBs. It takes a few minutes and can be done as part of the installation process. I suggest working with your DBAs to dupe your DB to a test instance, install your current version of 7.1.2 against it, and try upgrading it to the latest milestone.
0
permanent link
John Wang (101●16●12) | answered Jun 21 '11, 1:35 p.m.
Thanks Robert for your feedback.

Yes, I did use the word migrate based on the expirence I had with 7.0.x to 7.1.2. The BF project I am currently working on has drawn attentions from my management. So, I need to be extra cautious when applying the latest code. I would prefer if I don't need to do the upgarde.

I just tried Brent's recommendation.. the access group for both project and log filter are the same. If I set the "on Fail" to continue. it won't triger the notify failed. I also tried with exit code instead of the Log filter, same thing. However, I was able to work around this issue using another project and set it as Fail chain project. That worked.

Now, I am able to get the nofication with Project status as "Failed, but continue.". This is not what I like.. but for now.. It works. just extra logs in the DB.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.