[JIRA] (JENKINS-55724) join plugin no longer working since upgrade
Title: Message Title lode leroy updated an issue Jenkins / JENKINS-55724 join plugin no longer working since upgrade Change By: lode leroy Attachment: join_exception.txt 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-55724) join plugin no longer working since upgrade
Title: Message Title lode leroy created an issue Jenkins / JENKINS-55724 join plugin no longer working since upgrade Issue Type: Bug Assignee: mdonohue Attachments: join_exception.txt Components: join-plugin Created: 2019-01-22 10:30 Priority: Minor Reporter: lode leroy since upgrading to 2.161 the join plugin throws an exception for existing jobs, and cannot be used for new jobs Add Comment
[JIRA] (JENKINS-47470) Join plugin
Title: Message Title lode leroy commented on JENKINS-47470 Re: Join plugin I have a similar problem since upgrading. (see attachment) 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-47470) Join plugin
Title: Message Title lode leroy updated an issue Jenkins / JENKINS-47470 Join plugin Change By: lode leroy Attachment: join_exception.txt 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] [copyartifact-plugin] (JENKINS-26952) build selector last successful matrix sub-build
lode leroy updated JENKINS-26952 build selector last successful matrix sub-build Change By: lode leroy (13/Feb/15 9:04 AM) Description: Iwouldliketoknowhowtobettertousethematrixreloadedfeatureincombinationwiththecopyartefacts.Ihaveamatrixbuildthathas 3 2 dimensions:component,platformserver,win=OK,build=1client,win,=OK,build=1client,mac=OK,build=1attheend,theartefactsarearchived.server,win=OK,build=2client,win=FAILclient,mac=OK,build=2whenoneofthose6fails,Iwouldliketobeabletodoanewbuild,torebuildthefailedcomponentclient,win=OK,build=3now,Ihaveanotherbuildthatdoesacopyartefactsfromthismatrixbuild.Iwouldlikeabuildselectortousethefollowingbuilds:server,win=OK,build=2client,win=OK,build=3client,mac=OK,build=2now,thefailedbuild(2nd)doesnotcopytheartifacts,andthelastsuccessfulbuild(3rd)onlycopiesthearchivedartefactsfromthatbuild.soIendupwithserver,win=OK,build=1client,win=OK,build=3client,mac=OK,build=1 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] [copyartifact-plugin] (JENKINS-26952) build selector last successful matrix sub-build
lode leroy closed JENKINS-26952 as Not A Defect build selector last successful matrix sub-build Change By: lode leroy (13/Feb/15 9:20 AM) Status: Open Closed Resolution: NotADefect 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] [copyartifact-plugin] (JENKINS-26952) build selector last successful matrix sub-build
lode leroy created JENKINS-26952 build selector last successful matrix sub-build Issue Type: New Feature Assignee: Unassigned Components: copyartifact-plugin Created: 13/Feb/15 8:28 AM Description: I would like to know how to better to use the "matrix reloaded" feature in combination with the "copy artefacts". I have a matrix build that has 3 dimensions: component, platform server, win = OK , build=1 client, win, = OK , build=1 client, mac = OK , build=1 at the end, the artefacts are archived. server, win = OK , build=2 client, win = FAIL client, mac = OK , build=2 when one of those 6 fails, I would like to be able to do a new build, to rebuild the failed component client, win = OK , build=3 now, I have another build that does a "copy artefacts" from this matrix build. I would like a build selector to use the following builds: server, win = OK , build=2 client, win = OK , build=3 client, mac = OK , build=2 now, the failed build (2nd) does not copy the artifacts, and the "last successful build" (3rd) only copies the archived artefacts from that build. so I end up with server, win = OK , build=1 client, win = OK , build=3 client, mac = OK , build=1 Environment: Jenkins ver. 1.594 Project: Jenkins Labels: plugin Priority: Minor Reporter: lode leroy 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] [p4-plugin] (JENKINS-26925) P4 to adapt view spec to current workspace (like Perforce plugin)
lode leroy assigned JENKINS-26925 to Paul Allen P4 to adapt view spec to current workspace (like Perforce plugin) Change By: lode leroy (12/Feb/15 12:51 PM) Assignee: RobPetti PaulAllen 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] [p4-plugin] (JENKINS-26925) P4 to adapt view spec to current workspace (like Perforce plugin)
lode leroy
updated JENKINS-26925
P4 to adapt view spec to current workspace (like Perforce plugin)
Change By:
lode leroy
(12/Feb/15 12:51 PM)
Description:
thePerforcepluginreplacesthefirstpartoftheviewspecbythenameoftheworkspace.woulditbepossibletoprovidesimilarfunctionalityintheP4plugin.couldbeaseasyaeprovidinga${workspace}variable,butfor(backwards)compatibilityitwouldbehandytodothesameastheotherplugin:(fromthePerforceplugin:)Mappings:Thisisthedepottoclientmappinginthesamedepot-clientpairformatasastandardPerforceworkspacespec,withacoupleofhandyshortcutsadded:theworkspacenameprovidedinthesecondofeachpairisnotactuallyused--theactualworkspacenameisalwayssubstituted.And,thesecondmemberofanypairmaybeommittedwhichwillresultinanidentitymappingbeingused.ie,//depot/test/subdir/...willmapto//workspace/test/subdir/...IfLetHudson/JenkinsManageWorkspaceViewischeckedtheviewenteredherewilloverwritetheviewintheexistingclient.Typicalexamplesthathavethesamemeaning://depot/folder/...//workspace-name/folder/...//depot/folder/...//anyplaceholder/folder/...//depot/folder/...Note:Parametersubstitutionoftheform${parametername}canbeusedanywhereintheviewspectosubstitutejobparameters.
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] [p4-plugin] (JENKINS-26925) P4 to adapt view spec to current workspace (like Perforce plugin)
lode leroy updated JENKINS-26925 P4 to adapt view spec to current workspace (like Perforce plugin) Change By: lode leroy (12/Feb/15 12:49 PM) Component/s: p4-plugin Component/s: perforce-plugin 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] [perforce-plugin] (JENKINS-26925) P4 to adapt view spec to current workspace (like Perforce plugin)
lode leroy
created JENKINS-26925
P4 to adapt view spec to current workspace (like Perforce plugin)
Issue Type:
New Feature
Assignee:
Rob Petti
Components:
perforce-plugin
Created:
12/Feb/15 12:48 PM
Description:
the "Perforce" plugin replaces the first part of the view spec by the name of the workspace.
would it be possible to provide similar functionality in the "P4" plugin.
could be as easy ae providing a ${workspace} variable, but for (backwards) compatibility it would be handy to do the same as the other plugin:
(from the "Perforce" plugin
Mappings: This is the depot to client mapping in the same depot-client pair format as a standard Perforce workspace spec, with a couple of handy shortcuts added: the workspace name provided in the second of each pair is not actually used--the actual workspace name is always substituted. And, the second member of any pair may be ommitted which will result in an identity mapping being used. ie, //depot/test/subdir/... will map to //workspace/test/subdir/...
If "Let Hudson/Jenkins Manage Workspace View" is checked the view entered here will overwrite the view in the existing client.
Typical examples that have the same meaning:
//depot/folder/... //workspace-name/folder/...
//depot/folder/... //anyplaceholder/folder/...
//depot/folder/...
Note:Parameter substitution of the form ${parametername} can be used anywhere in the view spec to substitute job parameters.
Project:
Jenkins
Labels:
plugin
Priority:
Minor
Reporter:
lode leroy
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.
