[jira] [Commented] (FLINK-8819) Rework travis script to use build stages

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-8819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608550#comment-16608550 ] 

ASF GitHub Bot commented on FLINK-8819:
---------------------------------------

GJL commented on a change in pull request #6642: [FLINK-8819][travis] Rework travis script to use stages
URL: https://github.com/apache/flink/pull/6642#discussion_r216166677
 
 

 ##########
 File path: tools/travis/fold.sh
 ##########
 @@ -0,0 +1,33 @@
+#!/usr/bin/env bash
+################################################################################
+#  Licensed to the Apache Software Foundation (ASF) under one
+#  or more contributor license agreements.  See the NOTICE file
+#  distributed with this work for additional information
+#  regarding copyright ownership.  The ASF licenses this file
+#  to you under the Apache License, Version 2.0 (the
+#  "License"); you may not use this file except in compliance
+#  with the License.  You may obtain a copy of the License at
+#
+#      http://www.apache.org/licenses/LICENSE-2.0
+#
+#  Unless required by applicable law or agreed to in writing, software
+#  distributed under the License is distributed on an "AS IS" BASIS,
+#  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+#  See the License for the specific language governing permissions and
+# limitations under the License.
+################################################################################
+
+FOLD_ESCAPE="\x0d\x1b"
 
 Review comment:
   It wasn't done before but can we document the origins of these constants? It seems to be an undocumented travis feature.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Rework travis script to use build stages
> ----------------------------------------
>
>                 Key: FLINK-8819
>                 URL: https://issues.apache.org/jira/browse/FLINK-8819
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Build System, Travis
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Trivial
>              Labels: pull-request-available
>
> This issue is for tracking efforts to rework our Travis scripts to use [stages|https://docs.travis-ci.com/user/build-stages/].
> This feature allows us to define a sequence of jobs that are run one after another. This implies that we can define dependencies between jobs, in contrast to our existing jobs that have to be self-contained.
> As an example, we could have a compile stage, and a test stage with multiple jobs.
> The main benefit here is that we no longer have to compile modules multiple times, which would reduce our build times.
> The major issue here however is that there is no _proper_ support for passing build-artifacts from one stage to the next. According to this [issue|https://github.com/travis-ci/beta-features/issues/28] it is on their to-do-list however.
> In the mean-time we could manually transfer the artifacts between stages by either using the Travis cache or some other external storage. The cache solution would work by setting up a cached directory (just like the mvn cache) and creating build-scope directories within containing the artifacts (I have a prototype that works like this).
> The major concern here is that of cleaning up the cache/storage.
>  We can clean things up if
>  * our script fails
>  * the last stage succeeds.
> We can *not* clean things up if
>  * the build is canceled
>  * travis fails the build due to a timeout or similar
> as apparently there is [no way to run a script at the end of a build|https://github.com/travis-ci/travis-ci/issues/4221].
> Thus we would either have to periodically clear the cache, or encode more information into the cached files that would allow _other_ builds to clean up stale date. (For example the build number or date).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)