canonical-ci-engineering team mailing list archive
-
canonical-ci-engineering team
-
Mailing list archive
-
Message #01117
Fwd: ACTION REQUIRED: help us configure your ci services for wily / vivid overlay PPA
Hi,
This arrived in my inbox. Could the vanguard please take a look for me?
Let me know if you need more info.
Cheers,
---------- Forwarded message ----------
From: Pawel Stolowski <pawel.stolowski@xxxxxxxxxxxxx>
Date: Tue, May 19, 2015 at 9:53 PM
Subject: Re: ACTION REQUIRED: help us configure your ci services for wily /
vivid overlay PPA
To: Thomi Richards <thomi.richards@xxxxxxxxxxxxx>
Cc: Thomas Strehl <Thomas.Strehl@xxxxxxxxxxxxx>, Michi Henning <
michi.henning@xxxxxxxxxxxxx>
Hi Thomi,
After a lot of confusion about the situation with landings and not-so-clear
directions we were receiving, we concluded yesterday that the best and
proper way to move forward for some of the projects owned by my team is to
build our branches on top of willy, instead of vivid+overlay ppa as we
originally indicated in the spreadsheet, therefore I'd like to ask you to
reconfigure CI services for us once more. The change will affect all the
projects which have my irc nickname next to them (pstolowski), these are:
unity-api, unity-scopes-api, unity-scopes-shell, unity-scope-mediascanner.
I'm really sorry for the inconvenience caused by this change and the extra
effort required on your side. I hope we can avoid that kind of confusion in
the future...
Please let me know if I should update the spreadsheet.
Cheers,
Pawel
On 05/12/2015 06:43 AM, Thomi Richards wrote:
Hello,
The CI team are hard at work updating our CI platform for the Wily release.
If you manage a project that currently has CI services running on merge
proposals to your trunk branch, you need to tell us whether you want your
trunk branch to:
1.
build on top of wily
2.
build on top of vivid + the overlay PPA
To do this, fill in the details for your project(s) here:
https://docs.google.com/spreadsheets/d/1xaUV9QDNl_r9QJJ0DwiaigxD1qTYUW5V3aperJMRqsI/edit#gid=0
We need this information before Thursday 14th May, UTC, as we’ll be doing a
bulk config update before the end of this week. Please fill this in as soon
as possible, and we’ll do our best to keep autolanding & CI functioning
smoothly.
If you need a custom CI / autolanding solution, or if you need to make
configuration changes after the deadline, please send an email to the CI
engineering team:
canonical-ci-engineering@xxxxxxxxxxxxxxxxxxx
Cheers,
--
Thomi Richards
thomi.richards@xxxxxxxxxxxxx
--
Thomi Richards
thomi.richards@xxxxxxxxxxxxx