Re: User interface discussions - would it annoy people on this list?

[Stephen Connolly]

I would suggest using a subject line prefix, e.g. [UX] to allow people to
filter more easily if it gets distracting

On 4 February 2016 at 11:02, FredG  wrote:

> It will definitely be more interesting than account creation/commit
> access/plugin repository requests. ;)
>
> On Wednesday, February 3, 2016 at 10:22:20 AM UTC+1, Michael Neale wrote:
>>
>> If I wanted to "chatter" about user interface (not necessarily specific
>> plugins, but in general, related to Jenkins) would it be annoying on this
>> mailing list?
>> Would a separate list be more appropriate (who would want to be on it?).
>>
>> same applies to irc - is this topic specialised/uninteresting enough that
>> it warrants its own space?
>>
>>
>> --
> 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/1555f116-5e59-43c8-86d8-e0e30f4387fd%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/CA%2BnPnMyzvZ%3D9qAAGUkvwRymc4uzQs2ma85YcuQ34q-tBBtE0uQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Pull request to fix JENKINS-26318

[Slawomir Czarko-Wasiutycz]

Hello,

I haven't had any response on the pull request to fix JENKINS-26318 (issue 
here: https://issues.jenkins-ci.org/browse/JENKINS-26318)

https://github.com/jenkinsci/BlameSubversion-plugin/pull/2

What additional steps should be done to get this accepted?

Thank you,

Slawomir

-- 
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/5815dedb-fdbd-40e3-b02c-26ec17fb0a35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: User interface discussions - would it annoy people on this list?

[FredG]

It will definitely be more interesting than account creation/commit 
access/plugin repository requests. ;)

On Wednesday, February 3, 2016 at 10:22:20 AM UTC+1, Michael Neale wrote:
>
> If I wanted to "chatter" about user interface (not necessarily specific 
> plugins, but in general, related to Jenkins) would it be annoying on this 
> mailing list? 
> Would a separate list be more appropriate (who would want to be on it?). 
>
> same applies to irc - is this topic specialised/uninteresting enough that 
> it warrants its own space? 
>
>
>

-- 
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/1555f116-5e59-43c8-86d8-e0e30f4387fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: hot reloading - plugin development flow (what is meant to work?)

[Kanstantsin Shautsou]

Enter never worked because after restart descriptors changing links.
Reload doesn't affect removed classed, so only clean build and run can 
provide real working state after changes.

-- 
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/1dd1a2b7-c890-424b-8df6-85dcb5533121%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Artifactory server overloaded?

[Daniel Beck]

On 04.02.2016, at 01:54, Mark Waite  wrote:

> Is the artifactory server disabled or down?

I can access it right now, maybe a temporary outage?

-- 
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/E877C2D7-EB8E-4206-B109-55D134F2AF93%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins LTS interoperability and migration woes

[Stephen Connolly]

Updating slaves to Java 7 should be virtually zero risk. (better yet go to
Java 8 as Java 7 is End Of Life) as the slave.jar is well tested on Java 7
and Java 8 for 1.580.3

Then you can sort out upgrading the core.

You do not normally need the slaves to be running the exact same JVM as the
master... but they all need to respect the minimum bytecode version that
the Jenkins release was compiled against (i.e. for 1.625.1 you need Java 7
as a minimum)

Do not run two Jenkins processes on the same JENKINS_HOME at the same time
unless you want to live in a world of total and utter pain.

HTH

On 3 February 2016 at 19:07, Greg Mattson  wrote:

> All,
>
> I'd like to be able to migrate from jenkins version 1.580.3 to the newest
> LTS version 1.642.1.
>
> However, in the release notes for 1.625.1 I see the following:
>
> ** 1.625.1 is the first Jenkins LTS release that requires Java 7 to
> run.*
>
> Since I have a bunch of slaves that are on current java vm, I'm wondering
> how to safely migrate here.
>
>  In short, I need a way to the old jenkins instance in concert with the
> new, and slowly phase in the new version. I was thinking of a possible path
> forward here:
>
> * running jenkins on two ports, and pointing to the same, underlying
> metadata.
> * installing a new jvm in a different location and forwarding any new
> requests to this jvm.
>
> Anyways, I'm wondering exactly how feasible this is. It would allow us to
> use the two jenkins processes side-by-side to check for issue  and retreat
> if necessary, but if there are any incompatibilities between the two then I
> could see real problems going forwards, especially if the metadata between
> the two versions differs in any way or if there are any contention between
> the two processes.
>
> The alternative is to upgrade every single slave that we have to the new
> jvm, and after these are upgraded go forwards with the jenkins upgrade. But
> then, we may run into incompatibility issues with the new jvm and the old
> jenkins, and the upgrade will take a LONG time to get to because of high
> upfront cost.
>
> Any ideas here?
>
> Thanks much,
>
> --
> 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/b62b03d2-6bb0-4b30-b564-e79c5a491ae4%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/CA%2BnPnMx9Rc6yfJuA-%2Bi93%2BV_pZnuJcEsQ2oMfD-1FXZ2MkgbSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: simpleBuild - a pipeline DSL (and a sad tale about sandboxes)

[Michael Neale]

that was a copy paste error, I did use the correct map literal syntax of 
":". 

As Bobby said, map does work, however you can't really access any of it 
without whitelisting (I will work on that, should be fine). 

On Friday, February 5, 2016 at 1:41:21 AM UTC+11, Jesse Glick wrote:
>
> Try `[k: v]` not `[k = v]`, and file bugs in `script-security-plugin` 
> (label `workflow`) as needed.
>

-- 
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/4fbee5c3-3a58-4ffa-a146-1c77ed0930d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: simpleBuild - a pipeline DSL (and a sad tale about sandboxes)

[Jesse Glick]

On Thu, Feb 4, 2016 at 9:51 AM, Robert Sandell  wrote:
> I know by experience that map.isEmpty() is not whitelisted by default.

Just propose a PR in `script-security-plugin` where you run across
obvious cases. It takes just a few minutes.

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

Re: Please provide commit access to the gradle-plugin

['George Simpson' via Jenkins Developers]

Hi Oleg,
I tried to contact Gregory as you suggested and I never heard back.
Last commit was over a year ago, There are 9 open pull requests dating back
to Feb 2012.

Would you feel comfortable handing this over now given no one else is
working on it?

George

On Fri, Jan 22, 2016 at 12:54 AM Oleg Nenashev 
wrote:

> Gradle plugin has been maintained by Gregory Boissinot, who is not very
> active in the community right now.
> It's not in the "adopt-a-plugin" program, but maybe makes sense to
> handover it.
>
> Have you tried to contact Gregory directly?
> We commonly require a 2-week timeout after such request before providing
> permissisons
>
> BR, Oleg
>
> понедельник, 18 января 2016 г., 23:29:08 UTC+3 пользователь
> gsim...@netflix.com написал:
>>
>> I would like commit access to the gradle-plugin so I can merge some of
>> the outstanding pull requests.  My github id is 'gezerk'.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/gy9Fo0MqTCY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/9831580e-dfad-4c95-832b-cfcc3c9d08ab%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
George Simpson
Netflix 281-236-1916

-- 
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/CAPHzc0Npb%2BtyKHV9YwGtdrCXqSc2AV%2B0guV9tQBJrrd3Cowv%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bitbucket Server plugin

[domi]

Ok, i see - then this has to be made very clear in the names, artifactids and 
the documentation. As artifactids of existing plugins can't be changed without 
any impact for the enduser (we don't have an alias system), this should at 
least be done for new ones.
So then yes I think renaming should be fine (this was done for other plugins 
too) - maybe add a comment to the docu about the original name.
Domi

> Am 04.02.2016 um 20:02 schrieb Tomas Bjerre :
> 
> When responding to this, you should know that "Bitbucket" and "Bitbucket 
> Server" are two different products, with different API:s.
> 
> Get commits from Bitbucket:
> https://confluence.atlassian.com/bitbucket/commits-or-commit-resource-389775478.html#commitsorcommitResource-GETacommitslistforarepositoryorcomparecommitsacrossbranches
> 
> Get commits from Bitbucket Server:
> https://developer.atlassian.com/static/rest/bitbucket-server/4.3.1/bitbucket-rest.html#idp2523328
> 
> Browse the API:s and you will see more examples.
> 
> In my opinion, the naming is confusing. But that is a decision made by 
> Atlassian and nothing we can change. We can reduce the confusion by renaming 
> the stash-plugins to bitbucket-server-plugins. Because as more and more users 
> move to Bitbucket Server, people will forget that it was once called Stash.
> 
> 
> 2016-02-04 16:39 GMT+01:00 domi :
>> not sure about this, there are already a couple of bitbucket plugins and all 
>> of these address the hosted service bitbucket.
>> /Domi
>> 
>> 
>>> On 04 Feb 2016, at 16:38, Tomas Bjerre  wrote:
>>> 
>>> Now that "Atlassian Stash" has changed name to "Atlassian Bitbucket 
>>> Server", perhaps some of the plugins 
>>> (https://github.com/jenkinsci?utf8=%E2%9C%93=stash) should also 
>>> change name. Or they can all be merged into 1 single plugin "Bitbucket 
>>> Server plugin". What do you think?
>>> 
>>> -- 
>>> 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/3c33d9b6-8b8a-490e-83f6-9bc424de2bbf%40googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/ZZNVeE6mdA0/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/9F4305C0-80FF-4180-B7AD-9B4C4BB61FBD%40fortysix.ch.
>> 
>> 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/CAK89W5KKNePJphN6BgN1_nR6cGiDwYnnJmoJT4MwoBrGg8vpNQ%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/CC39C8AA-D251-44A0-B307-51A2DE15F05B%40fortysix.ch.
For more options, visit https://groups.google.com/d/optout.

Re: Enable html-include macro in the Jenkins tracking system

[Lars Kruse]

Hi Bobby

I'm really happy to hear that Confluence will be replaced wit something
else. Although I'm sorry to hear that we missed the boat.

I didn't see any threads on this topic, but I'd like to try to catch up.
Can you throw me some pointers: where did you discuss this and what did you
decide so far?

As we talked about 5 month's ago in CPH, the current state of the plugin
documentation is a big concern of ours, and we would obviously like to help
- if help is wanted.

In the meantime rtyler"s advice about abandoning ship and start hosting
docs outside Confluence like Job DSL and Pipeline seems like a good advice
in the light of the current situation.

So thanks for the enlightenment so far.
On Feb 4, 2016 17:07, "Robert Sandell"  wrote:

> I did mention the discussions we had on the Code Camp on the Jenkins 2.0
> Summit after FOSDEM while we were discussing the plugin documentation
> topic, but since we haven't heard anything about it since the Code Camp we
> couldn't assume anything about it. And the technology and focus has changed
> since then.
>
> You've had plenty of time to chime in to the website and documentation
> discussions that has been going on for a while on this list. And iirc KK's
> presentation about the goals of Jenkins 2.0, on this list, the blog, and
> office hours, is mentioning that Confluence will most likely die, so you've
> had some time to rethink and restart the discussions around how to handle
> the plugin docs.
> So I could only assume that you weren't working on it any more and so the
> Summit decided on a similar but slightly different approach of building the
> plugin documentations into the new jenkins.io site.
>
> Now IIUC jekyll and awestruct is pretty similar, so your work might be
> reusable in jenkins.io [1] so that rtyler and the website team doesn't
> have to do all the work themselves?
>
> [1] https://github.com/jenkins-infra/jenkins.io
>
> /B
>
>
> On Wed, Feb 3, 2016 at 8:49 PM, Lars Kruse  wrote:
>
>> >why wouldn't linking from the
>> >wiki to the generated GitHub pages repository suffice?
>>
>> ...well that wouldn't index to content on search engines in context of
>> the plugin - where we personally think that it belongs.
>>
>> I believe that both job DSL and pipeline plugins are doing what they are
>> doing - because the current state of the Jenkins confluence wiki is not
>> accommodating their needs (documentation along side the code). And driving
>> more and more plugins *away* from the wiki - as you just encouraged me
>> to do, is not the solution. Finding a way to contain the documentation
>> inside the wiki *is*.
>>
>> >One of the very active discussions we've had recently in IRC and in
>> person
>> >(FOSDEM) has been providing better documentation integration for plugin
>> >developers on the Jenkins primary site.
>>
>> Great, that you are discussing it! However, that dialog was kickstarted
>> on my colleague's Bue's initiative at the Jenkins Code Camp
>>  in Copenhagen last
>> summer, where he and Bobby Sandell and a handfuld of others discussed a
>> possible solution along the lines of what Bue describes in this blog
>> .
>> We're implementing it.
>>
>> As I mentioned earlier. Our aim here is *not* to encourage (or even
>> enable) cross-site javascript attacks on the Jenkins wiki. But to take a
>> step in the right direction of the vision that was put together last
>> summer; that documentation should ideally be MarkDown that could live in a
>> folder together with the source code itself, in the individual plugin
>> repositories - and still be released as part of the deployment process and
>> displayed on the community wiki - where it belongs.
>>
>> We're just making the statement, that having the documentation in the
>> repo instead of enforcing the manual detached update process on the
>> Confluence wiki is doable: We're suggesting a process.
>>
>> If we could - as an experiment - actually display the documentation on
>> the confluence wiki, it would enable us to get some user feedback (an
>> experiment, a Proof of Concept) - that *something like this* could be
>> the end result, and start a debate wether or not that would be desirable.
>>
>> We're prepared to convert the documentation of all our plugins to
>> MarkDown, so there would be a substantial material to gain the feed back
>> from.
>>
>> Generating static html from the MarkDown is as easy as running jekyll
>> build so the only blocker right now is to figure out a way to have that
>> html displayed on the plugin page on the confluence wiki.
>>
>> I'm not advocating that enabling {html-include:} is the right solution -
>> but it *is* nevertheless *a* solution, which - by the click of a
>> checkbox - would enable us to get som feedback on the concept. ≈ Proof of
>> Concept.
>>
>> Or it could even continue to be handled by a 

Re: Adopt request for jenkins-cloudformation-plugin

[Nathan Good]

Thanks, I have the account set up. It's nathanagood.



On Wed, Feb 3, 2016, 2:05 PM Baptiste Mathus  wrote:

> Compulsory: "Wow, that escalated quickly" :-)
>
> The plugin was indeed marked so yesterday when his current maintainer sent
> an email here.
>
> To grant you rights correctly, you're gonna need a full Jenkins-ci.org
> account too.
> https://jenkins-ci.org/account/signup
>
> Then provide your user id (because of current spam attack going on,
> creating that account may require more validation. Can be quick if you can
> come over IRC).
>
> Cheers
>
> 2016-02-03 20:47 GMT+01:00 Nathan Good :
>
>> Hello, this plugin is up for adoption. I (GitHub id nathanagood) would
>> like to be added as a maintainer. Please let me know if there is any
>> additional information you need from me.
>>
>> Best regards,
>>
>> --Nathan Good
>>
> --
>> 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/CAMo0kZgYENpw4v8XmK9VpibzQtpetMS577H7oksVfHjxNhsV1Q%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/CANWgJS75UZq%2BOQnDWR0FahoXv7m%2Bzr8u-AAQr41nLwHa8xpErA%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/CAMo0kZhA92pioj9RAKkSiKPFZJ9_qUc_SwbpwrO8A11KvvTmvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot read property 'value' of undefined

[Oscar Serna]

Thanks to you for helping me, don't hesitate to ask me whatever you need...


On Thursday, February 4, 2016 at 3:43:06 PM UTC+1, Antonio Muñiz wrote:
>
> Thanks for the example code. I'll take a look. 
>
> On Wed, Feb 3, 2016 at 12:55 PM, Oscar Serna  > wrote: 
> > Ey, I forgot to tell you that I saw the same problem with the 
> > ssh-agent-plugin plugin: 
> > 
> > https://wiki.jenkins-ci.org/display/JENKINS/SSH+Agent+Plugin 
> > 
> > As you can see in the capture below, if there is no credentials 
> configured 
> > previously, the list is empty and I see the same error: 
> > 
> > 
> > 
> > 
> > 
> > On Wednesday, February 3, 2016 at 12:14:43 PM UTC+1, Oscar Serna wrote: 
> >> 
> >> Also the URL: 
> >> 
> >> https://github.com/oserna/jenkins-plugin-example 
> >> 
> >> regards!! 
> >> 
> >> On Wednesday, February 3, 2016 at 12:13:56 PM UTC+1, Oscar Serna wrote: 
> >>> 
> >>> Hi Antonio, I've just seen your answer right now. I've created a 
> simple 
> >>> github repo with the code in order to allow you to reproduce the 
> error. The 
> >>> repo contains no more than several files, so it's really easy to set 
> the 
> >>> environment and get the error. 
> >>> 
> >>> Thanks in advance for your help. 
> >>> 
> >>> 
> >>> 
> >>> On Tuesday, February 2, 2016 at 9:13:04 PM UTC+1, Antonio Muñiz wrote: 
>  
>  Hi Oscar, 
>  
>  I don't see anything suspicious in your screenshots. 
>  If you provide a failing example (a public repo in GH?) I can take a 
>  look. 
>  
>  On Tue, Feb 2, 2016 at 12:59 PM, Oscar Serna  
>  wrote: 
> > 
> > 
> > Thanks for your quickly answer, below you can see what I have in my 
> in 
> > the Jelly config.jelly file: 
> > 
> > 
> > 
> > 
> > 
> > and in the Descriptor part: 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > In the next schema you can see the error: 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > It happens during the first two calls, the first one is a call to 
> > doFillStateItems() and just immediately after there is another call 
> to 
> > doFillCityItems(@QueryParameter String state) but without 
> parameters. In 
> > that case as you can see in the java code, I’m currently returning 
> an empty 
> > ListBoxModel 
> > 
> > 
> > 
> > Regards and thanks in advance. 
> > 
> > 
> > On Tuesday, February 2, 2016 at 12:43:35 PM UTC+1, Antonio Muñiz 
> wrote: 
> >> 
> >> Hi, 
> >> 
> >> First, what do you have in the jelly file? 
> >> And second, what's the real name of doFillXXX? It should be 
> >> "doFillXXXItems", where XXX is the name of the bean property. 
> >> 
> >> On Tue, Feb 2, 2016 at 10:08 AM, Oscar Serna  
>
> >> wrote: 
> >> > Hi devs, 
> >> > 
> >> > I'm working in a Jenkins plugin and I'm struggling with an issue. 
> >> > AFAIK in 
> >> > order to populate select combo using web methods the common 
> pattern 
> >> > to 
> >> > follow is to add this type of methods in the Descriptor class, as 
> >> > you can 
> >> > see below: 
> >> > 
> >> > public ListBoxModel doFillXXX(){ 
> >> >   ListBoxModel m = new ListBoxModel(); 
> >> >   for(){ 
> >> > ... 
> >> >m.add(displayName, name); 
> >> >   } 
> >> >   return  m; 
> >> > } 
> >> > 
> >> > However when the list is empty, so there is just the m object 
> >> > without 
> >> > Options I have an error in the Javascript select.js file. The 
> error 
> >> > is this: 
> >> > 
> >> > Uncaught TypeError: Cannot read property 'value' of undefined 
> >> > hasChanged @select.js:46 
> >> > updateListBox.onSuccess @select.js:76 
> >> > config.onSuccess @select.js:32 
> >> > Ajax.Request.Class.create.respondToReadyState 
> >> > @prototype.js:1657 
> >> > Ajax.Request.Class.create.onStateChange @prototype.js:1600 
> >> > (anonymous function) @prototype.js:414 
> >> > 
> >> > 
> >> > and in that line of the select.js file you can see: 
> >> > 
> >> > Behaviour.specify("SELECT.select", 'select', 1000, function(e) { 
> >> > 
> >> > function hasChanged(selectEl, originalValue) { 
> >> > var firstValue = selectEl.options[0].value; 
> >> > var selectedValue = selectEl.value; 
> >> > if (originalValue == "" && selectedValue == 
> firstValue) 
> >> > { 
> >> > // There was no value pre-selected but after the 
> >> > call to 
> >> > updateListBox the first value is selected by 
> >> > // default. This must not be considered a change. 
> >> > return false; 
> >> > } else { 
> >> > return originalValue != selectedValue; 
> >> > } 
> 

Re: Pull request to fix JENKINS-26318

[Slawomir Czarko-Wasiutycz]

Hi,

I program in C++ and my recent Java experience is only due to implementing 
a couple of bug fixes for Jenkins plugins.

Having said that I can give maintaining this plugin a go if the plugin is 
for adoption.

Cheers


On Thursday, 4 February 2016 14:46:50 UTC+1, Baptiste Mathus wrote:
>
> Hi,
>
> Though this plugin is not (yet?) marked as "to be adopted", I feel like we 
> would actually need to check how the current maintainer feels about.
>
> @Slawomir: in the event of the current maintainer confirming he doesn't 
> work on this anymore, would you be ready to take over maintenance?
> (that is: handling the plugin for /some/ time).
>
> Cheers
>
> 2016-02-04 11:58 GMT+00:00 Slawomir Czarko-Wasiutycz  >:
>
>> Hello,
>>
>> I haven't had any response on the pull request to fix JENKINS-26318 
>> (issue here: https://issues.jenkins-ci.org/browse/JENKINS-26318)
>>
>> https://github.com/jenkinsci/BlameSubversion-plugin/pull/2
>>
>> What additional steps should be done to get this accepted?
>>
>> Thank you,
>>
>> Slawomir
>>
>> -- 
>> 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/5815dedb-fdbd-40e3-b02c-26ec17fb0a35%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/3b437c58-c21a-40c7-8712-5665b1fb3ae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Cannot read property 'value' of undefined

[Antonio Muñiz]

Thanks for the example code. I'll take a look.

On Wed, Feb 3, 2016 at 12:55 PM, Oscar Serna  wrote:
> Ey, I forgot to tell you that I saw the same problem with the
> ssh-agent-plugin plugin:
>
> https://wiki.jenkins-ci.org/display/JENKINS/SSH+Agent+Plugin
>
> As you can see in the capture below, if there is no credentials configured
> previously, the list is empty and I see the same error:
>
>
>
>
>
> On Wednesday, February 3, 2016 at 12:14:43 PM UTC+1, Oscar Serna wrote:
>>
>> Also the URL:
>>
>> https://github.com/oserna/jenkins-plugin-example
>>
>> regards!!
>>
>> On Wednesday, February 3, 2016 at 12:13:56 PM UTC+1, Oscar Serna wrote:
>>>
>>> Hi Antonio, I've just seen your answer right now. I've created a simple
>>> github repo with the code in order to allow you to reproduce the error. The
>>> repo contains no more than several files, so it's really easy to set the
>>> environment and get the error.
>>>
>>> Thanks in advance for your help.
>>>
>>>
>>>
>>> On Tuesday, February 2, 2016 at 9:13:04 PM UTC+1, Antonio Muñiz wrote:

 Hi Oscar,

 I don't see anything suspicious in your screenshots.
 If you provide a failing example (a public repo in GH?) I can take a
 look.

 On Tue, Feb 2, 2016 at 12:59 PM, Oscar Serna 
 wrote:
>
>
> Thanks for your quickly answer, below you can see what I have in my in
> the Jelly config.jelly file:
>
>
>
>
>
> and in the Descriptor part:
>
>
>
>
>
>
>
> In the next schema you can see the error:
>
>
>
>
>
>
>
> It happens during the first two calls, the first one is a call to
> doFillStateItems() and just immediately after there is another call to
> doFillCityItems(@QueryParameter String state) but without parameters. In
> that case as you can see in the java code, I’m currently returning an 
> empty
> ListBoxModel
>
>
>
> Regards and thanks in advance.
>
>
> On Tuesday, February 2, 2016 at 12:43:35 PM UTC+1, Antonio Muñiz wrote:
>>
>> Hi,
>>
>> First, what do you have in the jelly file?
>> And second, what's the real name of doFillXXX? It should be
>> "doFillXXXItems", where XXX is the name of the bean property.
>>
>> On Tue, Feb 2, 2016 at 10:08 AM, Oscar Serna 
>> wrote:
>> > Hi devs,
>> >
>> > I'm working in a Jenkins plugin and I'm struggling with an issue.
>> > AFAIK in
>> > order to populate select combo using web methods the common pattern
>> > to
>> > follow is to add this type of methods in the Descriptor class, as
>> > you can
>> > see below:
>> >
>> > public ListBoxModel doFillXXX(){
>> >   ListBoxModel m = new ListBoxModel();
>> >   for(){
>> > ...
>> >m.add(displayName, name);
>> >   }
>> >   return  m;
>> > }
>> >
>> > However when the list is empty, so there is just the m object
>> > without
>> > Options I have an error in the Javascript select.js file. The error
>> > is this:
>> >
>> > Uncaught TypeError: Cannot read property 'value' of undefined
>> > hasChanged @select.js:46
>> > updateListBox.onSuccess @select.js:76
>> > config.onSuccess @select.js:32
>> > Ajax.Request.Class.create.respondToReadyState
>> > @prototype.js:1657
>> > Ajax.Request.Class.create.onStateChange @prototype.js:1600
>> > (anonymous function) @prototype.js:414
>> >
>> >
>> > and in that line of the select.js file you can see:
>> >
>> > Behaviour.specify("SELECT.select", 'select', 1000, function(e) {
>> >
>> > function hasChanged(selectEl, originalValue) {
>> > var firstValue = selectEl.options[0].value;
>> > var selectedValue = selectEl.value;
>> > if (originalValue == "" && selectedValue == firstValue)
>> > {
>> > // There was no value pre-selected but after the
>> > call to
>> > updateListBox the first value is selected by
>> > // default. This must not be considered a change.
>> > return false;
>> > } else {
>> > return originalValue != selectedValue;
>> > }
>> > };
>> >
>> > So, it seems like not adding options to the select causes this
>> > issue.
>> > Probably I'm making some type of mistake or maybe I'm missing
>> > something. Any
>> > help will be welcome. My Jenkins version is 1.644.
>> >
>> > Thanks in advance.
>> >
>> >
>> > --
>> > 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.

Re: Pull request to fix JENKINS-26318

[Baptiste Mathus]

Hi,

Though this plugin is not (yet?) marked as "to be adopted", I feel like we
would actually need to check how the current maintainer feels about.

@Slawomir: in the event of the current maintainer confirming he doesn't
work on this anymore, would you be ready to take over maintenance?
(that is: handling the plugin for /some/ time).

Cheers

2016-02-04 11:58 GMT+00:00 Slawomir Czarko-Wasiutycz <
slawomir.cza...@gmail.com>:

> Hello,
>
> I haven't had any response on the pull request to fix JENKINS-26318 (issue
> here: https://issues.jenkins-ci.org/browse/JENKINS-26318)
>
> https://github.com/jenkinsci/BlameSubversion-plugin/pull/2
>
> What additional steps should be done to get this accepted?
>
> Thank you,
>
> Slawomir
>
> --
> 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/5815dedb-fdbd-40e3-b02c-26ec17fb0a35%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/CANWgJS5RVH3dBT2bj--s2R5M1PsM3%3DQNjvtfacex59kgzriEcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: simpleBuild - a pipeline DSL (and a sad tale about sandboxes)

[Robert Sandell]

I know by experience that map.isEmpty() is not whitelisted by default. But
things like [k: v] and map[k] = v should work since I use it often for the
parallel step and I don't remember tearing out what little hair I have left
the first time I tried it. ;)

/B

On Thu, Feb 4, 2016 at 3:41 PM, Jesse Glick  wrote:

> Try `[k: v]` not `[k = v]`, and file bugs in `script-security-plugin`
> (label `workflow`) as needed.
>
> --
> 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/CANfRfr0o91owSQrfyb7-o8dS2ftNZBP9Mb_CD7D%3Dvinp3A_cXA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Adopt request for jenkins-cloudformation-plugin

[Baptiste Mathus]

All in!

Made you a committer of the plugin, you should have received an invitation.
Also made you the lead of the cloudformation-plugin JIRA component.

Welcome aboard!


2016-02-05 2:05 GMT+01:00 Nathan Good :

> Thanks, I have the account set up. It's nathanagood.
>
>
>
> On Wed, Feb 3, 2016, 2:05 PM Baptiste Mathus  wrote:
>
>> Compulsory: "Wow, that escalated quickly" :-)
>>
>> The plugin was indeed marked so yesterday when his current maintainer
>> sent an email here.
>>
>> To grant you rights correctly, you're gonna need a full Jenkins-ci.org
>> account too.
>> https://jenkins-ci.org/account/signup
>>
>> Then provide your user id (because of current spam attack going on,
>> creating that account may require more validation. Can be quick if you can
>> come over IRC).
>>
>> Cheers
>>
>> 2016-02-03 20:47 GMT+01:00 Nathan Good :
>>
>>> Hello, this plugin is up for adoption. I (GitHub id nathanagood) would
>>> like to be added as a maintainer. Please let me know if there is any
>>> additional information you need from me.
>>>
>>> Best regards,
>>>
>>> --Nathan Good
>>>
>> --
>>> 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/CAMo0kZgYENpw4v8XmK9VpibzQtpetMS577H7oksVfHjxNhsV1Q%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/CANWgJS75UZq%2BOQnDWR0FahoXv7m%2Bzr8u-AAQr41nLwHa8xpErA%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/CAMo0kZhA92pioj9RAKkSiKPFZJ9_qUc_SwbpwrO8A11KvvTmvg%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/CANWgJS5TqDc9LRcPKKPjtWvci39ibKU7o5nSi9LT2pK8waZDfQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins World Call For Paper is Open

[Alyssa Tong]

Hi All,

In case you haven't seen the post, Jenkins World CFP
is
currently open.
Submissions will be accepted until May 1, 2016 @ 11:59pm PT.  Event dates
are Sept 13-15, 2016 at the Santa Clara Convention Center.

looking forward to receiving submissions from around the globe!

Jenkins World CFP is HERE
.

thanks,
alyssa

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

Re: simpleBuild - a pipeline DSL (and a sad tale about sandboxes)

[Jesse Glick]

Try `[k: v]` not `[k = v]`, and file bugs in `script-security-plugin`
(label `workflow`) as needed.

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

Bitbucket Server plugin

[Tomas Bjerre]

Now that "Atlassian Stash" has changed name to "Atlassian Bitbucket 
Server", perhaps some of the plugins 
(https://github.com/jenkinsci?utf8=%E2%9C%93=stash) should also 
change name. Or they can all be merged into 1 single plugin "Bitbucket 
Server plugin". What do you think?

-- 
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/3c33d9b6-8b8a-490e-83f6-9bc424de2bbf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Backporting for 1.642.2 done

[Oliver Gondža]

Hi,

The backporting is done. We are ready for the RC.

One issue rejected: 
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%201.642.2-rejected
Most issues backported: 
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%201.642.2-fixed


--
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/56B38AE9.9040406%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Enable html-include macro in the Jenkins tracking system

[Robert Sandell]

I did mention the discussions we had on the Code Camp on the Jenkins 2.0
Summit after FOSDEM while we were discussing the plugin documentation
topic, but since we haven't heard anything about it since the Code Camp we
couldn't assume anything about it. And the technology and focus has changed
since then.

You've had plenty of time to chime in to the website and documentation
discussions that has been going on for a while on this list. And iirc KK's
presentation about the goals of Jenkins 2.0, on this list, the blog, and
office hours, is mentioning that Confluence will most likely die, so you've
had some time to rethink and restart the discussions around how to handle
the plugin docs.
So I could only assume that you weren't working on it any more and so the
Summit decided on a similar but slightly different approach of building the
plugin documentations into the new jenkins.io site.

Now IIUC jekyll and awestruct is pretty similar, so your work might be
reusable in jenkins.io [1] so that rtyler and the website team doesn't have
to do all the work themselves?

[1] https://github.com/jenkins-infra/jenkins.io

/B


On Wed, Feb 3, 2016 at 8:49 PM, Lars Kruse  wrote:

> >why wouldn't linking from the
> >wiki to the generated GitHub pages repository suffice?
>
> ...well that wouldn't index to content on search engines in context of the
> plugin - where we personally think that it belongs.
>
> I believe that both job DSL and pipeline plugins are doing what they are
> doing - because the current state of the Jenkins confluence wiki is not
> accommodating their needs (documentation along side the code). And driving
> more and more plugins *away* from the wiki - as you just encouraged me to
> do, is not the solution. Finding a way to contain the documentation inside
> the wiki *is*.
>
> >One of the very active discussions we've had recently in IRC and in person
> >(FOSDEM) has been providing better documentation integration for plugin
> >developers on the Jenkins primary site.
>
> Great, that you are discussing it! However, that dialog was kickstarted on
> my colleague's Bue's initiative at the Jenkins Code Camp
>  in Copenhagen last
> summer, where he and Bobby Sandell and a handfuld of others discussed a
> possible solution along the lines of what Bue describes in this blog
> .
> We're implementing it.
>
> As I mentioned earlier. Our aim here is *not* to encourage (or even
> enable) cross-site javascript attacks on the Jenkins wiki. But to take a
> step in the right direction of the vision that was put together last
> summer; that documentation should ideally be MarkDown that could live in a
> folder together with the source code itself, in the individual plugin
> repositories - and still be released as part of the deployment process and
> displayed on the community wiki - where it belongs.
>
> We're just making the statement, that having the documentation in the repo
> instead of enforcing the manual detached update process on the Confluence
> wiki is doable: We're suggesting a process.
>
> If we could - as an experiment - actually display the documentation on the
> confluence wiki, it would enable us to get some user feedback (an
> experiment, a Proof of Concept) - that *something like this* could be the
> end result, and start a debate wether or not that would be desirable.
>
> We're prepared to convert the documentation of all our plugins to
> MarkDown, so there would be a substantial material to gain the feed back
> from.
>
> Generating static html from the MarkDown is as easy as running jekyll
> build so the only blocker right now is to figure out a way to have that
> html displayed on the plugin page on the confluence wiki.
>
> I'm not advocating that enabling {html-include:} is the right solution -
> but it *is* nevertheless *a* solution, which - by the click of a checkbox
> - would enable us to get som feedback on the concept. ≈ Proof of Concept.
>
> Or it could even continue to be handled by a confluence macro. Think more
> in the terms of the final solution looking like this:
>
> {jenkins-plugin-info:pluginId=monkit-plugin}
>
> {markdown-documentation:src="/docs/"}
>
>
> Where {markdown-documentation} could be a confluence macro that builds
> whatever is on the master branch in the $(src) path of the plugin's
> repository, and then just insert the generated html - at this point -
> provided that a) jekyll build is succesful and b) the generated code
> doesn't contain any java script.
>
>
> >I personally don't want to spend much
> >effort, right now, on experimenting with a half-way solution which
> further
> >fragments documentation for users.
>
> I don't see why our contribution deserves to be categorized as *half-way* or
> *further fragmenting documentation*. Quite the opposite, Your
> encouragement thet we should host our documentation somewhere else is *further
> 

Re: Bitbucket Server plugin

[domi]

not sure about this, there are already a couple of bitbucket plugins and all of 
these address the hosted service bitbucket.
/Domi


> On 04 Feb 2016, at 16:38, Tomas Bjerre  wrote:
> 
> Now that "Atlassian Stash" has changed name to "Atlassian Bitbucket Server", 
> perhaps some of the plugins 
> (https://github.com/jenkinsci?utf8=%E2%9C%93=stash) should also change 
> name. Or they can all be merged into 1 single plugin "Bitbucket Server 
> plugin". What do you think?
> 
> -- 
> 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/3c33d9b6-8b8a-490e-83f6-9bc424de2bbf%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/9F4305C0-80FF-4180-B7AD-9B4C4BB61FBD%40fortysix.ch.
For more options, visit https://groups.google.com/d/optout.

Re: Request hosting for Performance Signature Plugin

[Raphael Pionke]

We pushed our changes in our repo 
.
Any update to this?

Kind regards,
Raphael


Am Donnerstag, 28. Januar 2016 14:07:06 UTC+1 schrieb Raphael Pionke:
>
> Hey Daniel,
>
> Sorry about the delay, we've developed a lot on the plugin and we're fine 
> with renaming the pluginID to "performance-signature-dynatrace".
> The displayname will be changed to "Performance Signature with Dynatrace".
>
> Are you fine with these changes?
>
> Am Donnerstag, 17. Dezember 2015 16:44:57 UTC+1 schrieb Daniel Beck:
>>
>> The plugin ID should ideally be close to the display name (as it's used 
>> e.g. in JIRA as component), and obvious about what it is. So 'dynatrace' 
>> should be in there. 
>>
>> On 17.12.2015, at 16:33, Raphael Pionke  wrote: 
>>
>> > Hi Oleg and Wolfgang, 
>> > 
>> > thanks Wolfgang for your answer. 
>> > We got Dynatrace already in the Plugin title: "Performance Signature 
>> with Dynatrace Plugin". 
>> > Do we have to update the artifactId, since we use plugin in several 
>> environments? 
>> > 
>> > Kind regards, 
>> > Raphael 
>> > 
>> > 
>> > Am Montag, 23. November 2015 10:38:08 UTC+1 schrieb Wolfgang 
>> Gottesheim: 
>> > Hi, 
>> > 
>> > It looks like I can't post to Google groups from the work email address 
>> I initially used here, sorry about the delay in getting back to you... 
>> > 
>> > - I'm also fine with replacing the current plugin with the new one, as 
>> it kind of replaces/augments the existing plugin anyway. 
>> > - I agree that the "dynatrace" prefix makes sense in any case. 
>> > 
>> > 
>> > Am Sonntag, 27. September 2015 21:43:47 UTC+2 schrieb Oleg Nenashev: 
>> > I've added the Dynatrace plugin owner to Cc. It would be great to get 
>> his feedback before going forward. 
>> > 
>> > Even if we go forward with a new plugin: 
>> > * performance-signature is vague IMHO 
>> > * If the plugin is dynatrace-specific, I would prefer to see 
>> "dynatrace" in its name 
>> > 
>> > пятница, 25 сентября 2015 г., 10:25:20 UTC+3 пользователь Raphael 
>> Pionke написал: 
>> > Any update to this? 
>> > 
>> > Kind regards, 
>> > Raphael 
>> > 
>> > Am Dienstag, 22. September 2015 11:09:59 UTC+2 schrieb Raphael Pionke: 
>> > Hi Oleg, 
>> > 
>> > we know the other Dynatrace plugin and after a long evaluation, we have 
>> decided to developed a new plugin with (good) serious reasons 
>> > 
>> > • completely different Workflow (the new plugin consists of 
>> several build-steps and a post-processing step) 
>> > • both Plugins can only handle Dynatrace as APM Tool, in future 
>> plugin versions Dynatrace will be replaced by other APM Tools 
>> > the original Plugin can only handle Dynatrace as APM Tool, the new 
>> Plugin is designed to be independent  from a specific APM-Tool (although 
>> currently only Dynatrace is supported) 
>> > • different approach to gain performance data (the current 
>> plugin uses a xml-report, the new uses Dynatrace Rest API) 
>> > • code reuse or integration is not imaginable / requires a hugh 
>> effort 
>> > • the most important thing is; the old Dynatrace plugin can 
>> only handle Unit tests, the new plugin can deal with different kinds of 
>> tests e.g. performance/load test, interfacetest, ui-test … 
>> > I thTo avoid name conflicts the plugin name should be like this: 
>> performance-signature 
>> > 
>> > Regards, 
>> > Raphael 
>> > 
>> > 
>> > Am Mittwoch, 16. September 2015 11:37:20 UTC+2 schrieb Oleg Nenashev: 
>> > There is and existing plugin for Dynatrace, which does the similar 
>> thing. https://wiki.jenkins-ci.org/display/JENKINS/Dynatrace+Plugin 
>> > 
>> > What is the difference between plugins? Would it be possible to merge 
>> the functionality? 
>> > 
>> > вторник, 15 сентября 2015 г., 15:00:17 UTC+3 пользователь Raphael 
>> Pionke написал: 
>> > Hi, 
>> > 
>> > this plugin fetches performance values from Dynatrace XML Dashboards 
>> during a build and evaluates and compares the result with previous builds 
>> and non-functional requirements. This plugin uses user-specified XML 
>> Dashboards and PDF detail Reports. Additionally this plugin adds several 
>> build steps to trigger the Dynatrace REST interface. 
>> > 
>> > Plugin name: performance-signature-dynatrace 
>> > Github ID: rpionke 
>> > Repository: https://github.com/T-Systems-MMS/perfsig-jenkins 
>> > 
>> > It would be nice to have it hosted on jekins-ci. 
>> > 
>> > Thanks in advance, 
>> > Raphael 
>> > 
>> > 
>> > 
>> > 
>> > -- 
>> > 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/4dcb1967-d92e-42b8-a37e-71152d3971ae%40googlegroups.com.
>>  
>>
>> > For more options, visit 

Re: Bitbucket Server plugin

[Tomas Bjerre]

When responding to this, you should know that "Bitbucket" and "Bitbucket
Server" are two different products, with different API:s.

Get commits from Bitbucket:
https://confluence.atlassian.com/bitbucket/commits-or-commit-resource-389775478.html#commitsorcommitResource-GETacommitslistforarepositoryorcomparecommitsacrossbranches

Get commits from Bitbucket Server:
https://developer.atlassian.com/static/rest/bitbucket-server/4.3.1/bitbucket-rest.html#idp2523328

Browse the API:s and you will see more examples.

In my opinion, the naming is confusing. But that is a decision made by
Atlassian and nothing we can change. We can reduce the confusion by
renaming the stash-plugins to bitbucket-server-plugins. Because as more and
more users move to Bitbucket Server, people will forget that it was once
called Stash.


2016-02-04 16:39 GMT+01:00 domi :

> not sure about this, there are already a couple of bitbucket plugins and
> all of these address the hosted service bitbucket.
> /Domi
>
>
> On 04 Feb 2016, at 16:38, Tomas Bjerre  wrote:
>
> Now that "Atlassian Stash" has changed name to "Atlassian Bitbucket
> Server", perhaps some of the plugins (
> https://github.com/jenkinsci?utf8=%E2%9C%93=stash) should also
> change name. Or they can all be merged into 1 single plugin "Bitbucket
> Server plugin". What do you think?
>
> --
> 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/3c33d9b6-8b8a-490e-83f6-9bc424de2bbf%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/ZZNVeE6mdA0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/9F4305C0-80FF-4180-B7AD-9B4C4BB61FBD%40fortysix.ch
> 
> .
>
> 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/CAK89W5KKNePJphN6BgN1_nR6cGiDwYnnJmoJT4MwoBrGg8vpNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

simpleBuild - a pipeline DSL (and a sad tale about sandboxes)

[Michael Neale]

Inspired by Jesse's example 

 DSL 
using docker workflow, I thought I would see how far I could take things in 
making DSLs. 
I wanted to make things that looked very similar to what people do with 
tools like travis - something at home in a Jenkinsfile that anyone can 
open, and read and immediately comprehend, for simple cases, what the build 
instructions are. 

This is mostly pretty easy: I have put it here for now 
https://github.com/michaelneale/jenkinsfile (until I sort out some issues). 
It can work with or without docker workflow (you just specify an image, or 
not), sends emails (even in failure), set environment variables etc, of 
course I would love for it to do more. 

However, one road block has been my use of literal maps and the sandbox. 
This all works grand if I don't use the sandbox, but use the sandbox (or 
multibranch/SCM, which enables sandbox), and sadness results that I can't 
work out how to get around:

org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: 
Scripts not permitted to use field java.util.HashMap$Node key
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectField(StaticWhitelist.java:169)
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.rejectField(SandboxInterceptor.java:195)
at 
org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:

- this shows up when I enable the sandbox (sadbox?). 

It seems NOTHING in java.util.Map is whitelisted. I am using maps at the 
moment as it makes for a nice DSL similar to what people may see elsewhere. 
For example: 

simpleBuild {

script = 'echo after $FOO'

notifications = [
email : "mne...@cloudbees.com"
]

env = [
FOO = "well hello",
BAR = "I don't even need to be here"
]

}

This is valid and works great *without* sandbox, but fails on notifications 
with sandbox on.  The notifications item (config.notifications in the DSL, 
from the closure passed into simpleBuild) is a java.util.Map. If I look 
closer, its actually a LinkedHashMap. 

Does any one have ideas on ways to get around this? the literal map 
notation is very neat, and would take no time for someone to glance at and 
follow, however, I don't see a way of working with a Map (I can call size() 
it seems, but nothing else, I can't get the values() or keySet() 
collections etc). 

Any ideas appreciated (perhaps using maps is inferior to another approach, 
which I would like to see, however, I love the idea of staying in 
pipieline-groovy script, with a DSL, as this takes away NONE of the power). 






-- 
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/685d07ee-0748-4666-924b-015113392ad7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: simpleBuild - a pipeline DSL (and a sad tale about sandboxes)

[domi]

I guess you already tried to prove the required calls in the script security 
plugin?
https://wiki.jenkins-ci.org/display/JENKINS/Script+Security+Plugin
/Domi


> On 04 Feb 2016, at 09:07, Michael Neale  wrote:
> 
> Inspired by Jesse's example 
> 
>  DSL using docker workflow, I thought I would see how far I could take things 
> in making DSLs. 
> I wanted to make things that looked very similar to what people do with tools 
> like travis - something at home in a Jenkinsfile that anyone can open, and 
> read and immediately comprehend, for simple cases, what the build 
> instructions are. 
> 
> This is mostly pretty easy: I have put it here for now 
> https://github.com/michaelneale/jenkinsfile 
>  (until I sort out some issues). 
> It can work with or without docker workflow (you just specify an image, or 
> not), sends emails (even in failure), set environment variables etc, of 
> course I would love for it to do more. 
> 
> However, one road block has been my use of literal maps and the sandbox. This 
> all works grand if I don't use the sandbox, but use the sandbox (or 
> multibranch/SCM, which enables sandbox), and sadness results that I can't 
> work out how to get around:
> 
> org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts 
> not permitted to use field java.util.HashMap$Node key
>   at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectField(StaticWhitelist.java:169)
>   at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.rejectField(SandboxInterceptor.java:195)
>   at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:
> 
> - this shows up when I enable the sandbox (sadbox?). 
> 
> It seems NOTHING in java.util.Map is whitelisted. I am using maps at the 
> moment as it makes for a nice DSL similar to what people may see elsewhere. 
> For example: 
> 
> simpleBuild {
> 
> script = 'echo after $FOO'
> 
> notifications = [
> email : "mne...@cloudbees.com"
> ]
> 
> env = [
> FOO = "well hello",
> BAR = "I don't even need to be here"
> ]
> 
> }
> 
> This is valid and works great *without* sandbox, but fails on notifications 
> with sandbox on.  The notifications item (config.notifications in the DSL, 
> from the closure passed into simpleBuild) is a java.util.Map. If I look 
> closer, its actually a LinkedHashMap. 
> 
> Does any one have ideas on ways to get around this? the literal map notation 
> is very neat, and would take no time for someone to glance at and follow, 
> however, I don't see a way of working with a Map (I can call size() it seems, 
> but nothing else, I can't get the values() or keySet() collections etc). 
> 
> Any ideas appreciated (perhaps using maps is inferior to another approach, 
> which I would like to see, however, I love the idea of staying in 
> pipieline-groovy script, with a DSL, as this takes away NONE of the power). 
> 
> 
> 
> 
> 
> 
> 
> -- 
> 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/685d07ee-0748-4666-924b-015113392ad7%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/6498A1FA-11AB-457E-802F-3A2248A5F73D%40fortysix.ch.
For more options, visit https://groups.google.com/d/optout.