Please provide more details so that others can duplicate the bug. I attempted to duplicate the bug with the following steps:

1. Create a freestyle job that uses a git repository and reports the environment variables after checkout
2. Run that freestyle job
3. Confirm the environment variables are reported

More details are in the commit message for the job that performs that check.

I see the environment variables output for my job as:

  GIT_AUTHOR_EMAIL=mwaite@mark-pc2.markwaite.net
  GIT_AUTHOR_NAME=Jenkins Docker User
  GIT_BRANCH=origin/master
  GIT_COMMIT=42fbc34cc227fd1514710d54e790cb6489c20282
  GIT_COMMITTER_EMAIL=mwaite@mark-pc2.markwaite.net
  GIT_COMMITTER_NAME=Jenkins Docker User
  GIT_PREVIOUS_COMMIT=42fbc34cc227fd1514710d54e790cb6489c20282
  GIT_URL=https://github.com/jenkinsci/git-client-plugin

Please provide more details to duplicate the problem you're seeing. I don't know how the job looks after DSL generates a freestyle job.

I tested as you did it (New Freestyle Job(by hand), only a git repo, ...) and the git-variables are still missing.

What can I do to provide you more information?

The picture of the environment variables screen was the key item. I've never used that page to see the environment variables which were set during the job.

The git plugin injects environment variables into the job but does not inject them in such a way that they are visible in that page. My example job shows that the environment variables are set by the plugin and are usable by "bat", "shell" and "cross-platform shell" steps. However, my "Environment Variables" page for each job does not show those variables.

Since the URL to that environment variables page is called "injectedEnvVars", I assume the git plugin is adding environment variables to the job by a different technique than other plugins.

Can you describe your use case more deeply? Are you reading the values of those environment variables from a program later?

It was because my job-sciprt shows that the variables were empty, so I was looking for the list to check if they where set, because in the past they where listed

But in the now it shows that I access the variables wrong. Every thing works as expected, except of the view as you find out.

If I change jobs and something went wrong with variables this is one of my first point to look at.

Any idea when the last version was that showed those environment variables in that page?

I'm not aware of any changes in the git plugin that would result in such a change in the environment variables page.

I found that the different is the build-step 'Inject environment variables' cause the git variables to show appear on the list.

Thanks for the investigation!