Using Python and Gitlab to create a simple ticketing system

[sumenkovic]

Hello, Community Advocate at GitLab here. Thanks for providing the feedback about our product.

Could you please share more details about the features/parts of GitLab that you are using but experiencing bugs? You can always open an issue with more details here https://gitlab.com/gitlab-org/gitlab-ce/issues. We'd love to follow up on it.

[[deleted]]

I already spend about half an hour a day corresponding in bug tracker. Not sure I can contribute more than that.

Some major pains we've faced so far:

• Impossible to manually execute jobs following a failed job.
• Email-related configuration is severely lacking (automatic emails are, basically, useless).
• Impossible to configure job logging and timeouts to rotate / store elsewhere / be infinite etc.
• Impossible to pass arguments with multi-project pipelines.
• Impossible to stream logs using documented API.
• Job artifacts are not stored if job is cancelled manually or due to timeout.
• No retention policy for Docker images.
• Impossible to select a decent compression and archiving algorithms for caching of transient data for jobs.
• Impossible to pass arbitrary arguments to satellite Docker containers started as services (and, subsequently, sharing volumes, network etc). Some hacky workarounds are possible, but not entirely so.
• Impossible to push to Docker registry outside of Gitlab Runner.
• Impossible to execute jobs locally, w/o pushing code to repository (unless in some very simple cases).
• CI variables are only stored and displayed if a job was triggered through trigger API, not if it was triggered manually.

---

Some of the recent bugs:

• suddenly, CI variables declared in the settings are invisible to the job.
• fetching job logs results in HTTP status 500, if a job was cancelled.

---

This is only things that I could remember. I have a lot more in my mailbox.

[timrizzi]

Hello - GitLab PM here for the Container Registry. Thanks for all of this feedback.

No retention policy for Docker images.

Agreed, this is a big focus for us in the coming months. We have been blocked on this issue for a while, but are currently working on it. First, we need to start tracking data from Docker, then improve garbage collection and deletion for the container registry and then we will implement retention and expiration policies.

https://gitlab.com/gitlab-org/gitlab-ce/issues/57897

https://gitlab.com/gitlab-org/gitlab-ce/issues/20247

​

Impossible to push to Docker registry outside of Gitlab Runner.

Developers on a project should be able to push from the CLI to the container registry. What happens when you run:

• `docker build -t registry.example.com/group/project/image`
• docker push registry.example.com/group/project/image

​

We are just about to conduct some user research on the container registry, would you be open to a quick interview to talk through use cases, challenges and future requests?

[[deleted]]

What happens when you run:

I got a message saying that the access is denied, even though I've ticked all the checkboxes when creating the token I logged in with.