Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • eossr eossr
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 17
    • Issues 17
    • 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
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ESCAPE2020ESCAPE2020
  • WP3WP3
  • eossreossr
  • Issues
  • #106
Closed
Open
Issue created Dec 05, 2022 by Vuillaume@vuillaumeOwner

publication includes build directories

Bug description and behavior

See https://zenodo.org/record/6826881

it includes build, eggs...

Expected behavior?

The repository content is published as is

Possible fixes

  1. git reset --hard HEAD && git clean -fd in snippet?
  • this requires adding git in the docker image
  • need to be careful with modified files during CI
  • check that HEAD is indeed the latest tag
  1. using gitlab zipball https://python-gitlab.readthedocs.io/en/stable/gl_objects/projects.html?highlight=zip#examples
  • but this is tight to gitlab => make a eossr-gitlab-release command?
Edited Dec 16, 2022 by Vuillaume
Assignee
Assign to
Time tracking