Pipeline: aborting an input step marks the stage as failed

[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 hovers overs the stage so I want to keep it there. 

The old-style stage without a body would have been marked as Aborted:

stage 'Deploy'
input 'Ready to deploy?'

(if the user Aborts, the stage is rightly marked as Aborted). 

Is there a way to make this work with the new stage format? 

Cheers

Lionel.

-- 
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/836c1a27-1ef7-4575-8ec1-7950e4d2efc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 trigger the Job-B

Below is my script using in buildflow: 

ignore(FAILURE) {

build("Job-A")

if (verify != success) {
println "Job-B"
build("Job-B")
}
}

-- 
Thanks & Regards,
Ravi Teja

-- 
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/92d79e07-2f54-4e42-ad25-685867a4a2bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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:59 AM UTC+5:30, mi...@ammd.com.au 
wrote:
>
> I have a long running Jenkins job that can run for more than one hour. 
>
> Via shell scripts, it kicks off an activity in AWS (runs a docker 
> container as a task), then monitors the state of the task every 30 seconds 
> and ends when the task finishes.
>
> As part of the process, it finishes by logging the exit code of the 
> container to the Jenkins console log.
>
> For runs that take less than 1 hour, the output is as expected.
>
> For runs that take more than one hour, the task in AWS continues to run. 
> However the Jenkins log, at the 60 minute mark, abruptly stops and displays 
> a SUCCESS status.
>
> I am thus trying to track down what might be the cause of this. 
>
> I am running Jenkins 2.33 via tomcat7 on a 64 bit AWS Linux server based 
> on the 2016.09 AMI.
>
> I suspect it may be the build_timeout plugin which is installed but not 
> enabled for this job. I have version 1.18 installed.
>
> I don't see anything of relevance in either the tomcat log or the Jenkins 
> system Log at the time.
>
> Any pointers as to what to look for next and where would be 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/e99cee13-7759-4bc1-86e3-dc0fb8c0d0b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: sshagent seems to cause serialization failure

[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 12, 2016 at 4:08:02 PM UTC-8, David Karr wrote:
>
> 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 job, I see the following:
>
> JP_MechIdPrivateKey[-private-key] class[java.lang.String]
>
> [ssh-agent] Using credentials 
> [ssh-agent] Looking for ssh-agent implementation...
> [ssh-agent]   Java/JNR ssh-agent
> [ssh-agent] Skipped registering BouncyCastle, not running on a remote 
> agent
> [ssh-agent] Started.
> [Pipeline] {
>
> [Pipeline] sh
> [ssh-agent] Stopped.
> [usl-parent] Running shell script
> [Pipeline] }
> [Pipeline] // sshagent
> [Pipeline] }
> [Pipeline] // dir
> [Pipeline] sh
> ...
> java.io.NotSerializableException: sun.nio.fs.UnixPath
> at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(
> RiverMarshaller.java:860)
> at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(
> BlockMarshaller.java:65)
> ...
> Caused by: an exception which occurred:
> in field locals
> in field caller
> in field e
> in field program
> in field thread
> in field body
> in field step
> in field thread
> in field this$0
> in field returnAddress
> in field parent
> in field caller
> in field parent
> in field parent
> in field parent
> in field parent
> in field capture
> in field def
> in field closures
> in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@d12af23
> Finished: FAILURE
>
> The code in question looks like this:
> println "JP_MechIdPrivateKey[${JP_MechIdPrivateKey}] 
> class[${JP_MechIdPrivateKey.class.name}]"
> sshagent (credentials: [JP_MechIdPrivateKey]) {
> sh "scp ${javadocJarPath} 
> ${JP_JavadocJarHost}:/tmp"
> sh "ssh ${JP_JavadocJarHost} \"cd 
> ${JP_JavadocRootRemotePath}; rm -rf ${versionNumber}; mkdir 
> ${versionNumber}\""
> sh "ssh ${JP_JavadocJarHost} \"cd 
> ${JP_JavadocRootRemotePath}; jar xvf /tmp/${baseFileName}\""
> }
>
> I believe I've heard that in order to avoid serialization issues, I have 
> to put things in @NonCPS methods, but I don't understand what parts of this 
> would need to go into a @NonCPS method, and what CANNOT go into a @NonCPS 
> method.
>

-- 
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/7d2a0dc5-07b5-43a5-acba-bd611fefde93%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

sshagent seems to cause serialization failure

[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 job, I see the following:

JP_MechIdPrivateKey[-private-key] class[java.lang.String]

[ssh-agent] Using credentials 
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent]   Java/JNR ssh-agent
[ssh-agent] Skipped registering BouncyCastle, not running on a remote agent
[ssh-agent] Started.
[Pipeline] {

[Pipeline] sh
[ssh-agent] Stopped.
[usl-parent] Running shell script
[Pipeline] }
[Pipeline] // sshagent
[Pipeline] }
[Pipeline] // dir
[Pipeline] sh
...
java.io.NotSerializableException: sun.nio.fs.UnixPath
at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(
RiverMarshaller.java:860)
at org.jboss.marshalling.river.BlockMarshaller.doWriteObject(
BlockMarshaller.java:65)
...
Caused by: an exception which occurred:
in field locals
in field caller
in field e
in field program
in field thread
in field body
in field step
in field thread
in field this$0
in field returnAddress
in field parent
in field caller
in field parent
in field parent
in field parent
in field parent
in field capture
in field def
in field closures
in object org.jenkinsci.plugins.workflow.cps.CpsThreadGroup@d12af23
Finished: FAILURE

