date:20150527

RE: Request for Commit Access to SSH-Plugin

2015-05-27 Thread John Tatum

Sorry I missed your replys.


Thank you for taking care of this for me,

John Tatum
john.ta...@live.com
http://scientifichooliganism.net

Although this e-mail and any attachments are believed to be free of any virus 
or other defect that might affect any computer system into which it is received 
and/or upon which it is opened, it is the responsibility of the recipient(s) to 
ensure that it is virus and/or defect free and John Tatum bears no 
responsibility for any loss and/or damage arising in any way from its use.

> Date: Wed, 27 May 2015 14:14:34 +0200
> From: ch...@orr.me.uk
> To: jenkinsci-dev@googlegroups.com
> Subject: Re: Request for Commit Access to SSH-Plugin
> 
> I believe I replied to you a couple of times on IRC, but I guess we 
> missed each other.
> 
> You should now have access.
> 
> Regards,
> Chris
> 
> 
> On 27/05/15 05:36, John Tatum wrote:
> > I reached out to Jesse Glick about this, and he recommended I send a
> > reminder to the list. I am still looking for anybody who can help me out
> > with this.
> >
> >
> > Thank You,
> >
> > John Tatum
> > john.ta...@live.com
> > http://scientifichooliganism.net
> >
> > Although this e-mail and any attachments are believed to be free of any
> > virus or other defect that might affect any computer system into which
> > it is received and/or upon which it is opened, it is the responsibility
> > of the recipient(s) to ensure that it is virus and/or defect free and
> > John Tatum bears no responsibility for any loss and/or damage arising in
> > any way from its use.
> >
> > 
> > From: john.ta...@live.com
> > To: jenkinsci-dev@googlegroups.com
> > Subject: RE: Request for Commit Access to SSH-Plugin
> > Date: Wed, 20 May 2015 22:44:30 -0400
> >
> > I hate to bump this, but I did not want to start a new thread. I have
> > tried getting onto IRC, but I think I am missing the peak times as I
> > have not managed to get a response yet. Can somebody please help me with
> > this?
> >
> >
> > Thank You,
> >
> > John Tatum
> > john.ta...@live.com
> > http://scientifichooliganism.net
> >
> > Although this e-mail and any attachments are believed to be free of any
> > virus or other defect that might affect any computer system into which
> > it is received and/or upon which it is opened, it is the responsibility
> > of the recipient(s) to ensure that it is virus and/or defect free and
> > John Tatum bears no responsibility for any loss and/or damage arising in
> > any way from its use.
> >
> > 
> > From: john.ta...@live.com
> > To: jenkinsci-dev@googlegroups.com
> > Subject: Request for Commit Access to SSH-Plugin
> > Date: Sat, 16 May 2015 13:51:55 -0400
> >
> > May I have commit access for the SSH-Plugin, specifically
> > https://github.com/jenkinsci/ssh-plugin? My GitHub user ID is
> > johnny-b-goode.
> >
> > I have tried reaching out to the maintainer indicated on the wiki,
> > Edmund Wagner, but have not received a response. His last commit was
> > about nine months ago. There are currently three pull requests pending,
> > and a number of issues in Jira that should be fairly quick fixes.
> >
> >
> > Thank You,
> >
> > John Tatum
> > john.ta...@live.com
> > http://scientifichooliganism.net
> 
> -- 
> 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/5565B52A.7000805%40orr.me.uk.
> 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/BLU179-W428A4C64A281B7CBF3384EF7CB0%40phx.gbl.
For more options, visit https://groups.google.com/d/optout.

Re: Captcha on wiki

2015-05-27 Thread 'Bruno P. Kinoshita' via Jenkins Developers

I have had similar problem in the past while editing the Testopia Plug-in Wiki
too. I was basically locked, and could not edit the page, it simply always
failed, even though I tried to slowly type the captcha.
So I tried rolling-back the Wiki to a previous version, and after that suddenly
I was able to edit and save it again with no problems.
Just my 0.02 cents
Bruno

From: Jesse Glick
To: Jenkins Dev
Sent: Thursday, May 28, 2015 10:18 AM
Subject: Re: Captcha on wiki

On Fri, May 22, 2015 at 6:19 AM, Stephen Connolly
wrote:
> Am I the only one who has to keep trying to guess the really bad captcha 50
> times just to save a page?

You are not the only one. Possibly relevant:
https://issues.jenkins-ci.org/browse/INFRA-300

--
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/CANfRfr1KY1DVYJyyE7TRBSxd9K7Koe%2BaUHOKhOOVR80JOPbgoQ%40mail.gmail.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/263143800.359863.1432765665000.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Captcha on wiki

2015-05-27 Thread Jesse Glick

On Fri, May 22, 2015 at 6:19 AM, Stephen Connolly
 wrote:
> Am I the only one who has to keep trying to guess the really bad captcha 50
> times just to save a page?

You are not the only one. Possibly relevant:
https://issues.jenkins-ci.org/browse/INFRA-300

-- 
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/CANfRfr1KY1DVYJyyE7TRBSxd9K7Koe%2BaUHOKhOOVR80JOPbgoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Workflow DSL with git (and others)

2015-05-27 Thread Jesse Glick

On Thu, May 21, 2015 at 11:34 AM, Sven Erik Knop  wrote:
> The "run" object that gets invoked has a getResult() value of null

Sure, because the flow is still running. It will eventually become
SUCCESS if nothing goes wrong later.

> (preventing me from labelling only for successful builds)

If the build failed with an exception, the rest of the flow should not
run, unless you are using a try-block.

See also the catchError step, which is a way to run a publisher even
if the build is _not_ successful.

> Usually the URL looks like this:
>
> http://localhost:8080/jenkins/job///tagBuild/
> for example:
> http://localhost:8080/jenkins/job/p4-direct/2/tagBuild/
>
> in my DSL case it is
> http://localhost:8080/jenkins/tagBuild/
>
> and the link points into nowhere.

Well debug whatever code constructs that URL and see why it is
omitting part of it. I have no idea offhand.

-- 
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/CANfRfr18%2B8u8gWFj8N3v_Fgp8K6GXRek%2B5a-bPowTbmWbkg_Pw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request: seed

2015-05-27 Thread Damien Coraboeuf

Hi,

Thanks for getting the Seed plug-in on board. The Wiki page has been 
created but I still have a problem with the build on Cloudbees 
at https://jenkins.ci.cloudbees.com/job/plugins/job/seed-plugin/

It has been created using a Maven template but this is actually a Gradle 
JPI project. Is it possible to adapt its configuration like for the Job DSL 
job a https://jenkins.ci.cloudbees.com/job/plugins/job/job-dsl-plugin/ ? Is 
there a way for me to access the Seed Plugin job configuration ?

Thanks,
Damien.

On Wednesday, 27 May 2015 14:11:42 UTC+2, Christopher wrote:
>
> Hi there, 
>
> Forked; you can now use this as your canonical Git repo: 
> https://github.com/jenkinsci/seed-plugin 
>
> You should have received a mail from GitHub to your personal GitHub 
> account. 
>
> Please create a wiki page, with the URL and update your build.gradle 
> file: https://wiki.jenkins-ci.org/display/JENKINS/Seed+Plugin 
>
> See here for more info: 
>
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-CreatingaWikipage
>  
>
> Regards, 
> Chris 
>
>
> On 18/05/15 19:42, Damien Coraboeuf wrote: 
> > Hi, 
> > 
> > I wanted to know if something could be done about the hosting of this 
> > plug-in. I'm already using it at my client and has a presentation about 
> > it at the JUC :( 
> > 
> > Thanks, 
> > Damien. 
> > 
> > On Tuesday, 5 May 2015 16:06:01 UTC+2, Damien Coraboeuf wrote: 
> > 
> > Hi, 
> > 
> > The Seed project aims to help automating the generation and 
> > management of pipelines for branches of a project in Jenkins. 
> > 
> > The Seed structure can be generated automatically 
> > 
> > seed --> project seed 
> > project seed --> branch seed for a given branch 
> > branch seed --> pipeline for this branch 
> > 
> > Plugin Name: seed 
> > My GitHub username: dcoraboeuf 
> > Existing repo: https://github.com/nemerosa/seed-plugin 
> >  
> > Documentation: https://github.com/nemerosa/seed-plugin/wiki 
> >  
> > 
> > Please note that this plug-in is using the Gradle JPI plug-in and 
> > uses Gradle for its build. 
> > 
> > Thanks for your consideration, 
> > Damien Coraboeuf. 
> > 
> > -- 
> > 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/a3a7314c-dade-41c9-ab1e-3f08fdbc267c%40googlegroups.com
>  
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/a3a7314c-dade-41c9-ab1e-3f08fdbc267c%40googlegroups.com?utm_medium=email&utm_source=footer>.
>  
>
> > 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/a49c007b-19ad-4aee-9e1a-3446c8d2ffb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Schedule for next release of Git Plugin?

2015-05-27 Thread Mark Waite

The most recent release allowed in a few regressions (my apologies, I
didn't test it throughly enough).  We would like to be more thorough
testing the next release.

If you're willing to help with the testing, a build containing most of the
changes likely to be included in the next release is at:

https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/818/org.jenkins-ci.plugins$git/


Note, that is not the current tip of the master branch.  That build is the
tip of the master branch plus a pull request to fix JENKINS-28506.

Thanks,
Mark Waite

On Wed, May 27, 2015, 10:42 AM Christian Galsterer <
christian.galste...@gmx.de> wrote:

> Hi,
>
> when is the next release of the Git plugin planned? Some changes we need
> are already merged but they are not yet released.
> Would be nice to get the new release soon.
>
> Br
> Christian
>
> --
> 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/0c18fe83-1883-4a70-9393-6ea8b9585750%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/CAO49JtFAV4fdatZPaE7XARhB--uJYNui_CXJcP8L0OCUFQ9GSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Schedule for next release of Git Plugin?

2015-05-27 Thread Christian Galsterer

Hi,

when is the next release of the Git plugin planned? Some changes we need 
are already merged but they are not yet released.
Would be nice to get the new release soon.

Br
Christian

-- 
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/0c18fe83-1883-4a70-9393-6ea8b9585750%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Propagate JAAS Subject from Core Jenkins to Custom step plugin

2015-05-27 Thread domi

This is actually a subject a couple of user wanted to come up with, but at the 
end I think all discarded the idea…
If still wanna do this, then you also have to think about scheduled jobs, these 
are triggered by no user interaction, which JAAS subject would you use in these 
cases?
/Domi


On 27 May 2015, at 16:48, Guillaume Delory  wrote:

> Actually after thinking a bit more about that. I guess that the user is 
> authenticated only when he start the job and add it to the queue. Then the 
> executor wil take care of it but user has nothing to do with it. So it makes 
> sense there is no Subject associated to it.
> 
> If I'm right, the only option would be to intercept the build creation and 
> somehow store the Subject somewhere if it's available, to make it available 
> for the actual build one by the Jenkins user. I have no idea if it's possible.
> 
> Any thoughts?
> 
> Thank you :)
> 
> Le mardi 26 mai 2015 14:24:19 UTC+2, Guillaume Delory a écrit :
> Hi everyone,
> 
> I'm running Jenkins in WebSphere 8.5 to manage authentication. It works fine 
> and I can get the JAAS Subject in the Script Console by doing:
> println com.ibm.websphere.security.auth.WSSubject.getCallerSubject()
> 
> I also wrote a plugin that adds a simple custom step (extending the Builder 
> class). I would like to use this plugin to contact some application also 
> running in WAS. To do this I need to get the caller Subject as I did in the 
> console. However, the code above in the perform method returns null. I guess 
> Jenkins runs the step in a different thread without pushing the JAAS Subject.
> 
> Is there any way (by configuration or programmatically) to force Jenkins to 
> push the Subject to the build step so I can use it? Or maybe a different way 
> to get the caller Subject from the plugin?
> 
> Thank you very much for your 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/fb1f9ab7-f118-42e6-9314-35f9aa509c9b%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/A9328AD6-B3C4-47B8-8CFC-A91E65A4FC79%40fortysix.ch.
For more options, visit https://groups.google.com/d/optout.

Re: Propagate JAAS Subject from Core Jenkins to Custom step plugin

2015-05-27 Thread Guillaume Delory

Actually after thinking a bit more about that. I guess that the user is 
authenticated only when he start the job and add it to the queue. Then the 
executor wil take care of it but user has nothing to do with it. So it 
makes sense there is no Subject associated to it.

If I'm right, the only option would be to intercept the build creation and 
somehow store the Subject somewhere if it's available, to make it available 
for the actual build one by the Jenkins user. I have no idea if it's 
possible.

Any thoughts?

Thank you :)

Le mardi 26 mai 2015 14:24:19 UTC+2, Guillaume Delory a écrit :
>
> Hi everyone,
>
> I'm running Jenkins in WebSphere 8.5 to manage authentication. It works 
> fine and I can get the JAAS Subject in the Script Console by doing:
> println com.ibm.websphere.security.auth.WSSubject.getCallerSubject()
>
> I also wrote a plugin that adds a simple custom step (extending the 
> Builder class). I would like to use this plugin to contact some application 
> also running in WAS. To do this I need to get the caller Subject as I did 
> in the console. However, the code above in the perform method returns null. 
> I guess Jenkins runs the step in a different thread without pushing the 
> JAAS Subject.
>
> Is there any way (by configuration or programmatically) to force Jenkins 
> to push the Subject to the build step so I can use it? Or maybe a different 
> way to get the caller Subject from the plugin?
>
> Thank you very much for your 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/fb1f9ab7-f118-42e6-9314-35f9aa509c9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Propagate JAAS Subject from Core Jenkins to Custom step plugin

2015-05-27 Thread Guillaume Delory

Hi,

Thank you very much for your help Stephen. It's been really helpful. I 
looked at the plugin and this is how they capture the current user and 
authenticate him:

Cause.UserIdCause cause = getRootUserIdCause(item);
if (cause != null) {
  User u = User.get(cause.getUserId(), false, Collections.emptyMap());
  if (u == null) {
return Jenkins.ANONYMOUS;
  }
  return u.impersonate();
}
return null;

Then impersonate the user who started the build. That returns a 
org.acegisecurity.Authentication. It is progress.

It gives me the Jenkins user. But problem is I don't think it is the Web 
container user, and is even related to it. (That would mean a Jenkins admin 
could impersonate any user from the Realm and contact any other 
application, which doesn't make any sense).

My next question is:

   - Do you think there is any way to get the Web Container user (Subject), 
   knowing that it looks like the thread doesn't get the authentication 
   (com.ibm.websphere.security.auth.WSSubject.getCallerSubject() returns null)
   - Or do you think it is possible to convert the Jenkins Authentication 
   to a Web Container Subject. I did create a Subject from the Jenkins 
   Authentication (which is a Principal) but of course it didn't work since it 
   is not related to the Web Container authentication and I had access 
   forbidden. I doubt it because Jenkins can impersonate anyone, and maybe it 
   will work only for the current user...

I don;t really know where to look next.

Thank you very much.


Le mercredi 27 mai 2015 09:25:02 UTC+2, Stephen Connolly a écrit :
>
> You may want to look at the (very un-obvious named) Authorize Project 
> plugin.
>
> That lets projects build with the identity of the user that triggered the 
> build.
>
> It's not going to get you all you want, but should get you closer. You'll 
> probably need to write an authorization strategy to capture the JAAS 
> subject and store it as a UserProperty
>
> On Tuesday, May 26, 2015, Guillaume Delory > 
> wrote:
>
>> Hi everyone,
>>
>> I'm running Jenkins in WebSphere 8.5 to manage authentication. It works 
>> fine and I can get the JAAS Subject in the Script Console by doing:
>> println com.ibm.websphere.security.auth.WSSubject.getCallerSubject()
>>
>> I also wrote a plugin that adds a simple custom step (extending the 
>> Builder class). I would like to use this plugin to contact some application 
>> also running in WAS. To do this I need to get the caller Subject as I did 
>> in the console. However, the code above in the perform method returns null. 
>> I guess Jenkins runs the step in a different thread without pushing the 
>> JAAS Subject.
>>
>> Is there any way (by configuration or programmatically) to force Jenkins 
>> to push the Subject to the build step so I can use it? Or maybe a different 
>> way to get the caller Subject from the plugin?
>>
>> Thank you very much for your 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/b9be9c04-cb9a-4fdd-a7cc-903d88d78db9%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9480017a-cd57-40c4-97bc-29989677bc8f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for commit access to Rally plugin repository (and code review)

2015-05-27 Thread Mike Rogers

Thanks for the response!

That sounds perfectly reasonable. Everything is ready to go at this point 
(in terms of new plugin functionality), I'm just waiting on permission. I 
released something last night as a fork-of-a-fork thing that I'm not too 
proud of, but my organization needed something concrete to go through their 
governance process. I can retract all that once I'm able to push to the 
proper plugin.

On Wednesday, May 27, 2015 at 8:01:45 AM UTC-4, Christopher wrote:
>
> It sounds like it would be best if you became another maintainer of the 
> plugin if the current maintainer doesn't have time at the moment. 
>
> If the maintainer was ok with that, we can give you commit access now. 
>
> In any case, from a user's point of view, it's better to have one plugin 
> than multiple plugins that are broadly similar. 
>
> Regards, 
> Chris 
>
>
> On 25/05/15 05:08, Mike Rogers wrote: 
> > I did finally get in contact with the maintainer of the Rally plugin. 
> > However, given the recent goings-on in his life and the amount that I've 
> > been throwing at him, I'm wondering if it would be in both of our 
> > interests to fork and have two separate plugins. Mine focuses more on 
> > the SCM integration; the original favors Rally 'accounting', i.e. 
> > maintaining time spent and estimates from within the context of commit 
> > messages. 
> > 
> > Are there any thoughts? I still haven't managed to get an accepted pull 
> > request or any feedback from a code review. I'll be backfilling tests 
> > and refactoring for the next couple of weeks, and I have yet a few 
> > features I'd like to add. 
> > 
> > On Tuesday, May 19, 2015 at 9:05:00 PM UTC-4, Mike Rogers wrote: 
> > 
> > Hello, 
> > 
> > 
> > I would like commit access to the Rally plugin repository 
> > (https://github.com/jenkinsci/rally-plugin 
> > ) and potentially 
> > leadership of that plugin. My team is using Rally on a fairly large 
> > project (alongside several other teams) and I'm seeing a few areas 
> > where minor improvements would yield pretty cool results. 
> > 
> > 
> > To that end I have spent the past few days refactoring and doing 
> > some minor feature additions. Could I get a code review on my 
> > branch, 
> > https://github.com/mike-rogers/rally-plugin/tree/minor-refactoring? 
> >  
> I 
> > have hooked it up to Travis-CI (the irony of which I recognize) and 
> > the build is green: 
> > https://travis-ci.org/mike-rogers/rally-plugin/branches 
> >  
> > 
> > 
> > I have added tests and refactored pretty heavily, while trying to 
> > keep the logic intact. If you review, I suggest getting a feel for 
> > the original repo and then looking at mine with fresh eyes. Looking 
> > at diffs may prove more confusing than not. 
> > 
> > 
> > If there are any questions or concerns, I love feedback. Please feel 
> > free to contact me. 
> > 
> > 
> > Thank you! 
> > 
> > 
> > -Mike 
> > 
> > 
> > PS - I have reached out to the primary committer of the repository, 
> > but his account has been nearly free of activity lately and I've 
> > heard nothing back. 
>

-- 
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/100b5dbd-55a6-4ec3-8e64-b4d71fe87a97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for Commit Access to SSH-Plugin

2015-05-27 Thread Christopher Orr

I believe I replied to you a couple of times on IRC, but I guess we 
missed each other.


You should now have access.

Regards,
Chris


On 27/05/15 05:36, John Tatum wrote:

I reached out to Jesse Glick about this, and he recommended I send a
reminder to the list. I am still looking for anybody who can help me out
with this.


Thank You,

John Tatum
john.ta...@live.com
http://scientifichooliganism.net

Although this e-mail and any attachments are believed to be free of any
virus or other defect that might affect any computer system into which
it is received and/or upon which it is opened, it is the responsibility
of the recipient(s) to ensure that it is virus and/or defect free and
John Tatum bears no responsibility for any loss and/or damage arising in
any way from its use.


From: john.ta...@live.com
To: jenkinsci-dev@googlegroups.com
Subject: RE: Request for Commit Access to SSH-Plugin
Date: Wed, 20 May 2015 22:44:30 -0400

I hate to bump this, but I did not want to start a new thread. I have
tried getting onto IRC, but I think I am missing the peak times as I
have not managed to get a response yet. Can somebody please help me with
this?


Thank You,

John Tatum
john.ta...@live.com
http://scientifichooliganism.net

Although this e-mail and any attachments are believed to be free of any
virus or other defect that might affect any computer system into which
it is received and/or upon which it is opened, it is the responsibility
of the recipient(s) to ensure that it is virus and/or defect free and
John Tatum bears no responsibility for any loss and/or damage arising in
any way from its use.


From: john.ta...@live.com
To: jenkinsci-dev@googlegroups.com
Subject: Request for Commit Access to SSH-Plugin
Date: Sat, 16 May 2015 13:51:55 -0400

May I have commit access for the SSH-Plugin, specifically
https://github.com/jenkinsci/ssh-plugin? My GitHub user ID is
johnny-b-goode.

I have tried reaching out to the maintainer indicated on the wiki,
Edmund Wagner, but have not received a response. His last commit was
about nine months ago. There are currently three pull requests pending,
and a number of issues in Jira that should be fairly quick fixes.


Thank You,

John Tatum
john.ta...@live.com
http://scientifichooliganism.net


--
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/5565B52A.7000805%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin hosting request: seed

2015-05-27 Thread Christopher Orr

Hi there,

Forked; you can now use this as your canonical Git repo:
https://github.com/jenkinsci/seed-plugin

You should have received a mail from GitHub to your personal GitHub account.

Please create a wiki page, with the URL and update your build.gradle
file: https://wiki.jenkins-ci.org/display/JENKINS/Seed+Plugin

See here for more info:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-CreatingaWikipage

Regards,
Chris

On 18/05/15 19:42, Damien Coraboeuf wrote:

Hi,

I wanted to know if something could be done about the hosting of this
plug-in. I'm already using it at my client and has a presentation about
it at the JUC :(

Thanks,
Damien.

On Tuesday, 5 May 2015 16:06:01 UTC+2, Damien Coraboeuf wrote:

Hi,

The Seed project aims to help automating the generation and
management of pipelines for branches of a project in Jenkins.

The Seed structure can be generated automatically

seed --> project seed
project seed --> branch seed for a given branch
branch seed --> pipeline for this branch

Plugin Name: seed
My GitHub username: dcoraboeuf
Existing repo: https://github.com/nemerosa/seed-plugin

Documentation: https://github.com/nemerosa/seed-plugin/wiki

Please note that this plug-in is using the Gradle JPI plug-in and
uses Gradle for its build.

Thanks for your consideration,
Damien Coraboeuf.

--
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/a3a7314c-dade-41c9-ab1e-3f08fdbc267c%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/5565B479.2080008%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

Re: Request for commit access to Rally plugin repository (and code review)

2015-05-27 Thread Christopher Orr

It sounds like it would be best if you became another maintainer of the 
plugin if the current maintainer doesn't have time at the moment.


If the maintainer was ok with that, we can give you commit access now.

In any case, from a user's point of view, it's better to have one plugin 
than multiple plugins that are broadly similar.


Regards,
Chris


On 25/05/15 05:08, Mike Rogers wrote:

I did finally get in contact with the maintainer of the Rally plugin.
However, given the recent goings-on in his life and the amount that I've
been throwing at him, I'm wondering if it would be in both of our
interests to fork and have two separate plugins. Mine focuses more on
the SCM integration; the original favors Rally 'accounting', i.e.
maintaining time spent and estimates from within the context of commit
messages.

Are there any thoughts? I still haven't managed to get an accepted pull
request or any feedback from a code review. I'll be backfilling tests
and refactoring for the next couple of weeks, and I have yet a few
features I'd like to add.

On Tuesday, May 19, 2015 at 9:05:00 PM UTC-4, Mike Rogers wrote:

Hello,


I would like commit access to the Rally plugin repository
(https://github.com/jenkinsci/rally-plugin
) and potentially
leadership of that plugin. My team is using Rally on a fairly large
project (alongside several other teams) and I'm seeing a few areas
where minor improvements would yield pretty cool results.


To that end I have spent the past few days refactoring and doing
some minor feature additions. Could I get a code review on my
branch,
https://github.com/mike-rogers/rally-plugin/tree/minor-refactoring?
 I
have hooked it up to Travis-CI (the irony of which I recognize) and
the build is green:
https://travis-ci.org/mike-rogers/rally-plugin/branches



I have added tests and refactored pretty heavily, while trying to
keep the logic intact. If you review, I suggest getting a feel for
the original repo and then looking at mine with fresh eyes. Looking
at diffs may prove more confusing than not.


If there are any questions or concerns, I love feedback. Please feel
free to contact me.


Thank you!


-Mike


PS - I have reached out to the primary committer of the repository,
but his account has been nearly free of activity lately and I've
heard nothing back.


--
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/5565B220.2020305%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.

java.util.zip.ZipException: archive is not a ZIP archive

2015-05-27 Thread 672162494

my dev plugin version 1.480


The error below occurs intermittently, with low frequency. 
but I have this zip file and can upzip it properly, I am not sure why this 
error pops up.
pls reply ,thx !


java.util.zip.ZipException: archive is not a ZIP archiveat 
org.apache.tools.zip.ZipFile.positionAtCentralDirectory(ZipFile.java:481)at 
org.apache.tools.zip.ZipFile.populateFromCentralDirectory(ZipFile.java:320)  at 
org.apache.tools.zip.ZipFile.(ZipFile.java:186)at 
org.apache.tools.zip.ZipFile.(ZipFile.java:163)at 
org.apache.tools.zip.ZipFile.(ZipFile.java:124)at 
hudson.FilePath.unzip(FilePath.java:571) at 
hudson.FilePath.access$300(FilePath.java:191)at 
hudson.FilePath$3.invoke(FilePath.java:496)  at 
hudson.FilePath$3.invoke(FilePath.java:492)  at 
hudson.FilePath.act(FilePath.java:989)   at 
hudson.FilePath.act(FilePath.java:967)   at 
hudson.FilePath.unzip(FilePath.java:492)at 
com.wangyin.ci.performance.PerformanceReporterPublisher.copyReportsToMaster(PerformanceReporterPublisher.java:742)
at 
com.wangyin.ci.performance.PerformanceReporterPublisher.perform(PerformanceReporterPublisher.java:334)
   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721)
   at hudson.model.Build$BuildExecution.post2(Build.java:183)  at 
hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670)  
 at hudson.model.Run.execute(Run.java:1766)  at 
hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)  at 
hudson.model.ResourceController.execute(ResourceController.java:98)  at 
hudson.model.Executor.run(Executor.java:374)
My code:(PerformanceReporterPublisher.copyReportsToMaster)
private void copyReportsToMaster(AbstractBuild build, PrintStream 
logger, FilePath[] listfilFilePaths, String parserDisplayName) throws 
IOException, InterruptedException {   FilePath remoteZipDir = null; 
  FilePath remoteZip = null;  try {   String 
zipString = "report-result.zip"; String zipDirString = 
"report-result";  remoteZipDir = new 
FilePath(build.getModuleRoot(), zipDirString);   
remoteZipDir.mkdirs();  logger.println("copy remote report to 
remote report-result dir");   for (FilePath src : 
listfilFilePaths) { src.copyTo(new 
FilePath(remoteZipDir, src.getName()));  }  
 remoteZip = new FilePath(remoteZipDir.getParent(), zipString); 
 logger.println("compress remote report-result dir ");  
 remoteZipDir.zip(remoteZip);File localReport = 
getPerformanceReport(build, parserDisplayName, zipString);   
FilePath localReportFilePath = new FilePath(localReport);   
logger.println("copy report-result zip to locate"); 
remoteZip.copyTo(localReportFilePath);  FilePath resultDir = 
new FilePath(localReportFilePath.getParent(), zipDirString);
   localReportFilePath.unzip(resultDir);




  



 

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

Re: Propagate JAAS Subject from Core Jenkins to Custom step plugin

2015-05-27 Thread Stephen Connolly

You may want to look at the (very un-obvious named) Authorize Project
plugin.

That lets projects build with the identity of the user that triggered the
build.

It's not going to get you all you want, but should get you closer. You'll
probably need to write an authorization strategy to capture the JAAS
subject and store it as a UserProperty

On Tuesday, May 26, 2015, Guillaume Delory  wrote:

> Hi everyone,
>
> I'm running Jenkins in WebSphere 8.5 to manage authentication. It works
> fine and I can get the JAAS Subject in the Script Console by doing:
> println com.ibm.websphere.security.auth.WSSubject.getCallerSubject()
>
> I also wrote a plugin that adds a simple custom step (extending the
> Builder class). I would like to use this plugin to contact some application
> also running in WAS. To do this I need to get the caller Subject as I did
> in the console. However, the code above in the perform method returns null.
> I guess Jenkins runs the step in a different thread without pushing the
> JAAS Subject.
>
> Is there any way (by configuration or programmatically) to force Jenkins
> to push the Subject to the build step so I can use it? Or maybe a different
> way to get the caller Subject from the plugin?
>
> Thank you very much for your 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
> 
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/b9be9c04-cb9a-4fdd-a7cc-903d88d78db9%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMyfeeZ7uYLoDBDGqYcgq%3D2Aq%2BoBTN-Oc84_5Dqv8qqK4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: Request for Commit Access to SSH-Plugin

Re: Captcha on wiki

Re: Captcha on wiki

Re: Workflow DSL with git (and others)

Re: Plugin hosting request: seed

Re: Schedule for next release of Git Plugin?

Schedule for next release of Git Plugin?

Re: Propagate JAAS Subject from Core Jenkins to Custom step plugin

Re: Propagate JAAS Subject from Core Jenkins to Custom step plugin

Re: Propagate JAAS Subject from Core Jenkins to Custom step plugin

Re: Request for commit access to Rally plugin repository (and code review)

Re: Request for Commit Access to SSH-Plugin

Re: Plugin hosting request: seed

Re: Request for commit access to Rally plugin repository (and code review)

java.util.zip.ZipException: archive is not a ZIP archive

Re: Propagate JAAS Subject from Core Jenkins to Custom step plugin

16 matches

Site Navigation

Mail list logo

Footer information