[
https://issues.apache.org/jira/browse/TEZ-4259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249702#comment-17249702
]
László Bodor commented on TEZ-4259:
-----------------------------------
thanks [~kgyrtkirk]
1. what I've seen so far, k8s environment is awesome (I even used it for
hunting TEZ-4230 down with hive unit tests, which was evil!), but fortunately,
tez pre-commit tends to show much fewer surprises than hive, so in the first
round, we can just focus on introducing plain PR integration (so isolation is
not a must-have now)
2. what I'm interested in more is that the actual testing of the Jenkinsfile,
maybe [~jeagles] already covered this, but I have no idea about that at the
moment, and I really want to play with the Jenkinsfile with dummy PRs, that's
because:
1. even if Jenkinsfile will make sense to me, and I feel it's a +1 LGTM, I have
no idea how it really works :)
2. I want to make sure that the precommit process covers everything which is in
my mind (findbugs, checkstyle, whatever, jdk8/jdk11 build ??, whatever)
could you please advise on this?
> Create Jenkinsfile for use with tez-multibranch (github yetus integration)
> --------------------------------------------------------------------------
>
> Key: TEZ-4259
> URL: https://issues.apache.org/jira/browse/TEZ-4259
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Jonathan Turner Eagles
> Assignee: Jonathan Turner Eagles
> Priority: Major
> Attachments: TEZ-4259.001.patch, TEZ-4259.002.patch
>
>
> Clone hadoop-multibranch to tez-multibranch
> https://ci-hadoop.apache.org/job/tez-multibranch/
> Couple of choices to base Jenkinsfile from.
> Scan will need a Jenkins file to correctly start builds based on github PR.
> Hadoop Jenkinsfile
> https://github.com/apache/hadoop/blob/trunk/Jenkinsfile
> HBase Jenkinsfile
> https://github.com/apache/hbase/blob/master/dev-support/Jenkinsfile_GitHub
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
