Skip to content
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

Linux configuration does not match the documentation? #586

Closed
ndw opened this issue Sep 16, 2021 · 6 comments
Closed

Linux configuration does not match the documentation? #586

ndw opened this issue Sep 16, 2021 · 6 comments

Comments

@ndw
Copy link

ndw commented Sep 16, 2021

Issue Type
  • Bug Report
  • Documentation Report
Summary

I followed the web instructions to download and install server and agent 21.2.0 on Linux. It seems to work fine. I'd like to make some global configuration adjustments to the jobs that are run. The docs suggest that configuration can be done in /etc/default/go-agent. In fact, https://cvjt.gitbooks.io/gocd-official-manual/content/installation/install/agent/linux.html suggests that I should configure GO_SERVER_URL in there.

But it doesn't exist.

Environment

Up-to-date Ubuntu Linux 21.04.

@chadlwilson
Copy link
Member

Hi @ndw, thanks for the report. The current documentation is at https://docs.gocd.org/current/installation/install/agent/linux.html#configuring-the-gocd-agent rather than that old Gitbook; although not sure why that is still published. Can you try and see if those suit your needs?

Did you Google to find the old GitBook manual, or was there a link to it somewhere that you came across that we need to correct?

@arvindsv do you have ability to unpublish/remove the old Gitbook docs? Unfortunately the SEO seems to still be strong in this one 😅

@ndw
Copy link
Author

ndw commented Sep 16, 2021

Funny story. I found the real documentation first, but persuaded myself that /usr/share/go-agent/wrapper-config/wrapper-properties.conf didn't exist. Eager to get started, I decided to just ignore the problem and press on. I got a few pipelines running but I found myself copying environment settings over and over, so I went back to find out how to do it globally. Searching the second time took me to the old Gitbook.

On more careful inspection, the wrapper-properties.conf file does exist but because the wrapper-config directory is only readable by root and go, I missed it. Might be worth highlighting the special permissions on that directory in the docs.

Anyway, thanks for pointing me in the right direction. Feel free to close this issue when you're ready.

@chadlwilson chadlwilson transferred this issue from gocd/gocd Sep 22, 2021
@arvindsv
Copy link
Member

@chadlwilson I wasn't even aware we had anything on gitbooks. I'm not sure it was put up by anyone I know ...

I checked and I have no credentials for gitbooks in my password manager. :(

@arvindsv
Copy link
Member

arvindsv commented Sep 22, 2021

Certainly nothing "official" about this. I remember we used to use gitbook a long time ago. But, not the hosted one. We used to publish the static output of the command-line gitbook on docs.go.cd and then docs.gocd.io and then docs.gocd.org. They then deprecated the command-line gitbook app and started pushing gitbook.com, and we moved away from it.

So, I'm not sure who put it up on gitbook.com. I don't recognise "cvjt". But https://github.com/cvjt is a real user, who might have done this?

Seeing that it's mentioning JDK 8 (https://cvjt.gitbooks.io/gocd-official-manual/content/installation/install/server/linux.html), it's from a long time ago.

@chadlwilson
Copy link
Member

Oh, I see. Thanks for the history! I saw the repo history and assumed that was ours, but I did think the domain was weird. Not familiar with gitbook publishing 😬

The links to edit came here rather than to a fork so made a bad assumption.

You are possibly right on your hunch. The other gitbook published under the same user there is a continuous delivery cookbook thingy, and seems some relationship. Let me try my luck contacting the user.

@chadlwilson
Copy link
Member

Closing for now, since not much we can do here :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants