Skip to content

[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

Merged
merged 6 commits into from
Nov 29, 2016

Conversation

dalmia
Copy link
Contributor

@dalmia dalmia commented Nov 11, 2016

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.

@dalmia
Copy link
Contributor Author

dalmia commented Nov 12, 2016

@nelson-liu Were you suggesting something like this?

@nelson-liu
Copy link
Contributor

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.

@dalmia
Copy link
Contributor Author

dalmia commented Nov 13, 2016

Thanks for the feedback. Will get back with the changes.
I did mention creating a PR and updating an existing one. Please let me know if this needs to be clarified more.

@dalmia
Copy link
Contributor Author

dalmia commented Nov 14, 2016

@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
Copy link
Contributor

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``
Copy link
Contributor

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?

@nelson-liu
Copy link
Contributor

thanks for the ping @dalmia, sorry for not following up on this.

@dalmia
Copy link
Contributor Author

dalmia commented Nov 14, 2016

No problem @nelson-liu, will make the desired changes and follow up..

@dalmia
Copy link
Contributor Author

dalmia commented Nov 15, 2016

@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``
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

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
Copy link
Member

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}``
Copy link
Member

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CircleCI

@dalmia
Copy link
Contributor Author

dalmia commented Nov 16, 2016

Waiting for the PR to be merged then!

@jnothman
Copy link
Member

LGTM pending scikit-learn/scikit-learn.github.io#5

@jnothman jnothman changed the title [WIP] DOC adding info about circleci build artifacts [MRG+1] DOC adding info about circleci build artifacts Nov 16, 2016
Copy link
Contributor

@nelson-liu nelson-liu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


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/#'.
Copy link
Contributor

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...

Copy link
Contributor

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

Copy link
Contributor Author

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.

Copy link
Contributor

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
Copy link
Contributor

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...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was using this as my reference for both PR as well as Build #. Thought this has both of them clearly mentioned.

screenshot from 2016-11-16 15 17 08

Do you feel I should be changing it then? Because mentioning both of them makes it a bit messy, I suppose.

Copy link
Contributor

@nelson-liu nelson-liu Nov 17, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whoops, it looks different on my screen
screen shot 2016-11-16 at 10 19 17 pm

I'd prefer the info to be something that would hopefully not change soon? I feel like the URL setup is a lot more static (in the sense that one day they can simply decide to radically change the UI), but this is fine as well.

Copy link
Contributor Author

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.

Copy link
Contributor

@nelson-liu nelson-liu left a 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

@dalmia
Copy link
Contributor Author

dalmia commented Nov 18, 2016

Thanks for the thorough review @nelson-liu

@jnothman
Copy link
Member

Happy with this, but I suspect we should fix #7815 first.

@dalmia
Copy link
Contributor Author

dalmia commented Nov 20, 2016

Please give me a week, busy with exams, and then I'll start working on that issue if it's still open.

@dalmia
Copy link
Contributor Author

dalmia commented Nov 29, 2016

@jnothman Since #7815 is fixed now, is this ready for merge?

@jnothman
Copy link
Member

Yes, I think I can merge this without another +1.

@jnothman jnothman merged commit 6cbef3e into scikit-learn:master Nov 29, 2016
@jnothman
Copy link
Member

Thanks @dalmia!

@dalmia dalmia deleted the 7451 branch November 29, 2016 20:40
sergeyf pushed a commit to sergeyf/scikit-learn that referenced this pull request Feb 28, 2017
Sundrique pushed a commit to Sundrique/scikit-learn that referenced this pull request Jun 14, 2017
NelleV pushed a commit to NelleV/scikit-learn that referenced this pull request Aug 11, 2017
paulha pushed a commit to paulha/scikit-learn that referenced this pull request Aug 19, 2017
maskani-moh pushed a commit to maskani-moh/scikit-learn that referenced this pull request Nov 15, 2017
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

Successfully merging this pull request may close these issues.

Add info about accessing built circleci doc artifacts
3 participants