Help reviewing Chinese translation?

[James Dumay]

Hi all,

Is there anyone that could spare a few minutes to review a Chinese 
translation for the Favorite plugin?

https://github.com/jenkinsci/favorite-plugin/pull/19 

Help is much appreciated :) 

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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f76475b8-3274-424f-b517-0ce7d1d568c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Pipeline is not getting displayed Properly in BlueOcen

[James Dumay]

Yes, please use jenkins-users in future. But add your use case and picture 
to the comments of the ticket Jesse quoted.

On Thursday, August 17, 2017 at 12:46:42 AM UTC+10, Jesse Glick wrote:
>
> On Wed, Aug 16, 2017 at 8:11 AM, Satbachan Singh 
> > wrote: 
> > any existing defect with already there in BlueOcean 
>
> https://issues.jenkins-ci.org/browse/JENKINS-38442 
>

-- 
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/48633902-62a3-432c-9028-60a22f82609f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Getting 403 when trying to create pipeline

[James Dumay]

You wouldn't be behind a corp HTTP proxy would you? That exception suggests 
that Blue Ocean can't reach Github.

On Thursday, August 17, 2017 at 4:43:19 AM UTC+10, Cliff Meyers wrote:
>
> Hello Mike and Th3Alibi,
>
> If one of you is willing to file a ticket in the Jenkins JIRA with repro 
> steps and cc me via comment, I'll be happy to take a look. 
>
> Thanks,
> Cliff
>
> On Sun, Aug 13, 2017 at 11:46 PM, Mike Flynn  > wrote:
>
>> Any update on this thread? I'm seeing the exact same error in my 
>> jenkins.log when trying to make a pipeline in a repo via the Blue Ocean 
>> wizard.
>>
>>
>> On Thursday, June 22, 2017 at 7:15:38 AM UTC-7, Th3Alibi wrote:
>>>
>>> I've tried both.
>>>
>>> On Tuesday, 20 June 2017 16:52:08 UTC-4, Keith Zantow wrote:

 Did you use the link in the Blue Ocean UI to create your token or did 
 you create it manually?


 On Tue, Jun 20, 2017 at 4:14 PM, Th3Alibi  wrote:

> I am having a hard time using Blue Ocean.  When I add my token and 
> attempt to create a new pipeline, Jenkins logs are showing below stack 
> trace.  This is happening in both standalone jenkins and cloudbees 
> enterprise.  The token is good, I have tested the auth.  We are using an 
> organization account with private repositories on GitHub.
>
> Standalone Jenkins: 2.46.3
> java version "1.8.0_40"
> Java(TM) SE Runtime Environment (build 1.8.0_40-b26)
> Java HotSpot(TM) Client VM (build 25.40-b25, mixed mode)
>
> Cloudbees Enterprise Anywhere:
> cje-mm:2.46.3-rolling
>
> Jun 20, 2017 4:00:46 PM 
> io.jenkins.blueocean.blueocean_github_pipeline.GithubPipelineCreateRequest
>  
> cleanupOnError
> SEVERE: Error creating pipeline [ORG_NAME]: {"message":"Bad 
> credentials","documentation_url":"https://developer.github.com/v3"}
> java.io.FileNotFoundException: {"message":"Bad 
> credentials","documentation_url":"https://developer.github.com/v3"}
> at 
> org.kohsuke.github.Requester.handleApiError(Requester.java:650)
> at org.kohsuke.github.Requester._to(Requester.java:283)
> at org.kohsuke.github.Requester.to(Requester.java:224)
> at 
> org.kohsuke.github.GitHub.checkApiUrlValidity(GitHub.java:668)
> at 
> org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.checkApiUrlValidity(GitHubSCMSource.java:501)
> at 
> org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:444)
> at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:300)
> at jenkins.scm.api.SCMSource.fetch(SCMSource.java:230)
> at 
> io.jenkins.blueocean.blueocean_github_pipeline.GithubPipelineCreateRequest.repoHasJenkinsFile(GithubPipelineCreateRequest.java:304)
> at 
> io.jenkins.blueocean.blueocean_github_pipeline.GithubPipelineCreateRequest.create(GithubPipelineCreateRequest.java:173)
> at 
> io.jenkins.blueocean.rest.model.BluePipelineContainer.create(BluePipelineContainer.java:48)
> at 
> io.jenkins.blueocean.rest.model.BluePipelineContainer.create(BluePipelineContainer.java:44)
> at java.lang.invoke.MethodHandle.invokeWithArguments(Unknown 
> Source)
> at 
> org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)
> at 
> org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)
> at 
> org.kohsuke.stapler.SelectionInterceptedFunction$Adapter.invoke(SelectionInterceptedFunction.java:36)
> at 
> org.kohsuke.stapler.verb.HttpVerbInterceptor.invoke(HttpVerbInterceptor.java:48)
> at 
> org.kohsuke.stapler.SelectionInterceptedFunction.bindAndInvoke(SelectionInterceptedFunction.java:26)
> at 
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)
> at 
> org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:26)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)
> at 
> org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:209)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)
> at 
> org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)
> at 
> org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)
> at 
>

Re: Proposal: Add optional "Released as" and "Stage Release" states to JIRA

[James Dumay]

I am merely giving a reasonable response to the proposal, which I think is 
fair, given I am the component leader on projects cited as benefiting from 
this change. 

The tool we use already makes provisions for the problems outlined. 
Additional statuses will not add clarity as this is now how JIRA projects 
are usually used which runs contrary to user expectations of this widely 
used tool. 

Secondly, as someone who spends much time in JIRA who would benefit from 
tracking such information, the proposed fields cannot be used in 
conjunction with JIRA reporting functionality such as Created vs Resolved 
charts, which are very beneficial to those who manage triaging and tracking 
the health of sub-projects.


On Tuesday, August 15, 2017 at 6:34:20 PM UTC+10, Oleg Nenashev wrote:
>
> Hi James,
>  
>
>> -1 JIRA was designed to have a project per software lifecycle. The fact 
>> that we have 1000 plugins in the same JENKINS project breaks all the nice 
>> things about JIRA, such as the Fixed For field and Versions, which was 
>> designed for this very problem.
>
>
> I know you do not like the current JIRA structure, but I do not see how 
> your comment is related to the proposal. I want to improve the current 
> project structure, not to create a new one.
>
> If you want to change the JIRA design and to decouple plugins to projects, 
> feel free to do it in a separate thread
>
> BR, Oleg
>
>
> 2017-08-15 9:19 GMT+02:00 James Dumay >
> :
>
>> -1 JIRA was designed to have a project per software lifecycle. The fact 
>> that we have 1000 plugins in the same JENKINS project breaks all the nice 
>> things about JIRA, such as the Fixed For field and Versions, which was 
>> designed for this very problem.
>>
>>
>> On Monday, August 14, 2017 at 7:45:08 PM UTC+10, Oleg Nenashev wrote:
>>>
>>> Hi all,
>>>
>>> As a Jenkins user and contributor, I sometimes have difficulties when I 
>>> need to understand in which release the fix is available. GitHub commit 
>>> links from the bot help much, but it requires extra time to navigate across 
>>> commits and UI. In Jenkins core, Remoting and my plugins I would like to 
>>> make it more explicit:
>>>
>>> I propose to...
>>>
>>>1. Modify workflow in the JENKINS project:
>>>   - Add a "Stage Release" state (or whatever similar name)
>>>   - Instead of "In Progress" => "Resolved", contributors can move 
>>>   integrated fixed into the "Stage Release" state.
>>>   - It may be helpful for components which do not release the 
>>>   integrated fixes immediately (e.g. Core, its modules, Remoting, 
>>> Stapler, 
>>>   Blue Ocean, other plugins)
>>>   2. Add an optional "Released As" field to JIRA (type=String)
>>>   - When a contributor moves the issue to "Stage release", 
>>>   "Resolved" or "Closed" state, an optional field appears in the dialog
>>>   - If the field is non-empty, it will appear in the ticket header, 
>>>   hence users won't need to look into comments and commit histories
>>>   
>>> This proposal could improve contributor and user experience, but the 
>>> proposed change is opt-in. 
>>>
>>> It does not make the field/state mandatory, hence the existing flows 
>>> won't be affected if the maintainers do not want to spend time on JIRA 
>>> updates.
>>>
>>>
>>> WDYT?
>>>
>>>
>>> Thanks in advance, 
>>>
>>> Oleg
>>>
>> -- 
>> 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/wzc4VLplHvs/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/a835c953-65a4-44a7-b1f0-55384d0498e9%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/a835c953-65a4-44a7-b1f0-55384d0498e9%40googlegroups.com?utm_medium=email&utm_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/61e48fa9-5b59-4ee8-8e2c-227376c251b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Add optional "Released as" and "Stage Release" states to JIRA

[James Dumay]

-1 JIRA was designed to have a project per software lifecycle. The fact 
that we have 1000 plugins in the same JENKINS project breaks all the nice 
things about JIRA, such as the Fixed For field and Versions, which was 
designed for this very problem.

On Monday, August 14, 2017 at 7:45:08 PM UTC+10, Oleg Nenashev wrote:
>
> Hi all,
>
> As a Jenkins user and contributor, I sometimes have difficulties when I 
> need to understand in which release the fix is available. GitHub commit 
> links from the bot help much, but it requires extra time to navigate across 
> commits and UI. In Jenkins core, Remoting and my plugins I would like to 
> make it more explicit:
>
> I propose to...
>
>1. Modify workflow in the JENKINS project:
>   - Add a "Stage Release" state (or whatever similar name)
>   - Instead of "In Progress" => "Resolved", contributors can move 
>   integrated fixed into the "Stage Release" state.
>   - It may be helpful for components which do not release the 
>   integrated fixes immediately (e.g. Core, its modules, Remoting, 
> Stapler, 
>   Blue Ocean, other plugins)
>   2. Add an optional "Released As" field to JIRA (type=String)
>   - When a contributor moves the issue to "Stage release", "Resolved" 
>   or "Closed" state, an optional field appears in the dialog
>   - If the field is non-empty, it will appear in the ticket header, 
>   hence users won't need to look into comments and commit histories
>   
> This proposal could improve contributor and user experience, but the 
> proposed change is opt-in. 
>
> It does not make the field/state mandatory, hence the existing flows won't 
> be affected if the maintainers do not want to spend time on JIRA updates.
>
>
> WDYT?
>
>
> Thanks in advance, 
>
> Oleg
>

-- 
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/a835c953-65a4-44a7-b1f0-55384d0498e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bamboo step plugin?

[James Dumay]

New contributions and plugins are always welcome :)

On Wednesday, August 9, 2017 at 8:28:41 AM UTC+10, Kyle Flavin wrote:
>
> We have a custom Bamboo step plugin that we're using in our Jenkinsfile to 
> call build plans on our Bamboo server from Jenkins.  I'm wondering if I 
> should try to get hosting for it in the community repositories, as there 
> doesn't seem to be anything else out there.  There's the Bamboo Notifier 
> , but it isn't specifically 
> built for use with pipeline.
>
> Here's an example usage from our Jenkinsfile:
>
> pipeline {
> ...
> stages {
> stage("Build Bamboo job") {
> steps {
> script {
> buildBamboo(projectKey: "PROJECT-KEY", planKey: "PKEY"
> , serverAddress: 'https://bamboo-server', 'username': env.BAMBOO_USER, 
> 'password': env.BAMBOO_PASS)
> }
> }
> }
> }
> ...
> }
>
>
> Just curious.  Will pursue if it makes sense.  We have one for BuildForge 
> as well.
>
> 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/77ea403d-c824-4556-bac9-de233396e632%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: RateLimitHandler error

[James Dumay]

Reflection is also going to break when someone inevitably changes the 
library. As a rule we do not use such hacks in Blue Ocean.

On Tuesday, July 4, 2017 at 5:08:14 PM UTC+10, Oleg Nenashev wrote:
>
> Thanks James for catching another dependency! Added Sam To Cc.
>
> Anyway, both plugins use new versions of GitHub API, hence the should not 
> cause the reported issue with the missing class. So it comes from something 
> else, maybe from a transient library dependency. We definitely need a bug 
> in JIRA with a list of plugin and a support core bundle to diagnose it more.
>
> Regarding the reflection proposal, it looks a good approach though I do 
> not know why BlueOcean can't just depend on the GitHub API plugin. In 
> Github API lib there is direct class name references, so reflection should 
> work. Proper reflection with OkHttp & Co will require more efforts though.
>
> BR, Oleg
>
>
> вторник, 4 июля 2017 г., 3:19:40 UTC+2 пользователь James Dumay написал:
>>
>> We depend on it directly because we use it directly to make the Pipeline 
>> Editor work. 
>>
>>
>> https://github.com/jenkinsci/blueocean-plugin/blob/404ac7275b4bac85b8ebaea3e7245abc94cb4769/pom.xml#L471
>>  
>>
>> We just started to use that new API for handling rate limits and abuse 
>> limits so the UI doesn't freeze up.
>>
>> https://github.com/jenkinsci/blueocean-plugin/pull/1214 
>>
>> The other plugin that does not depend on the Github plugin but probably 
>> shouldn't (isn't SCM related) is the Github Oauth plugin. It also uses the 
>> limit handlers to prevent web threads from being eaten and locking up the 
>> UI.
>>
>> https://github.com/jenkinsci/github-oauth-plugin 
>>
>> A few things here:
>> * perhaps we need to shade in the Github library into each plugin that 
>> requires it. Avoid version hell altogether
>> * start versioning the Github library so it's clear when there are major 
>> breaking changes between versions. Stephen C does an excellent job at this 
>> for all the branch and scm API changes.
>>
>>
>>
>> On Tue, Jul 4, 2017 at 2:49 AM Oleg Nenashev  wrote:
>>
>>> Likely it is a binary conflict with GitHub API version older than 1.64 
>>> (commit: 
>>> https://github.com/kohsuke/github-api/commit/4093e53b5b7eb16e0b4de184a93262285ee6164b).
>>>  
>>>
>>>
>>> The first step is to ensure that all plugins depend on GitHub API Plugin 
>>> instead of the direct library dependency. Added James Dumay to cc, because 
>>> here is something strange in BlueOcean: 
>>> https://github.com/jenkinsci/blueocean-plugin/blob/404ac7275b4bac85b8ebaea3e7245abc94cb4769/blueocean-github-pipeline/pom.xml#L32-L35
>>>  
>>> . I do not see other direct GitHub API usages within jenkinsci org plugins 
>>> from what I see
>>>
>>> понедельник, 3 июля 2017 г., 11:47:35 UTC+2 пользователь Ullrich Hafner 
>>> написал:
>>>>
>>>> Please use the issue tracker to report bugs.
>>>>
>>>> Am 03.07.2017 um 05:48 schrieb Luo :
>>>>
>>>> Hi Expert 
>>>>   I'm running Jenkins with gitlab, when I trigger a build, there are 
>>>> following error in console:
>>>>
>>>> FATAL: org/kohsuke/github/RateLimitHandlerjava.lang.NoClassDefFoundError 
>>>> <http://stacktrace.jenkins-ci.org/search?query=java.lang.NoClassDefFoundError>:
>>>>  org/kohsuke/github/RateLimitHandler
>>>>at 
>>>> org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification.createBuildCommitStatus(GitHubBuildStatusNotification.java:139)
>>>>  
>>>> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification.createBuildCommitStatus&entity=method>
>>>>at 
>>>> org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification.access$500(GitHubBuildStatusNotification.java:69)
>>>>  
>>>> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification.access$500&entity=method>
>>>>at 
>>>> org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification$JobCheckOutListener.onCheckout(GitHubBuildStatusNotification.java:285)
>>>>  
>>>> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification$JobCheckOutListener.onCheckout&entity=method>
>>>>at 
>

Re: RateLimitHandler error

[James Dumay]

We depend on it directly because we use it directly to make the Pipeline
Editor work.

https://github.com/jenkinsci/blueocean-plugin/blob/404ac7275b4bac85b8ebaea3e7245abc94cb4769/pom.xml#L471


We just started to use that new API for handling rate limits and abuse
limits so the UI doesn't freeze up.

https://github.com/jenkinsci/blueocean-plugin/pull/1214

The other plugin that does not depend on the Github plugin but probably
shouldn't (isn't SCM related) is the Github Oauth plugin. It also uses the
limit handlers to prevent web threads from being eaten and locking up the
UI.

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

A few things here:
* perhaps we need to shade in the Github library into each plugin that
requires it. Avoid version hell altogether
* start versioning the Github library so it's clear when there are major
breaking changes between versions. Stephen C does an excellent job at this
for all the branch and scm API changes.



On Tue, Jul 4, 2017 at 2:49 AM Oleg Nenashev  wrote:

> Likely it is a binary conflict with GitHub API version older than 1.64
> (commit:
> https://github.com/kohsuke/github-api/commit/4093e53b5b7eb16e0b4de184a93262285ee6164b).
>
>
> The first step is to ensure that all plugins depend on GitHub API Plugin
> instead of the direct library dependency. Added James Dumay to cc, because
> here is something strange in BlueOcean:
> https://github.com/jenkinsci/blueocean-plugin/blob/404ac7275b4bac85b8ebaea3e7245abc94cb4769/blueocean-github-pipeline/pom.xml#L32-L35
> . I do not see other direct GitHub API usages within jenkinsci org plugins
> from what I see
>
> понедельник, 3 июля 2017 г., 11:47:35 UTC+2 пользователь Ullrich Hafner
> написал:
>>
>> Please use the issue tracker to report bugs.
>>
>> Am 03.07.2017 um 05:48 schrieb Luo :
>>
>> Hi Expert
>>   I'm running Jenkins with gitlab, when I trigger a build, there are
>> following error in console:
>>
>> FATAL: org/kohsuke/github/RateLimitHandlerjava.lang.NoClassDefFoundError 
>> <http://stacktrace.jenkins-ci.org/search?query=java.lang.NoClassDefFoundError>:
>>  org/kohsuke/github/RateLimitHandler
>>  at 
>> org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification.createBuildCommitStatus(GitHubBuildStatusNotification.java:139)
>>  
>> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification.createBuildCommitStatus&entity=method>
>>  at 
>> org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification.access$500(GitHubBuildStatusNotification.java:69)
>>  
>> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification.access$500&entity=method>
>>  at 
>> org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification$JobCheckOutListener.onCheckout(GitHubBuildStatusNotification.java:285)
>>  
>> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.github_branch_source.GitHubBuildStatusNotification$JobCheckOutListener.onCheckout&entity=method>
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609)
>>  
>> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout&entity=method>
>>  at 
>> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 
>> <http://stacktrace.jenkins-ci.org/search/?query=jenkins.scm.SCMCheckoutStrategy.checkout&entity=method>
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
>>  
>> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.run&entity=method>
>>  at hudson.model.Run.execute(Run.java:1741) 
>> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute&entity=method>
>>  at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
>> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.run&entity=method>
>>  at hudson.model.ResourceController.execute(ResourceController.java:98) 
>> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method>
>>  at hudson.model.Executor.run(Executor.java:410) 
>> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method>
>> Caused by: java.lang.ClassNotFoundException 
>> <http://stacktrace.jenkins-ci.org/search?query=java.lang.ClassNotFoundException>:
>>  org.kohsuke.github.RateLimitHandler
>&g

Anonymous user analytics in Blue Ocean

[James Dumay]

Hi all,

I've opened a PR [1] to add anonymous user analytics to Blue Ocean. I want 
to use this data to help me understand what the usage patterns of Blue 
Ocean are. Many open source tools have this kind of anonymous analytics 
reporting - Docker and Homebrew to name a few. It's used for to help figure 
out where users are struggling and what enhancements we can make to help 
users.

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?). 

[1] https://github.com/jenkinsci/blueocean-plugin/pull/1202 
[2] 
https://mixpanel.com/blog/2009/06/10/introduction-to-analytics-funnel-analysis/
[3] https://wiki.jenkins.io/display/JENKINS/Usage+Statistics
[4] 
https://github.com/jenkinsci/blueocean-plugin/blob/418a4cd2c8729be13a55db7a398140c55efb9e37/blueocean-rest-impl/src/main/java/io/jenkins/blueocean/service/embedded/analytics/AbstractAnalytics.java#L64
 
[5] https://keen.io/

I will leave the PR unmerged for a week to hear out any objections, 
concerns, etc. 

Looking forward to your thoughts and feedback.

Cheers,

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

Re: So I guess it's time to leave Google Groups

[James Dumay]

ceived 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/CAPiUgVdvXbyzK1V2SiFXM-mYzagf1sZ%2BjSSxixhWLP80yCG3mA%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdvXbyzK1V2SiFXM-mYzagf1sZ%2BjSSxixhWLP80yCG3mA%40mail.gmail.com?utm_medium=email&utm_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/CAHtcACEaD4WKEh8wcCbuGvRrMRT5j4_36AA7XdqjwrmBn4rWRg%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAHtcACEaD4WKEh8wcCbuGvRrMRT5j4_36AA7XdqjwrmBn4rWRg%40mail.gmail.com?utm_medium=email&utm_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/f917ff56-54b5-4cd3-9c86-89e7dfa0e764%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/f917ff56-54b5-4cd3-9c86-89e7dfa0e764%40googlegroups.com?utm_medium=email&utm_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/ti_tmw23tyk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BzfM3CAOLsf%3DwxBOS0jQm4%3DpXbshGqEtLeXCopFtB7mWj-5Cw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BzfM3CAOLsf%3DwxBOS0jQm4%3DpXbshGqEtLeXCopFtB7mWj-5Cw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
James Dumay,
Director of Product Management.
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/CAErbOvSWKX_OAo%2Bu4pFWgizYy7gCJ97vVDwHibALg%2B1PoydVxA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Subversion plugin quality

[James Dumay]

Would appreciate a review 
of https://github.com/jenkinsci/subversion-plugin/pull/184 to fix a 
critical file handle leak. Fix was simple enough.

On Friday, May 26, 2017 at 6:39:42 PM UTC+10, Oleg Nenashev wrote:
>
> Hi,
>
> I have added Manuel Recena to Cc. He was the last one who claimed 
> ownership of the SVN plugin, and AFAIK he has not formally transferred the 
> ownership or marked the plugin for adoption. So he is a nominal maintainer 
> now.
>
> Generally the plugin is in the pretty unhealthy state now. It requires 
> man-months just to address bleeding issues in JIRA. Regarding the redesign, 
> it could be a good option if somebody is ready to invest significant amount 
> of time into it. I'm not (at least personal time). Not sure if we still 
> have many active committers using SVN.
>
> BR, Oleg
>
> четверг, 25 мая 2017 г., 21:28:25 UTC+2 пользователь slide написал:
>>
>> Oh, that makes it much nicer. I didn't know about the --xml option. I 
>> would say going the parsing route would be awesome. It would be great to 
>> have the ability to see the commands that are being executed, I believe the 
>> git plugin does this and it's very useful.
>>
>> On Thu, May 25, 2017 at 11:06 AM Jesse Glick  
>> wrote:
>>
>>> On Thu, May 25, 2017 at 12:00 PM, Slide  wrote:
>>> > Would JavaHL be a solution that could cut down on the amount of parsing
>>> > that would need to be done by the plugin?
>>>
>>> Sounds like even more trouble than SVNKit—native code, including
>>> possible JVM corruption issues, *and* platform dependencies.
>>>
>>> Parsing per se is not an issue since you can pass `--xml` to every 
>>> command.
>>>
>>> --
>>> 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/CANfRfr2a9TOHdEieZTL3Zf3Cwnme2XAHG%3Dq%2ByV45yV-Ueq6fFw%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/40087858-b64b-4df7-9ab6-7f83f02a6ce7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Subversion plugin quality

[James Dumay]

I started closing out some of the most ancient or inactive tickets, asking 
for people to reopen with reproduction instructions after having tested on 
the latest versions.

Would anyone be able to help triage the more recent ones? Filter can be 
found at https://issues.jenkins-ci.org/issues/?filter=17441 

On Friday, May 26, 2017 at 2:00:27 AM UTC+10, slide wrote:
>
> I'd like to help triage these as well, the subversion plugin was on my 
> priority list for the Bug Triage Team since it was second only to core in 
> terms of open issues. 
>
> Would JavaHL [1] be a solution that could cut down on the amount of 
> parsing that would need to be done by the plugin? It would still require a 
> native subversion (library) to be on the system.
>
> 1 - http://subversion.apache.org/docs/javahl/latest/
>
> On Thu, May 25, 2017 at 6:01 AM Jesse Glick  > wrote:
>
>> On Wed, May 24, 2017 at 8:02 PM, James Dumay > > wrote:
>> > are there any active maintainers for this plugin
>>
>> Not that I am aware of.
>>
>> > OK if I triaged the outstanding tickets?
>>
>> I cannot imagine anyone objecting to your volunteering such work.
>>
>> The broader issue I see is JENKINS-28251: the SVNKit-based
>> implementation is the source of countless problems, and given limited
>> development resources there is no way they will all get fixed. IMO the
>> only sustainable path for this plugin would be to deprecate that mode
>> and switch by default to a command-line implementation, as the Git
>> plugin does. This would involve a block of significant effort, but
>> after that further problems in the execution of SCM operations (the
>> main source of complaints for the plugin) would reduce to checking
>> whether the plugin is running the right command or not, a much more
>> approachable question for casual contributors. (The situation is
>> trickier for multibranch operations in `SubversionSCMSource`: we would
>> need to decide whether indexing operations should remain on SVNKit, or
>> whether the master would be required to have `svn` installed. The Git
>> plugin takes the former approach, the Mercurial plugin the latter.)
>>
>> By the way in your message I think you were attempting to post a
>> search link, but it did not come out that way.
>>
>> --
>> 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/CANfRfr0MxXEzjHsLGHWBHpQQEhC6AKVLwgzW-X4cwg6GD5rDUw%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/7f3bb076-6322-4bcf-b419-270aff4b3adb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Subversion plugin quality

[James Dumay]

The filter is https://issues.jenkins-ci.org/issues/?filter=17441 

On Thursday, May 25, 2017 at 11:01:13 PM UTC+10, Jesse Glick wrote:
>
> On Wed, May 24, 2017 at 8:02 PM, James Dumay  > wrote: 
> > are there any active maintainers for this plugin 
>
> Not that I am aware of. 
>
> > OK if I triaged the outstanding tickets? 
>
> I cannot imagine anyone objecting to your volunteering such work. 
>
> The broader issue I see is JENKINS-28251: the SVNKit-based 
> implementation is the source of countless problems, and given limited 
> development resources there is no way they will all get fixed. IMO the 
> only sustainable path for this plugin would be to deprecate that mode 
> and switch by default to a command-line implementation, as the Git 
> plugin does. This would involve a block of significant effort, but 
> after that further problems in the execution of SCM operations (the 
> main source of complaints for the plugin) would reduce to checking 
> whether the plugin is running the right command or not, a much more 
> approachable question for casual contributors. (The situation is 
> trickier for multibranch operations in `SubversionSCMSource`: we would 
> need to decide whether indexing operations should remain on SVNKit, or 
> whether the master would be required to have `svn` installed. The Git 
> plugin takes the former approach, the Mercurial plugin the latter.) 
>
> By the way in your message I think you were attempting to post a 
> search link, but it did not come out that way. 
>

-- 
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/3d8ae2c6-6523-4f07-a663-1cf06b017d81%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Subversion plugin quality

[James Dumay]

When I was working on *the other* CI system we had very good support for 
Subversion through SVNKit. I'd be very surprised if the quality issues stem 
from this component.

On Friday, May 26, 2017 at 4:06:48 AM UTC+10, Jesse Glick wrote:
>
> On Thu, May 25, 2017 at 12:00 PM, Slide > 
> wrote: 
> > Would JavaHL be a solution that could cut down on the amount of parsing 
> > that would need to be done by the plugin? 
>
> Sounds like even more trouble than SVNKit—native code, including 
> possible JVM corruption issues, *and* platform dependencies. 
>
> Parsing per se is not an issue since you can pass `--xml` to every 
> command. 
>

-- 
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/2b076866-079f-4441-8229-7f6844de9f79%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Subversion plugin quality

[James Dumay]

Hi all,

I've had a number of requests to integrate Subversion into Blue Ocean 
 (specifically for 
pipeline creation and editing). On review there seem to be a number of 
blocker or critical bugs 
 in JIRA assigned to 
the subversion-plugin which isn't giving me much optimism that if we 
integrate this with Blue Ocean that users are going to have a good 
experience with it. Though digging through the tickets there seem to be a 
number of blockers/critical open that have very few votes for their age 
(for example, this ticket 
that has zero votes and 
has had no activity since 2008). The situation might not be that bad after 
all.

My question is: are there any active maintainers for this plugin and would 
they be OK if I triaged the outstanding tickets? I'd love to whittle down 
what are real outstanding issues and what are not.

Cheers,

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

Re: So I guess it's time to leave Google Groups

[James Dumay]

OK so I've setup a trial that we can play around with at
http://jenkins.trydiscourse.com/

you can email jenkins+us...@discoursemail.com to create new topics

On Mon, May 15, 2017 at 5:54 AM James Dumay  wrote:

> Ill spin one up so we can take a look :)
> On Mon, 15 May 2017 at 5:26 am, James Dumay  wrote:
>
>> It looks like there's been a huge amount of work to get Discourse to act
>> like a mailman replacement
>>
>> https://github.com/discourse/discourse/pull/2012
>>
>> Perhaps we should collect some more requirements from the community then
>> evaluate more deeply and make a call based on that information?
>>
>>
>> On Mon, 15 May 2017 at 4:45 am, Richard Bywater 
>> wrote:
>>
>>> From memory the emails you receive were more like notification messages
>>> (with all kinds of guff about links to the page etc in). However they may
>>> have changed since I last used. (Basically would like to see as close to a
>>> like for like in terms of email readability and replyability)
>>>
>>> Richard
>>>
>>> On Mon, 15 May 2017, 6:34 AM Daniel Beck  wrote:
>>>
>>>>
>>>> > On 14.05.2017, at 09:37, Richard Bywater  wrote:
>>>> >
>>>> > Personally I'm -1 for Discourse. Discourse is a great forum but I
>>>> think the mailing list way works best.
>>>>
>>>> Can't Discourse be used via email as well?
>>>>
>>>> --
>>>> 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/FCEA8C69-D58E-4755-BCCD-BD914897EE55%40beckweb.net
>>>> .
>>>> 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/ti_tmw23tyk/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMui945mVJfHSO25VwfzJsiLLd4mWWS%3DDwsOimMAWi502ZdVpw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMui945mVJfHSO25VwfzJsiLLd4mWWS%3DDwsOimMAWi502ZdVpw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> James Dumay,
>> Director of Product Management.
>> CloudBees, Inc.
>> Skype: jdumaycb Twitter: i386
>>
> --
> James Dumay,
> Director of Product Management.
> CloudBees, Inc.
> Skype: jdumaycb Twitter: i386
>
-- 
James Dumay,
Director of Product Management.
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/CAErbOvS3kSgP50RQeoDUkQz9fmUbtOBo-nVC4mYDSGEuy5xmxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: So I guess it's time to leave Google Groups

[James Dumay]

Ill spin one up so we can take a look :)
On Mon, 15 May 2017 at 5:26 am, James Dumay  wrote:

> It looks like there's been a huge amount of work to get Discourse to act
> like a mailman replacement
>
> https://github.com/discourse/discourse/pull/2012
>
> Perhaps we should collect some more requirements from the community then
> evaluate more deeply and make a call based on that information?
>
>
> On Mon, 15 May 2017 at 4:45 am, Richard Bywater  wrote:
>
>> From memory the emails you receive were more like notification messages
>> (with all kinds of guff about links to the page etc in). However they may
>> have changed since I last used. (Basically would like to see as close to a
>> like for like in terms of email readability and replyability)
>>
>> Richard
>>
>> On Mon, 15 May 2017, 6:34 AM Daniel Beck  wrote:
>>
>>>
>>> > On 14.05.2017, at 09:37, Richard Bywater  wrote:
>>> >
>>> > Personally I'm -1 for Discourse. Discourse is a great forum but I
>>> think the mailing list way works best.
>>>
>>> Can't Discourse be used via email as well?
>>>
>>> --
>>> 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/FCEA8C69-D58E-4755-BCCD-BD914897EE55%40beckweb.net
>>> .
>>> 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/ti_tmw23tyk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMui945mVJfHSO25VwfzJsiLLd4mWWS%3DDwsOimMAWi502ZdVpw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMui945mVJfHSO25VwfzJsiLLd4mWWS%3DDwsOimMAWi502ZdVpw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> James Dumay,
> Director of Product Management.
> CloudBees, Inc.
> Skype: jdumaycb Twitter: i386
>
-- 
James Dumay,
Director of Product Management.
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/CAErbOvQZUpjN6R9dqmWePcssO8e72Fva9y%3DxL07Fpa1Ydur3OA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: So I guess it's time to leave Google Groups

[James Dumay]

It looks like there's been a huge amount of work to get Discourse to act
like a mailman replacement

https://github.com/discourse/discourse/pull/2012

Perhaps we should collect some more requirements from the community then
evaluate more deeply and make a call based on that information?


On Mon, 15 May 2017 at 4:45 am, Richard Bywater  wrote:

> From memory the emails you receive were more like notification messages
> (with all kinds of guff about links to the page etc in). However they may
> have changed since I last used. (Basically would like to see as close to a
> like for like in terms of email readability and replyability)
>
> Richard
>
> On Mon, 15 May 2017, 6:34 AM Daniel Beck  wrote:
>
>>
>> > On 14.05.2017, at 09:37, Richard Bywater  wrote:
>> >
>> > Personally I'm -1 for Discourse. Discourse is a great forum but I think
>> the mailing list way works best.
>>
>> Can't Discourse be used via email as well?
>>
>> --
>> 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/FCEA8C69-D58E-4755-BCCD-BD914897EE55%40beckweb.net
>> .
>> 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/ti_tmw23tyk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAMui945mVJfHSO25VwfzJsiLLd4mWWS%3DDwsOimMAWi502ZdVpw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMui945mVJfHSO25VwfzJsiLLd4mWWS%3DDwsOimMAWi502ZdVpw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
James Dumay,
Director of Product Management.
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/CAErbOvRojn1S3yF62KQ%3DZKiUpNapaS9NnYeBTE001nJG2H19eQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: So I guess it's time to leave Google Groups

[James Dumay]

I believe Discourse would be a great alternative. A lot of the new crowd 
thats coming in via Blue Ocean haven't interacted with mailing lists before 
so there is a chance here to bring more people in to the community that way.

Discourse can be self hosted or we can pay them to do it. I am sure we can 
find a sponsor for ether of those things.

https://www.discourse.org/ 


On Saturday, May 13, 2017 at 8:17:20 AM UTC+10, R Tyler Croy wrote:
>
> If you can read this, the Google Group has been reinstated as quietly as 
> it was 
> banned. 
>
>
> I think it might be time for us to be moving on :( 
>
>
> - 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/d202f508-470c-428c-b822-1ea33d49a953%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade to Jetty 9.4.x

[James Dumay]

Are there any major changes (apart from Java 8 requirement) that plugins 
authors should look out for?

On Wednesday, May 3, 2017 at 10:14:42 PM UTC+10, Olivier Lamy wrote:
>
> Hi Folks
> I have few prs to upgrade to jetty 9.4.x 
>
> https://github.com/jenkinsci/winstone/pull/32
> https://github.com/jenkinsci/jenkins/pull/2850
> https://github.com/jenkinsci/maven-hudson-dev-plugin/pull/5
>
> Let me know as I'm really close to push the merge button :-)
>
> Maybe hpi plugin as well, WDYT? (remember Jetty 9.4.x is Java 8 mandatory)
>
> Cheers
> -- 
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>

-- 
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/99c7e80a-9f4d-44cf-8ff6-f9b3ed637746%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue ocean

[James Dumay]

You should watch and vote for this ticket for updates!

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

On Thursday, April 6, 2017 at 4:26:56 PM UTC+10, Вячеслав Юрьевич Мандрица 
wrote:
>
> Good day!
>
> I'm very thankful for you answer and already have been using steps you 
> advised.
> What's more important, you made me confidant, that everything is okay on 
> the current stage of the Blue Ocean project and it is not linked with 
> manual install of this.
> The Blue Ocean plugin is awesome in idea and I wish you all best in it's 
> developing!
>
> 2017-04-05 18:11 GMT+03:00 Keith Zantow  >:
>
>> Hi!
>>
>> Currently, the visual pipeline editor is integrated as part of the 
>> pipeline creation flow. Due to some complexities in writing to a Git 
>> repository and lack of a generalized API for it, the visual editor is only 
>> available to save when using a Github organization at the moment.
>>
>> We're currently working on a design for these cases as well as a 
>> prototype of integrating with Git directly, this is definitely a high 
>> priority.
>>
>> However, you should be able to press CTRL-S on Windows or CMD-S to get 
>> the pipeline text to copy back to your repository manually until the 
>> aforementioned work is done.
>>
>> Thanks!
>>
>> On Wed, Apr 5, 2017 at 10:57 AM, Вячеслав Юрьевич Мандрица <
>> vj.ma...@physics.msu.ru > wrote:
>>
>>> Hello!
>>>
>>> We have been using Jenkins for several months, but now we Have me an 
>>> obstacle:
>>> Due to company politics, we cannot access Internet directly, thus we 
>>> have to update Jenkins manually.
>>>
>>> Today I have installed blue ocean 1.0.0 and there are some issues:
>>> 1) There is no Pipeline Editor button:
>>>
>>> 
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Going on "New pipeline" only creates one from Jenkinsfile on git/github 
>>> w/o opportunity of visual editing.
>>>
>>> 2) No save button on creating of pipeline
>>>
>>>
>>> 
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Thanks for answer and 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-de...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/fe956575-52e2-43bb-924b-1de6c69f209b%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/EuqOjO4aclA/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/CAJTHQaE9BQiP%3Dj%2B%2BGnPWFhm%3DUMnVKX%2BRhaSUQbanThAguptTqQ%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/479a4823-b0fe-47c7-8507-0e0728837203%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean taking over a minute to load

[James Dumay]

Yikes! Thats no good - I've raised JENKINS-43208 
 on your behalf and I 
am getting one of the CloudBees engineers to take a look. Would you be able 
to provide a full list of plugins and their versions that you are using on 
your instance? (Add them to the ticket)

Be sure to login to JIRA and click "watch" to get updates.

On Thursday, March 30, 2017 at 10:56:14 AM UTC+11, Marley Kudiabor wrote:
>
> I have an issue with Blue Ocean page loads taking an inordinate amount of 
> time to load. We have two Jenkins instances and only have this issue on one
>
> Blue Ocean version: 1.0.0-rc3
> Jenkins version: 2.32.2
>
> I've attached a har file of my issue
>
> There are only 28 jobs and the performance issues are exponentially worse 
> than on the other instance of jenkins running an older version of Blue 
> Ocean with a newer version of Jenkins
>

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

Re: Naming convention for sprints in Jira

[James Dumay]

Though this is one of those situations where if we used JIRA correctly
(anything having its own lifecycle should have a project) we could avoid
the name spacing issues (with the added bonus of being able to use Release
Versions - no more confusion as to what has shipped or not...)

On Tue, Mar 14, 2017 at 7:48 AM James Dumay  wrote:

> SGTM
>
> On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck  wrote:
>
> Hi everyone,
>
> it seems sprints in Jira are globally visible (across projects), and, when
> editing an issue, provide little context as to what that sprint is.
>
> I think some sort of prefix in names should be adopted by everyone using
> sprints in Jira -- basically James D right now -- to make it easy to see
> what it relates to. "1.1" is just too light on context. In James' case, BO,
> Blue Ocean, or similar would be helpful.
>
> In SECURITY related "sprints" (not really, but still helps plan) I've
> started using the 'SECURITY' prefix for sprints. So, for example, the
> 'sprint' released on Feb 1 was "SECURITY: Collins".
>
> WDYT?
>
> Daniel
>
> --
> James Dumay
> Product Manager
> CloudBees, Inc.
> Skype: jdumaycb Twitter: i386
>
-- 
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/CAErbOvSCb04K-2_K8q3DdfnGhX9YgqzCayd-mNz4cZpMCL%3DpXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Naming convention for sprints in Jira

[James Dumay]

SGTM

On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck  wrote:

> Hi everyone,
>
> it seems sprints in Jira are globally visible (across projects), and, when
> editing an issue, provide little context as to what that sprint is.
>
> I think some sort of prefix in names should be adopted by everyone using
> sprints in Jira -- basically James D right now -- to make it easy to see
> what it relates to. "1.1" is just too light on context. In James' case, BO,
> Blue Ocean, or similar would be helpful.
>
> In SECURITY related "sprints" (not really, but still helps plan) I've
> started using the 'SECURITY' prefix for sprints. So, for example, the
> 'sprint' released on Feb 1 was "SECURITY: Collins".
>
> WDYT?
>
> Daniel
>
> --
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/CAErbOvSZqeudFLcc8Ehh4WVVVpoGVAGUdT42KjOzo4eOniaMXQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Supporting Microsoft Edge

[James Dumay]

Hi all,

I believe we should now add Microsoft Edge to the Level 1 browser support
on https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix

To do this do we need any automation setup for testing with Edge? I am not
sure what our policy is here.

Thanks

-- 
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/CAErbOvT%2BkhDXr4Lr6-mf4%2BfNL1%2B9BDTAAP23R0R-CJfgzmWixg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Merge & release PR for mailer-plugin regression

[James Dumay]

Thanks :)
On Wed, 1 Feb 2017 at 2:30 am, Jesse Glick  wrote:

> On Tue, Jan 31, 2017 at 4:52 AM, James Dumay  wrote:
> > publish a new release?
>
> Done.
>
> --
> 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/JXih_zGAa2Y/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0hzb0yC77uXvPeTaXYUEtVbQU9j7vSGfa3VAVRw9S1dw%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
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/CAErbOvQX6YgnOWjhzWmf-C9HtA8DwaYefgjuHj6ocBQDBr4B%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Merge & release PR for mailer-plugin regression

[James Dumay]

Hi all,

I was just wondering if anyone would have some time to merge a reviewed PR 
for the mailer-plugin and publish a new release? I introduced a formatting 
issue  in an earlier PR.

https://github.com/jenkinsci/mailer-plugin/pull/34

Not sure who has the superpowers to do so but it would be incredibly 
helpful to get this one out of the way :)

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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1818aca1-451d-4e98-9e1f-f1bdc8359fd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean not running after update.

[James Dumay]

Hi Chris,

Hi Chris,

The best way we can help is if you file a bug against the blueocean-plugin 
component on https://issues.jenkins-ci.org/ 

Please provide your exact Blue Ocean and Jenkins version, along with any 
information you think would be helpful (such as use of a HTTP reverse proxy 
etc). For this issue I'd recommend attaching a few screenshots.

As Daniel mentioned, queries like this one are best performed on 
jenkinsci-users (and we monitor it daily too!)



On Tuesday, January 3, 2017 at 9:56:54 PM UTC+11, Chris wrote:
>
> Hi all, 
>
> After updating Blue Ocean after returning from the holidays it appears to 
> have stopped running.
>
> I can't see anything in the Jenkins logs regarding the plugin, is there 
> anywhere else I can look?
>
> Im running Blue Ocean beta - version 1.0.0-b14 and the issue occurs once I 
> have clicked onto 'Open Blue Ocean' returning a generic 'Can't connect to 
> the Server' message.
>
> If anyone can point me in the right direction it would be very helpful.
>
> 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/4528ff2f-474d-4da7-8929-c90946a4f571%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean]Stages in parallel not being displayed correctly

[James Dumay]

Alan how would you write the Jenkinsfile for that example?

On Fri, Dec 16, 2016 at 8:39 AM James Dumay  wrote:

> Thats great info Alan. BTW you should watch and vote for this ticket
> https://issues.jenkins-ci.org/browse/JENKINS-38442
>
> On Fri, Dec 16, 2016 at 8:35 AM Alan Wu  wrote:
>
> Thanks so much for all the quick responses.
>
> Personally I think having the ability to visualise nested stages within
> each parallel node are important.
>
> Says if I now have the parallel block within a stage called "Build and
> test" and add in a "deploy" stage after it,
> here is my two cents on how I imagine my use case should look.
>
>  / Slave1 -- configure -- build -- test \
>   Build and test - Slave2 -- configure -- build -- test - deploy
>  \ Slave3 -- configure -- build -- test /
>
>
>
> --
> 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/msDK4In10QU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/16e500b9-e0bf-4f58-9c5b-9a766dfd6a17%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/16e500b9-e0bf-4f58-9c5b-9a766dfd6a17%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> James Dumay
> Product Manager
> CloudBees, Inc.
> Skype: jdumaycb Twitter: i386
>
-- 
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/CAErbOvQY3sJGsKTPELKrLevdpQFagbBW9Xx5pM6iFVwAKSh0aA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean]Stages in parallel not being displayed correctly

[James Dumay]

Thats great info Alan. BTW you should watch and vote for this ticket
https://issues.jenkins-ci.org/browse/JENKINS-38442

On Fri, Dec 16, 2016 at 8:35 AM Alan Wu  wrote:

> Thanks so much for all the quick responses.
>
> Personally I think having the ability to visualise nested stages within
> each parallel node are important.
>
> Says if I now have the parallel block within a stage called "Build and
> test" and add in a "deploy" stage after it,
> here is my two cents on how I imagine my use case should look.
>
>  / Slave1 -- configure -- build -- test \
>   Build and test - Slave2 -- configure -- build -- test - deploy
>  \ Slave3 -- configure -- build -- test /
>
>
>
> --
> 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/msDK4In10QU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/16e500b9-e0bf-4f58-9c5b-9a766dfd6a17%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/16e500b9-e0bf-4f58-9c5b-9a766dfd6a17%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
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/CAErbOvQdOrrrL99fPnU03_MNxxLYc5C7yhVrXmp59DPsT6ZvGg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean]Stages in parallel not being displayed correctly

[James Dumay]

There's some design kinks to work out for nesting.

I've been asking people to illustrate their desired visualization for
nested staging when they've requested we fix visualization and I get a lot
of varied expectations regarding how it should look (I suspect we're going
to have to pick the most common interpretation)

Certainly something we want to look at in the post-1.0 time frame :)
On Fri, 16 Dec 2016 at 5:00 am, Jesse Glick  wrote:

> On Thu, Dec 15, 2016 at 2:00 AM, James Dumay  wrote:
> > […in Declarative Pipeline] Any parallels have to be within a stage and
> there is not nesting of stages.
>
> Making it unusable for the originally requested use case, since you
> could not differentiate the configure/make/test substages of each
> branch. Currently only the low-level *Pipeline Steps* link displays
> arbitrary structure. Stage View will display all the stages, but mixed
> up in a series, and the display gets messed up for builds in progress.
>
> --
> 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/msDK4In10QU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3y03Rpj9mZR%3D4VY19F7XUAcT0iryWzC58344Lf4_h73A%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
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/CAErbOvRTzZHpK44%3Dr%3DqSWNb9AK7MzVsj_H%2BzRgjZ3C7XWVa1sw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: What should we do with the CLI?

[James Dumay]

There is a REST API in Blue Ocean that could be repurposed for something 
like this if someone is keen.

On Tuesday, December 13, 2016 at 9:14:14 PM UTC+11, Robert Collins wrote:
>
> On 13 December 2016 at 17:03, Daniel Beck > 
> wrote: 
> > Hi everyone, 
> > 
> > We've now had not one, but two unauthenticated remote code execution 
> vulnerabilities in Jenkins: 
> > 
> > - SECURITY-218 in 
> https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11
>  
> > - SECURITY-360 in 
> https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-11-16
>  
> > 
> > Clearly, the current state of the CLI is a problem. Its Java 
> serialization based protocol without prior authentication has now 
> repeatedly resulted in remote code execution. For something like Jenkins, 
> keeper of all the secrets, this is just unacceptable. 
> > 
> > For now, we have a new system property that allows administrators to 
> disable all of the CLI. I don't think this is good enough, but it's all we 
> had time to do for SECURITY-360. 
> > https://jenkins.io/doc/upgrade-guide/2.19/#disabling-the-cli 
> > 
> > So, what are we going to do with the CLI? Remove it altogether? Only 
> allow access via SSHD? Only allow authenticated use? Don't use remoting? 
> Limit CLI remoting to specific users? WDYT? 
> > 
> > Daniel 
>
> Writing the CLI purely in terms of the REST API would be good - 
> security wise you then have a single path to secure, and no vulns 
> unique to the CLI; obviously some work is entailed :P. 
>
> -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/ff9dd158-7f22-422e-80b4-3853022f97df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean]Stages in parallel not being displayed correctly

[James Dumay]

While I am here, I'm going to plug Declarative Pipeline 
<https://github.com/jenkinsci/pipeline-model-definition-plugin/wiki/Parallelism>
 (new 
syntax for Pipeline). Any parallels have to be within a stage and there is 
not nesting of stages. As such Blue Ocean will visualise it perfectly for 
you every time you write a Jenkinsfile.

On Thursday, December 15, 2016 at 5:56:02 PM UTC+11, James Dumay wrote:
>
> That is correct. There is an open bug report tracking this issue 
> <https://issues.jenkins-ci.org/browse/JENKINS-39464> - please watch and 
> vote for it. The workaround is to surround your parallel with a stage block 
> and linked issue has an example of how to do that. 
>
> Longer term we may modify the display so parallels not in a stage 
> automatically look like they are defined within a stage for visualization 
> purposes.
>
> On Thursday, December 15, 2016 at 8:31:36 AM UTC+11, Jesse Glick wrote:
>>
>> On Wed, Dec 14, 2016 at 4:19 PM, Alan Wu  wrote: 
>> > As far as I know, stages in 
>> > parallel was implemented not long ago and perjaps Blue Ocean has not 
>> caught 
>> > up with that update yet? 
>>
>> B.O. devs can correct me but last I checked it will only display 
>> top-level `stage`s and a single level of `parallel` beneath those, not 
>> arbitrary nesting structures. 
>>
>

-- 
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/712806d7-a5ec-4bb8-b125-14a0f1c97b30%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean]Stages in parallel not being displayed correctly

[James Dumay]

That is correct. There is an open bug report tracking this issue 
 - please watch and 
vote for it. The workaround is to surround your parallel with a stage block 
and linked issue has an example of how to do that. 

Longer term we may modify the display so parallels not in a stage 
automatically look like they are defined within a stage for visualization 
purposes.

On Thursday, December 15, 2016 at 8:31:36 AM UTC+11, Jesse Glick wrote:
>
> On Wed, Dec 14, 2016 at 4:19 PM, Alan Wu  > wrote: 
> > As far as I know, stages in 
> > parallel was implemented not long ago and perjaps Blue Ocean has not 
> caught 
> > up with that update yet? 
>
> B.O. devs can correct me but last I checked it will only display 
> top-level `stage`s and a single level of `parallel` beneath those, not 
> arbitrary nesting structures. 
>

-- 
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/aecd1e46-b4c2-4c65-a5b8-bd5ab572e4ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[RFC] Stapler changes

[James Dumay]

Hi all,

We need to make some modifications to Stapler to fix a class of 
serialization issues which involve plugins and result in Blue Ocean pages 
not loading correctly. 

If a plugin’s Action fails to serialize it fails the serialization of the 
rest response. Just like the remote APIs, Blue Ocean returns serialized 
Actions for many of its responses. For Blue Ocean this is incredibly 
important as a failed REST call can cause the entire UI to fail and the 
blame is assigned to Blue Ocean rather than the plugin that threw the 
exception. There are thousands of plugins and 1000s of ways to make the UI 
fall over.

I've written a small document that summarize the changes and it would be 
great to get some feedback.

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

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/d4f1c02c-2966-4afc-ac7a-3b3f0030231f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[James Dumay]

A fix should be available in Blue Ocean beta 13 next week.

On Wednesday, November 30, 2016 at 5:58:17 PM UTC+11, James Dumay wrote:
>
> I've re-opened JENKINS-36907 
> <https://issues.jenkins-ci.org/browse/JENKINS-36907> and submitted a pull 
> request <https://github.com/jenkinsci/blueocean-plugin/pull/634> that 
> should fix this regardless of any errors in the translation. If all goes 
> well it should be in next weeks Blue Ocean beta.
>
> On Wednesday, November 30, 2016 at 4:09:33 AM UTC+11, Baptiste Mathus 
> wrote:
>>
>> This issue was fixed in 2.16 cf. 
>> https://github.com/jenkinsci/jenkins/commit/3956994c286941dab2da810c649269d637dc98d9
>>
>> So, if you're seeing something close or similar, please file an issue and 
>> use the users ML instead.
>>
>>
>> 2016-11-29 13:38 GMT+01:00 :
>>
>>> I'm using Jenkins 2.19.4 and still has this issue while on Spanish 
>>> language.
>>>
>>> When will this issue be fixed?
>>>
>>>
>>> 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 
>>>> <https://issues.jenkins-ci.org/browse/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 je

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

[James Dumay]

I've re-opened JENKINS-36907 
 and submitted a pull 
request  that 
should fix this regardless of any errors in the translation. If all goes 
well it should be in next weeks Blue Ocean beta.

On Wednesday, November 30, 2016 at 4:09:33 AM UTC+11, Baptiste Mathus wrote:
>
> This issue was fixed in 2.16 cf. 
> https://github.com/jenkinsci/jenkins/commit/3956994c286941dab2da810c649269d637dc98d9
>
> So, if you're seeing something close or similar, please file an issue and 
> use the users ML instead.
>
>
> 2016-11-29 13:38 GMT+01:00 >:
>
>> I'm using Jenkins 2.19.4 and still has this issue while on Spanish 
>> language.
>>
>> When will this issue be fixed?
>>
>>
>> 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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/b7a849ac-b33c-4725-8c78-c7f205eb653c%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/77f90507-1ace-417c-854a-3efe6224e049%40googlegroups.com.
For more options, visit https://grou

CLI install-plugin broken?

[James Dumay]

Hi there,

We had a report from a user trying to install blueocean via the CLI that 
the install-plugin command is broken. I've done some testing and it seems 
to be broken in 2.34 for any plugin install.

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

Is anyone aware of this issue?

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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d12ce39a-6d82-4526-bbcb-c39f4585873c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: BlueOcean with robotframework test

[James Dumay]

That is interesting - could you file a bug in JIRA and attach some 
roboframework report examples? I'd like to simulate how the plugin picks up the 
xml files and stores them. There may be something quick we can do to get them 
to display

Don't forget to set the component for blueocean-plugin and roboframework-plugin 
so we can easily find it :)

http://issues.jenkins-ci.org

-- 
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/6aeada8a-d387-490d-9065-300805b2fd09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

BlueOcean with robotframework test

[James Dumay]

I haven't tested it myself but it appears that the Robotframework Jenkins 
plugin uses the JUnit plugin under the hood. so you should be able to get tests 
to display in Blue Ocean using it.

https://wiki.jenkins-ci.org/display/JENKINS/Robot+Framework+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/29c112b6-9032-4116-906c-042d81784564%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Listener for plugin install/removal/etc?

[James Dumay]

Right. We just needed to invalidate a cache that wouldn't survive restart
anyway. Stephen pointed us to hudson.ExtensionListListener which seems to
do the trick in this case (we need to invalidate when the list of
extensions changes).

On Thu, Nov 10, 2016 at 9:57 AM Daniel Beck  wrote:

>
> > On 09.11.2016, at 23:39, James Dumay  wrote:
> >
> > From my understanding removing from the FS would break a bunch of things
> right?
>
> No. Shut down Jenkins, remove a plugin .jpi file, or create a plugin
> .jpi.disabled file, and start Jenkins again. Not really listenable (unless
> you want Jenkins to record plugins and compare, sending delayed
> notifications, but that's something your plugin can easily do itself).
>
> --
> 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/UiLSslvVOBA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/C556A548-BBAA-4431-AE4E-AC7D5924BCA7%40beckweb.net
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
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/CAErbOvTapc6_AUng9a9%2BFhyYnCiWroLGHfUQj9gBF7Ham4KELw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Listener for plugin install/removal/etc?

[James Dumay]

>From my understanding removing from the FS would break a bunch of things 
right?

On Thursday, November 10, 2016 at 9:20:50 AM UTC+11, Daniel Beck wrote:
>
>
> > On 09.11.2016, at 22:29, Stephen Connolly  > wrote: 
> > 
> > there is currently no removal or update without a restart 
>
> And those events could not be trusted anyway, as users could just disable 
> or remove plugins manually by modifying the file system. 
>
>

-- 
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/a3b4120f-5ce4-483e-b1c8-cef1d5707487%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Listener for plugin install/removal/etc?

[James Dumay]

Do you know what it is called?

On Thursday, November 10, 2016 at 8:29:33 AM UTC+11, Stephen Connolly wrote:
>
> There is a listener for addition, there is currently no removal or update 
> without a restart 
>
> On Wednesday 9 November 2016, James Dumay  > wrote:
>
>> Hi all,
>>
>> Is there a Listener we could use to listen for install/remove/etc events 
>> from the PluginManager? We have a cache that we'd like to invalidate 
>> <https://issues.jenkins-ci.org/browse/JENKINS-39609> every time the 
>> state of the plugin system changes.
>>
>> Thanks,
>>
>> -- 
>> 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/CAErbOvQPuaRz1hmnuW%2BO%3DOzKY4DGeDC%3DSEoV1doP377CtQvRhw%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAErbOvQPuaRz1hmnuW%2BO%3DOzKY4DGeDC%3DSEoV1doP377CtQvRhw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Sent from my phone
>

-- 
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/6e4d9bcd-7988-4888-8ad9-3c0289d5d58a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Listener for plugin install/removal/etc?

[James Dumay]

Hi all,

Is there a Listener we could use to listen for install/remove/etc events
from the PluginManager? We have a cache that we'd like to invalidate
<https://issues.jenkins-ci.org/browse/JENKINS-39609> every time the state
of the plugin system changes.

Thanks,

-- 
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/CAErbOvQPuaRz1hmnuW%2BO%3DOzKY4DGeDC%3DSEoV1doP377CtQvRhw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Adopting the favorite plugin

[James Dumay]

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
> <https://wiki.jenkins-ci.org/display/JENKINS/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
> <https://jenkins.io/images/post-images/blueocean/personalized-dashboard.png> 
> and
> we are planning new extensions to this plugin
> <https://github.com/i386/blueocean-autofavorite>.
>
> 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/CAErbOvR5d4Fvig72J8A4%2BDes6mNWzGJaheTuYx8RahLXDq5q4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Adopting the favorite plugin

[James Dumay]

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

-- 
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/9bfeb562-c37b-4475-affb-2efb018cb299%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Someone to take over GHPRB

[James Dumay]

I know this plugin is extensively in use for ci.swift.org (Yeah, Apple's 
Swift Language team use Jenkins!) and they are running into some issues (
https://github.com/janinko/ghprb/issues/150 and 
https://github.com/janinko/ghprb/issues/284 specifically) so it would be 
great to see someone pick up maintainership.

On Sunday, September 25, 2016 at 5:59:45 AM UTC+10, Ben Patterson wrote:
>
> Och I should have mentioned my github id: benpatterson
>
> sent via Android
>
> On Sep 24, 2016 12:56 PM, "Ben Patterson"  > wrote:
>
>> Hi Daniel and David - 
>>
>> I can help out with this plugin if you'd like someone to guide home the 
>> pull requests and such. I have some cycles.
>>
>> Care to give me contributor access?
>>
>> Ben
>>
>> On Friday, September 16, 2016 at 9:01:47 PM UTC-4, Daniel Beck wrote:
>>>
>>> I marked the plugin as 'up for adoption' in the wiki: 
>>>
>>> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin
>>>  
>>>
>>> > On 16.09.2016, at 13:25, David Tanner  wrote: 
>>> > 
>>> > Hello, 
>>> > 
>>> > I no longer have the time to dedicate to code reviews for this 
>>> project, can someone else take over?   
>>> > https://github.com/jenkinsci/ghprb-plugin 
>>> > 
>>> > Thanks, 
>>> > David Tanner 
>>> > 
>>> > -- 
>>> > 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/a62ad508-242a-4b0e-90e7-d18519e8bdce%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/iHBzu1sBOmI/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/32e9c050-4bf3-49a7-8fed-29391a784b9e%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/fa7d8796-3193-4f6a-a48f-f75d4a769c03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Slow page-loading

[James Dumay]

Thanks for sending the info through Andreas. You can keep up to date on its 
status by watching this ticket 
https://issues.jenkins-ci.org/browse/JENKINS-38079 

On Thursday, September 8, 2016 at 5:24:36 PM UTC+10, James Dumay wrote:
>
> Or every second by the looks of that timing info.
>
> On Thursday, September 8, 2016 at 5:23:59 PM UTC+10, James Dumay wrote:
>>
>> Actually, if you can repeat that thread dump command every 5 seconds 
>> starting from a few moments *before you request the dashboard and after* 
>> that 
>> would give us a better trace.
>>
>> On Thursday, September 8, 2016 at 5:22:35 PM UTC+10, James Dumay wrote:
>>>
>>> Hi Andreas,
>>>
>>> Hmm, that doesn't sound great. Could you try accessing Blue Ocean 
>>> without the proxy and see if it exhibits the same behaviour?
>>>
>>> If its not your proxy we will need a few things to help diagnose this:
>>>
>>>- Thread dump - "kill -3 $JENKINS_PID" should do the trick and spit 
>>>the thread dump into your Jenkins log
>>>- Generate a HAR file of the request for the dashboard from start to 
>>>finish. There's a good guide for doing this 
>>>
>>> <https://confluence.atlassian.com/kb/generating-har-files-and-analysing-web-requests-720420612.html>
>>>  
>>>in your browser of choice.
>>>- Info about your instance (number of Jobs, version of Jenkins)
>>>- Browser versions
>>>
>>> If you can send me the Jenkins server log and the HAR file (
>>> jdu...@cloudbees.com) I can get one of the CloudBees engineers to take 
>>> a look tomorrow.
>>>
>>> Regardless its to see you so enthusiastically trying Blue Ocean :)
>>>
>>> Thanks,
>>> James
>>>
>>> On Thursday, September 8, 2016 at 4:03:24 PM UTC+10, midn wrote:
>>>>
>>>> Hello!
>>>>
>>>> I'm using latest BlueOcean from *master* branch, currently updating on 
>>>> daily basis.
>>>> I have a strange problem, most of the pages are loading vry slowly 
>>>> compared to https://ci.blueocean.io/blue ( I cannot access it now 
>>>> sadly for some reason. )
>>>> I see no errors/issues regarding why it could be so slow in Jenkins 
>>>> logs or Nginx logs.
>>>>
>>>> I'm running Jenkins 2.7.2 on Docker on a 16gb mem, 4cpu instance.
>>>> Currently the only Pipeline project i have is Multibranch with around 
>>>> ~10 active branches. Project is set to keep only 10 builds for each branch.
>>>>
>>>> Slow examples:
>>>> 1. Main dashboard - All projects to load takes about ~3 seconds, total 
>>>> around ~20 projects.
>>>> *Link* - 
>>>> https://JENKINSHOST/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26
>>>> *Time* - 2.10s
>>>>
>>>> *Link *- https://JENKINSHOST/sse-gateway/configure?batchId=1
>>>> *Time* - 5.18s
>>>>
>>>> 2. Open link to my only Multibranch Pipeline Project, takes about 
>>>> ~10sec to load activity, even though activity shows some file was loaded 
>>>> in 
>>>> ~3 seconds, another 7 seconds it was doing something else, network 
>>>> activity 
>>>> didnt show any new changes.
>>>> *Link* - 
>>>> https://JENKINSHOST/blue/rest/search/?q=type:pipeline;organization:jenkins;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26
>>>> *Time* - 2.24s
>>>>
>>>> 3. Open details of single build, take around ~10 seconds.
>>>> *Link* - 
>>>> https://JENKINSHOST/blue/rest/organizations/jenkins/pipelines/NAME/branches/feature%252FXX/runs/4/
>>>> *Time *- 10.87s
>>>>
>>>> Sometimes it seems like to caches some pages and then opening details 
>>>> becomes fast for some, for some it's still extremely slow.
>>>> If i compared to https://ci.blueocean.io/blue ( Which i cannot access 
>>>> now :grin: ), blueoceans page was instant on the clicks with much more 
>>>> Activity/Projects.
>>>>
>>>> Any ideas what could be wrong, maybe some Limits in NGINX or Jenkins 
>>>> since BlueOcean is doing quite a lot of requests?
>>>> Any help appreciated 
>>>>
>>>> Regards,
>>>> Andres
>>>>
>>>>
>>>>

-- 
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/4b5132cd-1341-455d-9c14-ba1f571898c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Slow page-loading

[James Dumay]

Or every second by the looks of that timing info.

On Thursday, September 8, 2016 at 5:23:59 PM UTC+10, James Dumay wrote:
>
> Actually, if you can repeat that thread dump command every 5 seconds 
> starting from a few moments *before you request the dashboard and after* that 
> would give us a better trace.
>
> On Thursday, September 8, 2016 at 5:22:35 PM UTC+10, James Dumay wrote:
>>
>> Hi Andreas,
>>
>> Hmm, that doesn't sound great. Could you try accessing Blue Ocean without 
>> the proxy and see if it exhibits the same behaviour?
>>
>> If its not your proxy we will need a few things to help diagnose this:
>>
>>- Thread dump - "kill -3 $JENKINS_PID" should do the trick and spit 
>>the thread dump into your Jenkins log
>>- Generate a HAR file of the request for the dashboard from start to 
>>finish. There's a good guide for doing this 
>>
>> <https://confluence.atlassian.com/kb/generating-har-files-and-analysing-web-requests-720420612.html>
>>  
>>in your browser of choice.
>>- Info about your instance (number of Jobs, version of Jenkins)
>>- Browser versions
>>
>> If you can send me the Jenkins server log and the HAR file (
>> jdu...@cloudbees.com) I can get one of the CloudBees engineers to take a 
>> look tomorrow.
>>
>> Regardless its to see you so enthusiastically trying Blue Ocean :)
>>
>> Thanks,
>> James
>>
>> On Thursday, September 8, 2016 at 4:03:24 PM UTC+10, midn wrote:
>>>
>>> Hello!
>>>
>>> I'm using latest BlueOcean from *master* branch, currently updating on 
>>> daily basis.
>>> I have a strange problem, most of the pages are loading vry slowly 
>>> compared to https://ci.blueocean.io/blue ( I cannot access it now sadly 
>>> for some reason. )
>>> I see no errors/issues regarding why it could be so slow in Jenkins logs 
>>> or Nginx logs.
>>>
>>> I'm running Jenkins 2.7.2 on Docker on a 16gb mem, 4cpu instance.
>>> Currently the only Pipeline project i have is Multibranch with around 
>>> ~10 active branches. Project is set to keep only 10 builds for each branch.
>>>
>>> Slow examples:
>>> 1. Main dashboard - All projects to load takes about ~3 seconds, total 
>>> around ~20 projects.
>>> *Link* - 
>>> https://JENKINSHOST/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26
>>> *Time* - 2.10s
>>>
>>> *Link *- https://JENKINSHOST/sse-gateway/configure?batchId=1
>>> *Time* - 5.18s
>>>
>>> 2. Open link to my only Multibranch Pipeline Project, takes about ~10sec 
>>> to load activity, even though activity shows some file was loaded in ~3 
>>> seconds, another 7 seconds it was doing something else, network activity 
>>> didnt show any new changes.
>>> *Link* - 
>>> https://JENKINSHOST/blue/rest/search/?q=type:pipeline;organization:jenkins;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26
>>> *Time* - 2.24s
>>>
>>> 3. Open details of single build, take around ~10 seconds.
>>> *Link* - 
>>> https://JENKINSHOST/blue/rest/organizations/jenkins/pipelines/NAME/branches/feature%252FXX/runs/4/
>>> *Time *- 10.87s
>>>
>>> Sometimes it seems like to caches some pages and then opening details 
>>> becomes fast for some, for some it's still extremely slow.
>>> If i compared to https://ci.blueocean.io/blue ( Which i cannot access 
>>> now :grin: ), blueoceans page was instant on the clicks with much more 
>>> Activity/Projects.
>>>
>>> Any ideas what could be wrong, maybe some Limits in NGINX or Jenkins 
>>> since BlueOcean is doing quite a lot of requests?
>>> Any help appreciated 
>>>
>>> Regards,
>>> Andres
>>>
>>>
>>>

-- 
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/af18ed21-359b-4663-9c52-01d300818382%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Slow page-loading

[James Dumay]

Actually, if you can repeat that thread dump command every 5 seconds 
starting from a few moments *before you request the dashboard and after* that 
would give us a better trace.

On Thursday, September 8, 2016 at 5:22:35 PM UTC+10, James Dumay wrote:
>
> Hi Andreas,
>
> Hmm, that doesn't sound great. Could you try accessing Blue Ocean without 
> the proxy and see if it exhibits the same behaviour?
>
> If its not your proxy we will need a few things to help diagnose this:
>
>- Thread dump - "kill -3 $JENKINS_PID" should do the trick and spit 
>the thread dump into your Jenkins log
>- Generate a HAR file of the request for the dashboard from start to 
>finish. There's a good guide for doing this 
>
> <https://confluence.atlassian.com/kb/generating-har-files-and-analysing-web-requests-720420612.html>
>  
>in your browser of choice.
>- Info about your instance (number of Jobs, version of Jenkins)
>- Browser versions
>
> If you can send me the Jenkins server log and the HAR file (
> jdu...@cloudbees.com) I can get one of the CloudBees engineers to take a 
> look tomorrow.
>
> Regardless its to see you so enthusiastically trying Blue Ocean :)
>
> Thanks,
> James
>
> On Thursday, September 8, 2016 at 4:03:24 PM UTC+10, midn wrote:
>>
>> Hello!
>>
>> I'm using latest BlueOcean from *master* branch, currently updating on 
>> daily basis.
>> I have a strange problem, most of the pages are loading vry slowly 
>> compared to https://ci.blueocean.io/blue ( I cannot access it now sadly 
>> for some reason. )
>> I see no errors/issues regarding why it could be so slow in Jenkins logs 
>> or Nginx logs.
>>
>> I'm running Jenkins 2.7.2 on Docker on a 16gb mem, 4cpu instance.
>> Currently the only Pipeline project i have is Multibranch with around ~10 
>> active branches. Project is set to keep only 10 builds for each branch.
>>
>> Slow examples:
>> 1. Main dashboard - All projects to load takes about ~3 seconds, total 
>> around ~20 projects.
>> *Link* - 
>> https://JENKINSHOST/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26
>> *Time* - 2.10s
>>
>> *Link *- https://JENKINSHOST/sse-gateway/configure?batchId=1
>> *Time* - 5.18s
>>
>> 2. Open link to my only Multibranch Pipeline Project, takes about ~10sec 
>> to load activity, even though activity shows some file was loaded in ~3 
>> seconds, another 7 seconds it was doing something else, network activity 
>> didnt show any new changes.
>> *Link* - 
>> https://JENKINSHOST/blue/rest/search/?q=type:pipeline;organization:jenkins;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26
>> *Time* - 2.24s
>>
>> 3. Open details of single build, take around ~10 seconds.
>> *Link* - 
>> https://JENKINSHOST/blue/rest/organizations/jenkins/pipelines/NAME/branches/feature%252FXX/runs/4/
>> *Time *- 10.87s
>>
>> Sometimes it seems like to caches some pages and then opening details 
>> becomes fast for some, for some it's still extremely slow.
>> If i compared to https://ci.blueocean.io/blue ( Which i cannot access 
>> now :grin: ), blueoceans page was instant on the clicks with much more 
>> Activity/Projects.
>>
>> Any ideas what could be wrong, maybe some Limits in NGINX or Jenkins 
>> since BlueOcean is doing quite a lot of requests?
>> Any help appreciated 
>>
>> Regards,
>> Andres
>>
>>
>>

-- 
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/a4dbd5d1-2c46-4717-8b59-514b6602be62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Slow page-loading

[James Dumay]

Hi Andreas,

Hmm, that doesn't sound great. Could you try accessing Blue Ocean without 
the proxy and see if it exhibits the same behaviour?

If its not your proxy we will need a few things to help diagnose this:

   - Thread dump - "kill -3 $JENKINS_PID" should do the trick and spit the 
   thread dump into your Jenkins log
   - Generate a HAR file of the request for the dashboard from start to 
   finish. There's a good guide for doing this 
   

 
   in your browser of choice.
   - Info about your instance (number of Jobs, version of Jenkins)
   - Browser versions

If you can send me the Jenkins server log and the HAR file 
(jdu...@cloudbees.com) I can get one of the CloudBees engineers to take a 
look tomorrow.

Regardless its to see you so enthusiastically trying Blue Ocean :)

Thanks,
James

On Thursday, September 8, 2016 at 4:03:24 PM UTC+10, midn wrote:
>
> Hello!
>
> I'm using latest BlueOcean from *master* branch, currently updating on 
> daily basis.
> I have a strange problem, most of the pages are loading vry slowly 
> compared to https://ci.blueocean.io/blue ( I cannot access it now sadly 
> for some reason. )
> I see no errors/issues regarding why it could be so slow in Jenkins logs 
> or Nginx logs.
>
> I'm running Jenkins 2.7.2 on Docker on a 16gb mem, 4cpu instance.
> Currently the only Pipeline project i have is Multibranch with around ~10 
> active branches. Project is set to keep only 10 builds for each branch.
>
> Slow examples:
> 1. Main dashboard - All projects to load takes about ~3 seconds, total 
> around ~20 projects.
> *Link* - 
> https://JENKINSHOST/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26
> *Time* - 2.10s
>
> *Link *- https://JENKINSHOST/sse-gateway/configure?batchId=1
> *Time* - 5.18s
>
> 2. Open link to my only Multibranch Pipeline Project, takes about ~10sec 
> to load activity, even though activity shows some file was loaded in ~3 
> seconds, another 7 seconds it was doing something else, network activity 
> didnt show any new changes.
> *Link* - 
> https://JENKINSHOST/blue/rest/search/?q=type:pipeline;organization:jenkins;excludedFromFlattening:jenkins.branch.MultiBranchProject,hudson.matrix.MatrixProject&filter=no-folders&start=0&limit=26
> *Time* - 2.24s
>
> 3. Open details of single build, take around ~10 seconds.
> *Link* - 
> https://JENKINSHOST/blue/rest/organizations/jenkins/pipelines/NAME/branches/feature%252FXX/runs/4/
> *Time *- 10.87s
>
> Sometimes it seems like to caches some pages and then opening details 
> becomes fast for some, for some it's still extremely slow.
> If i compared to https://ci.blueocean.io/blue ( Which i cannot access now 
> :grin: ), blueoceans page was instant on the clicks with much more 
> Activity/Projects.
>
> Any ideas what could be wrong, maybe some Limits in NGINX or Jenkins since 
> BlueOcean is doing quite a lot of requests?
> Any help appreciated 
>
> Regards,
> Andres
>
>
>

-- 
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/82092553-c28a-4946-8a73-694c7147671d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Interested in building your plugin on ci.jenkins.io?

[James Dumay]

Hi Tyler, 

I'd love for https://github.com/jenkinsci/display-url-api-plugin to be 
built on that server. There is a Jenkinsfile already in the repo.

Thanks,
James

On Tuesday, August 9, 2016 at 1:48:24 AM UTC+10, R Tyler Croy wrote:
>
> Howdy there, your friendly project infrastructure dude here. I'm hoping to 
> get 
> more accurate usage requirements for our eventual migration of 
> https://ci.jenkins.io, and the rest of our infra, to Azure [0]. If your 
> plugin 
> repository already has a `Jenkinsfile`, or you're interested in creating 
> one 
> for your plugin, I would love to have your plugin built on our existing 
> Jenkins-on-Jenkins. 
>
>
> We already have a couple plugins [1] being built on ci.jenkins.io, but I 
> need 
> more! 
>
>
> If you're interested in having your plugin built and/or helping out, 
> please 
> reply or ping me (rtyler) in the #jenkins-infra channel. 
>
>
>
> [0] https://jenkins.io/blog/2016/05/18/announcing-azure-partnership/ 
> [1] https://ci.jenkins.io/job/Plugins/ 
>
>
> - R. Tyler Croy 
>
> -- 
>  Code:  
>   Chatter:  
>
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F 
> -- 
>

-- 
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/d0d770c8-6ac2-4d56-a972-62e5d5f5392b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: mailer release?

[James Dumay]

Thanks mate :)

-- 
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/ba4e64ab-fbc9-4728-96e1-41c2ab286e38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Rewriting URLs for alternative UIs (e.g. Blue Ocean)

[James Dumay]

FWIW, this plugin has now been approved and mailer has been the first 
plugin to accept changes.

On Friday, August 26, 2016 at 9:43:49 AM UTC+10, James Dumay wrote:
>
> Hi all,
>
> I've written a new API plugin called display-url-api that provides an 
> extension point to rewrite alternate URLs for use in notifications. For 
> example, if you installed Blue Ocean and wanted the mailer links to point 
> to Blue Ocean URLs instead of Jenkins Classic, this would provide the 
> mechanism for the Blue Ocean team to do so.
>
> https://github.com/i386/display-url-api-plugin 
> https://issues.jenkins-ci.org/browse/HOSTING-179 
>
> I've also spent some time filing PRs that make many Jenkins notification 
> plugins use the API:
>
>- https://github.com/jenkinsci/mailer-plugin/pull/29
>- https://github.com/jenkinsci/hipchat-plugin/pull/82
>- https://github.com/jenkinsci/slack-plugin/pull/245
>- https://github.com/jenkinsci/instant-messaging-plugin/pull/15
>- https://github.com/jenkinsci/ircbot-plugin/pull/17
>- https://github.com/jenkinsci/jabber-plugin/pull/15
>
>
> Originally this change was done in Jenkins core but it was recommended 
> that it be pulled out into a separate plugin. However, Daniel Beck thought 
> this would be a good candidate for including in core so that Blue Ocean 
> could also override the URLs generated in the RSS feeds (currently part of 
> core).
>
> What would be the best approach here?
>
>
>

-- 
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/529dc6f9-a8fa-485d-8ffa-bbb263ead2da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: mailer release?

[James Dumay]

It would be also great if someone could volunteer to give it a quick test

On Thursday, September 1, 2016 at 1:32:37 PM UTC+10, James Dumay wrote:
>
> Hi all,
>
> How can I go about getting a new release of mailer? I recently added 
> support to it for the Display URL Provider API
>
> https://github.com/jenkinsci/mailer-plugin/pull/29 
>
> 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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0a745368-0e5d-40be-81d5-517618548f9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

mailer release?

[James Dumay]

Hi all,

How can I go about getting a new release of mailer? I recently added 
support to it for the Display URL Provider API

https://github.com/jenkinsci/mailer-plugin/pull/29 

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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6eaf06bf-88c7-40d6-a409-fcb68bdf3323%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Rewriting URLs for alternative UIs (e.g. Blue Ocean)

[James Dumay]

Sounds like we can keep it as its own plugin.

Could someone approve the hosting ticket?

On Friday, August 26, 2016 at 11:49:39 AM UTC+10, Jesse Glick wrote:
>
> On Thu, Aug 25, 2016 at 7:43 PM, James Dumay  > wrote: 
> > Daniel Beck thought this 
> > would be a good candidate for including in core so that Blue Ocean could 
> > also override the URLs generated in the RSS feeds (currently part of 
> core). 
>
> We should just fix the latter: 
> https://issues.jenkins-ci.org/browse/JENKINS-26468 
>

-- 
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/953c23b8-66d9-4baa-ae98-cc75ac62880c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Rewriting URLs for alternative UIs (e.g. Blue Ocean)

[James Dumay]

Sounds good to me - it can be extended to allow either a global or user 
preference pretty easily (PRs welcome!)

On Friday, August 26, 2016 at 4:04:23 PM UTC+10, ogondza wrote:
>
> I do not know much about blue ocean or other alternative UIs but should 
> it not be an attribute of user config what UI flavor user wants to use? 
> Putting the information into notification urls seems to not allow that. 
>
> -- 
> oliver 
>

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

Rewriting URLs for alternative UIs (e.g. Blue Ocean)

[James Dumay]

Hi all,

I've written a new API plugin called display-url-api that provides an
extension point to rewrite alternate URLs for use in notifications. For
example, if you installed Blue Ocean and wanted the mailer links to point
to Blue Ocean URLs instead of Jenkins Classic, this would provide the
mechanism for the Blue Ocean team to do so.

https://github.com/i386/display-url-api-plugin
https://issues.jenkins-ci.org/browse/HOSTING-179

I've also spent some time filing PRs that make many Jenkins notification
plugins use the API:

   - https://github.com/jenkinsci/mailer-plugin/pull/29
   - https://github.com/jenkinsci/hipchat-plugin/pull/82
   - https://github.com/jenkinsci/slack-plugin/pull/245
   - https://github.com/jenkinsci/instant-messaging-plugin/pull/15
   - https://github.com/jenkinsci/ircbot-plugin/pull/17
   - https://github.com/jenkinsci/jabber-plugin/pull/15


Originally this change was done in Jenkins core but it was recommended that
it be pulled out into a separate plugin. However, Daniel Beck thought this
would be a good candidate for including in core so that Blue Ocean could
also override the URLs generated in the RSS feeds (currently part of core).

What would be the best approach here?

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

Re: Jenkins UX

[James Dumay]

Have you seen Blue Ocean? That's where most of the UX effort is happening right 
now. 

https://jenkins.io/blog/2016/05/26/introducing-blue-ocean/

-- 
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/b4420d9c-8b94-413a-9ba2-79e5fdf3fb1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Experiment] Reviewers Team

[James Dumay]

All of the blueocean-plugin PRs mention the reviewers team... so If you are 
looking to get involved in Blue Ocean reviewing is a great place to start!

On Wednesday, August 10, 2016 at 4:22:56 AM UTC+10, Baptiste Mathus wrote:
>
> Small bump: reminder this list 
>
> https://github.com/orgs/jenkinsci/teams/code-reviewers
>
> is open to *anyone* willing to review Jenkins code in general (core or 
> plugins). Either you want to grow your skills, or help in general, or both, 
> this is one good place.
>
> Note that being part of that team does *not* require you to review 
> anything where you get asked to.
>
> Le 6 janv. 2016 9:42 PM, "Baptiste Mathus" > 
> a écrit :
>
>> Hi everyone,
>>
>> If you've already tried to get feedback on a PR you were working on, or 
>> are interested in helping & learning things by reviewing other's code, read 
>> on.
>>
>> Daniel just helped set up a Jenkinsci GitHub organization new sub-team 
>> called '*code-reviewers*' to define a group of people willing to try and 
>> review code at the request of others.
>>
>>- If you want to be part of it, click on the right button on that 
>>page: 
>>   https://github.com/orgs/jenkinsci/teams/code-reviewers
>>
>>- If you want to notify that team (and get reviewed) in a comment, 
>>use the *@jenkinsci/code-reviewers* form (should autocomplete).
>>
>> Here it is. This is something we wanted to try and still very early in 
>> the process, don't hesitate to tell us what you think of it here or on IRC.
>>
>> Hope you find it useful!
>>
>> Cheers
>>
>> -- Baptiste
>>
>

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

Re: Accessibility- 508 Compliance

[James Dumay]

Hi Norman,

Wow that would be incredible! We run a development version of Blue Ocean 
at https://ci.blueocean.io/blue/pipelines and you can file reports 
at https://issues.jenkins-ci.org/ in the blueocean-plugin component.

Is there any way I can help you get started?

On Tuesday, August 2, 2016 at 4:06:15 AM UTC+10, Norman Robinson wrote:
>
> I can assist with the test results we are finding if someone on the dev 
> team can help guide me to the best place for the bug reporting. Note we 
> cover more than screen reader access; we utilize the Section 508 Compliance 
> Test Process for Applications ( www.dhs.gov/compliance-test-processes )
>
> If you have a new UI we can get at, we can try that too.
>
> On Wednesday, July 13, 2016 at 4:13:46 AM UTC-4, James Dumay wrote:
>>
>> This is something I am very interested in having for the new Blue Ocean 
>> UI.
>>
>> Is that something either of you would be interested helping us with?
>>
>> On Tuesday, July 12, 2016 at 12:42:20 AM UTC+10, Juliano Cesar wrote:
>>>
>>> i am a  blindpeople, I am   brazilian user  jenkins. Jenkins is a 
>>>  accessible tool, using a  screen  reader, jaws and  nvda. 
>>>
>>>
>>>
>>> 2016-07-11 11:18 GMT-03:00, ioporto : 
>>> > Has there been any efforts thus far to make Jenkins (any version) 508 
>>> > compliant? Or to create an interface specifically for users with 
>>> > disabilities? I know CloudBees has VPAT 508 Compliance documentation, 
>>> but 
>>> > was curious to know if similar efforts have been done for the 
>>> open-sourced 
>>> > version. 
>>> > 
>>> > -- 
>>> > 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/08ca8662-df53-45ee-b8d1-7ba523464711%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/7328908b-2b10-4e45-b777-eb004279e681%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[James Dumay]

Hi Javier,

Hmm, certainly sounds like something is up. How did you install Blue Ocean? 
If you built it from source could you try to install it from the experimental 
update center  and 
try again? 

We are performing weekly binary releases on the path to the beta release 
and you may have a snapshot where some key things (such as path encoding) 
was not working correctly.

Sorry for not responding sooner as I've been traveling for work.

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/42213fb6-7543-422a-84cc-b87892956ea4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessibility- 508 Compliance

[James Dumay]

This is something I am very interested in having for the new Blue Ocean UI.

Is that something either of you would be interested helping us with?

On Tuesday, July 12, 2016 at 12:42:20 AM UTC+10, Juliano Cesar wrote:
>
> i am a  blindpeople, I am   brazilian user  jenkins. Jenkins is a 
>  accessible tool, using a  screen  reader, jaws and  nvda. 
>
>
>
> 2016-07-11 11:18 GMT-03:00, ioporto >: 
> > Has there been any efforts thus far to make Jenkins (any version) 508 
> > compliant? Or to create an interface specifically for users with 
> > disabilities? I know CloudBees has VPAT 508 Compliance documentation, 
> but 
> > was curious to know if similar efforts have been done for the 
> open-sourced 
> > version. 
> > 
> > -- 
> > 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/08ca8662-df53-45ee-b8d1-7ba523464711%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/63675075-1cd1-43f0-a929-02548b4cc77f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[James Dumay]

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 <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"  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://*
>>>>>>>>>

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

[James Dumay]

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&utm_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 
> :
>
>> 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 center, as 
>>> installing by hand is quite hard to do because of the dependency 
>>> tree you 
>>> handle to manually handle right.
>>>
>>> If hacking on it is indeed what you want, then keep asking 
>>> questions ;-)
>>>
>>> Cheers
>>>
>>>
>>> 2016-07-08 13:40 GMT+00:00 Maelig Gohin <
>>> mgo...@arca-computing.fr>:
>>>
 I built it from the sources from github's project.

 I'm trying right now with the 
 release blueocean-parent-1.0-alpha-2. Do I have to cancel the 
 build ? 
 (25min to built first time :p )

 Le vendredi 8 juillet 2016 15:37:54 UTC+2, Baptiste Mathus a 
 écrit :
>
> Hi,
> if you built it from source, you're on the right list, if not, 
> then the users list would have been better.
>
> Which version do you use? By chance, would you be using 
> https://hub.docker.com/r/jenkinsci/blueocean/ ? If so, this 
> is a known issue, long time fixed but this image is outdated.
>
> Cheers
>
> 2016-07-08 13:27 GMT+00:00 Maelig Gohin <
> mgo...@arca-computing.fr>:
>
>> Hi,
>>
>> just installed the last version of Blue Ocean, successfully 
>> built it, run it, configure Jenkins, then go to blue ocean 
>> dashboard.
>>
>> When I click on "new pipeline" I'm getting : 
>>
>> 404 Not Found
>>
>> S

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

[James Dumay]

Uli we used this status to great effect on our JIRA before we moved the 
project into OSS - so I believe we will be happy to have it back :)

If it causes any detriment to other project members we can re-evaluate it 
again.

On Friday, July 8, 2016 at 7:51:39 PM UTC+10, Ullrich Hafner wrote:
>
>
> Am 08.07.2016 um 02:59 schrieb James Dumay  >:
>
> @daniel - yes, looks like an error.
>
>
> Any major objections?
>
>
> No, I think it is no big difference for the non-blue-ocean developers.
>
> (But I think you should check on your own in a couple of weeks if the new 
> state really helps you in your development process. From a lot of other 
> projects I have the experience that such states (that duplicate work) will 
> not be used with the same enthusiasm after a while)
>
>
> On Friday, July 8, 2016 at 7:01:47 AM UTC+10, Daniel Beck wrote:
>>
>>
>> > On 07.07.2016, at 21:57, R. Tyler Croy  wrote: 
>> > 
>> ><http://imgur.com/a/dZhGc> 
>>
>> Is one of the 'Start Review' supposed to be 'Stop Review'? 
>>
> -- 
> 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/70e4b2c2-795e-45c3-9806-8e6dbe33923b%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/70e4b2c2-795e-45c3-9806-8e6dbe33923b%40googlegroups.com?utm_medium=email&utm_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/21e110f0-8ed9-4b2a-b965-b56a436f8039%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[James Dumay]

@daniel - yes, looks like an error.


Any major objections?


On Friday, July 8, 2016 at 7:01:47 AM UTC+10, Daniel Beck wrote:
>
>
> > On 07.07.2016, at 21:57, R. Tyler Croy  > wrote: 
> > 
> > 
>
> Is one of the 'Start Review' supposed to be 'Stop Review'? 
>

-- 
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/70e4b2c2-795e-45c3-9806-8e6dbe33923b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[James Dumay]

You would just get an additional optional "In Review" transition. 
Everything else would be the same.

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/90404d4d-4bb3-4b6e-a629-50a2c00654ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Add an "In Review" state to JIRA?

[James Dumay]

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-dev+unsubscr...@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.

Re: [BlueOcean] Roadmap/Issues for contribution

[James Dumay]

This pair would also be a really good one as it spans both Jenkins and Blue 
Ocean

JENKINS-35868 <https://issues.jenkins-ci.org/browse/JENKINS-35868>
JENKINS-35890 <https://issues.jenkins-ci.org/browse/JENKINS-35890>


On Tuesday, June 21, 2016 at 12:21:19 PM UTC+10, Michael Neale wrote:
>
> 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/758ac8e8-c425-48b3-bdce-2fa02227268e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[BlueOcean] Roadmap/Issues for contribution

[James Dumay]

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/f966c534-2a5a-46b2-9956-747a63771fe7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[BlueOcean] Roadmap/Issues for contribution

[James Dumay]

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/bd7c83d7-c312-4126-bfea-7bf7afe38f5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] - blueocean ui not available

[James Dumay]

Best watch the blog and mailing lists - we will be announcing the availability 
of the plugin in the experimental update center in those location

-- 
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/f1bb0270-b886-4a5a-a83c-2b1ed2288293%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [blueocean-plugin] No pipelines found

[James Dumay]

Great to hear that you found a resolution. Restart has tripped me up a few 
times 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/8144563e-b48b-4575-a4ec-800e731965af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] - blueocean ui not available

[James Dumay]

FYI we are going to be publishing Blue Ocean to the experimental update 
center so you don't have to build it yourself. We will be publishing daily 
and it should be available in a day or two :)

On Thursday, June 16, 2016 at 5:54:52 AM UTC+9, Michael Madden wrote:
>
> That seems like the issue I was running into.  I was in the top level 
> *blueocean-plugin 
> *directory.
>
> On Wednesday, June 15, 2016 at 3:38:21 PM UTC-5, Alexandru Somai wrote:
>>
>> Hello Michael,
>>
>> Let's assume that you've cloned your project in /home/workspace.
>>
>> So the steps are like this:
>> /home/workspace/*blueocean-plugin*: *mvn clean install*
>> Afterwards, you must *switch *to the blueocean-plugin folder. This is 
>> *another 
>> *folder located within the project root directory. In this folder you 
>> must run mvn hpi:run:
>> /home/workspace/*blueocean-plugin/blueocean-plugin*: *mvn hpi:run*
>>
>> I hope that I was clear.
>>
>> Regards,
>> Alex
>>
>> On Wednesday, June 15, 2016 at 11:25:09 PM UTC+3, Michael Madden wrote:
>>>
>>> I've been working through the directions to setup / test the latest 
>>> version of jenkins. 
>>>
>>> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/ 
>>> https://github.com/jenkinsci/blueocean-plugin 
>>>
>>> Supposedly you can go to the following URL after running through all the 
>>> setup to use the new UI: 
>>>
>>> http://localhost:8080/jenkins/blue 
>>>
>>> However this is not working.  The more standard UI still works at: 
>>>
>>> http://localhost:8080/jenkins/ 
>>>
>>> Here is the error I get when accessing the blue URL:
>>>
>>> 404 Not Found
>>>
>>> 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@3d61f0ce.getDynamic("blue",...)==null. Back 
>>> tracking.
>>> -> 
>>> evaluate(((StaplerFallback)).getStaplerFallback(),"/blue")
>>> -> evaluate( 
>>> :hudson.model.AllView,"/blue")
>>> -> 
>>> evaluate(.getDynamic("blue",...),"")
>>> 
>>> hudson.model.AllView@74fb8a51[view/All/].getDynamic("blue",...)==null. Back 
>>> tracking.-> No matching rule was found on 
>>>  for "/blue"
>>>
>>>  has the following URL 
>>> mappings, in the order of preference:
>>>
>>>1. hudson.model.AllView.doCreateItem(...) for url=/createItem/...
>>>2. hudson.model.View.doConfigSubmit(...) for url=/configSubmit/...
>>>3. hudson.model.View.doConfigDotXml(...) for url=/config.xml/...
>>>4. hudson.model.View.doItemCategories(...) for 
>>>url=/itemCategories/...
>>>5. hudson.model.View.doRssLatest(...) for url=/rssLatest/...
>>>6. hudson.model.View.doSubmitDescription(...) for 
>>>url=/submitDescription/...
>>>7. hudson.model.View.doDoDelete(...) for url=/doDelete/...
>>>8. hudson.model.View.doRssAll(...) for url=/rssAll/...
>>>9. hudson.model.View.doRssFailed(...) for url=/rssFailed/...
>>>10. hudson.model.View.doCheckJobName(...) for url=/checkJobName/...
>>>11. hudson.model.View.doChildrenContextMenu(...) for 
>>>url=/childrenContextMenu/...
>>>12. TOKEN.groovy for url=/TOKEN
>>>13. VIEW.jelly for url=/VIEW
>>>14. hudson.model.View.LIST for url=/LIST/...
>>>15. hudson.model.View.SORTER for url=/SORTER/...
>>>16. hudson.model.View.PERMISSIONS for url=/PERMISSIONS/...
>>>17. hudson.model.View.CREATE for url=/CREATE/...
>>>18. hudson.model.View.DELETE for url=/DELETE/...
>>>19. hudson.model.View.CONFIGURE for url=/CONFIGURE/...
>>>20. hudson.model.View.READ for url=/READ/...
>>>21. hudson.model.View.NEW_PRONOUN for url=/NEW_PRONOUN/...
>>>22. hudson.model.Saveable.NOOP for url=/NOOP/...
>>>23. hudson.model.View.getItemCreatePermission() for 
>>>url=/itemCreatePermission/...
>>>24. hudson.model.View.getUrl() for url=/url/...
>>>25. hudson.model.View.getOwner() for url=/owner/...
>>>26. hudson.model.View.getAllItems() for url=/allItems/...
>>>27. hudson.model.View.getAllProperties() for url=/allProperties/...
>>>28. hudson.model.AbstractModelObject.getSearch() for url=/search/...
>>>29. hudson.model.View.getApplicablePropertyDescriptors() for 
>>>url=/applicablePropertyDescriptors/...
>>>30. hudson.model.View.getOwnerPrimaryView() for 
>>>url=/ownerPrimaryView/...
>>>31. hudson.model.View.getColumns() for url=/columns/...
>>>32. hudson.model.View.getDisplayName() for url=/displayName/...
>>>33. hudson.model.View.getNewPronoun() for url=/newPronoun/...
>>>34. java.lang.Object.getClass() for url=/class/...
>>>35. hudson.model.View.getWidgets() for url=/widgets/...
>>>36. hudson.model.View.getIndenter() for url=/indenter/...
>>>37. hudson.model.View.getAbsoluteUrl() for url=/absoluteUrl/...
>>>38. hudson.model.View.getBuilds() for url=/builds/...
>>

Re: [blue-ocean] No Branch/Pull Requests Displayed

[James Dumay]

Thanks for filing the bug report. You will need to be using a multi-branch 
pipeline to make use of the branches and pull requests in Blue Ocean. 
See https://jenkins.io/doc/book/pipeline-as-code/

On Thursday, June 16, 2016 at 4:28:39 AM UTC+9, Ian Ceicys wrote:
>
> I have blue-ocean up and running successfully. 
>
> But I am not seeing any of the associated branches or pull requests in the 
> UI. What do I need to do to configure these sections?
>
> Video with Repo steps: https://www.youtube.com/watch?v=qt6yRD_7CwU
>
>

-- 
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/aa743974-d6a2-4c5c-bc05-c6241765e812%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

[James Dumay]

Running pipelines hasn't been implemented yet but someone (Ivan) is working 
on it :)

It was waiting on some new JDL and rest component work but thats been done. 
See JENKINS-35813 

On Tuesday, June 14, 2016 at 8:49:02 PM UTC+9, fkp...@gmail.com wrote:
>
> Thanks! that worked. although i still can't simply press run on my 
> pipeline in order to run  - and i have to go to the old interface to do it.
> I'm having some kind of exception on symbolic link - could that be the 
> issue?
>
> On Tuesday, June 14, 2016 at 10:28:40 AM UTC+3, Tom Fennelly wrote:
>>
>> As said earlier  you will have a job if you are not running via 
>> hpi:run. You will need to gather and install more than just the blueocean 
>> plugins.
>>
>> You could use "mvn hpi:assemble-dependencies" to pull together all of 
>> the plugins you need. You'd need to run this inside blueocean-plugin/
>> blueocean-plugin.
>>
>> On 14 June 2016 at 14:57,  wrote:
>>
>>> Very partly by installing HPI's manually - but only some of the 
>>> functionalities worked (but without any errors)
>>>
>>>
>>> On Tuesday, June 14, 2016 at 8:14:44 AM UTC+3, Michael Neale wrote:

 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 a topic in the 
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/jenkinsci-dev/1A82YO-Ta2w/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/d05496c8-f66b-42e1-acb7-42790dbddf71%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/ec36d3fc-eba3-4d63-b15a-aa5b2c43c762%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Test reporting UI

[James Dumay]

Gotcha. You're not the first to mention a Gerrit centric workflow. Are you 
using any Gerrit plugins for Jenkins?

On Wednesday, June 1, 2016 at 11:30:35 AM UTC+10, Robert Collins wrote:
>
> On 1 June 2016 at 13:23, James Dumay > 
> wrote: 
> > Individual freestyle jobs will show up as different jobs in Blue Ocean 
> with 
> > their own test tab on the result and there are no plans to aggregate 
> > multiple freestyle jobs as Pipelines. 
> > 
> > Have you investigated using Pipeline? 
>
> I don't know :) - OpenStack's infra team encountered scaling issues 
> with Jenkins which led to deploying a cluster of Jenkins in a 
> federated setup, and most/all of the reporting is done through adding 
> comments to the code review in Gerrit, since Jenkins is treated as a 
> helper service essentially - many of the OpenStack contributors would 
> never even look at Jenkin's UI. 
>
> -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/3c47023c-6c4b-4f24-a3f2-9c957f724ae2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Test reporting UI

[James Dumay]

Individual freestyle jobs will show up as different jobs in Blue Ocean with 
their own test tab on the result and there are no plans to aggregate 
multiple freestyle jobs as Pipelines.

Have you investigated using Pipeline?

On Tuesday, May 31, 2016 at 11:13:29 AM UTC+10, Robert Collins wrote:
>
> On 31 May 2016 at 08:39, James Dumay > 
> wrote: 
> > Nice to see you, Rob :) 
>
> Likewise :) 
>
> > Thats a great use case. You only see a single one of these screens per 
> FreeStyle job however if you are using Jenkins Pipeline we could group it 
> by parallel node. How do you stitch together your pipeline? 
>
> Its a fairly massive Jenkins Job Builder setup. 
>
> http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs
>  
>
> -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/3ced9f24-1c08-43ab-9879-adcd3f840b2d%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

[James Dumay]

I think Tom is going to remove the symlink Magic soon.

-- 
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/5a2a5609-7811-4d9f-a1e3-f7703678125c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Jenkins WebUI

[James Dumay]

That's some awesome work! 😎

-- 
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/03ebc80d-535b-4b63-ac4f-07bb5615423d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Test reporting UI

[James Dumay]

Nice to see you, Rob :) 

Thats a great use case. You only see a single one of these screens per 
FreeStyle job however if you are using Jenkins Pipeline we could group it by 
parallel node. How do you stitch together your pipeline?

-- 
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/378a8115-92c8-4765-aada-77a5a58b714c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Blue Ocean] Test reporting UI

[James Dumay]

Hi all,

I just wanted to share some very early mockups of what the test reporting 
interface could look like in Blue Ocean. I believe it would be great if we 
had a standard interface for all test report types but plugin developers 
would be free to add their own custom UI via extension points. 

Very keen to get your feedback and particularly from those involved in test 
reporting plugins.

https://invis.io/6M7GY7Q8T 
https://invis.io/6H7GY6EQF 

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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a578bed7-580f-43f5-84af-c87100aa06f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] New UX project for jenkins

[James Dumay]

 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
>> <https://en.wikipedia.org/wiki/Design_language>). One thing front end
>> developers have found useful when building components is storybook
>> <https://voice.kadira.io/introducing-react-storybook-ec27f28de1e2>.
>>
>>
>>
>>
>> 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
>> <https://docs.google.com/presentation/d/1dbaYTIGjGT9xX1JnWnaqjMumq94M9nGwljfMQaVtUFc/edit?usp=sharing>
>> is a presentation on front end development with blue ocean for those
>> interested in looking a bit deeper.
>>
>> One again, the section on the blog post is worth reading, especially for
>> developers
>> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/#jenkins-design-language.
>> And the source code (for now, until migrated to jenkinsci org):
>> https://github.com/cloudbees/blueocean
>>
>> See you around #jenkins-ux (freenode) hopefully!
>>
>> Cheers. Mic.
>>
>> --
> 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/IIRW6MAfJnc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/4f72051b-a585-4da8-9636-a289bfa72cb6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/4f72051b-a585-4da8-9636-a289bfa72cb6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
James Dumay
Product Manager
CloudBees, Inc.
Skype: ap_myskype 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/CAErbOvRRLfi20-xE-rxN6M%3DGknB3DrcQ6EDCTSkGWuxxU_jPag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] - Jenkins Web Interface Improvements and Update Center 2.0

[James Dumay]

Great proposal Arshad. I'd echo Oleg's feedback in narrowing down the scope 
a bit. One thing that might hamper the delivery of this proposal is plugin 
compatibility - Gus Reiber and Tom Fennelly have done a lot of thinking 
about this and would be a good people to get advice from.


On Wednesday, March 9, 2016 at 10:13:09 AM UTC+11, Arshad Khan wrote:
>
>
>  Hello everyone,
>
> My name is Arshad Khan, I am a second year student 
> pursuing B.Tech. in Information Technology from Bharati Vidyapeeth College 
> of Engineering, New Delhi. I am currently doing internship as an Front-end 
> and UX developer at Broomberg Cleaning Services,New Delhi. I have been 
> learning and doing work with web development languages like HTML, CSS ,PHP, 
> JQuerry and JavaScript since my first year of engineering and worked as a 
> part of user experience team of several community projects. I have great 
> interest in designing and front-end architecture. I have worked as a 
> graphic designer for various technical societies of my college.As a  
> graphic designer, I have learned a lot about typography and color schemes.I 
> have working knowledge of Java(CS 106A), C, photoshop and illustrator too.
>
> I am really very excited  for these two projects because I have all the 
> skills mentioned for these projects. Most importantly, it will be 
> undoubtedly great learning experience for me. I think UI is very important 
> aspect of an application. It decides credibility of a  website or an 
> application and improves user experience.It will be a great opportunity for 
> me to work with Jenkins.
>
> I have installed jenkins on my system and downloaded the source code and 
> started working on it. Before diving deep into it, I saw a lot old and 
> non-elegant icons and alignment issues.I am eagerly waiting for the hangout 
> session to ask some questions and to know more about the ideas. I will 
> write back and submit my proposal after a deep analysis of the application.
>
> Links:
> LinkedIn: https://in.linkedin.com/in/arshdkhn1
> Twitter:  https://twitter.com/arshdkhn1
> Personal Website: www.collegenerd.in
> Github: https://github.com/arshdkhn1
> Broomberg Services: https://www.broomberg.in
> Graphic designs:http://collegenerd.in/graphic-designs/
>
> Best regards,
> Arshad Khan
>  
>
>
>
>
>

-- 
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/c6b8d984-67ed-4409-9dc8-b62487c8571b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: simpleBuild - a pipeline DSL (and a sad tale about sandboxes)

[James Dumay]

This is a really cool idea Michael - I'd love to see Pipeline DSL be easy 
for novices. Travis, etc have made it look so simple and I believe we could 
improve Pipeline adoption if we had a similar answer.

On Thursday, February 4, 2016 at 7:07:17 PM UTC+11, Michael Neale wrote:
>
> Inspired by Jesse's example 
> 
>  DSL 
> using docker workflow, I thought I would see how far I could take things in 
> making DSLs. 
> I wanted to make things that looked very similar to what people do with 
> tools like travis - something at home in a Jenkinsfile that anyone can 
> open, and read and immediately comprehend, for simple cases, what the build 
> instructions are. 
>
> This is mostly pretty easy: I have put it here for now 
> https://github.com/michaelneale/jenkinsfile (until I sort out some 
> issues). 
> It can work with or without docker workflow (you just specify an image, or 
> not), sends emails (even in failure), set environment variables etc, of 
> course I would love for it to do more. 
>
> However, one road block has been my use of literal maps and the sandbox. 
> This all works grand if I don't use the sandbox, but use the sandbox (or 
> multibranch/SCM, which enables sandbox), and sadness results that I can't 
> work out how to get around:
>
> org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: 
> Scripts not permitted to use field java.util.HashMap$Node key
> at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectField(StaticWhitelist.java:169)
> at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.rejectField(SandboxInterceptor.java:195)
> at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:
>
> - this shows up when I enable the sandbox (sadbox?). 
>
> It seems NOTHING in java.util.Map is whitelisted. I am using maps at the 
> moment as it makes for a nice DSL similar to what people may see elsewhere. 
> For example: 
>
> simpleBuild {
>
> script = 'echo after $FOO'
>
> notifications = [
> email : "mne...@cloudbees.com "
> ]
>
> env = [
> FOO = "well hello",
> BAR = "I don't even need to be here"
> ]
>
> }
>
> This is valid and works great *without* sandbox, but fails on 
> notifications with sandbox on.  The notifications item 
> (config.notifications in the DSL, from the closure passed into simpleBuild) 
> is a java.util.Map. If I look closer, its actually a LinkedHashMap. 
>
> Does any one have ideas on ways to get around this? the literal map 
> notation is very neat, and would take no time for someone to glance at and 
> follow, however, I don't see a way of working with a Map (I can call size() 
> it seems, but nothing else, I can't get the values() or keySet() 
> collections etc). 
>
> Any ideas appreciated (perhaps using maps is inferior to another approach, 
> which I would like to see, however, I love the idea of staying in 
> pipieline-groovy script, with a DSL, as this takes away NONE of the power). 
>
>
>
>
>
>
>

-- 
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/0d81f27a-d878-4e72-b4ca-1ba058bdf21c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.