[JIRA] (JENKINS-54932) SSC - Octane integration - inject SSC vulnerabilities to Octane is no working correctly
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-54932 SSC - Octane integration - inject SSC vulnerabilities to Octane is no working correctly Issue Type: Bug Assignee: Daniel Shmaya Components: hp-application-automation-tools-plugin Created: 2018-11-29 07:33 Priority: Critical Reporter: Radi Berkovich the list of open vulnerabilities that the plugin gets from Octane which uses the plugin to calculate issues to close - return always empty – as a result , calculation of closed vulnerabilities never happens. The plugin returns only new vulnerabilities – as a result , updated vulnerabilities are not injected and not get updated in Octane. Add Comment
[JIRA] (JENKINS-54904) "(hide)" and "(show)" links in console view of pipelines don't work
Title: Message Title Reinhold Füreder commented on JENKINS-54904 Re: "(hide)" and "(show)" links in console view of pipelines don't work Sorry for my incomplete report and congrats to your great intuition: Firefox 63.0.3 Browser console shows this error: TypeError: ss.rules is undefined[Weitere Informationen] 5 script.js:37:25 showHide https://jenkins.acme.com/static/cf22a270/descriptor/org.jenkinsci.plugins.workflow.job.console.NewNodeConsoleNote/script.js:37:25 showHidePipelineSection https://jenkins.acme.com/static/cf22a270/descriptor/org.jenkinsci.plugins.workflow.job.console.NewNodeConsoleNote/script.js:45:5 onclick https://jenkins.acme.com/job/Sandbox/job/acme.stage/95/console:1: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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54932) SSC - Octane integration - inject SSC vulnerabilities to Octane is not working correctly
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-54932 SSC - Octane integration - inject SSC vulnerabilities to Octane is not working correctly Change By: Radi Berkovich Summary: SSC - Octane integration - inject SSC vulnerabilities to Octane is no not working correctly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54221) Add an example of a certificate authentication with service-principal to documentation
Title: Message Title Jie Shen updated JENKINS-54221 Jenkins / JENKINS-54221 Add an example of a certificate authentication with service-principal to documentation Change By: Jie Shen 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54115) Remote Invocation of Jenkins API when using Azure AD Plugin
Title: Message Title Jie Shen started work on JENKINS-54115 Change By: Jie Shen 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54931) Support rundeck 3.0
Title: Message Title Jason You created an issue Jenkins / JENKINS-54931 Support rundeck 3.0 Issue Type: Improvement Assignee: Vincent Behar Attachments: image-2018-11-29-14-27-05-397.png Components: rundeck-plugin Created: 2018-11-29 06:27 Priority: Critical Reporter: Jason You Since rundeck 3.0 change the api endpoint. The "Rundeck Execution Result" can not work. Add Comment
[JIRA] (JENKINS-54776) Node stays suspended after node is started
Title: Message Title Jie Shen started work on JENKINS-54776 Change By: Jie Shen 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54894) Server becomes compute bound and unresponsive to http requests after org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0
Title: Message Title Björn Pedersen commented on JENKINS-54894 Re: Server becomes compute bound and unresponsive to http requests after org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0 From the error message this looks the root cause here is a ldap missconfiguration ( looping ldap referrals). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38101) Credentials are not working with newest Sonarqube version
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-38101 Re: Credentials are not working with newest Sonarqube version If there is any way to retrieve the sonar version (headers or an API endpoint that do no require login) maybe this could be a simple conditional. In anycase, there is a solution in pipeline with [waitForQualityGate|https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Jenkins#AnalyzingwithSonarQubeScannerforJenkins-Pausepipelineuntilqualitygateiscomputed]. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Reinhold Füreder commented on JENKINS-49997 Re: Pipeline Declarative post unsuccessful block Thanks Jose Blas Camacho Taboada and Andrew Bayer: this was very quick! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38101) Credentials are not working with newest Sonarqube version
Title: Message Title Allan BURDAJEWICZ edited a comment on JENKINS-38101 Re: Credentials are not working with newest Sonarqube version If there is any way to retrieve the sonar version (headers or an API endpoint that do no require login) maybe this could be a simple conditional. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38101) Credentials are not working with newest Sonarqube version
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-38101 Re: Credentials are not working with newest Sonarqube version If there is any way to retrieve the sonar version (headers or an API that do no require login) maybe this could be a simple conditional. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54448) Azure VM Agent does not work with Custom Managed Image with Unmanaged disk
Title: Message Title Jie Shen started work on JENKINS-54448 Change By: Jie Shen 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54930) withEnv should accept Map as well as List
Title: Message Title
Craig Ringer updated an issue
Jenkins / JENKINS-54930
withEnv should accept Map as well as List
Change By:
Craig Ringer
The {{withEnv}} step should accept a {{ java.util.{{Map}} }} , which is the natural form of an environment variable list. It expects a {{java.util.List}}, and dies with{code:java}java.lang.UnsupportedOperationException: must specify $class with an implementation of interface java.util.List at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:503) ...Caused: java.lang.IllegalArgumentException: Could not instantiate {overrides={}} for EnvStep(overrides: String[]) ...{code}if a {{Map}} is passed.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54930) withEnv should accept Map as well as List
Title: Message Title
Craig Ringer updated an issue
Jenkins / JENKINS-54930
withEnv should accept Map as well as List
Change By:
Craig Ringer
The ` {{ withEnv ` }} step should accept a java.util.{{ Map }} , which is the natural form of an environment variable list. It expects a ` {{ java.util.List ` }} , and dies with {code :java }java.lang.UnsupportedOperationException: must specify $class with an implementation of interface java.util.List at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:503) ...Caused: java.lang.IllegalArgumentException: Could not instantiate {overrides={}} for EnvStep(overrides: String[]) ...{code} if a {{ Map }} is passed.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54930) withEnv should accept Map as well as List
Title: Message Title
Craig Ringer created an issue
Jenkins / JENKINS-54930
withEnv should accept Map as well as List
Issue Type:
New Feature
Assignee:
Unassigned
Components:
workflow-basic-steps-plugin
Created:
2018-11-29 05:43
Priority:
Minor
Reporter:
Craig Ringer
The `withEnv` step should accept a Map, which is the natural form of an environment variable list. It expects a `java.util.List`, and dies with
java.lang.UnsupportedOperationException: must specify $class with an implementation of interface java.util.List
at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:503)
...
Caused: java.lang.IllegalArgumentException: Could not instantiate {overrides={}} for EnvStep(overrides: String[])
...
if a Map is passed.
Add Comment
[JIRA] (JENKINS-53481) Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1 and hudson.maven.reporters.MavenArtifactArchiver$2
Title: Message Title Olivier Lamy updated JENKINS-53481 Jenkins / JENKINS-53481 Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1 and hudson.maven.reporters.MavenArtifactArchiver$2 Change By: Olivier Lamy 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53481) Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1 and hudson.maven.reporters.MavenArtifactArchiver$2
Title: Message Title Olivier Lamy started work on JENKINS-53481 Change By: Olivier Lamy 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53481) Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1 and hudson.maven.reporters.MavenArtifactArchiver$2
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-53481 Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenFingerprinter$1 and hudson.maven.reporters.MavenArtifactArchiver$2 Change By: Olivier Lamy Assignee: Josh Soref Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54904) "(hide)" and "(show)" links in console view of pipelines don't work
Title: Message Title Jesse Glick commented on JENKINS-54904 Re: "(hide)" and "(show)" links in console view of pipelines don't work Working for me last I checked. Perhaps certain scripts do not work this way, or perhaps it does not work on certain browsers, or perhaps there are some errors in your browser console. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54904) "(hide)" and "(show)" links in console view of pipelines don't work
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-54904 "(hide)" and "(show)" links in console view of pipelines don't work Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Title: Message Title Jesse Glick commented on JENKINS-26313 Re: Workflow script fails if CPS-transformed methods are called from constructors Is there any way of putting a nice error message in the jenkins log? JENKINS-31314 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title
Jesse Glick commented on JENKINS-54654
Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths
Actually that warning was really intended for the broken old default ${ITEM_ROOTDIR}/workspace. Customized roots ending in …/${ITEM_FULLNAME} (or …/${ITEM_FULL_NAME}) should be supportable with the new managed layout. Again note that this only pertains to master-based builds; using agents is recommended.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Jesse Glick commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs workflow-step-api PR 38 is a sketch of what this kind of utility could look like. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52481) Stop infinite log when Kafka producer/consumer failed to connect
Title: Message Title Ming Xu commented on JENKINS-52481 Re: Stop infinite log when Kafka producer/consumer failed to connect I think it's not about wrong URL, you can reproduce it by shutting down kafka server(or zookeeper). Then both master and agent will print tons of log about trying to reconnect. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54287) Review student GSoC page for specific content
Title: Message Title Martin d'Anjou commented on JENKINS-54287 Re: Review student GSoC page for specific content The latest pushes on the aforementionned pull-request add the missing elements listed in the comment above. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title
Thorsten Langer commented on JENKINS-54515
Re: master triggers own branches
I can confirm this.
identical repos in 'master' and any branch.
identical pom.xml files in master and usually all branches. (at least in regard to all poms' own project/group|artifactId|version in top level and modules).
identical Jenkinsfile (see below)
but: different (git) branches. The distinction per {{when { buildingTag() } }} works quite fine
#!/usr/bin/env groovy
pipeline {
agent any
tools {
maven 'apache-maven-3.3.9'
jdk 'jdk1.8.0-latest'
}
options {
gitLabConnection('weblab.local')
gitlabBuilds(builds: ['Java-Build-And-Install'])
buildDiscarder logRotator(artifactDaysToKeepStr: '30',
artifactNumToKeepStr: '30',
daysToKeepStr: '30',
numToKeepStr: '30')
}
triggers {
gitlab(triggerOnPush: true,
triggerOnMergeRequest: true,
branchFilterType: 'All')
}
environment {
MAVEN_PROFILES = "-P continuousintegrationProfile -P slaSnapshotsProfile"
}
stages {
stage('Java-Build-And-Install') {
steps {
gitlabCommitStatus(name: 'Java-Build-And-Install') {
withMaven(
mavenLocalRepo: 'local-repo') {
sh "mvn clean install ${MAVEN_PROFILES}"
}
}
}
}
stage('Java-Deploy') {
when { anyOf {
branch "master"
buildingTag()
}}
steps {
gitlabBuilds(builds: ['Java-Deploy']) {
gitlabCommitStatus(name: 'Java-Deploy') {
withMaven(
mavenLocalRepo: 'local-repo') {
sh "mvn deploy -DskipTests=true ${MAVEN_PROFILES}"
}
}
}
}
}
}
post {
cleanup {
cleanWs()
}
}
}
Out current workaround is the following pre-install-stage: It gives the accidently-to-be-triggered artifacts in the branches branch-specific names, so they won't be triggered by builds in master.
stage('Java-Rename-Version') {
when { not { anyOf {
branch "master"
buildingTag()
}}}
steps {
gitlabBuilds(builds: ['Java-Rename-Version']) {
gitlabCommitStatus(name: 'Java-Rename-Version') {
withMaven(
[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-49337
Re: InterruptedException - Exception processing the logs
According to [~jglick], the InterruptedException is caused by the fact that withMaven collect build results in a {{ org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback.TailCall#finished() }} which is running in the CPS Thread which is NOT intended to have long tasks and which interrupts after probably 5 minutes.The fix would be to implement this logic in something similar to {{ org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution }} instead of a {{ org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback.TailCall#finished() }}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs According to Jesse Glick, the InterruptedException is caused by the fact that withMaven collect build results in a org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback.TailCall#finished() which is running in the CPS Thread which is NOT intended to have long tasks and which interrupts after probably 5 minutes. The fix would be to implement this logic in something similar to org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution instead of a org.jenkinsci.plugins.workflow.steps.BodyExecutionCallback.TailCall#finished() Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53131) "ALPN callback dropped" log line
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-53131 Re: "ALPN callback dropped" log line This message is logged by the okhttp library when an HTTP connection is made to an HTTP server that supports HTTP 2 but the platform on which okhttp is running on does not support ALPN. Jenkins currently supports JDK 8. ALPN has been added in JDK 9. So ALPN is not currently supported in Jenkins. Hence the warning. Some plugins - like for example GitHub API - uses okhttp library and GitHub supports HTTP2. So you might see these INFO messages. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title
Adam Delarosa updated an issue
Jenkins / JENKINS-54929
Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Change By:
Adam Delarosa
When using the Ansible Plugin with jenkins Pipeline , I can't see the entire log in on Jenkins PIpeline build output - Some output is missing at the end of the Ansible play.The output looks fine on a terminal - if I'll SSH to the server and run the ansible-playbook command from the command line. * This issue started about a month ago..Here is a screenshot of how the output look like now: [https://imgur.com/waX7XcM]Ansible Plugin: [https://jenkins.io/doc/pipeline/steps/ansible/]This is the Pipeline code that uses the Ansible Pipeline Plugin:{code:java}stage('running something') {steps {script {dir('my/path/here') { ansiblePlaybook([ inventory : 'hosts', playbook: 'main.yml', installation: 'ansible', sudoUser: null, colorized : true, extraVars : [ blah : "${params.blah}", some_var : "${params.some_var}" ] ])}}}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title
Adam Delarosa updated an issue
Jenkins / JENKINS-54929
Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Change By:
Adam Delarosa
When using the Ansible Plugin with jenkins Pipeline I can't see the entire log (I could see in the entire log terminal if I'll SSH to the server and run the command from the command line ) . This issue started about a month ago..Here is a screenshot of how the output look like now: [https://imgur.com/waX7XcM]Ansible Plugin: [https://jenkins.io/doc/pipeline/steps/ansible/]This is the Pipeline code that uses the Ansible Pipeline Plugin: {code:java}stage('running something') {steps {script {dir('my/path/here') { ansiblePlaybook([ inventory : 'hosts', playbook: 'main.yml', installation: 'ansible', sudoUser: null, colorized : true, extraVars : [ blah : "${params.blah}", some_var : "${params.some_var}" ] ])}}}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title
Adam Delarosa updated an issue
Jenkins / JENKINS-54929
Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Change By:
Adam Delarosa
When using the Ansible Plugin with jenkins PipelineI can't see the entire log (I could see the entire log if I'll SSH to the server and run the command from the command line).This issue started about a month ago..Here is a screenshot of how the output look like now:[https://imgur.com/waX7XcM]Ansible Plugin: [ https://jenkins.io/doc/pipeline/steps/ansible/ ]This is the Pipeline code that uses the Ansible Pipeline Plugin:{code:java}stage('running something') {steps {script {dir('my/path/here') { ansiblePlaybook([ inventory : 'hosts', playbook: 'main.yml', installation: 'ansible', sudoUser: null, colorized : true, extraVars : [ blah : "${params.blah}", some_var : "${params.some_var}" ] ])}}}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-51792) Incorrect Jenkinsfile with >1 steps section produces unclear error about `default` branch name
Title: Message Title Karl Shultz commented on JENKINS-51792 Re: Incorrect Jenkinsfile with >1 steps section produces unclear error about `default` branch name PR is up! And already approved, actually. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51792) Incorrect Jenkinsfile with >1 steps section produces unclear error about `default` branch name
Title: Message Title Karl Shultz updated JENKINS-51792 Jenkins / JENKINS-51792 Incorrect Jenkinsfile with >1 steps section produces unclear error about `default` branch name Change By: Karl Shultz 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Adam Delarosa created an issue Jenkins / JENKINS-54929 Some final output is missing in Jenkins Pipeline when using the Ansible Plugin Issue Type: Task Assignee: Jean-Christophe Sirot Attachments: waX7XcM.png Components: ansible-plugin, pipeline Created: 2018-11-28 22:28 Environment: Latest (11.29.18) Jenkins Version 2.153 (2018-11-25) Latest (11.29.18) Jenkins Ansible Pipeline plugin Version 1.0 (26 March 2018) Labels: jenkins pipeline ansible playbook ansible-plugin Priority: Major Reporter: Adam Delarosa When using the Ansible Plugin with jenkins Pipeline I can't see the entire log (I could see the entire log if I'll SSH to the server and run the command from the command line). This issue started about a month ago.. Here is a screenshot of how the output look like now: https://imgur.com/waX7XcM Ansible Plugin: https://jenkins.io/doc/pipeline/steps/ansible/
[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive
Title: Message Title Jeff Squyres commented on JENKINS-54187 Re: EC2 Plugin deadlock leaving Jenkins unresponsive +1 – we are hitting this issue, too. We had to disable all of the EC2 testing in the Open MPI project (github.com/open-mpi/ompi), which has unfortunately killed a good portion of our CI testing. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43561) PR build not being created when no master branch
Title: Message Title
aditya varma updated an issue
Jenkins / JENKINS-43561
PR build not being created when no master branch
Change By:
aditya varma
Our workflow when creating new projects is to create a master branch in github with 1 file in it.on a branch create an initial project including a Jenkinsfile when that build passes merge it to masterbut as of an update done in the last 2-3 days the pull request build isn't being created{code :java }Proposing repoLooking up org/repo Getting remote pull requests...Checking pull request #1(not from a trusted source)Job name: PR-1 ‘Jenkinsfile’ foundMet criteria 0 pull requests were processed (query completed){code} The user is a 'trusted' collaborator, I verified using the api the code uses. I think the change is related to: [ https://github.com/jenkinsci/github-branch-source-plugin/pull/128 ] I have downgraded the plugin 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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39377) Log js client side errors in support core
Title: Message Title Michael Neale commented on JENKINS-39377 Re: Log js client side errors in support core In case this comes up again: the best solution found so far is: 1) ask for HAR files (but be wary of the content) 2) integrate tools like rollbar, bugsnag etc to collect error stacktraces in aggregate if you have enough users to collect from. #1 is used typpically when a support bundle is used (as usually the error on its own is not enough, you need more context unless you can collect a LOT of errors a la #2) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54861) don't trigger initial build after branch detection
Title: Message Title Stephen Connolly assigned an issue to Unassigned Jenkins / JENKINS-54861 don't trigger initial build after branch detection Change By: Stephen Connolly Assignee: Stephen Connolly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54861) don't trigger initial build after branch detection
Title: Message Title Stephen Connolly commented on JENKINS-54861 Re: don't trigger initial build after branch detection You should be able to write your own branch build strategy in a custom extension 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39377) Log js client side errors in support core
Title: Message Title Owen Wood closed an issue as Won't Do Jenkins / JENKINS-39377 Log js client side errors in support core Change By: Owen Wood 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54536) Support T3 instance types
Title: Message Title Tony Kinsley commented on JENKINS-54536 Re: Support T3 instance types I just created a PR that adds support for the new A1 instance types (arm based). I based it on the PR for this one. https://github.com/jenkinsci/ec2-plugin/pull/325 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54928) SCM changes are not noticed and SCMpoll starts the build based on the cron.
Title: Message Title Ron Gebauer created an issue Jenkins / JENKINS-54928 SCM changes are not noticed and SCMpoll starts the build based on the cron. Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-11-28 20:28 Environment: Jenkins 2.138.3 auf CentOS 7 Labels: bitbucket-branch-source-plugin bitbucket Priority: Blocker Reporter: Ron Gebauer After updating to version 2.2.13/14/15 the pipelines don't recognize that a SCM change has already been built and try to rebuild it for every cron run. When I go back to version 2.2.12 the change is recognized immediately and the endless building has an end. For more information just let me know. Add Comment
[JIRA] (JENKINS-54747) In Multibranch pipeline job configuration shows and hangs
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-54747 In Multibranch pipeline job configuration shows and hangs Change By: Andrew Bayer Component/s: cloudbees-folder-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54904) "(hide)" and "(show)" links in console view of pipelines don't work
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-54904 "(hide)" and "(show)" links in console view of pipelines don't work Change By: Andrew Bayer Component/s: workflow-job-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54926) reactive parameters are no longer reacting
Title: Message Title marlene cote commented on JENKINS-54926 Re: reactive parameters are no longer reacting sorry to waste your time. you can close this. the problem was that jenkins reverted my config file somehow to an old one. the extensible choice parameter won't trigger the active choices reactive parameter. I made it an active choices parameter instead, and it is working again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54927) Job configuration Save/Apply buttons missing
Title: Message Title aditya varma created an issue Jenkins / JENKINS-54927 Job configuration Save/Apply buttons missing Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2018-11-28 at 11.45.42 AM.png Components: configure-job-column-plugin Created: 2018-11-28 19:46 Environment: I have upgraded my Jenkins version to 2.138.3 and suddenly I am not able to see the Save/Apply button in the job the configuration page. Priority: Blocker Reporter: aditya varma Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-54896) Can't get Jenkins to work with proxy under Windows
Title: Message Title Alfie Johnson commented on JENKINS-54896 Re: Can't get Jenkins to work with proxy under Windows So I don't know what I may have done, or maybe it was actually working all along, but it is working now. Let me document so others with similar problems may possibly find a solution. Most of the time any address put into the "Test URL" field would lead to the error mentioned in the main post. But I did realize that if I put https://www.github.com it would work. I have no idea why that URL works, while all others fail. So then I tried to install plugins, and got a different error. Some simple searching led to this post: https://stackoverflow.com/q/24563694 and the solution was right below that: https://stackoverflow.com/a/52468162 If you just want the solution: Go to the Manage Jenkins / Configure Global Security area and in the Plugin Manager section, check Use browser for metadata download then click Apply and after doing that, I can see all the possible plugins and have been able to install some so I guess Jenkins is actually getting through the proxy. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-47891) Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-47891 Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks Change By: Cyrille Le Clerc Summary: Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54926) reactive parameters are no longer reacting
Title: Message Title marlene cote updated an issue Jenkins / JENKINS-54926 reactive parameters are no longer reacting here is a picture of the results of changing the default branch field: the other fields should be set to release/v0.3, but nothing happens. Change By: marlene cote Attachment: image-2018-11-28-14-22-13-279.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54926) reactive parameters are no longer reacting
Title: Message Title marlene cote created an issue Jenkins / JENKINS-54926 reactive parameters are no longer reacting Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: image-2018-11-28-14-19-57-945.png Components: active-choices-plugin Created: 2018-11-28 19:21 Environment: Jenkins ver. 2.138.3 active choices plugin - 2.1 windows server Priority: Blocker Reporter: marlene cote my reactive parameters have stopped reacting. I believe it happend when I upgraded jenkins from 2.121.3 I have an extenisible choice parameter(defaultbranchname) that gives me a list of values. when I pick one of these values, a reactive parameter (branch for another repo) should be set to a value that matches the one picked in the extensible choice field. the groovy code is run when I initially execute Build with Parameters but it appears that the groovy code is not getting executed when I pick a different value for the default branch field. here is a picture of the initial page in jenkins:
[JIRA] (JENKINS-54922) Generated markdown should work in MacDown.app
Title: Message Title Owen Wood assigned an issue to Josh Soref Jenkins / JENKINS-54922 Generated markdown should work in MacDown.app Change By: Owen Wood Assignee: Emilio Escobar Josh Soref Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54680) Compressed build logs not rendering with update to workflow-job plugin >= 2.26
Title: Message Title Brant Niggemyer commented on JENKINS-54680 Re: Compressed build logs not rendering with update to workflow-job plugin >= 2.26 Experienced issue, we compress all build logs by default. Lost ability to view all logs. Downgraded Job Plugin to 2.25, and logs were again rendered in the console. Pretty significant regression for us. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54925) Define basic test cases to automate
Title: Message Title Isa Vilacides created an issue Jenkins / JENKINS-54925 Define basic test cases to automate Issue Type: Task Assignee: Oleg Nenashev Components: jenkinsfile-runner Created: 2018-11-28 18:36 Priority: Minor Reporter: Isa Vilacides Acceptance criteria There is a list of basic test cases/workflows as an input of the automation tasks Add Comment
[JIRA] (JENKINS-48106) java.io.EOFException continue occur when using health check with aws network load balancer
Title: Message Title Jeff Thompson commented on JENKINS-48106 Re: java.io.EOFException continue occur when using health check with aws network load balancer Looking at other reports, it's not clear that downgrading or ignoring this error is the correct thing to do in all environments. In some environments this message looks like it provides meaningful information. It sounds like Owen was correct initially, this is a duplicate of JENKINS-46893. Without further ideas I don't know what we could do here and sounds like there are some possibilities for addressing this in the system deployment configuration. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44042) jnlp slave ConnectionRefusalException None of the protocols were accepted
Title: Message Title Nirav Patel edited a comment on JENKINS-44042 Re: jnlp slave ConnectionRefusalException None of the protocols were accepted fyi, i saw this issue when my jenkins hosts' (my mac) IP changed. I updated kubernetes cloud config's jenkins host and tunnel host ip and that fixed it for me. It also happens if IPs are pointing to some other jenkins home host from which you haven't submitted original job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44042) jnlp slave ConnectionRefusalException None of the protocols were accepted
Title: Message Title Nirav Patel edited a comment on JENKINS-44042 Re: jnlp slave ConnectionRefusalException None of the protocols were accepted fyi, i saw this issue when my jenkins hosts' (my mac) IP changed. I updated kubernetes cloud config's jenkins host and tunnel host ip and that fixed it for me. It also happens if IPs are pointing to some other jenkins home from which you haven't submitted original job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44042) jnlp slave ConnectionRefusalException None of the protocols were accepted
Title: Message Title Nirav Patel commented on JENKINS-44042 Re: jnlp slave ConnectionRefusalException None of the protocols were accepted fyi, i saw this issue when my jenkins hosts' (my mac) IP changed. I updated kubernetes cloud config's jenkins host and tunnel host ip and that fixed it for me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54924) Script Runs In Script Console But Not Job DSL
Title: Message Title
Ben Moseley created an issue
Jenkins / JENKINS-54924
Script Runs In Script Console But Not Job DSL
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2018-11-28 17:51
Priority:
Minor
Reporter:
Ben Moseley
Related to JENKINS-28701 The following script executes just fine in script console, but the import throws an error in job console output. I looked at a ticket with an almost identical name, but I don't fully grasp how to solve the problem. I got the base script from another user and made some minor modifications to make it fit the intended purpose:
import hudson.plugins.shelveproject.ShelveProjectTaskdef daysBack=45;
Jenkins.instance.getAllItems(AbstractProject.class).each{ it->
def lastBuild=it.getLastBuild()
if(it.name.startsWith("BuildThor") || it.name.startsWith("IntTestThor")){
if(lastBuild != null){
def back = Calendar.getInstance()
back.set(Calendar.DAY_OF_YEAR,back.get(Calendar.DAY_OF_YEAR)-daysBack)
if (lastBuild.getTime().compareTo(back.getTime()) < 0) {
println it.name + " was built over " + daysBack + " days ago: " + lastBuild.getTime()
if (it instanceof AbstractProject){
println " *PROJECT SHELVED THIS ITERATION*"
def spt= new ShelveProjectTask(it)
Hudson.getInstance().getQueue().schedule(spt , 0 );
}
}
}
else{
println it.name + " was not shelved this iteration."
}
}
}
[JIRA] (JENKINS-54923) Spawning processes from build on windows server
Title: Message Title Sampath Kumar Kokkiripati updated an issue Jenkins / JENKINS-54923 Spawning processes from build on windows server Change By: Sampath Kumar Kokkiripati *I am currently experiencing this issue on Jenkins running on windows server* I'm currently using M.S. Build Script for build and deployment. It is killing my job in middle without executing the next build step and job is finishing with the following failure message. Process leaked file descriptors. See [https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors] for more information Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure [Office365connector] No webhooks to notify *Finished: FAILURE**[Jenkins ver. 2.143|https://jenkins.io/]* Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54923) Spawning processes from build on windows server
Title: Message Title Sampath Kumar Kokkiripati updated an issue Jenkins / JENKINS-54923 Spawning processes from build on windows server Change By: Sampath Kumar Kokkiripati * I am currently experiencing this issue on Jenkins running on windows server * It is killing my job in middle without executing the next build step and job is finishing with the failure message. Process leaked file descriptors. See [https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors] for more information Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure [Office365connector] No webhooks to notify * Finished: FAILURE * * [Jenkins ver. 2.143|https://jenkins.io/] * Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49577) delete bundle has no confirmation
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-49577 delete bundle has no confirmation Change By: Josh Soref Summary: delete bundle has no comfirmation confirmation Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54923) Spawning processes from build on windows server
Title: Message Title Sampath Kumar Kokkiripati updated an issue Jenkins / JENKINS-54923 Spawning processes from build on windows server Change By: Sampath Kumar Kokkiripati I am currently experiencing this issue on Jenkins running on windows server Process leaked file descriptors. See [https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors] for more information Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure [Office365connector] No webhooks to notify Finished: FAILURE [Jenkins ver. 2.143|https://jenkins.io/] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54923) Spawning processes from build on windows server
Title: Message Title Sampath Kumar Kokkiripati updated an issue Jenkins / JENKINS-54923 Spawning processes from build on windows server Change By: Sampath Kumar Kokkiripati I am currently experiencing this issue on Jenkins running on windows server Process leaked file descriptors. See [https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors] for more informationBuild step 'Build a Visual Studio project or solution using MSBuild' marked build as failure[Office365connector] No webhooks to notifyFinished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53184) Plugins and Core versions are redacted when they have 4 groups of digits
Title: Message Title Josh Soref commented on JENKINS-53184 Re: Plugins and Core versions are redacted when they have 4 groups of digits I think AboutContent could just add/remove the plugin versions as it goes. I might look into doing this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54923) Spawning processes from build on windows server
Title: Message Title Sampath Kumar Kokkiripati created an issue Jenkins / JENKINS-54923 Spawning processes from build on windows server Issue Type: Bug Assignee: Lionel Cabasson Components: msbuild-plugin Created: 2018-11-28 17:38 Environment: Windows Priority: Major Reporter: Sampath Kumar Kokkiripati I am currently experiencing this issue on windows server Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure [Office365connector] No webhooks to notify Finished: FAILURE Add Comment
[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block
Title: Message Title Andrew Bayer updated JENKINS-49997 This'll be in 1.3.4. Jenkins / JENKINS-49997 Pipeline Declarative post unsuccessful block Change By: Andrew Bayer Status: In Review 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven
Title: Message Title Brad DeWindt edited a comment on JENKINS-54871 Re: "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven Valentin,Thanks for the quick response. I was able to fix my this issue by adding tuning the JVM arguments as suggested:"-Dgatling.compilerJvmArgs="-Xmx512m"My test now runs without any issue.Thanks again!Brad Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54871) "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven
Title: Message Title Brad DeWindt commented on JENKINS-54871 Re: "java.lang.OutOfMemoryError: unable to create new native thread" running gatling test with maven Valentin, Thanks for the quick response. I was able to fix my issue by adding tuning the JVM arguments as suggested: "-Dgatling.compilerJvmArgs="-Xmx512m" My test now runs without any issue. Thanks again! Brad Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title John Hill updated an issue Jenkins / JENKINS-41497 Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries Change By: John Hill Comment: This is a pretty significant issue. We've removed our Global Pipeline Library config, restarted jenkins and it's still triggering events Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52860) Remove dependency on Build Flow
Title: Message Title Tim Jacomb updated JENKINS-52860 merged https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/91 Jenkins / JENKINS-52860 Remove dependency on Build Flow Change By: Tim Jacomb Status: Open 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title John Hill commented on JENKINS-41497 Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries This is a pretty significant issue. We've removed our Global Pipeline Library config, restarted jenkins and it's still triggering events Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Fernando Nasser commented on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Another option: def status = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches") Would return a Map, which can be seen as { 'rc': , 'stdout': , 'stderr': } A compromise would be to have both stderr and stdout together (easy to capture?) { 'rc': , 'output': } P.S.: The 'returnStderr' does not exist yet, I'll file a JIRA for it as it is useful independently.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54922) Generated markdown should work in MacDown.app
Title: Message Title Josh Soref commented on JENKINS-54922 Re: Generated markdown should work in MacDown.app jenkinsci/support-core-plugin#155 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54849) SVN_REVISION and/or SVN_REVISION_X not being set
Title: Message Title Alex Earl commented on JENKINS-54849 Re: SVN_REVISION and/or SVN_REVISION_X not being set These issues look related Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54922) Generated markdown should work in MacDown.app
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-54922
Generated markdown should work in MacDown.app
Issue Type:
Bug
Assignee:
Emilio Escobar
Components:
support-core-plugin
Created:
2018-11-28 15:50
Priority:
Minor
Reporter:
Josh Soref
Currently the generated Markdown doesn't do a good enough job of escaping {} characters and the sanitizer loves to generate {} which means that labels and node names have a tendency to generate partially italicized content when rendered in at least MacDown and potentially many other renderers. Sample raw content:
* computer_reliable_bulletin (`user_junior_process.slaves.DumbSlave`)
- Description:_Java 8_
- Executors: 1
- Remote FS root: `/home/jenkins`
- Labels: label_transparent_court label_religious_blood pipeline view_medieval_corn label_mutual_violation label_related_favourite label_easy_insurance
Rendered as:
computer reliable bulletin (user_junior_process.slaves.DumbSlave)
Description: Java 8
Executors: 1
Remote FS root: /home/jenkins
Labels: label_transparent_court label_religious_blood pipeline view_medieval_corn label_mutual_violation label_related_favourite label_easy_insurance
[JIRA] (JENKINS-54921) can not release connection
Title: Message Title
Sylvia Xie created an issue
Jenkins / JENKINS-54921
can not release connection
Issue Type:
Bug
Assignee:
Karl-Heinz Marbaise
Components:
java-client-api
Created:
2018-11-28 15:33
Priority:
Minor
Reporter:
Sylvia Xie
public InputStream getFile(URI path) throws IOException { HttpGet getMethod = new HttpGet(path); HttpResponse response = client.execute(getMethod, localContext); jenkinsVersion = ResponseUtils.getJenkinsVersion(response); httpResponseValidator.validateResponse(response); return new RequestReleasingInputStream(response.getEntity().getContent(), getMethod); } when invoke getFile method and occur exception at validateResponse(), connetions cannot be released
Add Comment
[JIRA] (JENKINS-32250) Multi-branch projects do not support Dashboard views
Title: Message Title Tomasz Lisowski commented on JENKINS-32250 Re: Multi-branch projects do not support Dashboard views Is there any workaround for this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Stephen Morley commented on JENKINS-54654 Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths Jesse Glick that might explain why the setting was not updated but why is it not valid to reference a directory outside of the JENKINS_HOME. Personally I don't like keeping active data sets in the "Program Files (x86)" directory. This has worked for over 5 years now and suddenly it fails. (Turns out we also have a problem with some utility which is not working with the spaces in the path name so our builds are broken using this form but without it Jenkins just chokes). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54882) Websphere Deploy Plugin Error ADMC0016E
Title: Message Title Hernan Tavella commented on JENKINS-54882 Re: Websphere Deploy Plugin Error ADMC0016E I changed the port to 8879 that seems to be the correct because now i can get the avaibles targets when i hit the button in the plug in config. But now i have a new error : Artifact is being deployed to virtual host: default_host Deploying 'AApp' to IBM WebSphere Application Server Error deploying to IBM WebSphere Application Server: Failed to install artifact: Failure uploading archive to server Performing rollback of 'AApp' WARNING: Artifact doesn't exist rollback repository Build step 'Deploy To IBM WebSphere Application Server' changed build result to FAILURE Finished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54920) Refactor AboutJenkins class
Title: Message Title Josh Soref commented on JENKINS-54920 Re: Refactor AboutJenkins class For reference, my current proposal is here: https://github.com/jsoref/support-core-plugin/tree/refactor I won't make a PR for it until jenkinsci/support-core-plugin#155 is merged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54920) Refactor AboutJenkins class
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-54920 Refactor AboutJenkins class Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2018-11-28 14:55 Priority: Minor Reporter: Josh Soref The AboutJenkins class is huge (>1000 lines) and coverage in AboutJenkinsTest consists of a single function mayBeDateSmokes. I'm trying to improve the output of the AboutJenkins code, and potentially improve the sanitization. But in order to do that (and not be laughed at by my colleagues), I need to be able to write tests for the pieces of code I'm changing. As is, AboutJenkins isn't practically testable in small units because everything is hidden in private class or private static. I understand that people may have pending pull requests (they should get them merged) and they may have code which depends on minute details of how this code works. If they care, they should get their changes merged and then help write tests documenting their expectations which would make it easier for future contributors to understand the constraints the code lives with when they write changes. Add Comment
[JIRA] (JENKINS-54688) Operating System informations are anonymized
Title: Message Title Francisco Fernández updated JENKINS-54688 Jenkins / JENKINS-54688 Operating System informations are anonymized Change By: Francisco Fernández Status: In Review Resolved Resolution: Fixed Released As: support-core-2.52 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title Andrew Bayer updated JENKINS-54919 Jenkins / JENKINS-54919 Newly defined parameters aren't available in Declarative agent configuration on first build 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title Andrew Bayer commented on JENKINS-54919 Re: Newly defined parameters aren't available in Declarative agent configuration on first build PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/301 - let's see if it doesn't regress anything else... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title Andrew Bayer started work on JENKINS-54919 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50220) Wrong link target for pipeline syntax link in pipeline jobs
Title: Message Title Torsten Werner commented on JENKINS-50220 Re: Wrong link target for pipeline syntax link in pipeline jobs It is fixed. The link is working again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45966) " 'Jenkinsfile' not found" due to race condition w/ webhooks and the GH Contents API
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-45966 " 'Jenkinsfile' not found" due to race condition w/ webhooks and the GH Contents API Change By: Josh Soref *The Symptom:*When using an enterprise GHE that is running slow (or I imagine, with a very fast jenkins instance, maybe even on production GH), a check for a Jenkinsfile in the branch events will say that one was not found, even though there is a Jenkinsfile in the PR's origin branch, and in the target branch. This seems to happen if you "slam" GH by creating a commit, branch, and PR all in one go (which people do with automated commits). *What I think is the cause:*As far as I can tell, GitHubSCMProbe is relying on the contents API to determine if a new branch or PR has a Jenkinsfile. When building merge PRs, it uses the merge refs with the contents API, but the merge refs aren't actually ready yet when GH sends out it's its webhooks. To prove this, I spun up a ruby sinatra app that listens for a PR webhook and immediately calls back to GH with the contents API. This reliably fails to find a ref (returns "No commit found for the ref"), unless you put a short sleep between when it receives the webhook, and when it calls out for content. You can find that here: [https://github.com/SpencerMalone/test-repo] if you want to play with it yourself. This is probably something that GH needs to fix, so I've sent them a support ticket, but just incase they are unable to, or in case it takes an exceedingly long time, I've opened this. I think in cases where we get a ref not found from the contents API while responding to branch events, there should be a short delay + retry. Add Comment
[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries
Title: Message Title Shahin Kordasti commented on JENKINS-41497 Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries I am confused as to what the "fix" is. I enabled the setting "Dont trigger build a build on commit notifications" for all our Jenkins jobs and they still get triggered whenever the global library SCM has a commit and this keeps happening after the first time. Do I need to remove the global library and re-add it again for this to 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26313) Workflow script fails if CPS-transformed methods are called from constructors
Title: Message Title Yngvar Kristiansen commented on JENKINS-26313 Re: Workflow script fails if CPS-transformed methods are called from constructors Is there any way of putting a nice error message in the jenkins log? It took some time to figure this out. In fact, all of my @NonCps-related problems have been time consuming, especially when you have never heard of it before. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-54919
Newly defined parameters aren't available in Declarative agent configuration on first build
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-11-28 13:53
Priority:
Major
Reporter:
Andrew Bayer
This is similar to both JENKINS-40574 and JENKINS-43911 (well, how JENKINS-43911 would behave from 1.2 onward - previously it was just that environment was evaluated after agent during execution) - parameters is evaluated at the beginning of the Declarative runtime, but agent is populated before that, at the very start of execution. So if params.FOO already exists when the build starts, then agent { label params.FOO }}} will work fine, but if it's a new parameter (like, say, on first build of a branch), {{params.FOO's value there will end up as null. A workaround for now is to do label "${params.FOO ?: 'whatever-the-default-value-should-be'}", but I'll work on a better solution.
Add Comment
[JIRA] (JENKINS-49778) If one stage in the pipeline fails, all the states are marked/color with the same status color
Title: Message Title Costin Caraivan closed an issue as Duplicate Jenkins / JENKINS-49778 If one stage in the pipeline fails, all the states are marked/color with the same status color Change By: Costin Caraivan 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54918) Purge machine support in ATH
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-54918 Purge machine support in ATH Issue Type: Task Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2018-11-28 13:47 Priority: Minor Reporter: Oliver Gondža https://github.com/jenkinsci/acceptance-test-harness/tree/master/src/main/java/org/jenkinsci/test/acceptance/machine This should remove a lot of maven dependencies including jclouds Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-54885) Azure VM Plugin: 1: The storage account name already exists. Use a different name.
Title: Message Title Peter Salvatore commented on JENKINS-54885 Re: Azure VM Plugin: 1: The storage account name already exists. Use a different name. Upgraded to 0.7.5 and we are back in business. Thank you so much Jie Shen ! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54917) Github pull request builds created but not triggered
Title: Message Title Vincent de Lagabbe created an issue Jenkins / JENKINS-54917 Github pull request builds created but not triggered Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-11-28 13:26 Environment: Jenkins version: 2.138.3 Github branch source plugin version: 2.4.1 Labels: github github-branch-source-plugin pull-request Priority: Minor Reporter: Vincent de Lagabbe I use the github branch source plugin with a github.com hosted organization The organization setup is: Discover branches: "Exclude branches that are also files as PR" Discover pull requests from origin: "Both the current pull request revision and the pull request merged with the current target branch revision" I recursively updates sub modules and checkout over SSH When a PR is created, the two pull request jenkins jobs "PR-head" and "PR-merge" are created, but Jenkins does not start them The "Organization event" log shows messages: > No automatic builds for PR-XX-head > No automatic builds for PR-XX-merge Why are the PRs jobs not built ? Thank you very much
[JIRA] (JENKINS-54700) Findbugs SAXParser not found
Title: Message Title Matt Wilson updated an issue Jenkins / JENKINS-54700 Findbugs SAXParser not found Change By: Matt Wilson We've traditionally used the individual plugins (PMD, Findbugs) but came across this when one of our projects moved from Findbugs to Spotbugs. We really like how the report looks and we're keen to use it in place of the older plugins...I've run into some trouble using the Findbugs option on the new plugin. When I try to collect findbugs information I get this:[FindBugs] [ERROR] Parsing of file 'x' failed due to an exception: org.dom4j.DocumentException: Sax error Nested exception: SAX2 driver class org.apache.xerces.parsers.SAXParser not found at edu.umd.cs.findbugs.SortedBugCollection.doReadXML(SortedBugCollection.java:391) at edu.umd.cs.findbugs.SortedBugCollection.doReadXML(SortedBugCollection.java:368) at edu.umd.cs.findbugs.SortedBugCollection.readXML(SortedBugCollection.java:355) at edu.hm.hafner.analysis.parser.FindBugsParser.readXml(FindBugsParser.java:230) at edu.hm.hafner.analysis.parser.FindBugsParser.parse(FindBugsParser.java:175) at edu.hm.hafner.analysis.parser.FindBugsParser.parse(FindBugsParser.java:111) at edu.hm.hafner.analysis.parser.FindBugsParser.parse(FindBugsParser.java:97) at edu.hm.hafner.analysis.IssueParser.parse(IssueParser.java:70) at io.jenkins.plugins.analysis.core.util.FilesScanner.aggregateIssuesOfFile(FilesScanner.java:101) at io.jenkins.plugins.analysis.core.util.FilesScanner.scanFiles(FilesScanner.java:85) at io.jenkins.plugins.analysis.core.util.FilesScanner.invoke(FilesScanner.java:68) at io.jenkins.plugins.analysis.core.util.FilesScanner.invoke(FilesScanner.java:29) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3085) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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)Caused by: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found The strange part is if I copy the findbugs xml files to a different job I don't get the error. The plugin does complain about not being able to find the source but it still process the data and gives me a nice report. I guess the issue is being triggered when the plugin attempts to parse through the source code. just an addition here. I'm seeing the same issue when I try and use spotbugs... I know that isn't a surprise, but I thought I'd post it.[SpotBugs] [ERROR] Parsing of file '...' failed due to an exception: *14:41:22* *14:41:22* org.dom4j.DocumentException: Sax error Nested exception: SAX2 driver class org.apache.xerces.parsers.SAXParser not found*14:41:22* at
[JIRA] (JENKINS-54700) Findbugs SAXParser not found
Title: Message Title Christian Asselmeyer commented on JENKINS-54700 Re: Findbugs SAXParser not found Tomasz Lisowski I also had to downgrade analysis-model-api to 1.0.0-beta13 to get the Warning NG 1.0.0-beta4 working properly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54916) Collapse trivial tests to meaningful use-cases
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-54916 Collapse trivial tests to meaningful use-cases Issue Type: Task Assignee: Oliver Gondža Components: acceptance-test-harness Created: 2018-11-28 13:10 Priority: Minor Reporter: Oliver Gondža Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54915) Remove no_docker tests now when upstream CI supports docker
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-54915 Remove no_docker tests now when upstream CI supports docker Change By: Oliver Gondža Issue Type: Epic Task Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
