Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add parent dependency check on samples #195
Add parent dependency check on samples #195
Changes from 11 commits
aa0e1dd
81113bf
1abda83
1321736
8d71e6c
9c86d26
76b1f4e
563d791
88722d5
a5da72e
3464e43
959de4d
1b375fb
7c0d08c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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've tried to test the script locally following the instructions:
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.
@thepetk What is your output for
go version
?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.
Made changes 7c0d08c so
STACKS_DIR
can be either a relative or absolute path when executingvalidate_devfile_schemas.sh
.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.
@michael-valdron output is
go version go1.19.1 linux/amd64
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.
@thepetk try running it again with a go 1.18.x runtime, go 1.19.1 could be having issues running it.
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.
Finally got it run successfully :)
One thing I had to do other than those steps, was to add a
go.work
file in my repo's root dir.It seems that is working fine :)
One test I tried to make is to update the go-basic sample inside the extraDevfileEntries. I've tried to include multiple sample versions:
In the parent file I had:
(Which is ok)
During testing I was expecting to see the test fail for one of the golang children (go-basic version 2.1.0). Although I had an issue with the
quarkus
. The trace of the test was: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 an interesting result, it is reporting the stack as being
code-with-quarkus
but the error in the test seems to be the expected one withgo-basic 2.1.0
, I'll need to check if there is a problem with the inputs or if there is a bug within this test suite which is causing the wrong stack name to be reported.