[JIRA] (JENKINS-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak edited a comment on JENKINS-39332 Re: ApiSlRuntimeErrors.UnsafeCode error during analysis Hi,Which plugin version do you use?Do you use any of the LR 12.53 patches?Please also try the following - In your scenario, under results, results settings, do not set the 'automatically create a results directory for each scenario execution'.save and run again. !UncheckAllBoxesInResult.JPG|thumbnail!Please make sure you're following guidelines for setting Jenkins slave on the LR node - https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools#HPApplicationAutomationTools-SlavesandTestingToolsInstallation.Could you please upload the configuration -Jenkins configuration files - build.xml, Log, Config.xml - all obtainable from Jenkins folder on master- for example:C:\Jenkins\jjobs\\config.xml, c:\Jenkins\jobs\\builds\\log,build.xml.And any information possible on your configuration - i.e.:* Jenkins master and slave on same machine?* does the script and scenario reside on the same machine as the Jenkins node or you use UNC path?* Did you follow the above guidelines and verified there is no change in LR default configuration or analysis? (especially - result menu under * LoadRunner 12.53 without any patches?You can also send it to: kazak- at- hpe - dot - com.I will try to reproduce again and update. Thanks ahead Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+uns
[JIRA] (JENKINS-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-39332 ApiSlRuntimeErrors.UnsafeCode error during analysis Change By: Yafim Kazak Attachment: UncheckAllBoxesInResult.JPG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39193) Unable to use rbenv plugin together with ruby environment plugin
Title: Message Title Björn Häuser commented on JENKINS-39193 Re: Unable to use rbenv plugin together with ruby environment plugin This is exactly what I am trying The rbenv build wrapper works with ruby-environment 0.12 but does NOT work with ruby-environment 0.13. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39193) Unable to use rbenv plugin together with ruby environment plugin
Title: Message Title Björn Häuser updated JENKINS-39193 Jenkins / JENKINS-39193 Unable to use rbenv plugin together with ruby environment plugin Change By: Björn Häuser Status: Closed In Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39193) Unable to use rbenv plugin together with ruby environment plugin
Title: Message Title Björn Häuser commented on JENKINS-39193 Re: Unable to use rbenv plugin together with ruby environment plugin I am not able to re-open the issue, sorry for generating noise when trying. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40885) Environment variables are not exposed in pipeline script
Title: Message Title
Mor L created an issue
Jenkins / JENKINS-40885
Environment variables are not exposed in pipeline script
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2017/Jan/08 11:56 AM
Priority:
Minor
Reporter:
Mor L
Hi, Following this p4-plugin exposed variables - I would expect the following code to work:
node ('somenode')
{
stage ('checkout')
{
checkout([
$class: 'PerforceScm',
credential: '1----', //not actual value
populate: [
$class: 'ForceCleanImpl',
have: false,
parallel: [
enable: false,
minbytes: '1024',
minfiles: '1',
path: '/usr/local/bin/p4',
threads: '4'
],
pin: '',
quiet: true
],
workspace: [
$class: 'ManualWorkspaceImpl',
charset: 'none',
name: "jenkins-${NODE_NAME}-${JOB_NAME}",
pinHost: false,
spec: [
allwrite: false,
clobber: false,
compress: false,
line: 'LOCAL',
locked: false,
modtime: false,
rmdir: false,
streamName: '',
view: "//Depot/... //jenkins-${NODE_NAME}-${JOB_NAME}/..."
]
]
]
)
}
println "P4_CHANGELIST=${env.P4_CHANGELIST}"
println "P4_CLIENT=${env.P4_CLIENT}"
println "P4_PORT=${env.P4_PORT}"
println "P4_USER=${env.P4_USER}"
println "P4_TICKET=${env.P4_TICKET}"
pri
[JIRA] (JENKINS-40885) Environment variables are not exposed in pipeline script
Title: Message Title
Mor L updated an issue
Jenkins / JENKINS-40885
Environment variables are not exposed in pipeline script
Change By:
Mor L
Hi,Following this [p4-plugin exposed variables|https://github.com/jenkinsci/p4-plugin/blob/master/SETUP.md#exposed-variables] - I would expect the following code to work:{code:java}node ('somenode'){stage ('checkout'){checkout([$class: 'PerforceScm', credential: '1----', //not actual valuepopulate: [$class: 'ForceCleanImpl', have: false,parallel: [enable: false,minbytes: '1024',minfiles: '1', path: '/usr/local/bin/p4',threads: '4'], pin: '', quiet: true], workspace: [$class: 'ManualWorkspaceImpl', charset: 'none', name: "jenkins-${NODE_NAME}-${JOB_NAME}", pinHost: false, spec: [allwrite: false, clobber: false, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, streamName: '', view: "//Depot/... //jenkins-${NODE_NAME}-${JOB_NAME}/..."]]])}println "P4_CHANGELIST=${env.P4_CHANGELIST}"println "P4_CLIENT=${env.P4_CLIENT}"println "P4_PORT=${env.P4_PORT}"println "P4_USER=${env.P4_USER}"println "P4_TICKET=${env.P4_TICKET}"println "HUDSON_CHANGELOG_FILE=${env.HUDSON_CHANGELOG_FILE}"sh 'echo $P4_CHANGELIST'}{code}But all I get are nulls even though the build does have changes (i.e I purge the build history and reset build # to 1 - then run the job manually for the 1st time).{code:java}...P4 Task: syncing files at change: 1703...[Pipeline] }[Pipeline] // stage[Pipeline] echoP4_CHANGELIST=null[Pipeline] echoP4_CLIENT=null[Pipeline] echoP4_PORT=null[Pipeline] echoP4_USER=null[Pipeline] echoP4_TICKET=null[Pipeline] echoHUDSON_CHANGELOG_FILE=null[Pipeline] echonull[Pipeline] sh[UI-CSR-Dev-tag test] Running shell script+ echo[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{code}
[JIRA] (JENKINS-40885) Environment variables are not exposed in pipeline script
Title: Message Title
Mor L updated an issue
Jenkins / JENKINS-40885
Environment variables are not exposed in pipeline script
Change By:
Mor L
Hi,Following [p4-plugin exposed variables|https://github.com/jenkinsci/p4-plugin/blob/master/SETUP.md#exposed-variables] - I would expect the following code to work:{code:java}node ('somenode'){stage ('checkout'){checkout([$class: 'PerforceScm', credential: '1----', //not actual valuepopulate: [$class: 'ForceCleanImpl', have: false,parallel: [enable: false,minbytes: '1024',minfiles: '1', path: '/usr/local/bin/p4',threads: '4'], pin: '', quiet: true], workspace: [$class: 'ManualWorkspaceImpl', charset: 'none', name: "jenkins-${NODE_NAME}-${JOB_NAME}", pinHost: false, spec: [allwrite: false, clobber: false, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, streamName: '', view: "//Depot/... //jenkins-${NODE_NAME}-${JOB_NAME}/..."]]])}println "P4_CHANGELIST=${env.P4_CHANGELIST}"println "P4_CLIENT=${env.P4_CLIENT}"println "P4_PORT=${env.P4_PORT}"println "P4_USER=${env.P4_USER}"println "P4_TICKET=${env.P4_TICKET}"println "HUDSON_CHANGELOG_FILE=${env.HUDSON_CHANGELOG_FILE}"sh 'echo $P4_CHANGELIST'}{code}But all I get are nulls even though the build does have changes (i.e I purge the build history and reset build # to 1 - then run the job manually for the 1st time).{code:java}...P4 Task: syncing files at change: 1703...[Pipeline] }[Pipeline] // stage[Pipeline] echoP4_CHANGELIST=null[Pipeline] echoP4_CLIENT=null[Pipeline] echoP4_PORT=null[Pipeline] echoP4_USER=null[Pipeline] echoP4_TICKET=null[Pipeline] echoHUDSON_CHANGELOG_FILE=null[Pipeline] echonull[Pipeline] sh[UI-CSR-Dev-tag test] Running shell script+ echo[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{code}
[JIRA] (JENKINS-39193) Unable to use rbenv plugin together with ruby environment plugin
Title: Message Title
Björn Häuser commented on JENKINS-39193
Re: Unable to use rbenv plugin together with ruby environment plugin
The interesting thing is, that even when I try to generate the rbenv plugin via configure block it still does not work:
job.configure { it ->
it / 'buildWrappers' << 'ruby-proxy-object' {
'ruby-object'('ruby-class': 'Jenkins::Tasks::BuildWrapperProxy', pluginid: 'rbenv') {
object('ruby-class': 'RbenvWrapper', pluginid: 'rbenv') {
ruby__build__repository('https://github.com/sstephenson/ruby-build.git', [pluginid: 'rbenv', 'ruby-class': 'String'])
ruby__build__revision('master', [pluginid: 'rbenv', 'ruby-class': 'String'])
rbenv__root('$HOME/.rbenv', [pluginid: 'rbenv', 'ruby-class': 'String'])
rbenv__revision('master', [pluginid: 'rbenv', 'ruby-class': 'String'])
ruby__configure__opts([pluginid: 'rbenv', 'ruby-class': 'String'])
rbenv__repository('https://github.com/sstephenson/rbenv.git', [pluginid: 'rbenv', 'ruby-class': 'String'])
version(rubyVersion, [pluginid: 'rbenv', 'ruby-class': 'String'])
gem__list(['bundler', 'rake'].join(','), [pluginid: 'rbenv', 'ruby-class': 'String'])
configure__opts('', [pluginid: 'rbenv', 'ruby-class': 'String'])
ignore__local__version(['ruby-class': 'FalseClass', pluginid: 'rbenv'])
}
pluginid('rbenv', [pluginid: 'rbenv', 'ruby-class': 'String'])
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39193) Unable to use rbenv plugin together with ruby environment plugin
Title: Message Title Björn Häuser commented on JENKINS-39193 Re: Unable to use rbenv plugin together with ruby environment plugin Looks like a duplicate from JENKINS-37422, right? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39193) Unable to use rbenv plugin together with ruby environment plugin
Title: Message Title Björn Häuser commented on JENKINS-39193 Re: Unable to use rbenv plugin together with ruby environment plugin Or totally different problem, same as in JENKINS-38145 :/ i am lost here :/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34395) Support for building tags
Title: Message Title tim vdh commented on JENKINS-34395 Re: Support for building tags +1 Was enjoying the pipeline functionality until I hit this issue. My requirements: one job per repository run job on every commit and tag if tagged build release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34362) Delivery Pipeline should show pipeline parameters
Title: Message Title Jean-Marc Collin commented on JENKINS-34362 Re: Delivery Pipeline should show pipeline parameters Tommy Tynjä I will not be able to develop anything on Jenkins. No time and no skill for doing that. Sorry. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40797) Job DSL Custom config file with name not found
Title: Message Title Subhas Dandapani commented on JENKINS-40797 Re: Job DSL Custom config file with name not found Daniel Spilker Thank you so much for the fixes The plugin says 1.56 released, but we don't see it updated in Jenkins yet, can you please cross check if possible? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18862) Add an ability to specify external GIT repository for scripts
Title: Message Title Hakan Tandogan commented on JENKINS-18862 Re: Add an ability to specify external GIT repository for scripts Dominik Bartholdi, can I launch this "Import" step through a groovy script as well? That way, I could have a job that listens to my in-house git repository, and imports all new/changed scripts on every push. Which would be as good as specifiying an external GIT repo. Of course, if I manage the scripts externally, a way to forbid direct changes through the Jenkins UI would be necessary, but this is the next step Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40866) docker.inside() like syntax that keeps the workspace
Title: Message Title Michael Neale commented on JENKINS-40866 Re: docker.inside() like syntax that keeps the workspace Good writeup Tom Larrow. I actually do a very similar thing myself (but without k8s). I think this isn't an unreasonable scenario. So basically you want to effectively run a bunch of docker.inside like stages, each doing a different thing, but on the one shared workspace, on the one slave, until the pipeline is run, right? Ideally you would just specify the agent labelle once at the pipeline level, and then inside each stage, specify the docker image you want (and it would run on the same labelled slave in an ideal world). You are right to see if there is a way to do this without resorting to docker.inside. I think this may require some changes to declarative, so will see what Andrew Bayer says: When using agent .. docker, should checkout scm always happen outside of docker? (so the image doesn't need to have git)? If there is an agent specified with a label globally, and then in a stage an agent is specified which only requires docker, could it be made to use the one slave that is already provisioned? (this would cover this entire scenario). Not sure how "hacky" these things are and if this opens up other surprising side effects we don't want. In general, the simplest thing for a pipeline is one workspace on one slave, so I think it is reasonable that someone may expect things to work like this in this situation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40866) docker.inside() like syntax that keeps the workspace
Title: Message Title Michael Neale edited a comment on JENKINS-40866 Re: docker.inside() like syntax that keeps the workspace Good writeup [~tomlarrow]. I actually do a very similar thing myself (but without k8s). I think this isn't an unreasonable scenario. So basically you want to effectively run a bunch of docker.inside like stages, each doing a different thing, but on the one shared workspace, on the one slave, until the pipeline is run, right? Ideally you would just specify the agent labelle once at the pipeline level, and then inside each stage, specify the docker image you want (and it would run on the same labelled slave in an ideal world). You are right to see if there is a way to do this without resorting to docker script . inside. I think this may require some changes to declarative, so will see what [~abayer] says: * When using agent .. docker, should checkout scm always happen outside of docker? (so the image doesn't need to have git)?* If there is an agent specified with a label globally, and then in a stage an agent is specified which only requires docker, could it be made to use the one slave that is already provisioned? (this would cover this entire scenario). Not sure how "hacky" these things are and if this opens up other surprising side effects we don't want. In general, the simplest thing for a pipeline is one workspace on one slave, so I think it is reasonable that someone may expect things to work like this in this situation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscri
[JIRA] (JENKINS-22692) Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues
Title: Message Title Oleg Nenashev updated JENKINS-22692 Jenkins / JENKINS-22692 Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues Change By: Oleg Nenashev Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22024) Windows "services" shows Jenkins as not running.. but it is.
Title: Message Title Oleg Nenashev commented on JENKINS-22024 Re: Windows "services" shows Jenkins as not running.. but it is. It's possible that Jenkins master also runs away. Ideally requires some diagnostics on the winsw side Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12660) Fail to start the windows service when trying to launch slave node
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-12660 Fail to start the windows service when trying to launch slave node Change By: Oleg Nenashev Component/s: windows-slave-installer-module Component/s: windows-slaves-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12660) Fail to start the windows service when trying to launch slave node
Title: Message Title Oleg Nenashev commented on JENKINS-12660 Re: Fail to start the windows service when trying to launch slave node Still actual, I'd guess. Will verify it and cross-post a bug to WinSW if it still exists Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16730) Cannot install Jenkins slave in path with blanks
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-16730 Cannot install Jenkins slave in path with blanks Change By: Oleg Nenashev Component/s: windows-slave-installer-module Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17624) jenkins-slave - Need a more robust wrapper for Windows services.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-17624 jenkins-slave - Need a more robust wrapper for Windows services. Change By: Oleg Nenashev Component/s: windows-slave-installer-module Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22239) Doesn't create root folder when installing JNLP Windows Service
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-22239 Doesn't create root folder when installing JNLP Windows Service Change By: Oleg Nenashev Component/s: remoting Component/s: windows-slave-installer-module Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22239) Doesn't create root folder when installing JNLP Windows Service
Title: Message Title Oleg Nenashev commented on JENKINS-22239 Re: Doesn't create root folder when installing JNLP Windows Service Should be fixed by JENKINS-18578 once all changes are integrated Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23487) Add support of shared directories mapping to Windows slave services
Title: Message Title Oleg Nenashev started work on JENKINS-23487 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40854) REGRESSION - Run button is present but looks invisible
Title: Message Title Michael Neale commented on JENKINS-40854 Re: REGRESSION - Run button is present but looks invisible Thanks for looking into this Ivan Meredith - the ATH for this is: https://github.com/jenkinsci/blueocean-acceptance-test/blob/master/src/test/js/notMultibranch/freestyleRunning.js I think it looks for the run button the first time, but not the second. I actually modified the pipeline test to run it multiple times just the other week for this scenario, but apparently not freestyle: https://github.com/jenkinsci/blueocean-acceptance-test/blob/master/src/test/js/notMultibranch/pipelineRunning.js#L36 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16490) New versions of slave.jar not reliably pushed via JNLP
Title: Message Title Oleg Nenashev started work on JENKINS-16490 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38833) Remoting 3 Improvements
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38833 Remoting 3 Improvements Change By: Oleg Nenashev Component/s: windows-slave-installer-module Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38513) Unable to copy existing job, getting NoClassDefFoundError AbstractFolder)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38513 Re: Unable to copy existing job, getting NoClassDefFoundError AbstractFolder) Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderItemListener.java http://jenkins-ci.org/commit/ownership-plugin/4382b5cb1017e1fb7fdf828eca1696d78b427016 Log: [FIXED JENKINS-38513] - FolderItemListener should handle the case when Folder plugin is not installed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38353) Add support for multi-branch pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38353 Re: Add support for multi-branch pipeline Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderItemListener.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipAction.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipActionFactory.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipProperty.java http://jenkins-ci.org/commit/ownership-plugin/e6a4ff38fee7ae8642cdddf02adffeb0b23128a7 Log: JENKINS-38353 - Fix handling of Computed folders Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40710) Remoting plugin searches for case-sensitive headers
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40710 Re: Remoting plugin searches for case-sensitive headers Code changed in jenkins User: Daniel Beck Path: src/main/java/org/jenkinsci/remoting/engine/JnlpAgentEndpointResolver.java http://jenkins-ci.org/commit/remoting/628cf4cbae684b48a598ff062d430e747b160a54 Log: [FIX JENKINS-40710] Match headers case-insensitively Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40494) Administrative monitor for installed unsafe plugins
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40494 Re: Administrative monitor for installed unsafe plugins Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/UpdateSite.java core/src/main/java/jenkins/security/UpdateSiteWarningsConfiguration.java core/src/main/java/jenkins/security/UpdateSiteWarningsMonitor.java core/src/main/resources/hudson/PluginManager/table.jelly core/src/main/resources/hudson/PluginManager/table.properties core/src/main/resources/jenkins/security/Messages.properties core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/config.groovy core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/config.properties core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/help.html core/src/main/resources/jenkins/security/UpdateSiteWarningsConfiguration/style.css core/src/main/resources/jenkins/security/UpdateSiteWarningsMonitor/message.groovy core/src/main/resources/jenkins/security/UpdateSiteWarningsMonitor/message.properties test/src/test/java/hudson/model/UpdateSiteTest.java test/src/test/resources/plugins/warnings-update-center-malformed.json war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/c252a764024a94f018fe34dc58702885a48fff8f Log: JENKINS-40494 Process warnings from update sites (#2680) [FIX JENKINS-40494] Process warnings from update sites JENKINS-40494 Address review comments JENKINS-40494 Add warnings to available/update plugin manager tabs JENKINS-40494 Add tests JENKINS-40494 Address review feedback Add Comment
[JIRA] (JENKINS-40749) Set greater threshold for disk full by default
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40749 Re: Set greater threshold for disk full by default Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/diagnosis/HudsonHomeDiskUsageChecker.java http://jenkins-ci.org/commit/jenkins/7b51d56a7b5ad9854993c4e8c65d112c5f4e0b7c Log: [FIX JENKINS-40749] Set default disk free threshold to 10GB (#2695) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38175) Preparing Jenkins for shutdown via Manage Jenkins -> system-log-out.png throws an HTTP 405 (POST is required for jenkins.model.Jenkins.doQuietDown); works fine via "Prepare for
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38175 Re: Preparing Jenkins for shutdown via Manage Jenkins -> system-log-out.png throws an HTTP 405 (POST is required for jenkins.model.Jenkins.doQuietDown); works fine via "Prepare for Shutdown" link Code changed in jenkins User: Daniel Beck Path: core/src/main/java/jenkins/management/ReloadLink.java core/src/main/resources/jenkins/model/Jenkins/manage.jelly http://jenkins-ci.org/commit/jenkins/c9b878f4889659b889d03e24aa8e5cb6eb763b89 Log: [FIX JENKINS-38175] Fix various ManagementLink related bugs In the context menu, the 'post' flag was set iff 'requiresConfirmation' was set, even though they're independent (e.g. Prepare for shutdown requires the former but not the latter) /manage screen: The icon (t:summary) does not support POST or confirmation links, but was set to not link only if no confirmation was required (i.e. POST links did not POST when the icon was clicked now the icon is not clickable as a workaround) /manage screen: All links requiring confirmation did POST, which masked the fact that the 'Reload from disk' link wasn't set up to require POST (it was only broken in the context menu). Now, confirmation and POST are separate flags, and 'Reload from disk' link now requests POST. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40886) Enable JNLP4 protocol by default
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-40886 Enable JNLP4 protocol by default Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Jan/08 10:33 PM Priority: Major Reporter: Oleg Nenashev JNLP4 protocol has been soaked since 2.27, and with remoting-3.4 it should work fine. Time to upgrade it Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40886) Enable JNLP4 protocol by default
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40886 Enable JNLP4 protocol by default Change By: Oleg Nenashev Labels: remoting Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38353) Add support for multi-branch pipeline
Title: Message Title Oleg Nenashev updated JENKINS-38353 Should be fixed in 0.9.1 Jenkins / JENKINS-38353 Add support for multi-branch pipeline Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38353) Add support for multi-branch pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38353 Add support for multi-branch pipeline Change By: Oleg Nenashev Issue Type: New Feature Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38513) Unable to copy existing job, getting NoClassDefFoundError AbstractFolder)
Title: Message Title Oleg Nenashev updated JENKINS-38513 Should be fixed in 0.9.1 Jenkins / JENKINS-38513 Unable to copy existing job, getting NoClassDefFoundError AbstractFolder) Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com
[JIRA] (JENKINS-40395) Support for file input parameter type
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40395
Support for file input parameter type
Change By:
James Dumay
{panel:title=Support for this input type is unplanned}If you need support for this Input type please vote for this ticket and leave a comment explaining your use case with an example.{panel} In Scope* Support the "file" input parameter type
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40396) Support for run input parameter type
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40396
Support for run input parameter type
Change By:
James Dumay
{panel:title=Support for this input type is unplanned}If you need support for this Input type please vote for this ticket and leave a comment explaining your use case with an example.{panel} *In Scope** Support for run input parameter type
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40398) Support the "credentials" input parameter type
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40398
Support the "credentials" input parameter type
Change By:
James Dumay
{panel:title=Support for this input type is unplanned}If you need support for this Input type please vote for this ticket and leave a comment explaining your use case with an example.{panel} *In Scope** Support the "credentials" input parameter type
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40397) Support for run "list subversion tag" parameter type
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40397
Support for run "list subversion tag" parameter type
Change By:
James Dumay
{panel:title=Support for this input type is unplanned}If you need support for this Input type please vote for this ticket and leave a comment explaining your use case with an example.{panel} *In scope** Support for run "list subversion tag" parameter type
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40881) Request for option to filter based on the branch or build status options
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-40881 Request for option to filter based on the branch or build status options Change By: Brody Maclean Summary: Request for option to filter baed based on the branch or build status options Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40871
Running Pipeline Status with Milestone/Locks Needs Better visualization
Change By:
James Dumay
It is a common practice to batch changes in a pipeline via milestone/lock [1]. That way, resources are more efficiently used since there is only one instance of each stage running at a time. In practice, the milestone step aborts any instance of a pipeline if another pipeline instance, with new commits on it, reaches the milestone point.Currently, blue-ocean shows the steps that run on the pipeline in green, then the ones that didn't run on that instance (since a newer one hit the milestone) are rendered as grey. Users that need to track where in the pipeline their change is need to close their pipeline instance page, then manually look for the first non-aborted pipeline instance after.Ideally, Jenkins should provide a better way to track where the change is. Maybe show the pipeline stages that are running on a different instance (due to a milestone) in grey, but as running? Some other way?[1] https://jenkins.io/blog/2016/10/16/stage-lock-milestone/*Technical notes*{{CancelledCause}} contains the data needed to find out what run replaced one that was canceled. {{CancelledCause}} is set on the Runs {{InterruptedBuildAction}}.This [pull request|https://github.com/jenkinsci/pipeline-milestone-step-plugin/pull/7] should allow the {{CancelledCause}} to serialize all the data we need to do the work here. *Design notes*The run that does succeed should roll up all the changesets of the aborted runs that came before it since the last non-aborted run. Perhaps we should be doing this for whole series of successful runs?
Add Comment
[JIRA] (JENKINS-40887) Update ChangeSet API for a span of failing runs to be inclusive
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40887 Update ChangeSet API for a span of failing runs to be inclusive Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/08 11:36 PM Priority: Minor Reporter: James Dumay Scenario We have 5 runs: run 5 - Successful run 4 - Failure run 3 - Abort run 2 - Failure run 1 - Success When run 5, 4, 3's changesets are displayed it should include all the changes that occured back to run 2. This is so the developer has an accurate view of what changes made it through all steps in the pipeline. Add Comment
[JIRA] (JENKINS-39515) Failed to install Go 1.7.3
Title: Message Title Bradley Falzon commented on JENKINS-39515 Re: Failed to install Go 1.7.3 I've also had the same issue since Go 1.7.3, testing Go 1.8 I've used the following workaround. This should be good enough, comment is there's improvements. Open Jenkins Manage Jenkins Global Tool Configuration Go Installations... Add Go Name: Go 1.8 Delete install from golang.org installer Add installer: Shell command Label: Command (see below) Tool Home: . Save wget -q https://storage.googleapis.com/golang/go1.8beta2.linux-amd64.tar.gz rm -rf go tar xzf go1.8beta2.linux-amd64.tar.gz rm -f go1.8beta2.linux-amd64.tar.gz mv go/* . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39515) Failed to install Go 1.7.3
Title: Message Title
Bradley Falzon edited a comment on JENKINS-39515
Re: Failed to install Go 1.7.3
I've also had the same issue since Go 1.7.3, testing Go 1.8 I've used the following workaround. This should be good enough, comment is there's improvements (obviously make adjustments for the later Go versions as appropriate) .# Open Jenkins# Manage Jenkins# Global Tool Configuration# Go Installations...# Add Go# Name: Go 1.8# Delete install from golang.org installer# Add installer: Shell command# Label:# Command (see below)# Tool Home: .# Save{code:java}wget -q https://storage.googleapis.com/golang/go1.8beta2.linux-amd64.tar.gzrm -rf gotar xzf go1.8beta2.linux-amd64.tar.gzrm -f go1.8beta2.linux-amd64.tar.gzmv go/* .{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40888) Developer can paginate through the changesets of a run
Title: Message Title James Dumay created an issue Jenkins / JENKINS-40888 Developer can paginate through the changesets of a run Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/08 11:37 PM Priority: Minor Reporter: James Dumay In Scope Developer can click "show more" to reveal more changes for a run. Add Comment
[JIRA] (JENKINS-40888) Developer can paginate through the changesets of a run
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40888 Developer can paginate through the changesets of a run Change By: James Dumay In Scope* Developer can click "show more" to reveal more changes for a run. This is needed as exceeding the page size will be more common with the completion of JENKINS-40887. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38496) Aborted state should not look like failure
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-38496 Aborted state should not look like failure Change By: Brody Maclean Sprint: tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39515) Failed to install Go 1.7.3
Title: Message Title
Bradley Falzon edited a comment on JENKINS-39515
Re: Failed to install Go 1.7.3
I've also had the same issue since Go 1.7.3, testing Go 1.8 I've used the following workaround. This should be good enough, comment is there's improvements (obviously make adjustments for the later Go versions as appropriate).# Open Jenkins# Manage Jenkins# Global Tool Configuration# Go Installations...# Add Go# Name: Go 1.8# Delete install from golang.org installer# Add installer: Shell command# Label:# Command (see below)# Tool Home: .# Save{code:java} test -e ./bin/go && exit wget -q https://storage.googleapis.com/golang/go1.8beta2.linux-amd64.tar.gzrm -rf gotar xzf go1.8beta2.linux-amd64.tar.gzrm -f go1.8beta2.linux-amd64.tar.gzmv go/* .{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40856) Developer can see if the Pipeline execution is blocked waiting for resources
Title: Message Title James Dumay commented on JENKINS-40856 Re: Developer can see if the Pipeline execution is blocked waiting for resources Defer work on this until we get an idea from Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40856) Developer can see if the Pipeline execution is blocked waiting for resources
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40856 Developer can see if the Pipeline execution is blocked waiting for resources Change By: James Dumay Sprint: tethys release candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38496) Aborted state should not look like failure
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-38496 Aborted state should not look like failure Change By: James Dumay Assignee: Ivan Meredith Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40854) REGRESSION - Run button is present but looks invisible
Title: Message Title James Dumay started work on JENKINS-40854 Change By: James Dumay Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38496) Aborted state should not look like failure
Title: Message Title Brody Maclean edited a comment on JENKINS-38496 Re: Aborted state should not look like failure Zeplin link https://zpl.io/H3odiIcon = Remove – https://design.google.com/icons/#ic_removeMockup !Aborted.png|thumbnail! !Screen Shot 2017-01-09 at 11.27.00 am.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38496) Aborted state should not look like failure
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-38496 Aborted state should not look like failure Change By: Brody Maclean Attachment: Screen Shot 2017-01-09 at 11.27.00 am.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40672) Consistent state for completed input steps
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40672 Consistent state for completed input steps Change By: James Dumay Sprint: tethys, christmas , post-release Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40889) cannot apply and save base clearcase dynamic views
Title: Message Title satish k created an issue Jenkins / JENKINS-40889 cannot apply and save base clearcase dynamic views Issue Type: Bug Assignee: Praqma Support Attachments: Clearcase posted in JIRA issues.docx Components: clearcase-plugin Created: 2017/Jan/09 12:33 AM Environment: Jenkins 2.19.1; Clear case 8, Base clear case , Dynamic views Labels: jenkins clearcaseplugin Priority: Blocker Reporter: satish k Helllo Team, I'm trying to implement "Pipeline as a code" with "Pipeline script from SCM" Base Clear case; Dynamic views. I'm wondering when save or apply worked for free style project with same configurations didn't work for "pipeline script from SCM" PFA for more information on configuration and error screen shots.
[JIRA] (JENKINS-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title Brody Maclean started work on JENKINS-40877 Change By: Brody Maclean Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40877 Display links to Github PR and Branch on Pipeline Result Change By: James Dumay *Design Brief*Developers desire a link back to Github for or branch and pull requests contextually in Blue Ocean.At a minimum it would be useful if a developer could click through to the web interface on Github for a branch or PR from the Run screen.*Scope** Modify the Run screen design so we can surface a branch or PR link * If the run is for a PR then it should read "Pull Request" instead of "Branch" *Notes*May want to think about what we want to show if the user clicks on the branches name e.g. does that take you to Github or does it take you to Activity with the filter set for that branch.Decide if we want to open in a new window vs existing window (new window sounds good?) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay commented on JENKINS-39794 Re: API to check that MBP indexing has completed Blocking Cliffs Creation epic Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39794) API to check that MBP indexing has completed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39794 API to check that MBP indexing has completed Change By: James Dumay Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40854) REGRESSION - Run button is present but looks invisible
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40854 Re: REGRESSION - Run button is present but looks invisible Code changed in jenkins User: Ivan Meredith Path: src/test/js/notMultibranch/freestyleRunning.js http://jenkins-ci.org/commit/blueocean-acceptance-test/9abf832727c716ee86fc1f7ca4fc216f13d78254 Log: JENKINS-40854 Check to make sure that run button is showing correctly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39341) Update favourite card design
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39341 Update favourite card design Change By: James Dumay Priority: Trivial Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39056) Empty state component not center positioned for IE
Title: Message Title James Dumay resolved as Postponed New empty states Jenkins / JENKINS-39056 Empty state component not center positioned for IE Change By: James Dumay Status: Open Resolved Resolution: Postponed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39512) Blue Ocean should allow me to get to the GitHub link for a Pipeline run
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-39512 Blue Ocean should allow me to get to the GitHub link for a Pipeline run Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39635) Right click on expander should not open the test result
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39635 Right click on expander should not open the test result Change By: James Dumay Sprint: post- release candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39860) messages column in blue ocean should display if there are more commits
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39860 messages column in blue ocean should display if there are more commits Change By: James Dumay Sprint: tasman, post- release candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38088) Allow re-run of successful builds
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38088 Allow re-run of successful builds Change By: James Dumay Sprint: atlantic, post- release candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36083) Error handling
Title: Message Title Brody Maclean closed an issue as Duplicate Jenkins / JENKINS-36083 Error handling Change By: Brody Maclean Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40326) Pipeline results (karaoke) doesn't reload when master is restarted
Title: Message Title Michael Neale assigned an issue to Tom FENNELLY Jenkins / JENKINS-40326 Pipeline results (karaoke) doesn't reload when master is restarted Change By: Michael Neale Assignee: Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40326) Pipeline results (karaoke) doesn't reload when master is restarted
Title: Message Title Michael Neale commented on JENKINS-40326 Re: Pipeline results (karaoke) doesn't reload when master is restarted Tom FENNELLY do you mind picking this one up some time - as you did it nicely on other screens, its just karaoke that doensn't realise the session has expired etc. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40326) Pipeline results (karaoke) doesn't reload when master is restarted
Title: Message Title Michael Neale edited a comment on JENKINS-40326 Re: Pipeline results (karaoke) doesn't reload when master is restarted [~tfennelly] do you mind picking this one up some time - ? as you did it nicely on other screens, its just karaoke that doensn't realise the session has expired etc. You would think this is an edge case, but it matters a lot to some people who often work on the infra (eg Tyler) who love using karaoke (and sometimes they bounce the master). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39055) CSS3 Animations not working on IE
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39055 CSS3 Animations not working on IE Change By: James Dumay Sprint: release candidate tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39055) CSS3 Animations not working on IE
Title: Message Title James Dumay assigned an issue to Tom FENNELLY Jenkins / JENKINS-39055 CSS3 Animations not working on IE Change By: James Dumay Assignee: Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39894) REGRESSION: SSE broken on MS Edge and IE11
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39894 REGRESSION: SSE broken on MS Edge and IE11 Change By: James Dumay Sprint: release candidate tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40326) Pipeline results (karaoke) doesn't reload when master is restarted
Title: Message Title Michael Neale edited a comment on JENKINS-40326 Re: Pipeline results (karaoke) doesn't reload when master is restarted [~tfennelly] do you mind picking this one up some time - as you did it nicely on other screens, its just karaoke that doensn't realise the session has expired etc. You would think this is an edge case, but it matters a lot to some people who often work on the infra (eg Tyler) who love using karaoke (and sometimes they bounce the master). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39057) JDL text is not centered vertically on IE
Title: Message Title James Dumay resolved as Won't Fix IE11 is going to be EOL'd this year so I don't think this is important unless it breaks functionality. Jenkins / JENKINS-39057 JDL text is not centered vertically on IE Change By: James Dumay Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-40302) Handle Pipelines that have many stages
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40302 Handle Pipelines that have many stages Change By: James Dumay Sprint: post- release candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40032) Handle errors and 404s consistently
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40032 Handle errors and 404s consistently Change By: James Dumay Sprint: tasman, post- release candidate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40749) Set greater threshold for disk full by default
Title: Message Title Daniel Beck updated JENKINS-40749 Jenkins / JENKINS-40749 Set greater threshold for disk full by default Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40494) Administrative monitor for installed unsafe plugins
Title: Message Title Daniel Beck updated JENKINS-40494 Jenkins / JENKINS-40494 Administrative monitor for installed unsafe plugins Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38175) Preparing Jenkins for shutdown via Manage Jenkins -> system-log-out.png throws an HTTP 405 (POST is required for jenkins.model.Jenkins.doQuietDown); works fine via "Prepare for
Title: Message Title Daniel Beck updated JENKINS-38175 Jenkins / JENKINS-38175 Preparing Jenkins for shutdown via Manage Jenkins -> system-log-out.png throws an HTTP 405 (POST is required for jenkins.model.Jenkins.doQuietDown); works fine via "Prepare for Shutdown" link Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title Alejandro del Castillo commented on JENKINS-40871 Re: Running Pipeline Status with Milestone/Locks Needs Better visualization I think there is value in keeping the pipelines that were aborted. From a user's point of view, his submission creates a pipeline instance and that's all he cares. The tricky part is how to convey visually that a pipeline was aborted/replaced by another one. A link (like the one you proposed) works, but maybe it's possible to show that information on the pipeline visual itself instead of a link. Maybe we can show the running stages on the pipeline view of the aborted pipeline with a different color? Not sure if that "fits" with blue ocean paradigmsjust a suggestion to consider since I am not a UX person. Thanks for taking the time to look at this issue! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39800) Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException
Title: Message Title Kevin Logan commented on JENKINS-39800 Re: Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException Has anyone been able to look at this? It's been a while with no response. Daniel Beck I believe that is what is causing this error when I was looking through the code, but I'm not great with java. Any ideas on a possible workaround? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30700) Make Cobertura plug-in support the workflow plugin
Title: Message Title Yibin Sheng commented on JENKINS-30700 Re: Make Cobertura plug-in support the workflow plugin Aravind Krishna just as Kamil P posted. BTW, you may use the jenkins groovy syntax box to generate the DSL. To report multiple files in different module in one site, you may put the report dir empty and the reported files pointing to its file path. That's all I know about the plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39800) Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException
Title: Message Title Daniel Beck commented on JENKINS-39800 Re: Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException Don't continue the process past the lifetime of its invoking shell. If my guess is true, and the problem is that Jenkins is trying to kill a process that suddenly stops existing, don't make it kill it by quitting in time. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-40877 Display links to Github PR and Branch on Pipeline Result Change By: Brody Maclean Attachment: Aborted.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title Brody Maclean commented on JENKINS-40877 Re: Display links to Github PR and Branch on Pipeline Result Zeplin Link https://zpl.io/H3odihttps://material.io/icons/#ic_launch #FF @ 50% opacity Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title Brody Maclean stopped work on JENKINS-40877 Change By: Brody Maclean Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40877) Display links to Github PR and Branch on Pipeline Result
Title: Message Title Brody Maclean assigned an issue to James Dumay Jenkins / JENKINS-40877 Display links to Github PR and Branch on Pipeline Result Change By: Brody Maclean Assignee: Brody Maclean James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40885) Environment variables are not exposed in pipeline script
Title: Message Title
Cedric Perthuis edited a comment on JENKINS-40885
Re: Environment variables are not exposed in pipeline script
I can reproduce the same issue on a windows slave with jenkins 2.3 (https://hub.docker.com/_/jenkins/, 2.32.1-alpine) and P4 Plugin 1.4.12.There's a workaround which worked for me as explained on in JENKINS-37584.To get the workaround to run, you have to run the script several times and whitelist some security exceptions in 'Manage Jenkins > In-process Script Approval'.{code:java}println "${env.P4_CHANGELIST}" //nullprintln "${env.P4_USER}" //nullprintln "${env.P4_PORT}" //nullprintln "${env.P4_TICKET}" //nullprintln currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"] //correctprintln currentBuild.getRawBuild().getEnvironment()["P4_USER"] //correctprintln currentBuild.getRawBuild().getEnvironment()["P4_PORT"] //correctprintln currentBuild.getRawBuild().getEnvironment()["P4_TICKET"] //correct{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40885) Environment variables are not exposed in pipeline script
Title: Message Title
Cedric Perthuis commented on JENKINS-40885
Re: Environment variables are not exposed in pipeline script
I can reproduce the same issue on a windows slave with jenkins 2.3 (https://hub.docker.com/_/jenkins/, 2.32.1-alpine) and P4 Plugin 1.4.12. There's a workaround which worked for me as explained on JENKINS-37584. To get the workaround to run, you have to run the script several times and whitelist some security exceptions in 'Manage Jenkins > In-process Script Approval'.
println "${env.P4_CHANGELIST}" //null
println "${env.P4_USER}" //null
println "${env.P4_PORT}" //null
println "${env.P4_TICKET}" //null
println currentBuild.getRawBuild().getEnvironment()["P4_CHANGELIST"] //correct
println currentBuild.getRawBuild().getEnvironment()["P4_USER"] //correct
println currentBuild.getRawBuild().getEnvironment()["P4_PORT"] //correct
println currentBuild.getRawBuild().getEnvironment()["P4_TICKET"] //correct
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optou
[JIRA] (JENKINS-40660) Parallel Test Stage in Blue Ocean marks build as successful before completing
Title: Message Title
Michael Neale commented on JENKINS-40660
Re: Parallel Test Stage in Blue Ocean marks build as successful before completing
thanks Roni Frantchi - is there any way to reduce that further? It isn't really reproducible in that form as there is a lot going on (and can't really copy and paste it to see it). I am not sure if it is that specific use of parallel. Some things to try: use stage('test') {... (ie block scoped stage. Try commenting out the junit archive step to see if that is tricking it...
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36083) Error handling
Title: Message Title Brody Maclean reopened an issue Jenkins / JENKINS-36083 Error handling Change By: Brody Maclean Resolution: Duplicate Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40737) Managed script/configs aren't found/cannot be read/throw exceptions
Title: Message Title Rick Liu commented on JENKINS-40737 Re: Managed script/configs aren't found/cannot be read/throw exceptions Hi~ Somehow I still can't find the 2.15.3 release from Jenkins plugin repo. Could you check again? http://updates.jenkins-ci.org/download/plugins/config-file-provider/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
