diff options
author | distix ticketing system <distix@pieni.net> | 2018-04-05 09:11:03 +0000 |
---|---|---|
committer | distix ticketing system <distix@pieni.net> | 2018-04-05 09:11:03 +0000 |
commit | b8932f185fc2d71102ac74ad27122bb32c4fde83 (patch) | |
tree | c8a9a36f2511afdaf8b7208080077b54474216bc | |
parent | 86bb52faf91345b6027994ac7e37cfc4fc0c8f25 (diff) | |
download | ick-devel-distix-b8932f185fc2d71102ac74ad27122bb32c4fde83.tar.gz |
imported mails
-rw-r--r-- | tickets/8d735e5266c94ec48cf9356549b593c6/Maildir/new/1522919463.M158643P16856Q1.koom | 130 |
1 files changed, 130 insertions, 0 deletions
diff --git a/tickets/8d735e5266c94ec48cf9356549b593c6/Maildir/new/1522919463.M158643P16856Q1.koom b/tickets/8d735e5266c94ec48cf9356549b593c6/Maildir/new/1522919463.M158643P16856Q1.koom new file mode 100644 index 0000000..a9c3c57 --- /dev/null +++ b/tickets/8d735e5266c94ec48cf9356549b593c6/Maildir/new/1522919463.M158643P16856Q1.koom @@ -0,0 +1,130 @@ +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 E75EF406EB
+ for <distix@pieni.net>; Thu, 5 Apr 2018 09:10:11 +0000 (UTC) +Received: from platypus.pepperfish.net (unknown [10.112.101.20])
+ by yaffle.pepperfish.net (Postfix) with ESMTP id C53A641840
+ for <distix@pieni.net>; Thu, 5 Apr 2018 10:10:11 +0100 (BST) +Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net)
+ by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian))
+ id 1f40uJ-0003h6-Ni; Thu, 05 Apr 2018 10:10:11 +0100 +Received: from [10.112.101.104] (helo=mx4.pepperfish.net)
+ by platypus.pepperfish.net with esmtps (Exim 4.80 #2 (Debian))
+ id 1f40uI-0003gt-Vh
+ for <ick-discuss@ick.liw.fi>; Thu, 05 Apr 2018 10:10:11 +0100 +Received: from mail.steve.org.uk ([176.9.183.102] helo=ssh.steve.org.uk)
+ by mx4.pepperfish.net with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
+ (Exim 4.89) (envelope-from <steve@steve.org.uk>) id 1f40uE-0005N2-Ub
+ for ick-discuss@ick.liw.fi; Thu, 05 Apr 2018 09:10:10 +0000 +DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
+ d=steve.org.uk; s=20150726; h=References:In-Reply-To:Message-ID:Date:Subject:
+ From:Cc:To:Sender:Reply-To:MIME-Version:Content-Type:
+ Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:
+ Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:
+ List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
+ bh=NXSwnVIkvJUhy4QWC+LS8UuvMyQsYmz89Ofjvx2CQZ8=; b=Cp0f+HjrdS/PPoDW4aMxKj0i7
+ T22GcNHhmAlKPKNKKESzeXoZo9Dm505iD8W7nmYiFMihIiz4dLehuNakGvESOoZczxWPOpqxn+CsU
+ Q/ayPMmeuA6Twyexvgwx7MfYrt6zTj5kAfrNUFjicTnDMwUsrCdg9Fd10c7p7Fxi9Ch/I=; +Received: from steve by ssh.steve.org.uk with local (Exim 4.89)
+ (envelope-from <steve@steve.org.uk>) id 1f40u7-0007BE-AZ
+ for ick-discuss@ick.liw.fi; Thu, 05 Apr 2018 09:09:59 +0000 +To: ick-discuss@ick.liw.fi +Cc: +From: Steve Kemp <steve@steve.org.uk> +Date: Thu, 05 Apr 2018 09:01:15 +0000 +Message-ID: <1522918875.22924.0@ssh.steve.org.uk> +In-Reply-To: <1522917706.3679.0.camel@liw.fi> +References: <1522917706.3679.0.camel@liw.fi> +X-added-header: steve.org.uk +X-Pepperfish-Transaction: 488f-3e01-9c53-eb2c +X-Spam-Score: 3.4 +X-Spam-Score-int: 34 +X-Spam-Bar: +++ +X-Scanned-By: pepperfish.net, Thu, 05 Apr 2018 09:10:10 +0000 +X-Spam-Report: Content analysis details: (3.4 points)
+ pts rule name description
+ ---- ---------------------- --------------------------------------------------
+ 2.5 PPF_GTLD_LONG Long gTLD, probably cheap throw-away domain
+ -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
+ domain
+ 1.0 BAYES_50 BODY: Bayes spam probability is 40 to 60%
+ [score: 0.5000]
+ -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
+ -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
+ domain
+ 0.1 DKIM_SIGNED Message has a DKIM or DK signature,
+ not necessarily valid +X-ACL-Warn: message may be spam +X-Scan-Signature: 37750eb53cbbcd37f0cf4d6178be310e +Subject: Re: Architecture doc updated - feedback welcom +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 + +> Any review and feedback would be welcome. Especially about things that
+> are unclear or missing.
+
+ In your example project you use inline python to execute the
+ three jobs "get_source", "build_ikiwiki_site" & "publish_html",
+ but I see that the action of the last task is defined as:
+
+ actions:
+ - shell: |
+
+ Which looks like a mistake, as it doesn't match the previous
+ entries.
+
+ (Might be nice to make it use a shell-command, to show how
+ the steps allow non-python!)
+
+ In the section "Getting an access token" you have a broken/bogus
+ markdown link "[Qvisqve][]".
+
+ All in all this is a great read, I only have two lingering
+ concerns:
+
+ * Each pipeline acts in the same workspace. The entire pipeline is
+ executed on the same worker.
+
+ * Credential management.
+
+ The first choice, to let all things work on the same worker, is
+ obviously simplest. It means that the existing workspace is present
+ and you don't need to use your artifact storage-system to upload
+ any in-progress work, and then refetch it. But I suspect that
+ in complex pipelines running jobs in parallel would be nice.
+
+ With regard to credentials I wonder how you'd clone the source
+ of a private repository, via git. I could imagine a (horrid)
+ hack using:
+
+ echo "ssh ..." > .ssh/id_rsa
+ ssh-keyscan git.example.com > .ssh/known_hosts
+ git clone ..
+
+ But that is obviously horrid. Do you have any plans to allow
+ credentials such that private repositories can be cloned? (I
+ appreciate that this doesn't really belong in the architecture
+ guide per se.)
+
+
+Steve
+--
+https://www.steve.org.uk/
+
+_______________________________________________
+ick-discuss mailing list
+ick-discuss@ick.liw.fi
+https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi
|