On 11/07/17 20:04, KatolaZ wrote:
> On Tue, Jul 11, 2017 at 07:49:41PM +1200, Daniel Reurich wrote:
>> On 11/07/17 19:25, Jaromil wrote:
>>> On Mon, 10 Jul 2017, KatolaZ wrote:
>>>
>>>> Centurion_Dan: I really need to have full access to Jenkins, at this
>>>> point.
>> To what end, you don't need such access and shouldn't have it for the
>> user that executes builds. I can set up a user - I'm assuming you're
>> using the jenkins api?
>>
> I have been asking you to let me control jenkins jobs for two
> months now. I still can't do more than creating issue on gitlab with
> buildadd or build as a subject.
Bullshit - this is the way it's been since the last time:



You have had these permissions since the last time we looked at it. You
have had the all the permissions you need to manage jobs. Are you
actually using the correct username?? If you want more sure, lets talk
about it.

But if you can't modify jobs already then there is something wrong with
your logon and we need to fix that first.
Can we setup a hangout or something so we can debug it??
>
> But evidently I am too young to master the true depths of Jenkins...
Oh come on!! That's simply not helpful..
>> Besides root access to the server doesn't give you better access to
>> jenkins anyway, which presumably is what your'e after. Not saying you
>> can't have full access either, but we need to talk about it and ensure
>> that you understand the full implications as well.
>>
> Thanks for the trust :\ I will go and RTFM for the next two years.
>
> I thought you were genuinely against allowing single points of
> fault. At present, you are a single point of fault.
I'm not a single point of failure as you can see above, but I'm being
cautious as well. It took me nearly a year to get nextimes trust, and
I'm just trying to be a little careful too with that sharing that trust,
and messing with jenkins could destroy what we have. Let's talk video
conference about this.

Daniel


--
Daniel Reurich
Centurion Computer Technology (2005) Ltd.
021 797 722