|
|
|
|
8/24/2017 7:56:40 PM
(#1346)
Added a config azkaban.storage.artifact.max.retention(default: 0)
Based on the storage parameter the files are removed and the project_versions table entries are removed.
``` /* * The max number of artifacts retained per project. * Accepted Values: * - 0 : Save all artifacts. No clean up is done on storage. * - 1, 2, 3, ... (any +ve integer 'n') : Maintain 'n' latest versions in storage * * Note: Having an unacceptable value results in an exception and the service would REFUSE * to start. * * Example: * a) azkaban.storage.artifact.max.retention=all * implies save all artifacts * b) azkaban.storage.artifact.max.retention=3 * implies save latest 3 versions saved in storage. **/ public static final String AZKABAN_STORAGE_ARTIFACT_MAX_RETENTION = "azkaban.storage.artifact.max.retention";
```
|
8/23/2017 2:04:06 PM
this PR is a follow-up of #1345. Last but not least, I'm migrating remained methods in JdbcExecutorloader to use new DB API. This commit should be the last one of the series.
|
8/23/2017 1:58:43 PM
PR is a follow-up of #1361 , which aimed at clearing the submodule dependency management. We explicitly depend on some internals from azkaban-db. It would be nice if we could hide this detail.
The solution originated from:
https://softnoise.wordpress.com/2014/09/07/gradle-sub-project-test-dependencies-in-multi-project-builds/
|
8/23/2017 11:21:30 AM
currently builds the `Server` and `Context` objects inside itself. The current refactor pulls out these code pieces into separate `@Provider` methods which are being injected by `Guice`. A separate submodule has been created for the purpose.
|
8/22/2017 7:47:38 PM
the change history at https://github
.com/tbroyer/gradle-errorprone-plugin/commits/master
|
8/22/2017 6:07:05 PM
plugin adds an errorprone configuration that automatically uses the latest release of error-prone. You can override it to use a specific version "
see https://github.com/tbroyer/gradle-errorprone-plugin
It appears that by latest version it will use the last locally cached
version. This caused inconsistency in builds.
## Fix:
Specify a fixed version
Will update to the latest version after the internal Artifactory
is updated with the latest version.
## Test:
Deleted the gradle cache and run the build again and verified in the
console output that the specified version was downloaded.
|
8/22/2017 5:25:23 PM
3.33.0
PR is a follow-up of #1345. Last but not least, I'm moving assignExecutor and UnAssignExecutor to a new DAO file.
The reason I don't create a new test file:
Not usre how much in-memory h2 database consume resources. We could use only one test class (in-memory h2) to do testing.
|
8/22/2017 3:15:23 PM
Fix build failure by suppressing MissingFail warning
* Explicitly fail the test if no exception is thrown.
|