The code in question looks like this:
println "JP_MechIdPrivateKey[${JP_MechIdPrivateKey}] 
class[${JP_MechIdPrivateKey.class.name}]"
sshagent (credentials: [JP_MechIdPrivateKey]) {
sh "scp ${javadocJarPath} ${JP_JavadocJarHost}:/tmp"
sh "ssh ${JP_JavadocJarHost} \"cd 
${JP_JavadocRootRemotePath}; rm -rf ${versionNumber}; mkdir 
${versionNumber}\""
sh "ssh ${JP_JavadocJarHost} \"cd 
${JP_JavadocRootRemotePath}; jar xvf /tmp/${baseFileName}\""
}

I believe I've heard that in order to avoid serialization issues, I have to 
put things in @NonCPS methods, but I don't understand what parts of this 
would need to go into a @NonCPS method, and what CANNOT go into a @NonCPS 
method.

-- 
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/ea3ea892-e1ac-46fe-8381-572fa453b88b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Attachments in pipeline notiufication

[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 our build, not just that the build was 
"successful" or "failed".

-- 
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/279b7033-24a0-43c4-9478-73d530d3b653%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Polling both svn and git from pipeline

[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 possible with Pipeline:
>
> *Polling is supported across multiple SCMs (changes in one or more will 
> trigger a new build), and again is done according to the SCMs used in the 
> last build of the pipeline.*
>
> You'll have to run it once manually for listening to SCM changes.
>
> More information: 
> https://github.com/jenkinsci/workflow-scm-step-plugin/blob/master/README.md
>
> Best regards,
> Rachel
>
> El jueves, 13 de octubre de 2016, 22:56:16 (UTC+2), Rachel escribió:
>>
>> Hi,
>>
>> In your case, I would have two separated Jenkins jobs, but sharing the 
>> same workspace:
>>
>>- Advanced Project Options > Use custom workspace 
>>
>> I hope be useful.
>>
>> Best regards,
>> Rachel
>>
>> El miércoles, 12 de octubre de 2016, 2:47:08 (UTC+2), taroc...@gmail.com 
>> escribió:
>>>
>>> Is it possible to poll for changes from both svn and git repositories 
>>> from within a pipeline job? In Jenkins, pipeline scm configuration is tied 
>>> to a particular scm type (due to a radio button), but I would like to poll 
>>> both svn and git at the same time. As a result of the poll detecting an scm 
>>> change, I want to invoke only one build.
>>>
>>> As a workaround, maybe I need to have two separate Jenkins jobs? 
>>>
>>

-- 
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/3f0b0a8d-afdd-44f3-9d5e-71d117f392e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline: Hos to test them locally

[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('master') {
  load "${sourcepath}/Jenkinsfile"
}

That allows me to just save locally and run the job.

Even better, I can then run the job using the jenkins-cli.jar and see 
the output in my shell which removes the need to interact with the 
jenkins UI altogether.


java -jar jenkins-cli.jar -s $JENKINS_URL build $JOB_NAME -s -v

Of course you have to be disciplined about checking in WIP and making 
sure that all files your pipeline is trying to use checked in 
eventually, and there are some cases where the above method acts a 
little differently than when pulling from SCM.  Also be sure to check 
"Use Groovy Sandbox" since pipeline scripts coming from SCM have that set.


Pete

On 12/10/2016 9:59 AM, Michael Kobit wrote:
You can use the "Replay" option, which might help you iterate a little 
bit faster. There isn't really a good way to test and validate that 
your pipeline is correct other than just running it.


https://issues.jenkins-ci.org/browse/JENKINS-33925 is open for a test 
framework for Jenkinsfile.


On Fri, Dec 9, 2016 at 1:20 AM Victor Martinez 
> 
wrote:


Hi there,

Just wondering if there is any new supported feature of testing
Jenkinsfile, aka pipelines, locally, if so, where can i find some
examples/docs? I want to get rid of the manual and tedious process
of pushing changes to my repo then look at the jebkibs job andsee
whether it does what i coded. I'd like to speed up my development
with lets say some TDD. If no, will it be supported in the near
future? Or it doesnt make sense?

Thanks guys

--
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/c6122b07-85f3-407b-8e81-ae23651e0b27%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/CALELY9HHZ1wnJq6fvXgBS5DZGxTjMRZo%2B_PxpRZNQDHBJ5ubsQ%40mail.gmail.com 
.

For more options, visit https://groups.google.com/d/optout.



--
Peter McNab | Engineering Tools Tech Lead
T: +1 510-473-3124 | M: +1 408-203-7114
http://www.perforce.com

--
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/584EDC1C.4080604%40perforce.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build abort on shell action not working in pipeline

[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 
>
> Are you on the newest versions of all Pipeline-related plugins?

-- 
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/5f0f6b40-ab23-424e-b582-0f69dbde2d48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
ace-editor  1.1 truefalse
analysis-collector  1.49truefalse
analysis-core   1.80truefalse
ansicolor   0.4.3   truefalse
ant 1.4 truefalse
antisamy-markup-formatter   1.5 truefalse
artifactory 2.8.1   truefalse
audit-trail 2.1 truefalse
authentication-tokens   1.3 truefalse
blueocean   1.0.0-b13   truefalse
blueocean-autofavorite  0.5 truefalse
blueocean-commons   1.0.0-b13   truefalse
blueocean-config1.0.0-b13   truefalse
blueocean-dashboard 1.0.0-b13   truefalse
blueocean-display-url   1.3 truefalse
blueocean-events1.0.0-b13   truefalse
blueocean-i18n  1.0.0-b13   truefalse
blueocean-jwt   1.0.0-b13   truefalse
blueocean-personalization   1.0.0-b13   truefalse
blueocean-pipeline-api-impl 1.0.0-b13   truefalse
blueocean-rest  1.0.0-b13   truefalse
blueocean-rest-impl 1.0.0-b13   truefalse
blueocean-web   1.0.0-b13   truefalse
bouncycastle-api2.16.0  truefalse
branch-api  1.11.1  truefalse
build-metrics   1.3 truefalse
build-name-setter   1.6.5   truefalse
build-timeout   1.18truefalse
build-with-parameters   1.3 false   false
checkstyle  3.47truefalse
cloudbees-folder5.13truefalse
conditional-buildstep   1.3.5   truefalse
config-file-provider2.13truefalse
credentials 2.1.10  truefalse
credentials-binding 1.10truefalse
dashboard-view  2.9.10  truefalse
database1.5 truefalse
database-postgresql 1.0 truefalse
dependency-check-jenkins-plugin 1.4.4   truefalse
display-url-api 0.5 truefalse
docker-build-publish1.3.1   truefalse
docker-build-step   1.35truefalse
docker-commons  1.5 truefalse
docker-traceability 1.1 truefalse
docker-workflow 1.9 truefalse
durable-task1.12truefalse
email-ext   2.40.4  truefalse
envinject   1.93.1  truefalse
external-monitor-job1.6 truefalse
favorite2.0.2   truefalse
findbugs4.69truefalse
flexible-publish0.15.2  truefalse
ghprb   1.33.1  false   false
git 3.0.1   truefalse
git-client  2.1.0   truefalse
git-server  1.7 truefalse
github  1.24.0  truefalse
github-api  1.80truefalse
github-branch-source1.10.1  truefalse
github-organization-folder  1.5 truefalse
github-pr-coverage-status   1.1.0   false   false
github-pullrequest  0.1.0-rc17  truefalse
global-build-stats  1.4 truefalse
gradle  1.25truefalse
groovy  1.30truefalse
groovy-postbuild2.3.1   truefalse
handlebars  1.1.1   truefalse
hsts-filter-plugin  1.0 truefalse
icon-shim   2.0.3   truefalse
ivy 1.26truefalse
jackson2-api2.7.3   truefalse
jacoco  2.1.0   truefalse
javadoc 1.3 truefalse
jenkins-multijob-plugin 1.23truefalse
job-dsl 1.53truefalse
jobConfigHistory2.15truefalse
jobgenerator1.22truefalse
jquery  1.11.2-0truefalse
jquery-detached 1.2.1   truefalse
junit   1.19truefalse
ldap1.11truefalse
logfilesizechecker  1.2 truefalse
m2release   0.14.0  truefalse
mailer  1.18truefalse
managed-scripts 1.2.4   truefalse
mapdb-api   1.0.6.0 truefalse
matrix-auth 1.4 truefalse
matrix-project  1.7.1   truefalse
maven-plugin2.14truefalse
mesos   0.13.1  truefalse
metrics 3.1.2.9 truefalse
metrics-graphite3.0.0   truefalse
modernstatus1.2 truefalse
momentjs1.1.1   truefalse
multiple-scms   0.6 truefalse
pam-auth1.2 truefalse
parameterized-trigger   2.32truefalse
pipeline-aggregator-view1.4 truefalse
pipeline-build-step 2.4 truefalse
pipeline-githubnotify-step  1.0.0   

Re: Spawn multiple jobs

[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 not passing different parameters -- just print 
`deployment` inside the actual block, not directly in the loop.

And if that's correct: Jenkins collapses identical queue items. Use different 
parameters if you want different builds.


-- 
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/13988E3A-45F0-4D43-9C16-9D6F5DE9BB4C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Build abort on shell action not working in pipeline

[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 
"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/6CB774B0-60B7-4071-8ACF-1D0E85C79A98%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Spawn multiple jobs

[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").split(/[ ,]+/)
def branches = [:]
def int i = 0 
for (String deployment : inputParameter) {
  println("${i} ${deployment}")
  
  branches["deployment-${deployment}"] = {
build( 'aa', inputParameter: "${deployment}" )
  }
  
  i++   
}

parallel branches

OUTPUT:

Started by user
0 a
1 b
2 c
3 d
4 e
5 f
parallel {
Schedule job aa 
Schedule job aa 
Schedule job aa 
Schedule job aa 
Schedule job aa 
Schedule job aa 
Build aa #23  started
Build aa #23  started
Build aa #23  started
Build aa #23  started
Build aa #23  started
Build aa #23  started
aa #23  completed 
}
Aborted by
Build was aborted
Finished: ABORTED




-- 
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/e38e3d52-31cf-4fbd-be0d-aa73a875b4aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline one-liner causes hanging job ?

[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 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/a1019ca5-c93f-46bb-9368-6289e9ec348d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

OSX Jenkins UI password

[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 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/b0d36922-b35b-4e50-b97d-f6d6a478d4cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 


You can check the Pipeline Syntax link on you Pipeline script, on how to 
use the sh: Shell script step, to pass a normal scp/ssh command. 

-- 
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/05a23acd-1a2d-4af6-ae75-003d5cfa5281%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Build abort on shell action not working in pipeline

[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 /'
  }
}

Notice that this pipeline does nothing but kick off a single long running 
shell command. grep is known to respect SIGINT on pretty much every *nix 
out there. So the expectation on trying to abort this build would be for 
the step to stop executing on reception of SIGINT. However, the grep 
continues to run and issuing multiple abort requests throws up the familiar 
*Click 
here to forcibly terminate running steps* message. Clicking on it issues a 
different signal, presumably SIGKILL and this seems to get reliably 
delivered to the process. The question of course is why is SIGINT not 
getting delivered to the shell command whereas SIGKILL does seem to get 
delivered.

The slave is/was launched using the mesos cloud i.e. it connects over JNLP 
and not ssh

-- 
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/962ad5d7-3c31-4bd5-a5e3-ba038747c900%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[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 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/57e2aeee-6667-45cb-bf83-4105c92a1e47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.