Re: Maintainers/owners of github.com/jenkinsci/js-libs

[Tom Fennelly]

Hey Oleg.

Yes, let's put up for adoption anything that should be adopted and I
suppose we should delete/remove/deprecate/whatever the ones that are dead.

Based on yesterday's permissions PR
<https://github.com/jenkins-infra/repository-permissions-updater/pull/1903>,
it seems like the list is very short:

   1. uithemes/uithemes-processor
   2. uithemes/uithemes-pom

I guess it needs to be established whether or not these plugins are in use
at all?

Regards,

Tom.




On Tue, 30 Mar 2021 at 11:13, Oleg Nenashev  wrote:

> Hi Tom,
>
> Thanks a lot for the update! And what about other components? If you are a
> sole maintainer, would you like to put them for adoption?
>
> Best wishes,
> Oleg
>
>
> On Mon, Mar 29, 2021, 12:49 Tom Fennelly  wrote:
>
>> Hi.
>>
>> I've not been working on anything related to
>> https://github.com/jenkinsci/js-libs for some time now (and not likely
>> to do so for the foreseeable future) so it makes sense to reassign
>> ownership/leadership to someone else.
>>
>> Regards,
>>
>> Tom.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPao%2B6%2BViis%2BfzwdjWiVw6%3DYqRQvCeG265pZ%3D-jiy3v8qOSg%40mail.gmail.com.

Maintainers/owners of github.com/jenkinsci/js-libs

[Tom Fennelly]

Hi.

I've not been working on anything related to
https://github.com/jenkinsci/js-libs for some time now (and not likely to
do so for the foreseeable future) so it makes sense to reassign
ownership/leadership to someone else.

Regards,

Tom.

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

Re: Failed to build js-lib plugins from source

[Tom Fennelly]

See https://github.com/jenkinsci/js-libs/pull/4 
and https://github.com/jenkinsci/jenkins/pull/3215. Should fix these issues.

-- 
You received this message because you are 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/6888eb97-7539-4066-8852-4ecd4a1b00ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Newbie Question, can I create a plugin that replaces the form buliding in jenkins that uses modern web frameworks?

[Tom Fennelly]

Have you looked at Blue Ocean?

On Thursday, April 27, 2017 at 4:07:57 PM UTC+1, Tomer Ben David wrote:
>
> Can I create a jenkins plugin (I saw this for example: 
> https://github.com/jenkinsci/extreme-feedback-plugin/blob/master/src/main/resources/org/jenkinsci/plugins/extremefeedback/XfManagementLink/index.groovy)
>  
> which uses modern web frameworks like bootstrap/react/angularjs etc and 
> when I click "run build" it would show my input boxes and UI instead of the 
> standard ones? 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/aa2997a6-4af7-4e54-bfda-3973e16a6331%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Integrate EsLint wint Jenkins

[Tom Fennelly]

Hi Raul. Can you elaborate on what you mean by "integrate with the Jenkins
tool" please? You might be talking about writing a Jenkins plugin specific
to eslint, or just wanting to know how to run it in a maven build env.

On 25 March 2017 at 22:07, Baptiste Mathus  wrote:

> I know close to nothing yet about that subject, but looking at
> https://github.com/tfennelly/jenkins-js-eslint-config I'm adding Tom in
> cc because he would probably be more helpful than me :-).
>
> 2017-03-20 19:49 GMT+01:00 Raul Frias :
>
>> Hi,
>>
>> I am working with Eslint tool and works very well, I installed it in my
>> project locally and I run it by console, is great.
>>
>> My question is, how can I integrate Eslint  with Jenkins tool?
>>
>> I was thinking create a bat or .cmd file to run by console and  then run
>> it with Jenkins some way.
>>
>> I was researching about this, but for the moment I do not find nothing.
>>
>> If there is someone that help me with this.
>>
>> Thank
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/985411de-466f-4a96-9ddf-6abe11716426%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/CA%2BbPaoJATcbXqtC4A0BJkfYgHT3uwgoi5%3DcV8vEBq9_nvLNOjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Blue Ocean] Yeoman generator for creating a Blue Ocean extension plugin

[Tom Fennelly]

For anyone interested in taking it for a spin: 
https://www.npmjs.com/package/generator-blueocean-usain

-- 
You received this message because you are 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/893fb37d-ef2f-441f-b9c8-33779bcbc43f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Removing name autocompletion in new job creation

[Tom Fennelly]

Why move the input Vs the warning text?

On 9 August 2016 at 06:45, Samat Davletshin  wrote:

> The autocomplete parameter  is not specified in jelly so I believe it is
> browser behavior remembering name="name" input.
>
> In #2501  pull request I
> propose to move input box so that autocomplete will not hide warning
> message. What do you think?
>
> However, I think that UI changes may complicate the initial pull request.
> May be it is better to decide on leaving or removing autocomplete here and
> consider moving elements in a separate PR.
>
> --
> 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/2qZDQe2_QxI/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/68ed7d22-7051-4a18-b79f-a33034fc1618%
> 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/CA%2BbPaoJY4101XBRUErG1FE_yf3TQeL1J5V4G87%3DSC-wWk0ugOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Removing name autocompletion in new job creation

[Tom Fennelly]

Is autocomplete of the job name an actual feature, or just something that's 
there by default from the browser? If autocomplete must stay, maybe the 
placement of the validation warnings could be moved e.g. above the input?

On Monday, August 8, 2016 at 1:06:19 PM UTC+1, Samat Davletshin wrote:
>
> Hello!
>
> In my Pull Request I propose to make name validation of a new job more 
> interactive.
> https://github.com/jenkinsci/jenkins/pull/2416
>
> However, it was noted that because of autocomplete the warning message 
> will not always be visible.
>
> Do you think that I should remove the autocomplete of new job name or keep 
> it?
>

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

A UUID on Jobs, Runs and others (perhaps) ?

[Tom Fennelly]

Just wondering if this was done elsewhere as a method of always being able 
to find a Job, Run etc instance Vs the current mechanisms that use the 
name/fullName and break if that ever changes?

-- 
You received this message because you are 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/5a01f50d-400d-4153-83b9-1d5cc46959ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Running Blue Ocean on a port other than 8080

[Tom Fennelly]

Have you tried running a new Jenkins instance, setting $JENKINS_HOME to 
something new and specifying --httpPort to run on a different port?

See https://wiki.jenkins-ci.org/display/JENKINS/Starting+and+Accessing+Jenkins

On Wednesday, July 13, 2016 at 10:56:09 PM UTC+1, Erica wrote:
>
> Hi folks,
>
> I'm attempting to play with Blue Ocean a bit, but already have things 
> running on port 8080. Is there a way I can run it on a port other than 
> 8080? Other posters with this issue were advised to use Docker, but 
> unfortunately, that's not an option for me.
>
> Any help would be immensely appreciated.
>
> Thanks!
> Erica
>

-- 
You received this message because you are 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/aa51451b-45cf-4011-9910-6b9fab7d5b21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Tom Fennelly]

I do not know the answer off the top of my head. As Mic says, all those 
packages are in the public repo so "should just work" (famous last 
words). Create a JIRA ticket (describing your setup and what you tried) and 
I or someone else will look at it.

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

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

Re: [GSoC2016] Jenkins WebUI

[Tom Fennelly]

I'm happy to meet for 30 mins, but Samat also knows he can contact me
directly if he needs help on something. 8am in the morning might not be
such a good time for me ;)

On 4 July 2016 at 12:15, Samat Davletshin  wrote:

> I would be glad to meet as often as you want.
> So you can decide on a convenient time(s) and I will attend.
> In particular, yes, Wednesday 8 AM UTC works well for me.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/fk5deO_SszU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/4d77664d-c95c-42cb-9e23-a2b15d6fb2a0%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/CA%2BbPaoKHgyq3xMuFo1K-xRvwJvTsHCAUTMUah_9Nye9T3ebREg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] - blueocean ui not available

[Tom Fennelly]

As said earlier ... manually installing (Vs using hpi:run from source) the
plugins is a pita at the moment and not going to work unless you get
absolutely all the deps you need (including transitive deps). We hope to be
doing an experimental update site release in the next few days. That should
make things a lot easier for people.

If you want to continue trying to get it working on a Jenkins instance (not
using hpi:run) then you could try using hpi:assemble-dependencies and then
manually dropping them into JENKINS_HOME.

On 22 June 2016 at 10:43, Ivan Peshev  wrote:

> Can't install BlueOcean plugins on Jenkins 2.10 , tried several methods
> including: manual upload of hpi files ( only two are installed the others
> are failing ) , through console utility
> java -jar /tmp/jenkins-cli.jar -s http://localhost install-plugin ...
> this is passing but then nothing has changed in jenkins and only blueocean
> is in list of installed plugins with list-plugins command.
> Also have tried to put the files into jenkins plugins directory , it
> processes those but after restart nothing changes.
> Am I doing something wrong, or I should wait for official release of
> blueocean as jenkins plugin in plugin registries ?
>
> --
> 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/FUQED3BAteg/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/932043ce-df95-4522-8053-0a80cfee6b0e%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/CA%2BbPaoLZfzHToQznVmx8xAsU8KexYyYbRQ-kv2g11VKTK1ZV0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin site overhaul?

[Tom Fennelly]

Looks cool Gus.

On Wednesday, June 15, 2016 at 5:43:22 AM UTC+9, Gus Reiber wrote:
>
> +1 to GitHub readme as well. Why put the same doc in 2 places.
>
>
>
> On Tuesday, June 14, 2016 at 1:30:24 PM UTC-7, slide wrote:
>>
>> +1 for the effort, ideally I'd like to see something that can pull 
>> information from the github README.md files and have people push updates to 
>> the descriptions that would be shown to their own plugin repositories. 
>> Perhaps some of the other information could be pulled from a metadata file 
>> that was also in the plugin repository. 
>>
>> On Tue, Jun 14, 2016 at 1:02 PM Gus Reiber  wrote:
>>
>>> Hey all,
>>>So I have on and off pushed the idea that the Jenkins community could 
>>> benefit greatly from an overhaul of the wiki based plugins site. As an 
>>> ultimate goal, I don't see any reason we couldn't build something that 
>>> approach a modern app store, like https://play.google.com/store, but 
>>> for the short run, it seems like we should be able to improove upon the 
>>> browsing experience of the existing list page and detail view.
>>>
>>> Existing: 
>>>
>>>- list: https://wiki.jenkins-ci.org/display/JENKINS/Plugins
>>>- detail: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin
>>>
>>> I think as a minimum, we ought to be able to provide a reasonable search 
>>> interface and means of filtering plugins by maintainer, Jenkins core 
>>> requirement, plugins labels, and installation count. Plugins should also be 
>>> assigned to categories that map to Jenkins user expectations a bit better 
>>> than the current list of ~30ish maintainer assigned labels do today. 
>>> Ideally the user ought to be able to manage the list of all plugins by 
>>> specific features of the plugin and by some suggestion of quality or 
>>> currentness of the plugin.
>>>
>>> At various points, my interest in bringing this value to the community 
>>> has been great enough to assemble a couple of different prototypes and 
>>> wireframes, attempting to generate interest. I have also had a chance to 
>>> play with some prototypes from others all with what seems to me to be 
>>> reasonable implementation paths. Attached are a few more recent sketches 
>>> showing the gist of how we might handle searching and filtering as well as 
>>> the plugin details.
>>>
>>> Anyway, at the moment, the plugin site is maintained by our 
>>> representatives here in the community. So it is really the will of the 
>>> community that should be reflected in any efforts that are actually 
>>> deployed and later maintained by our community. Thus again, I am looking 
>>> for grass roots support for the effort, support that potentially includes 
>>> some avenue for long term hosting and support.
>>>
>>> So my questions are these: Is enhancing the plugin site really worth 
>>> that degree of effort to the community? If you think it is, would you be 
>>> willing to join the effort, both for the immediate development needs, but 
>>> also for longer term support? Do you have any experience with other 
>>> communities who manage to accomplish this sort of ends?
>>>
>>> ...and finally, could you help articulate a set of minimum requirements 
>>> that would make overhauling the plugin site worth while?
>>>
>>> Thanks in advance,
>>> Gus
>>>
>>> -- 
>>> You received this message because you are 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/33ab5051-e2b8-4684-8d9e-0d5aa6ab1284%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/5eebcfb4-e11e-4b80-9dc7-9b2a941c0649%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Tom Fennelly]

On Thursday, June 16, 2016 at 10:38:45 PM UTC+9, Quentin Dufour wrote:
>
> My Pull Request has been accepted, but I've found some other pom.xml 
> missing the same entry.
> Here is the list I've found :
>
>- https://github.com/jenkinsci/jenkins/blob/master/war/pom.xml
>- 
>
> https://github.com/jenkinsci/js-builder/blob/master/res/sample_extract_pom.xml
>- 
>https://github.com/jenkinsci/js-libs/blob/master/js-module-base/pom.xml
>
> As I'm new here, I don't really know what to do next. 
>
> As far as I know, nodejs is only needed during compilation because it's 
> used by blueocean and some other plugins which need gulp and its 
> "ecosystem" to generate frontend assets.
> I don't completely understand why nodejs have to be redownloaded in the 
> above files, but I think it could cause some trouble if my modified pom.xml 
> doesn't match the others.
>
> @andresrc recommended that I open a PR on jenkinsci/jenkins in order that 
> we get more input about supported architecture.
>
>- Should I open a PR for linux i386 on every project ? 
>- Should we discuss about supported architecture for compilation 
>before ? 
>- Should I open an issue on Jira ?
>
> Yes, I think it would be worth doing it for Jenkins core (as suggested by 
@andresrc). Thanks Quentin !!

-- 
You received this message because you are 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/8bf96024-61ba-497d-b9f9-f3f8a9ce69ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] - blueocean ui not available

[Tom Fennelly]

On Thursday, June 16, 2016 at 11:43:52 PM UTC+9, Daniel Beck wrote:
>
>
> > On 16.06.2016, at 16:40, Michael Madden  > wrote: 
> > 
> > by starting with a recent 2.x build of Jenkins (war, rpm, or deb) & then 
> add the experimental update site to get the newer plugins? 
>
> Yes. 
>

Once the plugins are in the experimental update center. They're not there 
yet. 

-- 
You received this message because you are 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/c2615316-cbf9-4448-be30-f1b3dab6c29d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [blueocean-plugin] No pipelines found

[Tom Fennelly]

Hi Wayne. So how did you install Blue Ocean on your Jenkins instance. It 
sounds as though one of the blueocean-* plugins are missing. Can you check 
the JavaScript console in the browser and let us know if you see any 
errors/warnings?

On Thursday, June 16, 2016 at 3:20:58 AM UTC+9, Wayne Warren wrote:
>
> Howdy folks!
>
> So recently I built and installed the blueocean-plugin from the 
> https://github.com/jenkinsci/blueocean-plugin git repo. The SHA from 
> which I built the plugin is 1d5239dd00cec9f7b233a9d960b5cb72a9144320.
>
> I am using a clean install of 
> http://pkg.jenkins-ci.org/debian/binary/jenkins_2.8_all.deb with 
> authentication set up such that any user logged in through LDAP can "do 
> anything".
>
> I created one job without using a folder (someone on IRC mentioned that 
> blueocean-plugin doesn't "see" folders). The config.xml for that job is 
> here:
>
> 
>   
>   false
>   
>plugin="workflow-cps@2.5">
> node { stage 'Stage 1' echo 'Hello World 1' stage 'Stage 2' 
> echo 'Hello World 2'}
> true
>   
>   
> 
>
> When I navigate to $HOST/blue/pipelines all I see below the blue bar in 
> the UI is "No pipelines found."
>
> Anyone have advice for how to figure out why my pipeline job isn't showing 
> up? Am I using the wrong job type? When I created it I selected the 
> "Pipeline" project type in the UI. Thanks in advance for whatever help you 
> can offer!
>

-- 
You received this message because you are 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/239d5906-37e3-4451-b9fb-5b712f3e941b%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

[Tom Fennelly]

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-dev+unsubscr...@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/CA%2BbPaoJ8ErKb%2BAGy4kOf2p2Q-gGxG4YDrZWs_m5_Tf88G5C3Mw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do I have a disabled entry in a Jelly form

[Tom Fennelly]

I guess it depends on how you want to eventually reenable the elements on 
the page, but in general you're talking about using JavaScript on the page 
that watches the values change in certain fields and then enables/disables 
the "special" fields.

On Friday, June 10, 2016 at 8:27:32 PM UTC+9, Marc Carter wrote:
>
> Hi
> I think the subject says it all but to expand: I wish to conditionally 
> show some f:entry/f:checkbox elements as greyed-out (ideally with a 
> suitable tooltip) rather than simply not displaying them. Is this not 
> possible?
>

-- 
You received this message because you are 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/32bb3c97-44b1-41a1-a694-4ea5fc998500%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

[Tom Fennelly]

Hi there.

The Blue Ocean plugins are not yet in the Update center, so installing it 
in a Jenkins instance is a bit tricky atm Vs running hpi:run from source.

As for your plugin ... maybe start a new thread about that, giving some 
details of the plugin etc.


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

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

Re: Time to update the Browser Compatibility Matrix?

[Tom Fennelly]

Sorry for the typos ;)

-- 
You received this message because you are 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/6cc92fcd-da97-4194-b5a8-a86a180ef39f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Time to update the Browser Compatibility Matrix?

[Tom Fennelly]

Hi all.

While doing some testing/fixing of Blue Ocean to get it building on Windows 
I notice that the Jenkins Browser Compatibility Matrix 
 
is a bit outdated.

Any thoughts on the changes we should make.

Some points of ref ...

   1. Microsoft Edge browser. Only on Windows 10. I don't use Windows and 
   have not tried Jenkins on Edge. Should we be stating anything support level 
   for this yet?
   2. Latest Safari is 9.1 (right?). What should we be saying about this? 
   We're currently saying 
   6+. https://en.wikipedia.org/wiki/Safari_version_history
   3. Browser usage. Depends on who you ask + Jenkins users may not follow 
   the "norm", so take these with a grain of salt:
  - http://www.w3schools.com/browsers/browsers_stats.asp
  - 
  
https://www.netmarketshare.com/browser-market-share.aspx?qprid=2=0
   

-- 
You received this message because you are 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/790389f0-3773-4a8b-962c-7cd56214f9b8%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

[Tom Fennelly]

Cool. These fixes have been merged to master. Also added a related comment 
in the readme wrt building on windows.

On Thursday, June 9, 2016 at 8:27:20 AM UTC+1, Itai Sanders wrote:
>
> I can confirm that it does indeed run 
> funny thing - after I shut down our working Jenkins service, run this 
> project on a different folder and then go back to our own service - the 
> Blue Ocean plugin is installed and updated on our Jenkins as well so I can 
> just do this for the update and then go back to see our pipelines in the 
> new view.
>
>
>
> Itai Sanders
>
> <http://www.morphisec.com/>
>
> On Wed, Jun 8, 2016 at 6:36 PM, Tom Fennelly <tom.fe...@gmail.com 
> > wrote:
>
>> Again ... build by doing ....
>>
>> mvn clean install -DskipTests
>>
>> On 8 June 2016 at 16:35, Tom Fennelly <tom.fe...@gmail.com > 
>> wrote:
>>
>>> Ok ... I have a build passing on windows (using -DskipTests). The UI 
>>> opens in chrome, but we have some big'ish issues running on internet 
>>> explorer (I tried it on IE 11).
>>>
>>> PR #239 <https://github.com/jenkinsci/blueocean-plugin/pull/239>, 
>>> branch ... UX-163 
>>> <https://github.com/jenkinsci/blueocean-plugin/tree/UX-163>.
>>>
>>> On 8 June 2016 at 11:49, Tom Fennelly <tom.fe...@gmail.com 
>>> > wrote:
>>>
>>>> I'm trying to get a build running on windows here. Will try get a 
>>>> working version skipping tests. We're going to have to get this sorted 
>>>> soon 
>>>> anyway.
>>>>
>>>> On 8 June 2016 at 00:37, Michael Neale <mne...@cloudbees.com 
>>>> > wrote:
>>>>
>>>>> Right - I guess if the aim is to just try things, this will be in the 
>>>>> update center soon one way or another for people to try. 
>>>>>
>>>>> In the meantime, if all the hpi's are copied into the plugins dir of a 
>>>>> running jenkins (and transitive dependencies satisfied) - then it should 
>>>>> work. 
>>>>>
>>>>> On Wednesday, June 8, 2016 at 4:22:27 AM UTC+10, Tom Fennelly wrote:
>>>>>>
>>>>>> On Tuesday, June 7, 2016 at 5:23:18 PM UTC+1, Ian Ceicys wrote:
>>>>>>>
>>>>>>> I tried the same steps and got the same result as Itai
>>>>>>>
>>>>>>
>>>>>> My guess is that the symlink in blueocean-web is screwing things up 
>>>>>> for windows hence no styles etc. 
>>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to a topic in the 
>>>>> Google Groups "Jenkins Developers" group.
>>>>> To unsubscribe from this topic, visit 
>>>>> https://groups.google.com/d/topic/jenkinsci-dev/otY1UkS9f4w/unsubscribe
>>>>> .
>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>> jenkinsci-de...@googlegroups.com .
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/e7145900-2a17-40b9-8ebd-7a89684d3abf%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/e7145900-2a17-40b9-8ebd-7a89684d3abf%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-dev/otY1UkS9f4w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPaoKGhzVi1kB9N_kGykuEtiPqQOCF0w65oSYf7T9fODhF%2Bw%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPaoKGhzVi1kB9N_kGykuEtiPqQOCF0w65oSYf7T9fODhF%2Bw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8a132cca-f3bb-4696-9ba2-692bf439dcfd%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

[Tom Fennelly]

Again ... build by doing 

mvn clean install -DskipTests

On 8 June 2016 at 16:35, Tom Fennelly <tom.fenne...@gmail.com> wrote:

> Ok ... I have a build passing on windows (using -DskipTests). The UI opens
> in chrome, but we have some big'ish issues running on internet explorer (I
> tried it on IE 11).
>
> PR #239 <https://github.com/jenkinsci/blueocean-plugin/pull/239>, branch
> ... UX-163 <https://github.com/jenkinsci/blueocean-plugin/tree/UX-163>.
>
> On 8 June 2016 at 11:49, Tom Fennelly <tom.fenne...@gmail.com> wrote:
>
>> I'm trying to get a build running on windows here. Will try get a working
>> version skipping tests. We're going to have to get this sorted soon anyway.
>>
>> On 8 June 2016 at 00:37, Michael Neale <mne...@cloudbees.com> wrote:
>>
>>> Right - I guess if the aim is to just try things, this will be in the
>>> update center soon one way or another for people to try.
>>>
>>> In the meantime, if all the hpi's are copied into the plugins dir of a
>>> running jenkins (and transitive dependencies satisfied) - then it should
>>> work.
>>>
>>> On Wednesday, June 8, 2016 at 4:22:27 AM UTC+10, Tom Fennelly wrote:
>>>>
>>>> On Tuesday, June 7, 2016 at 5:23:18 PM UTC+1, Ian Ceicys wrote:
>>>>>
>>>>> I tried the same steps and got the same result as Itai
>>>>>
>>>>
>>>> My guess is that the symlink in blueocean-web is screwing things up for
>>>> windows hence no styles etc.
>>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/jenkinsci-dev/otY1UkS9f4w/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/e7145900-2a17-40b9-8ebd-7a89684d3abf%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/e7145900-2a17-40b9-8ebd-7a89684d3abf%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPaoKGhzVi1kB9N_kGykuEtiPqQOCF0w65oSYf7T9fODhF%2Bw%40mail.gmail.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

[Tom Fennelly]

Ok ... I have a build passing on windows (using -DskipTests). The UI opens
in chrome, but we have some big'ish issues running on internet explorer (I
tried it on IE 11).

PR #239 <https://github.com/jenkinsci/blueocean-plugin/pull/239>, branch
... UX-163 <https://github.com/jenkinsci/blueocean-plugin/tree/UX-163>.

On 8 June 2016 at 11:49, Tom Fennelly <tom.fenne...@gmail.com> wrote:

> I'm trying to get a build running on windows here. Will try get a working
> version skipping tests. We're going to have to get this sorted soon anyway.
>
> On 8 June 2016 at 00:37, Michael Neale <mne...@cloudbees.com> wrote:
>
>> Right - I guess if the aim is to just try things, this will be in the
>> update center soon one way or another for people to try.
>>
>> In the meantime, if all the hpi's are copied into the plugins dir of a
>> running jenkins (and transitive dependencies satisfied) - then it should
>> work.
>>
>> On Wednesday, June 8, 2016 at 4:22:27 AM UTC+10, Tom Fennelly wrote:
>>>
>>> On Tuesday, June 7, 2016 at 5:23:18 PM UTC+1, Ian Ceicys wrote:
>>>>
>>>> I tried the same steps and got the same result as Itai
>>>>
>>>
>>> My guess is that the symlink in blueocean-web is screwing things up for
>>> windows hence no styles etc.
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/otY1UkS9f4w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/e7145900-2a17-40b9-8ebd-7a89684d3abf%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/e7145900-2a17-40b9-8ebd-7a89684d3abf%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPaoLpzsZeXG56PRPC0Gov3qE2QF_HKiDJcNW4KpByEUjV-Q%40mail.gmail.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

[Tom Fennelly]

I'm trying to get a build running on windows here. Will try get a working
version skipping tests. We're going to have to get this sorted soon anyway.

On 8 June 2016 at 00:37, Michael Neale <mne...@cloudbees.com> wrote:

> Right - I guess if the aim is to just try things, this will be in the
> update center soon one way or another for people to try.
>
> In the meantime, if all the hpi's are copied into the plugins dir of a
> running jenkins (and transitive dependencies satisfied) - then it should
> work.
>
> On Wednesday, June 8, 2016 at 4:22:27 AM UTC+10, Tom Fennelly wrote:
>>
>> On Tuesday, June 7, 2016 at 5:23:18 PM UTC+1, Ian Ceicys wrote:
>>>
>>> I tried the same steps and got the same result as Itai
>>>
>>
>> My guess is that the symlink in blueocean-web is screwing things up for
>> windows hence no styles etc.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/otY1UkS9f4w/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/e7145900-2a17-40b9-8ebd-7a89684d3abf%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/e7145900-2a17-40b9-8ebd-7a89684d3abf%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPaoLv5pihS%3DtKHGpCzNkZ3ZYGtF8DNMuR7Q-fAREZdYwNyA%40mail.gmail.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

[Tom Fennelly]

On Tuesday, June 7, 2016 at 5:23:18 PM UTC+1, Ian Ceicys wrote:
>
> I tried the same steps and got the same result as Itai
>

My guess is that the symlink in blueocean-web is screwing things up for 
windows hence no styles etc. 

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

Re: [Blue Ocean] Tracking NPM dependencies and managing the js download sizes

[Tom Fennelly]

On 7 June 2016 at 17:14, Robert Sandell  wrote:

> Are there any code sharing between bundles?
> I mean if two bundles are using jquery 1.99.3 will there be two separate
> instances of that code downloaded and compiled? Or is the various packages
> downloaded independently and then just instantiated separately in each
> module?
>
> /B
>

It can work either way. If you are creating a bundle that uses jQuery
internally, it can be created to include its own copy of jQuery, or can be
created to use an "externalized" shared instance of that particular version
of jQuery.

Some more docs on how to do that can be found in this sample plugin

.

So what this means then in this case is ... say plugin bundles A and B both
externalizes jquery 1.99.3 (not even sure such a version exists ... doesn't
matter) ... at runtime, plugin A loads first and triggers the loading of
the externalized jquery 1.99.3 ... when plugin B is loaded (later) it will
get the same/shared instance of jquery 1.99.3 loaded earlier by plugin A.

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

[Blue Ocean] Tracking NPM dependencies and managing the js download sizes

[Tom Fennelly]

Thought I'd share something with those interested in Blue Ocean wrt how 
we're building things there and some of the challenges we're trying to deal 
with.

The Blue Ocean (BO) UI is a single page app (SPA), with lots of client-side 
JavaScript, using new frameworks/tools/libs such as React, Redux and more. 
So there's lots of "new" stuff in there when compared with how Jenkins UI's 
have been built in the past ... a big learning process for everyone 
involved.

All of this client-side code is not in a single .js file, but instead split 
across multiple self-contained javascript "bundles", and using some 
js-builder  
and js-modules 
 magic to 
"link" things together at runtime.

The main/startup "bundle" is currently defined in the "blueocean-web" and 
it is responsible for loading some/all of the "core" modules used by BO, 
including react, react-dom and some others. This means that these modules 
are all inside the blueocean-web "bundle" (it has to be this way because of 
how react works).

One of the ongoing challenges we are looking at is - how do we make sure 
these bundles don't get too bloated and cause suckie UX because the user is 
kept waiting on JS to load. This is always going to be a challenge and 
something we need to monitor, just like personal fitness and weight is a 
constant challenge for people.

Anyway ... what I wanted to share here was a simple tool we found for 
analysing browserify generated bundles (we're currently using Browserify to 
generate the actual .js bundles). It tells you the composition of the 
bundle and which npm packages and CommonJS modules are contributing most to 
the bundle size. It's called discify 
 and after installing 
and running it, you can get some interesting info from it in the form of an 
interactive (hover the different slices to get details) chart that 
highlights the packages/modules going into the bundle, and the percentage 
of the bundle size each is contributing.



Yeah ... the above is just giving a flavour ... you really need to run it 
and interact with it to see. I'd encourage people to do that, especially if 
they are contributing to BO and adding dependencies ... we need to be very 
careful that the weight added by a new dependency is really justified in 
terms of the benefits that dependency brings. Adding every new "shinny" lib 
we see is just going to result in problems down the road !!

Installing discify  is 
dead easy ...

npm install -g disc


Then in one of the BO plugins (e.g. blueocean-web), just run gulp build as 
normal, but adding the --full-paths switch ...

gulp --full-paths


As this runs, the build will output the locations to where the bundles are 
being generated. You can use this to work out the path that needs to be 
supplied to the discify 
 command (or you can 
just look in the gulpfile.js). e.g. for the blueocean.js bundle generated 
by the blueocean-web build 

discify 
/Users/tfennelly/projects/blueocean/blueocean-web/target/classes/io/jenkins/blueocean/blueocean.js
 
-O


Of course, we can use minification and gzipping to reduce the full size, 
but we need to keep a close track on this and be careful when adding 
dependencies.



-- 
You received this message because you are 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/640a15b7-ede1-421c-849d-c78bc9ffee1e%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

[Tom Fennelly]

Can you go to the plugins page and check that the Blue Ocean plugin is
actually installed.

Something looks strange here. How are you running and from where are you
running ?

On 7 June 2016 at 10:00, Itai Sanders <i...@morphisec.com> wrote:

> status report:
> got the in-project jenkins to run under http://localhost:8080/jenkins
> I didn't understand at first that this is going to run on a different
> jenkins instance. too bad, cause I was hoping to test our daily work with
> jenkins using blue ocean and report here. even created a small pipeline to
> update the local instance regularly.
>
> anyhow, http://localhost:8080/jenkins/blue doesn't seem to work.
> attaching 404 error page in case it's any help.
>
>
>
> Itai Sanders
>
> <http://www.morphisec.com/>
>
> On Tue, Jun 7, 2016 at 11:20 AM, Tom Fennelly <tom.fenne...@gmail.com>
> wrote:
>
>> On Tuesday, June 7, 2016 at 9:01:14 AM UTC+1, Itai Sanders wrote:
>>>
>>> ok, I ran it without the testing.
>>> now it compiles, but wouldn't start on the same port that Jenkins is
>>> using (8080):
>>>
>>>> FAILED ServerConnector@5949bcfe{HTTP/1.1}{0.0.0.0:8080}:
>>>> java.net.BindException: Address already in use: bind
>>>
>>>
>>> should I close Jenkins and let BlueOcean start it for me?
>>>
>>
>> Right, you will not be able to run it on port 8080 if it's already
>> running on port 8080. Stop all processes listening on port 8080 and then
>> run.
>>
>> Btw, there is a way of specifying a different port, but lets not
>> complicate things.
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/otY1UkS9f4w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/384e2309-041f-4c54-a383-613b3f9fbd53%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/384e2309-041f-4c54-a383-613b3f9fbd53%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/otY1UkS9f4w/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CADxfEAbemBWpAf3MakxDdkPLVKt2kFhCJJBvL9A6tFJPUW6M6g%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CADxfEAbemBWpAf3MakxDdkPLVKt2kFhCJJBvL9A6tFJPUW6M6g%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPaoJnYQjqRNeCprACv3KAetyvp1akOXdqeWCNgZLDz%3DgRgQ%40mail.gmail.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

[Tom Fennelly]

On Tuesday, June 7, 2016 at 9:01:14 AM UTC+1, Itai Sanders wrote:
>
> ok, I ran it without the testing.
> now it compiles, but wouldn't start on the same port that Jenkins is using 
> (8080):
>
>> FAILED ServerConnector@5949bcfe{HTTP/1.1}{0.0.0.0:8080}: 
>> java.net.BindException: Address already in use: bind
>
>
> should I close Jenkins and let BlueOcean start it for me?
>

Right, you will not be able to run it on port 8080 if it's already running 
on port 8080. Stop all processes listening on port 8080 and then run.

Btw, there is a way of specifying a different port, but lets not complicate 
things.

-- 
You received this message because you are 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/384e2309-041f-4c54-a383-613b3f9fbd53%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

[Tom Fennelly]

Hi guys.

For now, in order to get a build to completion on Windows, you'll need to
build with the -DskipTests switch e.g.

mvn clean install -DskipTests

We have a job to go back and fix the tests to run on Windows.


On 7 June 2016 at 08:16, Michael Neale <mne...@cloudbees.com> wrote:

> Right, the tests will need to be changed to accomodate windows.
>
> Looking at:
> https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-rest-impl/src/test/java/io/jenkins/blueocean/service/embedded/PipelineNodeTest.java#L33
>
> You can see it is using shell steps which will fail in this way. If any
> time "sh" is used in a test, "echo" is used, then maybe it will pass the
> tests on windows.
>
>
> On Tuesday, June 7, 2016 at 4:48:06 PM UTC+10, Itai Sanders wrote:
>>
>> Hi Tom,
>>
>> I am too running Jenkins on Windows (Server 2012) and had the above
>> failure, so I found my way to this thread looking for a solution.
>> I tried compiling branch UX-431 as you suggested. the process indeed
>> passed the Dashboard stage, but failed again in REST API implementation
>> stage. it appears that there are some unix commands trying to run because I
>> get a few error messages in the form of:
>>
>>> java.io.IOException
>>> <http://stacktrace.jenkins-ci.org/search?query=java.io.IOException>:
>>> Cannot run program "sh" (in directory
>>> "C:\Windows\TEMP\hudson5061178017739584096test\workspace\pipeline4"):
>>> CreateProcess error=2, The system cannot find the file specified
>>
>> java.io.IOException: Cannot run program "nohup" (in directory 
>> "C:\Windows\TEMP\hudson7279525167245141650test\workspace\pipeline1"): 
>> CreateProcess error=2, The system cannot find the file specified
>>
>>
>> attaching the full log just in case...
>>
>> eager to hop on the wagon,
>> Itai
>>
>>
>>
>> On Monday, June 6, 2016 at 10:35:34 PM UTC+3, Tom Fennelly wrote:
>>>
>>> On 6 June 2016 at 14:54, Ian Ceicys <ianc...@gmail.com> wrote:
>>>
>>>> I found that this issue was already logged and included a possible
>>>> partial workaround.
>>>>
>>>> https://issues.jenkins-ci.org/browse/JENKINS-35180
>>>>
>>>>
>>>> I attempted the workaround and updated file
>>>> (\blueocean-plugin\js-extensions@jenkins-cd\subs\extensions-bundle.js)
>>>> var relPath = path.relative(targetRoot, srcRoot);
>>>> to
>>>> var relPath = path.relative(targetRoot,
>>>> srcRoot).split("\\").join("");
>>>>
>>>> Now I am receiving a new error message:
>>>> [INFO] [11:35:23] error: Error: Cannot find module
>>>> '..srcmainjs/PipelineRoutes.jsx' from
>>>> 'D:\GIT\blueocean-plugin\blueocean-dashboard\target'
>>>>
>>>> Here is a 2 minute video of my repo steps.
>>>> https://www.youtube.com/watch?v=AkhTkTvuETQ?version=3=hd1080
>>>>
>>>> I am still unable to build successfully on windows.
>>>>
>>>>
>>>> Thanks for the help on getting this issue resolved.
>>>>
>>>> On Thursday, June 2, 2016 at 5:43:59 PM UTC-4, Thorsten Scherler wrote:
>>>>>
>>>>>
>>>>> import component_0 from '..\src\main\js/AdminNavLink.jsx';
>>>>>
>>>>> yeah @tom your fix should work
>>>>>
>>>>> salu2
>>>>>
>>>>> On Thursday, June 2, 2016 at 7:54:12 PM UTC+2, Tom Fennelly wrote:
>>>>>>
>>>>>> Specifically we're talking about relPath
>>>>>> <https://github.com/jenkinsci/blueocean-plugin/blob/master/js-extensions/%40jenkins-cd/subs/extensions-bundle.js#L120>
>>>>>> and making sure it always contains unix file path token separators.
>>>>>>
>>>>>> On 2 June 2016 at 18:51, Tom Fennelly <tom.fe...@gmail.com> wrote:
>>>>>>
>>>>>>> Hey Ian. Thanks for the video.
>>>>>>>
>>>>>>> After running the build, please get the contents of
>>>>>>> ./blueocean-dashboard/target/jenkins-js-extension.jsx and attach it back
>>>>>>> here.
>>>>>>>
>>>>>>> Looks like we need a fix we need a fix in
>>>>>>> js-extensions/@jenkins-cd/subs/extensions-bundle.js#L120 to stop it
>>>>>>> translating the paths to the system format

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

[Tom Fennelly]

On 6 June 2016 at 14:54, Ian Ceicys <iancei...@gmail.com> wrote:

> I found that this issue was already logged and included a possible partial
> workaround.
>
> https://issues.jenkins-ci.org/browse/JENKINS-35180
>
>
> I attempted the workaround and updated file
> (\blueocean-plugin\js-extensions@jenkins-cd\subs\extensions-bundle.js)
> var relPath = path.relative(targetRoot, srcRoot);
> to
> var relPath = path.relative(targetRoot, srcRoot).split("\\").join("");
>
> Now I am receiving a new error message:
> [INFO] [11:35:23] error: Error: Cannot find module
> '..srcmainjs/PipelineRoutes.jsx' from
> 'D:\GIT\blueocean-plugin\blueocean-dashboard\target'
>
> Here is a 2 minute video of my repo steps.
> https://www.youtube.com/watch?v=AkhTkTvuETQ?version=3=hd1080
>
> I am still unable to build successfully on windows.
>
>
> Thanks for the help on getting this issue resolved.
>
> On Thursday, June 2, 2016 at 5:43:59 PM UTC-4, Thorsten Scherler wrote:
>>
>>
>> import component_0 from '..\src\main\js/AdminNavLink.jsx';
>>
>> yeah @tom your fix should work
>>
>> salu2
>>
>> On Thursday, June 2, 2016 at 7:54:12 PM UTC+2, Tom Fennelly wrote:
>>>
>>> Specifically we're talking about relPath
>>> <https://github.com/jenkinsci/blueocean-plugin/blob/master/js-extensions/%40jenkins-cd/subs/extensions-bundle.js#L120>
>>> and making sure it always contains unix file path token separators.
>>>
>>> On 2 June 2016 at 18:51, Tom Fennelly <tom.fe...@gmail.com> wrote:
>>>
>>>> Hey Ian. Thanks for the video.
>>>>
>>>> After running the build, please get the contents of
>>>> ./blueocean-dashboard/target/jenkins-js-extension.jsx and attach it back
>>>> here.
>>>>
>>>> Looks like we need a fix we need a fix in
>>>> js-extensions/@jenkins-cd/subs/extensions-bundle.js#L120 to stop it
>>>> translating the paths to the system format. It's an easy fix.
>>>>
>>>> On 2 June 2016 at 17:51, Ian Ceicys <ianc...@gmail.com> wrote:
>>>>
>>>>> I too am running into the 'Cannot find module '..srcmainjs/AdminNavLi
>>>>> nk.jsx' issue when running the following command (mvn clean install) on
>>>>> Windows Server 2012 R2.
>>>>>
>>>>> I have verified that I am running Python 2.7.3 (
>>>>> https://www.python.org/ftp/python/2.7.3/python-2.7.3.msi) as there
>>>>> appears to be an issue running Python 3.5.1.
>>>>>
>>>>> *3 min Video of the Repo Steps:*
>>>>> https://www.youtube.com/watch?v=zetNEjLYX2Q?version=3=hd1080
>>>>>
>>>>> Error Message:
>>>>> [INFO] [12:27:17] Finished 'less_bundle_extensions_bundle_4' after
>>>>> 5.74 ms
>>>>> [INFO] [12:27:18] LESS CSS pre-processing completed to
>>>>> 'target/classes/org/jenki
>>>>> ns/ui/jsmodules/blueocean_dashboard'.
>>>>> [INFO] [12:27:20] Browserify bundle processing error
>>>>> [INFO] [12:27:20]   error: Error: Cannot find module
>>>>> '..srcmainjs/AdminNavLi
>>>>> nk.jsx' from 'D:\GIT\blueocean-plugin\blueocean-dashboard\target'
>>>>> [ERROR]
>>>>> [ERROR]
>>>>> D:\GIT\blueocean-plugin\blueocean-dashboard\node_modules\@jenkins-cd\js-
>>>>> builder\index.js:555
>>>>> [ERROR] throw 'Browserify bundle processing
>>>>> error. See a
>>>>> bove for details.';
>>>>> [ERROR] ^
>>>>> [ERROR] Browserify bundle processing error. See above for details.
>>>>>
>>>>>
>>>>>
>>>>> On Tuesday, May 31, 2016 at 7:29:23 PM UTC-4, Michael Neale wrote:
>>>>>>
>>>>>> *shakes fist at bill gates*. I think "\" was picked as a path
>>>>>> separator deliberately to be different in the 70s when DOS was invented.
>>>>>>
>>>>>> This really shoudl build on windows, but may take some time. Some of
>>>>>> the tests are also creating and executing pipelines that involve "sh" 
>>>>>> steps
>>>>>> which may be a problem once this build issue is overcome. They can 
>>>>>> probably
>>>>>> be amended to use echo steps - which are cross platform I believe.
>>>>>>
>>>>>> So, work to be d

Re: [Blue Ocean] New UX project for jenkins

[Tom Fennelly]

On Thursday, June 2, 2016 at 7:03:17 PM UTC+1, Tom Fennelly wrote:
>
> We created a blueocean-acceptance-test 
> <https://github.com/cloudbees/blueocean-acceptance-test> repo and have 
> some initial acceptance/smoke tests in it.
>
> Hoping the repo can be moved to jenkinsci (HOSTING-109 
> <https://issues.jenkins-ci.org/browse/HOSTING-109>).
>
> Builds on the main acceptance-test-harness. Initial tests are written 
> using a JS selenium toolkit called Nightwatch.js 
> <http://nightwatchjs.org/>. There's a video on the README.md.
>

And of course this may end up being merged back into the  main 
acceptance-test-harness repo at some stage ... we'll see :)

-- 
You received this message because you are 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/39b659a6-35b9-4d28-8b7c-0380d9844fa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] New UX project for jenkins

[Tom Fennelly]

We created a blueocean-acceptance-test 
 repo and have some 
initial acceptance/smoke tests in it.

Hoping the repo can be moved to jenkinsci (HOSTING-109 
).

Builds on the main acceptance-test-harness. Initial tests are written using 
a JS selenium toolkit called Nightwatch.js . 
There's a video on the README.md.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9d2686ec-34af-4a5e-861a-c4543b994055%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

[Tom Fennelly]

Specifically we're talking about relPath
<https://github.com/jenkinsci/blueocean-plugin/blob/master/js-extensions/%40jenkins-cd/subs/extensions-bundle.js#L120>
and making sure it always contains unix file path token separators.

On 2 June 2016 at 18:51, Tom Fennelly <tom.fenne...@gmail.com> wrote:

> Hey Ian. Thanks for the video.
>
> After running the build, please get the contents of
> ./blueocean-dashboard/target/jenkins-js-extension.jsx and attach it back
> here.
>
> Looks like we need a fix we need a fix in
> js-extensions/@jenkins-cd/subs/extensions-bundle.js#L120 to stop it
> translating the paths to the system format. It's an easy fix.
>
> On 2 June 2016 at 17:51, Ian Ceicys <iancei...@gmail.com> wrote:
>
>> I too am running into the 'Cannot find module '..srcmainjs/AdminNavLi
>> nk.jsx' issue when running the following command (mvn clean install) on
>> Windows Server 2012 R2.
>>
>> I have verified that I am running Python 2.7.3 (
>> https://www.python.org/ftp/python/2.7.3/python-2.7.3.msi) as there
>> appears to be an issue running Python 3.5.1.
>>
>> *3 min Video of the Repo Steps:*
>> https://www.youtube.com/watch?v=zetNEjLYX2Q?version=3=hd1080
>>
>> Error Message:
>> [INFO] [12:27:17] Finished 'less_bundle_extensions_bundle_4' after 5.74 ms
>> [INFO] [12:27:18] LESS CSS pre-processing completed to
>> 'target/classes/org/jenki
>> ns/ui/jsmodules/blueocean_dashboard'.
>> [INFO] [12:27:20] Browserify bundle processing error
>> [INFO] [12:27:20]   error: Error: Cannot find module
>> '..srcmainjs/AdminNavLi
>> nk.jsx' from 'D:\GIT\blueocean-plugin\blueocean-dashboard\target'
>> [ERROR]
>> [ERROR]
>> D:\GIT\blueocean-plugin\blueocean-dashboard\node_modules\@jenkins-cd\js-
>> builder\index.js:555
>> [ERROR] throw 'Browserify bundle processing
>> error. See a
>> bove for details.';
>> [ERROR] ^
>> [ERROR] Browserify bundle processing error. See above for details.
>>
>>
>>
>> On Tuesday, May 31, 2016 at 7:29:23 PM UTC-4, Michael Neale wrote:
>>>
>>> *shakes fist at bill gates*. I think "\" was picked as a path separator
>>> deliberately to be different in the 70s when DOS was invented.
>>>
>>> This really shoudl build on windows, but may take some time. Some of the
>>> tests are also creating and executing pipelines that involve "sh" steps
>>> which may be a problem once this build issue is overcome. They can probably
>>> be amended to use echo steps - which are cross platform I believe.
>>>
>>> So, work to be done..
>>>
>>> On Wednesday, June 1, 2016 at 9:22:42 AM UTC+10, Thorsten Scherler wrote:
>>>>
>>>> Yeah I am with Tom, one / is getting "eaten"
>>>>
>>>> .srcmainjs/AdminNavLink.jsx' from
>>>> 'C:\Users\Admin\Downloads\blueocean\blueocean-dashboard\target'
>>>>
>>>> the whole path until the last is missing it. That is coming from bo-web
>>>> assembling the extensions points.
>>>>
>>>> BTW that file should be called DashboardNavLink. ;)
>>>>
>>>> salu2
>>>>
>>>> On Tuesday, May 31, 2016 at 10:26:33 PM UTC+2, Tom Fennelly wrote:
>>>>>
>>>>> On Tuesday, 31 May 2016 06:04:44 UTC+1, Richard Bywater wrote:
>>>>>>
>>>>>> I assume the cause of the issue is:
>>>>>> "Cannot find module '..srcmainjs/AdminNavLink.jsx"
>>>>>>
>>>>>> It looks like something is trying to write a string probably started
>>>>>> as "..\src\main\js/AdminNavLink.jsx" and its entered something like Java
>>>>>> which has seen those backslashes as escape characters (and hence ended up
>>>>>> as srcmainjs)
>>>>>>
>>>>>> Haven't looked at *any* of the code but hopefully that might point
>>>>>> someone in a useful direction.
>>>>>>
>>>>>> Richard.
>>>>>>
>>>>>
>>>>> I'd need to check, but I doubt this error has anything to do with the
>>>>> symlink.
>>>>>
>>>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/otY1UkS9f4w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/d495fecf-749b-409c-b9a5-efac078ec31b%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/d495fecf-749b-409c-b9a5-efac078ec31b%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPaoLTeYUj1_S_CG1PRc-K40EKmjcw8wJeBAQE7XDLCGoSMw%40mail.gmail.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

[Tom Fennelly]

Hey Ian. Thanks for the video.

After running the build, please get the contents of
./blueocean-dashboard/target/jenkins-js-extension.jsx and attach it back
here.

Looks like we need a fix we need a fix in
js-extensions/@jenkins-cd/subs/extensions-bundle.js#L120 to stop it
translating the paths to the system format. It's an easy fix.

On 2 June 2016 at 17:51, Ian Ceicys <iancei...@gmail.com> wrote:

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

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

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

[Tom Fennelly]

The error 

java.io.IOException: Dependency blueocean-commons (1.0-SNAPSHOT), 
blueocean-web (1.0-SNAPSHOT) doesn't exist

... strongly suggests that "all" of the plugins are not built before doing 
hpi:run.

To fix this ... run "mvn clean install" from the top level folder of the 
blueocean repo clone i.e. the parent folder ot "blueocean-commons", 
"blueocean-rest" etc. After getting a successful here, cd into 
"blueocean-plugin" (sibling dir of "blueocean-rest" etc --- yes, it's 
confusing because the repo also has this name ... we will fix this) and run 
"mvn hpi:run".

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

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3b6f42cf-6161-4f25-9751-7e2e74274159%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

[Tom Fennelly]

On Tuesday, 31 May 2016 06:04:44 UTC+1, Richard Bywater wrote:
>
> I assume the cause of the issue is:
> "Cannot find module '..srcmainjs/AdminNavLink.jsx"
>
> It looks like something is trying to write a string probably started as 
> "..\src\main\js/AdminNavLink.jsx" and its entered something like Java which 
> has seen those backslashes as escape characters (and hence ended up as 
> srcmainjs)
>
> Haven't looked at *any* of the code but hopefully that might point someone 
> in a useful direction.
>
> Richard.
>

I'd need to check, but I doubt this error has anything to do with the 
symlink. 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/10e83b50-25a1-4fb9-a699-578a27e93fd3%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

[Tom Fennelly]

On Tuesday, 31 May 2016 05:22:13 UTC+1, Michael Neale wrote:
>
>
> As far as I know the platform version of npm/node should not be needed, 
> and thus the version not matter - right Tom? 
>

Right, the build gets a fixed local version of node and npm and uses that. 
The version installed on the machine "should not" matter (yeah  famous 
last words).

-- 
You received this message because you are 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/17b44c4b-3a30-424e-a78f-1ca48bef0a5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] Test reporting UI

