[OSSTEST PATCH] README.dev: Document how to do a force push.

[OSSTEST PATCH] README.dev: Document how to do a force push.

[Ian Campbell]

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
 README.dev | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/README.dev b/README.dev
index eb72659..1257649 100644
--- a/README.dev
+++ b/README.dev
@@ -123,3 +123,12 @@ initial push works
 When pushing the patches, be sure to make sure that the
 for-$branch.git repo can fast forward to the pushed version (perhaps
 by resetting it).
+
+Force pushing a branch
+======================
+
+As osstest user on test controller
+$ cd ~/branches/for-$branch.git
+$ OSSTEST_CONFIG=production-config ./ap-push $branch $revision
+
+NOTE: $revision must be a revision *not* a tag.
-- 
2.1.1

[PATCH] README.dev: Document the usage of stop files

[Ian Campbell]

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
 README.dev | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/README.dev b/README.dev
index 1257649..7ef4f89 100644
--- a/README.dev
+++ b/README.dev
@@ -132,3 +132,16 @@ $ cd ~/branches/for-$branch.git
 $ OSSTEST_CONFIG=production-config ./ap-push $branch $revision
 
 NOTE: $revision must be a revision *not* a tag.
+
+Temporarily stopping a branch or the entire system
+==================================================
+
+osstest can be paused by dropping a stop file into either the central
+$HOME/testing.git or ~/branches/for-$branch.git etc.
+
+stop			-- stops everything
+daily.stop		-- stops all regular daily tests
+bisects.stop		-- stops all bisections
+$branch.stop		-- stops $branch
+$xenbranch.stop		-- stops everything using $xenbranch
+daily.stop		-- stops all regular daily tests
-- 
2.1.4

Re: [PATCH] README.dev: Document the usage of stop files

[Ian Jackson]

Ian Campbell writes ("[PATCH] README.dev: Document the usage of stop files"):
...
>  NOTE: $revision must be a revision *not* a tag.
> +
> +Temporarily stopping a branch or the entire system
> +==================================================
> +
> +osstest can be paused by dropping a stop file into either the central
> +$HOME/testing.git or ~/branches/for-$branch.git etc.
> +
> +stop			-- stops everything
> +daily.stop		-- stops all regular daily tests
> +bisects.stop		-- stops all bisections
> +$branch.stop		-- stops $branch
> +$xenbranch.stop		-- stops everything using $xenbranch
> +daily.stop		-- stops all regular daily tests

`daily.stop' is mentioned twice here.

You should probably mention that dropping `stop' into for-$branch.git
doesn't stop "everything" but only that branch.

Ian.

Re: [PATCH] README.dev: Document the usage of stop files

[Ian Campbell]

On Fri, 2015-01-23 at 15:20 +0000, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH] README.dev: Document the usage of stop files"):
> ...
> >  NOTE: $revision must be a revision *not* a tag.
> > +
> > +Temporarily stopping a branch or the entire system
> > +==================================================
> > +
> > +osstest can be paused by dropping a stop file into either the central
> > +$HOME/testing.git or ~/branches/for-$branch.git etc.
> > +
> > +stop			-- stops everything
> > +daily.stop		-- stops all regular daily tests
> > +bisects.stop		-- stops all bisections
> > +$branch.stop		-- stops $branch
> > +$xenbranch.stop		-- stops everything using $xenbranch
> > +daily.stop		-- stops all regular daily tests
> 
> `daily.stop' is mentioned twice here.
> 
> You should probably mention that dropping `stop' into for-$branch.git
> doesn't stop "everything" but only that branch.

I've redone it as below which I think is probably (?) clearer. There are
some less useful things you can do like
$HOME/branches/for-$branch.git/$branch.stop, but that's a bit redundant
so I didn't document it. Likewise I think
$HOME/branches/for-$branch.git/$xenbranch.stop (i.e. stop this branch
iff it is using $xenbranch) isn't terribly helpful.

I think I'm correct that $HOME/testing.git/$branch.stop stops both
regular flights and bisects?

Please could you also take a look at "README.dev: Document how to do a
force push." from
<1420552277-4358-1-git-send-email-ian.campbell@citrix.com>.

8<------

>From 5f4cf7b340828b42f0828a141ad8275eea7b6d22 Mon Sep 17 00:00:00 2001
From: Ian Campbell <ian.campbell@citrix.com>
Date: Fri, 23 Jan 2015 15:13:20 +0000
Subject: [PATCH] README.dev: Document the usage of stop files

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
---
v2: Improve (?)
---
 README.dev | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/README.dev b/README.dev
index 1257649..5e69cb8 100644
--- a/README.dev
+++ b/README.dev
@@ -132,3 +132,37 @@ $ cd ~/branches/for-$branch.git
 $ OSSTEST_CONFIG=production-config ./ap-push $branch $revision
 
 NOTE: $revision must be a revision *not* a tag.
+
+Temporarily stopping a branch or the entire system
+==================================================
+
+osstest can be paused by dropping a stop file into either the central
+$HOME/testing.git or $HOME/branches/for-$branch.git etc.
+
+$HOME/testing.git/stop
+
+  stop everything
+
+$HOME/testing.git/daily.stop
+
+  stops all regular tests
+
+$HOME/testing.git/bisect.stop
+
+  stops all bisections
+
+$HOME/testing.git/$branch.stop
+
+  stop regular tests and bisections of $branch
+
+$HOME/branches/for-$branch.git/stop
+
+  stops regular tests $branch
+
+$HOME/bisects/for-$branch.git/stop
+
+  stops bisections of $branch
+
+$HOME/testing.git/$xenbranch.stop
+
+  stops everything using $xenbranch
-- 
2.1.4

Re: [PATCH] README.dev: Document the usage of stop files

[Ian Jackson]

Ian Campbell writes ("Re: [PATCH] README.dev: Document the usage of stop files"):
> I've redone it as below which I think is probably (?) clearer.

Yes, I think it's much clearer, thanks.

Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

> There are  some less useful things you can do like [stuff]
> but that's a bit redundant so I didn't document it.

Yes.

> I think I'm correct that $HOME/testing.git/$branch.stop stops both
> regular flights and bisects?

Yes.

Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>

I will accumulate this into a branch of mine, as I now have an
outstanding ovmf patch from Wei which is waiting for a test flight.

Ian.

Re: [OSSTEST PATCH] README.dev: Document how to do a force push.

[Ian Jackson]

Ian Campbell writes ("[OSSTEST PATCH] README.dev: Document how to do a force push."):
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
...
> +Force pushing a branch
> +======================
> +
> +As osstest user on test controller
> +$ cd ~/branches/for-$branch.git
> +$ OSSTEST_CONFIG=production-config ./ap-push $branch $revision

This works in ~osstest/testing.git too.

Ian.

>From c9cfea3529c7f75b519a861df6457b9d44b167ac Mon Sep 17 00:00:00 2001
From: Ian Campbell <ian.campbell@citrix.com>
Date: Tue, 6 Jan 2015 13:51:17 +0000
Subject: [OSSTEST PATCH] README.dev: Document how to do a force push.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Signed-off-by: Ian Jackson <ian.jackson@eu.citrix.com>
---
 README.dev |   13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/README.dev b/README.dev
index eb72659..ed8dcf9 100644
--- a/README.dev
+++ b/README.dev
@@ -123,3 +123,16 @@ initial push works
 When pushing the patches, be sure to make sure that the
 for-$branch.git repo can fast forward to the pushed version (perhaps
 by resetting it).
+
+Force pushing a branch
+======================
+
+As osstest user on test controller
+
+$ cd ~/branches/for-$branch.git
+OR
+$ cd ~/testing.git
+
+$ OSSTEST_CONFIG=production-config ./ap-push $branch $revision
+
+NOTE: $revision must be a revision *not* a tag.
-- 
1.7.10.4

Re: [OSSTEST PATCH] README.dev: Document how to do a force push.

[Ian Campbell]

On Fri, 2015-01-23 at 16:53 +0000, Ian Jackson wrote:
> Ian Campbell writes ("[OSSTEST PATCH] README.dev: Document how to do a force push."):
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> ...
> > +Force pushing a branch
> > +======================
> > +
> > +As osstest user on test controller
> > +$ cd ~/branches/for-$branch.git
> > +$ OSSTEST_CONFIG=production-config ./ap-push $branch $revision
> 
> This works in ~osstest/testing.git too.

Thanks, and I see you've pushed both of these too, cheers!