I suppose this is tied to lots of intermittent failures on git clone updates that Jenkins has [1] error: cannot lock ref 'refs/remotes/origin/MNG-6169/all-updated': 'refs/ remotes/origin/MNG-6169' exists; cannot create 'refs/remotes/origin/MNG-6169/ all-updated' ! [new branch] MNG-6169/all-updated -> origin/MNG-6169/all-updated (unable to update local ref)
This creation of branches in MNG-6169/ after having removed MNG-6169 has bad impact on every clone that does not correctly prune remote references: I suppose the github cloning script has the same issue. I see 2 options: 1. try to fix the github cloning script (I don't know where it is) and any other failing update (I'm fighting with Jenkins on this for a few days, since it seems it keeps copies every here and there...) 2. rename MNG-6169/* branches to something like MNG-6169_* to workaround the issue Any other idea? Regards, Hervé [1] https://builds.apache.org/job/core-integration-testing-maven-3-jdk-1.8/1007/console Le lundi 10 avril 2017, 22:42:47 CEST Mario Krizmanić a écrit : > Hi, > > Could one check and update Github's mirror: https://github.com/apache/maven > <https://github.com/apache/maven> (g...@github.com > <mailto:g...@github.com>:apache/maven.git) > > The last commit in the master branch is 87cf1ee while the last one in the > origin's master is 08f3c76a. > > Thanks, > Mario --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
