[JIRA] (JENKINS-50593) Docker image from private registry is ignored in the global container template configuration
Title: Message Title Michael Kühn closed an issue as Postponed User fault Jenkins / JENKINS-50593 Docker image from private registry is ignored in the global container template configuration Change By: Michael Kühn Status: Open Closed Resolution: Postponed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.goog
[JIRA] (JENKINS-50593) Docker image from private registry is ignored in the global container template configuration
Title: Message Title Michael Kühn commented on JENKINS-50593 Re: Docker image from private registry is ignored in the global container template configuration Thanks, everything works as designed. The mistake was ours. The correct template was not used. There was a fault in the template name and six eyes didn't see it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50601) SSH plugin cannot negotiate
Title: Message Title Zack Snyder commented on JENKINS-50601 Re: SSH plugin cannot negotiate Like I already said, connection via bash works without a problem. The problem is the ssh jenkins plugin which is outdated. It seems to ship with an own openssh agent , which is of course wrong. It should always use the native one. (but I am not sure about that, maybe it invokes it wrong). Anyway, the problem is the jenkins plugin. I have the latest version of jenks. See the system_info. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50616 JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Change By: Oleg Nenashev Component/s: ruby-runtime Component/s: ruby-runtime-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev commented on JENKINS-50616 Re: JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons CI-Skip Uses RubyRuntime, which is known to be impacted by JEP-200. Before the release in 2.102 we have whitelisted classes on the core's side: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/jenkins/security/whitelisted-classes.txt#L177-L189 . But apparently this whitelist is not enough. Ideally we need https://github.com/jenkinsci/ruby-runtime-plugin/pull/5 to be updated and released. The plugin has no maintainer, but I will check whether we can do that Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50616 JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Change By: Oleg Nenashev Labels: JEP-200 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-50616 JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Change By: Oleg Nenashev Assignee: Kohei Hasegawa Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50593) Docker image from private registry is ignored in the global container template configuration
Title: Message Title Carlos Sanchez reopened an issue Jenkins / JENKINS-50593 Docker image from private registry is ignored in the global container template configuration Change By: Carlos Sanchez Resolution: Postponed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50593) Docker image from private registry is ignored in the global container template configuration
Title: Message Title Carlos Sanchez closed an issue as Not A Defect Jenkins / JENKINS-50593 Docker image from private registry is ignored in the global container template configuration Change By: Carlos Sanchez Status: Reopened Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50518) Use presigned URLs for upload
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50518 Re: Use presigned URLs for upload Code changed in jenkins User: Carlos Sanchez Path: pom.xml src/test/java/io/jenkins/plugins/artifact_manager_s3/JCloudsAbstractTest.java src/test/java/io/jenkins/plugins/artifact_manager_s3/JCloudsArtifactManagerTest.java http://jenkins-ci.org/commit/artifact-manager-s3-plugin/fb9698c455b46c03abaf6f2f88dcb832f0e4bccc Log: Merge pull request #7 from jenkinsci/docker-JENKINS-50518 JENKINS-50518 Run tests inside Dockerized agents Compare: https://github.com/jenkinsci/artifact-manager-s3-plugin/compare/23cd4398c949...fb9698c455b4 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50518) Use presigned URLs for upload
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50518 Re: Use presigned URLs for upload Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/artifact-manager-s3-plugin/8c62ca6a7efb07c3718f218adb33b0aa11c0e244 Log: JENKINS-50518 Picking up https://github.com/jenkinsci/workflow-api-plugin/pull/67/commits/915f652453f8199069459ad733193e30492d96e6 and https://github.com/jenkinsci/docker-fixtures/pull/19 to run tests inside Dockerized agents. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31579) phaseJobs() are being skipped when there are no changes.
Title: Message Title Miguel Santos commented on JENKINS-31579 Re: phaseJobs() are being skipped when there are no changes. Any news on this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50386) Job configuration Save/Apply buttons missing
Title: Message Title Kimmo Toro commented on JENKINS-50386 Re: Job configuration Save/Apply buttons missing Comment from one of our developers: I have a hard time getting Save/Apply buttons if I open a Jenkins job configuration page in Edge. Also, when having the DevTools pane or window open in Chrome seems to decrease the odds of getting the buttons. It seems the issue is timing-related... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50591) Files and paths with ampersand cause exception
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50591 Re: Files and paths with ampersand cause exception Code changed in jenkins User: Carlos Sanchez Path: pom.xml src/test/java/io/jenkins/plugins/artifact_manager_s3/JCloudsAbstractTest.java src/test/java/io/jenkins/plugins/artifact_manager_s3/JCloudsArtifactManagerTest.java http://jenkins-ci.org/commit/artifact-manager-s3-plugin/4392c8caa313e01b197a7abbc76cc428bb4eb921 Log: Merge branch 'master' into JENKINS-50591 Compare: https://github.com/jenkinsci/artifact-manager-s3-plugin/compare/dd963e3c5fa3...4392c8caa313 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev started work on JENKINS-50616 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50616) JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons
Title: Message Title Oleg Nenashev updated JENKINS-50616 Jenkins / JENKINS-50616 JEP-200 Refusing to marshal org.jruby.RubyNil for security reasons Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-47286
Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
[~benkeil83] Great + thanks!Some questions and comments WRT [ https://github.com/comquent/imperative-when: ] # [~jamesdumay] {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils.markStageSkippedForConditional(STAGE_NAME)}} is annotated with {{@Restricted(NoExternalUse.class)}} => I assume one therefore should not and cannot rely on this method being available forever. However, since this approach seems to work very well or would be at least an acceptable workaround for scripted pipelines, how are the chances that this will be get part of the official API (via removing this annotation?) or might even get used/wrapped by a new official API? ** When trying out the other similarly named methods in {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils}} (i.e. {{markStageFailedAndContinued}}, {{markStageSkippedForFailure}}, {{markStageSkippedForUnstable}}, {{markStageSkippedForConditional}}) the behaviour is rather surprising and "proofs" the aforementioned annotation ;) => so let's just stay with {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils.markStageSkippedForConditional(STAGE_NAME)}} # [~jamesdumay] The mouse over hovering text in blue ocean shows "common.state.skipped": Since I also get this in a little declarative pipeline prototype I guess this is a minor bug (missing translation, or -- – maybe even better/preferable -- – missing to state the reason for the skipping) {color:#707070}and not a side effect of (ab-)using this method in the wrong context{color}?# @ All: I am wondering why the {{body}} closure evaluation is coded with delegation based on {{config}} map in this example!?# @ All: The {{STAGE_NAME}} is an unknown property in class section of shared library (that is not in "vars" section) but works in "Jenkinsfile" -- – I guess that is due to some transformation magic applied on "vars" section?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50591) Files and paths with ampersand cause exception
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50591 Re: Files and paths with ampersand cause exception Code changed in jenkins User: Carlos Sanchez Path: src/test/java/io/jenkins/plugins/artifact_manager_s3/JCloudsBlobStoreTest.java http://jenkins-ci.org/commit/artifact-manager-s3-plugin/3a5d4d308c0de4d519c5927477abf280e6b58196 Log: Merge pull request #9 from jenkinsci/JENKINS-50591 JENKINS-50591[JCLOUDS-1401] Add test that shows jclouds issue Compare: https://github.com/jenkinsci/artifact-manager-s3-plugin/compare/eef7980cc3c4...3a5d4d308c0d Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50591) Files and paths with ampersand cause exception
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50591 Re: Files and paths with ampersand cause exception Code changed in jenkins User: Carlos Sanchez Path: src/test/java/io/jenkins/plugins/artifact_manager_s3/JCloudsBlobStoreTest.java http://jenkins-ci.org/commit/artifact-manager-s3-plugin/eac0c920597d3fed060f857a52edc915ab3851d7 Log: JENKINS-50591[JCLOUDS-1401] Add test that shows jclouds issue when the listing using a prefix that contains ampersand Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-47286
Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
[~benkeil83] Great + thanks!Some questions and comments WRT [https://github.com/comquent/imperative-when:] # [~jamesdumay] {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils.markStageSkippedForConditional(STAGE_NAME)}} is annotated with {{@Restricted(NoExternalUse.class)}} => I assume one therefore should not and cannot rely on this method being available forever. However, since this approach seems to work very well or would be at least an acceptable workaround for scripted pipelines, how are the chances that this will be get part of the official API (via removing this annotation?) or might even get used/wrapped by a new official API? ** When trying out the other similarly named methods in {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils}} (i.e. {{markStageFailedAndContinued}}, {{markStageSkippedForFailure}}, {{markStageSkippedForUnstable}}, {{markStageSkippedForConditional}}) the behaviour is rather surprising and "proofs" the aforementioned annotation ;) => so let's just stay with {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils.markStageSkippedForConditional(STAGE_NAME)}} # [~jamesdumay] The mouse over hovering text in blue ocean shows "common.state.skipped": Since I also get this in a little declarative pipeline prototype I guess this is a minor bug (missing translation, or – maybe even better/preferable – missing to state the reason for the skipping) {color:#707070}and not a side effect of (ab-)using this method in the wrong context{color}? # @ All: I am wondering why the {{body}} closure evaluation is coded with delegation based on {{config}} map in this example!? # @ All: The {{STAGE_NAME}} is an unknown property in class section of shared library (that is not in "vars" section) but works in "Jenkinsfile" – I guess that is due to some transformation magic applied on "vars" section? # @ All: Is that unfortunately leading to such SEVERE log lines:{noformat}2018-04-06 11:04:03 SEVERE [io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor ] Could not find execution for run ACME-Pipeline#2347{noformat}
Add Comment
[JIRA] (JENKINS-50620) PTC - No checkin performed, if include field is empty
Title: Message Title Carsten Snider created an issue Jenkins / JENKINS-50620 PTC - No checkin performed, if include field is empty Issue Type: Bug Assignee: PTC ALM Components: integrity-plugin Created: 2018-04-06 09:27 Environment: Plugin Version 2.2 Jenkins 2.114 Priority: Minor Reporter: Carsten Snider An update of the PTC password in the Jenkins options is not correctly propogated to all projects. I think the problem is, that the fields "project specific username / password" are only fetched once from the Jenkins options, if you create a new project, but are not refreshed. After I deleted the user and password in the project configuration the new values from the jenkins options are fetched. Add Comment
[JIRA] (JENKINS-50620) PTC - New password not copied to projects
Title: Message Title Carsten Snider updated an issue Jenkins / JENKINS-50620 PTC - New password not copied to projects Change By: Carsten Snider Summary: PTC - No checkin performed, if include field is empty New password not copied to projects Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50621) add the runATH step to the git-plugin in a PR basis
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-50621 add the runATH step to the git-plugin in a PR basis Issue Type: Task Assignee: Mark Waite Components: git-plugin Created: 2018-04-06 09:28 Priority: Minor Reporter: Raul Arabaolaza Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jen
[JIRA] (JENKINS-50621) add the runATH step to the git-plugin in a PR basis
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-50621 add the runATH step to the git-plugin in a PR basis Change By: Raul Arabaolaza Labels: essentials Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50621) add the runATH step to the git-plugin in a PR basis
Title: Message Title Raul Arabaolaza assigned an issue to Unassigned Jenkins / JENKINS-50621 add the runATH step to the git-plugin in a PR basis Change By: Raul Arabaolaza Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50537) git-plugin ATH audit
Title: Message Title Raul Arabaolaza started work on JENKINS-50537 Change By: Raul Arabaolaza Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50537) git-plugin ATH audit
Title: Message Title Raul Arabaolaza stopped work on JENKINS-50537 Change By: Raul Arabaolaza Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50622) when condition not correctly discovering branch
Title: Message Title
Dominik Bartholdi updated an issue
Jenkins / JENKINS-50622
when condition not correctly discovering branch
Change By:
Dominik Bartholdi
I created a new pipeline job and defined "Pipeline script from SCM" using Git: * repo Url: g...@bitbucket.org:yooture/xxx.git * branch specifier: */master * Repository browser: (auto) * Additional Behaviours: none * Script Path: Jenkinsfile * Lightweight checkout: onIn have the following simele simple pipeline: {code:java}pipeline { agent { label 'lxc-fedora25' } tools { maven 'MVN_352' jdk "Oracle JDK 1.8 (latest)" } stages { stage('build Snapshot') { when { not { branch 'master' } } steps { sh 'mvn clean install -Dmaven.test.failure.ignore' } } stage('Build Release') { when { branch 'master' } steps { sh "mvn clean deploy" } } }}{code} even though the branch specifier is specified as "*/master", "build Snapshot" stage is always executed :(
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50622) when condition not correctly discovering branch
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-50622
when condition not correctly discovering branch
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-04-06 09:31
Environment:
Pipeline Model Definition Plugin: 1.2.2
Priority:
Critical
Reporter:
Dominik Bartholdi
I created a new pipeline job and defined "Pipeline script from SCM" using Git:
repo Url: g...@bitbucket.org:yooture/xxx.git
branch specifier: */master
Repository browser: (auto)
Additional Behaviours: none
Script Path: Jenkinsfile
Lightweight checkout: on
In have the following simele pipeline:
pipeline {
agent { label 'lxc-fedora25' }
tools {
maven 'MVN_352'
jdk "Oracle JDK 1.8 (latest)"
}
stages {
stage('build Snapshot') {
when { not { branch 'master' } }
steps {
sh 'mvn clean install -Dmaven.test.failure.ignore'
}
}
stage('Build Release') {
when { branch 'master' }
steps {
sh "mvn clean deploy"
}
}
}
}
[JIRA] (JENKINS-50535) git-plugin unit and integration coverage analysis
Title: Message Title Raul Arabaolaza started work on JENKINS-50535 Change By: Raul Arabaolaza Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50585) Extend pipeline-library runAth() function to allow calling full ATH suite
Title: Message Title Raul Arabaolaza commented on JENKINS-50585 Re: Extend pipeline-library runAth() function to allow calling full ATH suite Oliver Gondža I have been thinking about this, this metadata file works for running the entire ATH. To be honest, this is not fully intentional but maybe is enough?: ath: jenkins: 'latest' useLocalSnapshots: false tests: - '*' Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Carlos Sanchez updated JENKINS-50525 Merged https://github.com/jenkinsci/kubernetes-plugin/pull/303 Jenkins / JENKINS-50525 Error When Provisioning Slave: mountPath: Required value Change By: Carlos Sanchez Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit ht
[JIRA] (JENKINS-47821) vsphere plugin 2.16 not respecting slave disconnect settings
Title: Message Title pjdarton commented on JENKINS-47821 Re: vsphere plugin 2.16 not respecting slave disconnect settings In that case then I'm going to need you to describe your setup, as that's not what I see here (but then, I mostly use the plugin's "Cloud" functionality and am unfamiliar with its other functionality, which I'm guessing is what you're using). If you can provide a description of how to set up a Jenkins server (that has the vSphere plugin installed) to reproduce this issue, I'll see if I can reproduce it. If I can reproduce it, there's a chance I might be able to fix it. (FYI fixing bugs in this plugin is not my official day job, so the easier you can make it for me to see the issue for myself, the better the chances are that I can come up with a fix before my boss tells me to do something that is my official day job) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50535) git-plugin unit and integration coverage analysis
Title: Message Title Raul Arabaolaza commented on JENKINS-50535 Re: git-plugin unit and integration coverage analysis Thanks Jesse Glick and Mark Waite I am going to start generating some code coverage reports to get some readable data here. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50622) when condition not correctly discovering branch
Title: Message Title
Dominik Bartholdi commented on JENKINS-50622
Re: when condition not correctly discovering branch
btw. this stage:
stage('prepare yoo') {
steps {
echo "on ${env.BRANCH_NAME}"
}
}
does print 'on null' - I guess this is the root problem, but I have no idea why this is the case...
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50598) Add support of running JTH with custom WAR
Title: Message Title Oliver Gondža commented on JENKINS-50598 Re: Add support of running JTH with custom WAR Will we ever benefit from the ability to test against wars except for Custom WAR Packager testing? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50598) Add support of running JTH with custom WAR
Title: Message Title Oleg Nenashev commented on JENKINS-50598 Re: Add support of running JTH with custom WAR Oliver Gondža I am not sure I get your question. During JEP-200 testing in Dec/Jan I have applied many patches to Plugin Compat Tester (JENKINS-48734), and currently it works well for stock Jenkins WARs (released and unreleased ones) I also bumped your thread in https://groups.google.com/forum/#!searchin/jenkinsci-dev/plugin$20compat$20tester%7Csort:date/jenkinsci-dev/jPiDzfWmMyw/ZP0SBz1oCgAJ about PCT this winter Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50535) git-plugin unit and integration coverage analysis
Title: Message Title Raul Arabaolaza assigned an issue to Raul Arabaolaza Jenkins / JENKINS-50535 git-plugin unit and integration coverage analysis Change By: Raul Arabaolaza Assignee: Raul Arabaolaza Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50598) Add support of running JTH with custom WAR
Title: Message Title Oleg Nenashev commented on JENKINS-50598 Re: Add support of running JTH with custom WAR PCT documentation is also in place now: https://github.com/jenkinsci/plugin-compat-tester Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50598) Add support of running JTH with custom WAR
Title: Message Title Oliver Gondža commented on JENKINS-50598 Re: Add support of running JTH with custom WAR What I meant is if the change proposed here is to support the experiment/adoption of the Custom WAR Packager or if there are any other benefits for traditional JTH against core / plugins that has some old problems originating from different dependency handling. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49805) Prototype error telemetry logging with a Java Util Logger configuration
Title: Message Title Baptiste Mathus commented on JENKINS-49805 Re: Prototype error telemetry logging with a Java Util Logger configuration R. Tyler Croy processory question: do you prefer we create smaller tasks for downstream things and so on, or keeping the central one is enough (OK, I see the answer coming: it depends ). Here my example is: I'm going to start the hosting process of the Jenkins Essentials Plugin to move forward with my previous comment. For this example, would you create some specific task on "our" side like "Host the Essentials plugin", or you wouldn't bother, or you don't care at all? Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50535) git-plugin unit and integration coverage analysis
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-50535 git-plugin unit and integration coverage analysis Change By: Raul Arabaolaza Attachment: jacoco-git.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50535) git-plugin unit and integration coverage analysis
Title: Message Title Raul Arabaolaza commented on JENKINS-50535 Re: git-plugin unit and integration coverage analysis Attached jacoco report:I am starting to analyze it in detail to get some data about poor coverage areas Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50535) git-plugin unit and integration coverage analysis
Title: Message Title Raul Arabaolaza updated an issue Jenkins / JENKINS-50535 git-plugin unit and integration coverage analysis Change By: Raul Arabaolaza Attachment: jacoco.zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Simon Wydooghe commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value Cool, cheers! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50535) git-plugin unit and integration coverage analysis
Title: Message Title Raul Arabaolaza edited a comment on JENKINS-50535 Re: git-plugin unit and integration coverage analysis Attached jacoco report: !jacoco-git.png|thumbnail! I am starting to analyze it in detail to get some data about poor coverage areas, after that, I can start to take a look at tests in [~markewaite] private environment to see if they cover those areas and probably also at the ATH for the same reason. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50535) git-plugin unit and integration coverage analysis
Title: Message Title Raul Arabaolaza edited a comment on JENKINS-50535 Re: git-plugin unit and integration coverage analysis Attached jacoco report: !jacoco-git.png|thumbnail! I am starting to analyze it in detail to get some data about poor coverage areas , after that, I can start to take a look at tests in [~markewaite] to see if they cover those areas and probably also at the ATH for the same reason. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50291) Customize where AsyncPeriodicWork are logged
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50291 Re: Customize where AsyncPeriodicWork are logged Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/jenkins/metrics/api/Metrics.java src/test/java/jenkins/metrics/api/MetricsTest.java http://jenkins-ci.org/commit/metrics-plugin/39718de3379b73abb17bf80261999e5bca9b378a Log: Merge pull request #30 from batmat/JENKINS-50291 JENKINS-50291 Move health-checker.log under the now configurable logs root directory Compare: https://github.com/jenkinsci/metrics-plugin/compare/87988e92d3c0...39718de3379b Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50291) Customize where AsyncPeriodicWork are logged
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50291 Re: Customize where AsyncPeriodicWork are logged Code changed in jenkins User: Baptiste Mathus Path: src/main/java/jenkins/metrics/api/Metrics.java src/test/java/jenkins/metrics/api/MetricsTest.java http://jenkins-ci.org/commit/metrics-plugin/c0dc0077401211952b216e91a6b16741273652b9 Log: JENKINS-50291 Test showing the issue Expected to fail on the second assertion Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50291) Customize where AsyncPeriodicWork are logged
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50291 Re: Customize where AsyncPeriodicWork are logged Code changed in jenkins User: Baptiste Mathus Path: src/main/java/jenkins/metrics/api/Metrics.java http://jenkins-ci.org/commit/metrics-plugin/1c838cc7b78558d79e02f74eec8cfd30b8a7f3c7 Log: JENKINS-50291 Adjust to new logs root location Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49805) Prototype error telemetry logging with a Java Util Logger configuration
Title: Message Title Baptiste Mathus commented on JENKINS-49805 Re: Prototype error telemetry logging with a Java Util Logger configuration HOSTING-541 created. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-47286
Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
[~benkeil83] Great + thanks!Some questions and comments WRT [https://github.com/comquent/imperative-when:] # [~jamesdumay] {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils.markStageSkippedForConditional(STAGE_NAME)}} is annotated with {{@Restricted(NoExternalUse.class)}} => I assume one therefore should not and cannot rely on this method being available forever. However, since this approach seems to work very well or would be at least an acceptable workaround for scripted pipelines, how are the chances that this will be get part of the official API (via removing this annotation?) or might even get used/wrapped by a new official API? ** When trying out the other similarly named methods in {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils}} (i.e. {{markStageFailedAndContinued}}, {{markStageSkippedForFailure}}, {{markStageSkippedForUnstable}}, {{markStageSkippedForConditional}}) the behaviour is rather surprising and "proofs" the aforementioned annotation ;) => so let's just stay with {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils.markStageSkippedForConditional(STAGE_NAME)}} # [~jamesdumay] The mouse over hovering text in blue ocean shows "common.state.skipped": Since I also get this in a little declarative pipeline prototype I guess this is a minor bug (missing translation, or – maybe even better/preferable – missing to state the reason for the skipping) {color:#707070}and not a side effect of (ab-)using this method in the wrong context{color}? # @ All: I am wondering why the {{body}} closure evaluation is coded with delegation based on {{config}} map in this example!? # @ All: The {{STAGE_NAME}} is an unknown property in class section of shared library (that is not in "vars" section) but works in "Jenkinsfile" – I guess that is due to some transformation magic applied on "vars" section? # -@ All: Is that unfortunately leading to such SEVERE log lines:-{noformat}2018-04-06 11:04:03 SEVERE [io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor ] Could not find execution for run ACME-Pipeline#2347{noformat} # ** * Update:* No that is another Jenkins pipeline or Blue Ocean bug, because it also happens for builds that do NOT use this method/approach; or that even do not skip any stages...
Add Comment
[JIRA] (JENKINS-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-47286
Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
[~benkeil83] Great + thanks!Some questions and comments WRT [https://github.com/comquent/imperative-when:] # [~jamesdumay] {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils.markStageSkippedForConditional(STAGE_NAME)}} is annotated with {{@Restricted(NoExternalUse.class)}} => I assume one therefore should not and cannot rely on this method being available forever. However, since this approach seems to work very well or would be at least an acceptable workaround for scripted pipelines, how are the chances that this will be get part of the official API (via removing this annotation?) or might even get used/wrapped by a new official API? ** When trying out the other similarly named methods in {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils}} (i.e. {{markStageFailedAndContinued}}, {{markStageSkippedForFailure}}, {{markStageSkippedForUnstable}}, {{markStageSkippedForConditional}}) the behaviour is rather surprising and "proofs" the aforementioned annotation ;) => so let's just stay with {{org.jenkinsci.plugins.pipeline.modeldefinition.Utils.markStageSkippedForConditional(STAGE_NAME)}} # [~jamesdumay] The mouse over hovering text in blue ocean shows "common.state.skipped": Since I also get this in a little declarative pipeline prototype I guess this is a minor bug (missing translation, or – maybe even better/preferable – missing to state the reason for the skipping) {color:#707070}and not a side effect of (ab-)using this method in the wrong context{color}? # @ All: I am wondering why the {{body}} closure evaluation is coded with delegation based on {{config}} map in this example!? # @ All: The {{STAGE_NAME}} is an unknown property in class section of shared library (that is not in "vars" section) but works in "Jenkinsfile" – I guess that is due to some transformation magic applied on "vars" section? # - @ All: Is that unfortunately leading to such SEVERE log lines: - {noformat}2018-04-06 11:04:03 SEVERE [io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor ] Could not find execution for run ACME-Pipeline#2347{noformat} ** *Update:* No that is another Jenkins pipeline or Blue Ocean bug, because it also happens for builds that do NOT use this method/approach; or that even do not skip any stages...
Add Comment
[JIRA] (JENKINS-50623) Build trigger using SVN is getting error in URL
Title: Message Title Priyanga G created an issue Jenkins / JENKINS-50623 Build trigger using SVN is getting error in URL Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: subversion-plugin Created: 2018-04-06 10:38 Environment: jenkins-2.101 os-windows 7 Priority: Minor Reporter: Priyanga G I am triggering job in Jenkins using post-commit-hook in svn. my jenkins url is: Add Comment
[JIRA] (JENKINS-50623) Build trigger using SVN is getting error in URL
Title: Message Title Priyanga G updated an issue Jenkins / JENKINS-50623 Build trigger using SVN is getting error in URL Change By: Priyanga G Attachment: Post-Commit-Hook.bat Attachment: POST_COMMIT_HOOK.py Attachment: post-commit-hook-error.txt I am triggering job in Jenkins using post-commit-hook in svn.my jenkins url is: [http://priyanga:07a66fcd8261dd011c8eeba76eeed1d9@localhost:8080/job/FORD/build?token=TOKEN_NAME&cause=svn-post-commit] I am checking the changes in svn using python.[^post-commit-hook-error.txt] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Edd Grant commented on JENKINS-43171 Re: Correct Pom for build-monitor-plugin Hey Daniel Spilker, Yep we originally tested that build as it happens, double checked it again this morning and got the same error: > Could not resolve org.jenkins-ci.plugins:build-monitor-plugin:1.12+build.201708172343. > Could not parse POM https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/build-monitor-plugin/1.12+build.201708172343/build-monitor-plugin-1.12+build.201708172343.pom > Could not find org.jenkins-ci.plugins:build-monitor:1.12+build.201708172343. > Could not resolve org.jenkins-ci.plugins:build-monitor-plugin:1.12+build.201708172343. > Could not parse POM https://nexus-build.tax.service.gov.uk/content/groups/public/org/jenkins-ci/plugins/build-monitor-plugin/1.12+build.201708172343/build-monitor-plugin-1.12+build.201708172343.pom > Could not find org.jenkins-ci.plugins:build-monitor:1.12+build.201708172343. Interestingly I cloned the build-monitor-plugin repository, changed the version to 1.12-SNAPSHOT and ran a mvn install. I then was able to get Gradle to use this artefact just fine by using mavenLocal(). This confused me as I was expecting to get the same error I got when pulling the official artefact, could it be that there's something going on in the publishing phase which is modifying the pom? Cheers! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50624) Rework the custom plugins builds hack to make it easier to add/remove a plugin
Title: Message Title Baptiste Mathus started work on JENKINS-50624 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50624) Rework the custom plugins builds hack to make it easier to add/remove a plugin
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-50624 Rework the custom plugins builds hack to make it easier to add/remove a plugin Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50624) Rework the custom plugins builds hack to make it easier to add/remove a plugin
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-50624 Rework the custom plugins builds hack to make it easier to add/remove a plugin Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-04-06 10:46 Priority: Minor Reporter: Baptiste Mathus Currently, we have a custom build for Essentials for the configuration-as-code plugin, and the essentials one. I am about to: remove essentials once HOSTING-541 is processed and we can release it remove configuration-as-code as we now switch back to the latest release since we do not use anything specific in the master branch add the metrics plugin to move forward as long as https://github.com/jenkinsci/metrics-plugin/pull/30 is not released (it is already merged at the time of writing) We can expect adding/removing plugins is going to be pretty common in the next weeks as we move forward. So we should have simpler way to do that instead of basically copy-pasting or removing some lines of Makefile around to add or remove a new plugin, and commenting out or not the line in the plugins.aria file currently...
[JIRA] (JENKINS-50624) Rework the custom plugins builds hack to make it easier to add/remove a plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50624 Rework the custom plugins builds hack to make it easier to add/remove a plugin Change By: Baptiste Mathus Labels: essentials technical-debt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50624) Rework the custom plugins builds hack to make it easier to add/remove a plugin
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50624 Rework the custom plugins builds hack to make it easier to add/remove a plugin Change By: Baptiste Mathus Labels: essentials essentials-triggered technical-debt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44451) Cannot save pipeline with a wrapper
Title: Message Title Max von Preuschen reopened an issue Reopening this issue, since it seems there is no possibility to enter a valid value into the "Delegate" text input field. Expecting "class jenkins.tasks.SimpleBuildWrapper" for parameter "delegate" but got "..." of type class java.lang.String instead Jenkins / JENKINS-44451 Cannot save pipeline with a wrapper Change By: Max von Preuschen Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50027) Polling build filters in jenkinsfile broken or need guidance on what code should be
Title: Message Title
Karl Wirth commented on JENKINS-50027
Re: Polling build filters in jenkinsfile broken or need guidance on what code should be
A slight twist. Only happens if there are files that match the build filter. Repro case: (1) Create stream depot. (2) Add files in '//streams/main/workers'. (3) Create Jenkins job with following content:
pipeline {
agent {label 'master'}
stages {
stage('Sync code') {
steps {
echo "Starting"
checkout perforce(credential: 'MasterServer',
filter: [viewFilter(viewMask: '''//streams/main/workers''')],
populate: autoClean(delete: true, modtime: false,
parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'],
pin: '', quiet: false, replace: true, tidy: false),
workspace: streamSpec(charset: 'none',
format: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}',
pinHost: false, streamName: '//streams/main'))
}
}
}
(4) Run 'Build Now'. (5) Run 'Poll Now'. No errors in polling log.
Perforce Software Polling Log
Started on Apr 6, 2018 11:17:00 AM
P4: Polling on: master with:jenkins-master-FilteredPipeline-0
Found last change 417 on syncID jenkins-NODE_NAME-FilteredPipeline-EXECUTOR_NUMBER
... p4 client -o jenkins-master-FilteredPipeline-0 +
... p4 info +
P4 Task: establishing connection.
... server: 10.1.3.217:1666
... node: vm-kwirth-swarm174-xenial
P4: Polling with range: 417,now
... p4 changes -m20 //jenkins-master-FilteredPipeline-0/...@417,now +
... p4 repos -C +
Done. Took 0.11 sec
No changes
(6) Edit and submit //streams/main/workers/f1. (7) Run 'Poll Now'. Following errors seen:
Perforce Software Polling Log
Started on Apr 6, 2018 11:15:00 AM
P4: Polling on: master with:jenkins-master-FilteredPipeline-0
Found last change 415 on syncID jenkins-NODE_NAME-FilteredPipeline-EXECUTOR_NUMBER
... p4 client -o jenkins-master-FilteredPipeline-0 +
... p4 info +
P4 Task: establishing connection.
... server: 10.1.3.217:1666
... node: vm-kwirth-swarm174-xenial
P4: Polling with range: 415,now
... p4 changes -m20 //jenkins-master-FilteredPipeline-0/...@415,now +
... p4 change -o 417 +
... p4 describe -s 417 +
P4 Task: attempt: 1
P4 Task: failed: java.lang.NullPointerException
ERROR: polling failed in /var/lib/jenkins/workspace/FilteredPipeline on : P4 Task: failed: java.lang.NullPointerException
Done. Took 3.1 sec
No changes
(8) Error in Jenkins log:
P4 Task: attempt: 1
Apr 06, 2018 11:14:03 AM WARNING org.jenkinsci.plugi
[JIRA] (JENKINS-50623) Build trigger using SVN is getting error in URL
Title: Message Title Priyanga G updated an issue Jenkins / JENKINS-50623 Build trigger using SVN is getting error in URL Change By: Priyanga G Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50625) BUG: Java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration
Title: Message Title Ashutosh Dash created an issue Jenkins / JENKINS-50625 BUG: Java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration Issue Type: Task Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 2018-04-06 11:48 Priority: Major Reporter: Ashutosh Dash I am experiencing some problem while deploying my project EAR to Weblogic Server through Jenkins. Task 2 failed: [Deployer:149026]deploy application iotp-ear-7 on AdminServer. Target state: deploy failed on Server AdminServer java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration Add Comment
[JIRA] (JENKINS-50625) BUG: Java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration
Title: Message Title Ashutosh Dash updated an issue Jenkins / JENKINS-50625 BUG: Java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfiguration Change By: Ashutosh Dash Attachment: Error.txt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50460) Builds marked as failed - Dr Memory plugin (JEP-200)
Title: Message Title Piotr Bogdanski commented on JENKINS-50460 Re: Builds marked as failed - Dr Memory plugin (JEP-200) Dear Ewelina Wilkosz, Do you have any update on this issue? Thanks. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50460) Builds marked as failed - Dr Memory plugin (JEP-200)
Title: Message Title Ewelina Wilkosz commented on JENKINS-50460 Re: Builds marked as failed - Dr Memory plugin (JEP-200) Bue Petersen is going to provide some information next week, is that correct Bue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-9130) Add a dynamic parser to colorize and indent groovy textareas
Title: Message Title Yusuf Tarık Günaydın commented on JENKINS-9130 Re: Add a dynamic parser to colorize and indent groovy textareas Sorry for reviving an old issue, but System Groovy script doesn't have syntax coloring in build steps. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46984) p4-plugin: rebuild doesn't work properly with "build review"
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-46984 p4-plugin: rebuild doesn't work properly with "build review" Change By: Karl Wirth Labels: P4_BACKLOG P4_VERIFY Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46984) p4-plugin: rebuild doesn't work properly with "build review"
Title: Message Title Karl Wirth commented on JENKINS-46984 Re: p4-plugin: rebuild doesn't work properly with "build review" Reproduction Steps (1) Trigger a Jenkins review build from Swarm by submitting a review. (In this case Review 425; change 426) (2) Submit a new changelist to project path (change 427). (3) Click Rebuild (from Rebuilder plugin). On paramaters page check that review is 425 and changelist is 426). (4) When Rebuild job runs it will sync changelist 427 not 426. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50623) Build trigger using SVN is getting error in URL
Title: Message Title Priyanga G assigned an issue to Mathieu Cantin Jenkins / JENKINS-50623 Build trigger using SVN is getting error in URL Change By: Priyanga G Assignee: Ivan Fernandez Calvo Mathieu Cantin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50626) PCT "-mavenProperties" argument does nothing
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50626 PCT "-mavenProperties" argument does nothing Issue Type: Bug Assignee: Unassigned Components: plugin-compat-tester Created: 2018-04-06 12:20 Priority: Minor Reporter: Oleg Nenashev I was experimenting with running PCT for custom WARs, but it appears that I cannot pass any custom Maven Properties with "-mavenProperties" file, because... this parameter is just ignored in the PCT CLI codebase Add Comment This message was s
[JIRA] (JENKINS-50628) Rebuild does not regenerate pass/fail URL callback
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-50628 Rebuild does not regenerate pass/fail URL callback Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2018-04-06 12:21 Priority: Minor Reporter: Karl Wirth When using the Rebuilder plugin to rebuild a Swarm triggered review build the callback to Swarm stating the new job status is not sent. Reproductions Steps: (1) Create a Swarm project linked to a Jenkins Review build. (2) Purposefully put in code that fails the build. For example shell script with command "argggh". (3) Create review to trigger build. When it fails correct callback is sent to Swarm and is seen in Swarm Apache access logs. (4) Fix Jenkins job taking out the failing code. (5) Click 'Rebuild' on the failed job. The pass and fail URLs are correctly presented in the parameters dialog. Click 'Rebuild'. (6) Swarm test fail icon does not change. Callback is not seen in Swarm Apache logs. Add Comment
[JIRA] (JENKINS-50627) Custom WAR Packager - Support running PCT and ATH with Custom WAR Packager
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50627 Custom WAR Packager - Support running PCT and ATH with Custom WAR Packager Issue Type: Epic Assignee: Oleg Nenashev Components: custom-war-packager Created: 2018-04-06 12:21 Priority: Minor Reporter: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscr
[JIRA] (JENKINS-50628) Rebuild does not regenerate pass/fail URL callback
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-50628 Rebuild does not regenerate pass/fail URL callback Change By: Karl Wirth Labels: P4_VERIFY Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50598) Add support of running JTH with custom WAR
Title: Message Title Oleg Nenashev commented on JENKINS-50598 Re: Add support of running JTH with custom WAR Oliver Gondža In the current state I doubt there will be benefit for traditional flows. "Custom WAR packager" enables JTH testing with Bundled plugins/groovy scripts and offers fixes for some issues there (e.g. resolves conflicts between bundled plugins and test dependencies). So far I do not see ho these patches could help classic flows which do not bundle plugins or scripts. The proposed patches could be applied to detached plugins, probably. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50627) Custom WAR Packager - Support running PCT and ATH with Custom WAR Packager
Title: Message Title Oleg Nenashev commented on JENKINS-50627 Re: Custom WAR Packager - Support running PCT and ATH with Custom WAR Packager So far ATH works OOTB, but PCT hits some issues Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50627) Custom WAR Packager - Support running PCT and ATH with Custom WAR Packager
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50627 Custom WAR Packager - Support running PCT and ATH with Custom WAR Packager Change By: Oleg Nenashev Component/s: plugin-compat-tester Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50627) Custom WAR Packager - Support running PCT and ATH with Custom WAR Packager
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50627 Custom WAR Packager - Support running PCT and ATH with Custom WAR Packager Change By: Oleg Nenashev Idea: Enable flow with PCT/ATH for a custom WAR package.Example of the demo flow with Jenkinsfile: https://github.com/oleg-nenashev/jenkins-custom-war-packager-ci-demo Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50626) PCT "-mavenProperties" argument does nothing
Title: Message Title Oleg Nenashev started work on JENKINS-50626 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50627) Custom WAR Packager - Support running PCT and ATH with Custom WAR Packager
Title: Message Title Oleg Nenashev started work on JENKINS-50627 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50629) PCT Docker Image should support passing custom Maven Options
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50629 PCT Docker Image should support passing custom Maven Options Issue Type: New Feature Assignee: Unassigned Components: plugin-compat-tester Created: 2018-04-06 12:41 Priority: Minor Reporter: Oleg Nenashev Currently the Docker Image does not allow passing custom Maven Options to the PCT Run. It would be great to have such option Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50630) Allow passing extra Maven Properties to PCT as string
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50630 Allow passing extra Maven Properties to PCT as string Issue Type: New Feature Assignee: Unassigned Components: plugin-compat-tester Created: 2018-04-06 12:56 Priority: Minor Reporter: Oleg Nenashev Currently PCT supports only property files with property definitions. It would be great to support passing extra options just as a string Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50630) Allow passing extra Maven Properties to PCT as string
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-50630 Allow passing extra Maven Properties to PCT as string Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50631) provideXslReport option is never passed to the PCT Library
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-50631 provideXslReport option is never passed to the PCT Library Issue Type: New Feature Assignee: Unassigned Components: plugin-compat-tester Created: 2018-04-06 12:58 Priority: Minor Reporter: Oleg Nenashev Just noticed it during the fixes for PCT support in JENKINS-50630. "serProvideXslReport()" in PluginCompatTesterConfig is never invoked, so I assume it's not properly propagated from CLI Add Comment This message was sent
[JIRA] (JENKINS-49967) Expose the ability to use an existing p4 client (workspace)
Title: Message Title Paul Allen commented on JENKINS-49967 Re: Expose the ability to use an existing p4 client (workspace) I'm not sure it is possible to fix as the Perforce client root is tightly coupled to the Jenkins workspace root. Are you able to remaining at the workspace root and use Perforce Depot, Client or relative Local syntax for the p4groovy operations. e.g. Local syntax: "p4 change -m1 sub2/..." Client syntax: "p4 change -m1 //client_name/sub2/..." Depot syntax: "p4 change -m1 //depot/projectX/sub2/..." Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50623) Build trigger using SVN is getting error in URL
Title: Message Title Priyanga G updated an issue Jenkins / JENKINS-50623 Build trigger using SVN is getting error in URL Change By: Priyanga G I am triggering job in Jenkins using post-commit-hook in svn.my jenkins url is:[http://priyanga:07a66fcd8261dd011c8eeba76eeed1d9@localhost:8080/job/FORD/build?token=TOKEN_NAME& amp; cause=svn-post-commit] I am checking the changes in svn using python.[^post-commit-hook-error.txt] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50631) provideXslReport option is never passed to the PCT Library
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50631 provideXslReport option is never passed to the PCT Library Change By: Oleg Nenashev Labels: newbie-friendly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50631) provideXslReport option is never passed to the PCT Library
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50631 provideXslReport option is never passed to the PCT Library Change By: Oleg Nenashev Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17488) java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult
Title: Message Title Sverre Moe commented on JENKINS-17488 Re: java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult We have this problem also. A slightly different stack trace looks like problem is relatated to BlueOcean Running Jenkins 2.114 BlueOcean 1.4.2 TAP Plugin 2.2.1 step([$class: "TapPublisher", testResults: "test-suite.log"]) Mar 08, 2018 1:40:50 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: Error while serving https://build-ci.company.com:8443/view/systems/job/packageA/job/master/tapResults/graph java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:237) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:214) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain
[JIRA] (JENKINS-50624) Rework the custom plugins builds hack to make it easier to add/remove a plugin
Title: Message Title Baptiste Mathus updated JENKINS-50624 Jenkins / JENKINS-50624 Rework the custom plugins builds hack to make it easier to add/remove a plugin Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50632) JEP-200 - Refusing to marshal org.apache.maven.model
Title: Message Title Test User created an issue Jenkins / JENKINS-50632 JEP-200 - Refusing to marshal org.apache.maven.model Issue Type: Bug Assignee: Unassigned Components: workflow-support-plugin Created: 2018-04-06 13:43 Environment: Jenkins 2.114, Pipeline: Supporting APIs 2.18 Labels: JEP-200 Priority: Major Reporter: Test User After update to latest Jenkins version I'm getting this errors: Apr 06, 2018 7:26:37 AM org.jenkinsci.plugins.workflow.cps.CpsFlowExecution maybeAutoPersistNode WARNING: Attempt to persist triggered IOException for node 24 java.io.IOException: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.workflow.support.storage.SimpleXStreamFlowNodeStorage$Tag#actions for class org.jenkinsci.plugins.workflow.support.storage.SimpleXStreamFlowNodeStorage$Tag at hudson.XmlFile.write(XmlFile.java:200) at org.jenkinsci.plugins.workflow.support.PipelineIOUtils.writeByXStream(PipelineIOUtils.java:30) at org.jenkinsci.plugins.workflow.support.storage.SimpleXStreamFlowNodeStorage.writeNode(SimpleXStreamFlowNodeStorage.java:182) at org.jenkinsci.plugins.workflow.support.storage.SimpleXStreamFlowNodeStorage.flushNode(SimpleXStreamFlowNodeStorage.java:151) at org.jenkinsci.plugins.workflow.support.storage.SimpleXStreamFlowNodeStorage.autopersist(SimpleXStreamFlowNodeStorage.java:136) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$TimingFlowNo
[JIRA] (JENKINS-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title R. Tyler Croy commented on JENKINS-50405 Re: runATH leads to deadlock of resource consumption for core PR builds I believe this is safe to close up now Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title Raul Arabaolaza updated JENKINS-50405 Jenkins / JENKINS-50405 runATH leads to deadlock of resource consumption for core PR builds Change By: Raul Arabaolaza Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50633) JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
Title: Message Title Test User created an issue Jenkins / JENKINS-50633 JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2018-04-06 13:53 Environment: Jenkins 2.114, Maven Integration plugin 3.1.2 Labels: JEP-200 Priority: Major Reporter: Test User Errors after update to latest Jenkins version: WARNING: org.apache.maven.model.Model in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ WARNING: org.apache.maven.model.DistributionManagement in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ WARNING: org.apache.maven.model.Dependency in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ WARNING: org.apache.maven.model.Build in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ WARNING: org.apache.maven.model.DeploymentRepository in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/cl
[JIRA] (JENKINS-50633) JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
Title: Message Title
Test User updated an issue
Jenkins / JENKINS-50633
JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
Change By:
Test User
Errors after update to latest Jenkins version:{noformat}WARNING: org.apache.maven.model.Model in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.DistributionManagement in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.Dependency in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.Build in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.DeploymentRepository in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.Plugin in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.PluginExecution in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/{noformat} {noformat}WARNING: org.apache.maven.model.Model in file:/var/lib/jenkins/plugins/pipeline-utility-steps/WEB-INF/lib/maven-model-3.3.9.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.DistributionManagement in file:/var/lib/jenkins/plugins/pipeline-utility-steps/WEB-INF/lib/maven-model-3.3.9.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.Plugin in file:/var/lib/jenkins/plugins/pipeline-utility-steps/WEB-INF/lib/maven-model-3.3.9.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/{noformat}
[JIRA] (JENKINS-50633) JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
Title: Message Title Test User updated an issue Jenkins / JENKINS-50633 JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting Change By: Test User Environment: Jenkins 2.114, Maven Integration plugin 3.1.2 , Pipeline Utility Steps 2.0.2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50633) JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
Title: Message Title Test User updated an issue Jenkins / JENKINS-50633 JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting Change By: Test User Component/s: pipeline-utility-steps-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50633) JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
Title: Message Title
Test User updated an issue
Jenkins / JENKINS-50633
JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
Change By:
Test User
Errors after update to latest Jenkins version:{noformat}WARNING: org.apache.maven.model.Model in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.DistributionManagement in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.Dependency in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.Build in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.DeploymentRepository in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.Plugin in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.PluginExecution in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ WARNING: org.apache.maven.model.Exclusion in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.Parent in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.codehaus.plexus.util.xml.Xpp3Dom in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/plexus-utils-3.0.24.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.Resource in file:/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-model-3.1.0.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ {noformat}{noformat}WARNING: org.apache.maven.model.Model in file:/var/lib/jenkins/plugins/pipeline-utility-steps/WEB-INF/lib/maven-model-3.3.9.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.DistributionManagement in file:/var/lib/jenkins/plugins/pipeline-utility-steps/WEB-INF/lib/maven-model-3.3.9.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/WARNING: org.apache.maven.model.Plugin in file:/var/lib/jenkins/plugins/pipeline-utility-steps/WEB-INF/lib/maven-model-3.3.9.jar might be da
