1. Shut down the buildbot-related containers and make sure they don't restart again when the host machine is rebooted.

2. Shut down the computers that we don't need any more (at least the Mac and Windows machines; also dmi-hydra?). Let the computer admins know that we no longer need them for the buildbot and possibly return the machines.

3. Remove or disable the buildbot-related Apache configuration.

4. Update the README file in the infrastructure repository.

5. Decide what to do with the various buildbot-related things in the infrastructure repository (under "hosts" and "services") and do it.

6. Remove misc/buildbot from the Fast Downward repository. Are there other buildbot-related things in this repository?

7. Update https://wiki.dmi.unibas.ch/doku.php?id=fbi:ai:infrastructure-documentation. Let Bas know which services no longer need to be migrated.

8. Update the Fast Downward wiki if there are references to the buildbot.

9. Remove the buildbot.fast-downward.org DNS entry, if it actually is a dedicated entry and not just a wildcard.

The last open point here was to shut down and return the machines that were running the buildbot. This has been done for some time now but it seems we forgot to close the issue.

I merged the pull request.

Regarding 2., I asked on ai@... if we still have a use for these machines. Depending on the answers, we can either have them turned off or returned in a week or so.

Regarding 9., there was no need for a configuration change and I have marked it as done.

Pull request looks good to me, too. Easy to review. :-)

Old issue scripts are there to be archived, not maintained. I would just keep it where it is. The only maintained file is the README file.

Thanks for taking care of all these TODOs! The pull request looks good to me. I also didn't find other references to "buildbot" in the repo, except for an old issue script "experiments/issue581/run-tests", which we could also remove. The script was added by me, but probably shouldn't have been added to the repo in the first place.

I added a pull request for removing the regression tests. I didn't find other references to the buildbot.

https://github.com/aibasel/downward/pull/37

I did the following steps
 1.* shut down the buildbot master container
 3. removed the apache conf
 4. removed references to buildbot in infrastructure/README
 5. removed the docker and docker-compose files in the infrastructure repo
 7. removed documentation from the wiki and contacted Bas
 8. removed all references to "buildbot" from the wiki
 
*) I have no ssh access to the buildbot workers, so I cannot shut them down from here. Anyway, shutting down the computers and formatting the harddrives will take care of this. I see no reason to clean up the containers on there first.

What remains to do is
 2. I cannot do this from home. We should also discuss if we want to keep the Windows and Mac machines for locally testing builds (e.g., not as buildbot worker, just as a test system).

 6. I can prepare a pull request.
 
 9. I don't have access to this.

> I can do 1. and 3. Should I do those now or is there something we are
> still waiting for?

Please do, we are no longer waiting for anything. The autodoc github action has been merged.

> Regarding 4. and 7., should we just remove all buildbot related things? I guess
> there is no reason to keep or archive them, is there? I would also remove the
> docker files from the infrastructure repository (If we need them, they are
> in the history).

I agree. Did you mean 4-7, or why 4 and 7 specifically?

In general, just let me know which of the steps you'll do, and I'll do the others. I'm happy to do anything that isn't related to docker, which I know very little about.

> @Florian: some of these will require your expertise. I'm happy to help with
> this as well. Shall we discuss how to proceed?

I can do 1. and 3. Should I do those now or is there something we are still waiting for? Regarding 4. and 7., should we just remove all buildbot related things? I guess there is no reason to keep or archive them, is there? I would also remove the docker files from the infrastructure repository (If we need them, they are in the history).

Most open items in issue1001 are all unrelated to the buildbot in the sense that they don't replace existing things we did on the buildbot but add new stuff.

It is a Github Actions wishlist, or more generally a continuous integration wishlist. (I'm not sure if Github Actions is really what we would use to track performance over time.) Perhaps the issue should be renamed.

What do we do with issue1001, which is "to replace the buildbot by Github actions"? Should it become "think about further tests to do in Github actions" or something along those lines? The issues feel a bit duplicate, otherwise.

Issue1013 is resolved.

We can disable the buildbot once issue1013 has been merged.

I've added the steps for removing the buildbot that I can think of to the summary.

@Florian: some of these will require your expertise. I'm happy to help with this as well. Shall we discuss how to proceed?