Re: Request to host plugin "hierarchy-killer"

[Thorsten Möllers]

On 18/09/15 01:19, Daniel Beck wrote:

On 17.09.2015, at 17:04, Thorsten Möllers  wrote:


- I doubt you really need the RunData, why not query all running jobs for what 
their (upstream) causes are when you get notified about a run abort? Not sure 
what's saved/loaded in the Plugin class, but I expect the current design with the 
static >   HashMap doesn't handle a Jenkins restart well (the queue is 
persisted and restored on restart).

Because it is not only supposed to kill upstream. If I kill the upstream build, 
I want to kill other downstream builds as well. Problem is I couldn't find a a 
way to get a list of all downstream builds for a running build.
Therefore I collect this information at runtime.

Right. That's why I wrote you'd need to look at all running builds' causes to determine 
whether they are downstream from the "reference build". I think that should 
work and allow you to do this without RunData.
I don't think this is an option. We have a huge set of running jobs, a 
lot of them short lived, so I try to keep the cost for a single job 
exiting minimal. As I see it, currently the memory allocated in my 
plugin for a single build is O(1), since the hierarchy structure is more 
or less static. The execution time to handle a single notification is 
also O(1), for the same reason. Going through all builds would add an 
operation O(n), n being the number of currently running builds, which is 
quite huge in our system. Since a lot of our builds are short-lived, 
this task would be executed quite frequently.

.
Also the log info in the console output is invaluable for us, to see the 
full chain of jobs being killed leading to the most upstream one being 
killed. This data is collected in RunData.reason.



BTW, it looks like you don't look at queue items. If a build is still in the 
queue when you abort whatever is upstream from it, it'll not be canceled.


This would be a good improvement for the next version. But from what I 
see, Jenkins does not provide notifications for triggered builds, just 
for started ones. Where do I get a list of queued builds?





Jenkins restart: I have to make sure that no persistent data is stored.

If you have no persistent data, and the queue gets restored on restart, how can 
your plugin behave correctly afterwards?
Jenkins restart would be the exception. Usually, Jenkins runs for weeks 
in our setup without a restart, and when it restarts, it is usually a 
scheduled maintenance break where no jobs are active anyway. In the rare 
case of an unexpected Jenkins restart I could live with some builds 
being continued instead of aborted, it would be the least of our problems.

A non-library plugin without any UI is not a great idea as admins may easily 
forget it exists, and users don't even know it's there.

I agree, you have a point there. Not sure how to align with my previous comment 
though.

Maybe provide both static checkboxes in job config for all the options, and 
treat them like env-vars, giving users the option to use one or the other? 
Makes checking whether an option is set a bit more effort, but you have the 
option to do both full UI (static) config, and allow the alternative of 
per-build configuration through env vars.

I will look into it, but not for a first release probably.

For the naming: How about "BuildHierarchyKiller"? I think that would be 
unambiguous...


Br,
Thorsten

--
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/55FBA708.8050705%40thorzten.de.
For more options, visit https://groups.google.com/d/optout.

Re: Request hosting for plugin

[Oleg Nenashev]

Hi Catalin,

What are your GitHub and JIRA accounts? Should we also add Andrei to the 
plugin developers?

Thanks in advance,
Oleg

понедельник, 14 сентября 2015 г., 14:45:34 UTC+3 пользователь Catalin Luta 
написал:
>
> Hello guys,
>
> I've received a reply from Stephan. Due to lack of time he can no longer 
> maintain the plugin (JiraTestResultReporter), so he would be happy if we 
> could take it over. 
>
> Is there a standard procedure of doing this?
>
> Cheers,
> Catalin
>

-- 
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/6a13d22b-1837-4c86-bfaa-4757cda1c00d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Guidance on how far SECURITY fixes should go

[Oleg Nenashev]

>
> The annotation processing to deliver BigFatSecuritySwitch (or deferring to 
> another method) is basically what I'd do.
>

It would be a simple way, but it does not allow a fine-grain control. The 
impact of the pending and potential fixes is too high, so many Jenkins 
installations may blow up.

Well @Restricted(DoNotUse.class) should give you a build time failure 
> if you are using the Maven toolchain... if you are using the groovy 
> toolchain I presume you can add the same checks... 

 

> We could then add an Admin monitor that looks at the until fields on 
> Jenkins and tells you if any of your plugins were compiled against a 
> version of Jenkins older than the until... similarly the plugin 
> manager could alert you for plugins that are compiled against an older 
> jenkins than your oldest until...
>

I like the idea of a second unsafe method, but we will also need to notify 
users that a plugin uses unsafe API. Otherwise instance maintainers won't 
be aware that they are installing a plugin having a security risk.

There are following TODOs:

   - Just warn users about it in UC
   - Process the limitations in Script Security Plugin
   - [Optional] - Allow filtering out plugins with unsafe API by a global 
   switch in UC
   - [Optional] - Process plugins during the load/installation procedure 
   and add all kinds admin monitors
  - It is especially required to cover the use-case with manual plugin 
  installation
   
I suspect the efforts would be quite big in any case.


среда, 16 сентября 2015 г., 17:02:54 UTC+3 пользователь Jesse Glick написал:
>
> On Wed, Sep 16, 2015 at 7:27 AM, Stephen Connolly 
> > wrote: 
> > @UnsecureAlternative(name="getFooUnsafe", until="1.650") 
> > public Foo getFoo(...) { 
> > ... 
> > } 
>
> Too complicated, too reflective. Let us keep it to basic 
> statically-checked idioms as much as possible. 
>
> Anyway I am not convinced the actual problems at hand warrant this 
> much fuss, or any incompatibility at all, but it cannot be discussed 
> here. 
>

-- 
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/869ee2f4-01eb-40e3-8de1-9ce209955b4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new Plugin hosting

[Oleg Nenashev]

Hello,

I've forked the repository and created the JIRA component.
The new location 
is: https://github.com/jenkinsci/convertigo-mobile-platform-plugin
You should get an invitation to jenkinsci organisation soon.

Welcome aboard!

Best regards,
Oleg


среда, 16 сентября 2015 г., 18:01:25 UTC+3 пользователь Olivier Picciotto 
написал:
>
> Hello,
>
>  
>
> convertigo-mobile-platform  is OK.
>
>  
>
> We will change the id in the GIT repo.
>
>  
>
> Thanks
>
> Olivier
>
>  
>
>  
>
> *De :* jenkin...@googlegroups.com  [mailto:
> jenkin...@googlegroups.com ] *De la part de* Oleg Nenashev
> *Envoyé :* mercredi 16 septembre 2015 10:42
> *À :* Jenkins Developers >
> *Objet :* Re: Request for new Plugin hosting
>
>  
>
> Seems Convertigo has several products, so probably it makes sense to add 
> something else to the plugin ID. "ci" seems to be also vague for me, 
> because the plugin could be used for CD and other methodologies and 
> marketing buzz-words.
>
>  
>
> What about "convertigo-madp" or "convertigo-mobile-platform"?
>
>
> вторник, 15 сентября 2015 г., 7:50:39 UTC+3 пользователь Olivier Picciotto 
> написал:
>
> Hello, 
>
>  
>
> Any news about this request ?
>
>  
>
> Kind Regards
>
> Olivier
>
>  
>
> -- 
> 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/lvi8CGnS9Bo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-de...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/4def2c83-8436-4ec1-ac7d-e0c59f1c8536%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/197e4a86-d2a6-4a3a-bf6e-9a81b19ec1f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new plugin hosting

[Oleg Nenashev]

I've forked the repo and created the JIRA 
component. https://github.com/jenkinsci/groovy-events-listener-plugin
You should get a notification to jenkinsci organisation soon.

Welcome aboard!

пятница, 18 сентября 2015 г., 1:40:11 UTC+3 пользователь Nick Grealy 
написал:
>
> I'm happy with "groovy-events-listener-plugin" - sounds good. 
>
> I'll create a JIRA task for ththe integration, once the project is setup. 
>
> Thanks! 
>
>
>

-- 
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/4c0b9b45-f512-4426-888f-252dc3c20775%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

#jenkins-meeting is ready

[Daniel Beck]

Hi everyone,

A while back we decided to use a separate channel for the project governance 
meetings.

#jenkins-meeting is now ready to be used, so we should hold the next governance 
meeting there, and only post a reminder in #jenkins.

Daniel

-- 
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/822097CF-24FD-4359-96FB-30292B0CCD9A%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Jenkins Meetups and CIA

[Alyssa Tong]

Hi All,

There's an initiative to start Jenkins Area Meetup (JAM)

to help local communities stay on top of the latest and greatest Jenkins
technology. With over 120,000 active plugins it's important that we
continue to educate and inspire others on the use of Jenkins. We want to
spread Jenkins far and wide.

We are looking for folks who are interested in starting a JAM or
become a Jenkins
CIA . In
support of this effort, CloudBees has sponsored an initial $75,000 to help
communities startup/revive JAMs/CIA programs. If you've already established
a Jenkins Meetup, and need help getting your meeting started, I can
definitely help here as well, just shoot me an email.

Other ways you can be involved:

   - Sign up to become a speaker - share your war stories and show those
   battle scars!
   - Be a venue sponsor
   - Suggest a speaker who has a great Jenkins story to share.
   - Share your ideas for what makes JAMs relevant, and useful for the
   extended community.

Let's join forces to spread Jenkins!!!

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

Re: Request to host plugin "hierarchy-killer"

[Daniel Beck]

On 17.09.2015, at 17:04, Thorsten Möllers  wrote:

> 
>> - I doubt you really need the RunData, why not query all running jobs for 
>> what their (upstream) causes are when you get notified about a run abort? 
>> Not sure what's saved/loaded in the Plugin class, but I expect the current 
>> design with the static >   HashMap doesn't handle a Jenkins restart well 
>> (the queue is persisted and restored on restart).
> 
> Because it is not only supposed to kill upstream. If I kill the upstream 
> build, I want to kill other downstream builds as well. Problem is I couldn't 
> find a a way to get a list of all downstream builds for a running build.
> Therefore I collect this information at runtime.

Right. That's why I wrote you'd need to look at all running builds' causes to 
determine whether they are downstream from the "reference build". I think that 
should work and allow you to do this without RunData.

BTW, it looks like you don't look at queue items. If a build is still in the 
queue when you abort whatever is upstream from it, it'll not be canceled.

> Jenkins restart: I have to make sure that no persistent data is stored.

If you have no persistent data, and the queue gets restored on restart, how can 
your plugin behave correctly afterwards?

> 
>> A non-library plugin without any UI is not a great idea as admins may easily 
>> forget it exists, and users don't even know it's there.
> I agree, you have a point there. Not sure how to align with my previous 
> comment though.

Maybe provide both static checkboxes in job config for all the options, and 
treat them like env-vars, giving users the option to use one or the other? 
Makes checking whether an option is set a bit more effort, but you have the 
option to do both full UI (static) config, and allow the alternative of 
per-build configuration through env vars.

> 
>> - While I understand that Parameterized Trigger allows having an upstream 
>> project that still runs, I wonder doubt it's always only one, which seems to 
>> be the assumption in your code. While that feature may not consider quiet 
>> periods, the node may be missing, so two identically parameterized builds 
>> could be collapsed in the queue while waiting for the node to free up.
> Isn't this something only the Workflow plugin does? I saw it with workflow, 
> but never with Parameterized Trigger. If this is really an issue for normal 
> builds as well, I will replace iUpstream also with a list (vector).

- You have the build step provided by Parameterized Trigger that triggers a 
build which the current build is still running.
- A build waits in the queue until a required node ("Restrict where this can 
run") becomes available.
- Two queue items with identical parameters are collapsed into one and their 
causes merged.

I think it should be fairly straightforward to test this.

-- 
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/D7FFD881-8B99-49CB-9DA6-E2BFD3E9E58F%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new plugin hosting

[Nick Grealy]

I'm happy with "groovy-events-listener-plugin" - sounds good. 

I'll create a JIRA task for ththe integration, once the project is setup. 

Thanks! 


-- 
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/d2f12b04-6447-42a2-b21c-33071d0c2f62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new plugin hosting

[Nick Grealy]

I'm happy with "groovy-events-listener-plugin" - sounds good. 

I'll create a JIRA task for ththe integration, once the project is setup. 

Thanks! 


-- 
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/ff0d75c1-116a-4354-88c1-df21d88d4fac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new plugin hosting

[Nick Grealy]

I'm happy with "groovy-events-listener-plugin" - sounds good. 

I'll create a JIRA task for ththe integration, once the project is setup. 

Thanks! 


-- 
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/da94666c-3c18-4c63-8c8a-0239f2ec0a69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new plugin hosting

[Nick Grealy]

I'm happy with "groovy-events-listener-plugin" - sounds good. 

I'll create a JIRA task for ththe integration, once the project is setup. 

Thanks! 


-- 
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/b591b112-5efe-421c-99b1-39e8a357524e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new plugin hosting

[Nick Grealy]

I'm happy with "groovy-events-listener-plugin" - sounds good. 

I'll create a JIRA task for ththe integration, once the project is setup. 

Thanks! 


-- 
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/c49d0fd3-200c-45d8-8f1a-b68e88127106%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new plugin hosting

[Nick Grealy]

I'm happy with "groovy-events-listener-plugin" - sounds good. 

I'll create a JIRA task for ththe integration, once the project is setup. 

Thanks! 


-- 
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/c760331f-8bcf-4a27-9cc1-d30bf71a793c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hosting request for new plugin sumologic-publisher-plugin

[Deven Norton]

Github url: https://github.com/SumoLogic/sumologic-jenkins-plugin
target repo name: sumologic-publisher-plugin
github user id: devennorton
jenkinsci user id: d 
evennorton

publishes jenkins metadata to sumologic. Particularly build metadata 
(status, description, failed tests, duration, etc) and some periodic system 
metadata (number of slaves, free/busy executors, etc)

-- 
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/62082400-92ab-4899-916b-cfc9dc5fd646%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Hosting a new Plugin - Percentage DiskSpace usage column

[Victor Martinez]

Awesome Thanks Daniel, 

Regarding your question, I just wanted a tiny plugin with simple 
functionality rather than a complex one which might be harder to maintain. 
Thanks for the advice of the plugin name, I've just renamed it as 
"percentage-du-column"

*Repo*: https://github.com/v1v/percentage-du-column-plugin

Let me know if you need further clarification

Thanks again

On Tuesday, 15 September 2015 00:25:20 UTC+2, Daniel Beck wrote:
>
>
> On 02.09.2015, at 23:53, Victor Martinez  > wrote: 
>
> >  - The Extra Columns plugin is job based I'm afraid, does it make sense 
> to merge those functionalities? 
>
> No. You cannot actually hide node columns AFAIK, so every installed + 
> enabled plugin always contributes its columns to the list. Until this 
> changes, having a plugin collecting node columns would be bad. Like only 
> having the AllView and all columns being visible by default. 
>
> >  - Does it make sense to use % of remaining free disk space or % disk 
> usage? 
>
> Do you have options for slave columns like list view columns do, or do you 
> need to decide on one or the other? If the latter, I'd go for % used like 
> `df` does. 
>
> >  - Regarding the name of that plugin, what do you think about 
> "PercentageFreeDiskSpaceColumn" and "PercentageDiskUsageColumn"? Is it too 
> long? 
>
> FWIW in general the pattern is foo-bar-baz rather than FooBarBaz. 
>
> Otherwise this seems to be fine. It's a very narrow scoped plugin so the 
> name should be descriptive. 
>
> >  - Finally, Do you think it should handle some thresholds based on % in 
> order to monitor each slave as DiskSpace does? Is it a valuable use case? 
>
> Yes, absolutely. If you have very different slaves, a fixed threshold in 
> MB or GB may be useless, but something like 90% fill level across all 
> slaves before taking them offline may work. 
>
> Assuming nobody objects (I explained why a collection plugin, or really 
> any integration with something related, would be bad here) I'll fork this 
> tomorrow. 
>
>

-- 
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/4d6546cc-9eed-4d71-8468-7e14066e2f76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Next Windows Slave Installer release

[Oleg Nenashev]

New windows-slave-installer 
 has been 
released.
I've also created a PR to Jenkins 
core: https://github.com/jenkinsci/jenkins/pull/1832

среда, 16 сентября 2015 г., 10:50:28 UTC+3 пользователь Oleg Nenashev 
написал:
>
> Thanks for the reminder. I'm working on the new release.
>
> среда, 16 сентября 2015 г., 9:19:17 UTC+3 пользователь Claus Schneider 
> написал:
>>
>> Friendly reminder.. :)
>>
>> On Friday, August 28, 2015 at 9:19:46 AM UTC+2, Claus Schneider wrote:
>>>
>>> Hi..
>>>
>>> Sound good.. any ETA?
>>>
>>> Do you have a deep link to an integration for me to test it out..?
>>>
>>> br
>>> Claus
>>>
>>> On Tuesday, August 25, 2015 at 10:38:50 PM UTC+2, Oleg Nenashev wrote:

 The module has not been released yet. 
 I think it makes sense to bump the winsw dependency to 1.18 in order to 
 get several bugfixes.

 вторник, 25 августа 2015 г., 15:26:17 UTC+3 пользователь Claus 
 Schneider написал:
>
> Hi guys
>
> A follow-up on the JUES.. Great event and integrated code.. :)
>
> The  
> https://github.com/jenkinsci/windows-slave-installer-module/pull/2 
> 
>  is 
> merged in to the repo. I have tried to install the lastest weekly (1.626 
> ), 
> but it seems the change is not included. Kohsuke mentioned that it should 
> be automatically in the upcoming weekly. Unfortunately so far I have not 
> found any indication on the Change Log nor does it seem the change is 
> included..
> Or did it have a problem?
>
> Can I have an estimate of the release? 
>
> Thanks a lot in advance..
>
> // Claus Schneider
>


-- 
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/ed1e4d21-4d65-4a34-a931-19e1a77db332%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reg Root pom and svn directory info

[RajuS]

Hi,

Please help me in getting the RootPom's usage and what to configure. I 
tried a lot combinations but all failed.

Question and other information is in this link.

http://stackoverflow.com/questions/32637913/mule-maven-jenkins-ci

Regards,
RajuS

-- 
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/27bf8cec-f430-415f-8cf7-a5c570b5695b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: please publish the build pipeline plugin 1.4.8 release notes

[Manuel Jesús Recena Soto]

My mistake. I thought I'd done it.

Regards,

2015-09-17 15:38 GMT+02:00 martinda :
> Please publish the build pipeline plugin 1.4.8 release notes to the wiki.
>
> Thank you.
>
> --
> 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/ab7a7844-68b5-4472-bb6f-f65a52582525%40googlegroups.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-UoeT_Y_v6psjKGA34AA6-u9ZDSSY7HvuU89_uU2Y-azBxw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: Crowd2 1.8 plugin

[marathiboy]

Thanks,

I did see those additional setting and set the time to max, and did see good 
improvement ☺

Thanks for update.

S

From: Arnaud Héritier [via Jenkins CI] 
[mailto:ml-node+s361315n4770875...@n4.nabble.com]
Sent: Thursday, September 17, 2015 2:57 PM
To: LIGADE, SHAILESH
Subject: Re: Crowd2 1.8 plugin

With the patched version you have some additional cache settings. They are 
deactivated by default for backward compatibility.

Like Kanstantsin said a huge work was started to fix SSO issues and the cache 
will have to be backported in its current form or using its native ehcache 
integration if it is possible and allow end users to configure it.

My patched version was developed in few hours when I met the same performance 
issue with 'recent' Jenkins versions which are providing a more dynamic UI but 
which in counter part test the user permissions more often. As far as I 
remember I used the same authorization strategy.

Best regards

Le jeudi 17 septembre 2015, Kanstantsin Shautsou <[hidden 
email]> a écrit :
Crowd2 plugin code is trash, initial author mapped SSO into remember me. I 
fully refactored it to work right and it works fine with username/password. I'm 
waiting @aheritier's help to fix SSO part. His PR with custom caching may be 
redundant because crowd-client provides built-in ehcache and i will prefer 
shift any problem to crowd-client authors.
If you want help, then feel free to help trace SSO auth routines in refactored 
code.

On Thursday, September 17, 2015 at 6:59:24 PM UTC+3, marathiboy wrote:
Thanks BR,

I did install that patch as well as restarted, but didn’t see any noticeable 
performance difference. Without SSO, response is under 2 sec, with SSO, it is 
more like 25 sec ☹

I am using Jenkins 1.594, crowd 2.8, plugin 1.8 + patch

We do use ‘Project-based Matrix Authorization Strategy’ not sure that is 
causing the problem…

Thanks

S


From: Arnaud Héritier [via Jenkins CI] [mailto:[hidden 
email]]
Sent: Wednesday, September 16, 2015 4:54 PM
To: LIGADE, SHAILESH
Subject: Re: Crowd2 1.8 plugin

Hi,

  For https://issues.jenkins-ci.org/browse/JENKINS-16703 there is a pull 
request with a fix implementing a cache mechanism
  We hope to integrate it correctly in the master branch soon
  There is a patch jar attached to the issue that various people are using in 
production.

BR

On Wed, Sep 16, 2015 at 10:02 PM, marathiboy <[hidden 
email]> wrote:
Hello,

I am using crowd2 plugin, the SSO part is working as well, however, the
server is very slow. Each page take about 30 seconds to load. I can see that
Jenkins is making way too many requests to crowd server.

Is there any setting that I am missing?

I also saw similar issue
http://jenkins-ci.361315.n4.nabble.com/JIRA-JENKINS-16703-Too-many-periodic-requests-to-Crowd-server-td4654843.html

and not sure how it was resolved. The ticket states that as of April 15,
there was new update to plugin but plugin page states that the latest plugin
is 1.8 from Aug 2014

Thanks

S



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598.html
Sent from the Jenkins dev mailing list archive at Nabble.com.

--
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 [hidden email].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1442433770093-4770598.post%40n4.nabble.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 [hidden email].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_jDxvkTHXS38dfkd2WJ1svO8JdP9CwdFcCTUJ%2Bt5muQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


If you reply to this email, your message will be added to the discussion below:
http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598p4770617.html
To unsubscribe from Crowd2 1.8 plugin, click here<
NAML




--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598p

Re: Request for new plugin hosting

[Oleg Nenashev]

Let's try "groovy-events-listener-plugin". It's also vague a bit, but 
should work along with the summary description. WDYT?

I see you're a recent committer to the plugin, so perhaps you've got a 
> better idea. How about we put this "integration" in the backlog of work.


Agreed. The plugin may be blacklisted on particular environments like 
CloudBees DEV@Cloud setting up high security requirements, but 
Jenkins.ADMINISTER should be enough to restrict the access for 99% use-case.

воскресенье, 13 сентября 2015 г., 15:22:16 UTC+3 пользователь Nick Grealy 
написал:
>
> Hi,
>
> Could you please setup a place for me to host the following plugin?
>
> *GitHub URL:* https://github.com/nickgrealy/global-events
> *The name the repository should have:* global-events-plugin
> *My **GitHub username:* nickgrealy
> *My **jenkins-ci.org  username:* nickg
>
> *A description of what the plugin does, and what makes it different from 
> other similar plugins:*
>
> The global-events-plugin, is a jenkins plugin, which executes groovy code 
> when an event occurs.
>
> The reason I created the plugin was because I wanted to integrate Jenkins 
> with an external application. Invoking a Jenkins jobs via the REST api was 
> simple, but getting Jenkins to callback the external application wasn't 
> straight forward.
>
> All the plugins I'd seen either had to be individually configured per job 
> (i.e. in a post build step), or their features were limited to making a 
> HTTP GET/POST request (a bit restrictive).
>
> Bascially:
>
>- I wanted to be able to write my own code
>- I didn't want to repeat myself
>
> So I wrote this plugin. Along the way, I realised it could have some other 
> applications too:
>
>- customised logging
>- performance monitoring
>- incident escalation
>- integration with 3rd party applications
>
>
> *Similar Plugins*
>
> These plugins have similar (but different) functionality:
>
>- https://wiki.jenkins-ci.org/display/JENKINS/Notification+Plugin
>- 
>https://wiki.jenkins-ci.org/display/JENKINS/Extreme+Notification+Plugin
>- https://github.com/speedledger/elasticsearch-jenkins
>- https://github.com/jenkinsci/post-completed-build-result-plugin
>
> Kind regards,
>
> Nick Grealy
>

-- 
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/dfc2586f-51cb-43f9-a762-9ce191891259%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Crowd2 1.8 plugin

[Arnaud Héritier]

With the patched version you have some additional cache settings. They are
deactivated by default for backward compatibility.

Like Kanstantsin said a huge work was started to fix SSO issues and the
cache will have to be backported in its current form or using its native
ehcache integration if it is possible and allow end users to configure it.

My patched version was developed in few hours when I met the same
performance issue with 'recent' Jenkins versions which are providing a more
dynamic UI but which in counter part test the user permissions more often.
As far as I remember I used the same authorization strategy.

Best regards

Le jeudi 17 septembre 2015, Kanstantsin Shautsou 
a écrit :

> Crowd2 plugin code is trash, initial author mapped SSO into remember me. I
> fully refactored it to work right and it works fine with username/password.
> I'm waiting @aheritier's help to fix SSO part. His PR with custom caching
> may be redundant because crowd-client provides built-in ehcache and i will
> prefer shift any problem to crowd-client authors.
> If you want help, then feel free to help trace SSO auth routines in
> refactored code.
>
> On Thursday, September 17, 2015 at 6:59:24 PM UTC+3, marathiboy wrote:
>>
>> Thanks BR,
>>
>> I did install that patch as well as restarted, but didn’t see any
>> noticeable performance difference. Without SSO, response is under 2 sec,
>> with SSO, it is more like 25 sec ☹
>>
>> I am using Jenkins 1.594, crowd 2.8, plugin 1.8 + patch
>>
>> We do use ‘Project-based Matrix Authorization Strategy’ not sure that is
>> causing the problem…
>>
>> Thanks
>>
>> S
>>
>>
>> From: Arnaud Héritier [via Jenkins CI] [mailto:
>> ml-node+s361315n4770617...@n4.nabble.com]
>> Sent: Wednesday, September 16, 2015 4:54 PM
>> To: LIGADE, SHAILESH
>> Subject: Re: Crowd2 1.8 plugin
>>
>> Hi,
>>
>>   For https://issues.jenkins-ci.org/browse/JENKINS-16703 there is a pull
>> request with a fix implementing a cache mechanism
>>   We hope to integrate it correctly in the master branch soon
>>   There is a patch jar attached to the issue that various people are
>> using in production.
>>
>> BR
>>
>> On Wed, Sep 16, 2015 at 10:02 PM, marathiboy <[hidden
>> email]> wrote:
>> Hello,
>>
>> I am using crowd2 plugin, the SSO part is working as well, however, the
>> server is very slow. Each page take about 30 seconds to load. I can see
>> that
>> Jenkins is making way too many requests to crowd server.
>>
>> Is there any setting that I am missing?
>>
>> I also saw similar issue
>>
>> http://jenkins-ci.361315.n4.nabble.com/JIRA-JENKINS-16703-Too-many-periodic-requests-to-Crowd-server-td4654843.html
>>
>> and not sure how it was resolved. The ticket states that as of April 15,
>> there was new update to plugin but plugin page states that the latest
>> plugin
>> is 1.8 from Aug 2014
>>
>> Thanks
>>
>> S
>>
>>
>>
>> --
>> View this message in context:
>> http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598.html
>> Sent from the Jenkins dev mailing list archive at Nabble.com.
>>
>> --
>> 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 [hidden email].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/1442433770093-4770598.post%40n4.nabble.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 [hidden email].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_jDxvkTHXS38dfkd2WJ1svO8JdP9CwdFcCTUJ%2Bt5muQQ%40mail.gmail.com
>> <
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_jDxvkTHXS38dfkd2WJ1svO8JdP9CwdFcCTUJ%2Bt5muQQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>> 
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598p4770617.html
>> To unsubscribe from Crowd2 1.8 plugin, click here<
>> http://jenkins-ci.361315.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4770598&code=c2hhaWxlc2gubGlnYWRlQGNicC5kaHMuZ292fDQ3NzA1OTh8LTU4MDAxMjMz>.
>>
>> NAML<
>> http://jenkins-ci.361315.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail

Re: Test case contribution

[Romain SOMMERARD]

Thanks for your feedback.
As you say, I think that we will go on git-plugin.

But I have a question about test contribution:
If we write a test which describe a bug, is it good to make a pull request 
for this test without fix ?
I mean, if pull request is accepted, automatic build will fail, is it good 
way to make that like you say@Mark ? (Maybe the pull request would stay in 
stage while a fix's coming ?)

I precise that we want write test cases and not fix bugs.

-- 
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/67c946b9-3c78-40da-8662-029281fa19e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Crowd2 1.8 plugin

[Kanstantsin Shautsou]

Crowd2 plugin code is trash, initial author mapped SSO into remember me. I 
fully refactored it to work right and it works fine with username/password. 
I'm waiting @aheritier's help to fix SSO part. His PR with custom caching 
may be redundant because crowd-client provides built-in ehcache and i will 
prefer shift any problem to crowd-client authors.
If you want help, then feel free to help trace SSO auth routines in 
refactored code.

On Thursday, September 17, 2015 at 6:59:24 PM UTC+3, marathiboy wrote:
>
> Thanks BR, 
>
> I did install that patch as well as restarted, but didn’t see any 
> noticeable performance difference. Without SSO, response is under 2 sec, 
> with SSO, it is more like 25 sec ☹ 
>
> I am using Jenkins 1.594, crowd 2.8, plugin 1.8 + patch 
>
> We do use ‘Project-based Matrix Authorization Strategy’ not sure that is 
> causing the problem… 
>
> Thanks 
>
> S 
>
>
> From: Arnaud Héritier [via Jenkins CI] [mailto:
> ml-node+s361315n4770617...@n4.nabble.com ] 
> Sent: Wednesday, September 16, 2015 4:54 PM 
> To: LIGADE, SHAILESH 
> Subject: Re: Crowd2 1.8 plugin 
>
> Hi, 
>
>   For https://issues.jenkins-ci.org/browse/JENKINS-16703 there is a pull 
> request with a fix implementing a cache mechanism 
>   We hope to integrate it correctly in the master branch soon 
>   There is a patch jar attached to the issue that various people are using 
> in production. 
>
> BR 
>
> On Wed, Sep 16, 2015 at 10:02 PM, marathiboy <[hidden 
> email]> wrote: 
> Hello, 
>
> I am using crowd2 plugin, the SSO part is working as well, however, the 
> server is very slow. Each page take about 30 seconds to load. I can see 
> that 
> Jenkins is making way too many requests to crowd server. 
>
> Is there any setting that I am missing? 
>
> I also saw similar issue 
>
> http://jenkins-ci.361315.n4.nabble.com/JIRA-JENKINS-16703-Too-many-periodic-requests-to-Crowd-server-td4654843.html
>  
>
> and not sure how it was resolved. The ticket states that as of April 15, 
> there was new update to plugin but plugin page states that the latest 
> plugin 
> is 1.8 from Aug 2014 
>
> Thanks 
>
> S 
>
>
>
> -- 
> View this message in context: 
> http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598.html 
> Sent from the Jenkins dev mailing list archive at Nabble.com. 
>
> -- 
> 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 [hidden email]. 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/1442433770093-4770598.post%40n4.nabble.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 [hidden email]. 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_jDxvkTHXS38dfkd2WJ1svO8JdP9CwdFcCTUJ%2Bt5muQQ%40mail.gmail.com
> <
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_jDxvkTHXS38dfkd2WJ1svO8JdP9CwdFcCTUJ%2Bt5muQQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>  
>
> For more options, visit https://groups.google.com/d/optout. 
>
>  
> If you reply to this email, your message will be added to the discussion 
> below: 
>
> http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598p4770617.html
>  
> To unsubscribe from Crowd2 1.8 plugin, click here<
> http://jenkins-ci.361315.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4770598&code=c2hhaWxlc2gubGlnYWRlQGNicC5kaHMuZ292fDQ3NzA1OTh8LTU4MDAxMjMz>.
>  
>
> NAML<
> http://jenkins-ci.361315.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>  
>
>
>
>
>
> -- 
> View this message in context: 
> http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598p4770827.html
>  
> Sent from the Jenkins dev mailing list archive at Nabble.com. 
>

-- 
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/528d96c7-8519-4b4d-a780-87adb250552e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: please publish the build pipeline plugin 1.4.8 release notes

[Kanstantsin Shautsou]

CC'ed 
On Thursday, September 17, 2015 at 4:38:36 PM UTC+3, martinda wrote:
>
> Please publish the build pipeline plugin 1.4.8 release notes to the wiki.
>
> Thank you.
>

-- 
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/5a7ae46e-2df0-4b49-88de-6e514e29546f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Slide]

I second the idea that core should not depend on a plugin. This seems it
would lead to lots of compatibility issues. Core should be self contained.

On Thu, Sep 17, 2015, 09:53 Tom Fennelly  wrote:

> On Thursday, September 17, 2015 at 5:38:37 PM UTC+1, Jesse Glick wrote:
>
>> On Thu, Sep 17, 2015 at 11:49 AM, Tom Fennelly 
>> wrote:
>> >> Jenkins core cannot depend on a plugin, this makes no sense.
>> >
>> > I still don't get why it's such a no-no.
>>
>> Violates the very notion of what a “plugin” is. By definition, plugins
>> depend on core, and core does not depend on any plugin.
>>
>
> But is it not possible to redefine what it means to be a plugin?
>
> BTW, it is possible for us to do a totally self contained install wizard
> that has everything it needs bundled inside it. I just think it's a waste
> if we are going to be doing other things too in core.
>
> --
> 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/609c84fc-1bf8-4bc1-8d82-5510b76de99e%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/CAPiUgVc8YZX2zT7Akvn26_gsYchUd0vN0RsicX1UbBt09DdU1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

On Thursday, September 17, 2015 at 5:38:37 PM UTC+1, Jesse Glick wrote:
>
> On Thu, Sep 17, 2015 at 11:49 AM, Tom Fennelly  > wrote: 
> >> Jenkins core cannot depend on a plugin, this makes no sense. 
> > 
> > I still don't get why it's such a no-no. 
>
> Violates the very notion of what a “plugin” is. By definition, plugins 
> depend on core, and core does not depend on any plugin. 
>

But is it not possible to redefine what it means to be a plugin?

BTW, it is possible for us to do a totally self contained install wizard 
that has everything it needs bundled inside it. I just think it's a waste 
if we are going to be doing other things too in core.

-- 
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/609c84fc-1bf8-4bc1-8d82-5510b76de99e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Jesse Glick]

On Thu, Sep 17, 2015 at 11:49 AM, Tom Fennelly  wrote:
>> Jenkins core cannot depend on a plugin, this makes no sense.
>
> I still don't get why it's such a no-no.

Violates the very notion of what a “plugin” is. By definition, plugins
depend on core, and core does not depend on any plugin.

> if […] this restriction is imposed then we need
> to rethink how we do the UI stuff in Jenkins core (wizard

The plugin installation wizard is obviously a special case. Either it
is itself a plugin which some bootstrap code installs (my preference),
or it is written so as to avoid using any libraries not already in
core.

> config page changes

Either JENKINS-26464 (my preference), or written so as to use no new
dependencies, or figure out how to make `jenkins-module`s work for
your purposes, or register an extension which swaps out a plain UI.

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

Re: Plugins are hard to find, e.g. conditional-buildstep and Conditional Build Step Plugin

[Baptiste Mathus]

Right! What is your proposal to make them easier to find?

Thanks!
Le 17 sept. 2015 4:17 PM, "martinda"  a écrit :

> It is not easy to find plugins in the update center. For example, some
> plugins refer to it as "Conditional Build Step Plugin", but if you search
> for that in the browser with ctrl-f, you cannot find it. After much looking
> around, I found that it actually shows as "conditional-buildstep".
>
> Martin
>
> --
> 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/6ac25020-6469-47e7-9051-f201bfaa999d%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/CANWgJS5oLgdWurmA3spm9FZ4CiEofYtd6_ts%2B8qWv5mmzcxRuw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: Crowd2 1.8 plugin

[marathiboy]

Thanks BR,

I did install that patch as well as restarted, but didn’t see any noticeable 
performance difference. Without SSO, response is under 2 sec, with SSO, it is 
more like 25 sec ☹

I am using Jenkins 1.594, crowd 2.8, plugin 1.8 + patch

We do use ‘Project-based Matrix Authorization Strategy’ not sure that is 
causing the problem…

Thanks

S


From: Arnaud Héritier [via Jenkins CI] 
[mailto:ml-node+s361315n4770617...@n4.nabble.com]
Sent: Wednesday, September 16, 2015 4:54 PM
To: LIGADE, SHAILESH
Subject: Re: Crowd2 1.8 plugin

Hi,

  For https://issues.jenkins-ci.org/browse/JENKINS-16703 there is a pull 
request with a fix implementing a cache mechanism
  We hope to integrate it correctly in the master branch soon
  There is a patch jar attached to the issue that various people are using in 
production.

BR

On Wed, Sep 16, 2015 at 10:02 PM, marathiboy <[hidden 
email]> wrote:
Hello,

I am using crowd2 plugin, the SSO part is working as well, however, the
server is very slow. Each page take about 30 seconds to load. I can see that
Jenkins is making way too many requests to crowd server.

Is there any setting that I am missing?

I also saw similar issue
http://jenkins-ci.361315.n4.nabble.com/JIRA-JENKINS-16703-Too-many-periodic-requests-to-Crowd-server-td4654843.html

and not sure how it was resolved. The ticket states that as of April 15,
there was new update to plugin but plugin page states that the latest plugin
is 1.8 from Aug 2014

Thanks

S



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598.html
Sent from the Jenkins dev mailing list archive at Nabble.com.

--
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 [hidden email].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1442433770093-4770598.post%40n4.nabble.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 [hidden email].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-_jDxvkTHXS38dfkd2WJ1svO8JdP9CwdFcCTUJ%2Bt5muQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


If you reply to this email, your message will be added to the discussion below:
http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598p4770617.html
To unsubscribe from Crowd2 1.8 plugin, click 
here.
NAML




--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Crowd2-1-8-plugin-tp4770598p4770827.html
Sent from the Jenkins dev mailing list archive at Nabble.com.

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

Re: Revisiting bundled plugins

[Tom Fennelly]

On Thursday, September 17, 2015 at 3:59:46 PM UTC+1, Jesse Glick wrote:
>
> So my running proposal
> · nothing, nada, in `WEB-INF/plugins/` 
>
> > dependencies of "feature" plugins OR Jenkins core itself 
>
> Jenkins core cannot depend on a plugin, this makes no sense. 

(There 
> are `jenkins-module`s shared among core and plugins, but the user has 
> no control over their installation, they are just in `WEB-INF/lib/`.) 
>

I think maybe KK needs to chip in here. I thought I outlined a scenario 
where I thought it does make sense from the pov of how we plan to do some 
UI enhancements going forward (and KK seemed to think so too). I still 
don't get why it's such a no-no. Well, I do get the issues re it being 
possible for someone to disable them, but that to me is a different issue 
and goes back to my point about the lack of distinction between different 
kinds of plugins and what people are allowed to do to them, how the appear 
in the PM etc.

Anyway, if this is the approach and this restriction is imposed then we 
need to rethink how we do the UI stuff in Jenkins core (wizard, config page 
changes etc). That's another discussion I guess, but does seem to indicate 
to me that there's a hole (in this logic, or my understanding :) ) that 
needs filling. jenkins-modules are available but don't seem to meet the 
requirements (easy exposing of web resource without Java hackery) and can't 
be updated (require a new Jenkins).
 

-- 
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/bc405bf1-a1f4-48a3-8ff9-83032232a9c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to host plugin "hierarchy-killer"

[Thorsten Möllers]

Thanks for the feedback. There are lots of relevant things to keep me 
busy for today


- I don't think there's a reason for you to subclass Plugin. It 
doesn't really do anything here. You could move the static stuff into 
the listener directly.

You are probably right. I will look into it.

- You're missing the resource file that contains the plugin 
description for the plugin manager (src/main/resources/index.jelly).

Ok

- Don't reinvent logging levels (especially if they cannot be changed 
once compiled), use java.util.logging consistently.

Ok

- Don't write in the build log of jobs that you're not enabled for. 
That can break things like log parsing etc., as well as look weird. 
AFAIU this is added the moment another (upstream) job is aborted.
I don't. If the variable "HIERARCHY_KILLER_ENABLED" is not defined, it 
will ignore the upstream job.



- Don't prefix instance variables with 'i'.

Ok

- I doubt you really need the RunData, why not query all running jobs 
for what their (upstream) causes are when you get notified about a run 
abort? Not sure what's saved/loaded in the Plugin class, but I expect 
the current design with the static >   HashMap doesn't handle a 
Jenkins restart well (the queue is persisted and restored on restart).


Because it is not only supposed to kill upstream. If I kill the upstream 
build, I want to kill other downstream builds as well. Problem is I 
couldn't find a a way to get a list of all downstream builds for a 
running build.

Therefore I collect this information at runtime.

Jenkins restart: I have to make sure that no persistent data is stored.



- Don't rely on the JENKINS_URL env var to be set.

Ok

- Given how many env vars you check, I think at least 
ENABLE_HIERARCHY_KILLER can be replaced by a job config option (e.g. a 
JobProperty). This would also have the advantage that the plugin would 
have some UI, and could have an inline help text

  explaining how it works.
But it wouldn't automatically be propagated downstream, and if it is, 
the downstream job can not easily overwrite it again.


A non-library plugin without any UI is not a great idea as admins may 
easily forget it exists, and users don't even know it's there.
I agree, you have a point there. Not sure how to align with my previous 
comment though.


- It likely doesn't work with Workflow plugin, whose Runs aren't 
AbstractBuilds. Build Flow plugin probably has the same problem.
These jobs would be ignored by my plugin. (I just updated it to ignore 
the notifications for everything but AbstractBuilds.)


- While I understand that Parameterized Trigger allows having an 
upstream project that still runs, I wonder doubt it's always only one, 
which seems to be the assumption in your code. While that feature may 
not consider quiet periods, the node may be missing, so two 
identically parameterized builds could be collapsed in the queue while 
waiting for the node to free up.
Isn't this something only the Workflow plugin does? I saw it with 
workflow, but never with Parameterized Trigger. If this is really an 
issue for normal builds as well, I will replace iUpstream also with a 
list (vector).


Again, thanks for your feedback. For the naming: "Downstream-killer" is 
incomplete, because to fail early it also needs to be able to kill 
upstream. abort-related-jobs might work. However, I somehow like the 
name; in our company we are often talking about job-hierarchies. Maybe 
some others can chime in and give a comment?


Br,
Thorsten

--
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/55FAD674.5020404%40thorzten.de.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Jesse Glick]

On Thu, Sep 17, 2015 at 6:16 AM, Daniel Beck  wrote:
>> we will upgrade if the plugin does not meet the minimum version requirements 
>> i.e. is less than the bundled version (in /WEB-INF/detached-plugins).
>
> Yep, it looks like that's what Jesse is arguing for.

Yes. So my running proposal (beware that I have not had time to work
through every implication, the onus is on you to test the corner
cases!):

· nothing, nada, in `WEB-INF/plugins/`
· `WEB-INF/detached-plugins/` only for plugins historically split out
of core, and only the 1.0 release created at the time of the split
  · but amended as needed to 1.0.x to pick up important fixes either
for accidental regressions in the original split, or core
incompatibilities introduced subsequently
  · also for the transitive dependencies of split plugins (e.g.,
`script-security`), in the minimal possible versions satisfying stated
dependencies
· `*.jpi.pinned` to be ignored/deleted henceforth
· plugin list in an existing installation left unmodified except
  · split plugins added as needed, according to last-run version
  · in the special case of a *previous* automatic installation of a
1.0 split plugin, if 1.0.x is now in `detached-plugins`, upgrade
  · likewise, if a dependency of a split plugin is newer than the
installed version, upgrade
· delete `PinningIsBlockingBundledPluginMonitor`

> we'd lose Translation Assistance

Just check it by default in the new plugin wizard. I do not see how
this is any different from any other plugin we broadly recommend users
install.

> dependencies of "feature" plugins OR Jenkins core itself

Jenkins core cannot depend on a plugin, this makes no sense. (There
are `jenkins-module`s shared among core and plugins, but the user has
no control over their installation, they are just in `WEB-INF/lib/`.)

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

Re: Revisiting bundled plugins

[Tom Fennelly]

On Thursday, September 17, 2015 at 1:04:15 PM UTC+1, Daniel Beck wrote:
>
>
> On 17.09.2015, at 13:02, Tom Fennelly > 
> wrote: 
>
> > while other plugins are just "dependency" plugins … and are dependencies 
> … Jenkins core itself. 
>
> These do not exist today. 


Sure, I'm just suggesting that there should be some sort of distinction of 
different types of plugins. They all seem to be treated the same atm, which 
seems wrong to me.
 

> If you need them for other changes, this will need to be considered 
> separately. Remember, every plugin, even the bundled ones, can be disabled, 
> which would in this case break Jenkins. Maybe the solution to that issue 
> even blocks finalizing this one?
>

Well I do think these things need to be considered at some stage, but not 
as blockers for this (imo). Jenkins has always been at varying degrees of 
mercy of people disabling plugins at a bad time, right? Sure, this would be 
more unmerciful though :)

-- 
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/9ba3271e-c01f-43b8-9019-54b0b7f4946c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Plugins are hard to find, e.g. conditional-buildstep and Conditional Build Step Plugin

[martinda]

It is not easy to find plugins in the update center. For example, some 
plugins refer to it as "Conditional Build Step Plugin", but if you search 
for that in the browser with ctrl-f, you cannot find it. After much looking 
around, I found that it actually shows as "conditional-buildstep".

Martin

-- 
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/6ac25020-6469-47e7-9051-f201bfaa999d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Sign up for an account

[R. Tyler Croy]

(replies inline)

On Thu, 17 Sep 2015, Stolzenberger, Tobias wrote:

> Hi,
> 
> I would like to sign up for an account to submit a but report. I already 
> registered with user name tobias_stolzenberger here 
> https://jenkins-ci.org/account/signup. Afterwards I got the message: "Due to 
> the spam problem, we need additional verification for your sign-up request. 
> Please contact 
> jenkinsci-dev@googlegroups.com???
> 
> Can you please help me here?


I've gone ahead and completed the creation of your acconut. I saw three or four
creation attempts which I believe may have triggered the spam filter. Sorry for
the inconvenience but you should be all set to go now!


- R. Tyler Croy

--
 Code: 
  Chatter: 

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

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/20150917134056.GI4154%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

please publish the build pipeline plugin 1.4.8 release notes

[martinda]

Please publish the build pipeline plugin 1.4.8 release notes to the wiki.

Thank you.

-- 
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/ab7a7844-68b5-4472-bb6f-f65a52582525%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new plugin hosting

[Nick Grealy]

Hi Oleg,

*Naming*

Regarding the name, I've named it "global-events-plugin", because:

- *global* - because it listens to events right across the Jenkins context
- *events* - because I want to run groovy code in response to events

It's not limited to "RunListener" events, it also contains "Start" and 
"Stop" events for the plugin. I'd eventually like to extend it to 
incorporate even more events (along the lines of the "
extreme-notification-plugin 

"). 
I suppose it makes sense to incorporate *groovy* into the name, as it only 
currently supports running a groovy script. I see *groovy *as a defacto 
standard for Jenkins though... is it worth including in the plugin name?
I'd be happy to substitute *events* for *listener*, if you think it makes 
more sense. 

How about "*global-listener-plugin*" or "*groovy-events-plugin*" or "
*groovy-listener-plugin*"? (I don't really mind).

*Script Security*

Am I aware of the security implications of the plugin? Yes. This plugin can 
only be configured through the "Jenkins > Manage Jenkins > Configure 
System" page, which (as you mentioned) in a production system should only 
be accessible by an Administrator. As an administrator, I would want the 
Groovy script to have full access to the Jenkins architecture - e.g. to 
kick off jobs, to change security settings or run shell commands on the 
server.

Probably it needs to be integrated with 
https://wiki.jenkins-ci.org/display/JENKINS/Script+Security+Plugin  (though 
the configurations are accessible to admins only).
I've had a quick look at the "Script Security Plugin", and it also requires 
an administrator access to the "Jenkins > Manage Jenkins > In-process 
Script Approval" page (similar to above). It looks like this plugin is 
tailored towards Groovy Scripts being configured in the build steps of 
Jenkins jobs by developers/users, so I'm not sure it's necessarily 
applicable to the "global-events-plugin" (there were no screenshots or 
mention of where to configure the plugin).

I see you're a recent committer to the plugin, so perhaps you've got a 
better idea. How about we put this "integration" in the backlog of work.

If you're happy with the name change suggestions (I am), and sidelining the 
"integration with Script-Security-Plugin" work until later (and there 
aren't any more blockers) - can we setup plugin hosting?

Kind regards,

Nick Grealy


On Wednesday, 16 September 2015 19:45:16 UTC+10, Oleg Nenashev wrote:
>
> According to the implementation, it should be renamed to something like 
> "groovy-run-listener" plugin.
>
> Are you aware about Security implications of the plugin? Probably it needs 
> to be integrated with 
> https://wiki.jenkins-ci.org/display/JENKINS/Script+Security+Plugin 
> (though the configurations are accessible to admins only).
>
> воскресенье, 13 сентября 2015 г., 15:22:16 UTC+3 пользователь Nick Grealy 
> написал:
>>
>> Hi,
>>
>> Could you please setup a place for me to host the following plugin?
>>
>> *GitHub URL:* https://github.com/nickgrealy/global-events
>> *The name the repository should have:* global-events-plugin
>> *My **GitHub username:* nickgrealy
>> *My **jenkins-ci.org  username:* nickg
>>
>> *A description of what the plugin does, and what makes it different from 
>> other similar plugins:*
>>
>> The global-events-plugin, is a jenkins plugin, which executes groovy code 
>> when an event occurs.
>>
>> The reason I created the plugin was because I wanted to integrate Jenkins 
>> with an external application. Invoking a Jenkins jobs via the REST api was 
>> simple, but getting Jenkins to callback the external application wasn't 
>> straight forward.
>>
>> All the plugins I'd seen either had to be individually configured per job 
>> (i.e. in a post build step), or their features were limited to making a 
>> HTTP GET/POST request (a bit restrictive).
>>
>> Bascially:
>>
>>- I wanted to be able to write my own code
>>- I didn't want to repeat myself
>>
>> So I wrote this plugin. Along the way, I realised it could have some 
>> other applications too:
>>
>>- customised logging
>>- performance monitoring
>>- incident escalation
>>- integration with 3rd party applications
>>
>>
>> *Similar Plugins*
>>
>> These plugins have similar (but different) functionality:
>>
>>- https://wiki.jenkins-ci.org/display/JENKINS/Notification+Plugin
>>- 
>>https://wiki.jenkins-ci.org/display/JENKINS/Extreme+Notification+Plugin
>>- https://github.com/speedledger/elasticsearch-jenkins
>>- https://github.com/jenkinsci/post-completed-build-result-plugin
>>
>> Kind regards,
>>
>> Nick Grealy
>>
>

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

Re: Revisiting bundled plugins

[Daniel Beck]

On 17.09.2015, at 13:02, Tom Fennelly  wrote:

> while other plugins are just "dependency" plugins … and are dependencies … 
> Jenkins core itself.

These do not exist today. If you need them for other changes, this will need to 
be considered separately. Remember, every plugin, even the bundled ones, can be 
disabled, which would in this case break Jenkins. Maybe the solution to that 
issue even blocks finalizing this one?


-- 
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/56FBEC7B-B040-4AEA-A031-5E9CC61191F7%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Request to host plugin "hierarchy-killer"

[Daniel Beck]

On 17.09.2015, at 13:19, Thorsten Möllers  wrote:

> if anyone would care to review the plugin for obvious flaws, I would be 
> happy. 

Some of the following (especially the one on variable naming) is probably 
subjective...

- I don't think there's a reason for you to subclass Plugin. It doesn't really 
do anything here. You could move the static stuff into the listener directly.
- You're missing the resource file that contains the plugin description for the 
plugin manager (src/main/resources/index.jelly).
- Don't reinvent logging levels (especially if they cannot be changed once 
compiled), use java.util.logging consistently.
- Don't write in the build log of jobs that you're not enabled for. That can 
break things like log parsing etc., as well as look weird. AFAIU this is added 
the moment another (upstream) job is aborted.
- Don't prefix instance variables with 'i'.
- I doubt you really need the RunData, why not query all running jobs for what 
their (upstream) causes are when you get notified about a run abort? Not sure 
what's saved/loaded in the Plugin class, but I expect the current design with 
the static HashMap doesn't handle a Jenkins restart well (the queue is 
persisted and restored on restart).
- Don't rely on the JENKINS_URL env var to be set.
- Given how many env vars you check, I think at least ENABLE_HIERARCHY_KILLER 
can be replaced by a job config option (e.g. a JobProperty). This would also 
have the advantage that the plugin would have some UI, and could have an inline 
help text explaining how it works. A non-library plugin without any UI is not a 
great idea as admins may easily forget it exists, and users don't even know 
it's there.
- It likely doesn't work with Workflow plugin, whose Runs aren't 
AbstractBuilds. Build Flow plugin probably has the same problem.
- While I understand that Parameterized Trigger allows having an upstream 
project that still runs, I wonder doubt it's always only one, which seems to be 
the assumption in your code. While that feature may not consider quiet periods, 
the node may be missing, so two identically parameterized builds could be 
collapsed in the queue while waiting for the node to free up.

Those remarks out of the way:

When I first saw the plugin name, I thought of the process tree killing feature 
of Jenkins (https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller) -- 
as in 'process hierarchy'. Wouldn't something like downstream-killer or 
abort-related-jobs be better?

-- 
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/31EF4B0F-947B-40E8-AD7E-2AD2877B06F9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Put Jenkins on the map

[James Nord]

Sounds like this could be automated.  GitHub already has the location of 
users (if they choose to add it), and it knows a list of comitors and all 
our repositories, and there are sites that will convert generic locations 
to addresses



On Thursday, September 17, 2015 at 12:07:03 PM UTC+1, Jesse Farinacci wrote:
>
> Sorry about the name, I guess I thought more people would be familiar 
> with satellite technology than actually are.. ;-) Now I'm glad I 
> didn't choose first choice of KH-10. 
>
> +1 project rename 
>
> On Thu, Sep 17, 2015 at 6:33 AM, Daniel Beck  > wrote: 
> > 
> > On 17.09.2015, at 11:03, Baptiste Mathus  > wrote: 
> > 
> >> +1 with Oleg, never heard of that repo before. 
> >> 
> > 
> > Unsurprising, given its weird name. Like it doesn't want to be found. 
> Something boring like backend-contributor-map would be more suitable. 
> > 
> > -- 
> > 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/308A75A4-B826-434E-9FBE-A8891819A852%40beckweb.net.
>  
>
> > 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/edab3d61-4b94-41fb-92ed-815de47cd579%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fwd: Request to host plugin "hierarchy-killer"

[Thorsten Möllers]

Hi,

I would like to contribute a new plugin to allow complex trees of CI 
jobs o fail early and/or to be aborted by just aborting the root of the 
tree.


In a complex CI environment, for each commit dozens or even hundreds of 
different builds and tests are triggered to verify the commit. The 
purpose is to give feedback to the developer, if the commit is valid or 
not. There are two opposing views on what the developer expects:


Either the developer wants as *much* feedback as possible for each 
commit, or he wants feedback as *fast* as possible.


If the target is to provide feedback as *fast* as possible, all testing 
can be stopped on the first failed build/test job. This is where this 
plugin comes into play: If configured accordingly, the plugin will kill 
all upstream- and downstream jobs of a failing job.




The plugin is hosted on https://github.com/thors/hierarchy-killer-plugin
My github username is "thors"
My jenkins-ci username is also "thors"

A more detailed description of what the plugin does is available on 
https://github.com/thors/hierarchy-killer-plugin/wiki


BTW: I'm not yet very experienced in Java programming, so if anyone 
would care to review the plugin for obvious flaws, I would be happy.


Best regards,
Thorsten


Best regards,
Thorsten



--
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/55FAA1C3.8070900%40thorzten.de.
For more options, visit https://groups.google.com/d/optout.

Re: Put Jenkins on the map

[jieryn]

Sorry about the name, I guess I thought more people would be familiar
with satellite technology than actually are.. ;-) Now I'm glad I
didn't choose first choice of KH-10.

+1 project rename

On Thu, Sep 17, 2015 at 6:33 AM, Daniel Beck  wrote:
>
> On 17.09.2015, at 11:03, Baptiste Mathus  wrote:
>
>> +1 with Oleg, never heard of that repo before.
>>
>
> Unsurprising, given its weird name. Like it doesn't want to be found. 
> Something boring like backend-contributor-map would be more suitable.
>
> --
> 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/308A75A4-B826-434E-9FBE-A8891819A852%40beckweb.net.
> 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/CAArU9iawXkRq-%2BaCNuobK0S53jue5UDSutv5JzD3b%3DdwHQGxPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

On Thursday, September 17, 2015 at 11:16:41 AM UTC+1, Daniel Beck wrote:
>
>
> On 17.09.2015, at 11:26, Tom Fennelly > 
> wrote: 
>
> > Sorry ... typo in #2 on the last email. I should have said "This only 
> seems relevant to me if the answer to #1 is no" i.e. we will upgrade if the 
> plugin does not meet the minimum version requirements i.e. is less than the 
> bundled version (in /WEB-INF/detached-plugins). 
>
> Yep, it looks like that's what Jesse is arguing for. I'd have kept pinning 
> around for now, but it looks _really_ unpopular. It's basically what we 
> discussed a few days back, without the pinning. 
>

So this is what's in the PR then, minus the pinning. I'm fine with removing 
pinning, but would be interested to know why it's so unpopular? There seems 
to be a strong logic to it's existence and not liking doesn't seem like a 
good reason to ditch it.
 

>
> Regarding your proposal, note that there are detached plugins that have 
> since picked up dependencies. Those dependencies would also be in 
> detached-plugins/ right? 
>

Right, I outlined that in the post I made here yesterday ... detached 
plugin dependencies (and dependencies of dependencies etc) are deployed if 
that detached plugin is deployed (it gets that info from the manifest). 
Dependencies must also be in the /WEB-INF/detached-plugin folder in the war.
 

> Not sure we should keep plugins/ -- probably. Ideally official Jenkins 
> would come without any. (Which means we'd lose Translation Assistance... 
> not sure what a good solution is here...) 
>

I think this should stay for now at least (and so does KK).

For one thing, the new approach to JavaScript modularization (which these 
changes are using - and will be used in other ui enhancements) uses plugins 
to bundle JavaScript "bundles" (see here 
). Yes, jenkins modules 
etc etc, but they do not allow easy upgrade and require what I consider to 
be ugly hacks in order to make the web resources available 
(UnprotectedRootActions 
etc sorry ... yeuck).

It seems to me like there's a problem here in that all plugins are treated 
equally when they really are not all equal. Some plugins provide actual 
"features", while other plugins are just "dependency" plugins (call them 
what you like) and are dependencies of "feature" plugins OR Jenkins core 
itself. I'd think it makes sense to allow these "dependency" type plugins 
to be bundled in Jenkins core, but not the "feature" plugins. Jenkins 
modules could work instead of some of these "dependency" plugins, but not 
them all because of the updating issue with modules (you need a new 
Jenkins).

-- 
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/4c16b781-477c-46d5-849f-5123ac8d4b69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Put Jenkins on the map

['Bruno P. Kinoshita' via Jenkins Developers]

I think it could be useful to have multiple layers on the map, with all enabled 
by default, but with an option to display only core committers, plug-in 
developers, CIA ambassadors, and so it goes.
 
  From: Baptiste Mathus 
 To: jenkinsci-dev@googlegroups.com 
 Sent: Thursday, 17 September 2015 8:49 PM
 Subject: Re: Put Jenkins on the map
   
Wondering, is this the jenkins developers at large that would appear on this 
map or only jenkins "core"? I.e. plugin developers too or not?
2015-09-17 10:46 GMT+02:00 Robert Sandell :



I made a quick fix to the map page, it's not beautiful, but now it should at 
least work again :)

http://jenkinsci.github.io/keyhole/


On Wed, Sep 16, 2015 at 7:38 PM, Alyssa Tong  wrote:

Hi Oleg,
it would be awesome to have both. This would be a good indicator of the growth 
of Jenkins. Since i'm not at all a developer, could someone help me to develop 
this map(s)?
thnxalyssa
On Sat, Sep 12, 2015 at 12:48 AM, Oleg Nenashev  wrote:

Hi Alyssa,

Are you looking for the "Jenkins events" map or for the "Jenkins contributors" 
map (probably both)? 
BTW here is the actual map setup guide: 
https://developers.google.com/maps/tutorials/kml/

Best regards,
Oleg

пятница, 11 сентября 2015 г., 11:29:55 UTC+3 пользователь Robert Sandell 
написал:
Well Google Maps no longer supports embedded KML without some changes

https://support.google.com/maps/answer/41136?p=kml&hl=en&rd=1

On Thu, Sep 10, 2015 at 8:08 PM, jieryn  wrote:

Sigh. You must be, you must be the change you want to see in the world. :-)

On Thu, Sep 10, 2015 at 2:07 PM, jieryn  wrote:
> You must the the change you want to see in the world. :-)
>
> On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
>  wrote:
>> 2015-09-10 19:27 GMT+02:00 jieryn :
>>> https://github.com/jenkinsci/keyhole
>>
>> Not working due to https://developers.google.com/maps/support/kmlmaps
>>
>> --
>> * Antonio Muñiz
>> * amunizmartin.com
>> * amuniz...@gmail.com
>>
>> --
>> 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/CACpar97Dpcq8vTcVnkJ_j1wc%3DOzXuvyrmK6-Ua9Y1o%3DjLucycQ%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-de...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAArU9iYZjcp1N2Nd3ewS5NorzJ%2BGQn8vEaX02ERYBtBCqVgCFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.




-- 
Robert SandellSoftware EngineerCloudBees 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/2da6e9f5-a152-40b7-880f-6977d7d3212c%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/CAC9wNawXkcZ5A5XwtX%3DOJOBhF3cXyzYyWEsh%3DKk80_QEoh%2BkVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.




-- 
Robert SandellSoftware EngineerCloudBees 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/CALzHZS0tdtXEG%3DALSY%2B-XGa0AQYpNjz3asxGVDW0MsycXrJSiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.




-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !-- 
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/CANWgJS7cG3dNQHV5%3D9gWCLHcqqNk1dVVjwrw%2B%3De5kzNCcUgxRA%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 Develop

Re: Put Jenkins on the map

[Daniel Beck]

On 17.09.2015, at 11:03, Baptiste Mathus  wrote:

> +1 with Oleg, never heard of that repo before.
> 

Unsurprising, given its weird name. Like it doesn't want to be found. Something 
boring like backend-contributor-map would be more suitable.

-- 
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/308A75A4-B826-434E-9FBE-A8891819A852%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Daniel Beck]

On 17.09.2015, at 11:26, Tom Fennelly  wrote:

> Sorry ... typo in #2 on the last email. I should have said "This only seems 
> relevant to me if the answer to #1 is no" i.e. we will upgrade if the plugin 
> does not meet the minimum version requirements i.e. is less than the bundled 
> version (in /WEB-INF/detached-plugins).

Yep, it looks like that's what Jesse is arguing for. I'd have kept pinning 
around for now, but it looks _really_ unpopular. It's basically what we 
discussed a few days back, without the pinning.

Regarding your proposal, note that there are detached plugins that have since 
picked up dependencies. Those dependencies would also be in detached-plugins/ 
right?

Not sure we should keep plugins/ -- probably. Ideally official Jenkins would 
come without any. (Which means we'd lose Translation Assistance... not sure 
what a good solution is here...)

-- 
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/6B9AF998-56AE-4598-BE53-74256A9B8906%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

Maybe we should clarify what it means for a plugin to be bundled in 
"/WEB-INF/plugins" Vs "/WEB-INF/detached-plugins".

My understanding/interpretation is:

   - */WEB-INF/plugins*: These are plugins that must always be 
   installed/updated. Same as before. The versions are kept as up-to-date as 
   possible (I think, right?).
   - */WEB-INF/detached-plugins*: Selectively installed based on the 
   criteria I outlined above/yesterday (Sept 16). The versions are *set to 
   the minimum* required for Jenkins to work without throwing a wobbler of 
   errors i.e. not kept up-to-date with latest version of that plugin.
   
So as I see it, upgrades from /WEB-INF/detached-plugins only happen if the 
installed version is below the minimum version required for the new Jenkins 
to work. We don't just upgrade "for fun".

-- 
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/0cea22d7-3bf9-4abf-8f00-497a2d38de88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

Sorry ... typo in #2 on the last email. I should have said "This only seems
relevant to me if the answer to #1 is no" i.e. we will upgrade if the
plugin does not meet the minimum version requirements i.e. is less than the
bundled version (in /WEB-INF/detached-plugins).

On 17 September 2015 at 10:23, Tom Fennelly  wrote:

> So where are we now guys?
>
>1. Are we still saying we are not going to update existing plugins on
>an upgrade? Jesse seemed definitive on this one but I still don't know the
>reasoning.
>2. Are we still saying pinned files should be ignored ala what Jesse
>said earlier? Again, I still haven't heard the reasons why they should be
>ignored. This only seems relevant to me if the answer to #1 is yes (we are
>updating existing plugins on an upgrade).
>
> Basically, I want to agreement on what changes are needed on the PR.
>
> --
> 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/kRobm-cxFw8/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/d7209aea-08d3-46ec-92f4-ff5070cc1410%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%2BbPao%2By5NjKG8zovQLjKJ2mWXzhuEavWhRQ29SbH1NmhSZgMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

So where are we now guys?

   1. Are we still saying we are not going to update existing plugins on an 
   upgrade? Jesse seemed definitive on this one but I still don't know the 
   reasoning.
   2. Are we still saying pinned files should be ignored ala what Jesse 
   said earlier? Again, I still haven't heard the reasons why they should be 
   ignored. This only seems relevant to me if the answer to #1 is yes (we are 
   updating existing plugins on an upgrade).

Basically, I want to agreement on what changes are needed on the PR.

-- 
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/d7209aea-08d3-46ec-92f4-ff5070cc1410%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Put Jenkins on the map

[Robert Sandell]

Well, I'm not sure the kml file is actually needed, someone with a bit more
free time could probably walk through the public members list of the
Jenkinsci org via the GitHub API and use the user's location info to build
a more complete map. :)

/B

On Thu, Sep 17, 2015 at 11:03 AM, Baptiste Mathus 
wrote:

> OK, done then :-) https://github.com/jenkinsci/keyhole/pull/1 (I tried
> committing directly, but seems I'm not authorized, not a bad thing that not
> everyone can directly commit maybe).
>
> +1 with Oleg, never heard of that repo before.
>
> And btw, the coordinates are weirdly reversed IIUC. Copy-pasting google
> maps coordinates will display you on the wrong place. Thanks to Oleg's
> mistake (;-)) I think I committed the right thing but I would absolutely
> certainly have done the same ;-)
>
>
> 2015-09-17 10:56 GMT+02:00 Oleg Nenashev :
>
>> On the other hand, I have not ever heard about this repo before this
>> thread :)
>> If we want to publish a relevant information, makes sense to advertise it
>> a bit.
>>
>> On 17 Sep 2015, at 11:54, Robert Sandell  wrote:
>>
>> It is who ever that has pushed their coordinates to
>> https://github.com/jenkinsci/keyhole
>>
>> So imho it is those that consider themselves "Jenkins Developers" I added
>> my coords there before my first official core commit and I considered
>> myself as much of a Jenkins Developer then as I do now ;)
>>
>> /B
>>
>> On Thu, Sep 17, 2015 at 10:49 AM, Baptiste Mathus 
>> wrote:
>>
>>> Wondering, is this the jenkins developers at large that would appear on
>>> this map or only jenkins "core"?
>>> I.e. plugin developers too or not?
>>>
>>> 2015-09-17 10:46 GMT+02:00 Robert Sandell :
>>>
 I made a quick fix to the map page, it's not beautiful, but now it
 should at least work again :)

 http://jenkinsci.github.io/keyhole/


 On Wed, Sep 16, 2015 at 7:38 PM, Alyssa Tong 
 wrote:

> Hi Oleg,
>
> it would be awesome to have both. This would be a good indicator of
> the growth of Jenkins. Since i'm not at all a developer, could someone 
> help
> me to develop this map(s)?
>
> thnx
> alyssa
>
> On Sat, Sep 12, 2015 at 12:48 AM, Oleg Nenashev <
> o.v.nenas...@gmail.com> wrote:
>
>> Hi Alyssa,
>>
>> Are you looking for the "Jenkins events" map or for the "Jenkins
>> contributors" map (probably both)?
>> BTW here is the actual map setup guide:
>> https://developers.google.com/maps/tutorials/kml/
>>
>> Best regards,
>> Oleg
>>
>> пятница, 11 сентября 2015 г., 11:29:55 UTC+3 пользователь Robert
>> Sandell написал:
>>>
>>> Well Google Maps no longer supports embedded KML without some changes
>>>
>>> https://support.google.com/maps/answer/41136?p=kml&hl=en&rd=1
>>>
>>> On Thu, Sep 10, 2015 at 8:08 PM, jieryn  wrote:
>>>
 Sigh. You must be, you must be the change you want to see in the
 world. :-)

 On Thu, Sep 10, 2015 at 2:07 PM, jieryn  wrote:
 > You must the the change you want to see in the world. :-)
 >
 > On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
 >  wrote:
 >> 2015-09-10 19:27 GMT+02:00 jieryn :
 >>> https://github.com/jenkinsci/keyhole
 >>
 >> Not working due to
 https://developers.google.com/maps/support/kmlmaps
 >>
 >> --
 >> * Antonio Muñiz
 >> * amunizmartin.com
 >> * amuniz...@gmail.com
 >>
 >> --
 >> 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/CACpar97Dpcq8vTcVnkJ_j1wc%3DOzXuvyrmK6-Ua9Y1o%3DjLucycQ%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-de...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CAArU9iYZjcp1N2Nd3ewS5NorzJ%2BGQn8vEaX02ERYBtBCqVgCFA%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-d

Re: Put Jenkins on the map

[Baptiste Mathus]

OK, done then :-) https://github.com/jenkinsci/keyhole/pull/1 (I tried
committing directly, but seems I'm not authorized, not a bad thing that not
everyone can directly commit maybe).

+1 with Oleg, never heard of that repo before.

And btw, the coordinates are weirdly reversed IIUC. Copy-pasting google
maps coordinates will display you on the wrong place. Thanks to Oleg's
mistake (;-)) I think I committed the right thing but I would absolutely
certainly have done the same ;-)


2015-09-17 10:56 GMT+02:00 Oleg Nenashev :

> On the other hand, I have not ever heard about this repo before this
> thread :)
> If we want to publish a relevant information, makes sense to advertise it
> a bit.
>
> On 17 Sep 2015, at 11:54, Robert Sandell  wrote:
>
> It is who ever that has pushed their coordinates to
> https://github.com/jenkinsci/keyhole
>
> So imho it is those that consider themselves "Jenkins Developers" I added
> my coords there before my first official core commit and I considered
> myself as much of a Jenkins Developer then as I do now ;)
>
> /B
>
> On Thu, Sep 17, 2015 at 10:49 AM, Baptiste Mathus 
> wrote:
>
>> Wondering, is this the jenkins developers at large that would appear on
>> this map or only jenkins "core"?
>> I.e. plugin developers too or not?
>>
>> 2015-09-17 10:46 GMT+02:00 Robert Sandell :
>>
>>> I made a quick fix to the map page, it's not beautiful, but now it
>>> should at least work again :)
>>>
>>> http://jenkinsci.github.io/keyhole/
>>>
>>>
>>> On Wed, Sep 16, 2015 at 7:38 PM, Alyssa Tong 
>>> wrote:
>>>
 Hi Oleg,

 it would be awesome to have both. This would be a good indicator of the
 growth of Jenkins. Since i'm not at all a developer, could someone help me
 to develop this map(s)?

 thnx
 alyssa

 On Sat, Sep 12, 2015 at 12:48 AM, Oleg Nenashev >>> > wrote:

> Hi Alyssa,
>
> Are you looking for the "Jenkins events" map or for the "Jenkins
> contributors" map (probably both)?
> BTW here is the actual map setup guide:
> https://developers.google.com/maps/tutorials/kml/
>
> Best regards,
> Oleg
>
> пятница, 11 сентября 2015 г., 11:29:55 UTC+3 пользователь Robert
> Sandell написал:
>>
>> Well Google Maps no longer supports embedded KML without some changes
>>
>> https://support.google.com/maps/answer/41136?p=kml&hl=en&rd=1
>>
>> On Thu, Sep 10, 2015 at 8:08 PM, jieryn  wrote:
>>
>>> Sigh. You must be, you must be the change you want to see in the
>>> world. :-)
>>>
>>> On Thu, Sep 10, 2015 at 2:07 PM, jieryn  wrote:
>>> > You must the the change you want to see in the world. :-)
>>> >
>>> > On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
>>> >  wrote:
>>> >> 2015-09-10 19:27 GMT+02:00 jieryn :
>>> >>> https://github.com/jenkinsci/keyhole
>>> >>
>>> >> Not working due to
>>> https://developers.google.com/maps/support/kmlmaps
>>> >>
>>> >> --
>>> >> * Antonio Muñiz
>>> >> * amunizmartin.com
>>> >> * amuniz...@gmail.com
>>> >>
>>> >> --
>>> >> 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/CACpar97Dpcq8vTcVnkJ_j1wc%3DOzXuvyrmK6-Ua9Y1o%3DjLucycQ%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-de...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAArU9iYZjcp1N2Nd3ewS5NorzJ%2BGQn8vEaX02ERYBtBCqVgCFA%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/2da6e9f5-a152-40b7-880f-6977d7d3212c%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>


 --
 You received this message because y

Re: Put Jenkins on the map

[Arnaud Héritier]

Myself I was surprised to find me on the map. I forgot that I added my
coordinates 4 years ago ...

On Thu, Sep 17, 2015 at 10:56 AM, Oleg Nenashev 
wrote:

> On the other hand, I have not ever heard about this repo before this
> thread :)
> If we want to publish a relevant information, makes sense to advertise it
> a bit.
>
> On 17 Sep 2015, at 11:54, Robert Sandell  wrote:
>
> It is who ever that has pushed their coordinates to
> https://github.com/jenkinsci/keyhole
>
> So imho it is those that consider themselves "Jenkins Developers" I added
> my coords there before my first official core commit and I considered
> myself as much of a Jenkins Developer then as I do now ;)
>
> /B
>
> On Thu, Sep 17, 2015 at 10:49 AM, Baptiste Mathus 
> wrote:
>
>> Wondering, is this the jenkins developers at large that would appear on
>> this map or only jenkins "core"?
>> I.e. plugin developers too or not?
>>
>> 2015-09-17 10:46 GMT+02:00 Robert Sandell :
>>
>>> I made a quick fix to the map page, it's not beautiful, but now it
>>> should at least work again :)
>>>
>>> http://jenkinsci.github.io/keyhole/
>>>
>>>
>>> On Wed, Sep 16, 2015 at 7:38 PM, Alyssa Tong 
>>> wrote:
>>>
 Hi Oleg,

 it would be awesome to have both. This would be a good indicator of the
 growth of Jenkins. Since i'm not at all a developer, could someone help me
 to develop this map(s)?

 thnx
 alyssa

 On Sat, Sep 12, 2015 at 12:48 AM, Oleg Nenashev >>> > wrote:

> Hi Alyssa,
>
> Are you looking for the "Jenkins events" map or for the "Jenkins
> contributors" map (probably both)?
> BTW here is the actual map setup guide:
> https://developers.google.com/maps/tutorials/kml/
>
> Best regards,
> Oleg
>
> пятница, 11 сентября 2015 г., 11:29:55 UTC+3 пользователь Robert
> Sandell написал:
>>
>> Well Google Maps no longer supports embedded KML without some changes
>>
>> https://support.google.com/maps/answer/41136?p=kml&hl=en&rd=1
>>
>> On Thu, Sep 10, 2015 at 8:08 PM, jieryn  wrote:
>>
>>> Sigh. You must be, you must be the change you want to see in the
>>> world. :-)
>>>
>>> On Thu, Sep 10, 2015 at 2:07 PM, jieryn  wrote:
>>> > You must the the change you want to see in the world. :-)
>>> >
>>> > On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
>>> >  wrote:
>>> >> 2015-09-10 19:27 GMT+02:00 jieryn :
>>> >>> https://github.com/jenkinsci/keyhole
>>> >>
>>> >> Not working due to
>>> https://developers.google.com/maps/support/kmlmaps
>>> >>
>>> >> --
>>> >> * Antonio Muñiz
>>> >> * amunizmartin.com
>>> >> * amuniz...@gmail.com
>>> >>
>>> >> --
>>> >> 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/CACpar97Dpcq8vTcVnkJ_j1wc%3DOzXuvyrmK6-Ua9Y1o%3DjLucycQ%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-de...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAArU9iYZjcp1N2Nd3ewS5NorzJ%2BGQn8vEaX02ERYBtBCqVgCFA%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/2da6e9f5-a152-40b7-880f-6977d7d3212c%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/CAC9wNawXkcZ5A5XwtX%3DOJOBhF3cXyzYyWEsh%3DKk80_QEoh%2BkVQ%40mai

Re: Put Jenkins on the map

[Oleg Nenashev]

On the other hand, I have not ever heard about this repo before this thread :)
If we want to publish a relevant information, makes sense to advertise it a bit.

> On 17 Sep 2015, at 11:54, Robert Sandell  wrote:
> 
> It is who ever that has pushed their coordinates to 
> https://github.com/jenkinsci/keyhole 
> 
> So imho it is those that consider themselves "Jenkins Developers" I added my 
> coords there before my first official core commit and I considered myself as 
> much of a Jenkins Developer then as I do now ;)
> 
> /B
> 
> On Thu, Sep 17, 2015 at 10:49 AM, Baptiste Mathus  > wrote:
> Wondering, is this the jenkins developers at large that would appear on this 
> map or only jenkins "core"? 
> I.e. plugin developers too or not?
> 
> 2015-09-17 10:46 GMT+02:00 Robert Sandell  >:
> I made a quick fix to the map page, it's not beautiful, but now it should at 
> least work again :)
> 
> http://jenkinsci.github.io/keyhole/ 
> 
> 
> On Wed, Sep 16, 2015 at 7:38 PM, Alyssa Tong  > wrote:
> Hi Oleg,
> 
> it would be awesome to have both. This would be a good indicator of the 
> growth of Jenkins. Since i'm not at all a developer, could someone help me to 
> develop this map(s)?
> 
> thnx
> alyssa
> 
> On Sat, Sep 12, 2015 at 12:48 AM, Oleg Nenashev  > wrote:
> Hi Alyssa,
> 
> Are you looking for the "Jenkins events" map or for the "Jenkins 
> contributors" map (probably both)? 
> BTW here is the actual map setup guide: 
> https://developers.google.com/maps/tutorials/kml/ 
> 
> 
> Best regards,
> Oleg
> 
> пятница, 11 сентября 2015 г., 11:29:55 UTC+3 пользователь Robert Sandell 
> написал:
> Well Google Maps no longer supports embedded KML without some changes
> 
> https://support.google.com/maps/answer/41136?p=kml&hl=en&rd=1 
> 
> 
> On Thu, Sep 10, 2015 at 8:08 PM, jieryn > wrote:
> Sigh. You must be, you must be the change you want to see in the world. :-)
> 
> On Thu, Sep 10, 2015 at 2:07 PM, jieryn > wrote:
> > You must the the change you want to see in the world. :-)
> >
> > On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
> > > wrote:
> >> 2015-09-10 19:27 GMT+02:00 jieryn >:
> >>> https://github.com/jenkinsci/keyhole 
> >>> 
> >>
> >> Not working due to https://developers.google.com/maps/support/kmlmaps 
> >> 
> >>
> >> --
> >> * Antonio Muñiz
> >> * amunizmartin.com 
> >> * amuniz...@gmail.com <>
> >>
> >> --
> >> 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/CACpar97Dpcq8vTcVnkJ_j1wc%3DOzXuvyrmK6-Ua9Y1o%3DjLucycQ%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-de...@googlegroups.com <>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAArU9iYZjcp1N2Nd3ewS5NorzJ%2BGQn8vEaX02ERYBtBCqVgCFA%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/2da6e9f5-a152-40b7-880f-6977d7d3212c%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 f

Re: Put Jenkins on the map

[Robert Sandell]

It is who ever that has pushed their coordinates to
https://github.com/jenkinsci/keyhole

So imho it is those that consider themselves "Jenkins Developers" I added
my coords there before my first official core commit and I considered
myself as much of a Jenkins Developer then as I do now ;)

/B

On Thu, Sep 17, 2015 at 10:49 AM, Baptiste Mathus 
wrote:

> Wondering, is this the jenkins developers at large that would appear on
> this map or only jenkins "core"?
> I.e. plugin developers too or not?
>
> 2015-09-17 10:46 GMT+02:00 Robert Sandell :
>
>> I made a quick fix to the map page, it's not beautiful, but now it should
>> at least work again :)
>>
>> http://jenkinsci.github.io/keyhole/
>>
>>
>> On Wed, Sep 16, 2015 at 7:38 PM, Alyssa Tong  wrote:
>>
>>> Hi Oleg,
>>>
>>> it would be awesome to have both. This would be a good indicator of the
>>> growth of Jenkins. Since i'm not at all a developer, could someone help me
>>> to develop this map(s)?
>>>
>>> thnx
>>> alyssa
>>>
>>> On Sat, Sep 12, 2015 at 12:48 AM, Oleg Nenashev 
>>> wrote:
>>>
 Hi Alyssa,

 Are you looking for the "Jenkins events" map or for the "Jenkins
 contributors" map (probably both)?
 BTW here is the actual map setup guide:
 https://developers.google.com/maps/tutorials/kml/

 Best regards,
 Oleg

 пятница, 11 сентября 2015 г., 11:29:55 UTC+3 пользователь Robert
 Sandell написал:
>
> Well Google Maps no longer supports embedded KML without some changes
>
> https://support.google.com/maps/answer/41136?p=kml&hl=en&rd=1
>
> On Thu, Sep 10, 2015 at 8:08 PM, jieryn  wrote:
>
>> Sigh. You must be, you must be the change you want to see in the
>> world. :-)
>>
>> On Thu, Sep 10, 2015 at 2:07 PM, jieryn  wrote:
>> > You must the the change you want to see in the world. :-)
>> >
>> > On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
>> >  wrote:
>> >> 2015-09-10 19:27 GMT+02:00 jieryn :
>> >>> https://github.com/jenkinsci/keyhole
>> >>
>> >> Not working due to
>> https://developers.google.com/maps/support/kmlmaps
>> >>
>> >> --
>> >> * Antonio Muñiz
>> >> * amunizmartin.com
>> >> * amuniz...@gmail.com
>> >>
>> >> --
>> >> 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/CACpar97Dpcq8vTcVnkJ_j1wc%3DOzXuvyrmK6-Ua9Y1o%3DjLucycQ%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-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAArU9iYZjcp1N2Nd3ewS5NorzJ%2BGQn8vEaX02ERYBtBCqVgCFA%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/2da6e9f5-a152-40b7-880f-6977d7d3212c%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/CAC9wNawXkcZ5A5XwtX%3DOJOBhF3cXyzYyWEsh%3DKk80_QEoh%2BkVQ%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
>> 

Re: Git Client Plugin: Advice on expanding MergeCommand

[thi]

Hey Mark,

I added two tests to a branch on my fork 
, which 
also contains my changes for adding --no-comit.
One fails for the JGit implementation, while the other fails for the CLI 
implementaion.
Yesterday's post was way too big, by the way, the whole thing just boils 
down to:
The current JGit implementation always overrides repository defaults, even 
when options weren't explicitly set.
The current CLI implementation sometimes doesn't override repository 
defaults, even when options were explicitly set.

So everything works fine, but things get a bit confusing once you start 
changing the repo defaults.
We'd have to keep track of which options the user actually set in the 
command builder and *only* add those.

To imagine this all started with "Should I call this method setCommit or 
setNoCommit?".. :)

Kind regards,
Thierry

-- 
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/d44b4c98-443a-4fde-ad48-acaae2fa721e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Put Jenkins on the map

[Baptiste Mathus]

Wondering, is this the jenkins developers at large that would appear on
this map or only jenkins "core"?
I.e. plugin developers too or not?

2015-09-17 10:46 GMT+02:00 Robert Sandell :

> I made a quick fix to the map page, it's not beautiful, but now it should
> at least work again :)
>
> http://jenkinsci.github.io/keyhole/
>
>
> On Wed, Sep 16, 2015 at 7:38 PM, Alyssa Tong  wrote:
>
>> Hi Oleg,
>>
>> it would be awesome to have both. This would be a good indicator of the
>> growth of Jenkins. Since i'm not at all a developer, could someone help me
>> to develop this map(s)?
>>
>> thnx
>> alyssa
>>
>> On Sat, Sep 12, 2015 at 12:48 AM, Oleg Nenashev 
>> wrote:
>>
>>> Hi Alyssa,
>>>
>>> Are you looking for the "Jenkins events" map or for the "Jenkins
>>> contributors" map (probably both)?
>>> BTW here is the actual map setup guide:
>>> https://developers.google.com/maps/tutorials/kml/
>>>
>>> Best regards,
>>> Oleg
>>>
>>> пятница, 11 сентября 2015 г., 11:29:55 UTC+3 пользователь Robert Sandell
>>> написал:

 Well Google Maps no longer supports embedded KML without some changes

 https://support.google.com/maps/answer/41136?p=kml&hl=en&rd=1

 On Thu, Sep 10, 2015 at 8:08 PM, jieryn  wrote:

> Sigh. You must be, you must be the change you want to see in the
> world. :-)
>
> On Thu, Sep 10, 2015 at 2:07 PM, jieryn  wrote:
> > You must the the change you want to see in the world. :-)
> >
> > On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
> >  wrote:
> >> 2015-09-10 19:27 GMT+02:00 jieryn :
> >>> https://github.com/jenkinsci/keyhole
> >>
> >> Not working due to
> https://developers.google.com/maps/support/kmlmaps
> >>
> >> --
> >> * Antonio Muñiz
> >> * amunizmartin.com
> >> * amuniz...@gmail.com
> >>
> >> --
> >> 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/CACpar97Dpcq8vTcVnkJ_j1wc%3DOzXuvyrmK6-Ua9Y1o%3DjLucycQ%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-de...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAArU9iYZjcp1N2Nd3ewS5NorzJ%2BGQn8vEaX02ERYBtBCqVgCFA%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/2da6e9f5-a152-40b7-880f-6977d7d3212c%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/CAC9wNawXkcZ5A5XwtX%3DOJOBhF3cXyzYyWEsh%3DKk80_QEoh%2BkVQ%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/CALzHZS0tdtXEG%3DALSY%2B-XGa0AQYpNjz3asxGVDW0MsycXrJSiw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Baptiste  MATHUS - http://batmat.n

Re: Put Jenkins on the map

[Robert Sandell]

I made a quick fix to the map page, it's not beautiful, but now it should
at least work again :)

http://jenkinsci.github.io/keyhole/


On Wed, Sep 16, 2015 at 7:38 PM, Alyssa Tong  wrote:

> Hi Oleg,
>
> it would be awesome to have both. This would be a good indicator of the
> growth of Jenkins. Since i'm not at all a developer, could someone help me
> to develop this map(s)?
>
> thnx
> alyssa
>
> On Sat, Sep 12, 2015 at 12:48 AM, Oleg Nenashev 
> wrote:
>
>> Hi Alyssa,
>>
>> Are you looking for the "Jenkins events" map or for the "Jenkins
>> contributors" map (probably both)?
>> BTW here is the actual map setup guide:
>> https://developers.google.com/maps/tutorials/kml/
>>
>> Best regards,
>> Oleg
>>
>> пятница, 11 сентября 2015 г., 11:29:55 UTC+3 пользователь Robert Sandell
>> написал:
>>>
>>> Well Google Maps no longer supports embedded KML without some changes
>>>
>>> https://support.google.com/maps/answer/41136?p=kml&hl=en&rd=1
>>>
>>> On Thu, Sep 10, 2015 at 8:08 PM, jieryn  wrote:
>>>
 Sigh. You must be, you must be the change you want to see in the world.
 :-)

 On Thu, Sep 10, 2015 at 2:07 PM, jieryn  wrote:
 > You must the the change you want to see in the world. :-)
 >
 > On Thu, Sep 10, 2015 at 2:06 PM, Antonio Manuel Muñiz Martín
 >  wrote:
 >> 2015-09-10 19:27 GMT+02:00 jieryn :
 >>> https://github.com/jenkinsci/keyhole
 >>
 >> Not working due to
 https://developers.google.com/maps/support/kmlmaps
 >>
 >> --
 >> * Antonio Muñiz
 >> * amunizmartin.com
 >> * amuniz...@gmail.com
 >>
 >> --
 >> 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/CACpar97Dpcq8vTcVnkJ_j1wc%3DOzXuvyrmK6-Ua9Y1o%3DjLucycQ%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-de...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CAArU9iYZjcp1N2Nd3ewS5NorzJ%2BGQn8vEaX02ERYBtBCqVgCFA%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/2da6e9f5-a152-40b7-880f-6977d7d3212c%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/CAC9wNawXkcZ5A5XwtX%3DOJOBhF3cXyzYyWEsh%3DKk80_QEoh%2BkVQ%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/CALzHZS0tdtXEG%3DALSY%2B-XGa0AQYpNjz3asxGVDW0MsycXrJSiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need inputs on a new plugin idea - Code Trigger Plugin

[Onl61]

Well, CodeTrigger is a Plugin used for software development. It provides an 
automation/command line interface so it can be called by CI environments 
for automated build, so it can be called by a Jenkins CI build. I don't 
know how many Jenkins users are using CodeTrigger (since it specializes in 
c#) but it doesn't sound like a good idea to have 2 continuous 
integration/software development automation plug-ins with the *same* *name* 
even if they do different things..

On Wednesday, September 16, 2015 at 4:24:08 PM UTC+1, A9S6 wrote:
>
> Yes, thanks... But what is does is completely different.
>
 

> On Sep 16, 2015 7:48 PM, "Onl61" 
>
>> There is already something called a CodeTrigger plugin. see 
>> www.codetrigger.com 
>>
>>


-- 
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/52733748-00f1-43a3-8d0e-3ce70f853c23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need inputs on a new plugin idea - Code Trigger Plugin

[Onl61]

Well, CodeTrigger is a Plugin used for software development. It provides an 
automation/command line interface so it can be called by CI environments 
for automated build, so it can be called by a Jenkins CI build. I don't 
know how many Jenkins users are using CodeTrigger (since it specializes in 
c#) but it doesn't sound like a good idea to have 2 continuous 
integration/software development automation plug-ins with the *same* *name* 
even if they do different things..


On Wednesday, September 16, 2015 at 4:24:08 PM UTC+1, A9S6 wrote:
>
> Yes, thanks... But what is does is completely different.
> On Sep 16, 2015 7:48 PM, "Onl61" > 
> wrote:
>
>> There is already something called a CodeTrigger plugin. see 
>> www.codetrigger.com 
>>
>> On Thursday, July 30, 2015 at 5:22:27 AM UTC+1, A9S6 wrote:
>>>
>>> Hi All,
>>>
>>> I am a bit confused as to whether the proposed *Code Trigger Plugin* 
>>> should be a part of the *Static Code Analysis Plugins* or not. *Task 
>>> Scanner* finds certain tags and displays different reports whereas the 
>>> Code Trigger Plugin would:
>>> >> Work on a formatted trigger tag
>>> >> Only display the Triggers which are due and need attention via a 
>>> single report page
>>> >> Send email for due triggers
>>> >> Have custom configuration options for emails, report format, 
>>> customising trigger format etc
>>>
>>> The new plugin will certainly be inspired by Task Scanner plugin because 
>>> of similarity in certain features such as workspace file scanning. 
>>>
>>> Please advice on whether to extend Task Scanner or write a new plugin. I 
>>> want to avoid the situation where after developing a new plugin it is not 
>>> accepted by Jenkins team on the ground that a similar plugin already exists.
>>>
>>> Thanks
>>> Abhi
>>>
>>>
>>> On Wednesday, July 15, 2015 at 5:44:23 PM UTC+5:30, A9S6 wrote:

 Hi All,

 I have a Jenkins plugin idea in mind that I want to share before 
 starting. I plan to call it *Code Trigger Plugin*. The main idea is to 
 read special tags inside the source code and trigger an action (mainly 
 send 
 out emails) based on the tags. The idea here is to remind developers that 
 a 
 particular piece of code needs attention every N months/years. For e.g. I 
 have a about box that displays a http link and the link changes every few 
 months and needs to be updated. Using Code Triggers, one can specify 
 something like the following above the line that sets the url in code:

 //TRIGGER: 07-15-2015,30,The link needs to be updated

 Which means that a trigger was created on 15July2015 and will send 
 notification every 30 days from creation date with the specified message.

 I got this idea while fixing an issue in a legacy application. One of 
 the functions in the application was converting an Oracle data type to a 
 custom type and I think the time it was written Oracle did not have the 
 NCHAR,NVARCHAR types and these were missed out. We can use the code 
 triggers for such situations too, to inform developers that a particular 
 method might require changes in future. I believe this will be helpful in 
 avoiding unwanted bugs.

 The plugin can be extended to support additional tags in future.

 I am looking for some inputs on whether a similar plugin already 
 exists? whether this can be done by extending an existing plugin or needs 
 a 
 new plugin?

 Thanks
 Abhi



-- 
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/bbb1e668-7bb2-4b63-89cd-b8ea306ed095%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Sign up for an account

[Stolzenberger, Tobias]

Hi,

I would like to sign up for an account to submit a but report. I already 
registered with user name tobias_stolzenberger here 
https://jenkins-ci.org/account/signup. Afterwards I got the message: "Due to 
the spam problem, we need additional verification for your sign-up request. 
Please contact 
jenkinsci-dev@googlegroups.com”

Can you please help me here?

Regards,
Tobias Stolzenberger

-- 
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/D2203E8D.B0CD%25tobias.stolzenberger%40sap.com.
For more options, visit https://groups.google.com/d/optout.