Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ jobs:
python: 3.6
- stage: precheck
env: PURPOSE='Dependency Check'
script: ./scripts/dependency/check.sh
script: ./scripts/ci/dependency_check.sh
python: 3.6
# - stage: verify
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't there be more edits to the CI where we install the CLI from the requirements file, such as before running tests?

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah, there's a family of PRs coming as I update the tests and installers. This was just to get started before I unleash all of those, to make sure we are all on the same page in terms of general approach.

Copy link
Member

Choose a reason for hiding this comment

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

So I think the existing script is more self-documenting in terms of what someone should do to fix the issue. I don't see where it calls out which requirements file is the offending one. Also, is this only being run for Python 3 Linux since that is what the CI runs? What about the other requirements files? How will we know they need to be updated?

Copy link
Member Author

Choose a reason for hiding this comment

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

Mind if I address this in a follow-up? I think the points raised here are important, but I think it's more critical that I get started on overhauling the installers to use these dependency lists.

Copy link
Member Author

@marstr marstr Jun 25, 2019

Choose a reason for hiding this comment

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

Tracked in #9795

# env: PURPOSE='Lint Command Table and Help'
Expand Down
16 changes: 16 additions & 0 deletions scripts/ci/dependency_check.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
#!/usr/bin/env bash

set -ev

REPO_ROOT="$(dirname ${BASH_SOURCE[0]})/../.."

# Install everything from our repository first.
find ${REPO_ROOT}/src -name setup.py -type f | xargs dirname | xargs pip3 install --no-deps

pip3 install -r ${REPO_ROOT}/src/azure-cli/requirements.py3.linux.txt

pip3 check
Copy link
Member

Choose a reason for hiding this comment

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

What does a failure look like here? The old script did have a decent amount of amplifying information to make the necessary course of action obvious.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fair question! You can see an example of failure here:
https://travis-ci.org/Azure/azure-cli/jobs/549989807#L800-L803


python3 -m azure.cli --version

python3 -m azure.cli self-test
75 changes: 0 additions & 75 deletions scripts/dependency/check.sh

This file was deleted.

108 changes: 0 additions & 108 deletions scripts/dependency/requirements.Darwin.external.txt

This file was deleted.

110 changes: 0 additions & 110 deletions scripts/dependency/requirements.Linux.external.txt

This file was deleted.

Loading