ci | dlang CI testing pipelines | Continous Integration library

I found an answer for regplots, but I can't get the same code to work for relplots. I want to change the transparency of the confidence intervals while keeping the lines of my graph darker, but the alpha input for relplots makes the entire graph more translucent.

My code:

This question is related to Azure MSIX Build and Package task only has Release and Debug configurations

We have a WinForms project that has an MSIX installer. Manually, we can successfully create

1. An MSIXBUNDLE and deploy it to Kudu
2. An MSIX and deploy it to an Azure VM through a VHDX. We have manually convert the MSIX to a VHDX first

We are now trying to automate the build and release process to create the VHDX. However, we are getting a blank screen when the VHDX is mounted using a process that we have already validated. The only thing different is the build method (i.e., MSBuild versus VS Publish).

How do we create a working VHDX in Azure CI Build Pipeline?

Below is the YAML.

We are experimenting with Jetbrains Space as our code repo and CI/CD. We are trying to find a way to setup the .space.kts file to deploy to AWS Lambda.

We want the develop branch to publish to the Lambda $Latest and when we merge to the main branch from the develop branch we want it to publish a new Lambda version and link that version to the alias pro.

I've looked around but haven't found anything that would suggest there is a pre-built solution for controlling AWS Lambda so my current thinking is something like this:

I am working on a CI config to push to multiple projects in remote server.

So I temporary push them on github public project, which have a config.cfg file contains these line below.

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'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'm using gitlab runner on a mac mini server. While using user named "runner" I manage to use this command:

I have a container with IBM MQ (Docker image ibmcom/mq/9.2.2.0-r1) exposing two ports (9443 - admin, 1414 - application).

All required setup in OpenShift is done (Pod, Service, Routes).

There are two routes, one for each port.

• https://route-admin.my.domain
• https://route-app.my.domain

pointing to the ports accordingly (external ports are default http=80, https=443).

Admin console is accessible through the first route, hence, MQ is up and running.

I tried to connect as a client (JMS 2.0, com.ibm.mq.allclient:9.2.2.0) using standard approach:

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