Custom Plugin Not Able to Authenticate with Registry

Good Morning! We are building a custom plugin based on Docker Build Publish that uses Source to Image to build the image on top

Re: WORKSPACE permission and viewing workspace files using plugins

IIRC the intention of the permission was to hinder users who don't have access to read the repo to retrieve the source code by "other means" i.e. through the Jenkins workspace browser. /B 2017-11-21 13:46 GMT+01:00 Ullrich Hafner : > I have a question on how to

Re: Unable to upload snapshot of teamconcert-plugin 401 Unauthorized error

> On 21. Nov 2017, at 15:27, Lakshmi Narasimhan Vaikuntam > wrote: > > Any reasons for this to happen? Please see https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues -- You received this message because you are

Unable to upload snapshot of teamconcert-plugin 401 Unauthorized error

I am trying to create a snapshot from the latest commit to teamconcert-plugin (https://github.com/jenkinsci/teamconcert-plugin). I get the following exception. Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Return code is: 401, ReasonPhrase: Unauthorized. I am able

Unable to upload snapshot of teamconcert-plugin 401 Unauthorized error

I am trying to create a snapshot from the latest commit to teamconcert-plugin (https://github.com/jenkinsci/teamconcert-plugin). I get the following exception. Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Return code is: 401, ReasonPhrase: Unauthorized. Any

WORKSPACE permission and viewing workspace files using plugins

I have a question on how to interpret the permission WORKSPACE in plug-ins. As far as I understand the changed documentation in [1] this permission should only be evaluated when trying to view workspace files using the workspace browser. However, in my static analysis plug-ins I implemented a

Re: Propose a workaround of missing multiple security realm feature

2017-11-20 16:25 GMT+01:00 Jesse Glick : > On Sat, Nov 18, 2017 at 9:57 AM, wrote: > > The idea is simple: create a new security realm (composite) which > delegates > > methods calls to some chosen security realms (components). > > The idea is indeed