You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove support for copying repositories into the release org. (#45268)
This support was helpful to get started but creates problems with the
current terraform-managed ros2-gbp org and with encouraging split-brain
releases where some are made from external release repositories and some
are made from the official release org.
Before running the migration, check the source distribution for release
repository urls outside the release org and mirror them to the release
org before continuing.
The rosdistro-bloom rewrite of this script intends to support this
workflow with a separate subcommand for mirroring repos.
Copy file name to clipboardExpand all lines: migration-tools/README.md
+4-8Lines changed: 4 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,21 +20,17 @@ Make sure rosdep is initialized if it isn't already.
20
20
21
21
sudo rosdep init
22
22
23
-
Configure a GitHub access token and release repository organization.
24
-
The token only needs public repository access and must belong to a member of the target GitHub organization with repository creation permissions.
25
-
26
-
```
27
-
GITHUB_TOKEN={token with public repository access}
28
-
export GITHUB_TOKEN
29
-
```
23
+
This script used to copy release repositories into the release org as-needed.
24
+
This worked for the initial bootstrapping but creates split-brain problems when releases are split between the official release org and others.
25
+
Instead, use `git clone --mirror` and `git push --mirror` on release repositories that are not yet in the release org and update your rosdistro before running this script.
30
26
31
27
## Script arguments
32
28
33
29
The migration script has several named arguments, all of which are required.
34
30
*`--dest DEST_ROSDISTRO`: The rosdistro which will receive the newly bloomed repositories.
35
31
*`--source SOURCE_ROSDISTRO`: The rosdistro to take release repositories from for migration.
36
32
*`--source-ref GIT_COMMIT_ID_OR_REF`: The migration may be attempted multiple times. Each attempt must specify ref or commit to start from so that future changes to the source distribution do not unintentionally affect migration. This also enables platform migration without changing the rosdistro name.
37
-
*`--release-org GITHUB_ORG`: A GitHub organization for storing release repositories. If the repository does not exist in this organization a new repository will be created.
33
+
*`--release-org GITHUB_ORG`: A GitHub organization for storing release repositories.
0 commit comments