Re: Looking for a new maintainer for the git-parameter plugin

2016-02-21 Thread Niklaus Giger
Hi Hi Bogusław

I would like to thank you very much for your offer to take over the 
maintainership for the git-parameter plugin.

For some unkown reason, my previous anwer to acknowlege did not get posted 
earlier.

I wish you good luck. If you have any question, I will try to answer them.

Best regards 

Niklaus

Am Montag, 7. Dezember 2015 22:13:00 UTC+1 schrieb Bogusław KLimas:
>
> Hi everyone,
>
> In recent days I wrote to Nicholas, on this subject. And I have approval 
> from him :)
> I think I can be maintainer of the plugin, of course, if you do not mind.
> One of pull request is my. 
>
> I want to start working in the open source world :) I think this is good 
> start.
>
> Best regards
>
> Boguslaw Klimas
>
> W dniu czwartek, 3 grudnia 2015 21:31:15 UTC+1 użytkownik Daniel Beck 
> napisał:
>>
>> I added the adopt-a-plugin label to the wiki page to make this more 
>> visible. 
>>
>> https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin 
>>
>> On 03.12.2015, at 20:30, Niklaus Giger <niklau...@gmail.com> wrote: 
>>
>> > Hi 
>> > 
>> > I adapted the git-parameter plugin as I neeeded some fixes for my paid 
>> work and thanks to the wonders of Free Software I was able to solve my 
>> problems and Jenkins still is an important part for our workflow for our 
>> OpenSource project, see https://srv.elexis.info/jenkins/. 
>> > 
>> > I have however overestimated my time budget and did not find any time 
>> at all to invest the needed hours to merge the open pull request, improve 
>> the test (there are a quite a few uncovered area). Therefore I added as a 
>> known limitiation in the wiki that it needs a new maintainer. 
>> > 
>> > Therefore I would really appreciate if somebody could step in, over 
>> 6000 users would appreciate it! If you need assistance for this part, I 
>> will try to do my best to help you. 
>> > 
>> > There are 10 open issues and 6 pull requests. 
>> > 
>> > Man thanks to all Jenkins developpers who contributed to a fine piece 
>> of software! 
>> > 
>> > Best regards 
>> > 
>> > Niklaus Giger 
>> > 
>> > 
>> > 
>> > -- 
>> > 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/33ec008e-9ebb-4adf-a399-a22a4b67025f%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/a2def2c3-124b-449d-a8c4-4a152a4a0858%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Looking for a new maintainer for the git-parameter plugin

2015-12-03 Thread Niklaus Giger
Hi

I adapted the git-parameter plugin as I neeeded some fixes for my paid work 
and thanks to the wonders of Free Software I was able to solve my problems 
and Jenkins still is an important part for our workflow for our OpenSource 
project, see https://srv.elexis.info/jenkins/.

I have however overestimated my time budget and did not find any time at 
all to invest the needed hours to merge the open pull request, improve the 
test (there are a quite a few uncovered area). Therefore I added as a known 
limitiation in the wiki that it needs a new maintainer.

Therefore I would really appreciate if somebody could step in, over 6000 
users would appreciate it! If you need assistance for this part, I will try 
to do my best to help you.

There are 10 open issues and 6 pull requests.

Man thanks to all Jenkins developpers who contributed to a fine piece of 
software!

Best regards

Niklaus Giger


-- 
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/33ec008e-9ebb-4adf-a399-a22a4b67025f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


git-parameter-plugin 0.3.2 released

2014-05-15 Thread Niklaus Giger
Hi

I am happy to announce that finally after more than two years we have a new 
version of the git-parameter plugin available.

As the previous maintainer Lukanus did not have time to work on this plugin 
I took over the work for the time being, but am happy that I could skype 
with him. It looks as he is interested in adding more features in the 
months to come.

New user visible feature are (see also 
https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin) are:

   - Updated help texts for configuration and when selecting your 
   tag/revision
   - Runs a fetch each time the user enters the Build with parameter.
   - Run clone when fetch fails on workspace empty (Gabor Liptak)
   - Merging SortMode from graeme-hill
   - With an empty workspace the tags are calculated after we made a 
   checkout. This may take a long time.

Changes relevant to developer

   - Added MIT-LICENSE.txt to use the same license as Jenkins-CI.
   - Added Contributors.textile
   - Display month not minutes in date. Add HH.mm. Display only first 8 
   chars of SHA1 (Niklaus Giger)
   - Add backup pluginRepository (Gabor Liptak)
   - Use GitTool to query configured location of the git executable 
   (gliptak)
   - Upgrade to git 2.2.0. (christ66)
   - Build against latest stable Jenkins-CI version 1.554.1
   - New co-maintainer/developer Niklaus Giger (id ngiger)
   - Version 0.3 and 0.3.1 never made it to the distribution, because of 
   problems with the release mechanism

I burned versions 0.3 and 0.3.1 because

   - I had an old jenkins-ci id ngiger via ngiger at java.net I forgot it 
   did exist.
   - using git/ssh in developerConnection did not work. scm:git:https works 
   fine for me
   - mvn release:prepare release:perform did not work. Finally I used mvn 
   deploy; mvn release:clean + adding -SNAPSHOT to version in pom.xml.

Thanks to everybody who helped me, especially for those who had their 
patches laying around for years.

It would be nice if you gave this version a chance!

Best regards

Niklaus


-- 
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: git-parameter-plugin 0.3.2 released

2014-05-15 Thread Niklaus Giger
Hi Jesse

Thanks for your feedback. Some comment of mine is inline.

Am Donnerstag, 15. Mai 2014 17:34:29 UTC+2 schrieb Jesse Glick:

 On Thu, May 15, 2014 at 3:24 AM, Niklaus Giger 
 niklau...@gmail.comjavascript: 
 wrote: 
  Runs a fetch each time the user enters the Build with parameter. 

 Why would you not just use ‘git ls-remote -t’ and avoid the need for 
 any local clone? 


There are two ways to use git-parameter. One using tags and one using 
commit-ids. git ls-remote works only with tags and is currently not 
supported by git-plugin. It is on my TODO list.
 

  Added MIT-LICENSE.txt to use the same license as Jenkins-CI. 

 BTW it suffices to specify licenses in the POM. 

Thanks for the hint. I was unsure about it. I will remove the MIT-LICENSE
for the next release. 


 Also your POM has a lot of redundant info that you get for free from 
 the plugin parent POM. No distributionManagement is necessary, for 
 example. Nor do you need to declare the dependency on jenkins-core, or 
 the source level, or the encoding. I have improved the plugin 
 archetype POM to show the minimal recommended stuff: 


 https://github.com/jenkinsci/maven-hpi-plugin/blob/master/hpi-archetype/pom.xml
  

Thanks. Will be fixed in the next relase
 

  using git/ssh in developerConnection did not work. scm:git:https works 
 fine 
  for me 
  mvn release:prepare release:perform did not work. Finally I used mvn 
 deploy; 
  mvn release:clean + adding -SNAPSHOT to version in pom.xml. 

 Yuck. When your local settings are configured properly, normal 
 release:{prepare,perform} with SSH developerConnection should work 
 fine. So you were probably missing an SSH private key, or were using a 
 version of Git unsupported by the default version of the Release 
 plugin, etc.  


Yeah, but a newbie like me can get very confused about it!
 

 IMO we need to stop making (or even letting!) developers run plugin 
 releases locally. Better to use Jenkins for this. I do not really 
 trust the M2Release plugin but perhaps there can be a parallel set of 
 plugin release jobs that use a plain Maven build step. The main issue 
 is how to give broad enough access to let these jobs be triggered by 
 anyone able to push to the GH repo, without letting anonymous users do 
 it. (Maybe a special parameter type which redirects you in an iframe 
 to github.com to log in, grabs a temporary API token, then passes this 
 to the build long enough to authenticate the release?) 


That would be fine for me and would certainly lower the barrier for 
newcomers, 
if triggering such a build would be easy, e.g. by pushing a version tag to 
the 
git repository.
 

-- 
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: Problem releasing git-parameter-plugin. Banned? Or problem pushing tag?

2014-05-14 Thread Niklaus Giger
Hi Björn

Thanks for your tip. This did not resolve my problem.

But as suggested in 
https://groups.google.com/forum/#!msg/jenkinsci-dev/OvWw0zqJI_E/-1PvLg_DeYkJ 
I switched from using ssh/git to https. 

And now pushing to github works.

mvn release:prepare release:perform  reports now success (after several 
hours) but my build does not show up. Will report this problem in separate 
thread.

Thanks for your help!

Best regards

Niklaus

Am Montag, 12. Mai 2014 22:34:52 UTC+2 schrieb Björn Berg:

 Hi Niklaus,

 I had the same problem months ago. You cannot use the environment 
 variables -Dusername and -Dpassword any longer while releasing a plugin.

 Edit your Maven settings.xml and add a new server section to it:
 server
 idmaven.jenkins-ci.org/id
  usernameniklaus_giger/username
  passwordcleartext_pw/password
  /server

 See https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins (section 
 Releasing to jenkins-ci.org) for more details on how to modify your 
 settings.xml.

 Kind regards
 Björn

 Am 11.05.2014 um 17:14 schrieb Niklaus Giger niklau...@gmail.comjavascript:
 :

 Hi

 I am trying to release my first jenkins plugin. I successfully pushed all 
 my changes to https://github.com/jenkinsci/git-parameter-plugin

 Calling 
 mvn release:prepare release:perform -Dusername=niklaus_giger 
 -Dpassword=cleartext_pw
 always resulted in 
 [INFO] Scanning for projects...
 [INFO]
  

 [INFO] 
 
 [INFO] Building Git Parameter Plug-In 0.3
 [INFO] 
 
 [INFO] 
 [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ 
 git-parameter ---
 [INFO] Resuming release from phase 'scm-tag'
 [INFO] Tagging release with the label git-parameter-0.3...
 [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci  git 
 tag -F /tmp/maven-scm-790953102.commit git-parameter-0.3
 [INFO] Working directory: /opt/src/git-parameter.jenkins.ci
 [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci  git 
 push 
 ssh://niklaus_giger:cleartext...@github.com:jenkinsci/git-parameter-plugin.gitgit-parameter-0.3
 [INFO] Working directory: /opt/src/git-parameter.jenkins.ci
 [INFO]
  

 [INFO] 
 
 [INFO] Skipping Git Parameter Plug-In
 [INFO] This project has been banned from the build due to previous 
 failures.
 [INFO] 
 

 Can anybody tell me why this plugin is banned or whether I must (and then 
 how) resolve the push problem.

 Best regards in advance.

 Niklaus Giger

 P.S. The pom.xml already defines 0.3 (instead of 0.3-SNAPSHOT) as version, 
 as I corrected a few things in the pom.xml.


 -- 
 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: Problem releasing git-parameter-plugin. Banned? Or problem pushing tag?

2014-05-14 Thread Niklaus Giger
Hi Björn

After researching more in this list, I remarked that I am not the only one 
having problems.

Updating the pom.xml to allow  mvn-release-plugin:2.5 did not help.

After burning version 0.3 and 0.3.1 I was able to push using 
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare (killed when 
taking too long)
mvn deploy

Now I just have to update the version in my pom.xml to SNAPSHOT if the 
plugin really shows up in a few hours.

Best regards

Niklaus

Am Mittwoch, 14. Mai 2014 19:40:56 UTC+2 schrieb Niklaus Giger:

 Hi Björn

 Thanks for your tip. This did not resolve my problem.

 But as suggested in 
 https://groups.google.com/forum/#!msg/jenkinsci-dev/OvWw0zqJI_E/-1PvLg_DeYkJI 
 switched from using ssh/git to https. 

 And now pushing to github works.

 mvn release:prepare release:perform  reports now success (after several 
 hours) but my build does not show up. Will report this problem in separate 
 thread.

 Thanks for your help!

 Best regards

 Niklaus

 Am Montag, 12. Mai 2014 22:34:52 UTC+2 schrieb Björn Berg:

 Hi Niklaus,

 I had the same problem months ago. You cannot use the environment 
 variables -Dusername and -Dpassword any longer while releasing a plugin.

 Edit your Maven settings.xml and add a new server section to it:
 server
 idmaven.jenkins-ci.org/id
  usernameniklaus_giger/username
  passwordcleartext_pw/password
  /server

 See https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins (section 
 Releasing to jenkins-ci.org) for more details on how to modify your 
 settings.xml.

 Kind regards
 Björn

 Am 11.05.2014 um 17:14 schrieb Niklaus Giger niklau...@gmail.com:

 Hi

 I am trying to release my first jenkins plugin. I successfully pushed all 
 my changes to https://github.com/jenkinsci/git-parameter-plugin

 Calling 
 mvn release:prepare release:perform -Dusername=niklaus_giger 
 -Dpassword=cleartext_pw
 always resulted in 
 [INFO] Scanning for projects...
 [INFO]   
   

 [INFO] 
 
 [INFO] Building Git Parameter Plug-In 0.3
 [INFO] 
 
 [INFO] 
 [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ 
 git-parameter ---
 [INFO] Resuming release from phase 'scm-tag'
 [INFO] Tagging release with the label git-parameter-0.3...
 [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci  git 
 tag -F /tmp/maven-scm-790953102.commit git-parameter-0.3
 [INFO] Working directory: /opt/src/git-parameter.jenkins.ci
 [INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci  git 
 push 
 ssh://niklaus_giger:cleartext...@github.com:jenkinsci/git-parameter-plugin.gitgit-parameter-0.3
 [INFO] Working directory: /opt/src/git-parameter.jenkins.ci
 [INFO]   
   

 [INFO] 
 
 [INFO] Skipping Git Parameter Plug-In
 [INFO] This project has been banned from the build due to previous 
 failures.
 [INFO] 
 

 Can anybody tell me why this plugin is banned or whether I must (and then 
 how) resolve the push problem.

 Best regards in advance.

 Niklaus Giger

 P.S. The pom.xml already defines 0.3 (instead of 0.3-SNAPSHOT) as 
 version, as I corrected a few things in the pom.xml.


 -- 
 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.
 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.


Problem releasing git-parameter-plugin. Banned? Or problem pushing tag?

2014-05-11 Thread Niklaus Giger
Hi

I am trying to release my first jenkins plugin. I successfully pushed all 
my changes to https://github.com/jenkinsci/git-parameter-plugin

Calling 
mvn release:prepare release:perform -Dusername=niklaus_giger 
-Dpassword=cleartext_pw
always resulted in 
[INFO] Scanning for projects...
[INFO] 

[INFO] 

[INFO] Building Git Parameter Plug-In 0.3
[INFO] 

[INFO] 
[INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @ git-parameter 
---
[INFO] Resuming release from phase 'scm-tag'
[INFO] Tagging release with the label git-parameter-0.3...
[INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci  git 
tag -F /tmp/maven-scm-790953102.commit git-parameter-0.3
[INFO] Working directory: /opt/src/git-parameter.jenkins.ci
[INFO] Executing: /bin/sh -c cd /opt/src/git-parameter.jenkins.ci  git 
push 
ssh://niklaus_giger:cleartext...@github.com:jenkinsci/git-parameter-plugin.git 
git-parameter-0.3
[INFO] Working directory: /opt/src/git-parameter.jenkins.ci
[INFO] 

[INFO] 

[INFO] Skipping Git Parameter Plug-In
[INFO] This project has been banned from the build due to previous failures.
[INFO] 


Can anybody tell me why this plugin is banned or whether I must (and then 
how) resolve the push problem.

Best regards in advance.

Niklaus Giger

P.S. The pom.xml already defines 0.3 (instead of 0.3-SNAPSHOT) as version, 
as I corrected a few things in the pom.xml.

-- 
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.


How to get listing of remote tags if no workspace is present?

2014-05-03 Thread Niklaus Giger
Hi

I am trying to fix an issue with the git-parameter plugin (using 
https://github.com/jenkinsci/git-parameter-plugin/tree/preview_0_3).

Listing/sorting the tags work fine if I have a workspace. After deleting 
the workspace the tags are no longer listed an I find the following error 
in my jenkins.log
Caused by: hudson.plugins.git.GitException: Error retrieving tag names
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getTagNames(CliGitAPIImpl.java:1699)
at 
net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:316)
at 
net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.getTagMap(GitParameterDefinition.java:366)
... 163 more
Caused by: hudson.plugins.git.GitException: Error performing command: git 
tag -l J-E3C*
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1283)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1253)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1249)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getTagNames(CliGitAPIImpl.java:1688)
... 165 more
Caused by: java.io.IOException: Cannot run program git (in directory 
/home/jenkins/jobs/Elexis-3.0-Core-Releases/workspace): error=2, No such 
file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
at hudson.Proc$LocalProc.init(Proc.java:244)
at hudson.Proc$LocalProc.init(Proc.java:216)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:773)
at hudson.Launcher$ProcStarter.start(Launcher.java:353)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1272)

How should I resolve this problem?  Create an empty 
/home/jenkins/jobs/Elexis-3.0-Core-Releases/workspace directory? With which 
API? Or create and cd to a temporary directory?

I would be thankful if you could give a hint to the Jenkins newbie I am.

Thanks in advance.

Niklaus


-- 
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: git-parameter plugin

2014-05-03 Thread Niklaus Giger
I pushed the most important changes to 
https://github.com/jenkinsci/git-parameter-plugin/tree/preview_0_3 and 
found via the git commits the email of the old maintainer (cc this message, 
too). I will give him a few days (lets say till next Friday) to answer. If 
not I will merge the branch preview_0_3 into master and release it.

I have not yet found a solution to the problem that no tags are shown when 
there is no (or not yet) a workspace available.

Best regards

Niklaus

Am Samstag, 3. Mai 2014 11:52:25 UTC+2 schrieb Ullrich Hafner:


 Am 02.05.2014 um 16:59 schrieb Niklaus Giger niklau...@gmail.comjavascript:
 :

 Hi Ulli

 Thanks for your confidence in me. On wiki.jenkins-ci.org I added myself 
 some time ago as niklaus_giger.

 I did not find an email for the maintainer (lukanus) neither.

 Thanks for the access rights. I would appreciate if you could answer the 
 following questions for which I could not
 find an answer in 
 https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins.

 * Did you review my changes? I would really appreciate if somebody could 
 review the plugin. Specially a some days later before publishing.


 I do not. You can ask for feedback on the dev-list, maybe someone else 
 will. But normally the spare time of the developers is quite limited so 
 they focus on their own work...

 * Shall I push my changes directly to the master branch of 
 jenkins-ci/git-parameter or open a branch there?


 This is your decision. Some developers always use feature branches, some 
 others commit directly to master… 

 * Is it a good idea to change the connection developerConnection elements 
 in pom.xml to use jenkinsci instead of lukanus?


 Yes, please update the pom

 * Should I copy the description of the 
 https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin to the 
 Readme of the code?


 Yes, a README would be good that contains some more information…

 Ulli

 Thanks in advance

 Niklaus Giger

 Am Donnerstag, 1. Mai 2014 22:14:17 UTC+2 schrieb Ullrich Hafner:

 I also think this plugin is not maintained anymore… So feel free to 
 integrate your changes and take over the development. 
 I did not find an email of the maintainer so if he is reading this list 
 he still can object to taking over the plugin development.

 Your access rights are all set. Welcome aboard!

 Should I also set your name as default assignee in Jira? What is your 
 Jenkins ID?

 Ulli 

 Am 01.05.2014 um 21:59 schrieb Niklaus Giger niklau...@gmail.com:

 Hi everybody

 I am long-time and happy user of Jenkins. Since a few years Jenkins (and 
 before Hudson) is a tool I use
 almost daily. I almost always found the plugins I needed and investing 
 once 100US$ via 
 freedomsponsors.org fixed a memory problem for me.

 Lately I needed for paid work the features provided by git-parameter. I 
 had to invest half a day to
 made it work and I would be willing to take over this (almost) dormant 
 plugin.

 I collected the following interesting points about it:

- The https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Pluginhas 
  3500 installations.
- Last version was 0.2 as of December 2012
- Old ( 2 years) open pull requests under 
https://github.com/lukanus/git-parameter/pulls
- 2 commits in 2014 under 
https://github.com/lukanus/git-parameter/commits/master
- 34 forks
- about 5 people having pushed back changes in their fork
- But no new version
- Sorting/filtering in via 

 https://github.com/graeme-hill/git-parameter/commit/92af536d617cc88684dfa48dd19ea354db2a136f
- My work is under https://github.com/ngiger/git-parameter

 I am willing to work on this plugin and would appreciate any comments on 
 how I can achieve it. A simple pull
 request will not suffice, as also under 
 https://github.com/jenkinsci/git-parameter-plugin/pulls you severals 
 which are
 open for over 2 years.

 Best regards

 Niklaus

 -- 
 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.
 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-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: git-parameter plugin

2014-05-02 Thread Niklaus Giger
Hi Ulli

Thanks for your confidence in me. On wiki.jenkins-ci.org I added myself 
some time ago as niklaus_giger.

I did not find an email for the maintainer (lukanus) neither.

Thanks for the access rights. I would appreciate if you could answer the 
following questions for which I could not
find an answer in 
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins.

* Did you review my changes? I would really appreciate if somebody could 
review the plugin. Specially a some days later before publishing.
* Shall I push my changes directly to the master branch of 
jenkins-ci/git-parameter or open a branch there?
* Is it a good idea to change the connection developerConnection elements 
in pom.xml to use jenkinsci instead of lukanus?
* Should I copy the description of the 
https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin to the 
Readme of the code?

Thanks in advance

Niklaus Giger

Am Donnerstag, 1. Mai 2014 22:14:17 UTC+2 schrieb Ullrich Hafner:

 I also think this plugin is not maintained anymore… So feel free to 
 integrate your changes and take over the development. 
 I did not find an email of the maintainer so if he is reading this list he 
 still can object to taking over the plugin development.

 Your access rights are all set. Welcome aboard!

 Should I also set your name as default assignee in Jira? What is your 
 Jenkins ID?

 Ulli 

 Am 01.05.2014 um 21:59 schrieb Niklaus Giger niklau...@gmail.comjavascript:
 :

 Hi everybody

 I am long-time and happy user of Jenkins. Since a few years Jenkins (and 
 before Hudson) is a tool I use
 almost daily. I almost always found the plugins I needed and investing 
 once 100US$ via 
 freedomsponsors.org fixed a memory problem for me.

 Lately I needed for paid work the features provided by git-parameter. I 
 had to invest half a day to
 made it work and I would be willing to take over this (almost) dormant 
 plugin.

 I collected the following interesting points about it:

- The https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Pluginhas 
  3500 installations.
- Last version was 0.2 as of December 2012
- Old ( 2 years) open pull requests under 
https://github.com/lukanus/git-parameter/pulls
- 2 commits in 2014 under 
https://github.com/lukanus/git-parameter/commits/master
- 34 forks
- about 5 people having pushed back changes in their fork
- But no new version
- Sorting/filtering in via 

 https://github.com/graeme-hill/git-parameter/commit/92af536d617cc88684dfa48dd19ea354db2a136f
- My work is under https://github.com/ngiger/git-parameter

 I am willing to work on this plugin and would appreciate any comments on 
 how I can achieve it. A simple pull
 request will not suffice, as also under 
 https://github.com/jenkinsci/git-parameter-plugin/pulls you severals 
 which are
 open for over 2 years.

 Best regards

 Niklaus

 -- 
 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.


git-parameter plugin

2014-05-01 Thread Niklaus Giger
Hi everybody

I am long-time and happy user of Jenkins. Since a few years Jenkins (and 
before Hudson) is a tool I use
almost daily. I almost always found the plugins I needed and investing once 
100US$ via 
freedomsponsors.org fixed a memory problem for me.

Lately I needed for paid work the features provided by git-parameter. I had 
to invest half a day to
made it work and I would be willing to take over this (almost) dormant 
plugin.

I collected the following interesting points about it:

   - The https://wiki.jenkins-ci.org/display/JENKINS/Git+Parameter+Plugin 
   has  3500 installations.
   - Last version was 0.2 as of December 2012
   - Old ( 2 years) open pull requests under 
   https://github.com/lukanus/git-parameter/pulls
   - 2 commits in 2014 under 
   https://github.com/lukanus/git-parameter/commits/master
   - 34 forks
   - about 5 people having pushed back changes in their fork
   - But no new version
   - Sorting/filtering in via 
   
https://github.com/graeme-hill/git-parameter/commit/92af536d617cc88684dfa48dd19ea354db2a136f
   - My work is under https://github.com/ngiger/git-parameter
   
I am willing to work on this plugin and would appreciate any comments on 
how I can achieve it. A simple pull
request will not suffice, as also under 
https://github.com/jenkinsci/git-parameter-plugin/pulls you severals which 
are
open for over 2 years.

Best regards

Niklaus

-- 
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.