git fetch + git push restored git-client and git plugins history
2013/11/10 Luca Milanesio luca.milane...@gmail.com
Hi all,
I have triggered an involuntary forced push last night on the list of
Jenkins-CI plugins indicated below in this e-mail.
*My apology *
I did not realise that I
I had pushed releases of credentials, ssh-credentials, ssh-agent and ec2 on
Friday, so I just re-pushed them. I don't think anyone made changes to
scm-api or branch-api since my last push, so I pushed those from my local
also
On 11 November 2013 09:05, nicolas de loof nicolas.del...@gmail.com
What is the recommended way to get a full restore, in the case where you do
not happen to have a local clone of the repository which was cloned before
the accident?
On Sun, Nov 10, 2013 at 7:55 PM, Luca Milanesio luca.milane...@gmail.comwrote:
Hi all,
I have triggered an involuntary forced
I can look into this while traveling to devoxx tomorrow
2013/11/11 Arnaud Héritier aherit...@gmail.com
Hi Nicolas.
For me it would be the safer issue. You could wait for tomorrow (it's a
day off today in France) but we just need to take care to not loose these
repositories.
—
Sent from
Yes, I think that would be a sensible approach.
As some of the people started already to push their up-to-date repo, it is
better a push from the CI node rather than a reset from the GitHub guys at
this stage.
Luca.
On 11 Nov 2013, at 10:38, nicolas de loof nicolas.del...@gmail.com wrote:
I
Created https://github.com/jenkinsci/awseb-deployment-plugin
You just need to create a new Jenkins account (https://jenkins-ci.org/account/)
in order to make changes in confluence.
Welcome aboard! Ulli
Am 10.11.2013 um 23:23 schrieb Aldrin Leal ald...@leal.eng.br:
Ok, I think I've managed all
I pushed transifex-plugin.git from my local tree, all fine for this plugin
now.
Regards,
Hakan
On Sunday, November 10, 2013 7:55:08 PM UTC+1, lucamilanesio wrote:
*The solution*
I can raise a request to GitHub to provide the reflog of those
repositories and restore the branches to the
HI there,
I just tried to connect to check out the plugin I maintain
(ironmq-notifier).
I have lost access to the repo completely.
I suspect that since I'm new, my rights were reverted due to this somehow.
Could someone add me back into the plugin ironmq-notifier.
Thanks
userid:mikecaspar
--
Actually, looks like it was just some weird caching problem.
Back into the repo now.
On Monday, November 11, 2013 7:22:58 AM UTC-5, Mike Caspar wrote:
HI there,
I just tried to connect to check out the plugin I maintain
(ironmq-notifier).
I have lost access to the repo completely.
I
I've pushed plugin's master branches from jenkins.ci.cloudbees.com,
some of then were rejected, like
g...@github.com:jenkinsci/warnings-plugin.git
! [rejected]master - master (non-fast-forward)
Anyway I guess most plugin repo should be restored now.
2013/11/11 Hakan Tandoğan
This one https://github.com/jenkinsci/copy-to-slave-plugin recovered only
some commits.
On Mon, Nov 11, 2013 at 7:46 PM, Mads Nielsen m...@praqma.net wrote:
I can confirm that the ones i was interested in are OK:
https://github.com/jenkinsci/clearcase-ucm-plugin
I already pushed my local commits again, so the history of the warnings plug-in
is up to date again.
Am 11.11.2013 um 15:09 schrieb nicolas de loof nicolas.del...@gmail.com:
I've pushed plugin's master branches from jenkins.ci.cloudbees.com,
some of then were rejected, like
Here are the repo that fail to git push as [rejected]master -
master (non-fast-forward)
branch-api-plugin.git
credentials-plugin.git
deployit-plugin.git
ec2-cloud-axis-plugin.git
ec2-plugin.git
email-ext-plugin.git
flexible-publish-plugin.git
gerrit-trigger-plugin.git
logfilesizechecker and scm2job restored from local copy (wasn’t complete)
https://github.com/jenkinsci/logfilesizechecker-plugin
https://github.com/jenkinsci/scm2job-plugin
Am 11.11.2013 um 15:26 schrieb nicolas de loof
nicolas.del...@gmail.commailto:nicolas.del...@gmail.com:
master branch is
just git push origin master
the unintentional force push just reverted history some weeks ago, so this
will re-add the missing commits
2013/11/11 Vivekanand S V svvivekan...@gmail.com
@nicolas, I have a local clone which I last used to push a release. What
do I need to do ?
On Mon, Nov
@nicolas, its done, copy-to-slave is upto date now.
Thanks a lot.
On Mon, Nov 11, 2013 at 9:26 PM, nicolas de loof
nicolas.del...@gmail.comwrote:
just git push origin master
the unintentional force push just reverted history some weeks ago, so this
will re-add the missing commits
It seems this plugin is still maintained in Subversion for some
reason, and there have been a couple of releases since ndeloof’s
commit to Git [1], so now history is mess: the Git fix is not in SVN,
and Jacob’s new releases are not in Git (not even in the svn branch).
The SVN log says only
Hi,
just FIY, if your plugin is not on this list, this doesn't mean the commits
were successfully restored - e.g. one of my plugins (beaker-builder) is not on
the list and the last commit is 3 months old [1], while actual last commit is
one week old [2], so please double check your plugins
yes indeed, this is just the last state on CI job, no guarantee it hasn't
been updated in the meantime based on github forced push
2013/11/11 Vojtech Juranek vjura...@redhat.com
Hi,
just FIY, if your plugin is not on this list, this doesn't mean the commits
were successfully restored - e.g.
perforce-plugin.git has been restored from my local copy.
It may be beneficial to look into implementing finer grained access control
for individual repos. For example, I thought that only myself, Oleg, and
the Jenkins project owners had write access to the perforce plugin. If
everyone has
On 11/10/2013 10:55 AM, Luca Milanesio wrote:
Hi all,
I have triggered an involuntary forced push last night on the list of
Jenkins-CI plugins indicated below in this e-mail.
*_My apology _*
I did not realise that I actually had forced push permissions and I do
apologise for the inconvenience
Yes, I was thinking about the same. The last run of this is Nov 9,
11:24pm in EST.
I really hope this is before the incident. But I'll find out soon.
On 11/11/2013 12:15 AM, Vojtech Juranek wrote:
On Sunday 10 November 2013 21:40:28 Luca Milanesio wrote:
That's really pitty :-( ... force
You should push 'master' in these repos to a separate ref so that we can
compare.
On 11/11/2013 06:37 AM, nicolas de loof wrote:
Here are the repo that fail to git push as [rejected]master -
master (non-fast-forward)
branch-api-plugin.git
credentials-plugin.git
Requesting commit access to GIT for new plugin
GitHub ID: billmanhillman
--
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
On 11/11/2013 12:23 PM, Kohsuke Kawaguchi wrote:
Yes, I was thinking about the same. The last run of this is Nov 9,
11:24pm in EST.
I really hope this is before the incident. But I'll find out soon.
Unfortunately, it appears that the last sync process has run after
luca's push -f.
I'll
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
We at the #jenkins channel in IRC were just wondering what the 'recovery'
branch is.
I think it makes sense to bring back 'master' to 'recovery' where it is
fast-forward, but let's walk bit slowly here...
2013/11/11 Luca Milanesio luca.milane...@gmail.com
Good news from GitHub: they have
What is your plug-in about? Did you already commit your sources in your Github
account? Then we need the name of your repository so that we can fork it. If
you did not publish yet we need a unique name for your repository.
Am 11.11.2013 um 22:22 schrieb Greg Peters gregpeter...@gmail.com:
On 11/11/2013 02:27 PM, Kohsuke Kawaguchi wrote:
We at the #jenkins channel in IRC were just wondering what the
'recovery' branch is.
I think it makes sense to bring back 'master' to 'recovery' where it is
fast-forward, but let's walk bit slowly here...
I'm downloading all the affected
You are all set now. Welcome aboard.
On 11/10/2013 10:48 AM, gregpeter...@gmail.com wrote:
Ok, moved to github.
I'm requesting commit access to github.
Github ID: billmanhillman
On Sunday, November 10, 2013 1:14:07 AM UTC-5, nicolas de loof wrote:
Hi,
svn isn't used anymore, we
On Mon, Nov 11, 2013 at 11:27 PM, Kohsuke Kawaguchi k...@kohsuke.org wrote:
We at the #jenkins channel in IRC were just wondering what the 'recovery'
branch is.
A big thx to Nathan Witmer !!
I think it makes sense to bring back 'master' to 'recovery' where it is
fast-forward, but let's
On Mon, Nov 11, 2013 at 11:46 PM, Kohsuke Kawaguchi
kkawagu...@cloudbees.com wrote:
On 11/11/2013 02:27 PM, Kohsuke Kawaguchi wrote:
We at the #jenkins channel in IRC were just wondering what the
'recovery' branch is.
I think it makes sense to bring back 'master' to 'recovery' where it is
Any more sanity checks on this course of action before I actually run
them? I've only heard from Arnaud...
On 11/11/2013 02:46 PM, Kohsuke Kawaguchi wrote:
On 11/11/2013 02:27 PM, Kohsuke Kawaguchi wrote:
We at the #jenkins channel in IRC were just wondering what the
'recovery' branch is.
Sounds perfect for me!
Domi
Am 12.11.2013 um 03:13 schrieb Kohsuke Kawaguchi kkawagu...@cloudbees.com:
Any more sanity checks on this course of action before I actually run them?
I've only heard from Arnaud...
On 11/11/2013 02:46 PM, Kohsuke Kawaguchi wrote:
On 11/11/2013 02:27 PM,
Now that the commits have been recovered and things are almost back to
normal, I think it's time to think about how to prevent this kind of
incidents in the future.
Our open commit access policy was partly made possible by the idea that any
bad commits can be always rolled back. But where I
Seems a very good idea, it is basically a remote audit trail.
The only concern is the throttling on the GitHub API: it would be better then
to do the scripting on a local mirror of the GitHub repos. When you receive a
forced update you do have anyway all the previous commits and the full
36 matches
Mail list logo
