Wait wait, I'd have to redo the jobs? I didn't even create them in the first place, I have no idea what and how to do that, I'm just here to make sure they keep running and give a shout if anything goes wrong. :-) Being a project in maintenance mode there's no one available to do that work, So if I understood it correctly this time I'll have to kick this up the chain to see how to best handle this. On Sat, Jul 18, 2020 at 8:54 PM Vipul Siddharth <vipul at redhat.com> wrote: > On Sat, Jul 18, 2020 at 11:43 PM Tako Schotanus <tschotan at redhat.com> > wrote: > > > > Ok, so if I understand correctly if we don't do anything any Jenkins > jobs should be transferred automatically? > > oh no! apologies! seems the doc is not as clear as I had hoped it to > be :) I will modify it again (tomorrow or on Monday) > We will create you a namespace (say Launcher) with Jenkins provisioned > and you can configure these jobs there. You will have admin access to > the namespace and the Jenkins so you would be able to do anything > there. > If I am still confusing you, please let me know and we can talk on IRC > or a call and then I will also try to refine the doc as per > suggestions. > > > > > > We have 4 configurations in the current CI: > > > > https://ci.centos.org/search/?q=launcher > > > > The only thing I care about is that they keep running for the near > future. > > We'll probably not touch them anymore. > > > > Thanks! > > > > > > > > > > On Sat, Jul 18, 2020 at 1:29 PM Vipul Siddharth <vipul at redhat.com> > wrote: > >> > >> > >> > >> On Mon, Jul 6, 2020 at 5:28 PM Tako Schotanus <tschotan at redhat.com> > wrote: > >>> > >>> Hi Vipul, > >>> > >>> you said "If you are using ci.centos.org, it's a very good time to > start working > >>> on updating your workload ". Our project is in maintenance mode but is > still > >>> built and images keep being pushed for regular updates, so it's > essential that > >>> that should keep working. But we don't have a dedicated person anymore > >>> dealing with the CI/CD side of things. So is there any documentation > you can > >>> point to that explains what " updating your workload " would entail > and how to > >>> go about migrating things? > >> > >> > >> Hi Tako, > >> Apologies for the delay > >> I wrote a page [1] trying to explain some things. I hope it helps. > >> If you think I should add something more there, please let me know and > I will do it with priority. > >> > >> [1] https://centosci.github.io/ocp4-docs/sops/migration/ > >> > >>> > >>> Thanks! > >>> -Tako > >>> > >>> On Mon, Jul 6, 2020 at 11:34 AM Vipul Siddharth <vipul at redhat.com> > wrote: > >>>> > >>>> Reminder to tenants :) > >>>> > >>>> ---------- Forwarded message --------- > >>>> From: Vipul Siddharth <vipul at redhat.com> > >>>> Date: Thu, Jun 25, 2020 at 1:48 PM > >>>> Subject: Call for migration to new openshift cluster > >>>> To: ci-users <ci-users at centos.org> > >>>> Cc: David Kirwan <dkirwan at redhat.com> > >>>> > >>>> > >>>> Hi all, > >>>> > >>>> We are done and ready with the new Openshift 4 CI cluster. Now we want > >>>> to start the second phase of it i.e migrating projects to the new > >>>> cluster. > >>>> > >>>> If you are currently using apps.ci.centos.org (OCP 3.6), please > >>>> contact us off-list so that we can create a namespace for you in the > >>>> new OCP 4.4 cluster, so you can start migrating your workloads. > >>>> > >>>> It's not a hard deadline but we are hoping to retire the older > >>>> Openshift 3.6 cluster in the upcoming quarter (3 months) and legacy > >>>> (ci.centos.org) environment in a couple of months after that. > >>>> > >>>> If you are using ci.centos.org, it's a very good time to start > working > >>>> on updating your workload > >>>> > >>>> If you have any questions, please reach out to us > >>>> Thank You and stay safe > >>>> > >>>> -- > >>>> Vipul Siddharth > >>>> Fedora | CentOS CI Infrastructure Team > >>>> > >>>> > >>>> -- > >>>> Vipul Siddharth > >>>> Fedora | CentOS CI Infrastructure Team > >>>> > >>>> _______________________________________________ > >>>> CI-users mailing list > >>>> CI-users at centos.org > >>>> https://lists.centos.org/mailman/listinfo/ci-users > >>>> > >>> > >>> > >>> -- > >>> TAKO SCHOTANUS > >>> SENIOR SOFTWARE ENGINEER > >>> Red Hat > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> CI-users mailing list > >>> CI-users at centos.org > >>> https://lists.centos.org/mailman/listinfo/ci-users > >> > >> > >> > >> -- > >> Vipul Siddharth > >> He/His/Him > >> Fedora | CentOS CI Infrastructure Team > >> _______________________________________________ > >> CI-users mailing list > >> CI-users at centos.org > >> https://lists.centos.org/mailman/listinfo/ci-users > > > > > > > > -- > > TAKO SCHOTANUS > > SENIOR SOFTWARE ENGINEER > > Red Hat > > > > > > > > > > _______________________________________________ > > CI-users mailing list > > CI-users at centos.org > > https://lists.centos.org/mailman/listinfo/ci-users > > > > -- > Vipul Siddharth > He/His/Him > Fedora | CentOS CI Infrastructure Team > > _______________________________________________ > CI-users mailing list > CI-users at centos.org > https://lists.centos.org/mailman/listinfo/ci-users > > -- *TAKO SCHOTANUS* SENIOR SOFTWARE ENGINEER Red Hat <http://redhat.com> <https://www.redhat.com/> <https://red.ht/sig> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/ci-users/attachments/20200719/0ee007d5/attachment-0003.html>