Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
pyvallex
pyvallex
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 57
    • Issues 57
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 3
    • Merge Requests 3
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jonathan L. Verner
  • pyvallexpyvallex
  • Issues
  • #94

Closed
Open
Opened Jul 08, 2020 by Anna Vernerová@Ansa211Maintainer

Do we still need the linexe CI job?

I suppose the point of the linexe CI job was to create a downloadable artifact such as https://gitlab.com/Verner/pyvallex/-/jobs/628656118/artifacts/browse/dist/

Now that pyvallex has been turned into a python package, do we still need the job? Is there any use for the created artifacts?

Related question: how often do we intend to create a new version of the vallex-tools python package? Should we add a CI job that updates the minor version of the package number by one and creates a new version with each commit (or, possibly, with each commit such that the commit message contains some defined keyword such as "RELEASE")?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: Verner/pyvallex#94