Customer Portal

CloverETL code deployment

Comments 2

  • Avatar
    admin
    0
    Comment actions Permalink
    Dear Snigdha,

    Yes, export from Designer is one possibility. Also, because our projects/sandboxes are plain directories you can use VCS systems like git, cvs, svn, ... for deploy.

    Also please see viewtopic.php?f=4&t=6750
  • Avatar
    martin_stangler
    0
    Comment actions Permalink
    export/import approach is generally not very good. It is not very common to use exported project as-is with no customization) in enterprise environments

    There are many problems to solve:
    - environment specific artifacts (such as specific urls, credentials, ssh keys, ...)
    - import/update/delete of schedules/services
    - different jndi context format on tomcat (dev) and for example weblogic (other environments)

    In my case shell script only installation is a must - use of designer is forbidden on some envs, server console is forbidden during installation.

    I wrote my own installer shell script suite to call multiple methods of simple http api and web-dav using curl. Some task such as backup existing sandbox before push changes use web service api

    There are many features missing in server api. I miss CRUD methods for schedules, launch services, users, ...

Please sign in to leave a comment.