Skip to content
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

Image sequencer, infragram, and RPi Cam for Raspberry Pi camera #53

Open
wants to merge 24 commits into
base: master
from

Conversation

@jywarren
Copy link
Contributor

jywarren commented Nov 9, 2018

Thanks for opening a pull request! In this repository, opening a PR will initiate the generation of a new Raspberry Pi image, and create an image file you can download and use in your Raspberry Pi.

The changes you add to the pull request, such as adding software to install, will be run on the generated image.

For an example, see the software installed and configured in this pull request: https://github.com/publiclab/image-builder-rpi/pull/15/files

Recipe

Use this space to describe what your "recipe" is intended to install and configure on a Raspberry Pi:


Download instructions

Generating the image will take a few minutes. Once the image is prepared, and if it succeeded, you'll see a green checkmark at the bottom of the pull request. To download the image:

  1. click the green checkmark; you'll go to a page at a URL like https://gitlab.com/publiclab/image-builder-rpi/pipelines/########/builds
  2. On this page, click the Jobs tab, next to Pipeline
  3. Click the green Passed button
  4. Click Download in the right-hand sidebar
  5. Unzip the artifacts.zip file, and also the hypriotos-rpi-camera_web.img.zip within it
  6. Use a program like https://etcher.io/ to flash it to an SD card

You'll also be able to read the output of the image generation in this window.

We hope to create a bot to report back the completed image URL in each pull request. If you can help create such a bot, please contact us at:

#16

Thanks!

@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Nov 9, 2018

trying to do it from a branch in the same repo... based on #50

@jywarren jywarren changed the title Image sequencer Image sequencer, infragram, and RPi Cam for Raspberry Pi camera Nov 9, 2018
@jywarren jywarren added the recipe label Nov 9, 2018
@jywarren

This comment was marked as outdated.

Copy link
Contributor Author

jywarren commented Nov 9, 2018

@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Nov 17, 2018

Rebuilding for new version of image sequencer!

@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Nov 18, 2018

@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Apr 27, 2019

Hi @icarito i've just published a new v0.2.0 version of https://github.com/publiclab/infragram on npm; if I want to rebuild with that version, should I just make a small arbitrary change here to trigger GitLab to generate a new image artifact? Thanks!

@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Jun 21, 2019

Same error as in #68 !

@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Jun 22, 2019

OK, this needs rebase now after #69 !

@jywarren jywarren force-pushed the image-sequencer branch from 01cdcbc to 11c7d2b Jul 1, 2019
@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Jul 1, 2019

Rebased! Update Hmm. not rebuilding. will try adding one more small commit.

Copy link
Contributor Author

jywarren left a comment

@icarito would you mind checking if my rebase introduced a bunch of unnecessary stuff vs. https://github.com/publiclab/pi-builder/pull/40/files ? Thank you!

@@ -84,7 +84,7 @@ ls -alh /image_with_kernel_*.tar.gz

# download the ready-made raw image for the RPi
if [ ! -f "${BUILD_RESULT_PATH}/${RAW_IMAGE}.zip" ]; then
wget -q -O "${BUILD_RESULT_PATH}/${RAW_IMAGE}.zip" "https://github.com/hypriot/image-builder-raw/releases/download/${RAW_IMAGE_VERSION}/${RAW_IMAGE}.zip"
wget -q -O "${BUILD_RESULT_PATH}/${RAW_IMAGE}.zip" "https://jenkins.laboratoriopublico.org/job/image-builder-raw/ws/${RAW_IMAGE}.zip"

This comment has been minimized.

Copy link
@jywarren

jywarren Jul 1, 2019

Author Contributor

@icarito can you check if this should be here? It exists on https://github.com/publiclab/pi-builder/pull/40/files but not sure if it's an artifact of rebasing.

get_gpg "${PACKAGECLOUD_FPR}" "${PACKAGECLOUD_KEY_URL}"

echo 'deb https://packagecloud.io/Hypriot/rpi/debian/ stretch main' > /etc/apt/sources.list.d/hypriot.list
# set up hypriot rpi repository for raspbian specific packages

This comment has been minimized.

Copy link
@jywarren

jywarren Jul 1, 2019

Author Contributor

Same here... is this right for this PR or is this reverting something?

@@ -0,0 +1,14 @@
#!/bin/sh -e

This comment has been minimized.

Copy link
@jywarren

jywarren Jul 1, 2019

Author Contributor

And one more spot I'm uncertain - this doesn't exist in https://github.com/publiclab/pi-builder/pull/40/files for example, which builds properly and is supposed to be almost the same as this PR.

@@ -4,14 +4,15 @@ ROOTFS_TAR_CHECKSUM="d1e7e6d48a25b4a206c5df99ecb8815388ec6945e4f97e78413d5a80778

# name of the ready made raw image for RPi
RAW_IMAGE="rpi-raw.img"
RAW_IMAGE_VERSION="v0.2.2"
RAW_IMAGE_CHECKSUM="2fbeb13b7b0f2308dbd0d82780b54c33003ad43d145ff08498b25fb8bbe1c2c6"
RAW_IMAGE_VERSION="master"

