artifact | The open source design documentation tool for everybody | User Interface library

I'm starting to use gitlab CI/CD pipeline but have some doubts regarding the output of the building process if i was to have a project(Repo) and inside this project I have the front and backend separated by the project structure, ex:

.gitlab-ci.yml

|__FrontEndCarProject

|__BackendCarProject

let's say that every time I change something in the frontend I would need to build it and deploy it to S3, but there is no need to build the backend (java application) and deploy it to elastic beanstalk (and vice versa for when i change the backend)..Is there a way to check where the changes have been made(FrontEndCarProject/BackendCarProject) using GitLab and redirect the .gitlab-ci.yml to a script file depending on if a have to deploy to S3 or elastic beanstalk?

Just trying

Note: another way is just to manually change the yml file depending on where i want to deploy..but is there a way to autodetect this and automated?

Just to get the idea, heres an example that would run in a linear way, but how can i conditionally build/deploy(depending on my front or backend)? should i keep them in different repos for simplicity? is it a good practice?

I have a Spring Boot 2.x project that uses Gradle 7.x.

I'm assembling a distribution of the artifact/service in a zip / tar file using the built-in Spring Boot task(s) provided. There is no meta-data associated with this asset, nor any need to add anything else to it.

I would like to copy (or publish) this zip / tar file into Artifactory (using Gradle), but so far everything I see around that subject includes (1) the file itself (usually a jar), (2) module meta-data and (3) the POM file.

Is there a way to accomplish what I'm looking for?

I have a dockerfile that works by itself, with

docker build -t image_apache .
docker run -tid -p 5000:80 --name=container_apache image_apache

This works, and I can connect to its webserver with 127.0.0.1:5000

But when I try to create a docker-compose.yml file to build and run the image with docker-compose, it doesn't appear to expose the port at all.

Here is the docker-compose.yaml

I'm running gitlab-ce on-prem with min.io as a local S3 service. CI/CD caching is working, and basic connectivity with the S3-compatible minio is good. (Versions: gitlab-ce:13.9.2-ce.0, gitlab-runner:v13.9.0, and minio/minio:latest currently c253244b6fb0.)

Is there additional configuration to differentiate between job-artifacts and pipeline-artifacts and storing them in on-prem S3-compatible object storage?

In my test repo, the "build" stage builds a sparse R package. When I was using local in-gitlab job artifacts, it succeeds and moves on to the "test" and "deploy" stages, no problems. (And that works with S3-stored cache, though that configuration is solely within gitlab-runner.) Now that I've configured minio as a local S3-compatible object storage for artifacts, though, it fails.

I have sample tests used from scalatest.org site and maven configuration again as mentioned in reference documents on scalatest.org, but whenever I run mvn clean install it throws the compile time error for scala test(s).

Sharing the pom.xml below

I am new to Spark and am trying to run on a hadoop cluster a simple spark jar file built through maven in intellij. But I am getting classnotfoundexception in all the ways I tried to submit the application through spark-submit.

My pom.xml:

Im trying to deploy a java web app to heroku, I did all their steps from https://devcenter.heroku.com/articles/deploying-java-applications-with-the-heroku-maven-plugin, but when I try to open a page where I have data from db I am getting:

I am attempting to create a CI pipeline for a WCF project. I got the CI to successfully run but cannot determine where to look for the artifact. My intent is to have the CI pipeline publish this artifact in Azure and then have the CD pipeline run transformations on config files. Ultimately, we want to take that output and store it in blob storage (that will probably be another post since the WCF site is for an API).

I also realize that I really do not want to zip the artifact since I will need to transform it anyway.

Here are my questions:

1. Where is the container that the artifact 'drop' is published to?
2. How would I publish the site to the container without making it a single file.

Thanks

I was following this tutorial https://kubernetes.io/docs/tutorials/configuration/configure-java-microservice/configure-java-microservice-interactive/

After packaging the mvn projects, I'm asked to deploy them by using the following YAML file with the following command