[JIRA] (JENKINS-60358) Support Root=null value in Template workspace - Currently it is overridden, failing sync

13 views
Skip to first unread message

kwirth@perforce.com (JIRA)

unread,
Dec 6, 2019, 9:26:03 AM12/6/19
to jenkinsc...@googlegroups.com
Karl Wirth updated an issue
 
Jenkins / Bug JENKINS-60358
Support Root=null value in Template workspace - Currently it is overridden, failing sync
Change By: Karl Wirth
Summary: Support Root=null value in Template workspace  - Currently it is overridden, failing sync
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

kwirth@perforce.com (JIRA)

unread,
Dec 6, 2019, 9:27:03 AM12/6/19
to jenkinsc...@googlegroups.com
Karl Wirth updated an issue
Change By: Karl Wirth
Issue Type: Bug Improvement

kwirth@perforce.com (JIRA)

unread,
Dec 6, 2019, 9:27:03 AM12/6/19
to jenkinsc...@googlegroups.com
Karl Wirth updated an issue
Change By: Karl Wirth
Priority: Minor Major

kwirth@perforce.com (JIRA)

unread,
Dec 6, 2019, 9:27:04 AM12/6/19
to jenkinsc...@googlegroups.com
Karl Wirth assigned an issue to Unassigned
Change By: Karl Wirth
Assignee: Karl Wirth

kwirth@perforce.com (JIRA)

unread,
Dec 6, 2019, 9:27:04 AM12/6/19
to jenkinsc...@googlegroups.com
Karl Wirth updated an issue
Change By: Karl Wirth
Labels: P4_SUPPORT P4_A P4_VERIFY

shaishap@gmail.com (JIRA)

unread,
Dec 15, 2019, 3:43:03 AM12/15/19
to jenkinsc...@googlegroups.com
Shai Shapira commented on Improvement JENKINS-60358
 
Re: Support Root=null value in Template workspace - Currently it is overridden, failing sync

Thanks, but this breaks current simplicity for allowing multi-config management as well (using Jenkins multi config add-on) - Use of pipeline job affects UI simplification for users, which we are currently looking for.

shaishap@gmail.com (JIRA)

unread,
Feb 1, 2020, 12:04:03 PM2/1/20
to jenkinsc...@googlegroups.com

Any Update?

kwirth@perforce.com (JIRA)

unread,
Feb 3, 2020, 3:39:02 AM2/3/20
to jenkinsc...@googlegroups.com

Hi Shai Shapira,

This is still in the backlog but you commenting on it will mark it as an active job for the developers the next time they review the backlog.

Your previous comments suggests that the reason you are not using the workaround is it is more confusing for users? Is that correct or did I misread it?

Regards,

Karl
Reply all
Reply to author
Forward
0 new messages