Git Product home page Git Product logo

waltz-docker's People

Contributors

rovats avatar

Stargazers

 avatar

Watchers

 avatar

waltz-docker's Issues

Issue with sql server builds

I can't seem to get this to build with sql server. the original pom for waltz requires a local install of sqljdbc4 but the same trick doesn't seem to work here for some reason.

I have tried multiple times to get docker build to work and installed the file in my local repo using
mvn install:install-file -Dfile=sqljdbc4.jar -Dpackaging=jar -DgroupId=com.microsoft.sqlserver -DartifactId=sqljdbc4 -Dversion=4.0

Not sure if there is something i the dependencies i am missing?

Organise output artifacts better

Currently the are created in build/output/ directory.

It would be better to create them under environment and db specific directories, eg:

build/output/local-postgres

The waltz-web.war file then doesn't need environment in it's name.

Test/Document/Support running builds behind http proxies

  • Document which settings need to be changed
    • In Docker (for pulling base images from docker hub)
    • Containers (for apt-get etc) - env variables?
    • Git
    • Maven
    • npm

Might need to support overriding config for some of these (similar to maven)

Build issues on Linux

I initially tried under Windows 10 but couldn't decide if errors where my fault or actual underlying issues. I''ve therefore switched to first trying the tutorial under Linux. However I cannot get the build to connect to the postgres instance.

I've installed postgres as per the instructions, and populated it using the LoadAll app in waltz-jobs. I can connect to this db on my dev machines Waltz instance (I remapped the port 5432 to 5632 via IntelliJ as the -p 5432:5432 param seemed to have not effect)

image

This works fine when running Waltz's Main and the Waltz's maven build with the appropriate settings, namely:

  <profile>
            <id>local-postgres</id>
            <activation><activeByDefault>false</activeByDefault></activation>
            <properties>
                <database.url>jdbc:postgresql://localhost:5632/waltz</database.url>
                <database.user>waltz</database.user>
                <database.password>waltz</database.password>
                <database.schema>public</database.schema>
                <database.catalog></database.catalog>
            </properties>

Docker

When running the command:

docker build --tag waltz-build:1.26a1 --build-arg maven_profiles=waltz-postgres,local-postgres -f build/build.Dockerfile .

it fails with:

[INFO] waltz .............................................. SUCCESS [ 13.869 s]
[INFO] waltz-common ....................................... SUCCESS [ 12.176 s]
[INFO] waltz-model ........................................ SUCCESS [  9.760 s]
[INFO] waltz-schema ....................................... FAILURE [  2.670 s]
[INFO] waltz-data ......................................... SKIPPED
[INFO] waltz-service ...................................... SKIPPED
[INFO] waltz-web .......................................... SKIPPED
[INFO] waltz-jobs ......................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  38.665 s
[INFO] Finished at: 2020-06-18T15:19:01Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.liquibase:liquibase-maven-plugin:3.5.1:update (default) on project waltz-schema: Error setting up or running Liquibase: liquibase.exception.DatabaseException: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.: Connection refused (Connection refused) -> [Help 1]

I've tried updating the settings xml with both ports (5432 & 5632) and they both give the same error.

Will continue trying things but thought I'd see if you could spot any obvious errors

Test on Windows

  • Document any syntax differences/gotchas
  • See if command syntax can be normalised, to work on both MacOS and Windows (eg: $PWD} when mapping volumes etc)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.