[JIRA] (JENKINS-50421) Option to turn on 'Maven Linker Publisher' from withMaven pipeline level configuration
Title: Message Title Bing Shiao started work on JENKINS-50421 Change By: Bing Shiao 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-50421) Option to turn on 'Maven Linker Publisher' from withMaven pipeline level configuration
Title: Message Title
Bing Shiao created an issue
Jenkins / JENKINS-50421
Option to turn on 'Maven Linker Publisher' from withMaven pipeline level configuration
Issue Type:
Improvement
Assignee:
Bing Shiao
Components:
pipeline-maven-plugin
Created:
2018-03-27 05:44
Priority:
Minor
Reporter:
Bing Shiao
With 'Maven Linker Publisher' disabled at 'Global Tool Configuration' (http://localhost:8080/configureTools/), users need a way to enable at pipeline level configuration.
withMaven(maven: 'maven-3.5.0', options: [mavenLinkerPublisher()]) {
}
Add Comment
[JIRA] (JENKINS-42144) Publish HP test result Failed with java.lang.NumberFormatException
Title: Message Title Yafim Kazak edited a comment on JENKINS-42144 Re: Publish HP test result Failed with java.lang.NumberFormatException What is HiIf the os locale of the Jenkins slave - loadrunner node machine ? is in English (the LR machine and the LG (if separated ) ? then i think it might be a different issue at all.I will need the full stack trace to make sure - please send it to kazak [at] [hpe] [com] 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-50420) Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4
Title: Message Title GMC Software Development B Corporate created an issue Jenkins / JENKINS-50420 Class-exception in Build Monitor Plugin with Groovy Postbuild Plugin 2.4 Issue Type: Bug Assignee: Stefan Wolf Components: build-monitor-plugin, groovy-postbuild-plugin Created: 2018-03-27 05:28 Environment: Jenkins LTS 2.107.1 on Windows Server 2008 R2 x64, build-monitor-plugin 1.12+build.201708172343 groovy-postbuild 2.4 badge 1.2 Labels: exception Priority: Blocker Reporter: GMC Software Development B Corporate Hi! After upgrading groovy-postbuild to version 2.4, which does split/extracte badge- and summary-features into the badge-plugin, this "combination" is no longer compatible with the current release of the build-monitor plugin; I.e., shows following exception in log ... Mar 27, 2018 7:10:41 AM WARNING org.kohsuke.stapler.HttpResponseRenderer$Default handleJavaScriptProxyMethodCall call to /$stapler/bound/4edcd493-d025-402e-bfaa-f596f57a8fd0/fetchJobViews failed java.lang.ClassNotFoundException: org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildAction at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(Unknown Source) Caused: java.lang.NoClassDefFoundError: org/jvnet/hudson/plugins/groovypostbuild/GroovyPostbuildAction at
[JIRA] (JENKINS-42144) Publish HP test result Failed with java.lang.NumberFormatException
Title: Message Title Yafim Kazak commented on JENKINS-42144 Re: Publish HP test result Failed with java.lang.NumberFormatException What is the os locale of the Jenkins slave - loadrunner machine? and the LG (if separated)? 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-50419) PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2
Title: Message Title Priyanga G commented on JENKINS-50419 Re: PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2 Sorry sir,I ask support from PRQA. Thank you for information 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-50419) PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2
Title: Message Title Oleg Nenashev commented on JENKINS-50419 Re: PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2 I am not a maintainer of PRQA plugin, please do not assign tickets to me. Contact the plugin's maintainers or PRQA support 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-50419) PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2
Title: Message Title Priyanga G created an issue Jenkins / JENKINS-50419 PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2 Issue Type: Bug Assignee: Oleg Nenashev Components: prqa-plugin Created: 2018-03-27 05:00 Environment: Jenkins-2.1.0.1 and PRQA-3.0.0 Priority: Minor Reporter: Priyanga G PRQA plugin is not supporting PRQA framework 2.1.2 and 2.1.4.Whether lower version of prqa plugin will support these version?? Add Comment
[JIRA] (JENKINS-50419) PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-50419 PRQA 3.0.0 is not supporting PRQA framework 2.1.4 and 2.1.2 Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50408) Highlight difficult to see after clicking on stage
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-50408 Highlight difficult to see after clicking on stage Change By: Craig Rodrigues Feedback from Gitter, Craig Rodrigues:for the circles displayed for each stage in the pipelinethere are 4 colors1. green = a stage has completed successfully2. red = a stage has failed3. blue = a stage is in progress * 4 . dark grey highlighted circle = I clicked on the stage in UI * for color 4., I would request that the visual clue that the stage has been selected be made more clear. When I have about 15 stages displayed on the screen, the dark grey highlight is difficult to see 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-50408) Highlight difficult to see after clicking on stage
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-50408 Highlight difficult to see after clicking on stage Change By: Craig Rodrigues Summary: Highlight difficult to see for grey pipelines after clicking on stage 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-50418) when {branch} stage conditional regression
Title: Message Title
Eric Nelson updated an issue
Jenkins / JENKINS-50418
when {branch} stage conditional regression
Change By:
Eric Nelson
The when branch conditional seems to still be broken. Similar to - JENKINS-41012 - . In this case we are using GitHub with webhooks to trigger a build. Following the good test code in 41012 I tested with the following. Results - I get echo _expression_ and echo env, but branch is always skipped. Test pipeline code stage is:{code:java}stages {stage('test condition: _expression_') {when {_expression_ {return env.GIT_BRANCH == "origin/master"}}steps {sh 'echo "_expression_"'}}stage('test when: env') {when {environment name: "GIT_BRANCH", value: "origin/master"}steps {sh 'echo "env"'}}stage('test when: branch') {when {branch " origin/ master"}steps {sh 'echo "branch"'}}}{code}
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
[JIRA] (JENKINS-50418) when {branch} stage conditional regression
Title: Message Title
Eric Nelson created an issue
Jenkins / JENKINS-50418
when {branch} stage conditional regression
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-03-27 03:00
Environment:
Jenkins 2.112 Pipeline: API 2.26 Pipeline: Model API 1.2.7
Priority:
Minor
Reporter:
Eric Nelson
The when branch conditional seems to still be broken. Similar to JENKINS-41012. In this case we are using GitHub with webhooks to trigger a build. Following the good test code in 41012 I tested with the following. Results - I get echo _expression_ and echo env, but branch is always skipped. Test pipeline code stage is:
stages {
stage('test condition: _expression_') {
when {
_expression_ {
return env.GIT_BRANCH == "origin/master"
}
}
steps {
sh 'echo "_expression_"'
}
}
stage('test when: env') {
when {
environment name: "GIT_BRANCH", value: "origin/master"
}
steps {
sh 'echo "env"'
}
}
stage('test when: branch') {
when {
branch "master"
}
steps {
sh 'echo "branch"'
}
}
}
[JIRA] (JENKINS-50417) download and upload attachments are not working on slaves but just on master node
Title: Message Title Naresh Rayapati updated JENKINS-50417 Jenkins / JENKINS-50417 download and upload attachments are not working on slaves but just on master node Change By: Naresh Rayapati Status: In Review Closed 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-50417) download and upload attachments are not working on slaves but just on master node
Title: Message Title Naresh Rayapati commented on JENKINS-50417 Re: download and upload attachments are not working on slaves but just on master node Released code with 1.4.1 Closing 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-50417) download and upload attachments are not working on slaves but just on master node
Title: Message Title Naresh Rayapati updated JENKINS-50417 Jenkins / JENKINS-50417 download and upload attachments are not working on slaves but just on master node Change By: Naresh Rayapati 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-50417) download and upload attachments are not working on slaves but just on master node
Title: Message Title Naresh Rayapati started work on JENKINS-50417 Change By: Naresh Rayapati 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-50417) download and upload attachments are not working on slaves but just on master node
Title: Message Title Naresh Rayapati commented on JENKINS-50417 Re: download and upload attachments are not working on slaves but just on master node PR: https://github.com/jenkinsci/jira-steps-plugin/pull/70 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-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Vivek Pandey commented on JENKINS-50406 Re: "Triggered Build" links broken with cloudbees-folder Josh McDonald Here is how you can create a freestyle job inside a folder on classic: 1. Go to http://localhost:8080/view/all/newJob and select Folder, give it name folder1, click save. 2. After step 1, you should land inside folder1 or go directly to http://localhost:8080/job/folder1/, click New Item again and create a 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-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Michael Neale commented on JENKINS-50406 Re: "Triggered Build" links broken with cloudbees-folder Josh McDonald is there enough ^ to reproduce? 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-50417) download and upload attachments are not working on slaves but just on master node
Title: Message Title
Naresh Rayapati created an issue
Jenkins / JENKINS-50417
download and upload attachments are not working on slaves but just on master node
Issue Type:
Bug
Assignee:
Naresh Rayapati
Components:
jira-steps-plugin
Created:
2018-03-27 01:37
Priority:
Minor
Reporter:
Naresh Rayapati
The below code works on master node, but not on the slave, unfortunately I couldn't catch this as I am running a local jenkins without any slaves but just a master with multiple agents.
node {
writeFile file: 'abc/test.txt', text: 'Test Attachment - Hello'
def attachment = jiraUploadAttachment idOrKey: 'TEST-123', file: 'abc/test.txt', site: 'JIRA'
def attachmentId = attachment.data[0].id.toString()
attachment = jiraGetAttachmentInfo id: attachmentId, site: 'JIRA'
echo attachment.data.toString()
jiraDownloadAttachment id: attachmentId, file: "abc/test.txt", override: true, site: 'JIRA'
def file = readFile 'abc/test.txt'
echo file.toString()
jiraDeleteAttachment id: attachmentId, site: 'JIRA'
}
[JIRA] (JENKINS-50416) git parameter plugin does not working with shared workspace plugin
Title: Message Title hohoon song created an issue Jenkins / JENKINS-50416 git parameter plugin does not working with shared workspace plugin Issue Type: Bug Assignee: Boguslaw Klimas Attachments: image-2018-03-27-10-34-39-259.png Components: git-parameter-plugin Created: 2018-03-27 01:36 Environment: Operating System : Amazon Linux AMI release 2017.03 64 bit Jdk : OpenJDK "1.7.0_141" Jenkins : 1.625.3 plugin version : 0.6.2 How you installed Jenkins : yum web browser (+ version) : Chrome 65.0.3325.181 Priority: Minor Reporter: hohoon song git-parameter plugin cannot resolve scm_url from "SHAREDSPACE_SCM_URL" maybe because of environment variable resolving order. Add Comment
[JIRA] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Mark Waite commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. Jared Miller, the wiki is not the preferred location for Pipeline documentation. Refer to the Pipeline: SCM Step page for an example using the environment variables as a map returned from the `checkout` step. There is a Jenkins Minute video that describes it as well. You can also read about it (briefly) in the Pipeline: SCM Step plugin page. If you'd like to add it to the Git plugin Wiki, you're welcome to do that as well. 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-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Jared Miller commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. This is not at all obvious if you just glance over: https://wiki.jenkins.io/display/JENKINS/Git+Plugin You'd never expect that to access those ENV variables you have to capture the output of checkout. Or am I mistaken? 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-46600) [JDK 9] Jenkins does not start with "java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter"
Title: Message Title Denys Digtiar commented on JENKINS-46600 Re: [JDK 9] Jenkins does not start with "java.lang.ClassNotFoundException: javax.xml.bind.DatatypeConverter" As per http://openjdk.java.net/jeps/320 EE modules are going to be removed from the Java SE 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-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title Denys Digtiar commented on JENKINS-47834 Re: Add the support for Remoting work dir configuration of JNLP Launcher Oleg Nenashev no worries, completely understandable. I updated the description a bit. 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-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title
Denys Digtiar updated an issue
Jenkins / JENKINS-47834
Add the support for Remoting work dir configuration of JNLP Launcher
Change By:
Denys Digtiar
[https://jenkins.io/doc/upgrade-guide/2.73/] see Remoting Working Directories sectionSee screenshot for the new fields that were introduced to the JNLP Launcher.These appear to be ignored by the [Slave Setup|https://plugins.jenkins.io/slave-setup] and/or [Libvirt Slaves|https://plugins.jenkins.io/libvirt-slave] plugins which results result in the following two arguments are being added empty no matter what is in the fields{{-workDir}} {{}} {{-internalDir}} {{}}This seem seems to break the JNLP launcher since it apper appers to be defaultig to the `/` as path in such 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
[JIRA] (JENKINS-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title
Denys Digtiar updated an issue
Jenkins / JENKINS-47834
Add the support for Remoting work dir configuration of JNLP Launcher
Change By:
Denys Digtiar
[https://jenkins.io/doc/upgrade-guide/2.73/] see Remoting Working Directories sectionSee screenshot for the new fields that were introduced to the JNLP Launcher.These appear to be ignored by the [Slave Setup|https://plugins.jenkins.io/slave-setup] and/or [Libvirt Slaves|https://plugins.jenkins.io/libvirt-slave] plugins which result in the following two arguments being added empty no matter what is in the fields{{-workDir}} {{}} {{-internalDir}} {{}}This seems to break the JNLP launcher since it appers appears to be defaultig defaulting to the `/` as a path in such 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
[JIRA] (JENKINS-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title
Denys Digtiar updated an issue
Jenkins / JENKINS-47834
Add the support for Remoting work dir configuration of JNLP Launcher
Change By:
Denys Digtiar
[https://jenkins.io/doc/upgrade-guide/2.73/] see Remoting Working Directories sectionSee screenshot for the new fields that were introduced to the JNLP Launcher.These appear to be ignored by the [Slave Setup plugin |https://plugins.jenkins.io/slave-setup] and /or [Libvirt Slaves|https://plugins.jenkins.io/libvirt-slave] plugins which results the following two arguments are added no matter what is in the fields{{-workDir}} {{}} {{-internalDir}} {{}}This seem to break the JNLP launcher since it apper to be defaultig to the `/` as path in such 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
[JIRA] (JENKINS-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title
Denys Digtiar updated an issue
Jenkins / JENKINS-47834
Add the support for Remoting work dir configuration of JNLP Launcher
Change By:
Denys Digtiar
[https://jenkins.io/doc/upgrade-guide/2.73/] see Remoting Working Directories sectionSee screenshot for the new fields that were introduced to the JNLP Launcher.These appear to be ignored by the [ Slave Setup plugin |https://plugins.jenkins.io/slave-setup] and the following two arguments are added no matter what is in the fields{{-workDir}}{{}}{{-internalDir}}{{}}This seem to break the JNLP launcher since it apper to be defaultig to the `/` as path in such 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-49668) Root CAs component appears broken
Title: Message Title Denys Digtiar resolved as Fixed Merged and ready for release. Jenkins / JENKINS-49668 Root CAs component appears broken Change By: Denys Digtiar 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-49668) Root CAs component appears broken
Title: Message Title Denys Digtiar updated JENKINS-49668 Jenkins / JENKINS-49668 Root CAs component appears broken Change By: Denys Digtiar Status: In Review 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-50301) [JDK9] Java WebStart Unsupported past Java 8
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-50301 [JDK9] Java WebStart Unsupported past Java 8 Change By: Michael Neale Priority: Minor Critical 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-21942) Unreliable defaulting of Jenkins.workspaceDir
Title: Message Title Jesse Glick commented on JENKINS-21942 Re: Unreliable defaulting of Jenkins.workspaceDir Baptiste Mathus yes I already said it is not reproducible in interactive setup; my concern was about new installations created via Docker or config-as-code generally. 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-33900) save/apply button is missing when editing mutibranch jobs created inside a github organization folder
Title: Message Title Jesse Glick commented on JENKINS-33900 Re: save/apply button is missing when editing mutibranch jobs created inside a github organization folder Matias De Santi no. This would require some kind of github-oauth integration. Brian Michaud repo folder configuration is effectively available in particular cases, but not in general. All of these discussions are off topic for this issue, which was about the Save and Apply buttons. 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-50415) Failed to login: Failed to send request to https://test.salesforce.com/services/Soap/u/33.0
Title: Message Title Renjesh Raju updated an issue Jenkins / JENKINS-50415 Failed to login: Failed to send request to https://test.salesforce.com/services/Soap/u/33.0 Change By: Renjesh Raju I have a Jenkins CI server, but today seeing an kind of login issue and all builds are failing.Failed to login: Failed to send request to [https://test.salesforce.com/services/Soap/u/33.0]What could be the reason for this failure? Any help will be appreciated 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-50415) Failed to login: Failed to send request to https://test.salesforce.com/services/Soap/u/33.0
Title: Message Title Renjesh Raju created an issue Jenkins / JENKINS-50415 Failed to login: Failed to send request to https://test.salesforce.com/services/Soap/u/33.0 Issue Type: Task Assignee: Armando Fernandez Components: ant-plugin, jenkinslint-plugin, jenkinswalldisplay Created: 2018-03-26 22:55 Priority: Minor Reporter: Renjesh Raju I have a CI server, but today seeing an issue and all builds are failing. Failed to login: Failed to send request to https://test.salesforce.com/services/Soap/u/33.0 What could be the reason for this failure? Any help will be appreciated Add Comment
[JIRA] (JENKINS-50389) Create a wiki page for badge plugin
Title: Message Title ikedam closed an issue as Fixed Thanks! Jenkins / JENKINS-50389 Create a wiki page for badge plugin Change By: ikedam 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-49220) Plastic Poll SCM ignoring jobs in the queue
Title: Message Title Ella Z resolved as Fixed Plastic team resolved the issue. version 2.11 Jenkins / JENKINS-49220 Plastic Poll SCM ignoring jobs in the queue Change By: Ella Z 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.google.com/d/optout.
[JIRA] (JENKINS-49952) Groovy post-build script in matrix job throws exception
Title: Message Title John David commented on JENKINS-49952 Re: Groovy post-build script in matrix job throws exception BTW I ran the groovy script with nothing but println "Test groovy code here" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17132) Show a warning when multi-line parser is selected
Title: Message Title SCM/JIRA link daemon commented on JENKINS-17132 Re: Show a warning when multi-line parser is selected Code changed in jenkins User: Ulli Hafner Path: src/main/java/io/jenkins/plugins/analysis/warnings/Doxygen.java src/main/java/io/jenkins/plugins/analysis/warnings/DrMemory.java src/main/java/io/jenkins/plugins/analysis/warnings/Eclipse.java src/main/java/io/jenkins/plugins/analysis/warnings/GhsMulti.java src/main/java/io/jenkins/plugins/analysis/warnings/GnuFortran.java src/main/java/io/jenkins/plugins/analysis/warnings/NagFortran.java src/main/java/io/jenkins/plugins/analysis/warnings/YuiCompressor.java src/main/resources/io/jenkins/plugins/analysis/warnings/Messages.properties http://jenkins-ci.org/commit/warnings-plugin/ec0337ca13dc5c1a90336bcce802e477c1125c34 Log: [FIXED JENKINS-17132] Show a warning if slow multi-line parser is selected. 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-17132) Show a warning when multi-line parser is selected
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-17132 Show a warning when multi-line parser is selected Change By: SCM/JIRA link daemon 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.google.com/d/optout.
[JIRA] (JENKINS-50399) Skipped steps show as passed - plugins uptodate but still nothing
Title: Message Title Keith Zantow updated an issue Jenkins / JENKINS-50399 Skipped steps show as passed - plugins uptodate but still nothing Change By: Keith Zantow Sprint: Blue Ocean 1.5 - beta 3 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-48973) Add prev link to Blueocean API response
Title: Message Title Michael Neale stopped work on JENKINS-48973 Change By: Michael Neale Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48075) Show next/prev links in results screen
Title: Message Title Michael Neale assigned an issue to Nicolae Pascu Jenkins / JENKINS-48075 Show next/prev links in results screen Change By: Michael Neale Assignee: Ivan Meredith Nicolae Pascu 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-48075) Show next/prev links in results screen
Title: Message Title Michael Neale stopped work on JENKINS-48075 Change By: Michael Neale Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48973) Add prev link to Blueocean API response
Title: Message Title Michael Neale assigned an issue to Nicolae Pascu Jenkins / JENKINS-48973 Add prev link to Blueocean API response Change By: Michael Neale Assignee: Ivan Meredith Nicolae Pascu 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-49637) Simplify BlueOcean JS development experience
Title: Message Title Michael Neale started work on JENKINS-49637 Change By: Michael Neale 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-49952) Groovy post-build script in matrix job throws exception
Title: Message Title John David commented on JENKINS-49952 Re: Groovy post-build script in matrix job throws exception I reverted the groovy change on that test job. I'll put it back in and send you the config.xml shortly. 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-50382) build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project
Title: Message Title Yeh Fang commented on JENKINS-50382 Re: build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project Kyle L Hi, just letting you know we have a fix but we're still confirming that it fully resolves 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 the Google 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-49952) Groovy post-build script in matrix job throws exception
Title: Message Title John David commented on JENKINS-49952 Re: Groovy post-build script in matrix job throws exception Daniel, Sorry for not being more specific. We run nothing on master so slaves was selected. This is a bit confusing on matrix jobs which has the concept of AXES and MATRIX. I ran this on a matrix job and selected MATRIX for the 'Matrix target' to run the groovy code on. 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-42623) PerforceScm(pipeline) checkout fails with "hudson.AbortException: P4: invalid client view"
Title: Message Title
boris avney commented on JENKINS-42623
Re: PerforceScm(pipeline) checkout fails with "hudson.AbortException: P4: invalid client view"
Karl Wirth the issue was with TAB between the lines in view(see below): (IMO should be allowed otherwise it's hard to format the entire function) ```view: '''-//my/path/... //${JOB_NAME}/... <<>>//my/path/x/y/z/... //${JOB_NAME}/...''']]])```
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-42623) PerforceScm(pipeline) checkout fails with "hudson.AbortException: P4: invalid client view"
Title: Message Title
boris avney edited a comment on JENKINS-42623
Re: PerforceScm(pipeline) checkout fails with "hudson.AbortException: P4: invalid client view"
[~p4karl]the issue was with TAB between the lines in view(see below):(IMO should be allowed otherwise it's hard to format the entire function) ``` {{ view: '''-//my/path/... //$\{JOB_NAME}/... }} {{ <<>>//my/path/x/y/z/... //$\{JOB_NAME}/...''']]]) ``` }}
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-42144) Publish HP test result Failed with java.lang.NumberFormatException
Title: Message Title Weston Dyer commented on JENKINS-42144 Re: Publish HP test result Failed with java.lang.NumberFormatException We tried the latest 5.3 from:https://wiki.jenkins.io/display/JENKINS/HPE+Application+Automation+Tools Also tried the build from above: 5.1-SNAPSHOT (private-c50a44c4-kazaky) Both builds gave the same error. We were able to workaround the issue by adding an SLA that does not result in a decimal number. 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-49227) Cannot configure findbugs reporter to mark build as unstable for findbugs failures
Title: Message Title Cyrille Le Clerc started work on JENKINS-49227 Change By: Cyrille Le Clerc 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-49227) Cannot configure findbugs reporter to mark build as unstable for findbugs failures
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-49227 Cannot configure findbugs reporter to mark build as unstable for findbugs failures Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-50414) Add healthy/unhealthy thresholds to the Open Task Scanner publisher
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50414 Re: Add healthy/unhealthy thresholds to the Open Task Scanner publisher Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/TasksScannerPublisher.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/TasksScannerPublisher/config.jelly http://jenkins-ci.org/commit/pipeline-maven-plugin/59dc8642e28a2bc5a3779d103fb9e18aa7729442 Log: JENKINS-50414 Add healthy/unhealthy thresholds to the Open Task Scanner publisher 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-50414) Add healthy/unhealthy thresholds to the Open Task Scanner publisher
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-50414 Add healthy/unhealthy thresholds to the Open Task Scanner publisher Issue Type: New Feature Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2018-03-26 21:05 Priority: Minor Reporter: Cyrille Le Clerc Add healthy/unhealthy thresholds to the Open Task Scanner publisher. Similar to JENKINS-49227 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50241) Add Maven details tab to build result page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50241 Re: Add Maven details tab to build result page Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenArtifact.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenDependency.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenSpyLogProcessor.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginNullDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/DependenciesFingerprintPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/DependenciesLister.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/JGivenTestsPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/PipelineGraphPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtils.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport/help-generatedArtifacts.html jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport/index.jelly jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2DaoTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/publishers/DependenciesListerTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/1729e64250c10213ca428141092540bdeeaba97a Log: JENKINS-50241 Add "dependencies" section on the Maven details screen (#137) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50413) DigitalOcean plugin provides stale/incorrect list of ssh public keys
Title: Message Title Andrew Hammond updated an issue Jenkins / JENKINS-50413 DigitalOcean plugin provides stale/incorrect list of ssh public keys Change By: Andrew Hammond When I create a DO cloud and add the API key, it populates the drop-box for ssh keys. This appears to be stale information. When I use the same api key to run `doctl compute ssh-key list` I get the correct and up-to-date list of ssh keys.This instance has been upgraded over the past 1.5 years. DO auto-scaling instances stopped working without warning or known change on our side about 1.5 months ago. 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-50413) DigitalOcean plugin provides stale/incorrect list of ssh public keys
Title: Message Title Andrew Hammond created an issue Jenkins / JENKINS-50413 DigitalOcean plugin provides stale/incorrect list of ssh public keys Issue Type: Bug Assignee: Unassigned Components: digitalocean-plugin Created: 2018-03-26 20:53 Environment: JENKINS_VERSION 2.107.1 digitalocean-plugin 0.17 Priority: Minor Reporter: Andrew Hammond When I create a DO cloud and add the API key, it populates the drop-box for ssh keys. This appears to be stale information. When I use the same api key to run `doctl compute ssh-key list` I get the correct and up-to-date list of ssh keys. This instance has been upgraded over the past 1.5 years. DO auto-scaling instances stopped working without warning about 1.5 months ago. Add Comment
[JIRA] (JENKINS-48179) [1.1.0] Generic shell script with parameter will not work
Title: Message Title Daniel Heid closed an issue as Cannot Reproduce Jenkins / JENKINS-48179 [1.1.0] Generic shell script with parameter will not work Change By: Daniel Heid Status: Open Closed Resolution: Cannot Reproduce 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-48179) [1.1.0] Generic shell script with parameter will not work
Title: Message Title Daniel Heid commented on JENKINS-48179 Re: [1.1.0] Generic shell script with parameter will not work Closing the issue due to lack of information. 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-49180) Each postBuildStep block takes 1 second to evaluate, DSL seed jobs went up from 10mins to 1 hour
Title: Message Title Daniel Heid commented on JENKINS-49180 Re: Each postBuildStep block takes 1 second to evaluate, DSL seed jobs went up from 10mins to 1 hour I'm closing the issue, since I cannot do anything at the moment. 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-49585) [Question] Assign MASTER role
Title: Message Title Daniel Heid closed an issue as Cannot Reproduce Jenkins / JENKINS-49585 [Question] Assign MASTER role Change By: Daniel Heid Status: Open Closed Resolution: Cannot Reproduce 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-49180) Each postBuildStep block takes 1 second to evaluate, DSL seed jobs went up from 10mins to 1 hour
Title: Message Title Daniel Heid closed an issue as Cannot Reproduce Jenkins / JENKINS-49180 Each postBuildStep block takes 1 second to evaluate, DSL seed jobs went up from 10mins to 1 hour Change By: Daniel Heid Status: Open Closed Resolution: Cannot Reproduce 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-49585) [Question] Assign MASTER role
Title: Message Title Daniel Heid commented on JENKINS-49585 Re: [Question] Assign MASTER role Closing the issue due to a lack of information. 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-49952) Groovy post-build script in matrix job throws exception
Title: Message Title Daniel Heid updated JENKINS-49952 Jenkins / JENKINS-49952 Groovy post-build script in matrix job throws exception Change By: Daniel Heid Status: Resolved In 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-49952) Groovy post-build script in matrix job throws exception
Title: Message Title Daniel Heid resolved as Cannot Reproduce Jenkins / JENKINS-49952 Groovy post-build script in matrix job throws exception Change By: Daniel Heid Status: Open Resolved Resolution: Cannot Reproduce 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-49952) Groovy post-build script in matrix job throws exception
Title: Message Title Daniel Heid commented on JENKINS-49952 Re: Groovy post-build script in matrix job throws exception Hi John! Sorry, but I cannot reproduce the problem. Are you running the script on the Jenkins master or an agent? Could you please provide the config.xml of the Jenkins 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-50382) build.xml not saved because: Failed to serialize hudson.plugins.sauce_ondemand.BrowserAxis#project
Title: Message Title Yeh Fang started work on JENKINS-50382 Change By: Yeh Fang 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-50412) Fingerprints logs should be less verbose
Title: Message Title Jeff Thompson started work on JENKINS-50412 Change By: Jeff Thompson 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-50412) Fingerprints logs should be less verbose
Title: Message Title Jeff Thompson created an issue Jenkins / JENKINS-50412 Fingerprints logs should be less verbose Issue Type: Improvement Assignee: Jeff Thompson Components: core Created: 2018-03-26 20:15 Priority: Minor Reporter: Jeff Thompson Fingerprint log files can grow large, mostly composed of a single, repeated line that provides little to no value, like this: possibly trimming /var/jenkins_home/fingerprints/[...] I propose we eliminate this line, to keep the log from growing so large and filling up with useless lines. This issue is also noted as an aside in a comment on JENKINS-19066. Add Comment
[JIRA] (JENKINS-50411) Job DSL Dynamic API Viewer Not Loading
Title: Message Title Maxfield Stewart updated an issue Jenkins / JENKINS-50411 Job DSL Dynamic API Viewer Not Loading Change By: Maxfield Stewart Getting the following stack trace, but I cannnot determine which plugin/class is causing the issue from the details so it's hard to be more helpful:Mar 26, 2018 7:46:20 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: Error while serving [http:// /job-dsl-api-viewer/data|http://10.202.78.42/job-dsl-api-viewer/data] *** java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.corsfilter.AccessControlsFilter.doFilter(AccessControlsFilter.java:79) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:237) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:214) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at
[JIRA] (JENKINS-50411) Job DSL Dynamic API Viewer Not Loading
Title: Message Title Maxfield Stewart created an issue Jenkins / JENKINS-50411 Job DSL Dynamic API Viewer Not Loading Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-03-26 19:55 Environment: Jenkins 2.112 Lots of various plugins: ace-editor 1.1 active-directory 2.6 analysis-core 1.95 android-emulator 3.0 android-lint 2.6 ansicolor 0.5.2 ant 1.8 antisamy-markup-formatter 1.5 apache-httpcomponents-client-4-api 4.5.3-2.1 audit-trail 2.2 authentication-tokens 1.3 blueocean 1.4.2 blueocean-autofavorite 1.2.2 blueocean-bitbucket-pipeline 1.4.2 blueocean-commons 1.4.2 blueocean-config 1.4.2 blueocean-core-js 1.4.2 blueocean-dashboard 1.4.2 blueocean-display-url 2.2.0 blueocean-events 1.4.2 blueocean-git-pipeline 1.4.2 blueocean-github-pipeline 1.4.2 blueocean-i18n 1.4.2 blueocean-jira 1.4.2 blueocean-jwt 1.4.2 blueocean-personalization 1.4.2 blueocean-pipeline-api-impl 1.4.2 blueocean-pipeline-editor 1.4.2 blueocean-pipeline-scm-api 1.4.2 blueocean-rest 1.4.2 blueocean-rest-impl 1.4.2 blueocean-web 1.4.2 bouncycastle-api 2.16.2 branch-api 2.0.18 build-flow-plugin 0.20 build-monitor-plugin 1.12+build.201708172343 build-timeout 1.19 buildgraph-view 1.8 built-on-column 1.1 checkstyle 3.50 cloud-stats 0.18 cloudbees-bitbucket-branch-source 2.2.10 cloudbees-folder 6.4 collapsing-console-sections 1.7.0 command-launcher 1.2 conditional-buildstep 1.3.6 config-file-provider 2.18 cors-filter 1.1 credentials 2.1.16 credentials-binding 1.16 cvs 2.14 display-url-api 2.2.0 docker-commons 1.11 docker-plugin 0.15.0 docker-workflow 1.15.1 durable-task 1.22 email-ext 2.61 embeddable-build-status 1.9 envinject 2.1.5 envinject-api 1.5 external-monitor-job 1.7 favorite 2.3.1 gatling 1.2.2 ghprb 1.40.0 git 3.8.0 git-client 2.7.1 git-server 1.7 github 1.29.0 github-api 1.90 github-branch-source 2.3.3 google-oauth-plugin 0.5 google-play-android-publisher 1.7 gradle 1.28 groovy 2.0 groovy-postbuild 2.3.1 handlebars 1.1.1 handy-uri-templates-2-api 2.1.6-1.0 htmlpublisher 1.14 http_request 1.8.22 icon-shim 2.0.3 instant-messaging 1.35 jabber 1.36 jackson2-api 2.8.11.1 javadoc 1.4 jclouds-jenkins 2.14 jdk-tool 1.1 jenkins-design-language 1.4.2 jenkins-flowdock-plugin 1.1.8 jira 2.5 jira-steps 1.3.1 job-dsl 1.68 jobConfigHistory 2.18 jquery 1.12.4-0 jquery-detached 1.2.1 jsch 0.1.54.2 junit 1.24 ldap 1.20 m2-repo-reaper 1.0 m2release 0.14.0 mailer 1.20 mapdb-api 1.0.9.0 mask-passwords 2.11.0 matrix-auth 2.2 matrix-project 1.12 maven-plugin 3.1 mercurial 2.3 metrics 3.1.2.11 metrics-graphite
[JIRA] (JENKINS-50411) Job DSL Dynamic API Viewer Not Loading
Title: Message Title Maxfield Stewart updated an issue Jenkins / JENKINS-50411 Job DSL Dynamic API Viewer Not Loading Change By: Maxfield Stewart Getting the following stack trace, but I cannnot determine which plugin/class is causing the issue from the details so it's hard to be more helpful:Mar 26, 2018 7:46:20 PM org.eclipse.jetty.server.handler.ContextHandler$Context logWARNING: Error while serving [ http:// /job-dsl-api-viewer/data|http:// 10.202.78.42/job-dsl-api-viewer/data ] java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.corsfilter.AccessControlsFilter.doFilter(AccessControlsFilter.java:79) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:237) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:214) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:114) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at
[JIRA] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Alex Taylor commented on JENKINS-20427 Re: Build Parameter variable in branch name causes polling to detect false changes in GIT Mark Waite- I was finally able to reproduce this issue 100% if you have access to bitbucket. 1. Have Bitbucket repository with at least 10 branches 2. Create a freestyle job and configure it to use the git plugin but connect to a Bitbucket repository at `$BITBUCKET_URL/git/$PROJECT/$REPO.git` 3. Add a parameter called BRANCH and has the default value of ** 4. Use that parameter in the `Branches to build` section 5. Add a poll for changes of `* * * * *` so that it will build every minute 6. Add a shell step of something like "echo hello" 7. Run one build This will then launch a new build for every branch and then once that is done you will see it build every minute seeing changes. Let me know if that does not work for you because it has worked 2x for me 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-46602) [JDK 9] Pipeline fails immediately - ASM illegal argument exception
Title: Message Title Mark Waite updated JENKINS-46602 Jenkins / JENKINS-46602 [JDK 9] Pipeline fails immediately - ASM illegal argument exception Change By: Mark Waite Status: In Review 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-46219) Should fetch origin/refs even if repository exists in work tree
Title: Message Title Mark Waite commented on JENKINS-46219 Re: Should fetch origin/refs even if repository exists in work tree @pjdarton I don't understand (based on your description) how to duplicate the conditions you're seeing. Can you create a repeatable series of steps so that others could see the same behavior? 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-50389) Create a wiki page for badge plugin
Title: Message Title Marc Brugger resolved as Fixed Linking to documentation and changelog in github Jenkins / JENKINS-50389 Create a wiki page for badge plugin Change By: Marc Brugger 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.google.com/d/optout.
[JIRA] (JENKINS-50251) Rejected: org.apache.maven.model.Notifier
Title: Message Title Jesse Glick commented on JENKINS-50251 Re: Rejected: org.apache.maven.model.Notifier Filed follow-up PR 117. 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-50376) New Item sidebar link is not working
Title: Message Title EVarona commented on JENKINS-50376 Re: New Item sidebar link is not working Daniel Beck, Thanks. We will look into Simple Theme. The timing may coincide with a logo change we made. 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-47520) Probable race condition in deleting/loading branches of a multibranch project
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-47520 Probable race condition in deleting/loading branches of a multibranch project Change By: Sam Van Oort Priority: Critical 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-48050) Replace Declarative Docker agent directive with new implementation
Title: Message Title Nicolas De Loof updated an issue Jenkins / JENKINS-48050 Replace Declarative Docker agent directive with new implementation Change By: Nicolas De Loof Component/s: docker-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48050) Replace Declarative Docker agent directive with new implementation
Title: Message Title Nicolas De Loof assigned an issue to Andrew Bayer Jenkins / JENKINS-48050 Replace Declarative Docker agent directive with new implementation Change By: Nicolas De Loof Assignee: Nicolas De Loof Andrew Bayer 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-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor closed an issue as Duplicate Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Change By: Alex Taylor Status: Open Closed Resolution: Duplicate 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-49962) P4 Plugin: The P4 client uses jenkins_home instead of workspace as root.
Title: Message Title Raven Alef commented on JENKINS-49962 Re: P4 Plugin: The P4 client uses jenkins_home instead of workspace as root. I've seen this on Jenkins ver. 2.109 P4 Plugin 1.8.6 please look into 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-47301) JClouds aws-ec2 always tries to use default subnet
Title: Message Title Basil Peace commented on JENKINS-47301 Re: JClouds aws-ec2 always tries to use default subnet +1 VPC setting is not honored. I got 'No default VPC for this user' error. 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-50303) Mesos Offer Selection Attributes Mesos Plugin JEP-200
Title: Message Title Michael Gibbons commented on JENKINS-50303 Re: Mesos Offer Selection Attributes Mesos Plugin JEP-200 Thanks Jesse Glick Vincent Latombe Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33900) save/apply button is missing when editing mutibranch jobs created inside a github organization folder
Title: Message Title Matias De Santi commented on JENKINS-33900 Re: save/apply button is missing when editing mutibranch jobs created inside a github organization folder Another use case I'm facing is the ability of configuring project-specific access. I have a situation where a user does not belong to our organization but he still works for us in a specific project. Given the current configuration, I can either give that user no access at all to all of my organization's builds or he can see all of them. I would love to change this specifically in the project he's working. The final configuration would be something like this: At the organization level, anyone belonging to my organization can see all the builds. If a person does not belong to my organization, then I would link to give that person access to the builds of the project he is working on. Not all the organization's. Is there any way to do this currently? 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-47251) Wrong order of steps in 'script' block of 'post' block in Blue Ocean
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47251 Wrong order of steps in 'script' block of 'post' block in Blue Ocean Change By: Vivek Pandey Sprint: Blue Ocean 1.5 - Candidates beta 3 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-47251) Wrong order of steps in 'script' block of 'post' block in Blue Ocean
Title: Message Title Vivek Pandey resolved as Fixed Fixed in JENKINS-49297, PR https://github.com/jenkinsci/blueocean-plugin/pull/1694. Jenkins / JENKINS-47251 Wrong order of steps in 'script' block of 'post' block in Blue Ocean Change By: Vivek Pandey 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
[JIRA] (JENKINS-49709) Proxy Config broken in Bitbucket Branch Source Plugin
Title: Message Title Jaco Greyling commented on JENKINS-49709 Re: Proxy Config broken in Bitbucket Branch Source Plugin Hi Thomas, I see you've closed my issue, before I could comment, so let me do it here. Whilst your solution certainly looks elegant on face value I do have a problem with it. You're trying to cast to a new class (URL) and if it fails it throws a MalformedURLException. The problem I have with this is the fact that when you through the Exception you don't know where it comes from (unless you investigate the stack trace). With my solution I merely strip the scheme:// and leave the validation to HttpGet. This means that if there is indeed a problem with the original URL it will be thrown by the HTTP client (in this case Apache HTTP Client) which in my opinion is a better place for it. It makes errors handling easier to interpret in a runtime situation. Perhaps that is just my view, but happy to see what the maintainers decide to do with it Thanks for your input, though! Jaco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50405 Re: runATH leads to deadlock of resource consumption for core PR builds Code changed in jenkins User: R. Tyler Croy Path: Jenkinsfile http://jenkins-ci.org/commit/jenkins/0ca03d89c7e3a2b7855965e79b84dac2c0052119 Log: Merge pull request #3371 from raul-arabaolaza/JENKINS-50405-Quick_fix JENKINS-50405 Run the entire thing in docker && highmem node Compare: https://github.com/jenkinsci/jenkins/compare/9f599911f612...0ca03d89c7e3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50405 Re: runATH leads to deadlock of resource consumption for core PR builds Code changed in jenkins User: Raul Arabaolaza Path: Jenkinsfile http://jenkins-ci.org/commit/jenkins/9f8b5d691e3d11d65625497a1b876e1d47c466d0 Log: JENKINS-50405 Run the entire thing in docker && highmem node 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-50407) NPE from SandboxContinuable.run0 after restart
Title: Message Title Jesse Glick commented on JENKINS-50407 Re: NPE from SandboxContinuable.run0 after restart Sam Van Oort claimed a possible link to a couple of other bugs under investigation. 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-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title
Vivek Pandey commented on JENKINS-50406
Re: "Triggered Build" links broken with cloudbees-folder
To reproduce: Create a freestyle job downstream-job inside folder 'folder1', and have a pipeline job below to reproduce it:
stage "Stage 1"
stage ("Trigger jobs") {
build '/folder1/downstream-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-50399) Skipped steps show as passed - plugins uptodate but still nothing
Title: Message Title Paul Dragoonis updated an issue Jenkins / JENKINS-50399 Skipped steps show as passed - plugins uptodate but still nothing Change By: Paul Dragoonis This functionality is said to be RESOLVED in the blue ocean 1.2 sprint: https://issues.jenkins-ci.org/browse/JENKINS-39628I already have these plugins installed: Pipeline API - 2.26 Pipeline: Declarative - 1.2.7Blue Ocean 1.4.2Pipeline Graph Analysis Plugin 1.6 [~kzantow] [~coervivek] and co .. can you tell me why I'm not seeing the desired results?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-31456) Git 'Clean before checkout' step fails on Windows nodes
Title: Message Title Mark Waite resolved as Not A Defect Problem is outside the scope of the Jenkins git plugin and outside the scope of the Jenkins git client plugin. Windows file system won't delete files that are busy. The plugins work very hard to not leave files busy (close files as soon as possible, etc.). In this case, it appears to be either a command line git change that is needed, or a Windows file system semantic change. Both are outside the plugin scope. Jenkins / JENKINS-31456 Git 'Clean before checkout' step fails on Windows nodes Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-44924) pipeline groovy script - Sort a list with custom comparator or closure not sorting
Title: Message Title Jakub Pawlinski commented on JENKINS-44924 Re: pipeline groovy script - Sort a list with custom comparator or closure not sorting Just lost two hours thinking that I'm doing something wrong. the org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified field java.lang.Integer Name is ** anything but helpful. tried all possible sorts with closure, with comparator, with OrderBy, finally falled back to Script Console to learn that each attempt I made works fine. Decided to submit a bug, but found its already here. Would love to have proper "@NonCPS" requirement messages/exceptions or even a list to refer to rather than integer error. 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.
