Re: Build abort on shell action not working in pipeline

[Daniel Beck]

> On 20.12.2016, at 13:41, Arvind Jayaprakash  wrote:
> 
> Should I be raising this as a bug instead?

If it's reproducible and you're on the newest plugin versions (and newest 
weekly or LTS release of Jenkins), then that seems reasonable.

-- 
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/F201C7E0-AFB8-4979-8A8D-05332844F8CC%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Build abort on shell action not working in pipeline

[Arvind Jayaprakash]

Should I be raising this as a bug instead?

On Monday, December 12, 2016 at 9:38:37 PM UTC+5:30, Arvind Jayaprakash 
wrote:
>
> 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/e12d459c-ac09-4021-9427-8377835e2a7b%40googlegroups.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: 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.

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.