[JIRA] (JENKINS-49757) Git plugin calls fetch twice for a single job
Title: Message Title
Kaiyuan Zhao commented on JENKINS-49757
Re: Git plugin calls fetch twice for a single job
Mark Waite First of all, my job is using Gerrit Trigger. When my Jenkinsfile is like
def scm = [
$class : 'GitSCM',
branches : [[name: '*/master']],
doGenerateSubmoduleConfigurations: false,
extensions : [
[$class: 'WipeWorkspace'],
[$class: 'CloneOption', depth: 2, honorRefspec: true, noTags: true, reference: '', shallow: true, timeout: 10],
[$class: 'BuildChooserSetting', buildChooser: [$class: 'GerritTriggerBuildChooser']]
],
submoduleCfg : [],
userRemoteConfigs: [
[
credentialsId: 'hide',
refspec : '$GERRIT_REFSPEC',
url : 'hide'
]
]
]
pipeline {
agent {
node {
label 'gerrit'
}
}
options {
skipDefaultCheckout true
}
stages {
stage('CheckOut') {
steps {
checkout(scm)
}
}
}
}
The console log
Wiping out workspace first.
Cloning the remote Git repository
Using shallow clone
shallow clone depth 2
Avoid fetching tags
Honoring refspec on initial clone
Cloning repository hide
> git init hide # timeout=10
Fetching upstream changes from hide
> git --version # timeout=10
using GIT_SSH to set credentials
> git fetch --no-tags --progress hide $GERRIT_REFSPEC --depth=2 # timeout=10
> git config remote.origin.url hide # timeout=10
> git config --add remote.origin.fetch $GERRIT_REFSPEC # timeout=10
> git config remote.origin.url hide # timeout=10
Fetching upstream changes from hide
using GIT_SSH to set credentials
> git fetch --no-tags --progress hide refs/changes/64/4264/7 --depth=2 # timeout=10
> git rev-parse 4b5226960edd4551bbafc058db4afc0e69bd103f^{commit} # timeout=10
Checking out Revision 4b5226960edd4551bbafc058db4afc0e69bd103f (refs/changes/64/4264/7)
> git config core.sparsecheckout # timeout=10
> git checkout -f 4b5226960edd4551bbafc058db4afc0e69bd103f
Commit message: "hide"
> git rev-parse FETCH_HEAD^{commit} # timeout=10
> git rev-list --no-walk a1323feb6fa57ce13c87a5fd6886b14aa3f75dab # timeout=10
Fetch twice and the first fetch cannot recognize $GERRIT_REFSPEC Then I changed my Jenkinsfile like
def scm = [
$class : 'GitSCM',
branches : [[name: '*/master']],
doGenerateSubmoduleConfigurations: false,
extensions : [
[$class: 'CloneOption', depth: 2, honorRefspec: true, noTags: true, reference: '', shallow: true, timeout: 10],
[$class: 'BuildChooser
[JIRA] (JENKINS-51237) Errors logged to C:\Program Files (x86)\Jenkins\workspace\test1\.git\lfs\logs\20180510T102945.2372387.log
Title: Message Title
swetha huded created an issue
Jenkins / JENKINS-51237
Errors logged to C:\Program Files (x86)\Jenkins\workspace\test1\.git\lfs\logs\20180510T102945.2372387.log
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
20180510T102945.2372387.log
Components:
core
Created:
2018-05-10 06:49
Environment:
Operating System : Windows 10 JRE/JDK vendors and versions : jdk1.8.0_161 Jenkins and plugin versions : jenkins-2.107.2 (Running directly no Tomcat used)
Priority:
Critical
Reporter:
swetha huded
Unable to clone the binary files(.so) from the Git. Started by user swetha Building in workspace C:\Program Files (x86)\Jenkins\workspace\test1 > C:\Program Files (x86)\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url https://github.qualcomm.com/ProdTools/CTA.git
timeout=10 Fetching upstream changes from https://github.qualcomm.com/ProdTools/CTA.git > C:\Program Files (x86)\Git\cmd\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials > C:\Program Files (x86)\Git\cmd\git.exe fetch --tags --progress https://github.qualcomm.com/ProdTools/CTA.git +refs/heads/:refs/remotes/origin/ > C:\Program Files (x86)\Git\cmd\git.exe rev-parse "refs/remotes/origin/master^{commit}" # timeout=10 > C:\Program Files (x86)\Git\cmd\git.exe rev-parse "refs/remotes/origin/origin/master^{commit}" # timeout=10 Checking out Rev
[JIRA] (JENKINS-51142) Jenkins multijob fails when slave reboots
Title: Message Title Deb Das assigned an issue to Peter Kranz Jenkins / JENKINS-51142 Jenkins multijob fails when slave reboots Change By: Deb Das Assignee: Peter Kranz 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-50111) HP ALM Plugin - allow adding a custom result file in the External Test Type
Title: Message Title Roy Lu started work on JENKINS-50111 Change By: Roy Lu 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-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title David van Laatum commented on JENKINS-51221 Re: Email-Ext groovy.template does show wrong changes what does the build page show for changes. If it doesn't agree with whats in the email then its a bug otherwise its either correct or a bug in the SCM api 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title David van Laatum commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients Determining who is the developer of a build is done by jenkins and the SCM api not emailext. If you look at the build details and you see no changelog emailext has no hope 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-51233) Jenkins plugin: Export virtual services from the project to one folder
Title: Message Title michael jing commented on JENKINS-51233 Re: Jenkins plugin: Export virtual services from the project to one folder fixed by: https://github.com/jenkinsci/hpe-application-automation-tools-plugin/pull/76 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-51236) SVConfigurator: Allow to export to vproja
Title: Message Title michael jing commented on JENKINS-51236 Re: SVConfigurator: Allow to export to vproja fixed by: https://github.com/jenkinsci/hpe-application-automation-tools-plugin/pull/76 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-50663) Deadlock on jenkins startup
Title: Message Title michael jing resolved as Fixed Jenkins / JENKINS-50663 Deadlock on jenkins startup Change By: michael jing Status: Open Resolved Assignee: michael jing 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-51236) SVConfigurator: Allow to export to vproja
Title: Message Title michael jing created an issue Jenkins / JENKINS-51236 SVConfigurator: Allow to export to vproja Issue Type: New Feature Assignee: michael jing Components: hp-application-automation-tools-plugin Created: 2018-05-10 05:35 Labels: ServiceVirtualization Priority: Critical Reporter: michael jing User would like to be able to export to vproja (archive) format from SVConfigurator, so he can easily deploy it via SVM. Add Comment
[JIRA] (JENKINS-51235) Come up with YAML definition samples
Title: Message Title Abhishek Gautam created an issue Jenkins / JENKINS-51235 Come up with YAML definition samples Issue Type: Task Assignee: Abhishek Gautam Components: simple-pull-request-job-plugin Created: 2018-05-10 05:33 Priority: Major Reporter: Abhishek Gautam Study Pipeline examples, come up with at least 4 YAML definition samples. Create a pull request with examples to the project’s GitHub repo (in README.md) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73
[JIRA] (JENKINS-51233) Jenkins plugin: Export virtual services from the project to one folder
Title: Message Title michael jing resolved as Fixed Method ExportProcessor.process() has new parameter "project". If it is set and "svc" is null, then it exports all services from the project into one project folder. Jenkins / JENKINS-51233 Jenkins plugin: Export virtual services from the project to one folder Change By: michael jing Status: In Progress 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 receivi
[JIRA] (JENKINS-51233) Jenkins plugin: Export virtual services from the project to one folder
Title: Message Title michael jing started work on JENKINS-51233 Change By: michael jing 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-51234) Setup a sample Jenkins plugin for Simple PR Job Plugin
Title: Message Title Abhishek Gautam created an issue Jenkins / JENKINS-51234 Setup a sample Jenkins plugin for Simple PR Job Plugin Issue Type: Task Assignee: Abhishek Gautam Components: simple-pull-request-job-plugin Created: 2018-05-10 05:30 Priority: Minor Reporter: Abhishek Gautam Setup a sample Jenkins plugin for Simple PR Job Plugin and create a Jenkins file for it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51233) Jenkins plugin: Export virtual services from the project to one folder
Title: Message Title michael jing created an issue Jenkins / JENKINS-51233 Jenkins plugin: Export virtual services from the project to one folder Issue Type: Bug Assignee: michael jing Components: hp-application-automation-tools-plugin Created: 2018-05-10 05:29 Labels: ServiceVirtualization Priority: Critical Reporter: michael jing This requirement makes sense, but it will not be easy. SVConfigurator is able to export one or all services. Export of services defined by project file has 2 steps: 1) getting list of services from project file 2) exporting all services one by one. And it is not able to merge services from one project into one folder in two separate SVConfigurator calls. It needs to add ability of SVConfigurator to export services by project (as in Jenkins plugin) or accept multiple services to export command. Add Comment
[JIRA] (JENKINS-42398) Build fails for empty project
Title: Message Title Alexander Melnichuk commented on JENKINS-42398 Re: Build fails for empty project Resolved by adding gradle dependencies: jenkinsTest 'org.jenkins-ci.main:jenkins-test-harness:2.8@jar', 'org.eclipse.jetty:jetty-webapp:9.2.24.v20180105@jar', 'org.eclipse.jetty:jetty-security:9.2.24.v20180105@jar' 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-49757) Git plugin calls fetch twice for a single job
Title: Message Title Mark Waite commented on JENKINS-49757 Re: Git plugin calls fetch twice for a single job Kaiyuan Zhao I believe you are seeing a different condition. The `sh 'git iniit'` initializes an empty git repository in the workspace. The `checkout(scm)` step likely erases the newly created empty git repository and creates a new git repository populated with the results of fetching changes from the remote server. The deleteDir() step removes the workspace contents at the end. As far as I understand declarative Pipeline, it will perform the initial checkout implicitly (unless you'v added the skipDefaultCheckout property), then it sees your `checkout scm` and does it again. 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-49757) Git plugin calls fetch twice for a single job
Title: Message Title
Kaiyuan Zhao commented on JENKINS-49757
Re: Git plugin calls fetch twice for a single job
Facing same issue when using gerrit trigger. My solution is using pipeline job like below
stage('CheckOut') {
steps {
sh "git init"
checkout(scm)
}
}
post {
cleanup {
deleteDir()
}
}
Init git repo first will skip clone step. Do not use WipeWorkspace in scm step, clean workspace in post closure
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-50492) Thread blocked
Title: Message Title sun pengshuai assigned an issue to Jesse Glick Jenkins / JENKINS-50492 Thread blocked Change By: sun pengshuai Assignee: Jesse Glick 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-51232) Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files.
Title: Message Title
johann ko created an issue
Jenkins / JENKINS-51232
Moving files from Nexus Maven Repository to Jenkins using pipeline withMaven plugins incorrectly unnecessarily references Parent POM when there isn't one in my files.
Issue Type:
Task
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2018-05-10 02:06
Environment:
Apache Maven 3.0.5, OS 'linux' Version "3.10.0-693.11.6.el7_4.x86_64/jre, Maven-dependency-plugin:3.1.0
Labels:
plugin
Priority:
Minor
Reporter:
johann ko
Context: Trying to move .zip file from Nexus Maven repository using Jenkins' withMaven plugin. However, Jenkins incorrectly references Parent POM file when there isn't a POM file in the repository. Error Message (With redacted URL): Failed to execute goal org.apache.maven.plugins:maven-dependency- plugin:3.1.0:get (default-cli) on project standalone-pom: Couldn't download artifact: Failed to read artifact descriptor for com.company.app.apigee:template-api:zip:dev:LATEST: Could not transfer artifact com.company.app.apigee:parent-pom:pom:1.0 from/to maven-snapshots (http://app-apigw-devops-nexus.srv.company:8081/repository/maven- snapshots/): Failed to transfer file: http://app-apigw-devops- nexus.srv.company:8081/repository/maven- snapshots/com/company/app/apigee/parent-pom/1.0/parent-pom-1.0.pom. Return code is: 400 , ReasonPhrase:Repository version policy: SNAPSHOT does not allow version: 1.0. -> [Help 1] Input to Jenkins' Pipeline configuration: {{node { stage('Deploy from Nexus') { withMaven(maven: 'M3') { sh 'mvn org.apache.maven.plugins:maven-dependency-plugi
[JIRA] (JENKINS-49532) autogenerated keystore should not be kept in temp directory
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-49532 Re: autogenerated keystore should not be kept in temp directory [~qwrrty] I am testing some stuff to save the configuration of the keystore ASAP I finished I will release an close this Jira. 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-49532) autogenerated keystore should not be kept in temp directory
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-49532 Re: autogenerated keystore should not be kept in temp directory Tim Pierce I testing some stuff to save the configuration of the keystore ASAP I finished I will release an close this Jira. 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-39143) Stage view disappears after restarting jenkins
Title: Message Title Sam Van Oort commented on JENKINS-39143 Re: Stage view disappears after restarting jenkins Jared Kauppila This is actually an issue with persisted data being lost. You likely will have it fixed by updating workflow-cps and workflow-job plugins 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-50829) Automated test for stopping running jobs in Blue Ocean
Title: Message Title Karl Shultz resolved as Done Merged 1724. Jenkins / JENKINS-50829 Automated test for stopping running jobs in Blue Ocean Change By: Karl Shultz Status: In Progress Resolved Resolution: Done 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-51229) Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information
Title: Message Title Oleg Nenashev commented on JENKINS-51229 Re: Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information BuildDiscatder is an extension point, so it can be implemented in a plugin. Also https://github.com/jenkinsci/buildrotator-plugin which may address this use-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-51229) Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51229 Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information Change By: Oleg Nenashev Component/s: plugin-proposals 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-50216) Google Auth Plugin is incompatible with Jenkins 2.102+
Title: Message Title Oleg Nenashev updated JENKINS-50216 The fix has been released in 0.6 Jenkins / JENKINS-50216 Google Auth Plugin is incompatible with Jenkins 2.102+ Change By: Oleg Nenashev 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-51046) Tool to incrementalify POM
Title: Message Title Jesse Glick commented on JENKINS-51046 Re: Tool to incrementalify POM First I am checking whether one of the more onerous requirements, the need to edit .gitignore, can be skipped; progress in plugin-pom PR 105. 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-50486) Pipeline shared library plugin doesn't allow you to select a configured Mercurial installation
Title: Message Title Darcy Willington updated an issue Jenkins / JENKINS-50486 Pipeline shared library plugin doesn't allow you to select a configured Mercurial installation Change By: Darcy Willington Attachment: sc.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-50486) Pipeline shared library plugin doesn't allow you to select a configured Mercurial installation
Title: Message Title Darcy Willington commented on JENKINS-50486 Re: Pipeline shared library plugin doesn't allow you to select a configured Mercurial installation Based on the help information, there is no mercurial plugin yet for Modern SCM. Legacy SCM worked for me. 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-51211) FSTrigger Polling not working because of SecurityException
Title: Message Title Oleg Nenashev commented on JENKINS-51211 Re: FSTrigger Polling not working because of SecurityException I confirm the issue. Ideally XTrigger Lib should be refactored to the plugin so that the classes get whitelisted automatically. CC Chris Lindee who was considering taking ownership of the lib. I will add the issue to https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200, but I have no plans to work on it so far 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-51211) FSTrigger Polling not working because of SecurityException
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-51211 FSTrigger Polling not working because of SecurityException Change By: Oleg Nenashev Assignee: Gregory Boissinot 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 Oleg Nenashev commented on JENKINS-50633 Re: JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting Fix released in 2.1.0 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 Oleg Nenashev updated JENKINS-50633 Jenkins / JENKINS-50633 JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting Change By: Oleg Nenashev 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-51046) Tool to incrementalify POM
Title: Message Title Jesse Glick started work on JENKINS-51046 Change By: Jesse Glick 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-38825) MultiJob does not build Pipeline jobs
Title: Message Title Ximei Zhang commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs In the build step, i call builds on other project. 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-51231) Add an ability to handle Aborted builds
Title: Message Title Igor Sarkisov created an issue Jenkins / JENKINS-51231 Add an ability to handle Aborted builds Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger-plugin Created: 2018-05-09 19:47 Priority: Major Reporter: Igor Sarkisov We started using 'Build Current Patches Only' option to have non-current patchset builds cancelled in Jenkins. However, the side effect of using this option is the fact that Aborted builds are handled just like Failed builds, we get -1 Verified for aborted builds. This functionality creates noise and confusion, so we would like to be able to handle Gerrit Reporting Values for Aborted builds. It would be nice if we can configure Aborted reporting values just like we can Started, Successful, Failed, Unstable, Not Built builds (ie be able to set 0, -1, 1 for aborted builds) Add Comment
[JIRA] (JENKINS-51227) Quiet period should be configured from declarative pipelines
Title: Message Title Jesse Glick commented on JENKINS-51227 Re: Quiet period should be configured from declarative pipelines Nothing to do with Declarative vs. Scripted, only multibranch vs. standalone. 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-51227) Quiet period should be configured from declarative pipelines
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51227 Quiet period should be configured from declarative pipelines Change By: Jesse Glick Component/s: workflow-job-plugin Component/s: pipeline 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-10383) platformlabeler plugin doesn't detect 64-bit windows
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-10383 platformlabeler plugin doesn't detect 64-bit windows Change By: Mark Waite Status: Resolved Closed 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-13144) platformlabeler link in Manage Plugins goes to hudson-ci.org wiki
Title: Message Title Mark Waite resolved as Fixed Fixed in platformlabeler plugin 2.0 released May 2018. Jenkins / JENKINS-13144 platformlabeler link in Manage Plugins goes to hudson-ci.org wiki Change By: Mark Waite Status: Open 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.goog
[JIRA] (JENKINS-7986) platformlabeler crashes on OpenSUSE
Title: Message Title Mark Waite closed an issue as Incomplete Jenkins / JENKINS-7986 platformlabeler crashes on OpenSUSE Change By: Mark Waite Status: Resolved Closed 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-13144) platformlabeler link in Manage Plugins goes to hudson-ci.org wiki
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-13144 platformlabeler link in Manage Plugins goes to hudson-ci.org wiki Change By: Mark Waite Status: Resolved Closed 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-51223) remoting processing of "no_proxy" env var needs improvement
Title: Message Title Gabe Montero commented on JENKINS-51223 Re: remoting processing of "no_proxy" env var needs improvement Provided https://github.com/jenkinsci/remoting/pull/269 as a proposal for addressing 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-38825) MultiJob does not build Pipeline jobs
Title: Message Title Balázs Bábos commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs Hm. And how do you call the pipeline from the freestyle job actually? You are not using a post build step, are you? 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-51226) debian package must depend on *some* jre
Title: Message Title vila updated an issue Jenkins / JENKINS-51226 debian package must depend on *some* jre Change By: vila While trying to test 2.107.3 I ran into the debian package not depending on any jre anymore. I.e.: 1) apt-get install jenkins fails, jenkins can't be started because java NotFound2) apt-get install default-jre-headless jenkins fails, systemd tries to start jenkins before installing the jre. Requiring users to do 'apt-get install default-jre-headless' then 'apt-get install jenkins' is not the way package dependencies should work ? IMHO. 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-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title NetAppBlueDevil commented on JENKINS-33843 Re: It's not possible to disable/uninstall optional dependencies +1 Trying to simplify by removing unneeded plugins is just no possible any more. I don't even know why the Green Balls plugin has the LDAP plugin listed as an optional dependency, but it means I can't drop the LDAP one. 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-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title NetAppBlueDevil edited a comment on JENKINS-33843 Re: It's not possible to disable/uninstall optional dependencies +1 Trying to simplify by removing unneeded plugins is just no not possible any more . I don't even know why the Green Balls plugin has the LDAP plugin listed as an optional dependency, but it means I can't drop the LDAP one. 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-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Title: Message Title
Michael Haskelsky updated an issue
Jenkins / JENKINS-49131
Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Change By:
Michael Haskelsky
1. If one (or more) parallel stage does not run is skipped due to "when" condition in declarative pipeline, Blue Ocean UI does not show up running steps inside active stages until all steps in all active stages are finished.2. In such case If one of steps is "input" step, there is no option to "Proceed" or "Abort" using Blue Ocean UI since no steps are shown up. It can be done only using regular UI or console output.3. If all stages are active, steps are shown up, but it is impossible to switch between output of "Stage A" to "Stage B" and see steps of "Stage B" until all steps in "Stage A" are finished.Example:{code:java}// code placeholderpipeline { agent any parameters { choice(choices: 'NO\nEVEN\nODD', description: '', name: 'A') choice(choices: 'NO\nEVEN\nODD', description: '', name: 'B') } environment { A = "${params.A}" B = "${params.B}" } stages { stage('ParallelStages') { parallel {stage('Stage A') { when { anyOf { environment name: 'A', value: 'EVEN' environment name: 'A', value: 'ODD' } }steps { echo "Running Stage A" sleep 10 echo "Finishing Stage A"} } stage('Stage B') {when { anyOf { environment name: 'B', value: 'EVEN' environment name: 'B', value: 'ODD' }}steps { echo "Running Stage B" sleep 30 echo "Finishing Stage B" }} } } }}{code}
Add Comment
[JIRA] (JENKINS-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Title: Message Title Michael Haskelsky assigned an issue to Unassigned Jenkins / JENKINS-49131 Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition Change By: Michael Haskelsky Assignee: Michael Haskelsky 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-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Title: Message Title Michael Haskelsky assigned an issue to Michael Haskelsky Jenkins / JENKINS-49131 Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition Change By: Michael Haskelsky Assignee: Michael Haskelsky 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-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
Title: Message Title Michael Haskelsky updated an issue Jenkins / JENKINS-49131 Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition Change By: Michael Haskelsky Summary: Steps are not shown up in Blue Ocean when one of parallel stages is not active skipped due to "when" condition 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-51230) Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages
Title: Message Title Michael Haskelsky updated an issue Jenkins / JENKINS-51230 Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages Change By: Michael Haskelsky After upgrading from 1.4.2 to 1.5.0 Blue Ocean UI gets stuck while running a big declarative pipeline job.The pipeline job has 4 stages running in parallel. Each stage contains 28 steps. 8 steps (out of 28) in each stage launch other pipeline job.When execution reaches somewhere about step 15-20, UI navigation between parallel stages becomes slower and slower, and at some point of time UI gets stuck for tens seconds and even minutes, so it is impossible to use it at all.I suppose that the issue can be related to the new feature [ UI for downstream jobs launched with 'build' step |https://issues.jenkins-ci.org/browse/JENKINS-38339] Downgrading to Blue Ocean 1.4.2 resolved the issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to
[JIRA] (JENKINS-51230) Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages
Title: Message Title Michael Haskelsky updated an issue Jenkins / JENKINS-51230 Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages Change By: Michael Haskelsky After upgrading from 1.4.2 to 1.5.0 Blue Ocean UI gets stuck while running a big declarative pipeline job.The pipeline job has 4 stages running in parallel. Each stage contains 28 steps. 8 steps (out of 28) in each stage launch other pipeline job.When execution reaches somewhere about step 15-20, UI navigation between parallel stages becomes slower and slower, and at some point of time UI gets stuck for tens seconds and even minutes, so it is impossible to use it at all.I suppose that the issue can be related to the new feature [ UI for downstream jobs launched with 'build' step |https://issues.jenkins-ci.org/browse/JENKINS-38339] Downgrading to Blue Ocean 1.4.2 resolved the issue Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed
[JIRA] (JENKINS-51230) Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages
Title: Message Title Michael Haskelsky created an issue Jenkins / JENKINS-51230 Blue Ocean UI 1.5.0 gets stuck while running a big Pipeline job with parallel stages Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-05-09 17:07 Environment: Jenkins 2.107.2 Blue Ocean 1.5.0 Windows 2012 Labels: blueocean parallel stuck Priority: Critical Reporter: Michael Haskelsky After upgrading from 1.4.2 to 1.5.0 Blue Ocean UI gets stuck while running a big pipeline job. The pipeline job has 4 stages running in parallel. Each stage contains 28 steps. 8 steps (out of 28) in each stage launch other pipeline job. When execution reaches somewhere about step 15-20, UI navigation between parallel stages becomes slower and slower, and at some point of time UI gets stuck for tens seconds and even minutes, so it is impossible to use it at all. I suppose that the issue can be related to the new feature UI for downstream jobs launched with 'build' step Downgrading to Blue Ocean 1.4.2 resolved the issue
[JIRA] (JENKINS-51203) Slave.setNodeProperties is unreliable and inefficient
Title: Message Title
pjdarton updated an issue
Jenkins / JENKINS-51203
Slave.setNodeProperties is unreliable and inefficient
Change By:
pjdarton
TL;DR: {{Slave.setNodeProperties}} is unreliable because it's doing stuff it shouldn't. When a cloud plugin's {{Cloud.provision}} method gets called, the plugin code has to create one or more instances of {{hudson.model.Slave}} and return them to Jenkins. Prior to returning them to Jenkins, it has to populate those instances with all the data required. This can (e.g. in the case of the docker-plugin) include a call to {{Slave.setNodeProperties}}.{{Slave.setNodeProperties}} calls {{nodeProperties.replaceBy()}}. {{nodeProperties}} are a {{hudson.util.PersistedList}} whose owner is {{Jenkins.getInstance().getNodesObject()}} (see [Slave.java line 150|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Slave.java#L150]), and {{PersistedList.replaceBy}} calls {{PersistedList.onModified()}} which then calls [{{Nodes.save()}}|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Nodes.java#L277] which writes all nodes to disk (which is a non-trivial operation that isn't thread-safe).i.e. At present, any change to the node properties for any slave (even those not persisted to disk yet) causes all slaves to get (re-)persisted to disk.This is very inefficient when there are a lot of slaves - it should, at most, persist just the slave in question, and in the case where a slave doesn't belong to anyone yet, it shouldn't get persisted at all. Worse still, when there's more than one slave being provisioned at a time (e.g. on a busy Jenkins server with a fast cloud), the persistence functionality can throw an exception and cause the entire operation to fail:{noformat}java.nio.file.NoSuchFileException: /var/jenkins_home/nodes/docker-22f02f15d4988b/atomic3648298142656815004tmp at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409) at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) at java.nio.file.Files.move(Files.java:1395) at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:206) at hudson.XmlFile.write(XmlFile.java:198) at jenkins.model.Nodes.save(Nodes.java:274) at hudson.util.PersistedList.onModified(PersistedList.java:173) at hudson.util.PersistedList.replaceBy(PersistedList.java:85) at hudson.model.Slave.setNodeProperties(Slave.java:299) at ...{noformat} What should happen instead is that changes to {{Slave.nodeProperties}} should only cause those changes to be persisted if the slave itself is persisted. Changes to Slaves that are not (yet) part of Jenkins' list of Nodes should not cause a re-save of the configuration to disk. e.g. much like the logic done in [{{Node.save()}}|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/mode
[JIRA] (JENKINS-51203) Slave.setNodeProperties is unreliable and inefficient
Title: Message Title
pjdarton updated an issue
Jenkins / JENKINS-51203
Slave.setNodeProperties is unreliable and inefficient
Change By:
pjdarton
TL;DR: {{Slave.setNodeProperties}} is unreliable because it's doing stuff it shouldn't. When a cloud plugin's {{Cloud.provision}} method gets called, the plugin code has to create one or more instances of {{hudson.model.Slave}} and return them to Jenkins. Prior to returning them to Jenkins, it has to populate those instances with all the data required. This can (e.g. in the case of the docker-plugin) include a call to {{Slave.setNodeProperties}}.{{Slave.setNodeProperties}} calls {{nodeProperties.replaceBy()}}. {{nodeProperties}} are a {{hudson.util.PersistedList}} whose owner is {{Jenkins.getInstance().getNodesObject()}} (see [Slave.java line 150|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Slave.java#L150]), and {{PersistedList.replaceBy}} calls {{PersistedList.onModified()}} which then calls [{{Nodes.save()}}|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Nodes.java#L277] which writes all nodes to disk (which is a non-trivial operation that isn't thread-safe).i.e. At present, any change to the node properties for any slave (even those not persisted to disk yet) causes all slaves to get (re-)persisted to disk.This is very inefficient when there are a lot of slaves - it should, at most, persist just the slave in question, and in the case where a slave doesn't belong to anyone yet, it shouldn't get persisted at all. Worse still, when there's more than one slave being provisioned at a time (e.g. on a busy Jenkins server with a fast cloud), the persistence functionality can throw an exception and cause the entire operation to fail:{noformat}java.nio.file.NoSuchFileException: /var/jenkins_home/nodes/docker-22f02f15d4988b/atomic3648298142656815004tmp at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409) at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) at java.nio.file.Files.move(Files.java:1395) at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:206) at hudson.XmlFile.write(XmlFile.java:198) at jenkins.model.Nodes.save(Nodes.java:274) at hudson.util.PersistedList.onModified(PersistedList.java:173) at hudson.util.PersistedList.replaceBy(PersistedList.java:85) at hudson.model.Slave.setNodeProperties(Slave.java:299) at ...{noformat} What should happen instead is that changes to {{Slave.nodeProperties}} should only cause those changes to be persisted if the slave itself is persisted. Changes to Slaves that are not (yet) part of Jenkins' list of Nodes should not cause a re-save of the configuration to disk. e.g. much like the logic done in [{{Node.save()}}|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/mode
[JIRA] (JENKINS-51229) Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information
Title: Message Title Thy Dai created an issue Jenkins / JENKINS-51229 Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information Issue Type: New Feature Assignee: Unassigned Attachments: consoleOutputOfBuild2withLogs.JPG, consoleOutputOfBuild2withoutLogs.JPG, consoleOutputOfBuildwithLogs.JPG, consoleOutputOfBuildwithoutLogs.JPG, job-view.JPG, numberOfBuilds.JPG, overviewOfBuild2withLogs.JPG, overviewOfBuild2withoutLogs.JPG, overviewOfBuildwithLogs.JPG, overviewOfBuildwithoutLogs.JPG Components: core Created: 2018-05-09 16:58 Priority: Minor Reporter: Thy Dai I've created a log discarder that acts similar to Jenkins' Log Rotation strategy to discard old builds. However, this log discarder will delete the logs for older builds, but does not delete build information such as when a build was started and how long it took for trend analysis. I'm willing to submit a pull request! This change will also mitigate the issue: https://issues.jenkins-ci.org/browse/JENKINS-48344 Add Com
[JIRA] (JENKINS-51203) Slave.setNodeProperties is unreliable and inefficient
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-51203 Slave.setNodeProperties is unreliable and inefficient Change By: pjdarton Environment: Jenkins with at least one cloud plugin Code that's dynamically- creating multiple Slave nodes , in parallel, that call setNodeProperties have nodeProperties . e.g. cloud plugins or pipelines running parallel jobs in dynamic slaves. 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-51228) Create Stapler integration tests
Title: Message Title Oleg Nenashev started work on JENKINS-51228 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-51228) Create Stapler integration tests
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-51228 Create Stapler integration tests Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-05-09 16:50 Priority: Minor Reporter: Oleg Nenashev Currently Jenkins is not tested during the build of Stapler, so we miss issues and handle them only when changes are proposed to the Jenkins core and integrated into Weekly. I propose to introduce some integration testing using the essentialsTest() framework we recently created Add Comment
[JIRA] (JENKINS-51203) Slave.setNodeProperties is unreliable and inefficient
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-51203 Slave.setNodeProperties is unreliable and inefficient Change By: pjdarton Summary: Slave.setNodeProperties causes spurious call to Nodes.save is unreliable and inefficient 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-51203) Slave.setNodeProperties causes spurious call to Nodes.save
Title: Message Title
pjdarton updated an issue
Jenkins / JENKINS-51203
Slave.setNodeProperties causes spurious call to Nodes.save
Change By:
pjdarton
TL;DR: {{Slave.setNodeProperties}} is unreliable because it's doing stuff it shouldn't. When a cloud plugin's {{Cloud.provision}} method gets called, the plugin code has to create one or more instances of {{hudson.model.Slave}} and return them to Jenkins.Prior to returning them to Jenkins, it has to populate those instances with all the data required. This can (e.g. in the case of the docker-plugin) include a call to {{Slave.setNodeProperties}}.{{Slave.setNodeProperties}} calls {{nodeProperties.replaceBy()}}. {{nodeProperties}} are a {{hudson.util.PersistedList}} whose owner is {{Jenkins.getInstance().getNodesObject()}} (see [Slave.java line 150|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Slave.java#L150]), and {{PersistedList.replaceBy}} calls {{PersistedList.onModified()}} which then calls [{{Nodes.save()}}|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Nodes.java#L277] which writes all nodes to disk (which is a non-trivial operation that isn't thread-safe ).i.e. At present, any change to the node properties for any slave (even those not persisted to disk yet) causes all slaves to get (re-) persisted to disk. This is very inefficient when there are a lot of slaves - it should, at most, persist just the slave in question, and in the case where a slave doesn't belong to anyone yet, it shouldn't get persisted at all.Worse still, when there's more than one slave being provisioned at a time ( quite easy e.g. on a busy Jenkins server with a fast cloud), the persistence functionality can throw an exception and cause the entire operation to fail:{ { noformat} java.nio.file.NoSuchFileException: /var/jenkins_home/nodes/docker-22f02f15d4988b/atomic3648298142656815004tmp at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409) at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) at java.nio.file.Files.move(Files.java:1395) at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:206) at hudson.XmlFile.write(XmlFile.java:198) at jenkins.model.Nodes.save(Nodes.java:274) at hudson.util.PersistedList.onModified(PersistedList.java:173) at hudson.util.PersistedList.replaceBy(PersistedList.java:85) at hudson.model.Slave.setNodeProperties(Slave.java:299) at ... {noformat } } What should happen instead is that changes to {{Slave.nodeProperties}} should only cause those changes to be persisted if the slave itself is persisted. Changes to Slaves that are not (yet) part of Jenkins' list of Nodes should not cause a re-save of the configuration to disk.e.g. much like the logic done in [{{Node.save()}}|https://github.com/jenkinsci/jenkins/blob/mas
[JIRA] (JENKINS-51203) Slave.setNodeProperties causes spurious call to Nodes.save
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-51203 Slave.setNodeProperties causes spurious call to Nodes.save Change By: pjdarton 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-51203) Slave.setNodeProperties causes spurious call to Nodes.save
Title: Message Title
pjdarton updated an issue
Jenkins / JENKINS-51203
Slave.setNodeProperties causes spurious call to Nodes.save
Change By:
pjdarton
When a cloud plugin's {{Cloud.provision}} method gets called, the plugin code has to create one or more instances of {{hudson.model.Slave}} and return them to Jenkins.Prior to returning them to Jenkins, it has to populate those instances with all the data required. This can (e.g. in the case of the docker-plugin) include a call to {{Slave.setNodeProperties}}.{{Slave.setNodeProperties}} calls {{nodeProperties.replaceBy()}}. {{nodeProperties}} are a {{hudson.util.PersistedList}} whose owner is {{Jenkins.getInstance().getNodesObject()}} (see [Slave.java line 150|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Slave.java#L150]), and {{PersistedList.replaceBy}} calls {{PersistedList.onModified()}} which then calls [{{Nodes.save()}}|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/Nodes.java#L277] which writes all nodes to disk (which is a non-trivial operation).i.e. At present, any change to the node properties for any slave (even those not persisted to disk yet) causes all slaves to get persisted to disk.This is very inefficient when there are a lot of slaves - it should, at most, persist just the slave in question, and in the case where a slave doesn't belong to anyone yet, it shouldn't get persisted at all. Worse still, when there's more than one slave being provisioned at a time (quite easy on a busy Jenkins server with a fast cloud), the persistence functionality can throw an exception and cause the entire operation to fail: {{java.nio.file.NoSuchFileException: /var/jenkins_home/nodes/docker-22f02f15d4988b/atomic3648298142656815004tmp at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409) at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262) at java.nio.file.Files.move(Files.java:1395) at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:206) at hudson.XmlFile.write(XmlFile.java:198) at jenkins.model.Nodes.save(Nodes.java:274) at hudson.util.PersistedList.onModified(PersistedList.java:173) at hudson.util.PersistedList.replaceBy(PersistedList.java:85) at hudson.model.Slave.setNodeProperties(Slave.java:299) at ...}} What should happen instead is that changes to {{Slave.nodeProperties}} should only cause those changes to be persisted if the slave itself is persisted. Changes to Slaves that are not (yet) part of Jenkins' list of Nodes should not cause a re-save of the configuration to disk.e.g. much like the logic done in [{{Node.save()}}|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Node.java#L131].FYI this was discovered while investigating the cause of numerous docker provisioning failures caused by
[JIRA] (JENKINS-51203) Slave.setNodeProperties causes spurious call to Nodes.save
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-51203 Slave.setNodeProperties causes spurious call to Nodes.save Change By: pjdarton Labels: performance robustness 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-38825) MultiJob does not build Pipeline jobs
Title: Message Title Ximei Zhang commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs Yeah pipeline job has no problem to get the param values from the freestyle 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-51219) Is Java 10 supported in Jenkins
Title: Message Title Oleg Nenashev resolved as Done Jenkins / JENKINS-51219 Is Java 10 supported in Jenkins Change By: Oleg Nenashev Status: Open Resolved Resolution: Done 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-51219) Is Java 10 supported in Jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-51219 Re: Is Java 10 supported in Jenkins No, Java 10 is not supported. It may work in some cases, but that's it. Things like Pipeline will likely break 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-51219) Is Java 10 supported in Jenkins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51219 Is Java 10 supported in Jenkins Change By: Oleg Nenashev Issue Type: Improvement Task 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-51219) Is Java 10 supported in Jenkins
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51219 Is Java 10 supported in Jenkins Change By: Oleg Nenashev Component/s: other Component/s: jenkins-tag-cloud 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-51116) Failed to set Access Control of CollabNet Security Realm
Title: Message Title mrc updated an issue Jenkins / JENKINS-51116 Failed to set Access Control of CollabNet Security Realm Change By: mrc 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-39143) Stage view disappears after restarting jenkins
Title: Message Title Jared Kauppila commented on JENKINS-39143 Re: Stage view disappears after restarting jenkins Is there any additional information we can provide to help move this along? Our main pipeline has hundreds of steps with numerous parallel stages so when the stage view disappears it's near impossible to get any information since the console output is so cluttered. 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-51227) Quiet period should be configured from declarative pipelines
Title: Message Title Javier Raez created an issue Jenkins / JENKINS-51227 Quiet period should be configured from declarative pipelines Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2018-05-09 16:21 Priority: Minor Reporter: Javier Raez The "quiet period" option is not possible to be configured from the Declarative pipeline like "options" or "parameters". Could be interesting to have that feature inside the declarative pipelines. Add Comment This message was sent
[JIRA] (JENKINS-27617) Isolate durable task in a dedicated Windows process group
Title: Message Title Gabriel Loewen commented on JENKINS-27617 Re: Isolate durable task in a dedicated Windows process group Not having durable tasks on Windows is a major blocker for me. Is there any update on this issue? 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-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title Gabriel Loewen updated an issue Jenkins / JENKINS-51145 PowerShell pipeline step does not seem to be durable Change By: Gabriel Loewen Labels: durability pipeline windows 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-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title Gabriel Loewen assigned an issue to Unassigned Jenkins / JENKINS-51145 PowerShell pipeline step does not seem to be durable Change By: Gabriel Loewen Assignee: Gabriel Loewen 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-51145) PowerShell pipeline step does not seem to be durable
Title: Message Title Gabriel Loewen commented on JENKINS-51145 Re: PowerShell pipeline step does not seem to be durable This seems to be the same issue as described here: https://issues.jenkins-ci.org/browse/JENKINS-27617 Am I to understand that durable tasks are not actually durable on Windows when Jenkins is running as a Windows service? 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-38825) MultiJob does not build Pipeline jobs
Title: Message Title Balázs Bábos commented on JENKINS-38825 Re: MultiJob does not build Pipeline jobs Dear Ximei, Did you manage to pass all parameters somehow to the pipeline job too? 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title Zack Snyder commented on JENKINS-51218 Re: EMail-Ext does not send email, because or empty recipients But it has the info who has committed the changes. So how can it be fixed? How can I get the developer of the current commit which is been building? 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-51226) debian package must depend on *some* jre
Title: Message Title vila created an issue Jenkins / JENKINS-51226 debian package must depend on *some* jre Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 2018-05-09 16:00 Environment: ubuntu 16.04 Priority: Minor Reporter: vila While trying to test 2.107.3 I ran into the debian package not depending on any jre anymore. I.e.: apt-get install default-jre-headless jenkins fails, systemd tries to start jenkins before installing the jre. Requiring users to do 'apt-get install default-jre-headless' then 'apt-get install jenkins' is not the way package dependencies should work ? Add Comment
[JIRA] (JENKINS-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title Zack Snyder commented on JENKINS-51221 Re: Email-Ext groovy.template does show wrong changes Okay, maybe the API has changed and you have to use something different? Is there something I can do to fix 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-48116) Jenkins 2.91 breaks builds which require Ruby
Title: Message Title
Jesse Glick edited a comment on JENKINS-48116
Re: Jenkins 2.91 breaks builds which require Ruby
Filed a PR switching to {{StreamTaskListener}} (more correct anyway, to the extent I understand this craziness), but as previously mentioned, to actually release the fix would apparently require 20 different repositories (acc. to {{fgrep ruby-runtime \ */ \ *.pluginspec}}) to be patched and then released.
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-47922) BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step)
Title: Message Title Sandeep Tingare edited a comment on JENKINS-47922 Re: BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step) Hi Andrew,"Coverity Defects" menu on the left side display displays 1000 warnings only. Count 3135 is returned by MISRA analysis done by the Coverity tool. One more point to mention. Reported 1000 defects are from the first phase of the retrieval by "Publish Coverity View Results" post build action. Please see attached snapshot in my previous comment. This is not a login issue. I have verified Coverity configuration on the Jenkins server and in the pipeline too. Also, 3135 is the right count as it is verified on the Coverity server.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-47922) BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step)
Title: Message Title Sandeep Tingare commented on JENKINS-47922 Re: BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step) Hi Andrew, "Coverity Defects" menu on the left side display 1000 warnings only. Count 3135 returned by MISRA analysis done by the Coverity tool. One more point to mention. Reported 1000 defects are from the first phase of the retrieval by "Publish Coverity View Results" post build action. This is not a login issue. I have verified Coverity configuration on the Jenkins server and in the pipeline too. Also, 3135 is the right count as it is verified on the Coverity server. 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-51225) Support for GitHub Checks API
Title: Message Title Dan Bovey updated an issue Jenkins / JENKINS-51225 Support for GitHub Checks API Change By: Dan Bovey My main use case for this would be for use in the github-branch-source-plugin to GitHub Organisation Folder/Branch Source Plugin. When building a pull request, it should post to the new GitHub Checks API instead of/as well as the Commit Status API. See: [https://help.github.com/articles/about-status-checks/#checks] 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-51225) Support for GitHub Checks API
Title: Message Title Dan Bovey created an issue Jenkins / JENKINS-51225 Support for GitHub Checks API Issue Type: New Feature Assignee: Unassigned Components: github-api-plugin Created: 2018-05-09 15:12 Priority: Minor Reporter: Dan Bovey My main use case for this would be for use in the github-branch-source-plugin to post to the new GitHub Checks API instead of/as well as the Commit Status API. See: https://help.github.com/articles/about-status-checks/#checks Add Comment This message was sen
[JIRA] (JENKINS-51221) Email-Ext groovy.template does show wrong changes
Title: Message Title David van Laatum commented on JENKINS-51221 Re: Email-Ext groovy.template does show wrong changes This is not a problem with emailext it purely asks the SCM api for the list of changes. 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-51218) EMail-Ext does not send email, because or empty recipients
Title: Message Title David van Laatum closed an issue as Won't Fix This is not actually a fault with emailext its with the SCM api. First build has no build to compare it to so no way to determine what has happened since. emailext purely asks the SCM api for this info Jenkins / JENKINS-51218 EMail-Ext does not send email, because or empty recipients Change By: David van Laatum Status: Open Closed Resolution: Won't Fix 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 unsub
[JIRA] (JENKINS-51224) Pipeline Maven plugin's extension points do not load correctly when Pipeline: Job plugin is not installed
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-51224 Pipeline Maven plugin's extension points do not load correctly when Pipeline: Job plugin is not installed Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline, pipeline-maven-plugin Created: 2018-05-09 14:43 Priority: Minor Reporter: Oleg Nenashev Pipeline: Job plugin is declared as optional in Maven Pipeline Plugin, but Listener extension point implementations do not handle it correctly. It results in extension loading failures when Jenkins starts up. The impact on the plugin behavior is unclear, I doubt anybody really uses it without Pipeline: Job plugin. I would just propose to make the plugin a mandatory dependency. Alternative approach is to properly check classes in the extension point static initializer methods. May 09, 2018 4:23:13 PM jenkins.InitReactorRunner$1 onAttained INFO: Listed all plugins May 09, 2018 4:23:14 PM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener java.lang.NoClassDefFoundError: org/jenkinsci/plugins/workflow/job/WorkflowRun at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:669) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:476) at hudson.ExtensionList.load(ExtensionList.java:366) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:304) at hudson.ExtensionList.getComponents(ExtensionList.java:169) at jenkins.model.Jenkins$6.onInitMilestoneAttained(Jenkins.java:1093) at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:83) at org.jvnet.hudson.reactor.ReactorListener$Aggregator.lambda$onAttained$3(ReactorListener.java:102) at org.jvnet.
[JIRA] (JENKINS-47922) BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step)
Title: Message Title Andrew Cho commented on JENKINS-47922 Re: BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step) Hi, Sandeep. Just wondering if the build job has 3135 defects. You can check this by clicking on the "Coverity Defects" menu on the left side. That will display all the defects the plugin fetched from the coverity connect in a table. We are trying to figure out whether this is just a logging issue or did not fetch all the defects. We appreciate your help. 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-51223) remoting processing of "no_proxy" env var needs improvement
Title: Message Title Gabe Montero created an issue Jenkins / JENKINS-51223 remoting processing of "no_proxy" env var needs improvement Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2018-05-09 14:20 Environment: Seen as far back as v3.7 on Jenkins 2.43, and as recent as v3.15 on Jenkins 2.107 Priority: Major Reporter: Gabe Montero The regular _expression_ algorithm in org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.inNoProxyEnvVar(String)(String) does not match when a single element of a fully qualified hostname and domain is part of the no_proxy setting. For example, taking a host name of "jenkins.bnd-cd.svc", we tried adding ".svc", "svc", and "*.svc", "*svc", and none of them matched. We had to specify "bnd-cd.svc" in the no_proxy evn var. By comparison, in th same env, we were able to run curl with a no_proxy evn var containing ".svc" and it properly matched "jenkins.bnd-cd.svc" When running in kubernetes/openshift, having to specify "bnd-cd.svc" is problematic as "bnd-cd" corresponds to the project/namespace, and "svc" was the default suffix applied to all service hostnames. We wanted to have the http_proxy/no_proxy settings be applicable across jenkins running in any project/namespace. In addition to proving this when running an end to end Jenkins master/agent scenario using the standard jar, we also a) took the logic from org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.inNoProxyEnvVar(String) and put it in a simple main program where we set host and no_proxy accordingly b) create debug versions of remoting.jar with additional LOGGER calls to trace the behavior
[JIRA] (JENKINS-47922) BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step)
Title: Message Title Sandeep Tingare edited a comment on JENKINS-47922 Re: BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step) Same Similar issue is reported for Coverity plugin version 1.11.0 . Expected number of warnings = 3135, Number of warnings found at last = 1000 only. Snapshot below. !image-2018-05-09-19-33-18-145.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-47922) BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step)
Title: Message Title Sandeep Tingare commented on JENKINS-47922 Re: BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step) Same issue is reported for Coverity plugin version 1.11.0 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-47922) BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step)
Title: Message Title Sandeep Tingare updated an issue Jenkins / JENKINS-47922 BZ 112041 - Problem fetching more than 1,000 issues (using pipeline coverityResults step) Change By: Sandeep Tingare Attachment: image-2018-05-09-19-33-18-145.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-51140) Design (JEP) what the Error Telemetry API will be
Title: Message Title Baptiste Mathus commented on JENKINS-51140 Re: Design (JEP) what the Error Telemetry API will be Draft JEP submitted for feedback to Jenkins dev ML: https://groups.google.com/d/msg/jenkinsci-dev/ql9iX06IdGw/AJxFcGK5BgAJ 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-51140) Design (JEP) what the Error Telemetry API will be
Title: Message Title Baptiste Mathus updated JENKINS-51140 Jenkins / JENKINS-51140 Design (JEP) what the Error Telemetry API will be 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-51213) Add support of Essentials.yml format to Custom WAR Packager
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-51213 Add support of Essentials.yml format to Custom WAR Packager Change By: Oleg Nenashev Status: In Progress 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-51213) Add support of Essentials.yml format to Custom WAR Packager
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51213 Re: Add support of Essentials.yml format to Custom WAR Packager Code changed in jenkins User: Oleg Nenashev Path: custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/config/Config.java custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/config/EssentialsYMLConfig.java http://jenkins-ci.org/commit/custom-war-packager/6023613d85a4723629a95973a473b0d72907f6b2 Log: JENKINS-51213 - Add support of Essentials.yml to Custom WAR Packager 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-51213) Add support of Essentials.yml format to Custom WAR Packager
Title: Message Title SCM/JIRA link daemon commented on JENKINS-51213 Re: Add support of Essentials.yml format to Custom WAR Packager Code changed in jenkins User: Oleg Nenashev Path: custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/config/Config.java custom-war-packager-lib/src/main/java/io/jenkins/tools/warpackager/lib/config/EssentialsYMLConfig.java http://jenkins-ci.org/commit/custom-war-packager/8576d542346b0004149e5e6230c87b86adb90ffb Log: Merge pull request #25 from oleg-nenashev/JENKINS-51213 JENKINS-51213 - Add support of Essentials.yml to Custom WAR Packager Compare: https://github.com/jenkinsci/custom-war-packager/compare/4cec87c247ed...8576d542346b *NOTE:* This service been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ Functionality will be removed from GitHub.com on January 31st, 2019. 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.
