Problem description
Pravega uses HDFS, ExtendedS3, and NFS for tier 2 which is now named long-term-storage. The implementation for this change from binding to binding and requires different build jobs. The implementation is also coming via a separate PDP-34 and the repackaging done in the pravega-storage-adapters repository will be redone via the pull-request in pravega for issue-4907. This issue here tracks the convergence of the build automations into a consolidated template.

Problem location
The Jenkinsfile changes in the nautilus-pipelines repository.

Suggestions for an improvement
Although every repository has similar routines as building jars, images and libraries, the build files are maintained separately for say the server and tools. In this case, the storage adapters are also maintained separately from the main source code but it is in effect a part of the server. Build jobs are for the convenience of development while the script is for the template of steps for one or more code repositories. After the code and builds are stabilized for this repository, there can be a streamlining of steps so that the automation is using the same template.

Problem description
Currently there is no infrastructure in the build scripts to publish jars on Maven/BinTray/etc

Problem location
Build scripts

Suggestions for an improvement
Build scripts need to be extended with :publish task. Note that each storage adapter project should handle publishing of itself. The main build.gradle should have only common logic if any.

##Problem description
This repository produces bindings which are used in container deployments using docker images. This issue tracks the setup changes required to put the binding jars in the images so that they can be deployed as enhanced Pravega images.

they should be making a new Pravega image with only additonal jars, little or no additional files if possible

##Problem location
the docker file and associated build script

##Suggestions for an improvement

until this repository goes public, we can use internal image repositories but it should switch to Pravega and Travis will need the credentials to push the images there.

Problem description
HDFS and S3 have integration tests in the pravega segmentstore storage project which needs to be moved to this repository

Problem location
move
./segmentstore/server/host/src/test/java/io/pravega/segmentstore/server/host/HDFSIntegrationTest.java
./segmentstore/server/host/src/test/java/io/pravega/segmentstore/server/host/ExtendedS3IntegrationTest.java

Suggestions for an improvement
Put the integration test in the same project as the hdfs or extendeds3 but do not create a new integration project.
A new task called integration task is acceptable.
hdfs and extendeds3 can have their own build.gradle

##Problem description
The extendeds3 binding in the Pravega main source needs to be moved to this repository. Few criteria pertaining to the changes for this purpose:

1. they should be specific to extendeds3 in pravega main source, little or no additional files if possible
2. they should preserve history across repositories
3. they should include all the types of tests in this repository.
4. they should be as much as in sync with the Pravega main source as possible
5. they should not require to be imported elsewhere
6. they should handle all workflows using this binding

##Problem location
replace extendeds3 files in the new repo from those in the Pravega main source

##Suggestions for an improvement

• separation of pravega version for src,test,docker even though they may point to the same version

##Problem description
The hdfs binding in the Pravega main source needs to be moved to this repository. Few criteria pertaining to the changes for this purpose:

1. they should be specific to hdfs in pravega main source, little or no additional files if possible
2. they should preserve history across repositories
3. they should include all the types of tests in this repository.
4. they should be as much as in sync with the Pravega main source as possible
5. they should not require to be imported elsewhere
6. they should handle all workflows using this binding

##Problem location
replace hdfs files in the new repo from those in the Pravega main source

##Suggestions for an improvement

• separation of pravega version for src,test,docker even though they may point to the same version