Le mercredi 12 avril 2017, 22:05:02 CEST Michael Osipov a écrit :
> Am 2017-04-12 um 08:54 schrieb Hervé BOUTEMY:
> > yes, that's what I tried to say (there were 4 branches iin MNG-6169/)
> > 
> > I finally renamed the 4 branches and replaced / with _: now there won't be
> > any stupid failure on Jenkins, and I just checeked that the github mirror
> > is up to date also
> 
> Hell, seriously? You have renamed my dev branches without talking to me
> first?
yes, I fixed a lot of broken tools (many Jenkins jobs, github mirror) without 
breaking anything from your work

> you should have raised this with INFRA because they have to have
> a look at the shortcoming.
how do you intend to fix Jenkins clones?
renaming is easy, fixes a lot of things and does not break anything: I'm 
pragmatic, I prefer an easy workaround now instead of a fight against I don't 
know how many tools, in how much time

> 
> > issue fixed
> > and not to the team: warning about / use in branch names, that may not be
> > such a good idea
> 
> Not at all, using slashes to separate branches are a common approach.
perhaps nobody starts by creating a branch named "mybranch" then renaming to 
"mybranch/subbranch"
And when some unexpected failure happens, that causes tons of Jenkins 
failures, we need to have a quick fix: I did it

Regards,

Hervé


> 
> > Le mercredi 12 avril 2017, 06:08:55 CEST Stephen Connolly a écrit :
> >> I think it was the use of nested name that contributed too:
> >> origin/MNG-6169/updated-MCOMPILER
> >> 
> >> On Wed 12 Apr 2017 at 05:47, Karl Heinz Marbaise <[email protected]> 
wrote:
> >>> Hi Hervé,
> >>> 
> >>> On 12/04/17 04:35, Hervé BOUTEMY wrote:
> >>>> 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?
> >>> 
> >>> ~/ws-git/apache/maven (master)$ git fetch --prune origin
> >>> 
> >>>  From https://git-wip-us.apache.org/repos/asf/maven
> >>>  
> >>>   x [deleted]         (none)     -> origin/MNG-6169/all-updated
> >>>   x [deleted]         (none)     ->
> >>> 
> >>> origin/MNG-6169/not-updated-MJAR-MCOMPILER
> >>> 
> >>>   x [deleted]         (none)     -> origin/MNG-6169/updated-MCOMPILER
> >>>   x [deleted]         (none)     -> origin/MNG-6169/updated-MJAR
> >>>   x [deleted]         (none)     -> origin/MNG-6185
> >>>   x [deleted]         (none)     -> origin/MNG-6198
> >>> 
> >>> remote: Counting objects: 93, done.
> >>> remote: Compressing objects: 100% (32/32), done.
> >>> remote: Total 47 (delta 16), reused 0 (delta 0)
> >>> Unpacking objects: 100% (47/47), done.
> >>> 
> >>>     08f3c76..567af0d  master     -> origin/master
> >>>   
> >>>   * [new branch]      MNG-6209_multiple-build-extensions ->
> >>> 
> >>> origin/MNG-6209_multiple-build-extensions
> >>> 
> >>> That helped me...
> >>> 
> >>> Kind regards
> >>> Karl Heinz
> >>> 
> >>>> Regards,
> >>>> 
> >>>> Hervé
> >>>> 
> >>>> [1]
> >>> 
> >>> https://builds.apache.org/job/core-integration-testing-maven-3-jdk-1.8/1
> >>> 00
> >>> 7/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> ([email protected]
> >>>>> <mailto:[email protected]>: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: [email protected]
> >>> For additional commands, e-mail: [email protected]
> >>> 
> >>> --
> >> 
> >> Sent from my phone
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to