14:31:07 <bookwar> #startmeeting Fedora CI SIG
14:31:07 <zodbot> Meeting started Wed Apr 22 14:31:07 2020 UTC.
14:31:07 <zodbot> This meeting is logged and archived in a public location.
14:31:07 <zodbot> The chair is bookwar. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:31:07 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:31:07 <zodbot> The meeting name has been set to 'fedora_ci_sig'
14:31:53 <bookwar> #topic Hello
14:31:57 <bookwar> .hello2
14:31:58 <zodbot> bookwar: bookwar 'Aleksandra Fedorova' <alpha@bookwar.info>
14:32:02 <msrb> .hello2
14:32:03 <zodbot> msrb: msrb 'Michal Srb' <msrb@redhat.com>
14:32:50 <bookwar> #link https://etherpad.gnome.org/p/fedora-ci
14:33:10 <bookwar> i have couple of items on agenda, feel free to add yours
14:33:55 <bookwar> so let's give it another minute, ping tflink,fbo
14:34:59 <bookwar> #topic Communishift
14:35:14 <bookwar> let's start with the communishift migration first
14:35:22 <msrb> :)
14:35:38 <msrb> do we know when the migration will be finished?
14:36:12 <bookwar> so what we know: taskotron will be discontinued by Apr 30, and migration for Community Openshift is  scheduled till May 1st
14:36:40 <bookwar> so unfortunately we can not do a proper step by step migration
14:36:40 <msrb> that's one week, plus some change
14:37:15 <bookwar> let me record this
14:37:39 <bookwar> #info Community shift migration is ongoing, at least till May 1st
14:38:15 <bookwar> so we have an option to deploy our new jenkins jobs to the older jenkins
14:38:40 <msrb> is the older Jenkins running in some OpenShift?
14:38:42 <bookwar> but since tft backend is also not ready yet, looks like it won't give us anything
14:38:58 <bookwar> msrb: its on centos openshift cluster, the older one
14:39:10 <msrb> oh, right
14:39:20 <bookwar> msrb: so you do think we should try to deploy pipelines there?
14:40:01 <msrb> bookwar, well, only if the instance is under our full control
14:40:11 <msrb> if it is shared, then I wouldn't risk it :)
14:40:47 <bookwar> what would be the risk? what do we need for deploying new set of pipelines?
14:41:02 <bookwar> github branch plugin?
14:44:04 <bookwar> #idea Should we deploy new pipelines on old Jenkins in the meantime?
14:45:20 <bookwar> ok, now it is me only :)
14:45:24 <bookwar> moving on
14:46:03 <bookwar> #topic git_branch variable for use in tests.yml
14:47:15 <bookwar> after recent discussions on a mailing list, we are extending STI specification with the git branch parameter
14:47:19 <bookwar> #link https://pagure.io/fedora-ci/docs/pull-request/38
14:47:58 <bookwar> This will allow referencing to the current branch from the test description.
14:48:35 <bookwar> #info STR ansible roles will not use this parameter internally, it is up to the owner of tests.yml to use it in the playbook if needed
14:51:48 <bookwar> so, i guess we have a short meeting for today, for those who missed it - let's discuss on a mailing list
14:51:57 <bookwar> #endmeeting