[JIRA] (JENKINS-62162) Build Failure Analyzer persist Incorrect master field details in Statistics collections
Title: Message Title Lokanath Behera created an issue Jenkins / JENKINS-62162 Build Failure Analyzer persist Incorrect master field details in Statistics collections Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2020-05-05 05:31 Environment: Jenkins 2.138.4 above , Build Failure Analyzer 1.25.1 Labels: bfa buildfaulureanalyser missingbuildurl Priority: Blocker Reporter: Lokanath Behera Hello Currently we are using the Statistics details from mongodb to do post action of failed build. But we are having an issue that the master attribute not have the correct host info . So this issue blocking us to generate the actual build URL . I have describe the problem below in details We have hosted lots of Jenkins masters as below http://myServer:8080/jenkins1 http://myServer:8080/jenkins2 http://myServer:8080/jenkins3 http://myServer:8080/jenkins4 http://myServer:8080/jenkins5 Storage type - Mongo DB and Statistics is enabled Administrative settings . So that when there is failure from any of the Jenkins master details are persist . but when the Statistics info are saved only the initial part of Jenkins master url are saved eg: myServer:8080 its looks like getting as below removing the suffix part of our Jenkins master url String masterString = Jenkins.getInstance().getRootUrl(); //masterString is corret Jenkins master url (http://myServer:8080/jenkins) name = new URL(masterString).getHost(); //only considered the host info as myServer:8080 From
[JIRA] (JENKINS-62142) Race condition during init between jobs and agent
Title: Message Title Nigel Armstrong updated an issue Jenkins / JENKINS-62142 Race condition during init between jobs and agent Change By: Nigel Armstrong Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206061.1588367607000.21450.1588655160062%40Atlassian.JIRA.
[JIRA] (JENKINS-62142) Race condition during init between jobs and agent
Title: Message Title Nigel Armstrong commented on JENKINS-62142 Re: Race condition during init between jobs and agent Looked into this more and this seems to be exclusively an issue in branch-api-plugin, given that jenkins loads nodes at the same time it loads system configuration. Then a later milestone is achieved for loading the jobs. branch-api-plugin should not expect jobs to be loaded when nodes come online. See WorkspaceLocatorImpl.java L#586 (onOnline) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206061.1588367607000.21449.1588655100048%40Atlassian.JIRA.
[JIRA] (JENKINS-62142) Race condition during init between jobs and agent
Title: Message Title Nigel Armstrong assigned an issue to Unassigned Jenkins / JENKINS-62142 Race condition during init between jobs and agent Change By: Nigel Armstrong Assignee: Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206061.1588367607000.21448.1588655040772%40Atlassian.JIRA.
[JIRA] (JENKINS-62142) Race condition during init between jobs and agent
Title: Message Title Nigel Armstrong updated an issue Jenkins / JENKINS-62142 Race condition during init between jobs and agent Change By: Nigel Armstrong Component/s: branch-api-plugin Component/s: remoting Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206061.1588367607000.21446.1588655040478%40Atlassian.JIRA.
[JIRA] (JENKINS-62142) Race condition during init between jobs and agent
Title: Message Title Nigel Armstrong assigned an issue to Jeff Thompson Jenkins / JENKINS-62142 Race condition during init between jobs and agent Change By: Nigel Armstrong Assignee: FABRIZIO MANFREDI Jeff Thompson Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206061.1588367607000.21444.1588654860819%40Atlassian.JIRA.
[JIRA] (JENKINS-62142) Race condition during init between jobs and agent
Title: Message Title Nigel Armstrong updated an issue Jenkins / JENKINS-62142 Race condition during init between jobs and agent Change By: Nigel Armstrong Component/s: branch-api-plugin Component/s: ec2-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206061.1588367607000.21441.1588654860552%40Atlassian.JIRA.
[JIRA] (JENKINS-61959) CpsThread(Timeout) raises InterruptedException
Title: Message Title Thomas Ullrich commented on JENKINS-61959 Re: CpsThread(Timeout) raises InterruptedException Thanks for the link. I tried it out and it worked. Great! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205843.1587205537000.21439.1588653720136%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson closed an issue as Cannot Reproduce Jenkins / JENKINS-62040 pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan Change By: Marky Jackson Status: In Progress Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205931.1587715343000.21428.1588644611179%40Atlassian.JIRA.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman edited a comment on JENKINS-57411 Re: Upgrade github-branch-source-plugin to use okhttp3 The rebuilt incremental can be found at: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.7.2- rc1146 rc1149 . 5bac543b6ba0 0f9fd89495cc /This version uses okhttp3 v4.4.1 and is compatible with github-api-plugin 1.110+. IMPORTANT: It seems that the OkHttp3 version must match exactly. OkHttp3 uses some reflection features the mean if the github-api library is built with v4.4.1, the exact same version must be used at runtime or things go badly. This means okhttp3 is poor match the Jenkins (and much of Java) loose-dependency versioning. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199216.1557540525000.21425.1588638240900%40Atlassian.JIRA.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57411 Upgrade github-branch-source-plugin to use okhttp3 Change By: Liam Newman The latest OkHttp (v2.7.5) is over three years old. The web has come a long way. There are a significant number of Jenkins JIRA and Zendesk issues related to using this ancient library in key plugins.We should upgrade Jenkins to use OkHttp3.NOTES: * OkHttp 2.x and 3.x exist in separate packages and can run side-by-side without conflict. However, different versions of 3.x (and okhttp3 4.x) may be incompatible if clients are using obsolete classes/methods. * OkHttp 3.12.2 is the last version that is reasonably compatible with 2.7.5. Upgrading will require some changes but not huge ones. * OkHttp 3.13.1 has some notable incompatibilities with 2.7.5, but also some better defaults. * OkHttp 3.14.1 removes OkHttpUrlFactory which is a serious version-incompatible API change for several plugins. The github-api library pulled in a shim that provides a workaround OkHttpUrlFactory. Early exploration of this upgrade was started to test whether it would address issues such as JENKINS-54126.Finding so far while using 3.12.2: * okio v2.2.x is needed for okhttp3. * Some special class loading settings are needed to get the right versions okhttp3 and okio to be loaded.(Last updated May 1 4 , 2019 2020 ):The rebuilt incremental can be found at: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.7.2- rc1146 rc1149 . 5bac543b6ba0 0f9fd89495cc /This version uses okhttp3 and is compatible with github-api-plugin 1.110+. Add Comment
[JIRA] (JENKINS-62161) htmlpublisher-plugin occasionally fails with "script returned exit code 1"
Title: Message Title Nick Dimiduk commented on JENKINS-62161 Re: htmlpublisher-plugin occasionally fails with "script returned exit code 1" We see this failure in the html publisher even when the underly job would have otherwise succeeded. Indeed, this is the reason I started to pursue this problem in the first place. Curious, though, that you suspect this action is reporting the failure status of a different action in the pipeline. Seems like that should be a separate bug. Thanks for the quick response Richard Bywater! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206084.1588629273000.21417.1588637220185%40Atlassian.JIRA.
[JIRA] (JENKINS-61751) let :disabled and :deleted at the same time
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-61751 let :disabled and :deleted at the same time Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205582.1585633679000.21413.1588636920758%40Atlassian.JIRA.
[JIRA] (JENKINS-61751) let :disabled and :deleted at the same time
Title: Message Title Bruno P. Kinoshita updated an issue Jenkins / JENKINS-61751 let :disabled and :deleted at the same time Change By: Bruno P. Kinoshita Attachment: uno-choice.hpi Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205582.1585633679000.21414.1588636920845%40Atlassian.JIRA.
[JIRA] (JENKINS-62161) htmlpublisher-plugin occasionally fails with "script returned exit code 1"
Title: Message Title Richard Bywater commented on JENKINS-62161 Re: htmlpublisher-plugin occasionally fails with "script returned exit code 1" Nick Dimiduk I don't believe this is an issue with HTML Publisher - the only reason that I think you are seeing the Exit message after the publishHTML step is because publishHTML is set as a post action which always happens even with a failure. I'd suspect that the issue is actually coming from https://github.com/apache/hbase/blob/master/dev-support/Jenkinsfile#L233 (and so tracking down why its hitting that state might be what's needed). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206084.1588629273000.21411.1588636140268%40Atlassian.JIRA.
[JIRA] (JENKINS-62160) persistentVolumeClaimWorkspaceVolume produces emptyDir volume instead of PVC volume when used in Declarative pipelines
Title: Message Title
david warburton commented on JENKINS-62160
Re: persistentVolumeClaimWorkspaceVolume produces emptyDir volume instead of PVC volume when used in Declarative pipelines
This is the generated yaml (anonimized)
Agent anwhy-fklcld-fuckqof-0nfqavjvebjog-udedqcviwl-vwbxnctaf-8-f664h is provisioned from template vcres-tjkgar_msiukwa_0Dxnpfmycoprj-firsqsxnhi-fwbmghhdm_2-k4ksh-7njl0
---
apiVersion: "v1"
kind: "Pod"
metadata:
annotations:
buildUrl: "https://tv.fmoyos-pixchwrnpnvx.ush/wxoyciu/eld/PslgdnEmvukdyakmgi/tqv/ver-cjxujky-cnybig/ktm/dlobiak%675Bejoolkhhobs-kbefsuasgk-clmbrcmxy/6/"
runUrl: "job/HbypjmSytbncdpinxr/qko/vxv-pqtkmeu-eydfbq/sgw/sfmddvo%762Vvmqjvkxrqny-brfxhedxdu-ythsihpma/8/"
labels:
jenkins: "slave"
jenkins/label: "agawg-nacfrw_dkwnknh_4Qpwsnvjwaeuf-auyqsweurs-xiegsouti_5-x4cwt"
name: "mpaid-qguadg-nqxbyop-4cqwjivsgtfxq-twmrcsovdn-vhbojcfom-4-f581d"
spec:
containers:
- command:
- "/bin/cat"
image: "iankoulski/tree"
name: "tree"
tty: true
volumeMounts:
- mountPath: "/home/jenkins/agent"
name: "workspace-volume"
readOnly: false
- env:
- name: "JENKINS_SECRET"
value: ""
- name: "JENKINS_TUNNEL"
value: "02.147.7.56:1864"
- name: "JENKINS_AGENT_NAME"
value: "tgrmu-bgqrng-kkyqlcy-8hnyafxtetumr-shfdkhyxbo-cnjpbanyw-4-p847s"
- name: "JENKINS_NAME"
value: "utgyv-jbsnfr-blwxojh-4hthpvnmkqatm-iipmqvfxtx-ogetrxvlx-4-p847s"
- name: "JENKINS_AGENT_WORKDIR"
value: "/home/jenkins/agent"
- name: "JENKINS_URL"
value: "https://xy.kecynt-ytjugchsvagx.com/jenkins/"
image: "jenkins/jnlp-slave:4.0.1-1"
name: "jnlp"
resources:
requests:
cpu: "100m"
memory: "256Mi"
volumeMounts:
- mountPath: "/home/jenkins/agent"
name: "workspace-volume"
readOnly: false
nodeSelector:
beta.kubernetes.io/os: "linux"
restartPolicy: "Never"
securityContext: {}
volumes:
- emptyDir:
medium: ""
name: "workspace-volume"
Add Comment
[JIRA] (JENKINS-62161) htmlpublisher-plugin occasionally fails with "script returned exit code 1"
Title: Message Title
Nick Dimiduk created an issue
Jenkins / JENKINS-62161
htmlpublisher-plugin occasionally fails with "script returned exit code 1"
Issue Type:
Bug
Assignee:
Richard Bywater
Components:
htmlpublisher-plugin
Created:
2020-05-04 21:54
Priority:
Major
Reporter:
Nick Dimiduk
Over in Apache Foundation, Apache HBase makes use of Jenkins as a foundation-provided resource. We define a job that is driven by a Jenkinsfile. That jobs is comprised of multiple parallel stages. Many of the stages are nearly identical, and most of them conclude with a stanza that looks like
post {
always {
...
publishHTML target: [
allowMissing : true,
keepAll : true,
alwaysLinkToLastBuild: true,
// Has to be relative to WORKSPACE.
reportDir: "${env.OUTPUT_DIR_RELATIVE}",
reportFiles : 'console-report.html',
reportName : 'JDK11 Nightly Build Report (Hadoop3)'
]
}
}
Occasionally, stages in our BlueOcean builds will be marked as failed on this "Publish HTML reports" action. Output looks like this
[2020-05-02T11:13:44.352Z] [htmlpublisher] Archiving HTML reports...
[2020-05-02T11:13:44.370Z] [htmlpublisher] Archiving at BUILD level /home/jenkins/jenkins-slave/workspace/HBase_Nightly_branch-2.3@2/output-jdk11-hadoop3 to /x1/jenkins/jenkins-home/jobs/HBase Nightly/branches/branch-2-3.v4n2jn/builds/62/htmlreports/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29
script returned exit code 1
[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title Mads Mohr Christensen commented on JENKINS-60288 Re: Installator is broken on Alpine Please note that I didn't reject this issue and I still might try to fix it or accept PRs that fixes it. https://github.com/jenkinsci/adoptopenjdk-plugin#usage-recommendations Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203279.1574785565000.21336.1588629120156%40Atlassian.JIRA.
[JIRA] (JENKINS-62160) persistentVolumeClaimWorkspaceVolume produces emptyDir volume instead of PVC volume when used in Declarative pipelines
Title: Message Title david warburton commented on JENKINS-62160 Re: persistentVolumeClaimWorkspaceVolume produces emptyDir volume instead of PVC volume when used in Declarative pipelines There are additional posts about this issue here: https://stackoverflow.com/questions/57793663/how-to-define-workspace-volume-for-jenkins-pipeline-declarative and here https://groups.google.com/forum/#!topic/jenkinsci-users/DDo1Jf-GjiM Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206083.1588626613000.21334.1588626720132%40Atlassian.JIRA.
[JIRA] (JENKINS-62160) persistentVolumeClaimWorkspaceVolume produces emptyDir volume instead of PVC volume when used in Declarative pipelines
Title: Message Title
david warburton created an issue
Jenkins / JENKINS-62160
persistentVolumeClaimWorkspaceVolume produces emptyDir volume instead of PVC volume when used in Declarative pipelines
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2020-05-04 21:10
Priority:
Minor
Reporter:
david warburton
I have this feature working in a scripted pipeline but when I tried to use it in a declarative pipeline it would never create the workspace volume as a persistent volume claim, it would only mount "emptyDir" volumes for the workspace. The declarative pipeline I'm using is
pipeline {
agent {
kubernetes {
yamlFile 'jenkins/pv-pod.yaml'
defaultContainer 'tree'
}
}
options {
podTemplate(workspaceVolume: persistentVolumeClaimWorkspaceVolume(claimName: 'workspace', readOnly: false))
}
stages {
stage('read workspace') {
steps {
echo 'current env'
sh 'env'
sh '/usr/bin/tree'
echo 'previous env'
sh 'cat old-env.txt || true'
sh 'env > old-env.txt'
}
}
}
}
With a 'pv-pod.yaml' file with these contents
apiVersion: v1
kind: Pod
spec:
containers:
- name: tree
image: iankoulski/tree
command:
- /bin/cat
tty: true
This is in kubenernetes-plugin version 1.25.3.
[JIRA] (JENKINS-62159) Div infoPanelOuter is not position correctly
Title: Message Title Dawid Malinowski commented on JENKINS-62159 Re: Div infoPanelOuter is not position correctly https://github.com/Diabol/delivery-pipeline-plugin/pull/314 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206082.158861997.21330.1588620300046%40Atlassian.JIRA.
[JIRA] (JENKINS-62159) Div infoPanelOuter is not position correctly
Title: Message Title Dawid Malinowski started work on JENKINS-62159 Change By: Dawid Malinowski Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206082.158861997.21329.1588620240077%40Atlassian.JIRA.
[JIRA] (JENKINS-62159) Div infoPanelOuter is not position correctly
Title: Message Title
Dawid Malinowski commented on JENKINS-62159
Re: Div infoPanelOuter is not position correctly
Instead:
div.infoPanelOuter {
margin: 4px 2px 4px 4px;
we should have:
div.infoPanelOuter {
margin: 4px 2px;
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206082.158861997.21328.1588620060051%40Atlassian.JIRA.
[JIRA] (JENKINS-62159) Div infoPanelOuter is not position correctly
Title: Message Title Dawid Malinowski created an issue Jenkins / JENKINS-62159 Div infoPanelOuter is not position correctly Issue Type: Bug Assignee: Dawid Malinowski Attachments: Zrzut ekranu z 2020-05-04 21.06.07.png Components: delivery-pipeline-plugin Created: 2020-05-04 19:19 Priority: Minor Reporter: Dawid Malinowski Div infoPanelOuter is not position correctly between left and right. Add Comment
[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0
Title: Message Title Joseph Petersen commented on JENKINS-60091 Re: HashiCorp Vault plugin using approle is not working since v3.0.0 Christophe Le Guern That does not seem like a bug with the vault plugin. That seems like a bug with your pipeline script. Did you read the release notes? https://github.com/jenkinsci/hashicorp-vault-plugin/releases Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202936.1573144964000.21324.1588618860223%40Atlassian.JIRA.
[JIRA] (JENKINS-61326) Replace 24-column Bootstrap 3 grid with 12-column Bootstrap 4 version
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61326 Replace 24-column Bootstrap 3 grid with 12-column Bootstrap 4 version Change By: Ulli Hafner Released As: Jenkins 2.235 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204915.1583330952000.21322.1588616160229%40Atlassian.JIRA.
[JIRA] (JENKINS-62094) Extract unrelated elements in BS3 grid css file
Title: Message Title Ulli Hafner assigned an issue to Félix Queiruga Balado Jenkins / JENKINS-62094 Extract unrelated elements in BS3 grid css file Change By: Ulli Hafner Assignee: Félix Queiruga Balado Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206004.1588170143000.21318.1588616100250%40Atlassian.JIRA.
[JIRA] (JENKINS-62094) Extract unrelated elements in BS3 grid css file
Title: Message Title Ulli Hafner resolved as Fixed See https://github.com/jenkinsci/jenkins/pull/4693 Jenkins / JENKINS-62094 Extract unrelated elements in BS3 grid css file Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: 2.235 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-61326) Replace 24-column Bootstrap 3 grid with 12-column Bootstrap 4 version
Title: Message Title Ulli Hafner reopened an issue This issue is not fixed, we just have a workaround with https://github.com/jenkinsci/jenkins/pull/4693 Jenkins / JENKINS-61326 Replace 24-column Bootstrap 3 grid with 12-column Bootstrap 4 version Change By: Ulli Hafner Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Karl Shultz commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation I apologize for the noise just now, I must have hit a hotkey that assigned this to me. I've switched it back. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.21296.1588612920395%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Karl Shultz assigned an issue to Olivier Lamy Jenkins / JENKINS-58684 Linux max task resource exhaustion after excessive timer thread creation Change By: Karl Shultz Assignee: Karl Shultz Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.21278.1588612860515%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Karl Shultz assigned an issue to Karl Shultz Jenkins / JENKINS-58684 Linux max task resource exhaustion after excessive timer thread creation Change By: Karl Shultz Assignee: Olivier Lamy Karl Shultz Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.21275.1588612800788%40Atlassian.JIRA.
[JIRA] (JENKINS-61326) Replace 24-column Bootstrap 3 grid with 12-column Bootstrap 4 version
Title: Message Title Daniel Beck closed an issue as Fixed Jenkins / JENKINS-61326 Replace 24-column Bootstrap 3 grid with 12-column Bootstrap 4 version Change By: Daniel Beck Status: Open Closed Resolution: Fixed Released As: Jenkins 2.235 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204915.1583330952000.21254.1588612260421%40Atlassian.JIRA.
[JIRA] (JENKINS-62056) ExtensionComponent#compareTo violates its method contract
Title: Message Title Daniel Beck updated JENKINS-62056 Jenkins / JENKINS-62056 ExtensionComponent#compareTo violates its method contract Change By: Daniel Beck Status: Fixed but Unreleased Closed Released As: Jenkins 2.235 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205954.158784000.21252.1588612201279%40Atlassian.JIRA.
[JIRA] (JENKINS-61841) PathRemover methods can throw enormous CompositeIOExceptions
Title: Message Title Daniel Beck updated JENKINS-61841 Jenkins / JENKINS-61841 PathRemover methods can throw enormous CompositeIOExceptions Change By: Daniel Beck Status: In Review Closed Resolution: Fixed Released As: Jenkins 2.235 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205701.1586366831000.21246.1588612200974%40Atlassian.JIRA.
[JIRA] (JENKINS-61841) PathRemover methods can throw enormous CompositeIOExceptions
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61841 PathRemover methods can throw enormous CompositeIOExceptions Change By: Daniel Beck Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205701.1586366831000.21248.1588612201009%40Atlassian.JIRA.
[JIRA] (JENKINS-62006) Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get()
Title: Message Title Daniel Beck updated JENKINS-62006 Jenkins / JENKINS-62006 Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get() Change By: Daniel Beck Status: In Review Closed Resolution: Fixed Released As: Jenkins 2.235 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205898.1587552961000.21250.1588612201248%40Atlassian.JIRA.
[JIRA] (JENKINS-62065) The bread crumb navigation on the top of the job is not responding after clicking Apply
Title: Message Title Daniel Beck updated JENKINS-62065 Jenkins / JENKINS-62065 The bread crumb navigation on the top of the job is not responding after clicking Apply Change By: Daniel Beck Status: In Review Closed Resolution: Fixed Released As: Jenkins 2.235 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205964.1588002509000.21243.1588612200928%40Atlassian.JIRA.
[JIRA] (JENKINS-62133) Configure screen: Resource Root URL validation error - 404 instance-identity
Title: Message Title Daniel Beck updated JENKINS-62133 Jenkins / JENKINS-62133 Configure screen: Resource Root URL validation error - 404 instance-identity Change By: Daniel Beck Status: In Review Closed Resolution: Fixed Released As: Jenkins 2.235 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206049.1588285097000.21240.1588612140356%40Atlassian.JIRA.
[JIRA] (JENKINS-62100) Remove UI assertions from ChartsITest
Title: Message Title Mitja Oldenbourg assigned an issue to Mitja Oldenbourg Jenkins / JENKINS-62100 Remove UI assertions from ChartsITest Change By: Mitja Oldenbourg Assignee: Mitja Oldenbourg Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206011.1588188875000.21237.1588611780486%40Atlassian.JIRA.
[JIRA] (JENKINS-62100) Remove UI assertions from ChartsITest
Title: Message Title Mitja Oldenbourg started work on JENKINS-62100 Change By: Mitja Oldenbourg Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206011.1588188875000.21235.1588611780364%40Atlassian.JIRA.
[JIRA] (JENKINS-62140) Allow use of remote file for non-multibranch pipeline
Title: Message Title Laurent Goujon commented on JENKINS-62140 Re: Allow use of remote file for non-multibranch pipeline Is it though? In multipipeline, git is configured through the "branch sources" section, while the build configuration configures where Jenkinsfile can be found on all branches. But it doesn't allow you to configure to fetch Jenkinsfile in a separate repository. That's this use-case I would like to be supported by the pipeline jobs. When using "Pipeline from SCM", you need to configure one (or multiple) git repository, with one containing your Jenkinsfile. If Jenkinsfile and code to build are present in 2 separate repositories, you need 2 repositories, triggers apply to both, Jenkinsfile itself need to adapt itself to having both repositories, it's quite intrusive whereas I'd looking for something seamless like Jenkinsfile was in the same repository as the code. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206059.1588359835000.21233.1588609200324%40Atlassian.JIRA.
[JIRA] (JENKINS-47051) Per step "View as plain text" not working
Title: Message Title Ilguiz Latypov commented on JENKINS-47051 Re: Per step "View as plain text" not working Whoever comes to this ticket searching for a plain text output of a pipeline step, I see a work-around in using BlueOceans REST API, https://SERVER/blue/rest/organizations/jenkins/pipelines/FOLDER1/pipelines/FOLDER2/pipelines/FOLDER3/pipelines/FOLDER4/pipelines/JOB_BASE_NAME/runs/BUILD_ID/nodes/NODE_ID/steps/STEP_ID/log/ The API call shows after clicking the "BlueOcean" link and finding the job. The NODE_ID parameter does not show in the original Jenkins Pipeline Steps rich-format console log, https://SERVER/job/FOLDER1/job/FOLDER2/job/FOLDER3/job/FOLDER4/job/JOB_BASE_NAME/BUILD_ID/execution/node/STEP_ID/log/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185441.1506080644000.21226.1588608720284%40Atlassian.JIRA.
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Alan Wong edited a comment on JENKINS-61949 Re: Configuration of action triggers in an Organization folder - Jenkins Version: CloudBees Core Managed Master 2.204.2.2-rolling I believe the standalone organization plugin is deprecated in favor of the branch source plugin: - * *Jenkins Version*: CloudBees Core Managed Master 2.204.2.2-rolling * * GitHub Branch Source Plugin * : 2.6.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205829.1587131764000.21223.1588607040146%40Atlassian.JIRA.
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Alan Wong commented on JENKINS-61949 Re: Configuration of action triggers in an Organization folder Jenkins Version: CloudBees Core Managed Master 2.204.2.2-rolling I believe the standalone organization plugin is deprecated in favor of the branch source plugin: - GitHub Branch Source Plugin: 2.6.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205829.1587131764000.21221.1588606980133%40Atlassian.JIRA.
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Aytunc BEKEN commented on JENKINS-61949 Re: Configuration of action triggers in an Organization folder Interesting, my tests were okay, I will investigate. Could you please share below info ? Thanks. Jenkins Version GitGub Organization Plugin Version Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205829.1587131764000.21219.1588606380254%40Atlassian.JIRA.
[JIRA] (JENKINS-62152) Job changes via script lost after jenkins restart
Title: Message Title Nahuel Cassinari commented on JENKINS-62152 Re: Job changes via script lost after jenkins restart Daniel Beck So that means that this is a normal behavior, not a bug, right? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206074.1588587315000.21216.1588606320120%40Atlassian.JIRA.
[JIRA] (JENKINS-62158) Bad performance on EC2 instance for first build
Title: Message Title
Daniel Hoerner updated an issue
Jenkins / JENKINS-62158
Bad performance on EC2 instance for first build
Change By:
Daniel Hoerner
I have a pipeline project which should run at a EC2 instance node.I have configured an EC2 connection and starting EC2 t3.medium Windows 10 instances automatically. This all works fine.But, the first build at an EC2 instance always performs very bad (slow!!). The next build at the same instance (without rebott etc) is much more faster. {code:java}@Library('BMS-Libraries')import static bms.mail.Email.*import static bms.nexus.Nexus.*import static bms.utils.Utils.* node('AWS_VS2017') { stage('Cleanup Build Machine'){ //deleting current workspace directory deleteDir() }stage('Preparing Build machine...'){ retrieveAndExtractBuildTools(this) }//Do some more ...}{code}I attached a screenshot of the runtime of the different pipeline steps. I connected via RDP to the instance during first build nad task-manager didn't display a high CPU or Memory consumption
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-56794) Support saveOutput in the pipeline step for email-ext
Title: Message Title Alex Earl commented on JENKINS-56794 Re: Support saveOutput in the pipeline step for email-ext It should already be released. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198442.1553774639000.21209.1588605840619%40Atlassian.JIRA.
[JIRA] (JENKINS-56794) Support saveOutput in the pipeline step for email-ext
Title: Message Title Alex Earl updated JENKINS-56794 Jenkins / JENKINS-56794 Support saveOutput in the pipeline step for email-ext Change By: Alex Earl Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198442.1553774639000.21211.1588605840644%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title CloudBees Foundation Security assigned an issue to Ramon Leon Jenkins / JENKINS-61920 java.lang.ClassNotFoundException: javax.annotation.CheckForNull Change By: CloudBees Foundation Security Assignee: CloudBees Foundation Security Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.21197.1588605540480%40Atlassian.JIRA.
[JIRA] (JENKINS-61388) jiraGetFields: "Illegal base64 character" since 1.5.2
Title: Message Title Naresh Rayapati commented on JENKINS-61388 Re: jiraGetFields: "Illegal base64 character" since 1.5.2 Kevin Huber Thank you for the feedback, appreciate it! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205041.1583744817000.21192.1588603980751%40Atlassian.JIRA.
[JIRA] (JENKINS-26354) First time build does not show changelog
Title: Message Title Mark Waite edited a comment on JENKINS-26354 Re: First time build does not show changelog > bq. Does the git plugin check for changes using the git commit hash or message?It uses the commit hash. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160018.1420800265000.21177.1588603980579%40Atlassian.JIRA.
[JIRA] (JENKINS-26354) First time build does not show changelog
Title: Message Title Mark Waite commented on JENKINS-26354 Re: First time build does not show changelog > Does the git plugin check for changes using the git commit hash or message? It uses the commit hash. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160018.1420800265000.21173.1588603920627%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title CloudBees Foundation Security assigned an issue to CloudBees Foundation Security Jenkins / JENKINS-61920 java.lang.ClassNotFoundException: javax.annotation.CheckForNull Change By: CloudBees Foundation Security Assignee: CloudBees Foundation Security Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.21150.1588603873681%40Atlassian.JIRA.
[JIRA] (JENKINS-62152) Job changes via script lost after jenkins restart
Title: Message Title Daniel Beck closed an issue as Not A Defect This is an issue tracker, not a support site. Please ask for help in chat or on the users mailing list. Jenkins / JENKINS-62152 Job changes via script lost after jenkins restart Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-62158) Bad performance on EC2 instance for first build
Title: Message Title
Daniel Hoerner created an issue
Jenkins / JENKINS-62158
Bad performance on EC2 instance for first build
Issue Type:
Bug
Assignee:
FABRIZIO MANFREDI
Attachments:
2020-05-04 16_31_11-Window.jpg
Components:
ec2-plugin, pipeline
Created:
2020-05-04 14:36
Environment:
Jenkins ver. 2.220
Labels:
ec2-plugin pipeline jenkins
Priority:
Major
Reporter:
Daniel Hoerner
I have a pipeline project which should run at a EC2 instance node. I have configured an EC2 connection and starting EC2 t3.medium Windows 10 instances automatically. This all works fine. But, the first build at an EC2 instance always performs very bad (slow!!). The next build at the same instance (without rebott etc) is much more faster.
@Library('BMS-Libraries')
import static bms.mail.Email.*
import static bms.nexus.Nexus.*
import static bms.utils.Utils.*node('AWS_VS2017') {
stage('Cleanup Build Machine'){
//deleting current workspace directory
deleteDir()
}
stage('Preparing Build machine...'){ retrieveAndExtractBuildTools(this)
}
//Do some more ...
}
I
[JIRA] (JENKINS-61949) Configuration of action triggers in an Organization folder
Title: Message Title Alan Wong commented on JENKINS-61949 Re: Configuration of action triggers in an Organization folder I just tried the updated version (1.8.3) in our sandbox region and found the following things: When setting up the organization and filling out the new organization Pipeline Action Triggers section, these parameters are not forwarded to downstream projects after the organization scan. Attempting to trigger a delete event either through Scan Repository Now or Scan Organization Now did not appear to do anything. When updating the organization configuration, settings were not updated in downstream projects. They remained in their default settings on both initial creation and on update. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205829.1587131764000.21142.1588602600223%40Atlassian.JIRA.
[JIRA] (JENKINS-62157) GitHub Enterprise rate limiting no longer working
Title: Message Title
Brian Farrell created an issue
Jenkins / JENKINS-62157
GitHub Enterprise rate limiting no longer working
Issue Type:
Bug
Assignee:
Unassigned
Components:
github-branch-source-plugin
Created:
2020-05-04 14:10
Environment:
github-branch-source v2.6.0
Priority:
Major
Reporter:
Brian Farrell
The changes in JENKINS-59039 have broken rate limiting on our GitHub Enterprise instance. This GHE instance does not return rate limit information via the /rate_limit endpoint
{
"message": "Rate limiting is not enabled.",
"documentation_url": "https://developer.github.com/enterprise/2.19/v3/rate_limit/#get-your-current-rate-limit-status"
}
but does return X-RateLimit headers on every request:
< X-RateLimit-Limit: 5000
< X-RateLimit-Reset: 1588603124
< X-RateLimit-Remaining: 4999
Before JENKINS-59039, it looks like the code called org.kohsuke.github.GitHub#rateLimit, which will return header-based rate limit info if it exists. Now the code calls org.kohsuke.github.GitHub#getRateLimit, which exclusively uses the /rate_limit endpoint. The end result is that the plugin does not throttle itself during organization/repository scanning and for repositories with large
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick started work on JENKINS-61937 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.21137.1588600800290%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick updated JENKINS-61937 Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.21139.1588600800404%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick assigned an issue to Daniel Beck Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Jesse Glick Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.21135.1588600740147%40Atlassian.JIRA.
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Daniel Beck Labels: lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.21132.1588599660219%40Atlassian.JIRA.
[JIRA] (JENKINS-24031) GitHub remote script catalog tab not populated
Title: Message Title
Jonatas de Mello commented on JENKINS-24031
Re: GitHub remote script catalog tab not populated
Error log says:
May 03, 2020 9:42:35 PM WARNING net.sf.json.JSONObject morphPropertyValue
Can't transform property 'parameters' from java.lang.String into java.util.List. Will register a default Morpher
the issue is related to METADATA information in this plugin: https://github.com/jenkinsci/jenkins-scripts/blob/master/scriptler/listEC2Instances.groovy
"parameters" : "",
should be and array
"parameters" : [],
Fix: Open the file "\updates\org.jenkinsci.plugins.scriptler.CentralScriptJsonCatalog.json" and replace the quotes ("") by the brackets ([]) save the file, now the Remote Script catalogs should populate.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62102) Remove UI assertions from MiscIssueRecorderITest
Title: Message Title Simon Schoenwiese started work on JENKINS-62102 Change By: Simon Schoenwiese Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206013.1588189191000.21126.1588597320158%40Atlassian.JIRA.
[JIRA] (JENKINS-26354) First time build does not show changelog
Title: Message Title Sverre Moe edited a comment on JENKINS-26354 Re: First time build does not show changelog This issue has also been experienced on branches that had been rebased.If you rebase N-commits, for which thos commits was a part of the last builds changeset, then it will treat the new build as a first time build.Using ChangelogToBranch could work, but it will add additional boilerplate code to our pipeline, instead of just calling checkout scm.For use it is useless to configure it for the job, because we do not know the base branch (compareTarget) until the job has started. Does the git plugin check for changes using the git commit hash or message?If it detects "first time build", then it should use the latest commit as changeset.Build #1> Commit message: "fix: Correct this method"> First time build. Skipping changelogRebase commit, new hash, same message.Build #2> Commit message: "fix: Correct this method"> First time build. Skipping changelog Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160018.1420800265000.21112.1588595940449%40Atlassian.JIRA.
[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 Artur Czarnota commented on JENKINS-49131 Re: Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition Still reproducible with Jenkins 2.222.1 and Blue Ocean 1.22.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187966.1516792618000.21082.1588595522057%40Atlassian.JIRA.
[JIRA] (JENKINS-48879) User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.
Title: Message Title Artur Czarnota commented on JENKINS-48879 Re: User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages. Still reproducible with Jenkins 2.222.1 and Blue Ocean 1.22.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187674.1515586674000.21084.1588595522115%40Atlassian.JIRA.
[JIRA] (JENKINS-62156) How to display jobs in secondary jenkins in disabled state , as JOBS are shared location.
Title: Message Title Hemantkumar Desale created an issue Jenkins / JENKINS-62156 How to display jobs in secondary jenkins in disabled state , as JOBS are shared location. Issue Type: Task Assignee: Unassigned Components: other Created: 2020-05-04 12:29 Priority: Blocker Reporter: Hemantkumar Desale Hi , We have Primary and Secondary Jenkins avilable , jobs are present in the shared location. In the Secondary jenkins jobs are not displayed in GUI as we have not loaded the configuration from the disk . What we want is jobs should be displayed in the secondary jenkins in the disabled state , is there way to do the same. Add Comment
[JIRA] (JENKINS-61959) CpsThread(Timeout) raises InterruptedException
Title: Message Title Jesse Glick commented on JENKINS-61959 Re: CpsThread(Timeout) raises InterruptedException https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md#creating-an-asynchronous-step Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205843.1587205537000.21059.1588594020239%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Jesse Glick commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 I should add that the motivating use case for JEP-222 is Jenkins running behind a reverse proxy (such as Kubernetes ingress), in which case TLS is typically terminated at the proxy. If the problem involves some sort of incompatibility between the TLS implementation in Tyrus (or whatever library it is using for that) on the client side vs. the TLS implementation in Jetty running on Java 11 on the server side, then it would presumably not affect this environment. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204765.1582603216000.21052.1588593960233%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Edward Nys commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull Affected too, on jdk11 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.21035.1588591500244%40Atlassian.JIRA.
[JIRA] (JENKINS-62155) Edit button doesn't appear in Blue Ocean plugin when used with folders
Title: Message Title Harikishen Hosamana created an issue Jenkins / JENKINS-62155 Edit button doesn't appear in Blue Ocean plugin when used with folders Issue Type: Bug Assignee: Unassigned Components: blueocean-pipeline-editor-plugin Created: 2020-05-04 11:19 Environment: Blue ocean version 1.19.0 Labels: plugin blueocean-ui Priority: Minor Reporter: Harikishen Hosamana Edit button doesn't appear in Blue Ocean plugin when used with folders. The fix seems to be simple. I have made the same for the local installation. Add Comment
[JIRA] (JENKINS-26354) First time build does not show changelog
Title: Message Title Sverre Moe commented on JENKINS-26354 Re: First time build does not show changelog This issue has also been experienced on branches that had been rebased. If you rebase N-commits, for which thos commits was a part of the last builds changeset, then it will treat the new build as a first time build. Using ChangelogToBranch could work, but it will add additional boilerplate code to our pipeline, instead of just calling checkout scm. For use it is useless to configure it for the job, because we do not know the base branch (compareTarget) until the job has started. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160018.1420800265000.21020.1588590600513%40Atlassian.JIRA.
[JIRA] (JENKINS-62154) Move source code renderer to separate plugin
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-62154 Move source code renderer to separate plugin Change By: Ulli Hafner Labels: help-wanted Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206076.1588590014000.21015.1588590060278%40Atlassian.JIRA.
[JIRA] (JENKINS-62154) Move source code renderer to separate plugin
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62154 Move source code renderer to separate plugin Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206076.1588590014000.21014.1588590060261%40Atlassian.JIRA.
[JIRA] (JENKINS-62154) Move source code renderer to separate plugin
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62154 Move source code renderer to separate plugin Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-05-04 11:00 Priority: Minor Reporter: Ulli Hafner The source code renderer that is part of the warnings plugin should be extracted into a separate plugin so other plugins can use it as well. The required JS rendering engine Prism.js should also be moved to that plugin. Add Comment This
[JIRA] (JENKINS-61038) Add permissions for source code viewer
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61038 Add permissions for source code viewer Change By: Ulli Hafner Summary: Add option to disable permissions for source code persistence viewer Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204518.1581385995000.21012.1588589880155%40Atlassian.JIRA.
[JIRA] (JENKINS-60288) Installator is broken on Alpine
Title: Message Title Jakub Bochenski commented on JENKINS-60288 Re: Installator is broken on Alpine That is not practical if you need to support builds using different JDK versions. Replying "don't use the plugin" to a bug request isn't very helpful. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203279.1574785565000.21010.1588589520112%40Atlassian.JIRA.
[JIRA] (JENKINS-56794) Support saveOutput in the pipeline step for email-ext
Title: Message Title Avner Hartuv commented on JENKINS-56794 Re: Support saveOutput in the pipeline step for email-ext Hi Any idea when this fix will be released? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198442.1553774639000.21007.1588589460230%40Atlassian.JIRA.
[JIRA] (JENKINS-61038) Add option to disable source code persistence
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61038 Add option to disable source code persistence Change By: Ulli Hafner Summary: Ability Add option to disable source code view at master and/or project level persistence Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204518.1581385995000.21005.1588588320148%40Atlassian.JIRA.
[JIRA] (JENKINS-38992) Cache libraries specified by a permanent revision string
Title: Message Title Julien Duchesne commented on JENKINS-38992 Re: Cache libraries specified by a permanent revision string It was kept up-to-date for a year and a half. I got a bit tired of it. If you have any intentions of looking at it if I merge back master in it, I'll do it. Or merge that other pull request whichever you think is best. I honestly don't understand how anyone can wait 5 minutes for a library to be pulled from git and think that it is fine Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175410.1476454736000.20994.1588588260300%40Atlassian.JIRA.
[JIRA] (JENKINS-62151) Compress affected files?
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-62151 Compress affected files? Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206073.1588577889000.20988.1588588200264%40Atlassian.JIRA.
[JIRA] (JENKINS-62151) Add option to compress affected files
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-62151 Add option to compress affected files Change By: Ulli Hafner Labels: help-wanted Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206073.1588577889000.20992.1588588200316%40Atlassian.JIRA.
[JIRA] (JENKINS-62151) Add option to compress affected files
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-62151 Add option to compress affected files Change By: Ulli Hafner Summary: Compress Add option to compress affected files ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206073.1588577889000.20990.1588588200292%40Atlassian.JIRA.
[JIRA] (JENKINS-62153) Provide source code API plugin
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-62153 Provide source code API plugin Change By: Ulli Hafner Labels: help-wanted Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206075.1588587871000.20986.1588588140060%40Atlassian.JIRA.
[JIRA] (JENKINS-62153) Provide source code API plugin
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-62153 Provide source code API plugin Issue Type: Epic Assignee: Unassigned Components: code-coverage-api-plugin, core, warnings-ng-plugin Created: 2020-05-04 10:24 Priority: Major Reporter: Ulli Hafner Several reporter plugins show the source code of workspace files. Even in Jenkins Core the files of the current workspace can be access using the UI. It would make sense to create a new plugin that handles access, storage and visualization of source files in Jenkins in a central place. Add Comment
[JIRA] (JENKINS-62152) Job changes via script lost after jenkins restart
Title: Message Title
Nahuel Cassinari created an issue
Jenkins / JENKINS-62152
Job changes via script lost after jenkins restart
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2020-05-04 10:15
Priority:
Blocker
Reporter:
Nahuel Cassinari
Hello, We are trying to change git credentials in more than 200 jobs and so we are using a groovy script to do a bulk change:
import com.cloudbees.hudson.plugins.folder.Folder
import org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject
import com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSourcedef pipelines = Hudson.instance.getAllItems(WorkflowMultiBranchProject)def pipelinesUsingCredentials = pipelines.findAll { p ->
p.getSCMSources().findAll {
it.class == BitbucketSCMSource && it.credentialsId == 'Credential1'
}
}println "pipelines: ${pipelines.size()}"
println "pipelines using svnbuild.core: ${pipelinesUsingCredentials.size()}"pipelinesUsingCredentials.each { println "${it.name.padRight(30)} -- $it.fullName " }def updatePipeline(p) {
def sources = p.getSCMSources().findAll { it.class == BitbucketSCMSource && it.credentialsId == 'Credential1' }
sources.each { source ->
println " updating source: ${source.repository}"
println " existing credential id: ${source.credentialsId}"
it.credentialsId = 'Credential2'
println " new credential id: ${source.credentialsId}"
}
}pipelinesUsingCredentials.each { updatePipeline(it) }
The scripts is working ok but we noticed that every time we restart jenkins the value changed back to the old credentials. I checked and seems that the problem is because is not writing the changes in the config.xml of each job. Is this a normal
[JIRA] (JENKINS-56215) git submodule support
Title: Message Title Ulli Hafner commented on JENKINS-56215 Re: git submodule support jgit is the low level API to access Git, it makes no sense to touch that API. In order to fix this issue only the Git Jenkins API (and the Git Forensics plugin) should be used. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197774.1550660208000.20977.1588587120325%40Atlassian.JIRA.
[JIRA] (JENKINS-56215) git submodule support
Title: Message Title
Ulli Hafner edited a comment on JENKINS-56215
Re: git submodule support
{{jgit}} is the low level API to access Git, it makes no sense to touch that API. In order to fix this issue only the Git Jenkins API (and the Git Forensics plugin) should be used (and the API of the warnings plugin) .
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197774.1550660208000.20979.1588587120355%40Atlassian.JIRA.
[JIRA] (JENKINS-61195) How to avoid "Checks if running on a Unix-like node" in BlueOcean output
Title: Message Title
Florian Ramillien edited a comment on JENKINS-61195
Re: How to avoid "Checks if running on a Unix-like node" in BlueOcean output
Same problem for us, we have implemented a small wrapper around sh/bat commands, and devs see a lot of uneeded 'isUnix' steps.{noformat}def call(cmd) { if (isUnix()) {sh cmd } else {// If we use "returnStdout", need to remove command itself from stdout to work like 'sh' commandif (cmd instanceof Map && cmd.returnStdout) { cmd.script = '@' + cmd.script}bat cmd }}{noformat}If some steps can me marked as "invisible" (steps without side effects maybe ?) this could be great.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204742.158253620.20972.1588585920115%40Atlassian.JIRA.
[JIRA] (JENKINS-61195) How to avoid "Checks if running on a Unix-like node" in BlueOcean output
Title: Message Title
Florian Ramillien commented on JENKINS-61195
Re: How to avoid "Checks if running on a Unix-like node" in BlueOcean output
Same problem for us, we have implemented a small wrapper around sh/bat commands, devs see a lot of 'isUnix' steps.
def call(cmd) {
if (isUnix()) {
sh cmd
} else {
// If we use "returnStdout", need to remove command itself from stdout to work like 'sh' command
if (cmd instanceof Map && cmd.returnStdout) {
cmd.script = '@' + cmd.script
}
bat cmd
}
}
If some steps can me marked as "invisible" (steps without side effects maybe ?) this could be great.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204742.158253620.20970.1588585740097%40Atlassian.JIRA.
[JIRA] (JENKINS-61388) jiraGetFields: "Illegal base64 character" since 1.5.2
Title: Message Title Kevin Huber commented on JENKINS-61388 Re: jiraGetFields: "Illegal base64 character" since 1.5.2 Hey Naresh Rayapati, thanks for your help. I updated to 1.5.4 and changed back to OAuth without any problems. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205041.1583744817000.20967.1588585500151%40Atlassian.JIRA.
[JIRA] (JENKINS-62065) The bread crumb navigation on the top of the job is not responding after clicking Apply
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-62065 The bread crumb navigation on the top of the job is not responding after clicking Apply Change By: Daniel Beck Labels: lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205964.1588002509000.20962.1588585320237%40Atlassian.JIRA.
[JIRA] (JENKINS-56215) git submodule support
Title: Message Title Raphael Höser commented on JENKINS-56215 Re: git submodule support After digging around in the code from warnings-ng I can say that each issue in a report has a "getFolder()" method which returns the folder for the file of that issue. In my opinion this should be solved at an git-forensics-plugin level or even better in jgit (git implementation used by git-forensics-plugin). Sadly jgit is unrelated to this project and I didn't find an issue tracker for it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197774.1550660208000.20954.1588584900258%40Atlassian.JIRA.
[JIRA] (JENKINS-38992) Cache libraries specified by a permanent revision string
Title: Message Title Oleg Nenashev commented on JENKINS-38992 Re: Cache libraries specified by a permanent revision string It still need an action from maintainers Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175410.1476454736000.20933.1588584420761%40Atlassian.JIRA.
[JIRA] (JENKINS-38992) Cache libraries specified by a permanent revision string
Title: Message Title Oleg Nenashev commented on JENKINS-38992 Re: Cache libraries specified by a permanent revision string Alternative implementation: https://github.com/jenkinsci/workflow-cps-global-lib-plugin/pull/58 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175410.1476454736000.20944.1588584420935%40Atlassian.JIRA.
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title Daniel Beck commented on JENKINS-61990 Re: StackOverflowError on boot related to QueueItemAuthenticatorConfiguration Would be interesting to know in which Jenkins version this broke. My guess is that 2.220 is a good candidate (i.e. it still worked in 2.219). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205880.1587466781000.20928.1588583400153%40Atlassian.JIRA.
[JIRA] (JENKINS-61990) StackOverflowError on boot related to QueueItemAuthenticatorConfiguration
Title: Message Title Andre Szünstein commented on JENKINS-61990 Re: StackOverflowError on boot related to QueueItemAuthenticatorConfiguration The problem does not occur with an older jenkins version (around 2.190), and so I believe the bug does appear now due to some changes in the core. I did only a static analyzation of the generated call stack by folling the source code, no debugging ... I do not know why the first check does not suceed before the configuration is loaded at startup. And yes, the possibility for the loop itself is in the code for 3 years. Checking the authorization in a method that is called when reading the authorization configuration is not a good idea, if the check will result in reading the config again ... Here are some log lines, when starting jenkins ... I have shortened the call stacks. Maybe this will help to get down to the problem ... 2020-04-29 07:14:31.980+ [id=34] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 2020-04-29 07:14:31.980+ [id=34] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 2020-04-29 07:14:31.984+ [id=29] INFO jenkins.model.Jenkins$5#runTask: Took 0ms for null by pool-6-thread-1 2020-04-29 07:14:31.984+ [id=29] INFO jenkins.model.Jenkins$5#runTask: Took 0ms for null by pool-6-thread-1 2020-04-29 07:14:31.992+ [id=31] INFO jenkins.model.Jenkins$5#runTask: Took 8ms for Contributed.load by pool-6-thread-3 2020-04-29 07:14:32.117+ [id=34] INFO jenkins.model.Jenkins$5#runTask: Took 133ms for Resolving Dependent Plugins Graph by pool-6-thread-6 2020-04-29 07:14:33.204+ [id=39] WARNING hudson.model.Descriptor#load: Failed to load D:\Jenkins\jenkins.security.QueueItemAuthenticatorConfiguration.xml java.lang.StackOverflowError at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:344) ... at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:344) at hudson.ExtensionList.load(ExtensionList.java:381) Caused: java.io.IOException: Unable to read D:\Jenkins\jenkins.security.QueueItemAuthenticatorConfiguration.xml at hudson.XmlFile.unmarshal(XmlFile.java:183) at hudson.XmlFile.unmarshal(XmlFile.java:163) at hudson.model.Descriptor.load(Descriptor.java:914) ... at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:393) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:393) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:344) at hudson.ExtensionList.load(ExtensionList.java:381) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.getComponents(ExtensionList.java:183) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:194) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.iterator(ExtensionList.java:172) at hudson.ExtensionList.getInstance(ExtensionList.java:162) at jenkins.security.QueueItemAuthenticatorConfiguration.get(QueueItemAuthenticatorConfiguration.java:61) at org.jenkinsci.plugins.authorizeproject.ProjectQueueItemAuthenticator.getConfigured(ProjectQueueItemAuthenticator.java:178) at org.jenkinsci.plugins.authorizeproject.ProjectQueueItemAuthenticator.isConfigured(ProjectQueueItemAuthenticator.java:190) at org.jenkinsci.plugins.authorizeproject.AuthorizeProjectStrategy.checkUnsecuredConfiguration(AuthorizeProjectStrategy.java:186) at org.jenkinsci.plugins.authorizeproject.AuthorizeProjectStrategy.readResolve(AuthorizeProjectStrategy.java:176) ... Kind regards,
[JIRA] (JENKINS-56215) git submodule support
Title: Message Title Raphael Höser commented on JENKINS-56215 Re: git submodule support If I understand it correctly you somehow have the filepath in any shape or form which you pass to the GitBlamer. The Warnings-ng plugin shows this as "Folders" in the report. This information could be used. A also created an issue which was marked as duplicate where I saw the problem on the git blamer and not the warnings-ng side, because they also can resolve this problem by splitting the filename and the path and doing what I described. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197774.1550660208000.20917.1588582620278%40Atlassian.JIRA.
