Download button on pipeline page disappears after expire_in is passed for artifacts with paths containing special characters
Summary
On CI/CD > Pipelines page, artifacts download button for the last successful pipeline with latest artifacts disappears after expire_in
is over if the artifacts path contains special characters. This is with Keep artifacts from most recent successful jobs
feature enabled. It's possible to download artifacts from the job page though.
Example path I tried: Release_\*
.
Steps to reproduce
- Create a CI file with the following contents:
artifact:
stage: deploy
script:
- touch Release_*
artifacts:
expire_in: '10'
paths:
- Release_\*
- You'll find that the artifacts download button disappearing after 10 seconds on the Pipelines page.
Example Project
Sample project: https://gitlab.com/psureshbabu/artifacts-test-support
Pipeline page: https://gitlab.com/psureshbabu/artifacts-test-support/-/pipelines
What is the current bug behavior?
Artifacts download button disappears after expire_in
is over no matter if the artifacts actually exist.
What is the expected correct behavior?
Artifacts download button should be available if the artifacts exist.
Relevant logs and/or screenshots
Pipeline page:
Job page:
Output of checks
This bug happens on GitLab.com
GitLab SM version: 13.10.2
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Ubuntu 18.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.7.2p137 Gem Version: 3.1.4 Bundler Version:2.1.4 Rake Version: 13.0.3 Redis Version: 6.0.10 Git Version: 2.29.0 Sidekiq Version:5.2.9 Go Version: unknown GitLab information Version: 13.10.2-ee Revision: cc4224220e6 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 12.5 URL: https://ps-gitlab.sr.gitlab.support HTTP Clone URL: https://ps-gitlab.sr.gitlab.support/some-group/some-project.git SSH Clone URL: git@ps-gitlab.sr.gitlab.support:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 13.17.0 Repository storage paths: - default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 13.17.0 ? ... OK (13.17.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes Number of Sidekiq processes (cluster/worker) ... 1/1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Reply by email is disabled in config/gitlab.yml
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... skipped (no tmp uploads folder yet) Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 2/1 ... yes 1/2 ... yes 1/3 ... yes 1/4 ... yes 1/5 ... yes 1/6 ... yes 3/7 ... yes 1/8 ... yes 1/9 ... yes 1/10 ... yes 1/12 ... yes Redis version >= 4.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (2.7.2) Git version >= 2.29.0 ? ... yes (2.29.0) Git user has default SSH configuration? ... yes Active users: ... 1 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 7.x (6.4 - 6.x deprecated to be removed in 13.8)? ... skipped (elasticsearch is disabled)
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished