-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment on other CI systems #988
Comments
FYI I added GitLabPages plugin to use Documenter.jl in GitLab repository created by PkgTemplates.jl: JuliaCI/PkgTemplates.jl#54 However, it only publishes |
How does GitLab handle tags? Can you run CI on tags? |
Yes. It looks like you can detect it with I think a harder (?) issue is that GitLab pages is not a git branch as in GitHub. You create a directory |
I was just about to create a new issue suggesting adding support for Circle CI.... I think some of the environment variable checks could be done in the CI configuration - e. g. checking for pull requests isn't necessary if you only run the deploy job on the master branch... |
To add to this: GitHub Actions will be generally available soon and it would be nice be able to deploy to GitHub Pages from there. |
Just to second GitHub Actions! We have a nice set of actions in the works right now (https://github.com/julia-actions), and adding one for doc build and deploy would be great. |
Coming across this looking for a solution for versioned Documenter.jl output on Gitlab Pages. Does anyone have any update or idea if this is possible yet? |
This issue is a little dated, so I'll go ahead an close it. We do now have some built-in support for other CI systems: https://juliadocs.github.io/Documenter.jl/stable/man/hosting/#Deployment-systems I don't think the GitLab one supports pushing to GitLab Pages though. |
Currently we officially only support deploying GitHub repositories on Travis CI to GitHub pages.
deploydocs
also relies on Travis-specific environment variables mostly. We should probably support more Git hosting and CI systems (documentation + generalized API where necessary). The following come to mind:In the meantime, there are a few examples of how to work around current limitations:
The text was updated successfully, but these errors were encountered: