Different comportment between retry button in pipeline

Summary

I realize tests to prepare my project to use Gitlab CI. When I click on the retry button on the pipelines' page of my project I have not the same action than the retry button on the corresponding build.

Steps to reproduce

I have a VM with a user different of the gitlab-runner user. With this user I create a cron which triggers the build. I made a simple .gitlab-ci.yml which makes the "ls" command on a directory only created in the gitlab-runner directory. When the trigger run the "ls" command failed. I made an update on my project (add a space in a file) to launch the build without trigger. And now the build success So I want to retry the precedent build with the Gitlab pipelines interface. With this the test success. I go to the output of the failed test and relaunch the test with the retry button. Here the test fails.

Expected behavior

All retry buttons should make the same thing

Actual behavior

One use the gitlab-runner user and the other the VM user.

Results of GitLab environment info

System information System: Ubuntu 16.04 Current User: gitlab Using RVM: no Ruby Version: 2.3.1p112 Gem Version: 2.6.6 Bundler Version:1.13.5 Rake Version: 10.5.0 Sidekiq Version:4.2.1

GitLab information Version: 8.13.0 Revision: gitlab-ce@053a0a2ccdc74c2fd2ae400fd73675d0e14b1aba Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql URL: http://gitlab-srv.sycomore.corp HTTP Clone URL: http://gitlab-srv.sycomore.corp/some-group/some-project.git SSH Clone URL: gitlab@gitlab-srv.sycomore.corp:some-group/some-project.git Using LDAP: no Using Omniauth: no

GitLab Shell Version: 3.6.6 Repository storage paths:

• default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks/ Git: /opt/gitlab/embedded/bin/git

Runner Version: 1.7.1 Git revision: f896af7 Git branch: 1-7-stable GO version: go1.7.3 Built: Tue, 25 Oct 2016 16:57:56 +0000 OS/Arch: linux/amd64

I make a workaround (or normal way I don't know) by put the trigger in the gitlab-runner user's crontable.

Thanks a lot !