Re: External Artifact Storage

[Jesse Glick]

+1

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

External Artifact Storage

[Carlos Sanchez]

Hi there,

With the goal to make Jenkins more "cloud-friendly" or "cloud-native" I
have created a JEP draft to enable the storage of artifacts outside the
Jenkins home, ready for review

https://github.com/carlossg/jep/tree/jep-submission/jep/

TL;DR

Adding an ArtifactManager implementation (with required core changes) that
transparently stores artifacts in a external blob store / artifact
repository. First implementation using AWS S3

Please share your feedback

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

Upcoming JEP for usage of Incrementals repository

[Jesse Glick]

After IEP-9¹ there was a need for an actual system for producing and
consuming these quasi-release “incremental” artifacts from Jenkins
projects (typically based on Maven). This is just a heads-up that I am
working on a preparing a JEP, probably for the 3xx “Essentials”
series; and a reference implementation, namely some Maven tooling.
This is being tracked under JENKINS-50686². Anyone with deep
understanding of Maven (like Stephen…) is encouraged to take a peek at
my ongoing work.

¹ https://github.com/jenkins-infra/iep/blob/master/iep-009/README.adoc
² https://issues.jenkins-ci.org/browse/JENKINS-50686

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

Re: [Even:Jenkins World EU 2018] CFP Closes this Sunday

[Alyssa Tong]

Hi All,

A friendly reminder that Jenkins World EU CFP will be closing this Sunday,
15 April.

https://jenkinsworld2018cfp.hubb.me/Home/Index?ReturnUrl=%2fHome%2fDashboard

Thnx,
alyssa

On Thu, Mar 15, 2018 at 3:04 PM, Alyssa Tong  wrote:

> Hello,
>
> A few updates to Jenkins World 2018:
>
>- Jenkins World SF CFP
> has been extended
>to April 1, 2018
>- Jenkins World EU CFP
> has been extended
>to April 15, 2018
>- Jenkins World EU  will
>be located in Nice, France on October 22-25, 2018
>
> The CFP webpage  will
> be updated (soon) with this new information.
>
> BR,
> alyssa
>

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

Re: TODO-Plugin guidance

[Jesse Glick]

On Thu, Apr 12, 2018 at 7:57 AM, Ronald Petty  wrote:
> The
> global.jelly is not generated, so there was no Configure screen for the
> plugin.

Yes, that was removed from the `Builder` archetype, as it was using an
old idiom that does not generalize well and is no longer recommended.
There is a separate archetype showing how to use a
`GlobalConfiguration`.

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

Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

[Jesse Glick]

On Thu, Apr 12, 2018 at 5:13 AM, Robert Sandell  wrote:
> Yes declarative has both of these in a way via the when directive's branch 
> and changeset conditions. If I've interpreted forBranch and forChangesIn 
> correctly

`forChangesIn` sounded to me like something different—running its
block repeatedly somehow?—but I did not really grasp what it was
about. Probably best demonstrated by just writing the plugin for it
and submitting the hosting request.

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

Re: TODO-Plugin guidance

[Ronald Petty]

Thanks for the information.  I did find part of the issue for me.  The 
global.jelly is not generated, so there was no Configure screen for the 
plugin.  There was an option (which I didn't check first time) for the job, 
but not the plugin.  Adding global.jelly, repackage, it then worked like it 
use to.

On Wednesday, April 11, 2018 at 12:52:29 AM UTC-7, Baptiste Mathus wrote:
>
> Cool you're trying this! Welcome!
>
> You should follow https://jenkins.io/doc/developer/tutorial/create/ then 
> IIUC you will want to choose the (as of now) choice number 2: 
>
> "2: remote -> io.jenkins.archetypes:hello-world-plugin (Skeleton of a 
> Jenkins plugin with a POM and an example build step.)"
>
> FWIW, just tested it and it worked perfectly for me:
>
> Démarré par l'utilisateur anonymous
> Building in workspace 
> [...]/dev/tmp/2018-04-11T09h44m51+0200-/blah/work/workspace/fgfdffd
> Hello, baptiste!
> Finished: SUCCESS
>
>
> In the end, it /should/ be the very same as what you typed, but well, 
> better follow the documentation if you're still learning the basics. For 
> you, and to give us the opportunity to improve/fix the documentation for 
> newcomers :).
>
> Cheers
>
> 2018-04-11 5:46 GMT+02:00 Ronald Petty 
> :
>
>> Hello,
>>
>> I could be living in the past, but I am trying to get the old `mvn 
>> hpi:...` to work and it seems it has changed.  I found a page saying we 
>> should use this method here:
>>
>> mvn archetype:generate -B -DarchetypeGroupId=io.jenkins.archetypes 
>> -DarchetypeArtifactId=hello-world-plugin -DarchetypeVersion=1.4 
>> -DartifactId=first
>>
>> mvn hpi:run
>>
>> Things start up, and I see the TODO plugin installed, but the Hello World 
>> Builder is now gone.  No errors appear on start in the log.
>>
>> Can someone point me to a fool proof hello-world (TODO) tutorial for 
>> Jenkins 2.115 development?
>>
>> I appreciate the help.
>>
>> Regards.
>>
>> Ron
>>
>> -- 
>> You received this message because you are 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/b669b566-eb39-4b24-b76b-3965e14fa7e2%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/40d08dcd-3beb-4349-90cc-848419cee9b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

[Robert Sandell]

Yes declarative has both of these in a way via the when directive's branch
and changeset conditions. If I've interpreted forBranch and forChangesIn
correctly :)

https://jenkins.io/doc/book/pipeline/syntax/#when

/B


2018-04-11 23:39 GMT+02:00 Jesse Glick :

> Declarative Pipeline certainly can easily do the same as `forBranch`,
> and from Scripted you can trivially write the same thing, so I think
> no new step is warranted.
>
> Not quite sure I follow what `forChangesIn` is about, but sounds like
> a candidate for a new plugin.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CANfRfr0jXNj9-XCTWXERUQz%2B7Vx9sVrPor%2BraJU-
> GSHvaoMsWw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] 
E: rsand...@cloudbees.com
Twitter: robert_sandell

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

Re: [DISCUSS] Change Jenkins default logging format

[Cyrille Le Clerc]

As I have already said many times, I fully support this initiative.

Tomcat has done this move a while ago and it was a great success.

Cyrille

On Wednesday, April 4, 2018 at 3:18:00 PM UTC+2, Baptiste Mathus wrote:
>
> Hello everyone,
>
> Having worked on more things related to Jenkins logging recently, I've had 
> the opportunity to remember my past pain when I was operating a Jenkins 
> instance and sending logs to an ELK cluster.
> Compared to almost everything else in the infrastructure, the logstash 
> rules for Jenkins logs were unnecessarily complex.
>
> The main pain-points, for me at least, had been the two-lines (sigh) per 
> log default, and also the localized date format (or log level...). 
> Even now, so many years after reading those, I still struggle daily to 
> make sure I'm reading the right line/date associated to the message I'm 
> reading on the line above.
>
> I would like to propose we change the current logging format behavior to a 
> more readable and more operation-friendly one.
> This would result in something close to the following format:
>
> [   INFO][2018-04-04 12:40:49] Logging initialized @180ms to 
> org.eclipse.jetty.util.log.JavaUtilLog (from org.eclipse.jetty.util.log.Log 
> initialized)
> [   INFO][2018-04-04 12:40:49] Beginning extraction from war file (from 
> winstone.Logger logInternal)
> [WARNING][2018-04-04 12:40:49] Empty contextPath (from 
> org.eclipse.jetty.server.handler.ContextHandler setContextPath)
> [   INFO][2018-04-04 12:40:49] jetty-9.4.z-SNAPSHOT (from 
> org.eclipse.jetty.server.Server doStart)
>
> Instead of the usual:
>
> Apr 04, 2018 12:36:41 PM org.eclipse.jetty.util.log.Log initialized
> INFO: Logging initialized @354ms to org.eclipse.jetty.util.log.JavaUtilLog
> Apr 04, 2018 12:36:41 PM winstone.Logger logInternal
> INFO: Beginning extraction from war file
> Apr 04, 2018 12:36:42 PM org.eclipse.jetty.server.handler.ContextHandler 
> setContextPath
> WARNING: Empty contextPath
> Apr 04, 2018 12:36:42 PM org.eclipse.jetty.server.Server doStart
> INFO: jetty-9.4.z-SNAPSHOT
>
>
> WDYT?
>
> If this looks interesting to people, I'm ready to file the associated JEP 
> for it and possibly work on its implementation in the future.
>
> Obviously, we would need some way to revert to the "legacy" format, at 
> least for some time for users to adapt. But that is not something I'm 
> particularly worried about.
>
> -- Baptiste
>

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

Re: [GSoC 2018] - Preliminary announcement

[vidhi jindal]

Hi, 

I want to be a mentor. I cannot access this link. Is there any new link?

On Tuesday, December 19, 2017 at 4:32:42 PM UTC+5:30, Oleg Nenashev wrote:
>
> Hi,
>
> I suggest discussing the ideas in a Google Doc.
> Wiki is fine, but it is complicated to handle the feedback there.
> I have started 
> https://docs.google.com/document/d/1q2p_XZEdbkcVDMpEPTtjPS15i2Oq3CQgH_geJjPhofY/edit?usp=sharing
>  
> for now, so please feel free to propose your project ideas there.
>
> Once the ideas are finalized, I will be moving them to the jenkins.io 
> website.
>
> BR, Oleg
>
>
>
> понедельник, 18 декабря 2017 г., 9:18:13 UTC+1 пользователь Ewelina 
> Wilkosz написал:
>>
>> Count me in, for Jenkins Configuration as Code
>>
>> On Saturday, December 16, 2017 at 5:50:19 PM UTC+1, martinda wrote:
>>>
>>> I would like to renew this experience. You can count me in as a mentor.
>>>
>>> Where should we propose and discuss project ideas? I suggest a page on 
>>> the Wiki like GSoC 2016 project idea examples 
>>> .
>>> I have a few ideas already:
>>>
>>>- Improvements to workspace data retention feature (aka automatic 
>>>workspace clean up)
>>>   - Erase  builds older than X days of builds but always keep the 
>>>   last Y builds regardless of how old the builds are
>>>   - Erase the external workspaces 
>>>    in 
>>>   accordance with the workspace retention policy
>>>   - Summary Report plugin 
>>> workflow compatibility
>>>- Speed improvements to the ATH (like use a dockerized jenkins 
>>>instead of restarting jenkins for every test, but I am sure there are 
>>> many 
>>>ideas here)
>>>
>>> Martin
>>>
>>

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

Re: jep-200 issue

[Eugen Horovitz]

Thanks a lot Jesse.
We will consider all these things when upgrading .

Kind Regards,
Eugen



On Wed, Apr 11, 2018 at 7:51 PM, Jesse Glick  wrote:

> On Wed, Apr 11, 2018 at 10:54 AM, Eugen Horovitz
>  wrote:
> > The rule violations : https://gist.github.com/eugenhoro/
> 44e1495ff8d182c8760edeec0982d020
>
> Some of those would be corrected by just, say, updating the
> `maven-plugin` dep. Others look like real mistakes in your
> dependencies. For example, you are declaring an explicit dependency on
> a version of `wss-agent-api-client` older than what your other
> dependency `whitesource-fs-agent` claims to require, which could
> result in linkage errors at runtime. Anyway, something to address when
> next updating your parent POM.
>
> --
> 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/NI533mCeKgc/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/CANfRfr28u45aKvK53-PbN8MRYnOAoxRUa7-O%
> 2BGLMm0fDKS_Q-g%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Eugen Horovitz*

*Senior software engineer*



*WhiteSource  **empowers businesses
to develop better software *
*by harnessing the power of open source*




-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send 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%2BZxFhd41qyWrLOqMphHd5R5dwJ1HGO6t72NyPjHfJsEBSZV2g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.