• Type: New Feature
• Resolution: Unresolved
• Priority: Minor
• Component/s: ownership-plugin
• Labels:

  • jcasc-compatibility

[JENKINS-52311] Support JCasC in the Ownership plugin

Oleg Nenashev created issue - 2018-07-02 09:10

Oleg Nenashev made changes - 2018-07-02 09:10

Labels

New: jcasc-compatibility

Oleg Nenashev made changes - 2018-08-11 11:19

Link

New: This issue is duplicated by JENKINS-52961 [ JENKINS-52961 ]

Oleg Nenashev made changes - 2018-12-30 12:44

Assignee

Original: Oleg Nenashev [ oleg_nenashev ]

René Scheibe made changes - 2019-03-10 10:25

Remote Link

New: This issue links to "GitHub Issue #5 (Web Link)" [ 22459 ]

Collapse comment: Martin Cimbalek added a comment - 2021-04-30 07:27, Edited by Martin Cimbalek - 2021-04-30 07:27

Martin Cimbalek added a comment - 2021-04-30 07:27 - edited

Hello, are there any plans for resolving this? It would be very useful if either this is resolved or the behaviour described in [1] is altered. Thanks!

[1] https://issues.jenkins.io/browse/JENKINS-58000?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel

 

Expand comment: Martin Cimbalek added a comment - 2021-04-30 07:27, Edited by Martin Cimbalek - 2021-04-30 07:27

Martin Cimbalek added a comment - 2021-04-30 07:27 - edited Hello, are there any plans for resolving this? It would be very useful if either this is resolved or the behaviour described in [1] is altered. Thanks! [1] https://issues.jenkins.io/browse/JENKINS-58000?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel  

Collapse comment: Ted Sanders added a comment - 2021-10-21 14:33

Ted Sanders added a comment - 2021-10-21 14:33

Hello.  I have 3000 application teams that depend on this functionality. Is this being fixed?  My users are blocked from shifting primary and secondary ownership. 

We use casc, we also use ownership plugin to manage nodes. We do this because we don't provide global admin rights.  The two parts compliment each other. 

When I set a new primary or secondary owner, restart of the instance sets the owner back to the original person.

I see this in view casc configuration: 

      nodeProperties: |-
        FAILED TO EXPORT
        hudson.slaves.DumbSlave#nodeProperties: io.jenkins.plugins.casc.ConfiguratorException: Can't read attribute 'slaveOwnership' from com.synopsys.arc.jenkins.plugins.ownership.nodes.OwnerNodeProperty@146690a9
          at io.jenkins.plugins.casc.Attribute._getValue(Attribute.java:461)

Expand comment: Ted Sanders added a comment - 2021-10-21 14:33

Ted Sanders added a comment - 2021-10-21 14:33 Hello.  I have 3000 application teams that depend on this functionality. Is this being fixed?  My users are blocked from shifting primary and secondary ownership.  We use casc, we also use ownership plugin to manage nodes. We do this because we don't provide global admin rights.  The two parts compliment each other.  When I set a new primary or secondary owner, restart of the instance sets the owner back to the original person. I see this in view casc configuration:  nodeProperties: |- FAILED TO EXPORT hudson.slaves.DumbSlave#nodeProperties: io.jenkins.plugins.casc.ConfiguratorException: Can 't read attribute ' slaveOwnership' from com.synopsys.arc.jenkins.plugins.ownership.nodes.OwnerNodeProperty@146690a9 at io.jenkins.plugins.casc.Attribute._getValue(Attribute.java:461)