How to connect Remote Desktop Connection with Jenkins Slave using localhost:8080

2016-12-12 Thread saurabh chanchawat
I am not able to connect Remote Desktop Connection with Jenkins Slave using localhost:8080 Can anyone help me how to connect remote desktop using Jenkins. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop

Build abort on shell action not working in pipeline

2016-12-12 Thread Arvind Jayaprakash
I guess this is not the first report on the build abort action not working in a pipeline (based on past mails I see this group). I write to demonstrate a full example where this doesn't work. Here is my pipeline in it's entiry node('mvn-3.3-jdk-8') { stage('stoopid grep') { sh 'grep aa -R

Re: Techniques for managing an scp call to a remote box, with a specific principal

2016-12-12 Thread Rachel Moreno
Hi David, Sorry, it's true, you mentioned it. Please, take a look at: https://issues.jenkins-ci.org/browse/JENKINS-27963 I hope be useful. Best regards, Raquel On Sunday, December 11, 2016 at 11:50:19 PM UTC+1, David Karr wrote: > > > > On Sunday, December 11, 2016 at 1:05:19 PM UTC-8, Rachel

Re: Techniques for managing an scp call to a remote box, with a specific principal

2016-12-12 Thread ncosta
> > Yes, I've seen those two plugins, but I don't understand how I would use > either of these from a pipeline job. As Rachel mentioned, Publish over ssh is still lacking pipeline support. You can check additional pipeline plugins compatibility here

OSX Jenkins UI password

2016-12-12 Thread Poule Dodue
where is initialAdminPassword on OSX to log in to UI on port 80? not in /Users/Shared/Jenkins/Home/secrets not in /Users/YOURUSERNAME/.jenkins/secrets/initialAdminPassword -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe fro

Re: Pipeline one-liner causes hanging job ?

2016-12-12 Thread ncosta
> > This caused my Pipeline Job to hang - so I have to kill it. > As mentioned in this issue, you can use as workaround assert false : 'oh no!' Not sure if the resolution was already released. -- You received this message because you ar

Re: Spawn multiple jobs

2016-12-12 Thread Bryce Pepper
"a b c,d, e , f" parameters are passing now but I am not getting the "parallel" execution desired. All of the spawned jobs have the same build number and if I look at completed job it has the passed parameter "f". def inputParameter = build.buildVariableResolver.resolve("inputParameter").spli

Re: Build abort on shell action not working in pipeline

2016-12-12 Thread Daniel Beck
> On 12.12.2016, at 12:55, Arvind Jayaprakash wrote: > > I guess this is not the first report on the build abort action not working in > a pipeline Are you on the newest versions of all Pipeline-related plugins? -- You received this message because you are subscribed to the Google Groups "J

Re: Spawn multiple jobs

2016-12-12 Thread Daniel Beck
> On 12.12.2016, at 16:47, Bryce Pepper wrote: > > "a b c,d, e , f" parameters are passing now but I am not getting the > "parallel" execution desired. All of the spawned jobs have the same build > number and if I look at completed job it has the passed parameter "f". I'm pretty sure you're

Re: Build abort on shell action not working in pipeline

2016-12-12 Thread Arvind Jayaprakash
Yes. I've attached the versions of all plugins as a reference On Monday, December 12, 2016 at 9:33:31 PM UTC+5:30, Daniel Beck wrote: > > > > On 12.12.2016, at 12:55, Arvind Jayaprakash > wrote: > > > > I guess this is not the first report on the build abort action not > working in a pipeline

Re: Pipeline: Hos to test them locally

2016-12-12 Thread Peter McNab
The (far from perfect) method we've been using is to use a "testing" pipeline job. Rather than fetching the project from source, it is an explicit script that uses a "load" to load in the "real" pipeline script from my development environment (which is available via NFS). sourcepath = ' node(

Re: Polling both svn and git from pipeline

2016-12-12 Thread tarocaravan
Hi, Eventually I ended up building periodically and checking for SCM changee manually in each repository manually. It took some work, but I didn't want to define multiple jobs just for polling. Taro On Tuesday, October 18, 2016 at 2:44:22 PM UTC-7, Rachel Moreno wrote: > > Hi, > > Sorry, it's

Attachments in pipeline notiufication

2016-12-12 Thread tarocaravan
Is it possible to attach files to notifications sent from a pipeline? I'm interested in using slack or hipchat as documented at https://jenkins.io/blog/2016/07/18/pipline-notifications. I like notifications, but I'm trying to think of a way to let users know about many aspects (artifacts) of ou

sshagent seems to cause serialization failure

2016-12-12 Thread David Karr
In a Jenkinsfile, I'm trying to scp a zip file to a remote host, and ssh some commands to unpack it when it gets there. I managed to add a "SSH username with private key" credential, and I can see it in the "Credentials" list. I'm referencing that uuid in my "sshagent" block. When I run the j

Re: sshagent seems to cause serialization failure

2016-12-12 Thread David Karr
Oh, and I tried running this with the "sshagent" block commented out, and the exception does not occur (and nothing useful gets done, of course), so it's definitely coming from that, even though the stacktrace doesn't give me any hint of where it's happening in the script. On Monday, December 1

Re: Job unexpectedly being stopped with success exit code after exactly one hour

2016-12-12 Thread Arvind Jayaprakash
This might be unrelated, but I ran into the magic 60 minute barrier on AWS when using an ELB. Connections over ELB that are idle for 60 minutes get terminated. I'd check for similar settings on say your tomcat config, the connection to your slave etc. etc. On Tuesday, December 6, 2016 at 9:16:

How can i trigger Job-B if Job-A is failed in jenkins build flow

2016-12-12 Thread ravi
Hi, In Jenkins build flow iam trying to trigger Job-B when Job-A is expected to be failed. In below script its entering into the if condition of Job-B and iam able to see the print message as well but Job-B is not triggering. How can i handle when Job-A is expected to fail and need to trigge

Pipeline: aborting an input step marks the stage as failed

2016-12-12 Thread Lionel Orellana
Hi, Consider this stage step with a body and an input step. stage ('Deploy') { input 'Ready to deploy?' ... } If the user clicks Abort on the manual input step the stage is marked as failed. If the input step is moved outside of the stage then the dialog doesn't come up when the user hover