Add script to migrate existing build results to Pulp #3509
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
FrostyX
force-pushed
the
migrate-data-to-pulp
branch
2 times, most recently
from
305ead3
to
a7d33d1
Compare
FrostyX
force-pushed
the
migrate-data-to-pulp
branch
from
a7d33d1
to
92c67e6
Compare
|
I successfully used the script to migrate data from the Copr STG instance to the Pulp STG instance. It woks for CoprDirs as well: This successfully installs the package from Pulp. |
| sys.exit(1) | ||
|
|
||
| if args.delete: | ||
| print("Data removal is not supported yet") |
There was a problem hiding this comment.
Since we have a pre-initialized logger, I think we should avoid using print() command.
|
|
||
| for builddir in os.listdir(chrootdir): | ||
| resultdir = os.path.join(chrootdir, builddir) | ||
| if not os.path.isdir(resultdir): |
There was a problem hiding this comment.
I'm not sure this check is enough..., maybe the upload_build_results is clever enough to handle issues? But see how this checking is done for the resultdir cleaner crawler.
| log.error("Failed to publish a repository: %s", resultdir) | ||
| break | ||
|
|
||
| log.info("OK: %s", resultdir) |
There was a problem hiding this comment.
I suppose we can not make this in a transactional manner.. (if error happens, rollback). But would it be possible to first analyze the situation and gather the tasks that need to be done, fail if some problem happens, and only if no problems happen - start the processing?
Also, I'm curious if whether we need a project lock (for building and other modification).
Fix #3503