Michael,
Agree – oparent should be fully clean. Otherwise you cannot require
expectations that downstream projects be clean also.
Today on the PTL call Jimmy and myself want to bring up the issue of CLM run
frequency and what the responsibilities are for the PTL’s on this.
The CLM tool seems
Sounds good
When I posted "all" I only meant my pod - logging-analytics/POMBA
Essentially I am doing this - finding a gerrit review to run-clm in - does not
matter which one.
Running CLM weekly is not sufficient because CLM issues are being upgraded in
severity within the week - we loose up to
On 11/09/2018 04:40 PM, Michael O'Brien wrote:
> Team,
>
> Noticed some of the clm reports are stale – not reflecting current
> state of dependency issues.
>
> This is usually fixed by the magic word “run-clm” – in a current merge.
>
> Issue is how do I kick of builds in all the repos
Team,
Noticed some of the clm reports are stale - not reflecting current state of
dependency issues.
This is usually fixed by the magic word "run-clm" - in a current merge.
Issue is how do I kick of builds in all the repos without having to hunt
down the last commit for each repo - or
