-
Notifications
You must be signed in to change notification settings - Fork 347
Add APM to shared versioning #1187
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
Add APM to shared versioning #1187
Conversation
|
I'm going to try deprecating the |
|
Well that's cool. Updating the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but for a little extra paranoia lets rebuild everything and make sure nothin weird happened.
@elasticmachine, run elasticsearch-docs/doc rebuild
|
@elasticmachine, run elasticsearch-docs/doc rebuild |
|
@elasticmachine, run elasticsearch-ci/docs rebuild |
|
I noticed these in the last run, actually: |
|
@nik9000 SMART. Thank you for doing that. I'll look into those links. |
|
So this is really interesting. These broken links are in the stack docs, but they're only there because they're included via a tagged region. The links really live in the APM Overview. Specifically, this page, where they work 🤔. For some reason, the attributes for |
|
Ahhh, this could be because the stack-docs only just started using the shared version file at 4:29pm GMT yesterday (elastic/stack-docs#512) and @nik9000 started the rebuild test on this PR at 3:55pm GMT yesterday. I think if I rebuild again this should be fixed. @elasticmachine, run elasticsearch-ci/docs rebuild |
|
@elasticmachine, run elasticsearch-ci/docs rebuild |
|
Alright, I'm officially stuck. This PR build keeps failing on the ESS docs, which should be unrelated: I ran a rebuild in elastic/docs and it passed with flying colors: https://elasticsearch-ci.elastic.co/job/elastic+docs+master+build/4946/console |
888b47e to
ba98b4c
Compare
|
Have you tried merging master into your PR? Sometimes PR branches to docs
get out of date in funny ways that cause book builds to fail.
…On Tue, Sep 17, 2019, 07:28 Brandon Morelli ***@***.***> wrote:
Alright, I'm officially stuck. This build keeps failing on ESS:
ERROR building Elasticsearch Service - Hosted Elasticsearch and Kibana branch release-ms-25
I ran a rebuild in elastic/docs and it passed with flying colors:
https://elasticsearch-ci.elastic.co/job/elastic+docs+master+build/4946/console
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1187?email_source=notifications&email_token=AABUXIWF36HNJNXATMP3MFLQKC5MNA5CNFSM4IWNHTL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD64GWMI#issuecomment-532179761>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABUXIRAY2Z3HUZWYEEDUPDQKC5MNANCNFSM4IWNHTLQ>
.
|
|
🤦♂ Yeah, that worked. Going to do one more rebuild just to be safe, but the recent ci/docs was just green. @elasticmachine, run elasticsearch-ci/docs rebuild |
|
Actually, it didn't work. Same ESS failure: https://elasticsearch-ci.elastic.co/job/elastic+docs+docs+pull-request/271/console |
|
@elasticmachine, run elasticsearch-ci/docs rebuild |
|
Nik's fix worked! Now the problem is about 300 broken links due to unresolved attributes. I believe this is happening because APM Server isn't yet using the shared version file (where the attributes are described). |
|
I'm not going to remove the I'm taking this PR back to its roots by simply adding APM Server and APM Agents to the shared versioning files. |
|
@elasticmachine, run elasticsearch-ci/docs rebuild |
4466ae9 to
26eb41c
Compare
|
@elasticmachine, run elasticsearch-ci/docs rebuild |
|
After many, many attempts at this, the docs/ci rebuild is finally green. |
apm_server_versionAllows us to finally stop linking tocurrentversions of all APM Agent documentation 🎉Moves APM Agent version attributes to the shared version files.