Re: Creation of Jenkins slaves and Credentials using the Remote Access API

Below snippet worked for me curl -X POST 'http://jenkins_server:8080/credentials/store/system/domain/_/createCredentials' \ --user *userid:token* --data-urlencode 'json={ "": "0", "credentials": { "scope": "GLOBAL", "id": "user name", "username": "jenkinsUserID",

Re: Query

I need more information to respond. If you provide a link to the code, it would help a lot. - We provide hosting for open-source plugins, even if they integrate with Enterprise tools - We do not host private-source plugins, at all - We do not host open-source plugins if they bundle

Re: Trademark sublicense request: CloudBees Jenkins Metrics

Generally the request looks good to me. OTOH it would be great to get feedback from the maintainer of the Metrics Plugin (Stephen Connolly?). If CloudBees plans to release a "CloudBees Jenkins Metrics Plugin" as a part of this new

Re: Query

Hello, I _think_ not. We require plugins to be open-source, and that dependencies are also available (free of charge) for contributors to work on it. We can be more specific if you provide additional details I guess. Cheers 2018-03-08 7:05 GMT+01:00 Rahul Pure : > Hi, >

Re: Trademark sublicense request: CloudBees Jenkins Metrics

I personally find that the proposed name could cause confusion with the Metrics plugin, however given that the Metrics plugin was developed on company time, I feel it would be disingenuous of me to leverage a side-effect of being paid to do that development that has resulted in me being the

Re: [GSoc 2018] [Student Introduction] Jenkins Remoting over Message Bus/Queue

You still have not exposed "-p" option as proposed above. I kindly recommend to move this prototyping discussion to a separate thread so it does not pollute the project proposal discussion. Thanks in advance, Oleg On Thu, Mar 8, 2018 at 6:22 PM, Pham Vu Tuan wrote: > I

Re: [GSoc 2018] [Student Introduction] Jenkins Remoting over Message Bus/Queue

I resolved the JNLP warning message by passing env variable in Docker run. But I still encountered "Connection refused" error although I exposed the port 5 in the Dockerized master.

Re: Trademark sublicense request: CloudBees Jenkins Metrics

I think the presence of the "CloudBees" as a prefix has such overriding clarity in terms of the origin of the effort, that I'm having hard time imagining that creates a confusion in that regard. It is true that they share the same "Metrics" part, but that's not the trademarked part. That said, I

Re: having trouble with releasing to jenkins-ci.org

is there anyone that can provide additional guidance? i installed a linux virtual machine running CentOS 7.4 and i am still hitting the same issue. Some additional, but important details. * If i just run "mvn deploy", my package is uploaded the artifactory. so my creds in settings.xml are

Re: having trouble with releasing to jenkins-ci.org

if i also run "svn status" i get << [root@jenkinsslavecentos apprenda-plugin]# svn status svn: warning: W155007: '/root/apprenda-plugin' is not a working copy >> On Friday, March 9, 2018 at 4:56:58 AM UTC+3, Michael Michael wrote: > > i removed that line right now, cleaned up the target and the

Re: having trouble with releasing to jenkins-ci.org

one last thing. not sure if it is relevant or not, but i am using github's two factor authentication for logging in. this is required by my organization. On Friday, March 9, 2018 at 5:03:18 AM UTC+3, Michael Michael wrote: > > hi Daniel, > > may i ask what these commands do then in the output

Re: having trouble with releasing to jenkins-ci.org

> On 9. Mar 2018, at 03:03, Michael Michael wrote: > > may i ask what these commands do then in the output trail? It seems that SVN > is called in here, and this is the command that is failing > << > [INFO] Resuming release from phase 'scm-commit-release' > [INFO] Checking

Re: having trouble with releasing to jenkins-ci.org

> On 9. Mar 2018, at 02:56, Michael Michael wrote: > > i need to be setting up for SVN and its communication/interaction with git. It's unclear why you're asking this. Subversion should not be involved at all. Git is its replacement for us. Whatever link you followed is

Re: having trouble with releasing to jenkins-ci.org

i removed that line right now, cleaned up the target and the .m2\repository folders and still seeing the same failure. is there anything specific i need to be setting up for SVN and its communication/interaction with git. On Friday, March 9, 2018 at 4:34:42 AM UTC+3, Daniel Beck wrote: > > > >

Re: having trouble with releasing to jenkins-ci.org

i am working in a git repository. see command output below. << [root@jenkinsslavecentos apprenda-plugin]# git status # On branch master nothing to commit, working directory clean [root@jenkinsslavecentos apprenda-plugin]# dir pom.xml pom.xml [root@jenkinsslavecentos apprenda-plugin]# pwd

Re: having trouble with releasing to jenkins-ci.org

hi Daniel, may i ask what these commands do then in the output trail? It seems that SVN is called in here, and this is the command that is failing << [INFO] Resuming release from phase 'scm-commit-release' [INFO] Checking in modified POMs... [INFO] Executing: /bin/sh -c cd /root/apprenda-plugin

Re: having trouble with releasing to jenkins-ci.org

i added the distribution management section while i was troubleshooting to see if i could find what was wrong. i tried everything i would read online..and this was one of them. On Friday, March 9, 2018 at 6:37:33 AM UTC+3, Daniel Beck wrote: > > > > On 9. Mar 2018, at 03:03, Michael Michael

Re: [GSoc 2018] [Student Introduction] Jenkins Remoting over Message Bus/Queue

Hi Pham, In order to connect an agent to the Dockerized master, you need to expose the port for the agent (make the Agent port fixed in security settings + use "-p" option to expose it). I am not sure how BlueOcean image is configured, the standard Jenkins Docker image has it documented here: