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

[Michael Michael]

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  > 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 in modified POMs... 
> > [INFO] Executing: /bin/sh -c cd /root/apprenda-plugin && svn 
> --non-interactive commit --file /tmp/maven-scm-1675137483.commit --targets 
> /tmp/maven-scm-9172792877660663843-targets 
> > [INFO] Working directory: /root/apprenda-plugin 
> > >> 
> > 
>
> Are you working in a Git repository (working copy), or did you download 
> the sources? Perhaps it checks if you're in a Git repo, and if not, falls 
> back to SVN? IOW, in the directory that also contains pom.xml, does `git 
> status` show an error? 
>
> Besides that, 
> https://github.com/jenkinsci/apprenda-plugin/blob/b0e8592ba5b83f3ee63802bdf9a83ee14c84d3bc/pom.xml#L54
>  
> should be long obsolete, so it's unclear to me how you managed to deploy a 
> snapshot with that. (Unrelated to SCM problems though.) 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9dbd768f-c3c8-47f5-a59a-d394f2bb0220%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Michael]

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
/root/apprenda-plugin
[root@jenkinsslavecentos apprenda-plugin]# git remote -v
origin  https://github.com/jenkinsci/apprenda-plugin (fetch)
origin  https://github.com/jenkinsci/apprenda-plugin (push)
>>

On Friday, March 9, 2018 at 6:37:33 AM UTC+3, Daniel Beck wrote:
>
>
> > 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 in modified POMs... 
> > [INFO] Executing: /bin/sh -c cd /root/apprenda-plugin && svn 
> --non-interactive commit --file /tmp/maven-scm-1675137483.commit --targets 
> /tmp/maven-scm-9172792877660663843-targets 
> > [INFO] Working directory: /root/apprenda-plugin 
> > >> 
> > 
>
> Are you working in a Git repository (working copy), or did you download 
> the sources? Perhaps it checks if you're in a Git repo, and if not, falls 
> back to SVN? IOW, in the directory that also contains pom.xml, does `git 
> status` show an error? 
>
> Besides that, 
> https://github.com/jenkinsci/apprenda-plugin/blob/b0e8592ba5b83f3ee63802bdf9a83ee14c84d3bc/pom.xml#L54
>  
> should be long obsolete, so it's unclear to me how you managed to deploy a 
> snapshot with that. (Unrelated to SCM problems though.) 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/97d3a010-9c58-4c6d-b168-314e561a99ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Daniel Beck]

> 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 in modified POMs...
> [INFO] Executing: /bin/sh -c cd /root/apprenda-plugin && svn 
> --non-interactive commit --file /tmp/maven-scm-1675137483.commit --targets 
> /tmp/maven-scm-9172792877660663843-targets
> [INFO] Working directory: /root/apprenda-plugin
> >>
> 

Are you working in a Git repository (working copy), or did you download the 
sources? Perhaps it checks if you're in a Git repo, and if not, falls back to 
SVN? IOW, in the directory that also contains pom.xml, does `git status` show 
an error?

Besides that, 
https://github.com/jenkinsci/apprenda-plugin/blob/b0e8592ba5b83f3ee63802bdf9a83ee14c84d3bc/pom.xml#L54
 should be long obsolete, so it's unclear to me how you managed to deploy a 
snapshot with that. (Unrelated to SCM problems though.)

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/44DE13D2-7B8B-43AB-8C4C-AD638B789788%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Michael]

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 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 && svn 
> --non-interactive commit --file /tmp/maven-scm-1675137483.commit --targets 
> /tmp/maven-scm-9172792877660663843-targets
> [INFO] Working directory: /root/apprenda-plugin
> >>
>
> On Friday, March 9, 2018 at 4:59:12 AM UTC+3, Daniel Beck wrote:
>>
>>
>> > 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 probably 
>> long obsolete, as the Jenkins project does not use SVN anymore. 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0dfc0246-73a3-401f-821b-5c38abd73690%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Michael]

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 && svn 
--non-interactive commit --file /tmp/maven-scm-1675137483.commit --targets 
/tmp/maven-scm-9172792877660663843-targets
[INFO] Working directory: /root/apprenda-plugin
>>

On Friday, March 9, 2018 at 4:59:12 AM UTC+3, Daniel Beck wrote:
>
>
> > 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 probably 
> long obsolete, as the Jenkins project does not use SVN anymore. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0e868151-8d8d-4ab0-8489-48b4530d5793%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Michael]

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 
> .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:
>>
>>
>> > On 9. Mar 2018, at 02:15, Michael Michael  wrote: 
>> > 
>> > can someone help? 
>> > 
>>
>> Why are you specifying m-r-p 2.5.2 in your POM? 
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/11dfa0ba-439f-4d93-9d09-ac68ae322a85%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Daniel Beck]

> 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 probably long 
obsolete, as the Jenkins project does not use SVN anymore.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/DC604F54-7780-48D5-8A5C-F57AF924938E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Michael]

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:
>
>
> > On 9. Mar 2018, at 02:15, Michael Michael  > wrote: 
> > 
> > can someone help? 
> > 
>
> Why are you specifying m-r-p 2.5.2 in your POM? 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/86f87a6f-cfa4-4a36-ae35-95ff734e3acf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Daniel Beck]

> On 9. Mar 2018, at 02:15, Michael Michael  wrote:
> 
> can someone help?
> 

Why are you specifying m-r-p 2.5.2 in your POM?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1288BE82-6639-4004-8C7D-23DB22416EED%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Michael]

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 accurate and working
* if i run "ssh -T g...@github.com" i am able to successfully login to 
github using SSH

but the mvn release fails with exactly the same error.
can someone help?

[INFO] Working directory: /root/apprenda-plugin
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 4.024 s
[INFO] Finished at: 2018-03-09T01:15:00Z
[INFO] Final Memory: 18M/259M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare (default-cli) 
on project apprenda: Unable to commit files
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: E155007: '/root/apprenda-plugin/pom.xml' is not a working copy
[ERROR]
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
goal org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare 
(default-cli) on project apprenda: Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: E155007: '/root/apprenda-plugin/pom.xml' is not a working copy

at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 
(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit 
files
Provider message:
The svn command failed.
Command output:
svn: E155007: '/root/apprenda-plugin/pom.xml' is not a working copy

at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease 
(PrepareReleaseMojo.java:294)
at org.apache.maven.plugins.release.PrepareReleaseMojo.execute 
(PrepareReleaseMojo.java:240)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:146)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 
(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.

Re: Trademark sublicense request: CloudBees Jenkins Metrics

[Kohsuke Kawaguchi]

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 inquired on this point and I learned that it is technically
true that there exists a jpi file whose display name is "CloudBees Jenkins
Metrics plugin."

But Metrics plugin and CloudBees Jenkins Metrics operate on different
planes. Metrics plugin is a library plugin, and it's by and large relevant
only for those who "open the engine room." CloudBees Jenkins Metrics is a
feature of a product that show up in brochures and collateral. It's a
little bit like workflow-*-plugin and Pipeline. The former is a unit of
distribution and development and a concern to contributors, the latter is a
unit of feature and a concern to users.

In addition to that, CloudBees Jenkins Metrics plugin is not distributed
the same way Metrics plugin is. The former is a restricted access plugin
that's only available to customers, and the latter is a plugin that's on
the community update center.


On Thu, Mar 8, 2018 at 6:41 AM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> 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 maintainer of the plugin in order to apply my personal opinions
> to the same company.
>
> In any case, as an employee of CloudBees, I feel I have to recuse myself
> from the debate.
>
>
> On Thursday, 8 March 2018 12:46:22 UTC, Oleg Nenashev wrote:
>>
>> 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 product, it may cause some confusion.
>>
>> BR, Oleg
>>
>> On Wednesday, March 7, 2018 at 5:29:40 PM UTC+1, Kohsuke Kawaguchi wrote:
>>>
>>> On behalf of CloudBees, I’d like to request the permission to use the
>>> following name that uses ‘Jenkins’ in it:
>>>
>>>- CloudBees Jenkins Metrics
>>>
>>> To help people understand how this name is going to be used, let me
>>> describe a bit about the effort for which we’d like to use this name.
>>>
>>> Back several years ago, we have requested the sublicense to use
>>> ‘CloudBees Jenkins Analytics,’ which was subsequently approved
>>> . It
>>> is a feature that is a part of our products. It has evolved since then, and
>>> we’d like to give it a new name to more accurately reflect what it is.
>>>
>>> When we look at name approval requests like this, a key criteria is to
>>> make sure it doesn’t create confusion about the origin of the effort. From
>>> that perspective, this name has ‘CloudBees’ clearly in front of it, and it
>>> is consistent with other names that are already approved. The situation and
>>> the considerations that led to the approval of the past requests hasn't
>>> really changed, so I hope the new name doesn’t raise any eyebrows and
>>> result in a smooth approval.
>>>
>>> I’ve put this up as an agenda for Mar 14th project meeting to be able to
>>> get a decision there. If you have any concerns or objections, please chime
>>> in on this thread prior to the meeting, so that we can address them.
>>>
>>> --
>>> Kohsuke Kawaguchi
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/a24547c6-32e1-4a75-9fc9-a1666ef8cf5a%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Kohsuke Kawaguchi

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4wL6Q3_qDGw%3DtJGQvupooBEgckFDa43YepTg4DiEtLAtg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Oleg Nenashev]

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 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.
>
>
> 
>
>
> 
> My command to start the agent is: "docker run -e JNLP_PROTOCOL_OPTS='-Dorg.
> jenkinsci.remoting.engine.JnlpProtocol3.disabled=false'
> jenkins/jnlp-slave -url http://localhost:8080 abcd test-node".
> Any ideas on this?
>
> On Friday, March 9, 2018 at 12:13:56 AM UTC+8, Oleg Nenashev wrote:
>>
>> 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: https://github.com/jenkinsci/d
>> ocker#usage
>>
>> Hopefully it helps,
>> Oleg
>>
>> P.S: I'd guess it's another case of WEBSITE-474
>> , right?
>>
>>
>>
>> On Thu, Mar 8, 2018 at 4:59 PM, Pham Vu Tuan  wrote:
>>
>>> Hello,
>>>
>>> I am trying to setup the master and agent in my local machine. Server
>>> setup is fine, I used https://hub.docker.com/r/jenkinsci/blueocean/.
>>> But when I tried to connect an agent to it using
>>> https://hub.docker.com/r/jenkins/jnlp-slave/ by this command "docker
>>> run jenkins/jnlp-slave -url http://localhost:8080 abcd test-node" , I
>>> encountered some problems:
>>>
>>> - Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS
>>> to alter the behavior => Athough I set the env variable in the docker
>>> container for the server, I still encountered this warning message, am I
>>> missing to set it somewhere?
>>> - Not sure if this is related to the above issue, then I cannot connect
>>> the agent to server
>>>
 SEVERE: Failed to connect to http://localhost:8080/tcpSlave
 AgentListener/: Connection refused (Connection refused)
 java.io.IOException: Failed to connect to
 http://localhost:8080/tcpSlaveAgentListener/: Connection refused
 (Connection refused)
 at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.reso
 lve(JnlpAgentEndpointResolver.java:199)
 at hudson.remoting.Engine.innerRun(Engine.java:518)
 at hudson.remoting.Engine.run(Engine.java:469)
>>>
>>> Could someone help me with this setup issue?
>>>
>>> Regards,
>>> Pham Vu Tuan
>>>
>>> On Monday, March 5, 2018 at 12:31:29 AM UTC+8, Oleg Nenashev wrote:

 Hi all,

 Since we have several students interested in this project, I propose to
 spend some time at office hours on Wednesday in order to discuss it.

 From what I see, everybody in this thread can attend during the
 APAC/Europe timeslot, right? If yes, let's just talk about the project
 there.

 BR, Oleg

 On Sunday, March 4, 2018 at 7:48:47 AM UTC+1, ajm...@g.rit.edu wrote:
>
> I am Amit Magar a graduate student pursuing masters in Computer
> Science from Rochester Institute of Technology. I am specializing in
> Computer Networks and Artificial Intelligence. I have 8 years formal
> education in Computer Science.
>
>  I have 3 years of professional works experience at Accenture.
> Currently, I am working at Genex Services, Pensylvania as Intern in
> Advanced Analytics.
>
>  In my work experience I worked on Integration of heterogeneous
> services, packaged and legacy applications (more than 20 applications)
> using Enterprise Service Bus, Web Services, and JMS queue. Our Continuous
> Integration stack (DevOps) included Jenkins, GIT, Chef Server and Nexus so
> I have good knowledge of these Tools. I am well versed in Java,
> SoftwarPython, XML and Docker technologies too. I have closely worked on
> each phase of Software development life cycle.
>
>  I always wanted to do open source contribution, my long-term goal is
> to become a contributor(Github) open source code. I think GSoC
> is good platform to start open source contribution where I will mentorship
> from experience open source contributor and will get chance interact with
> open source community which will be helpful for future contribution in 
> open
> source.
>
> Jenkins caught my attention because I have used Jenkins before for
> Co

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

[Pham Vu Tuan]

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.




My command to start the agent is: "docker run -e 
JNLP_PROTOCOL_OPTS='-Dorg.jenkinsci.remoting.engine.JnlpProtocol3.disabled=false'
 
jenkins/jnlp-slave -url http://localhost:8080 abcd test-node".
Any ideas on this?

On Friday, March 9, 2018 at 12:13:56 AM UTC+8, Oleg Nenashev wrote:
>
> 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: 
> https://github.com/jenkinsci/docker#usage
>
> Hopefully it helps,
> Oleg
>
> P.S: I'd guess it's another case of WEBSITE-474 
> , right?
>
>
>
> On Thu, Mar 8, 2018 at 4:59 PM, Pham Vu Tuan  > wrote:
>
>> Hello,
>>
>> I am trying to setup the master and agent in my local machine. Server 
>> setup is fine, I used https://hub.docker.com/r/jenkinsci/blueocean/. But 
>> when I tried to connect an agent to it using 
>> https://hub.docker.com/r/jenkins/jnlp-slave/ by this command "docker run 
>> jenkins/jnlp-slave -url http://localhost:8080 abcd test-node" , I 
>> encountered some problems:
>>
>> - Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS 
>> to alter the behavior => Athough I set the env variable in the docker 
>> container for the server, I still encountered this warning message, am I 
>> missing to set it somewhere?
>> - Not sure if this is related to the above issue, then I cannot connect 
>> the agent to server 
>>
>>> SEVERE: Failed to connect to 
>>> http://localhost:8080/tcpSlaveAgentListener/: Connection refused 
>>> (Connection refused)
>>> java.io.IOException: Failed to connect to 
>>> http://localhost:8080/tcpSlaveAgentListener/: Connection refused 
>>> (Connection refused)
>>> at 
>>> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:199)
>>> at hudson.remoting.Engine.innerRun(Engine.java:518)
>>> at hudson.remoting.Engine.run(Engine.java:469)
>>
>> Could someone help me with this setup issue?
>>
>> Regards,
>> Pham Vu Tuan 
>>
>> On Monday, March 5, 2018 at 12:31:29 AM UTC+8, Oleg Nenashev wrote:
>>>
>>> Hi all,
>>>
>>> Since we have several students interested in this project, I propose to 
>>> spend some time at office hours on Wednesday in order to discuss it.
>>>
>>> From what I see, everybody in this thread can attend during the 
>>> APAC/Europe timeslot, right? If yes, let's just talk about the project 
>>> there.
>>>
>>> BR, Oleg
>>>
>>> On Sunday, March 4, 2018 at 7:48:47 AM UTC+1, ajm...@g.rit.edu wrote:

 I am Amit Magar a graduate student pursuing masters in Computer Science 
 from Rochester Institute of Technology. I am specializing in Computer 
 Networks and Artificial Intelligence. I have 8 years formal education in 
 Computer Science.

  I have 3 years of professional works experience at Accenture. 
 Currently, I am working at Genex Services, Pensylvania as Intern in 
 Advanced Analytics.

  In my work experience I worked on Integration of heterogeneous 
 services, packaged and legacy applications (more than 20 applications) 
 using Enterprise Service Bus, Web Services, and JMS queue. Our Continuous 
 Integration stack (DevOps) included Jenkins, GIT, Chef Server and Nexus so 
 I have good knowledge of these Tools. I am well versed in Java, 
 SoftwarPython, XML and Docker technologies too. I have closely worked on 
 each phase of Software development life cycle.

  I always wanted to do open source contribution, my long-term goal is 
 to become a contributor(Github) open source code. I think GSoC 
 is good platform to start open source contribution where I will mentorship 
 from experience open source contributor and will get chance interact with 
 open source community which will be helpful for future contribution in 
 open 
 source.

 Jenkins caught my attention because I have used Jenkins before for 
 Continuous Integration.I have gone through the detailed information of 
 "Jenkins Remoting over Message Bus/Queue" project. I am particularly 
 interested in "Jenkins Remoting over Message Bus/Queue" Because my 
 previous 
 work experience in Java, JMS queues will be helpful here and I will be 
 able 
 actively to contr

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

[Oleg Nenashev]

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: https://github.com/jenkinsci/d
ocker#usage

Hopefully it helps,
Oleg

P.S: I'd guess it's another case of WEBSITE-474
, right?



On Thu, Mar 8, 2018 at 4:59 PM, Pham Vu Tuan  wrote:

> Hello,
>
> I am trying to setup the master and agent in my local machine. Server
> setup is fine, I used https://hub.docker.com/r/jenkinsci/blueocean/. But
> when I tried to connect an agent to it using https://hub.docker.com/r
> /jenkins/jnlp-slave/ by this command "docker run jenkins/jnlp-slave -url
> http://localhost:8080 abcd test-node" , I encountered some problems:
>
> - Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to
> alter the behavior => Athough I set the env variable in the docker
> container for the server, I still encountered this warning message, am I
> missing to set it somewhere?
> - Not sure if this is related to the above issue, then I cannot connect
> the agent to server
>
>> SEVERE: Failed to connect to http://localhost:8080/tcpSlaveAgentListener/:
>> Connection refused (Connection refused)
>> java.io.IOException: Failed to connect to http://localhost:8080/tcpSlave
>> AgentListener/: Connection refused (Connection refused)
>> at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.reso
>> lve(JnlpAgentEndpointResolver.java:199)
>> at hudson.remoting.Engine.innerRun(Engine.java:518)
>> at hudson.remoting.Engine.run(Engine.java:469)
>
> Could someone help me with this setup issue?
>
> Regards,
> Pham Vu Tuan
>
> On Monday, March 5, 2018 at 12:31:29 AM UTC+8, Oleg Nenashev wrote:
>>
>> Hi all,
>>
>> Since we have several students interested in this project, I propose to
>> spend some time at office hours on Wednesday in order to discuss it.
>>
>> From what I see, everybody in this thread can attend during the
>> APAC/Europe timeslot, right? If yes, let's just talk about the project
>> there.
>>
>> BR, Oleg
>>
>> On Sunday, March 4, 2018 at 7:48:47 AM UTC+1, ajm...@g.rit.edu wrote:
>>>
>>> I am Amit Magar a graduate student pursuing masters in Computer Science
>>> from Rochester Institute of Technology. I am specializing in Computer
>>> Networks and Artificial Intelligence. I have 8 years formal education in
>>> Computer Science.
>>>
>>>  I have 3 years of professional works experience at Accenture.
>>> Currently, I am working at Genex Services, Pensylvania as Intern in
>>> Advanced Analytics.
>>>
>>>  In my work experience I worked on Integration of heterogeneous
>>> services, packaged and legacy applications (more than 20 applications)
>>> using Enterprise Service Bus, Web Services, and JMS queue. Our Continuous
>>> Integration stack (DevOps) included Jenkins, GIT, Chef Server and Nexus so
>>> I have good knowledge of these Tools. I am well versed in Java,
>>> SoftwarPython, XML and Docker technologies too. I have closely worked on
>>> each phase of Software development life cycle.
>>>
>>>  I always wanted to do open source contribution, my long-term goal is to
>>> become a contributor(Github) open source code. I think GSoC
>>> is good platform to start open source contribution where I will mentorship
>>> from experience open source contributor and will get chance interact with
>>> open source community which will be helpful for future contribution in open
>>> source.
>>>
>>> Jenkins caught my attention because I have used Jenkins before for
>>> Continuous Integration.I have gone through the detailed information of
>>> "Jenkins Remoting over Message Bus/Queue" project. I am particularly
>>> interested in "Jenkins Remoting over Message Bus/Queue" Because my previous
>>> work experience in Java, JMS queues will be helpful here and I will be able
>>> actively to contribute from day 1.
>>>
>>> You can find more information about me on below links,
>>> Linkedin: https://www.linkedin.com/in/amit-magar
>>> Github: https://github.com/AmitJMagar
>>>
>>> I would like to request mentors to give me some guidance here as well as
>>> in office hour to formulate a good proposal.
>>>
>>> Thanks and Regard,
>>> Amit Magar
>>>
>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/to
> pic/jenkinsci-dev/dMRn4zpSpkk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/jenkinsci-dev/9bc7adfe-b171-4767-822a-2c8ee3a6ac3e%40googlegroups.com
> 

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

