Indeed, looking at https://api.github.com/repos/jenkinsci/scoring-load-balancer-plugin/events, I see that Luca's push had changed master from 0ca553b933521ba82746a491b3c29d8c6cc2ae89 to 634609e0e7ffe754f1ec3fed8871a89f7403508b.
So there's something wrong with the list provided by GitHub... On 11/12/2013 04:16 AM, Ikedam wrote:
Unfortunately, there may be something wrong with this list... scoring-load-balancer-plugin have same orig_master and forced_master, 634609e. And the version in its pom.xml is 1.0.1-SNAPSHOT. But I have released scoring-load-balancer-1.0.1 last week. The latest commit should be: https://github.com/jenkinsci/scoring-load-balancer-plugin/commit/0ca553b933521ba82746a491b3c29d8c6cc2ae89 There may be same problems in other plugins if they are updated in a week. On Tuesday, November 12, 2013 7:22:55 AM UTC+9, lucamilanesio wrote: Good news from GitHub: they have extracted the full list of SHA-1 before the forced push ! Many thanks to Nathan Witmer :-) See below the full CSV with the SHA-1. He created as well a branch named 'recovery' that points to the candidate point for restoring the master branch. Hope this will help to sort out the remaining repos. Luca. > Hi Luca. > > Oh man, that sinking feeling! > > But, no worries: I've gone through each of the repos listed above and done the following: > > * retrieved the SHA for the previous `master` before you force-pushed > * created a branch called `recovery` pointing to each former master > > In some cases, these are the same. > > I can go further and reset the master refs to their former shas if you'd like, or you can recover these yourself. To do so, in each repo: > > $ git fetch > $ git checkout master > $ git reset --hard origin/recovery > $ git push --force origin master > > I've attached a csv containing the shas (former master and forced master) for each branch, for your reference. > > Good luck! > > Nathan. -- 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.
