Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 39,511
    • Issues 39,511
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,222
    • Merge requests 1,222
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #31367

Closed
Open
Created Aug 29, 2019 by StBriz@stbriz

Gitlab ignores new manual job variable values when you run a job the second time

Summary

After the first launch of a manual job with the input of variables - they are read. But if you abort the job and enter the variables again - they are ignored. Gitlab 12.2

Steps to reproduce

  1. Create MR and start new pipeline.
  2. Start new job with manual variables(see https://gitlab.com/gitlab-org/gitlab-ce/issues/24935)
  3. See\read this environments.
  4. Cancel job OR Wait until it finished and Erase job log
  5. chrome_2019-08-29_17-23-18
  6. Enter the variables, press start, wait and make sure that they will not be in the environment variables

What is the current bug behavior?

I can't read entered variables after retry job(see (4) above).

Edited Jul 20, 2020 by Jason Yavorska
Assignee
Assign to
Time tracking