[JIRA] (JENKINS-55484) Jenkins master zombie executors
Title: Message Title Taras Postument created an issue Jenkins / JENKINS-55484 Jenkins master zombie executors Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2019-01-09 at 4.39.31 PM.png Components: core Created: 2019-01-09 14:44 Environment: Jenkins ver. 2.157 Priority: Major Reporter: Taras Postument Hello. I'm using dockerized Jenkins master with 1 executor configured. I noticed that the number of Jenkins master "zombie" executors keep growing, not sure when but looks like after restart/upgrade. Any ideas on how to clean this up? This could be related to running jenkins in docker, maybe because of container hostname changes every time, etc. Add Comment
[JIRA] (JENKINS-54865) Can't store artifacts in the s3 bucket named with dots
Title: Message Title Taras Postument created an issue Jenkins / JENKINS-54865 Can't store artifacts in the s3 bucket named with dots Issue Type: Bug Assignee: Unassigned Components: artifact-manager-s3-plugin Created: 2018-11-26 16:44 Priority: Critical Reporter: Taras Postument Artifact upload fails with error Retrying upload after: javax.net.ssl.SSLPeerUnverifiedException: Certificate for doesn't match any of the subject alternative names: [*.s3.amazonaws.com, s3.amazonaws.com] Relevant SO Question: https://stackoverflow.com/questions/12755038/ssl-problems-with-s3-aws-using-the-java-api-hostname-in-certificate-didnt-mat Relevant AWS Forum Thread: https://forums.aws.amazon.com/thread.jspa?threadID=105357 Add Comment
[JIRA] (JENKINS-45469) Missing Pipeline DSL step exception is not caught by try-catch
Title: Message Title
Taras Postument commented on JENKINS-45469
Re: Missing Pipeline DSL step exception is not caught by try-catch
Catching Throwable works fine:
catch(Throwable t) {
throw e
}
https://stackoverflow.com/questions/38283476/java-nosuchmethoderror-not-caught-by-exception
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45469) Missing Pipeline DSL step exception is not caught by try-catch
Title: Message Title Taras Postument updated an issue Jenkins / JENKINS-45469 Missing Pipeline DSL step exception is not caught by try-catch Change By: Taras Postument Comment: And there is nothing to be done? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45469) Missing Pipeline DSL step exception is not caught by try-catch
Title: Message Title Taras Postument commented on JENKINS-45469 Re: Missing Pipeline DSL step exception is not caught by try-catch And there is nothing to be done? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52405) Mark parallel jobs cancelled by 'failFast' setting as cancelled, not failed
Title: Message Title Taras Postument commented on JENKINS-52405 Re: Mark parallel jobs cancelled by 'failFast' setting as cancelled, not failed Yep, I would like to this implemented as well Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39464) Pipeline with parallel and no stages does not get visualised correctly
Title: Message Title Taras Postument commented on JENKINS-39464 Re: Pipeline with parallel and no stages does not get visualised correctly Vivek Pandey I'm facing the same problem. Any progress here? See my complete issue described here: JENKINS-39464 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53751) The same parallel scripted and declarative pipelines rendered differently
Title: Message Title
Taras Postument created an issue
Jenkins / JENKINS-53751
The same parallel scripted and declarative pipelines rendered differently
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
declarative.log, declarative.png, scripted.log, scripted.png
Components:
blueocean-plugin
Created:
2018-09-24 17:02
Labels:
blueocean
Priority:
Major
Reporter:
Taras Postument
Hello, I'm trying to migrate my Declarative pipelines to scripted ones and cannot reproduce behavior completely. In order to visualize issue I created 2 identical pipelines defined in a scripted way and in a declarative way. Scripted:
node {
stage("Build") {
parallel([
"Android":{ stage("Android"){ stage("a"){ echo "x" }; stage("a1"){ echo "x" }}},
"iOS":{ stage("iOS"){stage("b"){ echo "x" }; stage("a2"){ echo "x" }}}
])
}
}
Declarative:
pipeline {
agent any
stages {
stage('Build') {
failFast true
parallel {
stage('Android') {
stages {
stage('a') { steps { echo
[JIRA] (JENKINS-53744) Use one agent for parallel stages
Title: Message Title
Taras Postument created an issue
Jenkins / JENKINS-53744
Use one agent for parallel stages
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-09-24 12:01
Priority:
Major
Reporter:
Taras Postument
When using top-level agent definition parallel steps running fine as separate processes on the same agent, but when using top-level "agent none" and trying to set agent for a stage which has 2 parallel stages defined getting the error:
"agent" is not allowed in stage "Test" as it contains parallel stages
What the difference? I want to be able to run parallel stages on one agent defined not on the top level.
pipeline {
agent none
stages {
stage('Test') {
agent { label "agent1" }
parallel {
stage('Build1') {
steps {
echo "Test Build1"
}
}
stage('Build2') {
steps {
echo "Test Build2"
}
}
}
}
}
}
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Taras Postument commented on JENKINS-53311 Re: [Blue Ocean] Sequential stages appear to be completed but are still executing Olivier Lamy I will once I gather more info. It seems too random for me now Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Taras Postument commented on JENKINS-53311 Re: [Blue Ocean] Sequential stages appear to be completed but are still executing Fix seems to be released in 1.8.3 but I can't say it fixes the issue for me. Sometimes steps status displayed correctly and sometimes it shows that no steps are running at all. Also, it seems like on the UI if I select the running step I can't see its details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
Taras Postument edited a comment on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
A bit cleaner workaround here:{code:java}withCredentials([sshUserPrivateKey(credentialsId: ' your- github- rw- key -id ', keyFileVariable: 'GITHUB_KEY')]) {withEnv(["GIT_SSH_COMMAND=ssh -i $GITHUB_KEY -o StrictHostKeyChecking=no"]) {git clone/push git@...}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
Taras Postument commented on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
A bit cleaner workaround here:
withCredentials([sshUserPrivateKey(credentialsId: 'github-rw-key', keyFileVariable: 'GITHUB_KEY')]) {
withEnv(["GIT_SSH_COMMAND=ssh -i $GITHUB_KEY -o StrictHostKeyChecking=no"]) {
git clone/push git@...
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53555) Only one parallel steps displayed like in progress on UI
Title: Message Title Taras Postument created an issue Jenkins / JENKINS-53555 Only one parallel steps displayed like in progress on UI Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2018-09-13 at 1.05.25 PM.png Components: blueocean-plugin Created: 2018-09-13 10:09 Priority: Major Reporter: Taras Postument We have a CI pipeline with 2 parallel execution branches (one for iOS and one for Android). We set it up as 2 parallel stages with substages each. But on the UI when 2 parallel substages being built, only one of them displayed as in progress (when actually both are) and the other one displayed as completed. Add Comment
[JIRA] (JENKINS-53492) Set priorities for Multibranch Pipelines
Title: Message Title Taras Postument created an issue Jenkins / JENKINS-53492 Set priorities for Multibranch Pipelines Issue Type: Improvement Assignee: Unassigned Components: pipeline, prioritysorter-plugin Created: 2018-09-10 09:51 Priority: Major Reporter: Taras Postument I don't see a way to set priorities for MultiBranch projects. I can see the checkbox for the generated job for a branch `Use specific priority for this Job`, but cannot set it, since this view is Read Only, and no such configuration on parent job. Add Comment
[JIRA] (JENKINS-53069) BlueOcean list view
Title: Message Title Taras Postument created an issue Jenkins / JENKINS-53069 BlueOcean list view Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-08-16 14:07 Priority: Major Reporter: Taras Postument Is blueocean planned to support list views? To be able to organize pipelines by category instead of having a huge list of jobs? I didn't see any mention of views in roadmap. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
[JIRA] (JENKINS-52859) ps: unrecognized option: p
Title: Message Title Taras Postument created an issue Jenkins / JENKINS-52859 ps: unrecognized option: p Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin, pipeline Created: 2018-08-02 15:37 Environment: Jenkins Alpine LTS Docker image Priority: Minor Reporter: Taras Postument Hello. I'm using the Blueocean and Pipelines on Alpine linux and started seeing next error on each Pipeline SH step: [Pipeline] sh[decline_cookies_policy-testing-job] Running shell script ps: unrecognized option: p BusyBox v1.28.4 (2018-05-30 10:45:57 UTC) multi-call binary. Usage: ps [-o COL1,COL2=HEADER] Show list of processes -o COL1,COL2=HEADER Select columns for display + echo hello world[Pipeline] } Looks like plugin tries to call `ps` with unsuported for Alpine parameters on each sh step. Add Comment
[JIRA] (JENKINS-49363) How to streaming mp4 artifact on Jenkins build page
Title: Message Title Taras Postument commented on JENKINS-49363 Re: How to streaming mp4 artifact on Jenkins build page Hey. I'm facing the same issue here. I have .mp4 recordings of the Selenium tests execution stored in the artifacts. When I want to play it in the browser I'm getting the Media resource http://jenkins.example.com/job/test/40/artifact/videos/test.mp4 could not be decoded, error: Error Code: NS_ERROR_DOM_MEDIA_METADATA_ERR (0x806e0006) Details: static MP4Metadata::ResultAndByteBuffer mozilla::MP4Metadata::Metadata(mozilla::ByteStream *): Cannot parse metadata Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
