docker-workflow-plugin | Jenkins plugin which allows building | Continuous Deployment library

by jenkinsci Java Version: 563.vd5d2e5c4007f License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | docker-workflow-plugin Summary

docker-workflow-plugin is a Java library typically used in Devops, Continuous Deployment, Jenkin, Docker applications. docker-workflow-plugin has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

Jenkins plugin which allows building, testing, and using Docker images from Jenkins Pipeline projects.

Support

Quality

Security

License

Reuse

Support

docker-workflow-plugin has a low active ecosystem.

It has 485 star(s) with 403 fork(s). There are 131 watchers for this library.

It had no major release in the last 12 months.

docker-workflow-plugin has no issues reported. There are 42 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of docker-workflow-plugin is 563.vd5d2e5c4007f

Quality

docker-workflow-plugin has 0 bugs and 0 code smells.

Security

docker-workflow-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

docker-workflow-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

docker-workflow-plugin is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

docker-workflow-plugin releases are available to install and integrate.

Build file is available. You can build the component from source.

docker-workflow-plugin saves you 2024 person hours of effort in developing the same functionality from scratch.

It has 4442 lines of code, 335 functions and 71 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed docker-workflow-plugin and discovered the below as its top functions. This is intended to give you an instant insight into docker-workflow-plugin implemented functionality, and help decide if they suit your requirements.

Get a script for an annotated agent
Returns the label of the current build
Returns the current run if it exists otherwise null
Returns the container id of the container
Get container id
Parse docker file arguments
Parse dockerfile argument
Tries to get the container ID
Launches the launcher
Retrieves the container record for a container
Get the date created for the given object id
Gets dockerfile path
Returns a list of mounted volumes of a container
Parse build - - - - args command line arguments
Get the Docker value of a script
Queries and returns the information about the current user
Run a docker image
Lists the top nodes in the container
Lists the current process
Adds an image to a container

Get all kandi verified functions for this library.

docker-workflow-plugin Key Features

No Key Features are available at this moment for docker-workflow-plugin.

docker-workflow-plugin Examples and Code Snippets

No Code Snippets are available at this moment for docker-workflow-plugin.

Community Discussions

Trending Discussions on docker-workflow-plugin

On Debian 11 (Bullseye) /proc/self/cgroup inside a docker container does not show docker infos

Jenkins pipeline DSL with docker-workflow-plugin .inside doesn't allow setting/modification of PATH via withEnv

QUESTION

On Debian 11 (Bullseye) /proc/self/cgroup inside a docker container does not show docker infos

Asked 2021-Aug-31 at 22:01

I recently updated from Debian 10 (Buster) to 11 (Bullseye) and since then my Jenkins setup inside Docker is not working anymore, as Jenkins tries to find out if it is running in a docker container by checking /proc/self/cgroup.

Normally /proc/self/cgroup inside a docker container would look something like this:

...

ANSWER

Answered 2021-Aug-31 at 22:01

The change in behavior is due to that debian uses cgroups v2 starting with Debian 11/Bullseye. The docker engine itself supports cgroups v2 since v20.10.x.

This means, as soon as you have a distribution that uses cgroups v2 and a recent version of the Docker engine, you cannot get the container id with your method.

I've opened a similar question to find an alternative method: How to get docker container ID from within the container with cgroup v2

The only way I know to get the id is by using the docker api, but that is not an elegant solution if you just want to know if the process runs inside a container. (And may pose a security risk if you expose the docker socket inside the container)

For now as a workaround you could manually signal the process that it is run inside a container environment, e.g. by specifying an environment variable on container creation.

Source https://stackoverflow.com/questions/69002675

QUESTION

Jenkins pipeline DSL with docker-workflow-plugin .inside doesn't allow setting/modification of PATH via withEnv

Asked 2021-Apr-28 at 14:27

Problem

I want to modify the path in a docker container to control tool selection without the need to modify existing pipeline code. I've a shared library and client builds call runAnsible which then runs pipeline DSL within a docker container via the docker-workflow-plugin.

However, when I use withEnv docker.inside, I cannot modify path

...

ANSWER

Answered 2021-Apr-28 at 14:27

Docker workflow plugin allows args to be passed to the docker run command which creates the container. These args are just a string and its integrity appears respected by the pluign whereas withEnv has some kind of filter in this context.

Therefore, this works but it does assume that I know or can determine the original path. I could run the container without path modification and use a sh(script: 'echo $PATH', returnStdout: true).trim() via docker.inside to get the knownOriginalPath in an earlier step to fee the code below

Source https://stackoverflow.com/questions/67302108

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install docker-workflow-plugin

You can download it from GitHub.
You can use docker-workflow-plugin like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the docker-workflow-plugin component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: