-
-
Notifications
You must be signed in to change notification settings - Fork 26k
[MRG+1] DOC adding info about circleci build artifacts #7855
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
Conversation
@nelson-liu Were you suggesting something like this? |
thanks for your contribution, I think it would be good to provide info about how to access the built artifacts (with the formula). Make sure you clarify the distinction between PR # and Build # as well, since Build # is the one that matters in this case. |
Thanks for the feedback. Will get back with the changes. |
@nelson-liu Could you please take a review of my changes? Would be really helpful. Thanks. |
@@ -383,6 +383,13 @@ documentation with the maths makes it more friendly towards | |||
users that are just interested in what the feature will do, as | |||
opposed to how it works "under the hood". | |||
|
|||
You may also be asked to show your changes when it's built. When you create | |||
a pull request or make changes in an existing one, circleci automatically | |||
builds the docs. Thus, you can easily view your changes in the built |
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.
hmm, I don't think circleci builds the docs if there are no changes to them?
builds the docs. Thus, you can easily view your changes in the built | ||
artifacts using the following formula: | ||
|
||
``https://{BUILD_NUMBER}-843222-gh.circle-artifacts.com/0//home/ubuntu/scikit-learn/doc/_build/html/stable/index.html`` |
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.
could you explain how to find the build number and note that it isn't the same as the pr # on github?
thanks for the ping @dalmia, sorry for not following up on this. |
No problem @nelson-liu, will make the desired changes and follow up.. |
@nelson-liu Please let me know if there are any more changes to be made. |
automatically builds them. Thus, you can easily view your changes in the built | ||
artifacts using the following formula: | ||
|
||
``https://{BUILD_NUMBER}-843222-gh.circle-artifacts.com/0//home/ubuntu/scikit-learn/doc/_build/html/stable/index.html`` |
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.
With scikit-learn/scikit-learn.github.io#5, we could shorten this URL to http://scikit-learn.org/circle?{BUILD_NUMBER}
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.
I was really hoping we didn't have to put that long a URL in the docs. This makes it so much cleaner. Thank you for letting me know. I'll make the change.
@@ -383,6 +383,17 @@ documentation with the maths makes it more friendly towards | |||
users that are just interested in what the feature will do, as | |||
opposed to how it works "under the hood". | |||
|
|||
You may also be asked to show your changes when it's built. When you create | |||
a pull request or make changes in an existing one modifying the docs, circleci |
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.
circleci -> CircleCI
automatically builds them. Thus, you can easily view your changes in the built | ||
artifacts using the following formula: | ||
|
||
``http://scikit-learn.org/circle?{BUILD_NUMBER}`` |
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.
(Btw, this doesn't work yet. Awaiting review.)
|
||
``http://scikit-learn.org/circle?{BUILD_NUMBER}`` | ||
|
||
Note: When you visit the details page of the circleci tests, you can find your |
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.
CircleCI
Waiting for the PR to be merged then! |
LGTM pending scikit-learn/scikit-learn.github.io#5 |
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.
scikit-learn/scikit-learn.github.io#5 is really neat btw, thanks @jnothman
|
||
Note: When you visit the details page of the CircleCI tests, you can find your | ||
BUILD_NUMBER mentioned as 'build #' which is different from your pull request number | ||
present as 'pull/#'. |
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.
your pull request number present as
-> your pull request number, which is presented as...
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.
i found pull/#
quite confusing for some reason, where did you get the info from? Perhaps clarify that it's the PR number on github
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.
@nelson-liu Please let me know if the reference I provided clears it up or should I be making any changes. Thanks.
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.
yes, it's good enough. can you fix the typo/grammar, though?
``http://scikit-learn.org/circle?{BUILD_NUMBER}`` | ||
|
||
Note: When you visit the details page of the CircleCI tests, you can find your | ||
BUILD_NUMBER mentioned as 'build #' which is different from your pull request number |
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.
i can't find where on the CI results page it says 'build #'...perhaps try to clarify this? maybe mention that it's in the circleci URL itself? that's a bit clunky, though...
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.
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.
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.
You are certainly correct there and I am also confused as to why we have different screens. Just that searching in the URL seems a bit clumsy, and this one is a lot cleaner. As you say, let's stick with this for now and reiterate if needed in the future.
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.
seems good to me now, thanks @dalmia
Thanks for the thorough review @nelson-liu |
Happy with this, but I suspect we should fix #7815 first. |
Please give me a week, busy with exams, and then I'll start working on that issue if it's still open. |
Yes, I think I can merge this without another +1. |
Thanks @dalmia! |
Reference Issue
Fixes #7451
What does this implement/fix? Explain your changes.
Added the information about accessing the circleci build artifacts when making doc changes.
Any other comments?
Still haven't included as to how the artifacts should be accessed. Should the formula mentioned in the thread be included? If not, then we need some way of letting them know how to access it or else adding this won't make much of a difference.