Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • dbispipeline dbispipeline
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Institut für Informatik
  • dbisdbis
  • softwaresoftware
  • dbispipelinedbispipeline
  • Issues
  • #53
Closed
Open
Issue created Nov 06, 2020 by User expired@csak8736Maintainer

Make script for releasing

releasing the software should be done automatically, and should include:

  1. check if the repo is clean and ready to release
  2. bump the version of the software (minor or patch, according to the command call)
  3. commit setup.cfg and setup.py with the commit message release vXXX, where XXX is the new version
  4. create a tag with the name 'vXXX'
  5. push content and tags
  6. run make release to push to pypi

Example: pipenv run release patch

Personally, I'd like to prevent accidentally releasing a version by running a command twice. This could be prevented by skipping bumping the version automatically (step 2), or more difficultly by checking whether there are commits since the last version. What do you think?

Assignee
Assign to
Time tracking