Skip to content

Feature/123 use env to define the configuration paths for doguv3 - #125

Merged
ppxl merged 7 commits into
dogu_v3/developfrom
feature/123-use-env-to-define-the-configuration-paths-for-doguv3
Sep 15, 2026
Merged

ppxl merged 7 commits into
dogu_v3/developfrom
feature/123-use-env-to-define-the-configuration-paths-for-doguv3

Conversation

@manoj-cloudogu

Copy link
Copy Markdown

No description provided.

@ppxl ppxl left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks for the change... again! 💙 😆 I see two things here, mainly the one I have already commented below, and the failing integration test into which you should take a look. Keep in mind though, that for us it suffices to make this dogu v3-ready. But the more we know about upcoming struggles the better...

Comment thread k8s/helm/templates/_helpers.tpl
Comment thread resources/var/tmp/scm/init.script.d/lib/EcoSystem.groovy
Comment thread resources/var/tmp/scm/init.script.d/lib/EcoSystem.groovy Outdated
Comment thread resources/var/tmp/scm/init.script.d/lib/EcoSystem.groovy Outdated
Comment thread Jenkinsfile
@@ -1,5 +1,5 @@
#!groovy
@Library(['github.com/cloudogu/ces-build-lib@5.1.0', 'github.com/cloudogu/dogu-build-lib@v3.5.1', 'github.com/cloudogu/zalenium-build-lib@3092363']) _

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Here is still zalenium used?? (o_O')

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

make no mistake, this dogu maintenance is under the control of the SCM team, so they have their say in selecting a UI int test framework... but still m)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Jeah, would be difficult for us to change this.

     Note to developer to remove the templates when doguctl is no longer used.
@manoj-cloudogu

Copy link
Copy Markdown
Author

Thanks for the change... again! 💙 😆 I see two things here, mainly the one I have already commented below, and the failing integration test into which you should take a look. Keep in mind though, that for us it suffices to make this dogu v3-ready. But the more we know about upcoming struggles the better...

Thanks for the comment 👍 How do I run the Integration tests ? But I see that the Jenkins pipeline succeeded. Can you please inform me where the integration tests are failing?

    Remove the unused  println

@ppxl ppxl left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM thanks, thanks for the change 💙

@ppxl
ppxl merged commit 6ee57cb into dogu_v3/develop Sep 15, 2026
1 check passed
@ppxl
ppxl deleted the feature/123-use-env-to-define-the-configuration-paths-for-doguv3 branch September 15, 2026 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants