|
|
10/3/2016 11:54:40 PM
Scheduling deployment (#759)
|
9/28/2016 4:28:04 PM
swap DOM and DOW ? and *
|
9/26/2016 5:42:53 PM
3.3.0
(#751)
|
9/26/2016 2:48:27 PM
(#750)
The distribution tasks for azkaban-test were pointing to an invalid directory and were not resulting in any artifacts. Removing this dead code. The zip / tar archives are not used anywhere else in the project.
|
9/22/2016 6:04:44 PM
Java 8 (#747)
This patch will disable travis build tests for Java 7 and retain only java 8 tests. The motivation is to reduce support load and also incorporate a bunch of syntax goodies and features supported by Java 8.
Since build already succeeds / is deployed for Java 8. No further testing is required.
Also, updated Gradle IntelliJ configuration to use Java 8 language level for the project.
|
9/22/2016 5:57:13 PM
(#746)
Hadoop Tokens retrieved by Azkaban for running user processes were left world readable in the temp directory. This poses a major security threat since anyone can fish tokens from the tmp directory and use them to authenticate with hadoop using Azkaban.
This has been fixed by ensuring that the tokens created by Azkaban are readable only to the specific user. They are left readable/writable by the azkaban group which is helpful for performing cleanup tasks later on.
Code Changes: The Hadoop 2 Security Manager after fetching the token now, restricts permissions on the file and changes the file ownership to the specific user executing the job.
Testing: Build succeeds. This has been manually tested on a Kerberos enabled Hadoop Cluster. Most Acceptance tests pass. Those which fail are due to time outs for unavailable services.
No Automated tests were added due to the nature of the change - running shell based commands on file creation. Mocking this API doesn't help with any testing either.
Note: This has been only fixed in Hadoop 2. For deployments, azkaban-hadoopsecuritymanageryarn jar has been deprecated and should not be used. please use the azkaban-hadoop-security-plugin jar instead.
|
9/19/2016 9:24:37 PM
3.2.0
|
9/19/2016 3:24:15 PM
(#733)
* Throw exception on deploy action fail. * Added unit tests to make sure this behaviour happens (#725)
* Made deploy action code raise RestLi exceptions on failure. (#729)
This allows us to choose the specific HTTP status code when operations
fail. The status codes for this action have been updated to return 400 on failure.
* Made checkReport package-private for encapsulation. (#729)
Also moved test file for this into a different package. Condensed some
of its logic for readability, and added a new test to ensure messages
are getting through on error.
* Resolved file name change problem (#725)
* Made DeployProjectTest more compact, and renamed checkReport to
checkReports. (#725)
|
|
|
