Re: Ability to get the current logged in user's api token

2015-12-22 Thread Victor Martinez
Hi, Jobddsl does support the credential plugin indeed. https://github.com/jenkinsci/job-dsl-plugin/wiki/Handling-Credentials Cheers -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails fr

Jenkins Project Configuration: stderr: Host key verification failed

2015-12-22 Thread Rammacher Frank
Hello, i try to configurate a Jenking Project for a test, but it fails (for this moment...) on Sorce-Code.Management: My System: - Windows 8.1 - Jenkins 1.643 - FreeSSHD - git version 2.6.3.windows.1 Ok, what i have is a project named jenkins_test, it is located on: C:\Program Files (x86)\Jenki

Re: Ability to get the current logged in user's api token

2015-12-22 Thread Daniel Beck
> On 21.12.2015, at 23:49, Joe Ferr wrote: > > I'd use the Mask Password plugin to hide the exposed token from the console > output so I don't think there would be a way to steal others users API tokens. That plugin can only hide build parameters and previously defined strings. Do you want to

Re: Users' cannot log out

2015-12-22 Thread Daniel Beck
> On 22.12.2015, at 07:26, Raveesh wrote: > > Ah that makes sense. I didn't consider it just re-signing in. I was expecting > to see an account selection screen from google. I'm pretty sure the behavior I describe is what's happening, but monitor the requests sent by your browser to find out

[workflow-plugin] Warnings plugin not parsing console?

