The git-plugin is missing at least one commit:
commit 1e894cd9ce564c2ed8e1283b091b1105512efcdd
Author: Stephen Connolly <...>
Date: Fri Nov 8 15:51:49 2013 +0000
switch to c:select to support in-place addition of credentials
On Tuesday, November 12, 2013 3:27:33 PM UTC-5, lucamilanesio wrote:
>
> I'm just checking using the GitHub GUI, will not push anything :-)
>
> I am trying the get the final list of repos that would need further
> fixing. Then would leave to the plugin maintainer to judge which is the
> latest, as it was not detected by the GitHub support team.
>
> Luca
> ---------
> Sent from my iPhone
> Luca Milanesio
> Skype: lucamilanesio
>
>
> On 12 Nov 2013, at 20:01, Slide <slide...@gmail.com <javascript:>> wrote:
>
> Please don't run any more scripts :-). The email-ext-plugin is just fine,
> please take it off your list for needing recovery.
>
>
> On Tue, Nov 12, 2013 at 12:35 PM, Luca Milanesio
> <luca.mi...@gmail.com<javascript:>
> > wrote:
>
>> I've checked as well and tfs-plugin was in the list of recovered repos
>> but I can't find the recovery branch either:
>> https://api.github.com/repos/jenkinsci/tfs-plugin/branches/recovery
>>
>> Will run a quick script for assess the situation with the others.
>>
>> In the meantime I've extracted the lists of repos with pre-push and
>> post-push SHA1 are the same (54 repos):
>> artifactory-plugin
>> branch-api-plugin
>> build-timeout-plugin
>> ci-game-plugin
>> clearcase-plugin
>> clearcase-ucm-plugin
>> collabnet-plugin
>> collapsing-console-sections-plugin
>> compress-artifacts-plugin
>> copy-project-link-plugin
>> copy-to-slave-plugin
>> credentials-plugin
>> crowd-plugin
>> crowd2-plugin
>> disable-failed-job-plugin
>> ec2-plugin
>> email-ext-plugin
>> gerrit-trigger-plugin
>> git-chooser-alternative-plugin
>> gitbucket-plugin
>> groovy-postbuild-plugin
>> humbug-plugin
>> jacoco-plugin
>> job-poll-action-plugin
>> jobConfigHistory-plugin
>> json-lib
>> leiningen-plugin
>> logfilesizechecker-plugin
>> mailer-plugin
>> maven-hpi-plugin
>> maven-info-plugin
>> nerrvana-plugin
>> next-build-number-plugin
>> next-executions-plugin
>> perforce-plugin
>> pitmutation-plugin
>> promoted-builds-plugin
>> prqa-plugin
>> rvm-plugin
>> scm-api-plugin
>> scm2job-plugin
>> scoring-load-balancer-plugin
>> selenium-tests
>> skype-im-plugin
>> ssh-agent-plugin
>> ssh-credentials-plugin
>> ssh-slaves-plugin
>> stashnotifier-plugin
>> subversion-plugin
>> swarm-plugin
>> transifex-plugin
>> vstestrunner-plugin
>> warnings-plugin
>> ws-cleanup-plugin
>>
>> Will check now their master SHA1 and compare with the one "post-push" to
>> see if the plugins maintainers have already pushed it or not.
>>
>> Luca.
>>
>> On 12 Nov 2013, at 14:04, Olivier Dagenais
>> <olivier....@gmail.com<javascript:>>
>> wrote:
>>
>> Hi,
>>
>> I learned of this situation last night. I'm the [current] maintainer of
>> the tfs-plugin and I don't see commits since I released version 2.0, nor do
>> I see a 'recovery' branch at https://github.com/jenkinsci/tfs-plugin
>>
>> The machine I last made release 3.0.1 from has a clone with the 24
>> missing commits, and it looks like I should be able to just push them.
>>
>> I don't want to interfere with any mass-fixing attempts discussed here
>> (especially by Kohsuke), so please let me know if I should proceed.
>>
>> Thanks!
>> - Oli
>> P.S.: I'm the one who released the last rake-plugin (which sort of makes
>> me a maintainer), but the last commit to that repo was long enough ago that
>> it wasn't affected.
>>
>> On Monday, November 11, 2013 5:22:55 PM UTC-5, 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-de...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>> --
>> 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-de...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> Website: http://earl-of-code.com
>
> --
> 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-de...@googlegroups.com <javascript:>.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
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.
