Hi Yuli, sorry I somehow missed your email. The CSIT job templates are just like other jobs in that they accept a stream/branch parameter. The intention is that you would create a separate set of jobs for each branch, e.g. one set of jobs for master, another set for 1.1.0, yet another for 1.2.0, etc.
Thanks, Gary From: Shlosberg, Yuli [mailto:ys9...@intl.att.com] Sent: Sunday, October 15, 2017 4:04 AM To: Gary Wu <gary.i...@huawei.com> Cc: Lando,Michael <ml6...@intl.att.com> Subject: RE: A question regarding cist jobs Hi Gary, Is there any best practice you can share with us ? Thanks, Yuli From: Shlosberg, Yuli Sent: Wednesday, October 11, 2017 2:17 PM To: 'Gary Wu' <gary.i...@huawei.com<mailto:gary.i...@huawei.com>> Cc: Lando,Michael <ml6...@intl.att.com<mailto:ml6...@intl.att.com>> Subject: A question regarding cist jobs Hi Gary, I've a question related to branches , today in SDC we have few branches like 1.1.0 and 1.2.0. My question is how can I use csit to test both versions using same trigger. For example: We would like to trigger csit job that will test both versions after our nightly build or after docker creation. Is there any best practice you can share with us ? Thanks in advance, Yuli
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
