9/13/2016 3:47:44 PM
gradle distribution code
Currently, the gradle code for building distributions of azkaban modules is hosted in the root project build script. Although this works fine in terms of building artifacts, it is not modular / easier to maintain since the expected way of using the gradle distribution plugin is to have the build code inside the submodule which it is trying to build.
For example:
The distribution code for azkaban-webserver should reside in ./azkaban-webserver/build.gradle instead of build.gradle.
The distribution code logic has been moved into each submodule. Each sub-project is more self contained.
Also the copying of files etc are being handled manually which is nicely supported by the DSL. This has been refactored so that the distribution plugin configuration is able to take care of the copy logic
Removal of azkaban.version file. The azkaban.version file used to store the version number of the tar ball according to the git tag. Since we store the version in the file name itself as well as in manifest attributes of jar files, the version file provides a second source of truth. Thus, the code to create this file has been removed.
All bash scripts have now been moved to src/bash instead of package/bin.
All conf scripts have been moved to src/main/resources instead of package/conf. This change is motivated by the general java project structure where properties files and configuration reside in resource directories.
* Adding task dependency
The problem with Gradle distribution plugin is that there is no root task which is depended upon by installDist, distTar and distZip. Thus, if we need to add a dependent task to the distribution, it needs to be added to all the 3 tasks.
* Removing errorprone configuration
Since the errorprone plugin is applied to all subprojects, we do not need any custom configurations for plugin integration. This was required for previous versions of the plugin / gradle
|
9/12/2016 4:57:13 PM
(#728)
1). #727
2). #693
This commit brings cron utilities to Azkaban. Users are able to define a cron job now through Azkaban UI or Rest Call to Azkaban. Besides, this commit fixed DST change bug (#727) by enforcing cron running at server timezone (e.g. Pacific time). To enable the new schedule panel UI/utilities:
1). specify azkaban.schedulePanelPageName=schedulepanel.vm in .conf file
2). restart webserver
|
9/8/2016 3:04:01 PM
copyJSLibs must dependon bowerInstall (bowerInstall is not completed before copyJSLibs)
|
|
|
|
|
|
|
9/2/2016 1:55:54 PM
(#718)
* adding bower Install plugin and install moment.js, moment-timezone.js, bootstrap-datetimepicker.js
* fixed outdated dateimepicker API in Azkaban
|
|
|
7/29/2016 1:16:31 PM
3.1.0
versioning and refactor of build scripts
Added plugin group: 'com.cinnober.gradle', name: 'semver-git', version: '2.2.0' to enable semantic versioning of azkaban artifacts.
Refactor: Moved all subproject build code to respective projects.
* Build versioning and refactor of build scripts
Incorporating review comments - restored .gitignore filter on build - switching semver plugin to 2.2.1 which works with Java 7
|
7/29/2016 2:29:55 AM
gradle clean in README
|
