jenkins | Development repository for the jenkins | Infrastructure Automation library

This functionality is only available on scripted pipeline at the moment, and is described in the documentation.

For example:

You need to replace \ with \\ if you are giving path with jenkins in Windows.
May be if file path is too huge or that is the root cause you can try mounting the directory to a short path

EDIT : Based on your modified question :
Open Jenkins dashboard. Navigate to Manage Jenkins-> Configure System. Under the Global properties section add another environment variable named GRADLE_USER_HOME as shown below.

I don't think you can directly run run-command accross account. But you could run in through AWS Systems Manager Automation. In your automation document you can use aws:runCommand.

This is possible because SSM Automation supports cross-account and cross-region deployments.

Based on the storage class spec, I think the problem is the volumeBindingMode being set as WaitForFirstConsumer which means the PV will remain unbound until there is a Pod to consume it.

You can change it Immediate to allow the PV to be bound immediately without requiring to create a Pod.

You can read about the different volume binding modes in detail in the docs.

I would start with running sp_who2 on the database server to see if sqlpackage has made a connection to it, and if it's blocking on the server somewhere.

If so, you can further investigate with the SQL Server Profiler (can be found in the Tools menu of SQL Server Management Studio)

Kubernetes is a container orchestrator that may use Docker as its container runtime. So, they are quite different things—essentially, different levels of abstraction.

You could theoretically run an application at both of these abstraction levels. Here's a comparison:

Docker

You can run an application as a Docker container on any machine that has Docker installed (i.e. any OS or cloud provider instance that supports Docker). However, you would need to implement any operations-related features that are relevant for production, such as health checks, replication, load balancing, etc. yourself.

Kubernetes

Running an application on Kubernetes requires a Kubernetes cluster. You can run a Kubernetes cluster either on-premises, in the cloud, or use a managed Kubernetes service (such as Amazon EKS, Google GKE, or Azure AKS). The big advantage of Kubernetes is that it provides all the production-relevant features mentioned above (health checks, replication, load balancing, etc.) as part of the platform. So, you don't need to implement them yourself but just use the primitives that Kubernetes provides to you.

Regarding your two requirements, Kubernetes provides both of them, while using Docker alone does not provide easy production-readiness (requirement 2). So, if you're opting for production stability, setting up a Kubernetes cluster is certainly worth the effort.

Go in the jenkins.xml file and change that port, for more info see, dpends on how do you launch jenkins:

• How to change port for jenkins window service when 8080 is being used
• How to start jenkins on different port rather than 8080 using command prompt in Windows?
• Change Jenkins port on macOS

This is a map that contains maps. [:] is the literal syntax for an empty map. Otherwise the map would be null and you couldn’t add anything to it. The map gets populated with 2 more maps. The argument you pass in decides which of the 2 maps is returned, if the argument doesn’t match either content1 or content2 the function returns null.

If you have groovy installed on your computer you can try your posted code out in groovyConsole and see what it does.

This is how Start-Process command was basically created. -PassThru switch redirects the output to an object ($sqlpackagepublish in this case). More on Start-Process here: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/start-process?view=powershell-5.1

There are few solutions.

1. Remove a -PassThru parameter and read files' content as you are doing it right now
2. Do it harder, but more robust .NET'y way: