CI setup #1
Merged
CI setup #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SevInf
force-pushed
the
ci
branch
16 times, most recently
from
a3ad6de to
38e6c64
Compare
Multiple different things are happening here:
1. Checked-in pre-compiled engines replaced by the download logic.
Engine hash is stored in checked-in `.versions/engine` file and is
downloaded in `prepare` script. Pre-compiled engines are still part of
published npm package but they are no longer checked into the
repository. That also removes the need for LFS setup.
2. CI workflow for automated testing is setup
It is pretty much e2e test from prisma/prisma moved into this repository
instead. Build example app and runs simple integration test on both iOS
and Android emulator. It also fixes a bunch of linting failures present
in the repo.
3. CI workflow for automated updates of client, engines, and automated
publishing of the package.
Polls npm on cron, if the update found on either `prisma@dev` or
`prisma@latest`, pulls in the new version, does update on the separate
temporary branch and runs aforementioned test on it. If the test is
succsful, branch is merged back into main and new `@prisma/react-native`
package is published with an identical version and npm tag.
Close prisma/team-orm#1106
SevInf
commented
Apr 30, 2024
| @@ -0,0 +1,30 @@ | |||
|
|
|||
| package com.prismaexample; | |||
There was a problem hiding this comment.
Jolg42
reviewed
Apr 30, 2024
Jolg42
approved these changes
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Multiple different things are happening here:
Checked-in pre-compiled engines replaced by the download logic.
Engine hash is stored in checked-in
.versions/enginefile and isdownloaded in
preparescript. Pre-compiled engines are still part ofpublished npm package but they are no longer checked into the
repository. That also removes the need for LFS setup.
CI workflow for automated testing is added
It is pretty much e2e test from prisma/prisma moved into this repository
instead. Build example app and runs simple integration test on both iOS
and Android emulator. It also fixes a bunch of linting failures present
in the repo.
CI workflow for automated updates of client, engines, and automated
publishing of the package.
Polls npm on cron, if the update found on either
prisma@devorprisma@latest, pulls in the new version, does update on the separatetemporary branch and runs aforementioned test on it. If the test is
succsful, branch is merged back into main and new
@prisma/react-nativepackage is published with an identical version and npm tag.
Bunch of different tools that were added to the dependencies but never actually worked are removed (turborepo, release-it)
Close https://github.com/prisma/team-orm/issues/1106