github-api and jackson2-api shared libraries hell

[Kanstantsin Shautsou]

https://github.com/jenkinsci/jackson2-api-plugin/blob/master/pom.xml#L45-L51
Additional maintainers 
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-github-api.yml#L7-L14
 

github-api 1.93 has this 
fix 
https://github.com/kohsuke/github-api/commit/d50ae63a5a10f08e046ea66491b53a057789cc4a

Since github-api 1.90 jackson 2.9.3 is 
required 
https://github.com/Rechi/github-api/commit/6415785220b2cfab393a12a68efcc4c274d208a2
 
but it work fine with 2.8 
until https://github.com/kohsuke/github-api/pull/422/files 
https://github.com/FasterXML/jackson-databind/commit/3711a1c585fe63d5bbd5da7f860dd81b233a6b84
My blind surprised attempt to bump 
dep 
https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgithub-api-plugin/detail/master/13/pipeline

https://issues.jenkins-ci.org/browse/JENKINS-51322 recommends to shade 
dependencies.

I think everybody understand what it mean for jenkins:
- release 2.9 and broke some number of plugins (or not?). Oleg & Stephen 
are maintainers
- shade plugin deps and stop shade-plugin hell
- revert enum, make new release in github-api (usually requires weeks or 
months to get Kohsuke attention on repository)
- stop using github-api in github plugins
- first/last classloader, classloader hacks, etc
- else?

-- 
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/0f4a8f8b-613f-4466-93fc-bd0d67d4296e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Removing the Everyone team in the jenkinsci GitHub org

[Kanstantsin Shautsou]

Last time Kohsuke blocked this question with his veto because jenkinsci 
should be a bazaar model (and everybody should be able to work on any 
plugin). 
What happened since last time when i (and some other persons) tried to 
implement this and remove RW from everyone? 
*Kohsuke, do you publicly approve that jenkins is not the bazaar anymore? *
PS Or JEP now removes King of project position?

Thanks.
On Tuesday, November 28, 2017 at 6:58:53 AM UTC+3, Kohsuke Kawaguchi wrote:
>
> Thanks for driving this. 
>
> If this change inadvertently remove somebody's commit access, presumably 
> we expect people to follow this 
> 
>  and 
> mail this list?
>
> On Mon, Nov 27, 2017 at 4:25 PM Daniel Beck  > wrote:
>
>> Hi everyone,
>>
>> For a long time, we didn't really manage GitHub permissions for plugins: 
>> We just added new repos and contributors to the 'Everyone' team, giving 
>> everyone access to everything, and that was it. Contrary to its name, it 
>> doesn't actually include _everyone_, at least not anymore: We've moved away 
>> from adding people to the Everyone team over a year ago. But it still has 
>> hundreds of members, and provides write access to more than 1200 
>> repositories.
>>
>> While contributors are mostly well-behaved, we've occasionally seen PRs 
>> merged by people who weren't regular contributors to those plugins, 
>> resulting in conflict with actual maintainers. Since these users cannot 
>> release the plugins anyway, the benefit of being able to do this is 
>> questionable at best. Not to mention the problem of malicious or accidental 
>> data loss through people force-pushing into Git (this, accidentally, has 
>> happened with dozens -- hundreds? -- of repositories back in 2015, and 
>> caused a considerable mess).
>>
>> I know that quite a few plugin maintainers have long removed the Everyone 
>> team from their plugin repositories to prevent such problems, but the 
>> default is still to add the team to a new plugin repo.
>>
>> Given the size of the Jenkins project, this is untenable. I plan to 
>> remove the Everyone team from all repositories, instead granting direct 
>> access to contributors who previously got their write access from the 
>> Everyone team. This way, we should be able to retain access for those who 
>> legitimately have it, while removing those who have no relationship to any 
>> particular plugin.
>>
>> Right now, I plan to grant direct write access to a plugin to users who:
>>
>> 1. Have write access to a repository through the Everyone team only
>> 2. Are considered 'contributors' by GitHub (meaning they have commits 
>> associated with them in the repo)
>> 3. Have at least 5 'contributions' (~commits in the contributors graph)
>>
>> The first two should be obvious (with the caveat that badly set up GH 
>> accounts -- their commits not associated with the account -- will lose 
>> access). The third is where it gets tricky: Not everyone who contributed to 
>> a repository, and currently has write access to it via 'Everyone' team, 
>> should legitimately have write access to it in the future. Unfortunately, 
>> GitHub makes it impossible to efficiently determine who has performed 
>> various maintainer-specific actions, such as created a release tag, or 
>> merged a pull request -- and these might still miss legitimate 
>> co-maintainers who just don't have direct access.
>>
>> So I will instead use a minimum number (currently 5) of contributions 
>> required for someone to retain access. Once we've drastically limited who 
>> has access to any given repo, we can always fine-tune this later. There 
>> will also be a log of what changed so this can be referenced later in case 
>> of questions related to lost permissions.
>>
>> While this may be a painful change if the above rules get the needed 
>> permissions wrong, it's an important one, and I'm trying to make it as 
>> smooth as possible. Please bring up your concerns and questions in this 
>> thread and I'll do my best to address them.
>>
>> I don't think this is JEPable, as this doesn't actually create a 
>> longer-running process, it's just a one-time legacy permission migration.
>>
>> 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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/ABF8E55F-0896-4DD0-AB07-6778F39F5A10%40beckweb.net
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Kohsuke Kawaguchi
>

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

Re: freestyle-multibranch, multibranch, scm-api questions

[Kanstantsin Shautsou]

So how to do the very easy feature: trigger PR/builds only when they match 
to some criteria unrelated to hash i.e. trigger branch only when commit 
message matches to XXX, PRs to some trigger message?
And the second case: trigger build only when PR is closed, branch deleted. 

How bypass dumb SCMHeadObserverImpl ? Make revision nondetermenistic and 
guess they way in if cases to offload trigger decision logic to flexible 
implementation?

Just curious, have you ever looked at ghprb and github-integration-plugins 
long existing features when designed scm-api?

-- 
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/3a3e7243-63a6-4e76-a9a5-8e2cafff9b94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: freestyle-multibranch, multibranch, scm-api questions

[Kanstantsin Shautsou]

On Friday, October 20, 2017 at 2:16:41 PM UTC+3, Stephen Connolly wrote:
>
>
>
> On 20 October 2017 at 04:02, Kanstantsin Shautsou <kanstan...@gmail.com 
> > wrote:
>
>>
>>
>> 2017-10-20 11:50 GMT+03:00 Stephen Connolly <stephen.al...@gmail.com 
>> >:
>>
>>> On 19 October 2017 at 17:42, Kanstantsin Shautsou <kanstan...@gmail.com 
>>> > wrote:
>>>
>>>> Trying to make multibranch support with not messed buildhistory by 
>>>> reusing my flexible github triggering code and experience. 
>>>>
>>>
>>> Unclear what you mean by "not messed build history"... with multibranch, 
>>> each branch gets its own clean history... the only issue that I know about 
>>> build history is that when a new branch is discovered, its first build will 
>>> have an empty history (we'd like to have it link to the other branch that 
>>> this new branch was forked from... though that may not always be possible)
>>>
>>> Or are you referring to the crazy of having git build many branches of 
>>> in a single job that drove me to develop multibranch in the first place.
>>>
>> Yes, i mean that it good to have separated history. 
>>
>>>  
>>>
>>>> Have some questions after first scm/branch/freestyle API reading 
>>>> impression:
>>>> - Why uncategorized view is primary 
>>>> jenkins.branch.MultiBranchProjectViewHolder#getViews and how to set own 
>>>> primary view?
>>>>
>>>
>>> Because the "standard" SCMHeads should not have a category.
>>>
>> Why?
>>
>
> because categories are a mix-in. Some SCMs will not have different types 
> of "branch like" things that can be discovered.
>
>  
>>
>>>  
>>>
>>>> - Why uncategorized DEFAULT view (category) is named "Branch" by 
>>>> default?
>>>>
>>>
>>> That is a decision for the SCMSource. If Accurev gets around to 
>>> implementing SCM API then that would probably have its uncategorised 
>>> category called `Stream`
>>>
>>> If you then have a multibranch project with two sources, one github and 
>>> the other accurev then you would have:
>>>
>>> - `Branches / Streams` as the default view
>>> - `Snapshots / Tags` if somebody has enabled tag discovery on both 
>>> SCMSources 
>>> - `Pull Requests` if you enable pull request discovery for GitHub but 
>>> there is no equivalent category for accurev... if accurev had an equivalent 
>>> functionality and it was enabled at the same time then you'd have this tab 
>>> called `Change Requests / Pull Requests` (in the event that Accurev uses 
>>> the term `Change Requests`... if they use the term `Pull Requests` then 
>>> this would be just `Pull Requests` as both sources would be agreeing on the 
>>> terminology. 
>>>
>> AFAIR they will be in one view only when they will have one category that 
>> sounds weird to mix different sources in one view. 
>>
>
> So the expected case is that you only ever have one SCMSource... but 
> consider the case where you are migrating from one SCM to another for your 
> "project"
>
> In that case you might have both Accurev and GitHub with the maintenance 
> branches on one and the new development on another.
>
> Now when I need to go look at the status of a "branch" (and as a developer 
> I don't give a f*ck whether the SCM called that a "Stream" or a "Branch") I 
> want to go to one tab and see all of them together... same goes for 
> tag/snapshot and pull request/change request.
>
> So we group the same categories together... categories are a way of 
> grouping outside of the class hierarchy
>  
>
>>  
>>>
>>>> - Freestyle-multibranch uses 
>>>> observer jenkins.branch.MultiBranchProject.SCMHeadObserverImpl#observe  is 
>>>> it possible to replace it with custom logic?
>>>>
>>>
>>> Why should it do custom logic? It's job is just to create the project 
>>> and trigger a build if and only if:
>>>
>>> 1. The SCMRevision is different from the previous
>>>
>> That wrong assumption locked all APIs to only this one possible thing in 
>> triggering branch/pr builds.
>> Though i can try to hack it and control build triggering via it in 
>> deterministics and equals. 
>>
>> 2. The BranchBuildStrategy gives the OK to build (or if there are no

Re: freestyle-multibranch, multibranch, scm-api questions

[Kanstantsin Shautsou]

2017-10-20 11:50 GMT+03:00 Stephen Connolly <stephen.alan.conno...@gmail.com
>:

> On 19 October 2017 at 17:42, Kanstantsin Shautsou <
> kanstantsin@gmail.com> wrote:
>
>> Trying to make multibranch support with not messed buildhistory by
>> reusing my flexible github triggering code and experience.
>>
>
> Unclear what you mean by "not messed build history"... with multibranch,
> each branch gets its own clean history... the only issue that I know about
> build history is that when a new branch is discovered, its first build will
> have an empty history (we'd like to have it link to the other branch that
> this new branch was forked from... though that may not always be possible)
>
> Or are you referring to the crazy of having git build many branches of in
> a single job that drove me to develop multibranch in the first place.
>
Yes, i mean that it good to have separated history.

>
>
>> Have some questions after first scm/branch/freestyle API reading
>> impression:
>> - Why uncategorized view is primary 
>> jenkins.branch.MultiBranchProjectViewHolder#getViews
>> and how to set own primary view?
>>
>
> Because the "standard" SCMHeads should not have a category.
>
Why?

>
>
>> - Why uncategorized DEFAULT view (category) is named "Branch" by default?
>>
>
> That is a decision for the SCMSource. If Accurev gets around to
> implementing SCM API then that would probably have its uncategorised
> category called `Stream`
>
> If you then have a multibranch project with two sources, one github and
> the other accurev then you would have:
>
> - `Branches / Streams` as the default view
> - `Snapshots / Tags` if somebody has enabled tag discovery on both
> SCMSources
> - `Pull Requests` if you enable pull request discovery for GitHub but
> there is no equivalent category for accurev... if accurev had an equivalent
> functionality and it was enabled at the same time then you'd have this tab
> called `Change Requests / Pull Requests` (in the event that Accurev uses
> the term `Change Requests`... if they use the term `Pull Requests` then
> this would be just `Pull Requests` as both sources would be agreeing on the
> terminology.
>
AFAIR they will be in one view only when they will have one category that
sounds weird to mix different sources in one view.

>
>
>> - Freestyle-multibranch uses observer jenkins.branch.MultiB
>> ranchProject.SCMHeadObserverImpl#observe  is it possible to replace it
>> with custom logic?
>>
>
> Why should it do custom logic? It's job is just to create the project and
> trigger a build if and only if:
>
> 1. The SCMRevision is different from the previous
>
That wrong assumption locked all APIs to only this one possible thing in
triggering branch/pr builds.
Though i can try to hack it and control build triggering via it in
deterministics and equals.

2. The BranchBuildStrategy gives the OK to build (or if there are no branch
> build strategies then auto-build everything except tags)
>
>
>> This observer is not flexible and not extendable, it can do only simple
>> case comparison this vs that by revision. How to run the same build if it
>> was already built? Revision+Head are not enough information.
>>
>
> BranchBuildStrategy is the place for more complex decisions, multibranch
> is opinionated and aims to remove the effect of 100 jobs trying to poll for
> changes and replace that with (worst case) one multibranch polling for
> changes or (best case) one multibranch being pushed events
>
Where did you saw 100 jobs targeted to one repository for 100 branches?
Before people used one trigger that produced messed build history with
different branches/prs in one job, but trigger was one, now the same.

>
>
>> (Probably this is an answer why there is still no smart messages for
>> rebuilds.
>>   if (rebuild) {
>>
>> listener.getLogger().format(
>>
>> "%s reopened: %s (%s)%n",)   < why API expects defined
>> behavior? Again, what if i want rebuild by comment, date, other ifluence?
>>
>
> Freestyle-multibranch was an early experiment, probably needs some
> updating to the latest code.
>
This code is from fresh branch api observer.

>
>
>> One more place of decision making is SCMSourceCriteria... Oh, and
>> Trait(?)... And BranchPropertyStrategy... How much places are designed for
>> decision making and influence on final result?
>>
>
> The SCMSourceCriteria is to decide *is this a branch/tag/pr that should
> have a project created*
>
> The BranchPropertyStrategy is to decorate each child job
>
> The BranchBuildStrategy is to deci

freestyle-multibranch, multibranch, scm-api questions

[Kanstantsin Shautsou]

Trying to make multibranch support with not messed buildhistory by reusing 
my flexible github triggering code and experience. Have some questions 
after first scm/branch/freestyle API reading impression:
- Why uncategorized view is primary 
jenkins.branch.MultiBranchProjectViewHolder#getViews and how to set own 
primary view?
- Why uncategorized DEFAULT view (category) is named "Branch" by default?
- Freestyle-multibranch uses 
observer jenkins.branch.MultiBranchProject.SCMHeadObserverImpl#observe  is 
it possible to replace it with custom logic?
This observer is not flexible and not extendable, it can do only simple 
case comparison this vs that by revision. How to run the same build if it 
was already built? Revision+Head are not enough information.
(Probably this is an answer why there is still no smart messages for 
rebuilds. 
  if (rebuild) {

listener.getLogger().format(

"%s reopened: %s (%s)%n",)   < why API expects defined 
behavior? Again, what if i want rebuild by comment, date, other ifluence? 
One more place of decision making is SCMSourceCriteria... Oh, and 
Trait(?)... And BranchPropertyStrategy... How much places are designed for 
decision making and influence on final result? 
Can i  decide in one (my) place and just return to multibranch my decision: 
"this head, branch, etc should be built, please create views by 
corresponding SCMHeadCategory, etc" Or just not call observe and bypass it?
- Is State.class expected to be used as persistent storage of data for 
plugins? If yes, then how to control exceptions during xmlread to exclude 
data clearing?

-- 
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/5e646943-4151-4084-9f92-89788467a5ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean for developers

[Kanstantsin Shautsou]

Waiting for 1 year for any information about non better (non jelly) UIs in 
jenkins for non workflow job types and other plugins. My impression is that 
jenkins is totally locked with hard deps to workflow job type today. Huge 
blueocean repo with model duplicates outside of plugin code is not 
something that we expect for development/usage.

On Friday, October 13, 2017 at 8:49:02 PM UTC+3, Kohsuke Kawaguchi wrote:
>
> This is one of the topics I'm really keen on. Needless to say, it's 
> incredibly important for plugins to be able to extend Blue Ocean just like 
> they can Jenkins.
>
> I've seen some of the stuff Keith has been working on, and I'm really 
> looking forward to those.
>
> On Fri, Oct 13, 2017 at 9:40 AM Keith Zantow  > wrote:
>
>> Hi Ullrich,
>>
>> I hope not to overstep my bounds, but I would like to say a few things:
>>
>> 1) Blue Ocean is currently extensible, there is an extensibility 
>> mechanism described in the README
>> 2) there is some ongoing work to provide a simpler and more type safe 
>> method of extending Blue Ocean, which will likely land before 2018
>>
>> I'm not sure of your needs, but holding off for just a bit might be wise.
>>
>> Thanks,
>> -Keith
>>
>> On Fri, Oct 13, 2017 at 10:55 AM, Ullrich Hafner > > wrote:
>>
>>> Is blue ocean ready for plug-in authors? Or is the API still in flow?
>>> I found two empty pages in the wiki:
>>>
>>> https://wiki.jenkins.io/display/JENKINS/Making+your+plugin+work+with+blue+ocean
>>> https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+development
>>> So I’m wondering if it makes sense to start to look at the current state 
>>> from a developers perspective?
>>> Or should I wait for more things (and documentation) to come? Is there a 
>>> good starting point for developers available?
>>> Or should I fork https://github.com/jenkinsci/blueocean-plugin and 
>>> start to look at the code and documentation there?
>>>
>>> Sorry for so many questions but I’m just not sure if I already should 
>>> spend time in that quite interesting new part of 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-de...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.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/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Kohsuke Kawaguchi
>

-- 
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/c1da530f-5a1e-47db-8fd2-72b9b94a1164%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean for developers

[Kanstantsin Shautsou]

s/non//

On Saturday, October 14, 2017 at 9:04:31 PM UTC+3, Kanstantsin Shautsou 
wrote:
>
> Waiting for 1 year for any information about non better (non jelly) UIs in 
> jenkins for non workflow job types and other plugins. My impression is that 
> jenkins is totally locked with hard deps to workflow job type today. Huge 
> blueocean repo with model duplicates outside of plugin code is not 
> something that we expect for development/usage.
>
> On Friday, October 13, 2017 at 8:49:02 PM UTC+3, Kohsuke Kawaguchi wrote:
>>
>> This is one of the topics I'm really keen on. Needless to say, it's 
>> incredibly important for plugins to be able to extend Blue Ocean just like 
>> they can Jenkins.
>>
>> I've seen some of the stuff Keith has been working on, and I'm really 
>> looking forward to those.
>>
>> On Fri, Oct 13, 2017 at 9:40 AM Keith Zantow <kza...@cloudbees.com> 
>> wrote:
>>
>>> Hi Ullrich,
>>>
>>> I hope not to overstep my bounds, but I would like to say a few things:
>>>
>>> 1) Blue Ocean is currently extensible, there is an extensibility 
>>> mechanism described in the README
>>> 2) there is some ongoing work to provide a simpler and more type safe 
>>> method of extending Blue Ocean, which will likely land before 2018
>>>
>>> I'm not sure of your needs, but holding off for just a bit might be wise.
>>>
>>> Thanks,
>>> -Keith
>>>
>>> On Fri, Oct 13, 2017 at 10:55 AM, Ullrich Hafner <ullrich...@gmail.com> 
>>> wrote:
>>>
>>>> Is blue ocean ready for plug-in authors? Or is the API still in flow?
>>>> I found two empty pages in the wiki:
>>>>
>>>> https://wiki.jenkins.io/display/JENKINS/Making+your+plugin+work+with+blue+ocean
>>>> https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+development
>>>> So I’m wondering if it makes sense to start to look at the current 
>>>> state from a developers perspective?
>>>> Or should I wait for more things (and documentation) to come? Is there 
>>>> a good starting point for developers available?
>>>> Or should I fork https://github.com/jenkinsci/blueocean-plugin and 
>>>> start to look at the code and documentation there?
>>>>
>>>> Sorry for so many questions but I’m just not sure if I already should 
>>>> spend time in that quite interesting new part of 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-de...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.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/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> -- 
>> Kohsuke Kawaguchi
>>
>

-- 
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/61dae4d9-8c63-4827-9cb8-d2834d21ec80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Proposal] Making all things Stapler more declarative

[Kanstantsin Shautsou]

Not really, but imho almost all plugins had/has security issues with
unclear stapler endpoints and simple annotations for stapler method may be
better for automated security checks. I think it related for
stapler/binding understanding also.

2017-07-06 2:20 GMT+03:00 Jesse Glick <jgl...@cloudbees.com>:

> On Wed, Jul 5, 2017 at 6:50 PM, Kanstantsin Shautsou
> <kanstantsin@gmail.com> wrote:
> > https://github.com/jenkinsci/github-plugin/blob/
> 93d40692ff3866705175624e93ec584d4ac88132/src/main/java/org/
> jenkinsci/plugins/github/admin/GitHubHookRegisterProblemMonit
> or.java#L182-L186
>
> These are not really related; they are just other interceptor
> annotations. (Which I do not really advocate, either—you should not
> use annotations where plain old method calls are just as readable, and
> far more flexible and debuggable.)
>
> --
> 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/UrVVT8wbHIE/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/CANfRfr2ShkBiyLgxO18eK%2BKtecKMR5tKWbNfYHiOcc-
> HqgEG4g%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: RateLimitHandler error

[Kanstantsin Shautsou]

>
>
> A few things here:
> * perhaps we need to shade in the Github library into each plugin that 
> requires it. Avoid version hell altogether
> * start versioning the Github library so it's clear when there are major 
> breaking changes between versions. Stephen C does an excellent job at this 
> for all the branch and scm API changes.
>
> This library is claimed as backward compatible by KK (okhttp isn't updated 
and User/Org difference isn't implement also because of this) , that's why 
it wrapped into jenkins plugin and used by all other plugins.  While i were 
maintaining gh-api-plugin and gh-plugin i were checking them before 
releases (until few devs started doing changes without approval violating 
project rules, but it other story) and found broken binary compatibility 
few times. It was caused by Kohsuke's "maintaining style", or simply saying 
merge everything, make changes in one evening and release few minutes 
later. So some projects using direct library dep may hit incompatibilities 
between available gh-api-plugin versions. 
In theory breakage shouldn't happen, but if somebody depend directly on 
library, then it should shade it or play by jenkins classloaders rules and 
use plugin wrapper. Even today there are issues with this library, so 
probably it even makes sense to starting thinking on using some other 
library or fork it.

For those who requested support and eclude abstract discussions, please 
provide 
 
https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription
 

-- 
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/4c784a1b-6bf2-4057-bd04-7ac9c10c37d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Proposal] Making all things Stapler more declarative

[Kanstantsin Shautsou]

On Tuesday, July 4, 2017 at 8:25:06 PM UTC+3, Stephen Connolly wrote:
>
> Actually I nearly forgot Oleg you were driving the Google summer of code 
> last year, what do you think?
>
>>
>>> And as usual seems you forgot github-plugin and Kirill that was GSOC 
mentor for some UI changes and already covered with annotations some pieces 
https://github.com/jenkinsci/github-plugin/blob/93d40692ff3866705175624e93ec584d4ac88132/src/main/java/org/jenkinsci/plugins/github/admin/GitHubHookRegisterProblemMonitor.java#L182-L186
 
 

-- 
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/de7cee3b-6cf9-4c5e-8263-ee5395294657%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Add icons 'disable project' & 'configure' to be on tap at dashboard

[Kanstantsin Shautsou]

As we are talking in maillist for developers could you provide Pull Request 
with your changes, then we will be able to discuss it?

> On Apr 28, 2017, at 15:15, Manuel Mariscal <mariscal.ma...@gmail.com> wrote:
> 
> Better for both (jenkins & blue ocean) and please, could be a button to 
> disable all jobs of the jenkins? It's really interesting to disconnect these 
> jobs once clicked, thank you very much.
> Regards
> 
> El vie., 28 de abril de 2017 14:10, Manuel Mariscal <mariscal.ma...@gmail.com 
> <mailto:mariscal.ma...@gmail.com>> escribió:
> Normal jenkins (Jenkins 2.57 nowadays)
> 
> Thank you
> 
> Regards
> 
> 
> El vie., 28 de abril de 2017 0:52, Kanstantsin Shautsou 
> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>> escribió:
> Workflow that still doesn't have disable button? ;)
> 
> 
> On Friday, April 28, 2017 at 1:46:30 AM UTC+3, Oleg Nenashev wrote:
> Could you please clarify what you mean?
> BlueOcean UI or what?
> 
> четверг, 27 апреля 2017 г., 11:15:33 UTC+2 пользователь Manuel Mariscal 
> написал:
> Hi everyone!
> 
> First of all, thank you very much for your job, it's really interesting and 
> useful.
> 
> I'd like to ask for if it's possible to change the state of jobs at the 
> right, and at the left set the most important icons (CONFIGURE, BUILD NOW, 
> DISABLE) in addition to the drop-down list (on Dashboard). Thank you very much
> 
> Kind regards
> 
> -- 
> 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/TCwsGotrvYc/unsubscribe 
> <https://groups.google.com/d/topic/jenkinsci-dev/TCwsGotrvYc/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/f46f5014-c9a5-4d04-a13f-3f3f6aaf9870%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/f46f5014-c9a5-4d04-a13f-3f3f6aaf9870%40googlegroups.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/TCwsGotrvYc/unsubscribe 
> <https://groups.google.com/d/topic/jenkinsci-dev/TCwsGotrvYc/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFEXo0qFfJ_ZA97rVr9SPy7ZR23XHXgdqD8iWPQH8eC8a%3Dexig%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFEXo0qFfJ_ZA97rVr9SPy7ZR23XHXgdqD8iWPQH8eC8a%3Dexig%40mail.gmail.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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/A413AEAF-A2EE-4D2F-9D91-F3725F99BECA%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Add icons 'disable project' & 'configure' to be on tap at dashboard

[Kanstantsin Shautsou]

Workflow that still doesn't have disable button? ;)

On Friday, April 28, 2017 at 1:46:30 AM UTC+3, Oleg Nenashev wrote:
>
> Could you please clarify what you mean?
> BlueOcean UI or what?
>
> четверг, 27 апреля 2017 г., 11:15:33 UTC+2 пользователь Manuel Mariscal 
> написал:
>>
>> Hi everyone!
>>
>> First of all, thank you very much for your job, it's really interesting 
>> and useful.
>>
>> I'd like to ask for if it's possible to change the state of jobs at the 
>> right, and at the left set the most important icons (CONFIGURE, BUILD NOW, 
>> DISABLE) in addition to the drop-down list (on Dashboard). Thank you very 
>> much
>>
>> Kind regards
>>
>

-- 
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/f46f5014-c9a5-4d04-a13f-3f3f6aaf9870%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer for docker-plugin

[Kanstantsin Shautsou]

According to magnayan's words - he is maintaining it. I don't work on it
anymore - it full of bugs. YAD also has bugs, but less ;)

2017-04-28 1:48 GMT+03:00 Oleg Nenashev :

> CCed Kanstantin Shatsou, who used to be a maintainer. I have no magnayan's
> contacts.
> Though I expect another discussion about Docker Plugin vs. Yet Another
> Docker Plugin, I expect it to be useful here
>
> среда, 26 апреля 2017 г., 21:49:11 UTC+2 пользователь Chris Albrecht
> написал:
>>
>> Hi,
>>
>> I see there are a number of open pull requests for the Docker Plugin (
>> https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin /
>> https://github.com/jenkinsci/docker-plugin) and I'd like to help get
>> some of these merged so that we can ship a new release.
>>
>> Could I be made a maintainer for this plugin?
>>
>> Thanks
>> Chris
>>
>

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

Re: LDAP Plugin STARTTLS support

[Kanstantsin Shautsou]

I guess root of issues is https://issues.jenkins-ci.org/browse/JENKINS-5303 
and we need wait 10 more years.

On Thursday, April 6, 2017 at 6:40:09 PM UTC+3, Joseph P wrote:
>
> Seems to be a old issue never resolved:
> https://issues.jenkins-ci.org/browse/JENKINS-14520
>
> Den torsdag den 6. april 2017 kl. 15.12.05 UTC+2 skrev GWarBand:
>>
>> Hello,
>>
>> I have solved the problem by recompile acegi-security-1.0.7 with starttls 
>> support.
>> I have also recompile the ldap plugin with starttls support.
>>
>> This is only a workaround but works fine for me, maybe in future there is 
>> an officiell plugin for 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/c47d8d2c-305f-49f1-8834-9767dcc862f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Install Private Plugin

[Kanstantsin Shautsou]

mvn:package should be enough. 
Yes, you can manually place plugin into plugins directory.
Yes, you can use jusepe for private needs. 

On Monday, April 3, 2017 at 8:34:00 PM UTC+3, David Brooks wrote:
>
> I have a private Jenkins plugin, in that it lives within a private GitHub 
> repo under my company's organization. I was wondering what the best way to 
> install it onto our Jenkins would be that would allow for updates made to 
> the plugin being recognized by Jenkins.
>
> I did come across juseppe  and 
> was wondering if this would be the preferred method of adding a private 
> plugin to our Jenkins.
>
> Another solution would be to checkout our repo to our Jenkins master and 
> then package it via `mvn hpi:hpi` and move the compiled source and .hpi to 
> our Jenkins' plugin folder?
>
> Would prefer a solution that rarely required Jenkins to be rebooted.
>
> Thanks,
> David
>

-- 
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/807d1b6a-3ff4-484e-866d-55f21f072c7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Naming convention for sprints in Jira

[Kanstantsin Shautsou]

Triangle and etc, or it finally removed?

On Wednesday, March 15, 2017 at 7:54:52 PM UTC+3, Daniel Beck wrote:
>
>
> > On 15.03.2017, at 17:39, Kanstantsin Shautsou <kanstan...@gmail.com 
> > wrote: 
> > 
> > Now it messed with statuses created for somebody needs. 
>
> What are you referring to? 
>
>

-- 
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/20a463aa-d874-49a8-9ef5-e8f42bcbc0cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Naming convention for sprints in Jira

[Kanstantsin Shautsou]

The best way for maintainer is not to use jenkins JIRA at all. Now it 
messed with statuses created for somebody needs. While in GH issues you 
have only list of issues and PRs related to code. 

On Tuesday, March 14, 2017 at 12:07:47 AM UTC+3, Stephen Connolly wrote:
>
> Yeah but then we'd have lots of fun as the same issue moves through 1000's 
> of products because the user didn't know which one to file in
>
> On 13 March 2017 at 20:54, James Dumay  > wrote:
>
>> Though this is one of those situations where if we used JIRA correctly 
>> (anything having its own lifecycle should have a project) we could avoid 
>> the name spacing issues (with the added bonus of being able to use Release 
>> Versions - no more confusion as to what has shipped or not...)
>>
>> On Tue, Mar 14, 2017 at 7:48 AM James Dumay > > wrote:
>>
>>> SGTM
>>>
>>> On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck >> > wrote:
>>>
 Hi everyone,

 it seems sprints in Jira are globally visible (across projects), and, 
 when editing an issue, provide little context as to what that sprint is.

 I think some sort of prefix in names should be adopted by everyone 
 using sprints in Jira -- basically James D right now -- to make it easy to 
 see what it relates to. "1.1" is just too light on context. In James' 
 case, 
 BO, Blue Ocean, or similar would be helpful.

 In SECURITY related "sprints" (not really, but still helps plan) I've 
 started using the 'SECURITY' prefix for sprints. So, for example, the 
 'sprint' released on Feb 1 was "SECURITY: Collins".

 WDYT?

 Daniel

 -- 
>>> James Dumay
>>> Product Manager
>>> CloudBees, Inc.
>>> Skype: jdumaycb Twitter: i386
>>>
>> -- 
>> James Dumay
>> Product Manager
>> CloudBees, Inc.
>> Skype: jdumaycb Twitter: i386
>>
>> -- 
>> 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/CAErbOvSCb04K-2_K8q3DdfnGhX9YgqzCayd-mNz4cZpMCL%3DpXg%40mail.gmail.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: Jenkins developers who are also IntelliJ users, please all pile on this bug

[Kanstantsin Shautsou]

Intellij users let's make jenkins integration! I'm more confused with IDEA 
APIs, than cloud apis.

2016.3 fails too much so i'm using 2016.2 and have no issues ;)

-- 
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/f2c91f73-7cf8-4a89-8491-5541e8905a8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: disk-usage-plugin seems to be abandoned

[Kanstantsin Shautsou]

Confirm. @lvotypko made refactorings and disappeared. 
I made few attempts to request release with fixes in last half year, but 
nobody from RedHat made release. Plugin is very useful and before lvotypko 
i was even ready to refactor or write new. 
Who remember @ogondza email? Please CC him. 

-- 
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/75c14ccf-3f37-405b-ba06-b43c3a739d21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

describable databinding from custom configs

[Kanstantsin Shautsou]

Is it possible to instantiate object (i guess only describables) for 
example from yaml. Let's assume that some Describable has Symbol annotation 
and contains some other fields.
And some yaml
describable1:
   describable2:
  someList : [one, two]
 What is required to materialise it? Crazy stapler logic or there is 
something easier?

-- 
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/3341ab82-a7b0-41ca-aee4-0d4c70228ed3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Repo plugin is up for adoption

[Kanstantsin Shautsou]

What plugin?

On Friday, January 13, 2017 at 12:55:31 PM UTC+3, Robert Sandell wrote:
>
> I've put the repo plugin up for adoption. I've been babysitting it for a 
> while since the former maintainers left; basically code reviewing, merging 
> pull requests and releasing new versions after merging. 
> And I can continue to do that, but I feel that I'm doing a disservice by 
> doing it since I'm no longer a repo user myself I can't really plan and 
> evolve the plugin and it could use some more active maintainership from 
> "real users".
>
> I'll continue merging and releasing, but don't be shy if you feel a bit 
> hungry for some more responsibility ;)
>
> -- 
> 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/2adbad8b-48dc-42a7-a0fa-99313192f8fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Should this list be moderated?

[Kanstantsin Shautsou]

Just press spam button.

On Tuesday, December 27, 2016 at 10:43:38 PM UTC+3, Owen B. Mehegan wrote:
>
> It seems like about 1/4 to 1/3 of the new threads on this list are either 
> spam or topics that belong on the users list instead of here. Is there any 
> interest in making the list moderated to help improve the signal to noise 
> ratio? I would be willing to help moderate. I think the only possible 
> downside is that we do want to direct people to the other list when 
> appropriate, so a moderator would need to reject their message but tell 
> them about the other list. But a number of us are doing that all the time 
> anyway, just as regular replies. 
>

-- 
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/208ea5aa-9552-49e5-9efa-8a9a5181e36b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pinned repositories on GitHub

[Kanstantsin Shautsou]

There is no even dynamic stats for recommended plugins, plugin of month 
will be very subjunctive.

On Monday, December 12, 2016 at 11:02:16 AM UTC+3, Aldrin Leal wrote:
>
> why not have a "Plugin of the Month" program and pin it accordingly? :)
>
> --
> -- Aldrin Leal, <ald...@leal.eng.br > / 
> http://about.me/aldrinleal
>
> On Sun, Dec 11, 2016 at 9:55 PM, Daniel Beck <m...@beckweb.net 
> > wrote:
>
>>
>> > On 11.12.2016, at 22:59, Kanstantsin Shautsou <kanstan...@gmail.com 
>> > wrote:
>> >
>> > Why https://github.com/jenkinsci/testrail-plugin is pinned?
>>
>> I don't know. GitHub doesn't keep track of pinning in the audit log. I 
>> asked support about it a while back when weird plugins were showing up 
>> there.
>>
>> I removed it.
>>
>> --
>> 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/FB570260-D7EE-42AC-BE21-6CE3F18D1C67%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/08fd09ec-42b4-48af-b0c0-37175f09ce25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Making a plugin with the same hudson.task.Builder and hudson.task.Publisher implementation

[Kanstantsin Shautsou]

Unfortunately freestyle build is not freestyle. I guess because of workflow 
nobody interested in merging/enhancing other job types. 
There is a workaround by using any-build-step/flexible publisher plugins 
that expose types vice versa. 

On Monday, December 12, 2016 at 7:18:36 PM UTC+3, Dan Alvizu wrote:
>
> Hi,
>
> I'm working on the jira-ext plugin, which updates JIRA tickets as a 
> hudson.task.Builder, which means it shows up in the drop-down of build 
> steps. I would also like to have it show up in the list of post-build 
> steps, which I understand means I must extend a hudson.task.Publisher.
>
> I can just copy-pasta this into another class and have that one extend 
> hudson.task.Publisher, but that seems wrong. The implementation is 
> essentially the same. Is there a smarter way of doing this?
>
> 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/6e9710ee-86df-40f1-9bbf-9d87e9930ae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pinned repositories on GitHub

[Kanstantsin Shautsou]

Why https://github.com/jenkinsci/testrail-plugin is pinned?

On Tuesday, November 1, 2016 at 12:14:52 PM UTC+3, Daniel Beck wrote:
>
>
> > On 01.11.2016, at 07:57, Oliver Gondža  
> wrote: 
> > 
> > (Presuming the point of pinning the repositories is to ease the access 
> for developers, of course.) 
>
> I haven't done this with this in mind, but rather showcase some 
> important/popular ones. 
>
> Established developers will have bookmarks or URL autocompletion for the 
> stuff they regularly work on. And the obscure stuff that nobody can ever 
> find like extras-executable-war shouldn't be highlighted 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/a754db99-1117-4c3a-81f8-63113e796a33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Credentials Provider

[Kanstantsin Shautsou]

I think you don't need CredentialsProvider, but you need firstly choose 
some `Credentials` type (if there is no suitable, then create own), then 
limit your code to work with it and store only String credentials ID. 
Better look into some existing plugin, i.e. github-plugin (or any other). 

CredentialsProvider is a source (via search/list methods) of Credentials 
that may be (or not) contained in some `CredentialsStore`.


On Monday, November 28, 2016 at 11:27:49 PM UTC+3, Stephen Connolly wrote:
>
> I am planning on working on some guides for integrating with the 
> credentials API in the near future. Responding to this thread is also on my 
> todo list
>
> On Mon 21 Nov 2016 at 22:36, Fritz Elfert  > wrote:
>
>> Somehow your screenshots are cut off - I cant see any Test-Connection
>> Button?!
>>
>> Anyway, implementing a test-connection is actually quite easy using a
>> validateButton element. It works like this:
>>
>> supposed, in your .jelly form you have the input-fields named "user",
>> "url" and "key", then you can write in your jelly:
>>
>> > method="testConnection" with="user,url,key"/>
>>
>> In your corresponding DescriptorImpl you then simply put a method that
>> gets the parameters specified in the with="..." attribute like this:
>>
>> public FormValidation doTestConnection(@QueryParameter String user,
>> @QueryParameter String url, @QueryParameter String key) throws 
>> IOException {
>> ...
>> }
>>
>> you get the idea ...
>>  -Fritz
>>
>> On 21.11.2016 22:11, iwarapter wrote:
>> > Hi,
>> >
>> > I'm currently in the process of creating a new credentials provider and
>> > looking for feedback on the based where to implement its authentication
>> > with the backend.
>> >
>> > I have two ways i can probably go with this one is provide the
>> > authentication through credentials similar to the kubernetes plugin for
>> > example:
>> >
>> > <
>> https://lh3.googleusercontent.com/-hXbsw3-YWd4/WDNgjt84AHI/ACg/tWrThothLN0yJchUEJT7b3l26jJNsHMaQCLcB/s1600/Screen%2BShot%2B2016-11-21%2Bat%2B20.59.05.png
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > The alternative is i provide it directly using something similar to the
>> > private key source
>> > <
>> https://github.com/jenkinsci/ssh-credentials-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey.java#L270
>> >
>> > mechanic used in the ssh-credentials plugin:
>> >
>> > <
>> https://lh3.googleusercontent.com/-AOC4CXYnZsc/WDNhde8cBQI/ACo/uUVEYKp22Wct31TJ8AmPbSo0y1CG8PNcQCLcB/s1600/Screen%2BShot%2B2016-11-21%2Bat%2B20.56.38.png
>> >
>> >
>> >
>> > The problem with the second option is providing a 'Test Connection'
>> > style button is very hard (i have no idea if Jelly could even do it).
>> > Whilst providing that feature with the first option is easy, however it
>> > seems a little silly using the original credentials provider as i would
>> > have to implement a new credential impl (for tokens). Am i over thinking
>> > this? I'm aware poor choices early on have the potential to cause alot
>> > of pain later down the line.
>> >
>> > Happy for feedback!
>> >
>> > --
>> > 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/6366b390-4a7b-4880-b35b-e661cc73d645%40googlegroups.com
>> > <
>> https://groups.google.com/d/msgid/jenkinsci-dev/6366b390-4a7b-4880-b35b-e661cc73d645%40googlegroups.com?utm_medium=email_source=footer
>> >.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/b1b6122a-7357-1b9d-1f5b-39c16cf729fc%40fritz-elfert.de
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Sent from my phone
>

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

Re: Disabling node monitors for single use computer

[Kanstantsin Shautsou]

Monitoring API is fully async and uncontrollable. I think you are free to 
contribute any related changed to core via PR where you will get stephenc 
review.

On Wednesday, November 16, 2016 at 4:36:58 AM UTC+3, Surya Gaddipati wrote:
>
> Hi, 
>
> I am running into an issue which I think is related to my single use 
> computer plugin ( 
> https://github.com/suryagaddipati/jenkins-docker-swarm-plugin), which 
> basically creates one computer/build and deletes it after its done. 
>
> This is resulting in accumulation of thousands of node monitor threads in 
> BLOCKED state. I suspect these threads don't go away once the computer goes 
> away. 
>
> I was curious if there is a way to either disable these monitors 
> entirely Jenkins wide or disable them for computer type perhaps a method 
> 'needsMonitoring()' on Computer. 
>
> eg: 
>
> "Monitoring thread for Response Time started on Mon Nov 14 20:55:26 UTC 2016" 
> #43777 daemon prio=5 os_prio=0 tid=0x2aab5f376800 nid=0x1f4b waiting for 
> monitor entry [0x2aabd4e3b000]
>java.lang.Thread.State: BLOCKED (on object monitor)
>   at hudson.remoting.Channel.send(Channel.java:577)
>   - waiting to lock <0x000548779748> (a hudson.remoting.Channel)
>   at hudson.remoting.Request.callAsync(Request.java:205)
>   at hudson.remoting.Channel.callAsync(Channel.java:823)
>   at 
> hudson.node_monitors.AbstractAsyncNodeMonitorDescriptor.monitor(AbstractAsyncNodeMonitorDescriptor.java:75)
>   at 
> hudson.node_monitors.ResponseTimeMonitor$1.monitor(ResponseTimeMonitor.java:57)
>   at 
> hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:305)
>
>
>
>
>

-- 
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/ca3e4b34-b68d-4dcf-9316-1fc180e23dbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can't yank a live executor

[Kanstantsin Shautsou]

1.625.3.1 sounds like CB product, please contact their support.

On Friday, October 28, 2016 at 1:19:56 AM UTC+3, Victor Martinez wrote:
>
> Wrong  mailing list, please ask in the jenkins user mailing list
>
>  https://jenkins.io/content/mailing-lists/
>

-- 
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/f8d2978a-d16a-4997-a55c-b4be453a4080%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adding a node with Queue.withLock in Jenkins

[Kanstantsin Shautsou]

I saw some stories (i.e. job auth context) that looks like a roadmap where 
everybody can join and help. Something the same.

> On Oct 24, 2016, at 00:02, Stephen Connolly <stephen.alan.conno...@gmail.com> 
> wrote:
> 
> I'm waiting for you to provide your usual interjection as to how to get this 
> on the roadmap.
> 
> More seriously, there is possibly some work coming up for trying to 
> rearchitect the queue... but I remain skeptical at present!
> 
> On Sunday 23 October 2016, Kanstantsin Shautsou <kanstantsin@gmail.com 
> <mailto:kanstantsin@gmail.com>> wrote:
> Is there any roadmap for it?
> 
> On Tuesday, October 18, 2016 at 7:48:43 PM UTC+3, Jesse Glick wrote:
> On Tue, Oct 18, 2016 at 12:10 PM, Surya Gaddipati
> <suryap...@gmail.com <>> wrote:
> > neither concerrentmodificationexception nor scheduling
> > on zombie node are applicable here .
> 
> If you are bypassing a lock, a CME seems like a risk.
> 
> > a patch to core that adds nodes to jenkins
> > without unnecessary queue locking.
> 
> Sounds like the wrong approach to me. For the short term Stephen’s advice was
> 
> > For now, use the queue lock methods, when we remove the need for a lock 
> > they will become no-ops that the JVM will inline away for plugins compiled 
> > against current cores
> 
> The real fix would be to bypass `Queue` altogether for these cases and
> inline all the launching and remoting into the lifecycle of the build
> itself. The main issue is that there are some places in Jenkins core
> where it is assumed that a valid `Node`/`Computer` is also in the
> global lists, which is not something you want here. You can create a
> `FilePath` and `Launcher` not tied to a `Node` or `Computer`, but that
> is also poorly supported in various places. So I think a larger
> redesign is necessary. Adding a one-off method which is not in general
> safe to call would just make a compatible transition harder.
> 
> --
> 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+unsubscribe@ 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>googlegroups.com 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/7123adbe-bae2-4a49-aec2-8826b8fc0e0a%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/7123adbe-bae2-4a49-aec2-8826b8fc0e0a%40googlegroups.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> 
> --
> Sent from my phone
> 
> --
> 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/Z2hKvdBDHbw/unsubscribe 
> <https://groups.google.com/d/topic/jenkinsci-dev/Z2hKvdBDHbw/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMw1rQHbB%3Dr1eFOKM5%2BZXmbOKXaB9J%2B%2Bd0GhurrTpUnV1Q%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMw1rQHbB%3Dr1eFOKM5%2BZXmbOKXaB9J%2B%2Bd0GhurrTpUnV1Q%40mail.gmail.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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/5F8B9191-C695-4377-9B95-D5ED7895FDA7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Adding a node with Queue.withLock in Jenkins

[Kanstantsin Shautsou]

Is there any roadmap for it? 

On Tuesday, October 18, 2016 at 7:48:43 PM UTC+3, Jesse Glick wrote:
>
> On Tue, Oct 18, 2016 at 12:10 PM, Surya Gaddipati 
>  wrote: 
> > neither concerrentmodificationexception nor scheduling 
> > on zombie node are applicable here . 
>
> If you are bypassing a lock, a CME seems like a risk. 
>
> > a patch to core that adds nodes to jenkins 
> > without unnecessary queue locking. 
>
> Sounds like the wrong approach to me. For the short term Stephen’s advice 
> was 
>
> > For now, use the queue lock methods, when we remove the need for a lock 
> they will become no-ops that the JVM will inline away for plugins compiled 
> against current cores 
>
> The real fix would be to bypass `Queue` altogether for these cases and 
> inline all the launching and remoting into the lifecycle of the build 
> itself. The main issue is that there are some places in Jenkins core 
> where it is assumed that a valid `Node`/`Computer` is also in the 
> global lists, which is not something you want here. You can create a 
> `FilePath` and `Launcher` not tied to a `Node` or `Computer`, but that 
> is also poorly supported in various places. So I think a larger 
> redesign is necessary. Adding a one-off method which is not in general 
> safe to call would just make a compatible transition harder. 
>

-- 
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/7123adbe-bae2-4a49-aec2-8826b8fc0e0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

[Kanstantsin Shautsou]

One more thing https://issues.jenkins-ci.org/browse/JENKINS-37080

-- 
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/1ec4164f-9cae-442a-9ef3-579ed3bb1a15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

[Kanstantsin Shautsou]

ROR

2016-10-15 21:21 GMT+04:00 Arnaud Héritier <aherit...@gmail.com>:

> FYI PR#66 I would like to apply Olivier's comment before applying it and
> PR#66 daniel's comment.
>
>
> Le samedi 15 octobre 2016, Arnaud Héritier <aherit...@gmail.com> a écrit :
>
>> I was supposed to work on it yesterday but I had a problem at home and I
>> had to stop to work early. There are 2 PRs I would like to finalize before
>> the release. I hope to do it tomorrow evening or at the later on Monday. I
>> don't know if Olivier had some others todo ?
>>
>> Le samedi 15 octobre 2016, Kanstantsin Shautsou <
>> kanstantsin@gmail.com> a écrit :
>>
>>> I have no stacktrace and test case as we replaced guice to released
>>> version in our custom build. Will do of course when get again, but PR in
>>> core is blocked only by maven-plugin release.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-dev/d71732a5-c118-446d-a1d1-01438ce3e3bd%40goo
>>> glegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/d71732a5-c118-446d-a1d1-01438ce3e3bd%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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
>>
>>
>
> --
> -
> 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 a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/fo5nKLhZK5U/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/CAFNCU-8XUYxeQ-fardYEBoEy1zPOxWn%
> 2B2HYhPbH4XMYqqxjQ3w%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8XUYxeQ-fardYEBoEy1zPOxWn%2B2HYhPbH4XMYqqxjQ3w%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

[Kanstantsin Shautsou]

I have no stacktrace and test case as we replaced guice to released version 
in our custom build. Will do of course when get again, but PR in core is 
blocked only by maven-plugin release.

-- 
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/d71732a5-c118-446d-a1d1-01438ce3e3bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: builds verification for stapler/stapler

[Kanstantsin Shautsou]

Thanks! Got build and notification to email from 
https://jenkins.ci.cloudbees.com/job/core/job/stapler/58/ 
<https://jenkins.ci.cloudbees.com/job/core/job/stapler/58/> but it didn’t set 
PR status.

> On Oct 14, 2016, at 16:32, Robert Sandell <rsand...@cloudbees.com> wrote:
> 
> I've updated the webhooks to be x-www-form-urlencoded
> 
> "github-pull-request-hook/" was already set to form encoding and I just 
> changed "github-webhook/ " to it as well.
> 
> /B
> 
> On Fri, Oct 14, 2016 at 3:26 PM, Kanstantsin Shautsou 
> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>> wrote:
> Could you try fix existing stapler/stapler builder?
> 
> Btw as i see idea plugin had some unreleased commits a year ago, does anyone 
> know anything about? Or everybody using IDEA without integrations?
> 
>> On Oct 14, 2016, at 16:24, Robert Sandell <rsand...@cloudbees.com 
>> <mailto:rsand...@cloudbees.com>> wrote:
>> 
>> Only KK has the Owner Role and can add more members to the org afaict.
>> 
>> /B
>> 
>> On Fri, Oct 14, 2016 at 3:19 PM, Kanstantsin Shautsou 
>> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>> wrote:
>> Filling infra issues doesn’t make sense when infra people has no access to 
>> repos.
>> 
>>> On Wednesday, October 12, 2016 at 8:30:18 PM UTC+3, Kanstantsin Shautsou 
>>> wrote:
>>> Issue was created, but could somebody give rtyler and danielbeck access to 
>>> stapler org?
>> 
>> 
>> --
>> 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 
>> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/C5DB22C2-1EFA-42FD-B641-09AB4080B386%40gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/C5DB22C2-1EFA-42FD-B641-09AB4080B386%40gmail.com?utm_medium=email_source=footer>.
>> 
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
>> 
>> 
>> 
>> --
>> Robert Sandell
>> Software Engineer
>> CloudBees Inc.
>> 
>> --
>> 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/tLGDeaVmxkU/unsubscribe 
>> <https://groups.google.com/d/topic/jenkinsci-dev/tLGDeaVmxkU/unsubscribe>.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-dev+unsubscr...@googlegroups.com 
>> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0DO6pgUx%2ByKUb-mXQJzi11aRh8T-QAEtu8L49_nkLq9Q%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0DO6pgUx%2ByKUb-mXQJzi11aRh8T-QAEtu8L49_nkLq9Q%40mail.gmail.com?utm_medium=email_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/8396AE37-1DD3-408C-A260-490EF64235B4%40gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/8396AE37-1DD3-408C-A260-490EF64235B4%40gmail.com?utm_medium=email_source=footer>.
> 
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> 
> 
> --
> Robert Sandell
> Software Engineer
> CloudBees Inc.
> 
> --
> 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/tLGDeaVmxkU/unsubscribe 
> <https://groups.google.com/d/topic/jenkinsci-dev/tLGDeaVmxkU/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> <mailto:

Re: builds verification for stapler/stapler

[Kanstantsin Shautsou]

Could you try fix existing stapler/stapler builder?

Btw as i see idea plugin had some unreleased commits a year ago, does anyone 
know anything about? Or everybody using IDEA without integrations?

> On Oct 14, 2016, at 16:24, Robert Sandell <rsand...@cloudbees.com> wrote:
> 
> Only KK has the Owner Role and can add more members to the org afaict.
> 
> /B
> 
> On Fri, Oct 14, 2016 at 3:19 PM, Kanstantsin Shautsou 
> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>> wrote:
> Filling infra issues doesn’t make sense when infra people has no access to 
> repos.
> 
>> On Wednesday, October 12, 2016 at 8:30:18 PM UTC+3, Kanstantsin Shautsou 
>> wrote:
>> Issue was created, but could somebody give rtyler and danielbeck access to 
>> stapler org?
> 
> 
> --
> 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 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/C5DB22C2-1EFA-42FD-B641-09AB4080B386%40gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/C5DB22C2-1EFA-42FD-B641-09AB4080B386%40gmail.com?utm_medium=email_source=footer>.
> 
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> 
> 
> --
> Robert Sandell
> Software Engineer
> CloudBees Inc.
> 
> --
> 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/tLGDeaVmxkU/unsubscribe 
> <https://groups.google.com/d/topic/jenkinsci-dev/tLGDeaVmxkU/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0DO6pgUx%2ByKUb-mXQJzi11aRh8T-QAEtu8L49_nkLq9Q%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS0DO6pgUx%2ByKUb-mXQJzi11aRh8T-QAEtu8L49_nkLq9Q%40mail.gmail.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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/8396AE37-1DD3-408C-A260-490EF64235B4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: builds verification for stapler/stapler

[Kanstantsin Shautsou]

Filling infra issues doesn’t make sense when infra people has no access to 
repos.

> On Wednesday, October 12, 2016 at 8:30:18 PM UTC+3, Kanstantsin Shautsou 
> wrote:
> Issue was created, but could somebody give rtyler and danielbeck access to 
> stapler org?

-- 
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/C5DB22C2-1EFA-42FD-B641-09AB4080B386%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: builds verification for stapler/stapler

[Kanstantsin Shautsou]

@jglick has no access to org. Who has access to stapler org?

On Wednesday, October 12, 2016 at 8:30:18 PM UTC+3, Kanstantsin Shautsou 
wrote:
>
> Issue was created, but could somebody give rtyler and danielbeck access to 
> stapler org?
>
> On Tuesday, October 11, 2016 at 8:19:54 PM UTC+3, Kanstantsin Shautsou 
> wrote:
>>
>>
>> On Tuesday, October 11, 2016 at 7:26:51 PM UTC+3, Jesse Glick wrote:
>>>
>>> On Tue, Oct 11, 2016 at 11:54 AM, Kanstantsin Shautsou 
>>> <kanstan...@gmail.com> wrote: 
>>> > does anyone remember wether https://github.com/stapler/stapler/ had 
>>> PR 
>>> > builds? 
>>> > I thought it was under 'library' folder on one of 
>>> jenkins-on-for-jenkins 
>>> > instances 
>>>
>>> https://jenkins.ci.cloudbees.com/job/stapler/job/stapler/ 
>>>
>>> Looks like webhooks were failing, apparently due to the webhook being 
>>> set to be delivered as JSON body rather than form encoding. And then 
>>> there is some other problem, I think with credentials. 
>>>
>>> Whatever, probably best to abandon that job and get something running 
>>> on ci.jenkins.io, whether in https://ci.jenkins.io/job/Libraries/ or 
>>> in https://ci.jenkins.io/job/Core/ I am not sure. File an INFRA ticket 
>>> for it. 
>>>
>> If it easy to fix existing, then imho faster fixup existing and then 
>> replace with new.
>> Will fill issue. 
>>
>

-- 
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/35b33ce5-a4cc-4097-a173-a9c751074f6a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

[Kanstantsin Shautsou]

Jenkins still has guice-beta that randomly fails under java8.

-- 
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/cffed57e-5e26-4c06-9318-8682a6ed66f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: builds verification for stapler/stapler

[Kanstantsin Shautsou]

Issue was created, but could somebody give rtyler and danielbeck access to 
stapler org?

On Tuesday, October 11, 2016 at 8:19:54 PM UTC+3, Kanstantsin Shautsou 
wrote:
>
>
> On Tuesday, October 11, 2016 at 7:26:51 PM UTC+3, Jesse Glick wrote:
>>
>> On Tue, Oct 11, 2016 at 11:54 AM, Kanstantsin Shautsou 
>> <kanstan...@gmail.com> wrote: 
>> > does anyone remember wether https://github.com/stapler/stapler/ had PR 
>> > builds? 
>> > I thought it was under 'library' folder on one of 
>> jenkins-on-for-jenkins 
>> > instances 
>>
>> https://jenkins.ci.cloudbees.com/job/stapler/job/stapler/ 
>>
>> Looks like webhooks were failing, apparently due to the webhook being 
>> set to be delivered as JSON body rather than form encoding. And then 
>> there is some other problem, I think with credentials. 
>>
>> Whatever, probably best to abandon that job and get something running 
>> on ci.jenkins.io, whether in https://ci.jenkins.io/job/Libraries/ or 
>> in https://ci.jenkins.io/job/Core/ I am not sure. File an INFRA ticket 
>> for it. 
>>
> If it easy to fix existing, then imho faster fixup existing and then 
> replace with new.
> Will fill issue. 
>

-- 
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/f1d2631e-3211-4270-97c0-a3e270d79572%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: builds verification for stapler/stapler

[Kanstantsin Shautsou]

On Tuesday, October 11, 2016 at 7:26:51 PM UTC+3, Jesse Glick wrote:
>
> On Tue, Oct 11, 2016 at 11:54 AM, Kanstantsin Shautsou 
> <kanstan...@gmail.com > wrote: 
> > does anyone remember wether https://github.com/stapler/stapler/ had PR 
> > builds? 
> > I thought it was under 'library' folder on one of jenkins-on-for-jenkins 
> > instances 
>
> https://jenkins.ci.cloudbees.com/job/stapler/job/stapler/ 
>
> Looks like webhooks were failing, apparently due to the webhook being 
> set to be delivered as JSON body rather than form encoding. And then 
> there is some other problem, I think with credentials. 
>
> Whatever, probably best to abandon that job and get something running 
> on ci.jenkins.io, whether in https://ci.jenkins.io/job/Libraries/ or 
> in https://ci.jenkins.io/job/Core/ I am not sure. File an INFRA ticket 
> for it. 
>
If it easy to fix existing, then imho faster fixup existing and then 
replace with new.
Will fill issue. 

-- 
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/0841e689-0ea7-4066-a305-91fc92393f4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

builds verification for stapler/stapler

[Kanstantsin Shautsou]

Hi, does anyone remember wether https://github.com/stapler/stapler/ had PR 
builds?
I thought it was under 'library' folder on one of jenkins-on-for-jenkins 
instances, but now can't find any commit status in old PRs.
Should it to be added on some of jenkins build instances?

PS Is maintained at all? Does jenkins automation account has access to this 
org?

-- 
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/c728711d-8201-4e42-bb0a-e7a06736133c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Setting CMS or G1 as the default GC algorithm for Jenkins?

[Kanstantsin Shautsou]

Applying theory to practise could be not proved without facts. I would 
suggest collect GC monitoring from jenkins on jenkins (or whatever it 
called now) and compare. Then it will be absolutely clear what is better.

G1 as default for java9... depends on how much patches and differences are 
between java8 and java9 and especially oracle vs openjdk.

On Friday, October 7, 2016 at 12:29:56 AM UTC+3, Samuel Van Oort wrote:
>
> Hi guys, 
> I'd like to propose that we explicitly set the Java args for the Jenkins 
> packages to use either Concurrent Mark Sweep or G1 as the default GC 
> algorithm. 
>
> The reason for this is that Jenkins is generally used as a long-running 
> server process, and large stop-the-world GC pauses can pose a problem for 
> stability and user experience.   The default Java GC algorithm (ParallelGC) 
> is tuned to optimize throughput at the expense of potentially multi-second 
> major GC pauses with large heaps, which is obviously not a good fit for 
> this case. This is why Oracle is moving to G1 as the default as of Java 9.
>
> I would suggest either CMS or G1 make good defaults for normal Jenkins 
> users, because they greatly reduce average and maximum GC pause times.
>
> Thoughts?
>
> Regards,
> Sam Van Oort
>

-- 
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/3d14ad26-e3fe-4c1f-9a0c-29ff705ec2e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pom.xml:parent:update to version:2.3 from 1.580.1

[Kanstantsin Shautsou]

You can 
try 
https://github.com/jenkinsci/dynamic-extended-choice-parameter-plugin/blob/a00bb347424abeaefb3b563fb1ed9a00b90feb56/pom.xml#L36

On Friday, October 7, 2016 at 5:34:24 PM UTC+3, Dzmitry Kashlach wrote:
>
> Hi All,
>
> Please, help with solving challenge.
> After updating 'parent' section in pom.xml to 2.3(
> https://issues.jenkins-ci.org/browse/INFRA-588)
> mvn hangs while running testsuite with 
> *'org.jvnet.hudson.test.JenkinsRule;'*
>
> I've tried to@Ignore this suite, but *mvn clean test* started to hang on 
> *'Running 
> Injected Test'*
>
> Please, advice how to solve 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/8d6ad31a-31c0-433f-8c72-d2a3fdd6152a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Manage our forks as ... git forks

[Kanstantsin Shautsou]

Rename will keep redirect, so not sure.

> On Oct 3, 2016, at 22:10, nicolas de loof <nicolas.del...@gmail.com> wrote:
> 
> My initial proposal was to rename existing as -legacy, which would result in 
> something comparable.
> 
> 
> Le 3 oct. 2016 9:07 PM, "Kanstantsin Shautsou" <kanstantsin@gmail.com 
> <mailto:kanstantsin@gmail.com>> a écrit :
> Backup, delete, fork, push back?
> 
>> On Oct 3, 2016, at 22:05, Baptiste Mathus <m...@batmat.net 
>> <mailto:m...@batmat.net>> wrote:
>> 
>> So, anyway, now we know. It's not possible to attach a fork afterwards 
>> <https://twitter.com/GitHubHelp/status/783018024056029184>.
>> 
>> 2016-10-03 14:52 GMT+02:00 nicolas de loof <nicolas.del...@gmail.com 
>> <mailto:nicolas.del...@gmail.com>>:
>> I'm not sure we can get such a repo easily configured as a fork from xstream
>> Also, this wouldn't help much to maintain our commits as we would then have 
>> two independent commit trees in the same repo
>> 
>> Anyway, if this is considered a better approach, I'm fine with it
>> 
>> 2016-10-03 14:45 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>> <mailto:kanstantsin@gmail.com>>:
>> I mean utilise existing repo instead of creating new. Everything the same 
>> that would be done in new repo, but in old.
>> 
>>> On Oct 3, 2016, at 15:40, nicolas de loof <nicolas.del...@gmail.com 
>>> <mailto:nicolas.del...@gmail.com>> wrote:
>>> 
>>> Not sure I understand your suggestion, how would this help get commits back 
>>> and forth jenkins and xstream plugin ?
>>> 
>>> 
>>> 
>>> 2016-10-03 14:30 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>>> <mailto:kanstantsin@gmail.com>>:
>>> But you can create scratch branch and import anything into?
>>> 
>>> 
>>>> On Oct 3, 2016, at 15:22, nicolas de loof <nicolas.del...@gmail.com 
>>>> <mailto:nicolas.del...@gmail.com>> wrote:
>>>> 
>>>> Our custom fork don't share any commit with the x-stream one as we only 
>>>> imported xstream releases to "incoming" branch. So we don't share history 
>>>> and there's nothing we could link to.
>>>> 
>>>> I've tried to use git grafts to re-attach xstream recent commits to 
>>>> Jenkins repo, but didn't got it to work, and also grafts can't be pushed 
>>>> to github (this is a local hack)
>>>> 
>>>> 
>>>> 2016-10-03 14:15 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>>>> <mailto:kanstantsin@gmail.com>>:
>>>> Maybe try firstly try only with this repo?
>>>> 
>>>>> On Oct 3, 2016, at 15:09, Baptiste Mathus <m...@batmat.net 
>>>>> <mailto:m...@batmat.net>> wrote:
>>>>> 
>>>>> Yup. Just asked through the GitHub support UI.
>>>>> 
>>>>> Then if we agree, I guess we'll just be left with creating the list of 
>>>>> repos to "reconcile" and issue a support request to batch update them via 
>>>>> support.
>>>>> 
>>>>> WDYT?
>>>>> 
>>>>> Cheers
>>>>> 
>>>>> 
>>>>> 2016-10-03 13:58 GMT+02:00 Kanstantsin Shautsou 
>>>>> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>>:
>>>>> Just write to support, they react really fast and solve issues.
>>>>> 
>>>>>> On Oct 3, 2016, at 14:57, Baptiste Mathus <m...@batmat.net 
>>>>>> <mailto:m...@batmat.net>> wrote:
>>>>>> 
>>>>>> Maybe GitHub could just set up the link on existing repos to 
>>>>>> [conceptually] forked ones? I've asked them on Twitter to see if they 
>>>>>> have an answer. Might be possible, since the contrary is and we 
>>>>>> regularly ask them to "break" fork links.
>>>>>> 
>>>>>> 2016-10-03 13:03 GMT+02:00 Kanstantsin Shautsou 
>>>>>> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>>:
>>>>>> +1 Url in top of page should be enough imho.
>>>>>> Maybe name repository `xstream-jenkins` as project do `-jenkins` 
>>>>>> releases?
>>>>>> 
>>>>>> On Monday, October 3, 2016 at 11:16:17 AM UTC+3, nicolas de loof wrote:
&

Re: Manage our forks as ... git forks

[Kanstantsin Shautsou]

Backup, delete, fork, push back?

> On Oct 3, 2016, at 22:05, Baptiste Mathus <m...@batmat.net> wrote:
> 
> So, anyway, now we know. It's not possible to attach a fork afterwards 
> <https://twitter.com/GitHubHelp/status/783018024056029184>.
> 
> 2016-10-03 14:52 GMT+02:00 nicolas de loof <nicolas.del...@gmail.com 
> <mailto:nicolas.del...@gmail.com>>:
> I'm not sure we can get such a repo easily configured as a fork from xstream
> Also, this wouldn't help much to maintain our commits as we would then have 
> two independent commit trees in the same repo
> 
> Anyway, if this is considered a better approach, I'm fine with it
> 
> 2016-10-03 14:45 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
> <mailto:kanstantsin@gmail.com>>:
> I mean utilise existing repo instead of creating new. Everything the same 
> that would be done in new repo, but in old.
> 
>> On Oct 3, 2016, at 15:40, nicolas de loof <nicolas.del...@gmail.com 
>> <mailto:nicolas.del...@gmail.com>> wrote:
>> 
>> Not sure I understand your suggestion, how would this help get commits back 
>> and forth jenkins and xstream plugin ?
>> 
>> 
>> 
>> 2016-10-03 14:30 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>> <mailto:kanstantsin@gmail.com>>:
>> But you can create scratch branch and import anything into?
>> 
>> 
>>> On Oct 3, 2016, at 15:22, nicolas de loof <nicolas.del...@gmail.com 
>>> <mailto:nicolas.del...@gmail.com>> wrote:
>>> 
>>> Our custom fork don't share any commit with the x-stream one as we only 
>>> imported xstream releases to "incoming" branch. So we don't share history 
>>> and there's nothing we could link to.
>>> 
>>> I've tried to use git grafts to re-attach xstream recent commits to Jenkins 
>>> repo, but didn't got it to work, and also grafts can't be pushed to github 
>>> (this is a local hack)
>>> 
>>> 
>>> 2016-10-03 14:15 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>>> <mailto:kanstantsin@gmail.com>>:
>>> Maybe try firstly try only with this repo?
>>> 
>>>> On Oct 3, 2016, at 15:09, Baptiste Mathus <m...@batmat.net 
>>>> <mailto:m...@batmat.net>> wrote:
>>>> 
>>>> Yup. Just asked through the GitHub support UI.
>>>> 
>>>> Then if we agree, I guess we'll just be left with creating the list of 
>>>> repos to "reconcile" and issue a support request to batch update them via 
>>>> support.
>>>> 
>>>> WDYT?
>>>> 
>>>> Cheers
>>>> 
>>>> 
>>>> 2016-10-03 13:58 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>>>> <mailto:kanstantsin@gmail.com>>:
>>>> Just write to support, they react really fast and solve issues.
>>>> 
>>>>> On Oct 3, 2016, at 14:57, Baptiste Mathus <m...@batmat.net 
>>>>> <mailto:m...@batmat.net>> wrote:
>>>>> 
>>>>> Maybe GitHub could just set up the link on existing repos to 
>>>>> [conceptually] forked ones? I've asked them on Twitter to see if they 
>>>>> have an answer. Might be possible, since the contrary is and we regularly 
>>>>> ask them to "break" fork links.
>>>>> 
>>>>> 2016-10-03 13:03 GMT+02:00 Kanstantsin Shautsou 
>>>>> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>>:
>>>>> +1 Url in top of page should be enough imho.
>>>>> Maybe name repository `xstream-jenkins` as project do `-jenkins` releases?
>>>>> 
>>>>> On Monday, October 3, 2016 at 11:16:17 AM UTC+3, nicolas de loof wrote:
>>>>> I've created https://github.com/jenkinsci/xstream-fork 
>>>>> <https://github.com/jenkinsci/xstream-fork>, branch "jenkins" is based on 
>>>>> upstream tag 1.4.7 + diff from our fork, so code is equivalent to 
>>>>> https://github.com/jenkinsci/xstream 
>>>>> <https://github.com/jenkinsci/xstream>
>>>>> 
>>>>> Are you OK I documented on jenkinsci/xstream this repo is deprecated and 
>>>>> redirect users to jenkinsci/xstream-fork if they want to propose PRs ?
>>>>> 
>>>>> 
>>>>> 2016-09-30 23:35 GMT+02:00 Mark Waite <mark.ea...@gmail.com <>>:
>>>>> Wouldn't it be bet

Re: Manage our forks as ... git forks

[Kanstantsin Shautsou]

I mean utilise existing repo instead of creating new. Everything the same that 
would be done in new repo, but in old.

> On Oct 3, 2016, at 15:40, nicolas de loof <nicolas.del...@gmail.com> wrote:
> 
> Not sure I understand your suggestion, how would this help get commits back 
> and forth jenkins and xstream plugin ?
> 
> 
> 
> 2016-10-03 14:30 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
> <mailto:kanstantsin@gmail.com>>:
> But you can create scratch branch and import anything into?
> 
> 
>> On Oct 3, 2016, at 15:22, nicolas de loof <nicolas.del...@gmail.com 
>> <mailto:nicolas.del...@gmail.com>> wrote:
>> 
>> Our custom fork don't share any commit with the x-stream one as we only 
>> imported xstream releases to "incoming" branch. So we don't share history 
>> and there's nothing we could link to.
>> 
>> I've tried to use git grafts to re-attach xstream recent commits to Jenkins 
>> repo, but didn't got it to work, and also grafts can't be pushed to github 
>> (this is a local hack)
>> 
>> 
>> 2016-10-03 14:15 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>> <mailto:kanstantsin@gmail.com>>:
>> Maybe try firstly try only with this repo?
>> 
>>> On Oct 3, 2016, at 15:09, Baptiste Mathus <m...@batmat.net 
>>> <mailto:m...@batmat.net>> wrote:
>>> 
>>> Yup. Just asked through the GitHub support UI.
>>> 
>>> Then if we agree, I guess we'll just be left with creating the list of 
>>> repos to "reconcile" and issue a support request to batch update them via 
>>> support.
>>> 
>>> WDYT?
>>> 
>>> Cheers
>>> 
>>> 
>>> 2016-10-03 13:58 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>>> <mailto:kanstantsin@gmail.com>>:
>>> Just write to support, they react really fast and solve issues.
>>> 
>>>> On Oct 3, 2016, at 14:57, Baptiste Mathus <m...@batmat.net 
>>>> <mailto:m...@batmat.net>> wrote:
>>>> 
>>>> Maybe GitHub could just set up the link on existing repos to 
>>>> [conceptually] forked ones? I've asked them on Twitter to see if they have 
>>>> an answer. Might be possible, since the contrary is and we regularly ask 
>>>> them to "break" fork links.
>>>> 
>>>> 2016-10-03 13:03 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>>>> <mailto:kanstantsin@gmail.com>>:
>>>> +1 Url in top of page should be enough imho.
>>>> Maybe name repository `xstream-jenkins` as project do `-jenkins` releases?
>>>> 
>>>> On Monday, October 3, 2016 at 11:16:17 AM UTC+3, nicolas de loof wrote:
>>>> I've created https://github.com/jenkinsci/xstream-fork 
>>>> <https://github.com/jenkinsci/xstream-fork>, branch "jenkins" is based on 
>>>> upstream tag 1.4.7 + diff from our fork, so code is equivalent to 
>>>> https://github.com/jenkinsci/xstream <https://github.com/jenkinsci/xstream>
>>>> 
>>>> Are you OK I documented on jenkinsci/xstream this repo is deprecated and 
>>>> redirect users to jenkinsci/xstream-fork if they want to propose PRs ?
>>>> 
>>>> 
>>>> 2016-09-30 23:35 GMT+02:00 Mark Waite <mark.ea...@gmail.com <>>:
>>>> Wouldn't it be better to leave the existing repository with its current 
>>>> name to prevent breaking anyone who depends on that location, then create 
>>>> the forked repository under an entirely new name (like xstream-fork)?
>>>> 
>>>> Other than that minor item, I think it is an interesting idea to clearly 
>>>> show projects which are forks of an upstream project.
>>>> 
>>>> Mark Waite
>>>> 
>>>> On Fri, Sep 30, 2016 at 2:32 PM nicolas de loof <nicolas...@gmail.com <>> 
>>>> wrote:
>>>> Hi,
>>>> 
>>>> Jenkins uses some custom builds of external libraries, typically XStream.
>>>> Today such projects are hosted on github, which would make easier to keep 
>>>> in sync and/or propose fixes to upstream project. But we can't reconcile 
>>>> existing repository with project's github.
>>>> 
>>>> Typical sample :
>>>> https://github.com/jenkinsci/xstream/ 
>>>> <https://github.com/jenkinsci/xstream/> vs 
>>>> https://github.com/x-stream/xst

Re: Manage our forks as ... git forks

[Kanstantsin Shautsou]

But you can create scratch branch and import anything into?


> On Oct 3, 2016, at 15:22, nicolas de loof <nicolas.del...@gmail.com> wrote:
> 
> Our custom fork don't share any commit with the x-stream one as we only 
> imported xstream releases to "incoming" branch. So we don't share history and 
> there's nothing we could link to.
> 
> I've tried to use git grafts to re-attach xstream recent commits to Jenkins 
> repo, but didn't got it to work, and also grafts can't be pushed to github 
> (this is a local hack)
> 
> 
> 2016-10-03 14:15 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
> <mailto:kanstantsin@gmail.com>>:
> Maybe try firstly try only with this repo?
> 
>> On Oct 3, 2016, at 15:09, Baptiste Mathus <m...@batmat.net 
>> <mailto:m...@batmat.net>> wrote:
>> 
>> Yup. Just asked through the GitHub support UI.
>> 
>> Then if we agree, I guess we'll just be left with creating the list of repos 
>> to "reconcile" and issue a support request to batch update them via support.
>> 
>> WDYT?
>> 
>> Cheers
>> 
>> 
>> 2016-10-03 13:58 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>> <mailto:kanstantsin@gmail.com>>:
>> Just write to support, they react really fast and solve issues.
>> 
>>> On Oct 3, 2016, at 14:57, Baptiste Mathus <m...@batmat.net 
>>> <mailto:m...@batmat.net>> wrote:
>>> 
>>> Maybe GitHub could just set up the link on existing repos to [conceptually] 
>>> forked ones? I've asked them on Twitter to see if they have an answer. 
>>> Might be possible, since the contrary is and we regularly ask them to 
>>> "break" fork links.
>>> 
>>> 2016-10-03 13:03 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>>> <mailto:kanstantsin@gmail.com>>:
>>> +1 Url in top of page should be enough imho.
>>> Maybe name repository `xstream-jenkins` as project do `-jenkins` releases?
>>> 
>>> On Monday, October 3, 2016 at 11:16:17 AM UTC+3, nicolas de loof wrote:
>>> I've created https://github.com/jenkinsci/xstream-fork 
>>> <https://github.com/jenkinsci/xstream-fork>, branch "jenkins" is based on 
>>> upstream tag 1.4.7 + diff from our fork, so code is equivalent to 
>>> https://github.com/jenkinsci/xstream <https://github.com/jenkinsci/xstream>
>>> 
>>> Are you OK I documented on jenkinsci/xstream this repo is deprecated and 
>>> redirect users to jenkinsci/xstream-fork if they want to propose PRs ?
>>> 
>>> 
>>> 2016-09-30 23:35 GMT+02:00 Mark Waite <mark.ea...@gmail.com <>>:
>>> Wouldn't it be better to leave the existing repository with its current 
>>> name to prevent breaking anyone who depends on that location, then create 
>>> the forked repository under an entirely new name (like xstream-fork)?
>>> 
>>> Other than that minor item, I think it is an interesting idea to clearly 
>>> show projects which are forks of an upstream project.
>>> 
>>> Mark Waite
>>> 
>>> On Fri, Sep 30, 2016 at 2:32 PM nicolas de loof <nicolas...@gmail.com <>> 
>>> wrote:
>>> Hi,
>>> 
>>> Jenkins uses some custom builds of external libraries, typically XStream.
>>> Today such projects are hosted on github, which would make easier to keep 
>>> in sync and/or propose fixes to upstream project. But we can't reconcile 
>>> existing repository with project's github.
>>> 
>>> Typical sample :
>>> https://github.com/jenkinsci/xstream/ 
>>> <https://github.com/jenkinsci/xstream/> vs 
>>> https://github.com/x-stream/xstream <https://github.com/x-stream/xstream>
>>> 
>>> I suggest we rename such a repo on jenkinsci organization as "-legacy", 
>>> then fork the upstream project, and apply a diff to ensure we get our own 
>>> changes back (or maybe try to cherry-pick patches, which would be nicer but 
>>> more complex).
>>> 
>>> We could then ensure PR made to jenkinsci are also proposed to upstream 
>>> project and we only include fixes that are strictly related to jenkins 
>>> usage, or at least changes we approved might be included in a future 
>>> upstream project release
>>> 
>>> wdyt ?
>>> 
>>> 
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Jenkins Devel

Re: Manage our forks as ... git forks

[Kanstantsin Shautsou]

Maybe try firstly try only with this repo?

> On Oct 3, 2016, at 15:09, Baptiste Mathus <m...@batmat.net> wrote:
> 
> Yup. Just asked through the GitHub support UI.
> 
> Then if we agree, I guess we'll just be left with creating the list of repos 
> to "reconcile" and issue a support request to batch update them via support.
> 
> WDYT?
> 
> Cheers
> 
> 
> 2016-10-03 13:58 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
> <mailto:kanstantsin@gmail.com>>:
> Just write to support, they react really fast and solve issues.
> 
>> On Oct 3, 2016, at 14:57, Baptiste Mathus <m...@batmat.net 
>> <mailto:m...@batmat.net>> wrote:
>> 
>> Maybe GitHub could just set up the link on existing repos to [conceptually] 
>> forked ones? I've asked them on Twitter to see if they have an answer. Might 
>> be possible, since the contrary is and we regularly ask them to "break" fork 
>> links.
>> 
>> 2016-10-03 13:03 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>> <mailto:kanstantsin@gmail.com>>:
>> +1 Url in top of page should be enough imho.
>> Maybe name repository `xstream-jenkins` as project do `-jenkins` releases?
>> 
>> On Monday, October 3, 2016 at 11:16:17 AM UTC+3, nicolas de loof wrote:
>> I've created https://github.com/jenkinsci/xstream-fork 
>> <https://github.com/jenkinsci/xstream-fork>, branch "jenkins" is based on 
>> upstream tag 1.4.7 + diff from our fork, so code is equivalent to 
>> https://github.com/jenkinsci/xstream <https://github.com/jenkinsci/xstream>
>> 
>> Are you OK I documented on jenkinsci/xstream this repo is deprecated and 
>> redirect users to jenkinsci/xstream-fork if they want to propose PRs ?
>> 
>> 
>> 2016-09-30 23:35 GMT+02:00 Mark Waite <mark.ea...@gmail.com <>>:
>> Wouldn't it be better to leave the existing repository with its current name 
>> to prevent breaking anyone who depends on that location, then create the 
>> forked repository under an entirely new name (like xstream-fork)?
>> 
>> Other than that minor item, I think it is an interesting idea to clearly 
>> show projects which are forks of an upstream project.
>> 
>> Mark Waite
>> 
>> On Fri, Sep 30, 2016 at 2:32 PM nicolas de loof <nicolas...@gmail.com <>> 
>> wrote:
>> Hi,
>> 
>> Jenkins uses some custom builds of external libraries, typically XStream.
>> Today such projects are hosted on github, which would make easier to keep in 
>> sync and/or propose fixes to upstream project. But we can't reconcile 
>> existing repository with project's github.
>> 
>> Typical sample :
>> https://github.com/jenkinsci/xstream/ 
>> <https://github.com/jenkinsci/xstream/> vs 
>> https://github.com/x-stream/xstream <https://github.com/x-stream/xstream>
>> 
>> I suggest we rename such a repo on jenkinsci organization as "-legacy", then 
>> fork the upstream project, and apply a diff to ensure we get our own changes 
>> back (or maybe try to cherry-pick patches, which would be nicer but more 
>> complex).
>> 
>> We could then ensure PR made to jenkinsci are also proposed to upstream 
>> project and we only include fixes that are strictly related to jenkins 
>> usage, or at least changes we approved might be included in a future 
>> upstream project release
>> 
>> wdyt ?
>> 
>> 
>> 
>> --
>> 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/CANMVJznvDaPk0t%2BMTbgDmiHb34eGZUT%3DLZJVCjd2VOcEcgDsyw%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznvDaPk0t%2BMTbgDmiHb34eGZUT%3DLZJVCjd2VOcEcgDsyw%40mail.gmail.com?utm_medium=email_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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/CAO49JtGPpRL%3Dh0kHeQ2Lh4isi6eNrboSZYhzRMd

Re: Manage our forks as ... git forks

[Kanstantsin Shautsou]

Just write to support, they react really fast and solve issues.

> On Oct 3, 2016, at 14:57, Baptiste Mathus <m...@batmat.net> wrote:
> 
> Maybe GitHub could just set up the link on existing repos to [conceptually] 
> forked ones? I've asked them on Twitter to see if they have an answer. Might 
> be possible, since the contrary is and we regularly ask them to "break" fork 
> links.
> 
> 2016-10-03 13:03 GMT+02:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
> <mailto:kanstantsin@gmail.com>>:
> +1 Url in top of page should be enough imho.
> Maybe name repository `xstream-jenkins` as project do `-jenkins` releases?
> 
> On Monday, October 3, 2016 at 11:16:17 AM UTC+3, nicolas de loof wrote:
> I've created https://github.com/jenkinsci/xstream-fork 
> <https://github.com/jenkinsci/xstream-fork>, branch "jenkins" is based on 
> upstream tag 1.4.7 + diff from our fork, so code is equivalent to 
> https://github.com/jenkinsci/xstream <https://github.com/jenkinsci/xstream>
> 
> Are you OK I documented on jenkinsci/xstream this repo is deprecated and 
> redirect users to jenkinsci/xstream-fork if they want to propose PRs ?
> 
> 
> 2016-09-30 23:35 GMT+02:00 Mark Waite <mark.ea...@gmail.com <>>:
> Wouldn't it be better to leave the existing repository with its current name 
> to prevent breaking anyone who depends on that location, then create the 
> forked repository under an entirely new name (like xstream-fork)?
> 
> Other than that minor item, I think it is an interesting idea to clearly show 
> projects which are forks of an upstream project.
> 
> Mark Waite
> 
> On Fri, Sep 30, 2016 at 2:32 PM nicolas de loof <nicolas...@gmail.com <>> 
> wrote:
> Hi,
> 
> Jenkins uses some custom builds of external libraries, typically XStream.
> Today such projects are hosted on github, which would make easier to keep in 
> sync and/or propose fixes to upstream project. But we can't reconcile 
> existing repository with project's github.
> 
> Typical sample :
> https://github.com/jenkinsci/xstream/ <https://github.com/jenkinsci/xstream/> 
> vs https://github.com/x-stream/xstream <https://github.com/x-stream/xstream>
> 
> I suggest we rename such a repo on jenkinsci organization as "-legacy", then 
> fork the upstream project, and apply a diff to ensure we get our own changes 
> back (or maybe try to cherry-pick patches, which would be nicer but more 
> complex).
> 
> We could then ensure PR made to jenkinsci are also proposed to upstream 
> project and we only include fixes that are strictly related to jenkins usage, 
> or at least changes we approved might be included in a future upstream 
> project release
> 
> wdyt ?
> 
> 
> 
> --
> 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/CANMVJznvDaPk0t%2BMTbgDmiHb34eGZUT%3DLZJVCjd2VOcEcgDsyw%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznvDaPk0t%2BMTbgDmiHb34eGZUT%3DLZJVCjd2VOcEcgDsyw%40mail.gmail.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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/CAO49JtGPpRL%3Dh0kHeQ2Lh4isi6eNrboSZYhzRMdx9PRm%2Bghz6A%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGPpRL%3Dh0kHeQ2Lh4isi6eNrboSZYhzRMdx9PRm%2Bghz6A%40mail.gmail.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/4feee351-d040-4782-8876-a90034266d12%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/4feee351-d040-4782-8876-a9003426

Re: Manage our forks as ... git forks

[Kanstantsin Shautsou]

+1 Url in top of page should be enough imho.
Maybe name repository `xstream-jenkins` as project do `-jenkins` releases?

On Monday, October 3, 2016 at 11:16:17 AM UTC+3, nicolas de loof wrote:
>
> I've created https://github.com/jenkinsci/xstream-fork, branch "jenkins" 
> is based on upstream tag 1.4.7 + diff from our fork, so code is equivalent 
> to https://github.com/jenkinsci/xstream
>
> Are you OK I documented on jenkinsci/xstream this repo is deprecated and 
> redirect users to jenkinsci/xstream-fork if they want to propose PRs ?
>
>
> 2016-09-30 23:35 GMT+02:00 Mark Waite 
> :
>
>> Wouldn't it be better to leave the existing repository with its current 
>> name to prevent breaking anyone who depends on that location, then create 
>> the forked repository under an entirely new name (like xstream-fork)?
>>
>> Other than that minor item, I think it is an interesting idea to clearly 
>> show projects which are forks of an upstream project.
>>
>> Mark Waite
>>
>> On Fri, Sep 30, 2016 at 2:32 PM nicolas de loof > > wrote:
>>
>>> Hi,
>>>
>>> Jenkins uses some custom builds of external libraries, typically XStream.
>>> Today such projects are hosted on github, which would make easier to 
>>> keep in sync and/or propose fixes to upstream project. But we can't 
>>> reconcile existing repository with project's github.
>>>
>>> Typical sample : 
>>> https://github.com/jenkinsci/xstream/ vs 
>>> https://github.com/x-stream/xstream
>>>
>>> I suggest we rename such a repo on jenkinsci organization as "-legacy", 
>>> then fork the upstream project, and apply a diff to ensure we get our own 
>>> changes back (or maybe try to cherry-pick patches, which would be nicer but 
>>> more complex).
>>>
>>> We could then ensure PR made to jenkinsci are also proposed to upstream 
>>> project and we only include fixes that are strictly related to jenkins 
>>> usage, or at least changes we approved might be included in a future 
>>> upstream project release
>>>
>>> wdyt ?
>>>
>>>
>>> -- 
>>> 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/CANMVJznvDaPk0t%2BMTbgDmiHb34eGZUT%3DLZJVCjd2VOcEcgDsyw%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/CAO49JtGPpRL%3Dh0kHeQ2Lh4isi6eNrboSZYhzRMdx9PRm%2Bghz6A%40mail.gmail.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: Deleted merged branches from jenkinsci/jenkins

[Kanstantsin Shautsou]

On Friday, September 23, 2016 at 2:33:55 AM UTC+3, Daniel Beck wrote:
>
>
> > On 22.09.2016, at 23:55, Kanstantsin Shautsou <kanstan...@gmail.com 
> > wrote: 
> > 
> > Finally! Now the question is about staled branches and single-person 
> branches. 
>
> Yes. I made a list and plan to contact the authors about them, to delete 
> them if obsolete, or, if not, at least move them over into their own 
> repositories. 
>
> It seems that GH now has feature that allows pushing commits into source 
PR branch and having shared branches will be easier. Would expected to see 
lower number of branches in jenkins origin.

If checked, users with write access to jenkinsci/jenkins can add new commits to 
your patch-6 branch. You can always change this setting later. 

-- 
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/ab71a9d4-1617-47c3-a448-fa5e2b3b4e5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deleted merged branches from jenkinsci/jenkins

[Kanstantsin Shautsou]

Finally! Now the question is about staled branches and single-person 
branches.

On Thursday, September 22, 2016 at 1:14:01 AM UTC+3, Daniel Beck wrote:
>
> Hi everyone, 
>
> I deleted a bunch of obsolete branches that have been merged into master 
> from jenkinsci/jenkins. It's not all merged branches, but most of them. The 
> list is below. 
>
> Daniel 
>
> 1.408 (was 1d4abe2). 
> 1.469-out-of-cycle (was 201bd2f). 
> 1.509 (was 02e0044). 
> 1.609 (was 152d00a). 
> 1.650 (was 3a44687). 
> 1.652 (was 3a44687). 
> PR-2138 (was 1735f3c). 
> SECURITY-54 (was f4496df). 
> add-plugin-without-restart (was 992158b). 
> artefacts-to-artifacts (was c5b55a1). 
> breadcrumb (was 17d9b62). 
> changelog (was 3bce100). 
> directly-modifiable-view (was 8fc60f0). 
> domain-discovery (was 358b9ce). 
> federated-login-service (was 872c664). 
> file_leak (was dc710b7). 
> groovy-view (was 77290b9). 
> guice (was 5d90351). 
> item-categorisation-2 (was 277a743). 
> jenkins-19898 (was 0e122df). 
> jruby (was 58d2024). 
> label-parameterization (was 6764621). 
> lazy-load (was 2f20f42). 
> localization-20131020 (was bc711ee). 
> main (was 8f6b8f1). 
> main-maven3-support (was 7cf3f7f). 
> matrix-subset (was 0203876). 
> maven-3.1.0 (was 6030c77). 
> ndeloof-patch-1 (was a6ce5a8). 
> prototype-incoming (was 8009dcc). 
> prototype-patched (was 34e8117). 
> publisher (was 58267c4). 
> pull-434.2 (was 72fbaba). 
> rc (was 501b61f). 
> svn (was 776008c). 
> type-on-body (was 9178977). 
> webmethods-improvements (was 490b3b4).

-- 
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/b8f96f83-5694-478d-a762-7c2fc417e0b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Interested in building your plugin on ci.jenkins.io?

[Kanstantsin Shautsou]

So moving back from flexible DSL to declarative configuration?

2016-09-06 23:41 GMT+03:00 :

> I assume you are talking about the new plugin created by Andrew Bayer?
>
>
>
> https://jenkins.io/blog/2016/09/06/jenkins-world-speaker-
> blog-pipeline-model-definition/
>
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+
> Model+Definition+Plugin
>
>
>
>
>
>
>
> *From: *Mark Waite 
> *Sent: *September 6, 2016 1:25 PM
> *To: *jenkinsci-dev@googlegroups.com
> *Subject: *Re: Interested in building your plugin on ci.jenkins.io?
>
>
>
>
>
> On Tue, Sep 6, 2016 at 2:08 PM R. Tyler Croy  wrote:
>
> (replies inline)
>
> On Sun, 04 Sep 2016, Mark Waite wrote:
>
> > Is there a plan to update ci.jenkins.io to the latest workflow plugin so
> > that I can switch to uses "{" and  "}" to identify blocks?  I'd like to
> > remove the warning from the jobs I host on my private machines, but I
> don't
> > want to break ci.jenkins.io with a Jenkinsfile that it does not yet
> > understand.
>
>
> I'm not sure I understand what you're referring to. To identify *stage*
> blocks
> I presume?
>
>
>
> Yes, to identify "stage" blocks.  Currently, the git client plugin and the
> git plugin both include a Jenkinsfile on their relevant branches.  Those
> files use the previous syntax:
>
>
>
> node {
>
>   stage 'Checkout'
>
>   checkout scm
>
>   stage 'Build'
>
>   mvn "clean install"
>
> }
>
>
>
> I'd like to switch to the new syntax:
>
>
>
> node {
>
>   stage('Checkout') {
>
> checkout scm
>
>   |
>
>   stage('Build') {
>
> mvn "clean install"
>
>   }
>
> }
>
>
>
> If I switch to the new syntax, machines running older versions of the
> pipeline plugins will fail because they don't understand the new syntax.
>
>
>
> Thanks,
>
> Mark Waite
>
>
>
>
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> --
> 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/20160906200817.GF18556%40blackberry.coupleofllamas.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/439-IDYNSVY/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/CAO49JtGH5V_LDZDd%3DXU9WbLp3b1WrO6SA_
> v7bgJd6scQHqd-0g%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/439-IDYNSVY/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/57cf29dc.46ec420a.ca6c.09c2%40mx.google.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/CAM9nkw9652gkpS-s_2t0FYBkinm3zb4zABxuXmPFOXr_hjCA2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Interested in building your plugin on ci.jenkins.io?

[Kanstantsin Shautsou]

In travis i have sudo and running docker, i can re-install it and i can run 
docker in docker. Prepare env in any way i need for integration tests.
So the same.
> On Aug 12, 2016, at 17:00, R. Tyler Croy <ty...@monkeypox.org> wrote:
> 
> (replies inline)
> 
> On Fri, 12 Aug 2016, Kanstantsin Shautsou wrote:
> 
>> Is it possible to run docker daemon?
> 
> 
> Could you expand more on what you mean by this? Does this mean executing an
> agent as root, or having the ability to run a Docker daemon parallel to the 
> one
> already running on the machine?
> 
> 
> As of right now there are no dynamically provisioned agents attached to
> ci.jenkins.io, but my plan is to change to having some Swarm-based agents and
> some freshly provisioned Azure agents.
> 
> 
> 
> Cheers
> - R. Tyler Croy
> 
> --
> Code: <https://github.com/rtyler>
>  Chatter: <https://twitter.com/agentdero>
> 
>  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> --
> 
> --
> 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/439-IDYNSVY/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/20160812140012.GD22427%40blackberry.coupleofllamas.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/995D86DE-E17E-4FAE-8D15-43D424B63365%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Interested in building your plugin on ci.jenkins.io?

[Kanstantsin Shautsou]

Is it possible to run docker daemon?

-- 
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/5fea5dd6-9c9f-412f-b0bc-e47ede6ef58e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Developers for a fun project

[Kanstantsin Shautsou]

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

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

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

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

[Kanstantsin Shautsou]

Bless you! :)

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

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

Re: Download stats no longer showing on some plugin-wikis

[Kanstantsin Shautsou]

Maybe reset cache?

On Thursday, July 28, 2016 at 1:12:46 AM UTC+3, Daniel Beck wrote:
>
> It was. 
>
> It's fixed now, but we cache aggressively, so may require adding a query 
> string to the URL to circumvent the cache. 
>
> > On 27.07.2016, at 17:29, Daniel Beck  
> wrote: 
> > 
> > I wonder whether this is related to the move of stats to 
> stats.jenkins.io… 
> > 
> >> On 27.07.2016, at 15:21, Martin Weber  > wrote: 
> >> 
> >> Hi, 
> >> topic says all. 
> >> 
> >> Missing in 
> >>  
> >>  
> >> 
> >> Showing in 
> >> <
> https://wiki.jenkins-ci.org/display/JENKINS/System+Load+Average+Monitor+Plugin>
>  
>
> >> 
> >> Martin 
> >> -- 
> >> Cd wrttn wtht vwls s mch trsr. 
> >> 
> >> 
> >> -- 
> >> 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/7036516.8FLrZlAcId%40linux. 
>
> >> 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/8CD5B8ED-ADBD-4CD6-898A-99A92CC22FF0%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/c273b612-4af2-4f44-82b7-747aa08704a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to enable Travis CI for jenkins plugin repo

[Kanstantsin Shautsou]

Thanks, will look. Doc appeared one week ago?

On Friday, July 22, 2016 at 2:46:44 PM UTC+3, Thomas Zoratto wrote:
>
> I’m not sure if this is what you mean by 'missing stats per branche' or 
> not but you can have different reports for each branch in SonarQube (see 
> sonar.branch property 
> http://docs.sonarqube.org/display/SONAR/Analysis+Parameters)
>
> Le 22 juil. 2016 à 00:27, Kanstantsin Shautsou <kanstan...@gmail.com 
> > a écrit :
>
> Good question, AFAIR we discussed few times to have SonarQube and Coverity 
> specially for Jenkins, but end with unability to do something in INFRA.
> According to email answer, public sonarqube (nemo instance?) has no 
> “service” feature where people can manage themselves configuration. 
> Codecov.io <http://codecov.io/> is only about coverage based on jacoco 
> results (sonar seems is more powerful, but missing stats per branche).
>
> Pushing automatically from jenkinsci will work. Jenkinsfile should work 
> for custom envs, but what could be done with env internals is under 
> question. With travis it is possible to run any SW/daemons internally. Ans 
> is Jenkinsfile already available for plugins?
>
> On Jul 21, 2016, at 22:52, Arnaud Héritier <aher...@gmail.com 
> > wrote:
>
> codecov is a competitor of SonarQube ?
>
> ex : https://sonarqube.com/overview?id=org.jenkins-ci.main%3Apom 
> <https://sonarqube.com/overview?id=org.jenkins-ci.main:pom>
>
> On Thu, Jul 21, 2016 at 8:18 PM, Gavin Mogan <ga...@gavinmogan.com 
> > wrote:
>
>> I asked the same question late last year.
>>
>> I have heard rumors that the cloudbees templates are being updated to use 
>> Jenkinsfile, which would be awesome.
>>
>> Right now we've forked and done development on our own repo so we can 
>> trigger a build that does codecov and a few other minor things, but it 
>> would be amazing to use jenkins full time and be able to provide secure 
>> credentials somewhow.
>>
>> Short term though, I'd love codecov ('cause thats what I'm using too)
>>
>> Gavin
>>
>> On Wednesday, July 20, 2016 at 1:51:14 PM UTC-7, Kohsuke Kawaguchi wrote:
>>>
>>> So in this case the motivation is to activate Codecov.io 
>>> <http://codecov.io/> on plugins. On 
>>> https://jenkins.ci.cloudbees.com/job/plugins/ we use templating so that 
>>> we only need to change the setting once to impact every plugin.
>>>
>>> If we make that change across the board, would that make you happy 
>>> enough to stop the use of Travis? It seems like it's a relatively easy 
>>> change to make it happen, and I think it'd benefit everyone.
>>>
>>> I'm asking because I think it sends a wrong signal when we are using 
>>> Travis for something Jenkins does just as well.
>>>
>>> On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <ap...@ya.ru> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm the maintainer for performance-plugin repo.
>>>>
>>>> I'm trying to use my typical approach with controlling the project 
>>>> quality using GitHub+TravisCI+Codecov integration, which proven its value 
>>>> for me. However, I'm missing the admin right on repo to enable TravisCI 
>>>> for 
>>>> it. Can anybody help me enabling it? I don't need the admin rights per se, 
>>>> just need to enable TravisCI for it.
>>>>
>>>> https://travis-ci.org/jenkinsci/performance-plugin
>>>>
>>>> --
>>>> Andrey
>>>>
>>>> -- 
>>>> 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/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> http

Re: How to enable Travis CI for jenkins plugin repo

[Kanstantsin Shautsou]

Good question, AFAIR we discussed few times to have SonarQube and Coverity 
specially for Jenkins, but end with unability to do something in INFRA.
According to email answer, public sonarqube (nemo instance?) has no “service” 
feature where people can manage themselves configuration.
Codecov.io is only about coverage based on jacoco results (sonar seems is more 
powerful, but missing stats per branche).

Pushing automatically from jenkinsci will work. Jenkinsfile should work for 
custom envs, but what could be done with env internals is under question. With 
travis it is possible to run any SW/daemons internally. Ans is Jenkinsfile 
already available for plugins?

> On Jul 21, 2016, at 22:52, Arnaud Héritier  wrote:
> 
> codecov is a competitor of SonarQube ?
> 
> ex : https://sonarqube.com/overview?id=org.jenkins-ci.main%3Apom 
> 
> 
> On Thu, Jul 21, 2016 at 8:18 PM, Gavin Mogan  > wrote:
> I asked the same question late last year.
> 
> I have heard rumors that the cloudbees templates are being updated to use 
> Jenkinsfile, which would be awesome.
> 
> Right now we've forked and done development on our own repo so we can trigger 
> a build that does codecov and a few other minor things, but it would be 
> amazing to use jenkins full time and be able to provide secure credentials 
> somewhow.
> 
> Short term though, I'd love codecov ('cause thats what I'm using too)
> 
> Gavin
> 
> On Wednesday, July 20, 2016 at 1:51:14 PM UTC-7, Kohsuke Kawaguchi wrote:
> So in this case the motivation is to activate Codecov.io on plugins. On 
> https://jenkins.ci.cloudbees.com/job/plugins/ 
>  we use templating so that we 
> only need to change the setting once to impact every plugin.
> 
> If we make that change across the board, would that make you happy enough to 
> stop the use of Travis? It seems like it's a relatively easy change to make 
> it happen, and I think it'd benefit everyone.
> 
> I'm asking because I think it sends a wrong signal when we are using Travis 
> for something Jenkins does just as well.
> 
> On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko > wrote:
> Hi,
> 
> I'm the maintainer for performance-plugin repo.
> 
> I'm trying to use my typical approach with controlling the project quality 
> using GitHub+TravisCI+Codecov integration, which proven its value for me. 
> However, I'm missing the admin right on repo to enable TravisCI for it. Can 
> anybody help me enabling it? I don't need the admin rights per se, just need 
> to enable TravisCI for it.
> 
> https://travis-ci.org/jenkinsci/performance-plugin 
> 
> 
> --
> Andrey
> 
> --
> 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/d43f9a06-568c-4d29-995f-e182f093a703%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/2a7e33bc-c9cf-403c-8e8c-a9eb53629bac%40googlegroups.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 a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/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/CAFNCU-8eTg0T9DYVvsEVBtLrBTA0_-acL4b%3DLhAZE3RUHt60eA%40mail.gmail.com
>  
> 

Re: How to enable Travis CI for jenkins plugin repo

[Kanstantsin Shautsou]

> On Jul 21, 2016, at 02:14, Kohsuke Kawaguchi <k...@kohsuke.org> wrote:
> 
> Jenkins does provide a way to configure the build process, for example via 
> Jenkinsfile, via Job DSL plugin, etc.
Thanks, i know.
> 
> Like I said in my previous email, it's just that in jenkins.io.cloudbees.com 
> <http://jenkins.io.cloudbees.com/> we choose to use a template to lock things 
> down.
That what i mean.
> 
> IIUC reviewable.io <http://reviewable.io/> is orthogonal to this. That's 
> between GitHub and it.
It requires admin access in repo to setup hooks.

> 
> On Wed, Jul 20, 2016 at 1:55 PM Kanstantsin Shautsou 
> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>> wrote:
> Jenkins CloudBees doesn’t provide any ways to control or configure build 
> process and integrations. In 2016 that’s blocker for development. Also you 
> can’t do anything with reviewable.io <http://reviewable.io/> because you have 
> no analogues.
> 
> 
>> On Jul 20, 2016, at 23:51, Kohsuke Kawaguchi <k...@kohsuke.org 
>> <mailto:k...@kohsuke.org>> wrote:
>> 
> 
>> So in this case the motivation is to activate Codecov.io 
>> <http://codecov.io/> on plugins. On 
>> https://jenkins.ci.cloudbees.com/job/plugins/ 
>> <https://jenkins.ci.cloudbees.com/job/plugins/> we use templating so that we 
>> only need to change the setting once to impact every plugin.
>> 
>> If we make that change across the board, would that make you happy enough to 
>> stop the use of Travis? It seems like it's a relatively easy change to make 
>> it happen, and I think it'd benefit everyone.
>> 
>> I'm asking because I think it sends a wrong signal when we are using Travis 
>> for something Jenkins does just as well.
>> 
>> On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko <a...@ya.ru 
>> <mailto:a...@ya.ru>> wrote:
>> Hi,
>> 
>> I'm the maintainer for performance-plugin repo.
>> 
>> I'm trying to use my typical approach with controlling the project quality 
>> using GitHub+TravisCI+Codecov integration, which proven its value for me. 
>> However, I'm missing the admin right on repo to enable TravisCI for it. Can 
>> anybody help me enabling it? I don't need the admin rights per se, just need 
>> to enable TravisCI for it.
>> 
>> https://travis-ci.org/jenkinsci/performance-plugin 
>> <https://travis-ci.org/jenkinsci/performance-plugin>
>> 
>> --
>> Andrey
>> 
>> --
>> 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 
>> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com?utm_medium=email_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
>> 
>> --
> 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe 
>> <https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/unsubscribe>.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-dev+unsubscr...@googlegroups.com 
>> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xaX%2BMp8es0%3DdkR01ychfL1JTxinPj%2BA0BYLpD5hnWOBQ%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xaX%2BMp8es0%3DdkR01ychfL1JTxinPj%2BA0BYLpD5hnWOBQ%40mail.gmail.com?utm_medium=email_source=footer>.
> 
>> 
>> For more options, visit https://groups.google.com/d/optout 
>> <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 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https:/

Re: How to enable Travis CI for jenkins plugin repo

[Kanstantsin Shautsou]

Jenkins CloudBees doesn’t provide any ways to control or configure build 
process and integrations. In 2016 that’s blocker for development. Also you 
can’t do anything with reviewable.io because you have no analogues.

> On Jul 20, 2016, at 23:51, Kohsuke Kawaguchi  wrote:
> 
> So in this case the motivation is to activate Codecov.io on plugins. On 
> https://jenkins.ci.cloudbees.com/job/plugins/ 
>  we use templating so that we 
> only need to change the setting once to impact every plugin.
> 
> If we make that change across the board, would that make you happy enough to 
> stop the use of Travis? It seems like it's a relatively easy change to make 
> it happen, and I think it'd benefit everyone.
> 
> I'm asking because I think it sends a wrong signal when we are using Travis 
> for something Jenkins does just as well.
> 
> On Wed, Jul 6, 2016 at 2:12 AM Andrey Pohilko  > wrote:
> Hi,
> 
> I'm the maintainer for performance-plugin repo.
> 
> I'm trying to use my typical approach with controlling the project quality 
> using GitHub+TravisCI+Codecov integration, which proven its value for me. 
> However, I'm missing the admin right on repo to enable TravisCI for it. Can 
> anybody help me enabling it? I don't need the admin rights per se, just need 
> to enable TravisCI for it.
> 
> https://travis-ci.org/jenkinsci/performance-plugin 
> 
> 
> --
> Andrey
> 
> --
> 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/d43f9a06-568c-4d29-995f-e182f093a703%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/n3b2LbHeV6Y/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/CAN4CQ4xaX%2BMp8es0%3DdkR01ychfL1JTxinPj%2BA0BYLpD5hnWOBQ%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

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


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Jenkins project build servers offline

[Kanstantsin Shautsou]

CC RTyler Abayer

On Sunday, July 17, 2016 at 2:06:00 AM UTC+3, Mark Waite wrote:
>
> The build servers where I usually see pull requests evaluated (
> https://jenkins.ci.cloudbees.com/job/plugins/job/git-client-plugin/) has 
> been preparing to shutdown for about 12 hours.
>
> Will it be back soon?
>
> Mark Waite
>

-- 
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/5c3a36b3-aca2-4384-a006-c19a527eb6fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to use jenkins dsl-plugin to pull the DB for 500 applications

[Kanstantsin Shautsou]

Please use users-maillist firstly. This maillist is aboud jenkins 
development itself.

On Saturday, July 16, 2016 at 4:25:05 PM UTC+3, Naga Saketh Jaligama wrote:
>
>
>1. We have 500 applications running in prod and we have all the 
>applications info in DB.
>2. We need to use jenkins job and tasks , in each job we will have 3 
>tasks to perform i.e a)read the application info from db into logs B)stop 
>the application C)verify the logs if application is stopped properly. So, 
> i 
>want these 3 taSks to be pErformed for every apPlication. So, is there any 
>easy way to do it instead of having 500 jobs for 500 applications and all 
>the applications are independent. So, any way to run them parallel. Our 
>jenkins is not yet installed too, it would be used only for this 
> automation.
>
>

-- 
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/1b8559f2-9802-4e18-bb10-ed2ab8b6b840%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to enable Travis CI for jenkins plugin repo

[Kanstantsin Shautsou]

Ability to configure build process, ability to set credentials and upload 
something to external services, etc.

> On Jul 16, 2016, at 00:35, Liam Newman  wrote:
> 
> Andrey,
> What does running in TravisCI provide that is not already in the 
> jenkinsci.org build?  Just wondering.
> 
> Thanks!
> Liam Newman
> 
> 
> --
> 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/n3b2LbHeV6Y/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/dd684a61-61cd-4d8e-bbf7-c7965949e32e%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/65E4F229-7B99-41D5-A889-3931E0EE23C7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: How to enable Travis CI for jenkins plugin repo

[Kanstantsin Shautsou]

Try contact INFRA team and ask them to provide admin access to your plugin. 

On Wednesday, July 6, 2016 at 12:12:07 PM UTC+3, Andrey Pohilko wrote:
>
> Hi,
>
> I'm the maintainer for performance-plugin repo.
>
> I'm trying to use my typical approach with controlling the project quality 
> using GitHub+TravisCI+Codecov integration, which proven its value for me. 
> However, I'm missing the admin right on repo to enable TravisCI for it. Can 
> anybody help me enabling it? I don't need the admin rights per se, just 
> need to enable TravisCI for it.
>
> https://travis-ci.org/jenkinsci/performance-plugin
>
> --
> Andrey
>

-- 
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/7e51e25d-cf8c-4494-b503-300e7f52f4f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Jenkins World 2016 ] Get 20% OFF

[Kanstantsin Shautsou]

AFAIK there is an events list for such announcements. And this list is
about development https://groups.google.com/forum/#!aboutgroup/jenkinsci-dev


2016-07-06 20:20 GMT+03:00 Alyssa Tong :

> My apologies this came across as spam. Just wanted to share the 20%
> discount.
>
> On Sat, Jul 2, 2016 at 12:15 PM, Samat Davletshin 
> wrote:
>
>> Yes, a bit too similar to a TV ad selling a brand new juicer :-)
>> May be a less persistent message would look better for a developer forum.
>> Telling as a marketing student :-)
>>
>> --
>> 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/d5f2a185-82cb-48c8-89c2-1d28b58f6989%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/kUIJAtsQ1VM/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/CAC9wNazcpXQhg2VBTYQHt%2BAhAb_jk8KZfHehSLqmj1z31xGSzw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: GitHub pull request builder plugin changelog and issues

[Kanstantsin Shautsou]

Those who need - will find! ;)

2016-07-05 12:39 GMT+03:00 Arnaud Héritier <aherit...@gmail.com>:

> Yes git logs gave me the same than Jira.
> But if each time we need to contact a plugin owner we need to find the
> email in git logs it will be a nightmare
>
> On Tue, Jul 5, 2016 at 11:28 AM, Kanstantsin Shautsou <
> kanstantsin@gmail.com> wrote:
>
>> git clone, git show? Does it have email?
>>
>> On Jul 5, 2016, at 12:22, Arnaud Héritier <aherit...@gmail.com> wrote:
>>
>>
>>
>> On Tue, Jul 5, 2016 at 9:57 AM, Kanstantsin Shautsou <
>> kanstantsin@gmail.com> wrote:
>>
>>> Most of devs doesn't read this maillist, write directly to latest
>>> committers to get response.
>>>
>>
>> :( But there is no email in David's profile (which I understand)
>>
>> I don't know how our community could improve the management of the
>> communication but it is painful :(
>>
>> @david I hope you are the right one in copy. I found your email in Jira.
>> If you have some feedbacks about my questions below
>>
>> Thanks a lot
>>
>> cheers
>>
>>
>>>
>>>
>>> On Tuesday, July 5, 2016 at 10:45:57 AM UTC+3, Arnaud Héritier wrote:
>>>>
>>>> ping ? no feedback ?
>>>>
>>>> On Mon, Jun 27, 2016 at 10:07 AM, Arnaud Héritier <aher...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi GitHub pull request builder plugin owners
>>>>>
>>>>>   I don't really know the reason but you have 2 issues trackers, the
>>>>> official JIRA component [1] and the GitHub issues tracker [2]. I don't 
>>>>> know
>>>>> where to report issues. Can you help me ?
>>>>>
>>>>>   Also it seems that the changelog isn't updated in Confluence [3]
>>>>> and in GitHub [4]. Latest version is 1.32.6 and I don't find anything
>>>>> documented after 1.30.2
>>>>>
>>>>>   Do we have to read github commits to see what was changed or do I
>>>>> miss something ?
>>>>>
>>>>> Thanks a  lot
>>>>>
>>>>> 1 :
>>>>> http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide=true=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27ghprb-plugin%27
>>>>> 2 : https://github.com/jenkinsci/ghprb-plugin/issues
>>>>> 3 :
>>>>> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin
>>>>> 4 : https://github.com/jenkinsci/ghprb-plugin/blob/master/README.md
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -
>>>>> Arnaud Héritier
>>>>> http://aheritier.net
>>>>> Mail/GTalk: aheritier AT gmail DOT com
>>>>> Twitter/Skype : aheritier
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -
>>>> Arnaud Héritier
>>>> http://aheritier.net
>>>> Mail/GTalk: aheritier AT gmail DOT com
>>>> Twitter/Skype : aheritier
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/c7be01b7-85a2-40fd-bfc1-8d8bb6715010%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/c7be01b7-85a2-40fd-bfc1-8d8bb6715010%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>> 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 a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/zpdxOxNCwRw/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/m

Re: GitHub pull request builder plugin changelog and issues

[Kanstantsin Shautsou]

git clone, git show? Does it have email?
> On Jul 5, 2016, at 12:22, Arnaud Héritier <aherit...@gmail.com> wrote:
> 
> 
> 
> On Tue, Jul 5, 2016 at 9:57 AM, Kanstantsin Shautsou 
> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>> wrote:
> Most of devs doesn't read this maillist, write directly to latest committers 
> to get response.
> 
> :( But there is no email in David's profile (which I understand)
> 
> I don't know how our community could improve the management of the 
> communication but it is painful :(
> 
> @david I hope you are the right one in copy. I found your email in Jira.
> If you have some feedbacks about my questions below
> 
> Thanks a lot
> 
> cheers
> 
> 
> 
> On Tuesday, July 5, 2016 at 10:45:57 AM UTC+3, Arnaud Héritier wrote:
> ping ? no feedback ?
> 
> On Mon, Jun 27, 2016 at 10:07 AM, Arnaud Héritier <aher...@gmail.com <>> 
> wrote:
> Hi GitHub pull request builder plugin owners
> 
>   I don't really know the reason but you have 2 issues trackers, the official 
> JIRA component [1] and the GitHub issues tracker [2]. I don't know where to 
> report issues. Can you help me ?
> 
>   Also it seems that the changelog isn't updated in Confluence [3] and in 
> GitHub [4]. Latest version is 1.32.6 and I don't find anything documented 
> after 1.30.2
> 
>   Do we have to read github commits to see what was changed or do I miss 
> something ?
> 
> Thanks a  lot
> 
> 1 : 
> http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide=true=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27ghprb-plugin%27
>  
> <http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide=true=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27ghprb-plugin%27>
> 2 : https://github.com/jenkinsci/ghprb-plugin/issues 
> <https://github.com/jenkinsci/ghprb-plugin/issues>
> 3 : 
> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin
>  
> <https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin>
> 4 : https://github.com/jenkinsci/ghprb-plugin/blob/master/README.md 
> <https://github.com/jenkinsci/ghprb-plugin/blob/master/README.md>
> 
> 
> 
> --
> -
> Arnaud Héritier
> http://aheritier.net <http://aheritier.net/>
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
> 
> 
> 
> --
> -
> Arnaud Héritier
> http://aheritier.net <http://aheritier.net/>
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
> 
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/c7be01b7-85a2-40fd-bfc1-8d8bb6715010%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/c7be01b7-85a2-40fd-bfc1-8d8bb6715010%40googlegroups.com?utm_medium=email_source=footer>.
> 
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> 
> 
> --
> -
> Arnaud Héritier
> http://aheritier.net <http://aheritier.net/>
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
> 
> --
> 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/zpdxOxNCwRw/unsubscribe 
> <https://groups.google.com/d/topic/jenkinsci-dev/zpdxOxNCwRw/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU--WjbaNVdwst94h7CGHbPB1DcS8%2BBV%3DHTfmLnrjaC9DNQ%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU--WjbaNVdwst94h7CGHbPB1DcS8%2BBV%3DHTfmLnrjaC9DNQ%40mail.gmail.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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/9E01C6C5-E36C-4487-BB74-B4704991F8A6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: GitHub pull request builder plugin changelog and issues

[Kanstantsin Shautsou]

Most of devs doesn't read this maillist, write directly to latest 
committers to get response.  

On Tuesday, July 5, 2016 at 10:45:57 AM UTC+3, Arnaud Héritier wrote:
>
> ping ? no feedback ?
>
> On Mon, Jun 27, 2016 at 10:07 AM, Arnaud Héritier  > wrote:
>
>> Hi GitHub pull request builder plugin owners
>>
>>   I don't really know the reason but you have 2 issues trackers, the 
>> official JIRA component [1] and the GitHub issues tracker [2]. I don't know 
>> where to report issues. Can you help me ?
>>
>>   Also it seems that the changelog isn't updated in Confluence [3] and in 
>> GitHub [4]. Latest version is 1.32.6 and I don't find anything documented 
>> after 1.30.2
>>
>>   Do we have to read github commits to see what was changed or do I miss 
>> something ?
>>
>> Thanks a  lot
>>
>> 1 : 
>> http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide=true=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27ghprb-plugin%27
>> 2 : https://github.com/jenkinsci/ghprb-plugin/issues
>> 3 : 
>> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin
>> 4 : https://github.com/jenkinsci/ghprb-plugin/blob/master/README.md
>>
>>   
>>
>> -- 
>> -
>> Arnaud Héritier
>> http://aheritier.net
>> Mail/GTalk: aheritier AT gmail DOT com
>> Twitter/Skype : aheritier
>>
>
>
>
> -- 
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>

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

Re: [Jenkins World 2016 ] Get 20% OFF

[Kanstantsin Shautsou]

Sorry, but that's smells like a spam.

On Friday, July 1, 2016 at 10:34:17 PM UTC+3, alytong13 wrote:
>
> [image: Inline image 1]
>
> *Go ALL IN and join us at Jenkins World 2016 
> , September 13 - 15, 
> 2016.* 
>
> Hello,
>
> Today is the last day to take advantage of early bird discount price, 
> $399. This discounted price will be *ending tonight (Friday, July 1) at 
> 11:59pm PDT.* 
>
> Starting today, you can get 20% off your registration, just use code: JWATONG 
> during registration 
> 
> .
>
> Not sure why you should attend?
>
>- 
>
>50+ sessions  from organizations 
>such as: Electronic Arts, FINRA, GerritForge, Google, NPR, Riot Games, 
>Shutterfly, Splunk and Verizon.
>- 
>
>Keynotes from Kohsuke Kawaguchi, Sacha Labourey and Gary Gruver.
>- 
>
>Free Jenkins and CloudBees Jenkins Platform certification exams 
>.
>- Network with the LARGEST gathering of Jenkins users in the world.
>
> See you in September!
>
> 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/066975a4-4706-42a1-ab80-d4af29499a63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins plugins to push tags to git repo after successful builds

[Kanstantsin Shautsou]

If you are keeping credentials in GIT Scm configuration you should use git 
publisher.
If not then you can create a trick with anybuildstep-plugin and do pushes 
from shell execution.

On Thursday, June 30, 2016 at 4:21:05 PM UTC+3, piyush joshi wrote:
>
> Hi,
>
> Is there any Jenkins plugins to push a tag to a git repo after successful 
> build creation as a post build step.
>
> Thanks 
> Piyush Joshi
> Phone No - 8859902165
>

-- 
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/51787c2f-c5d9-4dac-b101-a25208c88fb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

@jenkins_release twitter account dead?

[Kanstantsin Shautsou]

While i'm waiting statistics update decided to retweet newly released 
plugin version and... 
https://twitter.com/jenkins_release account dead? The last tweet is from 16 
Apr.

-- 
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/8fd0722d-e0c0-42c0-8b74-a1b1dc1531fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: sec-170: What need plugins to do to declare vars they provide?

[Kanstantsin Shautsou]

> On May 13, 2016, at 01:33, Jesse Glick  wrote:
> 
> Just set variables according to a `Cause` or similar.
> 
> --
> 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/YNLEDaGUsgg/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/CANfRfr3jBSXM%2BEN7QQnKUjbPxFcjFm%2BMQ%3DQiiabok9KJzh9a9A%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
Where? EnvironmentContributor? It participates in spaghetti routines of 
variable resolvers that full of infinite bugs for different types of jobs. It 
wrong architecture for providing things that must be in first place (triggered 
values and cause) instead of doing additional resolution calls and duplicating 
everything else.
Where is trusted field in StringParameter or any other objects then?

-- 
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/A3E547EE-AEBC-4A15-BDEA-4142E001914D%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: sec-170: What need plugins to do to declare vars they provide?

[Kanstantsin Shautsou]

EnvironmentContributor is the worst thing for trigger plugins imho. Trigger 
plugins injecting known and safe named variables, they should never be 
filtered out from job variables. 
Hiding vars for already setuped envs sounds like a disaster.

On Thursday, May 12, 2016 at 5:54:26 PM UTC+3, Daniel Beck wrote:
>
>
> > On 12.05.2016, at 16:47, Robert Sandell  > wrote: 
> > 
> > But at the same time I need to get a fix out for my users. 
>
> I fear that early implementations to handle this new restriction will be 
> heavily copy/pasted. So even if you intend to switch to a different 
> approach as soon as you consider it viable, other plugins may not, 
> perpetuating this hackish approach. 
>
>

-- 
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/12838f54-8c52-4bc8-95c2-916c9f011bd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Statistics generation disappeared?

[Kanstantsin Shautsou]

Hi, stats is missing statistics for previous month. I also can't find the 
job that generates it. Any ideas?

-- 
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/7ce9ae9b-63ec-4136-ad0f-55f2281bf5a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins cloud health reporting

[Kanstantsin Shautsou]

@ogondza you can try to look 
at https://github.com/KostyaSha/yet-another-docker-plugin where i 
clean-uped most of the code that i started working on in docker-plugin. Not 
ideal of course but i un-hardcoded and clean-uped as much as i can. All 
other plugins copy-pasting code without understanding how it works (my 
impression after reading a lot of cloud plugins).
PS feel free to contact about stats if you need some experiments.

On Wednesday, April 27, 2016 at 4:59:35 PM UTC+3, Stephen Connolly wrote:
>
> So you should not be checking that the slave is launched by running 
> through computer.connect(false) as that requires that you return early. 
> Instead you should be checking for e.g. the ssh service to be open and 
> responding to connection requests (you can do that easily with your 
> launcher... but a custom check would be better as you only want to check 
> that the port is open) then you return and let Jenkins add the node and 
> connect. The critical bug is 
> https://github.com/jenkinsci/jclouds-plugin/blob/master/jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsCloud.java#L297
>  
> i.e. you should *never* add the node to jenkins yourself, when you do 
> that you cause the second issue that you are then trying to correct.
>
> In short the future should return the Node instance to be added *when* the 
> actual Node instance is ready to connect. If you return the Node too soon, 
> then you get over-provisioning... which then leads to people trying to 
> "fix" that by copying the hacks in the EC2 plugin.
>
> The cloud API is a mess. I want to replace it with something that a sane 
> individual has a hope of implementing correctly.
>
> Do not fear, after dealing with the cloud API for many years now I have 
> come to the conclusion that it is IMPOSSIBLE to write a correct 
> implementation. The closest thing to a correct implementation is the 
> oc-cloud implementation used by CJOC (and that only avoids the bugs that 
> you cannot avoid because we can linearize operations in CJOC). 
>
> Our nectar-vmware plugin is "ok" (largely due to a shake-down we did when 
> we were using it for the predecessor to CJOC)
>
> The next closest to a correct implementation is Docker.
>
> After that... well it's all mostly sh1t... I loose the will to live when I 
> start looking at other implementations.
>
> If you pick EC2 as your template you will be following every wrong example 
> in the book.
>
> On 27 April 2016 at 13:54, Oliver Gondža  
> wrote:
>
>> On 04/27/2016 02:08 PM, Stephen Connolly wrote:
>>
>>>
>>> On 8 April 2016 at 14:44, Oliver Gondža >> > wrote:
>>>
>>> Some plugins even wait for launch to complete before leaving
>>> PlannedNode#future
>>>
>>>
>>> Those are broken plugins
>>>
>>
>> As a maintainer of one such plugin I would like to hear your input on [1] 
>> is it seems to be quite common. With regards to the cloud-stats plugin, it 
>> would not change much even if they all get fixed since launch can be 
>> started by Jenkins before it collects completed futures, it just makes it 
>> happen all the time instead of rarely.
>>
>> [1] 
>> https://github.com/jenkinsci/jclouds-plugin/blob/master/jclouds-plugin/src/main/java/jenkins/plugins/jclouds/compute/JCloudsCloud.java#L299-L303
>>
>> -- 
>> oliver
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/418b92f5-e0ca-c85b-ecf2-bc4d5a184422%40gmail.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/f2e5eff3-b59a-4ea1-abd8-90656f0a772f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Scheduled maintenance window April 15th - April 17th

[Kanstantsin Shautsou]

So you started migration on Friday? ;-))

On Monday, April 18, 2016 at 7:18:47 AM UTC+3, R Tyler Croy wrote:
>
> (replies inline) 
>
> On Fri, 15 Apr 2016, R. Tyler Croy wrote: 
>
> > Howdy folks, starting today I am migrating services from various hosts 
> this 
> > weekend. The services that are primarily going to be affected are: 
> > 
> >  * ci.jenkins-ci.org 
> >  * mirrors.jenkins-ci.org 
> >  * LDAP 
>
>
>
> With a *lot* of effort between Kohsuke and myself (with some help from 
> nibalizer, danielbeck and bwalding) we've migrated a few key services. 
> Most 
> notably ldap which is online at its new home. Our mirror infrastructure is 
> also 
> migrated and I will be performing the final cut-over in the morning. 
>
>
> Unfortunately we've run out of weekend time for the migration of 
> ci.jenkins-ci.org, which is going to expand into Monday. Aside from 
> builds 
> not running, this means that update center generation is on-hold until the 
> new 
> hosts are properly online. 
>
>
> I apologize for the inconvenience and trust that I'm working as fast as my 
> fingers and machine I/O will let me to get the service migration finished. 
>
>
> Cheers 
> - 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/5bd63707-ed0b-46bd-a9f1-e8e2c8369a23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [2.0] slipping date

[Kanstantsin Shautsou]

Check dmesg, for OOM killer
> On Apr 8, 2016, at 14:20, Antonio Muñiz <amu...@cloudbees.com> wrote:
> 
> One of the forked booters finished, the other one is blocked in a test. Any 
> idea?
> 
> "Executing 
> retainMasterLabelWhenNoSlaveDefined(jenkins.model.MasterBuildConfigurationTest)"
>  prio=10 tid=0x7f47f4007800 nid=0x3384 in Object.wait() 
> [0x7f47fbe88000]
>java.lang.Thread.State: WAITING (on object monitor)
>   at java.lang.Object.wait(Native Method)
>   - waiting on <0xc664a970> (a jenkins.model.Jenkins$8)
>   at java.lang.Object.wait(Object.java:503)
>   at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:267)
>   - locked <0xc664a970> (a jenkins.model.Jenkins$8)
>   at jenkins.InitReactorRunner.run(InitReactorRunner.java:44)
>   at jenkins.model.Jenkins.executeReactor(Jenkins.java:1020)
>   at jenkins.model.Jenkins.(Jenkins.java:864)
>   at hudson.model.Hudson.(Hudson.java:85)
>   at org.jvnet.hudson.test.JenkinsRule.newHudson(JenkinsRule.java:571)
>   at org.jvnet.hudson.test.JenkinsRule.before(JenkinsRule.java:358)
>   at org.jvnet.hudson.test.JenkinsRule$2.evaluate(JenkinsRule.java:516)
>   at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 
> On Fri, Apr 8, 2016 at 1:17 PM, Kanstantsin Shautsou 
> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>> wrote:
> 
>> On Apr 8, 2016, at 13:21, Antonio Muñiz <amu...@cloudbees.com 
>> <mailto:amu...@cloudbees.com>> wrote:
>> 
>> On Fri, Apr 8, 2016 at 11:55 AM, Kanstantsin Shautsou
>> <kanstantsin@gmail.com <mailto:kanstantsin@gmail.com>> wrote:
>>> check what you did with pom and threading in pom/test plugins.
>> 
>> Nothing was done, just -Xmx1g (which is not required IMO).
>> 
>> I think celery is not being able to manage the load and that's the
>> root cause of OOM errors. Arnaud just checked that the physical memory
>> was completely full some minutes ago (so 2.0 builds are getting OOM
>> even before hitting their 1GB limit).
>> 
>> I guess the number of concurrent builds increased in the last months?
>> 
>> If the problem persists, this would need to be reopen/merged to give
>> us some light: https://github.com/jenkinsci/jenkins/pull/2220 
>> <https://github.com/jenkinsci/jenkins/pull/2220>
> Your local runs wouldn’t reproduce anything because you have different 
> hardware.
> Check threading/forking in maven test plugins (surefire/failsafe).
>> 
>> --
>> Antonio Muñiz
>> Software Engineer
>> CloudBees, Inc.
>> 
>> --
>> 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/f4iUVX7w_PE/unsubscribe 
>> <https://groups.google.com/d/topic/jenkinsci-dev/f4iUVX7w_PE/unsubscribe>.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-dev+unsubscr...@googlegroups.com 
>> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRuBo8rgr7o1i0ko0vaD8YhA3g3txOj2ySbLqeYCyuysQ%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRuBo8rgr7o1i0ko0vaD8YhA3g3txOj2ySbLqeYCyuysQ%40mail.gmail.com>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/B1984CD6-146D-4D84-B794-B47E1093C5CB%40gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/B1984CD6-146D-4D84-B794-B47E1093C5CB%40gmail.com?utm_medium=email_source=footer>.
> 
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> 
> 
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.
> 
> --
> 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/f4iUVX7w_PE/unsubscribe 
> <ht

Re: [2.0] slipping date

[Kanstantsin Shautsou]

> On Apr 8, 2016, at 13:21, Antonio Muñiz <amu...@cloudbees.com> wrote:
> 
> On Fri, Apr 8, 2016 at 11:55 AM, Kanstantsin Shautsou
> <kanstantsin@gmail.com> wrote:
>> check what you did with pom and threading in pom/test plugins.
> 
> Nothing was done, just -Xmx1g (which is not required IMO).
> 
> I think celery is not being able to manage the load and that's the
> root cause of OOM errors. Arnaud just checked that the physical memory
> was completely full some minutes ago (so 2.0 builds are getting OOM
> even before hitting their 1GB limit).
> 
> I guess the number of concurrent builds increased in the last months?
> 
> If the problem persists, this would need to be reopen/merged to give
> us some light: https://github.com/jenkinsci/jenkins/pull/2220 
> <https://github.com/jenkinsci/jenkins/pull/2220>
Your local runs wouldn’t reproduce anything because you have different hardware.
Check threading/forking in maven test plugins (surefire/failsafe).
> 
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.
> 
> --
> 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/f4iUVX7w_PE/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/CAJc7kzRuBo8rgr7o1i0ko0vaD8YhA3g3txOj2ySbLqeYCyuysQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

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


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [2.0] slipping date

[Kanstantsin Shautsou]

Limit threading in build and check what you did with pom and threading in 
pom/test plugins.
> On Apr 8, 2016, at 11:59, Antonio Muñiz  wrote:
> 
> On Fri, Apr 8, 2016 at 10:32 AM, Arnaud Héritier  wrote:
>> Java 7 is the oldest version we are supporting for now it must run with it
>> :(
> 
> 
> `7` is set anyways. So building with JDK 8
> should be fine.
> BTW the test suite ran successfully in my local box - max memory
> consumption during tests: 500MB - (JDK 8, Maven 3.3.3)
> 
> But before changing anything, could someone check that `celery` node
> is ok? Last time Daniel checked there were a lot of zombie processes
> eating the memory (which leaded to OOM errors in new builds).
> 
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.
> 
> --
> 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/f4iUVX7w_PE/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/CAJc7kzQmaq1AA_CF7EL89K009gTXVQ52p8D5W1XXwOj6kYxgVg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8D9D26AD-D27E-48F2-9E1C-24A21DFE1E50%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Pipeline View Plugin

[Kanstantsin Shautsou]

I think README can answer on your question 
https://github.com/jenkinsci/pipeline-view-plugin/blob/master/README.md#jucies 

> On Apr 8, 2016, at 01:39, Michael Neale  wrote:
> 
> Sergei - this hasn't been published to any repo that I can see (and the wiki 
> doesn't show it up 
> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+View+Plugin) - is this 
> deliberate or a mistake? (I don't see any commits to do with release 
> preparing).
> 
> On Tuesday, March 29, 2016 at 10:51:21 AM UTC+11, Michael Neale wrote:
> this would be quite interesting, I think this all belongs in the stage view, 
> somehow. Having powerful APIs is useful for future visualisations as well.
> 
> Currently the stage view is more about stages (hence the name) so some 
> ability to reduce the "noise" of steps is required (I can imagine some folk 
> in a stage view may indeed want to see steps executing, not just a whole 
> stage).
> 
> 
> 
> 
> --
> 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/YZAHSXYCfDY/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/d46c322c-a897-43c7-b0ab-d3cc24d08eb6%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/1D96E2B1-BECE-4089-A3FB-2BDAD1695116%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [2.0] slipping date

[Kanstantsin Shautsou]

So, everybody would have 1.x without fixes for 2 months and 2.x that would 
be unstable? 

On Tuesday, March 29, 2016 at 3:54:36 AM UTC+3, Kohsuke Kawaguchi wrote:
>
> (For dev list...)
>
> This impacts the branching & 1.x release freeze plan 
>  
> announced by Daniel earlier, too.
>
>- April 3: 1.656 release, which will be the last 1.x release
>- April 6: RC.
>master will be merged into 2.0. Ideally we're not going to merge crazy 
>stuff into 'master' between now and next Wednesday to keep the risk of the 
>2.0 RC being terrible low. Any unmerged pull requests against '2.0' 
>will be closed, and '2.0' will be merged into 'master'. This means that 
>from that point on, anything happening on the 'master' branch will be 
>released as 2.1, as it makes no sense to continue releasing 1.x weeklies 
>while 2.0 code is frozen and we're preparing the release.
>- April 10: weekly release will be skipped
>- Apirl 17: weekly release will be skipped
>- April 20: 2.0 GA
>- April 26: More coordinated launch marketing activities commence
>- May 1:  2.1 and weekly release resumes
>
>
> Also, we agreed that "Major" and above fixes are only allowed until March 
> 30, "Critical" and above are allowed only until RC, and only "Blocker" past 
> that point, so that we do march toward the conversion and prevent the extra 
> time from getting used on random fixes that end up destabilzing.
>
> Thanks for focusing the effort around 2.0, especially those of you who are 
> working on fixes that are targeted for 2.0. Others, please continue to kick 
> the tire and report problems you find!
>
>
> 2016-03-28 17:45 GMT-07:00 Kohsuke Kawaguchi  >:
>
>> In today's 2.0 status check call, Daniel Beck as 2.0 release manager had 
>> raised that we still have too many issues in flight 
>>  and 
>> it's unrealistic to expect that we can fix them all in RC. So we decided to 
>> add one more week till RC.
>>
>> Then we realized that this is exactly the same thing that happened with 
>> beta. So it looks like it'd be a reasonable estimate that RC to release is 
>> going to need 2 weeks, too. That way we don't have to make a fool of 
>> ourselves by slipping it once again two weeks from now.
>>
>> That brings the updated time line to ...
>>
>>- April 6: Create first release candidate (RC)
>>- April 20: Create 2.0 proper release with last RC
>>- April 26: More coordinated launch marketing activities commence
>>
>> For the up-to-date information, please check the 2.0 Wiki page 
>> . My apologies 
>> for any inconvenience this may cause to anyone.
>>
>> -- 
>> Kohsuke Kawaguchi
>>
>
>
>
> -- 
> Kohsuke Kawaguchi
>

-- 
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/6ffecd61-b143-4bf6-82ab-01399d81e1d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: EOFException on slave disconnect

[Kanstantsin Shautsou]

> On Mar 22, 2016, at 19:20, Jesse Glick <jgl...@cloudbees.com> wrote:
> 
> On Sun, Mar 20, 2016 at 12:01 PM, Kanstantsin Shautsou
> <kanstantsin@gmail.com> wrote:
>> AFAIR it only warning and you could ignore it.
> 
> Yes, I think it is a bug in Remoting, probably not your fault.
> 
> --
> 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/tTJG_6eiWPg/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/CANfRfr0DfZGzHuRBo38qv_eG8cKabWWC84aN_VfN8wnK60og-A%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
I see difference traces when dealing with cloud. I.e. ServletException class 
not found for some magic getShel call. Sometimes i think async monitors causing 
traces because slave closed and deleted and some async work is in progress. 
Maybe Stephen C. knows where is architecture issue in all this async/sync work.

-- 
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/2395E2FF-0D4B-4410-9126-8C685C5E467B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Pipeline View Plugin

[Kanstantsin Shautsou]

Let’s try host you under jenkinsci and you will decide later whether it works 
for you.
I will handle :)
> On Mar 22, 2016, at 16:42, Sergei Egorov  wrote:
> 
> For me, it's too early but if you think that it's fine to include it under 
> jenkinsci in the current state then I don't mind. Yet I want to control 
> development of it for now and keep pull request model for it, I hope you 
> understand :)
> 
> Sergei
> 
> On Tue, Mar 22, 2016 at 3:40 PM Oleg Nenashev  > wrote:
> Why don't you just move it to jenkinsci org?
> The plugin is definitely useful, so I think it is reasonable.
> 
> P.S: I'm still planning to run the plugin against big pipelines. I'm just in 
> the slowpoke mode :(
> 
> BR, Oleg
> 
> вторник, 22 марта 2016 г., 14:07:39 UTC+1 пользователь Sergei Egorov написал:
> FYI I configured CircleCI for this plugin, so now it's possible to download 
> the latest *.hpi automated build from there:
> 
> i.e. Build #7:
> https://circleci.com/gh/bsideup/jenkins-pipeline-view/7#artifacts 
> 
> 
> On Tue, Mar 22, 2016 at 8:59 AM Michael Neale > wrote:
> In another case it looks like Execution, yes... never mind (should be easy to 
> fix once identified). I think the jackson stuff just happened to pick that 
> edge case up (I thought I saw a serialization problem and my brain suddenly 
> turned off looking for null pointers! hahaha.
> 
> Nice work!
> 
> 
> On Tuesday, March 22, 2016 at 5:49:49 PM UTC+11, Sergei Egorov wrote:
> Actually... getStartNode marked with @Nonnull, as well as getExecution(), so 
> one of them is null. Execution maybe?
> 
> On Tue, Mar 22, 2016 at 8:17 AM Sergei Egorov > wrote:
> Hi Michael,
> 
> Wow, interesting finding!
> 
> I checked with the sources and looks like it's not an issue of the plugin 
> itself, but StepEndNode. Jackson in plugin configured to serialize only 
> pre-configured fields/methods, and any new object in the domain will not 
> affect it.
> 
> What I see here is that StepEndNode::getTypeDisplayName throws an NPE. From 
> StepEndNode's source code, I see that there are no checks for getStartNode() 
> result, and for some reason it's null. This is a good place to start if you 
> want to figure out what's wrong in your setup (even better if you can put 
> conditional breakpoint on getTypeDisplayName and "getStartNode() == null", 
> because I see (in code) that it might be null, but getTypeDisplayName is not 
> null-safe.
> 
> On Tue, Mar 22, 2016 at 8:00 AM Michael Neale > wrote:
> As luck would have it, I notice this is tripped by by having global lib 
> variables added in (basically, DSLs). Is there a JIRA project for this?
> 
> (not a huge thing, I can't imagine many would run into this, but it looks 
> like it gets upset if not all the things are serializable).
> 
> Caused by: com.fasterxml.jackson.databind.JsonMappingException: (was 
> java.lang.NullPointerException) (through reference chain: 
> org.jenkinsci.plugins.workflow.cps.nodes.StepEndNode["typeDisplayName"])
> 
> at 
> com.fasterxml.jackson.databind.ser.DefaultSerializerProvider.serializeValue(DefaultSerializerProvider.java:141)
> 
> at 
> com.fasterxml.jackson.databind.ObjectMapper._configAndWriteValue(ObjectMapper.java:3559)
> 
> at 
> com.fasterxml.jackson.databind.ObjectMapper.writeValue(ObjectMapper.java:2909)
> 
> at 
> com.github.bsideup.jenkins.pipeline.ui.view.PipelineViewApi.doNodes(PipelineViewApi.java:75)
> 
> ... 89 more
> 
> Caused by: java.lang.IllegalArgumentException: (was 
> java.lang.NullPointerException) (through reference chain: 
> org.jenkinsci.plugins.workflow.cps.nodes.StepEndNode["typeDisplayName"])
> 
> at 
> com.fasterxml.jackson.databind.ObjectMapper._convert(ObjectMapper.java:3459)
> 
> at 
> com.fasterxml.jackson.databind.ObjectMapper.convertValue(ObjectMapper.java:3378)
> 
> at 
> com.github.bsideup.jenkins.pipeline.ui.view.PipelineViewApi$2.apply(PipelineViewApi.java:78)
> 
> at 
> com.github.bsideup.jenkins.pipeline.ui.view.PipelineViewApi$2.apply(PipelineViewApi.java:75)
> 
> at com.google.common.collect.Iterators$8.next(Iterators.java:812)
> 
> at 
> com.fasterxml.jackson.databind.ser.std.IterableSerializer.serializeContents(IterableSerializer.java:89)
> 
> at 
> com.fasterxml.jackson.databind.ser.std.IterableSerializer.serialize(IterableSerializer.java:74)
> 
> at 
> com.fasterxml.jackson.databind.ser.std.IterableSerializer.serialize(IterableSerializer.java:12)
> 
> at 
> com.fasterxml.jackson.databind.ser.DefaultSerializerProvider.serializeValue(DefaultSerializerProvider.java:130)
> 
> ... 92 more
> 
> 
> On Tuesday, March 22, 2016 at 10:49:54 AM UTC+11, Michael Neale wrote:
> Very cool, and I like the use of react!
> 
> On Monday, March 21, 2016 at 5:52:04 PM UTC+11, Sergei Egorov wrote:
> Hey everyone,
> 
> Yesterday I decided to publish sources for my 

Re: Pipeline View Plugin

[Kanstantsin Shautsou]

Cool work!

-- 
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/131022c9-3ea6-4683-9877-f34ab00277a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: EOFException on slave disconnect

[Kanstantsin Shautsou]

AFAIR it only warning and you could ignore it.

On Saturday, March 19, 2016 at 1:29:51 AM UTC+3, Ivo wrote:
>
> Hi,
>
> I'm creating a cloud plugin and keep running into the following stacktrace 
> on slave disconnect/termination:
>
> WARNING: Computer.threadPoolForRemoting [#8] for 18392a20986e8 terminated
> java.io.EOFException
> at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.
> java:613)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.
> java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at hudson.remoting.SingleLaneExecutorService$1.run(
> SingleLaneExecutorService.java:112)
> at jenkins.util.ContextResettingExecutorService$1.run(
> ContextResettingExecutorService.java:28)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.
> java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> I can not figure out why this is happening. I'm 
> calling Jenkins.getInstance().removeNode in my _terminate method. Is there 
> anything else I need to explicitly close/disconnect? The slave is 
> automatically connected through jnlp.
>
> Hopefully someone is able to help me out with this. I can provide 
> additional code details if necessary.
>
> Regards,
> Ivo
>

-- 
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/e3b98041-c0e1-4b5e-b858-115a03639818%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin Hosting Request: Violation Comments to GitHub

[Kanstantsin Shautsou]

On Friday, March 11, 2016 at 10:00:29 AM UTC+3, Tomas Bjerre wrote:
>
> Parsing report files produced by static code analysis is something that is 
> valuable also outside Jenkins community. That is why I think it should be 
> implemented in a library and released to Maven Central, not only Jenkins 
> Maven repos. And so I have done (
> https://github.com/tomasbjerre/violations-lib). I have the same argument 
> for commenting (https://github.com/tomasbjerre/violation-comments-lib) 
> and commenting GitHub (
> https://github.com/tomasbjerre/violation-comments-to-github-lib).
>
> This enables me to easily create Gradle and Maven plugins for this. Which 
> means I can also do this in Travis or any other build server.
>
And that is already implemented in 
http://docs.sonarqube.org/display/PLUG/GitHub+Plugin  

-- 
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/62fc442e-0520-473d-8e9e-bca99750df50%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin Hosting Request: Violation Comments to GitHub

[Kanstantsin Shautsou]

That what i implemented 1 year ago in 
https://github.com/jenkinsci/github-integration-plugin via email-ext 
templating. Templating described in email-ext plugin.

On Saturday, March 5, 2016 at 12:52:16 PM UTC+3, Tomas Bjerre wrote:
>
> Plugin Name: Violation Comments To GitHub
> My GitHub username: tomasbjerre
> Existing repo: 
> https://github.com/tomasbjerre/violation-comments-to-github-jenkins-plugin
> Doc: 
> https://github.com/tomasbjerre/violation-comments-to-github-jenkins-plugin
>
> This plugin will find report files from static code analysis and comment 
> GitHub pull requests with the content. Here 
>  is a live demo of 
> what it may look like on GitHub.
>

-- 
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/a5334ca7-a664-4bcc-a8df-c6a447f3fb6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: One-Shot Executors

[Kanstantsin Shautsou]

> On Mar 9, 2016, at 19:52, Suckow, Thomas J  wrote:
> 
> I like that this moves the provisioning to the build log.
> 
> I do agree that certain issues should fail immediately (image not found). 
> Certain other issues should perform exponential backoff (Cloud infrastructure 
> down). Provisioning limits could be annoying though, would be interesting if 
> they could be left in the queue until Jenkins side provisioning limits are 
> not violated. I am not sure how to handle an environment like Kubernetes 
> though where other entities may be utilizing resources and you have to 
> "share".
> 
> You mention using labels to pick the slave. I'm wondering if it would be 
> feasible and worthwhile to make such a plugin generic to be the middle layer 
> for the Jenkins hooks to the cloud specific implementation (Docker, 
> Kubernetes, AWS).
> 
> It could also handle the logic of some users wanting to configure slaves on a 
> per job basis. Would be interesting if could also be integrated into 
> cloudbees folder level. If the later could work then I wouldn't need to run 
> my own Jenkins install at work for using containers and instead could use the 
> company cloudbees Jenkins.
I guess folder has some FolderProperty that you cat get from job.getParent(), 
that’s all.
> 
> -
> Thomas
> 
> From:  > on behalf of nicolas de loof 
> >
> Reply-To: "jenkinsci-dev@googlegroups.com 
> "  >
> Date: Friday, March 4, 2016 at 3:08 AM
> To: "jenkinsci-dev@googlegroups.com " 
> >
> Subject: One-Shot Executors
> 
> Hi folks,
> 
> Yoann and I have extracted from our docker-slaves hack-ish pet project a 
> stable sub-component so a plugin can manage slaves that are dedicated to a 
> Build, not relying on Cloud API, and get them tied to a Build. i.e Slave and 
> Build share a common lifecycle. If Slave fails to start, Build will fail as 
> well. If slave is slow to start (maybe pulling a huge docker image), build 
> log will report the progress.
> etc.
> 
> design and use-case : 
> https://wiki.jenkins-ci.org/display/JENKINS/One-Shot+Executor 
> 
> code : https://github.com/jenkinsci/one-shot-executor-plugin 
> 
> 
> the current code base do rely on hacks, our goal is to demonstrate this use 
> case (can be tested reusing sample 
> )
>  so we can get the adequate hooks introduced in jenkins-core and later 
> re-implement same API on a cleaner basis.
> 
> 
> 
> 
> --
> 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/CANMVJznmnydODNX%2BYXmh0ujnJXsoZWcPT%2BpJCWwdR0_wUpfDTQ%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/WV6sPmIh-tk/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/D305926F.28292%25thomas.suckow%40pnnl.gov
>  
> .
> 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/32573B19-5EC2-47CA-9246-73AD90D53484%40gmail.com.
For 

Re: Proposal: forbid direct commits to master for core

[Kanstantsin Shautsou]

On Wednesday, March 9, 2016 at 12:45:40 AM UTC+3, Stephen Connolly wrote:
>
> On 8 March 2016 at 20:39, Daniel Beck  
> wrote:
>
>>
>> On 08.03.2016, at 21:29, Stephen Connolly > > wrote:
>>
>> > 2. Request review
>> > 3. Wait
>> > 4. If PR is no-longer mergable, or needs fix-up due to other PRs 
>> merged, Then fix up PR and Goto 2
>>
>> FWIW I would not consider most fix ups cause to go back to #2 if there 
>> have been positive reviews of the original version.
>>
>
> So you are saying that somebody making fix-ups won't make mistakes and the 
> changes do not need re-review?
>
> It's hard enough in the current process to know at what point you have the 
> OK to merge... 
>
I think it depends on contributors quality, somebody may request final 
review, somebody may merge. But that definitely better than invisible 
commits to master.


@Stephenc, when you are watching `jenskinci/jenkins` repository, are you 
getting notifications for all commits? I think no. 

How do you expect people reviewing/knowing about code changes without PRs? 

(Even if your change was right.) Do you think that your change is super 
important and everybody should be ignored? Or that’s personal kohsuke’s 
project that allows doing anything he want without caring on cooperation 
with other contributors that made a lot of 
https://github.com/jenkinsci/jenkins/graphs/contributors and testing?


This wasn't an automation or release process commit. It wasn't so difficult 
to make PR and keep discussions in PR thread that will have comments in it 
and not in commit. PR would allow ensure that build at all buildable.


I think the first small step should be to use PRs as gate of changes and 
degree of review could be adopted later.

>  
>
>>
>> --
>> 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/1F7F3EB2-706E-4E38-837A-903D126442D0%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/1eea0a94-bd31-43bf-8090-67586c3a9e45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: forbid direct commits to master for core

[Kanstantsin Shautsou]

Keeping just for logging of this topic to save future time during searching 
examples 
https://github.com/jenkinsci/jenkins/commit/bb7c8fcedbcc9b51c5b1bb5b32810af5ac6b1ffb
 

-- 
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/851cc3bd-5d6b-46db-acc9-d1f04874ae8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jelly Repeatable produces Javascript error

[Kanstantsin Shautsou]

Ah right! I also had issues with embedding one forms into other forms.
Note, JobProperty shouldn’t be available for all jobs by default, so you would 
need some tricks (you may search for existing plugins) or require to some 
latest core where Jesse implemented OptionalJobProperty that doesn’t render 
body by default.

> On Mar 5, 2016, at 19:05, 'konrad' via Jenkins Developers 
>  wrote:
> 
> Okay, I have the solution. You can't use f:entry inside a f:repeatable. If 
> you do it, that will destroy the generated HTML and jenkins repeatable.js 
> (line 112) can't find the div with class 'repeatable-insertion-point' as it 
> is outside of 'repeated-container' div.
> 
> Kanstantsin, how can I access my JobProperty instance from the config.jelly?
> 
> This is my property class:
> 
> public class MyJobProperty extends JobProperty
> {
> private boolean isMyProject;
> 
> public String getTest()
> {
> return "test";
> }
> 
> @Extension
> public static class DescriptorImpl extends JobPropertyDescriptor
> {
> @Override
> public JobProperty newInstance(StaplerRequest req, JSONObject 
> formData) throws FormException
> {
> return super.newInstance(req, formData);
> }
> 
> @Override
> public String getDisplayName()
> {
> return "...";
> }
> 
> public String getTest()
> {
> return "ttest";
> }
> }
> }
> 
> In my config.jelly I know I can do a ${descriptor.test} and I get "ttest". 
> But I would like to do something like ${jobProperty.test}.
> 
> --
> 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/NBRtnkAfDbU/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/fd19b6c7-c7b1-4e23-bdde-843a7ed52849%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/1C3D76A0-0C50-4379-952D-799A7C4F6CD1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: One-Shot Executors

[Kanstantsin Shautsou]

Ok, offtopic should die, i sent email to board, i will get explanations and 
description from board.

For cloud faster provisioning stephenc replied that will look at possible 
ways on Monday.

-- 
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/6b5e0b9b-76d2-42ec-af52-3fd746af98d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: One-Shot Executors

[Kanstantsin Shautsou]

Was it you? I still answering in PRs and issues. @magnayan is also not actively 
maintaining it, would you also remove it? If it was you (the person that never 
worked on this plugin) then i would be glad to see the list of plugins what you 
maintain and ensure that you also removed from all unrelated teams. Would it be 
fair? Either i would request descriptions to the Jenkins Board.

> On Mar 5, 2016, at 18:33, nicolas de loof <nicolas.del...@gmail.com> wrote:
> 
> *you* just said you aren't working anymore on this plugin. So why complain ?
> 
> 2016-03-05 16:31 GMT+01:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
> <mailto:kanstantsin@gmail.com>>:
> `You've been removed from the Jenkins team docker-plugin Developers`
> Thanks to anonymous person, removing person from team would be a great 
> benefit to this plugin! ;)
> That a bit offtop, please continue with the initial topic.
> 
> 
> On Saturday, March 5, 2016 at 11:47:09 AM UTC+3, Kanstantsin Shautsou wrote:
> 
>> On Mar 5, 2016, at 11:15, nicolas de loof <nicolas.del...@gmail.com 
>> <mailto:nicolas.del...@gmail.com>> wrote:
>> 
>> 
>> 
>> 2016-03-05 7:36 GMT+01:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>> <mailto:kanstantsin@gmail.com>>:
>> I made my plugin after @stephenc comments and seems that his work somebody 
>> finally tried to expose 
>> https://github.com/jenkinsci/mansion-cloud-plugin/pull/9 
>> <https://github.com/jenkinsci/mansion-cloud-plugin/pull/9> According to 
>> stephenc comments such logic should be generic and would make sense for all 
>> cloud plugins, that’s why i made separate plugin.
>> 
>> @batmat if you are using docker-plugin then it may have synchronisation or 
>> logic issues.
>> 
>> @KostyaSha is this something you're trying to address with you 
>> "yet-another-docker-plugin" ? Are you working on both plugins ?
> I’m not maintaining docker-plugin anymore (reasons described in readme). I 
> had good experience with migrating static ssh slaves to docker-plugin, but it 
> had not enough stability.  In yad-plugin i just continue the work and want 
> get stable and faster provisioning for standard Cloud slaves (for integration 
> tests invented remote run and configuration of master instance and started 
> working on jmeter plugin for doing performance tests). Delays mostly not a 
> cloud plugin issue, so experimental “faster” i placed in separate plugin. In 
> yad-plugin and docker-java library i almost resolved all related issues and 
> hope it will work good, stable and covered with ITs.
> For future I have some experimental ideas for DSLs, but they may duplicate 
> existing features with the difference that i will use docker-java. Even if 
> nobody will use it, i would have reference implementation for docker-java 
> where i’m co-maintainer. For example it should be possible to expose globally 
> configured docker connection into JobProperty configuration (that of course 
> will use QTD for hacks), but that would raise questions about limits and 
> security. Everything depends on free time and mood :)
> 
> yad-plugin -  is released into UC (it my experiment to host it under personal 
> account).
> faster-node-provision-plugin 
> <https://github.com/KostyaSha/faster-node-provision-plugin> - isn’t released 
> as i had no final conclusion on it’s stability (maybe it would require to 
> substitute the whole provisioning strategy). If stephenc will finally review 
> and bless then it would make sense to fork and release it.
> 
>> 
>>> On Mar 5, 2016, at 01:50, Baptiste Mathus <m...@batmat.net 
>>> <mailto:m...@batmat.net>> wrote:
>>> 
>>> 
>>> 2016-03-04 21:14 GMT+01:00 Kanstantsin Shautsou <kanstantsin@gmail.com 
>>> <mailto:kanstantsin@gmail.com>>:
>>> Cloud delays in theory should be possible to avoid by:
>>> 1) kicking suggestReview. I wrote plugin but had no ability to test on huge 
>>> installations https://github.com/KostyaSha/faster-node-provision-plugin 
>>> <https://github.com/KostyaSha/faster-node-provision-plugin>
>>> 2) increasing one of coefficients for provisioner(or statistics collector, 
>>> forgot classname) (jglick is using it in demo's and i'm using in my 
>>> installations).
>>> 
>>> NodeProvisionner?
>>> 
>>> Btw, that page might be related IIUC what you talk about. There're many 
>>> seemingly (didn't test yet) useful infos about those coeffs and what they 
>>> do:
>>> https://cloudbees.zendesk.com/hc/en-us/articles/204690520-Why-do-slaves-show-as-suspended-while-jo

Re: One-Shot Executors

[Kanstantsin Shautsou]

`You've been removed from the Jenkins team docker-plugin Developers`
Thanks to anonymous person, removing person from team would be a great 
benefit to this plugin! ;)
That a bit offtop, please continue with the initial topic. 

On Saturday, March 5, 2016 at 11:47:09 AM UTC+3, Kanstantsin Shautsou wrote:
>
>
> On Mar 5, 2016, at 11:15, nicolas de loof <nicolas.del...@gmail.com> 
> wrote:
>
>
>
> 2016-03-05 7:36 GMT+01:00 Kanstantsin Shautsou <kanstantsin@gmail.com>
> :
>
>> I made my plugin after @stephenc comments and seems that his work 
>> somebody finally tried to expose 
>> https://github.com/jenkinsci/mansion-cloud-plugin/pull/9 According to 
>> stephenc comments such logic should be generic and would make sense for all 
>> cloud plugins, that’s why i made separate plugin.
>>
>> @batmat if you are using docker-plugin then it may have synchronisation 
>> or logic issues. 
>>
>
> @KostyaSha is this something you're trying to address with you 
> "yet-another-docker-plugin" ? Are you working on both plugins ?
>
> I’m not maintaining docker-plugin anymore (reasons described in readme). I 
> had good experience with migrating static ssh slaves to docker-plugin, but 
> it had not enough stability.  In yad-plugin i just continue the work and 
> want get stable and faster provisioning for standard Cloud slaves (for 
> integration tests invented remote run and configuration of master instance 
> and started working on jmeter plugin for doing performance tests). Delays 
> mostly not a cloud plugin issue, so experimental “faster” i placed in 
> separate plugin. In yad-plugin and docker-java library i almost resolved 
> all related issues and hope it will work good, stable and covered with ITs.
> For future I have some experimental ideas for DSLs, but they may duplicate 
> existing features with the difference that i will use docker-java. Even if 
> nobody will use it, i would have reference implementation for docker-java 
> where i’m co-maintainer. For example it should be possible to expose 
> globally configured docker connection into JobProperty configuration (that 
> of course will use QTD for hacks), but that would raise questions about 
> limits and security. Everything depends on free time and mood :)
>
> yad-plugin -  is released into UC (it my experiment to host it under 
> personal account).
> faster-node-provision-plugin 
> <https://github.com/KostyaSha/faster-node-provision-plugin> - isn’t 
> released as i had no final conclusion on it’s stability (maybe it would 
> require to substitute the whole provisioning strategy). If stephenc will 
> finally review and bless then it would make sense to fork and release it.
>
>  
>
>> On Mar 5, 2016, at 01:50, Baptiste Mathus <m...@batmat.net> wrote:
>>
>>
>> 2016-03-04 21:14 GMT+01:00 Kanstantsin Shautsou <
>> kanstantsin@gmail.com>:
>>
>>> Cloud delays in theory should be possible to avoid by:
>>> 1) kicking suggestReview. I wrote plugin but had no ability to test on 
>>> huge installations 
>>> https://github.com/KostyaSha/faster-node-provision-plugin
>>> 2) increasing one of coefficients for provisioner(or statistics 
>>> collector, forgot classname) (jglick is using it in demo's and i'm using in 
>>> my installations).
>>>
>>
>> NodeProvisionner?
>>
>> Btw, that page might be related IIUC what you talk about. There're many 
>> seemingly (didn't test yet) useful infos about those coeffs and what they 
>> do:
>>
>> https://cloudbees.zendesk.com/hc/en-us/articles/204690520-Why-do-slaves-show-as-suspended-while-jobs-wait-in-the-queue-
>>
>> Btw, IIUC, this page might explain why I'm seeing my slave/agent docker 
>> containers being provisionned in between 5 seconds and roughly 6 minutes...
>>
>>
>>> AFAIK the main jenkins pain is the Queue locks. How this plugin will 
>>> deal with locks? 
>>>
>>>
>>>>>> 2016-03-04 12:08 GMT+01:00 nicolas de loof <nicolas...@gmail.com>:
>>>>>>
>>>>>>> Hi folks,
>>>>>>>
>>>>>>> Yoann and I have extracted from our docker-slaves hack-ish pet 
>>>>>>> project a stable sub-component so a plugin can manage slaves that are 
>>>>>>> dedicated to a Build, not relying on Cloud API, and get them tied to a 
>>>>>>> Build. i.e Slave and Build share a common lifecycle. If Slave fails to 
>>>>>>> start, Build will fail as well. If slave is slow to start (maybe 
>>>>>>> pulling a 
>>>&

Re: Jelly Repeatable produces Javascript error

[Kanstantsin Shautsou]

Well, if you do something custom then you need to place stapler-bag or 
stapler-class. Would keep this magic description to somebody else :)

> On Mar 5, 2016, at 17:14, 'konrad' via Jenkins Developers 
> <jenkinsci-dev@googlegroups.com> wrote:
> 
> It neither works with 1.580.3. Do you have any other idea where the issue 
> could be? Did I forget something in the jelly file?
> 
> I always do a mvn clean, thats developer cargo cult isn't it :D
> 
> Am Samstag, 5. März 2016 15:07:29 UTC+1 schrieb Kanstantsin Shautsou:
> Did you make `mnv clean` after switching to new version?
> If it wouldn’t work, then issue is somewhere else.
> 
>> On Mar 5, 2016, at 17:05, Kanstantsin Shautsou <kanstan...@gmail.com 
>> > wrote:
>> 
>> Try 1.580.3 firstly, some versions had bug but i don’t exactly remember what.
>> 
>>> On Mar 5, 2016, at 16:23, 'konrad' via Jenkins Developers 
>>> <jenkin...@googlegroups.com > wrote:
>>> 
>>> Thanks for your answer. I am using 1.580.1 :D I'll try 625
>>> 
>>> Am Freitag, 4. März 2016 21:23:14 UTC+1 schrieb Kanstantsin Shautsou:
>>> What core version do you use? 1.609.X? It broken, try 1.625.3 at least.
>>> 
>>> On Friday, March 4, 2016 at 10:21:12 PM UTC+3, konrad wrote:
>>> I am trying to use a repeatable inside a config.jelly of my jenkins plugin:
>>> 
>>> 
>>> >> xmlns:l="/lib/layout">
>>>  
>>>
>>>  
>>>  
>>>>> noAddButton="true" minimum="0">
>>>  
>>>
>>>  
>>>
>>>  
>>>  
>>>  
>>>  
>>> 
>>> 
>>> This produces the following javascript error:
>>> Uncaught TypeError: Cannot read property 'hasClassName' of undefined
>>> (anonymous function) @ repeatable.js:112
>>> (anonymous function) @ behavior.js:111
>>> (anonymous function) @ behavior.js:107
>>> Behaviour.applySubtree @ behavior.js:93
>>> Behaviour.apply @ behavior.js:76
>>> (anonymous function) @ behavior.js:71
>>> window.onload @ behavior.js:125
>>> window.onload @ behavior.js:125
>>> 
>>> 
>>> 
>>> 
>>> The failing codeine is in repeatable.js line 112. It tries to find a div 
>>> with  class 'repeatable-insertion-point'.
>>> // do the ones that extract innerHTML so that they can get their original 
>>> HTML before
>>> // other behavior rules change them (like YUI buttons.)
>>> Behaviour.specify("DIV.repeated-container", 'repeatable', -100, function(e) 
>>> {
>>> if(isInsideRemovable(e))return;
>>> 
>>> // compute the insertion point
>>> var ip = $(e.lastChild);
>>> while (!ip.hasClassName("repeatable-insertion-point"))
>>> ip = ip.previous();
>>> // set up the logic
>>> object(repeatableSupport).init(e, e.firstChild, ip);
>>> });
>>> 
>>> What am I doing wrong?
>>> 
>>> 
>>> --
>>> 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/NBRtnkAfDbU/unsubscribe 
>>> <https://groups.google.com/d/topic/jenkinsci-dev/NBRtnkAfDbU/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/34db963b-1304-4e1c-8890-5dfd9b916e0f%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/34db963b-1304-4e1c-8890-5dfd9b916e0f%40googlegroups.com?utm_medium=email_source=footer>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>.
>> 
> 
> 
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/NBRtnkAfDbU/unsubscribe 
> <https://groups.google.com/d/topic/jenkinsci-dev/NBRtnkAfDbU/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/afdd40bf-815a-44e5-8ad3-2ab18181abbe%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/afdd40bf-815a-44e5-8ad3-2ab18181abbe%40googlegroups.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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/6A69B9D1-E166-43CD-A16D-CA12EF795C38%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Jelly Repeatable produces Javascript error

[Kanstantsin Shautsou]

Did you make `mnv clean` after switching to new version?
If it wouldn’t work, then issue is somewhere else.

> On Mar 5, 2016, at 17:05, Kanstantsin Shautsou <kanstantsin@gmail.com> 
> wrote:
> 
> Try 1.580.3 firstly, some versions had bug but i don’t exactly remember what.
> 
>> On Mar 5, 2016, at 16:23, 'konrad' via Jenkins Developers 
>> <jenkinsci-dev@googlegroups.com <mailto:jenkinsci-dev@googlegroups.com>> 
>> wrote:
>> 
>> Thanks for your answer. I am using 1.580.1 :D I'll try 625
>> 
>> Am Freitag, 4. März 2016 21:23:14 UTC+1 schrieb Kanstantsin Shautsou:
>> What core version do you use? 1.609.X? It broken, try 1.625.3 at least.
>> 
>> On Friday, March 4, 2016 at 10:21:12 PM UTC+3, konrad wrote:
>> I am trying to use a repeatable inside a config.jelly of my jenkins plugin:
>> 
>> 
>> > xmlns:l="/lib/layout">
>>  
>>
>>  
>>  
>>> noAddButton="true" minimum="0">
>>  
>>
>>  
>>
>>  
>>  
>>  
>>  
>> 
>> 
>> This produces the following javascript error:
>> Uncaught TypeError: Cannot read property 'hasClassName' of undefined
>> (anonymous function) @ repeatable.js:112
>> (anonymous function) @ behavior.js:111
>> (anonymous function) @ behavior.js:107
>> Behaviour.applySubtree @ behavior.js:93
>> Behaviour.apply @ behavior.js:76
>> (anonymous function) @ behavior.js:71
>> window.onload @ behavior.js:125
>> window.onload @ behavior.js:125
>> 
>> 
>> 
>> 
>> The failing codeine is in repeatable.js line 112. It tries to find a div 
>> with  class 'repeatable-insertion-point'.
>> // do the ones that extract innerHTML so that they can get their original 
>> HTML before
>> // other behavior rules change them (like YUI buttons.)
>> Behaviour.specify("DIV.repeated-container", 'repeatable', -100, function(e) {
>> if(isInsideRemovable(e))return;
>> 
>> // compute the insertion point
>> var ip = $(e.lastChild);
>> while (!ip.hasClassName("repeatable-insertion-point"))
>> ip = ip.previous();
>> // set up the logic
>> object(repeatableSupport).init(e, e.firstChild, ip);
>> });
>> 
>> What am I doing wrong?
>> 
>> 
>> --
>> 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/NBRtnkAfDbU/unsubscribe 
>> <https://groups.google.com/d/topic/jenkinsci-dev/NBRtnkAfDbU/unsubscribe>.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-dev+unsubscr...@googlegroups.com 
>> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/34db963b-1304-4e1c-8890-5dfd9b916e0f%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/34db963b-1304-4e1c-8890-5dfd9b916e0f%40googlegroups.com?utm_medium=email_source=footer>.
>> For more options, visit https://groups.google.com/d/optout 
>> <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/4125F400-CB3D-414D-88B3-DEDEAB629143%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: Jelly Repeatable produces Javascript error

[Kanstantsin Shautsou]

Try 1.580.3 firstly, some versions had bug but i don’t exactly remember what.

> On Mar 5, 2016, at 16:23, 'konrad' via Jenkins Developers 
> <jenkinsci-dev@googlegroups.com> wrote:
> 
> Thanks for your answer. I am using 1.580.1 :D I'll try 625
> 
> Am Freitag, 4. März 2016 21:23:14 UTC+1 schrieb Kanstantsin Shautsou:
> What core version do you use? 1.609.X? It broken, try 1.625.3 at least.
> 
> On Friday, March 4, 2016 at 10:21:12 PM UTC+3, konrad wrote:
> I am trying to use a repeatable inside a config.jelly of my jenkins plugin:
> 
> 
>  xmlns:l="/lib/layout">
>  
>
>  
>  
> noAddButton="true" minimum="0">
>  
>
>  
>
>  
>  
>  
>  
> 
> 
> This produces the following javascript error:
> Uncaught TypeError: Cannot read property 'hasClassName' of undefined
> (anonymous function) @ repeatable.js:112
> (anonymous function) @ behavior.js:111
> (anonymous function) @ behavior.js:107
> Behaviour.applySubtree @ behavior.js:93
> Behaviour.apply @ behavior.js:76
> (anonymous function) @ behavior.js:71
> window.onload @ behavior.js:125
> window.onload @ behavior.js:125
> 
> 
> 
> 
> The failing codeine is in repeatable.js line 112. It tries to find a div with 
>  class 'repeatable-insertion-point'.
> // do the ones that extract innerHTML so that they can get their original 
> HTML before
> // other behavior rules change them (like YUI buttons.)
> Behaviour.specify("DIV.repeated-container", 'repeatable', -100, function(e) {
> if(isInsideRemovable(e))return;
> 
> // compute the insertion point
> var ip = $(e.lastChild);
> while (!ip.hasClassName("repeatable-insertion-point"))
> ip = ip.previous();
> // set up the logic
> object(repeatableSupport).init(e, e.firstChild, ip);
> });
> 
> What am I doing wrong?
> 
> 
> --
> 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/NBRtnkAfDbU/unsubscribe 
> <https://groups.google.com/d/topic/jenkinsci-dev/NBRtnkAfDbU/unsubscribe>.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/34db963b-1304-4e1c-8890-5dfd9b916e0f%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/34db963b-1304-4e1c-8890-5dfd9b916e0f%40googlegroups.com?utm_medium=email_source=footer>.
> For more options, visit https://groups.google.com/d/optout 
> <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/4B6311EB-1A6B-4F82-B00A-A1FF55E98862%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail