Re: commit access to scm-sync-configuration-plugin

[Ivan Kalinin]

Would be great for you to finally 
release https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/49

Also, +1 to to back Mr. Mavlyutov -- he's a good man and maintains stuff 
well.

On Thursday, December 8, 2016 at 3:14:27 PM UTC+3, Marat Mavlyutov wrote:
>
> Hi, there!
>
> I am interested in receiving commit access to maintain 
> scm-sync-configuration-plugin 
>  to address 
> [JENKINS-37500] (https://issues.jenkins-ci.org/browse/JENKINS-37500). 
> My GitHub account name is 'mavlyutov' and I am already maintainer/owner of 
> several plugins such as
> https://github.com/jenkinsci/debian-package-builder-plugin
> https://github.com/jenkinsci/allure-plugin
> https://github.com/jenkinsci/openstack-cloud-plugin
>
> Thank you for your assistance.
>
> --
> Marat Mavlyutov
>

-- 
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/4e220704-d9e5-4c60-a159-0a60f9341bdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Cloudbees] Access right to release a plugin I am developing

[Ivan Kalinin]

Folks, anyone?
At least a guide for "how do i use jenkins-on-jenkins in cloudbees"?

On Friday, October 23, 2015 at 7:47:10 PM UTC+3, Kanstantsin Shautsou wrote:
>
> There was somewhere thread about it... Can't find.
>
> On Friday, October 23, 2015 at 7:30:53 PM UTC+3, Ivan Kalinin wrote:
>>
>> Hi there, folks!
>>
>> I'm a mantainer for Debian package builder plugin, but I am unable to 
>> release it via Cloudbees.
>>
>> The job at 
>> https://jenkins.ci.cloudbees.com/job/plugins/job/debian-package-builder-plugin/
>>  
>> requires me to login to use Maven release feature, but neither my google 
>> account nor github one allows me to log in to that jenkins.
>>
>> What am I to do and how do I get access to that nice and shiny feature?
>>
>> Best regards,
>> Ivan Kalinin.
>>
>

-- 
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/6389173f-7be7-4f10-93ba-06960ea9dd76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Cloudbees] Access right to release a plugin I am developing

[Ivan Kalinin]

Hi there, folks!

I'm a mantainer for Debian package builder plugin, but I am unable to 
release it via Cloudbees.

The job at 
https://jenkins.ci.cloudbees.com/job/plugins/job/debian-package-builder-plugin/ 
requires me to login to use Maven release feature, but neither my google 
account nor github one allows me to log in to that jenkins.

What am I to do and how do I get access to that nice and shiny feature?

Best regards,
Ivan Kalinin.

-- 
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/a0acd096-848e-4a69-b108-b847cc1de308%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't get access to the release button of the debian-package-builder-plugin in cloudbees

[Ivan Kalinin]

But there is that fancy 'Release' button that performs mvn release on the 
plugin. Why is it there if a plugin owner cant uae it? 
I mean, the following workflow seema reasonable:
-- merge a PR
-- click tha button to release the plugin

Its generally useful to have possibility to release them changes without having 
to check out the source code and perform manual mvn operations.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Can't get access to the release button of the debian-package-builder-plugin in cloudbees

[Ivan Kalinin]

That job: 
https://jenkins.ci.cloudbees.com/job/plugins/job/debian-package-builder-plugin/

Either I do not have the permission or I am logging in wrong.
I've tried doing that with both google ID and github ID and all I can get 
is You are not authorized to use this Jenkins instance.

I assume I should have the described access since I'm a maintainer of that 
plugin.

Can plz someone help?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: Provision multiple instances of slaves with NodeProvisioner

[Ivan Kalinin]

Thumbs up for pluggable strategies!

Also, I volunteer to help if reasonable guidance is provided.

On Wednesday, July 16, 2014 6:24:31 PM UTC+4, Stephen Connolly wrote:

 idle is based on a long term average.

 There are two schools of thought when ramping up build resources.

 You can optimize for maximum resource utilization

 You can optimize for shortest waiting time

 You cannot do both at the same time.

 Since it is not instantaneous to start up a build node you can sometimes 
 get a faster build if you just wait for one of the existing builds to 
 complete... as a result firing up a build node for every job in the queue 
 will end up wasting resources.

 Similarly the decommissioning strategy is likely to leave build nodes 
 hanging around for a minute or two it would be good if we have some work 
 they could do rather than just throw them away.

 The default strategy in Jenkins is to try to maintain the build queue 
 length at approx the number of build nodes. (Yes this may shock you) In 
 other words Jenkins wants there always to be a job ready for each node when 
 it is finished its current work.

 That strategy will give the maximum utilization of resources with a 
 secondary minimum waiting time.

 I intend in the near future (once I complete getting the scalability 
 framework open sourced) to make the strategy plugable, thus allowing people 
 to, e.g.

 Provision nodes while there is a demand for them - which will minimize 
 waiting time at the expense of wasting resources

 At present the trick is to play with MARGIN and MARGIN0 and the decay rate 
 so that you get nodes provisioned faster in response to the exponentially 
 weighted average number of idle nodes changing... but be warned, adjusting 
 these values will cause idle nodes to get provisioned depending on the 
 build load.


 On 16 July 2014 15:00, yo...@ignissoft.com javascript: wrote:

 Hello,

 I'm writing a Jenkins Cloud plug-in that should work similar to EC2 
 plug-in.
 The sequence of events is as follows:
 1. Jenkins decides that there are not enough slaves to run jobs
 2. Jenkins access a private resource manager system to reserve and launch 
 test set-up. The resource manager returns an IP address of the test set-up
 3. Jenkins launches slave on the returned IP.
 4. The job is executed on the slave
 5. Once the job is completed Jenkins kills the slave and updates the 
 resouce manager that the set-up is free.

 I have extended Cloud, Slave, ComputerLauncher etc and I have a plugin 
 that does all of the above.
 However... Jenkins never provisions more than one slave from the resource 
 manager cloud.

 Looking into the code of NodeProvisioner.update, it seems that the 
 condition

 *if (idle  MARGIN || needSomeWhenNoneAtAll) {*Is never met once there 
 is one slave in the pool.

 When there are no slaves, *needSomeWhenNoneAtAll == true* and the *if* 
 clause is executed.
 When there is one slave, *needSomeWhenNoneAtAll == false* and i*dle  
 MARGIN* so the *if* clause is not executed.

 I've found out that MARGIN is set to 0.1 by default with the following 
 code:

 *private static final float MARGIN = 
 Integer.getInteger(NodeProvisioner.class.getName() + .MARGIN, 10) / 100f;*
 I've changed this line to 
 *private static final float MARGIN = 
 Integer.getInteger(NodeProvisioner.class.getName() + .MARGIN, 100) / 
 100f;*
 And forced *idle  MARGIN* so the *if* clause always gets executed and 
 Jenkins launches multiple slaves.


 *My questions are:*1. Why, by default, *MARGIN* is set to 0.1 so *idle  
 MARGIN* and Jenkins does not launch more than one slave?
 2. How can I change this default behaviour so Jenkins does not wait at 
 all? So as soon as it finds out there is awaiting job it will ask to 
 provision new slave?



 *Thanks,Yoram *

 -- 
 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 javascript:.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: Executing a shell/python command in Jenkins Dynamic Choice Parameter Plugin

[Ivan Kalinin]

Well, you can always try to fire a shell from the groovy script -- there 
seems to be a way to access current executor.

On Friday, July 18, 2014 5:41:28 PM UTC+4, Robert Parker wrote:

 I'd like to create a Jenkins job where I do a backup and deploy of certain 
 databases to a remote MongoDB instance. I'd like this build to be 
 parameterized so that at build time the user chooses from a list of valid 
 MongoDB hostnames and then once the user selects the valid DB hostname, a 
 second list parameter choice box will be dynamically populated with all 
 valid database names on that hostnames. Then once The user has selected the 
 DB name, that will be stored in a parameter DB that can be passed to a 
 Build Step Execute Shell script to do the actual work.

 My problem is that I need for a way to execute a script in the Jenkins 
 Dynamic Parameter (Cascading) Plug-in that will run a shell (or ideally, 
 python) script that will return a list of valid DB names on the selected 
 host. I'm not able to get groovy script portion of the plugin to execute 
 shell commands on the local OS (like theExecute Shell build step does).

 Ideally I'd like to run something like this where MONGOHOST is the first 
 parameter chosen by the user:

 #!/usr/bin/env pythonfrom pymongo import MongoClient
 client = MongoClient('mongodb://${MONGOHOST}:27017/')
 choicelist = client.database_names()
 client.close()

 I'd then like choicelist to be presented in such a way as they become 
 populated as the available choices for a DB parameter.

 How can I achieve this, especially since the Dynamic Choice parameter only 
 accepts groovy script and not native python?


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: Dynamic Provisioning of windows slaves using ssh

[Ivan Kalinin]

Hi there!

I belive you are not alone in the struggle of using SSH to windows slaves.
However, we do use vanilla SSHSlaves plugin for that and it works perfectly 
-- with regard to the paths part.

On Tuesday, June 17, 2014 3:44:08 AM UTC+4, Suresh Nallamilli wrote:

 Hi All,

  

 I am working on a sample plugin to dynamically provision windows slaves.

 Windows slave images are preconfigred with SSH server(cygwin openssh 
 server), 

 so after provionsing - machine comes up with ssh server installed.

  

 Once the slave is up , I am able to copy slave.jar and also able to 
 execute commands using ssh.

 However when I try to set the channel using below code – getting error 
 (see below stack trace)

 computer.setChannel(sess.getStdout(),sess.getStdin(),logger,new Listener() 
 {

 public void onClosed(Channel channel, IOException cause) {

 sess.close();

 conn.close();

   }

   });

  

  

 *Question:*

 1)  Is windows slaves launch supported via ssh? 

 What steps I need to take care to add ssh launch method support for 
 windows slaves?

  I am not seeing ssh support for windows slaves when adding node 
 manually , so wondering if this is supported or not?

  

 Stack Trace:

   java.io.EOFException: unexpected stream termination

 at 
 hudson.remoting.ClassicCommandTransport.create(ClassicCommandTransport.java:100)

 at hudson.remoting.Channel.init(Channel.java:392)

 at hudson.remoting.Channel.init(Channel.java:388)

 at hudson.remoting.Channel.init(Channel.java:349)

 at hudson.remoting.Channel.init(Channel.java:345)

  

  

 Thanks,

 Suresh Nallamilli.


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: Update center generation has been disabled

[Ivan Kalinin]

Ah, that's why our releases aren't showing up.

But what exact part of the update center generation causes load on 
Jira/Confluence? It looked like the job shouldn't mess a lot with it, just 
request each plugin's page once.

There are lots of com.atlassian.confluence.rpc.RemoteException: You're not 
allowed to view that page, or it does not exist. messages in the log for 
the pages that are generally publicly accessible. 

On Tuesday, May 27, 2014 2:41:42 AM UTC+4, R Tyler Croy wrote:

 See this ticket for more details 
 https://issues.jenkins-ci.org/browse/INFRA-70 


 I'm waiting to hear back from KK on how we can fix the update-center 
 generation 
 scripts from scraping/DoSing our JIRA instance before I re-enable the job. 



 - R. Tyler Croy 

 -- 
  Code: https://github.com/rtyler 
   Chatter: https://twitter.com/agentdero 

   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F 
 -- 


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: New Allure report publisher plugin

[Ivan Kalinin]

Can anybody handle this please? That's a good plugin!

On Wednesday, May 21, 2014 3:53:32 PM UTC+4, Denis Chernilevskiy wrote:

 Hello! 

 I'd like to publish our Allure report publisher plugin. 
 The plugin is currently hosted here: 
 https://github.com/allure-framework/allure-jenkins-plugin 
 My GitHub ID is dchr. 
 Please also add eroshenkoam, pupssman, vania-pooh, mavlyutov to 
 supporters list and give them commit rights.
 We're currently using it widely across our company and will present it at 
 a conference soon, so it would be great to get it published as soon as 
 possible.

 Thanks a lot in advance for your assistance! 

 P.S. Our company is already hosting a Debian package builder plugin and 
 maintaining JClouds plugin.  


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: mvn release does not work, only publishes SNAPSHOT releases

[Ivan Kalinin]

Hehehe. So there is no hope for fixing this ever?
At least, could you be so kind as to describe those neccessary changes that 
should fix the project layout? Like removing the extra depends/versions? Or 
separating the Jenkins pom from plugin 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.
For more options, visit https://groups.google.com/d/optout.

Re: mvn release does not work, only publishes SNAPSHOT releases

[Ivan Kalinin]

Have u got any patches / pull requests one can look at?

On Wednesday, May 14, 2014 1:26:24 PM UTC+4, Stephen Connolly wrote:

 Well I have long maintained that Jenkins's pom structure does it all 
 wrong but any time I have wanted to try and fix it *and* had a time window 
 to try, KK puts too much of a barrier with regard to people getting 
 confused.

 I guess it doesn't help that to fix it, I need to redo the hpi plugin so 
 that it actually works the Maven way... but then if the people who wrote 
 the original hpi plugin understood the Maven way they would never have 
 written the Maven project type in Jenkins the way they did and it would not 
 be evil!


 On 13 May 2014 23:46, Ivan Kalinin pups...@gmail.com javascript:wrote:

 Has similar problem recently and your fix did help. But latest parent (
 http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/jenkins/1.33/)
  
 still uses 2.2.2 -- is there any plan to fix that?


 On Saturday, March 8, 2014 11:05:15 PM UTC+4, Stephen Connolly wrote:

 mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare

 And if that tags correctly then same with perform. Should fix the 
 -SNAPSHOT issue... The other issue could be a different story

 On Saturday, 8 March 2014, Ulli Hafner ullrich...@gmail.com wrote:

 git version is 1.8.5.3

 The dependency hack does only work if the plugin is top-level. I’m 
 releasing in a sub-folder. 

 Am 08.03.2014 um 12:36 schrieb Stephen Connolly 
 stephen.alan.conno...@gmail.com:

 What version of git are you using?

 Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack

 On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com 
 wrote:

 Has someone a workaround for that problem if the plugin/libray to 
 release is not in the top-level folder of a git project?

 My findbugs plugin is divided into
 - findbugs-plugin/library shaded findbugs library
 - findbugs-plugin/plugin actual findbugs plugin

 When I try to release maven does only publish a SNAPSHOT.


 Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:

 That would be helpful, yes. 

 BTW: This fix does only work if the project is not in a sub-folder :-(

 Ulli

 Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:

 Should we pull a new release of 
 https://github.com/jenkinsci/pomincoporating the changes to the release 
 plugin configuration?

 Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:

 I hit that problem recently, adding

 plugin
   artifactIdmaven-release-plugin/artifactId
   version${maven-release-plugin.version}/version
   dependencies
 dependency
   groupIdorg.apache.maven.scm/groupId
   artifactIdmaven-scm-provider-gitexe/artifactId
   version1.9/version
 /dependency
   /dependencies
 /plugin

 was enough to work with latest git (1.8.5.2).

 HTH,

 Vincent


 2014/1/13 Dominik Bartholdi do...@fortysix.ch

 ;-)

 I’ll try to take a look at the m-r-p, but I currently can’t promise any 
 time - sorry :(
 /Domi


 On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com 
 wrote:



 On Sunday, 12 January 2014, Dominik Bartholdi wrote:

 The maven team 


 Nice dodge of self promotion there

 ;-)

 Btw do you want to take a run at m-r-p?
  

 has just release a git provider based on jgit, if you configure the 
 release plugin to use this one, then you don’t have to downgrade git.

 http://maven.apache.org/scm/maven-scm-providers/maven-scm-pr
 oviders-git/maven-scm-provider-jgit/index.html

 /Domi

 On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:

 I've just had this problem too, with two separate plugins.

 maven-release-plugin is just total crapola. Just do a manual mvn 
 versions:set and deploy.



 On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:

  To unsubscribe from this group and stop receiving emails from it, 
 send an email to jenkinsci-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




 -- 
 Sent from my phone

  -- 
 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 javascript:.
 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.
For more options, visit https://groups.google.com/d/optout.

nexus down or not responding

[Ivan Kalinin]

I'm getting problems releasing plugin via mvn release:prepare 
release:perform with 

Connection to http://maven.jenkins-ci.org:8081 refused: Connection timed out



Also, accessing http://maven.jenkins-ci.org:8081/ with browser fails, 
http://www.downforeveryoneorjustme.com/http://maven.jenkins-ci.org:8081/ 
reports that it is down.

So I've concluded that there is some kind of problem on the nexus side. Can 
anybody look into the issue?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: mvn release does not work, only publishes SNAPSHOT releases

[Ivan Kalinin]

Has similar problem recently and your fix did help. But latest parent 
(http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/jenkins/1.33/)
 
still uses 2.2.2 -- is there any plan to fix that?

On Saturday, March 8, 2014 11:05:15 PM UTC+4, Stephen Connolly wrote:

 mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare

 And if that tags correctly then same with perform. Should fix the 
 -SNAPSHOT issue... The other issue could be a different story

 On Saturday, 8 March 2014, Ulli Hafner ullrich...@gmail.com javascript: 
 wrote:

 git version is 1.8.5.3

 The dependency hack does only work if the plugin is top-level. I’m 
 releasing in a sub-folder. 

 Am 08.03.2014 um 12:36 schrieb Stephen Connolly 
 stephen.alan.conno...@gmail.com:

 What version of git are you using?

 Anything after 1.8.4 needs m-r-p 2.5 or the dependency hack

 On Saturday, 8 March 2014, Ulli Hafner ullrich.haf...@gmail.com wrote:

 Has someone a workaround for that problem if the plugin/libray to release 
 is not in the top-level folder of a git project?

 My findbugs plugin is divided into
 - findbugs-plugin/library shaded findbugs library
 - findbugs-plugin/plugin actual findbugs plugin

 When I try to release maven does only publish a SNAPSHOT.


 Am 11.02.2014 um 18:52 schrieb Ulli Hafner ullrich.haf...@gmail.com:

 That would be helpful, yes. 

 BTW: This fix does only work if the project is not in a sub-folder :-(

 Ulli

 Am 10.02.2014 um 23:16 schrieb Stefan Wolf glowwo...@gmail.com:

 Should we pull a new release of https://github.com/jenkinsci/pomincoporating 
 the changes to the release plugin configuration?

 Am Dienstag, 14. Januar 2014 17:47:35 UTC+1 schrieb Vincent Latombe:

 I hit that problem recently, adding

 plugin
   artifactIdmaven-release-plugin/artifactId
   version${maven-release-plugin.version}/version
   dependencies
 dependency
   groupIdorg.apache.maven.scm/groupId
   artifactIdmaven-scm-provider-gitexe/artifactId
   version1.9/version
 /dependency
   /dependencies
 /plugin

 was enough to work with latest git (1.8.5.2).

 HTH,

 Vincent


 2014/1/13 Dominik Bartholdi do...@fortysix.ch

 ;-)

 I’ll try to take a look at the m-r-p, but I currently can’t promise any 
 time - sorry :(
 /Domi


 On 13.01.2014, at 09:21, Stephen Connolly stephen.al...@gmail.com 
 wrote:



 On Sunday, 12 January 2014, Dominik Bartholdi wrote:

 The maven team 


 Nice dodge of self promotion there

 ;-)

 Btw do you want to take a run at m-r-p?
  

 has just release a git provider based on jgit, if you configure the 
 release plugin to use this one, then you don’t have to downgrade git.

 http://maven.apache.org/scm/maven-scm-providers/maven-scm-
 providers-git/maven-scm-provider-jgit/index.html

 /Domi

 On 12.01.2014, at 11:52, Nigel Magnay nigel.mag...@gmail.com wrote:

 I've just had this problem too, with two separate plugins.

 maven-release-plugin is just total crapola. Just do a manual mvn 
 versions:set and deploy.



 On Sat, Jan 4, 2014 at 4:17 PM, ogondza ogon...@gmail.com wrote:

  To unsubscribe from this group and stop receiving emails from it, send 
 an email to jenkinsci-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




 -- 
 Sent from my phone


-- 
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.
For more options, visit https://groups.google.com/d/optout.

ssh-agent, git publisher and build wrappers workflow

[Ivan Kalinin]

Hi, folks!

Recently SSH-Agent was updated to run before SCM scheckout and therefore 
became usable for the sake of git authentication.

However, there still is an issue with Git publisher. Due to general 
BuildWrappers' workflow in Free-style builds, BuildWrapper-produced 
Environment objects have their tearDown method called right after all the 
Builders finish for project (and before any Recorders/Notifiers are run). 
This makes impossible to use SSH-Agent for the sake of Git publisher (i.e. 
pushing changed branches to the master repository).

I've managed to create an ugly workaround (Recorder wrapper that runs 
BuildWrappers once again for a given recorder), but it does not look like a 
proper solution to me. Looks like the proper fix is to allow BuildWrapper 
effect extend upon the Publishers too, but it requires fix in the Jenkins 
core. 

Are there any other options? Maybe, there is already a plugin to solve this 
trouble?

Thanks in advance!

Best regards,
Ivan Kalinin.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Git plugin] Where in the code is the actual git merge command ?

[Ivan Kalinin]

Looks like it is here: 
https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L1160

On Saturday, July 6, 2013 1:46:56 AM UTC+4, michaelsdev wrote:

 Hi,

 Where in the code is the actual git merge command ?

 I could not find the place where it is executed.

 Thanks a lot

 Michael


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Modifying the computer list view with a plugin

[Ivan Kalinin]

Bump!

On Thursday, May 2, 2013 9:20:51 AM UTC+4, Marc MacIntyre wrote:

 I can't seem to find an extension point that allows modifying the way 
 computers are displayed in a list (in /computer); I see the ListView, but 
 that seems specific to the display of jobs.

 Do I have to create a completely new view to display the Computers in a 
 new way?  

 -- 
 Marc MacIntyre
  

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Request for commit access to debian-package-builder

[Ivan Kalinin]

Hi Sam!

Sorry for the long outage)

I am up to anything you prefer, but I belive a pull request from your repo 
would fit nicely.
I've got the idea of pbuilder, but what are those 'small workflow issues' 
you were about to address?

Best,
Ivan.

On Sunday, January 27, 2013 9:19:11 PM UTC+4, Sam Kottler wrote:

 Awesome, thanks for all your hard work!

 One of the main features I've added is the ability to use pbuilder (and 
 pdebuild) instead of just plain debuild. This is key because I'm building 
 around 1500 packages a day right now across dozens of slaves so having a 
 consistent base for build chroots via pbuilder is key. There are also a few 
 small workflow issues I've fixed that I would like to get upstream.

 What's the best workflow for you? I'm happy to just submit pull requests 
 or help maintain the plugin - totally your call.

 Thanks again,
 Sam

 On Sun, Jan 27, 2013 at 11:35 AM, Ivan Kalinin pups...@gmail.comjavascript:
  wrote:

 Hi, Sam!

 Its great to hear of your interest in that plugin!
 It happens that I am original developer of the thing and I'm glad to see 
 that it found some usage?
 Could you please tell what are the new features you are planning to add? 
 We are coming to the next iteration of the plugin development in a week or 
 two so we can cooperate a bit.
 Also, what is your deployment environment? What are you accomplishing 
 with the help of the plugin?

 Best regards,
 Ivan Kalinin.

 On Saturday, January 26, 2013 11:09:21 PM UTC+4, Sam Kottler wrote:

 Hi,

 Development seems to have become stagnant on the plugin and I'd like to 
 work on adding some features and fixing bugs I've come across with the 
 fairly large deployment I currently maintain.

 Thanks and let me know if you have any questions!

 -Sam

  -- 
  
  




-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Request for commit access to debian-package-builder

[Ivan Kalinin]

Hi, Sam!

Its great to hear of your interest in that plugin!
It happens that I am original developer of the thing and I'm glad to see 
that it found some usage?
Could you please tell what are the new features you are planning to add? We 
are coming to the next iteration of the plugin development in a week or two 
so we can cooperate a bit.
Also, what is your deployment environment? What are you accomplishing with 
the help of the plugin?

Best regards,
Ivan Kalinin.

On Saturday, January 26, 2013 11:09:21 PM UTC+4, Sam Kottler wrote:

 Hi,

 Development seems to have become stagnant on the plugin and I'd like to 
 work on adding some features and fixing bugs I've come across with the 
 fairly large deployment I currently maintain.

 Thanks and let me know if you have any questions!

 -Sam


-- 

Re: Query about running different job steps on different slaves

[Ivan Kalinin]

Hi there! 

So have u tried that thing? 
If its broken or something is missing I can try 2 fix that.

On Thursday, November 22, 2012 5:31:17 PM UTC+4, alok kumar wrote:

 Hey there,
 That would be great!! Can you please share it with me?
 Also, please let me know how to get it from github as I am new to this.

 Thanks a lot for the help.

 Alok

 On Thu, Nov 22, 2012 at 12:10 PM, Ivan Kalinin pups...@gmail.comjavascript:
  wrote:

 Hi!

 Actually, I've managed to develop a plugin for my own needs that 
 implements what you want. It allows to 'connect' a group of slaves to form 
 a so-called 'compound slave' - a virtual entity, proxying Slave.doBuild() 
 (or wassitsname) to a different subslave of the group. It adds a build step 
 'run something on a sub-node' to delegate particular build step to a 
 sub-slave. The plugin even can create 'compound' slaves on-the-fly as a 
 cloud provider from real slaves provisioned in some other cloud.

 If that sounds promising to you, I can share it on github (currently is 
 privately-hosted) and you can try to tweak it up to you needs.

 Cheers,
 pupssman.


 On Wednesday, November 21, 2012 6:18:29 PM UTC+4, alok kumar wrote:

 Hi,
 Can anyone let me know if it is possible to execute different build 
 steps on different slaves from within a single job?
 Is there any plugin that supports that? If not, what can be the 
 workaround to achieve the same?

 Any help would be greatly appreciated.

 Thanks,
 Alok

Re: Query about running different job steps on different slaves

[Ivan Kalinin]

Sure, here it is:
http://db.tt/reV8CziX

On Sunday, November 25, 2012 8:07:15 PM UTC+4, Jason Swager wrote:

 Having troubles getting a build environment built up.  Could you publish 
 the jpi so that it could be loaded directly into Jenkins?

 On Sunday, November 25, 2012 6:19:09 AM UTC-8, Ivan Kalinin wrote:

 Hi there! 

 So have u tried that thing? 
 If its broken or something is missing I can try 2 fix that.

 On Thursday, November 22, 2012 5:31:17 PM UTC+4, alok kumar wrote:

 Hey there,
 That would be great!! Can you please share it with me?
 Also, please let me know how to get it from github as I am new to this.

 Thanks a lot for the help.

 Alok

 On Thu, Nov 22, 2012 at 12:10 PM, Ivan Kalinin pups...@gmail.comwrote:

 Hi!

 Actually, I've managed to develop a plugin for my own needs that 
 implements what you want. It allows to 'connect' a group of slaves to form 
 a so-called 'compound slave' - a virtual entity, proxying Slave.doBuild() 
 (or wassitsname) to a different subslave of the group. It adds a build 
 step 
 'run something on a sub-node' to delegate particular build step to a 
 sub-slave. The plugin even can create 'compound' slaves on-the-fly as a 
 cloud provider from real slaves provisioned in some other cloud.

 If that sounds promising to you, I can share it on github (currently is 
 privately-hosted) and you can try to tweak it up to you needs.

 Cheers,
 pupssman.


 On Wednesday, November 21, 2012 6:18:29 PM UTC+4, alok kumar wrote:

 Hi,
 Can anyone let me know if it is possible to execute different build 
 steps on different slaves from within a single job?
 Is there any plugin that supports that? If not, what can be the 
 workaround to achieve the same?

 Any help would be greatly appreciated.

 Thanks,
 Alok

Re: Query about running different job steps on different slaves

[Ivan Kalinin]

Hi there again!

I managed to publish most of the plugin (without couple of still private 
plugin references) to the github over here:
https://github.com/pupssman/compound-slaves

If that builds and installs correctly, following stuff should happen:

   - there should be added Compound Slaves section to global config, 
   containing a configurable list of sub-slave roles
   - there should be a new slave creation option - Multi-node slave
   - and a new builder - Run something on a sub-node
   - and also a new cloud - CompoundCloud
   
All these configuration should be pretty self-explanatory (atleast, I hope 
so).

Any feedback and questions are greatly appreciated!

If the plugin is missing some features - start an issue in the tracker or 
create a pull request.

Best regards,
Ivan Kalinin.

On Thursday, November 22, 2012 5:31:17 PM UTC+4, alok kumar wrote:

 Hey there,
 That would be great!! Can you please share it with me?
 Also, please let me know how to get it from github as I am new to this.

 Thanks a lot for the help.

 Alok

 On Thu, Nov 22, 2012 at 12:10 PM, Ivan Kalinin pups...@gmail.comjavascript:
  wrote:

 Hi!

 Actually, I've managed to develop a plugin for my own needs that 
 implements what you want. It allows to 'connect' a group of slaves to form 
 a so-called 'compound slave' - a virtual entity, proxying Slave.doBuild() 
 (or wassitsname) to a different subslave of the group. It adds a build step 
 'run something on a sub-node' to delegate particular build step to a 
 sub-slave. The plugin even can create 'compound' slaves on-the-fly as a 
 cloud provider from real slaves provisioned in some other cloud.

 If that sounds promising to you, I can share it on github (currently is 
 privately-hosted) and you can try to tweak it up to you needs.

 Cheers,
 pupssman.


 On Wednesday, November 21, 2012 6:18:29 PM UTC+4, alok kumar wrote:

 Hi,
 Can anyone let me know if it is possible to execute different build 
 steps on different slaves from within a single job?
 Is there any plugin that supports that? If not, what can be the 
 workaround to achieve the same?

 Any help would be greatly appreciated.

 Thanks,
 Alok

