docs-travis-ci-com
docs-travis-ci-com copied to clipboard
Subversion and Git details missing
There does not seem to be any documentation on which versions of Git and Subversion are provided with each OS.
It does for git, at least, right? 2.28.0 Not for subversion, though.
I think i could look at solving this. Could you please show me the way? Like how to proceed and prerequisites??
Well, you need to find out versions for different runners. You can just use svn --version
probably in any of the phases in the configuration file, for any OS. Then you need to do a PR to these pages, to add the versions you've found that way.
@JJ okay. I am going to set up the project first and will ask you about it again. As what you told me is over my head right now. Sorry for being a pest.
Hey, just a guest here, same as you. But I can be of help, by all means.
abhishek@abhishek-ubuntu:~$ bundle install --binstubs
[DEPRECATED] The --binstubs option will be removed in favor of `bundle binstubs --all`
Could not locate Gemfile
abhishek@abhishek-ubuntu:~$ bundle binstubs --all
Could not locate Gemfile or .bundle/ directory
abhishek@abhishek-ubuntu:~$ bundle -v
Bundler version 2.2.16
abhishek@abhishek-ubuntu:~$ jekyll --version
jekyll 3.8.6
I tried to follow the documentation and it's not working out. No answer on the web either. @JJ @sebbASF
I am afraid I am not totally sure why you want to do this. You don't need to install the whole documentation anyway; probably the easiest is to just simply edit the pages you're interested in.
you need to find out versions for different runners. You can just use
svn --version
probably in any of the phases in the configuration file, for any OS. Then you need to do a PR to these pages, to add the versions you've found that way.
could you please tell me how should I start? I thought first running the project and following the readme file would be a way but now I dont get it.
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues