From dev-return-35684-archive-asf-public=cust-asf.ponee.io@sqoop.apache.org Fri Feb 23 23:39:08 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 8B8A918067E for ; Fri, 23 Feb 2018 23:39:07 +0100 (CET) Received: (qmail 79165 invoked by uid 500); 23 Feb 2018 22:39:06 -0000 Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sqoop.apache.org Delivered-To: mailing list dev@sqoop.apache.org Received: (qmail 79150 invoked by uid 99); 23 Feb 2018 22:39:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Feb 2018 22:39:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 001D1C11BE for ; Fri, 23 Feb 2018 22:39:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id mc_XzNk1W_wF for ; Fri, 23 Feb 2018 22:39:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3FF495FC52 for ; Fri, 23 Feb 2018 22:39:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 2DB9FE091C for ; Fri, 23 Feb 2018 22:39:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 03E41255D2 for ; Fri, 23 Feb 2018 22:39:01 +0000 (UTC) Date: Fri, 23 Feb 2018 22:39:01 +0000 (UTC) From: "Attila Szabo (JIRA)" To: dev@sqoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SQOOP-3289) Add .travis.yml MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SQOOP-3289?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1637= 5050#comment-16375050 ]=20 Attila Szabo commented on SQOOP-3289: ------------------------------------- Hey [~dvoros], I would love the idea to have to finally have a working and=C2=A0 (apache t= oolchain) independent CI/CD system. Though if don't mind I'd like to aim for something more ambitious. What do you think:: Would it be possible to setup travis in a way to execute automatically unit= and integration and 3rd test for trunk after every commit? The reason why I'm asking is the following: I do understand that for developers who prefer the Github fork way it would= be much easier to execute the unit tests with Travis compared to local one= , although this solution would barely differ from the currently existing [h= ttps://builds.apache.org/job/Sqoop-hadoop200/]=C2=A0solution, and IMHO we d= efinitely NEED a CI system where ALL of the tests are evaluated after every= commit. I've been trying to get in contact with the responsible ppl to mak= e changes in [https://builds.apache.org/job/Sqoop-hadoop200/]=C2=A0though I= did not make too big achievements sadly. =C2=A0 Thats why I'm asking: What about to aim for running every tests in travis? =C2=A0 Thanks, Attila > Add .travis.yml > --------------- > > Key: SQOOP-3289 > URL: https://issues.apache.org/jira/browse/SQOOP-3289 > Project: Sqoop > Issue Type: Task > Components: build > Affects Versions: 1.4.7 > Reporter: Daniel Voros > Assignee: Daniel Voros > Priority: Minor > Fix For: 1.5.0 > > > Adding a .travis.yml would enable running builds/tests on travis-ci.org. = Currently if you wish to use Travis for testing your changes, you have to m= anually add a .travis.yml to your branch. Having it committed to trunk woul= d save us this extra step. > I currently have an example [{{.travis.yml}}|https://github.com/dvoros/sq= oop/blob/93a4c06c1a3da1fd5305c99e379484507797b3eb/.travis.yml] on my travis= branch running unit tests for every commit and every pull request: https:/= /travis-ci.org/dvoros/sqoop/builds > Later we could add the build status to the project readme as well, see: h= ttps://github.com/dvoros/sqoop/tree/travis > Also, an example of a pull request: https://github.com/dvoros/sqoop/pull/= 1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)