Hi,
Take a look at https://github.com/jenkinsci/pipeline-view-plugin
it's non-blueocean plugin in ReactJS, so you can learn how to use React in
Jenkins without going BlueOcean-only way :)
BR,
Sergei
On Mon, Jun 20, 2016 at 10:32 AM wrote:
> Hi,
> i want to add support for graphs and plots i
Chris,
Sorry to have confused you. Yes, you're right, summary.jelly is the one
you're looking for and does exactly what you described :)
On Tue, May 17, 2016 at 7:39 PM Chris Price wrote:
> On Tue, May 17, 2016 at 8:52 AM, Sergei Egorov wrote:
>
>> Hey Chris,
>>
>
>>>
>>> On Sun, May 15, 2016 at 1:00 AM, Sergei Egorov
>>> wrote:
>>>
>>>> Hey Chris,
>>>>
>>>> I recommend you to take a look at
>>>> https://github.com/jenkinsci/pipeline-view-plugin - this is pipeline
>>>
Hey Chris,
I recommend you to take a look at
https://github.com/jenkinsci/pipeline-view-plugin - this is pipeline
visualization plugin in ReactJS. No jelly, just plain modern JS with
ES6/ES7, React, Webpack, etc...
BR,
Sergei
On Sun, May 15, 2016 at 6:50 AM Chris Price wrote:
> Well! I haven
nd reviewed. Just like the Atlassian Marketplace works. I started
> working on something like that (
> https://github.com/tomasbjerre/jenkins-plugins/ and
> http://www.jenkins-plugins.com/) but have not had time to finish it.
>
> -Tomas
>
>
> Den torsdag 28 april 2016 kl. 12:44:59 U
not sure how we can manage permissions for such kind of ecosystem, but
> it definitely doable from the technical PoV.
>
> четверг, 28 апреля 2016 г., 12:44:59 UTC+2 пользователь Sergei Egorov
> написал:
>
>> Hey everyone,
>>
>> Remember Jucies? ( https://github.com/jucies/re
Hey everyone,
Remember Jucies? ( https://github.com/jucies/releases ) - experimental
update center for Jenkins with releases directly from GitHub?
Today it became much better!
Starting from today, GitHub releases will be used to release your plugin.
That said, no publish, no PRs to update your p
Hey, everyone!
Just a reminder - if you want to release your plugin ASAP and don't want to
wait - use Jucies :)
https://github.com/jucies/releases
Fast plugin *releases* *directly from GitHub*, no need to build or
something.
In the last few weeks it was simplified as well - no need to configur
Hey Michael,
To be honest - I'm doing an experiment with Jucies, because I really want
to have such way of distribution of plugins :)
Maybe I'm too naive and users will deny using Jucies - this is fine as
well, negative experiments are also experiments, right?
If I understand correctly, you want
ousands of
> nodes.
>
> Thoughts?
>
> On Monday, March 21, 2016 at 2:52:04 AM UTC-4, Sergei Egorov wrote:
>>
>> Hey everyone,
>>
>> Yesterday I decided to publish sources for my pipeline visualization
>> plugin: https://github.com/bsideup/jenkins-pipeli
Hello, everyone!
I'm happy to announce this small, simple, but yet powerful project created
by me - Jucies:
https://github.com/jucies/releases
Jucies makes it simple to release Jenkins plugins by utilizing
https://jitpack.io/. For each listed plugin in the github repository under
"plugins/" folde
Ok, now it's under jenkinsci org:
https://github.com/jenkinsci/pipeline-view-plugin
I will prepare it for the release this week :)
On Wed, Mar 23, 2016 at 4:21 AM Michael Neale wrote:
> yep, Tyler pointed out to me! Good to know, in that case, all the more
> reason to have it moved on over and
Nenashev
wrote:
> Why don't you just move it to jenkinsci org?
> The plugin is definitely useful, so I think it is reasonable.
>
> P.S: I'm still planning to run the plugin against big pipelines. I'm just
> in the slowpoke mode :(
>
> BR, Oleg
>
> вторник, 22
On Tuesday, March 22, 2016 at 5:49:49 PM UTC+11, Sergei Egorov wrote:
>
>> Actually... getStartNode marked with @Nonnull, as well as getExecution(),
>> so one of them is null. Execution maybe?
>>
>> On Tue, Mar 22, 2016 at 8:17 AM Sergei Egorov wrote:
>>
> Hi M
Actually... getStartNode marked with @Nonnull, as well as getExecution(),
so one of them is null. Execution maybe?
On Tue, Mar 22, 2016 at 8:17 AM Sergei Egorov wrote:
> Hi Michael,
>
> Wow, interesting finding!
>
> I checked with the sources and looks like it's not an
.
>>>
>>> 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/bs
s nice! A nit about the README: it should emphasize that while in
> _dev mode_ you need to manually run a separate service and browse to
> another URL, the fully built plugin `*.hpi` is self-contained.
>
> On Mon, Mar 21, 2016 at 2:52 AM, Sergei Egorov wrote:
> > Why Jackson
Also, just noticed a typo in README: *build/libs/pipeline-view.hpi* instead
of "build/dist".
On Mon, Mar 21, 2016 at 2:03 PM Sergei Egorov wrote:
> Ah, yes, definitely my bad. Forgot to include peer dependency. Should be
> fine now if you pull the latest changes. Sorry :)
&g
Ah, yes, definitely my bad. Forgot to include peer dependency. Should be
fine now if you pull the latest changes. Sorry :)
On Mon, Mar 21, 2016 at 1:32 PM Sergei Egorov wrote:
> Het Antonio,
>
> Thanks for the report! I will clean my local installation and re-run build
> to make
ild/dist
> directory is empty.
> The build finishes wit success, but I see this error in the build log:
>
> ERROR in ./app/index.jsx
> Module build failed: Error: Cannot find module 'es2015'
>
> Something related to i18n?
>
> On Mon, Mar 21, 2016 at 7:5
velopment
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 s
21 matches
Mail list logo
