imported mails

1 files changed, 96 insertions, 0 deletions

diff --git a/tickets/df3c06a33121403aaf655e18065611a9/Maildir/new/1529507224.M133833P6075Q1.koom b/tickets/df3c06a33121403aaf655e18065611a9/Maildir/new/1529507224.M133833P6075Q1.koom
new file mode 100644
index 0000000..bd9b81f
--- /dev/null
+++ b/tickets/df3c06a33121403aaf655e18065611a9/Maildir/new/1529507224.M133833P6075Q1.koom
@@ -0,0 +1,96 @@
+Return-Path: <ick-discuss-bounces@ick.liw.fi>
+X-Original-To: distix@pieni.net
+Delivered-To: distix@pieni.net
+Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221])

+	by pieni.net (Postfix) with ESMTPS id B72414332D

+	for <distix@pieni.net>; Wed, 20 Jun 2018 15:06:12 +0000 (UTC)
+Received: from platypus.pepperfish.net (unknown [10.112.101.20])

+	by yaffle.pepperfish.net (Postfix) with ESMTP id 8B706414F2

+	for <distix@pieni.net>; Wed, 20 Jun 2018 16:06:12 +0100 (BST)
+Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)

+	by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))

+	id 1fVegW-0000Bl-Gd; Wed, 20 Jun 2018 16:06:12 +0100
+Received: from [148.252.241.226] (helo=somnambulist.local)

+ by platypus.pepperfish.net with esmtpsa (Exim 4.80 #2 (Debian))

+ id 1fVegU-0000B7-Pp

+ for <ick-discuss@ick.liw.fi>; Wed, 20 Jun 2018 16:06:10 +0100
+Date: Wed, 20 Jun 2018 16:06:09 +0100
+From: Daniel Silverstone <dsilvers@digital-scurf.org>
+To: ick-discuss@ick.liw.fi
+Message-ID: <20180620150609.a5xihmcbzeyxf3xx@somnambulist.local>
+References: <aa1c2a3004b3c67ad6bfa17911146e996e9159ba.camel@liw.fi>

+ <20180620134544.5wzm5rfff2oxqp5n@somnambulist.local>

+ <20180620150043.GA31229@exolobe1.liw.fi>
+MIME-Version: 1.0
+Content-Type: text/plain; charset=us-ascii
+Content-Disposition: inline
+In-Reply-To: <20180620150043.GA31229@exolobe1.liw.fi>
+User-Agent: NeoMutt/20170113 (1.7.2)
+X-Pepperfish-Transaction: f2d5-6558-035e-a7c7
+X-Pepperfish-Transaction-By: platypus
+Subject: Re: Ick and checking out source from git
+X-BeenThere: ick-discuss@ick.liw.fi
+X-Mailman-Version: 2.1.5
+Precedence: list
+List-Id: discussions about the ick CI system <ick-discuss-ick.liw.fi>
+List-Unsubscribe: <https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi>,

+ <mailto:ick-discuss-request@ick.liw.fi?subject=unsubscribe>
+List-Archive: <http://listmaster.pepperfish.net/pipermail/ick-discuss-ick.liw.fi>
+List-Post: <mailto:ick-discuss@ick.liw.fi>
+List-Help: <mailto:ick-discuss-request@ick.liw.fi?subject=help>
+List-Subscribe: <https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi>,

+ <mailto:ick-discuss-request@ick.liw.fi?subject=subscribe>
+Sender: ick-discuss-bounces@ick.liw.fi
+Errors-To: ick-discuss-bounces@ick.liw.fi
+
+On Wed, Jun 20, 2018 at 18:00:43 +0300, Lars Wirzenius wrote:

+> Hm. Supporting something like jinja2 in the controller is something

+> that may become necessary later on, but it's a complication that I'd

+> like to avoid until it is necessary to have it. Even if that means

+> more verbose .ick file. I guess it'd be possible to only support it

+> icktool, but I'll have to think about this.

+

+Supported in icktool and then uploading specialised pipelines would be

+acceptable.

+

+> Is your example really saving much typing? Since parameters are per

+> project, the following stanza would need to be repeated for each

+> project:

+

+doh, I meant for that to be part of a git pipeline step, and for source_name to

+be one of the parameters set in the project.  I was not explaining myself well.

+

+> I recognize that the .ick files get rather verbose as they are

+> currently defined. For the immediate future, I prefer that over a more

+> complicated controller. Later on, as we (as the ick project) gain more

+> experience of what the pain points are, we can make the .ick language

+> more powerful.

+

+It's possible that perhaps Yaml anchors and dictionary merges might help with

+some of this.

+

+> Maybe we can make the .ick language more powerful with better

+> defaults? Perhaps by having a "default parameters for all projects"

+> section? Also, sets of pipelines for different styles of projects?

+[snip]

+> No templating complexity, but rather less repetition. It's not as

+> generic a solution, of course. What do you think?

+

+I think that introduces a little bit too much magic into the git action,

+and another keyword (style) which I'm not convinced by.  For now let's

+stick as we are, and we can always consider preprocessing with jinja2

+in icktool or similar at a later date.

+

+At worst, for now, I have a shell script generate my ick file from a bunch

+of snippets and running sed :-)

+

+D.

+

+-- 

+Daniel Silverstone                         http://www.digital-scurf.org/

+PGP mail accepted and encouraged.            Key Id: 3CCE BABE 206C 3B69

+

+_______________________________________________

+ick-discuss mailing list

+ick-discuss@ick.liw.fi

+https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi