[JIRA] (JENKINS-33869) Run tests for previous commits
Title: Message Title Alexander Vorobiev updated an issue Jenkins / JENKINS-33869 Run tests for previous commits Change By: Alexander Vorobiev Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-43038 Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins 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-43031) On Delete project Workspace remains
Title: Message Title Oleg Nenashev commented on JENKINS-43031 Re: On Delete project Workspace remains The best communication way is the jenkins-users mailing list: https://groups.google.com/forum/#!forum/jenkinsci-users This is a bugtracker. The workspace deletion logic should be invoked during the project deletion in a background task IIRC. If this task fails due to whatever reason, Jenkins does not retry to cleanup such workspaces for deleted jobs. But maybe I am wrong. 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-42508) Class org.apache.commons.jexl.util.PropertyExecutor can not access a member of class javaposse.jobdsl.plugin.actions.GeneratedObjectsRunAction with modifiers "public"
Title: Message Title Simon van der Veldt commented on JENKINS-42508 Re: Class org.apache.commons.jexl.util.PropertyExecutor can not access a member of class javaposse.jobdsl.plugin.actions.GeneratedObjectsRunAction with modifiers "public" Sorry for the silence, whilst I can easily trigger this issue with out live seedjob, it's been hard pinpointing what exactly causes it, so I haven't been able to come up with a simple reproducible test case I can share. It might have something to do with the amount of jobs created (we have over 2500). I Will try the new version with our live seedjob though and see if it still happens. 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-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Félix Belzunce Arcos commented on JENKINS-42831 Re: Enable StartTls is always TRUE in the UI Yes, it is normal since it is not already merged. On any case this is a minor issue, because: 1. StartTLS was always enabled by default 2. It is an UI issue, on disk is correctly saved. 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-37203) "Override Authentication Token?" do not work
Title: Message Title Alexandru Calistru commented on JENKINS-37203 Re: "Override Authentication Token?" do not work Do you have any deadline on adding token override for Pipeline ? Thank you Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40545) NPE in console log when I configure a folder in a folder or a pipeline in a folder
Title: Message Title Nicolas Dupont-Jubien commented on JENKINS-40545 Re: NPE in console log when I configure a folder in a folder or a pipeline in a folder We have the same warnings for the plugins filters when opening the Jenkins System configure page. WARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /jenkins/configure. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:72) at hudson.Functions.filterDescriptors(Functions.java:1790) Here is the Jenkins war version: jenkins.war.LTS.2.32.3 The issue appears after an update of the Jenkins pipeline plugins and dependancies: name: credentials-binding version: '1.10' name: docker-commons version: '1.5' name: docker-workflow version: '1.9' name: durable-task version: '1.12' name: pipeline-build-step version: '2.4' name: pipeline-graph-analysis version: '1.1' name: pipeline-input-step version: '2.5' name: pipeline-milestone-step version: '1.3' name: pipeline-model-api version: '1.0' name: pipeline-model-declarative-agent version: '1.0' name: pipeline-model-definition version: '1.0' name: pipeline-rest-api version: '2.4' name: pipeline-stage-step version: '2.2' name: pipeline-stage-tags-metadata version: '1.0' name: pipeline-stage-view version: '2.4' name: workflow-aggregator version: '2.5' name: workflow-api version: '2.8' name: workflow-basic-steps version: '2.3' name: workflow-cps version: '2.24' name: workflow-cps-global-lib version: '2.5' name: workflow-durable-task-step version: '2.8' name: workflow-job version: '2.9' name: workflow-multibranch version: '2.9.2' name: workflow-scm-step version: '2.3' name: workflow-step-api version: '2.7'
[JIRA] (JENKINS-43084) pipeline multibranch job can't be triggered by upstream job
Title: Message Title Hubert Li created an issue Jenkins / JENKINS-43084 pipeline multibranch job can't be triggered by upstream job Issue Type: Bug Assignee: Denis Saponenko Components: pipeline-multibranch-defaults-plugin Created: 2017/Mar/24 8:59 AM Priority: Minor Reporter: Hubert Li I created a pipeline multibranch job, the Jenkinsfile call the library method to set the properties: properties([buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '8', numToKeepStr: '10')), pipelineTriggers([upstream(threshold: hudson.model.Result.SUCCESS, upstreamProjects: FullJobName)])]) The upstream job is triggered by other project. After the upstream project is completed building with success result, my pipeline multibranch job can't be triggered. I manually build the upstream job or the pipeline multibranch job, then in the next time after the upstream job building, my pipeline multibranch job can be triggered. Before I do the test, I already build the pipeline multibranch job, (no upstream job at that time) and I can see the job is configured the upstream project in UI. I also created a freestyle test job, which is configured triggering by the same upstream job, this freestyle test job cab be triggered by it in any case.
[JIRA] (JENKINS-43084) pipeline multibranch job can't be triggered by upstream job
Title: Message Title Hubert Li updated an issue Jenkins / JENKINS-43084 pipeline multibranch job can't be triggered by upstream job Change By: Hubert Li I created a pipeline multibranch job, the Jenkinsfile call the library method to set the properties: properties([buildDiscarder(logRotator(artifactDaysToKeepStr: '', artifactNumToKeepStr: '', daysToKeepStr: '8', numToKeepStr: '10')), pipelineTriggers([upstream(threshold: hudson.model.Result.SUCCESS, upstreamProjects: FullJobName)])])The upstream job is triggered by other project. After the upstream project is completed building with success result, my pipeline multibranch job can't be triggered. I manually build the upstream job or the pipeline multibranch job, then in the next time after the upstream job building, my pipeline multibranch job can be triggered.Before I do the test, I already build the pipeline multibranch job, (no upstream job at that time) and I can see the job is configured the upstream project in UI. I also created a freestyle test job, which is configured triggering by the same upstream job, this freestyle test job cab can be triggered by it in any case. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42048) Cannot Connect, PID NumberFormatException
Title: Message Title Sascha Vujevic commented on JENKINS-42048 Re: Cannot Connect, PID NumberFormatException Could this logoutput be avoided by setting a loglevel in Jenkins ? The logfile looks not pretty and it's not easy to filter the relevant logoutput. Thank you for your 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-41726) form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response
Title: Message Title Roger Lei commented on JENKINS-41726 Re: form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response Janario Oliveira Hi Janario, sorry for the late reply. I've tried both 127.0.0.1 and localhost. Almost got the error right after the job is running. I'm not sure if I've set the Form Authentication setting correctly under global configuration . I'm running on Jenkins1.610 with JDK version of 1.6. Does it require a higher version of Jenkins or JDK? Could you please advice if there's any document on how to setup and using this 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-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Thorsten Meinl commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" I have a vague feeling that this problem occurs when there is more than one job running on the slave. If I have time, I will try to restrict the Windows slaves to one slot and see if this makes the problem go away. Maybe some of you can try this, too. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title
valentina armenise updated an issue
Jenkins / JENKINS-43076
dropdownlist element does not define html name tag
Change By:
valentina armenise
The Dropdown jelly form does not use [the name attribute|https://github.com/jenkinsci/jenkins/blob/08def67a18eee51de9f3f99bc2a792fee1c160e0/core/src/main/resources/lib/form/dropdownList.jelly#L34]. This makes it difficult to reference in selenium tests. Similarly to what [dropDownListSelector does|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/lib/form/dropdownDescriptorSelector.jelly#L54] it should have something like{noformat} {noformat}in its jelly file.For all config files using a dropDownList in fact the [Form Element Path plugin|https://wiki.jenkins-ci.org/display/JENKINS/Form+Element+Path+Plugin] does not generate the path correctly (it would simply add "/" or "/" followed by a number cause it cannot compute the unique id using its name). For an example see [ https://github.com/jenkinsci/acceptance-test-harness/blob/47ae4d5cd6e1c17308c1dc2e28ee6b3b11bc3a0d/src/main/java/org/jenkinsci/test/acceptance/po/DumbSlave.java#L23 ] Besides that, the name field is defined and not used in the jelly file so .However, note that fixing this will make all selenium tests which use the form path plugin on dropdownList (ass SSh slave plugin selenium test) fail. Fixing this will require a fix of all of them with the new path. I think am not sure it should be fixed anyways 's worth it .
Add Comment
This message was sent by Atlassian
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-43076 dropdownlist element does not define html name tag Change By: valentina armenise Comment: Note that fixing this will make all selenium tests which use the form path plugin on dropdownList (ass SSh slave plugin selenium test) fail. Fixing this will require a fix of all of them with the new path 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-43076) dropdownlist element does not define html name tag
Title: Message Title valentina armenise commented on JENKINS-43076 Re: dropdownlist element does not define html name tag Note that fixing this will make all selenium tests which use the form path plugin on dropdownList (ass SSh slave plugin selenium test) fail. Fixing this will require a fix of all of them with the new path 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-12163) Cleaning VM before start next job in queue.
Title: Message Title Alexandru Calistru commented on JENKINS-12163 Re: Cleaning VM before start next job in queue. Do you have any updates on fixing this issue for Pipelines ? Thank you Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37717) CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
Title: Message Title
Andy Wang commented on JENKINS-37717
Re: CHANGES_SINCE_LAST_SUCCESS is not expanded for jenkins pipeline
Thanks David van Laatum I've encountered a situation here: Before pipeline was put into use, I used normal Freestyle job. In build actions, I used Inject environment vairables from a properties file in my workspace. The properties in the file contained the necessary variables which I would use in my email. So my email ext plugin's body part was like below:
"status">
"info">"6">$rom_type $BuildType Build $status
"main round_border">
$rom_type $BuildType Build $status
Build Artifact:
"$ROM_URL">$ROM_URL
The variables like rom_type and ROM_URL was set in the properties file. After migrated the job to pipeline, the variables in the properties file are failed to work. I've tried use withEnv and """ """ to wrap my email content. It is a temporary workaround but the {CHANGES_SINCE_LAST_SUCCESS, reverse="true", showPaths="true"} would fail to work. So I tried use ''' ''' to wrap my content. The {CHANGES_SINCE_LAST_SUCCESS, reverse="true", showPaths="true"} worked, but variables failed. What should I do to keep both work? Thank you.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message
[JIRA] (JENKINS-41515) Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not a subtype
Title: Message Title SCM/JIRA link daemon commented on JENKINS-41515 Re: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not a subtype Code changed in jenkins User: Dominik Stadler Path: pom.xml http://jenkins-ci.org/commit/jacoco-plugin/4baa40f8fb07cda1159880769e0f92024183d152 Log: JENKINS-41515: Update Jenkins parent to 1.625.3 to be able to test with current pipeline-plugin Adjust dependencies and add some exclusions to remove a number of unnecessary jars from the resulting hpi file 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-43085) Downstream promotion is getting auto approved on approving upstream promotion
Title: Message Title Saga P created an issue Jenkins / JENKINS-43085 Downstream promotion is getting auto approved on approving upstream promotion Issue Type: Bug Assignee: Oleg Nenashev Attachments: Capture.PNG Components: promoted-builds-plugin Created: 2017/Mar/24 10:01 AM Environment: Jenkins ver. 2.32 OS- Windows 7 Promoted build plugin 2.28 Priority: Critical Reporter: Saga P The Promotions are configured with these upstream criterias: A: manual B: manual, when A is promoted C: manual, when B is promoted 1.User Approves promotion A 2.User Clicks on the approve button of Promotion C. 3.User Approves promotion A On following the above steps promotion C is getting auto promoted after Promotion B is approved. First of all the approve buttons of downstream promotions should be disabled if one upstream promotion has not happened and downstream promotion has dependency on it.
[JIRA] (JENKINS-42428) Jenkins master throwing java.io.IOException when running pipeline in swarm client
Title: Message Title Mathias Rühle commented on JENKINS-42428 Re: Jenkins master throwing java.io.IOException when running pipeline in swarm client It's polluting our logs, too. Please fix soon. 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-35536) Monitoring nodes shouldn't requre Overall/Administer permission
Title: Message Title Oleg Nenashev assigned an issue to evernat Jenkins / JENKINS-35536 Monitoring nodes shouldn't requre Overall/Administer permission Change By: Oleg Nenashev Assignee: Oleg Nenashev evernat 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-41515) Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not a subtype
Title: Message Title centic resolved as Fixed Fixed on master by adding some excludes in the pom, this will become available with version 2.2.1 and newer. Jenkins / JENKINS-41515 Provider org.apache.xerces.jaxp.SAXParserFactoryImpl not a subtype Change By: centic 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.c
[JIRA] (JENKINS-14750) Unprivileged view permissions for monitoring
Title: Message Title Oleg Nenashev commented on JENKINS-14750 Re: Unprivileged view permissions for monitoring -1 for the Unprivileged access as a Jenkins Security team member. It is not only about gc() invocation. Operations like HeapDump collection may actually expose sensitive information. Thread termination by users may also cause cause significant damage. Etc. The thing which could be done is a special permission (e.g. "Computer.VIEW_MONITORING" impled By "Jenkins.ADMINISTER") with appropriate disclaimer in the documentation. 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-35536) Monitoring nodes shouldn't requre Overall/Administer permission
Title: Message Title Oleg Nenashev resolved as Duplicate Jenkins / JENKINS-35536 Monitoring nodes shouldn't requre Overall/Administer permission Change By: Oleg Nenashev Status: Open Resolved 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-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Mihai Stoichitescu commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" Thorsten Meinl we encounter this error on machines that only have 1 executor setup. Maybe this happens if there are flyweight executors running on the 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-43086) After Security-161 ssh-slave plugin requires to select a verification strategy
Title: Message Title valentina armenise created an issue Jenkins / JENKINS-43086 After Security-161 ssh-slave plugin requires to select a verification strategy Issue Type: Improvement Assignee: Oliver Gondža Components: acceptance-test-harness, ssh-slaves-plugin Created: 2017/Mar/24 10:28 AM Priority: Minor Reporter: valentina armenise After https://github.com/jenkinsci/ssh-slaves-plugin/commit/11ec7e7a10ae97ba7bef02dcc3a353136ccc576d the ssh-slave plugin requires to select a verification strategy to control how Jenkins verifies the SSH key presented by the remote host whilst connecting. The ssh-slave plugins test in the acceptance-test-harness suite will then fail when using version of ssh-slave plugin higher than 1.15 cause the default verification strategy is `Known host verification strategy` which implies to add the ssh keys of the slave to the known hosts file of the host. So we either need to refactor the tests to take further steps and ensure verification is successful or enforce a Non verification strategy. Although the enforced plugin version is 1.11 I think we should align the test to latest release and upgrade it to use 1.15 to make sure that other tests which use the latest version of the ssh-slave plugin run successfull.
[JIRA] (JENKINS-43086) After Security-161 ssh-slave plugin requires to select a verification strategy
Title: Message Title valentina armenise assigned an issue to valentina armenise Jenkins / JENKINS-43086 After Security-161 ssh-slave plugin requires to select a verification strategy Change By: valentina armenise Assignee: Oliver Gondža valentina armenise 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-43086) After Security-161 ssh-slave plugin requires to select a verification strategy
Title: Message Title valentina armenise started work on JENKINS-43086 Change By: valentina armenise 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-43086) After Security-161 ssh-slave plugin requires to select a verification strategy
Title: Message Title valentina armenise updated an issue Jenkins / JENKINS-43086 After Security-161 ssh-slave plugin requires to select a verification strategy Change By: valentina armenise After [https://github.com/jenkinsci/ssh-slaves-plugin/commit/11ec7e7a10ae97ba7bef02dcc3a353136ccc576d] the ssh-slave plugin requires to select a verification strategy to control how Jenkins verifies the SSH key presented by the remote host whilst connecting.The ssh-slave plugins test in the acceptance-test-harness suite will then fail when using version of ssh-slave plugin higher than 1.15 cause the default verification strategy is `Known host verification strategy` which implies to add the ssh keys of the slave to the known hosts file of the host.So we either need to refactor the tests to take further steps and ensure verification is successful or enforce a Non verification strategy. Although the enforced plugin version is 1.11 I think we should align the test to latest release and upgrade it to use 1.15 to make sure that other tests which use the latest version of the ssh-slave plugin run successfull. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43076) dropdownlist element does not define html name tag
Title: Message Title valentina armenise commented on JENKINS-43076 Re: dropdownlist element does not define html name tag PR here https://github.com/jenkinsci/jenkins/pull/2820. However I closed it cause fixing it will cause too much headache. I am not sure we should fix it but at least this JIRA will track the behaviour of dropdownList with form path 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-43086) After Security-161 ssh-slave plugin requires to select a verification strategy
Title: Message Title valentina armenise updated JENKINS-43086 Jenkins / JENKINS-43086 After Security-161 ssh-slave plugin requires to select a verification strategy Change By: valentina armenise 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-43078) Admin users could be defined as organization*team too
Title: Message Title Aleksi Aalto commented on JENKINS-43078 Re: Admin users could be defined as organization*team too Thanks, how could I miss that! Would it still be useful to have it possible if someone wants to use the "GitHub Committer Authorization Strategy"? 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-34469) robotframework pipeline-plugin compatibility
Title: Message Title Ben EINAUDI commented on JENKINS-34469 Re: robotframework pipeline-plugin compatibility Hi, Thank you so much for this post, I have been wandering through the web before founding this. I implemented this way: step( [ $class : 'RobotPublisher', outputPath : outputDirectory, outputFileName : "*.xml", disableArchiveOutput : false, passThreshold : 100, unstableThreshold: 95.0, otherFiles : "*.png", ] ) With this I can if I go under the build see the results navigate between files have an history of the errors, thei age, and so on. Yet I don't have nor results of the last build on the page of the job nor the button Robot Results on the left menu. How can I achieve this? Thank you very much. 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-34469) robotframework pipeline-plugin compatibility
Title: Message Title
Ben EINAUDI updated an issue
Jenkins / JENKINS-34469
robotframework pipeline-plugin compatibility
Change By:
Ben EINAUDI
Comment:
Hi, Thank you so much for this post, I have been wandering through the web before founding this.I implemented this way: {quote}step( [ {color:#6a8759}$class {color}: {color:#6a8759}'RobotPublisher'{color}, {color:#6a8759}outputPath {color}: outputDirectory, {color:#6a8759}outputFileName {color}: {color:#6a8759}"*.xml"{color}, {color:#6a8759}disableArchiveOutput {color}: {color:#cc7832}false{color}, {color:#6a8759}passThreshold {color}: {color:#6897bb}100{color}, {color:#6a8759}unstableThreshold{color}: {color:#6897bb}95.0{color}, {color:#6a8759}otherFiles {color}: {color:#6a8759}"*.png"{color}, ]){quote} With this I can *if I go under the build* * see the results * navigate between files * have an history of the errors, thei age, and so on.Yet I don't have nor results of the last build on the page of the job nor the button _Robot Results_ on the left menu. How can I achieve this? Thank you very much.
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 unsubs
[JIRA] (JENKINS-34469) robotframework pipeline-plugin compatibility
Title: Message Title Ben EINAUDI reopened an issue Hi, Thank you so much for this post, I have been wandering through the web before founding this. I implemented this way: step( [ $class : 'RobotPublisher', outputPath : outputDirectory, outputFileName : "*.xml", disableArchiveOutput : false, passThreshold : 100, unstableThreshold: 95.0, otherFiles : "*.png", ] ) With this I can if I go under the build see the results navigate between files have an history of the errors, thei age, and so on. Yet I don't have nor results of the last build on the page of the job nor the button Robot Results on the left menu. How can I achieve this? Thank you very much. Jenkins / JENKINS-34469 robotframework pipeline-plugin compatibility Change By: Ben EINAUDI Resolution: Not A Defect Status: Closed Reopened Add Comment
[JIRA] (JENKINS-22874) Ability to configure thresholds for each Warnings parser used
Title: Message Title Ulli Hafner commented on JENKINS-22874 Re: Ability to configure thresholds for each Warnings parser used Nobody is working on this. It can be implemented in the warnings plugin alone or in analysis-core and the warnings plugin. In the latter case it would make sense to rather implement JENKINS-14185 und reuse these concepts. I already started an implementation some years ago: https://github.com/jenkinsci/analysis-core-plugin/tree/JENKINS-14185. However, I never finished it. Are you interested in providing an implementation? Then I can bring the branch up to date 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-41375) JobConfigHistory fails to revert
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41375 Re: JobConfigHistory fails to revert Hello, I can't also reproduce this issue with running a Selenium grid hub on the same windows machine. Do you use some special characters (any character except a-z,A-Z,0-9) in your job names? Best regards, Jochen 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-43087) Add possibility to pass unspecified job params in pipeline build step (or affect triggered build ENV)
Title: Message Title Jakub Josef created an issue Jenkins / JENKINS-43087 Add possibility to pass unspecified job params in pipeline build step (or affect triggered build ENV) Issue Type: Improvement Assignee: Unassigned Components: pipeline-build-step-plugin Created: 2017/Mar/24 12:36 PM Priority: Major Reporter: Jakub Josef It would by nice if you can pass extra params in build pipeline step, i want to pass params from one pipeline to another and these params are not defined in pipeline parameters. Our case: We triggering a gating job pipeline from Gerrit, so triggered job get's GERRIT_* parameters automagically. In this pipeline we want to trigger another pipeline which needs GERRIT_* params as well. But we cannot pass GERRIT_* parameters by code lower because those parameters are undefined in triggered pipeline. build(job: "testJob", parameters: [ [$class: 'StringParameterValue', name: 'GERRIT_REFSPEC', value: "2485/12"], ... Passing undefined variables produce no error. Another option is add possibility to affect triggered build ENV.
[JIRA] (JENKINS-41375) JobConfigHistory fails to revert
Title: Message Title Antoni Yanev commented on JENKINS-41375 Re: JobConfigHistory fails to revert Hello, We have some jobs with - . or_ but most of them are just alphanumeric. Best Regards, Antoni 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-43087) Add possibility to pass unspecified job params in pipeline build step (or affect triggered build ENV)
Title: Message Title Jakub Josef updated an issue Jenkins / JENKINS-43087 Add possibility to pass unspecified job params in pipeline build step (or affect triggered build ENV) Change By: Jakub Josef Environment: Jenkins 2.49all plugins latest 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-43062) SSH Host Key Verifiers are not configured for all SSH slaves
Title: Message Title Michael Clarke commented on JENKINS-43062 Re: SSH Host Key Verifiers are not configured for all SSH slaves There is no publicly available 'No verification' strategy available (it's used internally for anyone upgrading the plugin and therefore not having a strategy set), so anyone submitting the form is forced to submit a strategy, and may therefore just end up with the 'Known hosts' strategy as a default since that's first in the list. I did have a view that anyone modifying the slave configuration should be made to explicitly set an option, but it's not clear that's happening from the way the form is presented and validation currently runs. I'll look at improving 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-43062) SSH Host Key Verifiers are not configured for all SSH slaves
Title: Message Title Michael Clarke assigned an issue to Michael Clarke Jenkins / JENKINS-43062 SSH Host Key Verifiers are not configured for all SSH slaves Change By: Michael Clarke Assignee: Kohsuke Kawaguchi Michael Clarke 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-41375) JobConfigHistory fails to revert
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41375 Re: JobConfigHistory fails to revert Ok, that should work. Have you tried to use JobConfigHistory when the Selenium grid hub is not running? I just want to be sure, that it doesn't have anything to do with it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27906) Fail to read NUnit3 output xml
Title: Message Title Hugues Massot commented on JENKINS-27906 Re: Fail to read NUnit3 output xml Hi, I'm new to Jenkins, NUnit, C#,...but I just wanted to say that your hpi file worked fine for my configuration 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-40235) Initial run of parameterized pipeline always fails the first time
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40235 Re: Initial run of parameterized pipeline always fails the first time Code changed in jenkins User: Gabriel Le Breton Path: TUTORIAL.md http://jenkins-ci.org/commit/pipeline-plugin/bd8d95b303b9e20d530b247d478261e76585feaf Log: Build parameters not groovy variables anymore I had an issue when working with Build parameters, found the solution in JENKINS-40235 and added details here: http://stackoverflow.com/a/41276956/1092815 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-40766) Make M2 Release Plugin compatible with pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40766 Re: Make M2 Release Plugin compatible with pipeline Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/b293156039a223ee592298cbd762fed9291f68a5 Log: Merge pull request #426 from estarter/patch-1 JENKINS-40765 JENKINS-40766 Add release/m2release plugins to the list Compare: https://github.com/jenkinsci/pipeline-plugin/compare/be4c63608ad5...b293156039a2 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-40765) Make Release Plugin compatible with pipeline
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40765 Re: Make Release Plugin compatible with pipeline Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/b293156039a223ee592298cbd762fed9291f68a5 Log: Merge pull request #426 from estarter/patch-1 JENKINS-40765 JENKINS-40766 Add release/m2release plugins to the list Compare: https://github.com/jenkinsci/pipeline-plugin/compare/be4c63608ad5...b293156039a2 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-42959) Failed known_hosts verification for SSH agent
Title: Message Title Michael Clarke commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent Misa Travel I'm not sure what your point in your final paragraph is saying. Jenkins looks for a known_hosts file in $user_home/,ssh/known_hosts which is the default location for a known_hosts file for most SSH clients, regardless of whether they're running on Linux or Windows. I could update the Known Hosts strategy to take a path for the known_hosts file but I'm not clear if that's the issue 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-42959) Failed known_hosts verification for SSH agent
Title: Message Title Michael Clarke commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent For the issue other people have mentioned here: Trilead is no longer an actively maintained library, although I'll raise a Pull Requests against the Jenkins fork to allow it to handle ECDSA host keys. This should fix the issue where validation works on a command prompt but fails in Jenkins. I'd rather not add arguments to the SSH command to force a specific key format to be used, as some hosts may not have that format, and it then causes upgrade issues if we ever chose to move format and some user's machines don't support newer formats. 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-41267) scoring-load-balancer support for pipeline jobs
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41267 scoring-load-balancer support for pipeline jobs Change By: Jesse Glick Component/s: pipeline Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41375) JobConfigHistory fails to revert
Title: Message Title Antoni Yanev commented on JENKINS-41375 Re: JobConfigHistory fails to revert Yes, we have tried doing it without the Selenium grid hub running. 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-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40624 nodejs installer not compatible with declarative pipeline definition Change By: Jesse Glick Component/s: pipeline-model-definition-plugin Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41402) Corner case in job deletion without history?
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41402 Re: Corner case in job deletion without history? You are right. However, if a job is not disabled and you delete a job, the Jenkins core internally first disables the job and than deletes it. So in this case you get two history entries, the first one with a copy of the job config (job was enabled). 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-40624) nodejs installer not compatible with declarative pipeline definition
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40624 Re: nodejs installer not compatible with declarative pipeline definition Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/ddf73bebcafd7bca9293f28b8fa84a0d7bda478b Log: Merge pull request #430 from nfalco79/master JENKINS-40624 Update COMPATIBILITY.md to update NodeJS plugin Compare: https://github.com/jenkinsci/pipeline-plugin/compare/b293156039a2...ddf73bebcafd 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-41726) form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response
Title: Message Title Janario Oliveira commented on JENKINS-41726 Re: form auth in http-request plugin getting HTTP/1.1 408 Request Timeout response The latest version requeries jdk1.7 and Jenkins 1.609.3 Have you tried on this versions? You could try http://requestb.in/ (it is a service that show details to every request sent to it) to see what is been sent from the job execution. With that detail also try with 'curl'. We have a few documentation here http://wiki.jenkins-ci.org/display/JENKINS/HTTP+Request+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-41375) JobConfigHistory fails to revert
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41375 Re: JobConfigHistory fails to revert Three more things: JobConfigHistory does not only persist changes in job configurations, but also changes in node configurations. Could you try JobConfigHistory on a node? Did you configure JobConfigHistory to use an other directory than the default one or did you even configure JobConfigHistory? (Global jenkins configuration page) I am also wondering about the stack trace you provided. There's the line at hudson.plugins.jobConfigHistory.JobConfigHistoryProjectAction.doRestore(JobConfigHistoryProjectAction.java:219) , however in JobConfigHistory 2.15 there's no method or anything in line 219, as you can see here. Maybe there went something wrong during the upgrade of JobConfigHistory. Can you rollback to the earlier version you installed, try it there and upgrade to the newest version again? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because yo
[JIRA] (JENKINS-41375) JobConfigHistory fails to revert
Title: Message Title Antoni Yanev commented on JENKINS-41375 Re: JobConfigHistory fails to revert I cannot test it on the node at the moment. The JobConfigHistory settings are the default ones. We had a previous version of JobConfigHistory (2.4) and got the same error, that's why we updated to 2.15. 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-43088) Missing Link "Checkmarx results last scan" in homepage of job maven when the Checmarx config is included in Conditional Step
Title: Message Title ERIC WISNIEWSKI created an issue Jenkins / JENKINS-43088 Missing Link "Checkmarx results last scan" in homepage of job maven when the Checmarx config is included in Conditional Step Issue Type: Bug Assignee: Sergey Kadaner Attachments: CondionalStepExecuteScanCheckmarx.png Components: checkmarx-plugin, conditional-buildstep-plugin Created: 2017/Mar/24 1:48 PM Environment: Jenkins 2.9 Checkmarx Plugin 8.2.1 Conditional BuildStep Plugin 1.3.3 Priority: Minor Reporter: ERIC WISNIEWSKI When we configure in Job maven Scan Checkmarx in Conditional Step (Mutliple), the link "Checkmarx Results last Scan " & Details Vulnerabilities aren't visibles in homepage of the job . But if the config checkmarx isn't in the conditional step then the link "Checkmarx Results last Scan " & Details Vulnerabilities are visibles
[JIRA] (JENKINS-41907) Evaluate to obtain IdP Metadata from URL
Title: Message Title Coltrey Mather commented on JENKINS-41907 Re: Evaluate to obtain IdP Metadata from URL +1 - Azure AD supports this and their metadata changes occasionally, requiring a manual update to the metadata xml (and an outage for users until that update happens). 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-43088) Missing Link "Checkmarx results last scan" in homepage of job maven when the Checmarx config is included in Conditional Step
Title: Message Title ERIC WISNIEWSKI updated an issue Jenkins / JENKINS-43088 Missing Link "Checkmarx results last scan" in homepage of job maven when the Checmarx config is included in Conditional Step Change By: ERIC WISNIEWSKI Component/s: conditional-buildstep-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-37475) Add a configurable switch on job that causes CPS to silently not continue on non-serializable code
Title: Message Title Jesse Glick resolved as Duplicate This is two unrelated RFEs. Please file separate issues in separate tickets. The first is a duplicate. The second is unimplementable. Jenkins / JENKINS-37475 Add a configurable switch on job that causes CPS to silently not continue on non-serializable code Change By: Jesse Glick Status: Open Resolved 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 e
[JIRA] (JENKINS-41375) JobConfigHistory fails to revert
Title: Message Title Jochen A. Fürbacher commented on JENKINS-41375 Re: JobConfigHistory fails to revert You don't need to test JCH on an existing node. You can create a new dumb slave node (e.g. "Launch slave agents via Java Web Start") that you don't start. Just create and reconfigure such a slave 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-43089) Emulate clean checkout with nested externals breaks sandbox
Title: Message Title Mikel Ortega created an issue Jenkins / JENKINS-43089 Emulate clean checkout with nested externals breaks sandbox Issue Type: Bug Assignee: Unassigned Attachments: externals.png, modifications.png, output.png, svnfolder.png Components: subversion-plugin Created: 2017/Mar/24 2:01 PM Environment: Windows 7 Pro 32 bits. Jenkins 2.51, installed with installer, running as a service. Subversion Workspace Version 1.8 Subversion Plug-in 2.7.2 Chrome 57.0 Labels: svn subversion externals nested EmulateCleanCheckout subversion-plugin Priority: Major Reporter: Mikel Ortega We have some nexted externals. These are configured on the first folder, for example: Path: Core URL: /MainRepository/trunk/OneProject/Core Path: Core/Plugins/Scripts URL: /MainRepository/OtherProject/Scripts So we have an external Core folder and inside, another external Scripts folder. When we configure the check-out strategy as "Emulate clean checkout" the workspace sandbox gets broken. I think Jenkins deletes all the contents in the nested external folder, also the contents inside .svn hidden folder so the repository does not work anymore. The only way to make it work again is doing a new checkout. Please, contact me if you need further details. Thank you.
[JIRA] (JENKINS-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title Kai Howelmeyer commented on JENKINS-28822 Re: Can't distinguish between durable task abort and failure in workflow plugin I am also confused by this handling: In https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L319 we send AbortException. If I surround a "sh" step with try/catch, I cannot tell if Abort was clicked or if the shell script failed. Is there an easy way to distinguish 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-42969) Computer.addAction will throw UnsupportedOperationException
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42969 Re: Computer.addAction will throw UnsupportedOperationException Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/Computer.java core/src/main/java/hudson/model/labels/LabelAtom.java test/src/test/java/hudson/model/ComputerTest.java http://jenkins-ci.org/commit/jenkins/838357700d3173380170ecb28f131a554da0af63 Log: [FIXED JENKINS-42969] UnsupportedOperationException from Computer.addAction. 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-35185) Trigger github multi-branch build via SQS
Title: Message Title
Idikoro Eradiri commented on JENKINS-35185
Re: Trigger github multi-branch build via SQS
the flow looks like this: github -> SNS -> SQS -> jenkins and this is the Jenkinsfile I used in my repo for the multibranch pipeline
pipeline {
agent any
triggers {
githubPush()
}
stages {
stage(do something') {
steps {
echo 'hello'
}
}
}
}
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-42831) Enable StartTls is always TRUE in the UI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-42831 Re: Enable StartTls is always TRUE in the UI Code changed in jenkins User: Emilio Escobar Path: src/main/resources/hudson/plugins/active_directory/ActiveDirectorySecurityRealm/configAdvanced.jelly http://jenkins-ci.org/commit/active-directory-plugin/acfe14518fdb38a3eea2a00f0a05de60bc31ea18 Log: [FIXED JENKINS-42831] should be default instead of checked 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-43090) Set BUILD_USER_ID for anonymous user
Title: Message Title Marcin Zajączkowski created an issue Jenkins / JENKINS-43090 Set BUILD_USER_ID for anonymous user Issue Type: Improvement Assignee: Marcin Zajączkowski Components: build-user-vars-plugin Created: 2017/Mar/24 2:41 PM Environment: 1.5 Priority: Minor Reporter: Marcin Zajączkowski For anonymous user BUILD_USER is set, but BUILD_USER_ID is not. It's problematic in places which use BUILD_USER_ID. ID should be set to "anonymous" which is a reserved username in Jenkins. Add Comment
[JIRA] (JENKINS-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title Félix Belzunce Arcos started work on JENKINS-43091 Change By: Félix Belzunce Arcos 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-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-43091 Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2017/Mar/24 2:42 PM Priority: Minor Reporter: Félix Belzunce Arcos After restart, we are seeing: INFO: Started termination Mar 24, 2017 12:47:07 PM jenkins.model.Jenkins$21 onTaskFailed SEVERE: Failed ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors com.google.inject.ConfigurationException: Guice configuration errors: 1) Could not find a suitable constructor in hudson.plugins.active_directory.ActiveDirectorySecurityRealm. Classes must have either one (and only one) constructor annotated with @Inject or a zero-argument constructor that is not private. at hudson.plugins.active_directory.ActiveDirectorySecurityRealm.class(ActiveDirectorySecurityRealm.java:108) while locating hudson.plugins.active_directory.ActiveDirectorySecurityRealm 1 error at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1042) at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1001) at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1051) at jenkins.ProxyInjector.getInstance(ProxyInjector.java:98) at hudson.init.TaskMethodFinder.lookUp(TaskMethodFinder.java:124) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at jenkins.model.Jenkins$20.execute(Jenkins.java:3240) at org.jvnet.hudson.reactor.Reacto
[JIRA] (JENKINS-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-43091 Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Change By: Félix Belzunce Arcos URL: https://github.com/jenkinsci/active-directory-plugin/pull/72 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-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43091 Re: Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Code changed in jenkins User: Félix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/a591b57c1a82f70128a685f724672b6411e4000a Log: JENKINS-43091 Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors 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-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43091 Re: Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Code changed in jenkins User: Felix Belzunce Arcos Path: src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java http://jenkins-ci.org/commit/active-directory-plugin/5e653988a136a0f2d73105390a78ec617f89dc9d Log: Merge pull request #72 from fbelzunc/JENKINS-43091 [FIXED JENKINS-43091] Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Compare: https://github.com/jenkinsci/active-directory-plugin/compare/847ace3121c2...5e653988a136 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-37203) "Override Authentication Token?" do not work
Title: Message Title Peter Tierno commented on JENKINS-37203 Re: "Override Authentication Token?" do not work Vaclav Adamec yes, i do. time has been an issue though. pr's are welcome. ideally i would like to create a legitimate pipeline step for 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-37203) "Override Authentication Token?" do not work
Title: Message Title Peter Tierno commented on JENKINS-37203 Re: "Override Authentication Token?" do not work Alexandru Calistru I dont have a deadline. time for this has been limited. pr's are welcome. 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-39207) "RSS for all" shows only a few builds
Title: Message Title Peter Goins edited a comment on JENKINS-39207 Re: "RSS for all" shows only a few builds I have the same problem. I first noticed something Removing my comment - my issue was wrong because the weather icon with missing metrics settings for one of our folders was Sunny (some builds have recently broken) and hovering over it didn't provide any summary on the ~15 projects within the a folder. When I looked at the "RSS for all", it only showed 21 builds across 9 of the projects.I renamed one of the earlier projects shortly after creating it, but there was already some build history. Perhaps that project rename corrupted something? 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-43092) Jenkins stages executions hangs when creating stages dynamically
Title: Message Title
Fahd Arshad created an issue
Jenkins / JENKINS-43092
Jenkins stages executions hangs when creating stages dynamically
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline, pipeline-stage-view-plugin
Created:
2017/Mar/24 3:02 PM
Environment:
2.32.3
Labels:
pipeline pipeline-stage-view shell shell-command steps
Priority:
Minor
Reporter:
Fahd Arshad
i have created a groovy closure inside a jenkinsfile like:
job {
stage1 = sh "something"
stage2 = sh "something2"
}
Using Jenkins global libraries i read the closure and create different stages by dynamically counting the number of times 'stage' word was used For each stage i use the "sh" command to run a script. The problem i am facing is, once a stage is created and the shell script runs inside the stage, even after the shell script exits jenkins does not move on to creating the next stage instead it hangs on the same stage. job.groovy
#!groovy def call(body) {
def args = [:]
body.resolveStrategy = Closure.DELEGATE_FIRST
body.delegate = args
body()
// Loading jenkins jenkinsLibrary
def lib = n
[JIRA] (JENKINS-43091) Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-43091 Guice failing on terminating ActiveDirectorySecurityRealm.shutDownthreadPoolExecutors Change By: SCM/JIRA link daemon 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-36765) Pipeline: Send notification "Back to normal" state
Title: Message Title Martin Sander edited a comment on JENKINS-36765 Re: Pipeline: Send notification "Back to normal" state [~jviki]:The attached code snippet is for the [Pipeline Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin], see e.g. https://jenkins.io/solutions/pipeline/.Your snippet seems to be using the "declarative pipeline" from the [Pipeline Model Definition Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Model+Definition+Plugin], which is not the same. The latter is supposed to be easier to use, but less powerful. Maybe you are looking for https://jenkins.io/blog/2017/02/15/declarative-notifications/. 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-36765) Pipeline: Send notification "Back to normal" state
Title: Message Title Martin Sander commented on JENKINS-36765 Re: Pipeline: Send notification "Back to normal" state Jan Viktorin: The attached code snippet is for the Pipeline Plugin, see e.g. https://jenkins.io/solutions/pipeline/. Your snippet seems to be using the "declarative pipeline" from the Pipeline Model Definition Plugin, which is not the same. The latter is supposed to be easier to use, but less powerful. 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-29253) Please set BUILD_USER to 'timer' for scheduled jobs
Title: Message Title Marcin Zajączkowski assigned an issue to Marcin Zajączkowski Jenkins / JENKINS-29253 Please set BUILD_USER to 'timer' for scheduled jobs Change By: Marcin Zajączkowski Assignee: Marcin Zajączkowski 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-29253) Please set BUILD_USER to 'timer' for scheduled jobs
Title: Message Title Marcin Zajączkowski commented on JENKINS-29253 Re: Please set BUILD_USER to 'timer' for scheduled jobs Fix provided in https://github.com/jenkinsci/build-user-vars-plugin/pull/13 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-43093) Replace NPE stacktrace with message when Gerrit change number and patchset numer are not set
Title: Message Title Tatiana Didik created an issue Jenkins / JENKINS-43093 Replace NPE stacktrace with message when Gerrit change number and patchset numer are not set Issue Type: Improvement Assignee: Tatiana Didik Components: sonar-gerrit-plugin Created: 2017/Mar/24 3:42 PM Priority: Minor Reporter: Tatiana Didik If Gerrit change number and patchset numer are not set build will be failed with NPE exception. (Example: if build is not triggered by Gerrit but started manually by button "Build now") Replace it with corresponding messages java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:542) at java.lang.Integer.parseInt(Integer.java:615) at org.jenkinsci.plugins.sonargerrit.SonarToGerritPublisher.perform(SonarToGerritPublisher.java:237) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1037) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) at hudson.model.Run.execute(Run.java:1763) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)
[JIRA] (JENKINS-43090) Set BUILD_USER_ID for anonymous user
Title: Message Title Marcin Zajączkowski commented on JENKINS-43090 Re: Set BUILD_USER_ID for anonymous user Should be fixed by https://github.com/jenkinsci/build-user-vars-plugin/pull/13 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-25199) Build user variables not supported for Auto triggered jobs
Title: Message Title Marcin Zajączkowski commented on JENKINS-25199 Re: Build user variables not supported for Auto triggered jobs Should be fixed by https://github.com/jenkinsci/build-user-vars-plugin/pull/13 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-43092) Jenkins stages executions hangs when creating stages dynamically
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-43092 Jenkins stages executions hangs when creating stages dynamically Change By: Sam Van Oort Component/s: pipeline-stage-view-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-43092) Jenkins stages executions hangs when creating stages dynamically
Title: Message Title Sam Van Oort commented on JENKINS-43092 Re: Jenkins stages executions hangs when creating stages dynamically Fahd Arshad It is not supported to run pipeline steps inside NonCPS blocks – this is in the pipeline docs, but the explanation here (best practices, bullet point 3c) is probably the most concise explanation. If you attempt to run steps inside a NonCPS block it is not guaranteed or even expected to work correctly, and hangs like this are merely one possibility. Remove the all the enclosing @NonCPS functions when dynamically defining stages and it should work (you can call out to NonCPS functions within that). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43092) Jenkins stages executions hangs when creating stages dynamically
Title: Message Title Sam Van Oort closed an issue as Not A Defect Jenkins / JENKINS-43092 Jenkins stages executions hangs when creating stages dynamically Change By: Sam Van Oort Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23251) BUILD_USER_ID is not set when the build is fired using the API
Title: Message Title Marcin Zajączkowski commented on JENKINS-23251 Re: BUILD_USER_ID is not set when the build is fired using the API Should be fixed by https://github.com/jenkinsci/build-user-vars-plugin/pull/13 . However, a build cause doesn't know about triggering user when a token is used and only "remoteTrigger" dummy username is set. 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-43066) With pipeline, tools does not setup properly the environment
Title: Message Title Sébastien Bro commented on JENKINS-43066 Re: With pipeline, tools does not setup properly the environment I'm facing the same issue with the standard Jenkins jobs. NodeJS is not added to the path while checking "Provide Node & npm bin/ folder to PATH" 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-43078) Admin users could be defined as organization*team too
Title: Message Title Sam Gleske commented on JENKINS-43078 Re: Admin users could be defined as organization*team too I think the GitHub Committer Authorization Strategy needs a complete overhaul. The way I'd like to see it done is akin to the matrix based authorization strategy but allowing users to define what Jenkins permissions a user gets based on their access to a repository. I don't really have off-hours time to commit at the moment to perform such an overhaul. 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-43078) Admin users could be defined as organization*team too
Title: Message Title Sam Gleske updated an issue Jenkins / JENKINS-43078 Admin users could be defined as organization*team too Change By: Sam Gleske Environment: Now admin users can be defined only with github-usernames. It would be very useful to be able to define Jenkins admins by Github teams.Especially, when administering a larger number of Jenkins, controlling the admin groups through one Github group would be very useful. 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-43078) Admin users could be defined as organization*team too
Title: Message Title Sam Gleske updated an issue Jenkins / JENKINS-43078 Admin users could be defined as organization*team too Change By: Sam Gleske Now admin users can be defined only with github-usernames. It would be very useful to be able to define Jenkins admins by Github teams.Especially, when administering a larger number of Jenkins, controlling the admin groups through one Github group would be very useful. edit: migrated description from environment by [~sag47] 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-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title dan turner commented on JENKINS-38005 Re: Using archiveArtifacts with a non-matching pattern silently fails the build bump, just spent 1/2 a day looking for 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-41336) Cron based jobs are triggered at random times and also at the time Stash is unavailable
Title: Message Title Larry Brigman commented on JENKINS-41336 Re: Cron based jobs are triggered at random times and also at the time Stash is unavailable I'm seeing jobs queue when I get this error: Mar 23, 2017 4:43:00 PM stashpullrequestbuilder.stashpullrequestbuilder.StashRepository getTargetPullRequests INFO: Fetch PullRequests (ansible-checks). java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Read timed out at java.util.concurrent.FutureTask.report(FutureTask.java:122) at java.util.concurrent.FutureTask.get(FutureTask.java:202) at stashpullrequestbuilder.stashpullrequestbuilder.stash.StashApiClient.getRequest(StashApiClient.java:254) at stashpullrequestbuilder.stashpullrequestbuilder.stash.StashApiClient.getPullRequests(StashApiClient.java:86) Using Jenkins 2.44 on Ubuntu 14.04 LTS OpenJDK 64bit Java 1.7.0_79 Stash Pull Request Builder 1.7 Against Stash/Bitbucket v4.4.1 The timeout is due to an issue on the bitbucket end but it shouldn't be causing a build to be queued. 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-43094) Support Fingerprinting of consumed dependencies
Title: Message Title Chris Russell created an issue Jenkins / JENKINS-43094 Support Fingerprinting of consumed dependencies Issue Type: Improvement Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2017/Mar/24 5:03 PM Priority: Minor Reporter: Chris Russell The standard Maven Project in Jenkins provides the ability to fingerprint consumed artifacts. If the consumed artifact was created by a Jenkins build (and fingerprinted), Jenkins will link you back to the point of origin. Use cases: When an upstream project causes an exception, you can easily find the build of the dependency to get information which will help narrow in on the root cause like the upstream changelog. When releasing (or preparing to release) the downstream build, you can see exactly what upstream builds are implicitly being released with it. Add Comment
[JIRA] (JENKINS-30782) Failed to read environment variable table error
Title: Message Title Oleg Nenashev commented on JENKINS-30782 Re: Failed to read environment variable table error I am currently working on the fix. I wish I could just take the implementation from processhacker2 "https://github.com/processhacker2/processhacker2/blob/69d9dcd2c79d52ce987cc8f0150f639426eb67f9/phlib/native.c#L867-L990", but it cannot be done since the code there is GNU GPL. Will consider alternatives 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-42772) New "WorkflowScript: 14: "ansiColor" should have 1 arguments but has 0 arguments instead" exception thrown in version 1.1.1
Title: Message Title Andrew Bayer reopened an issue Re-opening - I think I'm going to set it to not fail when it sees no parameters passed to a single-argument @DataBoundConstructor. Jenkins / JENKINS-42772 New "WorkflowScript: 14: "ansiColor" should have 1 arguments but has 0 arguments instead" exception thrown in version 1.1.1 Change By: Andrew Bayer Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-43094) Support Fingerprinting of consumed dependencies
Title: Message Title Chris Russell assigned an issue to Chris Russell Jenkins / JENKINS-43094 Support Fingerprinting of consumed dependencies Change By: Chris Russell Assignee: Alvaro Lobato Chris Russell 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-43094) Support Fingerprinting of consumed dependencies
Title: Message Title Chris Russell assigned an issue to Alvaro Lobato Jenkins / JENKINS-43094 Support Fingerprinting of consumed dependencies Change By: Chris Russell Assignee: Chris Russell Alvaro Lobato 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.
