Skip to content

update all stacks to use $PROJECT_SOURCE #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

Merged
merged 1 commit into from
Feb 15, 2022

Conversation

kadel
Copy link
Member

@kadel kadel commented Nov 24, 2021

WORK IN PROGRESS

$PROJECT_SOURCE should be used and not $PROJECTS_ROOT

What does this PR do?:

Summarize the changes. Are any stacks or samples added or updated?

Which issue(s) this PR fixes:

Link to github issue(s)

PR acceptance criteria:

  • Contributing guide
    Have you read the devfile registry contributing guide and followed its instructions?
  • Test automation
    Does this repository's tests pass with your changes?
  • Documentation
    Does any documentation need to be updated with your changes?

How to test changes / Special notes to the reviewer:

@kadel kadel force-pushed the use-PROJECT_SOURCE branch from 9a5e1f9 to 2554488 Compare February 11, 2022 16:07
@kadel
Copy link
Member Author

kadel commented Feb 14, 2022

/retest

@kadel
Copy link
Member Author

kadel commented Feb 14, 2022

java-quarkus test is failing, but that has nothing to do with this PR.
It fails to start application on

[ERROR] Failed to execute goal io.quarkus.platform:quarkus-maven-plugin:2.7.1.Final:dev (default-cli) on project code-with-quarkus: Detected Maven Version (3.6.2)  is not supported, it must be in [3.8.1,). -> [Help 1]

It looks like the starter project is incompatible with the image being used in devfile

reported quarkus issue in devfile/api#773

@openshift-ci
Copy link

openshift-ci bot commented Feb 14, 2022

@kadel: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/v4.7-registry-test 2554488 link true /test v4.7-registry-test

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@kadel kadel changed the title [WIP] update all stacks to use $PROJECT_SOURCE update all stacks to use $PROJECT_SOURCE Feb 14, 2022
@kadel
Copy link
Member Author

kadel commented Feb 15, 2022

@elsony @l0rd can you please review this? This is trying to address one of the items in Che/odo devfile compatibility devfile/api#679

Copy link
Contributor

@l0rd l0rd left a comment

Choose a reason for hiding this comment

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

LGTM with one note:

workingDir: ${PROJECT_SOURCE}

may be omitted as in the meantime, at least for Che, it has become the default: if workingDir is not specified we set it to ${PROJECT_SOURCE}.

@openshift-ci
Copy link

openshift-ci bot commented Feb 15, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kadel, l0rd

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

@openshift-ci openshift-ci bot added the lgtm Looks good to me label Feb 15, 2022
@elsony
Copy link
Contributor

elsony commented Feb 15, 2022

java-quarkus test is failing, but that has nothing to do with this PR.

This is a known problem and we have already opened a bug to track it: quarkusio/quarkus#23562

@elsony elsony merged commit 716351a into devfile:main Feb 15, 2022
@kadel
Copy link
Member Author

kadel commented Feb 15, 2022

may be omitted as in the meantime, at least for Che, it has become the default: if workingDir is not specified we set it to ${PROJECT_SOURCE}.

@l0rd The Devfile spec doesn't define any default value for this. We should not just assume ${PROJECT_SOURCE}. Odo in this case just uses the working directory as specified in the image.

${PROJECT_SOURCE} is a sensible default, but if we want that we should specify it in the devfile API spec.

@l0rd
Copy link
Contributor

l0rd commented Feb 15, 2022

yes, that's what I meant: if we agree on that we could specify it in the spec and update the registry.

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

Successfully merging this pull request may close these issues.

3 participants