Re: Jenkins Board & Officer Elections 2019

[Michael Neale]

+1 makes sense and great timing. 

On Thursday, September 5, 2019 at 6:38:22 AM UTC+10, Tracy Miranda wrote:
>
> Hi all, 
>
> As you may or may not know Jenkins project is run by a Governance Board 
> with support from a set of Officers. 
>
> While a process has been set out for elections we are overdue an election. 
> With Jenkins moving from SPI to CDF 
>  the timing is good to do 
> this. CD.Foundation is a multi-project foundation with corporate sponsors 
> and various oversight bodies. The nature of the foundation means we need to 
> ensure good channels for communications and a robust operating model. 
>
> With that in mind I am proposing the following set of dates for running a 
> new elections. The election process will be bootstrapped by the existing 
> board and we will request CDF run and supervise the election using the The 
> Condorcet Internet voting system .
>
> Please review the proposal below and links outlining the process for new 
> board and officer elections. 
>
> 2019 Election Schedule
>
> (Proposed):
>
> 13 September, 2019: Nominations open. To nominate someone, send an email 
> to jenkins...@googlegroups.com 
>
> 4 October, 2019: Nominations close
>
> 8 October, 2019: List of nominees posted to (mailing list)
>
> 11 October, 2019: Nominees’ personal statements made available
>
> 14 October, 2019: Voting begins
>
> 27 October, 2019: Voting closes 5pm Pacific Time
>
> 4 November, 2019: New representatives announced
>
> For voting eligibility I propose we generally stick with the process 
> outlined in the Board Election Process 
>  with the 
> following specific modifications:
>
>
>- cut-off date for voter eligibility being September 1st 2019.
>- I would also like to propose that any Jenkins contributor who does 
>not meet the eligibility criteria but is a community contributor can also 
>register to vote by writing to the existing board of directors. (as I have 
>been made aware of a subset of contributors who potentially fall in this 
>category)
>
>
> Please review the above and share your thoughts. Ideally we discuss now 
> with the goal of reaching consensus by the next governance meeting on 
> August 11th when we can finalize/ratify the proposal. 
>
> If you are happy with the proposal I hope you will consider putting 
> yourself forward for one of the positions. 
>
> Regards,
> Tracy
>
>
>
>
>

-- 
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/5255981b-b7b8-4718-887b-53885dc8c09c%40googlegroups.com.

Re: Fixing pot holes in Blue Ocean UI?

[Michael Neale]

So just checking in on this excellent list as of this week:

   - https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a 
   job in Blue Ocean - Looks like Gavin is starting this (sounded like some 
   good progress). 
   - https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does 
   not group changes for multiple SCM providers by SCM - Nicu has started on 
   that (shouldn't be major hopefully)
   - https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see 
   executors in Blue Ocean UI - Craig can this be closed? as your changes 
   merged in (once released) should resolve this
   - https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit build 
   information in Blue ocean UI - This one will be probably the biggest one, 
   and I am not sure how it can be tackled given build config can be highly 
   dynamic based on plugins installed. If there is a way to scope this a bit 
   better may make it easier to start. 




On Sunday, February 3, 2019 at 10:38:02 AM UTC+11, Craig Rodrigues wrote:
>
> Hi,
>
> I like the Blue Ocean UI a lot!  I am trying to use Blue Ocean
> as my "daily driver" when interacting with Jenkins.
> I spend a lot of my day starting/stopping jobs, examining logs,
> editing build descriptions, and disabling/enabling builds. 
>
> However, there are some gaps in the Blue Ocean UI.
>
> The gaps are small, but annoying enough that I need to keep switching
> back to the classic UI.  This is annoying.
>
> I mentioned this in this other discussion thread: 
> https://groups.google.com/d/msg/jenkinsci-dev/zNukeuLK4Og/DGwWnJyGCAAJ
> , but wanted to pull out this list to a separate discussion.
>
> Here are my top pet peeves, which I classify as "pot holes":
>
>
>- https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a 
>job in Blue Ocean
>- https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does 
>not group changes for multiple SCM providers by SCM
>- https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see 
>executors in Blue Ocean UI
>- https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit build 
>information in Blue ocean UI
>
>
> If anyone wants to collaborate on fixing these bugs, please communicate on 
> the Gitter channel: https://gitter.im/jenkinsci/blueocean-plugin
>
> --
> Craig
>
>
>

-- 
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/46600b1b-9853-4648-abfc-3f9869ef27be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Michael Neale]

On JENKINS-52825  have reopened and can discuss on the PR in place (as a 
bunch of work already there).

On Wednesday, February 13, 2019 at 1:03:00 PM UTC+11, David Lin wrote:
>
> Hi Craig,
>
> I was just pointed to this thread (Thanks @Michael!). We have 
> JENKINS-53022 on our radar already to fix, we were just finalizing some 
> Acceptance Test repairs and releasing a chunk of fixes. So it should be 
> coming up soon.
>
> As for JENKINS-52825, we're not exactly sure if it makes sense to pull it 
> into the root of Blue Ocean since it's already a plugin and was never fully 
> completed. Hopefully it still works for you that way.
>
> JENKINS-53019 and JENKINS-55691 will also be picked up to be completed 
> soon after the next release as well.
>
> Thanks again for your suggestions and contributions. It's very helpful, 
> keep them coming!
>
>  - David
>
>
>
> On Saturday, February 2, 2019 at 3:38:02 PM UTC-8, Craig Rodrigues wrote:
>>
>> Hi,
>>
>> I like the Blue Ocean UI a lot!  I am trying to use Blue Ocean
>> as my "daily driver" when interacting with Jenkins.
>> I spend a lot of my day starting/stopping jobs, examining logs,
>> editing build descriptions, and disabling/enabling builds. 
>>
>> However, there are some gaps in the Blue Ocean UI.
>>
>> The gaps are small, but annoying enough that I need to keep switching
>> back to the classic UI.  This is annoying.
>>
>> I mentioned this in this other discussion thread: 
>> https://groups.google.com/d/msg/jenkinsci-dev/zNukeuLK4Og/DGwWnJyGCAAJ
>> , but wanted to pull out this list to a separate discussion.
>>
>> Here are my top pet peeves, which I classify as "pot holes":
>>
>>
>>- https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a 
>>job in Blue Ocean
>>- https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does 
>>not group changes for multiple SCM providers by SCM
>>- https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see 
>>executors in Blue Ocean UI
>>- https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit 
>>build information in Blue ocean UI
>>
>>
>> If anyone wants to collaborate on fixing these bugs, please communicate 
>> on the Gitter channel: https://gitter.im/jenkinsci/blueocean-plugin
>>
>> --
>> Craig
>>
>>
>>

-- 
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/3ec344c1-6afc-4c10-a1a2-6df8b6dab431%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fixing pot holes in Blue Ocean UI?

[Michael Neale]

Thanks Craig. 

I think that makes a lot of sense - that was kept separate for historic 
reasons that no longer matter. 

I think there may be some more work to do to get it clean (as it was part 
of some acceptance test in the past) but can continue that on the PR. 

On Sunday, February 3, 2019 at 10:45:38 AM UTC+11, Craig Rodrigues wrote:
>
> Michael,
>
> I submitted this PR to import the blueocean-executor-info-plugin into the 
> blueocean-plugin
> via a git subtree merge, to preserve history:
>
> https://github.com/jenkinsci/blueocean-plugin/pull/1909
>
> blueocean-executor-info-plugin is not perfect, but having it inside the 
> blueocean-plugin core is
> better than not having it.
>
> --
> Craig
>
>
> On Mon, Jan 21, 2019 at 9:01 PM Michael Neale  > wrote:
>
>>
>> To Craig's point - that is a great and fairly reasonable hitlist to make 
>> something end to end useful. On the first one I put a comment (not sure if 
>> pipeline jobs can be disabled at all...) but it is valid. The others are 
>> doable (the hard one is editing build info - as that is where extensible 
>> GUIs of plugins can kick in - but likely the scope can be contained here to 
>> be reasonable to make something useful end to end). That would be great!
>>
>> For the executors one - we could resurrect the old executor visualisation 
>> plugin (this was mostly done as a demo of extensibility, but perhaps it is 
>> time to fold it in) - there is some code here: 
>> https://github.com/jenkinsci/blueocean-executor-info-plugin which may be 
>> useful for that (doesn't need to be its own plugin, really...)
>>
>>
>
> On Sat, Feb 2, 2019 at 3:37 PM Craig Rodrigues  > wrote:
>
>> Hi,
>>
>> I like the Blue Ocean UI a lot!  I am trying to use Blue Ocean
>> as my "daily driver" when interacting with Jenkins.
>> I spend a lot of my day starting/stopping jobs, examining logs,
>> editing build descriptions, and disabling/enabling builds. 
>>
>> However, there are some gaps in the Blue Ocean UI.
>>
>> The gaps are small, but annoying enough that I need to keep switching
>> back to the classic UI.  This is annoying.
>>
>> I mentioned this in this other discussion thread: 
>> https://groups.google.com/d/msg/jenkinsci-dev/zNukeuLK4Og/DGwWnJyGCAAJ
>> , but wanted to pull out this list to a separate discussion.
>>
>> Here are my top pet peeves, which I classify as "pot holes":
>>
>>
>>- https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a 
>>job in Blue Ocean
>>- https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does 
>>not group changes for multiple SCM providers by SCM
>>- https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see 
>>executors in Blue Ocean UI
>>- https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit 
>>build information in Blue ocean UI
>>
>>
>> If anyone wants to collaborate on fixing these bugs, please communicate 
>> on the Gitter channel: https://gitter.im/jenkinsci/blueocean-plugin
>>
>> --
>> Craig
>>
>>
>>

-- 
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/23c9fe25-f2f0-470f-a50b-73e36ecc0301%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What resources is Cloudbees allocating to Blue Ocean maintenance/development?

[Michael Neale]

Responding (but obviously nothing official) but I like the points brought 
up by Craig and Uli. 

To Ulis point: extensibility in GUI is haaard, and I don't think blue ocean 
has solved it to the point that those rich visual aspects of the 99% he 
alludes to can be catered to. There are some great ideas here - I liked the 
one of plugins thinking about visualisation specific to them (which may be 
able to be incorporated in many places). This plays into Kohsukes point "I 
think one key change in this space is that individualized feedback matters 
a lot more than it used to be" which I strongly agree with too. Eg people 
are looking at results right in pull requests, or slack messages and so on. 

To Craig's point - that is a great and fairly reasonable hitlist to make 
something end to end useful. On the first one I put a comment (not sure if 
pipeline jobs can be disabled at all...) but it is valid. The others are 
doable (the hard one is editing build info - as that is where extensible 
GUIs of plugins can kick in - but likely the scope can be contained here to 
be reasonable to make something useful end to end). That would be great!

For the executors one - we could resurrect the old executor visualisation 
plugin (this was mostly done as a demo of extensibility, but perhaps it is 
time to fold it in) - there is some code 
here: https://github.com/jenkinsci/blueocean-executor-info-plugin which may 
be useful for that (doesn't need to be its own plugin, really...)

On Saturday, January 19, 2019 at 5:08:48 PM UTC+11, Craig Rodrigues wrote:
>
> In my current job, we ely on the both the classic Jenkins UI and
> the Blue Ocean UI very heavily.  We have hundreds of tests, producing huge
> log files.  We use the  test report viewer in classic UI and Blue Ocean 
> very heavily.
>
> Two things (out of many things) that I like about the Blue Ocean UI are:
>
> 1.  massive text log files can be loaded more quickly in a web browser
> 2.  it is possible to hyperlink directly to a single line in a log file, 
> which is very useful for pasting
>  into an e-mail or a Slack message, to share with co-workers.
>
> I understand that the focus of Cloudbees has shifted to other things, and 
> maybe
> for the next few years the pace of massive new work on Blue Ocean will be 
> slow.
> However, it would still be nice to have someone (Cloudbees ?) fix some of 
> the minor
> pot holes in Blue Ocean.  For example:
>
>
>- https://issues.jenkins-ci.org/browse/JENKINS-53022 Cannot disable a 
>job in Blue Ocean
>- https://issues.jenkins-ci.org/browse/JENKINS-53019 Changes tab does 
>not group changes for multiple SCM providers by SCM
>- https://issues.jenkins-ci.org/browse/JENKINS-52825 Cannot see 
>executors in Blue Ocean UI
>- https://issues.jenkins-ci.org/browse/JENKINS-55691 Cannot edit build 
>information in Blue ocean UI
>
> If some level of activity (even low level) could be invested in fixing 
> these types of pot holes, that would be nice.
> If I am able, I will try to submit patches, but I'm a bit busy with my 
> job, and
> am not an expert in Node.js.
>
> --
> Craig
>
>
> On Thu, Jan 17, 2019 at 12:36 PM Kohsuke Kawaguchi  > wrote:
>
>>
>>  In a long run, I think UI is a crucial part of the value of Jenkins. 
>> It's what differentiated Jenkins from cron in the first place, and an 
>> important part of the continuous integration/delivery is to give visibility 
>> to more people, which to me necessarily includes consolidating information.
>>
>

-- 
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/27a3001c-8def-4329-a1ce-d7c6c921dee6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Slack plugin] Request commit access

[Michael Neale]

Hi Tim (missed you on irc, but saw the request). 

You should be a committer to it now on github. 

If you want to do a release - open a pull request with your jenkins.io user 
info 
here: 
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-slack.yml
 
(otherwise it won't let the plugin binary upload). 


On Wednesday, November 28, 2018 at 9:31:01 AM UTC+11, Tim Jacomb wrote:
>
> Hi
>
> Its been about two weeks now
> As detailed here:
> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin
>
> May I please take over this plugin?
>
> I've tagged on github:
>
> On Wed, 14 Nov 2018 at 20:27, Tim Jacomb > 
> wrote:
>
>> CC maintainers
>>
>> On Wed, 14 Nov 2018 at 20:25, Tim Jacomb > > wrote:
>>
>>> Hi
>>>
>>> I would like to request commit access for the slack plugin
>>> It has been discussed briefly here:
>>> https://github.com/jenkinsci/slack-plugin/issues/402
>>>
>>> Github: timja
>>> Jenkins infra: timja
>>>
>>> Thanks
>>> Tim
>>>
>>> -- 
>>> 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/cf050ffc-34bf-4502-b9c1-681018806fb8%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/0d0a3a28-d000-40b7-a60b-f7eedb73b14f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bitbucket Branch Source Plugin Maintainer

[Michael Neale]

I think we can still grant committer access via the irc bot (but will need 
to be added to permissions repo) - Antonio that makes sense? Interest is 
increasing in this plugin.

On Saturday, September 1, 2018 at 6:43:21 AM UTC+10, Joseph P wrote:
>
> I am pretty familiar with the code base, contributed and reviewed a lot of 
> the PRs, so if your up for it wouldn't mind being the second maintainer.
> Also maintainer on the bitbucket webhook plugin for non native webhook 
> bitbucket.
>
> 
>
> torsdag den 30. august 2018 kl. 09.47.21 UTC+2 skrev Antonio Muñiz:
>>
>> BTW, I'm one of the maintainers, but I'd like to get at least one more 
>> review from another maintainer.
>>
>> On Thu, 30 Aug 2018 at 09:18, Antonio Muñiz  wrote:
>>
>>> Review done.
>>>
>>> On Wed, 29 Aug 2018 at 04:05, Richard Bywater  wrote:
>>>
 Hi

 Just wanted to put out a call to see who identifies with being the 
 maintainer for the Bitbucket Branch Source Plugin at the moment.

 Reason I ask is that there's a few PRs building up at the moment and 
 one of them ( 
 https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/115 ) 
 would be of great use for those of us who use a different URL for HTTP & 
 SSH.

 Thanks in advance :)
 Richard.

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

>>>
>>>
>>> -- 
>>> Antonio Muñiz
>>> Software Engineer
>>> CloudBees, Inc.
>>>
>>
>>
>> -- 
>> Antonio Muñiz
>> 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/325c63bb-9db0-4c20-9563-9966649513e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Jenkins X | JEP-400] Weekly on air hangout/office hours

[Michael Neale]

Lets see what James says about May 8th (should be ok). 

On those other topics - yes bigger discussion. jenkins-x/jx issues are 
currently used as github issues are "dogfooded" - but I believe there is 
JIRA support so I think in time they can move to jira under a jenkins-x 
component. 

As for repos: there are currently 36 (and growing) in the org - so would 
need to namespace them to move them into main org. A lot of them are 
infra/biuld pack type things. There is also jenkins-infra which has 64, 
which is separate (but I guess it is managed out of band). If it is a 
matter of managing access to repos etc - could be solved I am sure. 

On Wednesday, May 2, 2018 at 1:26:58 PM UTC+10, Liam Newman wrote:
>
> Oleg: By "listing Jenkins X under sub-projects" do you also mean moving 
> the repositories under jenkinsci org on github and using the Jenkins JIRA?  
> I support that, but it something that should probably go on a separate 
> thread.  
>
> James, Michael,
> Obviously I dropped the ball on April 26th.  Shall I schedule the next 
> meeting on the May 8th?
>
> On Thursday, April 19, 2018 at 3:30:12 AM UTC-7, Oleg Nenashev wrote:
>>
>> No, it can happen at any moment IMHO. I do not see JEP-400 to be a 
>> blocker for referencing this project from jenkins.io. OTOH I am not sure 
>> it is within Jenkins organization governance now. E.g. using external org 
>> blocks Jenkins GitHub admins from managing permission requests, etc. Are 
>> there plans to migrate by the way? JEP-400 does not cover these governance 
>> things.
>>
>> BR, Oleg
>>
>> On Thu, Apr 19, 2018 at 12:17 PM, Michael Neale <mne...@cloudbees.com> 
>> wrote:
>>
>>> Does that have to happen after the JEP is accepted? 
>>>
>>> -- 
>>> 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/j_pqY84Pjag/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/ed611774-7746-48d6-bfa9-1b1ac3592b00%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/747821e2-6de5-4b9a-bc5f-c08632ae54a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins X status

[Michael Neale]

Is there a way to x-post that to a jenkins.io blog? (even as a PR/somewhat 
automatically?)

On Saturday, April 28, 2018 at 1:55:36 AM UTC+10, Rob Davies wrote:
>
> We've been pretty busy - but always need more help from the Jenkins 
> community. Here's the latest changes in Jenkins X land: 
> http://jenkins-x.io/news/changes-april-27-2018/
>
> thanks,
>
> Rob
>
>
> On Friday, April 13, 2018 at 7:53:09 AM UTC+1, Rob Davies wrote:
>>
>> 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 Anhttps://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/242436c0-fb70-4644-88c0-c0fcbf022f3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Jenkins X | JEP-400] Weekly on air hangout/office hours

[Michael Neale]

Does that have to happen after the JEP is accepted? 

-- 
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/ed611774-7746-48d6-bfa9-1b1ac3592b00%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jenkins X | JEP-400] Weekly on air hangout/office hours

[Michael Neale]

Hey all - James Rawlings has proposed a weekly on air/office hours. I know 
there is a jenkinscicd youtube channel capable of doing scheduled hangouts 
on air, so I think that would be the best place to do it? Liam? 

-- 
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/bf58389b-0aa8-4be0-ba1a-e8059607b676%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins X status

[Michael Neale]

Thanks Rob. 

Also a reminder that most of the chat happens for now in slack 
on http://slack.k8s.io/ - 
the https://kubernetes.slack.com/messages/C9LTHT2BB chat room (and on PRs 
and such of course), not on a mailing list. 
Also, https://github.com/jenkins-x/jx/issues has issues, not JIRA for the 
moment in case you are curious. 



On Friday, April 13, 2018 at 4:53:09 PM UTC+10, Rob Davies wrote:
>
> 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 Anhttps://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/bc98a2a6-6d5b-4097-8401-14b1a1a23975%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: first draft of a new JEP: Jenkins X: Jenkins for Kubernetes CD

[Michael Neale]

Nice description!

Given the disparate timezones of everyone involved, would it make sense to 
have a few office hour type things? (not sure if there is enough interest 
in APAC timezone, if there is, let me know.

On Thursday, March 15, 2018 at 1:32:48 PM UTC+11, Kohsuke Kawaguchi wrote:
>
> Thanks James,
>
> This is an important and exciting JEP for me, because it sets the mission 
> & scope for a new project “Jenkins X.”
> Starting from Jenkins 2, in contributor events and Jenkins Worlds, I’ve 
> always pitched that our Jenkins project needs to take a bigger role and 
> responsibility in serving our users and solving their challenges. 
> Historically, by and large we did it by writing plugins, but we’ve been so 
> successful in doing that, now we need to create solutions that combine 
> those plugins.
>
>
>
>

-- 
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/d5b2101c-6d5d-47e5-8848-115728369ed5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch event listener for Github PR labels

[Michael Neale]

Hi Steven. 

This seems to be a reasonably often asked for feature (I wasn't able to 
find a ticket though, for multibranch/github multibranch specifically, 
surely there is one?). 

Are you thinking that ideally in your case the branches/PRs would not 
appear at all until the label is applied? Would an alternative that makes 
it show up as not built or similar do? (may be easier to do that...)

On Thursday, March 15, 2018 at 1:50:00 AM UTC+11, Steven F wrote:
>
> Hi,
>
> I'm trying to write a filter for multibranch which accepts PRs with a 
> given github PR label. That part was simple. I also thought I should 
> implement an events subscriber (GHEventsSubscriber) and I'm having trouble 
> figuring out the details of that.
> I've tried basing it on the PullRequestGHEventSubscriber since it will be 
> creating/deleting heads rather than triggering builds but I couldn't figure 
> out how some things were used, specifically the *heads()* method. My 
> class is pretty much a copy paste with the actions changed to 
> labeled/unlabeled. Right now, I'm getting messages like
>
>> [Wed Mar 14 13:37:45 GMT 2018] Received Pull request #9 labeled in 
>>> repository sfoster/branch_filter_test CREATED event from 10.32.8.197 ⇒ 
>>> http://10.32.8.83:8080/jenkins/github-webhook/ with timestamp Wed Mar 
>>> 14 13:37:40 GMT 2018
>>
>> Found match against demo (new branch PR-9)
>>
>> [Wed Mar 14 13:37:47 GMT 2018] Finished processing Pull request #9 
>>> labeled in repository sfoster/branch_filter_test CREATED event from 
>>> 10.32.8.197 ⇒ http://10.32.8.83:8080/jenkins/github-webhook/ with 
>>> timestamp Wed Mar 14 13:37:40 GMT 2018. Matched 1.
>>
>>
>  in jenkins.branch.MultiBranchProject.log, and
>
> [Wed Mar 14 13:37:47 GMT 2018] Pull request #9 labeled in repository 
> sfoster/branch_filter_test CREATED event from 10.32.8.197 ⇒ 
> http://10.32.8.83:8080/jenkins/github-webhook/ with timestamp Wed Mar 14 
> 13:37:40 GMT 2018 processed in 2.3 sec
>>
>>
> in the projects  "repository events" page, but no sign of the new PR in 
> the project.
>
> I guess I'm not even sure how a successful result would play out, does it 
> trigger a repository indexing with the given Event? or do the new heads 
> just appear in the project?
>

-- 
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/dd155294-35eb-4733-9ac1-6709a7d58b9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: POTD: Jenkinsfile Runner

[Michael Neale]

As an example of how to use (abuse?) this: 

I was able to take a container with the set of "recommended" plugins, and 
run it on the "codeship pro" service (which uses docker): 
https://github.com/michaelneale/codeship-jenkinsfile



On Friday, March 2, 2018 at 6:23:15 AM UTC+11, Kohsuke Kawaguchi wrote:
>
> Jenkinsfile Runner is an experiment to package Jenkins pipeline execution 
> as a command line tool. The intend use cases include:
>
>- Use Jenkins in Function-as-a-Service context
>- Assist editing Jenkinsfile locally
>- Integration test shared libraries
>
> Over the past year, I've done some deep-dive 1:1 conversations with some 
> Jenkins users and I felt something like this might move the needle for them 
> in an important way.
>
> I'd love to hear any reactions on your side. Could something like this be 
> important for you, does it miss any key points for you? If you mentally 
> picture a perfect version of this, what would that do, and how would you 
> use?
>
> Let me know!
>
> -- 
> Kohsuke Kawaguchi
>

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

Re: hello & improving Jenkins & Kubernetes CI / CD

[Michael Neale]

Hi James - did you get to catch up with people about this? 

"baling wire and twine" - isn't that how the internet works? 

On Friday, March 2, 2018 at 5:05:07 PM UTC+11, Robert Collins wrote:
>
> Sure would. We have the two glued together with baling wire and twine. Hit 
> me up at rob...@vmware.com 
>
> Rob
>
>
> On 2 Mar. 2018 02:50, "James Strachan"  
> wrote:
>
>> Hello folks!
>>
>> I’m James Strachan. I’m a long time Jenkins user and OSS developer. (e.g. 
>> I created Groovy, Apache Camel, dom4j, jaxen etc  Though I’m going to keep 
>> quiet about Jelly... ;). I’ve worked on a few Jenkins plugins over the 
>> years but never much on the core of Jenkins.
>>
>> So I’ve been working with Jenkins on Kubernetes for about 3-4 years now; 
>> I was one of the folks behind fabric8 at Red Hat & helped bring Jenkins to 
>> OpenShift.
>>
>> I’ve recently joined CloudBees and have been thinking & experimenting 
>> with how to make Jenkins more awesome as a tool for CI / CD platform on 
>> Kubernetes.
>>
>> I’ve started working on a JEP to bring those experiments to this list. 
>> But until its a bit more fleshed out, I wonder if anyone fancies an off 
>> list heads up on what I’m thinking? I’d love some early feedback to before 
>> I try to bring my thoughts to this list.
>>
>> Many thanks in advance & see you soon :)
>>
>> -- 
>> James
>> ---
>> Twitter: @jstrachan
>> Email: james.s...@gmail.com 
>> Blog: https://medium.com/@jstrachan/
>>
>> -- 
>> 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/CALTd4v-mHefu81g%3D6T3m_7vFPb8%2BTR3-vGF-EfOGKpj8cHYs9Q%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/16603bef-7540-43bb-a687-920a4c573b6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: The Jenkins Enhancement Process (JEP) is ready for review

[Michael Neale]

Looks good to me. 

On Saturday, November 4, 2017 at 9:23:43 AM UTC+11, Liam Newman wrote:
>
> Hello all,
>
> I'm pleased to announce the that Jenkins Enhancement Process will be on 
> the agenda for governance meeting this coming week.
>
> While there are still some discussions occurring around some details for 
> the process, the overall structure seems to have stabilized enough for it 
> to be reviewed for Acceptance.
>
> You can review the current state of the proposal in preparation for the 
> meeting: https://github.com/jenkinsci/jep/pull/12 .  
>
> Discussion so far:
> https://groups.google.com/d/topic/jenkinsci-dev/spDAr8EJm3c/discussion
>
> Thanks, 
> -Liam Newman 
>
>
>

-- 
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/f2cd563c-de0a-4d59-98e6-e6746beed48a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: open the flood gates for all Plugins' Pipelines on ci.jenkins.io

[Michael Neale]

Have done: https://issues.jenkins-ci.org/browse/INFRA-1262 - good idea 

Tyler was working on it - there is a problem with scanning repos which may 
require a change/patch. Could we possibly turn off the org folder (delete 
it) until that is the case? as this is getting very hard to work with (some 
times it is like we don't have CI, which is delicious irony). 

On Wednesday, July 5, 2017 at 1:24:37 AM UTC+10, Jesse Glick wrote:
>
> On Tue, Jul 4, 2017 at 5:40 AM, Michael Neale <mne...@cloudbees.com 
> > wrote: 
> > Any ETA on when the pattern will be applied? 
>
> Best to file a ticket in INFRA so your issue can be tracked. 
>

-- 
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/086c7016-fb81-4e5c-a1bb-2274e9a9f256%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: open the flood gates for all Plugins' Pipelines on ci.jenkins.io

[Michael Neale]

Any ETA on when the pattern will be applied? still seeing failures on 
github with every new PR (at least as of a few hours ago)
I think there was some work/bug to be overcome to get it to rescan with 
such a prodigious number of repositories in a github org (it is a great 
pressure test of things!)

On Thursday, June 29, 2017 at 12:43:16 AM UTC+10, Jesse Glick wrote:
>
> On Tue, Jun 27, 2017 at 6:59 PM, Daniel Beck  > wrote: 
> >> I have opened the flood gates with the regex: 
> ((!blueocean-plugin)|(.*-plugin)) 
> > 
> > Does this actually work? I'd have expected something more like: 
> > 
> > .*-plugin(?
> Or 
>
> (?!blueocean-plugin).+-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/168b69b4-1f3d-470f-8e05-48c8a9c2d9b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: open the flood gates for all Plugins' Pipelines on ci.jenkins.io

[Michael Neale]

It doesn't work in as much as blue ocean - it is still triggering builds 
for it. 

On Wednesday, June 28, 2017 at 8:59:41 AM UTC+10, Daniel Beck wrote:
>
>
> > On 27. Jun 2017, at 17:52, R. Tyler Croy  > wrote: 
> > 
> > I have opened the flood gates with the regex: 
> ((!blueocean-plugin)|(.*-plugin)) 
>
> Does this actually work? I'd have expected something more like: 
>
> .*-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/3b55e3ac-1784-4886-a9e6-bbdf08c17716%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Anonymous user analytics in Blue Ocean

[Michael Neale]

I think it should/could be shared as it may be interesting to some. Can 
also make things transparent that no PII is fllowing. 



On Wednesday, June 28, 2017 at 1:48:21 AM UTC+10, R Tyler Croy wrote:
>
> (replies inline) 
>
> On Mon, 26 Jun 2017, James Dumay wrote: 
>
> > 
> > For example, we would like to know what the success rate of the pipeline 
> > creation process is. We would track events for each stage in the 
> creation 
> > flow and we can then use a funnel analysis [2] to see what step users 
> drop 
> > off (e.g. where we have failed). Another usage would be to record what 
> > browser versions are in use and that data could be used to have a more 
> > tailored Supported Browser policy for the project. 
> > 
> > In addition to improving the user experience, I am in a position at 
> > CloudBees where I have to decide how our employees time is being spent 
> on 
> > the Blue Ocean project and having this data would help us spend this 
> time 
> > more wisely. 
> > 
> > The data collected here is intended for development only (e.g. not 
> > marketing or other nefarious purposes) and is available under the exact 
> > same terms as the Jenkins Usage Statistics (e.g. email me and I can give 
> > you access). 
> > 
> > As for personally identifiable information, we strictly do not want to 
> > include this data in any user analytics. To ensure that we can identify 
> a 
> > users click stream, we have taken a sha256 hash of the instances public 
> key 
> > and the user ID and reported this back to the store as a key 
> representing 
> > the user. It would be great to have any security conscious developers 
> > review this code [4]. 
> > 
> > If this turns out to be something useful we can look at opening it up to 
> > more plugins. For this initial spike we are using a service called Keen 
> [5] 
> > but I would not be against pumping this data our to a service on Jenkins 
> > project infra (anyone want to write an analytics system?). 
>
>
>
> Here's me proactively unvolunteering to write an analytics system right to 
> host 
> in our project infra :P 
>
>
> More seriously though, I don't see any problem as long as you're taking 
> care to 
> make sure PII isn't being sent to Keen. I've seen a few plugins over the 
> years 
> do this, and as long as it's respecting the user's Anonymous usage 
> collection 
> setting, and not being stupid, then it's totally reasonable IMHO. 
>
>
>
> While I don't think there is any obligation to share what you learn from 
> these 
> analytics, I'm sure other plugin developers would find your eventual 
> conclusions useful. 
>
>
>
> God speed mooncat. 
>
> - R. Tyler Croy 
>
> -- 
>  Code:  
>   Chatter:  
>  xmpp: rty...@jabber.org  
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F 
> -- 
>

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

Re: Proposal: open the flood gates for all Plugins' Pipelines on ci.jenkins.io

[Michael Neale]

(ignore) - sorry I read out of order again :(
Hopefully that regex looks ok. Thanks. 

On Wednesday, June 28, 2017 at 8:51:00 AM UTC+10, Michael Neale wrote:
>
> If it hasn't been done already (chatted to tyler yesterday) - can we have 
> the "blueocean-plugin" excluded from the pattern/regex? 
>
> On Wednesday, June 28, 2017 at 6:08:30 AM UTC+10, Arnaud Héritier wrote:
>>
>> Hi everyone
>>
>>   As discussed with Tyler I now deactivated all jobs under 
>> https://jenkins.ci.cloudbees.com/job/plugins/
>>   It is now important to create a Jenkinsfile with a simple call: 
>> buildPlugin()
>>   You can review the discovery of plugins here : 
>> https://ci.jenkins.io/job/Plugins/computation/console
>>   If you are owner/admin of the github repository of the plugin it might 
>> be good to edit its webhooks to remove the useless ones like 
>> jenkins.ci.cloudbees.com ones
>>
>> Cheers
>>   
>>
>> On Tue, Jun 27, 2017 at 5:52 PM, R. Tyler Croy <ty...@monkeypox.org> 
>> wrote:
>>
>>> (replies inline)
>>>
>>> On Fri, 16 Jun 2017, R. Tyler Croy wrote:
>>>
>>> >
>>> > Last year we started allowing plugin developers use of new shiney 
>>> elastic
>>> > compute capacity on ci.jenkins.io provided by our friends at 
>>> Microsoft. Today I
>>> > would like to proposal that we open the flood gates, and add 
>>> "*-plugin" to our
>>> > GitHub Organization Folder here: https://ci.jenkins.io/job/Plugins/
>>>
>>>
>>> I have opened the flood gates with the regex: 
>>> ((!blueocean-plugin)|(.*-plugin))
>>>
>>>
>>>
>>>
>>> - R. Tyler Croy
>>>
>>> --
>>>  Code: <https://github.com/rtyler>
>>>   Chatter: <https://twitter.com/agentdero>
>>>  xmpp: rty...@jabber.org
>>>
>>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
>>> --
>>>
>>> --
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/20170627155232.b6hvdade5yczsnfx%40blackberry.coupleofllamas.com
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> -- 
>> -
>> Arnaud Héritier
>> http://aheritier.net
>> Mail/GTalk: aheritier AT gmail DOT com
>> Twitter/Skype : aheritier
>>
>

-- 
You received this message because you are subscribed to 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/8ba0d7b3-a6b2-4ffe-8332-0cb657927ff6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: open the flood gates for all Plugins' Pipelines on ci.jenkins.io

[Michael Neale]

If it hasn't been done already (chatted to tyler yesterday) - can we have 
the "blueocean-plugin" excluded from the pattern/regex? 

On Wednesday, June 28, 2017 at 6:08:30 AM UTC+10, Arnaud Héritier wrote:
>
> Hi everyone
>
>   As discussed with Tyler I now deactivated all jobs under 
> https://jenkins.ci.cloudbees.com/job/plugins/
>   It is now important to create a Jenkinsfile with a simple call: 
> buildPlugin()
>   You can review the discovery of plugins here : 
> https://ci.jenkins.io/job/Plugins/computation/console
>   If you are owner/admin of the github repository of the plugin it might 
> be good to edit its webhooks to remove the useless ones like 
> jenkins.ci.cloudbees.com ones
>
> Cheers
>   
>
> On Tue, Jun 27, 2017 at 5:52 PM, R. Tyler Croy  > wrote:
>
>> (replies inline)
>>
>> On Fri, 16 Jun 2017, R. Tyler Croy wrote:
>>
>> >
>> > Last year we started allowing plugin developers use of new shiney 
>> elastic
>> > compute capacity on ci.jenkins.io provided by our friends at 
>> Microsoft. Today I
>> > would like to proposal that we open the flood gates, and add "*-plugin" 
>> to our
>> > GitHub Organization Folder here: https://ci.jenkins.io/job/Plugins/
>>
>>
>> I have opened the flood gates with the regex: 
>> ((!blueocean-plugin)|(.*-plugin))
>>
>>
>>
>>
>> - R. Tyler Croy
>>
>> --
>>  Code: 
>>   Chatter: 
>>  xmpp: rty...@jabber.org 
>>
>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
>> --
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/20170627155232.b6hvdade5yczsnfx%40blackberry.coupleofllamas.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>

-- 
You received this message because you are subscribed to 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/2d8d48dd-b2dd-43a5-a252-10a2eb63f8b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub and Bitbucket branch source UI refactoring

[Michael Neale]

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 <kbur...@rosettastone.com 
> > 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 <mark.ea...@gmail.com> 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: 
>>>>> descriptor.calcFillSettings(field,attrs) in 
>>>>> /job/Git-Client-Folder/job/git-client-pipeline-github/configure. Reason: 
>>>>> java.lang.IllegalStateException: class 
>>>>> org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$DescriptorImpl 
>>>>> doesn't have the doFillCredentialsIdItems method for filling a drop-down 
>>>>> list
>>>>> java.lang.IllegalStateException: class 
>>>>> org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$DescriptorImpl 
>>>>> doesn't have the doFillCredentialsIdItems method for filling a drop-down 
>>>>> list
>>>>> at hudson.model.Descriptor.calcFillSettings(Descriptor.java:412)
>>>>> at sun.reflect.GeneratedMethodAccessor578.invoke(Unknown Source)
>>>>> at 
>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>> at java.lang.reflect.Method.invoke(Method.java:498)
>>>>> at 
>>>>> org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
>>>>> at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
>>>>> at 
>>>&

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

[Michael Neale]

Ah I didn't see the message when away... for the org folder. 

On Tuesday, June 27, 2017 at 10:02:01 AM UTC+10, Michael Neale wrote:
>
> Just as of today, I am seeing builds like: 
>
> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fblueocean-plugin/detail/PR-1193/1/pipeline
>
> but this was not requested - can this job get disabled? we have our own 
> "dogfood" server, and that is just adding confusing statuses to the pull 
> requests. 
>

-- 
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/b7de4a99-e817-4874-8439-171fba6abbf8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Michael Neale]

Just as of today, I am seeing builds like: 
https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fblueocean-plugin/detail/PR-1193/1/pipeline

but this was not requested - can this job get disabled? we have our own 
"dogfood" server, and that is just adding confusing statuses to the pull 
requests. 

-- 
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/f33afc0e-c442-4b13-9802-11fdf0f0dcd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub and Bitbucket branch source UI refactoring

[Michael Neale]

It does look better now with the new version. I confirmed running a scan 
didn't make anything go away. 


On Thursday, June 22, 2017 at 3:20:37 PM UTC+10, Stephen Connolly wrote:
>
>
> On Thu 22 Jun 2017 at 04:29, Michael Neale <mne...@cloudbees.com 
> > wrote:
>
>> I saw all jobs disappear in a github org folder that blue ocean created 
>> previously, when I triggered a scan. 
>>
>> (it also doesn't seem to trigger scans if I add change the pattern, or 
>> run the wizard again). 
>>
>
> I need to investigate some of the hacks BO is using.
>
> I suspect this is probably just one deprecated constructor that needs 
> tweaking
>
>
>>
>> On Thursday, June 22, 2017 at 4:39:30 AM UTC+10, Mark Waite wrote:
>>
>>> I haven't tried it yet.  I'm configuring the "before" state today and 
>>> will capture its state, then will deploy the new code tomorrow morning and 
>>> capture the after state.  I won't do anything to compare those until 
>>> tomorrow evening or this weekend.
>>>
>>> Mark Waite
>>>
>>> On Wed, Jun 21, 2017 at 12:30 PM Stephen Connolly <
>>> stephen.al...@gmail.com> wrote:
>>>
>> How many people have been able to try this so far?
>>>>
>>> On Tue 20 Jun 2017 at 14:52, Stephen Connolly <stephen.al...@gmail.com> 
>>>> wrote:
>>>>
>>> If you are chomping at the bit, here are all the binaries:
>>>>>
>>>>>
>>>>> https://www.dropbox.com/sh/47weboatdzus22w/AADNF_aBniOyEeQi9MvM82sMa?dl=0
>>>>>
>>>>> SHA1 checksums:
>>>>> d9c346ac8db497a35825c7dbbb934842a2bc429a  branch-api.hpi
>>>>> 16da429f09fb585fd1d744809ee22c8d612fb62c  
>>>>> cloudbees-bitbucket-branch-source.hpi
>>>>> 234fa8eb88dad3241d620bb0116dd12fb9decbba  git.hpi
>>>>> a68be01144f3045f81a5cf3c0bc60ad12f39b643  github-branch-source.hpi
>>>>> 92237097815b45260bb8b272caa9be9f92eb5085  mercurial.hpi
>>>>> 04c321420b3752a8d8b3af89cae1bf5934607b1c  scm-api.hpi
>>>>>
>>>>> SHA256 checksums:
>>>>> 858ce20992c3f179b850c51297084b11fe7c4c173cf6d4d2e07bbfebf3e7  
>>>>> branch-api.hpi
>>>>> 8ebff7a3ec43df276d4b51d1e5bcb910bbe8eb4cd47a4be0e35f2f2ca1cd0e03  
>>>>> cloudbees-bitbucket-branch-source.hpi
>>>>> 46cbbf11395df4a085829094d5a36dee7328aeba00d33e34b44aa0dcf9898248  
>>>>> git.hpi
>>>>> 6495a60f1bf0733d807f412434c6c2e24b7bba53fd7ce348ca5319ef38571f20  
>>>>> github-branch-source.hpi
>>>>> 173d12042fe8582efdb52e740f4e939b9daa05f181c6aaff31824337d519a31c  
>>>>> mercurial.hpi
>>>>> 9b58e9e6d13ce90a91b73f38142bf0977f244df9c52b948988f9d5bdc3785481  
>>>>> scm-api.hpi
>>>>>
>>>>> -Stephen
>>>>>
>>>> On 20 June 2017 at 14:29, Stephen Connolly <stephen.al...@gmail.com> 
>>>>> wrote:
>>>>>
>>>> OK! Here we are... testing time!
>>>>>>
>>>>>> These are the plugins that are being covered: (download links should 
>>>>>> be live in an hour or two)
>>>>>>
>>>>>> scm-api 2.2.0-alpha-1 
>>>>>> https://updates.jenkins.io/download/plugins/scm-api/2.2.0-alpha-1/scm-api.hpi
>>>>>> branch-api 2.0.11-alpha-1 
>>>>>> https://updates.jenkins.io/download/plugins/branch-api/2.0.11-alpha-1/branch-api.hpi
>>>>>> git 3.4.0-alpha-1 
>>>>>> https://updates.jenkins.io/download/plugins/git/3.4.0-alpha-1/git.hpi
>>>>>> mercurial 2.0-alpha-1 
>>>>>> https://updates.jenkins.io/download/plugins/mercurial/2.0-alpha-1/mercurial.hpi
>>>>>> github-branch-source 2.2.0-alpha-1 
>>>>>> https://updates.jenkins.io/download/plugins/github-branch-source/2.2.0-alpha-1/github-branch-source.hpi
>>>>>> cloudbees-bitbucket-branch-source 2.2.0-alpha-1 
>>>>>> https://updates.jenkins.io/download/plugins/cloudbees-bitbucket-branch-source/2.2.0-alpha-1/cloudbees-bitbucket-branch-source.hpi
>>>>>>
>>>>>> Recommended testing procedure:
>>>>>>
>>>>>> 1. Set up a throw-away Jenkins running a version similar to your 
>>>>>> production environment *with the pre-upgrade versions of the plugins 
>>>>>> you are using*.
>>>>>> 2. Set up ideally at least one o

Re: GitHub and Bitbucket branch source UI refactoring

[Michael Neale]

I saw all jobs disappear in a github org folder that blue ocean created 
previously, when I triggered a scan. 

(it also doesn't seem to trigger scans if I add change the pattern, or run 
the wizard again). 

On Thursday, June 22, 2017 at 4:39:30 AM UTC+10, Mark Waite wrote:
>
> I haven't tried it yet.  I'm configuring the "before" state today and will 
> capture its state, then will deploy the new code tomorrow morning and 
> capture the after state.  I won't do anything to compare those until 
> tomorrow evening or this weekend.
>
> Mark Waite
>
> On Wed, Jun 21, 2017 at 12:30 PM Stephen Connolly  > wrote:
>
>> How many people have been able to try this so far?
>>
>> On Tue 20 Jun 2017 at 14:52, Stephen Connolly > > wrote:
>>
>>> If you are chomping at the bit, here are all the binaries:
>>>
>>> https://www.dropbox.com/sh/47weboatdzus22w/AADNF_aBniOyEeQi9MvM82sMa?dl=0
>>>
>>> SHA1 checksums:
>>> d9c346ac8db497a35825c7dbbb934842a2bc429a  branch-api.hpi
>>> 16da429f09fb585fd1d744809ee22c8d612fb62c  
>>> cloudbees-bitbucket-branch-source.hpi
>>> 234fa8eb88dad3241d620bb0116dd12fb9decbba  git.hpi
>>> a68be01144f3045f81a5cf3c0bc60ad12f39b643  github-branch-source.hpi
>>> 92237097815b45260bb8b272caa9be9f92eb5085  mercurial.hpi
>>> 04c321420b3752a8d8b3af89cae1bf5934607b1c  scm-api.hpi
>>>
>>> SHA256 checksums:
>>> 858ce20992c3f179b850c51297084b11fe7c4c173cf6d4d2e07bbfebf3e7  
>>> branch-api.hpi
>>> 8ebff7a3ec43df276d4b51d1e5bcb910bbe8eb4cd47a4be0e35f2f2ca1cd0e03  
>>> cloudbees-bitbucket-branch-source.hpi
>>> 46cbbf11395df4a085829094d5a36dee7328aeba00d33e34b44aa0dcf9898248  git.hpi
>>> 6495a60f1bf0733d807f412434c6c2e24b7bba53fd7ce348ca5319ef38571f20  
>>> github-branch-source.hpi
>>> 173d12042fe8582efdb52e740f4e939b9daa05f181c6aaff31824337d519a31c  
>>> mercurial.hpi
>>> 9b58e9e6d13ce90a91b73f38142bf0977f244df9c52b948988f9d5bdc3785481  
>>> scm-api.hpi
>>>
>>> -Stephen
>>>
>>> On 20 June 2017 at 14:29, Stephen Connolly >> > wrote:
>>>
 OK! Here we are... testing time!

 These are the plugins that are being covered: (download links should be 
 live in an hour or two)

 scm-api 2.2.0-alpha-1 
 https://updates.jenkins.io/download/plugins/scm-api/2.2.0-alpha-1/scm-api.hpi
 branch-api 2.0.11-alpha-1 
 https://updates.jenkins.io/download/plugins/branch-api/2.0.11-alpha-1/branch-api.hpi
 git 3.4.0-alpha-1 
 https://updates.jenkins.io/download/plugins/git/3.4.0-alpha-1/git.hpi
 mercurial 2.0-alpha-1 
 https://updates.jenkins.io/download/plugins/mercurial/2.0-alpha-1/mercurial.hpi
 github-branch-source 2.2.0-alpha-1 
 https://updates.jenkins.io/download/plugins/github-branch-source/2.2.0-alpha-1/github-branch-source.hpi
 cloudbees-bitbucket-branch-source 2.2.0-alpha-1 
 https://updates.jenkins.io/download/plugins/cloudbees-bitbucket-branch-source/2.2.0-alpha-1/cloudbees-bitbucket-branch-source.hpi

 Recommended testing procedure:

 1. Set up a throw-away Jenkins running a version similar to your 
 production environment *with the pre-upgrade versions of the plugins 
 you are using*.
 2. Set up ideally at least one organization folder and one standalone 
 multibranch project building your source code - to a first order you do 
 not 
 care if the builds succeed or fail, only that the branches are found.
 3. Trigger a scan / index of your organization folders and standalone 
 multibranch projects.
 4. Wait for the queue to complete
 5. Run the script in the system script console: 
 https://gist.github.com/stephenc/64ef58783b4438a126ad4e3f43062df1 and 
 save the output to smoke-pre-upgrade.txt
 6. Upgrade the relevant plugins, restart Jenkins.
 7. Run the script in the system script console: 
 https://gist.github.com/stephenc/64ef58783b4438a126ad4e3f43062df1 and 
 save the output to smoke-post-upgrade.txt
 8. Trigger a scan / index of your organization folders and standalone 
 multibranch projects.
 9. Wait for the queue to complete
 10. Run the script in the system script console: 
 https://gist.github.com/stephenc/64ef58783b4438a126ad4e3f43062df1 and 
 save the output to smoke-post-rescan.txt

 At this point, do a diff between smoke-pre-upgrade.txt and 
 smoke-post-rescan.txt

 You are looking for three classes of difference:

 a. branch jobs that have been rebuilt for no reason (i.e. the revision 
 is the same)
 b. branch jobs that have disappeared for no good reason (i.e. the 
 branch is still present in the backing scm)
 c. branch jobs that have suddenly appeared for no good reason (i.e. the 
 branch was there before but not found) [expecting some of these for 
 BitBucket PRs from forks, but only after configuration updated, saved and 
 another rescan performed]

 My expectation is that nobody will have 

New user registration problem

[Michael Neale]

Hi a user with the id of quanlt has tried to signup. They were directed 
to https://wiki.jenkins-ci.org/display/JENKINS/User+Account+on+Jenkins - 
and posted the email to accounts but they are still not activated. How long 
should this take normally? (is this a new anti spam measure?)


-- 
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/d0b1d89f-0897-4724-a0ba-258fb0d001ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[BlueOcean] group/list for ux discussions

[Michael Neale]

Hey all. 

A lot of discussion has happened on JIRA tickets, and sometimes in pull 
request threads (more so in tickets) around blue ocean (and other UX 
related JIRA comment threads which go on quite a bit). 

Some suggested this is best done on a maililng list. Given this is likely 
to be fairly "chatty", Tyler 
created: https://groups.google.com/forum/#!forum/jenkinsci-ux, so feel free 
to "join the conversation" on UX topics if that interests you. 

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/614cfb52-3d9e-4156-a25d-087f1ec24f74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adopting the favorite plugin

[Michael Neale]

Great! 

I have opened a PR for permissions to 
publish: 
https://github.com/jenkins-infra/repository-permissions-updater/pull/105 
(it didn't have any permissions to start with, so hasn't been updated in a 
while according to that... odd). 

Access to the repo is already granted, so just this last piece and a new 
version can be released. 

Thanks Larry !

On Thursday, November 3, 2016 at 9:36:03 AM UTC+11, James Dumay wrote:
>
> Thank you! 
>
> On Thu, Nov 3, 2016 at 8:45 AM Larry Shatzer, Jr.  > wrote:
>
>> I approve this. Thanks for offering to take this up.
>>
>> On Wed, Nov 2, 2016 at 2:57 PM, James Dumay > > wrote:
>>
>>> Hi all,
>>>
>>> I'd like to adopt the favorite plugin 
>>>  as Larry, 
>>> the original author and maintainer, has recently put it up for adoption. My 
>>> github id is i386 and my Jenkins account is jamesdumay.
>>>
>>> I'd like to thank Larry for his great work on the favourites plugin. We 
>>> it extensively in Blue Ocean to provide the favoriting functionality for 
>>> the Personalised Dashboard 
>>> 
>>>  and 
>>> we are planning new extensions to this plugin 
>>> .
>>>
>>> Thanks,
>>> James
>>>
>>
>> -- 
> James Dumay
> Product Manager
> CloudBees, Inc.
> Skype: jdumaycb Twitter: i386
>

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

Re: Dealing with vulnerable plugins

[Michael Neale]

I like the sound of it, and seems a well trodden path as used by those 
other projects mentioned.

On Wednesday, November 2, 2016 at 11:59:28 PM UTC+11, Daniel Beck wrote:
>
> Hi everyone, 
>
> When the security team receives a report about a plugin, we try to contact 
> the maintainer and work with them to fix the issue. But between 
> unmaintained plugins, unresponsive maintainers, or maintainers with no time 
> to fix even security vulnerabilities, this doesn't always work out. 
>
> Unfortunately, the security team does not have the capacity to fix all 
> security vulnerabilities in all plugins -- so we may have reports, but no 
> way to fix the reported problems. Just sitting on the reports and hoping 
> for a new maintainer to dump the issues on is not a solution. 
>
> So what can we do instead? 
>
> My plan is that we adopt a policy similar to that of Wordpress[1] and 
> Drupal[2] (and possibly Typo3[3]): 
>
> We try to contact the maintainer. If they refuse (no time, no interest), 
> or don't respond in a timely manner (several weeks), and the security team 
> doesn't have the capacity to fix it, do the following: 
>
> 1. Publish a security advisory about the plugin, describing the nature of 
> the vulnerability as usual, but noting that there is no fix other than no 
> longer using the plugin (if there are workarounds, include them). 
> 2. Stop publishing the vulnerable plugin on the Jenkins update site. 
> 3. Add metadata to the plugin site indicating vulnerable plugins to inform 
> admins who already have the plugin installed. 
>
> #1 and #2 can be implemented immediately, but #3 needs infra and core 
> support. That said, it's more of a 'convenience' feature. The important 
> bits really are #1 and #2. 
>
> I will implement this plan going forward unless there are well-reasoned 
> objections. 
>
> Daniel 
>
> 1: https://wordpress.org/about/security/ 
> 2: https://www.drupal.org/security-team 
> 3: I found 
> https://typo3.org/teams/security/security-bulletins/typo3-extensions/typo3-ext-sa-2016-020/
>  
> which indicates they use a similar approach. 
>
>
>

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

Re: True High Availability/load balancing for Jenkins. Its possible!!

[Michael Neale]

Very nice Surya. 

I am guessing by looking that most of the magic 
in: https://github.com/suryagaddipati/HaJenkins

I know it is a common pattern to use redis as a queuing mechanism (but some 
point it wasn't really intended) - do you run redis itself in some HA 
configuration? 

On Tuesday, November 1, 2016 at 4:49:55 AM UTC+11, Surya Gaddipati wrote:
>
> You need the following ingredients 
>
>  1. DbBacked builds ( https://github.com/groupon/DotCi ) , i.e no in 
> memory build data.  
>  2. NFS mount for 'jobs' folder to share console output, artifacts ect. 
>  3. Message Passing between various masters ( eg: build queuing, build 
> abort, queue abort ect ) . https://github.com/suryagaddipati/HaJenkins
>  4. No shared agents. You could use any cloud plugin , although I like 
> instant provisioning ones eg: 
> https://github.com/suryagaddipati/jenkins-docker-swarm-plugin
>
>
> Setup: 
>
>  1. Install and configure plugins mentioned above
>  2. Start multiple Jenkins instances with share mounted/symlinked  'jobs' 
> folder . 
>  3. Done. 
>
>
> Method: 
>
>  Build Create: When a build comes into the queue, it gets saved into 
> redis queue 
> 
>  ( 
> I had to hack override Queue Implementation 
> 
>  
> to achieve this).  Build gets picked up any of the masters that are 
> watching the queue. 
>  Build Abort:  Aborting a 'ha build' puts a message into redis queue , 
> which gets processed by all masters 
> and
>  
> the master running the actual build aborts it. 
>  Queued item Abort: Same mechanism as above ^. 
>  Build Execution: Build execution happens in a dynamically created agent. 
>  Build info is written to db via DotCi, and build logs are synced to all 
> masters via NFS. 
>  Build Delete: Build gets deleted in DotCi database. 
>
>
>
>
> I've done some testing and this setup seems to work fine and is totally 
> transparent to end user.  But I haven't done any extensive testing for edge 
> cases.
>
> I am curious to know what experts here think about this. What are the 
> things that could go wrong with a setup like this? 
>
>
> Surya
>

-- 
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/3dc95214-9b8d-424f-a57d-9821e637a56c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: improving WorkspaceCleanupThread in a multi-branch world

[Michael Neale]

FYI Tylers ticket on parallel: 

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

"Nodes allocated inside of parallel() should have their workspaces removed 
immediately"

On Monday, October 10, 2016 at 1:50:57 PM UTC+11, Michael Neale wrote:
>
> On Saturday, October 8, 2016 at 5:27:40 AM UTC+11, Jesse Glick wrote:
>>
>> On Wed, Oct 5, 2016 at 8:07 PM, Michael Neale <mne...@cloudbees.com> 
>> wrote: 
>>
>> Yes, though it currently suffers from the issue that there is no 
>> record on a node of what was what. See my proposal: 
>>
>>
>> https://issues.jenkins-ci.org/browse/JENKINS-2111?focusedCommentId=270320=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-270320
>>  
>>
>
>
> That sounds pretty good, and would solve a lot of ills. 
>  
>
>>
>> > * Improve computed folder to be smarter about removed jobs 
>>
>> Not sure what that means. 
>>
>
>
>
> This was in relation to my PR which was on computed folder (seemed easiest 
> place to clean it up) - however JENKINS-2111 proposal (above) seems to 
> cover this. 
>  
>
>>
>> > * Remove workspaces when things are deleted, as much as possible. 
>>
>> This now happens for workspaces on online agents corresponding to 
>> branch projects that are deleted (via orphaning). 
>>
>
> Great. 
>  
>
>>
>> > Tyler has found a bug 
>> > with parallel 
>>
>> Issue reference? 
>>
>
> Will get Tyler to post it. 
>  
>

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

Re: improving WorkspaceCleanupThread in a multi-branch world

[Michael Neale]

On Saturday, October 8, 2016 at 5:27:40 AM UTC+11, Jesse Glick wrote:
>
> On Wed, Oct 5, 2016 at 8:07 PM, Michael Neale <mne...@cloudbees.com 
> > wrote: 
>
> Yes, though it currently suffers from the issue that there is no 
> record on a node of what was what. See my proposal: 
>
>
> https://issues.jenkins-ci.org/browse/JENKINS-2111?focusedCommentId=270320=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-270320
>  
>


That sounds pretty good, and would solve a lot of ills. 
 

>
> > * Improve computed folder to be smarter about removed jobs 
>
> Not sure what that means. 
>



This was in relation to my PR which was on computed folder (seemed easiest 
place to clean it up) - however JENKINS-2111 proposal (above) seems to 
cover this. 
 

>
> > * Remove workspaces when things are deleted, as much as possible. 
>
> This now happens for workspaces on online agents corresponding to 
> branch projects that are deleted (via orphaning). 
>

Great. 
 

>
> > Tyler has found a bug 
> > with parallel 
>
> Issue reference? 
>

Will get Tyler to post it. 
 

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

Re: improving WorkspaceCleanupThread in a multi-branch world

[Michael Neale]

Tilting at windmills again - this is still biting and there are no 
solutions out there. 

The 3 approaches I can see: 

* Improve workspace cleanup thread (garbage collection is always good) - 
this is a good catch all
* Improve computed folder to be smarter about removed jobs
* Remove workspaces when things are deleted, as much as possible. 

These aren't technically related to pipeline (although Tyler has found a 
bug with parallel) - but they are magnified by git flow with multibranch 
and pipeline.

On Friday, May 13, 2016 at 1:09:27 PM UTC+10, Michael Neale wrote:
>
> So talking in code instead, this could be done in the computed folder: 
>
> https://github.com/jenkinsci/cloudbees-folder-plugin/pull/62
> https://issues.jenkins-ci.org/browse/JENKINS-34781
>
> (doing similar work to what the cleanup thread does, but when it removes 
> the orphaned item). 
>
>
> On Friday, May 13, 2016 at 8:37:45 AM UTC+10, Jesse Glick wrote:
>>
>> On Thu, May 12, 2016 at 6:36 PM, Jesse Glick <jgl...@cloudbees.com> 
>> wrote: 
>> >> it will not cover any changes to item name 
>> > 
>> > Sure, but there is only so much we can do. 
>>
>> …though we could have an `ItemListener.onLocationChanged` which 
>> deletes workspaces from the old location too. 
>>
>

-- 
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/7d91ad03-81ac-41ab-a99d-de42abed3653%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Do we need to use the Jenkins jira?

[Michael Neale]

Given that part of deploying a plugin to update center will result in a 
"component" being created in JIRA for people to open tickets against, it 
means that people will always be able to open tickets in JIRA. 

So while some use github issues, there is a risk that things may be in 2 
places, creating a little more work for maintainers in theory. 


On Saturday, September 17, 2016 at 2:02:38 PM UTC+10, Gavin Mogan wrote:
>
> I know we are supposed to use the Jenkins org in github, but are we 
> required to use the the main jira?
>
> We have issues all over the place and trying to figure out our options.
>

-- 
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/b8a91fb9-2b00-45e7-891f-b625b0d1a392%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fine-grained Artifactory upload permissions

[Michael Neale]

I see the wiki has been updated. If someone opens a HOSTING ticket would it 
make sense to have the permission granted as part of that? 

On Monday, August 22, 2016 at 9:19:54 PM UTC+10, Daniel Beck wrote:
>
>
> > On 22.08.2016, at 11:38, Michael Neale <mne...@cloudbees.com 
> > wrote: 
> > 
> > How will this work with multi module projects? 
> > 
> > One needs to be created for each plugin that makes it up? If it tries, 
> then there is a partial deploy before a failure happens I expect? 
>
> For now, yes. 
>
> The format could support having multiple artifacts per file, making 
> management of multi-module projects easier, I just need to modify the tool 
> accordingly. 
>
> But when introducing a new module, right now there's the risk of that not 
> being prepared in permissions, and failing. 
>
>

-- 
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/f6f3ed4c-feaa-44e6-a05f-407246ad8698%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Fine-grained Artifactory upload permissions

[Michael Neale]

A PR for this - is this kind of right? 
https://github.com/jenkins-infra/repository-permissions-updater/pull/2



On Saturday, August 20, 2016 at 10:18:33 PM UTC+10, Daniel Beck wrote:
>
> Hi everyone, 
>
> I just enabled fine-grained Artifactory upload permissions, limiting who 
> is allowed to upload which artifacts. 
>
> What does this mean for you as Jenkins plugin developers? 
>
> Ideally, nothing more than a quick PR to this repository before you 
> release any particular plugin or other component _for the first time_: 
>
> https://github.com/jenkins-infra/repository-permissions-updater/ 
>
> I initialized permissions based on uploads since January 2014, so if 
> you've uploaded a plugin or other artifact since then, you should be in the 
> list of authorized uploaders (data you can check is in that repo). As this 
> wasn't a fully automated process, and there's a number of special 
> snowflakes in the repository, it's possible I accidentally left you out. In 
> that case, please file a PR as described in that repository's README, and 
> we'll get you set up. 
>
> A few notes: 
>
> - I'm still working through recent hosting requests. If your plugin is 
> unreleased, there is no corresponding permissions file, so uploads may 
> fail. 
> - Documentation beyond this email and the repository README does not yet 
> exist, but it will soon. 
>
> If you have any questions, suggestions, or urgently need a permission to 
> release something, let me know -- via email, directly or in this thread, or 
> contact danielbeck in #jenkins on Freenode. 
>
> Daniel 
>
>

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

Re: Fine-grained Artifactory upload permissions

[Michael Neale]

How will this work with multi module projects? 

One needs to be created for each plugin that makes it up? If it tries, then 
there is a partial deploy before a failure happens I expect? 

On Saturday, August 20, 2016 at 10:18:33 PM UTC+10, Daniel Beck wrote:
>
> Hi everyone, 
>
> I just enabled fine-grained Artifactory upload permissions, limiting who 
> is allowed to upload which artifacts. 
>
> What does this mean for you as Jenkins plugin developers? 
>
> Ideally, nothing more than a quick PR to this repository before you 
> release any particular plugin or other component _for the first time_: 
>
> https://github.com/jenkins-infra/repository-permissions-updater/ 
>
> I initialized permissions based on uploads since January 2014, so if 
> you've uploaded a plugin or other artifact since then, you should be in the 
> list of authorized uploaders (data you can check is in that repo). As this 
> wasn't a fully automated process, and there's a number of special 
> snowflakes in the repository, it's possible I accidentally left you out. In 
> that case, please file a PR as described in that repository's README, and 
> we'll get you set up. 
>
> A few notes: 
>
> - I'm still working through recent hosting requests. If your plugin is 
> unreleased, there is no corresponding permissions file, so uploads may 
> fail. 
> - Documentation beyond this email and the repository README does not yet 
> exist, but it will soon. 
>
> If you have any questions, suggestions, or urgently need a permission to 
> release something, let me know -- via email, directly or in this thread, or 
> contact danielbeck in #jenkins on Freenode. 
>
> Daniel 
>
>

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

Re: Review needed. Change in core: responsive new job name validation

[Michael Neale]

Daniel pointed out an annoyance with the "autocompletion" support with this 
new way of working in the PR (second from last comment) but the code 
refactoring looked good. 

On Monday, August 1, 2016 at 11:46:30 PM UTC+10, Samat Davletshin wrote:
>
> Hello!
> Here I propose to make a change in new job name validation. 
> https://github.com/jenkinsci/jenkins/pull/2416/files
>
> Now the GET request to check new job name for invalid characters is sent 
> only on 'blur' jQuery event. 
>
> That makes a user know about the invalid character only after he entered 
> the name and forces to go back to input field. 
>
> This validation may be improved by the addition of client side check after 
> each typed character ('keyup' jQuery event).
>
> If you can, please review the change and tell if you approve it or not.
>

-- 
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/c25eb5b4-8668-41ec-b2f2-59c51bda5994%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] API and UI URL mismatch behind reverse proxy

[Michael Neale]

Javier - its this type of thing that Ivan excels at. 

"hey Ivan I am seeing this really odd thing"


Ivan: "Oh hahaha I know exactly what that is". 


Everyone needs an Ivan. 

On Tuesday, July 26, 2016 at 5:32:59 PM UTC+10, Javier Martín Caro BEEVA 
wrote:
>
> Wow, I really appreciate it, I wouldn't found it in a million years! :)
>
> Thank you all.
>
> El lunes, 25 de julio de 2016, 8:45:18 (UTC+2), Ivan Meredith escribió:
>>
>> Hi there,
>>
>> It is because your Jenkins instance is in spanish!.
>>
>> There is this bit of code 
>> https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-rest-impl/src/main/java/io/jenkins/blueocean/service/embedded/rest/OrganizationImpl.java#L40
>>  
>> And a quick grep
>>
>> ivan@MacBook-Pro ~/w/jenkins/core/src/main/resources/jenkins/model 
>> (master)$ grep -R -E 'Hudson.DisplayName=.* $' .
>> ./Messages_es.properties:Hudson.DisplayName=Jenkins
>>
>> I created PR https://github.com/jenkinsci/jenkins/pull/2471 to fix it in 
>> Jenkins, 
>>
>> and also JENKINS-36907 
>>  to track it in Blue 
>> Ocean.
>>
>> Switching your language should fix this.I imagine this will be changed in 
>> Blue Ocean quickly too.
>>
>> On Thursday, July 21, 2016 at 8:31:43 PM UTC+12, Javier Martín Caro BEEVA 
>> wrote:
>>>
>>> Hi there!
>>>
>>> We have set up jenkins blue ocean behind a nginx reverse proxy and 
>>> configured successfully the prefix in the url to /jenkins. Despite of 
>>> this, when we access to the blue ocean ui in /jenkins/blue and try to 
>>> access some pipeline, a 422 (unprocessable entity error) is displayed in 
>>> the browser debugging console and a white screen is shown.
>>>
>>> The URL in the browser is like the following (note the encoded space):
>>>
>>> https:///jenkins/blue/organizations/*jenkins%20*
>>> //activity
>>>
>>>
>>>
>>> When we call the blue ocean API for organizations the following 
>>> information is shown (https:///jenkins/blue/rest/organizations/):
>>>
>>>
>>> [{"_class":"io.jenkins.blueocean.service.embedded.rest.OrganizationImpl","_links":{"pipelines":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>>>  
>>> /pipelines/"},"self":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>>>  
>>> /"},"user":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>>>  
>>> /user/"},"users":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>>>  /users/"}},"name":"jenkins "}]
>>>
>>>
>>> Note the white space in the organizations href after /jenkins /pipelines.
>>>
>>>
>>> If we call to 
>>> https:///jenkins/blue/rest/organizations/jenkins/pipelines//runs/
>>>  the following message is shown:
>>>
>>>
>>> {
>>>
>>>   "message" : "Organization jenkins not found",
>>>
>>>   "code" : 422,
>>>
>>>   "errors" : [ ]
>>>
>>> }
>>>
>>>
>>> But if we force the organization to be jenkins%20 
>>> (https:///jenkins/blue/rest/organizations/jenkins%20/pipelines//runs/)
>>>  the information is displayed correctly.
>>>
>>>
>>> Can someone help us to configure the proper name for the organization? We 
>>> thought it was the jenkins url in the settings page but this is set to 
>>> https:///jenkins/. 
>>>
>>>
>>> Old UI is working properly for all pipelines, folder organizations and 
>>> bitbucket team jobs.
>>>
>>>
>>> Thank you and regards!
>>>
>>>
>>>

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

Re: Developing a plugin in Scala

[Michael Neale]

I can't say I have tried scala for plugins before (but have used it a lot 
in the past). 

In my experience when implementing a specific java api, I found it was 
easier to "give in" an implement a shim of the java interface, in java, but 
have it call the scala from there (so the bulk of LOC is in scala, but the 
interfaces are in java). 



On Thursday, June 30, 2016 at 9:58:54 PM UTC+10, Jeremy Marshall wrote:
>
>
> I'm trying to write a plugin in Scala but have run into a road block. 
>
> I put a couple of java wrappers round parameterised types which broke the 
> scala compiler and a java version works using the wrappers.
>
> I think the problem is that scala can't expose java runtime annotations 
> (@Extension) on descriptors back in java so it never appears in the list of 
> extensions
>
> Presumably there is a way of adding a manual descriptor.
>
> my repo is here https://github.com/JeremyMarshall/hello-world-scala-plugin 
> and it uses a modified gradle-jpi builder and needs to be cleaned before 
> building. Its also picky about its version of java
>
> gradle clean server -Dorg.gradle.java.home=/Library/Java/
> JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home
>
> This is the groovy console script which shows the problem
>
> import org.jenkinsci.plugins.hw_scala.HelloWorldBuilder
> import hudson.tasks.BuildStepDescriptor
> import hudson.model.Descriptor
>   
> println(hudson.model.Hudson.instance.pluginManager.plugins)
>
> println "Running plugin enumerator"
> println ""
> def plugins = 
> jenkins.model.Jenkins.instance.getPluginManager().getPlugins()
> plugins.each {println "${it.getShortName()} - ${it.getVersion()}"}
> println ""
> println "Total number of plugins: ${plugins.size()}"
>
> def x = new HelloWorldBuilder('aa')
> print (x.dump())
>
> def y = new HelloWorldBuilder.DescriptorImpl()  
> print (y.dump())  
>   
> //fails 
> //jenkins.model.Jenkins.instance.getDescriptorOrDie(HelloWorldBuilder) 
>   
> jenkins.model.Jenkins.instance.getExtensionList(BuildStepDescriptor)
>  
> Any help gratefully received. I'm new to scala so I'm aware it might not 
> be the finest functional code...
>

-- 
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/585efc8d-6f4f-4a6b-831d-a8b303456abc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] API and UI URL mismatch behind reverse proxy

[Michael Neale]

haha - this is not the first time i18n has bitten URLs. 

Although in this case the extra space is incorrect (but Blue Ocean just 
happens to use that in the URL whereas classic does not). 

On Monday, July 25, 2016 at 4:45:18 PM UTC+10, Ivan Meredith wrote:
>
> Hi there,
>
> It is because your Jenkins instance is in spanish!.
>
> There is this bit of code 
> https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-rest-impl/src/main/java/io/jenkins/blueocean/service/embedded/rest/OrganizationImpl.java#L40
>  
> And a quick grep
>
> ivan@MacBook-Pro ~/w/jenkins/core/src/main/resources/jenkins/model 
> (master)$ grep -R -E 'Hudson.DisplayName=.* $' .
> ./Messages_es.properties:Hudson.DisplayName=Jenkins
>
> I created PR https://github.com/jenkinsci/jenkins/pull/2471 to fix it in 
> Jenkins, 
>
> and also JENKINS-36907 
>  to track it in Blue 
> Ocean.
>
> Switching your language should fix this.I imagine this will be changed in 
> Blue Ocean quickly too.
>
> On Thursday, July 21, 2016 at 8:31:43 PM UTC+12, Javier Martín Caro BEEVA 
> wrote:
>>
>> Hi there!
>>
>> We have set up jenkins blue ocean behind a nginx reverse proxy and 
>> configured successfully the prefix in the url to /jenkins. Despite of 
>> this, when we access to the blue ocean ui in /jenkins/blue and try to 
>> access some pipeline, a 422 (unprocessable entity error) is displayed in 
>> the browser debugging console and a white screen is shown.
>>
>> The URL in the browser is like the following (note the encoded space):
>>
>> https:///jenkins/blue/organizations/*jenkins%20*//activity
>>
>>
>>
>> When we call the blue ocean API for organizations the following 
>> information is shown (https:///jenkins/blue/rest/organizations/):
>>
>>
>> [{"_class":"io.jenkins.blueocean.service.embedded.rest.OrganizationImpl","_links":{"pipelines":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>>  
>> /pipelines/"},"self":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>>  
>> /"},"user":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>>  
>> /user/"},"users":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>>  /users/"}},"name":"jenkins "}]
>>
>>
>> Note the white space in the organizations href after /jenkins /pipelines.
>>
>>
>> If we call to 
>> https:///jenkins/blue/rest/organizations/jenkins/pipelines//runs/
>>  the following message is shown:
>>
>>
>> {
>>
>>   "message" : "Organization jenkins not found",
>>
>>   "code" : 422,
>>
>>   "errors" : [ ]
>>
>> }
>>
>>
>> But if we force the organization to be jenkins%20 
>> (https:///jenkins/blue/rest/organizations/jenkins%20/pipelines//runs/)
>>  the information is displayed correctly.
>>
>>
>> Can someone help us to configure the proper name for the organization? We 
>> thought it was the jenkins url in the settings page but this is set to 
>> https:///jenkins/. 
>>
>>
>> Old UI is working properly for all pipelines, folder organizations and 
>> bitbucket team jobs.
>>
>>
>> Thank you and regards!
>>
>>
>>

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

Re: [Blue Ocean] API and UI URL mismatch behind reverse proxy

[Michael Neale]

also, if you access direct, the extra encoded space, does that appear? 

On Thursday, July 21, 2016 at 6:31:43 PM UTC+10, Javier Martín Caro BEEVA 
wrote:
>
> Hi there!
>
> We have set up jenkins blue ocean behind a nginx reverse proxy and 
> configured successfully the prefix in the url to /jenkins. Despite of 
> this, when we access to the blue ocean ui in /jenkins/blue and try to 
> access some pipeline, a 422 (unprocessable entity error) is displayed in 
> the browser debugging console and a white screen is shown.
>
> The URL in the browser is like the following (note the encoded space):
>
> https:///jenkins/blue/organizations/*jenkins%20*//activity
>
>
>
> When we call the blue ocean API for organizations the following 
> information is shown (https:///jenkins/blue/rest/organizations/):
>
>
> [{"_class":"io.jenkins.blueocean.service.embedded.rest.OrganizationImpl","_links":{"pipelines":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>  
> /pipelines/"},"self":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>  
> /"},"user":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>  
> /user/"},"users":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>  /users/"}},"name":"jenkins "}]
>
>
> Note the white space in the organizations href after /jenkins /pipelines.
>
>
> If we call to 
> https:///jenkins/blue/rest/organizations/jenkins/pipelines//runs/
>  the following message is shown:
>
>
> {
>
>   "message" : "Organization jenkins not found",
>
>   "code" : 422,
>
>   "errors" : [ ]
>
> }
>
>
> But if we force the organization to be jenkins%20 
> (https:///jenkins/blue/rest/organizations/jenkins%20/pipelines//runs/)
>  the information is displayed correctly.
>
>
> Can someone help us to configure the proper name for the organization? We 
> thought it was the jenkins url in the settings page but this is set to 
> https:///jenkins/. 
>
>
> Old UI is working properly for all pipelines, folder organizations and 
> bitbucket team jobs.
>
>
> Thank you and regards!
>
>
>

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

Re: [Blue Ocean] API and UI URL mismatch behind reverse proxy

[Michael Neale]

The "dogfood" instance runs begind nginx at the moment (aside: there have 
been some problems with timing around SSE, but this sounds like you haven't 
got that far). 

so the first /jenkins resolves to the "classic" UI? 

It looks like nginx is stripping off the space somehow... 

I'll see if we can dig up a config that works and compare. 

are you able to share you nginx proxy config? 


On Thursday, July 21, 2016 at 6:31:43 PM UTC+10, Javier Martín Caro BEEVA 
wrote:
>
> Hi there!
>
> We have set up jenkins blue ocean behind a nginx reverse proxy and 
> configured successfully the prefix in the url to /jenkins. Despite of 
> this, when we access to the blue ocean ui in /jenkins/blue and try to 
> access some pipeline, a 422 (unprocessable entity error) is displayed in 
> the browser debugging console and a white screen is shown.
>
> The URL in the browser is like the following (note the encoded space):
>
> https:///jenkins/blue/organizations/*jenkins%20*//activity
>
>
>
> When we call the blue ocean API for organizations the following 
> information is shown (https:///jenkins/blue/rest/organizations/):
>
>
> [{"_class":"io.jenkins.blueocean.service.embedded.rest.OrganizationImpl","_links":{"pipelines":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>  
> /pipelines/"},"self":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>  
> /"},"user":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>  
> /user/"},"users":{"_class":"io.jenkins.blueocean.rest.hal.Link","href":"/blue/rest/organizations/jenkins
>  /users/"}},"name":"jenkins "}]
>
>
> Note the white space in the organizations href after /jenkins /pipelines.
>
>
> If we call to 
> https:///jenkins/blue/rest/organizations/jenkins/pipelines//runs/
>  the following message is shown:
>
>
> {
>
>   "message" : "Organization jenkins not found",
>
>   "code" : 422,
>
>   "errors" : [ ]
>
> }
>
>
> But if we force the organization to be jenkins%20 
> (https:///jenkins/blue/rest/organizations/jenkins%20/pipelines//runs/)
>  the information is displayed correctly.
>
>
> Can someone help us to configure the proper name for the organization? We 
> thought it was the jenkins url in the settings page but this is set to 
> https:///jenkins/. 
>
>
> Old UI is working properly for all pipelines, folder organizations and 
> bitbucket team jobs.
>
>
> Thank you and regards!
>
>
>

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

Re: Building PRs with github branch source

[Michael Neale]

Thanks, yes it makes sense now that I have seen it trigger PR rebuilds when 
master changes. This was surprising at first, but makes sense if you are to 
assume that validated against a merge with master means it is always safe 
to merge. 



On Wednesday, July 13, 2016 at 1:44:21 PM UTC+10, Jesse Glick wrote:
>
> On Tue, Jul 12, 2016 at 5:45 AM, Michael Neale <mne...@cloudbees.com 
> > wrote: 
> > The behavior I am seeing is that when there is an origin PR opened, it 
> kicks off 2 builds, one for the PR and one for the branch 
>
> Well that is what you requested—to build it both ways. 
>
> > even if there is no merge needed with master 
>
> Whether or not a merge is needed may change from build to build. Try 
> committing something to `master`. You should see a second build of the 
> PR job. 
>
> > I can't quite fathom what the help text says 
>
> PRs welcome. 
>
> BTW I did update the formal documentation to make mention of the new 
> options. But whoever is responsible for publishing these updates has 
> so far not done so. Perhaps you can help nudge them. When a 
> documentation person has the time, this documentation ought to get 
> moved to jenkins.io, or whatever the preferred home for plugin 
> documentation is these days (it seems to be in flux). 
>
> > What I would like is for branch to be built, but only an additional 
> build performed IF it actually isn't up to date with master. Is this 
> possible at the moment or not? 
>
> Not as such. Again, the checkboxes just control which *jobs* are 
> defined according to inherent aspects of the branches/PRs. The need 
> for, and validity of, a merge is liable to vary from one commit to the 
> next after the job has been created. 
>
> > Perhaps another option is to not build branches, but only build PRs, 
> then it would only show up once? 
>
> Sure, just uncheck “Build origin branches also filed as PRs”. 
>

-- 
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/1b7781f5-9365-4213-9a6b-aa68e7fdc050%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Building PRs with github branch source

[Michael Neale]

Thanks to a recent update, github branch source can build origin PRs. 

However, I find the choice of checkboxes rather perplexing. 

The behavior I am seeing is that when there is an origin PR opened, it 
kicks off 2 builds, one for the PR and one for the branch, even if there is 
no merge needed with master (in the case of a merge commit validation). 


I can't quite fathom what the help text says, or what combinations to use. 

What I would like is for branch to be built, but only an additional build 
performed IF it actually isn't up to date with master. Is this possible at 
the moment or not? 

Perhaps another option is to not build branches, but only build PRs, then 
it would only show up once? (perhaps that is the expectation?)

-- 
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/bb88e383-3f7a-49a3-9d5f-ae8caa8b1097%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] New pipeline --> 404

[Michael Neale]

<https://lh3.googleusercontent.com/-axHQsKIGpbY/V4S68K0ly9I/BZI/PFAfqhi2KeA-97tLQknUS4pmhzIimieTwCLcB/s1600/its_working_star_wars.gif>

Great. 
I commented on that ticket - if you can follow what it says, would be good 
to know (track the issue there).


On Tuesday, July 12, 2016 at 7:37:22 PM UTC+10, Maelig Gohin wrote:
>
> :o OMG you are right ! It's working !
>
> Le mardi 12 juillet 2016 11:32:55 UTC+2, Michael Neale a écrit :
>>
>> You can just create jobs the normal way in Jenkins. Blue ocean just 
>> redirects to there anyway. Perhaps that button is misleading. 
>>
>> On Tuesday, July 12, 2016 at 6:30:12 AM UTC+10, James Dumay wrote:
>>>
>>> Appreciated Maelig :)
>>>
>>> On Monday, July 11, 2016 at 6:42:29 PM UTC+10, Maelig Gohin wrote:
>>>>
>>>> I just wanted to try, but I spent too much time on it. 
>>>> I can provide some data to help you but I'll not continue trying :)
>>>>
>>>> Le lundi 11 juillet 2016 10:27:08 UTC+2, Baptiste Mathus a écrit :
>>>>>
>>>>> IMO we should take this off this list and into an issue in the big 
>>>>> tracker.
>>>>> Obviously, Maelig you will want to provide as much details as you can 
>>>>> since this issue was defined deemed fixed. Like the full list of 
>>>>> installed 
>>>>> plugins and versions, your platform,jdk version and so on.
>>>>>
>>>>> Cheers
>>>>> Le 11 juil. 2016 9:27 AM, "Maelig Gohin" <mgo...@arca-computing.fr> a 
>>>>> écrit :
>>>>>
>>>>>> I did it at least 5 times.
>>>>>> I'm always starting from a fresh Jenkins installation on my OSX.
>>>>>>
>>>>>> Le lundi 11 juillet 2016 02:00:27 UTC+2, James Dumay a écrit :
>>>>>>>
>>>>>>> Have you tried with a clean Jenkins home or uninstalling all the 
>>>>>>> manually installed Blue Ocean plugins first?
>>>>>>>
>>>>>>> On Saturday, July 9, 2016 at 6:49:55 PM UTC+10, Maelig Gohin wrote:
>>>>>>>>
>>>>>>>> I downloaded the .pkg from Jenkins website.
>>>>>>>> Jenkins ver. 2.7.1 <http://jenkins-ci.org/>
>>>>>>>>
>>>>>>>>
>>>>>>>> Le vendredi 8 juillet 2016 17:14:27 UTC+2, Baptiste Mathus a écrit :
>>>>>>>>>
>>>>>>>>> Do you run the Jenkins war directly for your Jenkins instance, or 
>>>>>>>>> do you deploy in tomcat? Or though rpm or something else?
>>>>>>>>>
>>>>>>>>> Which Jenkins version?
>>>>>>>>> Le 8 juil. 2016 4:52 PM, "Maelig Gohin" <mgo...@arca-computing.fr> 
>>>>>>>>> a écrit :
>>>>>>>>>
>>>>>>>>>> Yes I have full access to jenkins pages, and I also see the Blue 
>>>>>>>>>> Dashboard
>>>>>>>>>>
>>>>>>>>>> Le vendredi 8 juillet 2016 16:45:07 UTC+2, Thorsten Scherler a 
>>>>>>>>>> écrit :
>>>>>>>>>>>
>>>>>>>>>>> Hmm have not tried that myself, but it seems that there maybe 
>>>>>>>>>>> something wrong with the context path. Did you see "classic" 
>>>>>>>>>>> jjenkins 
>>>>>>>>>>> anyway?
>>>>>>>>>>>
>>>>>>>>>>> salu2
>>>>>>>>>>>
>>>>>>>>>>> On Friday, July 8, 2016 at 4:28:51 PM UTC+2, Maelig Gohin wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I'm using now the plugin from the plugin page of jenkins, so I 
>>>>>>>>>>>> don't run any command anymore
>>>>>>>>>>>>
>>>>>>>>>>>> Le vendredi 8 juillet 2016 16:25:44 UTC+2, Thorsten Scherler a 
>>>>>>>>>>>> écrit :
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi Maelig,
>>>>>>>>>>>>>
>>&g

Re: [Blue Ocean] New pipeline --> 404

[Michael Neale]

You can just create jobs the normal way in Jenkins. Blue ocean just 
redirects to there anyway. Perhaps that button is misleading. 

On Tuesday, July 12, 2016 at 6:30:12 AM UTC+10, James Dumay wrote:
>
> Appreciated Maelig :)
>
> On Monday, July 11, 2016 at 6:42:29 PM UTC+10, Maelig Gohin wrote:
>>
>> I just wanted to try, but I spent too much time on it. 
>> I can provide some data to help you but I'll not continue trying :)
>>
>> Le lundi 11 juillet 2016 10:27:08 UTC+2, Baptiste Mathus a écrit :
>>>
>>> IMO we should take this off this list and into an issue in the big 
>>> tracker.
>>> Obviously, Maelig you will want to provide as much details as you can 
>>> since this issue was defined deemed fixed. Like the full list of installed 
>>> plugins and versions, your platform,jdk version and so on.
>>>
>>> Cheers
>>> Le 11 juil. 2016 9:27 AM, "Maelig Gohin"  a 
>>> écrit :
>>>
 I did it at least 5 times.
 I'm always starting from a fresh Jenkins installation on my OSX.

 Le lundi 11 juillet 2016 02:00:27 UTC+2, James Dumay a écrit :
>
> Have you tried with a clean Jenkins home or uninstalling all the 
> manually installed Blue Ocean plugins first?
>
> On Saturday, July 9, 2016 at 6:49:55 PM UTC+10, Maelig Gohin wrote:
>>
>> I downloaded the .pkg from Jenkins website.
>> Jenkins ver. 2.7.1 
>>
>>
>> Le vendredi 8 juillet 2016 17:14:27 UTC+2, Baptiste Mathus a écrit :
>>>
>>> Do you run the Jenkins war directly for your Jenkins instance, or do 
>>> you deploy in tomcat? Or though rpm or something else?
>>>
>>> Which Jenkins version?
>>> Le 8 juil. 2016 4:52 PM, "Maelig Gohin"  
>>> a écrit :
>>>
 Yes I have full access to jenkins pages, and I also see the Blue 
 Dashboard

 Le vendredi 8 juillet 2016 16:45:07 UTC+2, Thorsten Scherler a 
 écrit :
>
> Hmm have not tried that myself, but it seems that there maybe 
> something wrong with the context path. Did you see "classic" jjenkins 
> anyway?
>
> salu2
>
> On Friday, July 8, 2016 at 4:28:51 PM UTC+2, Maelig Gohin wrote:
>>
>> Hi,
>>
>> I'm using now the plugin from the plugin page of jenkins, so I 
>> don't run any command anymore
>>
>> Le vendredi 8 juillet 2016 16:25:44 UTC+2, Thorsten Scherler a 
>> écrit :
>>>
>>> Hi Maelig,
>>>
>>> weird, that url should work. How do you start the plugin, 
>>> standalone, like:
>>>
>>> cd blueocean-plugin
>>> mvn hpi:run
>>>
>>> if so what does the console print when you request the newJob 
>>> page?
>>>
>>> salu2
>>>
>>> On Friday, July 8, 2016 at 4:08:30 PM UTC+2, Maelig Gohin wrote:

 So lucky me, I'm accessing http://localhost:8080/blue/pipelines 
 but when I click on "new pipeline" (goes to 
 http://localhost:8080/view/All/newJob) I'm getting :

 HTTP ERROR 404

 Problem accessing /view/All/newJob. Reason:

 Not Found

 --
 *Powered by Jetty://*



 Le vendredi 8 juillet 2016 15:57:43 UTC+2, Maelig Gohin a 
 écrit :
>
> Nice !
> Never used experimental plugins and don't worry, it's only by 
> curiosity, I'm using it on my local machine to test, no 
> production use yet 
> ^^
>
> Le vendredi 8 juillet 2016 15:54:29 UTC+2, Baptiste Mathus a 
> écrit :
>>
>> Yes, please see 
>> https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/jenkinsci-dev/8HLKwwz3OmU/NVSKvIXuBAAJ
>>
>> Note that this plugin is still alpha, for a reason, so 
>> classical reminder: don't use it in production yet.
>>
>> 2016-07-08 13:50 GMT+00:00 Maelig Gohin <
>> mgo...@arca-computing.fr>:
>>
>>> I don't find the plugin into the list of plugins in the 
>>> update center, I'm missing something ?
>>>
>>> Le vendredi 8 juillet 2016 15:44:33 UTC+2, Baptiste Mathus a 
>>> écrit :

 Not sure what you mean about building.

 Did you use hpi:run to use it as documented, or did you 
 install the plugins by hand?

 If you don't plan to hack on the project's code, then 
 indeed it's strongly recommended to install through the update 

Re: [GSoC2016] Jenkins WebUI

[Michael Neale]

yes, we can, that is fine

On Tuesday, July 12, 2016 at 3:20:02 AM UTC+10, Samat Davletshin wrote:
>
> Hello,
> So can we agree on 8AM UTC on Wednesdays for about 30 minute weekly 
> meetings?
> Michael and Kirill, are you ok with this time?
>

-- 
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/edb9529e-e43d-48b2-9ff3-5b11c9fdecfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What NPM proxies do I need to build Blue Ocean

[Michael Neale]

ie, https://www.npmjs.com/package/@jenkins-cd/js-extensions is the 
js-extensions package. 

So - just mirroring the public one should work (unless as 
per https://docs.npmjs.com/enterprise/mirroring you are whitelisting 
packages)

On Tuesday, July 5, 2016 at 11:11:08 AM UTC+10, Michael Neale wrote:
>
> Loins girded!
>
> Blue Ocean uses the regular public npm repo if I understand correctly, 
> and @jenkins-cd/js-extensions is published there. 
>
> Is it normal to enumerate in the README what can be computed? (assuming it 
> can be)? 
>
> What normally would go in there? 
>
> On Tuesday, July 5, 2016 at 6:35:11 AM UTC+10, Stephen Connolly wrote:
>>
>> Ok, Blue Ocean People... gird your loins...
>>
>> I'm going to put your build through the ringer to make sure that everyone 
>> can build it...
>>
>> So I have set up an NPM proxy for the CloudBees people... It works fine 
>> for Jenkins Core... but for BO we get `404 - Path 
>> /@jenkins-cd/js-extensions not found in group repository NPM 
>> Mirror`
>>
>> So what repositories do I need to mirror. 
>> https://github.com/jenkinsci/blueocean-plugin/blob/master/README.md does 
>> not mention anything about repositories that need to be in your .npmrc
>>
>> FTR this is not just a CloudBees issue, rather this is an issue for 
>> anyone else who wants to work on Blue Ocean behind a corporate proxy... 
>> hence why this mail is in the public domain.
>>
>> -Stephen
>>
>

-- 
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/9a499e8b-0106-4d45-b1f1-c54972b5498e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ERROR: Maven JVM terminated unexpectedly with exit code 137 - Building plugin

[Michael Neale]

It is likely getting things from a nearby proxy transparently, not the 
whole internet being downloaded every time ;)

Also, with regular builds, a warm workspace should be hit after a while (so 
it won't always even download each time). If it hasn't been built for a 
while, it may download things fresh though. 

On Monday, July 4, 2016 at 10:58:59 PM UTC+10, Michael Couck wrote:
>
> Hi Carlos,
>
> Thanks, seems like I can scape through with 512.
>
> Seems like Maven is downloading the entire internet for each build. Is 
> someone cleaning the local m2 repo with each build? Expensive on bandwidth 
> no? And time consuming of course.
>
> Cheers,
> Michael
>
> On Monday, 4 July 2016 14:19:25 UTC+2, Carlos Sanchez wrote:
>>
>> IIUC You are hitting the memory limits and the kernel is killing your 
>> process.
>> You are setting Xmx for surefire to 1GB, you should try lowering it if 
>> your tests don't really need that much memory.
>> https://github.com/jenkinsci/serenity-plugin/blob/master/pom.xml#L60
>>
>> On Mon, Jul 4, 2016 at 1:37 PM, Michael Couck  
>> wrote:
>>
>>> Hi all,
>>>
>>> I am getting the above on the CloudBees build for the Serenity plugin(
>>> https://jenkins.ci.cloudbees.com/job/plugins/job/serenity-plugin/). I 
>>> have seen this has popped up before, and seemingly it is a memory issue. 
>>> Unfortunately I don't have access to the job to increase the memory to see. 
>>> Could I get a little more memory please? Pretty please? ;) Perhaps 1024?
>>>
>>> The build is quite memory intensive in fact, exactly how much I wouldn't 
>>> know, but on my Jenkins I run the build with a gig, and that seems to be 
>>> enough. Of course the build works perfectly on my laptop, and on my server 
>>> running Jenkins, with the above memory parameters. Could be something else 
>>> of course, but for the life of me I can't imagine what. The jdk is the 
>>> same, and even the os is the same. There is some classloading interference, 
>>> but it is in a forked JVM so should be quite safe.
>>>
>>> Incidentally the build was running fine until I started fiddling around 
>>> with the profiler again...
>>>
>>> Sorry for the bother :( but I am stuck.
>>>
>>> Cheers,
>>> Michael
>>>
>>> -- 
>>> 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/8187fb6d-1fc2-48c8-ba6e-5f136ee78106%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/16208786-3096-4302-b00d-f98be86f6d8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What NPM proxies do I need to build Blue Ocean

[Michael Neale]

Loins girded!

Blue Ocean uses the regular public npm repo if I understand correctly, 
and @jenkins-cd/js-extensions is published there. 

Is it normal to enumerate in the README what can be computed? (assuming it 
can be)? 

What normally would go in there? 

On Tuesday, July 5, 2016 at 6:35:11 AM UTC+10, Stephen Connolly wrote:
>
> Ok, Blue Ocean People... gird your loins...
>
> I'm going to put your build through the ringer to make sure that everyone 
> can build it...
>
> So I have set up an NPM proxy for the CloudBees people... It works fine 
> for Jenkins Core... but for BO we get `404 - Path 
> /@jenkins-cd/js-extensions not found in group repository NPM 
> Mirror`
>
> So what repositories do I need to mirror. 
> https://github.com/jenkinsci/blueocean-plugin/blob/master/README.md does 
> not mention anything about repositories that need to be in your .npmrc
>
> FTR this is not just a CloudBees issue, rather this is an issue for anyone 
> else who wants to work on Blue Ocean behind a corporate proxy... hence why 
> this mail is in the public domain.
>
> -Stephen
>

-- 
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/3a24ac11-eab6-4c0c-9779-a1c24e0fff68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Blue Ocean] Alpha now available in experimental update center

[Michael Neale]

For those who are curious, and have a not very well developed sense of 
danger (joking!), Blue Ocean is available on the experimental update centre 
.

This is "alpha" for a reason, its still a very early version, and not 
feature complete. Notably, there is no paging of data in the front end code 
(although backend supports it) so it could make page loads slower than they 
should be. This is not for production use yet of course. 

I have verified it with the latest weekly (it requires a > 2.2 version). 

To install: 

1) add experimental update centre to the advanced tab of your plugins 
(ensure you have a Jenkins > 2.2, the current LTS won't do yet)
2) click on "Available" tab, Refresh the list (button down the bottom)
3) install the "(Alpha) Blue Ocean UX" plugin (it will drag in what 
dependencies it needs)

There are a bunch of other blueocean plugins which are just dependencies. 
Unfortunately they show up as "peers" of the real plugin you want to 
install: 




(I am sure there is a ticket open to allow for "library" plugins so they 
don't show up like this... if anyone knows the number let me know). 


Hopefully there will be quite frequent releases of this, as a lot is 
changing daily right now. 



Enjoy!
 

-- 
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/e47fe0cf-f8d4-46fa-bd43-d5d3406a8b6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed to connect to repository : Remote host closed connection during handshake

[Michael Neale]

There may be more in the main Jenkins log from when that happens. It could 
be an SSL/TLS related or network issue between your gitlab instance and 
Jenkins. 

On Monday, July 4, 2016 at 4:50:38 PM UTC+10, Sharon Francis wrote:
>
> I'm Getting this error while trying to connect to git repo through 
> jenkins. 
>
> if anyone has faced this issue pls share your views.
>

-- 
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/ed83af0e-a408-416d-ac9a-4a636edc4cf9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: help wanted: releasing to experimental update center (blue ocean)

[Michael Neale]

Thanks stephen. 

And as Baptiste pointed out (on irc) this pattern is used in the 1.10.x 
lineage of pipeline plugins 
(https://github.com/jenkinsci/pipeline-plugin/tree/1.10.x). 

I just did a push again with the  elements, and will see tomorrow (my 
time) if things land correctly in the experimental update centre and report 
back. 

Thanks!

On Monday, July 4, 2016 at 7:34:29 PM UTC+10, Stephen Connolly wrote:
>
> The check for a  in the pom does not take into account inheritance 
> from the parent. This is perhaps deliberate, but the check certainly could 
> be refined for these multi-module releases... 
>
> On the other hand the  property is one of the "magic" ones whereby if 
> unspecified it is the parent url plus the artifactId (depending on whether 
> the parent url has or doesn't have a trailin / or some other silly 
> convention) so perhaps it is best to force the "must override" rule
>
> On 4 July 2016 at 03:45, Michael Neale <mne...@cloudbees.com 
> > wrote:
>
>> Need some help from someone experienced in deploying new plugins. 
>>
>> Last week a release was performed on blue ocean, to get it to the 
>> experimental update center, but it hasn't shown up. 
>>
>> Blue ocean is a multi module project, with a few plugins, so this is a 
>> bit unfamiliar to most (pipeline was originally deployed this way). 
>>
>> Following the guide as per 
>> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins, there is a 
>> wiki https://wiki.jenkins-ci.org/display/JENKINS/Blue+Ocean+Plugin page 
>> setup in the pom.xml. 
>>
>> The plugins show up in the repo: 
>> http://repo.jenkins-ci.org/public/io/jenkins/blueocean/ 
>> but not in the update center: 
>> http://updates.jenkins-ci.org/experimental/update-center.json
>>
>>
>>
>> Perhaps given the plugin that people will in stall is the "aggregator" - 
>> should the  to the wiki page be in the blueocean-plugin submodule 
>> instead of on the parent? 
>>
>>
>>
>> Any reviews/tips appreciated: 
>> https://github.com/jenkinsci/blueocean-plugin
>>
>> The link at the bottom 
>> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins points to a 
>> non existent job that has the update center build log, so it isn't easy to 
>> see if something is going wrong. 
>>
>>
>>
>>
>> -- 
>> 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/b52ccf97-edfa-46c5-94e9-82f5770f70dd%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/b52ccf97-edfa-46c5-94e9-82f5770f70dd%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: [GSoC2016] Jenkins WebUI

[Michael Neale]

That sounds good to me.

I have 30 min put aside weekly for the office hours on Wednesday I think
8AM UTC. Would that be too early ? (I think it's a little early for Tom,
but you know you can reach him as needed)

Updates are OK to list or google doc. The list makes sense if it's progress
or you want feature discussion but a Google doc is also good.
On Sun, 3 Jul 2016 at 6:41 AM, Samat Davletshin  wrote:

> CC Tom, Kirill, Michael.
>
> Hello,
>
> 1. What do you think about weekly 30 minutes (or so) meeting for WebUI
> project? As discussed during last office hours, Oleg suggested that it
> could be good to meet weekly for the project. Especially since the general
> office hours will not be regularly conducted anymore. I think that could be
> an efficient way to discuss the project. Personally, I would like to try it
> since it seems like there can be more useful information for me, taking
> less of your time.
> What do you think? If you agree, we can decide a time and day for those
> who will participate. I think I can adjust to basically any time.
>
> 2. As discussed in office hours also, I think it would better post my
> daily progress in a Google Doc rather than here. Here is the link
>
> https://docs.google.com/document/d/1bImzlfHLIUpkQd23EzufkvRx7AzXt6Q-4Ic2Zz67NwE/edit?usp=sharing
> I will try to write there daily about what I did every day. You can also
> comment there if you want.
>

-- 
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/CAKVMTi5F4d05kuE2%2B%2B0-AYON2c419hMFMjJorT51JMhavWes%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

help wanted: releasing to experimental update center (blue ocean)

[Michael Neale]

Need some help from someone experienced in deploying new plugins. 

Last week a release was performed on blue ocean, to get it to the 
experimental update center, but it hasn't shown up. 

Blue ocean is a multi module project, with a few plugins, so this is a bit 
unfamiliar to most (pipeline was originally deployed this way). 

Following the guide as 
per https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins, there is a 
wiki https://wiki.jenkins-ci.org/display/JENKINS/Blue+Ocean+Plugin page 
setup in the pom.xml. 

The plugins show up in the 
repo: http://repo.jenkins-ci.org/public/io/jenkins/blueocean/ 
but not in the update center: 
http://updates.jenkins-ci.org/experimental/update-center.json



Perhaps given the plugin that people will in stall is the "aggregator" - 
should the  to the wiki page be in the blueocean-plugin submodule 
instead of on the parent? 



Any reviews/tips appreciated: 
https://github.com/jenkinsci/blueocean-plugin

The link at the bottom 
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins points to a non 
existent job that has the update center build log, so it isn't easy to see 
if something is going wrong. 




-- 
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/b52ccf97-edfa-46c5-94e9-82f5770f70dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Add an "In Review" state to JIRA?

[Michael Neale]

Given that most tickets/changes spend some time in PR-review state, this is 
exactly what in-review is for, so no real change for anyone.
They can choose to place an issue "in review" to save people thinking that 
there is still code being written for it (or they can leave it as is). 




On Friday, July 1, 2016 at 9:42:43 PM UTC+10, Daniel Beck wrote:
>
> How would the workflow change? I.e. what state transitions will be 
> added/removed? 
>
> > On 01.07.2016, at 00:39, James Dumay  
> wrote: 
> > 
> > Hi all, 
> > 
> > Blue Ocean had previously had an "In Review" state in JIRA to track 
> which changes are in development but are ready for review as a PR when we 
> had these tickets in a private JIRA. 
> > 
> > The developers working on Blue Ocean would like to introduce it again so 
> we  have a more accurate state for where each other's work is at. For the 
> design work the In Review state means that a design is "ready enough" 
> (proposed, rather than just spitballing) to receive input from the wider 
> community. In that last case we would be using this status to facilitate 
> feedback on UX with the community. 
> > 
> > Would there be any objections to adding this to the JENKINS project's 
> JIRA workflow? There should be minimal/no impact for other users. 
> > 
> > Request is being tracked on 
> https://issues.jenkins-ci.org/browse/INFRA-802   
> > 
> > Thanks, 
> > James 
> > 
> > -- 
> > 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/96ed51c5-dd8c-4090-8723-3bc226c04c20%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/2585055c-8ef9-45bf-854d-377493b1e71c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Jenkins WebUI

[Michael Neale]

So how does this work if there is existing help and someone wants to 
improve it? Do they get a blank screen to add additional information? 



On Wednesday, June 29, 2016 at 8:58:03 PM UTC+10, Samat Davletshin wrote:
>
> Hello,
> The fixes of first popup project are currently in progress. Tom helps a 
> lot with it.
> Yesterday I was mostly watching and reading about plugin development since 
> I may have to create one for my next project.
> The functionality to change help information will consist of front-end 
> interface (with which I would like to start) and back-end functionality to 
> save and use changed help information.
> As discussed with Kirill, the is likely no need to rewrite existing help 
> info. Since usually there is a need just to add some additional 
> information, a separate text box me be used, as displayed below.
>
>[image: http://i.imgur.com/zoSvB1G.gif]
>

 

-- 
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/9eb006ad-211d-410c-91a3-72386d26a0fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] an acceptance test harness

[Michael Neale]

Tom is best positioned to answer, but more the style of writing front end 
tests in js. 

On Wednesday, June 29, 2016 at 2:25:13 AM UTC+10, Jesse Glick wrote:
>
> On Tue, Jun 28, 2016 at 3:04 AM, Michael Neale <mne...@cloudbees.com 
> > wrote: 
> > This exercises things via javascript 
>
> What is the advantage over the existing ATH utilities? Seems like you 
> are preventing people from reusing knowledge of ATH idioms. 
>
> > It also has a mode that lets you run it 
> > against a "long running" jenkins, which can speed up the iteration cycle 
> in 
> > developing tests (vs waiting for a fresh launch each time). 
>
> You like 
> https://github.com/jenkinsci/acceptance-test-harness/blob/c35e9b940864f2ce76debc45c9712e36c1bbb644/docs/PRELAUNCH.md
>  
> ? 
>

-- 
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/97c3c4bc-9090-4a87-be35-f28da996be5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Blue Ocean] an acceptance test harness

[Michael Neale]

For those that are interested, based on the main Acceptance Test Harness 
(https://github.com/jenkinsci/acceptance-test-harness)

there is one with blue ocean specifics (built by Tom Fennelly): 
https://github.com/jenkinsci/blueocean-acceptance-test

This exercises things via javascript, for 
example: 
https://github.com/jenkinsci/blueocean-acceptance-test/blob/master/src/test/js/smoke.js
 
is a smoke test scenario. 

I thought this may interest some. It also has a mode that lets you run it 
against a "long running" jenkins, which can speed up the iteration cycle in 
developing tests (vs waiting for a fresh launch each time). 

-- 
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/ecd3e261-70b2-4909-a3c2-8d60e6c7f8b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline as a code events mechanism

[Michael Neale]

thanks! good to hear. 

I know Tom Fennelly was working on some other ways to get at these events, 
so there may be better code examples soon. 

Whatever you end up doing, post it here as others may likely benefit from 
this as well. 

On Monday, June 27, 2016 at 11:49:27 PM UTC+10, Ido Gadiel wrote:
>
> Hi Michael, thanks for your answer.
> You helped a lot!
>
>

-- 
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/e9f90663-2d49-44e1-8781-5b935f6a8c4e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline as a code events mechanism

[Michael Neale]

Hi Ido. 

Yes, there is a way. If you excuse my scratchings: 

https://github.com/jenkinsci/blueocean-plugin/blob/a2f6c7376b88b2a93bf0d4a68238099174d11560/blueocean-rest-impl/src/main/java/io/jenkins/blueocean/service/embedded/util/StageEventRunListener.java

I was trying to listen for the same. A run listener registers a graph 
listener - and from that, there are many events. 

On Sunday, June 26, 2016 at 8:23:11 PM UTC+10, Ido Gadiel wrote:
>
> Hi everybody! 
>
> I am trying to get events from the “Stages” that created by the groovy 
> script. 
> For “regular” jobs, we extended the  RunListener class, and got the 
> onStarted & onComplete methods, 
> But that doesn’t seems to work with those new “Stages”. 
>
> Is there any way to make a registration for a WorkflowJob’s (or 
> WorkflowRun )  events ? 
> Is there any other class to extend in order the get events? 
>
> Thank you very much, 
> Ido 
>
>

-- 
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/08306e27-4164-474d-b7de-fc8b52dd6205%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

variant plugin is missing in action - no wiki page or hpi in repo

[Michael Neale]

https://github.com/jenkinsci/variant-plugin

has no corresponding wiki page. 

https://updates.jenkins.io/latest/variant-plugin.hpi 
or https://updates.jenkins.io/latest/... shows no trace of it

I have created the wiki page as recommended by Baptiste so hopefully the 
next UC generation should pick it up, right? 




-- 
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/a14db244-6c1f-452c-aed1-657f94106e45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [BlueOcean] Roadmap/Issues for contribution

[Michael Neale]

Hi Sundar, great!

For beginner defects, there probably are a few. Often things that may 
appear easy may be annoyingly hard (but perhaps it helps teach things on 
the way, so worth it), so don't go crazy over something you think should be 
easy but it ends up hard!

Some recent examples: 

https://issues.jenkins-ci.org/browse/JENKINS-36102
https://issues.jenkins-ci.org/browse/JENKINS-36065
https://issues.jenkins-ci.org/browse/JENKINS-36100

But really - anything on the blueocean-plugin component that you wanted to 
look at that makes sense to you would be a good way to learn, or perhaps 
you encountered a new unknown problem. 

On Tuesday, June 21, 2016 at 5:16:58 AM UTC+10, Sundar wrote:
>
> Hey James,
>
> Thanks for the pointer!
>
> I am looking into the issues currently and would like to start with small 
> fixes, get familiar with architecture and structure of the project - and 
> later incrementally contribute on new ideas/development.
>
> Do you know if there is any list of beginner defects to work on? 
> Appreciate any pointers.
>
> Thanks,
> Sundar
>
>
>
> On Sunday, June 19, 2016 at 2:17:19 AM UTC-7, James Dumay wrote:
>>
>> Hi Sundar,
>>
>> Great to hear that you are exited about Blue Ocean and want to contribute!
>>
>> We are using the issues.jenkins-ci.org "blueocean-plugin" component to 
>> track the work. If you are interested on a ticket please comment to express 
>> your interest and I'll make sure that one of our developers can get you up 
>> and running.
>>
>> I need to publish a more formal roadmap but Jenkins.io/projects/blueocean 
>> is a good description for what we want to do for the 1.0.
>>
>> Is there anything in particular you would like to work on?
>>
>> Cheers
>> James
>>
>>

-- 
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/803467d5-b935-45b2-8f55-a102acab43e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker image security scan

[Michael Neale]

Those scans are useful for spotting parts of the the linux image layers 
that make up a docker image, that are problematic, and likely easy to 
remedy by refreshing things. 

For spotting stuff inside apps, the signal to noise ratio seems very low. 

On Tuesday, June 21, 2016 at 8:57:41 AM UTC+10, Kohsuke Kawaguchi wrote:
>
> Thanks. Some of the vulnerabilities doesn't apply to us (for example the 
> spring vulnerability that only affects JSP), but I don't suppose these 
> scanners would be able to make such a distinction.
>
> I'll file this as a SECURITY ticket so that the team can discuss any 
> legitimate issues that need fixing, as well as whether anything can be done 
> to avoid scaring users about vulnerabilities that do not apply.
>
>
> On Wed, Jun 15, 2016 at 1:05 AM Carlos Sanchez  > wrote:
>
>> Hi, 
>>
>> The last docker image for 1.651.3 is up in the docker hub.
>>
>> The official images are now security scanned, and you can see the results 
>> at https://hub.docker.com/r/library/jenkins/tags/1.651.3/ (need to be 
>> logged in)
>>
>> Some layers come from the parent Debian and Java images, but the last 
>> ones are from Jenkins war, showing several CVEs for Spring (critical), 
>> Groovy (critical), httpclient, commons-compress, xstream and jbcrypt
>>
>> -- 
>> 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/caf20fac-70d0-4429-8335-ed3366105982%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/0c653bce-c3be-4177-976b-b60646b38abc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Blue Ocean] backlog of issues are now in JENKINS jira project

[Michael Neale]

Thanks to some shaved yaks (Tyler, James Dumay), there is a bit of backlog 
of issues added to the blueocean-plugin component in JIRA. 

As always, open new tickets against the "blueocean-plugin" component. 




https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=171=planning=JENKINS-35773=visible

-- 
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/46f6b980-5c7a-42fb-b5dc-2ef77a1fb1cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [BlueOcean] Error during maven installation "Illegal character in path at index 32: https://nodejs.org/dist/v5.8.0/${node.download.file}"

[Michael Neale]

Wow, glad you worked that out!

Yes the front end pluging picks an appropriate pre-made node binary for the 
platform. This has happened before with BSD (no premade binaries exist for 
freebsd though, as far as I know). 

I assume you are showing up as i386 as you are 32bit? 

Did that change work? 

The repo that has the configuration for what node version to download is 
here: https://github.com/jenkinsci/plugin-pom/blob/master/pom.xml in the 
https://github.com/jenkinsci/plugin-pom/ repo. 



On Wednesday, June 15, 2016 at 7:44:51 AM UTC+10, Quentin Dufour wrote:
>
> Problem was due to my (old ?) architecture : i386.
> There is no entry for nodejs and linux i386.
>
> I've solved the problem by adding the following to * 
> ~/.m2/repository/org/jenkins-ci/plugins/plugin/2.10/plugin-2.10.pom* :
>  
>   node-classifier-linux-i386
>   
> 
>   Linux
>   i386
> 
>   
>   
> 
> node-v${node.version}-linux-x86.tar.gz
> 
>   
> 
>
> When I'll be sure that it solves the problem, I would be happy to propose 
> a pull request to JenkinsCI but I'm not sure of the corresponding file in 
> the repository.
> I'm supposing its 
> https://github.com/jenkinsci/jenkins/blob/00fc80fe29c4dd02afb6052715f3926bed6a8695/war/pom.xml
>
> I will try to test that tomorrow.
> Sorry for the useless post, I hope it will help someone :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/161536de-e459-4c75-8cba-f4321fd4ac9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean on a Windows 10 machine

[Michael Neale]

You said you had it working previously? 

On Tuesday, June 14, 2016 at 3:08:38 PM UTC+10, fkp...@gmail.com wrote:
>
> Thanks - but i'm still having strange difficulties runningthe plugin 
> similar to the Win 7 issues that were discussed previously.
>
> i'm adding my screen logs - after several retries to reinstall the plugin 
> (is it fit to run behind a corporate proxy? maybe that's the cause to all 
> the problems) - and now it simply won't run.
>
> be glad for any help.
>
>
> On Tuesday, June 14, 2016 at 6:51:55 AM UTC+3, Michael Neale wrote:
>>
>> Hey - that's cool!
>>
>> There is no "create pipeline" feature yet in blue ocean, hence it takes 
>> you to the classic UI. 
>>
>> For building plugins, 
>> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin 
>> is a sample plugin that you can look at. 
>> What is the plugin you are interested? many plugins will need to have the 
>> right extension point added in blue ocean which may not already be there. 
>>
>> On Tuesday, June 14, 2016 at 1:15:13 AM UTC+10, fkp...@gmail.com wrote:
>>>
>>> Finally succeed installing it on the machine after reinstalling with 
>>> jenkins 2.8.
>>> But couldn't use mvn run:hpi - >> installed all the plugins manually 
>>> from the folder with upload and then ran it. and it works =)
>>> Now the (great) ui works - but when i press new pipeline - it takes me 
>>> to the old screen - is it ok?
>>>
>>> Starting to check compatability between our plugin to the new UI - any 
>>> suggestions as where should i start the conversion? and how?
>>>  
>>>
>>> On Friday, June 10, 2016 at 6:44:30 PM UTC+3, fkp...@gmail.com wrote:
>>>>
>>>> Hi,
>>>> tried to compile the project to start testing related plugins on the 
>>>> project ui.
>>>> related tool versions:
>>>>
>>>>1. maven 3.3.9
>>>>2. jenkins 2.8 (latest release) - tried also with stable lts 
>>>>1.651.2 (same problems).
>>>>
>>>> attaching the build log after several retries, I read the past thread 
>>>> on win 7 issues but it seems as a different problem.
>>>>
>>>>
>>>>
>>>> Thanks ahead,
>>>>
>>>> Yafim.
>>>>
>>>>
>>>>
>>>>
>>>>

-- 
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/4f5aa36b-1375-47ad-9039-8308b86d978e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean on a Windows 10 machine

[Michael Neale]

Hey - that's cool!

There is no "create pipeline" feature yet in blue ocean, hence it takes you 
to the classic UI. 

For building 
plugins, 
https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin 
is a sample plugin that you can look at. 
What is the plugin you are interested? many plugins will need to have the 
right extension point added in blue ocean which may not already be there. 

On Tuesday, June 14, 2016 at 1:15:13 AM UTC+10, fkp...@gmail.com wrote:
>
> Finally succeed installing it on the machine after reinstalling with 
> jenkins 2.8.
> But couldn't use mvn run:hpi - >> installed all the plugins manually from 
> the folder with upload and then ran it. and it works =)
> Now the (great) ui works - but when i press new pipeline - it takes me to 
> the old screen - is it ok?
>
> Starting to check compatability between our plugin to the new UI - any 
> suggestions as where should i start the conversion? and how?
>  
>
> On Friday, June 10, 2016 at 6:44:30 PM UTC+3, fkp...@gmail.com wrote:
>>
>> Hi,
>> tried to compile the project to start testing related plugins on the 
>> project ui.
>> related tool versions:
>>
>>1. maven 3.3.9
>>2. jenkins 2.8 (latest release) - tried also with stable lts 1.651.2 
>>(same problems).
>>
>> attaching the build log after several retries, I read the past thread on 
>> win 7 issues but it seems as a different problem.
>>
>>
>>
>> Thanks ahead,
>>
>> Yafim.
>>
>>
>>
>>
>>

-- 
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/da2bc694-c785-42d7-a137-5e9444a2227d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Studying the evolution of Jenkins project

[Michael Neale]

Hi Igor. Others are better qualified to answer, but for github - I think 
most projects that migrate there from other platforms obtain more 
contribution due to the basic popularity of github, and visibility. 



On Wednesday, June 8, 2016 at 6:03:23 AM UTC+10, Igor Steinmacher wrote:
>
>
> Hi there, 
>
> I'm a researcher studying software evolution. As part of my current 
> research, I'm studying the implications of open-sourcing a proprietary 
> software, for instance, if the project succeed in attracting newcomers. 
> Jenkins was in my list. 
>
> To further analyze the impacts of Jenkins migration, we analyzed the git 
> log commit history of your project in terms of number of contributions, 
> number of newcomers, and number of contributors per month. The following 
> figure presents a temporal perspective regarding these three measures. 
>
> ​
>
> Given the numbers presented in the graphic, we would like to ask Jenkins 
> developers the following questions: 
>
> 1. What motivated the project to migrate to Github? How do you evaluate 
> the benefits of this migration?2. Does this snapshot make sense? Did you 
> find any inconsistency on the data?
> 3. Do you have any internal policy to promote/attract/retain newcomers? If 
> so, do them succeed?
> 4. Why did the number of contributors increased after its migration to 
> GitHub? Was it expected? 
>
> Thanks in advance for your collaboration, 
>
> Igor Steinmacher, PhD
> http://www.igor.pro.br   
>

-- 
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/93ba79f4-30e2-4147-a3bc-c5663ea16720%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Design for "Loading Screens"

[Michael Neale]

Some good ideas in there. 

One thing I am curious about is if people look for their "browser loading" 
as a sign of "things happening" (I am not actually sure myself, I think I 
ignore it) - which makes interstitials even more important (including some 
animation to show action). 

Facebook seems to do a good job at this, and now I think of it, I pay no 
mind to what my browser says, in fact, as I use chrome, it kind of hides it 
out of the way. I have to look right at the top at a tiny tab-spinner, or 
down the bottom left for very pale text telling me what assets it is 
loading. 

So yes, this is important!

On Wednesday, June 8, 2016 at 5:40:12 AM UTC+10, Cliff Meyers wrote:
>
> I wanted to take an opportunity to share some work I've been doing around 
> the user experience in Blue Ocean, specifically in the area of "progress 
> and interstitial states", more commonly known as "loading screens."
>
> We want to make sure that users understand when the application is busy 
> loading data and we want the transition from "loading" to a rendered screen 
> to be as smooth and aesthetically-pleasing as possible.
>
> Under the hood, we want be able to realize this experience with a minimal 
> amount of boilerplate code, and develop a toolkit that makes it easy for 
> others to adopt the same design elements. To that end, I've produced a 
> design document that discusses some of the challenges (and possible 
> technical solutions) around all this:
>
>
> https://docs.google.com/document/d/1DMuhbLlq7vJYOjory4AQWnSolhhK23Wu6DbExRDkgTY/edit#
>
> The document also briefly touches on error states in a few places, as they 
> are fairly closely related to progress states and could be handled 
> similarly. The doc also links out to a branch in Github that illustrates 
> how this could work in the context of the current Blue Ocean code base.
>
> Please go ahead and share any thoughts you have here on the thread. 
> Looking forward to your feedback!
>
> -Cliff
>

-- 
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/dbc6a278-99ec-4994-93ed-7f322025ba46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean : Dashboard in a Windows 7 PC

[Michael Neale]

Right - I guess if the aim is to just try things, this will be in the 
update center soon one way or another for people to try. 

In the meantime, if all the hpi's are copied into the plugins dir of a 
running jenkins (and transitive dependencies satisfied) - then it should 
work. 

On Wednesday, June 8, 2016 at 4:22:27 AM UTC+10, Tom Fennelly wrote:
>
> On Tuesday, June 7, 2016 at 5:23:18 PM UTC+1, Ian Ceicys wrote:
>>
>> I tried the same steps and got the same result as Itai
>>
>
> My guess is that the symlink in blueocean-web is screwing things up for 
> windows hence no styles etc. 
>

-- 
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/e7145900-2a17-40b9-8ebd-7a89684d3abf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Jenkins WebUI

[Michael Neale]

On Monday, June 6, 2016 at 10:00:21 PM UTC+10, Samat Davletshin wrote:
>
> Hello!
> I would like to ask about item types when a new job is created.
> It seems that add-item.js puts item types into categories: 
> standalone-projects, uncategorized, nested-projects.
>
> What is the purpose of these categories? Are they somehow involved in UI? 
> Is there a work in progress related to the categories and/or item types?
>


I think there was some work at one point in showing them differently, but 
what is in Jenkins 2 is not categorised as you can see. I am not sure if 
they have any current meaning or future plans. 
 

>
> I was trying to place item types in two columns but was a bit confused by 
> the structure.
> Additionally, how does add-item.js gets the data to know which item types 
> should be displayed?
>

-- 
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/ff1a85a6-84bb-4f45-afe0-b0bd5979f5db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean : Dashboard in a Windows 7 PC

[Michael Neale]

7.3.msi) as there 
>>>>>>> appears to be an issue running Python 3.5.1.
>>>>>>>
>>>>>>> *3 min Video of the Repo Steps:* 
>>>>>>> https://www.youtube.com/watch?v=zetNEjLYX2Q?version=3=hd1080
>>>>>>>
>>>>>>> Error Message: 
>>>>>>> [INFO] [12:27:17] Finished 'less_bundle_extensions_bundle_4' after 
>>>>>>> 5.74 ms
>>>>>>> [INFO] [12:27:18] LESS CSS pre-processing completed to 
>>>>>>> 'target/classes/org/jenki
>>>>>>> ns/ui/jsmodules/blueocean_dashboard'.
>>>>>>> [INFO] [12:27:20] Browserify bundle processing error
>>>>>>> [INFO] [12:27:20]   error: Error: Cannot find module 
>>>>>>> '..srcmainjs/AdminNavLi
>>>>>>> nk.jsx' from 'D:\GIT\blueocean-plugin\blueocean-dashboard\target'
>>>>>>> [ERROR]
>>>>>>> [ERROR] 
>>>>>>> D:\GIT\blueocean-plugin\blueocean-dashboard\node_modules\@jenkins-cd\js-
>>>>>>> builder\index.js:555
>>>>>>> [ERROR] throw 'Browserify bundle processing 
>>>>>>> error. See a
>>>>>>> bove for details.';
>>>>>>> [ERROR] ^
>>>>>>> [ERROR] Browserify bundle processing error. See above for details.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, May 31, 2016 at 7:29:23 PM UTC-4, Michael Neale wrote:
>>>>>>>>
>>>>>>>> *shakes fist at bill gates*. I think "\" was picked as a path 
>>>>>>>> separator deliberately to be different in the 70s when DOS was 
>>>>>>>> invented. 
>>>>>>>>
>>>>>>>> This really shoudl build on windows, but may take some time. Some 
>>>>>>>> of the tests are also creating and executing pipelines that involve 
>>>>>>>> "sh" 
>>>>>>>> steps which may be a problem once this build issue is overcome. They 
>>>>>>>> can 
>>>>>>>> probably be amended to use echo steps - which are cross platform I 
>>>>>>>> believe. 
>>>>>>>>
>>>>>>>> So, work to be done.. 
>>>>>>>>
>>>>>>>> On Wednesday, June 1, 2016 at 9:22:42 AM UTC+10, Thorsten Scherler 
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Yeah I am with Tom, one / is getting "eaten" 
>>>>>>>>>
>>>>>>>>> .srcmainjs/AdminNavLink.jsx' from 
>>>>>>>>> 'C:\Users\Admin\Downloads\blueocean\blueocean-dashboard\target'
>>>>>>>>>
>>>>>>>>> the whole path until the last is missing it. That is coming from 
>>>>>>>>> bo-web assembling the extensions points.
>>>>>>>>>
>>>>>>>>> BTW that file should be called DashboardNavLink. ;)
>>>>>>>>>
>>>>>>>>> salu2
>>>>>>>>>
>>>>>>>>> On Tuesday, May 31, 2016 at 10:26:33 PM UTC+2, Tom Fennelly wrote:
>>>>>>>>>>
>>>>>>>>>> On Tuesday, 31 May 2016 06:04:44 UTC+1, Richard Bywater wrote:
>>>>>>>>>>>
>>>>>>>>>>> I assume the cause of the issue is:
>>>>>>>>>>> "Cannot find module '..srcmainjs/AdminNavLink.jsx"
>>>>>>>>>>>
>>>>>>>>>>> It looks like something is trying to write a string probably 
>>>>>>>>>>> started as "..\src\main\js/AdminNavLink.jsx" and its entered 
>>>>>>>>>>> something like 
>>>>>>>>>>> Java which has seen those backslashes as escape characters (and 
>>>>>>>>>>> hence ended 
>>>>>>>>>>> up as srcmainjs)
>>>>>>>>>>>
>>>>>>>>>>> Haven't looked at *any* of the code but hopefully that might 
>>>>>>>>>>> point someone in a useful direction.
>>>>>>>>>>>
>>>>>>>>>>> Richard.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I'd need to check, but I doubt this error has anything to do with 
>>>>>>>>>> the symlink. 
>>>>>>>>>>
>>>>>>>>> -- 
>>>>>>> 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/otY1UkS9f4w/unsubscribe
>>>>>>> .
>>>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>>>> jenkinsci-de...@googlegroups.com.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/d495fecf-749b-409c-b9a5-efac078ec31b%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/d495fecf-749b-409c-b9a5-efac078ec31b%40googlegroups.com?utm_medium=email_source=footer>
>>>>>>> .
>>>>>>>
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>>
>>>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-dev/otY1UkS9f4w/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/cdf27cd0-4e0e-481b-978d-fa95118b448d%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/cdf27cd0-4e0e-481b-978d-fa95118b448d%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> Hi Ian. I have to try it on a windows machine myself, but PR #232 
>> <https://github.com/jenkinsci/blueocean-plugin/pull/232> (branch UX-431 
>> <https://github.com/jenkinsci/blueocean-plugin/tree/UX-431>) contains a 
>> possible fix for the windows path issue in js-extensions (more or less the 
>> same fix as suggested on the JIRA). I published a beta tag release of 
>> js-extensions, so it should build etc. Maybe you could check it out and 
>> give it a try? I'll try it on a windows machine tomorrow too.
>>
>>

-- 
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/c4986192-01ba-49e0-969c-2db49bd39b83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [BlueOcean] -> No matching rule was found on <hudson.model.AllView@257fc1dc[view/All/]> for "/blue"

[Michael Neale]

Right yes, I can see that is confusing (given the rename of the repo). 

Will see if can make that clearer. It looks like there is a fix in the 
works for the hpi plugin that will make this problem go away at some point 
as well. 

On Thursday, June 2, 2016 at 9:39:03 PM UTC+10, Ian Ceicys wrote:
>
> Works! Those steps (cd into "blueocean-plugin" (sibling dir 
> of "blueocean-rest") and running mvn hpi:run works. Can the readme be 
> updated for future contributors?
>
> Thanks for the assist much appreciated.
>
> On Thursday, June 2, 2016 at 3:37:56 AM UTC-4, Tom Fennelly wrote:
>>
>> The error 
>>
>> java.io.IOException: Dependency blueocean-commons (1.0-SNAPSHOT), 
>> blueocean-web (1.0-SNAPSHOT) doesn't exist
>>
>> ... strongly suggests that "all" of the plugins are not built before 
>> doing hpi:run.
>>
>> To fix this ... run "mvn clean install" from the top level folder of the 
>> blueocean repo clone i.e. the parent folder ot "blueocean-commons", 
>> "blueocean-rest" etc. After getting a successful here, cd into 
>> "blueocean-plugin" (sibling dir of "blueocean-rest" etc --- yes, it's 
>> confusing because the repo also has this name ... we will fix this) and run 
>> "mvn hpi:run".
>>
>> On Thursday, June 2, 2016 at 2:59:48 AM UTC+1, Ian Ceicys wrote:
>>>
>>> I was able to successfully build the latest version of source on my mac 
>>> and I was able to successfully run the commands:
>>>
>>>1. 
>>>
>>>mvn clean install
>>>
>>>2. 
>>>
>>>mvn hpi:run
>>>
>>>
>>> Jenkins is up and running and accessible at 
>>> http://localhost:8080/jenkins/
>>>
>>> However when I try to follow the instructions from the readme: 
>>> https://github.com/jenkinsci/blueocean-plugin
>>>
>>> And I try to access http://localhost:8080/jenkins/blue
>>>
>>> I get the following error: 
>>>
>>> Stapler processed this HTTP request as follows, but couldn't find the 
>>> resource to consume the request
>>>
>>> -> evaluate( :hudson.model.Hudson,"/blue")
>>> -> 
>>> evaluate(((StaplerProxy)).getTarget(),"/blue")
>>> -> evaluate(.getDynamic("blue",...),"")
>>> hudson.model.Hudson@2b46dffb.getDynamic("blue",...)==null. Back 
>>> tracking.
>>> -> 
>>> evaluate(((StaplerFallback)).getStaplerFallback(),"/blue")
>>> -> evaluate( 
>>> :hudson.model.AllView,"/blue")
>>> -> 
>>> evaluate(.getDynamic("blue",...),"")
>>> 
>>> hudson.model.AllView@257fc1dc[view/All/].getDynamic("blue",...)==null. Back 
>>> tracking.-> No matching rule was found on 
>>>  for "/blue"
>>>
>>>
>>>
>>> I am must be missing something pretty obvious. I've tried the bath /blue 
>>> and /blueocean but those don't work. 
>>>
>>> Thanks for the help. 
>>>
>>

-- 
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/8af2ceed-62ac-461d-8b8a-849cc0668838%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [BlueOcean] -> No matching rule was found on <hudson.model.AllView@257fc1dc[view/All/]> for "/blue"

[Michael Neale]

Hi - I did a fresh checkout of the latest, and wasn't able to see this. 

I am on OSX (El Capitain) with JDK8 installed. What is your environment? 

On Thursday, June 2, 2016 at 2:10:19 PM UTC+10, Michael Neale wrote:
>
> Did you run "mvn clean install" from the parent, and then mvn hpi:run from 
> blueocean-plugin directory?
>
> On Thursday, June 2, 2016 at 11:59:48 AM UTC+10, Ian Ceicys wrote:
>>
>> I was able to successfully build the latest version of source on my mac 
>> and I was able to successfully run the commands:
>>
>>1. 
>>
>>mvn clean install
>>
>>2. 
>>
>>mvn hpi:run
>>
>>
>> Jenkins is up and running and accessible at 
>> http://localhost:8080/jenkins/
>>
>> However when I try to follow the instructions from the readme: 
>> https://github.com/jenkinsci/blueocean-plugin
>>
>> And I try to access http://localhost:8080/jenkins/blue
>>
>> I get the following error: 
>>
>> Stapler processed this HTTP request as follows, but couldn't find the 
>> resource to consume the request
>>
>> -> evaluate(<hudson.model.Hudson@2b46dffb> :hudson.model.Hudson,"/blue")
>> -> 
>> evaluate(((StaplerProxy)<hudson.model.Hudson@2b46dffb>).getTarget(),"/blue")
>> -> evaluate(<hudson.model.Hudson@2b46dffb>.getDynamic("blue",...),"")
>> hudson.model.Hudson@2b46dffb.getDynamic("blue",...)==null. Back 
>> tracking.
>> -> 
>> evaluate(((StaplerFallback)<hudson.model.Hudson@2b46dffb>).getStaplerFallback(),"/blue")
>> -> evaluate(<hudson.model.AllView@257fc1dc[view/All/]> 
>> :hudson.model.AllView,"/blue")
>> -> 
>> evaluate(<hudson.model.AllView@257fc1dc[view/All/]>.getDynamic("blue",...),"")
>> 
>> hudson.model.AllView@257fc1dc[view/All/].getDynamic("blue",...)==null. Back 
>> tracking.-> No matching rule was found on 
>> <hudson.model.AllView@257fc1dc[view/All/]> for "/blue"
>>
>>
>>
>> I am must be missing something pretty obvious. I've tried the bath /blue 
>> and /blueocean but those don't work. 
>>
>> Thanks for the help. 
>>
>

-- 
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/5680d26a-c194-4393-a054-593e35fbff5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [BlueOcean] -> No matching rule was found on <hudson.model.AllView@257fc1dc[view/All/]> for "/blue"

[Michael Neale]

Did you run "mvn clean install" from the parent, and then mvn hpi:run from 
blueocean-plugin directory?

On Thursday, June 2, 2016 at 11:59:48 AM UTC+10, Ian Ceicys wrote:
>
> I was able to successfully build the latest version of source on my mac 
> and I was able to successfully run the commands:
>
>1. 
>
>mvn clean install
>
>2. 
>
>mvn hpi:run
>
>
> Jenkins is up and running and accessible at http://localhost:8080/jenkins/
>
> However when I try to follow the instructions from the readme: 
> https://github.com/jenkinsci/blueocean-plugin
>
> And I try to access http://localhost:8080/jenkins/blue
>
> I get the following error: 
>
> Stapler processed this HTTP request as follows, but couldn't find the 
> resource to consume the request
>
> -> evaluate( :hudson.model.Hudson,"/blue")
> -> 
> evaluate(((StaplerProxy)).getTarget(),"/blue")
> -> evaluate(.getDynamic("blue",...),"")
> hudson.model.Hudson@2b46dffb.getDynamic("blue",...)==null. Back 
> tracking.
> -> 
> evaluate(((StaplerFallback)).getStaplerFallback(),"/blue")
> -> evaluate( 
> :hudson.model.AllView,"/blue")
> -> 
> evaluate(.getDynamic("blue",...),"")
> 
> hudson.model.AllView@257fc1dc[view/All/].getDynamic("blue",...)==null. Back 
> tracking.-> No matching rule was found on 
>  for "/blue"
>
>
>
> I am must be missing something pretty obvious. I've tried the bath /blue 
> and /blueocean but those don't work. 
>
> Thanks for the help. 
>

-- 
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/199279d4-f766-4a62-b3b7-7ecb372bda1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[GSoC2016] Optional hangout at 8AM UTC every wednesday

[Michael Neale]

Every Wednesday, at 8AM UTC, I will be on https://jenkins-ci.org/hangout if 
anyone working on Google Summer Of Code is interested. 
(unless I am travelling). 


This is just an alternate time to talk about GSoC project stuff if anyone 
is interested, I will be lurking.

-- 
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/58a49ca9-7bdf-4f9c-96a8-146fea9a6cec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean : Dashboard in a Windows 7 PC

[Michael Neale]

*shakes fist at bill gates*. I think "\" was picked as a path separator 
deliberately to be different in the 70s when DOS was invented. 

This really shoudl build on windows, but may take some time. Some of the 
tests are also creating and executing pipelines that involve "sh" steps 
which may be a problem once this build issue is overcome. They can probably 
be amended to use echo steps - which are cross platform I believe. 

So, work to be done.. 

On Wednesday, June 1, 2016 at 9:22:42 AM UTC+10, Thorsten Scherler wrote:
>
> Yeah I am with Tom, one / is getting "eaten" 
>
> .srcmainjs/AdminNavLink.jsx' from 
> 'C:\Users\Admin\Downloads\blueocean\blueocean-dashboard\target'
>
> the whole path until the last is missing it. That is coming from bo-web 
> assembling the extensions points.
>
> BTW that file should be called DashboardNavLink. ;)
>
> salu2
>
> On Tuesday, May 31, 2016 at 10:26:33 PM UTC+2, Tom Fennelly wrote:
>>
>> On Tuesday, 31 May 2016 06:04:44 UTC+1, Richard Bywater wrote:
>>>
>>> I assume the cause of the issue is:
>>> "Cannot find module '..srcmainjs/AdminNavLink.jsx"
>>>
>>> It looks like something is trying to write a string probably started as 
>>> "..\src\main\js/AdminNavLink.jsx" and its entered something like Java which 
>>> has seen those backslashes as escape characters (and hence ended up as 
>>> srcmainjs)
>>>
>>> Haven't looked at *any* of the code but hopefully that might point 
>>> someone in a useful direction.
>>>
>>> Richard.
>>>
>>
>> I'd need to check, but I doubt this error has anything to do with the 
>> symlink. 
>>
>

-- 
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/0a755651-aad3-47a2-af64-53fd6129a622%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean : Dashboard in a Windows 7 PC

[Michael Neale]

As far as I know the platform version of npm/node should not be needed, and 
thus the version not matter - right Tom? 


On Tuesday, May 31, 2016 at 2:04:35 PM UTC+10, Naresh K wrote:
>
> I am using Node version 4.4.5 and npm is at 2.15.5.
>
> On Tuesday, May 31, 2016 at 2:05:52 AM UTC+5:30, Ivan Meredith wrote:
>>
>> It could be something specific to windows, as far as I know no one has 
>> built it on windows yet. What version of node/npm do you have installed?
>>
>> On Tuesday, May 31, 2016 at 12:16:15 AM UTC+12, Naresh K wrote:
>>>
>>> Hi All,
>>>
>>> I just came across blue ocean and the project sounds very interesting 
>>> and wanted to setup my windows 7 machine for dev purposes. But before that 
>>> i tried compiling the plugin by checking out the source code and running 
>>> 'mvn clean install' on it
>>> this is the error i get:
>>>
>>> [INFO] [16:41:34] Finished 'less_bundle_extensions_bundle_4' after 5 ms
>>> [INFO] [16:41:34] LESS CSS pre-processing completed to 
>>> 'target/classes/org/jenki
>>> ns/ui/jsmodules/blueocean_dashboard'.
>>> [INFO] [16:41:35] Finished 'js_bundle_immutable-3.8.1_bundle_1' after 
>>> 1.34 s
>>> [INFO] [16:41:35] Browserify bundle processing error
>>> [INFO] [16:41:35]   error: Error: Cannot find module 
>>> '..srcmainjs/AdminNavLi
>>> nk.jsx' from 
>>> 'C:\Users\Admin\Downloads\blueocean\blueocean-dashboard\target'
>>> [ERROR]
>>> [ERROR] 
>>> C:\Users\Admin\Downloads\blueocean\blueocean-dashboard\node_modules\@
>>> jenkins-cd\js-builder\index.js:555
>>> [ERROR] throw 'Browserify bundle processing 
>>> error. See a
>>> bove for details.';
>>> [ERROR] ^
>>> [ERROR] Browserify bundle processing error. See above for details.
>>> [INFO] 
>>> 
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Blue Ocean UI Parent ... SUCCESS [ 
>>>  7.282 s]
>>> [INFO] BlueOcean :: Commons API ... SUCCESS [ 
>>>  8.382 s]
>>> [INFO] BlueOcean :: Web module  SUCCESS [ 
>>> 29.429 s]
>>> [INFO] BlueOcean :: Rest module ... SUCCESS [ 
>>>  7.401 s]
>>> [INFO] BlueOcean :: Dashboard . FAILURE [ 
>>> 20.144 s]
>>> [INFO] BlueOcean :: Jenkins Plugin  SKIPPED
>>> [INFO] 
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO] 
>>> 
>>> [INFO] Total time: 01:14 min
>>> [INFO] Finished at: 2016-05-30T16:41:35+05:30
>>> [INFO] Final Memory: 262M/1564M
>>> [INFO] 
>>> 
>>> [ERROR] Failed to execute goal 
>>> com.github.eirslett:frontend-maven-plugin:0.0.23:
>>> gulp (gulp bundle) on project blueocean-dashboard: Failed to run task: 
>>> 'gulp bun
>>> dle --no-color' failed. (error code 1) -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the 
>>> -e swit
>>> ch.
>>> [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 rea
>>> d the following articles:
>>> [ERROR] [Help 1] 
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
>>> eption
>>> [ERROR]
>>> [ERROR] After correcting the problems, you can resume the build with the 
>>> command
>>>
>>> [ERROR]   mvn  -rf :blueocean-dashboard
>>>
>>>
>>> I checked the gulp file and everything seems fine. Am i missing 
>>> something. I have nodejs installed and gulp as well. Requesting members to 
>>> help me with this. nodejs is at 4.4.5
>>>
>>>
>>> Regards
>>> Naresh K
>>>
>>

-- 
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/351f412d-65b0-434c-b3cd-c8b928321898%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Build failure when compiling BlueOcean : Dashboard in a Windows 7 PC

[Michael Neale]

Where there any errors above? 

This uses the mvn front end plugin that builds things with node/npm which 
is specific to platform. 


On Tuesday, May 31, 2016 at 6:35:52 AM UTC+10, Ivan Meredith wrote:
>
> It could be something specific to windows, as far as I know no one has 
> built it on windows yet. What version of node/npm do you have installed?
>
> On Tuesday, May 31, 2016 at 12:16:15 AM UTC+12, Naresh K wrote:
>>
>> Hi All,
>>
>> I just came across blue ocean and the project sounds very interesting and 
>> wanted to setup my windows 7 machine for dev purposes. But before that i 
>> tried compiling the plugin by checking out the source code and running 'mvn 
>> clean install' on it
>> this is the error i get:
>>
>> [INFO] [16:41:34] Finished 'less_bundle_extensions_bundle_4' after 5 ms
>> [INFO] [16:41:34] LESS CSS pre-processing completed to 
>> 'target/classes/org/jenki
>> ns/ui/jsmodules/blueocean_dashboard'.
>> [INFO] [16:41:35] Finished 'js_bundle_immutable-3.8.1_bundle_1' after 
>> 1.34 s
>> [INFO] [16:41:35] Browserify bundle processing error
>> [INFO] [16:41:35]   error: Error: Cannot find module 
>> '..srcmainjs/AdminNavLi
>> nk.jsx' from 
>> 'C:\Users\Admin\Downloads\blueocean\blueocean-dashboard\target'
>> [ERROR]
>> [ERROR] 
>> C:\Users\Admin\Downloads\blueocean\blueocean-dashboard\node_modules\@
>> jenkins-cd\js-builder\index.js:555
>> [ERROR] throw 'Browserify bundle processing 
>> error. See a
>> bove for details.';
>> [ERROR] ^
>> [ERROR] Browserify bundle processing error. See above for details.
>> [INFO] 
>> 
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Blue Ocean UI Parent ... SUCCESS [ 
>>  7.282 s]
>> [INFO] BlueOcean :: Commons API ... SUCCESS [ 
>>  8.382 s]
>> [INFO] BlueOcean :: Web module  SUCCESS [ 
>> 29.429 s]
>> [INFO] BlueOcean :: Rest module ... SUCCESS [ 
>>  7.401 s]
>> [INFO] BlueOcean :: Dashboard . FAILURE [ 
>> 20.144 s]
>> [INFO] BlueOcean :: Jenkins Plugin  SKIPPED
>> [INFO] 
>> 
>> [INFO] BUILD FAILURE
>> [INFO] 
>> 
>> [INFO] Total time: 01:14 min
>> [INFO] Finished at: 2016-05-30T16:41:35+05:30
>> [INFO] Final Memory: 262M/1564M
>> [INFO] 
>> 
>> [ERROR] Failed to execute goal 
>> com.github.eirslett:frontend-maven-plugin:0.0.23:
>> gulp (gulp bundle) on project blueocean-dashboard: Failed to run task: 
>> 'gulp bun
>> dle --no-color' failed. (error code 1) -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the 
>> -e swit
>> ch.
>> [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 rea
>> d the following articles:
>> [ERROR] [Help 1] 
>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
>> eption
>> [ERROR]
>> [ERROR] After correcting the problems, you can resume the build with the 
>> command
>>
>> [ERROR]   mvn  -rf :blueocean-dashboard
>>
>>
>> I checked the gulp file and everything seems fine. Am i missing 
>> something. I have nodejs installed and gulp as well. Requesting members to 
>> help me with this. nodejs is at 4.4.5
>>
>>
>> Regards
>> Naresh K
>>
>

-- 
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/861eb4e8-2830-4913-bfd6-f0f051f3c0eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble building Blue Ocean

[Michael Neale]

Ah thanks for checking that Nicolas. 

The "New Pipeline" certainly points to the wrong place right now (that is 
known). 

On Monday, May 30, 2016 at 5:13:58 PM UTC+10, nicolas de loof wrote:
>
> I have the docker image running locally and can't see any broken link. 
> Could you please give more details ? screenshot ?
>
> 2016-05-30 8:52 GMT+02:00 Michael Neale <mne...@cloudbees.com 
> >:
>
>> Hrm, what are some links that you see broken? I have seen it run on / 
>> before - I wonder if the image has the wrong context root set somehow. 
>>
>>
>> On Sunday, May 29, 2016 at 12:10:40 AM UTC+10, Ross Boucher wrote:
>>>
>>> Thanks. I got the docker image running, but it looks like there's a 
>>> problem with jenkins believing it will be running at /jenkins/, but out of 
>>> the box it seems to be configured to actually run at the web root /. (The 
>>> initial page load works, but most links are broken).
>>>
>>> On Saturday, May 28, 2016 at 9:54:19 AM UTC-4, Baptiste Mathus wrote:
>>>>
>>>> Hi Ross,
>>>>
>>>> That's great! Depending on what you were planning to do (have a look, 
>>>> or start hacking on it?), if (at first) it's only playing with it, then 
>>>> you 
>>>> might want to use the dedicated docker image:
>>>>
>>>> $ docker run -p 8080:8080  jenkinsci/blueocean
>>>>
>>>> About your local error, I think you're just trying to build a maven 
>>>> module of the whole repo, but that plugin actually depends on some others.
>>>>
>>>> So, first get back to the root of the repo, and run 
>>>>
>>>> $ mvn clean install
>>>>
>>>> That will build and install all the plugins inside what's the local 
>>>> maven cache (or somewhat improperly /repository/, but really it's better 
>>>> to 
>>>> see it as a cache. Anyway).
>>>>
>>>> Then run hpi:run like you did.
>>>>
>>>> Cheers!
>>>>
>>>> 2016-05-28 15:45 GMT+02:00 Ross Boucher <rbou...@gmail.com>:
>>>>
>>>>> Hey all, I'm excited about the new Blue Ocean project. Tried to get it 
>>>>> running just now and I'm running into some trouble. After running `mvn 
>>>>> clean install`, on the next step, I'm getting this: 
>>>>>
>>>>> https://gist.github.com/boucher/1a9beb22ac3cbadf858a82f4db05c0f2
>>>>>
>>>>> Any suggestions?
>>>>>
>>>>> -Ross
>>>>>
>>>>> -- 
>>>>> 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/e2fbb62c-ad36-4f67-bdfd-898186a83316%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/e2fbb62c-ad36-4f67-bdfd-898186a83316%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/e753e554-b411-4036-b1b2-000c8bb4ce91%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/e753e554-b411-4036-b1b2-000c8bb4ce91%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: Trouble building Blue Ocean

[Michael Neale]

Hi - did you run "mvn install" from the top level directory first? 

Or - use the docker image as mentioned by Baptiste. 

On Saturday, May 28, 2016 at 11:45:28 PM UTC+10, Ross Boucher wrote:
>
> Hey all, I'm excited about the new Blue Ocean project. Tried to get it 
> running just now and I'm running into some trouble. After running `mvn 
> clean install`, on the next step, I'm getting this: 
>
> https://gist.github.com/boucher/1a9beb22ac3cbadf858a82f4db05c0f2
>
> Any suggestions?
>
> -Ross
>

-- 
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/53f3e41b-13e2-4375-9c4f-d9137684c810%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Trouble building Blue Ocean

[Michael Neale]

Hrm, what are some links that you see broken? I have seen it run on / 
before - I wonder if the image has the wrong context root set somehow. 

On Sunday, May 29, 2016 at 12:10:40 AM UTC+10, Ross Boucher wrote:
>
> Thanks. I got the docker image running, but it looks like there's a 
> problem with jenkins believing it will be running at /jenkins/, but out of 
> the box it seems to be configured to actually run at the web root /. (The 
> initial page load works, but most links are broken).
>
> On Saturday, May 28, 2016 at 9:54:19 AM UTC-4, Baptiste Mathus wrote:
>>
>> Hi Ross,
>>
>> That's great! Depending on what you were planning to do (have a look, or 
>> start hacking on it?), if (at first) it's only playing with it, then you 
>> might want to use the dedicated docker image:
>>
>> $ docker run -p 8080:8080  jenkinsci/blueocean
>>
>> About your local error, I think you're just trying to build a maven 
>> module of the whole repo, but that plugin actually depends on some others.
>>
>> So, first get back to the root of the repo, and run 
>>
>> $ mvn clean install
>>
>> That will build and install all the plugins inside what's the local maven 
>> cache (or somewhat improperly /repository/, but really it's better to see 
>> it as a cache. Anyway).
>>
>> Then run hpi:run like you did.
>>
>> Cheers!
>>
>> 2016-05-28 15:45 GMT+02:00 Ross Boucher :
>>
>>> Hey all, I'm excited about the new Blue Ocean project. Tried to get it 
>>> running just now and I'm running into some trouble. After running `mvn 
>>> clean install`, on the next step, I'm getting this: 
>>>
>>> https://gist.github.com/boucher/1a9beb22ac3cbadf858a82f4db05c0f2
>>>
>>> Any suggestions?
>>>
>>> -Ross
>>>
>>> -- 
>>> 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/e2fbb62c-ad36-4f67-bdfd-898186a83316%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/e753e554-b411-4036-b1b2-000c8bb4ce91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Jenkins WebUI

[Michael Neale]

Hi Samat, I fear those are probably not simple questions at all :/

For an external script, Tom may know the best way may depend if it is a 
common library other plugins may use or is the code you want to contribute. 

My experience is based on the js-modules use 
in: https://github.com/jenkinsci/pipeline-editor-plugin (you can see in 
resources there is js, less etc, which gets put into place by the build 
chain via "gulp"). 

For jelly - I am not sure. Perhaps it is a path issue - needing / at the 
start of the included file? or a full path to it? (I don't quite follow 
what you are doing)

Do you have work on a repo/branch somewhere others can look at? 



On Sunday, May 29, 2016 at 6:24:40 PM UTC+10, Samat Davletshin wrote:
>
> Hello,
> In previous post I showed that I could make a popup dialog window on home 
> page to create a new job. 
> However, I did it in a fast and dirty way and now I want to make it 
> properly.
>
> I am sorry if those are too simple questions. However, I would appreciate 
> if you could at least link me to where I can read about how to do it. 
>

> Currently I see 3 issues and I would like to have a hint on how to fix 
> them.
>
> 1. How do I add an external js, css library to js-modules 
>  or to js-libs 
>  so that I can require it on home 
> page?
>
> 2. For some reason, when I try to include my jelly file by  page="myjelly.jelly" /> it is not included. The myjelly file is in the same 
> folder as the file (sidepanel.jelly) where I try to include it. If I just 
> insert the same jelly in sidepanel file between  files it works.
>
> 3. Labels like ${%ItemName.label} are not replaced by the corresponding 
> string as you can see on GIF.
>

-- 
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/2284eed9-1b6b-4664-ab5f-eef26e4ac6c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] New UX project for jenkins

[Michael Neale]

FYI just did a "transfer of ownership" of the github repo to: 

https://github.com/jenkinsci/blueocean-plugin
https://github.com/jenkinsci/jenkins-design-language

old links redirect to there, and they are now fully operational. 

On Friday, May 27, 2016 at 8:44:06 AM UTC+10, Michael Neale wrote:
>
> I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the 
> so-called "blueocean" plugin. 
>
> You may have heard this announced via the blog post 
> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not, I'll 
> give you a few minutes 
>
> to have a read... 
>
> Just kidding, who has time for that, let me explain. No, there is too 
> much, let me sum up: 
>
> https://www.youtube.com/watch?v=GZYhDMCOyww
>
> (above is from the movie princess bride, more seriously, if you haven't 
> seen this movie you really should, kind of urgently)
>
> Blue Ocean aims to be a plugin (well, a few moving parts delivered as 
> plugins) that provides an extensible "next gen" user experience. Jenkins 
> GUI has been around for 10 years now, and can be hard to extend and 
> modernise (many of us have tried).
>
> Its initial focus is on "pipeline centric" and freestyle views for the 
> busy developer, and is very much a work in progress. 
>
> The interesting bits for us developers: 
>
> Blue Ocean is based on ES6 
> <https://medium.com/@rajaraodv/5-javascript-bad-parts-that-are-fixed-in-es6-c7c45d44fd81>,
>  
> Server Sent Events 
> <https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events>
>  
> (realtime notifications), React.js 
> <https://medium.com/@rajaraodv/5-javascript-bad-parts-that-are-fixed-in-es6-c7c45d44fd81>
>  
> for component model and gulp/npm <https://www.npmjs.com/> build chain, 
> but wired in via the already in use jenkins-js modules 
> <https://github.com/jenkinsci/js-modules> (this means there isn’t a need 
> to be familiar with the whole js toolchain unless you want to be, and mvn 
> install takes care of things normally). 
>
> Both client side (stuff in browser) and server side - are just Jenkins 
> plugins. The server side uses the usual Jenkins web middleware (yes, 
> stapler) and extensions/extension points. 
>
> A fair bit of head scratching was done to come up with an 
> “” concept for blue ocean client side, however it was worth 
> it as it means that plugins for the new UX can be delivered as normal 
> Jenkins plugins but with js componentry. Jenkins serves up these plugins to 
> the web browser so extension points in Blue Ocean pages can be fulfilled by 
> any plugin offering those extensions (GUI extension points have names). 
> This includes things like adding a new “route” for a new page to host a 
> feature, or could be augmenting an existing page or component. A sample 
> plugin and demo of it is here: 
> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin. 
>
> Extensions can be isolated in failure this way - so a bad bit of 
> javascript doesn’t brick a whole page. 
>
> Blue Ocean when installed currently provides the new UX on the /blue top 
> level route in Jenkins, so the classic GUI lives alongside it. The new GUI 
> (markup, js) that is delivered via a fresh set of markup and JS bundles, so 
> it doesn’t conflict with any existing GUI. 
>
> The UX model in blue ocean is more of a shift to what used to be called 
> “client server” but is now a “single page app” (kind of), using pretty much 
> standard React.js patterns (it is hoped that while React.js is the glue of 
> blue ocean, plugin authors don’t have to be an expert in it, and could use 
> something else to deliver their front end functionality). There is a server 
> side API plugin called “blueocean-rest” which provides a http/REST-like api 
> that helps drive the GUI (it too is extensible, but it just builds on stuff 
> already in Jenkins) - it has a fairly neat README explaining the API as it 
> is right now. You could describe this api as being a “BFF” pattern for the 
> front end (see http://samnewman.io/patterns/architectural/bff/)
>
>
> It’s still very early days obviously, but if you are interested take a 
> look at https://github.com/cloudbees/blueocean (as soon as HOSTING ticket 
> is resolved, development will move to the jenkinsci org’s fork of that 
> repository). It’s a multi module project (blueocean-plugin is the 
> aggregator). The “js-extensions” module is the middleware that makes the 
> new ExtensionPoint stuff work. 
>
> There is also the https://github.com/cloudbees/jenkins-design-language 
> repository (once again, will be forked into jenkinsci) which contains 
> visual assets, reusable components

[Blue Ocean] New UX project for jenkins

[Michael Neale]

I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the 
so-called "blueocean" plugin. 

You may have heard this announced via the blog post 
https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not, I'll 
give you a few minutes 

to have a read... 

Just kidding, who has time for that, let me explain. No, there is too much, 
let me sum up: 

https://www.youtube.com/watch?v=GZYhDMCOyww

(above is from the movie princess bride, more seriously, if you haven't 
seen this movie you really should, kind of urgently)

Blue Ocean aims to be a plugin (well, a few moving parts delivered as 
plugins) that provides an extensible "next gen" user experience. Jenkins 
GUI has been around for 10 years now, and can be hard to extend and 
modernise (many of us have tried).

Its initial focus is on "pipeline centric" and freestyle views for the busy 
developer, and is very much a work in progress. 

The interesting bits for us developers: 

Blue Ocean is based on ES6 
,
 
Server Sent Events 

 
(realtime notifications), React.js 

 
for component model and gulp/npm  build chain, but 
wired in via the already in use jenkins-js modules 
 (this means there isn’t a need to 
be familiar with the whole js toolchain unless you want to be, and mvn 
install takes care of things normally). 

Both client side (stuff in browser) and server side - are just Jenkins 
plugins. The server side uses the usual Jenkins web middleware (yes, 
stapler) and extensions/extension points. 

A fair bit of head scratching was done to come up with an 
“” concept for blue ocean client side, however it was worth 
it as it means that plugins for the new UX can be delivered as normal 
Jenkins plugins but with js componentry. Jenkins serves up these plugins to 
the web browser so extension points in Blue Ocean pages can be fulfilled by 
any plugin offering those extensions (GUI extension points have names). 
This includes things like adding a new “route” for a new page to host a 
feature, or could be augmenting an existing page or component. A sample 
plugin and demo of it is here: 
https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin. 

Extensions can be isolated in failure this way - so a bad bit of javascript 
doesn’t brick a whole page. 

Blue Ocean when installed currently provides the new UX on the /blue top 
level route in Jenkins, so the classic GUI lives alongside it. The new GUI 
(markup, js) that is delivered via a fresh set of markup and JS bundles, so 
it doesn’t conflict with any existing GUI. 

The UX model in blue ocean is more of a shift to what used to be called 
“client server” but is now a “single page app” (kind of), using pretty much 
standard React.js patterns (it is hoped that while React.js is the glue of 
blue ocean, plugin authors don’t have to be an expert in it, and could use 
something else to deliver their front end functionality). There is a server 
side API plugin called “blueocean-rest” which provides a http/REST-like api 
that helps drive the GUI (it too is extensible, but it just builds on stuff 
already in Jenkins) - it has a fairly neat README explaining the API as it 
is right now. You could describe this api as being a “BFF” pattern for the 
front end (see http://samnewman.io/patterns/architectural/bff/)


It’s still very early days obviously, but if you are interested take a look 
at https://github.com/cloudbees/blueocean (as soon as HOSTING ticket is 
resolved, development will move to the jenkinsci org’s fork of that 
repository). It’s a multi module project (blueocean-plugin is the 
aggregator). The “js-extensions” module is the middleware that makes the 
new ExtensionPoint stuff work. 

There is also the https://github.com/cloudbees/jenkins-design-language 
repository (once again, will be forked into jenkinsci) which contains 
visual assets, reusable components and tries to codify a standard look/feel 
(what is a design language ). 
One thing front end developers have found useful when building components 
is storybook 
.




If you are interested in talking about this, we are using #jenkins-ux on 
freenode irc (hopefully there is someone around most times), and also if 
you post to this dev list, please use [Blue Ocean] as the topic prefix, so 
the long suffering subscribers are able to filter out threads they are not 
interested in. 


There will be a blueocean “component” in JIRA for raising issues against 
once the HOSTING ticket is taken care of. 

Here 

Re: [GSoC2016] Jenkins WebUI

[Michael Neale]

I quite like that. 


On Wednesday, May 25, 2016 at 6:27:58 PM UTC+10, Samat Davletshin wrote:
>
> Hello!
>
> Thank you, Kirill. Yes, I would like to see PRs and work in progress from 
> Manuel. Since now I try to improve new job creation, I think that would be 
> useful to me.
>
>
> Now I work on new job creation popup. On the GIF below you can see my 
> current results. I used a Remodal 
> library 
> for popup and put there existing New Job containe 
> r.
>  
> I was glad and surprised that it is fully functional right away. On the GIF 
> you can see that popup receives all job types and then successfully submits 
> the post form creating a new job.
>
>
> I think that could be a good first step. Further I can start changing the 
> window itself.
>
>
> What do you think? Do you have any suggestions? 
>
>
>
> 
>

-- 
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/3fd7d40b-da14-44ef-8fc2-dfd01616c891%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: I am blocked by Jenkins wiki

[Michael Neale]

That email address is not a public internet address - so likely a firewall 
inside china is blocking it, I am not sure there is much we can do about it 
at this stage. 



On Wednesday, May 25, 2016 at 12:28:21 PM UTC+10, blem...@gmail.com wrote:
>
> Hi, 
> I am from China. And yesterday when i used Jenkins to deploy my war to 
> server, and after that, wanted to restart the Jenkins. But it didn't 
> succeed and at the same time, find my computer can't reach Jenkins Wiki 
> anymore but can enter other Jenkins websites.. And other computers of my 
> company also met the same problem. And my ip address is 10.32.6.100.  I 
> want to know how to solve this kind of problem.Can you help me and contact 
> with me (ble...@outlook.com ).
> Best regards,
> Jimmy Chen
>

-- 
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/24727c80-2265-40e1-b1ba-a59b30ebc487%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Jenkins WebUI

[Michael Neale]

(replies inline)

On Thursday, May 19, 2016 at 6:56:31 PM UTC+10, Samat Davletshin wrote:
>
>
> 3. Tom was proposing a step by step new job creation. Currently it would 
> contain only 2 steps - job name and job type. "Next, next" process would be 
> more intuitive and quicker to understand what to do. That may be done with 
> only JavaScript and CSS by hiding and showing parts. Tom liked this idea.
>

I think this makes sense. 
 

>
> So I am not saying that I do not want to do anything except JavaScript and 
> CSS. It is just may be better to start from more manageable surface and 
> then move deeper. What do you think? Kirill, Michael?
>

Much of the work now happens in javascript so I don't think there is a 
problem with that unless you really dislike javascript ;)
 

>
> Then about job validation. I personally think that there are now two ways 
> of improvements that could be a good place for me to start at:
> 1. Job name is checked for validity only when it loses focus. I think that 
> should not be hard to display a warning message right after the user types 
> in an invalid character
>

Invalid character is one, but validating the whole job name in the 
background (for duplicates) could be good. 
 

> 2. It is possible to submit job creating form with an invalid name. It 
> takes user to unnecessary empty page with error message forcing to click 
> back button. I tried to fix it yesterday but had difficulties with the GET 
> request to check the name. Apparently I cannot block form submission with 
> IF statement as it is done with empty name and no job type selected. So the 
> validation is better happen on server side? If so how should I approach 
> prevention of job submittion?
>

If #1 above is addressed, this would be less of an issue right? 
 

>
>
> Finally about job configuration page:
> 1. Changing help information probably stays now as in proposal.
> 2. More intuitive configuration page. There are now a lot of improvements 
> in 2.0. However, I think there are some new approaches to try such as 
> accordion based configuration. This part is very open to discussions and 
> feedback.
>

Yes it is a bit different now, it uses a scrollspy to combine scrolling 
with tabs (http://www.w3schools.com/bootstrap/bootstrap_scrollspy.asp). 
I am not sure about accordion, would be interested in what Kirill thinks on 
this. 
I think its a big improvement on how it was, for sure, but one thing that 
keeps irritating me is the text editor for freestyle or pipeline - isn't 
big enough and I can't resize it. 
 

>
>
> I would love to hear any feedback.
> Kirill, Michael if you think it is reasonable to talk I would be glad to 
> do so and get your feedback almost any time.
>

-- 
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/2e52807d-8362-495b-a380-45727265b942%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Jenkins WebUI

[Michael Neale]

So which option is this in the GSoC proposal - under "New Job Creation" 
there are 3 things that were proposed - the first one (new job creation 
wizard) seems somewhat redundant with Jenkins 2.0 which totally reworked 
that screen. 
The second option was job name validation, which is also more "real time" 
than it was before (although it isn't as you type now, it is only when it 
loses focus. Given these changes, the third proposal may make more sense:

[Optional] Simple new job configuration.
○ After creation, a new job are configured in the same creation popup.
○ This configuration contain only essential options such as SCM and main
build actions.

This would be interesting to see - the config page has been redesigned but 
it still doesn't directly guide you to setting up SCM and other critical 
things yet. Is that a better place to look? 




On Thursday, May 19, 2016 at 4:33:13 AM UTC+10, Kirill Merkushev wrote:
>
> As for configuration functionality on newJob page - what kind of 
> functionality do you want to see on this page (popup)? Build triggers can 
> be very complicated in their configuration, so i suggest to not to place it 
> there
>
>
> 2016-05-18 21:30 GMT+03:00 Kirill Merkushev  >:
>
>> - https://wiki.jenkins-ci.org/display/JENKINS/Form+Validation
>> - https://wiki.jenkins-ci.org/display/JENKINS/Web+Method
>>
>> You can save validation logic on the server side (as of any client side 
>> validation logic may be overridden), but change the trigger for ajax 
>> request to keypress.
>>
>> 2016-05-18 17:48 GMT+03:00 Samat Davletshin > >:
>>
>>> I also do not quite get how name validation happens on newJob creation.
>>> add-item.js sends GET request to localhost:8080/jenkins/checkJobName 
>>> If the job name is incorrect it receives an error string "message".
>>>
>>> Where can see what happens at /checkJobName? 
>>> Are there any problems with the check happening on client side in 
>>> JavaScript?
>>>
>>> It seems to me that job validation should not be very complicated and it 
>>> would be better to do it on client side. 
>>> This way it would be possible to give the user a real time feedback and 
>>> show the warning message right after he typed it. Currently it happens only 
>>> on blur what is inconvenient in my view.
>>>
>>> -- 
>>> 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/fk5deO_SszU/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-de...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/a2e4bf5a-7a02-441a-8421-feea54b582ad%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/bf16a741-9890-45fb-8fc5-899092115d34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Jenkins WebUI

[Michael Neale]

It is common in webapps to validate on the server side. Even if you also 
validate on the client side, server side will enforce the rules (there may 
be reasons such as security, to avoid injection attacks). 



On Thursday, May 19, 2016 at 12:48:46 AM UTC+10, Samat Davletshin wrote:
>
> I also do not quite get how name validation happens on newJob creation.
> add-item.js sends GET request to localhost:8080/jenkins/checkJobName 
> If the job name is incorrect it receives an error string "message".
>
> Where can see what happens at /checkJobName? 
> Are there any problems with the check happening on client side in 
> JavaScript?
>
> It seems to me that job validation should not be very complicated and it 
> would be better to do it on client side. 
> This way it would be possible to give the user a real time feedback and 
> show the warning message right after he typed it. Currently it happens only 
> on blur what is inconvenient in my view.
>

-- 
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/a641bc51-eafe-4743-bdd6-91e222656d1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Jenkins WebUI

[Michael Neale]

If you aren't 100% sure of formatting or details of how to publish a blog, 
open a pull request anyway and people will help fix it in review. 



On Tuesday, May 17, 2016 at 2:44:07 AM UTC+10, Oleg Nenashev wrote:
>
> Blogposting guide for Jenkins.IO: 
> https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#adding-a-blog-post
> Regarding the format, just follow the approaches in previous blogposts
>
> 2016-05-16 18:11 GMT+02:00 Samat Davletshin  >:
>
>> I would glad to do both if this is a good idea.
>> However, I am not very familiar with the blog format. Is it appropriate 
>> for discussion of mere plans without a ready result? If so should I follow 
>> some style guides?
>>
>> -- 
>> 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/fk5deO_SszU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/d2f6d7f5-b87a-4901-9854-24ae30b3dcfd%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/3e1ce2eb-8bd9-418d-8689-39a37e468431%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: improving WorkspaceCleanupThread in a multi-branch world

[Michael Neale]

So talking in code instead, this could be done in the computed folder: 

https://github.com/jenkinsci/cloudbees-folder-plugin/pull/62
https://issues.jenkins-ci.org/browse/JENKINS-34781

(doing similar work to what the cleanup thread does, but when it removes 
the orphaned item). 


On Friday, May 13, 2016 at 8:37:45 AM UTC+10, Jesse Glick wrote:
>
> On Thu, May 12, 2016 at 6:36 PM, Jesse Glick  > wrote: 
> >> it will not cover any changes to item name 
> > 
> > Sure, but there is only so much we can do. 
>
> …though we could have an `ItemListener.onLocationChanged` which 
> deletes workspaces from the old location too. 
>

-- 
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/b2f54e55-a20a-4868-af4e-b0bf83f35fe4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: improving WorkspaceCleanupThread in a multi-branch world

[Michael Neale]

On Wednesday, May 11, 2016 at 10:05:28 PM UTC+10, Daniel Beck wrote:
>
>
>
> WorkspaceCleanupThread should be moved into a plugin, and from there it 
> can be grown, be made configurable and/or get siblings. There are probably 
> already issues in Jira related to all that. 
>
>
For things like multibranch, do you think it is better they explicitly 
remove unneeded workspaces on the agents, vs tuning the cleanup thread? 
(given they know when it can safely be removed) - or they can provide their 
own supplemental cleanup. 

-- 
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/05dd2d52-7956-4b99-8ef6-3f46ad627a8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

improving WorkspaceCleanupThread in a multi-branch world

[Michael Neale]

One thing I have come across with using multibranch pipeline (with github, 
BTW) is that it generates a LOT of noise in a agent's workspace. 

The WorkspaceCleanupThread runs periodically to cleanup things, but will 
only remove workspaces on an agent (slave) machine that haven't been used 
in a month. Any younger and they are kept by default. 

In a multibranch world. you have jobs, and thus disposable workspaces 
popping into and out of existence like subatomic particles of the quantum 
foam of outer-space (getting carried away with metaphor here) - this can 
end up swamping the agent. 

Lets say you are lucky enough to have a productive team: they contribute 5 
pull requests a day that get merged at the rate of 1 a day (so, 5 branches 
pop into and out of existence each day). The master works great, but on the 
slave that means 5 new workspaces created each day. 

Say each workspace is about 1GB of "stuff" (it can happen, not hard with 
artifact caching, maven, npm). That is 5 Gig a day accumulated, or 100Gig a 
month of noise, before it is eligible to be cleaned up. 

Multiply this by a few teams, and you can end up using up a lot of disk for 
what amounts to the steady state of just a few jobs (remember, as branches 
are removed, Jenkins removes them from the master, but the workspaces on 
any agents have to be garbage collected). Disk space or inodes could be 
exhausted before the garbage collector could do its thing, and in any case 
it is fairly inefficient. 

https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/WorkspaceCleanupThread.java#L114
 
 - is the code that simply checks for age. Are there better heuristics we 
could apply in this world? (check for disk space, reduce age before 
deletion if it is low, inodes if you have a unix filesystem). Checking the 
ratio of "older" workspaces to current ones could also mean reducing the 
age at which things could be deleted. 

Is it worth exploring smarter heuristics, or is the real solution to have 
an alternative workspace cleaner that multibranch plugins include, that 
cleanup any workspaces on the event of a branch (job) removal? (not sure 
how easy this would be, may have to be best efforts, and supplement the 
workspace cleanup thread). 

Thoughts? 

-- 
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/5a612909-f7ef-42ae-b5fb-1e6e749885d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: write access to pipeline-examples

[Michael Neale]

Andrew has been travelling and on vacation of late (although still working 
a bit it seems) so may have a backlog. 

On Monday, May 9, 2016 at 12:36:07 AM UTC+10, Baptiste Mathus wrote:
>
> @Mike, actually, this repo is already mergeable by a bunch of people if 
> need be (core team at least IIUC), and I'm not sure this is where it needs 
> the more energy ;-). 
>
> If you can indeed review PR and give your +1/-1, then it's very welcome! 
> Then when say 2 or 3 people say it's OK to them, then merging is really 
> the easy part :-).
>
> Thanks for your help!
>
> Cheers
>
> 2016-05-08 16:17 GMT+02:00 Mike Caspar :
>
>> No  problemo.
>>
>> My understanding from the recent virtual conference is a *request for 
>> more help*.  I'm not worried so much about faster. I have the working 
>> code ;->    I'm simply wanting to help others.
>>
>> There is tons of missing information (such as a new documentation commit 
>> guidelines based on this message). 
>>
>> I'm happy to review PRs (even if it means not reviewing my own).  I'll 
>> reach out to Andrew to see if he's looking for help.
>>
>> Mike
>>
>>
>>
>> On 2016-05-08 9:58 AM, Baptiste Mathus wrote:
>>
>> Hi, This repo is currently maintained by Andrew Bayer and he's pretty 
>> active in general.  
>>
>> Also, even if I understand your desire to go faster, in that case IMO we 
>> may actually want to review things even more carefully and wait for more 
>> input (and many reviewers are doing that on this repo, just give it a few 
>> days).
>>
>> Cheers
>>
>>
>>
>> 2016-05-08 15:30 GMT+02:00 Mike Caspar > >:
>>
>>> Hi there, 
>>>
>>> I've started some work on examples and would also be happy to accept 
>>> other PRs as well after giving them a quick once over.
>>>
>>> Can someone help me get write access to this repo?
>>>
>>> https://github.com/jenkinsci/pipeline-examples
>>>
>>> See this thread for origin of request  
>>> 
>>> https://groups.google.com/forum/#!msg/jenkinsci-users/5sN7BR7daOs/oSFYaGqiNwAJ
>>>
>>> Mike Caspar
>>> (Jenkins plugin maintainer).
>>>
>>>
>>> -- 
>>> 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/7ab94c07-9c32-4f1b-bbb4-3949e0202c91%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/fNg223PDluw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6ejXRA6iN0n6Faz9vjhR9OF203iwB3MNZDB9DJHD62Wg%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/40129532-14fc-798c-0cfc-a066ad59a217%40caspar.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/352b5727-af27-4c0d-8358-d4eaa972748b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.