The Jenkins-Version field embedded in the plugin manifest file is the
minimum Jenkins version supported, not the maximum. Jenkins works very
hard to allow older plugins to continue operating in newer releases.
Mark Waite
On Thu, Sep 20, 2018 at 9:09 PM Narahari 'n' Savitha
wrote:
> Thank you f
Thank you folks in advance for your time and attention
Here is the scenario.
I have Jenkins LTS 2.122 version and I have plugins for that installed.
Now the Jenkins 2.138 is released and I want to upgrade.
How do I check the version for the plugin that works for 2.138 or below ?
Apart from dow
Thank you folks in advance for your time and help.
Need some input please.
I used Dockerfile to pull lts-alpine
I then installed requisites for ansible and installed ansible.
I ran container and mapped a volume so the jenkins home is shared with host.
It all works.
Now I can put jobs there from j
I think I there were two things wrong.
1) Out of frustration, I went ahead and installed the github pull request
builder plugin. I was then seeing messages in the jenkins log that
it was checking the PR but nothing got built.
2)After uninstalling the github pull request builder plugin, I figure
Hello there - I've a frustrating issue when "npm install" is executed
inside a Jenkins Groovy pipeline using the NodeJS plugin, the process hangs
with the following error -
npm install --ddd ng-cli
npm info it worked if it ends with ok
npm verb cli [
'/var/jenkins_home/tools/jenkins.plugins.nod
I'm trying to publish an Artifact from Jenkins to Sonatype Nexus Repository
Manager OSS 3.12.0-01 using the Nexus Artifact Uploader plugin. But, the
upload fails. Below are the details I have given in the plugin in Jenkins:
KeyValue
Nexus Version Nexus3
Protocal HTTP
Nexus URL $NEXUS-URL
C
The beta release of the warnings plug-in has also support for CPPcheck now. You
can try if your file works here.
https://jenkins.io/blog/2018/09/11/speaker-blog-warnings-plugin/
> Am 20.09.2018 um 14:29 schrieb Fabian Cenedese :
>
> Hi
>
> I have a job that among other things uses cppcheck to
Still failing validation error in jenkins LTS 2.121..but no issue with 1.644
Java.lang.AssertionError: file abcd.xml validation rule not trigger, validation
error found:[] expected [[abcd.xml]] but found [[]]
org.testing.Assert.fail(Aasert.java94))
org.testing.Assert.failNotEquals(Asser. Java:49
On Friday, September 14, 2018 at 10:49:06 PM UTC+5:30, Pranav Kv wrote:
> Hi I am getting error in a maven build.
> There is test fail after migrating jenkins to new server.. But no issues in
> the old jenkins instance
>
> Error
> Validation not trigger.. Expected(abcd.xml) but found()
> Java as
I have few problems locating scm related variables:
In scripted pipeline I used this:
scmVars = checkout scm
echo "scmVars: ${scmVars}"
echo "tagName: ${env.TAG_NAME}"
echo "branchName: ${env.BRANCH_NAME}"
echo "changeTarget: ${env.CHAN
Hi
I have a job that among other things uses cppcheck to examine the code.
This has worked on several systems (Ubuntu, Debian, Windows). However
I have a problem using the same job on the last Ubuntu 18.04. Here's a
snippet from a working build:
(Ubuntu 16.04, CppCheck 1.72)
[Cppcheck] Starting t
2.121 is a later version than 2.7
Not quite sure what you need more than that?
Regards, Andreas
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-user
12 matches
Mail list logo
