Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46,663
    • Issues 46,663
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,514
    • Merge requests 1,514
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #225914
Closed
Open
Issue created Jul 03, 2020 by Grant Young@grantyoungDeveloper

Rename default Browser Performance Testing job name (breaking change)

This is a follow up from !34634 (merged).

The default job name for Browser Performance Testing is currently named just performance in it's template. After several attempts in the MR to change it to the intended browser_performance it was concluded to not be feasible currently to do this as well as maintain backwards compatibility with users who are using the performance job currently.

In addition to this we should also update the PERFORMANCE_DISABLED AutoDevOps environment variable to BROWSER_PERFORMANCE_DISABLED.

As such, we'll look to do this later as a breaking change making sure to notify users with enough time.

Edited Jul 09, 2020 by Grant Young
Assignee
Assign to
Time tracking