# Detected dubious ownership in repository with Jenkins upgrade

**URL:** <https://community.jenkins.io/t/detected-dubious-ownership-in-repository-with-jenkins-upgrade/6182>\
**Category:** Ask a question\
**Tags:** question, docker\
**Created:** [March 9, 2023, 3:06pm UTC](https://community.jenkins.io/t/detected-dubious-ownership-in-repository-with-jenkins-upgrade/6182 "2023-03-09T15:06:53Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jonheckman](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/jonheckman/32/3585_2.png) [@jonheckman](https://community.jenkins.io/u/jonheckman)\
**Post date:** [March 9, 2023, 4:25pm UTC](https://community.jenkins.io/t/detected-dubious-ownership-in-repository-with-jenkins-upgrade/6182/2 "2023-03-09T16:25:33Z")

</div>

Update, I wanted to try to see if maybe I could find a solution that wasn’t a drastic one just to see what would happen.

So in the agent dockefle I set:

```auto
git config --global --add safe.directory '*'

```

This fixed the issue for a freestyle project but not for the pipeline.  
Both of the jobs are cloning the same repo and has the same configuration for the git checkout except for pipeline vs freestyle.

The error message for the pipeline has not changed so I am fully at a loss now.

---

_[View the full topic](https://community.jenkins.io/t/detected-dubious-ownership-in-repository-with-jenkins-upgrade/6182)._