This comment has been minimized.

Copy link
@jywarren

jywarren Jul 1, 2019

Author Contributor

Ah, one more, apologies. this is the last spot.

@icarito

This comment has been minimized.

Copy link
Member

icarito commented Jul 15, 2019

Sorry I just got around to check this!

I think that the issue is you're rebasing into master branch, but we're using main branch.

@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Jul 15, 2019

Ah, this makes sense, but actually all our PRs are against master - maybe we did the transition to main after these PRs were open? Should we merge to master from main to sync them, or are they forked in two different directions?

@icarito

This comment has been minimized.

Copy link
Member

icarito commented Jul 16, 2019

You're right our PR's are for master branch anyway. I'll review with more detail.

Merge branch 'image-sequencer' of https://gitlab.com/publiclab/pi-builder into image-sequencer
@icarito

This comment has been minimized.

Copy link
Member

icarito commented Jul 16, 2019

Hey, i figured out the issue is that you force-pushed and this stalled the repository synchronization. It's building now, fingers crossed!

@icarito

This comment has been minimized.

Copy link
Member

icarito commented Jul 16, 2019

I fixed the kernel reference from upstream, now running into:

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! gl@4.2.2 install: `prebuild-install || node-gyp rebuild`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the gl@4.2.2 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above

Perhaps this was faced by ImageSequencer before?

@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Jul 16, 2019

…bglew-dev pkg-config

# install infragram in the web public folder:
# prerequisites:
sudo apt-get install -y build-essential libxi-dev libglu1-mesa-dev libglew-dev pkg-config

This comment has been minimized.

Copy link
@jywarren

jywarren Jul 16, 2019

Author Contributor

Ok @icarito do I need to rebase this again?

This comment has been minimized.

Copy link
@jywarren

jywarren Jul 16, 2019

Author Contributor

Ah looks like no, it's building now!

@Divy123

This comment has been minimized.

Copy link
Member

Divy123 commented Jul 16, 2019

@jywarren is there something I can help here?

@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Jul 17, 2019

@Divy123 is python a requirement to build headless-gl?

gl@4.2.2 install /var/www/image-sequencer/node_modules/gl
> prebuild-install || node-gyp rebuild

prebuild-install WARN install No prebuilt binaries found (target=9.7.1 runtime=node arch=arm libc= platform=linux)
gyp ERR! configure error 
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack     at PythonFinder.failNoPython (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:483:19)
gyp ERR! stack     at PythonFinder.<anonymous> 
@Divy123

This comment has been minimized.

Copy link
Member

Divy123 commented Jul 17, 2019

yes, we do require!!

jywarren and others added 2 commits Jul 17, 2019
@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Jul 19, 2019

Hmm:

Error: Can't find Python executable "python", you can set the PYTHON env variable.

# install infragram in the web public folder:
# prerequisites:
sudo apt-get install -y build-essential libxi-dev libglu1-mesa-dev libglew-dev pkg-config python2.7 python2.7-dev

This comment has been minimized.

Copy link
@jywarren

jywarren Jul 19, 2019

Author Contributor

Maybe this doesn't install as python?

This comment has been minimized.

Copy link
@Divy123

Divy123 Jul 19, 2019

Member

Maybe this doesn't install as python?

I think this may be needed:
sudo apt-get install -y build-essential libxi-dev libgl1-mesa-dev libglew-dev pkg-config python2.7 python2.7-dev. Just confirming!!

@jywarren jywarren force-pushed the image-sequencer branch from ca35fc9 to b291018 Jul 19, 2019
@icarito icarito force-pushed the image-sequencer branch from 2fbdf9a to ca35fc9 Jul 19, 2019
@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Aug 1, 2019

Hmm, switching back to python 2.7, but really just trying to not have a force push so that this will build properly...

@jywarren

This comment has been minimized.

Copy link
Contributor Author

jywarren commented Aug 1, 2019

We may need to close this and move to a new PR which is against main... ok, opened #73 against main branch!

jywarren added 5 commits Aug 1, 2019
@icarito

This comment has been minimized.

Copy link
Member

icarito commented Aug 1, 2019

Hey, I just went to check the Gitlab repository configuration and I found I could modify the CI timeout - I set it to 4 hours! So maybe let's try again with the build that timed out? Thanks and sorry I didn't know that was possible!

@icarito

This comment has been minimized.

Copy link
Member

icarito commented Aug 1, 2019

Here I restarted the build from last week:
https://gitlab.com/publiclab/pi-builder/-/jobs/264078267

@icarito

This comment has been minimized.

Copy link
Member

icarito commented Aug 1, 2019

https://gitlab.com/publiclab/pi-builder/-/jobs/264059463 (revert builder/build.sh) timed out at one hour because it started before I changed the setting (the max is 3 hours). I'm restarting this build!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.