-
Notifications
You must be signed in to change notification settings - Fork 117
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
Include tash in the Task bundle build #1039
Conversation
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.
This is great!
Thanks for the suggestions I'll look into addressing them, other reviews welcome... |
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.
Nice, no more manual syncing of multiple versions of the same task 🎉
a3784fe
to
df45fab
Compare
I think I addressed all the comments, please do have another look. Notable differences from the previous version:
|
dd0b6d5
to
6c4f252
Compare
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.
buildah-remote-oci-ta seems to be missing the recipe.yaml, otherwise LGTM 🌮
Oh wait, that one is generated from buildah-oci-ta, isn't it |
It is generated using |
Looks like one of the e2e tests timed out:
/retest |
@@ -16,43 +16,45 @@ spec: | |||
When [Java dependency rebuild](https://redhat-appstudio.github.io/docs.stonesoup.io/Documentation/main/cli/proc_enabled_java_dependencies.html) is enabled it triggers rebuilds of Java artifacts. |
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.
This code is now generated from two different places, as the remote task generation is expecting to generate this from the buildah-oci-ta.
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.
From what I understand the hack/generate-buildah-remote.sh
script will generate task/buildah-remote-oci-ta/0.1/buildah-remote-oci-ta.yaml
, there is no recipe.yaml
in task/buildah-remote-oci-ta/0.1
so tash and the hack/generate-ta-tasks.sh
script will not try to generate this file.
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.
ok, I missed that it skipped this one, looks good to me.
I have a PR open at #1068 that moves this generator to the build-definitions repo.
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.
Yeah I saw that, I think we'll move this from ec/hacks here as well.
e2e tests keep failing with:
|
I wonder if this needs a rebase now that HAS has been disabled? |
These will be used by the `tash` tool to regenerate the Trusted Artifact variant of the Tasks based on the existing base Tasks.
This adds a script to regenerate the Trusted Artifact variant Tasks and a GitHub Workflow to check if files need regenerating.
Run `hack/generate-ta-tasks.sh` to regenerate the Trusted Artifacts Task variants.
This includes the tool to generate the Trusted Artifacts Task variants in the
hack/build-and-push.sh
script, now if the task has arecipe.yaml
file within its directory the tool will be used to regenerate the Trusted Artifact Task from the base Task.Fixes https://issues.redhat.com/browse/EC-650