Hi Sebb On Thu, Jul 16, 2020 at 11:25 PM sebb <seb...@gmail.com> wrote:
> > > What are the differences between the platforms and the plugins? > There are quite a lot of differences. Each jobs config would need adjusting manually to suit the new system, its plugins versions, the lack of views and the inclusion of Folders and its Auth strategy. The ci-builds main page points to > https://cwiki.apache.org/confluence/display/INFRA/Jenkins which > appears to document the old system > Yes I'll get a new page up soon. > > Is there no way to take config.xml from the old host and adjust it for > the new host? > If you want to do that for your project(s) feel free to have a try, I can provide the config, just tell me which project. I imagine then you would want to know what the adjusted config should look like? When you say 'take config.xml' and adjust it for the new host, it sounds so easy, but I'll tell you now that there is one for each job - that is there are *1759 config.xml* files. so yeah I am not going to go through each and every one of them trying to adjust them for the new system. I suspect most projects can just recreate their jobs just fine in the UI, or if needed I will supply them their config.xml files, with no guarantees that their tweaks will work. This is also an opportunity to remove old cruft that has been building up on Jenkins since 2008. Many jobs are disabled and won't need migrating. Many jobs are failing and have been for months if not longer, and so the project will notice this when migrating their jobs over. The current jobs folder is 2.4TB in size and so this is an opportunity to start again on this also. I have not just been lazy in deciding not to try and migrate all jobs, there are very good reasons for me not to do so. So please don't think I am passing the buck here, its the best way forward is to have every project involved in the moving of their own jobs.' > > There are currently 4 agents over there ready to take jobs, plus a > floating > > agent which is shared amongst many masters (more to come). I will migrate > > away 2 more agents from builds.a.o to ci-builds.a.o every few days, and > > will keep an eye of load across both and adjust accordingly. > > > > If needed, create a ticket on INFRA jira for any issues that crop up, or > > email here on builds@a.o. there may be one or two plugins we need to > > install/tweak etc. > > > > We will be not using 'Views' at the top level, but rather we will take > > advantage of 'Folders Plus' - each project will get its own Folder and > have > > authorisation access to create/edit jobs etc within that folder. I will > > create these folders as you ask for them to start with. This setup allows > > for credentials isolation amongst other benefits, including but not > limited > > to exclusive agents (Controlled Agents) for your own use , should you > have > > any project targeted donations of agents. > > > > As with other aspects of the ASF, projects can choose to just enable all > > committers access to their folder, just ask. > > > > We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will > not > > be setting up any forwarding rules or anything like that. > > > > So, please, get started *now *on this so you can be sure we are all > > completed before the final cutoff date of 15th August 2020. > > > > Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA > > tickets. > > > > Hadoop and related projects have their own migration path to follow, same > > cut off date, Cassandra, Beam, CouchDB have already migrated and are > doing > > very well in their new homes. > > > > Lets get going ... > > > > -- > > > > *Gavin McDonald* > > Systems Administrator > > ASF Infrastructure Team > -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
