Remove remnants of Travis

[zsunberg]

We need to go through and remove all .travis.yml files and travis badges. This would be easy to do - just need a volunteer to do it.

[dylan-asmar]

@zsunberg is there a particular workflow preference you have when we update this? In SARSOP.jl, I added separate workflows for documentation and code coverage of tests. I don't mind making similar changes as I come across different repos, but wanted to make sure that separate GitHub actions are ok or if you prefer one large workflow.

[zsunberg]

@dylan-asmar awesome! thanks for your work in SARSOP!

I tend to try to follow what PkgTemplates does, just because that will be the most common thing for the community. Looks like they have it in one file: https://github.com/invenia/PkgTemplates.jl/blob/master/templates/github/workflows/CI.yml

[zsunberg]

If you wanted to get really fancy and really embody the CS virtue of lazyness, you could write a script to do this for all the packages (possibly using the gh command line tool, but I don't think that is strictly needed).

[dylan-asmar]

Making some progress:

• Updated the CI to include codecov and docs in the original CI yml SARSOP.jl#60
• ci workflow update, readme update, files cleanup LaserTag.jl#15
• ci workflow update, readme update, files cleanup POMCPOW.jl#35
• ci workflow update, readme update, files cleanup POMDPModels.jl#87
• ci workflow update, readme update, files cleanup TabularTDLearning.jl#26
• ci workflow update, readme update, files cleanup BasicPOMCP.jl#32
• ci workflow update, docs build update, readme update, files cleanup MCTS.jl#94
• CI Updates and removal of POMDPSimulators from tests ARDESPOT.jl#33
• POMDPTools and CI updates DroneSurveillance.jl#19
• Badge fix and CI Update QuickPOMDPs.jl#38 (some Travis remnants remained)
• CI Update LocalApproximationValueIteration.jl#28 (some Travis remnants remained)
• Ci update and remaining travis-ci cleanup GlobalApproximationValueIteration.jl#16 Travis yml file remained)
• Updated to Flux 0.14, removed POMDPSimulators, updated CI DeepQLearning.jl#66
• CI update, badge update, and travis cleanup PointBasedValueIteration.jl#16
• JuMP and GLPK compat, POMDPTools, and CI updates IncrementalPruning.jl#36
• Docs update MCVI.jl#23
• POMDPTools and CI Updates BeliefGridValueIteration.jl#7
• POMDPTools and CI Updates AEMS.jl#14
• POMDPTools and CI Updates FiniteHorizonValueIteration.jl#11
• Travis cleanup ci updates POMDPLinter.jl#12
• Update to POMDPs 0.9 and POMDPTools BlinkPOMDPSimulator.jl#16
• LAMBDA-POMDP -> JuliaPOMDP and CI Updates AdaOPS.jl#11

Not planning on modifying deprecated packages (e.g. https://github.com/JuliaPOMDP/RLInterface.jl)

[zsunberg]

Awesome, @dylan-asmar , this is really great!

[mykelk]

Thanks so much @dylan-asmar ! I think you can merge these when ready.

[zsunberg]

Yeah, at this point, @dylan-asmar , I think you can just go ahead and merge all pull requests that you have yourself. Just make sure tests pass, etc. The only reason not to would be if you have specific questions that you're not sure how to answer.

Do you have the necessary github permissions to do that?

[dylan-asmar]

I believe I have the permissions. As I'm going through the repos I'm also making minor changes from time to time. I'll ping you @zsunberg on those to just make sure it doesn't mess something up.

[dylan-asmar]

For https://github.com/JuliaPOMDP/POMDPGallery.jl and https://github.com/JuliaPOMDP/POMDPExamples.jl, what are the thoughts on updating these repos with #241 and #417 still open?

[zsunberg]

I don't think we should maintain POMDPExamples. The important tutorials there should be moved to the main POMDPs.jl documentation (i.e. I still think we should fix #417).

I'm less sure about POMDPGallery. I guess since we list the problem repos in the POMDPs.jl README now, the best thing would be to move the examples from POMDPGallery to the individual project repos, but I am not 100% sure.

But that is a lot of work that is probably not the highest priority. If someone can do it, great! but it is not a disaster in the state it is in now.

[mykelk]

I think we should keep POMDPGallery. I use it quite a bit when demoing POMDPs.jl. I'm okay with POMDPExamples eventually being merged into the documentation of POMDPs.jl.

[dylan-asmar]

I think POMDPGallery is a great tool to show off POMDPs.jl. However, I think existing as a separate package doesn't add a lot of value. I think it would be better to have it as part of the docs of POMDPs.jl.

One option would be to have the scripts as examples and then the gifs get created at documentation generation. Another option is to just embed the gifs into the docs and make sure we update them at each new release of POMDPs.jl.

An alternative thought is to create a GitHub action with the problem repos where when updates to the problems occur, it autogenerates the gifs and submits a PR to this POMDPGallery repo.

[mykelk]

I'm good with moving them into the docs. I'd really like to make it easy for people to find a page with all of these examples. If in the docs, then I think we should link directly to that location from the readme.md.

[dylan-asmar]

If we agree to not update POMDPExamples and POMPGallery (move both to docs), then I think this issue is almost ready to be closed out.

The only repo that I think is left is POMDPLinter.jl. When updating that one, I ran into an issue where tests were failing (without updates). I opened an issue on that repo and once we address that issue we can merge the travis_cleanup_ci_updates branch.

@zsunberg , can you take a look at the issue on POMDPLinter.jl and provide any feedback/guidance? I don't mind making changes, but I wasn't sure if I was missing something there.

Is anybody aware of another repo that might have slipped by me and is still using Tavis-CI vs GitHub actions?

[dylan-asmar]

I think we are finally complete with this one.
If there are other repos that need to be addressed, please re-open this issue.