On 17 December 2017 at 14:18, Davide D'Alto wrote:
> I think using "Slave" alone might be goo enough.
+1 All jobs should use "Slave" unless there is need for an exception
to this rule :)
The known exceptions currently are:
- the one ORM job which tests using HANA, which should use the "HANA" la
I think using "Slave" alone might be goo enough.
It's generic and in the future, if we have some other different clouds,
jobs can use some additional labels to be more specific
At the moment, I think the only labels we need are: Master, Slave and HANA
On Sat, Dec 16, 2017 at 8:03 PM, Steve Eberso
Perhaps I am just dense here, but I still have no idea what you are
expecting me to use as the label for my ORM jobs
On Sat, Dec 16, 2017 at 12:53 PM Sanne Grinovero
wrote:
> On 16 December 2017 at 16:44, Steve Ebersole wrote:
> > For the main ORM job I see someone changed the label to "AWS&&S
On 16 December 2017 at 16:44, Steve Ebersole wrote:
> For the main ORM job I see someone changed the label to "AWS&&Slave", which
> is obviously different from the "Slave" label you recommended. Basically at
> this point I am completely lost as to what to use for these labels.
We used to have ma
For the main ORM job I see someone changed the label to "AWS&&Slave", which
is obviously different from the "Slave" label you recommended. Basically
at this point I am completely lost as to what to use for these labels.
Since I did not add this "AWS&&Slave" I am going to leave it alone. For
the
I see many jobs are still explicitly configured to request a build on
slaves tagged as "OS1".
Please get rid of that: we have no longer any slave running on OS1,
some of the new slaves use the "OS1" label to allow a smooth migration
- but it's a lie and it's been a long time since we removed OS1.
