[JIRA] (JENKINS-58534) Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)
Title: Message Title slav dok created an issue Jenkins / JENKINS-58534 Impossible to access promotion's console output (navigation is broken from links and breadcrumbs) Issue Type: Bug Assignee: Oleg Nenashev Components: promoted-builds-plugin Created: 2019-07-17 16:34 Environment: Jenkins LTS version: 2.176.1 Promoted Builds version: 3.3 openjdk version: 1.8.0_161 CentOS version: 7.2.1511 Labels: plugin promoted-builds breadcrumb navigation consoleoutput Priority: Major Reporter: slav dok This works fine in Promoted Builds version 3.2, but breaks once you upgrade to 3.3 Usually, you can access the promotion's console output by: Selecting Build job (for example "Build_Job") Selecting Build Number (for example "#5") Clicking Promotion Status link Picking a promotion from the list (for example "Promo1 > #2") This will provide navigation breadcrumbs like: Jenkins > Build_Job > #5 > Promotion Status > #2 At the same time, the URL would be like: server_url:port/job/Build_Job/5/promotion/Promo1/promotionBuild/2/console After upgrading to 3.3 The URL remains same, but the UI loops back to the
[JIRA] [run-condition-extras-plugin] (JENKINS-26005) Run condition trigger for Email-ext does not retain Send To information on Save/Apply
slav dok updated JENKINS-26005 Run condition trigger for Email-ext does not retain Send To information on Save/Apply Change By: slav dok (15/Dec/14 2:55 PM) Summary: Runconditiontrigger forEmail-ext doesnotretainSendToinformationonSave/Apply This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-26005) Run condition trigger does not retain Send To information on Save/Apply
slav dok created JENKINS-26005 Run condition trigger does not retain Send To information on Save/Apply Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 10/Dec/14 6:33 PM Description: Create new "Freestyle Project" Choose "Editable Email Notification" from "Post-build Actions" Click "Advanced Settings..." Click "Add Trigger" Select "Run condition trigger" Click "Add" for "Send To" of "Run condition trigger" Choose "Recipient List" (or any other) Click "Advanced..." of "Run condition trigger" Select "Run Condition" (can leave at "Always") Click Jenkins "Save" or "Apply" Leave the page, and return to the same configuration Expected result: All configuration was saved, "send to" has a list of selected recipients. Actual result: Most configuration was saved, "send to" list has been cleared. Please note this only happens for "Run condition trigger". Other triggers save correctly Environment: Jenkins ver: 1.565.3 Email Extension Plugin: 2.39 Project: Jenkins Labels: plugin email-ext Priority: Minor Reporter: slav dok This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [svnmerge-plugin] (JENKINS-25766) Rebase build action does not list/use Promotion permalinks, contrary to documentation
slav dok commented on JENKINS-25766 Rebase build action does not list/use Promotion permalinks, contrary to documentation I think I found the issue. The "Rebase" build action lists the permalinks/promotions of the child/branch job. This is still contrary to documentation and manual "Rebase from Upstream", both of which use permalinks/promotions of the parent/trunk job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [svnmerge-plugin] (JENKINS-25766) Rebase build action does not list/use Promotion permalinks, contrary to documentation
slav dok
updated JENKINS-25766
Rebase build action does not list/use Promotion permalinks, contrary to documentation
Change By:
slav dok
(26/Nov/14 4:40 AM)
Description:
Inthewikidocumentation,underAutomaticRebasesection,itexplicitlystatesabilitytorebasetoapointcreatedwithPromotedBuildspermalink:{quote}Specifyingthebuildtorebasetoisagoodwaytocontrolthefrequencyoftherebase.Forexample,imagineusingthebuildpromotionpluginonthetrunk,andpromoteabuildasrebasepointaboutonceaday(contingentonpassingQAjobs.){quote}Howeverversion2.3oftheplugindoesnotlist(norletuse)anyPromotedBuildspermalinks,itonlyshowdefaultlast,stable,unstable,etc,andLastIntegratedPleasenotethisproblemis*only*with*BuildAction*thatispartofregularbuildsteps.ThemanualRebasefromUpstreamlinkontheleftofproject_does_showcustom/promotedbuildspermalinks.
Edit:TheRebasebuildstepshowsthechild/branchpermalinks/promotions,whilethemanualactionRebasefromUpstreamanddocumentationuseparent/trunkpermalinks/promotions
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [svnmerge-plugin] (JENKINS-25217) Do not force automatic rebase upon successfull integration to upstream
slav dok commented on JENKINS-25217 Do not force automatic rebase upon successfull integration to upstream I agree with Hugues that "rebase" after "reintegrate" is absolutely required, as per SVN documentation. However what would be nice here is an option to only do "rebase" on the feature job, without triggering the rest of the build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [svnmerge-plugin] (JENKINS-25766) Rebase build action does not list/use Promotion permalinks, contrary to documentation
slav dok created JENKINS-25766 Rebase build action does not list/use Promotion permalinks, contrary to documentation Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 24/Nov/14 8:21 PM Description: In the wiki documentation, under "Automatic Rebase" section, it explicitly states ability to rebase to a point created with "Promoted Builds" permalink: Specifying the build to rebase to is a good way to control the frequency of the rebase. For example, imagine using the build promotion plugin on the trunk, and promote a build as "rebase point" about once a day (contingent on passing QA jobs.) However version 2.3 of the plugin does not list (nor let use) any Promoted Builds permalinks, it only show default "last, stable, unstable, etc, and Last Integrated" Environment: Jenkins: 1.565.3 Subversion Plug-in: 2.4.5 svnmerge plugin: 2.3 Project: Jenkins Priority: Minor Reporter: slav dok This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [svnmerge-plugin] (JENKINS-25769) Rebase build action cannot be triggered from Promoted Builds
slav dok created JENKINS-25769 Rebase build action cannot be triggered from Promoted Builds Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 24/Nov/14 9:28 PM Description: When executing "Rebase" action from Promoted Builds, it skips with indication that it's not an SVN project Started by user slavd Building on master in workspace D:\jobs\feature-trunk-slav-personal\workspace Promoting feature-trunk-slav-personal #68 Project does not build a Subversion feature branch. Skip rebase action. I understand that Promoted Builds don't appear like normal builds, however the "Rebase from Upstream" manual action always works on latest WORKSPACE anyways, so being able to trigger it from promotions (for reasons for checking tests/QA approval first) would be much appreciated. Environment: Jenkins: 1.565.3 Subversion Plug-in: 2.4.5 Promoted Builds Plugin: 2.18 svnmerge plugin: 2.3 Project: Jenkins Priority: Major Reporter: slav dok This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [svnmerge-plugin] (JENKINS-25766) Rebase build action does not list/use Promotion permalinks, contrary to documentation
slav dok
updated JENKINS-25766
Rebase build action does not list/use Promotion permalinks, contrary to documentation
Change By:
slav dok
(24/Nov/14 9:33 PM)
Description:
Inthewikidocumentation,underAutomaticRebasesection,itexplicitlystatesabilitytorebasetoapointcreatedwithPromotedBuildspermalink:{quote}Specifyingthebuildtorebasetoisagoodwaytocontrolthefrequencyoftherebase.Forexample,imagineusingthebuildpromotionpluginonthetrunk,andpromoteabuildasrebasepointaboutonceaday(contingentonpassingQAjobs.){quote}Howeverversion2.3oftheplugindoesnotlist(norletuse)anyPromotedBuildspermalinks,itonlyshowdefaultlast,stable,unstable,etc,andLastIntegrated
Pleasenotethisproblemis*only*with*BuildAction*thatispartofregularbuildsteps.ThemanualRebasefromUpstreamlinkontheleftofproject_does_showcustom/promotedbuildspermalinks.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [svnmerge-plugin] (JENKINS-25739) Wrong revision used for upstream integration
slav dok created JENKINS-25739 Wrong revision used for upstream integration Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 21/Nov/14 7:54 PM Description: The "Integrate Branch" action is selectable per run. Let's say I have two runs, #2 @57 and #1 @45. You can select a previous run, not necessarily the latest/@HEAD. If I select #1, and then click "Integrate Branch" action, the message that is displayed before "Integrate this build to upstream" button is clicked shows correct SVN revision of run #1 @45. However when the plugin operates, it does not merge from revision of #1 as selected. Instead, it merges to upstream from HEAD of branch. Here is my log. As you can see, I tried to integrate @45, as evident from message, however the plugin operated on @57: This will merge http://svn/branches/feature (rev.45) to trunk-build Last Failure Switching to the upstream (http://svn/trunk) U New Text Document.txt U. At revision 57 Merging http://svn/branches/feature (rev.57) to the upstream C New Text Document.txt U. Found conflict with the upstream. Reverting this failed merge Switching back to the branch (http://svn/branches/feature@57) U New Text Document.txt U. At revision 57 Conflict found. Please sync with the upstream to resolve this error. Completed If the plugin always integrates from @HEAD of branch, then the "Integrate Branch" action should be moved from per-run-level to job-level, and the message should be fixed Environment: Jenkins: 1.565.3 Subversion Plug-in: 2.4.5 svnmerge plugin: 2.3 Project: Jenkins Priority: Major Reporter: slav dok This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [scm-sync-configuration] (JENKINS-15898) Subversion back-end cannot handle renaming of jobs
slav dok commented on JENKINS-15898 Subversion back-end cannot handle renaming of jobs I've tested 0.0.8 Jenkins 1.565.3 (LTS) Still the same issue. Everything works until the job is renamed. Once it is renamed... the whole things breaks and no other commits are going through. INFO SVN commit directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration Oct 15, 2014 5:06:56 PM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness processCommitsQueue SEVERE: Error while processing commit queue : Error while copying file hierarchy to SCM checkouted directory INFO SVN remove working directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs Oct 15, 2014 5:07:18 PM org.tmatesoft.svn.core.internal.util.DefaultSVNDebugLogger log INFO: CLI: executing statement: CREATE TABLE DELETE_LIST (local_relpath TEXT PRIMARY KEY NOT NULL); INFO SVN commit directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration Oct 15, 2014 5:07:18 PM hudson.plugins.scm_sync_configuration.SCMManipulator checkinFiles SEVERE: checkinFiles Problem during SCM commit : svn: E175002: Commit failed (details follow): svn: E175002: DELETE /!svn/wrk/90eaa215-4901-0010-a0d4-0b2a729a5a4c/DEV/JENKINS_CONFIGS/jobs/MyJob failed Oct 15, 2014 5:07:18 PM hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness processCommitsQueue SEVERE: Error while processing commit queue : Error while checking in file to scm repository This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [pending-changes] (JENKINS-25027) Plugin exceptions with No credential to try with Subversion SCM plugin 2.0 and above
slav dok created JENKINS-25027 Plugin exceptions with No credential to try with Subversion SCM plugin 2.0 and above Issue Type: Bug Assignee: Unassigned Components: pending-changes Created: 07/Oct/14 3:40 PM Description: After Subversion SCM plugin version upgraded to 2.0 (and above), the stored credentials model has changed. Pending-changes plugin can no longer find valid credentials and exceptions with: "No credential to try. Authentication failed". Last working version was with Subversion 1.54 (before the upgrade to 2.0) Below is the exception trace: Oct 07, 2014 10:14:10 AM org.jenkinsci.plugins.pendingChanges.SubversionScmPendingChangesProvider retrieveSubversionLogEntries WARNING: retrieving logs failed org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /trunk/myproject failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:960) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1035) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:940) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:864) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1412) at org.jenkinsci.plugins.pendingChanges.SubversionScmPendingChangesProvider.retrieveSubversionLogEntries(SubversionScmPendingChangesProvider.java:130) at org.jenkinsci.plugins.pendingChanges.SubversionScmPendingChangesProvider.getPendingChanges(SubversionScmPendingChangesProvider.java:113) at org.jenkinsci.plugins.pendingChanges.PendingChangesAction.getPendingChanges(PendingChangesAction.java:87) at org.jenkinsci.plugins.pendingChanges.PendingChangesColumn.getPendingChanges(PendingChangesColumn.java:55) 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 org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at
[JIRA] [promoted-builds] (JENKINS-10068) Ability to remove a Promotion on a promoted build
slav dok commented on JENKINS-10068 Ability to remove a Promotion on a promoted build +1 vote for this. We use promotions extensively for workflow purposes, and often the workflow has to be restarted and erroneously triggered promotions needs to be deleted. Really hoping for a fix for this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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.
