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

👷Initial workflow to checkout and build the CSMS #7

Merged
merged 17 commits into from
Nov 14, 2024

Conversation

shankari
Copy link

@shankari shankari commented Nov 14, 2024

This can definitely be polished, but it works now so can unblock
EVerest#78

Changes:

  • Add a new workflow
  • Configure it with a hardcoded set of images to build for maeve
  • Apply compile-time patches
  • Build and push, similar to the original cicd workflow

@shankari
Copy link
Author

Tried to build with docker-compose and push, but the push is running into issues.

#34 DONE 0.1s
#35 [gateway] exporting to image
#35 exporting layers
#35 exporting layers 0.4s done
#35 writing image sha256:b080665af6f94968233aec8ec952b0c6c424576e2a271c42b5e9479e6fced0d7 done
#35 naming to docker.io/library/maeve-csms-gateway done
#35 DONE 0.4s

maeve-csms-gateway   latest      b080665af6f9   1 second ago     26.7MB
maeve-csms-manager   latest      f26bc6871258   12 seconds ago   39.5MB

maeve-csms-gateway                                latest      b080665af6f9   1 second ago     26.7MB
ghcr.io/everest/everest-demo/maeve-csms-gateway   0.0.16      b080665af6f9   1 second ago     26.7MB
maeve-csms-manager                                latest      f26bc6871258   12 seconds ago   39.5MB
ghcr.io/everest/everest-demo/maeve-csms-manager   0.0.16      f26bc6871258   12 seconds ago   39.5MB
moby/buildkit                                     latest      c6936aa67ee2   2 weeks ago      203MB

The push refers to repository [ghcr.io/everest/everest-demo/maeve-csms-gateway]

8fa10c0194df: Waiting
03af25190641: Waiting
denied: permission_denied: The requested installation does not exist.
Error: Process completed with exit code 1.

This seems to be because we don't have a package listed
Screenshot 2024-11-14 at 9 58 27 AM

Switching to the build-and-push action at least initially since it looks like it creates it properly.
Will have to hardcode for now though.

@shankari
Copy link
Author

This now appears to be fairly stable, squash merging and sending it over to the main branch we are working on

@shankari shankari merged commit b315eac into upgrade_to_sept_2024_release Nov 14, 2024
2 checks passed
@shankari shankari deleted the build_csms_in_ci branch November 14, 2024 20:00
shankari added a commit that referenced this pull request Nov 14, 2024
* 👷Initial workflow to checkout and build the CSMS

This can definitely be polished, but it works now so can unblock
EVerest#78

Changes:
- Add a new workflow
- Configure it with a hardcoded set of images to build for maeve
- Apply compile-time patches
- Build and push, similar to the original `cicd` workflow

----- full list of changes -----

* Build on pull requests to upgrade branches as well

* Handle the two directories correctly

Need to explicitly `cd` into `everest-demo`
And apply patches from there

* Fix repo format

* Fix checked out directory format

* Again change directory properly before building

* Now that build works, re-tag and push

* Fix invalid workflow format

* Really fix the format

* read the env properly (from within the demo)

* Login before pushing

* Switch to the build-push-action so that push to packages works

EVerest#78 (comment)

* Actually push the values

* Give more permissions to the token

To be consistent with
https://docs.github.com/en/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions

* Change the permission to "admin"

So that we can really really push?!

* Temporarily switch to US-JOET so we can verify that it works

* Split the maeve patches into compile time and runtime

And apply only the compile time patch while building the image

Signed-off-by: Shankari <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant