On 11/12/2013 03:13 PM, Luca Milanesio wrote:
d) The repos with not enough history or depth
None of those repositories were in the list of the 186 ones mentioned: can't
find any of them on my logs.
This means that in the event time window captured by GitHub there wasn't any
activity related to my account or any activity at all.
Maybe you have already explained this elsewhere, but how did you come up
with the list of 186 repositories in the first place? Is that what you
had on your Gerrit instance when it did "git push -f"?
The repositories listed under "[WARNING] events don't go back far
enough" are repositories that do report some events but none before the
Nov 9th. Thus there's a suspicion that some of those event history was
already lost, hence the warning. There are only three, and I think all
is accouned for:
- awseb-deployment-plugin (created yesterday)
- backend-git-pushf-finder (created today)
- websphere-deployer-plugin (created today)
Repositories listed under "[INFO ] no events in" are more numerous. I
agree with you that most likely there has been no activities for these
repositories in quite some time. For now I think we'd have to assume
that no commits were lost on them.
(If we have more cycles we could check the last commit in these repos to
really verify that none of them contain any new commits)
--- * ---
My suggestions:
a) I guess this is due of some initial 'git push' made for recovering
the situation at the timethat GitHub took the snapshot (the post-push
are mostly incorrect, not the pre-push)
Agreed.
b) I will make further analysis on the 4 exceptions
c) Those branches are definitely to be restored, using the pre-push SHA1 from
Kohsuke's list
d) Possibly cross-check with the plugins maintainers, but they should be OK and
not require fixing.
Yes, let's list up the repos of (b)+(c) above and find maintainers.
--- * ---
Any other thoughts / feedback ?
Luca.
On 12 Nov 2013, at 22:34, Luca Milanesio <luca.milane...@gmail.com> wrote:
I will cross-check with the list provided by GitHub.
(was doing a similar exercise on the suspect 54 repos anyway)
Luca.
On 12 Nov 2013, at 21:27, Kohsuke Kawaguchi <k...@kohsuke.org> wrote:
As I suggested in the e-mail thread, I've written a little program that looks
at the GitHub events API to figure out the push activities from Luca, and
assembled a list of refs and affected commits. The result is in [1].
The exact code is at [2], and I invite others to check my sanity. The basic
idea is to look at the events time line, and find the problematic push.
The meaning of the output is:
repository name, before, after, ref
"before" is the commit that's lost.
I'm going to compare this with the CSV file from GitHub now to see if there's a
pattern of discrepancy here.
[1] https://gist.github.com/kohsuke/7438914
[2]
https://github.com/jenkinsci/backend-git-pushf-finder/tree/eeb462c47dbaa45f2170ccada487eed33da81193
--
Kohsuke Kawaguchi http://kohsuke.org/
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