[Tom Fennelly]

On Tuesday, May 31, 2016 at 2:13:29 AM UTC+1, Robert Collins wrote:
>
> Its a fairly massive Jenkins Job Builder setup. 
>
> http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs
>  
>

Hey Rob.

And how does the test reporting appear for this?

-- 
You received this message because you are 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/b91f3554-a845-4c53-b591-13f7c92c5fb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Jenkins WebUI

[Tom Fennelly]

Ah ... I didn't look at remodal in detail and so didn't see that it was a
jQuery plugin. You'd think that would be the first thing they'd highlight
in their docs ;)

So ... the fact that it is a jQuery plugin does complicate things a bit. We
do not want to use jQuery in the normal way within Jenkins i.e. expose it
as a global. That causes all sorts of problems that are really hard to
solve once you go down that road. It has caused problems in Jenkins in the
past where we are still living with the consequences now today (e.g. the
prototypejs cancer).

Anyway ... I'm guessing that remodal assumes there's a jQuery bound to the
global scope. We would want remodal to not make that assumption and,
instead, get and deocorate it's own instance of jQuery. Doing it that way
makes sure that the remodal in use by Jenkins is something that has it's
own jQuery (and so no clashes with other jQuery plugins) that's not bound
to the global scope i.e. is not going to effect anything else in Jenkins
and is not going to be effected by anything else in Jenkins. So, it would
mean creating remodal equivalent of bootstrap-detached
.

On 30 May 2016 at 09:25, Samat Davletshin  wrote:

> I committed my changes to my fork here.
> 
> So do you advise to make a branch and re-upload changes there?
>
> Regarding the library I just added css and js code to random existing
> files (hudson-behavior.js and style.css) for testing, hoping to redo it
> later. I was thinking that it is just like bootstrap library - only css and
> js files for styling and behavior. Should it be added as bootstrap? Just
> seems to me that there is no single instance of "remodal" there to require
> as it is in jQuery. Is bootstrap getting required the same way?
> I am sorry, I just don't quite understand the procedure.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/fk5deO_SszU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/ee1f281e-473a-4820-9d07-b26cb302692f%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/CA%2BbPaoKuN%2BD%2BKz7pYijtu9BtUG6CdVqHLAJvyHy%2BcxfeZ46fNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSoC2016] Jenkins WebUI

[Tom Fennelly]

Hi Samat.

Can you create a branch and push your changes to it?

As for remodal ... you don't need to externalize it to get things working. 
Externalization is a runtime optimization that you can do later.

Looking at your changes, it looks like you are planning to use remodal via 
add-item.js ? add-item.js is built out of the "war" directory (see 
war/gulpfile.js for the bunble build instruction). So, the first thing you 
need to do is add a dependency on remodal, which you do by running "npm 
install --save remodal". After doing that, you should be able to "var 
remodal = require('remodal')" in the ad-item JavaScript code to get the 
remodal instance and do whatever it does.

Also  not sure I'd create the big .jelly file as you've done it. Maybe 
just outline how you are expecting this to work first and we can then 
figure out how best to implement it.

On Sunday, May 29, 2016 at 9:24:40 AM UTC+1, Samat Davletshin wrote:
>
> Hello,
> In previous post I showed that I could make a popup dialog window on home 
> page to create a new job. 
> However, I did it in a fast and dirty way and now I want to make it 
> properly.
>
> I am sorry if those are too simple questions. However, I would appreciate 
> if you could at least link me to where I can read about how to do it.
>
> Currently I see 3 issues and I would like to have a hint on how to fix 
> them.
>
> 1. How do I add an external js, css library to js-modules 
>  or to js-libs 
>  so that I can require it on home 
> page?
>
> 2. For some reason, when I try to include my jelly file by  page="myjelly.jelly" /> it is not included. The myjelly file is in the same 
> folder as the file (sidepanel.jelly) where I try to include it. If I just 
> insert the same jelly in sidepanel file between  files it works.
>
> 3. Labels like ${%ItemName.label} are not replaced by the corresponding 
> string as you can see on GIF.
>

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

Re: Pipeline View Plugin

[Tom Fennelly]

Nice work Sergei.

On Monday, March 21, 2016 at 6:52:04 AM UTC, Sergei Egorov wrote:
>
> Hey everyone, 
>
> Yesterday I decided to publish sources for my pipeline visualization 
> plugin: https://github.com/bsideup/jenkins-pipeline-view
>
> 
>
>
> What's cool about it? 
> First of all, it *can handle any graph* provided by pipeline because it 
> uses very powerful *JS graph library* to position steps. 
> Also, it's a *React* application, written in *ES7* (not even ES6!), with 
> ImmutableJS and RxJS inside - so hipsters will be happy :D But in fact, it 
> means that it's damn easy to develop this plugin and provide more 
> functionality. 
> I use *Webpack* to bundle everything (JS, CSS, fonts, images, SVG icons) 
> in one single pipe.js file. *No Jenkins JS Modules*, no conflicts, no 
> impact on others. Even CSS will not conflict because of *CSS-modules* ( 
> http://glenmaddern.com/articles/css-modules )
> All icons are SVG ones and look good on any screen, retina or not, and any 
> zoom level.
>
> I use Jackson on the backend side to serialize FlowNodes and their 
> actions. *Why Jackson?* Because it was much easier to implement 
> serialization of selected (non-exposed) fields and class info included 
> compared to Stapler. I saw something were done about classinfo in Stapler, 
> but at the moment of creation of this plugin, it wasn't delivered to 
> Jenkins core yet. Also, *almost none of the Pipeline actions are 
> @Expose-d*.
>
> I use *gradle-jpi-plugin* instead of Maven because it's much easier to 
> describe some complex build process with Gradle, especially when frontend 
> build is involved. In fact, it's just one line:
>
> https://github.com/bsideup/jenkins-pipeline-view/blob/954b895b6574cdf34815ff94a4a8db3ad3811aeb/build.gradle#L61
>
>
> Future development
> Will I continue to develop it? Definitely! Here, *at ZeroTurnaround*, we 
> use Jenkins a lot, and eventually we will migrate to the pipelines, and 
> proper visualization of the process is a must for us. And feel free to 
> contribute as well, it's really a good chance to learn *modern JS stack* as 
> well :)
>
>
>
> Best regards,
> Sergei Egorov
>

-- 
You received this message because you are 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/dc12f555-426d-4fdc-9361-95d5f34bb1e3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Meet jenkins.io

[Tom Fennelly]

Really nice. Thanks guys!!

On Thursday, March 24, 2016 at 12:58:35 PM UTC, Manuel Recena Soto wrote:
>
> CONGRATULATIONS!
>
> 2016-03-24 11:38 GMT+01:00 Krishna Gundala  >:
>
>> Excellent Work.. Kudos folks...
>> You rock Tyler..
>> Very Nice Website..
>>
>> ---
>>  
>>
>> Mohan Krishna Gundala
>> [image: https://]about.me/gmk.india
>>
>> 
>>   
>>  
>>
>> On Thu, Mar 24, 2016 at 2:31 PM, Baptiste Mathus > > wrote:
>>
>>> +1, congrats to everyone involved, and especially thanks to you Tyler. 
>>> Really nice website.
>>>
>>> 2016-03-24 6:23 GMT+00:00 domi :
>>>
 Really nice work!!!
 /Domi

 > On 24 Mar 2016, at 07:02, R. Tyler Croy  wrote:
 >
 > I finished up the final work for migration from 
 https://jenkins-ci.org to
 > https://jenkins.io today. The final step of the switchover was to 
 redirect
 > non-mapped URLs from jenkins-ci.org over to jenkins.io.
 >
 >
 > This project has been a tremendous amount of work with Gus Reiber, 
 Baptiste
 > Mathaus, James Dumay, Daniel Beck, Oleg Nenashev  and a number of 
 other
 > contributors filling in the new website with CSS, Haml, and most 
 importantly
 > AsciiDoc (for documentation!)
 >
 >
 > Some of the features of jenkins.io that are important to me, I'd 
 like to share:
 >
 > * Visual priority given to the LTS release line (yay)
 > * Built-in support for three layers of documentation: solution pages, 
 getting
 >   started guides and the "handbook".
 > * Visual elements to highlight upcoming events
 > * Certificates automated via letsencrypt.org (this is my favorite ;))
 >
 > The site is statically generated and contributions are welcome here:
 >
 >
 >
 > As I mentioned in our last project meeting, migration of other 
 properties such
 > as wiki.jenkins-ci.org to the jenkins.io domain will take a bit more 
 time. This
 > is an important first step however!
 >
 >
 >
 > Cheers
 > - 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-de...@googlegroups.com .
 > To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/20160324060209.GB15060%40blackberry.coupleofllamas.com
 .
 > For more options, visit https://groups.google.com/d/optout.

 --
 You received this message because you are subscribed to the Google 
 Groups "Jenkins Developers" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to jenkinsci-de...@googlegroups.com .
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-dev/509BAC1C-7F4D-47B6-85BA-5964EF6695DE%40fortysix.ch
 .
 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/CANWgJS7E9aiyFAHqpzSszv_sN%3DynoZE0Wt466t%2Bq%3DPN_8yNKZw%40mail.gmail.com
>>>  
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAMszB6yJ0aAZ94GaYke96rGmAXZvOdy3FLLBOgkNAF7iaxD27Q%40mail.gmail.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Manuel Recena Soto
> * manuelrecena.com [/blog]
> * linkedin.com/in/recena
>

-- 
You received this message 

Re: Job configuration page navigation with Tabs - Jenkins 2.0

[Tom Fennelly]

Thanks Antonio.

Daniel merged these changes to the 2.0 branch. There's a build available at
https://jenkins.ci.cloudbees.com/job/core/job/jenkins-core/3924/ if others
want to test it out (especially those running on Windows ... IE etc).

On 15 February 2016 at 12:52, Antonio Muñiz <amu...@cloudbees.com> wrote:

> Tested:
>
>  1. Install wizard with recommended plugins
>  2. Install wizard with custom plugins configuration (I miss lots of
> plugins in the list - but I think there is a process to decide what to
> include there (?))
>  3. Tabbed configuration page in jobs
>
> BTW loving the look and feel of the install wizard and the search bar in
> job config page! Nice!
>
>
> On Thu, Feb 11, 2016 at 9:37 PM, Tom Fennelly <tom.fenne...@gmail.com>
> wrote:
>
>> It would be great if one or more people could get the PR builder build
>> from https://github.com/jenkinsci/jenkins/pull/2006, take it for a spin
>> and let us know if they encounter any issues. 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/f018803f-73c3-4c42-a64b-9216cbb289fe%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/f018803f-73c3-4c42-a64b-9216cbb289fe%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.
>
> --
> 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/tXursfAKz7M/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/CAJc7kzShvOuuTYJ-bcc-ZGqLY4tQnbJYQ%3D19O0jRDabskZCv6w%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzShvOuuTYJ-bcc-ZGqLY4tQnbJYQ%3D19O0jRDabskZCv6w%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Job configuration page navigation with Tabs - Jenkins 2.0

[Tom Fennelly]

It would be great if one or more people could get the PR builder build 
from https://github.com/jenkinsci/jenkins/pull/2006, take it for a spin and 
let us know if they encounter any issues. 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/f018803f-73c3-4c42-a64b-9216cbb289fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can someone create a new jenkinsci repo please ("pipeline-rest-api-plugin")

[Tom Fennelly]

Thanks Daniel. I agree with you. Creating the repo in my own account and
then forking into jenkinsci just seemed like a sidestepping of the rules to
me. It seemed strange that one cannot create a new repo in jenkinsci, but
can fork an existing one into it.

On 2 February 2016 at 20:55, Daniel Beck <m...@beckweb.net> wrote:

>
> On 02.02.2016, at 21:42, Tom Fennelly <tom.fenne...@gmail.com> wrote:
>
> > What are you suggesting I fork to get to there? Are you suggesti ng that
> I create a repo in my own account and fork it into jenkinsci?
>
> Yes, and only (request to) fork once there is actually something in your
> repo, as documented[1].
>
> My favorite repos in the jenkinsci organization:
> https://github.com/jenkinsci?utf8=%E2%9C%93=jenkinsmobi
>
> If those began life in Luca's account and were only forked once the repos
> contained something (i.e. code), we'd either have a) no repos or b) repos
> with content. IMO either is better than what we have: empty repos that may
> or may not get filled (well, by now, the latter, so we should probably rm
> them).
>
> Again, this is just my preference based on this possible problem when
> creating repos instead of forking. Additionally, if nothing ever gets
> added, it's difficult to determine why/for whom they were created.
>
> 1:
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites
>
> --
> 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/z5BG3Ol2IhI/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/90928C57-D6DF-474B-A38B-C73C0F106763%40beckweb.net
> .
> 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/CA%2BbPaoJ6eBuZ10nsHbMidaNat7UyS5A6ZdvAiKySKusv%2B%2B2idQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can someone create a new jenkinsci repo please ("pipeline-rest-api-plugin")

[Tom Fennelly]

Well, we were a bit premature about creating the other repo, but it is
going to be used. What do you mean about forking a repo that already has
content? Do you mean use a single repo for multiple things as a repo saving
device? I don't mind doing that but I know others will get the underwear in
a bundle :)

On 2 February 2016 at 20:19, Daniel Beck <m...@beckweb.net> wrote:

> Due to the significant number of unused repositories (almost three weeks
> and not a single real commit in the one you mention) I'd prefer if you
> forked a repo that already has content.
>
> On 02.02.2016, at 21:12, Tom Fennelly <tom.fenne...@gmail.com> wrote:
>
> > Ah ok ... thanks Baptiste. I'll look see what I need to do.
> >
> > On 2 February 2016 at 18:56, Baptiste Mathus <m...@batmat.net> wrote:
> > IIRC you've been voiced some weeks ago. So you could do it yourself if
> you want?
> >
> > -- Baptiste
> >
> > Le 2 févr. 2016 7:21 PM, "Tom Fennelly" <tom.fenne...@gmail.com> a
> écrit :
> > We created https://github.com/jenkinsci/pipeline-stage-view-plugin a
> week or so ago, but also need "pipeline-rest-api-plugin". Would someone
> with privs mind creating it please?
> >
> > --
> > You received this message because you are 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/dbfd776e-be7d-42d3-bd87-8de787899273%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/z5BG3Ol2IhI/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/CANWgJS52ajM8J_QVyY-J7XwXTv4b9TC7%3Dpph%3Daf5TXVpu78UBA%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/CA%2BbPaoJH9UwrgunHatJ8Sy%2Bj8Pn45nNQPUsuWHX75Aq5kE46dA%40mail.gmail.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/z5BG3Ol2IhI/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/E3DC1DF0-A946-47BB-BBD8-16E49DC7E93D%40beckweb.net
> .
> 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/CA%2BbPaoJVzrnFEnd1aNG-ey65yYFpogMG3pS05shAMmnvQ_364g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Can someone create a new jenkinsci repo please ("pipeline-rest-api-plugin")

[Tom Fennelly]

We created https://github.com/jenkinsci/pipeline-stage-view-plugin a week 
or so ago, but also need "pipeline-rest-api-plugin". Would someone with 
privs mind creating it please?

-- 
You received this message because you are 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/dbfd776e-be7d-42d3-bd87-8de787899273%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can someone create a new jenkinsci repo please ("pipeline-rest-api-plugin")

[Tom Fennelly]

Ah ok ... thanks Baptiste. I'll look see what I need to do.

On 2 February 2016 at 18:56, Baptiste Mathus <m...@batmat.net> wrote:

> IIRC you've been voiced some weeks ago. So you could do it yourself if you
> want?
>
> -- Baptiste
> Le 2 févr. 2016 7:21 PM, "Tom Fennelly" <tom.fenne...@gmail.com> a écrit :
>
>> We created https://github.com/jenkinsci/pipeline-stage-view-plugin a
>> week or so ago, but also need "pipeline-rest-api-plugin". Would someone
>> with privs mind creating it please?
>>
>> --
>> You received this message because you are 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/dbfd776e-be7d-42d3-bd87-8de787899273%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/dbfd776e-be7d-42d3-bd87-8de787899273%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/z5BG3Ol2IhI/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/CANWgJS52ajM8J_QVyY-J7XwXTv4b9TC7%3Dpph%3Daf5TXVpu78UBA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS52ajM8J_QVyY-J7XwXTv4b9TC7%3Dpph%3Daf5TXVpu78UBA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Can someone create a new jenkinsci repo please ("pipeline-rest-api-plugin")

[Tom Fennelly]

On 2 February 2016 at 20:32, Daniel Beck  wrote:
>
> The problem we sometimes have is that someone creates/asks for creation of
> a repo, and then does nothing to add content.


I get the objective.


> The safer approach therefore is to fork another repo. Since forking an
> effectively empty repo would be pointless and have the same problem,
> forking should only be done once actual content has been pushed to that
> repo.
>

I don't get this part. I ultimately want to end up with a
"jenkinsci/pipeline-rest-api-plugin" repo. What are you suggesting I fork
to get to there? Are you suggesti ng that I create a repo in my own account
and fork it into jenkinsci?

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

Re: Job configuration page navigation with Tabs - Jenkins 2.0

[Tom Fennelly]

There's a proper PR now: #2006
<https://github.com/jenkinsci/jenkins/pull/2006>, so there should be a
runnable build soon.

On 25 January 2016 at 11:55, Robert Sandell <rsand...@cloudbees.com> wrote:

> Looks good Tom! Thanks for explaining.
>
> I'd like two Big Macs, a large bucket of wings and a diet coke please ;)
>
> /B
>
> On Sat, Jan 23, 2016 at 11:23 AM, Tom Fennelly <tom.fenne...@gmail.com>
> wrote:
>
>> I added a JIRA for phase 2 (and beyond)
>> <https://issues.jenkins-ci.org/browse/JENKINS-32578>.
>>
>> On 23 January 2016 at 08:51, Tom Fennelly <tom.fenne...@gmail.com> wrote:
>>
>>> Thanks Surya.
>>>
>>> I'll add finder auto-complete to the list of features to try add.
>>>
>>> On 22 January 2016 at 23:58, Surya Gaddipati <suryapraka...@gmail.com>
>>> wrote:
>>>
>>>> Great Stuff Tom.
>>>>
>>>> I was worried about loosing cmd+f but there is a find box.
>>>>
>>>> One suggestion I have would be to auto complete the find box so user
>>>> doesn't have to look through what is highlighted.
>>>>
>>>> Surya
>>>>
>>>> On Thursday, January 21, 2016 at 2:11:06 PM UTC-6, Tom Fennelly wrote:
>>>>>
>>>>> I've been working on the Job configuration pages a bit, trying to make
>>>>> them easier to use. The goals I have for this are:
>>>>>
>>>>>1. NOT break form submission.
>>>>>2. NOT break plugin backward compatibility.
>>>>>3. Improve usability by visually breaking up long configurations,
>>>>>hopefully making it easier to quickly see the sections and navigate 
>>>>> between
>>>>>them (Vs scrolling etc).
>>>>>4. Provide other usability tweaks where possible, but without
>>>>>breaking anything.
>>>>>5. Make things optional, allowing people to easily switch back to
>>>>>the "classic" Job config view.
>>>>>
>>>>> I've been labeling the work done so far as "phase 1" because I know
>>>>> this effort might need to go through a few iterations before we get it
>>>>> right.
>>>>>
>>>>> Some resources:
>>>>>
>>>>>- The JIRA: JENKINS-32357
>>>>><https://issues.jenkins-ci.org/browse/JENKINS-32357>.
>>>>>- A demo video: https://youtu.be/uOiclX_W37Q
>>>>>- A temporary PR on which to view the changes:
>>>>>https://github.com/tfennelly/jenkins/pull/1 . Please comment here
>>>>>though. I will be closing that PR.
>>>>>
>>>>> Please note that this is a WiP. It's still a bit of an experiment and
>>>>> we want to know what people think of it i.e. do people believe this is an
>>>>> improvement worth pursuing more and adding to Jenkins 2.0 etc.
>>>>>
>>>> --
>>>> 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/tXursfAKz7M/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/49c4a83b-efc6-4d5d-9dee-71dd091ff451%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/49c4a83b-efc6-4d5d-9dee-71dd091ff451%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPao%2BQuAMvTtY2rt%3D%2BMB8%2BvhzJi0rRmx7%2BxQbmndBuiOL%2BKw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPao%2BQuAMvTtY2rt%3D%2BMB8%2BvhzJi0rRmx7%2BxQbmndBuiOL%2BKw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> For more op

Re: Office Hour: The State of JavaScript development in Jenkins

[Tom Fennelly]

Thanks Daniel.

I believe strongly that we can make meaningful user experience improvements
to Jenkins, but it will require having more weapons in our arsenal in terms
of how we build plugins etc. This is what we'll be talking about in this
weeks office hour. It will be a developer-focused session where we'll start
off by talking a little about how UI development has traditionally been
done in Jenkins, before moving on to some newer patterns and tools that we
have been developing over the last few months that let us make use of a
wider range of more modern client-side development tools (some of which
Daniel linked to in his email). We'll also dissect and run some sample
plugins that show these newer client-side dev tools in action.

By the end of the session, I'm hoping people will have seen enough to stoke
their interest into giving some of these tools and patterns a try in their
plugins. I'm also hoping to hear the opinions of others on these topics.

As for posting comments or questions during the session, probably the best
place to do that is on the #jenkins IRC channel. I'm not the best at
multi-tasking while on these calls, so hopefully people can help me out
there.

Regards,

Tom.

On 25 January 2016 at 20:29, Daniel Beck <m...@beckweb.net> wrote:

> Hi everyone,
>
> Tom Fennelly will host this week's office hour, on Wednesday 11am PST, and
> he's going to talk about the current state of JavaScript in Jenkins and how
> plugin developers can use it. This includes things like…
>
> • https://github.com/jenkinsci/js-modules
> • https://github.com/jenkinsci/js-libs
> • Cool reusable JS stuff in https://github.com/jenkinsci/jenkins/pull/1995
>
> More about office hours:
> https://wiki.jenkins-ci.org/display/JENKINS/Office+Hours
>
> The wiki will have the links to watch and join before the event starts.
>
> Daniel
>
>

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

Re: Job configuration page navigation with Tabs - Jenkins 2.0

[Tom Fennelly]

I added a JIRA for phase 2 (and beyond)
<https://issues.jenkins-ci.org/browse/JENKINS-32578>.

On 23 January 2016 at 08:51, Tom Fennelly <tom.fenne...@gmail.com> wrote:

> Thanks Surya.
>
> I'll add finder auto-complete to the list of features to try add.
>
> On 22 January 2016 at 23:58, Surya Gaddipati <suryapraka...@gmail.com>
> wrote:
>
>> Great Stuff Tom.
>>
>> I was worried about loosing cmd+f but there is a find box.
>>
>> One suggestion I have would be to auto complete the find box so user
>> doesn't have to look through what is highlighted.
>>
>> Surya
>>
>> On Thursday, January 21, 2016 at 2:11:06 PM UTC-6, Tom Fennelly wrote:
>>>
>>> I've been working on the Job configuration pages a bit, trying to make
>>> them easier to use. The goals I have for this are:
>>>
>>>1. NOT break form submission.
>>>2. NOT break plugin backward compatibility.
>>>3. Improve usability by visually breaking up long configurations,
>>>hopefully making it easier to quickly see the sections and navigate 
>>> between
>>>them (Vs scrolling etc).
>>>4. Provide other usability tweaks where possible, but without
>>>breaking anything.
>>>5. Make things optional, allowing people to easily switch back to
>>>the "classic" Job config view.
>>>
>>> I've been labeling the work done so far as "phase 1" because I know this
>>> effort might need to go through a few iterations before we get it right.
>>>
>>> Some resources:
>>>
>>>- The JIRA: JENKINS-32357
>>><https://issues.jenkins-ci.org/browse/JENKINS-32357>.
>>>- A demo video: https://youtu.be/uOiclX_W37Q
>>>- A temporary PR on which to view the changes:
>>>https://github.com/tfennelly/jenkins/pull/1 . Please comment here
>>>though. I will be closing that PR.
>>>
>>> Please note that this is a WiP. It's still a bit of an experiment and we
>>> want to know what people think of it i.e. do people believe this is an
>>> improvement worth pursuing more and adding to Jenkins 2.0 etc.
>>>
>> --
>> 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/tXursfAKz7M/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/49c4a83b-efc6-4d5d-9dee-71dd091ff451%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/49c4a83b-efc6-4d5d-9dee-71dd091ff451%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Re: Job configuration page navigation with Tabs - Jenkins 2.0

[Tom Fennelly]

On 22 January 2016 at 10:57, Robert Sandell  wrote:

> The changes you showed in the video is in my mind not worthy of a 2.0
> label but could have been done in a weekly.
>

Ok, so reading between the lines here, it sounds like you are saying that
you believe a change worthy of a 2.0 label needs to be a change that can't
be made in 1.x i.e. a breaking change. To the best of my knowledge, that is
not what 2.0 is about, but does sound like 3.0.

Anyway ... 1.x, 2.x, 3.x debates aside... I did say this was still a WiP,
but it sounds like it's not something that tickles your fancy, which is
fine ... this is what we're trying to find out ... are people for or
against it.

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

Re: Job configuration page navigation with Tabs - Jenkins 2.0

[Tom Fennelly]

It would of course be possible to put this into 1.x (anything is possible),
but it would need to be reworked to use prototypejs etc (yeuk). At the
moment, it builds on top of the newer JavaScript building blocks that are
hopefully going in with the new Install Wizard (PR #1995
<https://github.com/jenkinsci/jenkins/pull/1995>). Doing it the older "1.x
way" would change it into a much uglier beast (from an impl pov).

On 22 January 2016 at 12:37, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> I really like this change... I also suspect that it would be fine in a
> weekly... but if you want to save it for 2.0 that's your call!
>
> On 22 January 2016 at 11:48, Tom Fennelly <tom.fenne...@gmail.com> wrote:
>
>> On 22 January 2016 at 10:57, Robert Sandell <rsand...@cloudbees.com>
>> wrote:
>>
>>> The changes you showed in the video is in my mind not worthy of a 2.0
>>> label but could have been done in a weekly.
>>>
>>
>> Ok, so reading between the lines here, it sounds like you are saying that
>> you believe a change worthy of a 2.0 label needs to be a change that can't
>> be made in 1.x i.e. a breaking change. To the best of my knowledge, that is
>> not what 2.0 is about, but does sound like 3.0.
>>
>> Anyway ... 1.x, 2.x, 3.x debates aside... I did say this was still a WiP,
>> but it sounds like it's not something that tickles your fancy, which is
>> fine ... this is what we're trying to find out ... are people for or
>> against it.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPao%2BBKrFUJ1LRiN%2BWNVGpCZntYXPjK%2B3XRE1Cj%2BVsVZdc1w%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPao%2BBKrFUJ1LRiN%2BWNVGpCZntYXPjK%2B3XRE1Cj%2BVsVZdc1w%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/tXursfAKz7M/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%2BnPnMwGSs9T9b0sAR58BtGAAw_t4%3DNtA91FVr6vGy3dHGJMzQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMwGSs9T9b0sAR58BtGAAw_t4%3DNtA91FVr6vGy3dHGJMzQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Job configuration page navigation with Tabs - Jenkins 2.0

[Tom Fennelly]

Sorry ... something that was not clear/obvious in my last post ... the new
Install Wizard (PR #1995 <https://github.com/jenkinsci/jenkins/pull/1995>)
is also targeted for 2.0.

On 22 January 2016 at 12:50, Tom Fennelly <tom.fenne...@gmail.com> wrote:

> It would of course be possible to put this into 1.x (anything is
> possible), but it would need to be reworked to use prototypejs etc (yeuk).
> At the moment, it builds on top of the newer JavaScript building blocks
> that are hopefully going in with the new Install Wizard (PR #1995
> <https://github.com/jenkinsci/jenkins/pull/1995>). Doing it the older
> "1.x way" would change it into a much uglier beast (from an impl pov).
>
> On 22 January 2016 at 12:37, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> I really like this change... I also suspect that it would be fine in a
>> weekly... but if you want to save it for 2.0 that's your call!
>>
>> On 22 January 2016 at 11:48, Tom Fennelly <tom.fenne...@gmail.com> wrote:
>>
>>> On 22 January 2016 at 10:57, Robert Sandell <rsand...@cloudbees.com>
>>> wrote:
>>>
>>>> The changes you showed in the video is in my mind not worthy of a 2.0
>>>> label but could have been done in a weekly.
>>>>
>>>
>>> Ok, so reading between the lines here, it sounds like you are saying
>>> that you believe a change worthy of a 2.0 label needs to be a change that
>>> can't be made in 1.x i.e. a breaking change. To the best of my knowledge,
>>> that is not what 2.0 is about, but does sound like 3.0.
>>>
>>> Anyway ... 1.x, 2.x, 3.x debates aside... I did say this was still a
>>> WiP, but it sounds like it's not something that tickles your fancy, which
>>> is fine ... this is what we're trying to find out ... are people for or
>>> against it.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPao%2BBKrFUJ1LRiN%2BWNVGpCZntYXPjK%2B3XRE1Cj%2BVsVZdc1w%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPao%2BBKrFUJ1LRiN%2BWNVGpCZntYXPjK%2B3XRE1Cj%2BVsVZdc1w%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/tXursfAKz7M/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%2BnPnMwGSs9T9b0sAR58BtGAAw_t4%3DNtA91FVr6vGy3dHGJMzQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMwGSs9T9b0sAR58BtGAAw_t4%3DNtA91FVr6vGy3dHGJMzQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

Job configuration page navigation with Tabs - Jenkins 2.0

[Tom Fennelly]

I've been working on the Job configuration pages a bit, trying to make them 
easier to use. The goals I have for this are:

   1. NOT break form submission.
   2. NOT break plugin backward compatibility.
   3. Improve usability by visually breaking up long configurations, 
   hopefully making it easier to quickly see the sections and navigate between 
   them (Vs scrolling etc).
   4. Provide other usability tweaks where possible, but without breaking 
   anything.
   5. Make things optional, allowing people to easily switch back to the 
   "classic" Job config view.

I've been labeling the work done so far as "phase 1" because I know this 
effort might need to go through a few iterations before we get it right. 

Some resources:

   - The JIRA: JENKINS-32357 
   .
   - A demo video: https://youtu.be/uOiclX_W37Q
   - A temporary PR on which to view the 
   changes: https://github.com/tfennelly/jenkins/pull/1 . Please comment here 
   though. I will be closing that PR.

Please note that this is a WiP. It's still a bit of an experiment and we 
want to know what people think of it i.e. do people believe this is an 
improvement worth pursuing more and adding to Jenkins 2.0 etc.

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

Re: Re-doing the 2.0 branch

[Tom Fennelly]

The plugin selection wizard (and plugin unbundling) PR is back 
... https://github.com/jenkinsci/jenkins/pull/1995

The current set of plugins in the wizard are just those that are currently 
bundled in Jenkins 1.x. The actual list needs to be decided. Let the debate 
begin 

-- 
You received this message because you are 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/44544ae9-0405-447b-9b63-f5a01ee3fca1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Highcharts usage in Jenkins Plugin - Licence

[Tom Fennelly]

On 25 November 2015 at 19:28, Michael Prankl <eidotterm...@gmail.com> wrote:

> @ Tom Fennelly:
>
> I already took a closer a look at Google Charts. One thing that I didn't
> like is that you're not allowed to host the Google Chart Library on your
> own server. So the plugin users must always have a working internet
> connection (maybe in some company intranets that may not be the case).
>

Ah that sucks.

I had a quick look at this:
http://socialcompare.com/en/comparison/javascript-graphs-and-charts-libraries
... hard to believe there are so many of them.

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

Re: Highcharts usage in Jenkins Plugin - Licence

[Tom Fennelly]

On 25 November 2015 at 10:10, Ullrich Hafner 
wrote:

> Wouldn’t it make sense to ask what a commercial license would cost for the
> Jenkins project so that users of Jenkins don’t need to bother about the
> license at all?
>

The Jenkins project buying a license (which it wouldn't need to anyway) to
use it would only entitle that org to use it. It would not cover commercial
entities that use Jenkins (and install this plugin).

IMO, using Highcharts is a bad idea because:

   1. It will limit the adoption of this plugin, which is a real pity imo
   as it looks to be really useful to a lot of people. Many commercial
   entities will not want the bother of managing yet another license.
   2. In order to be fair to end users, I think the plugin needs to do
   something that would force users to acknowledge that they are using
   software for which they require a license e.g. a first time popup that the
   need to "Accept" before using. That's kind suckie imo.

Is there a reason why something like Google Charts could not be used here
(or some other OSS lib)? Is Highcharts really so much better?

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

Re: Highcharts usage in Jenkins Plugin - Licence

[Tom Fennelly]

Hi Michael.

Off topic from your email subject, but I'd be interested in talking to you 
about how you're implementing this plugin and how you're using the JS libs. 
I know you've already contributed to jenkins-js-libs 
, but curious to get your thoughts 
etc. Maybe I can ping you directly and we can arrange to have a chat?

Regards,

Tom.

On Monday, November 23, 2015 at 1:15:57 PM UTC, Michael Prankl wrote:
>
> Hi,
>
> I'm currently working on a plugin, in which I would like to use Highcharts 
>  as a charting engine (attached a screenshot).
> The Highcharts FAQ states that Highcharts can be used under the Creative 
> commons licence "Attribution-NonCommercial 3.0 Unported (CC BY-NC 3.0)" 
> and if you are a "non-profit organization".
>
> So my questions are:
> Is Jenkins-CI a "non-profit organization"?
> Am I good to go and use Highcharts under the creative commons licence?
> Are there already Jenkins plugins which use Highcharts?
>
> Thanks
> Michael
>  
>
>
>

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

Please can I get push privs on the following repos ...

[Tom Fennelly]

 

   - https://github.com/jenkinsci/js-modules
   - https://github.com/jenkinsci/js-builder
   
I'm the maintainer of these repos (they were forked from me by KK).

-- 
You received this message because you are 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/545e2e67-f5a2-4131-b175-5915fa89947d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: JS Libs

[Tom Fennelly]

Hi Manuel.

Rather than saying they "replace" anything, I'd prefer to say that they are 
a different approach to using JS libraries in the Jenkins UI and that you 
would use one or the other, but not both.

The older plugins that you linked to are for use in the "traditional" (bind 
to global scope) mode where in the case of jQuery, there can only be one 
version in play at a given time. The approach in js-libs is that they are 
all "detached" from the global scope (allowing multiple "concurrent" 
versions etc) + are usable in a CommonJS type modular JS system. If 
interested, there's more info on these topics on jenkins-js-modules 
 and jenkins-js-builder 
.

-- 
You received this message because you are 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/6c9bf44c-5570-46d8-883d-21378ebaa524%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Please can I get push privs on the following repos ...

[Tom Fennelly]

Thanks Daniel.

On 24 November 2015 at 13:03, Daniel Beck <m...@beckweb.net> wrote:

> Makes sense. I gave you push access.
>
> On 24.11.2015, at 12:15, Tom Fennelly <tom.fenne...@gmail.com> wrote:
>
> > 
> >   • https://github.com/jenkinsci/js-modules
> >   • https://github.com/jenkinsci/js-builder
> > I'm the maintainer of these repos (they were forked from me by KK).
> >
> > --
> > You received this message because you are 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/545e2e67-f5a2-4131-b175-5915fa89947d%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/AhZ9floUqqg/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/E21B116E-1116-4F6A-A532-134662469584%40beckweb.net
> .
> 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/CA%2BbPao%2BrTYH9L4oWNDxwdPHeRpX3BacJxUkGXHkRQkSRv%2BhJpw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Refreshing the Jenkins UI

[Tom Fennelly]

Hi Kayn.

There's also an ongoing conversation about Jenkins 2.0. It's hoped that a 
big part of this will be improvements to the UX.  KK listed UX as being 
high on his wish list.

>From a UX perspective, we've been trying to put some things in place to 
help us do things better (using more modern tools, better patterns etc). 
See my early contribution on this topic to the Jenkins 2.0 thread 
<https://groups.google.com/d/msg/jenkinsci-dev/vbXK7JJekFw/iBcSiCJKBgAJ>. 
Hopefully it will help give some perspective.

Regards,

Tom.

On Thursday, October 8, 2015 at 2:24:40 PM UTC+1, Kayn Ty wrote:
>
> glad to hear it is still up!
> no problem with jelly, i am used to Twig template engine and Angularjs, it 
> should be not so different.
>
> I recommend to use NPM and Gulp for front-end workflow improovements (auto 
> refreshing localhost, compiling, concatenating, managing dependencies, 
> check test coverage).
> I personally prefer SASS than less to compile the css, it is more powerful 
> and fast.
> Jasmine is also a great companion to test things.
> bootstrap and font-awesome are also great sidekicks to theme with ease. 
> All these tools could be launched easily when you start from scratch by an 
> other one called Yeoman webapp generator ("yo" on NPM).
>
> so as a first step i cloned the official repo to my own github
> https://github.com/tykayn/jenkins
>
> i also found this uitheme plugin, 
> https://github.com/jenkinsci/uithemes-plugin maybe i would be more 
> efficient to contribute on this if i want to build a custom theme, but i 
> should first understand how to make a processor 
> <https://github.com/jenkinsci/uithemes-plugin/blob/master/processor> 
> module if i understood well the readme.
>
>
> Le mardi 6 octobre 2015 19:27:36 UTC+2, Gus Reiber a écrit :
>>
>> Hey Kayn!
>>Awesome.
>> Unfortunately, theming has died on the vine here a little bit. My friend 
>> and co-worker, Tom Fennelly had/has queued up some some core changes for 
>> Jenkins geared toward enabling LESS driven CSS to manipulate a significant 
>> portion of the Jenkins GUI, but that PR died in review.
>>
>> Since then, he and I with some guidance from KK and Daniel Beck have been 
>> looking for inroads to refactor the existing Jenkins DOM to be a little 
>> more semantic and refactor the Javascript to be a little more modern and a 
>> little more amenable to testing via Node.js and Jasmine.
>>
>> ...so the good news is that you are at the very front of the line for 
>> providing input on how all this should be done. The bad news is that at the 
>> moment, there isn't really any doc, largely because the enabling 
>> infrastructure isn't yet fully born.
>>
>> If you can tolerate some amount of work-in-progress vibe, feel free to 
>> contact me direction and I will do what I can to get you up and show you 
>> around, greiber(at-sign)cloudbees(dot-com).
>>
>> You can also follow my efforts (an any other Jenkins GUI efforts I am 
>> aware of) via Twitter: @gusreiber 
>> You can also follow me on Google+: plus.google.com/+GusReiberUI/posts
>>
>>
>>
>>
>>
>> On Tuesday, October 6, 2015 at 6:42:29 AM UTC-7, Kayn Ty wrote:
>>>
>>> hi folks,
>>> i would love to contribute to this UI refresh.
>>> i am looking for ressources to understand how it is organised and how to 
>>> test my new theme locally. (i know nothing about java, i am a front end dev)
>>> i can't find docs about theming, can you show me please ?
>>>
>>> Le lundi 26 mai 2014 15:54:21 UTC+2, Tom Fennelly a écrit :
>>>>
>>>> Hi guys.
>>>>
>>>> I've just started looking into ways in which we can "refresh" the look 
>>>> and feel of the Jenkins UI, as well as looking at tackling some of the 
>>>> main 
>>>> usability issues.  I've really only started, but have committed a small 
>>>> bit 
>>>> of code to a branch on github at 
>>>> https://github.com/tfennelly/jenkins/tree/ui-refresh.  As you might 
>>>> notice... Daniel Beck has already posted some good comments/feedback 
>>>> on the commit 
>>>> <https://github.com/tfennelly/jenkins/commit/d586be517616a3ba33ac11c6b5a85965d473c8ab>
>>>> .
>>>>
>>>> What I've experimented with so far:
>>>>
>>>>1. Tweaking the main layout in 
>>>>core/src/main/resources/lib/layout/layout.jelly (and added some CSS to 
>>>>style.css).  Everything was layed out with tables, so I changed that to 
>>>> use 
>>&g

Re: Jenkins-ci.org v.2 (for love or money!)

[Tom Fennelly]

Yep, this thread has been totally derailed. 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/6318bc9a-43f1-4fff-ad79-106c19e94d75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: theming jenkins

[Tom Fennelly]

On Wednesday, October 7, 2015 at 6:32:13 AM UTC+1, Oleg Nenashev wrote:
>
> Hi Kayn,
>
> I'm John Snow about web design, but any improvements about web interface & 
> custom themes may be useful.
>
> If you want to customize appearance of your own Jenkins instance:
>
>- There is a UI Themes plugin 
> from Tom Fennely (in Cc)
>
> Please note that the Jenkins core changes required to get this working 
(modularizations and parameterization of the CSS using LESS etc) were never 
pushed upstream. It was something I did as a POC and it seemed like people 
were not all that interested in it, so I didn't pursue it.

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

Re: Refreshing the Jenkins UI

[Tom Fennelly]

On Wednesday, October 7, 2015 at 6:09:17 AM UTC+1, Michael Neale wrote:
>
> I also think it would be great for those who are less into java to be able 
> to focus on the UI (as Kayn mentioned on another thread), a worthy goal. 
>

Right, using more modern JS frameworks + being able to upgrade them (+ 
being able to deprecate them when they become extinct) should help this. 
That said, because of how Jenkins is built, I don't think people will be 
totally able to avoid Java and Jelly unless they are really really lucky.

-- 
You received this message because you are 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/a28eea68-d743-4983-9dd1-a0a73b2012f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Improvement proposal for jenkinsci/jenkins repo review process

[Tom Fennelly]

On Monday, October 5, 2015 at 1:02:23 PM UTC+1, Daniel Beck wrote:
>
>
> On 05.10.2015, at 13:51, Tom Fennelly <tom.fe...@gmail.com > 
> wrote: 
>
> > I'm not even sure that was ever an agreed upon "rule" (thou shalt not 
> squash), but I do know there are people for and against it and nobody is 
> right (imo), so it should be the choice of the PR owner to do it or not 
> (without getting badgered either way). 
>
> The PR owner probably should not rewrite the PR history as this will lose 
> review comments AFAICT. And they generally cannot merge themselves.


That was why I said "once the review is completed". 

-- 
You received this message because you are 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/892aa0da-1b3e-46dc-bf3e-123c17a2cfe3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Improvement proposal for jenkinsci/jenkins repo review process

[Tom Fennelly]

I'm not sure about all of the labels, but +1 for the PR owner to be allowed 
(if they wish) perform a PR squash once the review has been completed.

I'm not even sure that was ever an agreed upon "rule" (thou shalt not 
squash), but I do know there are people for and against it and nobody is 
right (imo), so it should be the choice of the PR owner to do it or not 
(without getting badgered either way).

On Monday, October 5, 2015 at 11:59:15 AM UTC+1, Oleg Nenashev wrote:
>
> Hello,
>
> There are many open PRs in Jenkins core repo. Currently it's very hard to 
> perform reviews, because for every PR you need to go into and to see the 
> current status by going through the conversation. It would be great so 
> somehow show current statuses in the PR list.
>
> I propose to add the following labels:
>
>- needs-review (dark yellow)
>- needs-fix (orange)
>- needs-testcase (light orange)
>- needs-docs (ligh orange)
>- ready-for-merge (violet)
>   - Indicates that the PR has passed the review (e.g. "+1s and no 
>   responses during several days")
>   - A merger can merge the PR & squash it
>
> A similar approach is being used in Jenkins CERT team for a while. It 
> seems to be effective. 
>
> The approach could be also used in plugins. In the long-term it may be 
> possible to add overall PR status dashboards, which may be helpful for the 
> project.
>
> If there is no concerns, I'll go forward and add labels.
>
> Best regards, 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/b1140b91-d08b-4e62-991c-c338b83df306%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Plugin Install Wizard - check out the progress (video) ...

[Tom Fennelly]

On Friday, October 2, 2015 at 1:36:33 AM UTC+1, Daniel Beck wrote:
>
>
> On 01.10.2015, at 15:36, Victor Martinez  > wrote: 
>
> > - Does the plugin integrate well with Jenkins? Does it work well in 
> secured and distributed Jenkins? 
> >As I already mention "secured" shouldn't pruned any plugins as long 
> as those are heavily used by the community and it is an open source version 
>
> I think we'll have to agree to disagree here. If a plugin, without warning 
> you, undermines whatever security the admin sets up, it should not be 
> available in this dialog. 
>
> > - Are the features it provides useful to someone fairly new to Jenkins? 
> >What do you mean about someone fairly new to Jenkins? Configuration 
> as Code (Workflow, JobDSL or jenkins builder) will be fairly complex to 
> understand by someone new to Jenkins, even using  you use Workflow, don't 
> you think?Then some of those recommended plugins don't follow this 
> criteria. 
>
> You'll notice I left out plugins that, secured or not, are mostly useful 
> when scripting around in Jenkins internals. The kind of plugin that makes 
> people file issues like JENKINS-26416 or JENKINS-24790. For example, Groovy 
> Postbuild and Scriptler fall into this category. 
>
> Looking at the list of plugins you're showing me I can say with confidence 
> that this setup dialog is not meant for you, but that's okay -- it's not 
> meant for me either! It is for getting less (or in-)experienced users 
> started with a useful set of features, rather than dumping them into an 
> empty instance that doesn't even have their SCM. 
>

I think we all agree that the wizard should have a trimmed down list of 
"suggested" plugins, where the "suggested" plugins are a subset of "all" 
plugins and the "recommended" plugins are a subset of the "suggested" 
plugins:

   - "all" (> 1000 plugins)
  - "suggested" (< 100 plugins atm)
 - "recommended" (< 20 plugins atm)
  
I'd hope all would agree that having the wizard display "all" plugins (by 
default) is just plain nuts :) That's not going to help anyone (new or 
veteran Jenkins user). I'd hope all would agree that we just list/show the 
"suggested" plugins (by default).

So what do I mean by "by default" ? To me, the scrollable list of 
"suggested" plugins is most useful to new Jenkins users (and probably even 
new to CI/CD). I think it's really only new users that will NOT filter the 
list in some way - simply coz they're not sure what they're looking for and 
so wouldn't know what to filter on. To me, this is the only group to which 
the "suggested" list of plugins makes sense. Most other users will very 
likely know what they're looking  and so will filter the list Vs scrolling 
all the suggested plugins (~100 of).

I think once the user starts applying a filter to the selection (by typing 
in the search box) then we could actually filter on "all" Jenkins plugins 
(all 1000+ of them). In other words, we can think of the "suggested" 
plugins as just being the "default" filtered list.

-- 
You received this message because you are 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/c193938c-d62b-4940-a7a6-f7103ad4f351%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin Manager - Uninstalling/Disabling plugins that have active dependant plugins ???

[Tom Fennelly]

I Created PR #1847  for 
this.

Here's the changes in action: https://youtu.be/YMLKumX-kkI

-- 
You received this message because you are 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/8fbcea95-fef8-4313-b715-ebaf854922a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Plugin Install Wizard - check out the progress (video) ...

[Tom Fennelly]

On 30 September 2015 at 17:51, Victor Martinez <
victormartinezru...@gmail.com> wrote:

> I wonder whether we could somehow provide certain type of wizards. Let's
> say if you are using an enterprise version of Jenkins you might require the
> below recommend and secured plugins, if you use Jenkins for php then you
> might require another recommend list of plugins, and so on.
>
> An an example, eclipse already provide those default installations based
> on those needs:
> - https://eclipse.org/ide/
>
> Then that wizard installation might be more flexible and provide different
> solutions for different organizations.
>
> What do you think? Is it something feasible from the implementation point
> of view?
>
> Cheers
>

Hi Victor.

We did debate creating such as wizard on the other thread but came to the
conclusion that it would be too difficult to get agreement on it. So, we
just decided to go for the easier option as a v1, see how that goes and
then decide how it might evolve.

T.

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

Re: Jenkins 2.0 proposal

[Tom Fennelly]

On Wednesday, September 30, 2015 at 9:04:07 AM UTC+1, Tom Fennelly wrote:
>
> From a UI perspective, another thing I would like to see baked into a 2.0 
> is push notifications to the browser so we can get rid of the polling that 
> happens in many places (e.g. the build history). It would need to be 
> bi-directional (websockets). Something based on SSE/Long-poll would work.
>

Sorry  typo there  I meant to say "... it would NOT need to be 
bidirectional ..."

-- 
You received this message because you are 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/046c16d3-1d43-4c1e-9fc0-06001fa5a37a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Plugin Install Wizard - check out the progress (video) ...

[Tom Fennelly]

On 29 September 2015 at 23:24, Slide  wrote:

> I thought I saw workflow as one of the plugins that was a "recommended"
> plugin. If it wasn't there, then I misread and you can ignore me.
>

Workflow is there but it's not a cloudbees 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/CA%2BbPaoLqr5ATeM%2BDgF%2BhLME%3DWRj_2d43q1f1t592syijsW1Dvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0 proposal

[Tom Fennelly]

>From a UI perspective, another thing I would like to see baked into a 2.0
is push notifications to the browser so we can get rid of the polling that
happens in many places (e.g. the build history). It would need to be
bi-directional (websockets). Something based on SSE/Long-poll would work.

On 30 September 2015 at 03:43, R. Tyler Croy  wrote:

> (replies inline)
>
> On Tue, 29 Sep 2015, Surya Gaddipati wrote:
>
> > It would also be nice to move wiki pages to github readme's. Not really
> > important but just a suggestion.
>
> I've got a very love/hate relationship with Confluence (I love to hate it
> :))
> but the one useful aspect of having centralized documentation is ease of
> linking and search indexing!
>
> Perhaps what would be useful for plugin developers would be to write their
> README's and then incorporate some tooling to populate a wiki page with
> that
> data upon release?
>
> I.e. a wiki page might be:
>
>  {{pluginheadermacrothing}}
>
>  {{github-readme-macro}}
>
>  other-custom-content.
>
>
>
> Just thinking out loud, please don't consider this as me volunteering to
> write
> Confluence plugins! :)
>
> > On Thursday, September 24, 2015 at 11:54:03 PM UTC-5, Kohsuke Kawaguchi
> > wrote:
> > >
> > > Jenkins is over 10 years old, and it came quite a long way. I still
> > > remember the first few plugins that I wrote by myself, and now we have
> > > close to 1100 plugins. What's started as a hobby project that had run
> under
> > > my desk today boasts more than 100K installations driving half a
> > > million-ish build machines.
> > >
> > > We collectively came quite a long way. When I started Jenkins, having a
> > > server building & testing on every commit was a cutting-edge practice.
> So
> > > are automatically capturing changelogs and analysing test reports. But
> now,
> > > those are tablestakes, and the frontier of automation has moved
> further.
> > > Now we are talking about building pipelines & workflows, continuously
> > > deploying to servers, leveraging containers, and/or testing pull
> requests
> > > before they get merged. I'm going to call this much bigger entangled
> > > automation "Continuous Delivery", to contrast this with more classical
> > > automated build & test executions (aka "Continuous Integration") that
> we
> > > set out to do.
> > >
> > > The other thing I'd like to point out is that the adoption of Jenkins
> > > continues to grow at the incredible pace of 30% year over year. That
> is, a
> > > lot of people are starting new with Jenkins, and they are looking for
> us to
> > > help them get Continuous Delivery done. Therefore, this is a good time
> to
> > > step back and think about whether we are addressing those current user
> > > demands.
> > >
> > >
> > > For example, despite this advance during the last 10 years and 1000+
> > > plugins we've created, messaging in our website hasn't changed much
> since
> > > the first version I wrote on java.net. It spends more space talking
> about
> > > JNLP and zero mention of Git, pipeline, or Docker.
> > >
> > > The fresh installation of Jenkins is not much better. The CVS support
> is
> > > available out of the box, but Git isn't. All the cool stuff that the
> > > community has done and its collective best practices still need be
> learned
> > > by each and every new user. It's bit like we are making everyone
> assemble
> > > LEGO blocks. That's not doing enough justice to the 30K+ users that
> will be
> > > joining us in this year.
> > >
> > > So I propose we do Jenkins 2.0 to fix this.
> > >
> > > There are three important goals that I see in Jenkins 2.0.
> > >
> > >1. We need to claim our rightful place in Continuous Delivery. We
> have
> > >lots of pieces that address these modern needs, but we are not
> > >communicating this very well.
> > >
> > >2. We need to revisit out of the box experience, so that Jenkins
> > >itself speaks that story and makes it clear what we are aiming for.
> Our
> > >software needs to speak for itself and tell people where we are
> going, so
> > >that the community can better focus efforts on the important parts.
> > >
> > >3. And we need to do this while keeping what makes Jenkins great in
> > >the first place, which are the ecosystem, the community, and the
> > >extensibility that recognizes that one size does not fit all and
> let people
> > >do what they want to do.
> > >
> > >
> > > Incrementing the major version sends a clear message to people that we
> are
> > > moving forward. That's why I think 2.0 is appropriate for this effort.
> > >
> > >
> > >
> > > Now, 2.0 can mean a lot of different things to a lot of people, so let
> me
> > > outline what I think we should do and we shouldn't do.
> > >
> > > It's very important for me to make sure that my fellow Jenkins
> developers
> > > understand the motivation and the goal of this proposal, because that
> > > drives much of what we should and shouldn't do. So instead 

Re: Jenkins Plugin Install Wizard - check out the progress (video) ...

[Tom Fennelly]

On 30 September 2015 at 10:51, Robert Sandell 
wrote:

> Yes, so when coding it up you can make sure that the categories can be
> ordered, not by sorting on the name and that there also could be
> description text for each category ;)
>
> /B
>

That's how it is now ... they're not sorted by name or anything. The
categories are displayed in the order in which they are "loaded", as are
the plugins within the categories. So ... we can easily change that order.

So it sounds as though you've spotted a problem somewhere but I don't hear
you say where specifically. If you have, please let us know.

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

Re: Jenkins Plugin Install Wizard - check out the progress (video) ...

[Tom Fennelly]

On 30 September 2015 at 10:22, Robert Sandell 
wrote:

> Tom, my brain is still stuck on the categories ;)
>
> I think the experience could be made a bit better if the categories was
> ordered in a bit of a smarter way, both to follow some sort of thought
> pattern and to ease the user into the depths of what plugins can do.
>
> An example:
>
> Source Code Management
> Build Tools
> Reporters and Notifiers
>
> CD etc
> Job Organisation (folders, views et.al.)
> "All"
>
> *(I didn't remember what categories you chose exactly so I made some up)*
>
> By having the user first think about their build environment (the CI
> part), the scm, tools and report types etc. And then show conceptual things
> like CD pipelines. And at the end get the user thinking about how to
> organise it all into folders and such. and maybe some explanatory texts
> about the category itself.
> That could make the experience a bit easier and more thought through?
>
> /B
>

Yeah, you may be right. I didn't come up with the categories (I think
Daniel did) and, to be honest, I'm not too hung up on that right now
because I know we'll probably need to go through a few rounds before we
find what works "best" in the general sense.

I emphasise "best" there because I think no matter what we do it will not
be perfect and there will be situations where some may find it's not
logical (or smart) in some way. That's just the nature of this kind of
thing I think. So, if we concentrate on the mechanics of how the wizard
looks/works and make sure we provide a way to easily change the
categorisations etc later (without having to rewrite code etc), then we
should be good. That's my hope anyway.

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

Re: Jenkins 2.0 proposal

[Tom Fennelly]

On 30 September 2015 at 00:59, Surya Gaddipati 
wrote:

> Servlet 3.0 would be great for doing push to browser updates instead of
> constant polling that I have to do now. This has been a terrible for
> scaling our jenkins setup.
>

Sorry I missed this Surya  +1000 I think adding nice clean APIs for
doing push notifications (as opposed to every plugin etc opening a long
poll /event-stream request to Jenkins etc) would be a huge step forward. It
would

   1. greatly simplify the programming model
   2. better ux
   3. take load off the backend

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

Re: Jenkins 2.0 proposal

[Tom Fennelly]

On 30 September 2015 at 09:29, Michael Neale 
wrote:

>
>
> On Wed, Sep 30, 2015 at 9:59 AM Surya Gaddipati 
> wrote:
>
>> Great post Kohsuke. Thank you for creating Jenkins.
>>
>> >Time to bump up the system requirement to Java 8 and Servlet 3.0. Let's
>> think about what this would enable to users.
>>
>> I've been using Java 8 for serverside rendering of react fontend for
>> dotci using Nashorn. It has been working beautifully.
>>
>
> Oh that is quite interesting. By react you mean react from facebook?
>
>
We purposely stayed away from using the likes of React/Polymer etc in the
install wizard. We feel it would be too "controversial" to use in Jenkins
Core. However, I think they could be very interesting options in a plugin,
so making it easy to use these would be a great thing I think.

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

Jenkins Plugin Install Wizard - check out the progress (video) ...

[Tom Fennelly]

Hi.

Falling out of the "Revisiting bundled plugins 
"
 
thread, we now have ongoing work in PR #1822 
 (Keith Zantow, Gus Reiber 
and myself) to unbundle plugins from Jenkins core. As part of that, we are 
working on adding a Plugin Install Wizard as a way of making it easy to 
configure the initial set of plugin in Jenkins (for new or existing users).

Here's a short (rough) video showing the 
wizard: https://youtu.be/9pq5tHm4nWs

Keith did all the UI work with help from Gus, so kudos to them.

Also, please download and try he build from the CI server: jenkins.war 

.

Regards,

T.

-- 
You received this message because you are 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/7bdf63f7-621c-4dae-b5fc-19c60685fc06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0 proposal

[Tom Fennelly]

The new Plugin Install Wizard is an example of the sort of UX improvement 
we could target for a 2.0 release. See this short video of the current 
progress there: https://youtu.be/9pq5tHm4nWs

It is using the modularised JavaScript approaches we talked about earlier 
in this thread 


-- 
You received this message because you are 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/e23aac54-ae6e-48b1-9cfd-434b6d30fa1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

I started a new thread specific to the Plugin Install Wizard. See 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/c5bac890-2ecf-4f9c-ab30-861e057341ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0 proposal

[Tom Fennelly]

On Sunday, September 27, 2015 at 2:31:24 PM UTC+1, Baptiste Mathus wrote:
>
> Isn't this issue just about the thing Tom started (finished?) working on 
> some months ago? I.e. paginating the build details. 
>
> Because indeed, on a job with lots of build, you're gonna have a bad time 
> if you click on details. (Might be already fixed, didn't check that 
> specific point recently)
>

It's still in a PR: https://github.com/jenkinsci/jenkins/pull/1641

It's ready to be merged but I think Daniel wanted to remove some of the 
search features I added, leaving just the "fuzzy" search. Maybe others 
should declare their interest and whether they want the more advanced 
search or just the "fuzzy". A topic for another thread I suppose.

-- 
You received this message because you are 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/e1165d7b-e450-46c0-ba64-ce74b0dc6cb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin Manager - Uninstalling/Disabling plugins that have active dependant plugins ???

[Tom Fennelly]

Here's a 15s video of how it might work (from the code I linked to above) 
... https://youtu.be/EWkrbRjTqSs

-- 
You received this message because you are 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/790e14d0-2aaf-4bf4-95ea-116dc0ebca71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Plugin Manager - Uninstalling/Disabling plugins that have active dependant plugins ???

[Tom Fennelly]

Hi.

While doing the unbundling and plugin wizard, it became more obvious to me 
that how the Plugin Manager works is a bit weird. I can go in there and 
just uninstall or disable any plugin... restart Jenkins and BANG ... NCDF 
errors etc !!!

So, I did a bit of experimenting 

 and was fairly easily able to get the "Installed" page to only allow the 
Uninstall or Disable of plugins that do not have any active dependants. The 
disable part doesn't work fully (should be able to disable plugins after 
all dependant plugins have been disabled), but there's enough there to get 
the picture.

Do we think this is something we should fix?

I'm sure there's a long list of possible issues/scenarios with the PM that 
people could draw up. I'm not proposing to fix them all, but I think if we 
can fix some of them we are making progress.

-- 
You received this message because you are 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/7aced6c1-afcb-460b-8e42-4a84dda4e9a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin Manager - Uninstalling/Disabling plugins that have active dependant plugins ???

[Tom Fennelly]

On Saturday, September 26, 2015 at 11:31:16 AM UTC+1, Stephen Connolly 
wrote:
>
> +1000 (but I'd also like to see the dependencies listed on the "installed" 
> page - if you don't already - so I know what I need to disable/uninstall to 
> be able to do this one that is blocked)
>
> * me not watchee video clip so maybe you did that.
>

No I haven't done that yet but will for sure. It needs that. 

-- 
You received this message because you are 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/52f8b12d-3908-4a08-b2e3-81bbff5a256d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin Manager - Uninstalling/Disabling plugins that have active dependant plugins ???

[Tom Fennelly]

On Saturday, September 26, 2015 at 2:09:07 PM UTC+1, Stephen Connolly wrote:
>
>
>
> On Saturday 26 September 2015, Tom Fennelly <tom.fe...@gmail.com 
> > wrote:
>
>> On Saturday, September 26, 2015 at 11:31:16 AM UTC+1, Stephen Connolly 
>> wrote:
>>>
>>> +1000 (but I'd also like to see the dependencies listed on the 
>>> "installed" page - if you don't already - so I know what I need to 
>>> disable/uninstall to be able to do this one that is blocked)
>>>
>>> * me not watchee video clip so maybe you did that.
>>>
>>
>> No I haven't done that yet but will for sure. It needs that. 
>>
>
> What about my pony? 
>

Shouldn't be a problem. Would you like a trap with it? 

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

Re: Jenkins 2.0 proposal

[Tom Fennelly]

On Friday, September 25, 2015 at 7:21:34 AM UTC+1, Kohsuke Kawaguchi wrote:
>
> As you say, for compatibility reasons I don't think we can remove them.
>
> But that "brand-new way of doing frontend development" that I mentioned 
> touches a related space. It borrows a lot of tooling from NodeJS, such as 
> writing JavaScript in CommonJS modules, using JavaScript template libraries 
> like handlebar, etc. My hope is that that provides a different way of 
> building pages that require high degree of interactivity.
>
> The workflow stage view 
>  is 
> built using this technology. I'll let Tom chime in to talk more about this.
>

As far as stapler and jelly are concerned, I'd say the following:

   1. We're probably stuck with it.
   2. Even though there's much about them that I think sucks, I also think 
   they have some very important qualities that have contributed greatly 
   towards making Jenkins as popular as it is. The provide an easy way for 
   people (often with little or no UI skills) to get going with Jenkins and 
   create their first plugin that can contribute elements to the Jenkins UI. 
   So, we shouldn't throw out the baby with the bathwater.

I suppose the best place to start wrt the newer methodologies we've been 
adopting is to take a look at the following docs:

   - jenkins-js-modules : 
   A very simple JavaScript bundle loader tailored to the Jenkins 
   "environment". The main reason I point to this is because the docs there 
   try to explain the problems/challenges (+ there's a slide dec which people 
   might find useful).
   - jenkins-js-builder : 
   An NPM module to tries to simplify the process of working with this stuff. 
   Some docs there too.
   - jenkins-js-test : No 
   prices for guessing what this is about. Builds on Jasmine and jsdom, making 
   them a bit easier to use together. But, people can always use whatever they 
   want.

PLEASE note that we are not proposing to make any of this a mandatory part 
of learning or working with Jenkins. If you are happy with Stapler+Jelly 
and don't want to be bothered with any of this, then keep rock'n !! See 
this FAQ 

.

-- 
You received this message because you are 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/7d33e71e-b2be-43b0-8a55-cdd1e46d0cb4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

Ok, thanks guys. We can park the "plugins in core" discussion and have that 
in a separate thread. As far as the install wizard is concerned, lets say 
it will be totally self contained and will be loaded conditionally.

-- 
You received this message because you are 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/bf3d50a9-d0d1-4df9-917e-7ad6a59ba4a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

Sorry ... typo in #2 on the last email. I should have said "This only seems
relevant to me if the answer to #1 is no" i.e. we will upgrade if the
plugin does not meet the minimum version requirements i.e. is less than the
bundled version (in /WEB-INF/detached-plugins).

On 17 September 2015 at 10:23, Tom Fennelly <tom.fenne...@gmail.com> wrote:

> So where are we now guys?
>
>1. Are we still saying we are not going to update existing plugins on
>an upgrade? Jesse seemed definitive on this one but I still don't know the
>reasoning.
>2. Are we still saying pinned files should be ignored ala what Jesse
>said earlier? Again, I still haven't heard the reasons why they should be
>ignored. This only seems relevant to me if the answer to #1 is yes (we are
>updating existing plugins on an upgrade).
>
> Basically, I want to agreement on what changes are needed on the PR.
>
> --
> 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/kRobm-cxFw8/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/d7209aea-08d3-46ec-92f4-ff5070cc1410%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/d7209aea-08d3-46ec-92f4-ff5070cc1410%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: Revisiting bundled plugins

[Tom Fennelly]

So where are we now guys?

   1. Are we still saying we are not going to update existing plugins on an 
   upgrade? Jesse seemed definitive on this one but I still don't know the 
   reasoning.
   2. Are we still saying pinned files should be ignored ala what Jesse 
   said earlier? Again, I still haven't heard the reasons why they should be 
   ignored. This only seems relevant to me if the answer to #1 is yes (we are 
   updating existing plugins on an upgrade).

Basically, I want to agreement on what changes are needed on the PR.

-- 
You received this message because you are 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/d7209aea-08d3-46ec-92f4-ff5070cc1410%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

Maybe we should clarify what it means for a plugin to be bundled in 
"/WEB-INF/plugins" Vs "/WEB-INF/detached-plugins".

My understanding/interpretation is:

   - */WEB-INF/plugins*: These are plugins that must always be 
   installed/updated. Same as before. The versions are kept as up-to-date as 
   possible (I think, right?).
   - */WEB-INF/detached-plugins*: Selectively installed based on the 
   criteria I outlined above/yesterday (Sept 16). The versions are *set to 
   the minimum* required for Jenkins to work without throwing a wobbler of 
   errors i.e. not kept up-to-date with latest version of that plugin.
   
So as I see it, upgrades from /WEB-INF/detached-plugins only happen if the 
installed version is below the minimum version required for the new Jenkins 
to work. We don't just upgrade "for fun".

-- 
You received this message because you are 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/0cea22d7-3bf9-4abf-8f00-497a2d38de88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

On Thursday, September 17, 2015 at 1:04:15 PM UTC+1, Daniel Beck wrote:
>
>
> On 17.09.2015, at 13:02, Tom Fennelly <tom.fe...@gmail.com > 
> wrote: 
>
> > while other plugins are just "dependency" plugins … and are dependencies 
> … Jenkins core itself. 
>
> These do not exist today. 


Sure, I'm just suggesting that there should be some sort of distinction of 
different types of plugins. They all seem to be treated the same atm, which 
seems wrong to me.
 

> If you need them for other changes, this will need to be considered 
> separately. Remember, every plugin, even the bundled ones, can be disabled, 
> which would in this case break Jenkins. Maybe the solution to that issue 
> even blocks finalizing this one?
>

Well I do think these things need to be considered at some stage, but not 
as blockers for this (imo). Jenkins has always been at varying degrees of 
mercy of people disabling plugins at a bad time, right? Sure, this would be 
more unmerciful though :)

-- 
You received this message because you are 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/9ba3271e-c01f-43b8-9019-54b0b7f4946c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

On Thursday, September 17, 2015 at 5:38:37 PM UTC+1, Jesse Glick wrote:
>
> On Thu, Sep 17, 2015 at 11:49 AM, Tom Fennelly <tom.fe...@gmail.com 
> > wrote: 
> >> Jenkins core cannot depend on a plugin, this makes no sense. 
> > 
> > I still don't get why it's such a no-no. 
>
> Violates the very notion of what a “plugin” is. By definition, plugins 
> depend on core, and core does not depend on any plugin. 
>

But is it not possible to redefine what it means to be a plugin?

BTW, it is possible for us to do a totally self contained install wizard 
that has everything it needs bundled inside it. I just think it's a waste 
if we are going to be doing other things too in core.

-- 
You received this message because you are 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/609c84fc-1bf8-4bc1-8d82-5510b76de99e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

It would be good if some people could try out what we've done so far and 
let is know. Here's a link to a jenkins.war from the PR Builder 

 (or 
get the latest build via the PR 
 itself).

One of the important things people might could check is the upgrade path 
and how the detached/split plugins are handled. All the plugins that were 
bundled in the jenkins.war are still bundled (in WEB-INF/detached-plugins), 
but are only conditionally loaded on upgrade (not loaded at all on a new 
install - the wizard handles that).

The upgrade ("last" running jenkins instance version was less than "this") 
conditions under which detached plugins are loaded from 
WEB-INF/detached-plugins are:

   1. The plugin in WEB-INF/detached-plugins was detached since the "last" 
   running version.
   2. The plugin in WEB-INF/detached-plugins is already already installed 
   in "this" jenkins instance.
  - The only effect here will be a possible upgrade of the plugin if 
  the installed version is less than the bundled version AND the installed 
  version is not pinned.
  3. The plugin in WEB-INF/detached-plugins is a dependency of one of 
   the plugins selected via #1 or #2 above.
   - i.e. we also install the dependencies of plugins selected via criteria 
  #1 or #2 above. For this, we use the "Plugin-Dependencies" attribute in 
the 
  manifest. The dependency plugin must also be in 
  WEB-INF/detached-plugins.
   
The wizard you'll see (if you have an empty JENKINS_HOME i.e. not an 
upgrade) is just a temp wizard I created to allow us put in some of the 
backend bits. It only allows you to install some "recommended" plugins as a 
quick starter. You can try this of course but don't waste time critiquing 
it because it will be getting binned. Keith (Zantow) and Gus are building a 
nicer wizard and we should have that soon (will allow easy plugin selection 
etc).

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

Re: Revisiting bundled plugins

[Tom Fennelly]

On Wednesday, September 16, 2015 at 2:50:31 PM UTC+1, Jesse Glick wrote:
>
> On Wed, Sep 16, 2015 at 3:42 AM, Tom Fennelly <tom.fe...@gmail.com 
> > wrote: 
> > The plugin in WEB-INF/detached-plugins is already already installed in 
> > "this" jenkins instance. 
> > The only effect here will be a possible upgrade of the plugin if the 
> > installed version is less than the bundled version AND the installed 
> version 
> > is not pinned. 
>
> -1, `*.jpi.pinned` should be ignored henceforth, 


Daniel Beck is of the opinion that .pinned should be honoured.

It would help if you said why you think this.
 

> and we should leave 
> the installed version alone, period. 
>

Again, it would be helpful to know why you say this.

What I have seen here is that, if left with just the installed version 
(from the previous release - pre upgrade), you can end up getting 
exceptions on upgrade.

For example, Jenkins 1.547 has external-monitor-job version 1.2. Version 
1.4 of this plugin received updates that were moved out from Jenkins core 
<https://github.com/jenkinsci/external-monitor-job-plugin/commit/4175bb5f4fefe0fd7ffa73e195bd65233f83bdf5>.
 Jenkins 
core now has a hard dependency on external-monitor-job version 1.4+ 
(probably indirectly via one of the plugins that were detached between 
those releases?). Therefore, without updating this plugin to at least 
version 1.4 as part of the upgrade, we get the error you saw 2 days ago (not 
able to resolve <https://gist.github.com/tfennelly/c3211d3a8331db4b1c86> 
hudson.model.Messages.ExternalJob_DisplayName 
<https://gist.github.com/tfennelly/c3211d3a8331db4b1c86>) when upgrading 
from 1.547 to a new Jenkins that doesn't run version 1.4 of this plugin.

Maybe this could be solved by only updating already installed detached 
plugins if the new version is a dependency of one of the detached plugins 
since the last release?

The only other way I can see of solving this is by telling people that they 
need to update all plugins before shutting down the old version of Jenkins 
and installing the new version. That sucks imo (and probably wouldn't work 
anyway in many cases). Alternatively, we could just say that they need to 
manually update plugins after upgrade, which also seems to suck.

-- 
You received this message because you are 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/61c9a184-ef21-447d-88db-8886bfa33ab5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Revisiting bundled plugins

[Tom Fennelly]

A WiP PR relating to this: https://github.com/jenkinsci/jenkins/pull/1822

-- 
You received this message because you are 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/a496042b-7e73-44ca-b532-6ea889630851%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.