On Thu, Apr 26, 2018 at 5:08 PM, Alex Harui
wrote:
> On 4/26/18, 2:57 PM, "Greg Stein" wrote:
> On Thu, Apr 26, 2018, 16:42 Greg Stein wrote:
>
> > On Thu, Apr 26, 2018, 15:06 Alex Harui
> wrote:
> >
> >> Perhaps I wasn't clear. I am not concerned about Jenkins projects
> bei
On 4/26/18, 2:57 PM, "Greg Stein" wrote:
On Thu, Apr 26, 2018, 16:42 Greg Stein wrote:
> On Thu, Apr 26, 2018, 15:06 Alex Harui wrote:
>
>> Perhaps I wasn't clear. I am not concerned about Jenkins projects being
>> removed, just the artifacts of those projects. I a
On Thu, Apr 26, 2018, 16:42 Greg Stein wrote:
> On Thu, Apr 26, 2018, 15:06 Alex Harui wrote:
>
>> Perhaps I wasn't clear. I am not concerned about Jenkins projects being
>> removed, just the artifacts of those projects. I am trying to make two
>> points:
>>
>> 1) Old artifacts might have val
On Thu, Apr 26, 2018, 15:06 Alex Harui wrote:
> Perhaps I wasn't clear. I am not concerned about Jenkins projects being
> removed, just the artifacts of those projects. I am trying to make two
> points:
>
> 1) Old artifacts might have value as a known good build for a job that
> may not get ru
Perhaps I wasn't clear. I am not concerned about Jenkins projects being
removed, just the artifacts of those projects. I am trying to make two points:
1) Old artifacts might have value as a known good build for a job that may not
get run for years. So please don't run a clean up that deletes
Note that jobs will remain.
This is only about deleting build artifacts.
On Thu, Apr 26, 2018 at 12:40 PM, Alex Harui
wrote:
> HI Chris,
>
> Thanks for the list.
>
> I’m going through the Flex-related jobs and have some feedback:
>
> flex-blazeds (maven) We’ve kept this build around even thoug
HI Chris,
Thanks for the list.
I’m going through the Flex-related jobs and have some feedback:
flex-blazeds (maven) We’ve kept this build around even though it hasn’t run in
a while in case we need to do another release of blazeds. I would like to keep
at least one known good build in case w
