There is no information in the Merge Request description about environments extracted from the tag

Summary

In the description of the accepted Merge Request, we cannot see the environments for which our commit from the tag was pumped out, but we see the environments for which the rollout was NOT from the tag.

Steps to reproduce

Create .gitlab-ci.yml with the following contents:

stages:
  - test
  - build
  - deploy

test:
  stage: test
  script: echo "Running tests"
  tags:
    - build

build:
  stage: build
  script: echo "Building the app"
  tags:
    - build

deploy_staging:
  stage: deploy
  script:
    - echo "Deploy to staging server"
  environment:
    name: staging
    url: https://staging.example.com
  only:
  - master
  tags:
    - build

master:
  stage: deploy
  script:
    - echo "Deploy to master"
  environment:
    name: master
  only:
    - tags
  tags:
    - build

ea:
  stage: deploy
  script:
    - echo "Deploy to ea"
  environment:
    name: ea
  only:
    - tags
  tags:
    - build

stable:
  stage: deploy
  script:
    - echo "Deploy to stable"
  environment:
    name: stable
  only:
    - tags
  tags:
    - build

Let's create a Merge Requst, after which we will accept this Merge Request in master and we will have the deploy_staging stage executed. In the Merge Request description, we will see that this MP was deflated into the staging environment:

mr

After that, we will create a new tag from the master branch and all the other stages of stable, ea, master will be executed with rolling out into the environment of stable, ea, master.

However, in the description of the Merge Request we will not see that this Merge Request was pumped into these environments.

Example Project

https://gitlab.com/andrey.sidorov/test-ci/

What is the current bug behavior?

The accepted Merge Request does not display the environment where the tag with the given commit went.

What is the expected correct behavior?

The accepted Merge Request should display the environment where the tag with the given commit went.

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:         Ubuntu 16.04
Current User:   git
Using RVM:      no
Ruby Version:   2.6.3p62
Gem Version:    2.7.9
Bundler Version:1.17.3
Rake Version:   12.3.2
Redis Version:  3.2.12
Git Version:    2.21.0
Sidekiq Version:5.2.7
Go Version:     unknown


GitLab information
Version:        12.1.6
Revision:       4016bcac51d
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     10.7
URL:            https://gitlab.example.com
HTTP Clone URL: https://gitlab.example.com/some-group/some-project.git
SSH Clone URL:  git@gitlab.example.com:some-group/some-project.git
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers: saml


GitLab Shell
Version:        9.3.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 

sudo gitlab-rake gitlab:check SANITIZE=true


Checking GitLab subtasks ...


Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... OK (9.3.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


Access to /var/opt/gitlab/.ssh/authorized_keys: 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 ... 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? ... yes
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: ...
...
all migration ok
...


Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.3)
Git version >= 2.21.0 ? ... yes (2.21.0)
Git user has default SSH configuration? ... yes
Active users: ... 88


Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished