[JIRA] (JENKINS-32544) Commit message line breaks are stripped out in Changes page.
Title: Message Title Christopher Simons edited a comment on JENKINS-32544 Re: Commit message line breaks are stripped out in Changes page. Fixed in [PR #375|https://github.com/jenkinsci/git-plugin/pull/375] , though still unmerged 3 years later for unknown reasons .A screen shot of the fixed rendering is attached (file "32544-FIXED.png"): Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-40208) Grammar error on BlueOcean page
Title: Message Title Christopher Simons commented on JENKINS-40208 Re: Grammar error on BlueOcean page Fixed in PR #493. 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-40208) Grammar error on BlueOcean page
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-40208 Grammar error on BlueOcean page Change By: Christopher Simons Assignee: Christopher Simons 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] [core] (JENKINS-30431) Space in job name causes a spurious message from Maven
Title: Message Title Christopher Simons edited a comment on JENKINS-30431 Re: Space in job name causes a spurious message from Maven Could not reproduce. I ran a build under job name "bnt temp", both with and without the underlying project's directory name containing a space, and this warning did not appear in the job's console output (my HEAD is 5b4b66d8bcc4c3effae9329236edbfac2bccdd84 in branch 'master' ). This sounds like a Maven/POM issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [jacoco-plugin] (JENKINS-32717) Multiple class directories and source directories not parsed if there is a space after comma delimiter
Title: Message Title Christopher Simons commented on JENKINS-32717 Re: Multiple class directories and source directories not parsed if there is a space after comma delimiter Fixed in PR #68. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [jacoco-plugin] (JENKINS-32717) Multiple class directories and source directories not parsed if there is a space after comma delimiter
Title: Message Title Christopher Simons started work on JENKINS-32717 Change By: Christopher Simons Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [jacoco-plugin] (JENKINS-32721) configure which coverage metric to be shown in chart
Title: Message Title Christopher Simons created an issue Jenkins / JENKINS-32721 configure which coverage metric to be shown in chart Issue Type: Improvement Assignee: Unassigned Components: jacoco-plugin Created: 02/Feb/16 3:17 AM Priority: Minor Reporter: Christopher Simons Migrated from GitHub Issue #39; original description appears below, verbatim: It would be really nice if i could'e configure which coverage metric was shown in the chart, i.e. I'm interested only in line coverage percentage, so I want to see only that in the chart. Add Comment
[JIRA] [jacoco-plugin] (JENKINS-32720) report ignores coverage for groovy files
Title: Message Title Christopher Simons created an issue Jenkins / JENKINS-32720 report ignores coverage for groovy files Issue Type: New Feature Assignee: Unassigned Components: jacoco-plugin Created: 02/Feb/16 3:15 AM Priority: Minor Reporter: Christopher Simons Migrated from GitHub Issue #48; original description appears below, verbatim: jacoco plugin not showing coverage on groovy files. jacoco itself shows this coverage on its own report Add Comment
[JIRA] [jacoco-plugin] (JENKINS-32719) Ability to load properties from a file
Title: Message Title Christopher Simons created an issue Jenkins / JENKINS-32719 Ability to load properties from a file Issue Type: New Feature Assignee: Unassigned Components: jacoco-plugin Created: 02/Feb/16 3:13 AM Priority: Minor Reporter: Christopher Simons Migrated from GitHub Issue #52; original description appears below, verbatim: Currently the JaCoCo Jenkins plugin has 5 UI fields to set JaCoCo properties: exec files, class files, source files, inclusions. and exclusions. This causes an issue for us because it does not permit the use of dynamically generated inclusion/exclusion files and has overhead of maintaining job settings. It would be nice if there was an option to import properties from a file. Add Comment
[JIRA] [jacoco-plugin] (JENKINS-32718) Adaptive Build Health Thresholds
Title: Message Title Christopher Simons created an issue Jenkins / JENKINS-32718 Adaptive Build Health Thresholds Issue Type: New Feature Assignee: Unassigned Components: jacoco-plugin Created: 02/Feb/16 3:12 AM Priority: Minor Reporter: Christopher Simons Migrated from GitHub Issue #57; original description appears below, verbatim: This is a feature idea to support product teams adoption of test driven development (TDD). Right now it is a manual process to set the build failure thresholds, which is good in most cases. To support enforced improvement, these thresholds should be adaptive to the last successful build. That is, if the last successful build had a 81% test coverage, but the threshold was set to require only 80%, the threshold should automatically be increased. This is a special mode and must be selected as an option. The threshold increase is intended to only allow test coverage improvement while disallowing degradation. The manual process of setting these thresholds is not scalable for organizations as the jobs grow exponentially.
[JIRA] [jacoco-plugin] (JENKINS-32717) Multiple class directories and source directories not parsed if there is a space after comma delimiter
Title: Message Title Christopher Simons created an issue Jenkins / JENKINS-32717 Multiple class directories and source directories not parsed if there is a space after comma delimiter Issue Type: Bug Assignee: Christopher Simons Components: jacoco-plugin Created: 02/Feb/16 3:08 AM Priority: Minor Reporter: Christopher Simons Migrated from GitHub Issue #59; original description appears below, verbatim: This does not work: app/build/intermediates/classes/staging/debug, data/build/intermediates/classes/debug when changing to this: app/build/intermediates/classes/staging/debug,data/build/intermediates/classes/debug it works. Relates to this line https://github.com/jenkinsci/jacoco-plugin/blob/master/src/main/java/hudson/plugins/jacoco/JacocoPublisher.java#L272
[JIRA] [jacoco-plugin] (JENKINS-32528) Jenkins JaCoCo Plugin 2.0.0 shows HTML code in Coverage Trend
Title: Message Title Christopher Simons resolved as Duplicate This duplicates JENKINS-31751 . The problem has been fixed in version 2.0.1, which was released January 15, 2016. Jenkins / JENKINS-32528 Jenkins JaCoCo Plugin 2.0.0 shows HTML code in Coverage Trend Change By: Christopher Simons Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [jacoco-plugin] (JENKINS-32528) Jenkins JaCoCo Plugin 2.0.0 shows HTML code in Coverage Trend
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-32528 Jenkins JaCoCo Plugin 2.0.0 shows HTML code in Coverage Trend Change By: Christopher Simons Assignee: Ognjen Bubalo Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title
Christopher Simons updated an issue
Jenkins / JENKINS-32544
Commit message line breaks are not preserved in Changes page.
Change By:
Christopher Simons
If I have a commit that looks like this:{code}commit c8957035731691fd28df0871353950b99322b973Author: Christopher Simons < christopherleesimons person @ gmail company .com>Date: Wed Jan 20 21:49:45 2016 -0500[TICKET-123] fix widget ABC on page XYZPer the FOO spec, attribute 'bar' here cannot be empty. This changesuppresses the attribute in the case it is empty.This change fixes an automated test case, QUX, which is failing at thetime of this writing.{code}The commit message above appears, as of version 2.4.1, as follows in the Changes page:{code}[TICKET-123] fix widget ABC on page XYZPer the FOO spec, attribute 'bar' here cannot be empty. This changesuppresses the attribute in the case it is empty.This change fixes an automated test case, QUX, which is failing at thetime of this writing.{code}Screen shot attached (file "32544-BROKEN.png").
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title Christopher Simons edited a comment on JENKINS-32544 Re: Commit message line breaks are not preserved in Changes page. Fixed in [PR #375|https://github.com/jenkinsci/git-plugin/pull/375].A screen shot of the fixed rendering is attached (file " 2016 32544 - 01-20-git-plugin-commit-msg-whitespace-fixed FIXED .png"): Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-32544 Commit message line breaks are not preserved in Changes page. Change By: Christopher Simons Attachment: 2016-01-20-git-plugin-commit-msg-whitespace-fixed.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-32544 Commit message line breaks are not preserved in Changes page. Change By: Christopher Simons Attachment: 2016-01-20-git-plugin-commit-msg-whitespace-broken.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-32544 Commit message line breaks are not preserved in Changes page. Change By: Christopher Simons Attachment: 32544-FIXED.png Attachment: 32544-BROKEN.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title
Christopher Simons updated an issue
Jenkins / JENKINS-32544
Commit message line breaks are not preserved in Changes page.
Change By:
Christopher Simons
If I have a commit that looks like this:{code}commit c8957035731691fd28df0871353950b99322b973Author: Christopher Simons Date: Wed Jan 20 21:49:45 2016 -0500[TICKET-123] fix widget ABC on page XYZPer the FOO spec, attribute 'bar' here cannot be empty. This changesuppresses the attribute in the case it is empty.This change fixes an automated test case, QUX, which is failing at thetime of this writing.{code}The commit message above appears, as of version 2.4.1, as follows in the Changes page:{code}[TICKET-123] fix widget ABC on page XYZPer the FOO spec, attribute 'bar' here cannot be empty. This changesuppresses the attribute in the case it is empty.This change fixes an automated test case, QUX, which is failing at thetime of this writing.{code}Screen shot attached (file " 2016 32544 - 01-20-git-plugin-commit-msg-whitespace-broken BROKEN .png").
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-32544 Commit message line breaks are not preserved in Changes page. Change By: Christopher Simons Priority: Minor Trivial Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title
Christopher Simons updated an issue
Jenkins / JENKINS-32544
Commit message line breaks are not preserved in Changes page.
Change By:
Christopher Simons
If I have a commit that looks like this: {code} commit c8957035731691fd28df0871353950b99322b973Author: Christopher Simons Date: Wed Jan 20 21:49:45 2016 -0500[TICKET-123] fix widget ABC on page XYZPer the FOO spec, attribute 'bar' here cannot be empty. This changesuppresses the attribute in the case it is empty.This change fixes an automated test case, QUX, which is failing at thetime of this writing. {code} The commit message above appears, as of version 2.4.1, as follows in the Changes page: {code} [TICKET-123] fix widget ABC on page XYZPer the FOO spec, attribute 'bar' here cannot be empty. This changesuppresses the attribute in the case it is empty.This change fixes an automated test case, QUX, which is failing at thetime of this writing. {code} Screen shot attached (file "2016-01-20-git-plugin-commit-msg-whitespace-broken.png").
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title Christopher Simons edited a comment on JENKINS-32544 Re: Commit message line breaks are not preserved in Changes page. Fixed in [ PR #375| https://github.com/jenkinsci/git-plugin/pull/375 |PR #375 ].A screen shot of the fixed rendering is attached (file "2016-01-20-git-plugin-commit-msg-whitespace-fixed.png"): Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-32544 Commit message line breaks are not preserved in Changes page. Fixed in https://github.com/jenkinsci/git-plugin/pull/375. A screen shot of the fixed rendering is attached (file "2016-01-20-git-plugin-commit-msg-whitespace-fixed.png"): Change By: Christopher Simons Attachment: 2016-01-20-git-plugin-commit-msg-whitespace-fixed.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32544) Commit message line breaks are not preserved in Changes page.
Title: Message Title Christopher Simons created an issue Jenkins / JENKINS-32544 Commit message line breaks are not preserved in Changes page. Issue Type: Bug Assignee: Christopher Simons Attachments: 2016-01-20-git-plugin-commit-msg-whitespace-broken.png Components: git-plugin Created: 21/Jan/16 4:04 AM Priority: Minor Reporter: Christopher Simons If I have a commit that looks like this: commit c8957035731691fd28df0871353950b99322b973 Author: Christopher Simons Date: Wed Jan 20 21:49:45 2016 -0500 [TICKET-123] fix widget ABC on page XYZ Per the FOO spec, attribute 'bar' here cannot be empty. This change suppresses the attribute in the case it is empty. This change fixes an automated test case, QUX, which is failing at the time of this writing. The commit message above appears, as of version 2.4.1, as follows in the Changes page: [TICKET-123] fix widget ABC on page XYZ Per the FOO spec, attribute 'bar' here cannot be empty. This change suppresses the attribute in the case it is empty. This change fixes an automated test case, QUX, which is failing at the time of this writing.
[JIRA] [jacoco-plugin] (JENKINS-28636) Jacoco.exec can not be deleted
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-28636 Jacoco.exec can not be deleted Change By: Christopher Simons Hello,We have an issue where our Maven builds run for a little while, then at some point a new build will kick off and will not be able to clean the workspace because jacoco.exec is locked and can not be deleted. Our build user "BuildProp" is an administrator on this server and cannot remove the file.If I log in as myself, also and Admin, I can delete the file. However, once I navigate away from the folder and back, jacoco.exec will once again appear.This started about a week ago, I suspect is has something to do with us running builds on a slave node.Started by an SCM changeBuilding on master in workspace d:\jwsp\GIT.build1-maven3-developWiping out workspace first.java.nio.file.DirectoryNotEmptyException: d:\jwsp\GIT.build1-maven3-develop\abc\Apps\applications\Reconfirm\target at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.deleteFile(Util.java:247) at hudson.FilePath.deleteRecursive(FilePath.java:1202) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.deleteRecursive(FilePath.java:1193) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.deleteRecursive(FilePath.java:1193) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.deleteRecursive(FilePath.java:1193) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.deleteRecursive(FilePath.java:1193) at hudson.FilePath.deleteContentsRecursive(FilePath.java:1211) at hudson.FilePath.access$1100(FilePath.java:191) at hudson.FilePath$15.invoke(FilePath.java:1185) at hudson.FilePath$15.invoke(FilePath.java:1182) at hudson.FilePath.act(FilePath.java:989) at hudson.FilePath.act(FilePath.java:967) at hudson.FilePath.deleteContents(FilePath.java:1182) at hudson.plugins.git.extensions.impl.WipeWorkspace.beforeCheckout(WipeWorkspace.java:28) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1013) at hudson.scm.SCM.checkout(SCM.java:484) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at hudson.model.Run.execute(Run.java:1741) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)Archiving artifactsSkipping sonar analysis due to bad build status FAILURENotified Stash for commit with id e3f3c786a74c4be6eec44e5771650a8a0d1737cdEmail was triggered for: Failure - AnySending email for trigger: Failure - Any
[JIRA] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons edited a comment on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node (rather than editing), an error page is rendered with the message "Error: Slave called ‘foo’ already exists" and HTTP status 400. I'd propose reusing throwing this same error message upon trying to rename a node over another existing node.Fixed in [PR #1949|https://github.com/jenkinsci/jenkins/pull/1949]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons edited a comment on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node (rather than editing) , an error page is rendered with the message "Error: Slave called ‘foo’ already exists" and HTTP status 400. I'd propose rendering the reusing this same error message upon trying to rename a node over another existing node.Fixed in [PR #1949|https://github.com/jenkinsci/jenkins/pull/1949]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-29014) REST API Footer Link Doesn't Work from Subpages
Title: Message Title Christopher Simons edited a comment on JENKINS-29014 Re: REST API Footer Link Doesn't Work from Subpages I have submitted a fix for this: Fixed in [ Pull Request PR #1850|https://github.com/jenkinsci/jenkins/pull/1850]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a job is renamed to a string with a trailing space, it can be neither deleted nor renamed again (through the UI). Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory.This problem occurs only when renaming a job, and not when initially creating a job, because job names are trimmed when first created. It seems a sensible solution would be simply to trim the given job for rename operations as well, so that the name-setting behavior is consistent across create/update operations and inadvertent leading/trailing whitespace is removed before it can cause problems. I have submitted a fix for this: Fixed in [ Pull Request PR #1855|https://github.com/jenkinsci/jenkins/pull/1855]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31235) /createItem?mode=copy shouldn't require Content-Type header
Title: Message Title Christopher Simons edited a comment on JENKINS-31235 Re: /createItem?mode=copy shouldn't require Content-Type header I have submitted a fix for this: Fixed in [ Pull Request PR #1892|https://github.com/jenkinsci/jenkins/pull/1892]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30569) JS error triggered by collapsing build history
Title: Message Title Christopher Simons edited a comment on JENKINS-30569 Re: JS error triggered by collapsing build history I have submitted a fix for this: Fixed in [ Pull Request PR #1856|https://github.com/jenkinsci/jenkins/pull/1856]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons edited a comment on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node, an error page is rendered with the message "Error: Slave called ‘foo’ already exists" and HTTP status 400 . I'd propose rendering the same error message upon trying to rename a node over another existing node. Fixed in [PR #1949|https://github.com/jenkinsci/jenkins/pull/1949]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons started work on JENKINS-31321 Change By: Christopher Simons Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title
Christopher Simons updated an issue
Jenkins / JENKINS-31321
Renaming a node over another is possible and destroys both configurations
Change By:
Christopher Simons
When performing a node name rework, I was able to it is possible (partially?) overwrite a node with another one simply by renaming (which is a bit strange) but, apparently, the configuration of the "new" an existing node was broken so it was necessary to delete it and create it from scratch .Steps to reproduce:# Create a node named {{foo}}# Make {{foo}} node as temporarily offline# Create another node named {{bar}}# Go to the {{bar}} node configuration# Rename it to {{foo}} and press _Save_Expected results:* A prompt asking if that's what the user really intends: An error message. ** _Yes_ would be the equivalent to deleting {{foo}} node and replacing its configuration contents with the one from {{bar}} (now named {{foo}}) ** _No_ would cause the operation to be aborted Actual results:* Node {{bar}} replaces {{foo}} without any notice* Things start to behave wacky: build starts to fail without a reason (see attached edited log, {{Jenkins-BuildBreakageAfterNodeRename.txt}} Disclaimer: I wasn't able to validate the exact steps to reproduce procedure *nor* if making the node temporarily offline is really necessary as a Jenkins test instance was not available (procedure was compiled from memory).Workaround:* Delete a node before renaming another one over it* If such an undesired node rename was made, delete and reconfigure the affected node againPriority set to "major" as loss of information (node configuration) is involved. Build breakage (until the problem is understood and fixed) is also triggered, although that's not as serious and could be considered "minor".
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons edited a comment on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node, an error page is rendered with the message "Error: Slave called ‘foo’ already exists". I'd propose rendering the same error message is rendered upon trying to rename a node over another existing node. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons commented on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node, an error page is rendered with the message "Error: Slave called ‘foo’ already exists". I'd propose rendering the same error message is rendered upon trying to rename a node over another existing node. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-31321 Renaming a node over another is possible and destroys both configurations Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31511) Recent (since 1.628) bug introduced into pluginManager filter UI
Title: Message Title
Christopher Simons edited a comment on JENKINS-31511
Re: Recent (since 1.628) bug introduced into pluginManager filter UI
Verified bug exists on from Chrome in 46.0.2490.80 ( Linux 64-bit) on Linux against repository tag 'jenkins-1.638' but does not exist on tag 'jenkins-1.628'.When testing, note that the search does not seem to be broken on the default tab, but is broken on the "Installed" tab. When entering a search term, the list results do seem to change sometimes, but more results are returned than are warranted by the search term.Results of git-bisect debugging:{code}3b5424e507be2e59eabfd3f55ce16cd2b58a6195 is the first bad commitcommit 3b5424e507be2e59eabfd3f55ce16cd2b58a6195Author: tfennelly Date: Fri Sep 25 12:22:46 2015 +0100Only allow disable or uninstall when all dependants or dependencies are disabled/enabled{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-31511) Recent (since 1.628) bug introduced into pluginManager filter UI
Title: Message Title Christopher Simons edited a comment on JENKINS-31511 Re: Recent (since 1.628) bug introduced into pluginManager filter UI [~danielbeck] Initially I planned to fix this but have since gotten sidetracked by other demands. I've unassigned this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31511) Recent (since 1.628) bug introduced into pluginManager filter UI
Title: Message Title Christopher Simons edited a comment on JENKINS-31511 Re: Recent (since 1.628) bug introduced into pluginManager filter UI [~danielbeck] Initially I was planning on fixing planned to fix this but have since gotten sidetracked by other demands. I've unassigned this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31395) On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page
Title: Message Title Christopher Simons updated JENKINS-31395 Jenkins / JENKINS-31395 On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page Change By: Christopher Simons Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31395) On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page
Title: Message Title Christopher Simons assigned an issue to Unassigned Jenkins / JENKINS-31395 On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31511) Recent (since 1.628) bug introduced into pluginManager filter UI
Title: Message Title Christopher Simons assigned an issue to Unassigned Daniel Beck Initially I was planning on fixing this but have since gotten sidetracked by other demands. I've unassigned this. Jenkins / JENKINS-31511 Recent (since 1.628) bug introduced into pluginManager filter UI Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title Christopher Simons assigned an issue to Unassigned Jenkins / JENKINS-30852 404 Error saving a View with non URL-safe characters Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title Christopher Simons stopped work on JENKINS-30852 Change By: Christopher Simons Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31511) Recent (since 1.628) bug introduced into pluginManager filter UI
Title: Message Title Christopher Simons stopped work on JENKINS-31511 Change By: Christopher Simons Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31511) Recent (since 1.628) bug introduced into pluginManager filter UI
Title: Message Title Christopher Simons commented on JENKINS-31511 Re: Recent (since 1.628) bug introduced into pluginManager filter UI Verified bug exists on Chrome in 46.0.2490.80 (64-bit) on Linux against repository tag 'jenkins-1.638' but does not exist on tag 'jenkins-1.628'. When testing, note that the search does not seem to be broken on the default tab, but is broken on the "Installed" tab. When entering a search term, the list results do seem to change sometimes, but more results are returned than are warranted by the search term. Results of git-bisect debugging: 3b5424e507be2e59eabfd3f55ce16cd2b58a6195 is the first bad commit commit 3b5424e507be2e59eabfd3f55ce16cd2b58a6195 Author: tfennelly Date: Fri Sep 25 12:22:46 2015 +0100 Only allow disable or uninstall when all dependants or dependencies are disabled/enabled Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31511) Recent (since 1.628) bug introduced into pluginManager filter UI
Title: Message Title Christopher Simons started work on JENKINS-31511 Change By: Christopher Simons Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31511) Recent (since 1.628) bug introduced into pluginManager filter UI
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-31511 Recent (since 1.628) bug introduced into pluginManager filter UI Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31395) On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page
Title: Message Title Christopher Simons resolved as Fixed I have submitted a fix for this: Pull Request #1905. Jenkins / JENKINS-31395 On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page Change By: Christopher Simons Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31395) On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page
Title: Message Title Christopher Simons started work on JENKINS-31395 Change By: Christopher Simons Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31395) On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-31395 On the jenkins (LTS 1.625.1) homepage the footer scrolls up with the rest of the page Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title
Christopher Simons edited a comment on JENKINS-30852
Re: 404 Error saving a View with non URL-safe characters
Verified.According to my testing, the problem manifests when there is a space before the "»" character regardless of whether there is a space afterward. Also, note that the rename succeeds, but the redirect afterward is what fails; rather than redirecting to "ABC%20»%20DEF" the application redirects to "ABC%20%BB%20DEF", and %BB does not decode back to "»". Going to the application home page manually and then navigating to the renamed job succeeds, so this The correct encoding is "ABC%20%C2%BB%20DEF".This appears to be an encoding problem during the redirection that happens after saving the job configuration. The following can be observed error in the application log about the same time the redirect happens:{code}WARNING: Failed UTF-8 decode for request path upstream StaplerResponse.sendRedirect2(). Interestingly , trying ISO-8859-1{code} the encoding error also seems present in hudson.Util.encode().
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title
Christopher Simons edited a comment on JENKINS-30852
Re: 404 Error saving a View with non URL-safe characters
Verified.According to my testing, the problem manifests when there is a space before the "»" character regardless of whether there is a space afterward. Also, note that the rename succeeds, but the redirect afterward is what fails; rather than redirecting to "ABC%20»%20DEF" the application redirects to "ABC%20%BB%20DEF", and %BB does not decode back to "»". Going to the application home page manually and then navigating to the renamed job succeeds, so this appears to be an encoding problem during the redirection that happens after saving the job configuration. The following can be observed in the application log about the same time the redirect happens: {code} WARNING: Failed UTF-8 decode for request path, trying ISO-8859-1 {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title Christopher Simons edited a comment on JENKINS-30852 Re: 404 Error saving a View with non URL-safe characters Verified.According to my testing, the problem manifests when there is a space before the "»" character regardless of whether there is a space afterward. Also, note that the rename succeeds, but the redirect afterward is what fails; rather than redirecting to "ABC%20»%20DEF" the application redirects to "ABC%20%BB%20DEF", and %BB does not decode back to "»". Going to the application home page manually and then navigating to the renamed job succeeds, and no errors are seen in the log, so I suspect this is merely appears to be an encoding problem during the redirection that happens upon after saving the job configuration. The following can be observed in the application log about the same time the redirect happens:WARNING: Failed UTF-8 decode for request path, trying ISO-8859-1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title Christopher Simons edited a comment on JENKINS-30852 Re: 404 Error saving a View with non URL-safe characters Verified.According to my testing, the problem manifests when there is a space before the "»" character regardless of whether there is a space afterward. Also, note that the rename succeeds, but the redirect afterward is what fails; rather than redirecting to "ABC%20»%20DEF" the application redirects to "ABC%20%BB%20DEF", and %BB does not decode back to "»". Going to the application home page manually and then navigating to the renamed job succeeds, and no errors are seen in the log, so I suspect this is merely an encoding problem during the redirection that happens upon saving the job configuration . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title Christopher Simons edited a comment on JENKINS-30852 Re: 404 Error saving a View with non URL-safe characters Verified.According to my testing, the problem manifests when there is a space before the "»" character regardless of whether there is a space after afterward . Also, note that the rename succeeds, but the redirect afterward is what fails; rather than redirecting to "ABC%20»%20DEF" the application redirects to "ABC%20%BB%20DEF", and %BB does not decode back to "»". Correcting the URL or navigating back Going to the root of the application home page manually and then navigating to the renamed job manually succeeds, and no errors are seen in the log, so I suspect this is merely an encoding problem during the redirection. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title Christopher Simons commented on JENKINS-30852 Re: 404 Error saving a View with non URL-safe characters Verified. According to my testing, the problem manifests when there is a space before the "»" character regardless of whether there is a space after. Also, note that the rename succeeds, but the redirect afterward is what fails; rather than redirecting to "ABC%20»%20DEF" the application redirects to "ABC%20%BB%20DEF", and %BB does not decode back to "»". Correcting the URL or navigating back to the root of the application and then navigating to the job manually succeeds, and no errors are seen in the log, so I suspect this is merely an encoding problem during the redirection. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title Christopher Simons started work on JENKINS-30852 Change By: Christopher Simons Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30833) newline character is missing after import the config.xml
Title: Message Title Christopher Simons edited a comment on JENKINS-30833 Re: newline character is missing after import the config.xml Using curl -d does not preserve newlines in the input stream, so when following the steps above the newlines are stripped before the data reaches the application. In order to preserve newlines in the input stream, curl's --data-binary should be used rather than -d. I have verified the problem using -d and its correction using --data-binary. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30833) newline character is missing after import the config.xml
Title: Message Title Christopher Simons resolved as Not A Defect Using curl -d does not preserve newlines in the input stream, so when following the steps above the newlines are stripped before the data reaches the application. In order to preserve newlines in the input stream, curl's --data-binary should be used rather than -d. Jenkins / JENKINS-30833 newline character is missing after import the config.xml Change By: Christopher Simons Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30833) newline character is missing after import the config.xml
Title: Message Title
Christopher Simons updated an issue
Jenkins / JENKINS-30833
newline character is missing after import the config.xml
Change By:
Christopher Simons
I did some google search for how to import/export Jenkins jobs. Basically, I follow their suggestion. First, export the config.xml, and then import back to the Jenkins with a different Jenkins job name.After importing the config.xml, the newline characters inside the "Execute Shell" are removed.For example, I haveecho AAAecho BBBinside the "Execute Shell". {code:java}// Some comments herepublic String getFoo(){return foo;}{code} After the import, it became echoAAAechoBBBTherefore, I need to manually update the content of "Execute Shell".I had checked the content of config.xml. It looks fine; the newline character is intact.Following is my steps to repro this issue: 1) {code} curl http://:@/job/testbackup/config.xml {code} where testbackup is my Jenkins job 2) {code} cat config.xml | curl -X POST 'http://NEW_JENKINS/createItem?name=testbackup2' --header "Content-Type: application/xml" -d @- {code} where testbackup2 is my new Jenkins job namethanks
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-30833) newline character is missing after import the config.xml
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-30833 newline character is missing after import the config.xml Change By: Christopher Simons I did some google search for how to import/export Jenkins jobs. Basically, I follow their suggestion. First, export the config.xml, and then import back to the Jenkins with a different Jenkins job name.After importing the config.xml, the newline characters inside the "Execute Shell" are removed.For example, I haveecho AAAecho BBBinside the "Execute Shell".After the import, it became echoAAAechoBBBTherefore, I need to manually update the content of "Execute Shell".I had checked the content of config.xml. It looks fine; the newline character is intact.Following is my steps to repro this issue:1) curl http://:@/job/testbackup/config.xmlwhere testbackup is my Jenkins job2) cat config.xml | curl -X POST 'http://NEW_JENKINS/createItem?name=testbackup2' --header "Content-Type: application/xml" -d @- where testbackup2 is my new Jenkins job namethanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30833) newline character is missing after import the config.xml
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-30833 newline character is missing after import the config.xml Change By: Christopher Simons I did some google search for how to import/export Jenkins jobs. Basically, I follow their suggestion. First, export the config.xml, and then import back to the Jenkins with a different Jenkins job name.After importing the config.xml, the newline characters inside the "Execute Shell" are removed.For example, I haveecho AAAecho BBBinside the "Execute Shell".After the import, it became echoAAAechoBBBTherefore, I need to manually update the content of "Execute Shell".I had checked the content of config.xml. It looks fine; the newline character is intact.Following is my steps to repro this issue:1) curl http://:@/job/testbackup/config.xmlwhere testbackup is my Jenkins job2) cat config.xml | curl -X POST 'http://NEW_JENKINS/createItem?name=testbackup2' --header "Content-Type: application/xml" -d - @ - where testbackup2 is my new Jenkins job namethanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30833) newline character is missing after import the config.xml
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-30833 newline character is missing after import the config.xml Change By: Christopher Simons Environment: OS: CentOS Linux release 7.1.1503Jenkins version: 1.625Browser: Fireofx Firefox ESR 38.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31235) /createItem?mode=copy shouldn't require Content-Type header
Title: Message Title Christopher Simons resolved as Fixed I have submitted a fix for this: Pull Request #1892. Jenkins / JENKINS-31235 /createItem?mode=copy shouldn't require Content-Type header Change By: Christopher Simons Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31235) /createItem?mode=copy shouldn't require Content-Type header
Title: Message Title Christopher Simons stopped work on JENKINS-31235 Change By: Christopher Simons Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31235) /createItem?mode=copy shouldn't require Content-Type header
Title: Message Title Christopher Simons started work on JENKINS-31235 Change By: Christopher Simons Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31235) /createItem?mode=copy shouldn't require Content-Type header
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-31235 /createItem?mode=copy shouldn't require Content-Type header Change By: Christopher Simons Copying a job using the /createItem?mode=copy API requires the use of a Content-Type HTTP header, which doesn't make sense for the 'copy' operation as the input data is being sourced internally and not being supplied in the HTTP request (there is no user-supplied 'content' whose type needs describing in this case) .At the time of this writing, omitting the Content-Type header results in an error message, forcing the user to supply any arbitrary Content-Type in order to allow the request to succeed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31235) /createItem?mode=copy shouldn't require Content-Type header
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-31235 /createItem?mode=copy shouldn't require Content-Type header Change By: Christopher Simons Summary: /createItem?mode=copy shouldn't require content Content - type Type header Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-31235) /createItem?mode=copy shouldn't require content-type header
Title: Message Title Christopher Simons created an issue Jenkins / JENKINS-31235 /createItem?mode=copy shouldn't require content-type header Issue Type: Bug Assignee: Christopher Simons Components: core Created: 28/Oct/15 4:20 PM Priority: Minor Reporter: Christopher Simons Copying a job using the /createItem?mode=copy API requires the use of a Content-Type HTTP header, which doesn't make sense for the 'copy' operation as the input data is being sourced internally and not being supplied in the HTTP request. At the time of this writing, omitting the Content-Type header results in an error message, forcing the user to supply any arbitrary Content-Type in order to allow the request to succeed. Add Comment
[JIRA] [core] (JENKINS-30852) 404 Error saving a View with non URL-safe characters
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-30852 404 Error saving a View with non URL-safe characters Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30833) newline character is missing after import the config.xml
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-30833 newline character is missing after import the config.xml Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30660) Add a configurable display name to views
Title: Message Title Christopher Simons assigned an issue to Unassigned Jenkins / JENKINS-30660 Add a configurable display name to views Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons resolved as Fixed Jenkins / JENKINS-30502 Unable to delete project with trailing whitespace in name Change By: Christopher Simons Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30660) Add a configurable display name to views
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-30660 Add a configurable display name to views Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30569) JS error triggered by collapsing build history
Title: Message Title Christopher Simons resolved as Fixed Jenkins / JENKINS-30569 JS error triggered by collapsing build history Change By: Christopher Simons Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30431) Space in job name causes a spurious message from Maven
Title: Message Title Christopher Simons commented on JENKINS-30431 Re: Space in job name causes a spurious message from Maven Could not reproduce. I ran a build under job name "bnt temp", both with and without the underlying project's directory name containing a space, and this warning did not appear in the job's console output (my HEAD is 5b4b66d8bcc4c3effae9329236edbfac2bccdd84 in branch 'master'). This sounds like a Maven/POM issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30317) api should return the queue url in location header for parameterized builds
Title: Message Title
Christopher Simons edited a comment on JENKINS-30317
Re: api should return the queue url in location header for parameterized builds
Could not reproduce. Here is what I get when I post a request for a parameterized build (my HEAD is 5b4b66d8bcc4c3effae9329236edbfac2bccdd84 in master branch 'master' ):{code}$ curl -i -X POST http://localhost:8080/job/bnt_02/buildWithParameters?profile="" />HTTP/1.1 201 CreatedX-Content-Type-Options: nosniffLocation: http://localhost:8080/queue/item/55/Content-Length: 0Server: Jetty(winstone-2.8)${code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-30317) api should return the queue url in location header for parameterized builds
Title: Message Title
Christopher Simons edited a comment on JENKINS-30317
Re: api should return the queue url in location header for parameterized builds
Could not reproduce. Here is what I get when I post a request for a parameterized build (my HEAD is 5b4b66d8bcc4c3effae9329236edbfac2bccdd84 in master branch):{code}$ curl - i - X POST http://localhost:8080/job/bnt_02/buildWithParameters?profile="" />HTTP/1.1 201 CreatedX-Content-Type-Options: nosniffLocation: http://localhost:8080/queue/item/55/Content-Length: 0Server: Jetty(winstone-2.8)${code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-30317) api should return the queue url in location header for parameterized builds
Title: Message Title
Christopher Simons edited a comment on JENKINS-30317
Re: api should return the queue url in location header for parameterized builds
Could not reproduce. Here is what I get when I post a request for a parameterized build (my HEAD is 5b4b66d8bcc4c3effae9329236edbfac2bccdd84 in master branch) :{code}$ curl -X POST http://localhost:8080/job/bnt_02/buildWithParameters?profile="" />HTTP/1.1 201 CreatedX-Content-Type-Options: nosniffLocation: http://localhost:8080/queue/item/55/Content-Length: 0Server: Jetty(winstone-2.8)${code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [core] (JENKINS-30317) api should return the queue url in location header for parameterized builds
Title: Message Title Christopher Simons commented on JENKINS-30317 Re: api should return the queue url in location header for parameterized builds Could not reproduce. Here is what I get when I post a request for a parameterized build: $ curl -X POST http://localhost:8080/job/bnt_02/buildWithParameters?profile="" HTTP/1.1 201 Created X-Content-Type-Options: nosniff Location: http://localhost:8080/queue/item/55/ Content-Length: 0 Server: Jetty(winstone-2.8) $ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30660) Add a configurable display name to views
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-30660 Add a configurable display name to views Change By: Christopher Simons Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30569) JS error triggered by collapsing build history
Title: Message Title Christopher Simons commented on JENKINS-30569 Re: JS error triggered by collapsing build history I have submitted a fix for this: Pull Request #1856. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30569) JS error triggered by collapsing build history
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-30569 JS error triggered by collapsing build history Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a job is renamed to a string with a trailing space, it can be neither deleted nor renamed again (through the UI). Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory.This problem occurs only when renaming a job, and not when initially creating a job, because job names are trimmed when first created. It seems a sensible solution would be simply to trim the given job for rename operations as well, so that the name-setting behavior is consistent across create/update operations and inadvertent leading/trailing whitespace is removed before it can cause problems.I have submitted a fix for this: [ Pull Request #1855| https://github.com/jenkinsci/jenkins/pull/1855 |Pull Request #1855 ]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a job is renamed to a string with a trailing space, it can be neither deleted nor renamed again (through the UI). Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory.This problem occurs only when renaming a job, and not when initially creating a job, because job names are trimmed when first created. It seems a sensible solution would be simply to trim the given job for rename operations as well, so that the name-setting behavior is consistent across create/update operations and inadvertent leading/trailing whitespace is removed before it can cause problems. I have submitted a fix for this: [https://github.com/jenkinsci/jenkins/pull/1855|Pull Request #1855]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons stopped work on JENKINS-30502 Change By: Christopher Simons Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a job is renamed to a string with a trailing space, it can be neither deleted nor renamed again (through the UI) . Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory.This problem occurs only when renaming a job, and not when initially creating a job, because job names are trimmed when first created. It seems a sensible solution would be simply to trim the given job for rename operations as well, so that the name-setting behavior is consistent across create/update operations and inadvertent leading/trailing whitespace is removed before it can cause problems. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons started work on JENKINS-30502 Change By: Christopher Simons Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a job is renamed to a string with a trailing space, it can be neither deleted nor renamed again. Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory.This problem occurs only when renaming a job, and not when initially creating a job, because job names are trimmed when first created. It seems a sensible solution would be simply to trim the given job for rename operations as well, so that the naming name-setting behavior is consistent across create/update operations and inadvertent leading/trailing whitespace is removed before it can cause problems. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a job is renamed to a string with a trailing space, it can be neither deleted nor renamed again. Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory.This problem occurs only when renaming a job, and not when initially creating a job, because job names are trimmed when first created. It seems a sensible solution would be simply to trim the given job for rename operations as well, so that the naming behavior is consistent and inadvertent leading/trailing whitespace is removed before it can cause problems. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a job is renamed to a string with a trailing space, it can be neither deleted nor renamed again. Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory.This problem occurs only when renaming a job, and not when initially creating a job, because upon creation the job name is names are trimmed when first created . It seems a sensible solution would be simply to trim the given job for rename operations the same way as is done for creation operations well , so that inadvertent leading/trailing whitespace is removed before it can cause problems. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a project is renamed to a string with a trailing space, it can be neither deleted nor renamed again. Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory. This problem occurs only when renaming a job, and not when initially creating a job, because upon creation the job name is trimmed. It seems a sensible solution would be simply to trim the given job name before saving for rename operations the same way as is done for creation operations, so that inadvertent leading/trailing whitespace is removed before it can cause problems. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a project job is renamed to a string with a trailing space, it can be neither deleted nor renamed again. Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory.This problem occurs only when renaming a job, and not when initially creating a job, because upon creation the job name is trimmed. It seems a sensible solution would be simply to trim the given job for rename operations the same way as is done for creation operations, so that inadvertent leading/trailing whitespace is removed before it can cause problems. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons edited a comment on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a project is renamed to a string with a trailing space, it can be neither deleted nor renamed again. Part of the problem is that the initial rename (to a string with a trailing space) fails to rename the job directory. It seems a sensible solution would be simply to trim the job name before saving so that inadvertent leading/trailing whitespace is removed before it can cause problems. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons commented on JENKINS-30502 Re: Unable to delete project with trailing whitespace in name I've verified that once a project is renamed to a string with a trailing space, it can be neither deleted nor renamed again. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-30502) Unable to delete project with trailing whitespace in name
Title: Message Title Christopher Simons assigned an issue to Christopher Simons Jenkins / JENKINS-30502 Unable to delete project with trailing whitespace in name Change By: Christopher Simons Assignee: Christopher Simons Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-29014) REST API Footer Link Doesn't Work from Subpages
Title: Message Title Christopher Simons edited a comment on JENKINS-29014 Re: REST API Footer Link Doesn't Work from Subpages I have submitted a fix for this: [Pull Request #1850 | https://github.com/jenkinsci/jenkins/pull/1850]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-29014) REST API Footer Link Doesn't Work from Subpages
Title: Message Title Christopher Simons updated an issue Jenkins / JENKINS-29014 REST API Footer Link Doesn't Work from Subpages Change By: Christopher Simons Summary: REST api link doesn API Footer Link Doesn 't work Work from sub pages Subpages Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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.
