7/27/2017 8:26:53 PM
Add metrics for sending email successs/failure.
* Guicify Emailer class and refactor some test cases.
|
7/27/2017 6:49:31 PM
in DB. (#1288)
|
7/25/2017 6:40:06 PM
to classes's annotations
This patch refactors the Guice uses, and mainly move all singleton
binding to respective classes with singleton annotations. The corresponding
tests are added as well. A bit more context is at #1285 .
|
7/25/2017 12:31:14 AM
type for killing a job
The action is to kill a job and retry it based on the retry configuration of that job.
Previously only killing a flow is allowed when SLA is missed even if SLA is set on job level.
New action will kick in when user sets SLA rule on a job and enforce kill action on missing the SLA. There's no UI change.
Testing it manually with following flows:
jobA(retry num: 2)->jobB(retry num: 2)
SLA rule: if job A doesn't succeed in 1 min, kill the job
SLA rule: if job B doesn't succeed in 1 min, kill the job
jobA->jobB, jobA->jobC, jobB->jobD, B retry number is set to 2.
SLA rule: if job B doesn't succeed in 1 min, kill it.
|
7/24/2017 2:22:05 PM
(#1279)
|
7/23/2017 6:28:08 PM
is intended to prevent the bug happened on #1283. I simply annotate ProjectManager singleton in this patth. When developers guicify other classes relying on ProjectManager in future, they will not need to worry about generating bugs.
|
|
|
7/20/2017 5:52:33 PM
bug was found in local solo server built by July 19th's master
code. Our integration test tried to add trigger, which run every
minutes. The strange observation is that this trigger never run. We
debugged the code and found that the TriggerScannerThread was launched
twice, and newly added triggers were put into the should-not-exist
thread and never run. I noticed that TriggerManager did not bind to
Singleton in Guice Confs. I made this change, and the thread doesn't
launch twice. The bug disappeared.
|
7/19/2017 1:05:11 PM
have the right permissions. (#1237)
Detailed changes:
1. Upload button is enabled only for admin users and users with UPLOADPROJECTS
permission when the property 'lockdown.upload.projects' is set to true.
2. New permission UPLOADPROJECTS is created
3. Handle the case for ajax upload as well
4. Tests included
Verified all changes against the azkaban-solo-server.
|
7/18/2017 8:49:54 PM
(#1277)
* make passwordPlaceHolder and password error message configurable
Some Azkaban instances needs 2FA authentications. The password field in login UI doesn't only include user's password. We modified the UI and make password placeholder configurable, such that Azkaban admins will be able to define.
|
