[JIRA] (JENKINS-50685) UI should explain why you can't modify WorkflowJobs under a Multibranch project

2 views
Skip to first unread message

svanoort@cloudbees.com (JIRA)

unread,
Apr 9, 2018, 2:32:02 PM4/9/18
to jenkinsc...@googlegroups.com
Sam Van Oort created an issue
 
Jenkins / Improvement JENKINS-50685
UI should explain why you can't modify WorkflowJobs under a Multibranch project
Issue Type: Improvement Improvement
Assignee: Unassigned
Components: workflow-multibranch-plugin
Created: 2018-04-09 18:31
Labels: ux
Priority: Minor Minor
Reporter: Sam Van Oort

This is by design (see https://issues.jenkins-ci.org/browse/JENKINS-33900) but really confusing for users. We should add a comment "to modify configuration, see the Multibranch project and use Properties step" or something.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

svanoort@cloudbees.com (JIRA)

unread,
Apr 9, 2018, 2:33:02 PM4/9/18
to jenkinsc...@googlegroups.com
Sam Van Oort updated an issue
Change By: Sam Van Oort
This is by design (see https://issues.jenkins-ci.org/browse/JENKINS-33900) but really confusing for users.   We should add a comment "to modify configuration, see the Multibranch project and use Properties step" or * something * so they know what's up and how to control configuration .

svanoort@cloudbees.com (JIRA)

unread,
Apr 9, 2018, 2:33:02 PM4/9/18
to jenkinsc...@googlegroups.com
Sam Van Oort commented on Improvement JENKINS-50685
 
Re: UI should explain why you can't modify WorkflowJobs under a Multibranch project

Related issue where users thought it was a bug that this couldn't be done.

Carl@etaylor.me (JIRA)

unread,
Jul 24, 2019, 8:53:02 PM7/24/19
to jenkinsc...@googlegroups.com

I saw JENKINS-33900, and I don't agree with it. How else are you going to configure things like 'Build whenever a SNAPSHOT dependency is built' on subbranches? Additionally, I've found that the github project is stamped out, and you can no longer change it's branch matching strategy short of deleting the entire github project and re-scanning.

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages