pre-plugin | Documentation can be found at preprocess

by preprocess PHP Version: 0.13.0 License: MIT

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

kandi X-RAY | pre-plugin Summary

pre-plugin is a PHP library. pre-plugin has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Documentation can be found at preprocess.io.

Support

Quality

Security

License

Reuse

Support

pre-plugin has a low active ecosystem.

It has 93 star(s) with 8 fork(s). There are 3 watchers for this library.

It had no major release in the last 12 months.

There are 2 open issues and 5 have been closed. On average issues are closed in 85 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of pre-plugin is 0.13.0

Quality

pre-plugin has 0 bugs and 0 code smells.

Security

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

pre-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

pre-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

pre-plugin releases are available to install and integrate.

pre-plugin saves you 207 person hours of effort in developing the same functionality from scratch.

It has 507 lines of code, 48 functions and 10 files.

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

Top functions reviewed by kandi - BETA

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

Listen to pre - autoload event .
Format a PHP code .
Determine if the command should be optimized .
Get the install path .
Compile a file .
Add compilers .
Get all available macros .
Get the list of registered compilers .
Activate plugin .
Get the subscribed events .

Get all kandi verified functions for this library.

pre-plugin Key Features

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

pre-plugin Examples and Code Snippets

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

Community Discussions

Trending Discussions on pre-plugin

Jenkins jobs now fail after upgrading Jenkins kubernetes plugin from 1.14.2 --> 1.26.0. Plugin update changes build dir path- re-clarifying question

QUESTION

Jenkins jobs now fail after upgrading Jenkins kubernetes plugin from 1.14.2 --> 1.26.0. Plugin update changes build dir path- re-clarifying question

Asked 2020-Jun-12 at 13:51

Jenkins version is 2.222.4. We upgraded the jenkins kubernetes plugin from 1.14.2 --> 1.26.0. What this has done is pre-pluginupgrade, the jenkins slave would mount /home/jenkins as rw so it could use .gradle files in there for its build.

Post plugin upgrade, home/jenkins is now change to readonly, and instead the dir called /home/jenkins/agent has become the read/write. However the build job now has no more r/w access to files in home/jenkins which it needs.

I did a df -h on our slave jnlp pod pre upgrade (k8splugin-V1.14.2) and see the following:

Filesystem Size Used Available Use% Mounted on overlay 119.9G 5.6G 109.1G 5% / /dev/nvme0n1p2 119.9G 5.6G 109.1G 5% /home/jenkins

and can see its mounted as read/write

cat /proc/mounts | grep -i jenkins /dev/nvme0n1p2 /home/jenkins ext4 rw,relatime,data=ordered 0 0

Post plugin upgrade if I run a df -h I don't even see /home/jenkins mounted only: /dev/nvme0n1p2 120G 5.6G 110G 5% /etc/hosts

and if I cat /proc/mounts I only see this post upgrade

jenkins@buildpod:~$ cat /proc/mounts | grep -i jenkins /dev/nvme0n1p2 /home/jenkins/agent ext4 rw,relatime,data=ordered 0 0 /dev/nvme0n1p2 /home/jenkins/.jenkins ext4 rw,relatime,data=ordered 0 0

Also seeing this in the jenkins job log but not sure if it is relevant: WARNING] HOME is set to / in the jnlp container. You may encounter troubles when using tools or ssh client. This usually happens if the uid doesnt have any entry in /etc/passwd. Please add a user to your Dockerfile or set the HOME environment variable to a valid directory in the pod template definition.

Any ideas or workarounds would be most welcome as badly stuck by this issue. Brian

...

ANSWER

Answered 2020-Jun-12 at 13:51

My colleague just figured this out. He found it goes back to a change the plugin developers made sometime in August 2019, to be compatible with Kubernetes 1.18. That's when they changed the default workspace in release 1.18.0 of the plugin. It was spotted and supposed to be fixed here github.com/jenkinsci/kubernetes-plugin/pull/713 but it persists in our case. Workaround is to hardcode into the jenkinsfile of each job workingDir: '/home/jenkins' under the container

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

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

Vulnerabilities

No vulnerabilities reported

Install pre-plugin

You can download it from GitHub.
PHP requires the Visual C runtime (CRT). The Microsoft Visual C++ Redistributable for Visual Studio 2019 is suitable for all these PHP versions, see visualstudio.microsoft.com. You MUST download the x86 CRT for PHP x86 builds and the x64 CRT for PHP x64 builds. The CRT installer supports the /quiet and /norestart command-line switches, so you can also script it.

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: