-
Notifications
You must be signed in to change notification settings - Fork 7
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
base: main
Are you sure you want to change the base?
publish image nightly #50
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: liangyuanpeng 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 |
b4bc5ec
to
d4007c5
Compare
Signed-off-by: Lan Liang <[email protected]>
d4007c5
to
610ccaf
Compare
|
||
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 |
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.
Pending for a release of nightly.
apiVersion: v1 | ||
kind: Namespace | ||
metadata: | ||
name: shipwright-build |
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.
Necessary? when delete the release of triggers, it will be delete the namespace of shipwright-build
.
like:
kubectl delete -f release-triggers.yaml
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.
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.
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?
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. |
Changes
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes