To clarify, the branch/stream field for the CSIT job template refers to the
branch on the integration repo. At this time, only the master branch exists on
the integration repo. So, you just need a single CSIT job which is
"master-csit", but you should ensure that your test case scripts are
For sdc release 1.1.0 is the amsterdam release
Original Message
From: Gary Wu
Date: Tue, Oct 31, 2017, 18:53
To: "Lando,Michael" , "Shlosberg, Yuli"
CC: "Gitelman, Tal" , "Amit, Idan"
I recommend that you remove the release-1.1.0-csit jobs for the time being.
Until we work out the branching strategy for CSIT, it's expected that the
master-csit jobs be testing Amsterdam deliverables.
Thanks,
Gary
-Original Message-
From: Lando,Michael [mailto:ml6...@intl.att.com]
Thank you for the answer.
So this means that once each project branches we will lose the abelty to use
csit.
I think thia needs to be comunicated to guilds because we are being tracked by
him regurding the state of our jobs.
Original Message
From: Gary Wu
Hi Yuli,
The integration repo doesn't have a "release-1.1.0" branch, so
release-1.1.0-csit jobs would not work.
We'll need to figure out a way to have CSIT support project branches given that
every project may a different branch name. Once we have this figured out we'll
update the community.