-
Notifications
You must be signed in to change notification settings - Fork 85
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
Fixing small issues in WildFly 2.0.1 #368
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.
/lgtm tested against https://workspaces.openshift.com#https://raw.githubusercontent.com/ehsavoie/new-registry/wildfly-2.0.2/stacks/java-wildfly/2.0.2/devfile.yaml
and it works
fixes devfile/api#1493 |
@ehsavoie I've commited the suggestion for the usage of the |
@olexii4 FYI we had a question if the devfile is visible inside the workspace. Check here |
/retest |
@olexii4: changing LGTM is restricted to collaborators In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
3e386c3
to
7f9449e
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.
/lgtm I've opened it with the workspaces. One minor detail is if we would like to remove he deploy.yaml
& the dockerfile
now that the outerloop commands have been commented out
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.
Tested against https://workspaces.openshift.com#https://raw.githubusercontent.com/ehsavoie/new-registry/wildfly-2.0.2/stacks/java-wildfly/2.0.2/devfile.yaml, and everything worked as expected.
@olexii4: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@thepetk can we merge? |
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.
I'm not clear why some parts are commented out (not removed) from the devfile
I think we could remove them instead of commenting out, same applies for below comment:
cc @ehsavoie |
Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
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.
/lgtm the final version I think is ok and addresses all the comments made. I'll merge the PR once all the checks pass.
cc @ibuziuk
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ehsavoie, olexii4, thepetk The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
What does this PR do?:
Avoid the Containerfile conflict between the one from the git repo and the one from the registry
Which issue(s) this PR fixes:
Link to github issue(s)
PR acceptance criteria:
Have you read the devfile registry contributing guide and followed its instructions?
Does this repository's tests pass with your changes?
Does any documentation need to be updated with your changes?
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)
How to test changes / Special notes to the reviewer: