[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title tanmoy roy commented on JENKINS-57695 Re: Jira issue not created when jenkins build failed sathish chinnasamy you tried with the latest version of the plugin, or v 3.0.5. What if we need to create the issue as BUG, is that possible?? if not we need to manually update the raised ticket from Task to BUG. Please let me know if my understanding is correct. And if the above case that i mentioned is valid than i think its not a permanent solution. Please suggest. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199631.1558935625000.22366.1559803440350%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57698) Results are not saving in the mentioned directory after the execution in Execute Microfocus Test from Filesystem
Title: Message Title tanmoy roy edited a comment on JENKINS-57698 Re: Results are not saving in the mentioned directory after the execution in Execute Microfocus Test from Filesystem Let me elaborate my requirement.Present scenario- The results are saved in Jenkins Workspace with some random number folders eg- *36892c.*What we need- The result to be saved in any location which is preferable to the user. And also User can be able to save the results file with any kind of custom name.eg- /path to the results file to be saved/PrerformanceRun1 (or any other custom name to the results folder. Requirement is how we are currently saving the results using the LR controller where the user defines the result folder name. Want the same to be implemented in the LR plugin. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199636.155895364.22363.1559803260168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57686) Add Java 8 functional interfaces for behavioural design pattern
Title: Message Title Parichay Barpanda stopped work on JENKINS-57686 Change By: Parichay Barpanda Status: In Progress Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199621.1558824827000.22360.1559801580332%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57747) Add form validation for gitlab gold and ultimate server urls
Title: Message Title Parichay Barpanda stopped work on JENKINS-57747 Change By: Parichay Barpanda Status: In Progress Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199692.1559151818000.22361.1559801580409%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57872) Avoid handling events for Octane if no Octane client definition is defined
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-57872 Avoid handling events for Octane if no Octane client definition is defined Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-06-06 06:10 Priority: Minor Reporter: Radi Berkovich 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199836.1559801411000.22359.1559801460097%40Atlassian.JIRA. For more o
[JIRA] (JENKINS-57764) Document developer workflow for changing React component in a README in the repo
Title: Message Title Jack Shen resolved as Fixed https://github.com/ShenJack/working-hours-_javascript_-impl Jenkins / JENKINS-57764 Document developer workflow for changing React component in a README in the repo Change By: Jack Shen Status: Open Resolved Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199710.1559223295000.22350.1559797560199%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57740) M1-Extract the plugin from system configure to a standalone page
Title: Message Title Jack Shen updated JENKINS-57740 Jenkins / JENKINS-57740 M1-Extract the plugin from system configure to a standalone page Change By: Jack Shen Status: In Progress Fixed but Unreleased Resolution: 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199685.1559142249000.22348.1559797500290%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54656) cvs plugin broken - not possible to add new projects
Title: Message Title Daniel O'Connor commented on JENKINS-54656 Re: cvs plugin broken - not possible to add new projects David's patch works for me, +1 to commit 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195447.1542303074000.22345.1559797380369%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57698) Results are not saving in the mentioned directory after the execution in Execute Microfocus Test from Filesystem
Title: Message Title tanmoy roy commented on JENKINS-57698 Re: Results are not saving in the mentioned directory after the execution in Execute Microfocus Test from Filesystem Let me elaborate my requirement. Present scenario- The results are saved in Jenkins Workspace with some random number eg- 36892c. What we need- The result to be saved in any location which is preferable to the user. And also User can be able to save the results file with any kind of custom name. eg- /path to the results file to be saved/PrerformanceRun1 (or any other custom name to the results folder. Requirement is how we are currently saving the results using the LR controller where the user defines the result folder name. Want the same to be implemented in the LR plugin. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199636.155895364.22336.1559793780193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57871) Input directive is blocking executor in declarative pipeline
Title: Message Title
jubel han updated an issue
Jenkins / JENKINS-57871
Input directive is blocking executor in declarative pipeline
Change By:
jubel han
Here are the simple pipeline that I'm using{code: groove groovy }pipeline { agent {kubernetes { label 'mypod'} } stages {stage('input') { input { message "Should we continue?" } steps {echo "continued" }} }}{code}The issue was originally found in the usual declarative pipeline and it had been fixed eventually.https://issues.jenkins-ci.org/browse/JENKINS-37515https://issues.jenkins-ci.org/browse/JENKINS-48379however, it is reproducing with the kubernete plugin 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199834.1559784021000.22334.1559784060272%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57871) Input directive is blocking executor in declarative pipeline
Title: Message Title
jubel han created an issue
Jenkins / JENKINS-57871
Input directive is blocking executor in declarative pipeline
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
input-blocking-executor.png
Components:
kubernetes-plugin, pipeline-model-definition-plugin
Created:
2019-06-06 01:20
Environment:
Jenkins ver. 2.164.3 kubernetes plugin: 1.15.5 pipeline plugin: 2.6 Pipeline declarative plugin: 1.3.8
Labels:
declarative-pipeline input kubernetes-plugin
Priority:
Major
Reporter:
jubel han
Here are the simple pipeline that I'm using
Unable to find source-code formatter for language: groove. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, _javascript_, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
pipeline {
agent {
kubernetes {
label 'mypod'
}
}
stages {
stage('input') {
input {
m
[JIRA] (JENKINS-57870) populate: previewOnly(quiet: true) fail
Title: Message Title
Hokwang Lee created an issue
Jenkins / JENKINS-57870
populate: previewOnly(quiet: true) fail
Issue Type:
Bug
Assignee:
Paul Allen
Components:
p4-plugin
Created:
2019-06-06 00:52
Environment:
Jenkins ver. 2.164.3 p4-plugin : 1.10.0
Priority:
Blocker
Reporter:
Hokwang Lee
Hi, When I use jenkins with swarm automated test, I use the pipeline code like
checkout perforce(
populate: previewOnly(quiet: true)
workspace: templateSpec( ... )
)
and template workspace have all depot like
//depotA/... //$P4_CLIENT/depotA/...
//depotB/... //$P4_CLIENT/depotB/...
//depotC/... //$P4_CLIENT/depotC/...
...
and I create new workspace and delete after finished job always. as you know, because I want to do like unshelve files in the review item and run some test. I don't need sync, sync -n or sync -k and flush, delete, whatever.. here's error message. [Pipeline] container[Pipeline] {[Pipeline] checkout*02:02:57* (p4):cmd:... p4 client -o TEMPLATE_SE_SWARM_AT_SA*02:02:57* p4 client -o TEMPLATESE_SWARM_AT_SA*02:02:57* 02:02:57 (p4):stop:3*02:02:57* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z*02:02:57* p4 client -o jenkins-SE
[JIRA] (JENKINS-54530) Upgrade maven embedder from 3.1.0 to at least 3.5.4
Title: Message Title Olivier Lamy edited a comment on JENKINS-54530 Re: Upgrade maven embedder from 3.1.0 to at least 3.5.4 [~ianw] since for 2years now Jenkins core require 1.8... [https://jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195301.1541643577000.22328.1559782200150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57869) Add CI to repository
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-57869 Add CI to repository Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-06 00:18 Labels: plugin-manager gsoc-2019 Priority: Minor Reporter: Natasha Stopa Add Jenkinsfile which instructs ci.jenkins.io how to build the component. Add Comment
[JIRA] (JENKINS-54530) Upgrade maven embedder from 3.1.0 to at least 3.5.4
Title: Message Title Olivier Lamy commented on JENKINS-54530 Re: Upgrade maven embedder from 3.1.0 to at least 3.5.4 Ian Williams since 2years now Jenkins core require 1.8... https://jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195301.1541643577000.22312.1559778240101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Jesse Glick commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline Not currently, no. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175287.1476142592000.22289.1559778120546%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51641) Duplicate commits displayed on Pipeline build when using "Poll SCM" and "Pipeline script from SCM"
Title: Message Title Jack Bradach updated an issue Jenkins / JENKINS-51641 Duplicate commits displayed on Pipeline build when using "Poll SCM" and "Pipeline script from SCM" Change By: Jack Bradach Component/s: p4-plugin 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191054.1527786048000.22287.1559776980180%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51641) Duplicate commits displayed on Pipeline build when using "Poll SCM" and "Pipeline script from SCM"
Title: Message Title Jack Bradach commented on JENKINS-51641 Re: Duplicate commits displayed on Pipeline build when using "Poll SCM" and "Pipeline script from SCM" We see the same issue in our environment, using the Perforce plugin in poll mode. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191054.1527786048000.22284.1559776920162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34313) SAXParseException from parallel SCM checkout
Title: Message Title Devin Nusbaum updated JENKINS-34313 A fix for this issue was just released in Pipeline SCM Step Plugin version 2.8. Jenkins / JENKINS-34313 SAXParseException from parallel SCM checkout Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-scm-step 2.8 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169867.1460993343000.22251.1559769001530%40Atlassi
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Andrey Babushkin commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline Jesse Glick, are there any alternative ways to find out what builds were scheduled on a node? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175287.1476142592000.0.1559766120511%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Jesse Glick commented on JENKINS-57805 Re: Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance For the first stack trace, I would start by fixing bruteForceScanForEnclosingBlock to not assume !current.getParents().isEmpty(). You could probably remove the special-case handling of FlowStartNode in that case: when the parents list is empty for any reason, break the recursion and return null. Halting execution if there is a problem in the node graph seems reasonable to me. Something more important is likely to go wrong with the build anyway, or have gone wrong already. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199756.1559335134000.22218.1559765940167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-57805 Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance Change By: Jesse Glick Labels: robustness 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199756.1559335134000.22209.1559765340193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title Mike Pflugfelder edited a comment on JENKINS-50711 Re: plugin doesn't work with ssh link to git repo I'm having the same problem, and it appears at this time that the workaround of using https to clone the repo does in fact work. Jenkins: 2.179Git client plugin: 2.7.7Git Parameter Plug-In: 0.9.10Git plugin: 3.10.0 Jenkins master is Linux, Build slave is Windows 10 Pro 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189802.1523350889000.22167.1559763000267%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50711) plugin doesn't work with ssh link to git repo
Title: Message Title Mike Pflugfelder commented on JENKINS-50711 Re: plugin doesn't work with ssh link to git repo I'm having the same problem, and it appears at this time that the workaround of using https to clone the repo does in fact work. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189802.1523350889000.22161.1559762760193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57868) Bitbucket branch source plugin deletes all projects on connection issue
Title: Message Title Marzuk Rashid updated an issue Jenkins / JENKINS-57868 Bitbucket branch source plugin deletes all projects on connection issue Change By: Marzuk Rashid After a recent Bitbucket connection issue resulting from [this| [ https://bitbucket.status.atlassian.com/incidents/l50d1j43zdj9] ] Bitbucket outage, the [ Bitbucket brance bitbucket branch source plugin| [ https://wiki.jenkins.io/display/JENKINS/Bitbucket+Branch+Source+Plugin] |https://wiki.jenkins.io/display/JENKINS/Bitbucket+Branch+Source+Plugin] deleted all our projects. Once the plugin was able to connect to Bitbucket again, all previous builds were deleted and the build numbers restarted from 1. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199831.1559762494000.22158.1559762640058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57868) Bitbucket branch source plugin deletes all projects on connection issue
Title: Message Title Marzuk Rashid created an issue Jenkins / JENKINS-57868 Bitbucket branch source plugin deletes all projects on connection issue Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2019-06-05 19:21 Environment: Jenkins version 2.164.3 Bitbucket branch source ver. 2.4.4 Gentoo release 2.6 Priority: Critical Reporter: Marzuk Rashid After a recent Bitbucket connection issue resulting from [this|https://bitbucket.status.atlassian.com/incidents/l50d1j43zdj9] Bitbucket outage, the [Bitbucket brance source plugin|https://wiki.jenkins.io/display/JENKINS/Bitbucket+Branch+Source+Plugin|https://wiki.jenkins.io/display/JENKINS/Bitbucket+Branch+Source+Plugin] deleted all our projects. Once the plugin was able to connect to Bitbucket again, all previous builds were deleted and the build numbers restarted from 1. Add Comment
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Devin Nusbaum commented on JENKINS-57805 Re: Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance Jesse Glick Any thoughts on a good place to handle the error shown by the second stack trace in the description here in Pipeline code? (assuming you think it makes sense to try to handle this kind of error) Since FlowNodes are not eagerly loaded on restart and may need to be reloaded if they are evicted from the cache, it seems like anything that loads FlowNodes needs to throw IOException, but there are places where we swallow or rethrow these kinds of errors as a RuntimeException, potentially leaving the flow graph corrupt for other users (See FlowNode.getParents, StandardGraphLookupView.bruteForceScanForExistingBlock). Does my second idea (make FlowNode.getNode try to stop the execution when a node cannot be loaded) seem like something worth looking into? If it is even possible, I am a little concerned that it might cause executions that could have otherwise completed successfully or with minor data loss to fail completely. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199756.1559335134000.22156.1559762160048%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-57805
Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Change By:
Devin Nusbaum
I have seen the following exception break Queue maintenance and make it impossible for new jobs to be scheduled:{noformat}2019-04-29 14:24:14.748+ [id=118] SEVERE hudson.triggers.SafeTimerTask#run: Timer task hudson.model.Queue$MaintainTask@7edb0f64 failedjava.lang.IndexOutOfBoundsException: Index: 0 at java.util.Collections$EmptyList.get(Collections.java:4454) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.bruteForceScanForEnclosingBlock(StandardGraphLookupView.java:150) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.findEnclosingBlockStart(StandardGraphLookupView.java:197) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.findAllEnclosingBlockStarts(StandardGraphLookupView.java:217) at org.jenkinsci.plugins.workflow.flow.FlowExecution.findAllEnclosingBlockStarts(FlowExecution.java:299) at org.jenkinsci.plugins.workflow.graph.FlowNode.getEnclosingBlocks(FlowNode.java:195) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.concatenateAllEnclosingLabels(ExecutorStepExecution.java:527) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.getAffinityKey(ExecutorStepExecution.java:545) at hudson.model.LoadBalancer$1.assignGreedily(LoadBalancer.java:115) at hudson.model.LoadBalancer$1.map(LoadBalancer.java:105) at hudson.model.LoadBalancer$2.map(LoadBalancer.java:157) at hudson.model.Queue.maintain(Queue.java:1629) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2887) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){noformat}As best as I can tell, the root cause was that a channel reading a flow node's parent node XML file was interrupted, which threw an exception and left the flow graph corrupted. (I am not sure how or why the read was interrupted, but since the same thing would happen if the file was corrupted on disk it seems like a reasonable failure mode to handle.) Here is the stack trace for that issue:{noformat}2019-04-29 14:24:14.745+ [id=118] WARNING o.j.p.workflow.graph.FlowNode#loadParents: failed to load parents of 96java.nio.channels.ClosedByInterruptException at java
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-57805
Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Change By:
Devin Nusbaum
I have seen the following exception break Queue maintenance and make it impossible for new jobs to be scheduled:{noformat}2019-04-29 14:24:14.748+ [id=118] SEVERE hudson.triggers.SafeTimerTask#run: Timer task hudson.model.Queue$MaintainTask@7edb0f64 failedjava.lang.IndexOutOfBoundsException: Index: 0 at java.util.Collections$EmptyList.get(Collections.java:4454) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.bruteForceScanForEnclosingBlock(StandardGraphLookupView.java:150) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.findEnclosingBlockStart(StandardGraphLookupView.java:197) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.findAllEnclosingBlockStarts(StandardGraphLookupView.java:217) at org.jenkinsci.plugins.workflow.flow.FlowExecution.findAllEnclosingBlockStarts(FlowExecution.java:299) at org.jenkinsci.plugins.workflow.graph.FlowNode.getEnclosingBlocks(FlowNode.java:195) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.concatenateAllEnclosingLabels(ExecutorStepExecution.java:527) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.getAffinityKey(ExecutorStepExecution.java:545) at hudson.model.LoadBalancer$1.assignGreedily(LoadBalancer.java:115) at hudson.model.LoadBalancer$1.map(LoadBalancer.java:105) at hudson.model.LoadBalancer$2.map(LoadBalancer.java:157) at hudson.model.Queue.maintain(Queue.java:1629) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2887) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){noformat}As best as I can tell, the root cause was that a channel reading a flow node's parent node XML file was interrupted, which threw an exception and left the flow graph corrupted. (I am not sure how or why the read was interrupted, but since the same thing would happen if the file was corrupted on disk it seems like a reasonable failure mode to handle.) Here is the stack trace for that issue:{noformat}2019-04-29 14:24:14.745+ [id=118] WARNING o.j.p.workflow.graph.FlowNode#loadParents: failed to load parents of 96java.nio.channels.ClosedByInterruptException at java
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-57805
Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Change By:
Devin Nusbaum
I have seen the following exception break Queue maintenance and make it impossible for new jobs to be scheduled:{noformat}2019-04-29 14:24:14.748+ [id=118] SEVERE hudson.triggers.SafeTimerTask#run: Timer task hudson.model.Queue$MaintainTask@7edb0f64 failedjava.lang.IndexOutOfBoundsException: Index: 0 at java.util.Collections$EmptyList.get(Collections.java:4454) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.bruteForceScanForEnclosingBlock(StandardGraphLookupView.java:150) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.findEnclosingBlockStart(StandardGraphLookupView.java:197) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.findAllEnclosingBlockStarts(StandardGraphLookupView.java:217) at org.jenkinsci.plugins.workflow.flow.FlowExecution.findAllEnclosingBlockStarts(FlowExecution.java:299) at org.jenkinsci.plugins.workflow.graph.FlowNode.getEnclosingBlocks(FlowNode.java:195) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.concatenateAllEnclosingLabels(ExecutorStepExecution.java:527) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.getAffinityKey(ExecutorStepExecution.java:545) at hudson.model.LoadBalancer$1.assignGreedily(LoadBalancer.java:115) at hudson.model.LoadBalancer$1.map(LoadBalancer.java:105) at hudson.model.LoadBalancer$2.map(LoadBalancer.java:157) at hudson.model.Queue.maintain(Queue.java:1629) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2887) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){noformat}As best as I can tell, the root cause was that a channel reading a flow node's parent node XML file was interrupted, which threw an exception and left the flow graph corrupted. (I am not sure how or why the read was interrupted, but since the same thing would happen if the file was corrupted on disk it seems like a reasonable failure mode to handle.) Here is the stack trace for that issue:{noformat}2019-04-29 14:24:14.745+ [id=118] WARNING o.j.p.workflow.graph.FlowNode#loadParents: failed to load parents of 96java.nio.channels.ClosedByInterruptException at java
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-57805
Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Change By:
Devin Nusbaum
I have seen the following exception break Queue maintenance and make it impossible for new jobs to be scheduled:{noformat}2019-04-29 14:24:14.748+ [id=118] SEVERE hudson.triggers.SafeTimerTask#run: Timer task hudson.model.Queue$MaintainTask@7edb0f64 failedjava.lang.IndexOutOfBoundsException: Index: 0 at java.util.Collections$EmptyList.get(Collections.java:4454) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.bruteForceScanForEnclosingBlock(StandardGraphLookupView.java:150) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.findEnclosingBlockStart(StandardGraphLookupView.java:197) at org.jenkinsci.plugins.workflow.graph.StandardGraphLookupView.findAllEnclosingBlockStarts(StandardGraphLookupView.java:217) at org.jenkinsci.plugins.workflow.flow.FlowExecution.findAllEnclosingBlockStarts(FlowExecution.java:299) at org.jenkinsci.plugins.workflow.graph.FlowNode.getEnclosingBlocks(FlowNode.java:195) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.concatenateAllEnclosingLabels(ExecutorStepExecution.java:527) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask.getAffinityKey(ExecutorStepExecution.java:545) at hudson.model.LoadBalancer$1.assignGreedily(LoadBalancer.java:115) at hudson.model.LoadBalancer$1.map(LoadBalancer.java:105) at hudson.model.LoadBalancer$2.map(LoadBalancer.java:157) at hudson.model.Queue.maintain(Queue.java:1629) at hudson.model.Queue$MaintainTask.doRun(Queue.java:2887) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){noformat}As best as I can tell, the root cause was that a channel reading a flow node's parent node XML file was interrupted, which threw an exception and left the flow graph corrupted. (I am not sure how or why the read was interrupted, but since the same thing would happen if the file was corrupted on disk it seems like a reasonable failure mode to handle.) Here is the stack trace for that issue:{noformat}2019-04-29 14:24:14.745+ [id=118] WARNING o.j.p.workflow.graph.FlowNode#loadParents: failed to load parents of 96java.nio.channels.ClosedByInterruptException at java
[JIRA] (JENKINS-56682) Unable to use initializers in sandboxed Groovy scripts
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-56682
Unable to use initializers in sandboxed Groovy scripts
Change By:
Devin Nusbaum
Since the workflow-cps was upgraded to 2.64, fields defined on the class for the script itself using @Field annotations are or explicit class syntax, and static and instance initializer blocks for the script itself that reference other fields in the script do not working work anymore. This issue also affects the use of classes from shared libraries in initializers in Groovy scripts. Original reported case: The following pipeline works fine in 2.63:{code:java}import groovy.transform.Field@Field final SOMETHING='bar'@Field final MY_CONSTANT="foo $SOMETHING"node() { do_stuff()}def do_stuff() { sh "echo $MY_CONSTANT"}{code}With workflow-cps 2.64, this gives the following exception: {noformat}Groovy.lang.MissingPropertyException: No such property: SOMETHING for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:58) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:264) at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:288) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292) at org.kohsuke.groovy.sandbox.impl.Checker$checkedGetProperty.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:230) at WorkflowScript.(WorkflowScript:3) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:434)Caused: groovy.lang.GroovyRuntimeException: Failed to create Script instance for class: class WorkflowScript. Reason at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:466) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.lambda$doParse$0(CpsGroovyShell.java:135) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:136) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:132) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521) at org.jenkinsci.plugins.workflow.job.Wo
[JIRA] (JENKINS-56682) Unable to use initializers in sandboxed Groovy scripts
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-56682
Unable to use initializers in sandboxed Groovy scripts
Change By:
Devin Nusbaum
Since the workflow-cps was upgraded to 2.64, fields defined on the class for the script itself using @Field annotations are or explicit class syntax, and static and instance initializer blocks for the script itself that reference other fields in the script do not working work anymore. This issue also affects the use of classes from shared libraries in initializers in Groovy scripts. Original reported case: The following pipeline works fine in 2.63:{code:java}import groovy.transform.Field@Field final SOMETHING='bar'@Field final MY_CONSTANT="foo $SOMETHING"node() { do_stuff()}def do_stuff() { sh "echo $MY_CONSTANT"}{code}With workflow-cps 2.64, this gives the following exception: {noformat}Groovy.lang.MissingPropertyException: No such property: SOMETHING for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:58) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:264) at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:288) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292) at org.kohsuke.groovy.sandbox.impl.Checker$checkedGetProperty.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:230) at WorkflowScript.(WorkflowScript:3) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:434)Caused: groovy.lang.GroovyRuntimeException: Failed to create Script instance for class: class WorkflowScript. Reason at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:466) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.lambda$doParse$0(CpsGroovyShell.java:135) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:136) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:132) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521) at org.jenkinsci.plugins.workflow.job.Wo
[JIRA] (JENKINS-56682) Unable to use initializers in sandboxed Groovy scripts
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-56682
Unable to use initializers in sandboxed Groovy scripts
Change By:
Devin Nusbaum
Since the workflow-cps was upgraded to 2.64 /script-security 1.54 , fields defined on the class for the script itself using @Field annotations or explicit class syntax, and static and instance initializer blocks for the script itself that reference other fields in the script do not work anymore , are rejected by the Groovy sandbox . This issue also affects the use of classes from shared libraries in initializers in Groovy scripts.Original reported case:The following pipeline works fine in 2.63:{code:java}import groovy.transform.Field@Field final SOMETHING='bar'@Field final MY_CONSTANT="foo $SOMETHING"node() { do_stuff()}def do_stuff() { sh "echo $MY_CONSTANT"}{code}With workflow-cps 2.64, this gives the following exception:{noformat}Groovy.lang.MissingPropertyException: No such property: SOMETHING for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:58) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:264) at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:288) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292) at org.kohsuke.groovy.sandbox.impl.Checker$checkedGetProperty.callStatic(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:56) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:194) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:230) at WorkflowScript.(WorkflowScript:3) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:434)Caused: groovy.lang.GroovyRuntimeException: Failed to create Script instance for class: class WorkflowScript. Reason at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:466) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.lambda$doParse$0(CpsGroovyShell.java:135) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:136) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:132) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521) a
[JIRA] (JENKINS-56682) Unable to use initializers in sandboxed Groovy scripts
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-56682 Unable to use initializers in sandboxed Groovy scripts Change By: Devin Nusbaum Summary: Unable to use @Field annotations initializers in sandboxed Groovy scripts 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198319.1553261135000.22125.1559760480323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job
Title: Message Title Scott Hebert commented on JENKINS-57642 Re: Wrong parameter type and squashing its content when trigger a job Released in v1.1.8. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199573.1558615641000.22122.1559760420199%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title John Jones updated an issue Jenkins / JENKINS-50181 ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile Change By: John Jones Repro:- Add Credentials - set Kind to "SSH Username with private key" - tick "enter directly" - paste a password-less private key without a trailing newline- Attempt to use credentials (I used ssg ssh -agent from a Jenkinsfile)- Observe that ssh-add will prompt for a passphrase in the logs and the ssh-add has failed.The relevant part of my logs looked like this:```[Pipeline] sshagent[ssh-agent] Using credentials jenkins (Github SSH key)[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)$ ssh-agentSSH_AUTH_SOCK=/tmp/ssh-rEGjLSRTHULl/agent.3927SSH_AGENT_PID=3929[ssh-agent] started an agent$ ssh-add /var/lib/jenkins/workspace/job@tmp/private_key_2980200938951827942.keyEnter passphrase for /var/lib/jenkins/workspace/job@tmp/private_key_2980200938951827942.key: [Pipeline] // sshagent[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: Failed to run ssh-addFinished: FAILURE```Adding the trailing newline to input in the web-ui resolves this issue. Adding multiple newlines didn't seem have any adverse effect so Jenkins should probably just add a newline when it writes the keyfile. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57867) Optionally allow for idempotent handling of SCMEvents
Title: Message Title Phil Madden closed an issue as Won't Do Ticket opened erroneously. I did not realize that the git-branch-source-plugin has replaced this plugin. Jenkins / JENKINS-57867 Optionally allow for idempotent handling of SCMEvents Change By: Phil Madden Status: Open Closed Resolution: Won't Do 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199829.1559758162000.22111.1559759580096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50328) Pipeline editor not working if Script Path is set
Title: Message Title Jim Yanko commented on JENKINS-50328 Re: Pipeline editor not working if Script Path is set Just discovered this problem today while working on team adoption of Jenkins / BlueOcean. In our case, dev started out with placing the Jenkinsfile at the repo path /build/Jenkinsfile rather than at /Jenkinsfile and defining the path to the jenkinsfile in the job here http:///jenkins/job//configure As others have mentioned, builds do run, but the BlueOcean editor does not show any stages or steps when a user looks there. This in turn creates confusion since they see the steps in the build results screen, but not in the editor screen where they expect to see them. At this point, I'm concerned of the psychology at play when working with teams to get started using this. One of the selling points on BlueOcean to management is that it makes it easy to use and build the job steps, and the code gets commited to your repo easily. So changes can be made in a UI or by hand. In practice, when one project keeps the Jenkinsfile at root and another stores it elsewhere, this confuses the newer user who may be looking at a job configured by someone else for inspiration on how to add steps to a project/pipeline they are working on themselves when they see stages and steps in one project that but another appears to have no steps when they look at it in the UI. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189375.152167439.22104.1559759280251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57847) NPE when using Vault Plugin with older version of vault
Title: Message Title
Joshua Hoblitt commented on JENKINS-57847
Re: NPE when using Vault Plugin with older version of vault
I have also observed this with current master (2.2.1-SNAPSHOT (private-54946854-jhoblitt)) and vault 1.0.0.
java.lang.NullPointerException
at com.bettercloud.vault.api.Logical.read(Logical.java:73)
at com.datapipe.jenkins.vault.VaultAccessor.read(VaultAccessor.java:52)
at com.datapipe.jenkins.vault.VaultBuildWrapper.provideEnvironmentVariablesFromVault(VaultBuildWrapper.java:136)
at com.datapipe.jenkins.vault.VaultBuildWrapper.setUp(VaultBuildWrapper.java:89)
at org.jenkinsci.plugins.workflow.steps.CoreWrapperStep$Execution2.doStart(CoreWrapperStep.java:97)
at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE
It also looks like there is something strange with the behavior of the "Vault Token Credential" Credentials type – when "updating it" the token field is always blank (no ***}}s) as are present with the {{2.2.0 release.
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.
To view this discus
[JIRA] (JENKINS-57751) Unable to delete server configuration
Title: Message Title Parichay Barpanda updated JENKINS-57751 Jenkins / JENKINS-57751 Unable to delete server configuration Change By: Parichay Barpanda Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199696.1559161096000.22098.1559758620096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57867) Optionally allow for idempotent handling of SCMEvents
Title: Message Title Phil Madden created an issue Jenkins / JENKINS-57867 Optionally allow for idempotent handling of SCMEvents Issue Type: Improvement Assignee: Phil Madden Components: github-organization-folder-plugin Created: 2019-06-05 18:09 Priority: Minor Reporter: Phil Madden Add a check box to toggle idempotent handling of SCMEvents. Currently, the brach-api-plugin will not trigger jobs if an event is received for the same git revision multiple times. This works well for an optimization however it prevents the use of many git hooks. Releated tickets: JENKINS-57860 JENKINS-57014 Add Comment
[JIRA] (JENKINS-57866) ShellStepTest.abort flake on Windows
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-57866
ShellStepTest.abort flake on Windows
Change By:
Jesse Glick
On CI I see a lot of flakes on Windows:{code:none}java.lang.AssertionError: org.jenkinsci.plugins.workflow.steps.durable_task.ShellStepTest$1@52070d1b ... at org.jenkinsci.plugins.workflow.steps.durable_task.ShellStepTest.ensureForWhile(ShellStepTest.java:682) ... at org.jenkinsci.plugins.workflow.steps.durable_task.ShellStepTest.abort(ShellStepTest.java:192){code}The test is not written terribly well, but basically this means that the batch script running {{ping}} every second in a loop was sent a termination signal yet continued running for at least five seconds after the interrupt. Did the signal get lost? Sent to the wrong subprocess without breaking the loop? Was it going to get handled but the system was just too heavily loaded? Could probably improve test to:* Use a single process for the batch script, like {{ping -n 9 127.0.0.1 >tmp}}.* Wait indefinitely (up to global test timeout) for the file to _not_ have been touched in the last few seconds.
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+unsub
[JIRA] (JENKINS-57866) ShellStepTest.abort flake on Windows
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-57866 ShellStepTest.abort flake on Windows Issue Type: Bug Assignee: Unassigned Components: workflow-durable-task-step-plugin Created: 2019-06-05 17:19 Labels: flake Priority: Minor Reporter: Jesse Glick On CI I see a lot of flakes on Windows: java.lang.AssertionError: org.jenkinsci.plugins.workflow.steps.durable_task.ShellStepTest$1@52070d1b ... at org.jenkinsci.plugins.workflow.steps.durable_task.ShellStepTest.ensureForWhile(ShellStepTest.java:682) ... at org.jenkinsci.plugins.workflow.steps.durable_task.ShellStepTest.abort(ShellStepTest.java:192) The test is not written terribly well, but basically this means that the batch script running ping every second in a loop was sent a termination signal yet continued running for at least five seconds after the interrupt. Did the signal get lost? Sent to the wrong subprocess without breaking the loop? Was it going to get handled but the system was just too heavily loaded? Could probably improve test to: Use a single process for the batch script, like ping -n 9 127.0.0.1 >tmp. Wait indefinitely (up to global test timeout) for the file to not have been touched in the last few seconds.
[JIRA] (JENKINS-57862) A wrong configuration of CasC yaml kill Jenkins startup
Title: Message Title Ramon Leon commented on JENKINS-57862 Re: A wrong configuration of CasC yaml kill Jenkins startup https://github.com/jenkinsci/configuration-as-code-plugin/issues/912 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199824.1559748979000.22094.1559753820195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57863) CasC ciphers values already ciphered when running under test
Title: Message Title Ramon Leon commented on JENKINS-57863 Re: CasC ciphers values already ciphered when running under test https://github.com/jenkinsci/configuration-as-code-plugin/issues/913 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199825.1559751383000.22091.1559753760144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57865) Enhance plugin installation manager by fixing installation script docker issues
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-57865 Enhance plugin installation manager by fixing installation script docker issues Issue Type: Task Assignee: Natasha Stopa Components: docker, plugin-installation-manager-tool Created: 2019-06-05 16:51 Labels: gsoc-2019 plugin-manager docker Priority: Minor Reporter: Natasha Stopa Open Docker issues (https://github.com/jenkinsci/docker/issues) related to the plugin installation bash script can be reviewed to find what additional functionality can be added the the plugin installation manager tool to fix those issues. Add Comment
[JIRA] (JENKINS-57864) Test Converted Docker Plugin Bash Script
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-57864 Test Converted Docker Plugin Bash Script Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-06-05 16:45 Labels: gsoc-2019 plugin-manager Priority: Minor Reporter: Natasha Stopa Set up and run tests on plugin installation manager. Add Comment
[JIRA] (JENKINS-56909) Allow to unlock/lock keychain on demand
Title: Message Title Mathieu Delrocq updated JENKINS-56909 After tests, the functionnality is working correctly. Jenkins / JENKINS-56909 Allow to unlock/lock keychain on demand Change By: Mathieu Delrocq Status: In Review Resolved Resolution: Done Released As: xcode-plugin-2.0.12 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198582.155446542.22087.1559752740247%40Atlassian.JIRA. For more options, vis
[JIRA] (JENKINS-56909) Allow to unlock/lock keychain on demand
Title: Message Title Mathieu Delrocq updated JENKINS-56909 Jenkins / JENKINS-56909 Allow to unlock/lock keychain on demand Change By: Mathieu Delrocq Status: In Review Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198582.155446542.22083.1559752500408%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56909) Allow to unlock/lock keychain on demand
Title: Message Title Mathieu Delrocq updated JENKINS-56909 Jenkins / JENKINS-56909 Allow to unlock/lock keychain on demand Change By: Mathieu Delrocq Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198582.155446542.22085.1559752500441%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57836) Customize metadata information for only some jobs
Title: Message Title Ted updated JENKINS-57836 Jenkins / JENKINS-57836 Customize metadata information for only some jobs Change By: Ted Status: Open Fixed but Unreleased Resolution: Not A Defect 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199794.1559644291000.22081.1559751600245%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57836) Customize metadata information for only some jobs
Title: Message Title Ted commented on JENKINS-57836 Re: Customize metadata information for only some jobs https://wiki.jenkins.io/display/JENKINS/Splunk+Plugin+for+Jenkins please check section 3: Customize The Job Data Sent to Splunk Jenkins->Configure System->Splunk for Jenkins Configuration->Advanced ->Customize Event Processing Command There is an example in FAQ about collect info of upstream/downstream, I think you can reference that one for usage 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199794.1559644291000.22079.1559751600219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57863) CasC ciphers values already ciphered when running under test
Title: Message Title
Ramon Leon created an issue
Jenkins / JENKINS-57863
CasC ciphers values already ciphered when running under test
Issue Type:
Bug
Assignee:
Ewelina Wilkosz
Attachments:
GlobalCredentialsCiphered.yml
Components:
configuration-as-code-plugin
Created:
2019-06-05 16:16
Environment:
Jenkins 2.73.3, 2.164.1, 2.165 JCasC 1.19, 1.20-snapshot Credentials 2.19, 2.20
Labels:
jcasc-compatibility
Priority:
Major
Reporter:
Ramon Leon
Jenkins 2.73.3, 2.164.1, 2.165 when running " under test ", let's say `mvn hpi:run` or `mvn test`, ciphers the tokens even though they are ciphered in the YAML, whereas the same Jenkins running normally doesn't cipher the tokens if they are already ciphered. When configuring with the attached yml: If Jenkins is running normally (java -jar ...), in the viewExport page (View Configuration button) it shows: _ {AQAAABAQ93qR7ipIm+dYmOZ1AXqSLWDj9V+KUrHew/fiyPNoHTo=} _ The same as in the file. But when running under test, with mvn hpi:run or running integration tests (mvn package) it shows: usernamePassword: _ {AQAAABBA1e/z7rT6SsbMm5XmaDkHn0N8YeoHYRm8JltNZh68IZumi/SmbDrI+nH8Z51YNwSokbUbxkq85QMMe5CkEDLL+YNkXGcnAMwvSgTLLH71dlc=} _ basicSSHUserPrivateKey: _ {AQAAABBAb5Y+gVJlthgpEfLXRvFmnYtPqeTnxFDzNaKpRPDhpbWw70t7h4W1jI9h5u7TEafPxk6AhWmq+BoWkzAQtKLvzYFLCUwE2xNusw5nXeKVklY=} _ Even though both secrets are the same in
[JIRA] (JENKINS-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title
Jesse Glick commented on JENKINS-53315
Re: Timeout step should support a closure to execute prior to killing body
In the case of JUnit, you would probably want to write a simple TestRule (if one does not already exist) which is responsible for launching the external process, sending it SIGQUIT if the test fails, and finally sending in SIGTERM in all cases.
To your original proposal, if you really have to do this inside Pipeline script for some reason, try something like
timeout(time: 1, unit: 'HOURS') {
def ok = false
try {
sh 'java IntermittentlySlowProcess'
ok = true
} finally {
if (!ok) {
sh 'killall -3 java'
}
}
}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193394.1535544071000.22071.1559750940480%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57800) Convert Docker Plugin Bash Script to Java
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-57800 Convert Docker Plugin Bash Script to Java Change By: Natasha Stopa Component/s: plugin-installation-manager-tool Component/s: core 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199751.1559326912000.22066.1559749440275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57862) A wrong configuration of CasC yaml kill Jenkins startup
Title: Message Title Oleg Nenashev commented on JENKINS-57862 Re: A wrong configuration of CasC yaml kill Jenkins startup Ramon Leon for this plugin it is better to duplicate the issue in https://github.com/jenkinsci/configuration-as-code-plugin/issues 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199824.1559748979000.22061.1559749260182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57849) Move Plugin Management Repo to Jenkins
Title: Message Title Natasha Stopa commented on JENKINS-57849 Re: Move Plugin Management Repo to Jenkins https://github.com/jenkinsci/plugin-installation-manager-tool has been created. The next steps are to update the artifact id, move the code, and delete the original repo. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199807.1559678689000.22062.1559749260195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57849) Move Plugin Management Repo to Jenkins
Title: Message Title Natasha Stopa started work on JENKINS-57849 Change By: Natasha Stopa Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199807.1559678689000.22058.1559749140163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57862) A wrong configuration of CasC yaml kill Jenkins startup
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-57862 A wrong configuration of CasC yaml kill Jenkins startup Issue Type: Bug Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin Created: 2019-06-05 15:36 Labels: configuration-as-code jcasc-compatibility Priority: Major Reporter: Ramon Leon While testing the CasC plugin I've found that if the yaml is wrong, Jenkins stop restarting, leaving you with an unoperational instance. Steps to reproduce: Create a yaml with ssh credentials Import this yaml Remove credentials and ssh-credentials Restart Jenkins Expected: Some settings are established, others not. Current behavior: Jenkins doesn't start. Jun 05, 2019 5:27:03 PM jenkins.InitReactorRunner$1 onTaskFailedJun 05, 2019 5:27:03 PM jenkins.InitReactorRunner$1 onTaskFailedSEVERE: Failed ConfigurationAsCode.initjava.lang.Error: java.lang.reflect.InvocationT
[JIRA] (JENKINS-48248) pidFile switch should prevent launching of multiple copies
Title: Message Title Basil Crow updated JENKINS-48248 Thanks for the PR! This was merged in #114 and will be released in 3.18. Jenkins / JENKINS-48248 pidFile switch should prevent launching of multiple copies Change By: Basil Crow Status: Open Fixed but Unreleased Resolution: Fixed Released As: 3.18 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186829.1511808585000.22053.1559748420334%40Atlassian.JIRA.
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Checkmarx Administrator commented on JENKINS-57796 Re: Checkmarx affected by JEP-200 Hi, my name is Liran and I'm the CI Plugins product manager. Thank you for these comments. I'm sorry to hear you are experiencing these issues. We are looking into this problem. I'd appreciate if next time you contact Checkmarx official support for a faster response. Thank you! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199746.1559317468000.22022.1559747640761%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57171) Permissive script security plugin is broken after updating to script security 1.58
Title: Message Title X O commented on JENKINS-57171 Re: Permissive script security plugin is broken after updating to script security 1.58 Hi, yes 0.5 fixes this issue but it generates another one: instead seeing the Pipeline script from SCM (SCM/Git) for the pipeline definition in the configure page according to what is written the config.xml of a pipeline job, we see pipeline script with an empty script. It's impossible to view it in the GUI. Interestingly, the correct configuration is used. Reverting to 0.3 fix this behavior but of course lead to the current issue. BTW, the current issue seems only cosmetic, isn't it? There is no real need for an admin to enable the use of the "unsecured" methods. At least my pipelines do what they are suppose to do?! We have a lot of plugins but here are some details of what is used: Jenkins: 2.179 Script Security 1.60 Permissive Script Security 0.3 or 0.5 Pipeline Groovy 2.70 Git 3.10.0 Thanks 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198922.1556125514000.22007.1559747221363%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57861) Make(Manual Condition) work incorporating all the required dependencies.
Title: Message Title Prastik Gyawali updated an issue Jenkins / JENKINS-57861 Make(Manual Condition) work incorporating all the required dependencies. Change By: Prastik Gyawali Like the Self-Promotion Condition, make the manual condition compatible taking into consideration of all the backward compatibility conditions.+_*Expected Flow for the Implementation:*_+ * Since it is a parameterized build, PromotionProcess checks for its occurence, so make a new PromotionProcess Interface for this and carry out the same refactoring done for the Self-Promotion Condition. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199823.1559746182000.22003.1559746440113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57861) Make(Manual Condition) work incorporating all the required dependencies.
Title: Message Title Prastik Gyawali started work on JENKINS-57861 Change By: Prastik Gyawali Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199823.1559746182000.22004.1559746440161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Ramachandra Kamath Arbettu updated an issue Jenkins / JENKINS-57796 Checkmarx affected by JEP-200 Change By: Ramachandra Kamath Arbettu Priority: Major Critical 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199746.1559317468000.22001.1559746200386%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57861) Make(Manual Condition) work incorporating all the required dependencies.
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57861 Make(Manual Condition) work incorporating all the required dependencies. Issue Type: Task Assignee: Prastik Gyawali Components: promoted-builds-plugin Created: 2019-06-05 14:49 Labels: gsoc-2019 gsoc2019-artifact-promotion-in-pipeline Priority: Minor Reporter: Prastik Gyawali 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 rece
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Ramachandra Kamath Arbettu commented on JENKINS-57796 Re: Checkmarx affected by JEP-200 I confirm this issue from the version 8.9.0 of the plugin. We are encountering the same after updating from 8.80.0. We are running on Jenkins ver. 2.164.3 Failed to deserialize response to UserRequest:com.checkmarx.jenkins.CxScanCallable@557f1a37: java.lang.SecurityException: Rejected: com.cx.restclient.dto.ScanResults; see https://jenkins.io/redirect/class-filter/ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199746.1559317468000.21998.1559746140519%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53315) Timeout step should support a closure to execute prior to killing body
Title: Message Title Alexander Komarov commented on JENKINS-53315 Re: Timeout step should support a closure to execute prior to killing body Sadly that's not all I'm after. In the case of complex integration tests, the tests may be hanging due to a hung external process (ie a server) started as part of the test. That is the process I need the stacktrace for, not the test. Otherwise, Timeout rule would work great. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193394.1535544071000.21988.1559745660116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57860) Optionally allow for idempotent handling of SCMEvents
Title: Message Title Phil Madden created an issue Jenkins / JENKINS-57860 Optionally allow for idempotent handling of SCMEvents Issue Type: Improvement Assignee: Phil Madden Components: branch-api-plugin Created: 2019-06-05 14:38 Priority: Minor Reporter: Phil Madden Related to: https://issues.jenkins-ci.org/browse/JENKINS-57014 GitHub Conversation: https://github.com/jenkinsci/github-branch-source-plugin/pull/216 When GitHub publishes an event for a Deployment, the revision in the event payload is the same as the revision in the push event payload. Thus, the below line of code will not execute a pipeline upon receiving the deployment webhook. We would like the ability to optionally toggle on/off handling SCMEvents in an idempotent manner. https://github.com/jenkinsci/branch-api-plugin/blob/master/src/main/java/jenkins/branch/MultiBranchProject.java#L1546 Add Comment
[JIRA] (JENKINS-57849) Move Plugin Management Repo to Jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-57849 Re: Move Plugin Management Repo to Jenkins Covered by HOSTING-777 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199807.1559678689000.21984.1559745420183%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Title: Message Title Paul Allen assigned an issue to Kevin Williamson Jenkins / JENKINS-52679 p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs Change By: Paul Allen Assignee: Paul Allen Kevin Williamson 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192561.1532115007000.21980.1559745060196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Title: Message Title Paul Allen updated JENKINS-52679 Ready for release. Jenkins / JENKINS-52679 p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs Change By: Paul Allen Status: In Progress Fixed but Unreleased Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192561.1532115007000.21975.1559745000415%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57703) Add docker.image.inside and docker.image.withRun reference
Title: Message Title Janosch Deurer commented on JENKINS-57703 Re: Add docker.image.inside and docker.image.withRun reference For anybody who also struggles finding this, it can be found in your own jenkins server as described here: https://go.cloudbees.com/docs/plugins/docker-workflow/ However a link in the official documentation would still be most helpful. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199642.1558970297000.21973.1559745000370%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Marco Andries commented on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Devin Nusbaum, it seems to solve the issue with the empty console outputs. No idea why we first only had it when an error was thrown. But now with the plugins completely updated, the console output is there for failed, successful and aborted jobs when "Compress Build Logs" is turned off. Thanks! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.21972.1559744280300%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55736) Support proxy logins
Title: Message Title Jonathan Whitby commented on JENKINS-55736 Re: Support proxy logins I'll take a look, thank you Fernando Boaglio! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196932.1548180395000.21952.1559743440121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57826) catchError(buildResult: hudson.model.Result.SUCCESS, stageResult: hudson.model.Result.FAILURE) doesn't set stage to FAILURE
Title: Message Title Andrew Bayer commented on JENKINS-57826 Re: catchError(buildResult: hudson.model.Result.SUCCESS, stageResult: hudson.model.Result.FAILURE) doesn't set stage to FAILURE PR up! https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/330 - this should do the trick. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199781.1559585434000.21949.1559743380110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57826) catchError(buildResult: hudson.model.Result.SUCCESS, stageResult: hudson.model.Result.FAILURE) doesn't set stage to FAILURE
Title: Message Title Andrew Bayer updated JENKINS-57826 Jenkins / JENKINS-57826 catchError(buildResult: hudson.model.Result.SUCCESS, stageResult: hudson.model.Result.FAILURE) doesn't set stage to FAILURE Change By: Andrew Bayer Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199781.1559585434000.21946.1559743320842%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57826) catchError(buildResult: hudson.model.Result.SUCCESS, stageResult: hudson.model.Result.FAILURE) doesn't set stage to FAILURE
Title: Message Title Andrew Bayer started work on JENKINS-57826 Change By: Andrew Bayer Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199781.1559585434000.21943.1559743260562%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57826) catchError(buildResult: hudson.model.Result.SUCCESS, stageResult: hudson.model.Result.FAILURE) doesn't set stage to FAILURE
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-57826 catchError(buildResult: hudson.model.Result.SUCCESS, stageResult: hudson.model.Result.FAILURE) doesn't set stage to FAILURE Change By: Andrew Bayer Assignee: Andrew Bayer 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199781.1559585434000.21941.1559743260530%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57859) Creating new pipeline from Bitbucket cloud hangs fetching repos
Title: Message Title Matt Russell created an issue Jenkins / JENKINS-57859 Creating new pipeline from Bitbucket cloud hangs fetching repos Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-06-05 13:48 Environment: Jenkins 2.164.3 io.jenkins.blueocean:blueocean-bitbucket-pipeline:1.16.0 Priority: Major Reporter: Matt Russell Having a problem configuring our Jenkins to connect to Bitbucket Cloud: 1. Attempt to create a pipeline in Blue Ocean (https://$JENKINS/blue/create-pipeline) 2. Select Bitbucket Cloud, and provide credentials 3. Answer question "Which team does the repository belong to?" Expected behaviour: repositories from team are returned Actual behaviour: UI hangs indefinitely saying "Loading..." In the logs, the following exception is recorded: WARNING: Failed to get "repositories" from a io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer java.lang.reflect.InvocationTargetException ... Caused by: io.jenkins.blueocean.commons.ServiceException: Unknown Status Code at io.jenkins.blueocean.blueocean_bitbucket_pipeline.HttpResponse.getContent(HttpResponse.java:71) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.cloud.BitbucketCloudApi.getRepos(BitbucketCloudApi.java:161) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer$BitbucketRepositories.(BitbucketRepositoryContainer.java:80) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer.getRepositories(BitbucketRepositoryContainer.java:41) at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValu
[JIRA] (JENKINS-57751) Unable to delete server configuration
Title: Message Title Parichay Barpanda started work on JENKINS-57751 Change By: Parichay Barpanda Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199696.1559161096000.21908.1559742481142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57760) Add support for webhooks management
Title: Message Title Parichay Barpanda stopped work on JENKINS-57760 Change By: Parichay Barpanda Status: In Progress Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199706.1559207961000.21916.1559742481402%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Jae Gangemi started work on JENKINS-52669 Change By: Jae Gangemi Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192545.1532070393000.21918.1559742481431%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Jae Gangemi resolved as Fixed Jenkins / JENKINS-52669 IndexOutOfBoundsException after upgrade to 1.2.3 Change By: Jae Gangemi Status: In Progress Resolved Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192545.1532070393000.21930.1559742481629%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Jae Gangemi commented on JENKINS-52669 Re: IndexOutOfBoundsException after upgrade to 1.2.3 fixed in 1.2.6 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192545.1532070393000.21910.1559742481198%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Jae Gangemi assigned an issue to Jae Gangemi Jenkins / JENKINS-52669 IndexOutOfBoundsException after upgrade to 1.2.3 Change By: Jae Gangemi Assignee: Jae Gangemi 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192545.1532070393000.21932.1559742481655%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Title: Message Title Paul Allen started work on JENKINS-52679 Change By: Paul Allen Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192561.1532115007000.21906.1559741640228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47279) Full-duplex HTTP(S) transport with plain CLI protocol does not work with Apache reverse proxy in Jenkins >= 2.54
Title: Message Title Devin Nusbaum commented on JENKINS-47279 Re: Full-duplex HTTP(S) transport with plain CLI protocol does not work with Apache reverse proxy in Jenkins >= 2.54 Craig Ringer Yes, in Nginx you must use proxy_request_buffering off; and sometimes proxy_buffering off;, but Apache does not have any such feature as far as I can tell. Changes to mod_proxy could probably fix the issue, but I think you would end up having to provide a way to stop buffering requests/responses completely, because IIRC the plain CLI protocol sends only a single byte before waiting for a response in some cases. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185699.1507146144000.21904.1559741341142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54296) Docker cannot be used right after agent provisioning without sudo
Title: Message Title Baptiste Mathus stopped work on JENKINS-54296 Change By: Baptiste Mathus Status: In Progress Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194944.1540760532000.21889.1559741220236%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54296) Docker cannot be used right after agent provisioning without sudo
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-54296 Docker cannot be used right after agent provisioning without sudo Change By: Baptiste Mathus Assignee: Baptiste Mathus 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194944.1540760532000.21888.1559741220225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Marco Andries commented on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Devin Nusbaum, thanks for the reply. I will have a look. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.21886.1559740740975%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-55024
Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Ok, looks like a duplicated duplicate of JENKINS-54678. Compressed build logs are not supported by new versions of workflow-job. If your pipelines use {{compressBuildLog}}, you should remove that from their Jenkinsfile for now. If the Compress Build Logs plugin has some global option that causes all build logs to be compressed, then you'll have to turn that off 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.21874.1559740560721%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Devin Nusbaum closed an issue as Duplicate Jenkins / JENKINS-55024 Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Change By: Devin Nusbaum Status: Open Closed Resolution: Duplicate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.21876.1559740560809%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Devin Nusbaum commented on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Ok, looks like a duplicated of JENKINS-54678. Compressed build logs are not supported by new versions of workflow-job. If your pipelines use compressBuildLog, you should remove that from their Jenkinsfile for 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.21864.1559740500185%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Marco Andries commented on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Due to circumstances we needed to update the plugin and now we are experiencing that the console output is empty when the job is completed not only for failed jobs but also for aborted and successful jobs. I think to have found the issue we're experiencing. I saw the following when I look at the logs of a stage: When I check that location, I find the following: + ls -l /var/lib/jenkins/jobs/iText_7_Java/jobs/itextcore/branches/feature-QA-1892-3.0d3g52/builds/3 total 288 drwxr-xr-x 3 jenkins jenkins 16 Jun 5 14:42 archive rw-rr- 1 jenkins jenkins 54829 Jun 5 14:43 build.xml rw-rr- 1 jenkins jenkins 0 Jun 5 14:42 changelog0.xml rw-rr- 1 jenkins jenkins 39174 Jun 5 14:43 log.gz rw-rr- 1 jenkins jenkins 329 Jun 5 14:43 log-index rw-rr- 1 jenkins jenkins 58 Jun 5 14:43 open-tasks-fixed.xml rw-rr- 1 jenkins jenkins 171277 Jun 5 14:43 open-tasks.xml drwxr-xr-x 2 jenkins jenkins 8192 Jun 5 14:43 workflow drwxr-xr-x 2 jenkins jenkins 4096 Jun 5 14:42 workspace-files The log file is indeed not there but there's a log.gz file. I extracted the file running the following command: gzip -d /var/lib/jenkins/jobs/iText_7_Java/jobs/itextcore/branches/feature-QA-1892-3.0d3g52/builds/3/log.gz And now the console output is no longer empty and the stage log is also correct: So it seems there's an issue with packing and unpacking the log. Hope this helps 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.21862.1559740260325%40Atlassian.JIRA. For more options, visit https://groups.google.com/d
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Marco Andries updated an issue Jenkins / JENKINS-55024 Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Change By: Marco Andries Attachment: image-2019-06-05-15-09-19-247.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.21856.1559740201961%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Marco Andries updated an issue Jenkins / JENKINS-55024 Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Change By: Marco Andries Attachment: image-2019-06-05-14-56-21-611.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.21850.1559739420495%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Marco Andries updated an issue Jenkins / JENKINS-55024 Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Change By: Marco Andries Attachment: image-2019-06-05-14-55-49-292.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.21844.1559739360267%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57215) Plugin starts a worked and might immediately stop it, because of cached EC2Computer.getUptime()
Title: Message Title Daniel Atallah commented on JENKINS-57215 Re: Plugin starts a worked and might immediately stop it, because of cached EC2Computer.getUptime() I also discovered this same issue and created https://github.com/jenkinsci/ec2-plugin/pull/359 to fix it. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198972.1556526924000.21838.1559739300115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
