You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Elek, Marton (JIRA)" <ji...@apache.org> on 2017/07/30 14:56:00 UTC
[jira] [Commented] (RATIS-4) Setup jenkins
[ https://issues.apache.org/jira/browse/RATIS-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16106527#comment-16106527 ]
Elek, Marton commented on RATIS-4:
----------------------------------
Hi, I uploaded a proof-of-concept patch which contains a travis and a jenkins file.
1. Travis
As I know the capacity under the apache travis account is limited. But I saw at many places that the feature branches are tested by the creators of the fork with personal travis. (This pattern is used by Zeppelin and Hive as I know).
With a commited travis file it's easy to check the custom forks/feature brances by the users before the commit just with enabling travis for the forks. For example see my fork: https://travis-ci.org/elek/incubator-ratis
2. Jenkinsfile
The Jenkinsfile is tested on a local jenkins which used exactly the same version as the builds.apache.org. The name of tools are from other Jeknins files from apache respository, so it should be ok.
Still I have two big problems:
a.) protobuf: If I understood well the https://github.com/apache/infrastructure-puppet repository, the nodes have protoc but the default version from the operating system. This is 2.5/2.6 for the ubuntu nodes. Ratis use 3.1 protobuf as a dependency.
b.) I didn't find exact example for uploading the artifacts to the apache snapshot repository so it's missing from the Jenkinsfile
PROPOSAL:
To solve the protobuf problem I suggest to create a Dockerfile for build the project similar to the dev-support/docker/Dockerfile in the hadoop repository. As a first step we can create a simple shell script (build.sh) without yetus, which builds the docker image and after that, builds the project in the container.
If you agree, I would be happy to create the initial version from the Dockerfile and further improve the Jenkinsfile and .travis.yml.
> Setup jenkins
> --------------
>
> Key: RATIS-4
> URL: https://issues.apache.org/jira/browse/RATIS-4
> Project: Ratis
> Issue Type: Task
> Reporter: Enis Soztutar
> Attachments: RATIS-4.001.patch
>
>
> Jenkins unit test builds should be set up.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)