Create GitLab CI pipelines to build the "Prudence" web framework using Ant/Maven and deploy to Artifactory

We're a small software company offering web-based applications mainly around online video. For an older project, we are using the "Prudence" platform, which is a polyglot open-source web framework on top of Restlet: [login to view URL] Unfortunately, Prudence is not maintained anymore and prebuilt packages are only available via the original author's "ThreeCrickets" repository, which is however also not updated anymore and out of date: [login to view URL] So the goal of this project here is to create GitLab CI pipelines that build the Prudence stack including its dependencies from source on a docker runner and to deploy the resulting packages to a new Artifactory repository. And this new Artifactory repo is supposed to replace the ThreeCrickets repo. So currently, when building Prudence, there are build and runtime dependencies that are pulled as prebuilt packages from the ThreeCrickets repo. But these dependencies we want to build from source and maintain the resulting packages in our own Artifactory repo so that when building Prudence the ThreeCrickets repo should not be necessary anymore but all dependencies should be either pulled from the new Artifactory repo (with packages built from source) or from official Maven (if the dependency is available there). And the same should be true also for the Prudence example applications, e.g. "Mongovision": [login to view URL] Normally, Mongovision is installed with the command below and pulls its dependencies from the ThreeCrickets repo: sincerity create mycontainer : attach public three-crickets maven [login to view URL] : add [login to view URL] mongovision : install But after this task here is properly done, it should be possible to install Mongovision entirely without the ThreeCrickets repo by instead using the new Artifactory repo (because all the necessary unique dependencies would have been built from source). And for clarification: The ThreeCrickets repository contains a lot of packages which are just mirrored and also available elsewhere, for example Restlet and Jetty. These third-party dependencies do NOT need to be built from source!! Only the "[login to view URL]" packages which are nowhere else available than from the ThreeCrickets repo shall be built from source. So it should be "just" the following projects that need be built from source and for which we need GitLab CI pipelines (if I didn't miss any other obscure dependency...): [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] [login to view URL] We already run our own GitLab installation and our own Artifactory locally in our intranet but we will likely not be able to give you access. So for this task, assume that you'll need your own account at [login to view URL] and that you will need your own Artifactory instance to have a testing environment. Also, you can just fork the original projects on github to make the changes you need to do (e.g. like adding the .[login to view URL]). We'd further require that all environment-specific configurations like the Artifactory URL or Artifactory username/password, etc. should be configurable via variables ( similar to what is described e.g. here: [login to view URL] ) so that we can also easily run the builds on our GitLab installation and with our own Artifactory then later. And if you create a custom docker image to use with GitLab runner for the builds, you'll also need to provide a script/documentation which allows us to re-create the image ourselves from scratch (or from the official image that you started off with).