Skip to content
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

new stack for camel #497

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

brunoNetId
Copy link

Description of Changes

Created a new Stack to include a new Apache Camel sample

Related Issue(s)

The following issue was created to track this PR:
devfile/api#1651

Acceptance Criteria

  • Contributing guide

Have you read the devfile registry contributing guide and followed its instructions?
YES

  • Test automation
    I've run a build as per the contribution guide suggested.

Does this repository's tests pass with your changes?

  • Documentation

Does any documentation need to be updated with your changes?
Don't think this is needed

  • Check Tools Provider

Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)
I've tested the DevFile from the originating GIT repository

Tests Performed

Explain what tests you personally ran to ensure the changes are functioning as expected.
I've run the build as per the documentation in the contribution guide.
I've provisioned the devfile in the Developer Sandbox

How To Test

run the sample to provision in the Developer Sandbox.
Follow the instructions in the Readme file from:
https://github.com/RedHat-Middleware-Workshops/devsandbox-camel.git

Notes To Reviewer

I created this Sample after I was recommended to include the Stack as a contribution in this project.
The DevFile already existed in the originating GIT repo:
https://github.com/RedHat-Middleware-Workshops/devsandbox-camel.git
This repository runs various tutorials and has been improved and polished over the last 2 years

Although I've been working with devfiles for a while now, I'm not familiar with contributing Stacks/Samples in this project. Please help me to ensure I follow the steps needed.

@brunoNetId brunoNetId requested a review from a team as a code owner November 25, 2024 21:57
Copy link

openshift-ci bot commented Nov 25, 2024

Hi @brunoNetId. Thanks for your PR.

I'm waiting for a devfile member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

Copy link
Contributor

@Jdubrick Jdubrick left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution! Would it be possible to sign-off on your commits for the DCO check? Also, will you be the intended owner of this stack?

@brunoNetId
Copy link
Author

Also, will you be the intended owner of this stack?
Yes

Copy link

openshift-ci bot commented Nov 27, 2024

@apupier: 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-sigs/prow repository.

Copy link
Member

@michael-valdron michael-valdron left a comment

Choose a reason for hiding this comment

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

Hi @brunoNetId, thanks for the contribution!

Since this is a new stack, we'll need you to add an entry to CODEOWNERS, add the @devfile/che-team in the entry like this example:

/stacks/nodejs/ @BethGriggs @devfile/che-team

NOTE: Omit your username for now as we'll follow the trial period for new owners, at the end of this period if you wish to continue owning the stack you can follow the process for adding yourself to the stacks CODEOWNERS entry.

@brunoNetId
Copy link
Author

Thanks @michael-valdron
Do you have any particular preference over where to include the new Stack?
Is it ok under a new Camel group?

@michael-valdron
Copy link
Member

Thanks @michael-valdron Do you have any particular preference over where to include the new Stack? Is it ok under a new Camel group?

@brunoNetId New Camel group sounds good!

@brunoNetId
Copy link
Author

@michael-valdron I added the new entry.
I assumed the stacks are ordered in alphabetical order

.github/CODEOWNERS Outdated Show resolved Hide resolved
@michael-valdron
Copy link
Member

I assumed the stacks are ordered in alphabetical order

@brunoNetId Ordering in your changes is fine.

@michael-valdron
Copy link
Member

/ok-to-test

@@ -0,0 +1,78 @@
schemaVersion: 2.2.0
Copy link
Collaborator

Choose a reason for hiding this comment

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

You can use a newer version; at least 2.2.2
The latest version is 2.3.0, @michael-valdron do you know if we can use 2.3.0 schema version for stacks?

Copy link
Collaborator

@svor svor left a comment

Choose a reason for hiding this comment

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

LGTM

@openshift-ci openshift-ci bot added the lgtm Looks good to me label Nov 28, 2024
Copy link

openshift-ci bot commented Nov 28, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: apupier, brunoNetId, svor
Once this PR has been reviewed and has the lgtm label, please ask for approval from michael-valdron. For more information see the Kubernetes Code Review Process.

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

@brunoNetId
Copy link
Author

@svor @michael-valdron
I see failures with odo v3, but I'm not sure if there is anything to do on my side.

@brunoNetId
Copy link
Author

Hi @svor @michael-valdron
Can you review/comment on this PR when you can?
thanks

Copy link
Member

@michael-valdron michael-valdron left a comment

Choose a reason for hiding this comment

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

@svor @michael-valdron I see failures with odo v3, but I'm not sure if there is anything to do on my side.

Update: @brunoNetId No its a different stack causing this so nothing is needed on your side to do here.

Copy link
Member

@michael-valdron michael-valdron left a comment

Choose a reason for hiding this comment

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

@brunoNetId Try a rebase to the latest changes from main now.

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

Successfully merging this pull request may close these issues.

5 participants