[JIRA] (JENKINS-40352) Duplicate changesets in pipeline jobs
Title: Message Title Pratith Kanagaraj updated an issue Jenkins / JENKINS-40352 Duplicate changesets in pipeline jobs Change By: Pratith Kanagaraj Attachment: duplicates.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-40352) Duplicate changesets in pipeline jobs
Title: Message Title Pratith Kanagaraj updated an issue Jenkins / JENKINS-40352 Duplicate changesets in pipeline jobs Change By: Pratith Kanagaraj Attachment: duplicates.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-40352) Duplicate changesets in pipeline jobs
Title: Message Title Pratith Kanagaraj created an issue Jenkins / JENKINS-40352 Duplicate changesets in pipeline jobs Issue Type: Bug Assignee: Mark Waite Attachments: duplicates.PNG Components: git-plugin, pipeline Created: 2016/Dec/09 9:40 PM Labels: pipeline Priority: Minor Reporter: Pratith Kanagaraj In pipeline/workflow jobs, we get duplicate changesets in the JSON build data and also see duplicates in the UI as shown in the attachment below. Git plugin version is 2.5.1. Is this a known issue and been fixed in later versions? Add Comment
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Pratith Kanagaraj commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins Was this resolved? Because I am still facing the 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-39487) SVN changesets duplicated when using multibranch pipeline
Title: Message Title Pratith Kanagaraj commented on JENKINS-39487 Re: SVN changesets duplicated when using multibranch pipeline Happens in git as well. 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-39391) Support for from index greater than the actual array size during pagination
Title: Message Title
Pratith Kanagaraj updated an issue
Jenkins / JENKINS-39391
Support for from index greater than the actual array size during pagination
Change By:
Pratith Kanagaraj
In range notation during pagination, if the from index exceeds the actual array size, Jenkins throws an exception. Can't it return an empty response or something similar instead , so that we know when to stop ?For example, suppose a Jenkins server has 10840 jobs and we want to get all the jobs' details. We keep incrementing the lower bound according to page size (say 1000). Eventually, we hit: http://server/api/json?tree=jobs[name,url,builds[number,url]]{11000,12000} which throws the following exception:Caused by: java.lang.IllegalArgumentException: fromIndex(11000) > toIndex(10841)
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
[JIRA] (JENKINS-39391) Support for from index greater than the actual array size during pagination
Title: Message Title
Pratith Kanagaraj created an issue
Jenkins / JENKINS-39391
Support for from index greater than the actual array size during pagination
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2016/Oct/31 7:54 PM
Priority:
Major
Reporter:
Pratith Kanagaraj
In range notation during pagination, if the from index exceeds the actual array size, Jenkins throws an exception. Can't it return an empty response or something similar instead? For example, suppose a Jenkins server has 10840 jobs and we want to get all the jobs' details. We keep incrementing the lower bound according to page size (say 1000). Eventually, we hit: http://server/api/json?tree=jobs[name,url,builds[number,url]] {11000,12000} which throws the following exception: Caused by: java.lang.IllegalArgumentException: fromIndex(11000) > toIndex(10841)
Add Comment
[JIRA] (JENKINS-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title Pratith Kanagaraj commented on JENKINS-38800 Re: remoteUrls are unordered in build data JSON when multiple git repositories are configured I am not sure either why someone would configure multiple git repositories in the Jenkins Git plugin, but I am writing a tool which gathers information from the build data json and associates the branch information with the corresponding repository url. Since the Git plugin allows the user to configure multiple repositories, I am trying to get the tool to handle it, but the remoteUrls being unordered makes it impossible to do so unless we assume the repositories are exact copies each having the same branches. It won't work even in the case where one repository is a superset of another (it could have additional branches). 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-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title
Pratith Kanagaraj updated an issue
Jenkins / JENKINS-38800
remoteUrls are unordered in build data JSON when multiple git repositories are configured
Change By:
Pratith Kanagaraj
When multiple Git repositories are added to the git plugin (not Multiple SCM plugin), the remoteUrls in the build data JSON are unordered (different from the order in which they were configured in the Jenkins job). This is because the remoteUrls are stored in a HashSet in BuildData.java. We can instead store them in a LinkedHashSet and preserve the order.This is needed so that we can associate the branch built, origin[x] (where x is the repository index) in lastBuiltRevision with the appropriate repository URL for which there is no provision right now when there are multiple repositories.{ quote}{ "buildsByBranchName" : {"origin/master" : {"buildNumber" : 1813,"buildResult" : null,"revision" : {"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6","branch" : [{ "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "name" : "origin/master" }]}},"origin/mri" : {"buildNumber" : 50,"buildResult" : null,"revision" : {"SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513","branch" : [{ "SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513", "name" : "origin/mri" }]}}},"lastBuiltRevision" : {"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6","branch" : [{ "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "name" : "origin1/master" }],"remoteUrls" : ["https://github.com/repo1.git","https://github.com/repo2.git",]} ,{quote}
Add Comment
[JIRA] (JENKINS-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title Pratith Kanagaraj commented on JENKINS-38800 Re: remoteUrls are unordered in build data JSON when multiple git repositories are configured Created pull 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-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title
Pratith Kanagaraj updated an issue
Jenkins / JENKINS-38800
remoteUrls are unordered in build data JSON when multiple git repositories are configured
Change By:
Pratith Kanagaraj
When multiple Git repositories are added to the git plugin (not Multiple SCM plugin), the remoteUrls in the build data JSON are unordered (different from the order in which they were configured in the Jenkins job). This is because the remoteUrls are stored in a HashSet in BuildData.java. We can instead store them in a LinkedHashSet and preserve the order.This is needed so that we can associate the branch built, origin[x] (where x is the repository index) in lastBuiltRevision with the appropriate repository URL for which there is no provision right now when there are multiple repositories.{ quote}{ "buildsByBranchName" : {"origin/master" : {"buildNumber" : 1813,"buildResult" : null,"revision" : {"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6","branch" : [{ "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "name" : "origin/master" }]}},"origin/mri" : {"buildNumber" : 50,"buildResult" : null,"revision" : {"SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513","branch" : [{ "SHA1" : "f68f612f42908af792e831613deb4b6fe43ff513", "name" : "origin/mri" }]}}},"lastBuiltRevision" : {"SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6","branch" : [{ "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "name" : "origin1/master" }],"remoteUrls" : ["https://github.com/repo1.git","https://github.com/repo2.git",]}, {quote}
Add Comment
[JIRA] (JENKINS-38800) remoteUrls are unordered in build data JSON when multiple git repositories are configured
Title: Message Title
Pratith Kanagaraj created an issue
Jenkins / JENKINS-38800
remoteUrls are unordered in build data JSON when multiple git repositories are configured
Issue Type:
Improvement
Assignee:
Mark Waite
Components:
git-plugin
Created:
2016/Oct/06 8:37 PM
Environment:
Operating System: Jenkins server running on Windows 7 Enterprise SP1 (64-bit), slave node running on Ubuntu 3.13.0-85-generic (64-bit) VM launched via SSH. Java 1.8 Jenkins ver. 2.7.1, Git plugin ver. 3.0.0 Browser: Google Chrome Version 53.0.2785.116 m (64-bit)
Labels:
git-plugin remoteUrls
Priority:
Major
Reporter:
Pratith Kanagaraj
When multiple Git repositories are added to the git plugin (not Multiple SCM plugin), the remoteUrls in the build data JSON are unordered (different from the order in which they were configured in the Jenkins job). This is because the remoteUrls are stored in a HashSet in BuildData.java. We can instead store them in a LinkedHashSet and preserve the order. This is needed so that we can associate the branch built, origin[x] (where x is the repository index) in lastBuiltRevision with the appropriate repository URL for which there is no provision right now when there are multiple repositories. { "buildsByBranchName" : { "origin/master" : { "buildNumber" : 1813, "buildResult" : null, "revision" : { "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "branch" : [ { "SHA1" : "a0b422c02d45c71ca6e5317eb3aa6026d0f4ada6", "name" : "origin/master" } ] } }, "origin/mri" : { "buildNumber" : 50, "buildResult" : null, "revision" : { "SHA1" :
