[JIRA] (JENKINS-37092) Fix for NPE in CCUCM Plugin (case 14958)
Title: Message Title Mads Nielsen updated an issue Jenkins / JENKINS-37092 Fix for NPE in CCUCM Plugin (case 14958) Change By: Mads Nielsen Summary: Fix for NPE in CCUCM Plugin (case 14958) 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-37108) Cannot trigger a job on the same node with "Blocking" checked
Title: Message Title vandana gopal closed an issue as Not A Defect Jenkins / JENKINS-37108 Cannot trigger a job on the same node with "Blocking" checked Change By: vandana gopal Status: Open Closed Resolution: Not A Defect 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-37109) Ability to use Credentials for Basic/Digest Authentications
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-37109 Re: Ability to use Credentials for Basic/Digest Authentications Sorry just noticed there was already a ticket for this: https://issues.jenkins-ci.org/browse/JENKINS-36760 Note: The link from the wiki to open issues is broken because the plugin id is `http_request` 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-37110) Last stage is always marked as failed if any other stage failed
Title: Message Title
Claus Näveke created an issue
Jenkins / JENKINS-37110
Last stage is always marked as failed if any other stage failed
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin
Created:
2016/Aug/02 6:20 AM
Priority:
Major
Reporter:
Claus Näveke
We are using a pipeline for which has steps like this: stage 'Test USB Update' try { build job: 'UpdateTest-USB' } catch(exception) { currentBuild.result = 'FAILURE' } (Basic idea: Run the sub job. If it fails, fail this step, but continue the pipeline) Unfortunately the last step is always shown as failed, if one of the other steps failed. When looking at the "Pipeline steps" page for the build, everything is correct and the last step is marked as "Success", so I'm pretty sure it's a display problem.
Add Comment
[JIRA] (JENKINS-37109) Ability to use Credentials for Basic/Digest Authentications
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-37109 Ability to use Credentials for Basic/Digest Authentications Issue Type: Improvement Assignee: Janario Oliveira Attachments: http-request-auth.png Components: http-request-plugin Created: 2016/Aug/02 6:17 AM Environment: jenkins:1.651.3 http-request-plugin:1.8.11 Priority: Major Reporter: Allan BURDAJEWICZ Instead of specifying Username/Password in the global configuration for Basic/Digest Authentication, it would be a great improvement to be able to define Credentials in Jenkins and select them in the configuration of HTTP Request. Add Comment
[JIRA] (JENKINS-37108) Cannot trigger a job on the same node with "Blocking" checked
Title: Message Title vandana gopal created an issue Jenkins / JENKINS-37108 Cannot trigger a job on the same node with "Blocking" checked Issue Type: Bug Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2016/Aug/02 5:54 AM Priority: Major Reporter: vandana gopal I have two jobs - one to run a batch script 1 and another job to run batch script 2. I want job 1 to trigger job 2 and both to run on the same node. I want job1 to block until job2 completes. However when I do this, both are stuck in an infinite loop - job1 says it is waiting for job2, job2 says it is waiting for next executor to run on the node. If job1 is just waiting for job2 to complete, why cannot job2 run on the same node? Add Comment
[JIRA] (JENKINS-37107) Jenkins will now refuse to load plugins with unsatisfied dependencies catastrophically breaks Scriptler and other plugins
Title: Message Title apgray created an issue Jenkins / JENKINS-37107 Jenkins will now refuse to load plugins with unsatisfied dependencies catastrophically breaks Scriptler and other plugins Issue Type: Bug Assignee: Dominik Bartholdi Components: core, scriptler-plugin Created: 2016/Aug/02 3:58 AM Environment: Windows 10, Jenkins 2.16, scriptler latest available version. Priority: Critical Reporter: apgray Upgrading to Jenkins 2.16 was horrendous. It broke two of my plugins, scriptler and something relying on version 2.6 of Subversion plugin (stated fix version is not available anywhere). DON"T upgrade to v2.16 unless you want to spend hours restoring your job configurations after downgrading to v2.15. Add Comment
[JIRA] (JENKINS-35544) coder review
Title: Message Title Feng Tan commented on JENKINS-35544 Re: coder review Michael Porter: thanks for providing the output of the drush command ! It looks like the problem is caused by Drupal modules that do not have any version in their .info file. I have commited a fix – see message above. If some of you folks could test the fix that would be awesome ! 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-35544) coder review
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35544 Re: coder review Code changed in jenkins User: Fengtan 冯坦 Path: src/main/java/org/jenkinsci/plugins/drupal/beans/DrushInvocation.java http://jenkins-ci.org/commit/drupal-developer-plugin/7e538e8b494a79ff2c6446ab2974055cc645123e Log: JENKINS-35544 Fix NPE when module has no version. 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-26653) Build Pipeline Dashboard fails with ServletException: No page found 'noJob.jelly'
Title: Message Title Denys Digtiar reopened an issue Jenkins / JENKINS-26653 Build Pipeline Dashboard fails with ServletException: No page found 'noJob.jelly' Change By: Denys Digtiar Resolution: Incomplete Status: Resolved 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-26653) Build Pipeline Dashboard fails with ServletException: No page found 'noJob.jelly'
Title: Message Title Denys Digtiar commented on JENKINS-26653 Re: Build Pipeline Dashboard fails with ServletException: No page found 'noJob.jelly' "Build Pipeline Dashboard View" Portlet appears to be causing the issue when there are no Runs to display. Environment: Running as Executable WAR Jenkins Version: 1.642.4 Plugin Version: 1.5.3.1 java version "1.8.0_92" Java(TM) SE Runtime Environment (build 1.8.0_92-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode) Steps to reproduce 1. Create a new Freestyle project 2. Configure a new Dashboard as follows 2.1 Select at least one Job in the Job Filter 2.2 Add "Build Pipeline Dashboard View" in any of the Dashboard Portlets sections 2.3 Select the Job from Step 1 in the Select Initial Job dropdown 3. Open new Dashboard Expected behaviour: The empty pipeline is displayed with appropriate message (e.g. "This view has no jobs associated with it.") Actual behaviour: The error page is rendered inside the portlet. See the stacktrace in the description. 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-36574) Add option to choose static notification context
Title: Message Title Christian Höltje commented on JENKINS-36574 Re: Add option to choose static notification context I barely know enough Java to do what I did. Ideally I would want to be able to replace the jenkins with something identifying what Jenkins. e.g. automan But that'd require understanding Jelly, 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-36574) Add option to choose static notification context
Title: Message Title
Julien Maitrehenry edited a comment on JENKINS-36574
Re: Add option to choose static notification context
I really like this solution, but is it possible, in an another version to be able to configure {{continuous-integration /jenkins }}? It's a nice feature when you migrate from one jenkins to another and don't want to mix the status check on Github.
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-36574) Add option to choose static notification context
Title: Message Title Julien Maitrehenry commented on JENKINS-36574 Re: Add option to choose static notification context I really like this solution, but is it possible, in an another version to be able to configure continuous-integration? It's a nice feature when you migrate from one jenkins to another and don't want to mix the status check on Github. 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-21670) Option to anonymize customer labels
Title: Message Title Minudika Malshan edited a comment on JENKINS-21670 Re: Option to anonymize customer labels [~aheritier] What did you mean by "views"? Jenkins.getInstance().getViewActions() ?Also could you please tell me is there a way to get the information of users/accounts through API? [~jglick] Is this [https://github.com/kohsuke/wordnet-random-name] random word generator available as a maven dependency? Or do we have to add that jar or classes to Support core plug-in project manually? Thanks a lot! 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-37047) Unable to copy job when running as 'SYSTEM'
Title: Message Title ikedam commented on JENKINS-37047 Re: Unable to copy job when running as 'SYSTEM' 1 + "Run as User who Triggered Build" and 2 are designated solutions for now. Or you may downgrade jobcopy-builder to 1.3.0 for 3. I want to know more about why you don't like 2 as I believe it's an generic issue of the build authorization feature of Jenkins. Is your problem resolved if you can create a "static" user outside Active Directory? 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-37018) Blue Ocean dashboard page never finishes loading
Title: Message Title Vivek Pandey commented on JENKINS-37018 Re: Blue Ocean dashboard page never finishes loading Hi Dana Goyette, http://localhost:8080/jenkins/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject&start=0&limit=100 should give you 100 results. If you want to include less you can, basically I want to look at actions that are getting serialized in there so send them across after scrubbing. thanks. 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-21670) Option to anonymize customer labels
Title: Message Title Minudika Malshan edited a comment on JENKINS-21670 Re: Option to anonymize customer labels [~aheritier] What did you mean by " views " ? Jenkins.getInstance().getViewActions() ?Also could you please tell me is there a way to get the information of users/accounts through API?Thanks a lot! 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-21670) Option to anonymize customer labels
Title: Message Title Minudika Malshan commented on JENKINS-21670 Re: Option to anonymize customer labels Arnaud Héritier What did you mean by views? Jenkins.getInstance().getViewActions() ? Also could you please tell me is there a way to get the information of users/accounts through API? Thanks a lot! 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-37106) Empty state on dashboard for login
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37106 Empty state on dashboard for login Issue Type: Task Assignee: James Dumay Components: blueocean-plugin Created: 2016/Aug/01 11:46 PM Priority: Minor Reporter: 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" gr
[JIRA] (JENKINS-36229) API for UI to honour permissions
Title: Message Title James Dumay edited a comment on JENKINS-36229 Re: API for UI to honour permissions Can the user:* Start runs* Stop runs* Can create items* Is an administratorDon't know if handled elsewhere but can we tell if auth is on or off? Logged In vs Logged Out vs Anonymous (no auth) 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-36229) API for UI to honour permissions
Title: Message Title James Dumay commented on JENKINS-36229 Re: API for UI to honour permissions Can the user: Start runs Stop runs Can create items Is an administrator 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-37105) Ensure that matrix jobs experience is not broken
Title: Message Title James Dumay resolved as Won't Fix Jenkins / JENKINS-37105 Ensure that matrix jobs experience is not broken 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37104) Matrix project support
Title: Message Title James Dumay updated JENKINS-37104 Jenkins / JENKINS-37104 Matrix project support Change By: James Dumay 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-37104) Matrix project support
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37104 Matrix project support Change By: James Dumay Sprint: 1.0-pre-beta-1 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-37104) Matrix project support
Title: Message Title James Dumay updated JENKINS-37104 Jenkins / JENKINS-37104 Matrix project support Change By: James Dumay Status: Resolved 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-37104) Matrix project support
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-37104 Matrix project support Change By: James Dumay Status: In Progress 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-37104) Matrix project support
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37104 Matrix project support Change By: James Dumay Priority: Major Minor 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-37105) Ensure that matrix jobs experience is not broken
Title: Message Title James Dumay created an issue Jenkins / JENKINS-37105 Ensure that matrix jobs experience is not broken Issue Type: Task Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Aug/01 11:24 PM Priority: Trivial Reporter: James Dumay In Scope Ensure that you can open up a matrix dependency and it not 404s Add Comment
[JIRA] (JENKINS-36937) Detect parmetrised jobs and redirect to classic
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36937 Detect parmetrised jobs and redirect to classic Change By: James Dumay Sprint: 1.0-beta-1 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-37018) Blue Ocean dashboard page never finishes loading
Title: Message Title Dana Goyette commented on JENKINS-37018 Re: Blue Ocean dashboard page never finishes loading If you can tell me a way to get the full response, I can run it through 'sed' to replace any sensitive stuff with placeholder values, such as "product1-branch1". (When I tried using curl, the output was truncated.) 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-35794) Developer wants to re-run a failing or unstable result from the activity tab
Title: Message Title James Dumay assigned an issue to Cliff Meyers Jenkins / JENKINS-35794 Developer wants to re-run a failing or unstable result from the activity tab Change By: James Dumay Assignee: Ivan Meredith Cliff Meyers 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-36424) Run modal to also accommodate queued items (and not just runs)
Title: Message Title James Dumay started work on JENKINS-36424 Change By: James Dumay Status: Reopened 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-37104) Matrix project support
Title: Message Title Vivek Pandey started work on JENKINS-37104 Change By: Vivek Pandey 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-37018) Blue Ocean dashboard page never finishes loading
Title: Message Title Vivek Pandey commented on JENKINS-37018 Re: Blue Ocean dashboard page never finishes loading Dana Goyette Based on configuration provided, I expected about 120 (3*10*2*2) pipelines/jobs and each inlining its own run and its actions. It is worth while to investigate which is the culprit inning these 1000 of actions per build. Would it be possible to provide output response in full? 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-20905) jenkins-cli authentication error message is out of date
Title: Message Title Marius Karnauskas commented on JENKINS-20905 Re: jenkins-cli authentication error message is out of date Hi Noah Kantrowitz, can you provide information how to reproduce this error? 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-35855) Review all our icon whether they come from react-material-icons if so use the direct dep
Title: Message Title James Dumay closed an issue as Won't Fix Jenkins / JENKINS-35855 Review all our icon whether they come from react-material-icons if so use the direct dep Change By: James Dumay Status: In Progress Closed 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37047) Unable to copy job when running as 'SYSTEM'
Title: Message Title Brian Krische commented on JENKINS-37047 Re: Unable to copy job when running as 'SYSTEM' I use the Active Directory plugin for employees to authenticate with Jenkins. As far as I'm aware, it's not possible to have some kind of "static" Jenkins account while also using LDAP/AD for authentication. All users get created in Jenkins automatically after successful AD authentication and any login credentials given to Jenkins are tried against the AD server. Which, I believe, leaves me with 3 options: 1. Give all users create/configure job permissions, which I think we both would agree is not desirable. 2. Run the copy job as some arbitrary Active Directory user such as myself, which I'm not a big fan of honestly. 3. Run the copy job as SYSTEM, which in my mind acts like a "static" user with the permissions to create/configure jobs. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Alastair D'Silva commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Michael Neale As currently implemented, the same encoded name is used by the Multibranch Project for all of the directories (top level job, slave workspaces) and the branch name (eg. GCC_BRANCH above). 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-37010) Modules licenses for JS libs are not included in standard HPI
Title: Message Title Keith Zantow started work on JENKINS-37010 Change By: Keith Zantow 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-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title Keith Zantow started work on JENKINS-35776 Change By: Keith Zantow 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-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title Keith Zantow stopped work on JENKINS-35776 Change By: Keith Zantow 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-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-35776 Bundle all licenses in the license directory and display them on /legal Change By: Keith Zantow Assignee: Josh McDonald Keith Zantow 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-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title Keith Zantow started work on JENKINS-35776 Change By: Keith Zantow 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-37101) Race condition in concurrently executed tests running short Pipeline jobs
Title: Message Title Andrew Bayer commented on JENKINS-37101 Re: Race condition in concurrently executed tests running short Pipeline jobs Note that this was all with jobs with the same name, so there may be correlation there. So far, when switching to use story.j.createProject(WorkflowJob.class) to get a random name per job, I haven't seen this. 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Michael Neale commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Alastair D'Silva oh I think that the name of the encoding on disk (or in URI) for that matter should not impact how you interact with a named job ideally anyway (that is its own serious concern). 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-37047) Unable to copy job when running as 'SYSTEM'
Title: Message Title ikedam commented on JENKINS-37047 Re: Unable to copy job when running as 'SYSTEM' I cannot get why you have to use SYSTEM. I don't think it's a good idea to depend on authorize-project, as it's a just a implementaion of `QueueItemAuthenticator` which decides who builds run as. There can be another implementaion of `QueueItemAuthenticator`. Describe more about the configuration of your Jenkins. Why don't you configure the job to run as a user who can read jobs to copy from? 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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Alastair D'Silva edited a comment on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I think you've misunderstood our use case. We are using Multibranch Project (as we do not have control over a number of the projects that we build, so we can't drop in Jenkinsfiles, which rules out pipelines), and rely on the "Copy artifacts from another project" build step, eg.Project name: {noformat} gcc_binutils_toolchain/${GCC_BRANCH}/HOST_OS=${HOST_OS},HOST_PLATFORM=${HOST_PLATFORM},TARGET_PLATFORM=${HOST_PLATFORM} {noformat} (Where GCC_BRANCH is an axis on the current project).As you can see, the branch name is (and should be, for readability) part of the path by which the artifacts are referenced.
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-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title
Alastair D'Silva commented on JENKINS-34564
Re: Give the ability to choose how the multibranch subprojects will be named.
I think you've misunderstood our use case. We are using Multibranch Project (as we do not have control over a number of the projects that we build, so we can't drop in Jenkinsfiles, which rules out pipelines), and rely on the "Copy artifacts from another project" build step, eg. Project name: gcc_binutils_toolchain/$ {GCC_BRANCH} /HOST_OS=$ {HOST_OS} ,HOST_PLATFORM=$ {HOST_PLATFORM},TARGET_PLATFORM=${HOST_PLATFORM} (Where GCC_BRANCH is an axis on the current project). As you can see, the branch name is (and should be, for readability) part of the path by which the artifacts are referenced.
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-37018) Blue Ocean dashboard page never finishes loading
Title: Message Title
Vivek Pandey updated an issue
Jenkins / JENKINS-37018
Blue Ocean dashboard page never finishes loading
Change By:
Vivek Pandey
When I try opening the Blue Ocean dashboard view, it never finishes loading, and instead says "No pipelines found."If I open the Chrome developer tools, I can see it making a request that never finishes:https:///blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProjectIf I use curl to retrieve that page, it takes 15 minutes to load, and produces a 53-megabyte json file that's truncated at the end.The most notable large sections, from what I can tell (with job and test class names changed for privacy):{"_class":"io.jenkins.blueocean.service.embedded.rest.ActionProxiesImpl","_links":{"self":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins/pipelines/REDACTED-JOB-NAME/jobConfigHistory/"}},"_class":"hudson.plugins.jobConfigHistory.JobConfigHistoryProjectAction","jobConfigHistory":[{"currentName":"","date":"2016-07-27_01-38-02","hasConfig":true,"job":"REDACTED-JOB-NAME","oldName":"","operation":"Changed","user":"SYSTEM","userID":"SYSTEM"},(I'd say I see two-digit numbers of these "currentName" entries){"_class":"io.jenkins.blueocean.service.embedded.rest.ActionProxiesImpl","_links":{"self": { "_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins/pipelines/FOLDER_NAME_HERE/pipelines/JOB_NAME_HERE/runs/4/testReport/"}},"_class":"hudson.tasks.test.MatrixTestResult","failCount":11,"skipCount":21,"totalCount":3644,"childReports":[{"child":{"_class":"hudson.matrix.MatrixRun","number":4,"url":"https:///job/FOLDER_HERE/job/MATRIXJOB_NAME_HERE/AXIS_NAME_HERE/4/"},"result":{"_class":"hudson.tasks.junit.TestResult","testActions":[],"duration":6332.9766,"empty":false,"failCount":3," passCount passCou{nt ":903,"skipCount":5,"suites":[{"cases":[{"testActions":[{"_class":"de.esailors.jenkins.teststability.StabilityTestAction"}],"age":0,"className":"CLASS NAME HERE","duration":2.051724,"failedSince":0,"name":"TEST NAME HERE","skipped":false,"status":"PASSED"},(Thousands of these StabilityTestAction entries)
Add Comment
[JIRA] (JENKINS-37095) "git build data" always with the branch "master"
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-37095 "git build data" always with the branch "master" Change By: Mark Waite Assignee: Mark Waite 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-37103) Job DSL documentation broken
Title: Message Title Owen Wood closed an issue as Won't Fix Will handle internally Jenkins / JENKINS-37103 Job DSL documentation broken Change By: Owen Wood Status: Open Closed 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 options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37103) Job DSL documentation broken
Title: Message Title
Steven Christou updated an issue
Jenkins / JENKINS-37103
Job DSL documentation broken
Change By:
Steven Christou
About:Jenkins ver. 1.651.3 .1 (CloudBees Jenkins Enterprise 16.06) job-dsl:1.48Steps:* Load attached job (config.xml)* From job page, click "Job DSL API Reference"Stack trace thrown:{code}Error while serving http://jenkins/plugin/job-dsl/api-viewer/build/data/update-center.jsonpjava.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:403) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at com.cloudbees.jenkins.ha.HAHealthCheckFilter.doFilter(HAHealthCheckFilter.java:35) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:38) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter._doFilter(OfflineSecurityRealmFilter.java:90) at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter.doFilter(OfflineSecurityRealmFilter.java:67) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.cloudbees.opscenter.security.ClusterSessionFilter._doFilter(ClusterSessionFilter.java:69) at com.cloudbees.opscenter.security.ClusterSessionFilter.doFilter(ClusterSessionFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:201) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:178) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.
[JIRA] (JENKINS-37103) Job DSL documentation broken
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-37103 Job DSL documentation broken Change By: Steven Christou Summary: Job DSL documentation broken in CJE 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-34218) Shallow clone broken after JENKINS-24728
Title: Message Title Mark Waite resolved as Cannot Reproduce Jenkins / JENKINS-34218 Shallow clone broken after JENKINS-24728 Change By: Mark Waite Status: Open Resolved Resolution: Cannot Reproduce 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-37098) file leak with slave.log
Title: Message Title recampbell updated an issue Jenkins / JENKINS-37098 file leak with slave.log Change By: recampbell Labels: lts-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-36574) Add option to choose static notification context
Title: Message Title Christian Höltje commented on JENKINS-36574 Re: Add option to choose static notification context I pushed up a Pull Request that sets the context to one of: continuous-integration/jenkins/pr continuous-integration/jenkins/branch It's hacky (it looks at job.getName() to figure out if it is a PR or not) because I couldn't figure out a better way to detect if it is a PR or not. 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-37018) Blue Ocean dashboard page never finishes loading
Title: Message Title Vivek Pandey commented on JENKINS-37018 Re: Blue Ocean dashboard page never finishes loading James Dumay Test data is not served as part of response in latest run of pipeline. However there is some action data with test description and high level stats is present. We can also consider option to not inline actions, instead only provide links to it, but then UI needs to make separate call to get action object. I think pagination should mitigate this behavior so maybe thats all is needed. There is a bigger issue. Backend API doesn't handle matrix project correctly. In fact matrix is not modeled in backend API. Each combination of matrix axis is instance of particular run. For example if you have two axis, OS and JDK, so a run/build will be repeated for each combination of OS and JDK combination. I have opened issue https://issues.jenkins-ci.org/browse/JENKINS-37104. It might have impact on UI depending on how we want to expose matrix projects. 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-37104) Matrix project support
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-37104 Matrix project support Issue Type: Task Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Aug/01 8:38 PM Priority: Major Reporter: Vivek Pandey Backend API doesn't support Matrix style projects. Matrix or Multi-configuration project has build configuration where it can have multiple axis and for each combination of axis values build is repeated. For example if there are two axis, OS with values linux and windows and JDK with values 1.7 and 1.8. then a build will result in to 4 instance of builds: OS=linux,JDK1.7 OS=linux,JDK1.8 OS=windows,JDK1.7 OS=windows,JDK1.8 Project itself is supported and can be accessed using pipelines API but underlying matrix project properties such as axis and combination of axis is not handled. Backend should define API model and how they are exposed via REST API. Add Comment
[JIRA] (JENKINS-37103) Job DSL documentation broken in CJE
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-37103 Job DSL documentation broken in CJE Issue Type: Bug Assignee: Daniel Spilker Attachments: config.xml Components: job-dsl-plugin Created: 2016/Aug/01 8:29 PM Priority: Minor Reporter: Owen Wood About: Jenkins ver. 1.651.3.1 (CloudBees Jenkins Enterprise 16.06) job-dsl:1.48 Steps: Load attached job (config.xml) From job page, click "Job DSL API Reference" Stack trace thrown: Error while serving http://jenkins/plugin/job-dsl/api-viewer/build/data/update-center.jsonp java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:403) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.Name
[JIRA] (JENKINS-36958) Multi-branch maven project can't fetch Gitlab code, cmdline git can fetch same code
Title: Message Title ptho ho commented on JENKINS-36958 Re: Multi-branch maven project can't fetch Gitlab code, cmdline git can fetch same code same issue here. I enabled JGIT as a valid implementation, authentication still fails for multibranch pipeline. Right now, I can't get multibranch pipeline to work with GIT/JGIT. Pipeline project works fine 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-19921) Git clone fails with JGit and SSH Credentials
Title: Message Title Mark Waite commented on JENKINS-19921 Re: Git clone fails with JGit and SSH Credentials Refer to JENKINS-36958 for the bug which tracks one case where a multi-branch pipeline cannot authenticate in the same environment where a freestyle job can authenticate. The distinction in that case is that the freestyle job uses command line git for its initial clone, while the multi-branch pipeline uses JGit 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-35567) multibranch project and ssh+git broken
Title: Message Title ptho ho edited a comment on JENKINS-35567 Re: multibranch project and ssh+git broken i have the same issue. Pipeline project works but multibranch pipeline project doesn't.Setting origin to g...@somecompany.com:RnD/test.gitFetching origin...FATAL: Failed to recompute children of test_multibranch_pipelinejava.lang.IllegalStateException: Cannot open session, connection is not authenticated.Add jgit too to GIT under Global Tool Configuration, still the same issue.A bug somewhere in multibranch pipeline. tried different things, still don't get GIT to work for multibranch pipeline. 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-35567) multibranch project and ssh+git broken
Title: Message Title ptho ho edited a comment on JENKINS-35567 Re: multibranch project and ssh+git broken i have the same issue. Pipeline work project works but multibranch pipeline project doesn't.Setting origin to g...@somecompany.com:RnD/test.gitFetching origin...FATAL: Failed to recompute children of test_multibranch_pipelinejava.lang.IllegalStateException: Cannot open session, connection is not authenticated. Add jgit too to GIT under Global Tool Configuration, still the same 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-35567) multibranch project and ssh+git broken
Title: Message Title ptho ho commented on JENKINS-35567 Re: multibranch project and ssh+git broken i have the same issue. Pipeline work works but multibranch pipeline doesn't. Setting origin to g...@somecompany.com:RnD/test.git Fetching origin... FATAL: Failed to recompute children of test_multibranch_pipeline java.lang.IllegalStateException: Cannot open session, connection is not authenticated. 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-19921) Git clone fails with JGit and SSH Credentials
Title: Message Title ptho ho commented on JENKINS-19921 Re: Git clone fails with JGit and SSH Credentials I run into the same issue. Pipeline works but Multibranch Pipeline job doesn't work . Add JGit to under GIT in Global Tool Configuration as well, it's not working. Setting origin to g...@github.somecompany.com:RnD/test.git Fetching origin... FATAL: Failed to recompute children of test_multibranch_pipeline java.lang.IllegalStateException: Cannot open session, connection is not authenticated. I tried different credentials, none worked in multibranch pipeline. 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-37102) StepDescriptor.checkContextAvailability doesn't show all missing contexts
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-37102 StepDescriptor.checkContextAvailability doesn't show all missing contexts Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Aug/01 7:57 PM Environment: workflow-step-api plugin 2.3 Priority: Minor Reporter: Andrew Bayer I uncovered this trying to write a test to verify that trying to run something outside a node block would throw the right exceptions. StepDescriptor.checkContextAvailability(StepContext) uses StepDescriptor.getRequiredContext(), which returns a Set. Obviously, that means the ordering is not guaranteed. As a result, I'd get one of two different missing context exceptions in my test execution (either for hudson.Launcher or hudson.FilePath) but never both, and without any way to know which one will show up, which makes testing for the presence of the right error in the logs a challenge. That made me think that in general, we should be reporting all missing contexts, not just the first one we encounter. Ordering would still be nondeterministic, but I don't think that's a deal breaker if we're getting all the info anyway.
[JIRA] (JENKINS-37101) Race condition in concurrently executed tests running short Pipeline jobs
Title: Message Title Andrew Bayer assigned an issue to Jesse Glick Jenkins / JENKINS-37101 Race condition in concurrently executed tests running short Pipeline jobs Change By: Andrew Bayer Assignee: Oliver Gondža Jesse Glick 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-37101) Race condition in concurrently executed tests running short Pipeline jobs
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-37101
Race condition in concurrently executed tests running short Pipeline jobs
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
jenkins-test-harness, workflow-plugin
Created:
2016/Aug/01 7:49 PM
Environment:
Plugin parent 2.11, workflow-cps plugin 2.10, Jenkins core 2.7, workflow-multibranch plugin 2.8, workflow-job plugin 2.15 (via multibranch)
Priority:
Major
Reporter:
Andrew Bayer
I'm running into situations where tests pass fine when run individually or serially, but some of them will fail when run in the standard concurrency from the plugin parent. Output from such a failed test looks like https://gist.github.com/abayer/7eb7bb645efa181ecd869b04017fea74 - note that the compilation error there is actually the desired result, but when I use story.j.assertLogContains("MultipleCompilationErrorsException: startup failed"), the test fails, and the test failure output doesn't have anything after First time build. Skipping changelog.. The tests are fairly simple - along the lines of:
// Stuff constructing sampleRepo
WorkflowJob p = story.j.jenkins.createProject(WorkflowJob.class, "p");
p.setDefinition(new CpsScmFlowDefinition(new GitStep(sampleRepo.toString()).createSCM(), "Jenkinsfile"));
WorkflowRun b = p.scheduleBuild2(0).waitForStart();
story.j.assertBuildStatus(Result.FAILURE, story.j.waitForCompletion(b));
story.j.assertLogContains("MultipleCompilationErrorsException: startup failed:", b);
[JIRA] (JENKINS-36574) Add option to choose static notification context
Title: Message Title Christian Höltje commented on JENKINS-36574 Re: Add option to choose static notification context Heh. I didn't find this when searching originally, in part because I didn't know what was causing this problem. So I filed JENKINS-37100 about this. I think Nick Jones's suggestion is the right one. I'll see if I can figure it out how to do a pull request for that. 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-37100) GitHub status check "context" should be constant
Title: Message Title Christian Höltje closed an issue as Duplicate Jenkins / JENKINS-37100 GitHub status check "context" should be constant Change By: Christian Höltje 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-37100) GitHub status check "context" should be constant
Title: Message Title Christian Höltje commented on JENKINS-37100 Re: GitHub status check "context" should be constant Ah, I found some comments on this on https://github.com/jenkinsci/github-branch-source-plugin/commit/5a98d2a885aa951087ba329acdc560bc1e6b7062 and a duplicate issue https://issues.jenkins-ci.org/browse/JENKINS-36574. 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-37100) GitHub status check "context" should be constant
Title: Message Title
Christian Höltje commented on JENKINS-37100
Re: GitHub status check "context" should be constant
I think I found the source of the problem in the github-branch-source-plugin:...GitHubBuildStatusNotification.java:73. It seems like it should be replaced with something like:
private static void createCommitStatus(@Nonnull GHRepository repo, @Nonnull String revision, @Nonnull GHCommitState state, @Nonnull String url, @Nonnull String message, @Nonnull Job job) throws IOException {
LOGGER.log(Level.FINE, "{0}/commit/{1} {2} from {3}", new Object[] {repo.getHtmlUrl(), revision, state, url});
repo.createCommitStatus(revision, state, url, message, "Jenkins job " + job.getParent().getName());
}
I added getParent() so that the context name would become "Jenkins job " instead of "Jenkins job ".
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-37100) GitHub status check "context" should be constant
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-37100 GitHub status check "context" should be constant Change By: Christian Höltje Component/s: github-organization-folder-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-37100) GitHub status check "context" should be constant
Title: Message Title Christian Höltje commented on JENKINS-37100 Re: GitHub status check "context" should be constant It looks like this Jenkinsfile snippet is supposed to change the status check "context" name but it doesn't work if using the github-organization-folder plugin: properties([ [$class: 'GithubProjectProperty', displayName: 'STATICNAME', projectUrlStr: 'https://github.com//'] ]); So I guess this is a bug in the github-organization-folder 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-37100) GitHub status check "context" should be constant
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-37100 GitHub status check "context" should be constant Change By: Christian Höltje Environment: Jenkins: 2.7.1github-api.jpi v1.76github-branch-source.jpi v1.8.1github-oauth.jpi v0.24github-organization-folder.jpi v1. 3 4 github.jpi v1. 19 20 . 3 0 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-30909) queue.xml only gets persisted on successful shutdown
Title: Message Title Tim Vail commented on JENKINS-30909 Re: queue.xml only gets persisted on successful shutdown Jesse – this appears to be an old issue. However, I'm finding a few issues with Jenkins and the queue persistence. Particularly on Windows. If you run Jenkins as a service then you restart the service (as opposed to telling Jenkins to exit) then there is no queue.xml created and the build queue is therefore lost. Prior situation means that if the machine is rebooted – we would probably lose the queue. Even more interesting – it appears that your fix somehow isn't working for /safeRestart or /restart. It is like /exit (which does save the queue.xml) is actually safer than /safeRestart. Considering all things – why don't we simply write queue.xml to the disk on every queue change? With today's HDD and SSD's – I'd think for most servers Jenkins is running on – the cost of doing so should be minimal. Compared to the writing of build logs to disk this is practically nothing. At least, why not make it an option to continuously persist the build queue (if so, then I'd think it should be on by default). 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,
[JIRA] (JENKINS-37100) GitHub status check "context" should be constant
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-37100 GitHub status check "context" should be constant Change By: Christian Höltje Environment: Jenkins: 2.7.1 GitHub github - Plugin: api.jpi v1.76github-branch-source.jpi v1.8. 1 github-oauth . 20 jpi v0 . 0 24 Git github - Plugin: 2 organization-folder . 5 jpi v1 .3 github.jpi v1.19.3 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-37100) GitHub status check "context" should be constant
Title: Message Title
Christian Höltje updated an issue
Jenkins / JENKINS-37100
GitHub status check "context" should be constant
Change By:
Christian Höltje
When doing a pull request , the github PR page is updated with a " status " check showing the progress or result of a Jenkins build.Currently, the name for the status looks something like {{Jenkins job PR-1}}. In the [github api docs|https://developer.github.com/v3/repos/statuses/], they call this the "context".The problem is that the "context" changes for each PR and branch. This makes setting up protections for branches impossible.If you turn on protections for a branch and then go to {{ https://github.com/my-org/my-project/settings/branches/my-branch }} and turn on "Require status checks to pass before merging" you'll be shown "Status checks found in the last week for this repository" which might include (for example):* Jenkins job PR-1* Jenkins job PR-2* Jenkins job masterYou can't require any of these status checks because the next status check will have a context with a new (previously unseen) PR number.Instead, it should just say "Jenkins" or a customized name specified in the default branches branch's {{Jenkinsfile}}.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37100) GitHub status check "context" should be constant
Title: Message Title Christian Höltje updated an issue Jenkins / JENKINS-37100 GitHub status check "context" should be constant Change By: Christian Höltje Summary: PR GitHub status name shouldn't vary check "context" should be constant 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-37100) PR status name shouldn't vary
Title: Message Title Christian Höltje created an issue Jenkins / JENKINS-37100 PR status name shouldn't vary Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2016/Aug/01 6:32 PM Environment: Jenkins: 2.7.1 GitHub-Plugin: 1.20.0 Git-Plugin: 2.5.3 Priority: Major Reporter: Christian Höltje When doing a pull request the github PR page is updated with a "status" showing the progress or result of a Jenkins build. Currently, the name for the status looks something like Jenkins job PR-1. In the github api docs, they call this the "context". The problem is that the "context" changes for each PR and branch. This makes setting up protections for branches impossible. If you turn on protections for a branch and then go to https://github.com/my-org/my-project/settings/branches/my-branch and turn on "Require status checks to pass before merging" you'll be shown "Status checks found in the last week for this repository" which might include (for example): Jenkins job PR-1 Jenkins job PR-2 Jenkins job master You can't require any of these status checks because the next status check will have a context with a new (previously unseen) PR number. Instead, it should just say "Jenkins" or a customized name specified in the default branches Jenkinsfile.
[JIRA] (JENKINS-6819) Jobs are triggered twice occasionally
Title: Message Title Christian Munsayac commented on JENKINS-6819 Re: Jobs are triggered twice occasionally This is also hapenning in 2.15 version. Jobs builds twice using poll scm cron or manually clicking the build. The job executes twice 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-37099) Null value passed through ParametersAction causes all jobs to throw StackTrace
Title: Message Title Stacey Fletcher created an issue Jenkins / JENKINS-37099 Null value passed through ParametersAction causes all jobs to throw StackTrace Issue Type: Bug Assignee: vjuranek Attachments: jenkins_stack_trace.txt Components: core, groovy-plugin Created: 2016/Aug/01 6:02 PM Environment: Jenkins 1.642.4 Labels: Groovy NPE ParametersAction Queue isStuck Priority: Major Reporter: Stacey Fletcher I was attempting to trigger a build using the System Groovy Script with the following method call: item.scheduleBuild2(0, new Cause.UpstreamCause(build), new ParametersAction(null)) The passing of null should cause an NPE, but because of this all jobs that were submitted from then on were stuck in our Build Queue. In order to fix it we had to bounce our Jenkins instance. Initial Stack Trace: SEVERE: Timer task hudson.model.LoadStatistics$LoadStatisticsUpdater@1b2ee745 failed java.lang.NullPointerException at hudson.model.ParametersAction.getAssignedLabel(ParametersAction.java:140) at hudson.model.Queue$Item.getAssignedLabelFor(Queue.java:2079) at hudson.model.Label$1.matches(Label.java:120) at hudson.model.LoadStatistics.computeSnapshot(LoadStatistics.java:361) at hudson.model.LoadStatistics$LoadStatisticsUpdater.doRun(LoadStatistics.java:395) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50) at java.util.concurrent.Executors$RunnableAdapter.ca
[JIRA] (JENKINS-21670) Option to anonymize customer labels
Title: Message Title Arnaud Héritier commented on JENKINS-21670 Re: Option to anonymize customer labels Really good question cc Steven Christou As we are running in Jenkins I think that the best is to use its APIs to find all kind of Jobs (Jenkins.instance.getAllItems...) and then to create a map to replace each name. We probably need to do the same for views, users/accounts, After this we need a mechanism of filter when we are getting logs, config files, ... to replace all orginal names by the "protected" value 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-21670) Option to anonymize customer labels
Title: Message Title Minudika Malshan commented on JENKINS-21670 Re: Option to anonymize customer labels Arnaud Héritier Jesse Glick Since the entities like job names does not have a specific format like network addresses do, how to find a string as such a name which is needed to be anatomized? 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-37047) Unable to copy job when running as 'SYSTEM'
Title: Message Title
Brian Krische edited a comment on JENKINS-37047
Re: Unable to copy job when running as 'SYSTEM'
Actually, looking through the Jenkins documentation more, wouldn't something like this be even better:{code:title=JobcopyBuilder.java}if (ACL.SYSTEM.equals(Jenkins.getAuthentication())) {JobProperty systemAuthorizationStrategy = build.getProject().getProperty("SystemAuthorizationStrategy");if (systemAuthorizationStrategy == null) {orig = ACL.impersonate(Jenkins.ANONYMOUS);}}{code}Then you shouldn't even have to depend on "Authorize Project" at all. *Edit:* Nevermind, I just realized that the property is {{AuthorizeProjectProperty}} class which then we would have to run {{.getStrategy()}} to determine the authorization strategy.
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-37047) Unable to copy job when running as 'SYSTEM'
Title: Message Title
Brian Krische edited a comment on JENKINS-37047
Re: Unable to copy job when running as 'SYSTEM'
Actually, looking through the Jenkins documentation more, wouldn't something like this be even better:{code:title=JobcopyBuilder.java}if (ACL.SYSTEM.equals(Jenkins.getAuthentication())) { if (ACL.SYSTEM.equals(Jenkins.getAuthentication())) { JobProperty systemAuthorizationStrategy = build.getProject().getProperty("SystemAuthorizationStrategy");if (systemAuthorizationStrategy == null) {orig = ACL.impersonate(Jenkins.ANONYMOUS);}}{code}Then you shouldn't even have to depend on "Authorize Project" at all.
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-37047) Unable to copy job when running as 'SYSTEM'
Title: Message Title
Brian Krische commented on JENKINS-37047
Re: Unable to copy job when running as 'SYSTEM'
Actually, looking through the Jenkins documentation more, wouldn't something like this be even better:
JobcopyBuilder.java
if (ACL.SYSTEM.equals(Jenkins.getAuthentication())) {
if (ACL.SYSTEM.equals(Jenkins.getAuthentication())) {
JobProperty systemAuthorizationStrategy = build.getProject().getProperty("SystemAuthorizationStrategy");
if (systemAuthorizationStrategy == null) {
orig = ACL.impersonate(Jenkins.ANONYMOUS);
}
}
Then you shouldn't even have to depend on "Authorize Project" at all.
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-37047) Unable to copy job when running as 'SYSTEM'
Title: Message Title
Brian Krische commented on JENKINS-37047
Re: Unable to copy job when running as 'SYSTEM'
What about doing something like in my commit:
JobcopyBuilder.java
if (ACL.SYSTEM.equals(Jenkins.getAuthentication())) {
boolean configuredAsSystem = false;
for (Object jobProperty : build.getProject().getAllProperties()) {
if (jobProperty instanceof AuthorizeProjectProperty) {
if (((AuthorizeProjectProperty) jobProperty).getStrategy() instanceof SystemAuthorizationStrategy) {
configuredAsSystem = true;
}
}
}
if (!configuredAsSystem) {
orig = ACL.impersonate(Jenkins.ANONYMOUS);
}
}
That should allow it to execute as SYSTEM if it was configured to do so by the Authorize Project plugin. But if it wasn't, then it would be hard-coded to ANONYMOUS like you had it. I'm not to familiar with writing Jenkins plugins, but could you configure Job Copy to optionally depend on Authorize Project, and do that kind of check only if the plugin is installed?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscrib
[JIRA] (JENKINS-27548) Sporadic IOException: Failed to persist config
Title: Message Title
Grigor Lechev edited a comment on JENKINS-27548
Re: Sporadic IOException: Failed to persist config
Here you go, the common plugin is findbugs here. [ { code ] } jenkins@8ed06777b6e7:/var/jenkins_home/plugins$ grep -ir 'org.xml.sax.driver' *Binary file analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar matchesBinary file findbugs/WEB-INF/lib/library-2.0.4.jar matchesBinary file fortify360/WEB-INF/lib/xercesImpl-2.6.2.jar matchesBinary file jacoco/WEB-INF/lib/xercesImpl-2.9.1.jar matches [ { 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-36724) Branch indexing hangs
Title: Message Title Shauvik Roy Choudhary edited a comment on JENKINS-36724 Re: Branch indexing hangs After a few days there are so many "Branch Indexing" messages that it fills up the screen and doesn't process new PRs anymore. :( !branch-indexing-hangs-2.png|thumbnail! *Jenkins needs to be restarted for this to be fixed bypassed .* 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-27548) Sporadic IOException: Failed to persist config
Title: Message Title Grigor Lechev commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config Here you go, the common plugin is findbugs here. [code]jenkins@8ed06777b6e7:/var/jenkins_home/plugins$ grep -ir 'org.xml.sax.driver' * Binary file analysis-core/WEB-INF/lib/xercesImpl-2.11.0.jar matches Binary file findbugs/WEB-INF/lib/library-2.0.4.jar matches Binary file fortify360/WEB-INF/lib/xercesImpl-2.6.2.jar matches Binary file jacoco/WEB-INF/lib/xercesImpl-2.9.1.jar matches[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-36724) Branch indexing hangs
Title: Message Title Shauvik Roy Choudhary edited a comment on JENKINS-36724 Re: Branch indexing hangs After a few days there are so many "Branch Indexing" messages that it fills up the screen and doesn't process new PRs anymore. :( !branch-indexing-hangs-2.png|thumbnail!*Jenkins needs to be restarted for this to be 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-36724) Branch indexing hangs
Title: Message Title Shauvik Roy Choudhary commented on JENKINS-36724 Re: Branch indexing hangs After a few days there are so many "Branch Indexing" messages that it fills up the screen and doesn't process new PRs anymore. 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-36724) Branch indexing hangs
Title: Message Title Shauvik Roy Choudhary updated an issue Jenkins / JENKINS-36724 Branch indexing hangs Change By: Shauvik Roy Choudhary Attachment: branch-indexing-hangs-2.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-36375) Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Title: Message Title simon so commented on JENKINS-36375 Re: Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs Same here change-assembly-version-plugin 1.5.1 Slave Windows 10 build node 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-36993) Cookie header too long, causing a 413 HTTP error
Title: Message Title Daniel Beck resolved as Duplicate Jenkins / JENKINS-36993 Cookie header too long, causing a 413 HTTP error Change By: Daniel Beck 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-37098) file leak with slave.log
Title: Message Title Nicolas De Loof created an issue Jenkins / JENKINS-37098 file leak with slave.log Issue Type: Bug Assignee: Nicolas De Loof Components: core Created: 2016/Aug/01 4:10 PM Priority: Major Reporter: Nicolas De Loof SlaveComputer uses a ReopenableFileOutputStream for it's log introduced by https://github.com/jenkinsci/jenkins/commit/0ddb0c5cca757a4a34e0c162bbca6504f5cec25f, intent was to track some termination issue and report status to user. this results in a file-leak when channel.onClose logs termination but kill() already invoked close on the log stream. By nature, ReopenableFileOutputStream introduce a risk for a writer to reopen the stream without any control on who is responsible to close it. in the meantime, https://github.com/jenkinsci/jenkins/commit/733f091125099a7ed823c0d0d7cb96ae8d39f364 introduced deletion of the slave's log directory on termination (which makes previous fix useless) Depending on race condition, this can result in: listener to fail log it's termination status - but PrintStream#write do capture the IOException and PrintStream#checkError is never checked, so silently ignored slave log directory deletion to fail due to file lock issue (detected on Windows), resulting in a non-blocker error reported in Jenkins log.
[JIRA] (JENKINS-37083) Jenkins wiki for Remote Access API needs improvement to increase clarity of the matter
Title: Message Title Daniel Beck resolved as Not A Defect That's the Jenkins wiki, not the man curl wiki. Besides, it's a wiki, so anyone can fix it. Jenkins / JENKINS-37083 Jenkins wiki for Remote Access API needs improvement to increase clarity of the matter Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect 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
[JIRA] (JENKINS-36871) JNLPProtocol4
Title: Message Title Daniel Beck reopened an issue Oops, wasn't fixed by that change. Jenkins / JENKINS-36871 JNLPProtocol4 Change By: Daniel Beck Resolution: Fixed Status: Resolved 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.
