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

Build docker image workflow #377

Closed

Conversation

dwertent
Copy link
Contributor

@dwertent dwertent commented Nov 5, 2024

The workflow is designed to build the Docker images for both the paladin core and the operator. Currently, this build process is triggered each time code is pushed to the main branch, and the image is tagged using the branch name (main, in this case).

To make this workflow function properly, the following repository secrets are required:

  • DOCKERHUB_USERNAME
  • DOCKERHUB_TOKEN

Additionally, ensure that the paladin and paladin-operator repositories have been created in the Docker registry.

For reference, here is an example of a successful workflow run:
Example Workflow Run

Copy link
Contributor

@peterbroadhurst peterbroadhurst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. As you say it will need @ryjones help to get the right credentials in place to push to the final LFDT-labs location in dockerhub.

@ryjones
Copy link
Contributor

ryjones commented Nov 5, 2024

please add a workflow_dispatch trigger

@ryjones
Copy link
Contributor

ryjones commented Nov 5, 2024

also, consider rebasing your commits, not merging in main. this makes life easier later.

Signed-off-by: dwertent <david.wertenteil@kaleido.io>
Signed-off-by: dwertent <david.wertenteil@kaleido.io>
@dwertent dwertent closed this Nov 5, 2024
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.

3 participants