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

publish image nightly #50

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

liangyuanpeng
Copy link

Changes

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 20, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: liangyuanpeng
Once this PR has been reviewed and has the lgtm label, please assign qu1queee for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@liangyuanpeng liangyuanpeng marked this pull request as draft May 20, 2023 12:20
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 20, 2023
@liangyuanpeng liangyuanpeng force-pushed the publish_image_nightly branch 4 times, most recently from b4bc5ec to d4007c5 Compare May 25, 2023 07:18
Signed-off-by: Lan Liang <gcslyp@gmail.com>
@liangyuanpeng liangyuanpeng marked this pull request as ready for review May 25, 2023 07:27
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 25, 2023

mv release.yaml nightly-${{ steps.date.outputs.date }}.yaml
mv release-debug.yaml nightly-${{ steps.date.outputs.date }}-debug.yaml
# gh release upload nightly nightly-${{ steps.date.outputs.date }}.yaml
Copy link
Author

Choose a reason for hiding this comment

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

Pending for a release of nightly.

apiVersion: v1
kind: Namespace
metadata:
name: shipwright-build
Copy link
Author

@liangyuanpeng liangyuanpeng May 25, 2023

Choose a reason for hiding this comment

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

Necessary? when delete the release of triggers, it will be delete the namespace of shipwright-build.

like:

kubectl delete -f release-triggers.yaml

Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

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

The release yaml creation should be based on the helm chart that exists. It should not introduce new deployment artifacts. Basically like I started here: main...SaschaSchwarze0:shipwright-io-triggers:sascha-nightly. But we also want to publish the Helm chart itself to something like ArtifactHub which I had not yet time to look into.

@liangyuanpeng
Copy link
Author

liangyuanpeng commented May 29, 2023

The release yaml creation should be based on the helm chart that exists. It should not introduce new deployment artifacts. Basically like I started here: main...SaschaSchwarze0:shipwright-io-triggers:sascha-nightly.

So we will create a helm chart for triggers? I thought this was a mistake because we could deploy triggers from operator. 😅

And have not found Helm chart for shipwright build, So a question is just create alone Helm chart for triggers or have plan to work for all of component?

But we also want to publish the Helm chart itself to something like ArtifactHub

Publish the Helm chart to ghcr.io with oci would be great, ArtifactHub do not store something, it's just show something.

Also can create a artifacthub repository for shipwright trigger after release helm chart for observability.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants