Skip to content

Minimum upgrade of the builds docs #5398

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 4 commits into from
Mar 5, 2019
Merged

Conversation

humitos
Copy link
Member

@humitos humitos commented Mar 5, 2019

  • Removed a code example section that does not reflects what exactly happens anymore
  • Replace the mention to options from the Admin UI for the config V2 file
  • More specific on the limits

@humitos humitos requested a review from a team March 5, 2019 10:26
@humitos humitos force-pushed the humitos/update-builds-docs branch from c83f65b to ed15959 Compare March 5, 2019 10:29
Copy link
Member

@ericholscher ericholscher left a comment

Choose a reason for hiding this comment

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

Good updates. I think it's useful to explain to the user more how builds work though, not just delete that information.

docs/builds.rst Outdated
if project.requirements_file:
run('pip install -r %s' % project.requirements_file)
build_docs(version=version)
copy_files(artifact_dir)
Copy link
Member

Choose a reason for hiding this comment

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

I wonder if we should still include some updated version of this. I think it's useful for users to get a mental model of what's happening.

Copy link
Member Author

@humitos humitos Mar 5, 2019

Choose a reason for hiding this comment

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

I thought about this, but I came up that it was more complicated to explain in code now considering that we have many options on our config file. In the end, I seemed to me to be more confusing than clarifying.

What about this? I tried to keep some consistency with YAML options.

    update_docs_from_vcs(version)
    config = get_config(project)
    if config.python.install.method.setuptools:
        run('python setup.py install')
    if config.python.install.method.pip:
        run('pip install .')
    if config.python.install.requirement:
        run('pip install -r %s' % config.python.install.requirement)
    build_docs(version=version)
    copy_files(artifact_dir)

It's not 100% accurate, but maybe it's better than removing it. What do you think?

Copy link
Member

Choose a reason for hiding this comment

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

Looks good to me. 👍

@humitos humitos force-pushed the humitos/update-builds-docs branch from dffb58c to a1e33af Compare March 5, 2019 16:45
@humitos humitos requested a review from ericholscher March 5, 2019 16:45
@humitos humitos merged commit 0917fbd into master Mar 5, 2019
@delete-merged-branch delete-merged-branch bot deleted the humitos/update-builds-docs branch March 5, 2019 16:58
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.

2 participants