Re: Jelly script changelogset date issue with Mercurial plugin

[Oleg Nenashev]

So, somebody needs to create a bug to the core

вторник, 27 июня 2017 г., 0:18:22 UTC+2 пользователь Jesse Glick написал:
>
> On Mon, Jun 26, 2017 at 6:04 PM, Daniel Beck  > wrote: 
> > That's a long. I think this asks for how to get a human readable date. 
>
> Yes, I left that as an exercise for the reader. My point was that this 
> is the generic API implemented by all SCMs, so there is no special 
> consideration for the `mercurial` 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/577be9e2-334d-404e-be7e-c6a5405cf3f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Password reset isn't working

[Oleg Nenashev]

Added the infra team to Cc

четверг, 22 июня 2017 г., 20:07:46 UTC+2 пользователь cmo...@xactlycorp.com 
написал:
>
> I tried to reset my password but I am not receiving the email and now I 
> can't get in. Can an administrator help me with this problem?
>
>
>
> [image: What's New with Xactly] 
>
>   [image: LinkedIn] 
>   [image: Twitter] 
>   [image: Facebook] 
>   [image: YouTube] 
> 

-- 
You received this message because you are 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/4d99632b-660e-48b5-a619-d075fef9afd9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Due to the spam problem, we will need additional verification for your sign-up request.

[Oleg Nenashev]

Likely we just missed this request.
Could you please ping again in the thread?

понедельник, 26 июня 2017 г., 16:37:08 UTC+2 пользователь 
snobb...@gmail.com написал:
>
> I've been trying to create an account via this page 
> https://accounts.jenkins.io/signup, but I get an error redirecting me to 
> this page 
> https://wiki.jenkins-ci.org/display/JENKINS/User+Account+on+Jenkins
> I've tried mailing jenkinsci...@googlegroups.com  as 
> recommended on that page, but I haven't got any response from that mailing 
> list.
> Is there somewhere else I can go to get set up with an account?
>
> Thanks
>
> On Thursday, April 27, 2017 at 10:56:05 PM UTC+1, Christopher wrote:
>>
>> On Thu, 27 Apr 2017, at 07:51, Dikla wrote: 
>> > Please create my account: 
>> > 
>> > User ID: dikla_sahar 
>>
>> This is the wrong place to post this; please read the instructions 
>> again: 
>> https://wiki.jenkins-ci.org/display/JENKINS/User+Account+on+Jenkins 
>>
>

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

Re: GitHub and Bitbucket branch source UI refactoring

[kshultz]

JFYI. I opened JENKINS-45242 
 to capture the private 
versus public repos problem that Mark and I have observed.

--Karl

On Friday, June 30, 2017 at 10:20:07 AM UTC-4, ksh...@cloudbees.com wrote:
>
> Mark, good catch. I've observed a similar thing. It's as though I'm unable 
> to see the private repos at all, using credentials which used to show them. 
>
> On Thursday, June 29, 2017 at 10:43:48 AM UTC-4, Mark Waite wrote:
>>
>> I think I have detected the difference between by multi-branch pipelines 
>> with GitHub branch sources.
>>
>> The problem job is a GitHub private repository (
>> https://github.com/MarkEWaite/jenkins-bugs-private), while the working 
>> job is a GitHub public repository (
>> https://github.com/MarkEWaite/jenkins-bugs) .
>>
>> When I configure the private repository job, it presents the list of 
>> repositories but only includes public repositories in the list.  The 
>> credentials are valid and are used in other jobs, but it is as though the 
>> list of repositories is not being refreshed with the credentials.
>>
>> Mark Waite
>>
>> On Thu, Jun 29, 2017 at 8:27 AM Mark Waite  wrote:
>>
>>> I'm using latest betas (as far as I can tell).  The GitHub source is now 
>>> working in the cases that were failing previously.  Thanks very much for 
>>> that!
>>>
>>> Unfortunately, when I open the "Configure" page for one of my 
>>> multi-branch pipeline job that is using GitHub as a branch source, it 
>>> reverts the repository choice to the top of the list, instead of showing 
>>> the originally selected repository.
>>>
>>> When I open the "Configure" page for another of my multi-branch pipeline 
>>> jobs that is using GitHub as a branch source, it retains the repository 
>>> choice.
>>>
>>> Unfortunately, I don't know what is different between those two cases of 
>>> a GitHub branch source for a multi-branch pipeline.
>>>
>>> I'll let you know if I identify key attributes which make the two cases 
>>> behave differently.
>>>
>>> Mark Waite 
>>>
>>>
>>> On Monday, June 26, 2017 at 10:04:00 PM UTC-6, Michael Neale wrote:

 I retested with latest betas and looking good (binary compat, migration 
 etc). 

 On Monday, June 26, 2017 at 11:46:49 PM UTC+10, Stephen Connolly wrote:
>
>
>
> On 26 June 2017 at 06:13, Kevin Burnett  
> wrote:
>
>> This is so good. :)
>>
>
> Great to hear it. I love feedback (+ve or -ve beats none)
>  
>
>>
>> The pre and post diffs looked right, and the new UI and functionality 
>> gives me everything that I was hoping for.
>>
>
> w00t
>  
>
>>
>> I'm going to remove the "discover pull requests from [everywhere]" 
>> behaviors and select "Only branches that are also filed as PRs" on 
>> production as soon as possible.
>>
>> Michael Neale mentioned that one issue he had seen "does look better 
>> now with the new version." I used the plugin versions that Stephen 
>> originally posted on June 20, but I take Michael's comment to mean there 
>> might be newer versions. Please make this irrelevant by issuing release 
>> versions of these plugins this week. :)
>>
>> Thanks a ton!
>> -KB
>>
>> On Friday, June 23, 2017 at 12:45:44 PM UTC-4, Stephen Connolly wrote:
>>>
>>>
>>>
>>> On 23 June 2017 at 17:24, Mark Waite  wrote:
>>>
 I see duplicate entries in the "Add' configuration of the Bitbucket 
 source for "Checkout over ssh".  Let me know if you need steps to see 
 that.

>>>
>>> Shouldn't... may just be a bug in the drop down populator when you 
>>> have GitHub and Bitbucket
>>>  
>>>

 I also wonder if the text "General", "Git" and "Bitbucket" should 
 be italicized, or bold, or separated with dashes, or something, so 
 that the 
 user has a concept that things will be appearing under them.  They 
 seem to 
 be standard text currently, and it wasn't obvious to me that they were 
 categories into which settings would be placed.

>>>
>>> Cannot style the drop-down menu without significant JS changes that 
>>> risk affecting form binding.
>>>  
>>>

 Mark Waite


 On Friday, June 23, 2017 at 9:58:52 AM UTC-6, Mark Waite wrote:
>
> The UI experience has been great for me in the two or three places 
> where I've used it.  I was a little surprised (and pleased) with the 
> adaptation that the local branch setting is now a toggle.  I think 
> that's 
> the right approach, since (as far as I can tell) that is the 99% use 
> case.
>
> Earlier I reported an NPE when configuring a multi-branch pipeline 
> that uses GitHub 

Re: GitHub and Bitbucket branch source UI refactoring

[kshultz]

Mark, good catch. I've observed a similar thing. It's as though I'm unable 
to see the private repos at all, using credentials which used to show them. 

On Thursday, June 29, 2017 at 10:43:48 AM UTC-4, Mark Waite wrote:
>
> I think I have detected the difference between by multi-branch pipelines 
> with GitHub branch sources.
>
> The problem job is a GitHub private repository (
> https://github.com/MarkEWaite/jenkins-bugs-private), while the working 
> job is a GitHub public repository (
> https://github.com/MarkEWaite/jenkins-bugs) .
>
> When I configure the private repository job, it presents the list of 
> repositories but only includes public repositories in the list.  The 
> credentials are valid and are used in other jobs, but it is as though the 
> list of repositories is not being refreshed with the credentials.
>
> Mark Waite
>
> On Thu, Jun 29, 2017 at 8:27 AM Mark Waite  > wrote:
>
>> I'm using latest betas (as far as I can tell).  The GitHub source is now 
>> working in the cases that were failing previously.  Thanks very much for 
>> that!
>>
>> Unfortunately, when I open the "Configure" page for one of my 
>> multi-branch pipeline job that is using GitHub as a branch source, it 
>> reverts the repository choice to the top of the list, instead of showing 
>> the originally selected repository.
>>
>> When I open the "Configure" page for another of my multi-branch pipeline 
>> jobs that is using GitHub as a branch source, it retains the repository 
>> choice.
>>
>> Unfortunately, I don't know what is different between those two cases of 
>> a GitHub branch source for a multi-branch pipeline.
>>
>> I'll let you know if I identify key attributes which make the two cases 
>> behave differently.
>>
>> Mark Waite 
>>
>>
>> On Monday, June 26, 2017 at 10:04:00 PM UTC-6, Michael Neale wrote:
>>>
>>> I retested with latest betas and looking good (binary compat, migration 
>>> etc). 
>>>
>>> On Monday, June 26, 2017 at 11:46:49 PM UTC+10, Stephen Connolly wrote:



 On 26 June 2017 at 06:13, Kevin Burnett  
 wrote:

> This is so good. :)
>

 Great to hear it. I love feedback (+ve or -ve beats none)
  

>
> The pre and post diffs looked right, and the new UI and functionality 
> gives me everything that I was hoping for.
>

 w00t
  

>
> I'm going to remove the "discover pull requests from [everywhere]" 
> behaviors and select "Only branches that are also filed as PRs" on 
> production as soon as possible.
>
> Michael Neale mentioned that one issue he had seen "does look better 
> now with the new version." I used the plugin versions that Stephen 
> originally posted on June 20, but I take Michael's comment to mean there 
> might be newer versions. Please make this irrelevant by issuing release 
> versions of these plugins this week. :)
>
> Thanks a ton!
> -KB
>
> On Friday, June 23, 2017 at 12:45:44 PM UTC-4, Stephen Connolly wrote:
>>
>>
>>
>> On 23 June 2017 at 17:24, Mark Waite  wrote:
>>
>>> I see duplicate entries in the "Add' configuration of the Bitbucket 
>>> source for "Checkout over ssh".  Let me know if you need steps to see 
>>> that.
>>>
>>
>> Shouldn't... may just be a bug in the drop down populator when you 
>> have GitHub and Bitbucket
>>  
>>
>>>
>>> I also wonder if the text "General", "Git" and "Bitbucket" should be 
>>> italicized, or bold, or separated with dashes, or something, so that 
>>> the 
>>> user has a concept that things will be appearing under them.  They seem 
>>> to 
>>> be standard text currently, and it wasn't obvious to me that they were 
>>> categories into which settings would be placed.
>>>
>>
>> Cannot style the drop-down menu without significant JS changes that 
>> risk affecting form binding.
>>  
>>
>>>
>>> Mark Waite
>>>
>>>
>>> On Friday, June 23, 2017 at 9:58:52 AM UTC-6, Mark Waite wrote:

 The UI experience has been great for me in the two or three places 
 where I've used it.  I was a little surprised (and pleased) with the 
 adaptation that the local branch setting is now a toggle.  I think 
 that's 
 the right approach, since (as far as I can tell) that is the 99% use 
 case.

 Earlier I reported an NPE when configuring a multi-branch pipeline 
 that uses GitHub as source instead of Git as source.  The NPE was 
 resolved 
 by removing the multiple-scms plugin.  Unfortunately, the 404 is still 
 there, along with a stack trace that starts with this:

 Jun 23, 2017 9:51:38 AM hudson.ExpressionFactory2$JexlExpression 
 evaluate
 WARNING: Caught exception evaluating: 
 

Re: ci.jenkins.io is building and I don't want it to - polluting PR statuses

[Oleg Nenashev]

Hi Michael,

I suppose you have missed the discussion in 
https://groups.google.com/forum/#!msg/jenkinsci-dev/yKAceS-6bwI/VqRxqYKEAAAJ

Please feel free to respond there.

BR, Oleg


среда, 28 июня 2017 г., 16:33:17 UTC+2 пользователь Jesse Glick написал:
>
> On Mon, Jun 26, 2017 at 8:02 PM, Michael Neale  > wrote: 
> > can this job get disabled? 
>
> File an INFRA ticket (component `ci`) to exclude`blueocean-plugin` 
> from the organization folder scan. 
>

-- 
You received this message because you are 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/35e72640-ffc4-47b5-8202-cae9dd709569%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Upgrading remoting to Java 8

[Oleg Nenashev]

Hi all,

A while a go I have created a ticket for upgrading Remoting to Java 8 (
JENKINS-43985 ). I was 
waiting with this step, because 2.46.x LTS was Java 7 compatible. Now we 
have completely switched to Java 8 in 2.60.1, hence it is not a blocker 
anymore. So I would like to update the Java requirement in Remoting, 
especially since there is an interest to do it in order to use some Java 8 
features (e.g. here ).

Potential impact, edge cases:

   - If somebody uses custom Remoting versions (e.g. by downloading the 
   latest version to pick fixes), such approach will stop working on Java 7. 
   So, all users of Java 7 will have to do custom builds if they want to get 
   Remoting fixes
   - Backporting of fixes (e.g. custom forks or security backports) may be 
   complicated
   - Swarm Plugin's Client will have to update to Java 8 in order to bundle 
   the new remoting version
   
Does anybody have any concerns about it?

Thanks in advance,
Oleg Nenashev

-- 
You received this message because you are 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/c784b3a4-c64d-413d-872c-4cad1d0c5642%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anyone else seeing a -SNAPSHOT deployed as a release for gradle plugin?

[Daniel Spilker]

https://issues.jenkins-ci.org/browse/JENKINS-45126


On Fri, Jun 30, 2017 at 12:07 PM, Robert Sandell 
wrote:

> Yes, I saw that yesterday as well when I installed 2.60.1
>
> /B
>
> 2017-06-30 11:49 GMT+02:00 Stephen Connolly  com>:
>
>>
>> ​
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/CA%2BnPnMzBxooXbih8Vek96xHU%3D2eZLB1BV15rG
>> bAXjtTjbxXNAA%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Robert Sandell
> *Software Engineer*
> *CloudBees Inc.*
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CALzHZS0a8cEszW0nS5Z-sNtddXCiWUWLzUMGmt697eqQoadGFg
> %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/CAKqW32AkLZAgA1EkyLBYHa%2ByrMTVpYJgTXQCOX8%3DeN79hTAZzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anyone else seeing a -SNAPSHOT deployed as a release for gradle plugin?

[Robert Sandell]

Yes, I saw that yesterday as well when I installed 2.60.1

/B

2017-06-30 11:49 GMT+02:00 Stephen Connolly :

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



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Anyone else seeing a -SNAPSHOT deployed as a release for gradle plugin?

[Stephen Connolly]

​

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

Re: Pipeline Build Wrapper

[Robert Sandell]

https://jenkins.io/doc/developer/extensions/jenkins-core/#globalconfiguration
http://javadoc.jenkins.io/jenkins/model/GlobalConfiguration.html

/B

2017-06-30 11:00 GMT+02:00 Steven F :

>
>
> On Wednesday, June 28, 2017 at 3:39:20 PM UTC+1, Jesse Glick wrote:
>>
>> cf. JENKINS-28822
>>
>
>  Sorry for another basic question, but do you have the name of a class I
> should look into to add a global configuration (from Manage Jenkins) that
> would be accessible to my RunListener? I've used Descriptors with other
> extension points but it doesn't seem to apply here since there is only one
> instance. I've also looked into OptionalJobProperty but that wouldn't be on
> a global level.
>
> --
> You received this message because you are 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/cb4724c6-1138-4739-94e5-cd245573fd60%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Pipeline Build Wrapper

[Robert Sandell]

https://jenkins.io/doc/developer/extensions/jenkins-core/#globalconfiguration
http://javadoc.jenkins.io/jenkins/model/GlobalConfiguration.html

/B

2017-06-30 11:00 GMT+02:00 Steven F :

>
>
> On Wednesday, June 28, 2017 at 3:39:20 PM UTC+1, Jesse Glick wrote:
>>
>> cf. JENKINS-28822
>>
>
>  Sorry for another basic question, but do you have the name of a class I
> should look into to add a global configuration (from Manage Jenkins) that
> would be accessible to my RunListener? I've used Descriptors with other
> extension points but it doesn't seem to apply here since there is only one
> instance. I've also looked into OptionalJobProperty but that wouldn't be on
> a global level.
>
> --
> You received this message because you are 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/cb4724c6-1138-4739-94e5-cd245573fd60%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Pipeline Build Wrapper

[Steven F]

On Wednesday, June 28, 2017 at 3:39:20 PM UTC+1, Jesse Glick wrote:
>
> cf. JENKINS-28822 
>

 Sorry for another basic question, but do you have the name of a class I 
should look into to add a global configuration (from Manage Jenkins) that 
would be accessible to my RunListener? I've used Descriptors with other 
extension points but it doesn't seem to apply here since there is only one 
instance. I've also looked into OptionalJobProperty but that wouldn't be on 
a global level.

-- 
You received this message because you are 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/cb4724c6-1138-4739-94e5-cd245573fd60%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.