[GitHub] [ofbiz-framework]: Workflow run "Java CI with Gradle" is working again!
The GitHub Actions job "Java CI with Gradle" on ofbiz-framework.git has succeeded. Run started by GitHub user asfgit (triggered by asfgit). Head commit for run: 50a7044d230f44404418d8b77a5aa9f813531926 / Jacques Le Roux Fixed: We have build problems in branches with plugins (OFBIZ-11284) OK must be https://github.com/apache/ofbiz-plugins/branches/... But does not work for trunk (410): https://github.com/apache/ofbiz-plugins/branches/trunk So we really need to amend https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz Report URL: https://github.com/apache/ofbiz-framework/actions/runs/4166724770 With regards, GitHub Actions via GitBox
[jira] [Commented] (OFBIZ-11284) We have build problems in branches with plugins
[ https://issues.apache.org/jira/browse/OFBIZ-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688081#comment-17688081 ] ASF subversion and git services commented on OFBIZ-11284: - Commit 50a7044d230f44404418d8b77a5aa9f813531926 in ofbiz-framework's branch refs/heads/release22.01 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=50a7044d23 ] Fixed: We have build problems in branches with plugins (OFBIZ-11284) OK must be https://github.com/apache/ofbiz-plugins/branches/... But does not work for trunk (410): https://github.com/apache/ofbiz-plugins/branches/trunk So we really need to amend https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz > We have build problems in branches with plugins > --- > > Key: OFBIZ-11284 > URL: https://issues.apache.org/jira/browse/OFBIZ-11284 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Release Branch 18.12, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 18.12.01 > > > There are discrepancies between Gitbox and Github Subversion. Mostly diamond > use on Github Subversion not in Gitbox , and few others -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-11284) We have build problems in branches with plugins
[ https://issues.apache.org/jira/browse/OFBIZ-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688082#comment-17688082 ] ASF subversion and git services commented on OFBIZ-11284: - Commit 499e7acd76e7d030d1d2259ced147db1a60335da in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=499e7acd76 ] Fixed: We have build problems in branches with plugins (OFBIZ-11284) OK must be https://github.com/apache/ofbiz-plugins/branches/... But does not work for trunk (410): https://github.com/apache/ofbiz-plugins/branches/trunk So we really need to amend https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz > We have build problems in branches with plugins > --- > > Key: OFBIZ-11284 > URL: https://issues.apache.org/jira/browse/OFBIZ-11284 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Release Branch 18.12, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 18.12.01 > > > There are discrepancies between Gitbox and Github Subversion. Mostly diamond > use on Github Subversion not in Gitbox , and few others -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (OFBIZ-11284) We have build problems in branches with plugins
[ https://issues.apache.org/jira/browse/OFBIZ-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-11284. --- Fix Version/s: 22.01.01 Resolution: Fixed > We have build problems in branches with plugins > --- > > Key: OFBIZ-11284 > URL: https://issues.apache.org/jira/browse/OFBIZ-11284 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Release Branch 18.12, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 22.01.01, 18.12.01, 17.12.01 > > > There are discrepancies between Gitbox and Github Subversion. Mostly diamond > use on Github Subversion not in Gitbox , and few others -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-11284) We have build problems in branches with plugins
[ https://issues.apache.org/jira/browse/OFBIZ-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688073#comment-17688073 ] Jacques Le Roux commented on OFBIZ-11284: - OK must be https://github.com/apache/ofbiz-plugins/branches/... But does not work for trunk (410): https://github.com/apache/ofbiz-plugins/branches/trunk So we really need to amend https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz (cf. OFBIZ-12757 for initial remark) > We have build problems in branches with plugins > --- > > Key: OFBIZ-11284 > URL: https://issues.apache.org/jira/browse/OFBIZ-11284 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Release Branch 18.12, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 18.12.01 > > > There are discrepancies between Gitbox and Github Subversion. Mostly diamond > use on Github Subversion not in Gitbox , and few others -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (OFBIZ-11284) We have build problems in branches with plugins
[ https://issues.apache.org/jira/browse/OFBIZ-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688066#comment-17688066 ] Jacques Le Roux edited comment on OFBIZ-11284 at 2/13/23 6:23 PM: -- It worked locally but not in CI (GH anb BB) * What went wrong: Execution failed for task ':pullPluginsFromSvn'. > svn-checkout failed for https://github.com/apache/ofbiz-plugins/release22.01 svn: E17: URL 'https://github.com/apache/ofbiz-plugins/release22.01' doesn't exist was (Author: jacques.le.roux): It worked locally but not in CI (GH anb BB) > We have build problems in branches with plugins > --- > > Key: OFBIZ-11284 > URL: https://issues.apache.org/jira/browse/OFBIZ-11284 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Release Branch 18.12, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 18.12.01 > > > There are discrepancies between Gitbox and Github Subversion. Mostly diamond > use on Github Subversion not in Gitbox , and few others -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (OFBIZ-11284) We have build problems in branches with plugins
[ https://issues.apache.org/jira/browse/OFBIZ-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reopened OFBIZ-11284: - It worked locally but not in CI (GH anb BB) > We have build problems in branches with plugins > --- > > Key: OFBIZ-11284 > URL: https://issues.apache.org/jira/browse/OFBIZ-11284 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Release Branch 18.12, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 18.12.01 > > > There are discrepancies between Gitbox and Github Subversion. Mostly diamond > use on Github Subversion not in Gitbox , and few others -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [ofbiz-framework]: Workflow run "Java CI with Gradle" failed!
The GitHub Actions job "Java CI with Gradle" on ofbiz-framework.git has failed. Run started by GitHub user asfgit (triggered by asfgit). Head commit for run: 450195921698a35c5cba22325af315b510764dfe / Jacques Le Roux Fixed: We have build problems in branches with plugins (OFBIZ-11284) Fixes using Subversion over Github in build.gradle to avoid hard coded branches and rather uses the real current branch While at it, replaces curled double and single quotes by straight ones Report URL: https://github.com/apache/ofbiz-framework/actions/runs/4166196614 With regards, GitHub Actions via GitBox
[jira] [Commented] (OFBIZ-11284) We have build problems in branches with plugins
[ https://issues.apache.org/jira/browse/OFBIZ-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688047#comment-17688047 ] ASF subversion and git services commented on OFBIZ-11284: - Commit 450195921698a35c5cba22325af315b510764dfe in ofbiz-framework's branch refs/heads/release22.01 from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=4501959216 ] Fixed: We have build problems in branches with plugins (OFBIZ-11284) Fixes using Subversion over Github in build.gradle to avoid hard coded branches and rather uses the real current branch While at it, replaces curled double and single quotes by straight ones > We have build problems in branches with plugins > --- > > Key: OFBIZ-11284 > URL: https://issues.apache.org/jira/browse/OFBIZ-11284 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Release Branch 18.12, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 18.12.01 > > > There are discrepancies between Gitbox and Github Subversion. Mostly diamond > use on Github Subversion not in Gitbox , and few others -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12757) Experiment with deploying OFBiz containers to the demo sites server
[ https://issues.apache.org/jira/browse/OFBIZ-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688045#comment-17688045 ] Jacques Le Roux commented on OFBIZ-12757: - Done with OFBIZ-11284 > Experiment with deploying OFBiz containers to the demo sites server > --- > > Key: OFBIZ-12757 > URL: https://issues.apache.org/jira/browse/OFBIZ-12757 > Project: OFBiz > Issue Type: New Feature > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > This ticket has been created to track and report on progress with deploying > OFBiz to the demo server (ofbiz-vm1.apache.org) using docker containers. > The rest of this ticket's description is an excerpt from a message sent to > the PMC requesting server access and describing the intention behind the > request. It is included here are it gives an overview of the experiment: > > ... I would like to explore the configuration of the VM and experiment with > hosting an instance of OFBiz in a docker container. > > If experimentation with container based deployments of OFBiz demo sites is > successful, I believe the project could leverage such deployments in future > to avoid issues around the installed JDK version not being compatible with > all current demo sites. > h1. Proposed approach: > * Create a branch in the ofbiz-framework repository from trunk where > Dockerfiles and other changes to the build process needed to produce Docker > containers for demo sites can be implemented. > * Create one or more CNAME DNS entries, pointing to > [ofbiz-vm1.apache.org|http://ofbiz-vm1.apache.org/], which can be used to > access any experimental container-based demo site instances. > * Deploy Traefik as a reverse proxy to access the experimental demo sites, > assuming this approach does not conflict with any reverse proxy solution > already in place on the VM - hence the need to gain access and explore the > current server configuration. > * Create build configuration(s) for the new branch to build the > ofbiz-framework as a container image with pre-loaded demo data, and push the > container image to an appropriate container repository. > * Implement scripts at the VM to pull and deploy the latest version of the > demo container image daily. > h1. Items to explore/resolve: > h2. How should we build container images? > We should be able to use either BuildBot or GitHub Actions for this. I assume > BuildBot is preferred since we already have builds running in that service > and it is managed directly by the ASF. > h2. Where should we store built container images? > Infra have advised (via Slack) that the ASF has a space within Docker Hub and > also has an Artifactory instance ([apache.jfrog.io|http://apache.jfrog.io/]). > It looks like we are free to use either to host container images. I imagine > we would want to use whichever service helps us manage the lifecycle of > container images (e.g. expire older images). > h2. How to create DNS entries? > I imagine Infra will advise. > h1. Expected benefits if experiment is successful: > * All dependencies used by OFBiz, including the JDK, are packaged in the > container image. We should be able to deploy different instances of OFBiz on > the same VM without fear of JDK version clash. > * Act as a catalyst to help the project settle on an approach to > containerisation and further alter OFBiz to better support container > deployments. > * Provide an alternative deployment option for users to deploy and evaluate > OFBiz. > * Help committers test PRs: > ** I often test PRs by creating a trunk container image with demo data > loaded. From this I then create a second image, specific to the PR under > test, which is fast to build and load since the bulk of computation and data > processing has already been handled in the base image. Once testing is > complete I throw away the second image and can quickly resume work from the > base image. > h1. Future work if experiment is successful: > * Incorporate container build scripts into trunk. > * Build versions of the OFBiz demo container that include plugins. > * Start using containers for demo site deployments. > * Promote containers as a supported deployment mechanism: > ** Develop guidance for connecting OFBiz containers with external databases. > ** See this GitHub repository for a setup of OFBiz with PostgreSQL: > [danwatford/docker-postgres-ofbiz > (github.com)|https://github.com/danwatford/docker-postgres-ofbiz] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-11284) We have build problems in branches with plugins
[ https://issues.apache.org/jira/browse/OFBIZ-11284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688038#comment-17688038 ] ASF subversion and git services commented on OFBIZ-11284: - Commit 8f5a44cce31f5eed2abd0297477bfbc1b3c8afa0 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux [ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=8f5a44cce3 ] Fixed: We have build problems in branches with plugins (OFBIZ-11284) Fixes using Subversion over Github in build.gradle to avoid hard coded branches and rather uses the real current branch While at it, replaces curled double and single quotes by straight ones > We have build problems in branches with plugins > --- > > Key: OFBIZ-11284 > URL: https://issues.apache.org/jira/browse/OFBIZ-11284 > Project: OFBiz > Issue Type: Sub-task >Affects Versions: Release Branch 18.12, Release Branch 17.12 >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Major > Fix For: 17.12.01, 18.12.01 > > > There are discrepancies between Gitbox and Github Subversion. Mostly diamond > use on Github Subversion not in Gitbox , and few others -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12757) Experiment with deploying OFBiz containers to the demo sites server
[
https://issues.apache.org/jira/browse/OFBIZ-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687995#comment-17687995
]
Jacques Le Roux commented on OFBIZ-12757:
-
No need to amend wiki, I'll use {{git branch --show-current}}
> Experiment with deploying OFBiz containers to the demo sites server
> ---
>
> Key: OFBIZ-12757
> URL: https://issues.apache.org/jira/browse/OFBIZ-12757
> Project: OFBiz
> Issue Type: New Feature
> Components: Demo
>Affects Versions: Upcoming Branch
>Reporter: Daniel Watford
>Assignee: Daniel Watford
>Priority: Trivial
>
> This ticket has been created to track and report on progress with deploying
> OFBiz to the demo server (ofbiz-vm1.apache.org) using docker containers.
> The rest of this ticket's description is an excerpt from a message sent to
> the PMC requesting server access and describing the intention behind the
> request. It is included here are it gives an overview of the experiment:
>
> ... I would like to explore the configuration of the VM and experiment with
> hosting an instance of OFBiz in a docker container.
>
> If experimentation with container based deployments of OFBiz demo sites is
> successful, I believe the project could leverage such deployments in future
> to avoid issues around the installed JDK version not being compatible with
> all current demo sites.
> h1. Proposed approach:
> * Create a branch in the ofbiz-framework repository from trunk where
> Dockerfiles and other changes to the build process needed to produce Docker
> containers for demo sites can be implemented.
> * Create one or more CNAME DNS entries, pointing to
> [ofbiz-vm1.apache.org|http://ofbiz-vm1.apache.org/], which can be used to
> access any experimental container-based demo site instances.
> * Deploy Traefik as a reverse proxy to access the experimental demo sites,
> assuming this approach does not conflict with any reverse proxy solution
> already in place on the VM - hence the need to gain access and explore the
> current server configuration.
> * Create build configuration(s) for the new branch to build the
> ofbiz-framework as a container image with pre-loaded demo data, and push the
> container image to an appropriate container repository.
> * Implement scripts at the VM to pull and deploy the latest version of the
> demo container image daily.
> h1. Items to explore/resolve:
> h2. How should we build container images?
> We should be able to use either BuildBot or GitHub Actions for this. I assume
> BuildBot is preferred since we already have builds running in that service
> and it is managed directly by the ASF.
> h2. Where should we store built container images?
> Infra have advised (via Slack) that the ASF has a space within Docker Hub and
> also has an Artifactory instance ([apache.jfrog.io|http://apache.jfrog.io/]).
> It looks like we are free to use either to host container images. I imagine
> we would want to use whichever service helps us manage the lifecycle of
> container images (e.g. expire older images).
> h2. How to create DNS entries?
> I imagine Infra will advise.
> h1. Expected benefits if experiment is successful:
> * All dependencies used by OFBiz, including the JDK, are packaged in the
> container image. We should be able to deploy different instances of OFBiz on
> the same VM without fear of JDK version clash.
> * Act as a catalyst to help the project settle on an approach to
> containerisation and further alter OFBiz to better support container
> deployments.
> * Provide an alternative deployment option for users to deploy and evaluate
> OFBiz.
> * Help committers test PRs:
> ** I often test PRs by creating a trunk container image with demo data
> loaded. From this I then create a second image, specific to the PR under
> test, which is fast to build and load since the bulk of computation and data
> processing has already been handled in the base image. Once testing is
> complete I throw away the second image and can quickly resume work from the
> base image.
> h1. Future work if experiment is successful:
> * Incorporate container build scripts into trunk.
> * Build versions of the OFBiz demo container that include plugins.
> * Start using containers for demo site deployments.
> * Promote containers as a supported deployment mechanism:
> ** Develop guidance for connecting OFBiz containers with external databases.
> ** See this GitHub repository for a setup of OFBiz with PostgreSQL:
> [danwatford/docker-postgres-ofbiz
> (github.com)|https://github.com/danwatford/docker-postgres-ofbiz]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OFBIZ-12757) Experiment with deploying OFBiz containers to the demo sites server
[ https://issues.apache.org/jira/browse/OFBIZ-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687992#comment-17687992 ] Jacques Le Roux commented on OFBIZ-12757: - OK, this was handled with OFBIZ-11284 and forgotten for 22.01. I'll fix that and amend https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz > Experiment with deploying OFBiz containers to the demo sites server > --- > > Key: OFBIZ-12757 > URL: https://issues.apache.org/jira/browse/OFBIZ-12757 > Project: OFBiz > Issue Type: New Feature > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > This ticket has been created to track and report on progress with deploying > OFBiz to the demo server (ofbiz-vm1.apache.org) using docker containers. > The rest of this ticket's description is an excerpt from a message sent to > the PMC requesting server access and describing the intention behind the > request. It is included here are it gives an overview of the experiment: > > ... I would like to explore the configuration of the VM and experiment with > hosting an instance of OFBiz in a docker container. > > If experimentation with container based deployments of OFBiz demo sites is > successful, I believe the project could leverage such deployments in future > to avoid issues around the installed JDK version not being compatible with > all current demo sites. > h1. Proposed approach: > * Create a branch in the ofbiz-framework repository from trunk where > Dockerfiles and other changes to the build process needed to produce Docker > containers for demo sites can be implemented. > * Create one or more CNAME DNS entries, pointing to > [ofbiz-vm1.apache.org|http://ofbiz-vm1.apache.org/], which can be used to > access any experimental container-based demo site instances. > * Deploy Traefik as a reverse proxy to access the experimental demo sites, > assuming this approach does not conflict with any reverse proxy solution > already in place on the VM - hence the need to gain access and explore the > current server configuration. > * Create build configuration(s) for the new branch to build the > ofbiz-framework as a container image with pre-loaded demo data, and push the > container image to an appropriate container repository. > * Implement scripts at the VM to pull and deploy the latest version of the > demo container image daily. > h1. Items to explore/resolve: > h2. How should we build container images? > We should be able to use either BuildBot or GitHub Actions for this. I assume > BuildBot is preferred since we already have builds running in that service > and it is managed directly by the ASF. > h2. Where should we store built container images? > Infra have advised (via Slack) that the ASF has a space within Docker Hub and > also has an Artifactory instance ([apache.jfrog.io|http://apache.jfrog.io/]). > It looks like we are free to use either to host container images. I imagine > we would want to use whichever service helps us manage the lifecycle of > container images (e.g. expire older images). > h2. How to create DNS entries? > I imagine Infra will advise. > h1. Expected benefits if experiment is successful: > * All dependencies used by OFBiz, including the JDK, are packaged in the > container image. We should be able to deploy different instances of OFBiz on > the same VM without fear of JDK version clash. > * Act as a catalyst to help the project settle on an approach to > containerisation and further alter OFBiz to better support container > deployments. > * Provide an alternative deployment option for users to deploy and evaluate > OFBiz. > * Help committers test PRs: > ** I often test PRs by creating a trunk container image with demo data > loaded. From this I then create a second image, specific to the PR under > test, which is fast to build and load since the bulk of computation and data > processing has already been handled in the base image. Once testing is > complete I throw away the second image and can quickly resume work from the > base image. > h1. Future work if experiment is successful: > * Incorporate container build scripts into trunk. > * Build versions of the OFBiz demo container that include plugins. > * Start using containers for demo site deployments. > * Promote containers as a supported deployment mechanism: > ** Develop guidance for connecting OFBiz containers with external databases. > ** See this GitHub repository for a setup of OFBiz with PostgreSQL: > [danwatford/docker-postgres-ofbiz > (github.com)|https://github.com/danwatford/docker-postgres-ofbiz] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12757) Experiment with deploying OFBiz containers to the demo sites server
[ https://issues.apache.org/jira/browse/OFBIZ-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687990#comment-17687990 ] Jacques Le Roux commented on OFBIZ-12757: - BTW, I just realised that we always use the trunk version of plugins. I don't remember if we agreed about it or if it's slipped-up. > Experiment with deploying OFBiz containers to the demo sites server > --- > > Key: OFBIZ-12757 > URL: https://issues.apache.org/jira/browse/OFBIZ-12757 > Project: OFBiz > Issue Type: New Feature > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > This ticket has been created to track and report on progress with deploying > OFBiz to the demo server (ofbiz-vm1.apache.org) using docker containers. > The rest of this ticket's description is an excerpt from a message sent to > the PMC requesting server access and describing the intention behind the > request. It is included here are it gives an overview of the experiment: > > ... I would like to explore the configuration of the VM and experiment with > hosting an instance of OFBiz in a docker container. > > If experimentation with container based deployments of OFBiz demo sites is > successful, I believe the project could leverage such deployments in future > to avoid issues around the installed JDK version not being compatible with > all current demo sites. > h1. Proposed approach: > * Create a branch in the ofbiz-framework repository from trunk where > Dockerfiles and other changes to the build process needed to produce Docker > containers for demo sites can be implemented. > * Create one or more CNAME DNS entries, pointing to > [ofbiz-vm1.apache.org|http://ofbiz-vm1.apache.org/], which can be used to > access any experimental container-based demo site instances. > * Deploy Traefik as a reverse proxy to access the experimental demo sites, > assuming this approach does not conflict with any reverse proxy solution > already in place on the VM - hence the need to gain access and explore the > current server configuration. > * Create build configuration(s) for the new branch to build the > ofbiz-framework as a container image with pre-loaded demo data, and push the > container image to an appropriate container repository. > * Implement scripts at the VM to pull and deploy the latest version of the > demo container image daily. > h1. Items to explore/resolve: > h2. How should we build container images? > We should be able to use either BuildBot or GitHub Actions for this. I assume > BuildBot is preferred since we already have builds running in that service > and it is managed directly by the ASF. > h2. Where should we store built container images? > Infra have advised (via Slack) that the ASF has a space within Docker Hub and > also has an Artifactory instance ([apache.jfrog.io|http://apache.jfrog.io/]). > It looks like we are free to use either to host container images. I imagine > we would want to use whichever service helps us manage the lifecycle of > container images (e.g. expire older images). > h2. How to create DNS entries? > I imagine Infra will advise. > h1. Expected benefits if experiment is successful: > * All dependencies used by OFBiz, including the JDK, are packaged in the > container image. We should be able to deploy different instances of OFBiz on > the same VM without fear of JDK version clash. > * Act as a catalyst to help the project settle on an approach to > containerisation and further alter OFBiz to better support container > deployments. > * Provide an alternative deployment option for users to deploy and evaluate > OFBiz. > * Help committers test PRs: > ** I often test PRs by creating a trunk container image with demo data > loaded. From this I then create a second image, specific to the PR under > test, which is fast to build and load since the bulk of computation and data > processing has already been handled in the base image. Once testing is > complete I throw away the second image and can quickly resume work from the > base image. > h1. Future work if experiment is successful: > * Incorporate container build scripts into trunk. > * Build versions of the OFBiz demo container that include plugins. > * Start using containers for demo site deployments. > * Promote containers as a supported deployment mechanism: > ** Develop guidance for connecting OFBiz containers with external databases. > ** See this GitHub repository for a setup of OFBiz with PostgreSQL: > [danwatford/docker-postgres-ofbiz > (github.com)|https://github.com/danwatford/docker-postgres-ofbiz] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12757) Experiment with deploying OFBiz containers to the demo sites server
[ https://issues.apache.org/jira/browse/OFBIZ-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687986#comment-17687986 ] Jacques Le Roux commented on OFBIZ-12757: - As mentionned in main build.gradle[985]: bq. // GitHub SVN feature https://docs.github.com/en/github/importing-your-projects-to-github/working-with-subversion-on-github/support-for-subversion-clients > Experiment with deploying OFBiz containers to the demo sites server > --- > > Key: OFBIZ-12757 > URL: https://issues.apache.org/jira/browse/OFBIZ-12757 > Project: OFBiz > Issue Type: New Feature > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > This ticket has been created to track and report on progress with deploying > OFBiz to the demo server (ofbiz-vm1.apache.org) using docker containers. > The rest of this ticket's description is an excerpt from a message sent to > the PMC requesting server access and describing the intention behind the > request. It is included here are it gives an overview of the experiment: > > ... I would like to explore the configuration of the VM and experiment with > hosting an instance of OFBiz in a docker container. > > If experimentation with container based deployments of OFBiz demo sites is > successful, I believe the project could leverage such deployments in future > to avoid issues around the installed JDK version not being compatible with > all current demo sites. > h1. Proposed approach: > * Create a branch in the ofbiz-framework repository from trunk where > Dockerfiles and other changes to the build process needed to produce Docker > containers for demo sites can be implemented. > * Create one or more CNAME DNS entries, pointing to > [ofbiz-vm1.apache.org|http://ofbiz-vm1.apache.org/], which can be used to > access any experimental container-based demo site instances. > * Deploy Traefik as a reverse proxy to access the experimental demo sites, > assuming this approach does not conflict with any reverse proxy solution > already in place on the VM - hence the need to gain access and explore the > current server configuration. > * Create build configuration(s) for the new branch to build the > ofbiz-framework as a container image with pre-loaded demo data, and push the > container image to an appropriate container repository. > * Implement scripts at the VM to pull and deploy the latest version of the > demo container image daily. > h1. Items to explore/resolve: > h2. How should we build container images? > We should be able to use either BuildBot or GitHub Actions for this. I assume > BuildBot is preferred since we already have builds running in that service > and it is managed directly by the ASF. > h2. Where should we store built container images? > Infra have advised (via Slack) that the ASF has a space within Docker Hub and > also has an Artifactory instance ([apache.jfrog.io|http://apache.jfrog.io/]). > It looks like we are free to use either to host container images. I imagine > we would want to use whichever service helps us manage the lifecycle of > container images (e.g. expire older images). > h2. How to create DNS entries? > I imagine Infra will advise. > h1. Expected benefits if experiment is successful: > * All dependencies used by OFBiz, including the JDK, are packaged in the > container image. We should be able to deploy different instances of OFBiz on > the same VM without fear of JDK version clash. > * Act as a catalyst to help the project settle on an approach to > containerisation and further alter OFBiz to better support container > deployments. > * Provide an alternative deployment option for users to deploy and evaluate > OFBiz. > * Help committers test PRs: > ** I often test PRs by creating a trunk container image with demo data > loaded. From this I then create a second image, specific to the PR under > test, which is fast to build and load since the bulk of computation and data > processing has already been handled in the base image. Once testing is > complete I throw away the second image and can quickly resume work from the > base image. > h1. Future work if experiment is successful: > * Incorporate container build scripts into trunk. > * Build versions of the OFBiz demo container that include plugins. > * Start using containers for demo site deployments. > * Promote containers as a supported deployment mechanism: > ** Develop guidance for connecting OFBiz containers with external databases. > ** See this GitHub repository for a setup of OFBiz with PostgreSQL: > [danwatford/docker-postgres-ofbiz > (github.com)|https://github.com/danwatford/docker-postgres-ofbiz] > -- This message was sent by
[jira] [Commented] (OFBIZ-12757) Experiment with deploying OFBiz containers to the demo sites server
[ https://issues.apache.org/jira/browse/OFBIZ-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687964#comment-17687964 ] Daniel Watford commented on OFBIZ-12757: [~jleroux] Is a script actually trying to run Subversion commands, or is svn-checkout an alias for 'git pull' or something similar? > Experiment with deploying OFBiz containers to the demo sites server > --- > > Key: OFBIZ-12757 > URL: https://issues.apache.org/jira/browse/OFBIZ-12757 > Project: OFBiz > Issue Type: New Feature > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > This ticket has been created to track and report on progress with deploying > OFBiz to the demo server (ofbiz-vm1.apache.org) using docker containers. > The rest of this ticket's description is an excerpt from a message sent to > the PMC requesting server access and describing the intention behind the > request. It is included here are it gives an overview of the experiment: > > ... I would like to explore the configuration of the VM and experiment with > hosting an instance of OFBiz in a docker container. > > If experimentation with container based deployments of OFBiz demo sites is > successful, I believe the project could leverage such deployments in future > to avoid issues around the installed JDK version not being compatible with > all current demo sites. > h1. Proposed approach: > * Create a branch in the ofbiz-framework repository from trunk where > Dockerfiles and other changes to the build process needed to produce Docker > containers for demo sites can be implemented. > * Create one or more CNAME DNS entries, pointing to > [ofbiz-vm1.apache.org|http://ofbiz-vm1.apache.org/], which can be used to > access any experimental container-based demo site instances. > * Deploy Traefik as a reverse proxy to access the experimental demo sites, > assuming this approach does not conflict with any reverse proxy solution > already in place on the VM - hence the need to gain access and explore the > current server configuration. > * Create build configuration(s) for the new branch to build the > ofbiz-framework as a container image with pre-loaded demo data, and push the > container image to an appropriate container repository. > * Implement scripts at the VM to pull and deploy the latest version of the > demo container image daily. > h1. Items to explore/resolve: > h2. How should we build container images? > We should be able to use either BuildBot or GitHub Actions for this. I assume > BuildBot is preferred since we already have builds running in that service > and it is managed directly by the ASF. > h2. Where should we store built container images? > Infra have advised (via Slack) that the ASF has a space within Docker Hub and > also has an Artifactory instance ([apache.jfrog.io|http://apache.jfrog.io/]). > It looks like we are free to use either to host container images. I imagine > we would want to use whichever service helps us manage the lifecycle of > container images (e.g. expire older images). > h2. How to create DNS entries? > I imagine Infra will advise. > h1. Expected benefits if experiment is successful: > * All dependencies used by OFBiz, including the JDK, are packaged in the > container image. We should be able to deploy different instances of OFBiz on > the same VM without fear of JDK version clash. > * Act as a catalyst to help the project settle on an approach to > containerisation and further alter OFBiz to better support container > deployments. > * Provide an alternative deployment option for users to deploy and evaluate > OFBiz. > * Help committers test PRs: > ** I often test PRs by creating a trunk container image with demo data > loaded. From this I then create a second image, specific to the PR under > test, which is fast to build and load since the bulk of computation and data > processing has already been handled in the base image. Once testing is > complete I throw away the second image and can quickly resume work from the > base image. > h1. Future work if experiment is successful: > * Incorporate container build scripts into trunk. > * Build versions of the OFBiz demo container that include plugins. > * Start using containers for demo site deployments. > * Promote containers as a supported deployment mechanism: > ** Develop guidance for connecting OFBiz containers with external databases. > ** See this GitHub repository for a setup of OFBiz with PostgreSQL: > [danwatford/docker-postgres-ofbiz > (github.com)|https://github.com/danwatford/docker-postgres-ofbiz] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12757) Experiment with deploying OFBiz containers to the demo sites server
[ https://issues.apache.org/jira/browse/OFBIZ-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687950#comment-17687950 ] Jacques Le Roux commented on OFBIZ-12757: - It's that, VM failure, multiple errors: > Task :pullPluginsFromSvn FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':pullPluginsFromSvn'. > svn-checkout failed for https://github.com/apache/ofbiz-plugins/trunk svn: E175002: PROPFIND of '/apache/ofbiz-plugins/trunk': 500 Internal Server Error (https://github.com) Execution failed for task ':pullPluginsFromSvn'. > svn-checkout failed for > https://github.com/apache/ofbiz-plugins/branches/release18.12 svn: E175002: OPTIONS of '/apache/ofbiz-plugins/branches/release18.12': 500 Internal Server Error (https://github.com) svn: E175002: OPTIONS request failed on '/apache/ofbiz-plugins/branches/release18.12' > Experiment with deploying OFBiz containers to the demo sites server > --- > > Key: OFBIZ-12757 > URL: https://issues.apache.org/jira/browse/OFBIZ-12757 > Project: OFBiz > Issue Type: New Feature > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > This ticket has been created to track and report on progress with deploying > OFBiz to the demo server (ofbiz-vm1.apache.org) using docker containers. > The rest of this ticket's description is an excerpt from a message sent to > the PMC requesting server access and describing the intention behind the > request. It is included here are it gives an overview of the experiment: > > ... I would like to explore the configuration of the VM and experiment with > hosting an instance of OFBiz in a docker container. > > If experimentation with container based deployments of OFBiz demo sites is > successful, I believe the project could leverage such deployments in future > to avoid issues around the installed JDK version not being compatible with > all current demo sites. > h1. Proposed approach: > * Create a branch in the ofbiz-framework repository from trunk where > Dockerfiles and other changes to the build process needed to produce Docker > containers for demo sites can be implemented. > * Create one or more CNAME DNS entries, pointing to > [ofbiz-vm1.apache.org|http://ofbiz-vm1.apache.org/], which can be used to > access any experimental container-based demo site instances. > * Deploy Traefik as a reverse proxy to access the experimental demo sites, > assuming this approach does not conflict with any reverse proxy solution > already in place on the VM - hence the need to gain access and explore the > current server configuration. > * Create build configuration(s) for the new branch to build the > ofbiz-framework as a container image with pre-loaded demo data, and push the > container image to an appropriate container repository. > * Implement scripts at the VM to pull and deploy the latest version of the > demo container image daily. > h1. Items to explore/resolve: > h2. How should we build container images? > We should be able to use either BuildBot or GitHub Actions for this. I assume > BuildBot is preferred since we already have builds running in that service > and it is managed directly by the ASF. > h2. Where should we store built container images? > Infra have advised (via Slack) that the ASF has a space within Docker Hub and > also has an Artifactory instance ([apache.jfrog.io|http://apache.jfrog.io/]). > It looks like we are free to use either to host container images. I imagine > we would want to use whichever service helps us manage the lifecycle of > container images (e.g. expire older images). > h2. How to create DNS entries? > I imagine Infra will advise. > h1. Expected benefits if experiment is successful: > * All dependencies used by OFBiz, including the JDK, are packaged in the > container image. We should be able to deploy different instances of OFBiz on > the same VM without fear of JDK version clash. > * Act as a catalyst to help the project settle on an approach to > containerisation and further alter OFBiz to better support container > deployments. > * Provide an alternative deployment option for users to deploy and evaluate > OFBiz. > * Help committers test PRs: > ** I often test PRs by creating a trunk container image with demo data > loaded. From this I then create a second image, specific to the PR under > test, which is fast to build and load since the bulk of computation and data > processing has already been handled in the base image. Once testing is > complete I throw away the second image and can quickly resume work from the > base image. > h1. Future work if experiment is successful: > * Incorporate
[jira] [Commented] (OFBIZ-12757) Experiment with deploying OFBiz containers to the demo sites server
[ https://issues.apache.org/jira/browse/OFBIZ-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687916#comment-17687916 ] Jacques Le Roux commented on OFBIZ-12757: - Thanks Daniel, Indeed, could be a temporary issue on the VM. Let's forget it ;) > Experiment with deploying OFBiz containers to the demo sites server > --- > > Key: OFBIZ-12757 > URL: https://issues.apache.org/jira/browse/OFBIZ-12757 > Project: OFBiz > Issue Type: New Feature > Components: Demo >Affects Versions: Upcoming Branch >Reporter: Daniel Watford >Assignee: Daniel Watford >Priority: Trivial > > This ticket has been created to track and report on progress with deploying > OFBiz to the demo server (ofbiz-vm1.apache.org) using docker containers. > The rest of this ticket's description is an excerpt from a message sent to > the PMC requesting server access and describing the intention behind the > request. It is included here are it gives an overview of the experiment: > > ... I would like to explore the configuration of the VM and experiment with > hosting an instance of OFBiz in a docker container. > > If experimentation with container based deployments of OFBiz demo sites is > successful, I believe the project could leverage such deployments in future > to avoid issues around the installed JDK version not being compatible with > all current demo sites. > h1. Proposed approach: > * Create a branch in the ofbiz-framework repository from trunk where > Dockerfiles and other changes to the build process needed to produce Docker > containers for demo sites can be implemented. > * Create one or more CNAME DNS entries, pointing to > [ofbiz-vm1.apache.org|http://ofbiz-vm1.apache.org/], which can be used to > access any experimental container-based demo site instances. > * Deploy Traefik as a reverse proxy to access the experimental demo sites, > assuming this approach does not conflict with any reverse proxy solution > already in place on the VM - hence the need to gain access and explore the > current server configuration. > * Create build configuration(s) for the new branch to build the > ofbiz-framework as a container image with pre-loaded demo data, and push the > container image to an appropriate container repository. > * Implement scripts at the VM to pull and deploy the latest version of the > demo container image daily. > h1. Items to explore/resolve: > h2. How should we build container images? > We should be able to use either BuildBot or GitHub Actions for this. I assume > BuildBot is preferred since we already have builds running in that service > and it is managed directly by the ASF. > h2. Where should we store built container images? > Infra have advised (via Slack) that the ASF has a space within Docker Hub and > also has an Artifactory instance ([apache.jfrog.io|http://apache.jfrog.io/]). > It looks like we are free to use either to host container images. I imagine > we would want to use whichever service helps us manage the lifecycle of > container images (e.g. expire older images). > h2. How to create DNS entries? > I imagine Infra will advise. > h1. Expected benefits if experiment is successful: > * All dependencies used by OFBiz, including the JDK, are packaged in the > container image. We should be able to deploy different instances of OFBiz on > the same VM without fear of JDK version clash. > * Act as a catalyst to help the project settle on an approach to > containerisation and further alter OFBiz to better support container > deployments. > * Provide an alternative deployment option for users to deploy and evaluate > OFBiz. > * Help committers test PRs: > ** I often test PRs by creating a trunk container image with demo data > loaded. From this I then create a second image, specific to the PR under > test, which is fast to build and load since the bulk of computation and data > processing has already been handled in the base image. Once testing is > complete I throw away the second image and can quickly resume work from the > base image. > h1. Future work if experiment is successful: > * Incorporate container build scripts into trunk. > * Build versions of the OFBiz demo container that include plugins. > * Start using containers for demo site deployments. > * Promote containers as a supported deployment mechanism: > ** Develop guidance for connecting OFBiz containers with external databases. > ** See this GitHub repository for a setup of OFBiz with PostgreSQL: > [danwatford/docker-postgres-ofbiz > (github.com)|https://github.com/danwatford/docker-postgres-ofbiz] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OFBIZ-12757) Experiment with deploying OFBiz containers to the demo sites server
[
https://issues.apache.org/jira/browse/OFBIZ-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687910#comment-17687910
]
Daniel Watford commented on OFBIZ-12757:
Hi [~jleroux] ,
I shut down the all containers at 2023-02-11 12:26 as I didn't want to leave
them running unattended,
Something that might be of interest, this was in the cronlog-svn-update.log
files:
{noformat}
./stable-manual.sh: line 28: ./gradlew: No such file or directory
./stable-manual.sh: line 29: ./gradlew: No such file or directory
./stable-manual.sh: line 30: ./gradlew: No such file or directory
./stable-manual.sh: line 31: ./gradlew: No such file or directory
./stable-manual.sh: line 32: ./gradlew: No such file or directory{noformat}
I can't see anything obvious to explain why gradlew could not be found.
> Experiment with deploying OFBiz containers to the demo sites server
> ---
>
> Key: OFBIZ-12757
> URL: https://issues.apache.org/jira/browse/OFBIZ-12757
> Project: OFBiz
> Issue Type: New Feature
> Components: Demo
>Affects Versions: Upcoming Branch
>Reporter: Daniel Watford
>Assignee: Daniel Watford
>Priority: Trivial
>
> This ticket has been created to track and report on progress with deploying
> OFBiz to the demo server (ofbiz-vm1.apache.org) using docker containers.
> The rest of this ticket's description is an excerpt from a message sent to
> the PMC requesting server access and describing the intention behind the
> request. It is included here are it gives an overview of the experiment:
>
> ... I would like to explore the configuration of the VM and experiment with
> hosting an instance of OFBiz in a docker container.
>
> If experimentation with container based deployments of OFBiz demo sites is
> successful, I believe the project could leverage such deployments in future
> to avoid issues around the installed JDK version not being compatible with
> all current demo sites.
> h1. Proposed approach:
> * Create a branch in the ofbiz-framework repository from trunk where
> Dockerfiles and other changes to the build process needed to produce Docker
> containers for demo sites can be implemented.
> * Create one or more CNAME DNS entries, pointing to
> [ofbiz-vm1.apache.org|http://ofbiz-vm1.apache.org/], which can be used to
> access any experimental container-based demo site instances.
> * Deploy Traefik as a reverse proxy to access the experimental demo sites,
> assuming this approach does not conflict with any reverse proxy solution
> already in place on the VM - hence the need to gain access and explore the
> current server configuration.
> * Create build configuration(s) for the new branch to build the
> ofbiz-framework as a container image with pre-loaded demo data, and push the
> container image to an appropriate container repository.
> * Implement scripts at the VM to pull and deploy the latest version of the
> demo container image daily.
> h1. Items to explore/resolve:
> h2. How should we build container images?
> We should be able to use either BuildBot or GitHub Actions for this. I assume
> BuildBot is preferred since we already have builds running in that service
> and it is managed directly by the ASF.
> h2. Where should we store built container images?
> Infra have advised (via Slack) that the ASF has a space within Docker Hub and
> also has an Artifactory instance ([apache.jfrog.io|http://apache.jfrog.io/]).
> It looks like we are free to use either to host container images. I imagine
> we would want to use whichever service helps us manage the lifecycle of
> container images (e.g. expire older images).
> h2. How to create DNS entries?
> I imagine Infra will advise.
> h1. Expected benefits if experiment is successful:
> * All dependencies used by OFBiz, including the JDK, are packaged in the
> container image. We should be able to deploy different instances of OFBiz on
> the same VM without fear of JDK version clash.
> * Act as a catalyst to help the project settle on an approach to
> containerisation and further alter OFBiz to better support container
> deployments.
> * Provide an alternative deployment option for users to deploy and evaluate
> OFBiz.
> * Help committers test PRs:
> ** I often test PRs by creating a trunk container image with demo data
> loaded. From this I then create a second image, specific to the PR under
> test, which is fast to build and load since the bulk of computation and data
> processing has already been handled in the base image. Once testing is
> complete I throw away the second image and can quickly resume work from the
> base image.
> h1. Future work if experiment is successful:
> * Incorporate container build scripts into trunk.
> * Build versions of the OFBiz demo container that
[jira] [Commented] (OFBIZ-12757) Experiment with deploying OFBiz containers to the demo sites server
[
https://issues.apache.org/jira/browse/OFBIZ-12757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687812#comment-17687812
]
Jacques Le Roux commented on OFBIZ-12757:
-
Hi Daniel,
I'm not sure it's related, but there are good chances, this morning I had to
restart stable and next demos. It seems they did not start, or did not stop.
That never happened, see next tail of console log:
{noformat}
2023-02-13 03:00:35,645 |.0.0.1-28009-exec-10 |ControlServlet
|T| [[[ordermgr::FindRequirements (Domain:https://demo-next.ofbiz.apache.org)]
Request Done- total:0.229,since last([ordermgr::FindRe...):0.229]]
> Task :ofbiz --start --portoffset 2 FAILED
* Try:
> Run with --stacktrace option to get the stack trace.FAILURE: Build failed
> with an exception.
* What went wrong:
Execution failed for task ':ofbiz --start --portoffset 2'.
> Process 'command
> '/home/ofbizDemo/.sdkman/candidates/java/17.0.2-tem/bin/java'' finished with
> non-zero exit value 137
{noformat}
We will see tmrw. If it happens again I'll dig more...
> Experiment with deploying OFBiz containers to the demo sites server
> ---
>
> Key: OFBIZ-12757
> URL: https://issues.apache.org/jira/browse/OFBIZ-12757
> Project: OFBiz
> Issue Type: New Feature
> Components: Demo
>Affects Versions: Upcoming Branch
>Reporter: Daniel Watford
>Assignee: Daniel Watford
>Priority: Trivial
>
> This ticket has been created to track and report on progress with deploying
> OFBiz to the demo server (ofbiz-vm1.apache.org) using docker containers.
> The rest of this ticket's description is an excerpt from a message sent to
> the PMC requesting server access and describing the intention behind the
> request. It is included here are it gives an overview of the experiment:
>
> ... I would like to explore the configuration of the VM and experiment with
> hosting an instance of OFBiz in a docker container.
>
> If experimentation with container based deployments of OFBiz demo sites is
> successful, I believe the project could leverage such deployments in future
> to avoid issues around the installed JDK version not being compatible with
> all current demo sites.
> h1. Proposed approach:
> * Create a branch in the ofbiz-framework repository from trunk where
> Dockerfiles and other changes to the build process needed to produce Docker
> containers for demo sites can be implemented.
> * Create one or more CNAME DNS entries, pointing to
> [ofbiz-vm1.apache.org|http://ofbiz-vm1.apache.org/], which can be used to
> access any experimental container-based demo site instances.
> * Deploy Traefik as a reverse proxy to access the experimental demo sites,
> assuming this approach does not conflict with any reverse proxy solution
> already in place on the VM - hence the need to gain access and explore the
> current server configuration.
> * Create build configuration(s) for the new branch to build the
> ofbiz-framework as a container image with pre-loaded demo data, and push the
> container image to an appropriate container repository.
> * Implement scripts at the VM to pull and deploy the latest version of the
> demo container image daily.
> h1. Items to explore/resolve:
> h2. How should we build container images?
> We should be able to use either BuildBot or GitHub Actions for this. I assume
> BuildBot is preferred since we already have builds running in that service
> and it is managed directly by the ASF.
> h2. Where should we store built container images?
> Infra have advised (via Slack) that the ASF has a space within Docker Hub and
> also has an Artifactory instance ([apache.jfrog.io|http://apache.jfrog.io/]).
> It looks like we are free to use either to host container images. I imagine
> we would want to use whichever service helps us manage the lifecycle of
> container images (e.g. expire older images).
> h2. How to create DNS entries?
> I imagine Infra will advise.
> h1. Expected benefits if experiment is successful:
> * All dependencies used by OFBiz, including the JDK, are packaged in the
> container image. We should be able to deploy different instances of OFBiz on
> the same VM without fear of JDK version clash.
> * Act as a catalyst to help the project settle on an approach to
> containerisation and further alter OFBiz to better support container
> deployments.
> * Provide an alternative deployment option for users to deploy and evaluate
> OFBiz.
> * Help committers test PRs:
> ** I often test PRs by creating a trunk container image with demo data
> loaded. From this I then create a second image, specific to the PR under
> test, which is fast to build and load since the bulk of computation and data
> processing has already been handled in the base image. Once
[jira] [Commented] (OFBIZ-9984) Convert OrderServices.xml mini-lang to groovyDSL
[ https://issues.apache.org/jira/browse/OFBIZ-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17687808#comment-17687808 ] Gil Portenseigne commented on OFBIZ-9984: - Hello Jacques, IIRW it was not complete, only partly done, as [~sberg] offers to continue the work, i stopped working on it and got on other subject. [~sberg] do you intent to continue ? Thanks Gil > Convert OrderServices.xml mini-lang to groovyDSL > > > Key: OFBIZ-9984 > URL: https://issues.apache.org/jira/browse/OFBIZ-9984 > Project: OFBiz > Issue Type: Sub-task > Components: order >Affects Versions: Trunk, Upcoming Branch >Reporter: Julien NICOLAS >Assignee: Gil Portenseigne >Priority: Minor > Labels: groovy, mini-lang > Attachments: OFBIZ-9984-v1.patch, OFBIZ-9984.patch > > > With the purpose to deprecate mini-lang OFBIZ-9350, I tried to convert some > mini-lang service to groovy script. -- This message was sent by Atlassian Jira (v8.20.10#820010)
