-
Notifications
You must be signed in to change notification settings - Fork 26
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
Project "Jiffy Lube": TypeScript, Continuous Integration, React 16.13, etc. #131
Conversation
so modern, so sleek! |
I see that we now have automated testing here, cool! do you think we could also use this for the builds. i know with circleci, it can store generated artifacts |
Yes! CI is set up to package the app on every OS. It looks to me like it should also publish the builds so that they're accessible as artifacts on Github. If they're not when we get the builds passing I'll make sure we get that set up |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there's something weird going on in the labjs folder, we have both protocols and scripts. I think only one set is needed. there seems to be some legacy formatting in the stroop task for jspsych. I believe jspsych and jspsych are no longer even in the package (i removed them myself). we should clean up its references including the Trial, and Timeline parts seen around the project.
this looks so great, fantastic overhaul. this will really streamline a lot of the development in the app and the build process will be greatly simplified.
env: | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
run: | | ||
yarn package-ci |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are packaged artifacts only generated with the merge or should we see them listed under the artifact section on the testing page for github actions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like this CI setup doesn't attach artifacts to actions, but to Github releases. Once CI completes next, we should see app installers automatically attached to this draft release https://github.com/makebrainwaves/BrainWaves/releases/tag/v0.14.0
Co-authored-by: Teon L Brooks <[email protected]>
Co-authored-by: Teon L Brooks <[email protected]>
…BrainWaves into dano/boilerplate
Wooo! We got artifacts!! https://github.com/makebrainwaves/BrainWaves/releases/tag/untagged-f20fb7aa8bffc9778dbf |
awesome, good to see the modernization! i'm having some difficulty on my Mac with running the app, from the artifacts generated, it just opens up a blank screen. i've then updated my local dev environment and I get the same thing. I do get this traceback though:
should I make a separate issue for this? |
I though that error looked familiar :) FWIU, this error should only apply when you're building the app on Mac, so this might not explain why the compiled artifact doesn't work. Let's get to the point where you can successfully build on Mac locally and then investigate why published artifacts aren't working. |
No description provided.