Re: log4j version in jenkins.war is too old

[Ivan Kalinin]

Bump? Anyone?

On Wednesday, November 7, 2012 9:26:22 PM UTC+4, Ivan Kalinin wrote:

 Hi, people!

 I bumped into a problem with some third-party libraries (namely, 
 dasein-cloud-nimbula) that I am trying to use within a plugin. 
 The library depends on log4j version no less than 1.2.15, but jenkins.war 
 contains 1.2.9 that has classpath precedence over one supplied in plugin 
 (or I guess so).
 That conflict causes *java.lang.NoSuchMethodError: 
 org.apache.log4j.Logger.isTraceEnabled()Z* errors due to the method 
 absent in 1.2.9.

 mvn depency:tree points that log4j dependency comes from a *
 org.acegisecurity.acegi-security* dependency in core/pom.xml, put pom for 
 the acegi-security contains no version specification in log4j dependency. see 
 herehttp://repo1.maven.org/maven2/org/acegisecurity/acegi-security/1.0.5/acegi-security-1.0.5.pom

 My questions are:

1. can log4j in Jenkins be promoted to the latest version? If so, I 
could create a pull request as soon as someone points me the way to do it.
2. how can I override that dependency problem in my plugin's pom.xml? 
Maybe, thats not a problem at all.

 Testbed that gives me the error is *mvn hpi:run* in my plugin dev 
 project. 

 TY for any help or hints.

log4j version in jenkins.war is too old

[Ivan Kalinin]

Hi, people!

I bumped into a problem with some third-party libraries (namely, 
dasein-cloud-nimbula) that I am trying to use within a plugin. 
The library depends on log4j version no less than 1.2.15, but jenkins.war 
contains 1.2.9 that has classpath precedence over one supplied in plugin 
(or I guess so).
That conflict causes *java.lang.NoSuchMethodError: 
org.apache.log4j.Logger.isTraceEnabled()Z* errors due to the method absent 
in 1.2.9.

mvn depency:tree points that log4j dependency comes from a *
org.acegisecurity.acegi-security* dependency in core/pom.xml, put pom for 
the acegi-security contains no version specification in log4j dependency. see 
herehttp://repo1.maven.org/maven2/org/acegisecurity/acegi-security/1.0.5/acegi-security-1.0.5.pom

My questions are:

   1. can log4j in Jenkins be promoted to the latest version? If so, I 
   could create a pull request as soon as someone points me the way to do it.
   2. how can I override that dependency problem in my plugin's pom.xml? 
   Maybe, thats not a problem at all.

Testbed that gives me the error is *mvn hpi:run* in my plugin dev project. 

TY for any help or hints.

Re: accessing VCS credentials from inside a Builder

[Ivan Kalinin]

Hi there!

What particularly are you trying to accomplish?
To get SVN credentials to use with the SVNKit, you can try to do as follows:

hudson.scm.SubversionSCM.DescriptorImpl descriptor = 
(hudson.scm.SubversionSCM.DescriptorImpl) 
Jenkins.getInstance().getDescriptor(hudson.scm.SubversionSCM.class);
ISVNAuthenticationProvider authenticationProvider = 
descriptor.createAuthenticationProvider(build.getProject());


And use the authenticationProvider with SVNKit stuff.

On Thursday, November 1, 2012 1:35:15 PM UTC+4, Michael Hüttermann wrote:

 Hello, 

 in a Builder, how can I access the Subversion credentials that are used to 
 access the Subversion repository for checkout of code? 


 Thank you. 


 Best regards 
 Michael 

New plugin - debian package builder

[Ivan Kalinin]

Hello! I would like to contribute a plugin to the community – a debian 
package builder tool. It's created to analyze, build and publish debian 
packages.

My github id is *pupssman*, the plugin is at 
https://github.com/pupssman/debian-package-builder

Best,
Ivan Kalinin.