Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C curvepy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NumerikGang
  • curvepy
  • Issues
  • #1

Closed
Open
Created Aug 18, 2020 by lars.quentin@lars.quentin💬Owner1 of 19 tasks completed1/19 tasks

Creation of a proper CI/CD pipeline

  • Restructuring Folders by the standard proposed by "Serious Python"
  • Different linter pipelines
    • both PEP conformatity. Look into tox with pep8, Pyflakes (or flake8 for PEP 8 integraton) and Pylint
    • Especially PEP 257 for docstrings
  • Maybe use other static analysis tools
    • Codeclimate?
  • documentation generation from Docstrings
    • Check for documentation coverage
    • If possible, CD it to gitlab pages
      • Evaluate it against Read the Docs
    • Create a few overview pages (or create an issue for it)
  • unit testing
  • property based testing with Hypothesis
  • Update README.md accordingly

If I haven't completely read "serious python" by then, create another issue to revisit it once its read

Meta Tasks:

  • Read about best practises python pipelines
  • Read about other possibly helpful toolings
  • Read (and talk) about PyQT integration tests

Later:

  • Add package update to pypi as hook when the project is in a further state.
    • Which intervals are best practise? Especially since PEP 440 isnt compatible with hash based version names. Maybe we can create a Hook for a release tag? When this is done, we can split up the GUI from the library in order to properly use it via pip.

Extra: Great quote for write-up later: https://www.martinfowler.com/articles/continuousIntegration.html

Edited Dec 18, 2020 by lars.quentin
Assignee
Assign to
Time tracking