All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: "open list:-----------------..." <qemu-devel@nongnu.org>,
	serge.fdrv@gmail.com, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2] .travis.yml: Disable IRC build status updates from forks
Date: Tue, 28 Jun 2016 12:58:01 +0100	[thread overview]
Message-ID: <87d1n1ed9y.fsf@linaro.org> (raw)
In-Reply-To: <20160627181322.17082-1-bobby.prani@gmail.com>


Pranith Kumar <bobby.prani@gmail.com> writes:

> We want the travis build bot to post notifications on IRC only for the
> master qemu repository and not the various forks/branches of
> others. Currently there is no direct option to restrict the updates to
> one repository. This is being worked upon by the developers and
> tracked in https://github.com/travis-ci/travis-ci/issues/1094.
>
> Until such time, we can use the workaround as posted in
> ref. https://github.com/facebook/flow/pull/1822.
>
> This basically creates an ecrypted string which decrypts to qemu IRC
> channel only on "qemu/qemu" repo and not on the forks. This enables
> the build bot to notify the IRC only for the main repo.
>
> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
> CC: serge.fdrv@gmail.com
> CC: peter.maydell@linaro.org
> ---
> v2: Add comment about what the string is and how the string is generated
>
>  .travis.yml | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index c13881e..f30b10e 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -34,10 +34,13 @@ addons:
>        - sparse
>        - uuid-dev
>
> +# The channel name "irc.oftc.net#qemu" is encrypted against qemu/qemu
> +# to prevent IRC notifications from forks. This was created using:
> +# $ travis encrypt -r "qemu/qemu" "irc.oftc.net#qemu"

Interesting. I didn't realise anyone outside the repository can still
create encrypted strings. I guess there is a repository secret that we
never see.

>  notifications:
>    irc:
>      channels:
> -      - "irc.oftc.net#qemu"
> +      - secure: "F7GDRgjuOo5IUyRLqSkmDL7kvdU4UcH3Lm/W2db2JnDHTGCqgEdaYEYKciyCLZ57vOTsTsOgesN8iUT7hNHBd1KWKjZe9KDTZWppWRYVwAwQMzVeSOsbbU4tRoJ6Pp+3qhH1Z0eGYR9ZgKYAoTumDFgSAYRp4IscKS8jkoedOqM="
>      on_success: change
>      on_failure: always
>  env:


--
Alex Bennée

  reply	other threads:[~2016-06-28 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-27 18:13 [Qemu-devel] [PATCH v2] .travis.yml: Disable IRC build status updates from forks Pranith Kumar
2016-06-28 11:58 ` Alex Bennée [this message]
2016-06-28 13:35   ` Pranith Kumar
2016-06-28 16:09     ` Alex Bennée

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d1n1ed9y.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=bobby.prani@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=serge.fdrv@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.