Re: Upcoming JEP for usage of Incrementals repository

[R. Tyler Croy]

(replies inline)

On Fri, 13 Apr 2018, Jesse Glick wrote:

> Filed a draft request:
> 
> https://github.com/jenkinsci/jep/pull/84


Jesse this is a very thorough and well-thought out document! Thank you so much
for putting the effort into it.

I understand that you have prototyped this work with strictly plugins at this
point, and the document makes allusions to core and 'modules' potentially being
able to use this same approach and tooling.

The only question I had was whether you think it's important to verify that
core and modules function with this model before rolling out this type of a
design? From the IEP-9 standpoint, I don't really care what tooling is required
to get  incremental builds into the maven repository, but I'm not sure if you
consider applicability to core part of "acceptance criteria" for this design.

I hope the question makes sense, put more shortly: does core need to be figured
out for this to come into effect?




Have a good weekend :D

-- 
You received this message because you are subscribed to the Google 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/20180414002112.GE1836%40grape.lasagna.io.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: [Jenkins World 2018] - Graders wanted

[Jon Hermansen]

Hey Alyssa,

I'd love to participate, sign me up.

I'm a long time user of Jenkins, was co-organizer of the LA JAM, and more
recently became the maintainer for a Jenkins plugin. I'd really like to
take this opportunity to learn even more about Jenkins and related
technologies. I also love reading and going to conferences. I believe we
met at Jenkins World a few years ago.

Thanks!

On Fri, Apr 13, 2018 at 12:09 PM Alyssa Tong  wrote:

> Hello,
>
> I am looking for additional graders to join the Jenkins World (JW) review
> committee to help grade Jenkins World 2018 SF & EU proposals.
>
> Time commitment expected:
>
>- JW SF: 137 Jenkins submissions.
>- JW EU: 76 Jenkins submissions at the moment but most likely will
>increase after close of CFP this Sunday.
>
> What you get:
>
>- Pix, bio on the Committee webpage (part of JW website)
>- JW swag
>- Free conference ticket to JW
>
> Criteria:
>
>- You love to read and has a keen mind for the latest and greatest,
>trendy technical topics
>
> Pls respond to this thread if you're interested.
>
> 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/CAC9wNaxGJ-r-Jz%3D1Nyx7otR0TsHEYDPR-V-sR%2B%3D5JRCTsZNbRw%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/CANpo23KbaWiTv4gDQxXX99bcZKYninJTq9uyE%2B3is0vrBgX_-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Another "can't release plugin" thread

[Emory Penney]

If at first you don't succeed, try, try again!  53rd time was the charm and
my plugin is released!  Well, there went my Friday, have a good weekend!

On Fri, Apr 13, 2018 at 3:23 PM, Emory Penney 
wrote:

> Alright, it looks like my "ProxyCommand" in my ssh config wasn't correct,
> believe it or not it was your comment about the ssh-agent that sent me in
> that direction so, thanks!  I don't know why it worked with git pushes and
> not with Maven but correcting that has gotten me a bit further and I'm not
> going to question it at this point.  Now I've got a new issue, I don't seem
> to be able to get through the deploy portion of the release:
>
> Uploading to maven.jenkins-ci.org: https://repo.jenkins-ci.org/
> releases/org/jenkins-ci/plugins/startup-trigger-
> plugin/2.9.1/startup-trigger-plugin-2.9.1.pom
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 40.998 s
> [INFO] Finished at: 2018-04-13T14:43:20-07:00
> [INFO] 
> 
> *[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
> on project startup-trigger-plugin: Failed to deploy artifacts: Could not
> transfer artifact org.jenkins-ci.plugins:startup-trigger-plugin:hpi:2.9.1
> from/to maven.jenkins-ci.org 
> (https://repo.jenkins-ci.org/releases/
> ): Failed to transfer file:
> https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/startup-trigger-plugin/2.9.1/startup-trigger-plugin-2.9.1.hpi
> .
> Return code is: 401, ReasonPhrase: . -> [Help 1]*
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/
> MojoExecutionException
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 04:00 min
> [INFO] Finished at: 2018-04-13T14:43:20-07:00
> [INFO] 
> 
> [ERROR] Failed to execute goal org.apache.maven.plugins:
> maven-release-plugin:2.5.3:perform (default-cli) on project
> startup-trigger-plugin: Maven execution failed, exit code: '1' -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/
> MojoExecutionException
>
>
> Now I've just spent the last 30 minutes spinning my wheels running "mvn
> deploy" repeatedly trying to get it right... I'm certain I have the
> password correct.  I iterated the version number a few times to make sure I
> wasn't re-uploading a version that had already been uploaded.  The *deploy
> *goal errors basically the same way only the failing URL is
> https://repo.jenkins-ci.org/*snapshots/*org/jenkins-ci/
> plugins/startup-trigger-plugin/2.9.2-SNAPSHOT/startup-
> trigger-plugin-2.9.2-20180413.220421-1.hpi  I noticed
> https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/
> *startup-trigger-plugin* doesn't exist, but I think that may be a red
> herring.
>
> I'm going to try iterating the version one more time, but I'm open to
> suggestions about why this may not be working?  I haven't released this
> plugin in over a year and I wonder if there's some new process I may have
> not signed up for yet?
>
>
> On Fri, Apr 13, 2018 at 2:47 PM, Slide  wrote:
>
>> Can you verify that the scm setup in your pom.xml matches what you are
>> expecting it to be with your plain git push commands that you are running
>> on the command line? Maven will use the configuration from the 
>> section in your pom.xml for the release process.
>>
>> On Fri, Apr 13, 2018 at 2:14 PM Emory Penney 
>> wrote:
>>
>>> Well, I just verified my ssh-agent is running and my key is loaded, but
>>> the same error as above persists.  The error says connection attempted to
>>> timeout, wouldn't I be getting an authentication error if there was
>>> something wrong with my key?  And again, straight *git push *works,
>>> it's only 

Re: Upcoming JEP for usage of Incrementals repository

[Jesse Glick]

Filed a draft request:

https://github.com/jenkinsci/jep/pull/84

-- 
You received this message because you are subscribed to the Google 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/CANfRfr2GPoCqEBvr4yKEcKtm59%2BJ_8p4NCPmUN%3Du4Swbus%3DEuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Another "can't release plugin" thread

[Emory Penney]

Alright, it looks like my "ProxyCommand" in my ssh config wasn't correct,
believe it or not it was your comment about the ssh-agent that sent me in
that direction so, thanks!  I don't know why it worked with git pushes and
not with Maven but correcting that has gotten me a bit further and I'm not
going to question it at this point.  Now I've got a new issue, I don't seem
to be able to get through the deploy portion of the release:

Uploading to maven.jenkins-ci.org:
https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/startup-trigger-plugin/2.9.1/startup-trigger-plugin-2.9.1.pom
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 40.998 s
[INFO] Finished at: 2018-04-13T14:43:20-07:00
[INFO]

*[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy)
on project startup-trigger-plugin: Failed to deploy artifacts: Could not
transfer artifact org.jenkins-ci.plugins:startup-trigger-plugin:hpi:2.9.1
from/to maven.jenkins-ci.org 
(https://repo.jenkins-ci.org/releases/
): Failed to transfer file:
https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/startup-trigger-plugin/2.9.1/startup-trigger-plugin-2.9.1.hpi
.
Return code is: 401, ReasonPhrase: . -> [Help 1]*
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 04:00 min
[INFO] Finished at: 2018-04-13T14:43:20-07:00
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli)
on project startup-trigger-plugin: Maven execution failed, exit code: '1'
-> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException


Now I've just spent the last 30 minutes spinning my wheels running "mvn
deploy" repeatedly trying to get it right... I'm certain I have the
password correct.  I iterated the version number a few times to make sure I
wasn't re-uploading a version that had already been uploaded.  The
*deploy *goal
errors basically the same way only the failing URL is
https://repo.jenkins-ci.org/*snapshots/*org/jenkins-ci/plugins/startup-trigger-plugin/2.9.2-SNAPSHOT/startup-trigger-plugin-2.9.2-20180413.220421-1.hpi
I noticed https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/
*startup-trigger-plugin* doesn't exist, but I think that may be a red
herring.

I'm going to try iterating the version one more time, but I'm open to
suggestions about why this may not be working?  I haven't released this
plugin in over a year and I wonder if there's some new process I may have
not signed up for yet?


On Fri, Apr 13, 2018 at 2:47 PM, Slide  wrote:

> Can you verify that the scm setup in your pom.xml matches what you are
> expecting it to be with your plain git push commands that you are running
> on the command line? Maven will use the configuration from the 
> section in your pom.xml for the release process.
>
> On Fri, Apr 13, 2018 at 2:14 PM Emory Penney 
> wrote:
>
>> Well, I just verified my ssh-agent is running and my key is loaded, but
>> the same error as above persists.  The error says connection attempted to
>> timeout, wouldn't I be getting an authentication error if there was
>> something wrong with my key?  And again, straight *git push *works, it's
>> only failing when I run through maven...  The "connection timeout" message
>> leads me to believe this has something to do with the proxy but I can't
>> fathom why Git would be ignoring my proxy settings when called by Maven.
>>
>>
>> On Friday, April 13, 2018 at 12:41:50 PM UTC-7, Emory Penney wrote:
>>>
>>> Yes I did, that resulted in the error indicating my username was an
>>> invalid hostname. I'd be happy to 

Re: Another "can't release plugin" thread

[Slide]

Can you verify that the scm setup in your pom.xml matches what you are
expecting it to be with your plain git push commands that you are running
on the command line? Maven will use the configuration from the 
section in your pom.xml for the release process.

On Fri, Apr 13, 2018 at 2:14 PM Emory Penney  wrote:

> Well, I just verified my ssh-agent is running and my key is loaded, but
> the same error as above persists.  The error says connection attempted to
> timeout, wouldn't I be getting an authentication error if there was
> something wrong with my key?  And again, straight *git push *works, it's
> only failing when I run through maven...  The "connection timeout" message
> leads me to believe this has something to do with the proxy but I can't
> fathom why Git would be ignoring my proxy settings when called by Maven.
>
>
> On Friday, April 13, 2018 at 12:41:50 PM UTC-7, Emory Penney wrote:
>>
>> Yes I did, that resulted in the error indicating my username was an
>> invalid hostname. I'd be happy to try to figure that method out if it would
>> work better...
>>
>> On Fri, Apr 13, 2018, 12:38 Slide  wrote:
>>
>>> Just to be clear, you did -Dusername= -Dpassword=
>>> correct?
>>>
>>> On Fri, Apr 13, 2018 at 12:34 PM Emory Penney 
>>> wrote:
>>>
 I know there are a bunch of threads on this but I haven't found any
 feedback in any of the existing threads that helped me resolve this at
 all.  Releases fail to push to GIT during prepare:

 [INFO] Working directory:
 C:\Users\ejpenney\Desktop\startup-trigger-plugin
 [INFO] Executing: cmd.exe /X /C "git push 
 g...@github.com:jenkinsci/startup-trigger-plugin.git
 refs/heads/master:refs/heads/master"
 [INFO] Working directory:
 C:\Users\ejpenney\Desktop\startup-trigger-plugin
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 02:55 min
 [INFO] Finished at: 2018-04-13T12:21:00-07:00
 [INFO]
 
 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli)
 on project startup-trigger-plugin: Unable to commit files
 [ERROR] Provider message:
 [ERROR] The git-push command failed.
 [ERROR] Command output:

 *[ERROR] ssh: connect to host github.com  port 22:
 Connection timed out[ERROR] fatal: Could not read from remote repository.*
 [ERROR]
 [ERROR] Please make sure you have the correct access rights
 [ERROR] and the repository exists.
 [ERROR]
 [ERROR] -> [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with
 the -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

 I'm running Maven 3.5.3 on Windows 10, with Git for Windows (MSYS
 2.16.2-windows.1).  The Jenkins Support Wiki
 indicates
 this could be a problem with Tortoise GIT, which I do not have installed,
 so I can't utilize the documented work around.  If I specify -*Dusername
 *and -*Dpassword *on the command line then I get the error where it
 says my username is not a valid hostname so I've set my username and
 password in the Maven settings.xml.

 I'm running behind an http_proxy (that does not require
 authentication).  I've set all the usual environment variables to point at
 my proxy (ALL_PROXY, HTTPS_PROXY, HTTP_PROXY, FTP_PROXY).  I've configured
 maven to use the proxy in settings.xml.  I've set git config --system
 http.proxy as well as --global.  As a matter of fact, *mvn install*
 and *git push* work just fine.  It only fails during release:prepare.
 Read that again: Git pulls and pushes work fine UNLESS they're happening
 from inside Maven.

 What the heck am I missing?  Why can't GIT connect?

 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/34afdb62-a0ea-4ce9-bdb3-f0bbf0c9d7fc%40googlegroups.com
 
 .
 

Re: Another "can't release plugin" thread

[Emory Penney]

Well, I just verified my ssh-agent is running and my key is loaded, but the 
same error as above persists.  The error says connection attempted to 
timeout, wouldn't I be getting an authentication error if there was 
something wrong with my key?  And again, straight *git push *works, it's 
only failing when I run through maven...  The "connection timeout" message 
leads me to believe this has something to do with the proxy but I can't 
fathom why Git would be ignoring my proxy settings when called by Maven.

On Friday, April 13, 2018 at 12:41:50 PM UTC-7, Emory Penney wrote:
>
> Yes I did, that resulted in the error indicating my username was an 
> invalid hostname. I'd be happy to try to figure that method out if it would 
> work better...
>
> On Fri, Apr 13, 2018, 12:38 Slide  wrote:
>
>> Just to be clear, you did -Dusername= -Dpassword= 
>> correct?
>>
>> On Fri, Apr 13, 2018 at 12:34 PM Emory Penney  
>> wrote:
>>
>>> I know there are a bunch of threads on this but I haven't found any 
>>> feedback in any of the existing threads that helped me resolve this at 
>>> all.  Releases fail to push to GIT during prepare:
>>>
>>> [INFO] Working directory: 
>>> C:\Users\ejpenney\Desktop\startup-trigger-plugin
>>> [INFO] Executing: cmd.exe /X /C "git push 
>>> g...@github.com:jenkinsci/startup-trigger-plugin.git 
>>> refs/heads/master:refs/heads/master"
>>> [INFO] Working directory: 
>>> C:\Users\ejpenney\Desktop\startup-trigger-plugin
>>> [INFO] 
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO] 
>>> 
>>> [INFO] Total time: 02:55 min
>>> [INFO] Finished at: 2018-04-13T12:21:00-07:00
>>> [INFO] 
>>> 
>>> [ERROR] Failed to execute goal 
>>> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) 
>>> on project startup-trigger-plugin: Unable to commit files
>>> [ERROR] Provider message:
>>> [ERROR] The git-push command failed.
>>> [ERROR] Command output:
>>>
>>> *[ERROR] ssh: connect to host github.com  port 22: 
>>> Connection timed out[ERROR] fatal: Could not read from remote repository.*
>>> [ERROR]
>>> [ERROR] Please make sure you have the correct access rights
>>> [ERROR] and the repository exists.
>>> [ERROR]
>>> [ERROR] -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the 
>>> -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions, 
>>> please read the following articles:
>>> [ERROR] [Help 1] 
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>>
>>> I'm running Maven 3.5.3 on Windows 10, with Git for Windows (MSYS 
>>> 2.16.2-windows.1).  The Jenkins Support Wiki 
>>> indicates this 
>>> could be a problem with Tortoise GIT, which I do not have installed, so I 
>>> can't utilize the documented work around.  If I specify -*Dusername *and 
>>> -*Dpassword *on the command line then I get the error where it says my 
>>> username is not a valid hostname so I've set my username and password in 
>>> the Maven settings.xml.
>>>
>>> I'm running behind an http_proxy (that does not require 
>>> authentication).  I've set all the usual environment variables to point at 
>>> my proxy (ALL_PROXY, HTTPS_PROXY, HTTP_PROXY, FTP_PROXY).  I've configured 
>>> maven to use the proxy in settings.xml.  I've set git config --system 
>>> http.proxy as well as --global.  As a matter of fact, *mvn install* and 
>>> *git 
>>> push* work just fine.  It only fails during release:prepare.  Read that 
>>> again: Git pulls and pushes work fine UNLESS they're happening from inside 
>>> Maven.
>>>
>>> What the heck am I missing?  Why can't GIT connect?
>>>
>>> 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/34afdb62-a0ea-4ce9-bdb3-f0bbf0c9d7fc%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/1FDdo2h2wug/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> 

Re: Jenkins External Artifact Storage core changes in LTS

[R. Tyler Croy]

(replies inline)

On Fri, 13 Apr 2018, Oliver Gond??a wrote:

> On 2018-04-13 18:23, Carlos Sanchez wrote:
> > Hi Oliver,
> > 
> > There are some changes for core that would be really helpful to have in
> > hands of people for testing sooner than later
> > 
> > https://github.com/jenkinsci/jenkins/pull/3302
> > 
> > All new methods are marked with the new @Beta annotation so it should be
> > clear that it's not final.
> > 
> > We expect this to be in the next weekly or so,but I would really like to
> > ensure we can pull this into the next LTS if at all possible,what can I
> > do to help prepare these changes for the LTS,even if we tried to
> > backport it?
> 
> Hi, Let's make the discussion public.
> 
> My personal take is the LTS and Beta.class are quite orthogonal in
> principle. When it comes to the actual change, it feels far from trivial for
> such an exception IMO. What is the motivation here? Backporting this will
> get it in LTS in 4 weeks, otherwise it will get in in 8 weeks.
> 
> Thoughts? I would really like to avoid backporting something before it has
> its final shape (IOW, merged to master).


Hey Oliver, I was chatting with Carlos about this earlier and encouraged him to
reach out to you to better understand your thoughts for considering code coming
into the LTS.

>From my understanding of what Carlos is asking about, is not pulling anything
into an LTS which isn't already in a Weekly release. Rather, I think Carlos is
apprehensive about the timing between Weekly releases and LTS, and is worried
about missing the last Weekly before our typical 2-weeks-before LTS cutoff."

I think Carlos's team has worked quite hard to get the underlying code to
enable external artifacts ready, and considers one indication of "success" to
have that code delivered in our next LTS cycle, since LTSes are consumed by the
vast majority of Jenkins users who would benefit from this functionality.


I *hope* I've captured the situation clearly.


The questions Carlos has about LTS timing I think are all moot assuming that
the aforementioned pull request gets reviewed and merged in a timely manner for
next week's release (from my understanding).



Cheers

-- 
You received this message because you are subscribed to the Google 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/20180413200804.GD1836%40grape.lasagna.io.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: PGP signature

Re: Another "can't release plugin" thread

[Emory Penney]

Yes I did, that resulted in the error indicating my username was an invalid
hostname. I'd be happy to try to figure that method out if it would work
better...

On Fri, Apr 13, 2018, 12:38 Slide  wrote:

> Just to be clear, you did -Dusername= -Dpassword=
> correct?
>
> On Fri, Apr 13, 2018 at 12:34 PM Emory Penney 
> wrote:
>
>> I know there are a bunch of threads on this but I haven't found any
>> feedback in any of the existing threads that helped me resolve this at
>> all.  Releases fail to push to GIT during prepare:
>>
>> [INFO] Working directory: C:\Users\ejpenney\Desktop\startup-trigger-plugin
>> [INFO] Executing: cmd.exe /X /C "git push 
>> g...@github.com:jenkinsci/startup-trigger-plugin.git
>> refs/heads/master:refs/heads/master"
>> [INFO] Working directory: C:\Users\ejpenney\Desktop\startup-trigger-plugin
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 02:55 min
>> [INFO] Finished at: 2018-04-13T12:21:00-07:00
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli)
>> on project startup-trigger-plugin: Unable to commit files
>> [ERROR] Provider message:
>> [ERROR] The git-push command failed.
>> [ERROR] Command output:
>>
>> *[ERROR] ssh: connect to host github.com  port 22:
>> Connection timed out[ERROR] fatal: Could not read from remote repository.*
>> [ERROR]
>> [ERROR] Please make sure you have the correct access rights
>> [ERROR] and the repository exists.
>> [ERROR]
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>> I'm running Maven 3.5.3 on Windows 10, with Git for Windows (MSYS
>> 2.16.2-windows.1).  The Jenkins Support Wiki
>> indicates this
>> could be a problem with Tortoise GIT, which I do not have installed, so I
>> can't utilize the documented work around.  If I specify -*Dusername *and
>> -*Dpassword *on the command line then I get the error where it says my
>> username is not a valid hostname so I've set my username and password in
>> the Maven settings.xml.
>>
>> I'm running behind an http_proxy (that does not require authentication).
>> I've set all the usual environment variables to point at my proxy
>> (ALL_PROXY, HTTPS_PROXY, HTTP_PROXY, FTP_PROXY).  I've configured maven to
>> use the proxy in settings.xml.  I've set git config --system http.proxy as
>> well as --global.  As a matter of fact, *mvn install* and *git push*
>> work just fine.  It only fails during release:prepare.  Read that again:
>> Git pulls and pushes work fine UNLESS they're happening from inside Maven.
>>
>> What the heck am I missing?  Why can't GIT connect?
>>
>> 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/34afdb62-a0ea-4ce9-bdb3-f0bbf0c9d7fc%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/1FDdo2h2wug/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/CAPiUgVf2YUiX67br2xg%3DzPW9v0fEPDaq3Y705DYiAhD6eLW6cg%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: Another "can't release plugin" thread

[Slide]

Actually, now that I review [1] if you are using ssh with GitHub, it says
you must NOT specify those on the command line and that you have to setup
an ssh-agent for it to work.

1-
https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkins-ci.org

On Fri, Apr 13, 2018 at 12:38 PM Slide  wrote:

> Just to be clear, you did -Dusername= -Dpassword=
> correct?
>
> On Fri, Apr 13, 2018 at 12:34 PM Emory Penney 
> wrote:
>
>> I know there are a bunch of threads on this but I haven't found any
>> feedback in any of the existing threads that helped me resolve this at
>> all.  Releases fail to push to GIT during prepare:
>>
>> [INFO] Working directory: C:\Users\ejpenney\Desktop\startup-trigger-plugin
>> [INFO] Executing: cmd.exe /X /C "git push 
>> g...@github.com:jenkinsci/startup-trigger-plugin.git
>> refs/heads/master:refs/heads/master"
>> [INFO] Working directory: C:\Users\ejpenney\Desktop\startup-trigger-plugin
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 02:55 min
>> [INFO] Finished at: 2018-04-13T12:21:00-07:00
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli)
>> on project startup-trigger-plugin: Unable to commit files
>> [ERROR] Provider message:
>> [ERROR] The git-push command failed.
>> [ERROR] Command output:
>>
>> *[ERROR] ssh: connect to host github.com  port 22:
>> Connection timed out[ERROR] fatal: Could not read from remote repository.*
>> [ERROR]
>> [ERROR] Please make sure you have the correct access rights
>> [ERROR] and the repository exists.
>> [ERROR]
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>> I'm running Maven 3.5.3 on Windows 10, with Git for Windows (MSYS
>> 2.16.2-windows.1).  The Jenkins Support Wiki
>> indicates this
>> could be a problem with Tortoise GIT, which I do not have installed, so I
>> can't utilize the documented work around.  If I specify -*Dusername *and
>> -*Dpassword *on the command line then I get the error where it says my
>> username is not a valid hostname so I've set my username and password in
>> the Maven settings.xml.
>>
>> I'm running behind an http_proxy (that does not require authentication).
>> I've set all the usual environment variables to point at my proxy
>> (ALL_PROXY, HTTPS_PROXY, HTTP_PROXY, FTP_PROXY).  I've configured maven to
>> use the proxy in settings.xml.  I've set git config --system http.proxy as
>> well as --global.  As a matter of fact, *mvn install* and *git push*
>> work just fine.  It only fails during release:prepare.  Read that again:
>> Git pulls and pushes work fine UNLESS they're happening from inside Maven.
>>
>> What the heck am I missing?  Why can't GIT connect?
>>
>> 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/34afdb62-a0ea-4ce9-bdb3-f0bbf0c9d7fc%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/CAPiUgVedrHx_SR0u28Qi%3DwzoBknFUNrgim%2BxUq-P5StFOwxZnw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Another "can't release plugin" thread

[Slide]

Just to be clear, you did -Dusername= -Dpassword=
correct?

On Fri, Apr 13, 2018 at 12:34 PM Emory Penney 
wrote:

> I know there are a bunch of threads on this but I haven't found any
> feedback in any of the existing threads that helped me resolve this at
> all.  Releases fail to push to GIT during prepare:
>
> [INFO] Working directory: C:\Users\ejpenney\Desktop\startup-trigger-plugin
> [INFO] Executing: cmd.exe /X /C "git push 
> g...@github.com:jenkinsci/startup-trigger-plugin.git
> refs/heads/master:refs/heads/master"
> [INFO] Working directory: C:\Users\ejpenney\Desktop\startup-trigger-plugin
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 02:55 min
> [INFO] Finished at: 2018-04-13T12:21:00-07:00
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli)
> on project startup-trigger-plugin: Unable to commit files
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
>
> *[ERROR] ssh: connect to host github.com  port 22:
> Connection timed out[ERROR] fatal: Could not read from remote repository.*
> [ERROR]
> [ERROR] Please make sure you have the correct access rights
> [ERROR] and the repository exists.
> [ERROR]
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
> I'm running Maven 3.5.3 on Windows 10, with Git for Windows (MSYS
> 2.16.2-windows.1).  The Jenkins Support Wiki
> indicates this
> could be a problem with Tortoise GIT, which I do not have installed, so I
> can't utilize the documented work around.  If I specify -*Dusername *and 
> -*Dpassword
> *on the command line then I get the error where it says my username is
> not a valid hostname so I've set my username and password in the Maven
> settings.xml.
>
> I'm running behind an http_proxy (that does not require authentication).
> I've set all the usual environment variables to point at my proxy
> (ALL_PROXY, HTTPS_PROXY, HTTP_PROXY, FTP_PROXY).  I've configured maven to
> use the proxy in settings.xml.  I've set git config --system http.proxy as
> well as --global.  As a matter of fact, *mvn install* and *git push* work
> just fine.  It only fails during release:prepare.  Read that again: Git
> pulls and pushes work fine UNLESS they're happening from inside Maven.
>
> What the heck am I missing?  Why can't GIT connect?
>
> 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/34afdb62-a0ea-4ce9-bdb3-f0bbf0c9d7fc%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/CAPiUgVf2YUiX67br2xg%3DzPW9v0fEPDaq3Y705DYiAhD6eLW6cg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Another "can't release plugin" thread

[Emory Penney]

I know there are a bunch of threads on this but I haven't found any 
feedback in any of the existing threads that helped me resolve this at 
all.  Releases fail to push to GIT during prepare:

[INFO] Working directory: C:\Users\ejpenney\Desktop\startup-trigger-plugin
[INFO] Executing: cmd.exe /X /C "git push 
g...@github.com:jenkinsci/startup-trigger-plugin.git 
refs/heads/master:refs/heads/master"
[INFO] Working directory: C:\Users\ejpenney\Desktop\startup-trigger-plugin
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 02:55 min
[INFO] Finished at: 2018-04-13T12:21:00-07:00
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) 
on project startup-trigger-plugin: Unable to commit files
[ERROR] Provider message:
[ERROR] The git-push command failed.
[ERROR] Command output:

*[ERROR] ssh: connect to host github.com port 22: Connection timed 
out[ERROR] fatal: Could not read from remote repository.*
[ERROR]
[ERROR] Please make sure you have the correct access rights
[ERROR] and the repository exists.
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

I'm running Maven 3.5.3 on Windows 10, with Git for Windows (MSYS 
2.16.2-windows.1).  The Jenkins Support Wiki 
indicates this 
could be a problem with Tortoise GIT, which I do not have installed, so I 
can't utilize the documented work around.  If I specify -*Dusername *and 
-*Dpassword 
*on the command line then I get the error where it says my username is not 
a valid hostname so I've set my username and password in the Maven 
settings.xml.

I'm running behind an http_proxy (that does not require authentication).  
I've set all the usual environment variables to point at my proxy 
(ALL_PROXY, HTTPS_PROXY, HTTP_PROXY, FTP_PROXY).  I've configured maven to 
use the proxy in settings.xml.  I've set git config --system http.proxy as 
well as --global.  As a matter of fact, *mvn install* and *git push* work 
just fine.  It only fails during release:prepare.  Read that again: Git 
pulls and pushes work fine UNLESS they're happening from inside Maven.

What the heck am I missing?  Why can't GIT connect?

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/34afdb62-a0ea-4ce9-bdb3-f0bbf0c9d7fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins External Artifact Storage core changes in LTS

[Oliver Gondža]

On 2018-04-13 18:23, Carlos Sanchez wrote:

Hi Oliver,

There are some changes for core that would be really helpful to have in 
hands of people for testing sooner than later


https://github.com/jenkinsci/jenkins/pull/3302

All new methods are marked with the new @Beta annotation so it should be 
clear that it's not final.


We expect this to be in the next weekly or so,but I would really like to 
ensure we can pull this into the next LTS if at all possible,what can I 
do to help prepare these changes for the LTS,even if we tried to 
backport it?


Hi, Let's make the discussion public.

My personal take is the LTS and Beta.class are quite orthogonal in 
principle. When it comes to the actual change, it feels far from trivial 
for such an exception IMO. What is the motivation here? Backporting this 
will get it in LTS in 4 weeks, otherwise it will get in in 8 weeks.


Thoughts? I would really like to avoid backporting something before it 
has its final shape (IOW, merged to master).

--
oliver

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

Re: [Jenkins World 2018] - Graders wanted

[Adrien Lecharpentier]

I'd be happy to help as well. I submitted a subject to the French CFP, I
don't know if that makes me inadmissible for the review.

-- Adrien

Le ven. 13 avr. 2018 à 20:46, Michael Pailloncy 
a écrit :

> Hi Alyssa,
>
> I would be very happy to help.
>
> Cheers
> Michaël
>
>
> On Fri, Apr 13, 2018 at 6:09 PM, Alyssa Tong  wrote:
>
>> Hello,
>>
>> I am looking for additional graders to join the Jenkins World (JW) review
>> committee to help grade Jenkins World 2018 SF & EU proposals.
>>
>> Time commitment expected:
>>
>>- JW SF: 137 Jenkins submissions.
>>- JW EU: 76 Jenkins submissions at the moment but most likely will
>>increase after close of CFP this Sunday.
>>
>> What you get:
>>
>>- Pix, bio on the Committee webpage (part of JW website)
>>- JW swag
>>- Free conference ticket to JW
>>
>> Criteria:
>>
>>- You love to read and has a keen mind for the latest and greatest,
>>trendy technical topics
>>
>> Pls respond to this thread if you're interested.
>>
>> 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/CAC9wNaxGJ-r-Jz%3D1Nyx7otR0TsHEYDPR-V-sR%2B%3D5JRCTsZNbRw%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 Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAPO77c1Lu0C4zH%3D7dV1n%3DeDgixovk9LLWdhzGTB8N-HmYKpvdg%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/CAKwJSvxVSJm5vGb4Ls97TXPgHX%3DgBLWRqczL_sB5Wo29_%3DG92A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Jenkins World 2018] - Graders wanted

[Alyssa Tong]

Hello,

I am looking for additional graders to join the Jenkins World (JW) review
committee to help grade Jenkins World 2018 SF & EU proposals.

Time commitment expected:

   - JW SF: 137 Jenkins submissions.
   - JW EU: 76 Jenkins submissions at the moment but most likely will
   increase after close of CFP this Sunday.

What you get:

   - Pix, bio on the Committee webpage (part of JW website)
   - JW swag
   - Free conference ticket to JW

Criteria:

   - You love to read and has a keen mind for the latest and greatest,
   trendy technical topics

Pls respond to this thread if you're interested.

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/CAC9wNaxGJ-r-Jz%3D1Nyx7otR0TsHEYDPR-V-sR%2B%3D5JRCTsZNbRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: External Artifact Storage

[Carlos Sanchez]

PR submitted at https://github.com/jenkinsci/jep/pull/83

On Fri, Apr 13, 2018 at 5:24 PM, Oleg Nenashev 
wrote:

> Looks good to me **as a DRAFT**.
> Please propose a pull request so that JEP editors can review it.
>
> We also need somebody to be selected as BDFL Delegate if KK is not
> available to review it.
>
> BR, Oleg
>
>
> On Friday, April 13, 2018 at 4:25:38 AM UTC+2, Jesse Glick wrote:
>>
>> +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/0851cc7d-d3cc-4da9-8a76-b841817e38da%
> 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/CALHFn6P6vQxzVXmLLQnff7CFeOTYbC6aF7OmM-KVBM%2BXwGPbjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: External Artifact Storage

[Oleg Nenashev]

Looks good to me **as a DRAFT**.
Please propose a pull request so that JEP editors can review it.

We also need somebody to be selected as BDFL Delegate if KK is not 
available to review it.

BR, Oleg


On Friday, April 13, 2018 at 4:25:38 AM UTC+2, Jesse Glick wrote:
>
> +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/0851cc7d-d3cc-4da9-8a76-b841817e38da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Jesse Glick]

On Fri, Apr 13, 2018 at 1:14 AM,  wrote:
> Is "when" also possible in scripted pipelines?

You would just use `if` statements and the like.

-- 
You received this message because you are subscribed to the Google 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/CANfRfr051Mhd8PtLfdbDzq5GFZbGFMgqwVQFAZ4CCrh88%3D%3D6tA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to become maintainer of the statistics-gatherer-plugin

[Luca Milanesio]

PIng ... any news from the current Maintainers?
Are we set for end of next week to make a decision on this?

Luca.

> On 10 Apr 2018, at 08:07, Luca Milanesio  wrote:
> 
> 2 weeks sound good to me, and yes, I always avoid forks :-)
> 
> Luca.
> 
>> On 10 Apr 2018, at 08:02, Joseph P  wrote:
>> 
>> Usually the wait period is 2 weeks :) I would not recommend creating another 
>> 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/8b9ce146-6cf1-4b5a-a702-108ffe540d29%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/F344B6F7-7224-455F-BC60-693F0C8AC51F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins X status

[Rob Davies]

Whilst the Jenkins X JEP proposal is still under consideration 
 -  I 
thought it would be worthwhile giving a quick summary of where we stand 
with the project.
There's actually a great summary of community stats done in a generated 
 blog using jenkins-X but 
the hlighlights include  integration with Github issues, GitHub Enterprise 
and Jira. Continued development of BitBucket and Gitea integrations. We 
have gained 10 new commiiters and 18 new contributors - which is fantastic 
- but we would love more! Work is being undertaken on integrating An
https://github.com/anchorechore for validation of container images in 
pipelines. Anchore also have a Jenkins plugin.

Rob

-- 
You received this message because you are subscribed to the Google 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/972146ce-6eb3-471f-8b74-d70614e6bb87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[thorsten . hoeger]

I think this will be a way to support those two features. Is "when" also 
possible in scripted pipelines?

Am Donnerstag, 12. April 2018 11:13:28 UTC+2 schrieb 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-de...@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: rsan...@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/395f2158-3934-43c4-885e-ee834e4950c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to be made a maintainer of audit-trail-plugin

[tomasz . sek . 88]

Hi

Any updates?

Cheers,
Tomasz

-- 
You received this message because you are subscribed to the Google 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/1263e546-1aad-409a-bc10-75330b8fa609%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.