Skip to content
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 CI functionalities #30

Merged
merged 6 commits into from
May 2, 2020
Merged

Add CI functionalities #30

merged 6 commits into from
May 2, 2020

Conversation

jordiferrero
Copy link
Contributor

Added TravisCI (with only 2 Linux machines) and Coveralls.

Testing devop pipeline service connection endpoint settings.
* Simplified travis pipelines

* Travis leave Linux-only machines

* Add coveralls and coverage

* Add travis and coveralls badges

* Remove Azure pipelines
@jordiferrero jordiferrero merged commit 2704e4b into master May 2, 2020
@jordiferrero jordiferrero deleted the continuous-dev branch May 2, 2020 11:34
@jordiferrero
Copy link
Contributor Author

@ericpre I have set TravisCI and Coveralls for the master branch now, dealing with issue #24.
The Azure pipeline setup gave me many issues so I decided to not implement it now yet.

I've seen the tests you have written for signal_registration all pass.
Now I am able to start writing tests for the other new functions too to increase coverage.

Let me know if you see any errors as it is the first time I deal with CI.

Copy link
Contributor

@ericpre ericpre left a comment

Choose a reason for hiding this comment

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

In this PR, there are two travis builds (#22 and #23) which seems to have been triggered on different condition ("on PR" and "on push") and they should be only one to save CI ressources. Not sure, but it may simply be a setting in the LumiSpy/lumispy project on travis.

Regarding azure pipeline, I can't see what is the issue (access denied). I have used it for a couple of repos and it works fine, providing the service connection is set up. If you think something in https://github.com/hyperspy/ci-scripts should be fixed or better documented, please open an issue there.

.travis.yml Show resolved Hide resolved
matrix:
include:
- name: "Linux, 3.8, pip"
env: export ENV=pip; PIP_SELECTOR="all, tests"
Copy link
Contributor

Choose a reason for hiding this comment

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

If you don't use the "extra" selector for pip install (https://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies), then you don't need to define the PIP_SELECTOR environment variable. In travis/hyperspy, the minimum and optional dependencies are defined in setup.py and we select the ones which are necessary for the travis.

# Install the package
# - pip install --upgrade -e .["${PIP_SELECTOR}"]
- pip install hyperspy
- pip install pytest-cov coveralls coverage
Copy link
Contributor

Choose a reason for hiding this comment

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

To be more tidy, I would define these optional dependencies using extras_require in setup.py and use the appropriate pip extra selector to install lumispy.

@ericpre ericpre mentioned this pull request May 2, 2020
@jordiferrero jordiferrero mentioned this pull request May 6, 2020
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.

None yet

2 participants