2015-12-22 Thread Craig Rodrigues
Hi, I installed: workflow-plugin 1.12 warnings plugin 4.51 jenkins 1.641 I used the workflow snipper generator to generate code to invoke the warnings plugin. I came up with the following example: node { writeFile(file: "a.c", text: ''' #include #include void func1(void) { }

Re: [workflow-plugin] Warnings plugin not parsing console?

2015-12-22 Thread Ullrich Hafner
Hmm, seems that the workflow plug-in does not handle the console in the same way as for standard jobs. I’m not sure if this is a bug in the workflow plug-in or in the workflow implementation of the warnings-plug-in. You can try to pipe the compiler output to a file and then parse the file. > Am

Looking for a Plugin to hook Build Deletion

2015-12-22 Thread John Mellor
Is there a Jenkins plugin that would allow me to hook the deletion of a build? I can't continue to add large artifacts to my repositories forever, and need to construct some automated mechanism to delete them throughout the enterprise when they are no longer useful. I want to add lifecycle to th

Re: [workflow-plugin] Warnings plugin not parsing console?

2015-12-22 Thread Craig Rodrigues
Hi, Piping to a file works, but I don't want to do that, because I want the output to appear in the normal Jenkins job console output screen. Your guess was right, in that the output doesn't seem to be fully available to the warnings plugin at the time that I called it. I seemed to have fixed th

Re: Looking for a Plugin to hook Build Deletion

2015-12-22 Thread Andrew Bayer
You can see an example of doing something like that at https://github.com/jenkinsci/associated-files-plugin/blob/master/src/main/groovy/org/jenkinsci/plugins/associatedfiles/AssociatedFilesRunListener.groovy . A. On Tue, Dec 22, 2015 at 1:11 PM, John Mellor wrote: > Is there a Jenkins plugin th

I'm in upgrade HELL (upgrading to 1.625.3). Need help.

2015-12-22 Thread Steve K
I keep getting the red devil from hell. I tried upgrading from 1.580.1 to 1.625.3 (LTS release). Now, every time I click on a job, I get the red devil. I tried a full install of 1.625.3 (vs an upgrade) and still I have the problem. Pardon the verbosity, but, in the past people have wanted to se

Re: Build date / time showing December 31, 1969 after upgrading from 1.596.2 LTS to 1.625.3

2015-12-22 Thread Steve K
Marc, Did you ever resolve your problem? I have a feeling that my current upgrade HELL (just posted a plea for help on that) is related to changes in format. If you haven't resolved it, sorry if I got your hopes up when you saw a reply :-( Regards, Steve K. -- You received this message be

Re: I'm in upgrade HELL (upgrading to 1.625.3). Need help.

2015-12-22 Thread Andrew Bayer
Looks like you might be missing the xunit plugin? On Tue, Dec 22, 2015 at 3:01 PM, Steve K wrote: > I keep getting the red devil from hell. > I tried upgrading from 1.580.1 to 1.625.3 (LTS release). Now, every time > I click on a job, I get the red devil. > I tried a full install of 1.625.3 (vs

Re: I'm in upgrade HELL (upgrading to 1.625.3). Need help.

2015-12-22 Thread Steve K
Andrew, thank you. the xunit plugin had been de-activated. That may have been a problem, but it is not THE problem causing the devil to appear. Here's the stack taken directly from an access that failed (vs from the jenkins.error.log): javax.servlet.ServletException: org.apache.commons.jelly.Je

Re: I'm in upgrade HELL (upgrading to 1.625.3). Need help.

2015-12-22 Thread Daniel Beck
You need to update the Disk Usage Plugin. Your old version isn't compatible to the new Jenkins. > On 22.12.2015, at 22:02, Steve K wrote: > > Andrew, thank you. the xunit plugin had been de-activated. That may have > been a problem, but it is not THE problem causing the devil to appear. > Her

Re: Build date / time showing December 31, 1969 after upgrading from 1.596.2 LTS to 1.625.3

2015-12-22 Thread Marc Esher
Hey Steve, I did not resolve this problem on 2 of the jenkinses. However, on a 3rd, I did a straight update from 1.596 to 1.625, and I did not experience this behavior, so I'm thinking that my original problem is not quite as described. It seems that the problem originated on the busted jenkin

[workflow-plugin] Example using NodeLabel Parameter plugin?

2015-12-22 Thread Craig Rodrigues
Hi, Can someone provide some workflow groovy which takes a "Node Parameter" from the NodeLabel Parameter plugin, and then uses it in a workflow script? I couldn't figure out how to do it, and kept getting null exceptions when I tried to use the parameter. -- Craig -- You received this message

Re: I'm in upgrade HELL (upgrading to 1.625.3). Need help.

2015-12-22 Thread Steve K
Daniel, you nailed it! Thank you very much! I have ascended from hell and am back to my normal Purgatory ;-) BTW. For future reference, what did you see that pointed you to the "Disk Usage" plugin as the culprit? Many thanks. Steve K. -- You received this message because you are subscribed

Re: I'm in upgrade HELL (upgrading to 1.625.3). Need help.

2015-12-22 Thread Daniel Beck
On 22.12.2015, at 22:58, Steve K wrote: > For future reference, what did you see that pointed you to the "Disk Usage" > plugin as the culprit? The most relevant lines of a Java stack trace are typically the last one starting with "Caused by" and the one (or few) below that. In this case: > C

[workflow-plugin] RFC: workflow script to Build/Boot/Test FreeBSD

2015-12-22 Thread Craig Rodrigues
Hi, I am making some serious efforts to convert my existing Jenkins jobs to use workflow. My first attempt is here: https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/build-test.groovy The script calls several helper scripts, but overall what it is trying to do is: 1. Builds t

Re: Workflow (pipeline) visual editor

2015-12-22 Thread Michael Neale
FYI this should be available soon in the experimental update center: http://jenkins-ci.org/content/experimental-plugins-update-center On Monday, December 21, 2015 at 6:18:43 PM UTC+11, Michael Neale wrote: > > (I posted this to jenkins-dev last week, but thought some users here may > be interest

Slave missing Jenkins Groovy api jars

2015-12-22 Thread Baz Lov
I have a windows slave I am trying to use the Jenkins Groovy api on from the Groovy plugin "Execute Groovy Script" job element. However when I run the script it keeps throwing class not found exceptions for classes that come from dependencies of the Jenkins Groovy api. The first one was jenkins

Jclouds openstack instance creation

2015-12-22 Thread anoop negi
Hi, I'm using Jclouds plugin to create openstack instance on the fly during job build and terminate as job get finished. but i'm facing problem in ssh authentication. Jclouds trying to login with ssh key pair with login user as "root" instead of "ubuntu"on ubuntu cloud image. where to configure i

Re: Build date / time showing December 31, 1969 after upgrading from 1.596.2 LTS to 1.625.3

2015-12-22 Thread Baptiste Mathus
Just a small hint, in case it can help get you forward: the date you have seems to match Epoch. So I suppose at some point, the computed timestamp for the build is 0 (or defaulted to). My 0.2 cents. 2015-12-22 22:32 GMT+01:00 Marc Esher : > Hey Steve, > > I did not resolve this problem on 2