OK.
On Thu, Jan 14, 2016 at 2:31 PM, Sandro Bonazzola
wrote:
>
>
> On Wed, Jan 13, 2016 at 10:07 AM, Eyal Edri wrote:
>
>> My question was why do we need the build artifacts for e.g?
>> I'm OK with the check-patch jobs that verify compilation for e.g, but are
>> we using the 3.6.2 build artifac
On Wed, Jan 13, 2016 at 10:07 AM, Eyal Edri wrote:
> My question was why do we need the build artifacts for e.g?
> I'm OK with the check-patch jobs that verify compilation for e.g, but are
> we using the 3.6.2 build artifacts jobs?
>
I'm using it for releasing engine and for getting engine rpms
My question was why do we need the build artifacts for e.g?
I'm OK with the check-patch jobs that verify compilation for e.g, but are
we using the 3.6.2 build artifacts jobs?
e.
On Wed, Jan 13, 2016 at 9:59 AM, Sandro Bonazzola
wrote:
>
>
> On Wed, Jan 13, 2016 at 8:22 AM, Eyal Edri wrote:
>
>
On Wed, Jan 13, 2016 at 8:22 AM, Eyal Edri wrote:
> I can't recall which 3.6.2 jobs we said we'll keep and which we'll drop.
> IIRC, we don't need the build artifacts jobs [1]
>
> Tal, you mentioned there were some jobs you do want to see running on the
> version branch,
> Do you recall which?
>
I can't recall which 3.6.2 jobs we said we'll keep and which we'll drop.
IIRC, we don't need the build artifacts jobs [1]
Tal, you mentioned there were some jobs you do want to see running on the
version branch,
Do you recall which?
I remind that running these temporarily jobs is an overhead sinc
