On Tue, Jul 4, 2017 at 3:49 PM, Sagi Shnaidman wrote:
> Every job contains topology file too, like "1cont_1comp" for example. And
> generally could be different jobs that run the same featureset024 but with
> different topologies. So I think the topology part is necessary
Every job contains topology file too, like "1cont_1comp" for example. And
generally could be different jobs that run the same featureset024 but with
different topologies. So I think the topology part is necessary too.
On Tue, Jul 4, 2017 at 8:45 PM, Emilien Macchi wrote:
>
On Fri, Jun 30, 2017 at 11:06 AM, Jiří Stránský wrote:
> On 30.6.2017 15:04, Attila Darazs wrote:
>>
>> = Renaming the CI jobs =
>>
>> When we started the job transition to Quickstart, we introduced the
>> concept of featuresets[1] that define a certain combination of features
HI
I think job names should be meaningful too. We can include like
"featureset024" or even "-f024"
in job name to make reproducing easily, or just to make another table of
featuresets and job names, like we have for file names and features.
On 30.6.2017 17:06, Jiří Stránský wrote:
On 30.6.2017 15:04, Attila Darazs wrote:
= Renaming the CI jobs =
When we started the job transition to Quickstart, we introduced the
concept of featuresets[1] that define a certain combination of features
for each job.
This seemed to be a sensible
On 30.6.2017 15:04, Attila Darazs wrote:
= Renaming the CI jobs =
When we started the job transition to Quickstart, we introduced the
concept of featuresets[1] that define a certain combination of features
for each job.
This seemed to be a sensible solution, as it's not practical to mention
If the topics below interest you and you want to contribute to the
discussion, feel free to join the next meeting:
Time: Thursdays, 14:30-15:30 UTC
Place: https://bluejeans.com/4113567798/
Full minutes: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting
= Renaming the CI jobs =
When