[JIRA] (JENKINS-56284) Refactor GitSCM.computeChangeLog() to be extensible
Title: Message Title Francisco Fernández started work on JENKINS-56284 Change By: Francisco Fernández Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197862.155117892.10617.1580716500518%40Atlassian.JIRA.
[JIRA] (JENKINS-56284) Refactor GitSCM.computeChangeLog() to be extensible
Title: Message Title Francisco Fernández updated JENKINS-56284 Jenkins / JENKINS-56284 Refactor GitSCM.computeChangeLog() to be extensible Change By: Francisco Fernández Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197862.155117892.10619.1580716500565%40Atlassian.JIRA.
[JIRA] (JENKINS-60946) Wrong result of function getLocalDir() if "local" equals empty string
Title: Message Title Aleksandr Iarovoi created an issue Jenkins / JENKINS-60946 Wrong result of function getLocalDir() if "local" equals empty string Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: subversion-plugin Created: 2020-02-03 07:42 Environment: Jenkins ver. 2.190.1 Subversion Plug-in 2.12.2 Priority: Major Reporter: Aleksandr Iarovoi Current implementation of getLocalDir function if(local==null) return getLastPathComponent(getURL()); return local; When local == "" the function returns workspace, but checkout occurs in last path component of the URL relative to the workspace root. Conditions should be if(local==null || local == "") Add Comment
[JIRA] (JENKINS-50462) Artifacts tab presents everything as a flat list, making navigation time consuming
Title: Message Title Igor Litmanovich commented on JENKINS-50462 Re: Artifacts tab presents everything as a flat list, making navigation time consuming This issue seems to be stuck - any chance it will be resolved? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189521.1522249108000.10602.1580714940289%40Atlassian.JIRA.
[JIRA] (JENKINS-60878) "Region" list is empty when using JCasC to configure Azure VM agent
Title: Message Title Muhammad Faizan ul haq commented on JENKINS-60878 Re: "Region" list is empty when using JCasC to configure Azure VM agent Jie Shen But there are other options like: "Virtual Machine Size" "Storage Account Name" "Resource Group Name". I assume there are also loaded from Network. It seems like, their drop down list is available but not the "Region" list. Is there any other clue ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204260.1580136009000.10600.1580713320287%40Atlassian.JIRA.
[JIRA] (JENKINS-60906) Write list data to
Title: Message Title Aleksi Simell edited a comment on JENKINS-60906 Re: Write list data to Hi,This feature is discussed in https://issues.jenkins-ci.org/browse/ JENKINS-57240. Closing this as duplicate. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204297.1580312483000.10597.1580712780189%40Atlassian.JIRA.
[JIRA] (JENKINS-60906) Write list data to
Title: Message Title Aleksi Simell closed an issue as Duplicate Hi, This feature is discussed in https://issues.jenkins-ci.org/browse/JENKINS-57240. Closing this as duplicate. Jenkins / JENKINS-60906 Write list data to Change By: Aleksi Simell Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view thi
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title sreepadh chitti edited a comment on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error [~udayasree18] thanks for the info. May I know is there any other way to trigger Jenkins job when comment created or updated in Jira ticket or can you please provide some more information like what are those variables that has been blocked by Jira cloud ? (Incase If you have such information any) Thanks in advance! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194307.1537972591000.10589.1580711940650%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title sreepadh chitti commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error Udaya Sree thanks for the info. May I know is there any other way to trigger Jenkins job when comment created or updated in Jira ticket? Thanks in advance! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194307.1537972591000.10582.1580710860407%40Atlassian.JIRA.
[JIRA] (JENKINS-60222) Centos 8, not working email send - TLC error
Title: Message Title Konstantin A commented on JENKINS-60222 Re: Centos 8, not working email send - TLC error TLS 1.0, 1.1, 1.2 disabled by default in Centos 8 https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/considerations_in_adopting_rhel_8/security_considerations-in-adopting-rhel-8#tls-v10-v11_security it works: update-crypto-policies --set LEGACY Setting system policy to LEGACY Note: System-wide crypto policies are applied on application start-up. It is recommended to restart the system for the change of policies to fully take place. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203195.1574241065000.10578.1580706300167%40Atlassian.JIRA.
[JIRA] (JENKINS-57980) Incorrect links in /manage
Title: Message Title Aman Bora commented on JENKINS-57980 Re: Incorrect links in /manage I would like to work on this issue, is it available? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199965.1560329204000.10570.1580699820173%40Atlassian.JIRA.
[JIRA] (JENKINS-60878) "Region" list is empty when using JCasC to configure Azure VM agent
Title: Message Title Jie Shen commented on JENKINS-60878 Re: "Region" list is empty when using JCasC to configure Azure VM agent The region options are dynamically loaded from the server side. So please verify the configuration and make sure network is available. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204260.1580136009000.10566.1580697300139%40Atlassian.JIRA.
[JIRA] (JENKINS-60878) "Region" list is empty when using JCasC to configure Azure VM agent
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-60878 "Region" list is empty when using JCasC to configure Azure VM agent Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204260.1580136009000.10563.1580697060252%40Atlassian.JIRA.
[JIRA] (JENKINS-60008) Build fails due to Distribution Group in AppCenter not having Correct Permissions
Title: Message Title Mez Pahlan updated JENKINS-60008 Jenkins / JENKINS-60008 Build fails due to Distribution Group in AppCenter not having Correct Permissions Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Released As: 0.8.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202825.1572558119000.10550.1580689440236%40Atlassian.JIRA.
[JIRA] (JENKINS-60232) Add AppCenter API models for error responses for used APIs
Title: Message Title Mez Pahlan updated JENKINS-60232 Jenkins / JENKINS-60232 Add AppCenter API models for error responses for used APIs Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Released As: 0.8.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203208.157426942.10551.1580689440248%40Atlassian.JIRA.
[JIRA] (JENKINS-60171) HTTP 422 uploading Android APK artifact
Title: Message Title Mez Pahlan commented on JENKINS-60171 Re: HTTP 422 uploading Android APK artifact Hi Terry Wallace, I'm in the process of releasing 0.8.1 of the plugin that will better output the HTTP error when we encounter it. Could you give it another go with that version and let me know the error output. Many thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203126.1573734069000.10546.1580689080167%40Atlassian.JIRA.
[JIRA] (JENKINS-60008) Build fails due to Distribution Group in AppCenter not having Correct Permissions
Title: Message Title Mez Pahlan commented on JENKINS-60008 Re: Build fails due to Distribution Group in AppCenter not having Correct Permissions Hi Josh Brozen apologies for the slow movement of this over the Christmas period and the New Year. I'm releasing 0.8.1 that will at least point you in the right direction regarding permissions and API errors. It's not going to automatically fix the missing permission in AppCenter but at least it will be more obvious now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202825.1572558119000.10544.1580687220195%40Atlassian.JIRA.
[JIRA] (JENKINS-60008) Build fails due to Distribution Group in AppCenter not having Correct Permissions
Title: Message Title Mez Pahlan updated JENKINS-60008 Jenkins / JENKINS-60008 Build fails due to Distribution Group in AppCenter not having Correct Permissions Change By: Mez Pahlan Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202825.1572558119000.10542.1580686920418%40Atlassian.JIRA.
[JIRA] (JENKINS-60008) Build fails due to Distribution Group in AppCenter not having Correct Permissions
Title: Message Title Mez Pahlan updated JENKINS-60008 Jenkins / JENKINS-60008 Build fails due to Distribution Group in AppCenter not having Correct Permissions Change By: Mez Pahlan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202825.1572558119000.10540.1580686920393%40Atlassian.JIRA.
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Martin Henschke commented on JENKINS-60917 Re: Jenkins Pipeline requires at least one successfull build for the trigger to work Hi Sven, My initial read of the bug suggested this was likely the same root cause as JENKINS-60649- but doing a bit more investigation it looks like they have separate causes. Accordingly, I've reopened the ticket. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.10538.1580678880151%40Atlassian.JIRA.
[JIRA] (JENKINS-60917) Jenkins Pipeline requires at least one successfull build for the trigger to work
Title: Message Title Martin Henschke reopened an issue Jenkins / JENKINS-60917 Jenkins Pipeline requires at least one successfull build for the trigger to work Change By: Martin Henschke Resolution: Duplicate Status: Closed Reopened Assignee: Kristy Hughes Martin Henschke Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204311.1580371734000.10536.1580678820352%40Atlassian.JIRA.
[JIRA] (JENKINS-60933) Temporal coupling metric
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-60933 Temporal coupling metric Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204330.1580470059000.10531.1580677860111%40Atlassian.JIRA.
[JIRA] (JENKINS-60932) Indentation Level metric
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-60932 Indentation Level metric Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204329.1580469432000.10532.1580677860206%40Atlassian.JIRA.
[JIRA] (JENKINS-60934) Word cloud of commit messages
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-60934 Word cloud of commit messages Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204331.1580470104000.10533.1580677860220%40Atlassian.JIRA.
[JIRA] (JENKINS-60935) Code churn metric
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-60935 Code churn metric Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204332.1580470141000.10530.1580677800057%40Atlassian.JIRA.
[JIRA] (JENKINS-60931) Incremental analysis
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-60931 Incremental analysis Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204328.158049000.10529.1580677080063%40Atlassian.JIRA.
[JIRA] (JENKINS-60945) Inspect all repository commits (without selecting the files)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-60945 Inspect all repository commits (without selecting the files) Issue Type: Improvement Assignee: Unassigned Components: git-forensics-plugin Created: 2020-02-02 20:54 Labels: newbie-friendly Priority: Minor Reporter: Ulli Hafner Currently, the GitRepositoryMiner analyzes the repository by iterating over all files and inspecting the commits per file. This makes sense if only a few files need to be inspected. On the other hand, if the whole repository is scanned it makes much more sense to change that algorithm so that all commits of the repository are scanned in a row and the statistics of the containing files are updated for each commit. This should speed up the processing. Add Comment
[JIRA] (JENKINS-60944) Add runtime of miner to RepositoryStatistics
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-60944
Add runtime of miner to RepositoryStatistics
Change By:
Ulli Hafner
Currently, the {{[GitRepositoryMiner|https://github.com/jenkinsci/git-forensics-plugin/blob/master/src/main/java/io/jenkins/plugins/forensics/git/miner/GitRepositoryMiner.java]}} logs the runtime of the mining process to the console log only:{noformat}[Forensics] Creating SCM miner to obtain statistics for affected repository files[Forensics] -> Git miner successfully created in working tree '/var/data/workspace/Forensics'[Forensics] Analyzing the commit log of the Git repository '/var/data/workspace/Forensics'[Forensics] -> created report for 697 files in 41 seconds{noformat}It would be nice if this information would be stored in the {{[RepositoryStatistics|https://github.com/jenkinsci/forensics-api-plugin/blob/master/src/main/java/io/jenkins/plugins/forensics/miner/RepositoryStatistics.java]}} instance as well. This feature should require a change in the model object only. Steps to do:- Record the current time stamp (see {{[GitRepositoryMiner| https://github.com/jenkinsci/git-forensics-plugin/blob/master/src/main/java/io/jenkins/plugins/forensics/git/miner/GitRepositoryMiner.java#L54 ]}} ) when the {{[RepositoryStatistics|https://github.com/jenkinsci/forensics-api-plugin/blob/master/src/main/java/io/jenkins/plugins/forensics/miner/RepositoryStatistics.java]}} instance is created (constructor)- Update the total runtime whenever a new modifying operation has been invoked on the instance (all {{add * }} methods) - Visualize the total time in the [user interface|https://github.com/jenkinsci/forensics-api-plugin/blob/master/src/main/resources/io/jenkins/plugins/forensics/miner/ForensicsBuildAction/summary.jelly]
Add Comment
[JIRA] (JENKINS-60944) Add runtime of miner to RepositoryStatistics
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60944 Add runtime of miner to RepositoryStatistics Change By: Ulli Hafner Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204346.158067573.10526.1580676000155%40Atlassian.JIRA.
[JIRA] (JENKINS-60944) Add runtime of miner to RepositoryStatistics
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-60944
Add runtime of miner to RepositoryStatistics
Change By:
Ulli Hafner
Currently, the {{ [ GitRepositoryMiner |https://github.com/jenkinsci/git-forensics-plugin/blob/master/src/main/java/io/jenkins/plugins/forensics/git/miner/GitRepositoryMiner.java] }} logs the runtime of the mining process to the console log only:{noformat}[Forensics] Creating SCM miner to obtain statistics for affected repository files[Forensics] -> Git miner successfully created in working tree '/var/data/workspace/Forensics'[Forensics] Analyzing the commit log of the Git repository '/var/data/workspace/Forensics'[Forensics] -> created report for 697 files in 41 seconds{noformat}It would be nice if this information would be stored in the {{ [ RepositoryStatistics |https://github.com/jenkinsci/forensics-api-plugin/blob/master/src/main/java/io/jenkins/plugins/forensics/miner/RepositoryStatistics.java] }} instance as well. This feature should require a change in the model object only. Steps to do:- Record the current time stamp (see https://github.com/jenkinsci/git-forensics-plugin/blob/master/src/main/java/io/jenkins/plugins/forensics/git/miner/GitRepositoryMiner.java#L54) when the {{ [ RepositoryStatistics |https://github.com/jenkinsci/forensics-api-plugin/blob/master/src/main/java/io/jenkins/plugins/forensics/miner/RepositoryStatistics.java] }} instance is created (constructor)- Update the total runtime whenever a new modifying operation has been invoked on the instance (all {{add*}} methods)
Add Comment
[JIRA] (JENKINS-60944) Add runtime of miner to RepositoryStatistics
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-60944
Add runtime of miner to RepositoryStatistics
Change By:
Ulli Hafner
Currently, the {{GitRepositoryMiner}} logs the runtime of the mining process to the console log only:{noformat}[Forensics] Creating SCM miner to obtain statistics for affected repository files[Forensics] -> Git miner successfully created in working tree '/var/data/workspace/Forensics'[Forensics] Analyzing the commit log of the Git repository '/var/data/workspace/Forensics'[Forensics] -> created report for 697 files in 41 seconds{noformat}It would be nice if this information would be stored in the {{RepositoryStatistics}} instance as well. This feature should require a change in the model object only. Steps to do:- Record the current time stamp (see https://github.com/jenkinsci/git-forensics-plugin/blob/master/src/main/java/io/jenkins/plugins/forensics/git/miner/GitRepositoryMiner.java#L54) when the {{RepositoryStatistics}} instance is created (constructor) - Update the total runtime whenever a new modifying operation has been invoked on the instance (all {{add*}} methods)
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60944) Add runtime of miner to RepositoryStatistics
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-60944 Add runtime of miner to RepositoryStatistics Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204346.158067573.10523.1580675820056%40Atlassian.JIRA.
[JIRA] (JENKINS-60944) Add runtime of miner to RepositoryStatistics
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-60944 Add runtime of miner to RepositoryStatistics Issue Type: New Feature Assignee: Ulli Hafner Components: forensics-api-plugin, git-forensics-plugin Created: 2020-02-02 20:35 Priority: Minor Reporter: Ulli Hafner Currently, the GitRepositoryMiner logs the runtime of the mining process to the console log only: [Forensics] Creating SCM miner to obtain statistics for affected repository files [Forensics] -> Git miner successfully created in working tree '/var/data/workspace/Forensics' [Forensics] Analyzing the commit log of the Git repository '/var/data/workspace/Forensics' [Forensics] -> created report for 697 files in 41 seconds It would be nice if this information would be stored in the RepositoryStatistics instance as well. This feature should require a change in the model object only. Steps to do: Record the current time stamp (see https://github.com/jenkinsci/git-forensics-plugin/blob/master/src/main/java/io/jenkins/plugins/forensics/git/miner/GitRepositoryMiner.java#L54) when the instance is created Update the total runtime whenever a new modifying operation has been invoked on the instance
[JIRA] (JENKINS-54219) portlet rich-text-publisher-plugin rendering broken with 2.146
Title: Message Title Tobias Gruetzmacher updated an issue Jenkins / JENKINS-54219 portlet rich-text-publisher-plugin rendering broken with 2.146 Change By: Tobias Gruetzmacher Component/s: dashboard-view-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194858.1540378373000.10514.1580671380298%40Atlassian.JIRA.
[JIRA] (JENKINS-12863) dashboard - jobs list portlet - add summary statistics
Title: Message Title Tobias Gruetzmacher closed an issue as Won't Do Jenkins / JENKINS-12863 dashboard - jobs list portlet - add summary statistics Change By: Tobias Gruetzmacher Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143321.1329952336000.10511.1580671320298%40Atlassian.JIRA.
[JIRA] (JENKINS-12167) add a klocwork portlet to dashboard view
Title: Message Title Tobias Gruetzmacher closed an issue as Won't Do Jenkins / JENKINS-12167 add a klocwork portlet to dashboard view Change By: Tobias Gruetzmacher Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142489.1324394811000.10509.1580671200321%40Atlassian.JIRA.
[JIRA] (JENKINS-60943) Add JCasC support for remote retrieval of plugins
Title: Message Title
Tiran Meltser created an issue
Jenkins / JENKINS-60943
Add JCasC support for remote retrieval of plugins
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2020-02-02 19:14
Labels:
jcasc Plugins
Priority:
Minor
Reporter:
Tiran Meltser
I would like to suggest enhancing the JCasC mechanism in regards to plugins installation. Current procedure is quite intrusive and requires building a special Dockerfile. I suggest eliminating this cumbersome need, simply by adding another environment variable , similar to CASC_JENKINS_CONFIG (e.g. }}{{CASC_JENKINS_PLUGINS_CONFIG) which will hold a path or (more likely) a URL (e.g. to designated Git repository that holds the Jenkins configuration) in which the list of desired plugins will be retrieved in same format as today, and thus keep allowing running Jenkins container as today (with the addition of this new environment variable).{{}} I personally will wait for such a feature before reverting to JCasC (which is a great initiative). I very much hope this improvement will find its way into Jenkins in a short time.{{}}
[JIRA] (JENKINS-56123) JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all
Title: Message Title Tobias Gruetzmacher commented on JENKINS-56123 Re: JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all The jacoco-plugin brings its own dashboard portlet, removing dashboard-view-plugin from components, because this must be fixed in the jacoco-plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197559.1550064915000.10505.1580670900235%40Atlassian.JIRA.
[JIRA] (JENKINS-56123) JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all
Title: Message Title Tobias Gruetzmacher updated an issue Jenkins / JENKINS-56123 JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all Change By: Tobias Gruetzmacher Component/s: dashboard-view-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197559.1550064915000.10498.1580670720359%40Atlassian.JIRA.
[JIRA] (JENKINS-56123) JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all
Title: Message Title Tobias Gruetzmacher assigned an issue to Ognjen Bubalo Jenkins / JENKINS-56123 JaCoCo Coverage Statistics Grid Portlet reports 100% coverage in case there is no coverage collected at all Change By: Tobias Gruetzmacher Assignee: Tobias Gruetzmacher Ognjen Bubalo Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197559.1550064915000.10501.1580670720407%40Atlassian.JIRA.
[JIRA] (JENKINS-28538) CCE after Upgrade to 1.6 Jenkins
Title: Message Title Tobias Gruetzmacher updated an issue Jenkins / JENKINS-28538 CCE after Upgrade to 1.6 Jenkins Change By: Tobias Gruetzmacher Component/s: dashboard-view-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162977.1432232482000.10492.1580670540540%40Atlassian.JIRA.
[JIRA] (JENKINS-28538) CCE after Upgrade to 1.6 Jenkins
Title: Message Title Tobias Gruetzmacher commented on JENKINS-28538 Re: CCE after Upgrade to 1.6 Jenkins I don't think this is a bug in the dashboard-view-plugin, but in the jacoco-plugin. Removing dashboard-view for now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162977.1432232482000.10486.1580670540416%40Atlassian.JIRA.
[JIRA] (JENKINS-60275) Connecting via https with Jenkins_URL as http breaks Favicon theme element
Title: Message Title Tobias Gruetzmacher updated JENKINS-60275 Jenkins / JENKINS-60275 Connecting via https with Jenkins_URL as http breaks Favicon theme element Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/simple-theme-plugin/releases/tag/simple-theme-plugin-0.6 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203265.1574726114000.10481.1580670180365%40Atlassian.JIRA.
[JIRA] (JENKINS-58590) JCasC: simple theme plugin cannot export extra css elements
Title: Message Title Tobias Gruetzmacher updated JENKINS-58590 Jenkins / JENKINS-58590 JCasC: simple theme plugin cannot export extra css elements Change By: Tobias Gruetzmacher Status: Fixed but Unreleased Resolved Released As: https://github.com/jenkinsci/simple-theme-plugin/releases/tag/simple-theme-plugin-0.6 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200746.1563767491000.10483.1580670180399%40Atlassian.JIRA.
[JIRA] (JENKINS-60942) swarm plugin requires anonymous/overall/read if not started with user/password
Title: Message Title Amit Dar updated an issue Jenkins / JENKINS-60942 swarm plugin requires anonymous/overall/read if not started with user/password Change By: Amit Dar Summary: swarm plugin requires anonymous/ overall/read if not started with user/password Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204343.158066135.10479.1580663460158%40Atlassian.JIRA.
[JIRA] (JENKINS-60275) Connecting via https with Jenkins_URL as http breaks Favicon theme element
Title: Message Title Tobias Gruetzmacher updated JENKINS-60275 Jenkins / JENKINS-60275 Connecting via https with Jenkins_URL as http breaks Favicon theme element Change By: Tobias Gruetzmacher Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203265.1574726114000.10477.1580661900265%40Atlassian.JIRA.
[JIRA] (JENKINS-60942) swarm plugin requires overall/read if not started with user/password
Title: Message Title Amit Dar created an issue Jenkins / JENKINS-60942 swarm plugin requires overall/read if not started with user/password Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin, swarm-plugin Created: 2020-02-02 16:35 Environment: jenkins 2.190.2 swarm plugin 3.17 matrix authorization plugin 2.5 Labels: swarm matrix matrix-project Priority: Major Reporter: Amit Dar Hi, I'm a heavy user of the Jenkins swarm plugin. we are using the plugin to enable users to connect their own machines to the server upon request, perform a check, and then disconnect it. since we don't require username/password to connect the machines, we had to enable the "anonymous/overall/read" in the global security security (we are using project based matrix authorization). what I recently discovered is that the jenkins server is not redirecting non-logged in users to the login page if they are trying to access the server using a link sent to them from a failed job execution. they get a 404 error instead. removing the anonymous/overall/read from global security - fixed that problem. however, now users are unable to connect their machines to the server unless they provide username and password. is there a way to make the swarm plugin NOT use the anonymous/overall/read from global security? maybe there is another way to make this combination work? this is a really weird behavior I can provide additional info upon request.
[JIRA] (JENKINS-60931) Incremental analysis
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60931 Incremental analysis Change By: Ulli Hafner Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204328.158049000.10473.1580661120109%40Atlassian.JIRA.
[JIRA] (JENKINS-60262) Jenkins AppCenter Plugin cannot used
Title: Message Title Mez Pahlan closed an issue as Won't Fix Insufficient information. Jenkins / JENKINS-60262 Jenkins AppCenter Plugin cannot used Change By: Mez Pahlan Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-i
[JIRA] (JENKINS-60275) Connecting via https with Jenkins_URL as http breaks Favicon theme element
Title: Message Title Tobias Gruetzmacher assigned an issue to Tobias Gruetzmacher Jenkins / JENKINS-60275 Connecting via https with Jenkins_URL as http breaks Favicon theme element Change By: Tobias Gruetzmacher Assignee: William Brode Tobias Gruetzmacher Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203265.1574726114000.10466.1580657700447%40Atlassian.JIRA.
[JIRA] (JENKINS-60275) Connecting via https with Jenkins_URL as http breaks Favicon theme element
Title: Message Title Tobias Gruetzmacher stopped work on JENKINS-60275 Change By: Tobias Gruetzmacher Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203265.1574726114000.10468.1580657700482%40Atlassian.JIRA.
[JIRA] (JENKINS-54278) Pipeline builds fail when cleanWs() in post stage
Title: Message Title
Nick Jones commented on JENKINS-54278
Re: Pipeline builds fail when cleanWs() in post stage
Simple repro:
pipeline {
agent none
options {
skipDefaultCheckout(true)
}
stages {
stage('Prepare') {
steps {
echo 'Preparing...'
}
}
}
post {
always {
cleanWs deleteDirs: true
}
}
}
This was deliberately designed without a pipeline-level agent – it is the skeleton of an implementation I'm working on that will have stage-level agents instead – and the cleanWs failed. It seems this should be more defensively coded so that cleanWs can cleanly exit (at most with a warning) if there simply isn't a workspace to be cleaned. I'll probably end up putting cleanWs in the post blocks for stages that do use agents (which would be a better place for that command anyway), but again, I'd still expect the above to be a no-op (with possibly a warning) rather than throwing an uncaught exception.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues
[JIRA] (JENKINS-60941) SUPER BOWL: Chiefs vs 49ers Live Stream
Title: Message Title Kristy ashton commented on JENKINS-60941 Re: SUPER BOWL: Chiefs vs 49ers Live Stream SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204342.1580641718000.10426.1580641800614%40Atlassian.JIRA.
[JIRA] (JENKINS-60941) SUPER BOWL: Chiefs vs 49ers Live Stream
Title: Message Title Kristy ashton commented on JENKINS-60941 Re: SUPER BOWL: Chiefs vs 49ers Live Stream SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204342.1580641718000.10428.1580641800642%40Atlassian.JIRA.
[JIRA] (JENKINS-60941) SUPER BOWL: Chiefs vs 49ers Live Stream
Title: Message Title Kristy ashton created an issue Jenkins / JENKINS-60941 SUPER BOWL: Chiefs vs 49ers Live Stream Issue Type: Story Assignee: Alexander A Components: s3-plugin Created: 2020-02-02 11:08 Environment: SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc Labels: plugin Priority: Trivial Reporter: Kristy ashton SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc SUPER BOWL: Chiefs vs 49ers Live Stream https://medium.com/@kristyk.ashton/super-bowl-chiefs-vs-49ers-live-stream-3a1631f4c1dc Add Comment
[JIRA] (JENKINS-28379) FingerFacets should be able to block the deletion of facets
Title: Message Title Sumit Sarin assigned an issue to Sumit Sarin Jenkins / JENKINS-28379 FingerFacets should be able to block the deletion of facets Change By: Sumit Sarin Assignee: Sumit Sarin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162815.1431532278000.10415.1580632740183%40Atlassian.JIRA.
[JIRA] (JENKINS-32143) Set git merge timeout
Title: Message Title Mark Waite updated JENKINS-32143 Jenkins / JENKINS-32143 Set git merge timeout Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167115.1450433966000.10413.1580632560480%40Atlassian.JIRA.
[JIRA] (JENKINS-32143) Set git merge timeout
Title: Message Title Mark Waite started work on JENKINS-32143 Change By: Mark Waite Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167115.1450433966000.10410.1580632560434%40Atlassian.JIRA.
[JIRA] (JENKINS-60940) Convert git client plugin tests from JUnit 3 to JUnit 4
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-60940 Convert git client plugin tests from JUnit 3 to JUnit 4 Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2020-02-02 08:31 Labels: newbie-friendly Priority: Minor Reporter: Mark Waite The git client plugin tests have started their transition process to retire the JUnit 3 based GitAPITestCase, CliGitAPIImplTest, and JGitAPIImplTest. They should be replaced by the parameterized GitClientTest. For each test in GitAPITestCase, CliGitAPIImplTest, and JGitAPIImplTest: If it is already tested in GitClientTest, delete the test from the JUnit 3 based tests If it is not already tested in GitClientTest, write a test in GitClientTest and delete the test from the JUnit 3 based tests This issue could be worked by multiple people concurrently, so long as they coordinate with one another on the specific tests they are converting.
