Commit 67bb5913 authored by totten's avatar totten
Browse files

Update instructions for newer 'releaser'

parent 9765042a
......@@ -39,7 +39,7 @@ You can do the full process in one command:
```
cd /path/to/civicrm
releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --get --sign --tag --publish
releaser -v gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json get sign tag publish
```
or do the steps individually:
......@@ -48,22 +48,22 @@ or do the steps individually:
cd /path/to/civicrm
## Download and rename the RC tarballs
releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --get
releaser -v gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json get
## Generate signatures for tarballs
releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --sign
releaser -v gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json sign
## Generate tags in each repo (dry run)
releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --tag -n
releaser -v gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json tag -N
## Publish tarballs to Sourceforge and Gcloud (dry run)
releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --publish -n
releaser -v gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json publish -N
## Generate tags in each repo (really)
releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --tag -f
releaser -v gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json tag -f
## Publish tarballs to Sourceforge and Gcloud (really)
releaser gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json --publish
releaser -v gs://civicrm-build/4.6/civicrm-4.6.28-201705030600.json publish
```
## 4: Update `versions.json`
......
......@@ -39,7 +39,7 @@ You can do the full process in one command:
```
cd ~/src/4.7
releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --get --sign --tag --publish
releaser -v gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json get sign tag publish
```
or do the steps individually:
......@@ -48,22 +48,22 @@ or do the steps individually:
cd ~/src/4.7
## Download and rename the RC tarballs
releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --get
releaser -v gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json get
## Generate signatures for tarballs
releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --sign
releaser -v gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json sign
## Generate tags in each repo (dry run)
releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --tag -n
releaser -v gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json tag -N
## Publish tarballs to Sourceforge and Gcloud (dry run)
releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --publish -n
releaser -v gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json publish -N
## Generate tags in each repo (really)
releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --tag -f
releaser -v gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json tag -f
## Publish tarballs to Sourceforge and Gcloud (really)
releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --publish
releaser -v gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json publish
```
You might want to spot-check a few URLs to ensure the tags were published, e.g.
......
......@@ -49,7 +49,7 @@ You can do the full process in one command:
```
cd ~/src/master
releaser gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json --get --sign --tag --publish
releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json get sign tag publish
```
or do the steps individually:
......@@ -58,22 +58,22 @@ or do the steps individually:
cd ~/src/master
## Download and rename the RC tarballs
releaser gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json --get
releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json get
## Generate signatures for tarballs
releaser gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json --sign
releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json sign
## Generate tags in each repo (dry run)
releaser gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json --tag -n
releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json tag -N
## Publish tarballs to Sourceforge and Gcloud (dry run)
releaser gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json --publish -n
releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json publish -N
## Generate tags in each repo (really)
releaser gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json --tag -f
releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json tag -f
## Publish tarballs to Sourceforge and Gcloud (really)
releaser gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json --publish
releaser -v gs://civicrm-build/5.2/civicrm-5.2.0-201705030600.json publish
```
To ensure the various tags were published and match the branches, use `civi-git-table`, as in:
......
......@@ -57,7 +57,7 @@ You can do the full process in one command:
```
cd ~/src/master
releaser gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json --get --sign --tag --publish
releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json get sign tag publish
```
or do the steps individually:
......@@ -66,22 +66,22 @@ or do the steps individually:
cd ~/src/master
## Download and rename the RC tarballs
releaser gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json --get
releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json get
## Generate signatures for tarballs
releaser gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json --sign
releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json sign
## Generate tags in each repo (dry run)
releaser gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json --tag -n
releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json tag -N
## Publish tarballs to Sourceforge and Gcloud (dry run)
releaser gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json --publish -n
releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json publish -N
## Generate tags in each repo (really)
releaser gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json --tag -f
releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json tag -f
## Publish tarballs to Sourceforge and Gcloud (really)
releaser gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json --publish
releaser -v gs://civicrm-build/5.2/civicrm-5.2.1-201705030600.json publish
```
To ensure the various tags were published and match the branches, use `civi-git-table`, as in:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment