-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync pipeline 1 and 2? #22
Comments
Mind that I do not at all care whether KB1 is the current working KB.. For all I care this could be an old KB; the most important thing here is that it contains the same data as KB2, and ideally, that this was the version used to generate either pdb or pdb-alpha.. |
I think having P1 and P2 mirror each other will be an asset before we do the full migration. What do you think? |
This is potentially hard given that these are a moving target. pdb is always behind except when we've just made a release. The P1 pipeline is flaky enough that staging (pdb-alpha) is often doesn't completely reflect which datasets are production as it may require some surgery or data cleaning. |
If its too much work dont worry; I just wanted to bring it to the table. |
It might be best to ask @Robbie1977 to make frozen clones of KB and an in sync pdb. Until then I wouldn't worry too much about trying to make everything match up. I can do a bit more analysis. I'm likely to spot problems quicker then you. |
To effectively compare the two pipelines I need the synced up entirely; so basically I need a KB1 that corresponds exactly to the KB2, and a PDB1 that is in sync with KB1. Is this somehow possible? If this is too hard work, no problem, just wanted to check to avoid me chasing down ghosts.
The text was updated successfully, but these errors were encountered: