Talk:Project Management
Jump to navigation
Jump to search
Initial Discussion
- Just to clarify on your point about Jenkins. Jenkins is about automated project workflows so that is focused on the user side of the PKC? And then kubernetes is focused on resource automation that manages the resource workflows, and the dockerized tools we employ? --Baliforester (talk) 05:53, 10 July 2021 (UTC)
- Jenkins is used for automating the overall software and content migration activities on the server side. Users usually don't have to do much about it. Kubernetes is dedicated to ensure all the deployed services are running in the right state. It works with docker's container standard to deploy the docker images that we deployed for certain functionalities added to MediaWiki and others through adding extensions. --Benkoo (talk) 06:03, 10 July 2021 (UTC)
- So basically we use Jenkins to build and integrate technology while kubernetes is mostly for deployment of the technology making sure it’s reliable and secure.--Baliforester (talk) 07:48, 10 July 2021 (UTC)
- It is important for us to have template for every process that matters. As we are aware that we have regular meeting every 2 days, we should start building correspondent templates containing key-value pairs. As more data flow and fill in a specific dictionary during our usage, a more complete and precise namespace will be constructed. Meeting Templates Design.