Re: Checker runs once before applyNameRef, causing relative path to fail

2016-08-04 Thread Guillaume Delory 
Ok so I investigated a bit more, and it seems this is happening because the 
INPUT.validated rule is coming before the TR.row-set-end rule (priority 26 
vs 43).

Anyone already had issue with behaviour rules execution order, any way to 
change this easily? I've tried changing the order using the debugger tool 
and that works fine if I move the TR.row-set-end (which as a reminder is 
the one setting the ref/refName relationship for blocks), before the 
validators. That way the first validation can use ref/refName and relative 
path are resolved correctly.

Thanks for your help.

Le jeudi 4 août 2016 22:58:25 UTC+2, Guillaume Delory a écrit :
>
> Hi,
>
> I'm trying to use validation on a field with a form a bit unusual because 
> it's using a lot of radioBlock and I need relative path. So I set up my 
> validation method like that:
>
> public FormValidation doCheckIdcmsInputFile(@QueryParameter("value") final 
> String value, @RelativePath("../..") @QueryParameter final String 
> fileOrManual, @RelativePath("..") @QueryParameter final String inputtype)
>
> It does create the correct checkUrl and checkDependsOn attributes 
> dynamically, the problem is that checker function (hudson-behavior.js:444) 
> is called once on the field before applyNameRef is called. As you may know, 
> this function is setting the ref/nameRef relation ship between radio button 
> and their corresponding block. Therefore the first time it's running, it's 
> failing to resolve the path and causes a javascript error preventing my 
> form to load (because the ../.. go way to high without the ref/nameRef). If 
> I stop in debug the first run and change the relative path to make it work 
> without ref/nameRef, then after ref/nameRef did it job my relative path 
> work perfectly fine.
>
> I'm using Jenkins 1.638. Any of you already encountered this 
> checke/nameRef condition race when using relative path? How did you solve 
> it?
>
> Here is my form for your information, I removed all unnecessary parts to 
> make it clearer for this question:
>
> 
>   
>   
> 
>   
>
> 
>
>  id="manualinput" title="Build a DCS Build File">
>   
>   
> title="GSA">
>   
> 
>   
>   
> 
>   
> 
>  title="IDCMS">
>   
> 
>   
> 
>   
>   
> 
>
> Thanks for your help and I hope I was in the right group to ask that, not 
> sure if I should open a bug in the JIRA as well, I thought I would rather 
> ask in the group first.
>

-- 
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/899c5263-c7fd-4807-8499-3d86b39536a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Checker runs once before applyNameRef, causing relative path to fail

2016-08-04 Thread Guillaume Delory 
Hi,

I'm trying to use validation on a field with a form a bit unusual because
it's using a lot of radioBlock and I need relative path. So I set up my
validation method like that:

public FormValidation doCheckIdcmsInputFile(@QueryParameter("value") final
String value, @RelativePath("../..") @QueryParameter final String
fileOrManual, @RelativePath("..") @QueryParameter final String inputtype)

It does create the correct checkUrl and checkDependsOn attributes
dynamically, the problem is that checker function (hudson-behavior.js:444)
is called once on the field before applyNameRef is called. As you may know,
this function is setting the ref/nameRef relation ship between radio button
and their corresponding block. Therefore the first time it's running, it's
failing to resolve the path and causes a javascript error preventing my
form to load (because the ../.. go way to high without the ref/nameRef). If
I stop in debug the first run and change the relative path to make it work
without ref/nameRef, then after ref/nameRef did it job my relative path
work perfectly fine.

I'm using Jenkins 1.638. Any of you already encountered this checke/nameRef
condition race when using relative path? How did you solve it?

Here is my form for your information, I removed all unnecessary parts to
make it clearer for this question:


  
  

  
   



  
  
   
  

  
  

  


  

  

  
  


Thanks for your help and I hope I was in the right group to ask that, not
sure if I should open a bug in the JIRA as well, I thought I would rather
ask in the group first.

-- 
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/CALuJxw%2BCfi-x8mmkcWJyyX4Cs%3Do9v%2BaU2YcWU2L7T9MN5Myfyw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automate recommended plugin unittest run against latest Jenkins core

2016-08-04 Thread Slide 
With releases coming often, it is hard to test against the latest Jenkins
when trying to deal with issues and so forth. Most maintainers just don't
have the time to test against the latest release, the latest LTS and a few
things in between.

On Thu, Aug 4, 2016 at 12:23 AM ogondza  wrote:

> Right, not the best wording. What I had in mind is: "It is something we
> would like to have confirmed before declaring the release is good to go".
>
> Unfortunately, many maintainers do not put that much effort into making
> sure their plugins work with latests cores, myself including.
>
> --
> oliver
>
> --
> 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/f373a327-d354-4446-87d8-25eb2472d733%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/CAPiUgVfkvZ0vhdwittDEvfMebh9SLtnz%3DwSrAu%3DDekuru1s3KQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automate recommended plugin unittest run against latest Jenkins core

2016-08-04 Thread Mark Waite 
On Thu, Aug 4, 2016 at 12:46 PM Manuel Jesús Recena Soto 
wrote:

> Hello Oliver,
>
> I like the idea.
>
> General speaking, ATH and PCT are very important and we should look after
> its healthy.
>
> IMHO, PCT results are a nice place to figure out bad symptoms on some
> plugins.
>
>
Can you describe the types of symptoms you envision detecting with PCT?

I am interested in running the plugin tests with a different
jenkins.version value, after compiling with an unmodified jenkins.version
value.  That seems like an interesting test alternative that might surface
interesting differences in the test harnesses or the core code.

I'm not really interested in having some external automation tell me that
the current code does not compile with the latest Jenkins core.
JENKINS-36646 seems like the same condition I see, failure to compile with
the newer Jenkins version because code changes are required before the
plugin can depend on the newer version.

I update the Jenkins core dependency rarely and with great care.  A bug
report like JENKINS-36646 is a distraction rather than a help, since I will
see the compilation failure as soon as I prepare the change for the plugin
to support the new Jenkins core version.

For example, the git plugin 3.0.0-beta already has the necessary change to
compile with more recent Jenkins core, but the automation probably won't
know that it needs to evaluate a beta version on a different branch than
master.

Mark Waite


> Please, find here two issues as result of PCT: JENKINS-36646
>  and JENKINS-36623
> 
>
> What we maybe need is make more usable and accessible this information.
>
> Regards,
>
>
> 2016-08-03 15:31 GMT+02:00 Oliver Gondža :
>
>> Hi,
>>
>> I created an issue[1] to verify if all recommended plugins has passing
>> unittest when run against latest core. I would like to use that as a GA
>> criteria for releases, LTS ones at least.
>>
>> I see people are still updating plugin-compat-tester so I guess it is not
>> dead, though I did not manage to find any recent documentation or running
>> CI job. Can it be used to implement that? Is somebody working on this?
>>
>> [1] https://issues.jenkins-ci.org/browse/JENKINS-37145
>> --
>> oliver
>>
>> --
>> 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/08d33372-c328-71d5-a2c6-870976e3b688%40gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Manuel Recena Soto
> * manuelrecena.com [/blog]
> * linkedin.com/in/recena
>
> --
> 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/CABa-UocUg78nQkNas9iyKK0JLKZvv%3DuT9eDoZLn1f0YYfsTPSA%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/CAO49JtFWnPvcmjCXE3ikhe9cFUSjNbnoLzuBq9AQU49gwB7zYw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automate recommended plugin unittest run against latest Jenkins core

2016-08-04 Thread Manuel Jesús Recena Soto 
Hello Oliver,

I like the idea.

General speaking, ATH and PCT are very important and we should look after
its healthy.

IMHO, PCT results are a nice place to figure out bad symptoms on some
plugins.

Please, find here two issues as result of PCT: JENKINS-36646
 and JENKINS-36623


What we maybe need is make more usable and accessible this information.

Regards,


2016-08-03 15:31 GMT+02:00 Oliver Gondža :

> Hi,
>
> I created an issue[1] to verify if all recommended plugins has passing
> unittest when run against latest core. I would like to use that as a GA
> criteria for releases, LTS ones at least.
>
> I see people are still updating plugin-compat-tester so I guess it is not
> dead, though I did not manage to find any recent documentation or running
> CI job. Can it be used to implement that? Is somebody working on this?
>
> [1] https://issues.jenkins-ci.org/browse/JENKINS-37145
> --
> oliver
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/jenkinsci-dev/08d33372-c328-71d5-a2c6-870976e3b688%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Manuel Recena Soto
* manuelrecena.com [/blog]
* linkedin.com/in/recena

-- 
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/CABa-UocUg78nQkNas9iyKK0JLKZvv%3DuT9eDoZLn1f0YYfsTPSA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin to hide/mask/obfuscate regex in all build output?

2016-08-04 Thread Jason Antman 
Yeah, I found the extension point - ConsoleLogFliter.

I've opened a pull request for my changes - 
https://github.com/jenkinsci/mask-passwords-plugin/pull/6

On Thursday, August 4, 2016 at 10:47:04 AM UTC-4, Jesse Glick wrote:
>
> On Fri, Jul 29, 2016 at 7:19 AM, Jason Antman  > wrote: 
> > some way to **force** this for EVERY job, 
> > period. I understand that's a feature most people wouldn't want, and I 
> might 
> > well keep that code in an internal branch only, rather than a pull 
> request I 
> > submit. However... I'm wondering if there's any way to accomplish this? 
>
> IIRC there is an extension point for this purpose. 
>

-- 
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/2f3775db-024f-4a89-8d92-de2d107680d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automate recommended plugin unittest run against latest Jenkins core

2016-08-04 Thread Jesse Glick 
On Wed, Aug 3, 2016 at 9:31 AM, Oliver Gondža  wrote:
> Is somebody working on this?

Maybe ask andresrc.

-- 
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/CANfRfr3Nb4k0c7_zDuDMT%2B9f6s-XeA%3DEzcD2RU2YTp8Xmubw-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: WorkflowMultiBranchProject getLastBuild

2016-08-04 Thread Jesse Glick 
On Wed, Aug 3, 2016 at 5:14 AM, Sverre Moe  wrote:
> I need to get the latest build job in my Groovy build script.

Did you look at the documentation under Global Variables for `currentBuild`?

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

Re: how to create 2 page in RootAction

2016-08-04 Thread Jesse Glick 
On Wed, Aug 3, 2016 at 3:11 AM, Shurik  wrote:
> How in jelly I can configure the next button ?

Just a regular HTML link or form. You need to create a second view
after `index.jelly`.

-- 
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/CANfRfr3%2BNK-VBFX936jz8veyBuuWdsC%3DEGOhJqyygNP2DrXSGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: API access to update pipeline stages

2016-08-04 Thread Jesse Glick 
On Tue, Aug 2, 2016 at 12:26 PM, Daniel Watrous
 wrote:
> I'm struggling to find documentation around these or an example that might
> help me to accomplish what I'm trying to do.

Perhaps you are looking for

https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md#creating-an-asynchronous-step

?

-- 
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/CANfRfr0YmDfg%3DuT_A-bGM3k33aqoeujFT142FAWNp9nJmgQp8w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: combine multiple pipeline steps

2016-08-04 Thread Jesse Glick 
On Tue, Aug 2, 2016 at 11:53 AM, Ioannis Canellos  wrote:
> And how do I wrap a snippet like this inside a jenkins plugin?

See `docker-workflow` for an example of `GroovyShellDecorator`.
Probably a higher-level API will be introduced in the future.

-- 
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/CANfRfr1i_syTUFZieFFxMeE%2Bk4opm64npanoN-1B9BLLV90b%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with pipeline as a code dependency (workflow-aggregator)

2016-08-04 Thread Jesse Glick 
On Mon, Aug 1, 2016 at 4:54 AM, Ido Gadiel  wrote:
> I get this exception while Im trying to run the test: "clean test 
> -DskipTests=false -Dtest=myTest" (but it runs perfectly on regular run, e.g 
> hpi:run -Djetty.port=9192)
> java.lang.InstantiationException: java.lang.NoClassDefFoundError: 
> org/jenkinsci/main/modules/sshd/SshCommandFactory

Harmless, and can be worked around by adding an explicit dependency on
the SSHD module, but best to get rid of the `workflow-aggregator`
dependency and use the ones you actually need: at least `workflow-cps`
and `workflow-job`, typically some others like `workflow-basic-steps`
and/or `workflow-durable-task-step`.

And use `test` not `true`.

-- 
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/CANfRfr0%3D4XdWRD_Vx2jFt%3DR5SJTcfo8tCF8ejBaBsYXehysKRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin to hide/mask/obfuscate regex in all build output?

2016-08-04 Thread Jesse Glick 
On Fri, Jul 29, 2016 at 7:19 AM, Jason Antman  wrote:
> some way to **force** this for EVERY job,
> period. I understand that's a feature most people wouldn't want, and I might
> well keep that code in an internal branch only, rather than a pull request I
> submit. However... I'm wondering if there's any way to accomplish this?

IIRC there is an extension point for this purpose.

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

Re: Pipeline Syntax page and arguments of type Object

2016-08-04 Thread Jesse Glick 
On Fri, Jul 29, 2016 at 6:47 AM, David van Laatum  wrote:
> @DataBoundSetter
> public void setValue(String value) {
>   this.value = value;
> }
>
> @DataBoundSetter
> public void setValue(Integer value) {
>   this.value = value;
> }

You have to pick different parameters for each type.

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

Re: slack-plugin

2016-08-04 Thread Minudika Malshan 
Hi Nadishka,

If you haven't checked the source code of above mentioned project, clone it
and go through it. It's ok if you can't understand most of it. But if you
carefully observe it, you will be able to get an idea about the flow of the
code.

Furthermore, refer this documentation[1] to get a better understanding
about plug-in development.
Also this[2] will be helpful too.

After getting familiar with the source code, try to solve that JIRA issue.
It would be a better approach than jumping straight to the solving an issue
IMHO.

[1] https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial
[2] https://www.youtube.com/watch?v=eUzYZZsNBIA

BR.
Minudika

On Thu, Aug 4, 2016 at 11:28 AM, nadishka prabhashani <
nadishkaprabhashani...@gmail.com> wrote:

> Hi,
> I am new for the open source contribution. I like to try to fix this bugs
> in slack-plugin.
> I choose a bug which is "Feature Request - Display both author and
> committer #219".
> But I don't understand from where to start.
> Therefore I need your help.
>
> Prabhashani.
>
> --
> 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/0de7040b-fe10-4fdf-9ef3-0fb82a7d7e98%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/CAMqS2UcxuujcVk9wB2jZm6LDZiRk5w3Ye_iD95Ar%3D9bRGpKd4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to enable Travis CI for jenkins plugin repo

2016-08-04 Thread Arnaud Héritier 
INFRA-741 fixed. But I agree that it is better to not assign them.
Also our community CI should evolve soon with our recent partnership with
Azure : https://jenkins.io/blog/2016/05/18/announcing-azure-partnership/

On Thu, Aug 4, 2016 at 9:15 AM, Craig Rodrigues  wrote:

> I'm OK with Cloudbees using a template to lock things down for
> jenkins.io.cloudbees.com.
>
> One thing I would suggest is that in JIRA, if someone files an issue at
> https://issues.jenkins-ci.org
> in Project *Infrastructure*, Component: *ci*, instead of auto-assigning
> the issue to one
> person (rtyler), it goes to a team of people who can maintain this.
>
> For example, I filed https://issues.jenkins-ci.org/browse/INFRA-741 in
> June, and that got punted to Andrew Bayer.
> Andrew is super-busy doing dev work on Jenkins, so I'm glad he has helped
> in the past, but I don't
> think this kind of stuff should get assigned to him, because his
> considerable brainpower is better spent
> on other activities, IMHO.
>
> Regarding Travis, it is an excellent service, and I use it heavily for
> some other projects I am involved in.
> I have also used Appveyor and Codecov.io, and they are also excellent
> services.
>
> Travis and Appveyor are slightly competing with Jenkins, so I think it is
> understandable for Cloudbees to want to
> favor Jenkins for doing CI rather than using third party products and
> services.  It doesn't look good, otherwise.
>
> However, the Jenkins project and Cloudbees should see what can be done to
> improve the level of support,
> and also the feature set of jenkins.io.cloudbees.com, so that users do
> not even have to consider using Travis
> for Jenkins plugins.
>
> On a side note, I hope that the Plumber plugin work that Andrew has been
> working on goes farther along.
> Andrew gave me a demo of a YAML based configuration of a  pipeline
> workflow.  I was impressed.  This is very close
> to the YAML configurations that Travis and Appveyor offer.
>
> --
> Craig
>
>
> On Wed, Jul 20, 2016 at 4:14 PM, Kohsuke Kawaguchi  wrote:
>
>>
>> Like I said in my previous email, it's just that in
>> jenkins.io.cloudbees.com we choose to use a template to lock things down.
>>
>> --
> 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/CAG%3DrPVeNHKKoRT-9Mv%3DJY41D%2BNWa%3DEogXQiS7n358C1fNNN%3DXg%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

-- 
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/CAFNCU-9vBC6y28pZODjgDLcQWW_tD7pQmfTqp%3Dd7h8pYZ5keLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Developers for a fun project

2016-08-04 Thread Kanstantsin Shautsou 
Is it description of product or real plan of work? Why do you need "Jenkins 
developer" for it, all what i see is configure & learn your product?

On Wednesday, August 3, 2016 at 11:36:18 PM UTC+3, shay klapper wrote:
>
> We are looking for experienced Jenkins developers to run a project for us 
> in their sphere time.  We are willing to pay $20 per hour and a minimum 
> of $500 per the project. Please take a look at the project specs and let 
> me know if you can perform this project at the required level.
>
> Have a great day,
>
> Shay
> Blazemeter.com
>
> *Benchmark: Native Jenkins and Taurus*
>
> 1. Record a Selenium Java script for a website, use Taurus to run it, and 
> then put it into Jenkins.
>
> 2. Install Jenkins, go to the website blazedemo.com and build a set of 
> comprehensive tests including functional, regression, and performance (not 
> load) using Selenium and JMeter. Make sure you use a script per function, 
> make sure you end up with at least 10 different scripts.
>
> 3. Create a Jenkins job to run all of the above tests post build and 
> include all of the relevant plugins for reporting threshold and trending. 
> Add as many threshold as you possibly can.
>
> 4. Learn Taurus, accomplish all of the above using only Taurus and 
> Blazemeter. Send YML and Scripts for feedback. Expect multiple interaction 
> with the BlazeMeter support team.  
>
> 5. Document the project in detail and send us your report.
>

-- 
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/a0e29d89-68d9-46eb-82ac-d53f09c3d1ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: IMPORTANT: Do you have any `extends JnlpAgentReceiver` classes?

2016-08-04 Thread Kanstantsin Shautsou 
Bless you! :)

On Tuesday, August 2, 2016 at 4:08:59 PM UTC+3, Stephen Connolly wrote:
>
> The JnlpAgentReceiver API contract is too heavily tied to the 
> NioChannelHub abstraction (which is fundamentally incompatible with 
> SSLEngine)
>
> As such for JNLP4-connect a.k.a. JENKINS-36871 I basically have to rip it 
> out.
>
> Now this should not be *too* big a deal as there is only one Open Source 
> implementation of JnlpAgentReceiver - the one in Jenkins core - and I know 
> of one other closed source implementation (but that's a CloudBees one so I 
> can fix that)
>
> So I am calling for to see if there are other implementations. If there 
> are other implementations then I will see if there is a way to maintain 
> binary compatibility with those implementations (unlikely, but I can try 
> again... I may be able to get it if there are some methods I can throw out 
> on JnlpServerHandshake... though I should note that JNLP3-connect broke the 
> API binary compatibility as well as the API contract, so it is actually 
> highly unlikely that anyone has a working implementation)
>
> If you have or know of an additional implementation, please contact me 
> ASAP, otherwise I will be removing the code to replace with a nicer API 
> that does not make as many assumptions about the I/O and how that should be 
> wired up.
>
> -Stephen
>
> P.S. it will probably be end of this week before I start to consider 
> merging
>

-- 
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/4872ddb9-7cb4-40d5-82fe-5b8fe427c348%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automate recommended plugin unittest run against latest Jenkins core

2016-08-04 Thread ogondza 
Right, not the best wording. What I had in mind is: "It is something we 
would like to have confirmed before declaring the release is good to go".

Unfortunately, many maintainers do not put that much effort into making 
sure their plugins work with latests cores, myself including.

--
oliver

-- 
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/f373a327-d354-4446-87d8-25eb2472d733%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to enable Travis CI for jenkins plugin repo

2016-08-04 Thread Craig Rodrigues 
I'm OK with Cloudbees using a template to lock things down for
jenkins.io.cloudbees.com.

One thing I would suggest is that in JIRA, if someone files an issue at
https://issues.jenkins-ci.org
in Project *Infrastructure*, Component: *ci*, instead of auto-assigning the
issue to one
person (rtyler), it goes to a team of people who can maintain this.

For example, I filed https://issues.jenkins-ci.org/browse/INFRA-741 in
June, and that got punted to Andrew Bayer.
Andrew is super-busy doing dev work on Jenkins, so I'm glad he has helped
in the past, but I don't
think this kind of stuff should get assigned to him, because his
considerable brainpower is better spent
on other activities, IMHO.

Regarding Travis, it is an excellent service, and I use it heavily for some
other projects I am involved in.
I have also used Appveyor and Codecov.io, and they are also excellent
services.

Travis and Appveyor are slightly competing with Jenkins, so I think it is
understandable for Cloudbees to want to
favor Jenkins for doing CI rather than using third party products and
services.  It doesn't look good, otherwise.

However, the Jenkins project and Cloudbees should see what can be done to
improve the level of support,
and also the feature set of jenkins.io.cloudbees.com, so that users do not
even have to consider using Travis
for Jenkins plugins.

On a side note, I hope that the Plumber plugin work that Andrew has been
working on goes farther along.
Andrew gave me a demo of a YAML based configuration of a  pipeline
workflow.  I was impressed.  This is very close
to the YAML configurations that Travis and Appveyor offer.

--
Craig


On Wed, Jul 20, 2016 at 4:14 PM, Kohsuke Kawaguchi  wrote:

>
> Like I said in my previous email, it's just that in
> jenkins.io.cloudbees.com we choose to use a template to lock things down.
>
>

-- 
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/CAG%3DrPVeNHKKoRT-9Mv%3DJY41D%2BNWa%3DEogXQiS7n358C1fNNN%3DXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.