Re: How to check plugin version for a specific jenkins version

[Mark Waite]

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 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 downloading plugin, unwrapping it and look at the Jenkins
> version field, is there any other way ?
>
> This is doable but it is very laborious and I have to go from what ver of
> plugin I have and go up one level check and keep going up the version list.
>
> I am trying to pick minds of smart people here please.
>
> -N
>
> --
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/3507d3d8-4478-4024-952d-4c49f7b587f8%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEXU3GiUM-i8yDB15H09G%3D_dQij862eXMjYA7XWjFsG3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

How to check plugin version for a specific jenkins version

[Narahari 'n' Savitha]

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 downloading plugin, unwrapping it and look at the Jenkins 
version field, is there any other way ?

This is doable but it is very laborious and I have to go from what ver of 
plugin I have and go up one level check and keep going up the version list.

I am trying to pick minds of smart people here please.

-N

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3507d3d8-4478-4024-952d-4c49f7b587f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to dockerize jenkins in the right way ?

[Narahari 'n' Savitha]

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 jenkins where we backup the config.xml.

Now for some best practice questions help please

I plan to setup Jenkins the way I want to (docker exec update plugins, jobs 
from git etc.,)
Re start container but mount host to a /tmp/jenkins folder inside container.
cp -Rf /tmp/jenkins /var/jenkins_home
Stop container and docker commit the image.

Start container with new image.  This way the image is completely self 
contained.
What do you folks think ?  Is this a good idea ?
I plan to update the cmd in the Dockerfile to use git to update jobs from 
git at startup or I can keep the latest job in the docker image.
I am in confusion.  Kindly advise.

-Narahari

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7a8fe5a7-90b3-481e-84c9-fb6a3897966e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: PRs not building

[Tom Duerr]

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 figured out 
that the endpoint for the branch-source-plugin PR builder hook was 
incorrect. The
correct endpoint was http/github-webhook.

Bottom line, you don't need the github pull request builder plugin if you 
are using github branch source plugin, it just needs to be properly 
configured.

Thanks Jan for the response.

Tom









On Wednesday, September 19, 2018 at 5:26:01 AM UTC-7, Jan Monterrubio wrote:
>
> Do you have the web hooks and services configured on the repository to 
> receive push notifications from Jenkins / vice versa. 
>
> On Wed, Sep 19, 2018 at 00:19 Tom Duerr > 
> wrote:
>
>> Hi, 
>> Im using:
>>
>> jenkins: 2.139
>> Github-Branch-Source 2.3.4
>> BlueOcean
>> GitHub Enterprise
>>
>> This is our first attempt at pipelines and I'm a bit confused.
>>
>> I did a "Scan Organization Now" and it detected the repo with the 
>> JenkinsFile.
>> I can create a PR and do a "Scan Repository Now" and it will detect the 
>> PR and
>> build. However, If I don't do a "Scan Repository Now" then nothing ever 
>> happens.
>> I never see anything in "Respository Events" and the PR never gets 
>> built.  
>> Its unclear if I need to install the github pull request builder.
>>
>> Thanks,
>> Tom
>>
>> -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/eb424294-ec96-475d-8b29-b3c06a956f13%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/627e9e37-148c-4efc-b470-200067af2226%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Dockerised Jenkins Hangs NPM Install

[sweeny_here]

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.nodejs.tools.NodeJSInstallation/nodejs893-v2/bin/node',
npm verb cli  
 
'/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs893-v2/bin/npm',
npm verb cli   'install',
npm verb cli   '--ddd',
npm verb cli   'ng-cli' ]
npm info using npm@5.5.1
npm info using node@v8.9.3
npm verb npm-session e522ad0a36f1c038
npm sill install loadCurrentTree
npm sill install readLocalPackageData
npm http fetch GET 503 https://registry.npmjs.org/ng-cli 70252ms attempt #3
npm sill fetchPackageMetaData error for ng-cli@latest 503 Service 
Unavailable: ng-cli@latest
npm verb stack Error: 503 Service Unavailable: ng-cli@latest

When the command is executed directly on the EC2, the package installs 
without issue as the Jenkins user.

Also when the npm install is executed inside the Jenkins Docker, the 
package installs without issue as the Jenkins user using the same Node 
installation.

The Docker instance is not limited by CPU or RAM.

The setup is Jenkins v2.138.1 running inside a Docker container, which in 
turn is hosted on an EC2 v2018.03. Jenkins home is mounted as an EFS 
volume. The JVM is running on Java v1.8.0_181. NPM is v5.1.1.

Any pointers would be much appreciated.

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/96a2775b-e88c-42ab-9734-39fac65666b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Issue pushing Artifact to Nexus from Jenkins using Nexus Artifact Uploader

[gotviseryon]

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
Credentials Cre
GroupId group-01
Version 0.0.1
Repository testrepo
ArtifactId abcd-0.3
Type tgz
Classifier  
File abcd-0.3.tgz

 

 

When I try to build, I get the following output

Uploading: $REPOSITORY_URL/group-01/abcd-0.3/0.0.1/abcd-0.3-0.0.1.tgz
10 % completed (193 kB / 1.9 MB).
20 % completed (385 kB / 1.9 MB).
30 % completed (578 kB / 1.9 MB).
40 % completed (770 kB / 1.9 MB).
50 % completed (958 kB / 1.9 MB).
Failed to deploy artifacts: Could not transfer artifact 
group-01:abcd-0.3:tgz:0.0.1 from/to testrepo ($REPOSITORY_URL): Broken pipe 
(Write failed)
ERROR: Uploading file abcd-0.3.tgz failed.
[Office365connector] No webhooks to notify
Finished: FAILURE

The *repository type* of the testrepo is *hosted* and the *repository 
format* is *npm*.  But, with the same configuration, I'm able to push the 
file to another repository for which the *repository type* is *hosted* and 
the *repository format* is *raw*.  Also, I'm manually able to upload this 
file through Nexus UI into the *npm*repository (for which the Jenkins job 
is unable to push artifact).

 

Please suggest.

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3415644e-ec2c-43c4-932a-73ecc4a81e3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: CppCheck plugin fails on Ubuntu 18.04

[Ullrich Hafner]

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 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 the cppcheck analysis.
> [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
> [Cppcheck] Not changing build status, since no threshold has been exceeded.
> [Cppcheck] Ending the cppcheck analysis.
> 
> And this is what happens on Ubuntu 18.04
> 
> (Ubuntu 18.04, CppCheck 1.82)
> [Cppcheck] Starting the cppcheck analysis.
> [Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
> [Cppcheck] Error on cppcheck analysis: java.io.IOException: remote file 
> operation failed: 
> /var/lib/jenkins/workspace/inos_unittest_desktop/INOSTYPE/600205020 
> Linux/OPT/Debug/OS/linux/label/inos_desktop at 
> hudson.remoting.Channel@282557ba:Ub18-04-64: java.io.IOException: Remote call 
> on Ub18-04-64 failed
> Build step 'Publish Cppcheck results' changed build result to FAILURE
> Build step 'Publish Cppcheck results' marked build as failure
> 
> The cppcheck logfile looks the same, xml with version 2. So what else
> could be the reason for this exception? Is there a log file on the slave
> that has more information? Or can I tell the slave to output more information
> to the master?
> 
> Thanks
> 
> bye  Fabi
> 
> --
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/20180920122925.855C736B177E%40macserver.private.
> For more options, visit https://groups.google.com/d/optout.

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0AD00919-3BF6-40E1-97CE-E5E1C37A92C7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

Re: Jenkins Testing failed after migrating to 2.121 LTS

[Pranav Kv]

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:494)
org.testing.Assert.assertEqual(Assert.java:808)

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8a6efbb7-2868-4885-b4c7-ef9294ea4dde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Testing failed after migrating to 2.121 LTS

[Pranav Kv]

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 assertion
> 
> COULD any please help me to resolve? 
> Regards
> Pranav

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f4ef7569-60c3-4aa5-a496-cd2fc8c2b6ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Declarative Pipeline - how to get scm variables

[nirav]

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.CHANGE_TARGET}"

Since in declarative one I dont need to checkout, how do I get hang of 
variables?

env.TAG_NAME, env.BRANCH_NAME all coming up null.

is see 'branch' is used in conditional 'when' expression 
 when {
branch 'master'
}
but how many such variables are available ?

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/210db091-d249-4483-a263-96bcf5a14df1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

CppCheck plugin fails on Ubuntu 18.04

[Fabian Cenedese]

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 the cppcheck analysis.
[Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
[Cppcheck] Not changing build status, since no threshold has been exceeded.
[Cppcheck] Ending the cppcheck analysis.

And this is what happens on Ubuntu 18.04

(Ubuntu 18.04, CppCheck 1.82)
[Cppcheck] Starting the cppcheck analysis.
[Cppcheck] Processing 1 files with the pattern 'cppcheck.xml'.
[Cppcheck] Error on cppcheck analysis: java.io.IOException: remote file 
operation failed: 
/var/lib/jenkins/workspace/inos_unittest_desktop/INOSTYPE/600205020 
Linux/OPT/Debug/OS/linux/label/inos_desktop at 
hudson.remoting.Channel@282557ba:Ub18-04-64: java.io.IOException: Remote call 
on Ub18-04-64 failed
Build step 'Publish Cppcheck results' changed build result to FAILURE
Build step 'Publish Cppcheck results' marked build as failure

The cppcheck logfile looks the same, xml with version 2. So what else
could be the reason for this exception? Is there a log file on the slave
that has more information? Or can I tell the slave to output more information
to the master?

Thanks

bye  Fabi

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20180920122925.855C736B177E%40macserver.private.
For more options, visit https://groups.google.com/d/optout.

Re: Blue ocean plugin supported version

[Andreas Magnusson]

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/99bd807a-1831-4061-9541-9c734cfa6413%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.