Re: [GSOC 2018] Student Introduction (Discard Build Step plugin)

[Jay Shresth]

Hi Oleg,

Sorry for the typo error in my email proposal. By that statement, I was 
meant that I'll always be able to communicate with Jenkins developers 
during implementation phase. I have amended the same statement in my 
proposal document and uploaded the updated one for your reference.

https://docs.google.com/document/d/1Cq7CNTkpuMcMU4oPGprrevUk8EnPR6ZWUgjhg1qiZ3c/edit?usp=sharing

Should there be any other doubt, query or suggestion for me, please let me 
know.

With Regards,

Jay

On Tuesday, 27 March 2018 10:49:30 UTC+5:30, Oleg Nenashev wrote:
>
> It is view-only, so I cannot comment in the proposal. Would it be possible 
> to adjust permissions?
>
> I also wonder about the "I have always been able to effectively 
> communicate with Jenkins project developers prior and during GSoC 
> application period." statement in the proposal.
> I do not see any communications between you and the Jenkins community 
> before March 24, this year. I checked mailing lists, JIRA and GitHub. If I 
> miss something, could you please provide links?
>
> Thanks in advance,
> Oleg
>
>
> On Tue, Mar 27, 2018 at 5:54 AM, Jay Shresth  > wrote:
>
>>  
>>
>>>  Hi Martin,

>>>
>> Please find attached proposal link for your reference:
>>
>> https://docs.google.com/document/d/1Cq7CNTkpuMcMU4oPGprrevUk8EnPR6ZWUgjhg1qiZ3c/edit?usp=sharing
>>
>> Any feedback on proposal will be highly appreciated.
>>
>> Have a good day!
>>
>> With Regards,
>>
>> Jay
>>
>> -- 
>> 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/3tfk2F7D0mA/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/53c8e050-7594-4924-a2bc-b55a53b45231%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/f3b3fc48-b707-4358-a923-0bee60ed9caf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: alpha version of Jenkins Configuration as Code plugin available

[Oleg Nenashev]

Hi Harsh,

It would be great if you allow comments in the proposal

Thanks in advance,
Oleg

On Tuesday, March 27, 2018 at 7:06:29 AM UTC+2, Harsh Bajaj wrote:
>
> Hi Ewelina
> I have written  a proposal for GSocC 2018.
> I know it's not that great but please offer your feedback I will 
> appreciate that.I am very entusiatic about getting involved with 
> configuration as code plugin
>
>
>
> https://docs.google.com/document/d/1JwApTLHUf1bWjxP4rcIYUzNJ7uOT6-9hiU0YcfneiYY/edit?usp=sharing
>
>
> Please let me know how I can impove How can learn more about this product 
> and work better to start working on it.
>
> Thanks and Regards
>
>
> On Monday, February 26, 2018 at 10:00:00 AM UTC-6, Ewelina Wilkosz wrote:
>>
>> Last Friday we've released 0.1-alpha of Jenkins Configuration as Code 
>>  plugin. Use 
>> carefully, number of key features still missing but we're getting there!
>>
>

-- 
You received this message because you are 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/cc248259-c2cd-42df-9239-5367e325f852%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2018] Student Introduction (Discard Build Step plugin)

[Oleg Nenashev]

It is view-only, so I cannot comment in the proposal. Would it be possible
to adjust permissions?

I also wonder about the "I have always been able to effectively communicate
with Jenkins project developers prior and during GSoC application period."
statement in the proposal.
I do not see any communications between you and the Jenkins community
before March 24, this year. I checked mailing lists, JIRA and GitHub. If I
miss something, could you please provide links?

Thanks in advance,
Oleg


On Tue, Mar 27, 2018 at 5:54 AM, Jay Shresth 
wrote:

>
>
>>  Hi Martin,
>>>
>>
> Please find attached proposal link for your reference:
> https://docs.google.com/document/d/1Cq7CNTkpuMcMU4oPGprrevUk8EnPR
> 6ZWUgjhg1qiZ3c/edit?usp=sharing
>
> Any feedback on proposal will be highly appreciated.
>
> Have a good day!
>
> With Regards,
>
> Jay
>
> --
> 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/3tfk2F7D0mA/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/53c8e050-7594-4924-a2bc-b55a53b45231%
> 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/CAPfivLAjwVWeegmH4w-JLd7gqmqF_1PHR38j9KwhAdw34Q_J1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: alpha version of Jenkins Configuration as Code plugin available

[Harsh Bajaj]

Hi Ewelina
I have written  a proposal for GSocC 2018.
I know it's not that great but please offer your feedback I will appreciate 
that.I am very entusiatic about getting involved with configuration as code 
plugin


https://docs.google.com/document/d/1JwApTLHUf1bWjxP4rcIYUzNJ7uOT6-9hiU0YcfneiYY/edit?usp=sharing


Please let me know how I can impove How can learn more about this product 
and work better to start working on it.

Thanks and Regards


On Monday, February 26, 2018 at 10:00:00 AM UTC-6, Ewelina Wilkosz wrote:
>
> Last Friday we've released 0.1-alpha of Jenkins Configuration as Code 
>  plugin. Use 
> carefully, number of key features still missing but we're getting there!
>

-- 
You received this message because you are 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/52534841-dd79-4453-b376-79c21be50c51%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2018] Student Introduction (Discard Build Step plugin)

[Jay Shresth]

 

>  Hi Martin,
>>
>
Please find attached proposal link for your reference:
https://docs.google.com/document/d/1Cq7CNTkpuMcMU4oPGprrevUk8EnPR6ZWUgjhg1qiZ3c/edit?usp=sharing

Any feedback on proposal will be highly appreciated.

Have a good day!

With Regards,

Jay

-- 
You received this message because you are 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/53c8e050-7594-4924-a2bc-b55a53b45231%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC] Jenkins Configuration as Code

[harsh]

Hi,
Thanks for that.I am aware of that.I have prepared a proposal and I will be
submitting to your organization.Please consider me .

Regards

Harsh Bajaj

On Mon, Mar 26, 2018, 6:13 AM Oleg Nenashev  wrote:

> Hi Harsh,
>
> Just FYI, Mar 27 16:00 PM UTC is a deadline for proposals.
> If you are still interested in the project, please make sure to submit
> your final proposal by this time.
>
> We will also have the last Q office hours
>  today at 18:00PM UTC.
> Feel free to join if you have any questions.
>
> Best regards,
> Oleg Nenashev
>
> On Wednesday, February 28, 2018 at 6:21:40 PM UTC+1, Harsh Bajaj wrote:
>>
>> Alright thanks
>
> --
> 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/mxtSgk6csUs/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/6208839e-c26b-494a-bdb8-63984d72efeb%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Remoting work dir configuration of JNLP Launcher

[Glenn Burkhardt]

So, how do we get a copy of the libvirt plugin compiled against the current 
Jenkins core code?  It looks like the libvirt plugin was compiled against 
jenkins-core-1.625.3.jar, and the JNLPLauncher class didn't contain a 
"RemotingWorkDirSettings workDirSettings" field at that time.  It might be 
that simply re-compiling against a more current version of core Jenkins 
code will fix it.

I've been trying to do that, but I'm new to Maven, and it's not clear to me 
yet how to force the build to use a more current Jenkins release.

Thanks!

On Saturday, March 24, 2018 at 9:42:57 AM UTC-4, Oleg Nenashev wrote:
>
> The ticket has been created to a wrong component, so it has never been 
> triaged. I will the components.
> From what I see the Libvirt plugin inherits standard Agent's UI, so the 
> new Jenkins core tries to generate JNLP with workDir.
>
> Also, how does one debug a jelly script like "slave-agent.jnlp.jelly"?  I 
>> can't find it anywhere in my deployed Jenkins system.
>>
>
> Please see 
> https://wiki.jenkins.io/display/JENKINS/Figuring+out+URL+binding+of+Stapler
>  
>
> On Friday, March 23, 2018 at 6:46:03 PM UTC+1, Glenn Burkhardt wrote:
>>
>> Jenkins ver. 2.108 , Libvirt Slaves plugin 1.8.5 
>>
>> I'm trying to get a slave windows client running in a VM under 'libvirt' 
>> to start properly.  I've identified the problem to be the same as described 
>> in https://issues.jenkins-ci.org/browse/JENKINS-47834.
>> The problem is that the "slave-agent.jnlp" generated by Jenkins omits the 
>> argument for "-workDir" and "-remoteDir".
>>
>> I've been trying to understand how the "slave-agent.jnlp.jelly" script 
>> generates the file, and I suspect that the script and the Libvirt plugin 
>> are out of sync.  In particular, there's a reference in the script to 
>> "launcher.workDirSettings.workDirPath".  But the VirtualMachineLauncher 
>> class defined in the plugin doesn't contain a 'workDirSettings' field.  
>> The delegate does, and the debugger indicates that it's a JNLPLauncher 
>> class.  
>>
>> I see a line in the script that says:
>>
>> 
>>
>> Does that somehow get mapped to the delegate field in 
>> the VirtualMachineSlaveComputer class, which is what the 'it' argument 
>> passed to EncryptedSlaveAgentJnlpFile turns out to be.
>>
>> Also, how does one debug a jelly script like "slave-agent.jnlp.jelly"?  I 
>> can't find it anywhere in my deployed Jenkins system.
>>
>> 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/6391013d-1a45-4d5e-b884-034b1fca8a2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: JEP: Modification of "Accepted" JEPs

[Liam Newman]

Andrew,

That's an interesting point as well. The process is still relatively new,
so it's not surprising that there's a learning curve and a need for more
examples. JEPs with tighter focus will definitely move through the process
more quickly, since they will require less discussion, design-time,
implementation time, and consensus building.   JEP-200 was a good example
of that tight focus and it still took some time.

One way that Tyler has been addressing the scope considerations in relation
the Jenkins Essentials is splitting the overall project into multiple
JEPs.  JEP-300 covers the overall goals and high-level design, and
delegates the internal design of those components to sub-JEPs that are
being filed as work gets rolling.   I don't know if that means JEP-300 will
be accepted sooner or will remain as draft, but it looks like that will be
the case.

It would be nice to have more JEPs filed to for a base of examples we can
point people to, but I suspect we'll have to wait for that to grow
organically over time.

-L.


On Sat, Mar 24, 2018 at 7:48 AM Andrew Bayer  wrote:

> I think it’s more a cultural thing re comfortableness of followup JEPs -
> we need to have precedents and examples so that people will feel like oh,
> it’s ok that this stuff didn’t get into that JEP, we can just do a new JEP
> with it. Leaving proposals open for too long in order to make sure every
> possible tangentially related matter gets in is a path to stagnation. We’re
> far better off with more JEPs of potentially smaller size/scope,
> potentially amending earlier JEPs, than a small number of bloated ones, IMO.
>
> A.
>
> On Sat, Mar 24, 2018 at 9:34 AM Liam Newman  wrote:
>
>> This is a ton of great feedback, thanks!
>>
>> Ewelina,
>>
>> JEPs have a number of purposes, but they are definitely _not_ meant to
>> stifle innovation.  At minimum though, they are meant to provide a medium
>> for building consensus on the design and implementation of major
>> features/processes of the Jenkins (and related) project.
>>
>> Without JEP, contributors such as yourself, might do months of work only
>> to have that work rejected or asked to be redesigned.  From the other side,
>> the Project might get random contributors who ride in and want to have drop
>> in some massive features without having discussed and reviewed with the
>> rest of the project.
>>
>> I think the main misunderstanding (due to lack of clarity in JEP-1) is
>> the idea that a JEP must be "Accepted" in order for contributors to have
>> confidence in the value and validity of their work. That is absolutely not
>> the case.
>>
>> "Accepted" means that that Reviewer and Sponsor have looked at the JEP
>> and agreed that _scoping and design_ are complete and have the consensus of
>> the community, and that what remains is completing the (already well
>> underway) implementation.  "Accepted" is a description of the technical
>> state of the proposed component/feature/process.  "Accepted" is _not_ (and
>> should not be viewed or used as) a "vote of confidence".
>>
>> Conversely, "Draft" is not a commentary on the likelihood that the JEP
>> will eventually be "Accepted".  That can only determined by the Sponsors
>> and the Reviewers based on discussion and feedback on the mailing list or
>> other forums. "Draft" is _not_ (and should not be viewed as) an indicator
>> of any lack of confidence in a proposal.
>>
>> > Now when I see a requirement
>> *> "all 'significant changes' to a JEP should be completed before it is
>> Accepted"*
>> > it makes me worry that if I end up working on next JEP, for another
>> project,
>> > I will be very careful and it will take ages to put it into "Accepted"
>> (maybe it's
>> > not a problem). And then, like with JCasC, we learn while we implement
>> it,
>> > we discover issues and things that we can't do the way we want to do.
>> > Do we have to discover all of that before "Accepting" JEP?
>>
>> In short, yes, but as you might gather from my response above, that is
>> not a bad thing.
>>
>> In the case of JEP-201, there has been no commentary it indicate that it
>> lacks support, nor any doubt about the value of the work being done.  I
>> think that the lack of clarity about the meaning of "Accepted" extends to
>> the reviewers, so JEP-201 was marked as "Accepted" before the design was
>> sufficiently complete.   But I also personally have no doubt that once the
>> design is complete, JEP-201 will be "Accepted".
>>
>> > Maybe it wouldn't be the worst idea to organize a Jenkins Online
>> Meetup around JEP concept?
>>
>> Yes, as noted above, I agree there is still misunderstanding about the
>> JEP process.  I wouldn't have though to have JOM on this, but maybe we
>> should.  It would be good to highlight that this process exists, talk about
>> when and how to use it, and so on.  It would probably have to wait until
>> May (April is looking pretty full already).  In the meanwhile, I still want
>> to 

Re: Taking over maintenance for fitnesse plugin

[Slide]

Michaël,

Please file a PR against
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-fitnesse.yml
adding
your Jenkins username to the list (NOT Github). Be sure to follow the steps
in the PR template and reference this email chain for sign-off purposes.

Regards,

Alex

On Mon, Mar 26, 2018 at 12:27 PM lessonz  wrote:

> I'm happy to give it over, but I do not see where I have privileges to do
> so. I originally took over for similar reasons, but I no longer use
> Fitnesse. I wish you the best of luck.
>
> On Mon, Mar 26, 2018 at 11:44 AM Michaël St-Georges 
> wrote:
>
>> Hi all,
>>
>> The fitnesse plugin seems to be dead. There are a few PRs that are
>> pending for quite some time including some that are required to make the
>> plugin work with the current version of Jenkins.
>>
>> I would like to give a hand by becoming maintainer for this plugin. My
>> github and jenkins infra account is CSLTech.
>>
>> Sincerely,
>> Michaël St-Georges
>>
> --
> You received this message because you are 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/CAAkggDoBS%3D9OQxq-QPXAi2aQYa9aG5mREhQfBLTNqMENk5OsFA%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/CAPiUgVf4JR8%3Dt4eH%3DiaKzmc5g3ffXiqn18FZ%2B1pTBwC33RK3aw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Taking over maintenance for fitnesse plugin

[lessonz]

I'm happy to give it over, but I do not see where I have privileges to do
so. I originally took over for similar reasons, but I no longer use
Fitnesse. I wish you the best of luck.

On Mon, Mar 26, 2018 at 11:44 AM Michaël St-Georges 
wrote:

> Hi all,
>
> The fitnesse plugin seems to be dead. There are a few PRs that are pending
> for quite some time including some that are required to make the plugin
> work with the current version of Jenkins.
>
> I would like to give a hand by becoming maintainer for this plugin. My
> github and jenkins infra account is CSLTech.
>
> Sincerely,
> Michaël St-Georges
>

-- 
You received this message because you are 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/CAAkggDoBS%3D9OQxq-QPXAi2aQYa9aG5mREhQfBLTNqMENk5OsFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC 2018] UPDATE for CODE Coverage API Plugin

[Rajgure Abhishek Sanjay Abhishek Sanjay]

 HI,

i have read all comments and made some improvements to proposal
i would request you to review it
here is the link
https://docs.google.com/document/d/1RJy1t8O5e_ATb7wd8__a83QZg5bjt29kt1MCJp_meKQ/edit?usp=sharing



On Mon, Mar 26, 2018 at 12:20 PM, Rajgure Abhishek Sanjay Abhishek Sanjay <
iit2014...@iiita.ac.in> wrote:

> hi oleg
> sorry for that , i changed it now can you please review it
>
> On Mon, Mar 26, 2018 at 3:48 AM, Oleg Nenashev 
> wrote:
>
>> Now I cannot open it at all. Please use a separate window in private mode
>> to verify permissions.
>>
>> BR, Oleg
>>
>> On Mar 25, 2018 22:54, "Rajgure Abhishek Sanjay Abhishek Sanjay" <
>> iit2014...@iiita.ac.in> wrote:
>>
>>> i have changed it ,can you please review it now
>>>
>>> On Mon, Mar 26, 2018 at 2:03 AM, Oleg Nenashev 
>>> wrote:
>>>
 Hi,

 Thanks for the proposal!
 Your document is view-only, so I cannot review it. Could you please
 allow comments for any user with the link?

 Thanks in advance,
 Oleg

 On Sun, Mar 25, 2018 at 10:04 PM, Rajgure Abhishek Sanjay Abhishek
 Sanjay  wrote:

> please review my proposal
> sorry for late submission
>
> https://docs.google.com/document/d/1RJy1t8O5e_ATb7wd8__a83QZ
> g5bjt29kt1MCJp_meKQ/edit
>
> On Tue, Mar 20, 2018 at 12:12 PM, Oleg Nenashev <
> o.v.nenas...@gmail.com> wrote:
>
>> See https://groups.google.com/forum/#!topic/jenkinsci-dev/-zDJi8swnIE
>>
>> On Monday, March 19, 2018 at 3:14:26 PM UTC+1, Oleg Nenashev wrote:
>>>
>>> I have reached out to the project mentors.
>>> IIUC they are going to setup a meeting to this week, stay tuned.
>>>
>>> BR, Oleg
>>>
>>>
>>> On Mon, Mar 19, 2018 at 3:07 PM, Rajgure Abhishek Sanjay Abhishek
>>> Sanjay  wrote:
>>>
 can you guys suggest me some time slots according to your schedule ,
 i wish you too show my work and discuss about the another possible
 solution for this problem.

 --
 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/RtqsrVk6Aoc/
 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/4e15f968-930
 4-4e47-b9d4-80283e59bf51%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/to
>> pic/jenkinsci-dev/RtqsrVk6Aoc/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/adbd0614-a1f
>> c-4889-8b4b-a84838ae5437%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/to
> pic/jenkinsci-dev/RtqsrVk6Aoc/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/CAPrCTm8XpaX
> 6StS4aR%3DhnMyZK4O9%3DGfnznEb8%3DPY0HkvvqfUSw%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/to
 

Re: [GSOC 2018] Student Introduction (Discard Build Step plugin)

[martinda]

Hi Jay,

Can you please make a draft version of your proposal available in google 
doc and send us the link?

It seems that even mentors do not have access to the final until after the 
deadline which is not convenient but it is what it is.

Thanks,
Martin

On Monday, March 26, 2018 at 1:32:18 AM UTC-4, Jay Shresth wrote:
>
> Thanks Oleg for details. I will contact you soon for any further details.
>
>

-- 
You received this message because you are 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/c2af83a1-d39c-45b0-a8d6-e1579200d710%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2018] EDA Plugin : Developing a Jenkins Plugin for one of the EDA tools viz FuseSOC

[Oleg Nenashev]

OK, thanks for the update!
Good luck with your project.

Best regards,
Oleg Nenashev

On Monday, March 26, 2018 at 4:35:40 PM UTC+2, Lakhan Shiva wrote:
>
> Hi, 
>
> For LibreCores this time, I have chosen to go forward with the FuseSOC 
> provider for Librecores API - The mock API to list all the cores 
> dynamically.
> I have made a proposal, and have got it reviewed. Submitted the same after 
> several edits. 
>
> Cheers,
> Lakhan
>
> On Monday, March 26, 2018 at 4:41:50 PM UTC+5:30, Oleg Nenashev wrote:
>>
>> Hi Lakhan,
>>
>> Just FYI, Mar 27 16:00 PM UTC is a deadline for proposals.
>> If you are still interested in the project, please make sure to submit 
>> your proposal by this time.
>>
>> We will also have the last Q office hours 
>>  today at 18:00PM UTC. 
>> Feel free to join if you have any questions.
>>
>> Best regards,
>> Oleg Nenashev
>>
>> On Saturday, March 17, 2018 at 9:22:54 PM UTC+1, Oleg Nenashev wrote:
>>>
>>> Hi Lakhan,
>>>
>>> Yes, it would be great to extend Jenkins features for OSS EDA tools you 
>>> mentioned. Regarding your query, it would be great to limit the scope of 
>>> the project to few tools to that you could keep focused when you create a 
>>> project proposal draft. Regarding FuseSoC, we also have active project 
>>> maintainers who may be interested to co-mentor the project. All other tools 
>>> in the list are also feasible.
>>>
>>> We are also setting up a GSoC sync-up call between Jenkins and 
>>> LibreCores/FOSSi community members to next week. Currently the slot is TBD, 
>>> please add options possible to you: 
>>> https://doodle.com/poll/w38ne6qekiyfrb9u
>>>
>>> Best regards,
>>> Oleg
>>>
>>> On Saturday, March 17, 2018 at 3:15:18 AM UTC+1, martinda wrote:

 Hi Lakhan,

 Thank you for your interest in the GSoC project on EDA plugin for 
 Jenkins.

 There are many things a Jenkins EDA plugin can do. It can run the EDA 
 tool, but that is rather trivial as anyone can shell out and call the tool 
 from the command line. But what get more interesting is interpreting and 
 reporting the results. Think of what is important when interpreting 
 hardware simulations and synthesis results, what users are interested in 
 knowing (simulation pass/fail criteria, log parsing, resource utilization, 
 timing, etc) and that should provide a lot of material for coding the 
 plugin. It is probably better to have one plugin for each EDA tool.

 Note that we are also in contact with the librecores community 
 regarding this plugin, so you should definitely join that community too (
 https://gitter.im/librecores/Lobby). A good approach would be to use 
 one of their open source projects and build it with the EDA plugin. Lastly 
 we have office hours (https://jenkins.io/projects/gsoc/#office-hours), 
 all students are invited to participate and ask questions.

 Best Regards,
 Martin d'Anjou


 On Friday, March 16, 2018 at 1:04:02 AM UTC-4, Lakhan Shiva wrote:
>
> Hi, 
>
> My name is Lakhan Shiva Kamireddy. I am a second year graduate student 
> at University of Colorado Boulder. I am interested in developing a 
> Jenkins 
> Plugin for one of the EDA tools viz,
> FuseSOC, Yosys, icetools, ArachnePnr, etc. It will help to report 
> FPGA resource utilization per build, etc. 
>
> I am a user of Jenkins CI build platform while i was a backend web 
> application developer for a multinational consulting corporation 
> (Deloitte 
> Consulting).
>
> Last year summer, I was an intern at Google, Sunnyvale office in 
> Califronia,as a Hardware Engineering intern and developed a Formal 
> Verification library (SystemVerilog and Perl)
> which falls under RTL design and Verification domain. I think this 
> would be a great project and would like to come up with a proposal for 
> this. I would like to get as much details as possible 
> for this project and also its potential to get accepted as a GSOC 2018 
> project for Jenkins.
>
> I have pursued some graduate level courses like Logic Synthesis and 
> Optimization, Computer Aided Verification(Formal Verification) at the 
> University of Colorado Boulder in the past years. 
>
> Kindly contact me, to fuel this project as a potential GSOC 2018 
> candidate.
>
> Thanks and Kind Regards, 
> Lakhan Shiva Kamireddy
>


-- 
You received this message because you are 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/f62bf225-bd52-4928-b652-e99a409492a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Taking over maintenance for fitnesse plugin

[Michaël St-Georges]

 Hi all,

The fitnesse plugin seems to be dead. There are a few PRs that are pending
for quite some time including some that are required to make the plugin
work with the current version of Jenkins.

I would like to give a hand by becoming maintainer for this plugin. My
github and jenkins infra account is CSLTech.

Sincerely,
Michaël St-Georges

-- 
You received this message because you are 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/CADX_6P_rRMEGZGRza-pq7DW8fcs77JZSqRLScd5Ti%2BqNwTcJCw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: validating-string-parameter plugin and pipeline compatibility

[Jesse Glick]

On Mon, Mar 26, 2018 at 1:20 PM, Juri Lelli  wrote:
> ideally I would actually like to prevent user hitting "Build" button
> if form validation wasn't OK. Is there a way to perform realtime
> validation (validation is currently performed when the field looses
> focus) and grey out "Build" button if validation didn't succeed?

Not that I am aware.

> I was thinking that ParameterDefinition:createValue()
> might be changed to possibly throw some form of exception
> (AbortException maybe?)

Try throwing `Failure`.

-- 
You received this message because you are 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/CANfRfr2rWhehOfTjfcSOd%2BuP5t3uthAALkZwff_SWVvYuKKH1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

validating-string-parameter plugin and pipeline compatibility

[Juri Lelli]

Hi,

I'm trying to make validating-string-parameter-plugin [1] work with
Jenkins Pipelines.

So far I've managed to get it "working" by throwing a raw
RuntimeException from the @Override buildEnvironment [2]. But this is
far from optimal, as AFAIU buildEnvironment shouldn't be dealing with
parameters valitation at all. The problem with the current version of
the plugin instead is that runtime validation is performed by setUp
method of BuildWrapper(), which doesn't get invoked when using
Pipelines.

So, ideally I would actually like to prevent user hitting "Build" button
if form validation wasn't OK. Is there a way to perform realtime
validation (validation is currently performed when the field looses
focus) and grey out "Build" button if validation didn't succeed?

Alternatively, I was thinking that ParameterDefinition:createValue()
might be changed to possibly throw some form of exception
(AbortException maybe?) if something was wrong at the time user hit
"Build". Of course this would require Jenkins' core mods, would that be
a reasonable and acceptable approach?

Thanks in advance for your help!

Best,

- Juri

[1] https://github.com/jenkinsci/validating-string-parameter-plugin
[2] 
https://github.com/jlelli/validating-string-parameter-plugin/commit/c76ec48b645fb5315c064bf23553e708f671c530#diff-7f2cc2852df243adfa24654a14dc3d5cR94
[3] 
https://github.com/jenkinsci/validating-string-parameter-plugin/blob/master/src/main/java/hudson/plugins/validating_string_parameter/ValidatingStringParameterValue.java#L73

-- 
You received this message because you are 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/20180326172052.GA25184%40localhost.localdomain.
For more options, visit https://groups.google.com/d/optout.

Re: Anything wrong with storing expanded plugin data in var cache?

[Damien Duportal]

Hello,

As a Jenkins User, I've run instances in production or punctually 
(workshops) with the "plugins" directory into a RAMDISK without issues.
When the persistence was required, I use to migrate this to a "machine 
local directory" (generally hypervisor local disk) to avoid having it 
stored on the NFS or the SAN used for Jenkins_home.

@Baptiste, I understand the concern about Evergreen. Obviously a trade-off 
will be in this specific case. Let's say you declare it as a separate 
volume in the initial Docker image, what would be the impact for the end 
user? My point here is to use the Docker "VOLUME" instruction to give a 
good default implementation, but without having to bother the end user: 
Docker ill take care of creating a dedicated data volume for this. It will 
ensure a fairly good default performance (if Docker's data volumes are 
slow, then the plugins directory will be the least of your concern :) ), 
and will work everywhere (Docker will take care of creating the volume at 
initial startup). Also, advanced Docker users would be able to tune it if 
they have specific needs. But it will still be a different VOLUME in the 
Image's metadata, expressing the different persistence properties. What do 
you think?

Le lundi 26 mars 2018 11:19:52 UTC+2, Baptiste Mathus a écrit :
>
> For context, I asked Sam to come and discuss this here after his comment 
> 
>  
> on the JEP about Essentials Evergreen snapshotting system, in the part 
> where we explain how we plan to aggressively segregate data 
> .
>
> So, my take is going to be two-fold:
>
>
>- On Essentials, I think we are free to do more things because we have 
>basically no existing setup. So I'm leaning towards doing this. 
>I'm just slightly worried about:
>- Bad performance (though heavily depending on the storage driver) 
>   writing things in a layer that could grow pretty big outside the 
>   $EVERGREEN_HOME volume. 
>  - At the same time, this would also be a good thing® since by 
>  definition this would be cleaned up if someone starts with a fresh 
> image 
>  version (though it's not *really* the use case of Essentials, as the 
>  content will auto-update)
>  - we could also have a second volume dedicated to writing 
>  caches, but I'm not very keen on doing that since I feel this would 
> go 
>  against the evergreen idea to be very simple to use. And users would 
>  probably have to manage the data written in that second volume 
> instead of a 
>  single one (which I suppose people are more used to see).
>  
>  - For Jenkins packages, I think this would be a good thing to do 
>to, it's just that it's clearly more complex to do since there are 
> existing 
>setups out there. So we'll want to make sure we don't break people 
>instances when upgrading after such a change. 
>
>
>
> 2018-03-24 1:29 GMT+01:00 Sam Gleske :
>
>> I normally store expanded plugin metadata within 
>> /var/cache/jenkins/plugins similar to how WAR filre metadata is stored in 
>> /var/cache/jenkins/war.
>>
>> Is there any particular reason the Jenkins packages don't do this?  Are 
>> there any drawbacks?  I'm curious if others have any opinions on this.
>>
>> I've been running Jenkins quite a while like this.
>>
>> [1]: 
>> https://github.com/samrocketman/jenkins-bootstrap-shared/blob/1a409cad89007f56ed36342427b767dd4e88fbd9/packaging/docker/run.sh.in#L38
>>
>> --
>> You received this message because you are 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/05beb1e5-a824-428c-b980-07a4e343acdc%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/c2e92766-3007-4723-920a-8a9773b3055b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

[Daniel Beck]

> On 26. Mar 2018, at 17:13, R. Tyler Croy  wrote:
> 
> I'm curious why you assume that the security SIG would be broader in scope 
> than
> the present day CERT?

Well, it _could_ be broader in scope. It certainly could be more open. Security 
isn't just finding and fixing vulnerabilities.

Right now, general improvements (like Wadeck's API token PR[1] in core) or 
discussions related to security (perhaps about Jenkins' integrations with 
various auth providers) have no real home. Some of that happens in CERT sort of 
by default, but unless it's about an actual vulnerability, it's not necessary 
to keep it in a closed group only few can participate in. People without 
special permissions can still contribute.

1: https://github.com/jenkinsci/jenkins/pull/3271

-- 
You received this message because you are 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/2061DF32-13B1-4921-B9AD-4E6CE9195BE4%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: [Essentials] RFC: first cut at registration and authentication for Jenkins Essentials

[R. Tyler Croy]

(replies inline)

On Mon, 26 Mar 2018, Jesse Glick wrote:

> Jenkins already includes the `instance-identity` module, which is the
> standard mechanism¹ for both uniquely identifying a Jenkins
> installation, and permitting asymmetrically-encrypted communications
> with it. Is there a reason you are not using it? If so, that should be
> clearly documented under ???Alternative Approaches???. There is a vague
> mention of OpenSSH keys, but this module is not limited to SSH (much
> less OpenSSH), and public-key encryption has widespread library
> support.


Thanks for taking a look Jesse! You're right that Jenkins already does have an
instance identity floating around. In a much earlier iteration of my thinking I 
was
considering using this until I started to think about how this would work in
practice for new installations.

Unfortunately when the jenkins/evergreen image comes online and checks for
updates, it will not have run `jenkins.war` at all yet, and therefore no
instance identity. Rather than have one unprotected/identified route in the
service backend for bootstrapping new nodes, I am erring on the side of
treating all "got updates?" requests the same, which requires a client
registration and identity to kick the process off.

You're absolutely right that the 'Alternative Approaches" section doesn't list
this and should, I'll update shortly.



Cheers
- R. Tyler Croy

--
 Code: 
  Chatter: 
 xmpp: rty...@jabber.org

  % 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/20180326153407.5on7xn7gdl7odfue%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: POTD: Jenkinsfile Runner

[Jesse Glick]

On Sat, Mar 24, 2018 at 12:53 PM,   wrote:
> This might have something to do with this warning, issued right at the start
> of the pipeline.
>
> jenkins.security.ClassFilterImpl#isBlacklisted: rejecting 
> org.codehaus.groovy.runtime.powerassert.PowerAssertionError according to 
> standard blacklist; see https://jenkins.io/redirect/class-filter/

Sounds like JENKINS-41751. Make sure you have updated `workflow-api`
to 2.26. Any other discussion of this should take place in a JIRA
issue with complete steps to reproduce from scratch using a fully
up-to-date installation.

-- 
You received this message because you are 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/CANfRfr0y91PMquYu9CpQ137kOoO_rXJxCsxtCtin6nGsaw1%2B_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

[R. Tyler Croy]

(replies inline)

On Mon, 26 Mar 2018, Daniel Beck wrote:

> 
> > On 22. Mar 2018, at 22:04, R. Tyler Croy  wrote:
> > 
> > I think we already have some groups, which are almost informal SIGs, such as
> > Security, GSoC, Infra, etc. The aspects of SIGs which I really would like to
> > formalize, and support from a community infra standpoint are:
> > 
> >* Clear problem domain/focus area.
> > ???
> > 
> > Some SIGs which I would love to see for starters, would be:
> > 
> > * Security, lead by Daniel
> 
> What's the intended relation between existing teams and SIGs?
> 
> I'm asking mostly about security, which is more narrow in scope that what a 
> potential 'security SIG' would be.
> 
> Would there be a security team with the narrow scope, and a security SIG with 
> much wider scope?


I'm curious why you assume that the security SIG would be broader in scope than
the present day CERT?

Based on the Kubernetes project's descriptions of SIGs, I think cERT is more or
less a SIG already :P



Cheers
- R. Tyler Croy

--
 Code: 
  Chatter: 
 xmpp: rty...@jabber.org

  % 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/20180326151341.gywu5lmjltsxcadf%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: [Essentials] RFC: first cut at registration and authentication for Jenkins Essentials

[Jesse Glick]

Jenkins already includes the `instance-identity` module, which is the
standard mechanism¹ for both uniquely identifying a Jenkins
installation, and permitting asymmetrically-encrypted communications
with it. Is there a reason you are not using it? If so, that should be
clearly documented under “Alternative Approaches”. There is a vague
mention of OpenSSH keys, but this module is not limited to SSH (much
less OpenSSH), and public-key encryption has widespread library
support.


¹ https://wiki.jenkins.io/display/JENKINS/Instance+Identity

-- 
You received this message because you are 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/CANfRfr2RgWBM-2f-Ys6-hONCdiOuyHayf0NhZF7oEMcbpNWHnQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

[Daniel Beck]

> On 22. Mar 2018, at 22:04, R. Tyler Croy  wrote:
> 
> I think we already have some groups, which are almost informal SIGs, such as
> Security, GSoC, Infra, etc. The aspects of SIGs which I really would like to
> formalize, and support from a community infra standpoint are:
> 
>* Clear problem domain/focus area.
> …
> 
> Some SIGs which I would love to see for starters, would be:
> 
> * Security, lead by Daniel

What's the intended relation between existing teams and SIGs?

I'm asking mostly about security, which is more narrow in scope that what a 
potential 'security SIG' would be.

Would there be a security team with the narrow scope, and a security SIG with 
much wider scope?

-- 
You received this message because you are 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/007CA23C-D53A-47FA-869F-8A6E2BC73B9B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Anything wrong with storing expanded plugin data in var cache?

[Samuel Van Oort]

I think it's a genuinely great proposal and it sounds like most of the 
things I'd be concerned about have already been thoroughly considered and 
addressed effectively.  There are two remaining points to consider:

I think it might be desirable to give plugins some mechanism to interact 
with the Gitignore (or an equivalent) -- at least for cases where there's a 
non-standard storage mechanism that needs to be included in the SNAPSHOT 
(or excluded).  Extra flexibility will also help with addressing any 
edge-case issues that might crop up, and enables the project to push some 
of the pain onto plugin maintainers if they're (ab)using the Filesystem in 
non-idomatic (for Jenkins) ways that are hard to support.  I say that in 
the nicest way, hoping that I'm not a guilty party.

Also, I do worry a bit that we might encounter compatibility issues when 
separating the job config from their builds -- probably plugins doing 
something relative to the ITEM directory (which is *wrong*, but could still 
happen).  I know some of our senior Jenkins engineers don't see any issues 
with breaking plugins that are Doing It Wrong (tm), but generally I'd like 
to see some testing across different plugins and a healthy beta period with 
*healthy 
in-the-wild-use *just to ensure positive user experiences.  Relocating 
build records isn't done as often aside from expert installations, and less 
experienced users won't be able to distinguish between "Evergreen broke me" 
and "some random plugin broke because that wasn't respecting the build 
record directory."  Also this burn-in-testing period will help us identify 
and build out the rules for what to include/exclude in snapshots.

Bonuses: I like *a lot* that we're limiting the scope to just 
upgrade/downgrade and not trying to use this as a general-purpose backup.  
It might even be desirable to limit the Git history in some fashion to 
prevent it becoming bloated.  

In general this is a well-considered and valuable addition to the Jenkins 
ecosystem.  Should generally help with performance -- especially if we end 
up splitting into a couple volumes down the road which can be relocated to 
faster/slower performance as needed.

On Monday, March 26, 2018 at 8:49:17 AM UTC-4, Stephen Connolly wrote:
>
> I see nothing wrong with it... but I would say that having added the 
> --pluginroot option myself iirc ;-)
>
> On 24 March 2018 at 00:29, Sam Gleske  
> wrote:
>
>> I normally store expanded plugin metadata within 
>> /var/cache/jenkins/plugins similar to how WAR filre metadata is stored in 
>> /var/cache/jenkins/war.
>>
>> Is there any particular reason the Jenkins packages don't do this?  Are 
>> there any drawbacks?  I'm curious if others have any opinions on this.
>>
>> I've been running Jenkins quite a while like this.
>>
>> [1]: 
>> https://github.com/samrocketman/jenkins-bootstrap-shared/blob/1a409cad89007f56ed36342427b767dd4e88fbd9/packaging/docker/run.sh.in#L38
>>
>> --
>> You received this message because you are 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/05beb1e5-a824-428c-b980-07a4e343acdc%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/1434c647-7743-4cb7-9d18-d1d58beb7e95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2018] EDA Plugin : Developing a Jenkins Plugin for one of the EDA tools viz FuseSOC

[Lakhan Shiva]

Hi, 

For LibreCores this time, I have chosen to go forward with the FuseSOC 
provider for Librecores API - The mock API to list all the cores 
dynamically.
I have made a proposal, and have got it reviewed. Submitted the same after 
several edits. 

Cheers,
Lakhan

On Monday, March 26, 2018 at 4:41:50 PM UTC+5:30, Oleg Nenashev wrote:
>
> Hi Lakhan,
>
> Just FYI, Mar 27 16:00 PM UTC is a deadline for proposals.
> If you are still interested in the project, please make sure to submit 
> your proposal by this time.
>
> We will also have the last Q office hours 
>  today at 18:00PM UTC. 
> Feel free to join if you have any questions.
>
> Best regards,
> Oleg Nenashev
>
> On Saturday, March 17, 2018 at 9:22:54 PM UTC+1, Oleg Nenashev wrote:
>>
>> Hi Lakhan,
>>
>> Yes, it would be great to extend Jenkins features for OSS EDA tools you 
>> mentioned. Regarding your query, it would be great to limit the scope of 
>> the project to few tools to that you could keep focused when you create a 
>> project proposal draft. Regarding FuseSoC, we also have active project 
>> maintainers who may be interested to co-mentor the project. All other tools 
>> in the list are also feasible.
>>
>> We are also setting up a GSoC sync-up call between Jenkins and 
>> LibreCores/FOSSi community members to next week. Currently the slot is TBD, 
>> please add options possible to you: 
>> https://doodle.com/poll/w38ne6qekiyfrb9u
>>
>> Best regards,
>> Oleg
>>
>> On Saturday, March 17, 2018 at 3:15:18 AM UTC+1, martinda wrote:
>>>
>>> Hi Lakhan,
>>>
>>> Thank you for your interest in the GSoC project on EDA plugin for 
>>> Jenkins.
>>>
>>> There are many things a Jenkins EDA plugin can do. It can run the EDA 
>>> tool, but that is rather trivial as anyone can shell out and call the tool 
>>> from the command line. But what get more interesting is interpreting and 
>>> reporting the results. Think of what is important when interpreting 
>>> hardware simulations and synthesis results, what users are interested in 
>>> knowing (simulation pass/fail criteria, log parsing, resource utilization, 
>>> timing, etc) and that should provide a lot of material for coding the 
>>> plugin. It is probably better to have one plugin for each EDA tool.
>>>
>>> Note that we are also in contact with the librecores community regarding 
>>> this plugin, so you should definitely join that community too (
>>> https://gitter.im/librecores/Lobby). A good approach would be to use 
>>> one of their open source projects and build it with the EDA plugin. Lastly 
>>> we have office hours (https://jenkins.io/projects/gsoc/#office-hours), 
>>> all students are invited to participate and ask questions.
>>>
>>> Best Regards,
>>> Martin d'Anjou
>>>
>>>
>>> On Friday, March 16, 2018 at 1:04:02 AM UTC-4, Lakhan Shiva wrote:

 Hi, 

 My name is Lakhan Shiva Kamireddy. I am a second year graduate student 
 at University of Colorado Boulder. I am interested in developing a Jenkins 
 Plugin for one of the EDA tools viz,
 FuseSOC, Yosys, icetools, ArachnePnr, etc. It will help to report FPGA 
 resource utilization per build, etc. 

 I am a user of Jenkins CI build platform while i was a backend web 
 application developer for a multinational consulting corporation (Deloitte 
 Consulting).

 Last year summer, I was an intern at Google, Sunnyvale office in 
 Califronia,as a Hardware Engineering intern and developed a Formal 
 Verification library (SystemVerilog and Perl)
 which falls under RTL design and Verification domain. I think this 
 would be a great project and would like to come up with a proposal for 
 this. I would like to get as much details as possible 
 for this project and also its potential to get accepted as a GSOC 2018 
 project for Jenkins.

 I have pursued some graduate level courses like Logic Synthesis and 
 Optimization, Computer Aided Verification(Formal Verification) at the 
 University of Colorado Boulder in the past years. 

 Kindly contact me, to fuel this project as a potential GSOC 2018 
 candidate.

 Thanks and Kind Regards, 
 Lakhan Shiva Kamireddy

>>>

-- 
You received this message because you are 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/60b77f64-e6de-4b78-88df-e6e5bcb19ddd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anything wrong with storing expanded plugin data in var cache?

[Stephen Connolly]

I see nothing wrong with it... but I would say that having added the
--pluginroot option myself iirc ;-)

On 24 March 2018 at 00:29, Sam Gleske  wrote:

> I normally store expanded plugin metadata within
> /var/cache/jenkins/plugins similar to how WAR filre metadata is stored in
> /var/cache/jenkins/war.
>
> Is there any particular reason the Jenkins packages don't do this?  Are
> there any drawbacks?  I'm curious if others have any opinions on this.
>
> I've been running Jenkins quite a while like this.
>
> [1]: https://github.com/samrocketman/jenkins-bootstrap-shared/blob/
> 1a409cad89007f56ed36342427b767dd4e88fbd9/packaging/docker/run.sh.in#L38
>
> --
> You received this message because you are 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/05beb1e5-a824-428c-b980-07a4e343acdc%
> 40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [GSoc 2018] [Student Introduction] Jenkins Remoting over Message Bus/Queue

[Oleg Nenashev]

Hi Goncalo and Amit,

Just a reminder, Mar 27 16:00 PM UTC is a deadline for proposals.
If you are still interested in the project, please make sure to submit your 
final proposal by this time.

We will also have the last Q office hours 
 today at 18:00PM UTC. Feel 
free to join if you have any questions.

Best regards,
Oleg Nenashev

On Thursday, March 15, 2018 at 4:57:49 PM UTC+1, Oleg Nenashev wrote:
>
> Hi all,
>
> Just heads-up before the incoming call.
> I have created a new filter, which captures more Remoting-related 
> newbie-friendly issues in JIRA different components: 
> https://issues.jenkins-ci.org/issues/?filter=18242
>
> Best regards,
> Oleg
>
> On Tuesday, March 13, 2018 at 12:05:57 PM UTC+1, Oleg Nenashev wrote:
>>
>> Hi all,
>>
>> I have scheduled the meeting to Thursday, 4PM-5PM UTC.
>> If you are a member of 
>> https://groups.google.com/forum/#!forum/jenkinsci-gsoc-all-public , you 
>> should have received an invitation. If no, please join this mailing list 
>> and ping me.
>>
>> BR, Oleg
>>
>>
>>
>> On Mon, Mar 12, 2018 at 12:28 AM, Oleg Nenashev  
>> wrote:
>>
>>> Hi all,
>>>
>>> Thanks to Pham for the proposal! Will try to review it tomorrow
>>>
>>> Since we have several students interested in Remoting, I propose to 
>>> setup a separate session to discuss it.
>>> I have created a poll regarding suitable times here: 
>>> https://doodle.com/poll/a93m25nzzaf29sya
>>>
>>> Best regards,
>>> Oleg
>>>
>>>
>>>
>>> On Saturday, March 10, 2018 at 10:57:41 AM UTC+1, Pham Vu Tuan wrote:

 Hi,

 I put my draft proposal for GSoC here 
 https://docs.google.com/document/d/17vmPvDtMbHT7nTKRlGReFRgOtwVImhgsETLOGPW9Rso/edit?usp=sharing.
  
 I would like to receive reviews and comments about my draft proposal 
 before 
 the submission deadline.

 Thanks,
 Pham Vu Tuan

 On Friday, March 9, 2018 at 1:26:37 AM UTC+8, Oleg Nenashev wrote:
>
> You still have not exposed "-p" option as proposed above.
> I kindly recommend to move this prototyping discussion to a separate 
> thread so it does not pollute the project proposal discussion.
>
> Thanks in advance,
> Oleg
>
> On Thu, Mar 8, 2018 at 6:22 PM, Pham Vu Tuan  
> wrote:
>
>> I resolved the JNLP warning message by passing env variable in Docker 
>> run.
>> But I still encountered "Connection refused" error although I exposed 
>> the port 5 in the Dockerized master.
>>
>>
>> 
>>
>>
>> 
>> My command to start the agent is: "docker run -e 
>> JNLP_PROTOCOL_OPTS='-Dorg.jenkinsci.remoting.engine.JnlpProtocol3.disabled=false'
>>  
>> jenkins/jnlp-slave -url http://localhost:8080 abcd test-node".
>> Any ideas on this?
>>
>> On Friday, March 9, 2018 at 12:13:56 AM UTC+8, Oleg Nenashev wrote:
>>>
>>> Hi Pham,
>>>
>>> In order to connect an agent to the Dockerized master, you need to 
>>> expose the port for the agent (make the Agent port fixed in security 
>>> settings + use "-p" option to expose it).
>>> I am not sure how BlueOcean image is configured, the standard 
>>> Jenkins Docker image has it documented here: 
>>> https://github.com/jenkinsci/docker#usage
>>>
>>> Hopefully it helps,
>>> Oleg
>>>
>>> P.S: I'd guess it's another case of WEBSITE-474 
>>> , right?
>>>
>>>
>>>
>>> On Thu, Mar 8, 2018 at 4:59 PM, Pham Vu Tuan  
>>> wrote:
>>>
 Hello,

 I am trying to setup the master and agent in my local machine. 
 Server setup is fine, I used 
 https://hub.docker.com/r/jenkinsci/blueocean/. But when I tried to 
 connect an agent to it using 
 https://hub.docker.com/r/jenkins/jnlp-slave/ by this command 
 "docker run jenkins/jnlp-slave -url http://localhost:8080 abcd 
 test-node" , I encountered some problems:

 - Warning: JnlpProtocol3 is disabled by default, use 
 JNLP_PROTOCOL_OPTS to alter the behavior => Athough I set the env 
 variable 
 in the docker container for the server, I still encountered this 
 warning 
 message, am I missing to set it somewhere?
 - Not sure if this is related to the above issue, then I cannot 
 connect the agent to server 

> SEVERE: Failed to connect to 
> http://localhost:8080/tcpSlaveAgentListener/: Connection 

Re: [GSOC 2018] Code Coverage API Plugin

[Oleg Nenashev]

Hi Pavan,

Just a reminder, Mar 27 16:00 PM UTC is a deadline for proposals.
If you are still interested in the project, please make sure to submit your 
final proposal by this time.

We will also have the last Q office hours 
 today at 18:00PM UTC. Feel 
free to join if you have any questions.

Best regards,
Oleg Nenashev

On Monday, March 19, 2018 at 6:39:53 PM UTC+1, Supun Wanniarachchi wrote:
>
> Hi Pavan,
>
> Of course not. You have time until March 27 16:00 UTC. Please check 
> information for students[1] for more details about application guidelines.
> I would suggest you to share your draft proposal as soon as possible, so 
> Mentors can review it and suggest improvements. Also, you can join office 
> hours to discuss the project as I mentioned earlier.
>
> [1] https://jenkins.io/projects/gsoc/students 
>
> Best regards,
> Supun Wanniarachchi
>
> On Mon, Mar 19, 2018 at 4:00 PM, Pavan Hegde  > wrote:
>
>> Hi,
>>
>> Thank you so much for taking your time to respond. I have a doubt?. Am i 
>> too late for preparing the project idea?
>>
>> Thanks
>> Pavan
>>
>> On Saturday, 17 March 2018 23:44:00 UTC-7, Pavan Hegde wrote:
>>>
>>> Hi,
>>>
>>> I'm Pavan Hegde i'm currently pursuing my 3rd year of B.E. in computer 
>>> science in City Engineering College Bangalore.
>>> Based on my knowledge in Java and HTML i chose Code Coverage API 
>>> Project. But i have very less knowledge in Jenkins, but i'm interested to 
>>> learn more about it and contribute to it.
>>> So where can i find the appropriate resources regarding the project?
>>>
>>> Thanks in advance
>>> Pavan Hegde
>>>
>>> -- 
>> 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/gQ0MImyZ0Jg/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/6ae8da9f-0c54-4af2-b7ff-aad213ea963b%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Supun Wanniarachchi
> Software Engineering Undergraduate
> Informatics Institute of Technology Sri Lanka (Affiliated with University 
> of Westminster, UK)
> Mobile: +94 716326119
> Blog: http://blog.supun.me 
>
> [image: Github]  [image: LinkedIn] 
>  [image: 
> Twitter] 
>

-- 
You received this message because you are 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/a6f91dd6-5dba-4cb6-adab-52a4656d346c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Hello everyone & a few questions for a students project

[Oleg Nenashev]

Hi Federico,

Sorry, I have missed this thread. Is this still actual? If yes, I will try 
to provide responses once the GSoC application period finishes.

Just to follow-up on our discussion about GSoC, Mar 27 16:00 PM UTC is a 
deadline for proposals.
If you are still interested in the project, please make sure to submit your 
final proposal by this time.

We will also have the last Q office hours 
 today at 18:00PM UTC. Feel 
free to join if you have any questions.

Best regards,
Oleg Nenashev

On Friday, March 2, 2018 at 5:58:00 PM UTC+1, Federico Fiorini wrote:
>
> Hi everyone, 
> I am Federico Fiorini and I am currently studying at TU Delft. I am part 
> of a group for the course Software Architecture (Course Link 
> ) and we are currently studying the 
> Jenkins software in depth. 
> For the second assignment we have to make a pull request (which we already 
> made, #3320 , and we 
> already received a review so we're working on it) as well as a complete 
> "Development View" for the project.
>
> In particular, we need to carefully study how the development process goes 
> for Jenkins, and how is it organised in terms of modules (and folders for 
> source code), dependencies between the many modules, and so on.
> Since it's very difficult to study the software by only looking at the 
> website and the github page (as we did for the first assignment, more about 
> general information of the case study), we thought that it would have been 
> a great idea to ask a few questions to the developers' community and/or the 
> creator of the project. 
>
> I'll make a bulleted list such that it would be easier to understand which 
> are the answers we're looking for.
>
>- How the source code is organised into modules (and how is it stored 
>as folders) and which are the dependencies between the modules
>- Are there any third-party libraries or tools in the code? Where are 
>they used?
>- How are security concerns (also in communication between modules) or 
>internalisation managed? 
>- Are there any automated tools for build, test and release of the 
>software? Is it possible to have a "release roadmap" to better understand 
>how a new release is made and which steps does the code have to pass? (We 
>will focus this concerning LTS versions)
>
>
> Thank you in advance for the replies, we are very grateful for any little 
> help received. 
>
> I will also leave a link to the ongoing project : Team-Jenkins 
> 
>
> Kind regards,
>
> Federico Fiorini, Jeroen Vrijenhoef, Ka Wing Man
>

-- 
You received this message because you are 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/be94dcd8-23fb-42a9-80c7-4b8460998b1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC] Interested in Code Coverage API Plugin Project

[Oleg Nenashev]

Hi Israel,

Just FYI, Mar 27 16:00 PM UTC is a deadline for proposals.
If you are still interested in the project, please make sure to submit your 
final proposal by this time.

We will also have the last Q office hours 
 today at 18:00PM UTC. Feel 
free to join if you have any questions.

Best regards,
Oleg Nenashev

On Tuesday, February 27, 2018 at 12:35:22 AM UTC+1, Steve Christou wrote:
>
> Hello Israel and welcome!
>
> I would recommend taking a look at some of the current existing bugs for 
> the cobertura plugin: 
> https://issues.jenkins-ci.org/browse/JENKINS-31353?jql=component%20%3D%20%27cobertura-plugin%27%20and%20status%20%3D%20Open%20
>  and 
> see which ones look easy to fix. I will be available during office hours 
> this week Wednesday and Friday from 11am to 1 pm PST. If these times don't 
> work, then please let me know.
>
> Thank you,
> Steven.
>
> On Sun, Feb 25, 2018 at 2:13 PM Oleg Nenashev  > wrote:
>
>> Hi Israël,
>>
>> I have pinged the potential mentors about this thread.
>> Hopefully we will get their response soon.
>>
>> I would suggest to start from looking at small tasks for Coverage plugins 
>> like Cobertura or JaCoCo.
>>
>> BR, Oleg
>>
>>
>>
>> On Saturday, February 24, 2018 at 2:01:41 PM UTC+1, Israël Mekomou wrote:
>>>
>>> Hi,
>>>
>>> My name is Israel, I am a third year student in Computer Science and 
>>> Technology at University Institute of Technology from Cameroon. I am trying 
>>> to improve my coding skills and I think this is a good opportunity for me 
>>> to improve it.
>>> I am interested in the Code Coverage API Plugin Project and I wish to 
>>> know how I can get started in the project. Any link to microtask?
>>>
>>> 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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/b4e46d88-c685-42fa-8b48-5a4ec47d3e65%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/dbedca35-4638-4828-9275-fcd147b19018%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC 2018] [Student Introduction] Simple Pull-Request Job Plugin

[Oleg Nenashev]

Hi Andrei,

Just FYI, Mar 27 16:00 PM UTC is a deadline for proposals.
If you are still interested in the project, please make sure to submit your 
final proposal by this time.

We will also have the last Q office hours 
 today at 18:00PM UTC. Feel 
free to join if you have any questions.

Best regards,
Oleg Nenashev

On Sunday, February 18, 2018 at 4:27:03 AM UTC+1, Andrei Vînătoru wrote:
>
> Hi Martin,
>
> This looks like an interesting project for GSoC. I'll do my best to 
> understand what I have to do. Right now I'm reading the plugin tutorial and 
> next I'll look up the external workspace manager plugin to see how it is 
> structured.
>
> Andrei
>
> On Friday, 16 February 2018 12:57:39 UTC+2, martinda wrote:
>>
>> Hello Andrei,
>>
>> Some ideas that have been presented, IMO the project is attracting some 
>> good discussions which will likely continue for a little bit while the 
>> project is being more fully defined. Is this something you'd be interested 
>> in for GSoC?
>>
>> What do you think so far on the direction this project should be going?
>>
>> Martin
>>
>> On Thursday, February 15, 2018 at 2:31:16 PM UTC-5, Jesse Glick wrote:
>>>
>>> On Thu, Feb 15, 2018 at 10:19 AM, martinda  
>>> wrote: 
>>> > My users will never write a Jenkinsfile, ever. But I 
>>> > was able to get them to specify a (very) small YAML file. 
>>> > 
>>> > Maybe you are suggesting that this should be implemented as an 
>>> open-source 
>>> > Pipeline library and Jenkinsfile 
>>>
>>> You can of course do that, though then you still need to have some 
>>> kind of boilerplate: 
>>>
>>> ---%<--- Jenkinsfile 
>>> library('github.com/whatever/jenkins-yaml-lib').run('jenkins.yaml') 
>>> --->%--- 
>>>
>>> CloudBees users can eliminate the need for even that using 
>>>
>>>
>>> https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#pipeline-custom-factories
>>>  
>>>
>>> Or you can write a small plugin which implements the same 
>>> `AbstractWorkflowBranchProjectFactory` / 
>>> `AbstractWorkflowMultiBranchProjectFactory` extension points and bakes 
>>> in an opinionated file name and script. 
>>>
>>> I am not saying that is the only way to accomplish your goal, but it 
>>> is certainly the easiest. You would get support for GitHub & BitBucket 
>>> (including pull requests, webhooks, and organization folders) for 
>>> free, as well as visualization via Blue Ocean and so on. (I suppose 
>>> you could even build an analogue to 
>>>
>>> https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-pipeline-editor
>>>  
>>> if you wanted, though I do not know much about that.) 
>>>
>>

-- 
You received this message because you are 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/b6ff66fa-793f-45a3-a4f4-3fdf1bcf7948%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC] Jenkins Configuration as Code

[Oleg Nenashev]

Hi Harsh,

Just FYI, Mar 27 16:00 PM UTC is a deadline for proposals.
If you are still interested in the project, please make sure to submit your 
final proposal by this time.

We will also have the last Q office hours 
 today at 18:00PM UTC. Feel 
free to join if you have any questions.

Best regards,
Oleg Nenashev

On Wednesday, February 28, 2018 at 6:21:40 PM UTC+1, Harsh Bajaj wrote:
>
> Alright 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/6208839e-c26b-494a-bdb8-63984d72efeb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC] 2018 Student Introduction

[Oleg Nenashev]

Hi Ibrahim,

Just FYI, Mar 27 16:00 PM UTC is a deadline for proposals.
If you are still interested in the project, please make sure to submit your 
final proposal by this time.

We will also have the last Q office hours 
 today at 18:00PM UTC. Feel 
free to join if you have any questions.

Best regards,
Oleg Nenashev

On Wednesday, March 14, 2018 at 1:06:25 PM UTC+1, Jeff Knurek wrote:
>
> Hello Ibrahim,
>
> Thanks for the interest!
> Please see information for students 
>  for application guidelines.
>
> My recommendation would be to...
>
>1. Study the existing plugins, try to setup your Jenkins instance with 
>them. It may give you some ideas of what needs to be enhanced there
>2. Take a look at existing plugin issues, for example the Cobertura 
>plugin 
>
> 
> 
>3. Join one of office hours to discuss the project with them (
>https://jenkins.io/projects/gsoc/#office-hours)
>
> Hopefully it helps,
> Jeff
>
>
> On Monday, March 12, 2018 at 1:50:02 AM UTC+1, Ibrahim Abdullah wrote:
>>
>> Hello,
>>
>> My name is Ibrahim Abdullah, a final year student at Ashesi University 
>> College, Ghana. I am studying computer science and very interested in 
>> software development, distributed systems and Machine learning. Java is the 
>> main programming language I use for development and have little experience 
>> with Jenkins as well. 
>>
>> I have always wanted to contribute to open source projects to improve my 
>> programming skills but find it difficult to start as a newbie. I believe 
>> Google Summer of Code will provide the platform and give me a head start to 
>> join the open source community. Additionally, I found some of the Jenkins 
>> projects exciting to work on given that I have a strong Java background and 
>> quite familiar with using Jenkins as a developer. I will like to work on 
>> any of the following projects: Jenkins Remoting over Message Bus/Queues, 
>> Code Coverage Plugin and Simple pull request Plugin.
>>
>> The following are the links GutHub and LinkedIn profile;
>>
>> GitHub : https://github.com/Ibrahim-Abdullah
>> LinkedIn : www.linkedin.com/in/ibabdullah
>> Twitter: https://twitter.com/braimahabdulla
>>
>>

-- 
You received this message because you are 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/ddb55b3f-a931-45fb-b456-07bf476f552c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

[Ewelina Wilkosz]

+1 to that Baptiste, let's try to make it in a way that
1. will not isolate us, but "keep us together"
2. will make it easy for us to keep the track

and easy to say without providing ideas, but for now I just wanted to 
highlight I believe those two are important things to keep in mind while 
setting things up
I will try to come up with some specifics when I'm done with "fire 
fighting" in the office :)

On Monday, March 26, 2018 at 10:54:00 AM UTC+2, Baptiste Mathus wrote:
>
> I think this is a good initiative to keep us moving forward. As the 
> Jenkins Project keeps growing, we definitely have various people with 
> various interests, and anything that can help people contribute without 
> feeling they're getting spammed by dozens of "unrelated" emails seems a 
> good idea.
>
> I'm slightly worried about the segmentation/explosion of number of mailing 
> lists though, and the segmentation of the community too. 
> I guess we'll need to be even cautious finding a way to still "keep us 
> together", and be more aggressive with regard to JEPping things even more 
> commonly to make sure important things are not decided in the deep of a 
> given thread of a given sub-ML.
>
> My 2 cents
>
>
> 2018-03-23 13:04 GMT+01:00 Carlos Sanchez  >:
>
>> I think the materialization of SIGs would be a great addition to the 
>> community, thanks Tyler for the write up
>>
>> I am working on draft JEPs to be proposed regarding "cloud native": 
>> external storage, external logging,... you'll be reading more from me in 
>> the following weeks :) 
>>
>>
>>
>> On Thu, Mar 22, 2018, 22:04 R. Tyler Croy > > wrote:
>>
>>>
>>> I have been looking at some of the great things the Kubernetes community 
>>> has
>>> been doing for ideas we can borrow, and one idea which really sticks out 
>>> is:
>>> Special Interest Groups (SIGs)
>>> <
>>> https://github.com/kubernetes/community/blob/master/governance.md#sigs>
>>>
>>> A full list of the Kubernetes community SIGs can be found here:
>>> 
>>>
>>> I think we already have some groups, which are almost informal SIGs, 
>>> such as
>>> Security, GSoC, Infra, etc. The aspects of SIGs which I really would 
>>> like to
>>> formalize, and support from a community infra standpoint are:
>>>
>>> * Clear problem domain/focus area.
>>> * Regularly scheduled and published meetings. I can easily imagine 
>>> re-using
>>>   #jenkins-meeting or our public YouTube channel for regularly 
>>> scheduling
>>>   and hosting weekly meetings for these various groups. I run a 
>>> weekly
>>>   infra team sync on jenkins.io/hangout for example, but that's not
>>>   recorded anywhere :(
>>> * "Chairs" (i.e. team leads)
>>> * Dedicated discussion channel/group (i.e. mailing list)
>>>
>>>
>>> Some SIGs which I would love to see for starters, would be:
>>>
>>>  * Security, lead by Daniel
>>>  * GSoC, lead by Oleg
>>>  * Infra, lead by Olivier and myself
>>>  * Cloud Native (Kubernetes, Jenkins X, CLOUD, etc), lead by Carlos
>>>  * Essentials, lead by myself
>>>  * LTS, lead by Oliver
>>>  * Automation/Configuration (config as code, puppet, chef, etc), lead by 
>>> Ewelina
>>>
>>>
>>> From my part on the infrastructure side, I'm more than willing to do the
>>> necessary work to support SIGs, as I really feel like they will help 
>>> bring more
>>> folks to the table for focused contribution to the Jenkins project.
>>>
>>>
>>> I'm curious how others feel about a SIG structure and whether you all 
>>> agree
>>> that it will help channel/focus discussions and contributions?
>>>
>>>
>>>
>>> If there's strong interest, I'm happy to take point on writing a Process 
>>> JEP.
>>>
>>>
>>> Cheers
>>> - R. Tyler Croy
>>>
>>> --
>>>  Code: 
>>>   Chatter: 
>>>  xmpp: rty...@jabber.org 
>>>
>>>   % 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-de...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/20180322210421.4ikcudf7m65yilvo%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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> 

Re: [GSOC 2018] EDA Plugin : Developing a Jenkins Plugin for one of the EDA tools viz FuseSOC

[Oleg Nenashev]

Hi Lakhan,

Just FYI, Mar 27 16:00 PM UTC is a deadline for proposals.
If you are still interested in the project, please make sure to submit your 
proposal by this time.

We will also have the last Q office hours 
 today at 18:00PM UTC. Feel 
free to join if you have any questions.

Best regards,
Oleg Nenashev

On Saturday, March 17, 2018 at 9:22:54 PM UTC+1, Oleg Nenashev wrote:
>
> Hi Lakhan,
>
> Yes, it would be great to extend Jenkins features for OSS EDA tools you 
> mentioned. Regarding your query, it would be great to limit the scope of 
> the project to few tools to that you could keep focused when you create a 
> project proposal draft. Regarding FuseSoC, we also have active project 
> maintainers who may be interested to co-mentor the project. All other tools 
> in the list are also feasible.
>
> We are also setting up a GSoC sync-up call between Jenkins and 
> LibreCores/FOSSi community members to next week. Currently the slot is TBD, 
> please add options possible to you: 
> https://doodle.com/poll/w38ne6qekiyfrb9u
>
> Best regards,
> Oleg
>
> On Saturday, March 17, 2018 at 3:15:18 AM UTC+1, martinda wrote:
>>
>> Hi Lakhan,
>>
>> Thank you for your interest in the GSoC project on EDA plugin for Jenkins.
>>
>> There are many things a Jenkins EDA plugin can do. It can run the EDA 
>> tool, but that is rather trivial as anyone can shell out and call the tool 
>> from the command line. But what get more interesting is interpreting and 
>> reporting the results. Think of what is important when interpreting 
>> hardware simulations and synthesis results, what users are interested in 
>> knowing (simulation pass/fail criteria, log parsing, resource utilization, 
>> timing, etc) and that should provide a lot of material for coding the 
>> plugin. It is probably better to have one plugin for each EDA tool.
>>
>> Note that we are also in contact with the librecores community regarding 
>> this plugin, so you should definitely join that community too (
>> https://gitter.im/librecores/Lobby). A good approach would be to use one 
>> of their open source projects and build it with the EDA plugin. Lastly we 
>> have office hours (https://jenkins.io/projects/gsoc/#office-hours), all 
>> students are invited to participate and ask questions.
>>
>> Best Regards,
>> Martin d'Anjou
>>
>>
>> On Friday, March 16, 2018 at 1:04:02 AM UTC-4, Lakhan Shiva wrote:
>>>
>>> Hi, 
>>>
>>> My name is Lakhan Shiva Kamireddy. I am a second year graduate student 
>>> at University of Colorado Boulder. I am interested in developing a Jenkins 
>>> Plugin for one of the EDA tools viz,
>>> FuseSOC, Yosys, icetools, ArachnePnr, etc. It will help to report FPGA 
>>> resource utilization per build, etc. 
>>>
>>> I am a user of Jenkins CI build platform while i was a backend web 
>>> application developer for a multinational consulting corporation (Deloitte 
>>> Consulting).
>>>
>>> Last year summer, I was an intern at Google, Sunnyvale office in 
>>> Califronia,as a Hardware Engineering intern and developed a Formal 
>>> Verification library (SystemVerilog and Perl)
>>> which falls under RTL design and Verification domain. I think this would 
>>> be a great project and would like to come up with a proposal for this. I 
>>> would like to get as much details as possible 
>>> for this project and also its potential to get accepted as a GSOC 2018 
>>> project for Jenkins.
>>>
>>> I have pursued some graduate level courses like Logic Synthesis and 
>>> Optimization, Computer Aided Verification(Formal Verification) at the 
>>> University of Colorado Boulder in the past years. 
>>>
>>> Kindly contact me, to fuel this project as a potential GSOC 2018 
>>> candidate.
>>>
>>> Thanks and Kind Regards, 
>>> Lakhan Shiva Kamireddy
>>>
>>

-- 
You received this message because you are 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/70eb26f1-ca96-4998-96ae-6e5e9526d6d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC] Introductory mail for writing java plugin for Jenkins project 2018

[Oleg Nenashev]

Hi Sunny,

Just FYI, Mar 27 16:00 PM UTC is a deadline for proposals.
If you are still interested in the project, please make sure to submit your 
proposal by this time.

We will also have the last Q office hours 
 today at 18:00PM UTC. Feel 
free to join if you have any questions.

Best regards,
Oleg Nenashev

On Tuesday, March 20, 2018 at 11:55:21 PM UTC+1, Oleg Nenashev wrote:
>
> Hi,
>
> Thanks for the interest!
> We are looking forward to hear some details about your project proposal.
> You can find the information for students here: 
> https://jenkins.io/projects/gsoc/students/
>
> Best regards,
> Oleg Nenashev
>
> On Sunday, March 18, 2018 at 3:05:16 PM UTC+1, sunny blaze wrote:
>>
>>
>> -- Forwarded message --
>> From: sunny blaze 
>> Date: Sun, Mar 18, 2018 at 2:45 PM
>> Subject: [GSoC] Introductory mail for writing java plugin for Jenkins 
>> project 2018
>> To: jenkin...@googlegroups.com
>>
>>
>> Hello! Team,
>>
>> My name is Amowe Sunday Alexander, I’m a Computer Science (major) student 
>> at Adekunle Ajasin University Akungba, (AAUA) Akoko, Ondo State, Nigeria. 
>> Am currently in my fourth year, with interest in server side programming 
>> (using java, php and node.js) and I love solving challenging problems in 
>> various areas and I’m always ready to learn new concept and technology for 
>> solving problems.
>>
>>
>> I have few experience in developing android application using Java, I 
>> also partake in few programming contest (such as CodeChef Snack Down 2017, 
>> Google Hash Code 2018 and some other local programming contest) using the 
>> Java programing language, some of my solutions to this competitions can be 
>> found on my personal github repo (https://github.com/sunnyblaze/CodeChef, 
>> https://github.com/sunnyblaze/Competitive-Programming), I am currently 
>> working on a project called “AAUA ASSISTANT” for my institution and I 
>> currently have few personal android and desktop project that I’m working on 
>> using Java.
>>
>>
>> I have also partaken in some freelancing job (such as web designing using 
>> PHP, SQL, JavaScript, HTML and CSS) one of my most recent freelance job is 
>> www.ismailautomobile.com.ng.
>>
>> And I am currently a member of Google Developers Group (GDG) AAUA 
>> Chapter, where I was opportune to partake in almost all their project both 
>> android and web. I also have professional certificate in website design 
>> from MAGNATE MUSCLE LIMITED, Nigeria.
>>
>> Key skills:
>>
>> ü  Java =>*fluently.*
>>
>> ü  PHP =>*fluently*
>>
>> ü  SQL=>*Intermediate *
>>
>> ü  JavaScript=>   *fluently*
>>
>> ü  Html=>*fluently*
>>
>> ü  *XML=>   intermediate*
>>
>> ü  CSS =>*fluently*
>>
>> ü  Bootstrap =>*Intermediate*
>>
>> ü  C =>*Beginner*
>>
>>  
>>
>> Why I’m interested in the Jenkins project:
>>
>> After several months of research on Jenkins project, I was able to 
>> understood that Jenkins is a server application written purely in java that 
>> runs in java servlet just as apache tomcat and the likes. Jenkins has 
>> various plugins that extend its use to projects written in other 
>> languages, 
>>
>> Jenkins is a Continuous Integration server, basically you can run your 
>> tests on a non-developer machine automatically everytime someone pushes new 
>> code into the source repository. With Jenkins, organizations can 
>> accelerate the software development process through automation. Jenkins 
>> integrates development life-cycle processes of all kinds, including build, 
>> document, test, package, stage, deploy, static analysis and much more. Most 
>> importantly Jenkins has given a lot to the community of developers 
>> including myself by being an open source. In my little way of showing 
>> appreciation I love to contribute to the Jenkins project by writing plugins 
>> for the Jenkins project.
>>
>> With my knowledge of computer networking and few experience in Java SE(8 
>> and 9)  Jenkins project is the perfect suite for me to actualize my 
>> childhood dream of being a software engineer (server-side). 
>>
>>  
>>
>> Interested Project Idea
>>
>> “Jenkins Remoting over Message Bus/Queue” This will enable me to apply 
>> my knowledge into solving real life problem and also give back to the 
>> Jenkins community
>>
>>

-- 
You received this message because you are 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 

Re: [GSoC 2018] [Student Introduction] Cloud Features for External Work-space Manager Plugin

[Oleg Nenashev]

Hi Vineeth,

Sorry, I have missed that thread.
If you are familiar with Azure, my recommendation would be to stick to it 
and to describe storage features available there.

Even if you have concerns about the implementation, my recommendation is to 
submit a draft so that we can review it and help you with polishing the 
proposal. There will be also office hours at 6PM UTC today, please feel 
free to join.

BR, Oleg

On Thursday, March 22, 2018 at 9:29:42 AM UTC+1, Vineeth Reddy wrote:
>
> I am familiar with java ,maven and Microsoft azure as this project needs 
> some cloud experience.
> But I am unable to get on to the implementation part. 
> I am new to open source community 
> May be am not good enough for the project.
> As implementation part is still a challenge to me am unable to come up 
> with timeline part in application.
>
>
>
>
> On Wed, 21 Mar 2018 at 4:39 AM, Oleg Nenashev  > wrote:
>
>> Hi Vineeth,
>>
>> Generally you tell us. In GSoC mentors propose "project ideas", but 
>> students have a freedom to adjust these ideas to their vision and 
>> interests. Since you have gone through the linked materials and issues, 
>> what is your impression? Which topics would you prefer to work on? Please 
>> do not hesitate to ask in JIRA tickets or in this thread if something is 
>> not clear.
>>
>> Best regards,
>> Oleg Nenashev
>>
>>
>> On Tuesday, March 20, 2018 at 8:04:52 PM UTC+1, Vineeth Reddy wrote:
>>
>>> I went through all the resources provided and would like to know more 
>>> about cloud features required for this project.
>>>
>>> On Sun, 18 Mar 2018 at 3:21 AM, martinda  wrote:
>>>
>> Hi,

 I should also mention that there are videos that explain how the 
 external workspace manager plugin works.
 These provide good starting points for understanding from the user 
 point of view.

 1. Lightning talk (Jenkins World 2016): 
 https://www.youtube.com/watch?v=mZaCngHQaO4
 2. GSoC 2016 final presentations (first presentation is the external 
 workspace manager plugin): https://youtu.be/lo8sZJt2WhM?t=404

 Martin


 On Friday, March 16, 2018 at 10:16:10 PM UTC-4, martinda wrote:
>
> I forgot to mention that we have office hours and all students are 
> invited to participate and ask questions about GSoC.
> See https://jenkins.io/projects/gsoc/#office-hours for the times.
>
> Martin
>
> On Friday, March 16, 2018 at 9:50:28 PM UTC-4, martinda wrote:
>>
>> Hello Vineeth,
>>
>> Thank you for your interest.
>>
>> We have some student information, but it looks like you have already 
>> read it: https://jenkins.io/projects/gsoc/students/
>> If you find something is missing please let us know.
>>
>> If you have already studied the external workspace manager code base 
>> and know the extension points 
>> ,
>>  
>> then I recommend familiarizing yourself with cloud based storage, for 
>> example azure, amazon, google, etc. This should help you write your 
>> project 
>> proposal.
>>
>> Best Regards,
>> Martin d'Anjou
>>
>> On Friday, March 16, 2018 at 3:18:03 PM UTC-4, Vineeth Reddy wrote:
>>>
>>>
>>> I am a newbie in open source community but i feel i am capable 
>>> enough to understand and give back to community my best. 
>>>
>>> I am interested in working with "CLOUD FEATURES FOR EXTERNAL 
>>> WORKSPACE MANAGER PLUGIN. "
>>>
>>> I spent decent time on understanding project and would like to look 
>>> into it more detail.
>>>
>>> As application closes in 11 days. I am unable to contribute much in 
>>> prior but would like to make it this summer.
>>>
>>> Please guide with through additional info, resources on this project 
>>> and ways to selected for this project and in starting  the contribution 
>>> right away.
>>>
>>> -- 
 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/6BgDrjm6_Lk/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/34c19ab7-b00f-4336-9d11-661b761f5cb4%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 
>> 

Re: Anything wrong with storing expanded plugin data in var cache?

[Baptiste Mathus]

For context, I asked Sam to come and discuss this here after his comment

on the JEP about Essentials Evergreen snapshotting system, in the part
where we explain how we plan to aggressively segregate data
.

So, my take is going to be two-fold:


   - On Essentials, I think we are free to do more things because we have
   basically no existing setup. So I'm leaning towards doing this.
   I'm just slightly worried about:
   - Bad performance (though heavily depending on the storage driver)
  writing things in a layer that could grow pretty big outside the
  $EVERGREEN_HOME volume.
 - At the same time, this would also be a good thing® since by
 definition this would be cleaned up if someone starts with a
fresh image
 version (though it's not *really* the use case of Essentials, as the
 content will auto-update)
 - we could also have a second volume dedicated to writing caches,
 but I'm not very keen on doing that since I feel this would
go against the
 evergreen idea to be very simple to use. And users would
probably have to
 manage the data written in that second volume instead of a single one
 (which I suppose people are more used to see).

 - For Jenkins packages, I think this would be a good thing to do
   to, it's just that it's clearly more complex to do since there are existing
   setups out there. So we'll want to make sure we don't break people
   instances when upgrading after such a change.



2018-03-24 1:29 GMT+01:00 Sam Gleske :

> I normally store expanded plugin metadata within
> /var/cache/jenkins/plugins similar to how WAR filre metadata is stored in
> /var/cache/jenkins/war.
>
> Is there any particular reason the Jenkins packages don't do this?  Are
> there any drawbacks?  I'm curious if others have any opinions on this.
>
> I've been running Jenkins quite a while like this.
>
> [1]: https://github.com/samrocketman/jenkins-bootstrap-shared/blob/
> 1a409cad89007f56ed36342427b767dd4e88fbd9/packaging/docker/run.sh.in#L38
>
> --
> You received this message because you are 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/05beb1e5-a824-428c-b980-07a4e343acdc%
> 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/CANWgJS6PokYyp4tidUh-tz1PTjuAPKttVO-DJwx4r6JvNXOsdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Rename Confluence Page?

[Daniel Beck]

> On 26. Mar 2018, at 09:56, Oleg Nenashev  wrote:
> 
> AFAIK JIRA does not put redirects for renamed pages, so the renaming may 
> break something (e.g. built-in plugin documentation)

It does but our cache does not support it. Needs infra issue filed so we 
manually delete 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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/35E9C0F5-2C6D-47B9-A14C-D33226F1EB01%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

[Baptiste Mathus]

I think this is a good initiative to keep us moving forward. As the Jenkins
Project keeps growing, we definitely have various people with various
interests, and anything that can help people contribute without feeling
they're getting spammed by dozens of "unrelated" emails seems a good idea.

I'm slightly worried about the segmentation/explosion of number of mailing
lists though, and the segmentation of the community too.
I guess we'll need to be even cautious finding a way to still "keep us
together", and be more aggressive with regard to JEPping things even more
commonly to make sure important things are not decided in the deep of a
given thread of a given sub-ML.

My 2 cents


2018-03-23 13:04 GMT+01:00 Carlos Sanchez :

> I think the materialization of SIGs would be a great addition to the
> community, thanks Tyler for the write up
>
> I am working on draft JEPs to be proposed regarding "cloud native":
> external storage, external logging,... you'll be reading more from me in
> the following weeks :)
>
>
>
> On Thu, Mar 22, 2018, 22:04 R. Tyler Croy  wrote:
>
>>
>> I have been looking at some of the great things the Kubernetes community
>> has
>> been doing for ideas we can borrow, and one idea which really sticks out
>> is:
>> Special Interest Groups (SIGs)
>> > governance.md#sigs>
>>
>> A full list of the Kubernetes community SIGs can be found here:
>> 
>>
>> I think we already have some groups, which are almost informal SIGs, such
>> as
>> Security, GSoC, Infra, etc. The aspects of SIGs which I really would like
>> to
>> formalize, and support from a community infra standpoint are:
>>
>> * Clear problem domain/focus area.
>> * Regularly scheduled and published meetings. I can easily imagine
>> re-using
>>   #jenkins-meeting or our public YouTube channel for regularly
>> scheduling
>>   and hosting weekly meetings for these various groups. I run a weekly
>>   infra team sync on jenkins.io/hangout for example, but that's not
>>   recorded anywhere :(
>> * "Chairs" (i.e. team leads)
>> * Dedicated discussion channel/group (i.e. mailing list)
>>
>>
>> Some SIGs which I would love to see for starters, would be:
>>
>>  * Security, lead by Daniel
>>  * GSoC, lead by Oleg
>>  * Infra, lead by Olivier and myself
>>  * Cloud Native (Kubernetes, Jenkins X, CLOUD, etc), lead by Carlos
>>  * Essentials, lead by myself
>>  * LTS, lead by Oliver
>>  * Automation/Configuration (config as code, puppet, chef, etc), lead by
>> Ewelina
>>
>>
>> From my part on the infrastructure side, I'm more than willing to do the
>> necessary work to support SIGs, as I really feel like they will help
>> bring more
>> folks to the table for focused contribution to the Jenkins project.
>>
>>
>> I'm curious how others feel about a SIG structure and whether you all
>> agree
>> that it will help channel/focus discussions and contributions?
>>
>>
>>
>> If there's strong interest, I'm happy to take point on writing a Process
>> JEP.
>>
>>
>> Cheers
>> - R. Tyler Croy
>>
>> --
>>  Code: 
>>   Chatter: 
>>  xmpp: rty...@jabber.org
>>
>>   % 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/ms
>> gid/jenkinsci-dev/20180322210421.4ikcudf7m65yilvo%
>> 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/CALHFn6OE--pazM4C%2BFt6F066PfmhP5L7s2ZQX3AB6NW_
> uQo2rQ%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 

Re: Rename Confluence Page?

[Oleg Nenashev]

Hi Richard,

I would contact the maintainer.
AFAIK JIRA does not put redirects for renamed pages, so the renaming may 
break something (e.g. built-in plugin documentation)

BR, Oleg


On Monday, March 26, 2018 at 8:22:32 AM UTC+2, Richard Bywater wrote:
>
> Hi
>
> Just found this page on the Wiki - 
> https://wiki.jenkins.io/display/JENKINS/HTML+Publisher 
> 
>  - 
> which isn't actually anything to do with the HTML Publisher plugin but is 
> named in such a way that it could confuse people (Appears from the 
> breadcrumbs to be related to the ZAP plugin - Pages / Home / Plugins / zap 
> plugin / Configure the Job / HTML Publisher)
>
> What's the best approach to fixing it up so its not likely to confuse 
> users - rename it myself, try and track down the maintainer to rename it, 
> or something else?
>
> Cheers
> Richard.
>

-- 
You received this message because you are 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/8d758998-73ba-4053-9130-40095623b4b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC 2018] UPDATE for CODE Coverage API Plugin

[Rajgure Abhishek Sanjay Abhishek Sanjay]

hi oleg
sorry for that , i changed it now can you please review it

On Mon, Mar 26, 2018 at 3:48 AM, Oleg Nenashev 
wrote:

> Now I cannot open it at all. Please use a separate window in private mode
> to verify permissions.
>
> BR, Oleg
>
> On Mar 25, 2018 22:54, "Rajgure Abhishek Sanjay Abhishek Sanjay" <
> iit2014...@iiita.ac.in> wrote:
>
>> i have changed it ,can you please review it now
>>
>> On Mon, Mar 26, 2018 at 2:03 AM, Oleg Nenashev 
>> wrote:
>>
>>> Hi,
>>>
>>> Thanks for the proposal!
>>> Your document is view-only, so I cannot review it. Could you please
>>> allow comments for any user with the link?
>>>
>>> Thanks in advance,
>>> Oleg
>>>
>>> On Sun, Mar 25, 2018 at 10:04 PM, Rajgure Abhishek Sanjay Abhishek
>>> Sanjay  wrote:
>>>
 please review my proposal
 sorry for late submission

 https://docs.google.com/document/d/1RJy1t8O5e_ATb7wd8__a83QZ
 g5bjt29kt1MCJp_meKQ/edit

 On Tue, Mar 20, 2018 at 12:12 PM, Oleg Nenashev  wrote:

> See https://groups.google.com/forum/#!topic/jenkinsci-dev/-zDJi8swnIE
>
> On Monday, March 19, 2018 at 3:14:26 PM UTC+1, Oleg Nenashev wrote:
>>
>> I have reached out to the project mentors.
>> IIUC they are going to setup a meeting to this week, stay tuned.
>>
>> BR, Oleg
>>
>>
>> On Mon, Mar 19, 2018 at 3:07 PM, Rajgure Abhishek Sanjay Abhishek
>> Sanjay  wrote:
>>
>>> can you guys suggest me some time slots according to your schedule ,
>>> i wish you too show my work and discuss about the another possible
>>> solution for this problem.
>>>
>>> --
>>> 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/to
>>> pic/jenkinsci-dev/RtqsrVk6Aoc/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/4e15f968-930
>>> 4-4e47-b9d4-80283e59bf51%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/to
> pic/jenkinsci-dev/RtqsrVk6Aoc/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/adbd0614-a1f
> c-4889-8b4b-a84838ae5437%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/to
 pic/jenkinsci-dev/RtqsrVk6Aoc/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/ms
 gid/jenkinsci-dev/CAPrCTm8XpaX6StS4aR%3DhnMyZK4O9%3DGfnznEb8
 %3DPY0HkvvqfUSw%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/to
>>> pic/jenkinsci-dev/RtqsrVk6Aoc/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/ms
>>> gid/jenkinsci-dev/CAPfivLBrDK2TQR_2XoC9F3Qzu6bg7RDaGFgsNe_H3
>>> S%3DrmG3%3Diw%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
>> 

Rename Confluence Page?

[Richard Bywater]

Hi

Just found this page on the Wiki -
https://wiki.jenkins.io/display/JENKINS/HTML+Publisher - which isn't
actually anything to do with the HTML Publisher plugin but is named in such
a way that it could confuse people (Appears from the breadcrumbs to be
related to the ZAP plugin - Pages / Home / Plugins / zap plugin / Configure
the Job / HTML Publisher)

What's the best approach to fixing it up so its not likely to confuse users
- rename it myself, try and track down the maintainer to rename it, or
something else?

Cheers
Richard.

-- 
You received this message because you are 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/CAMui9451j3-HWLt_08Ur6HMRUVRZKyJtniRORw0Rr9UN4R6OAg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.