Pipeline script from SCM loses ownership

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Pipeline script from SCM loses ownership

jeankst
Hi all,

We have pipeline jobs configured to use a script from GIT.
Those jobs ownership are lost each time they are built.
  1. create a Pipeline job with definition being pipeline from SCM
  2. save
  3. set ownership (if not set automatically to job creator)
  4. build
  5. notice that ownership no more set
This happens whatever the "Ownership management policy on job modifications" option is set to (Do not assign ownership or Assign job creators as owners)

Setup:
  • Jenkins 2.53
  • Job and Node ownership plugin 0.9.1
Anybody faced this issue? or am I missing something?

Thanks,
Jean.


--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9ae49b59-da06-45d4-9399-78a852e92d80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Pipeline script from SCM loses ownership

jeankst
To answer my own question:
I was using properties - I thought it was updating properties as stated here
But as it was in a pipeline job (not multibranch) so all job properties got lost:

WARNING: The properties step will remove all JobPropertys currently configured in this job, either from the UI or from an earlier properties step.



On Thursday, April 13, 2017 at 1:15:49 PM UTC+2, jeankst wrote:
Hi all,

We have pipeline jobs configured to use a script from GIT.
Those jobs ownership are lost each time they are built.
  1. create a Pipeline job with definition being pipeline from SCM
  2. save
  3. set ownership (if not set automatically to job creator)
  4. build
  5. notice that ownership no more set
This happens whatever the "Ownership management policy on job modifications" option is set to (Do not assign ownership or Assign job creators as owners)

Setup:
  • Jenkins 2.53
  • Job and Node ownership plugin 0.9.1
Anybody faced this issue? or am I missing something?

Thanks,
Jean.


--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0178776f-1309-4c0e-b90f-d97a42662443%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...