[Pham Vu Tuan]

Hello,

I am trying to setup the master and agent in my local machine. Server setup 
is fine, I used https://hub.docker.com/r/jenkinsci/blueocean/. But when I 
tried to connect an agent to it using 
https://hub.docker.com/r/jenkins/jnlp-slave/ by this command "docker run 
jenkins/jnlp-slave -url http://localhost:8080 abcd test-node" , I 
encountered some problems:

- Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to 
alter the behavior => Athough I set the env variable in the docker 
container for the server, I still encountered this warning message, am I 
missing to set it somewhere?
- Not sure if this is related to the above issue, then I cannot connect the 
agent to server 

> SEVERE: Failed to connect to http://localhost:8080/tcpSlaveAgentListener/: 
> Connection refused (Connection refused)
> java.io.IOException: Failed to connect to 
> http://localhost:8080/tcpSlaveAgentListener/: Connection refused 
> (Connection refused)
> at 
> org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:199)
> at hudson.remoting.Engine.innerRun(Engine.java:518)
> at hudson.remoting.Engine.run(Engine.java:469)

Could someone help me with this setup issue?

Regards,
Pham Vu Tuan 

On Monday, March 5, 2018 at 12:31:29 AM UTC+8, Oleg Nenashev wrote:
>
> Hi all,
>
> Since we have several students interested in this project, I propose to 
> spend some time at office hours on Wednesday in order to discuss it.
>
> From what I see, everybody in this thread can attend during the 
> APAC/Europe timeslot, right? If yes, let's just talk about the project 
> there.
>
> BR, Oleg
>
> On Sunday, March 4, 2018 at 7:48:47 AM UTC+1, ajm...@g.rit.edu wrote:
>>
>> I am Amit Magar a graduate student pursuing masters in Computer Science 
>> from Rochester Institute of Technology. I am specializing in Computer 
>> Networks and Artificial Intelligence. I have 8 years formal education in 
>> Computer Science.
>>
>>  I have 3 years of professional works experience at Accenture. Currently, 
>> I am working at Genex Services, Pensylvania as Intern in Advanced Analytics.
>>
>>  In my work experience I worked on Integration of heterogeneous services, 
>> packaged and legacy applications (more than 20 applications) using 
>> Enterprise Service Bus, Web Services, and JMS queue. Our Continuous 
>> Integration stack (DevOps) included Jenkins, GIT, Chef Server and Nexus so 
>> I have good knowledge of these Tools. I am well versed in Java, 
>> SoftwarPython, XML and Docker technologies too. I have closely worked on 
>> each phase of Software development life cycle.
>>
>>  I always wanted to do open source contribution, my long-term goal is to 
>> become a contributor(Github) open source code. I think GSoC 
>> is good platform to start open source contribution where I will mentorship 
>> from experience open source contributor and will get chance interact with 
>> open source community which will be helpful for future contribution in open 
>> source.
>>
>> Jenkins caught my attention because I have used Jenkins before for 
>> Continuous Integration.I have gone through the detailed information of 
>> "Jenkins Remoting over Message Bus/Queue" project. I am particularly 
>> interested in "Jenkins Remoting over Message Bus/Queue" Because my previous 
>> work experience in Java, JMS queues will be helpful here and I will be able 
>> actively to contribute from day 1.
>>
>> You can find more information about me on below links,
>> Linkedin: https://www.linkedin.com/in/amit-magar
>> Github: https://github.com/AmitJMagar
>>
>> I would like to request mentors to give me some guidance here as well as 
>> in office hour to formulate a good proposal.
>>
>> Thanks and Regard,
>> Amit Magar
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9bc7adfe-b171-4767-822a-2c8ee3a6ac3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trademark sublicense request: CloudBees Jenkins Metrics

[Stephen Connolly]

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 maintainer of the plugin in order to apply my personal opinions 
to the same company.

In any case, as an employee of CloudBees, I feel I have to recuse myself 
from the debate.

On Thursday, 8 March 2018 12:46:22 UTC, Oleg Nenashev wrote:
>
> 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 product, it may cause some confusion.
>
> BR, Oleg
>
> On Wednesday, March 7, 2018 at 5:29:40 PM UTC+1, Kohsuke Kawaguchi wrote:
>>
>> On behalf of CloudBees, I’d like to request the permission to use the 
>> following name that uses ‘Jenkins’ in it:
>>
>>- CloudBees Jenkins Metrics
>>
>> To help people understand how this name is going to be used, let me 
>> describe a bit about the effort for which we’d like to use this name.
>>
>> Back several years ago, we have requested the sublicense to use 
>> ‘CloudBees Jenkins Analytics,’ which was subsequently approved 
>> . It 
>> is a feature that is a part of our products. It has evolved since then, and 
>> we’d like to give it a new name to more accurately reflect what it is. 
>>
>> When we look at name approval requests like this, a key criteria is to 
>> make sure it doesn’t create confusion about the origin of the effort. From 
>> that perspective, this name has ‘CloudBees’ clearly in front of it, and it 
>> is consistent with other names that are already approved. The situation and 
>> the considerations that led to the approval of the past requests hasn't 
>> really changed, so I hope the new name doesn’t raise any eyebrows and 
>> result in a smooth approval.
>>
>> I’ve put this up as an agenda for Mar 14th project meeting to be able to 
>> get a decision there. If you have any concerns or objections, please chime 
>> in on this thread prior to the meeting, so that we can address them.
>>
>> -- 
>> Kohsuke Kawaguchi
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a24547c6-32e1-4a75-9fc9-a1666ef8cf5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trademark sublicense request: CloudBees Jenkins Metrics

[Oleg Nenashev]

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 product, it may cause some confusion.

BR, Oleg

On Wednesday, March 7, 2018 at 5:29:40 PM UTC+1, Kohsuke Kawaguchi wrote:
>
> On behalf of CloudBees, I’d like to request the permission to use the 
> following name that uses ‘Jenkins’ in it:
>
>- CloudBees Jenkins Metrics
>
> To help people understand how this name is going to be used, let me 
> describe a bit about the effort for which we’d like to use this name.
>
> Back several years ago, we have requested the sublicense to use ‘CloudBees 
> Jenkins Analytics,’ which was subsequently approved 
> . It is 
> a feature that is a part of our products. It has evolved since then, and 
> we’d like to give it a new name to more accurately reflect what it is. 
>
> When we look at name approval requests like this, a key criteria is to 
> make sure it doesn’t create confusion about the origin of the effort. From 
> that perspective, this name has ‘CloudBees’ clearly in front of it, and it 
> is consistent with other names that are already approved. The situation and 
> the considerations that led to the approval of the past requests hasn't 
> really changed, so I hope the new name doesn’t raise any eyebrows and 
> result in a smooth approval.
>
> I’ve put this up as an agenda for Mar 14th project meeting to be able to 
> get a decision there. If you have any concerns or objections, please chime 
> in on this thread prior to the meeting, so that we can address them.
>
> -- 
> Kohsuke Kawaguchi
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3de27a86-1f9f-4c4c-82b6-00e5bf3e4219%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Query

[Oleg Nenashev]

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 proprietary 
   dependencies with incompatible licenses

BR, Oleg

On Thursday, March 8, 2018 at 11:49:23 AM UTC+1, Baptiste Mathus wrote:
>
> 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,
>> i want to host my plugin but i used Data table ,i was purchase it so can 
>> i host my plugin ?
>>
>> Thanks
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/6d9e4205-a8ee-4388-942c-dd1fc6573e02%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/771f5905-3524-4031-a6af-3075b43feef2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Query

[Baptiste Mathus]

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,
> i want to host my plugin but i used Data table ,i was purchase it so can i
> host my plugin ?
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/jenkinsci-dev/6d9e4205-a8ee-4388-942c-dd1fc6573e02%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6yaAWy8Tw0m1W3ioBdOJAxP4ACM7dNPObJ_ZkUK_QSvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Rajender Venkatpur]

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",
"password": "passwordToken",
"description": "Short decription of user",
"$class": 
"com.cloudbees.plugins.credentials.impl.UsernamePasswordCredentialsImpl"



Thank you
Rajender

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0b878208-ac7e-407f-9979-a829d9b238b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.