Re: Jenkins Testing failed after migrating to 2.121 LTS

[Jan Monterrubio]

Does the maven build only fail in Jenkins?

On Fri, Sep 14, 2018 at 12:18 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/b7ce0fa4-273f-4680-a8e7-c10fd7ba08d7%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/CADgiF9K3ZjZQRkFxRTn68q6JynAyupKGV%2Bu5X0GC%2BnTtz%3DoN8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

I get "Handle is invalid" when trying to run psexec command via batch step build

[גלית קרנר]

When running the same psexec command from the slave itself it is working 
smoothly.
Same user and password for both- admin credentials!


Can anyone help?

Thanks!

-- 
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/cec42c25-d3ac-4040-87d2-f91d776a9ffc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: use Blue Ocean to create a maven java project on Windows platform (without using a docker agent)

[Jan Monterrubio]

Would something like this get you started:

pipeline {

agent any

stages {

stage('Build') {

steps {

bat 'mvn -v'

}

}

}

}




On Mon, Sep 10, 2018 at 14:37 Mario Jauvin  wrote:

> By "Google has not provided any insight" I meant that google search did
> not return any useful information.
>
> --
> 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/de8aa194-4d71-4057-bf58-e8acba9ba2eb%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/CADgiF9JiMzGM9JhRPPAkTPYn9zog-OGUX2jdL_t%3DzvzN2ia0Ow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Still Have Login Problem.

[Steve Burrus]

Baptiste I am sorry for the nature of my posts. I don't guess that you can
help me with my login  problem?



On Sun, Sep 16, 2018 at 6:04 AM Baptiste Mathus  wrote:

> Please keep using the previous thread. Afaict also Mark Waite answered you
> there last and you didn't reply.
>
> Also, please do not use all caps this way. It looks rude. People here are
> helping on their free time, please respect this.
>
> Thank you
>
>
> Le jeu. 13 sept. 2018 à 18:32, Steve Burrus  a
> écrit :
>
>> *This is Steve Burrus again and even though it's been several edays si
>> nce I last posted I STILL have that problem with getting that login page
>> when I go to "http://localhost:[port num.]", which is attached. Is there
>> any "fresh ideas" from anyone as to how to FINALLY resolve this problem?*
>>
>>
>>
>> --
>> 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/CABinwmWmEAG%3D%3DPrUBRLWdJHA81Sg%3DsP0r3cjQw7roegqkUQZAg%40mail.gmail.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/CANWgJS5hJ7KgAktxcLziSKbMf4TMSkKcYok4wXJ2nFrLzPw3%2BA%40mail.gmail.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/CABinwmWAbzSVZc%2BQvEVjcS8T2%3DNJU8_LG%2BBSw1%3DOjwy5OB0K7A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Log contains escape sequence characters

[Baptiste Mathus]

I think these escape sequences are just color ones. Hence I do not think
they are the 'culprits'.

By chance, could you show your pipeline or some gist of it exposing the
issue?

Le ven. 14 sept. 2018 à 14:26, David Aldrich 
a écrit :

> My declarative script job is failing.  I understand the reason for the
> failure but I'm getting an unhelpful message in the log:
>
>  [31mERROR: Errors occurred during the build. [0m
>
>
> How can I capture the real error message without these escape sequences?
>
> --
> 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/CAJK_ieixJMUBwaHaPgn91aAZzjd%3DXZwEk8j33tx8eyZRU6EDJQ%40mail.gmail.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/CANWgJS5mhVpq2AYHQeE6arNKX7sNH5Jn9TPSz250pXu_vbpxDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Still Have Login Problem.

[Baptiste Mathus]

Please keep using the previous thread. Afaict also Mark Waite answered you
there last and you didn't reply.

Also, please do not use all caps this way. It looks rude. People here are
helping on their free time, please respect this.

Thank you


Le jeu. 13 sept. 2018 à 18:32, Steve Burrus  a écrit :

> *This is Steve Burrus again and even though it's been several edays si nce
> I last posted I STILL have that problem with getting that login page when I
> go to "http://localhost:[port num.]", which is attached. Is there any
> "fresh ideas" from anyone as to how to FINALLY resolve this problem?*
>
>
>
> --
> 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/CABinwmWmEAG%3D%3DPrUBRLWdJHA81Sg%3DsP0r3cjQw7roegqkUQZAg%40mail.gmail.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/CANWgJS5hJ7KgAktxcLziSKbMf4TMSkKcYok4wXJ2nFrLzPw3%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Slave / master terms

[Baptiste Mathus]

Yes, +1. We all have been committed to do that to change and it was done in
early Jenkins 2.x a few years ago.

Normally the core UI has fully been fixed. Most classes could unfortunately
not be renamed for binary compatibility reasons.
So about the JEP, good question. Because it's been fixed already, I'm
leaning towards saying JEPing might not be strictly necessary. (?)

There could be a few leftovers here and there, mainly in some less
maintained plugins, so don't hesitate to file JIRAs and possibly PRs if you
find some of these. We're happy to fix together the last remainders of this.

Cheers

-- Baptiste

Le ven. 14 sept. 2018 à 14:29, matthew.web...@diamond.ac.uk <
matthew.web...@diamond.ac.uk> a écrit :

> > Master/slave concept has been on Jenkins since the start, despite the
> cultural reinforcement of slavery-related terms.
> > Maybe a JEP could follow the trend to more harmonious terms:
>
> In Jenkins 2, slaves (also sometimes known as nodes), were renamed to
> agents.
>
>
>
> --
> This e-mail and any attachments may contain confidential, copyright and or
> privileged material, and are for the use of the intended addressee only. If
> you are not the intended addressee or an authorised recipient of the
> addressee please notify us of receipt by returning the e-mail and do not
> use, copy, retain, distribute or disclose the information in or attached to
> the e-mail.
> Any opinions expressed within this e-mail are those of the individual and
> not necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any
> attachments are free from viruses and we cannot accept liability for any
> damage which you may sustain as a result of software viruses which may be
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England
> and Wales with its registered office at Diamond House, Harwell Science and
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
> --
> 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/12021635ce4d46998d66b74c0735ad3e%40Diamond.ac.uk
> .
> 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/CANWgJS6H%3DmYr4Ue9ZEh6-v37ow2FSXQwBp_kKa76pvZTvrZDug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Managed scripts are missing after upgrade to 2.131.3

[Baptiste Mathus]

Probably unrelated to Jenkins core I guess.
Didn't you also update the configfiles plugin? To 3.0 or so? I think I saw
reports of issues for this


Le jeu. 13 sept. 2018 à 18:28, Steve K  a
écrit :

> Just upgraded from 2.89.2 to 2.131.3
>
> I copied over the org.jenkinsci.plugins.configfiles.GlobalConfigFiles.xml
> and reloaded the configuration from disk, but that didn't help.
>
> Any clues?
>
> --
> 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/f85aefa8-86db-4a2e-b25d-da9b0e71cdd3%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/CANWgJS7Tsw6CBZ2TQU7P-Ky4nU3y5rpWayL5nehrU7TRsDS2Ug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Chroot: base image as matrix axis

[Baptiste Mathus]

You lost at the second sentence. Why are you trying to chroot?

Having agents of these different Linux flavors, or using docker images
(seems easier if you don't need to actually test a specific kernel or so).

Cheers

Le jeu. 13 sept. 2018 à 14:51, Simon Richter  a
écrit :

> Hi,
>
> I'd like to build a project against different Linux distributions.
>
> Using the chroot plugin, I can easily set up a chroot for each, but I
> need to specify the name of the base image in the project config.
>
> Can I somehow select the chroot base image by a label, so a matrix build
> with "debian-stretch", "debian-buster", "debian-sid", "ubuntu-xenial",
> ... would use the image configured with the appropriate label?
>
>Simon
>
> --
> 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/d64d1cab-3025-1742-1fb9-07751bf4638f%40hogyros.de
> .
> 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/CANWgJS5VvSSvEF-BTT8FB1yx6LEUynBJwEfSKZ1af9Zfj%2B8D4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoClassDefFoundError: Could not initialize class sun.util.calendar.ZoneInfoFile

[Baptiste Mathus]

Versions? Jenkins, Java VM, plugins. Are you using latest of everything?

Thanks

Le jeu. 13 sept. 2018 à 14:33, Víctor Puertas 
a écrit :

> Console Output shows the following issue
>
> java.lang.NoClassDefFoundError: Could not initialize class
>> sun.util.calendar.ZoneInfoFile
>>
>
> This is are the traces
>
> Required context class hudson.FilePath is missing
> Perhaps you forgot to surround the code with a step that provides this, such 
> as: node[Pipeline] }[Pipeline] // stage[Pipeline] End of PipelineAlso:   
> hudson.remoting.Channel$CallSiteStackTrace: Remote call to fatcat 
> (192.168.1.4)
>   at 
> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)
>   at 
> hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)
>   at hudson.remoting.Channel.call(Channel.java:955)
>   at hudson.FilePath.act(FilePath.java:998)
>   at hudson.FilePath.act(FilePath.java:987)
>   at hudson.FilePath.mkdirs(FilePath.java:1175)
>   at hudson.plugins.git.GitSCM.createClient(GitSCM.java:784)
>   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1154)
>   at 
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113)
>   at 
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
>   at 
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
>   at 
> org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
>   at hudson.security.ACL.impersonate(ACL.java:290)
>   at 
> org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> java.lang.NoClassDefFoundError: Could not initialize class 
> sun.util.calendar.ZoneInfoFile
>   at sun.util.calendar.ZoneInfo.getTimeZone(ZoneInfo.java:589)
>   at java.util.TimeZone.getTimeZone(TimeZone.java:560)
>   at java.util.TimeZone.setDefaultZone(TimeZone.java:666)
>   at java.util.TimeZone.getDefaultRef(TimeZone.java:636)
>   at java.util.TimeZone.getDefault(TimeZone.java:625)
>   at java.util.Calendar.getInstance(Calendar.java:1640)
>   at 
> java.util.Formatter$FormatSpecifier.printDateTime(Formatter.java:2826)
>   at java.util.Formatter$FormatSpecifier.print(Formatter.java:2740)
>   at java.util.Formatter.format(Formatter.java:2526)
>   at java.util.Formatter.format(Formatter.java:2455)
>   at java.lang.String.format(String.java:2940)
>   at java.util.logging.SimpleFormatter.format(SimpleFormatter.java:161)
>   at java.util.logging.StreamHandler.publish(StreamHandler.java:211)
>   at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:116)
>   at java.util.logging.Logger.log(Logger.java:738)
>   at java.util.logging.Logger.doLog(Logger.java:765)
>   at java.util.logging.Logger.log(Logger.java:876)
>   at hudson.remoting.UserRequest.perform(UserRequest.java:217)
>   at hudson.remoting.UserRequest.perform(UserRequest.java:54)
>   at hudson.remoting.Request$2.run(Request.java:369)
>   at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> Caused: java.io.IOException: Remote call on fatcat (192.168.1.4) failed
>   at hudson.remoting.Channel.call(Channel.java:961)
>   at hudson.FilePath.act(FilePath.java:998)
> Caused: java.io.IOException: remote file operation failed: 
> /home/jenkins/workspace/fatcat at hudson.remoting.Channel@28db12e1:fatcat 
> (192.168.1.4)
>   at hudson.FilePath.act(FilePath.java:1005)
>   at hudson.FilePath.act(FilePath.java:987)
>   at hudson.FilePath.mkdirs(FilePath.java:1175)
>   at hudson.plugins.git.GitSCM.createClient(GitSCM.java:784)
>   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1154)
>   at 
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113)
>   at 
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
>   at 
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
>   at 
>