Re: Run Jenkins as a service and NOT headless

[Simon Richter]

Hi,

On 27.05.2016 17:50, developer.go...@gmail.com wrote:

> How do i run Jenkins as a service but not headless. If i am doing
> browser testing, i want to see it open Firefox, Chrome, etc. Thank you!

This is more a Windows sysadmin question:

Windows services have an option in their configuration that allows them
access to the desktop. By default, this is disabled, and enabling it
will allow programs to open visually.

That was the easy part. The hard part is that weird stuff will happen if
no one is logged in, so ideally you'd ask your local Windows admin
whether they have a good idea about that (e.g. automatic login, or
switching the logon screen to use a small window rather than a full-screen).

   Simon

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


signature.asc
Description: OpenPGP digital signature

Re: [Blue Ocean] A new user experience project for Jenkins

[Kohsuke Kawaguchi]

Some of those are in https://github.com/jenkinsci/pipeline-examples

On Fri, May 27, 2016 at 7:04 AM Maciej Jaros  wrote:

>
> I think this would be solved by providing recepies that would be updated
> for each Jenkins version. Some recepies ideas:
>
>1. How to read a build parameter and conditionally run some shell
>script.
>2. How to trigger build of another project.
>3. How to trigger build of another project with some static parameters
>of various types.
>4. How to trigger build of another project passing all parameters from
>current job/build.
>5. How to copy artifacts from another project.
>6. How to send files over SSH.
>7. How to execute scripts over SSH.
>
>

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

Re: [Blue Ocean] A new user experience project for Jenkins

[Michael Neale]

BTW the github repositories have been "transferred" (ownership) into the 
jenkinsci org fully now (old links automatically redirect). 

On Friday, May 27, 2016 at 8:22:00 AM UTC+10, James Dumay wrote:
>
> Hi Jenkins users,
>
> Today I am happy to announce the open sourcing of a new user experience 
> for Jenkins called Blue Ocean.
>
> We are looking to build an excellent experience around Pipeline and 
> Freestyle jobs with a focus on developer experience - how you as a 
> developer build better automation, easily diagnose failures, integrate with 
> tools like Github, Bitbucket or Slack and onboard new team members. These 
> are goals of the uttermost importance to this project.
>
> We realise that we can’t do this alone and it will take more than just 
> Jenkins developers to make this effort successful. We need to hear from the 
> Jenkins user community about their thoughts on the project, where it is 
> heading and how we can help you hone your craft and build better software 
> using Jenkins. 
>
> Today we’ve made the source code  
> available on Github, written a blog post 
>  and created 
> a video  explaining the 
> project in more detail. We will be posting more updates to both the blog 
> and mailing lists when there are more updates to share.
>
> If you have any questions or comments please reply to this post and I’ll 
> be more than happy to answer any questions you may have :)
>
> Thanks,
> James
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e1a79309-71ff-422e-b088-3decf7017985%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

running cucumber tests from jenkins

[ziffification]

>
> I am running with the cucumber plugin with the following parameters
>
 



and after doing these 2 things


  /var/lib/jenkins/.rvm/bin/rvm @global do gem install bundler
  /var/lib/jenkins/.rvm/bin/rvm  use ruby 1.8.7 && gem install bundler




I still am getting this message:


Started by user rob m 
Building in workspace /var/lib/jenkins/workspace/SASEBI
 [30m [31m [1mstage: [0m [0m [0m  [1m [30m [34mruning cucumber tests [0m [0m [0m
 [30m [31m [1mruby_version: [0m [0m [0m  [1m [30m [34m1.8.7 [0m [0m [0m
 [30m [31m [1mcucumber profile: [0m [0m [0m  [1m [30m [34m [0m [0m [0m
 [30m [31m [1mdirectory: [0m [0m [0m  [1m [30m [34mtestebi [0m [0m [0m
$ bash -c "source /var/lib/jenkins/.rvm/scripts/rvm && cd 
/var/lib/jenkins/workspace/SASEBI/testebi && rvm use ruby 1.8.7 && bundle && 
bundle exec cucumber -p  -c no_proxy=127.0.0.1 browser=chrome DISPLAY=:11 
--color"
Using /var/lib/jenkins/.rvm/gems/ruby-1.8.7-head
bash: bundle: command not found
ERROR:  (Java::Hudson::AbortException)
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
java.lang.reflect.Constructor.newInstance(Constructor.java:423)




indicating that it cannot find bundle ? any idea what i am missing?



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

Re: maven projects become slow after a couple of months

[Mykola Nikishov]

Jorg Heymans 
writes:

> It is easy to tell a job is getting slow because during maven init it takes 
> a long time to get passed "Scanning for projects" :
>
>
> 13:06:54 [INFO] Scanning for projects...
> 13:08:03 [INFO] 
> 
>
> Any thoughts as to what could be causing this ?

How about getting more info with 'mvn --debug'?

-- 
Mykola
https://manandbytes.github.io/

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

Re: Proxy and certificate

[Mykola Nikishov]

sebastienjfoss...@free.fr writes:

> We have just installed Jenkins and we want to install some plugins (Git, 
> ...). But in plugins section, Advanced tab, the "validate proxy" fails with 
> following message : "
>
> javax.net.ssl.SSLHandshakeException: 
> sun.security.validator.ValidatorException: PKIX path building failed: 
> sun.security.provider.certpath.SunCertPathBuilderException: unable to find 
> valid certification path to requested target". It seems we have a 
> certificate issue. Can someone tell us where to get information about the 
> good way to manage these certificates for Jenkins.
>
> The "Test URL" was "http://jenkins-ci.org/; ; there is no problem for 
> accessing this URL in brower with same proxy configuration.

Seems you have a transparent proxy that terminates HTTPS traffic from
the target site, re-encrypts/signs it with its own key/certificate and
forwards it to the client. Quite often such intermediate certificates
are self-signed thus breaking the chain of trust.

Check this SO question [1] to better understand and how to 'fix' this
issue.

[1] 
https://stackoverflow.com/questions/6908948/java-sun-security-provider-certpath-suncertpathbuilderexception-unable-to-find

-- 
Mykola
https://manandbytes.github.io/

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

Re: [Blue Ocean] A new user experience project for Jenkins

[Arnaud Héritier]

+1000 with this Stephen
I think you are taking a good blog post idea :-)

On Fri, May 27, 2016 at 8:34 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> The Jenkins specific tasks should be mostly single purpose and logicless
> in my view.
>
> The complex logic should be testable outside of Jenkins.
>
> But building complex logic in groovy "just because it is there" and not
> "because we cannot do it elsewhere" is the problem my rant is directed at
>
>
> On Friday 27 May 2016, Maciej Jaros  wrote:
>
>> Stephen Connolly (2016-05-27 12:12):
>>
>>
>>
>> On 27 May 2016 at 07:59, Craig Rodrigues  wrote:
>>
>>> Hi,
>>>
>>> The new Jenkins UI looks nice, and will be a big improvement over the
>>> existing UI.
>>>
>>> The original selling point of Jenkins was that even with the simplistic
>>> forms-based UI,
>>> someone could fill out a relatively simple form, and have a continuous
>>> integration pipeline.
>>> I have met people who were general devops and scripting people, and
>>> could use Jenkins quite nicely.
>>>
>>> While I understand the motivation for Pipeline (previously known as
>>> Workflow), I can't say I'm very happy with the results.
>>>
>>> Here are some of the pain points I've encountered with Pipeline scripts:
>>>
>>>- Other than the most trivial of scripts, you need to be a
>>>knowledgable Groovy programmer.  For example, to make a global variable,
>>>you need to use a @Field.  (What?!)  Most scripting and devops people 
>>> that
>>>I know don't really know Groovy.
>>>
>>> So in my personal opinion, this is a sign of People Doing Things Wrong™
>>
>> By this I mean that your Jenkinsfile should *not* be doing complex
>> things. You should have shell scripts or equivalent to do the complex
>> functionality. That lets you test each individual step in the phase on
>> local developer machines. Then your pipeline should end up mostly being
>>
>>
>> But you cannot test everything locally, because you e.g. don't have build
>> parameters, you might not have certain SSH credentials defined... That said
>> I do tend to move everything to scripts, but this really defeats the
>> purpose of almost all Jenkins plugins... And plugins gives you some
>> integrations (especially with credentials) you don't have in scripts. And
>> it's much easier to add build step for triggering e.g. call of another
>> project and passing all parameters to it from current build (which BTW is
>> overly hard with Groovy).
>>
>> Regards,
>> Nux.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/fac125e7-9e6c-46f1-bbe7-42067660d98c%40mol.com.pl
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Sent from my phone
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMxSo6%3D9WaaBUZYxdYfMsj%3DRgbcrQyO3F3J%3D2oUuXcuoFA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

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

Re: [Blue Ocean] A new user experience project for Jenkins

[Stephen Connolly]

The Jenkins specific tasks should be mostly single purpose and logicless in
my view.

The complex logic should be testable outside of Jenkins.

But building complex logic in groovy "just because it is there" and not
"because we cannot do it elsewhere" is the problem my rant is directed at

On Friday 27 May 2016, Maciej Jaros  wrote:

> Stephen Connolly (2016-05-27 12:12):
>
>
>
> On 27 May 2016 at 07:59, Craig Rodrigues  > wrote:
>
>> Hi,
>>
>> The new Jenkins UI looks nice, and will be a big improvement over the
>> existing UI.
>>
>> The original selling point of Jenkins was that even with the simplistic
>> forms-based UI,
>> someone could fill out a relatively simple form, and have a continuous
>> integration pipeline.
>> I have met people who were general devops and scripting people, and could
>> use Jenkins quite nicely.
>>
>> While I understand the motivation for Pipeline (previously known as
>> Workflow), I can't say I'm very happy with the results.
>>
>> Here are some of the pain points I've encountered with Pipeline scripts:
>>
>>- Other than the most trivial of scripts, you need to be a
>>knowledgable Groovy programmer.  For example, to make a global variable,
>>you need to use a @Field.  (What?!)  Most scripting and devops people that
>>I know don't really know Groovy.
>>
>> So in my personal opinion, this is a sign of People Doing Things Wrong™
>
> By this I mean that your Jenkinsfile should *not* be doing complex things.
> You should have shell scripts or equivalent to do the complex
> functionality. That lets you test each individual step in the phase on
> local developer machines. Then your pipeline should end up mostly being
>
>
> But you cannot test everything locally, because you e.g. don't have build
> parameters, you might not have certain SSH credentials defined... That said
> I do tend to move everything to scripts, but this really defeats the
> purpose of almost all Jenkins plugins... And plugins gives you some
> integrations (especially with credentials) you don't have in scripts. And
> it's much easier to add build step for triggering e.g. call of another
> project and passing all parameters to it from current build (which BTW is
> overly hard with Groovy).
>
> Regards,
> Nux.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com
> 
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/fac125e7-9e6c-46f1-bbe7-42067660d98c%40mol.com.pl
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my phone

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

Gerrit Trigger + Pipeline Jobs question

[Jacob Scott]

Hi,

I've been using Gerrit Trigger + Jenkins 1.6 for a fairly vanilla pre merge
unit test setup. I've recently upgraded to Jenkins 2.1 and want to upgrade
my job for improved functionality -- I think using pipeline jobs -- but I
haven't written any pipeline jobs yet and am not quite sure where to start.
The Gerrit Trigger wiki page (
https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger) mentions
pipeline jobs but I think I'm too new to pipeline jobs to understand the
writeup.

Currently, I have a single job which is Gerrit Triggered on Patchset
creation and does a build and runs unit tests & verifies/etc.

I would like to augment this such that I have a initial job which is Gerrit
Triggered on Patchset creation, introspects the commit (e.g., to determine
whether modifies javascript files, python files, or both), and based on the
results of that introspection, triggers one of a few possible downstream
jobs (e.g. "build + unit tests", "build + unit tests + end to end tests",
etc).

I want these downstream builds to verify back to gerrit -- and I'm not sure
how to configure these downstream jobs or inject the right context/env
vars/etc so that behave basically as if they were vanilla "Gerrit Trigger
on Patchset creation" jobs even though they are actually being triggered by
the upstream "dispatch" job.

I would appreciate any suggestions, examples, pointers to resources, etc.

Thanks!

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

Jenkins on AIX Installation

[nk1306was]

I am new to the Jenkins, Can we install Jenkins on AIX server? If so, can 
someone post the actual process. I am trying to download package for AIX in 
Jenkins-ci website, i don't find it.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/520bf60e-377c-472d-b159-b78528404d35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Stable version of Jenkins and the Robot Framework Plugin?

[developer . goran]

1.651.2 LTS and 1.6.4, the report and log files cannot be opened from 
within Jenkins. Does anyone know of a stable release that in the 1.6X 
series or the 2.X series that works with the current robot framework plugin?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/688fd536-90b7-42a5-913b-bde180abd2a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Run Jenkins as a service and NOT headless

[developer . goran]

How do i run Jenkins as a service but not headless. If i am doing browser 
testing, i want to see it open Firefox, Chrome, etc. Thank you!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8380c9d4-b4ec-4b3c-bc1f-628679d89f26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] A new user experience project for Jenkins

[Kent Johnson]

James, this looks really valuable and useful. I am looking to create one or 
two video training courses involving the Pipeline plugin suite. it is great 
to see the work you have done with Blue Ocean. Is Blue Ocean the future of 
the Jenkins UI? If so, I'd like to build the training courses around the 
new UI. I could do things in the new and the old, though if Blue Ocean is 
certainly the way of the future then I may as well focus on that.

Thanks for all your work to make the Jenkins user experience better.

On Thursday, May 26, 2016 at 4:22:00 PM UTC-6, James Dumay wrote:
>
> Hi Jenkins users,
>
> Today I am happy to announce the open sourcing of a new user experience 
> for Jenkins called Blue Ocean.
>
> We are looking to build an excellent experience around Pipeline and 
> Freestyle jobs with a focus on developer experience - how you as a 
> developer build better automation, easily diagnose failures, integrate with 
> tools like Github, Bitbucket or Slack and onboard new team members. These 
> are goals of the uttermost importance to this project.
>
> We realise that we can’t do this alone and it will take more than just 
> Jenkins developers to make this effort successful. We need to hear from the 
> Jenkins user community about their thoughts on the project, where it is 
> heading and how we can help you hone your craft and build better software 
> using Jenkins. 
>
> Today we’ve made the source code  
> available on Github, written a blog post 
>  and created 
> a video  explaining the 
> project in more detail. We will be posting more updates to both the blog 
> and mailing lists when there are more updates to share.
>
> If you have any questions or comments please reply to this post and I’ll 
> be more than happy to answer any questions you may have :)
>
> Thanks,
> James
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0b4be40b-3a72-4af1-89fc-89feca1a31b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Making a Course on Pipeline Plugin

[Kent Johnson]

Yes, Anderson, the Jenkins DSL was where I thought I would start.
That will be interesting to cover as Kotlin becomes more supported as 
another language in addition to Groovy to write build scripts in.

When you say scaling I think of spinning up a collection of containers for 
a test grid. It looks like you are also referring to multi-project builds 
and using the same binary artifacts for multiple projects. Is that what you 
are saying? I definitely want to cover multi-project builds whether in the 
introduction course or the advanced course.

I definitely want to cover artifact storage integrations. The storage 
integrations I am thinking of consists of JFrog's Artifactory, Sonatype's 
Nexus, and Docker's Docker Registry. I hadn't thought of Amazon's S3, so 
I'll add that to the list.

I don't want to go too extensively into examples on one point though I want 
to give a broad overview and rich selection of what successful products and 
teams use in our industry to automate integration and delivery processes.

On Thursday, May 26, 2016 at 4:53:10 AM UTC-6, Anderson Goulart wrote:
>
> Hi,
>
> I don't know if is pertinent, but here are my suggestions:
>
> Jenkinsfile DSL 
>
> Scaling (what are the design options for managing multiple projects? How 
> to share code between them? )
>
> Integrations (like pushing artifacts to S3)
>
>
> -- global
>
> On 25/05/2016 16:47, Kent Johnson wrote:
>
> Hi all, I am making a course on how to use Jenkins with the Pipeline 
> plugin to automate continuous integration and builds. 
> My goal is to make having a short, low-noise, high-reliability feedback 
> loop a practical possibility for the average developer.
> I am thinking this means that I would show how to use Docker to spin up 
> Jenkins locally and a test-grid locally as well as how to create or plug 
> into an existing enterprise Jenkins Pipeline build system.
>
> See this Github repo for the TOC:  
> 
> https://github.com/kentoj/jenkins-pipeline-course
>
> Though I have used the Pipeline plugin (back when it was called the 
> Workflow plugin) I am not familiar with even a small fraction of the best 
> use cases for it.
>
> Will you, the other community members, help me put together a good table 
> of contents or outline for a solid three to four hour course on how people 
> could use and benefit from Jenkins with the Pipeline plugin?
>
> I understand there are many ways to use Jenkins and the Pipeline so I am 
> having to pick a small scope to begin with, though I would like to go as 
> deep as showing test reports, running tests on test grids, and doing a 
> build for every pushed branch to a repo.
>
> I would greatly appreciate any contributions to the TOC. Please submit any 
> suggestions or criticism as an issue or a pull request.
>
> I believe we can create a great course together with the time I have to 
> make it and the knowledge of this community.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com .
> To view this discussion on the web visit 
> 
> https://groups.google.com/d/msgid/jenkinsci-users/353ea3a4-cbf6-4adc-8947-a76040714c20%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/26002c5c-d870-4d6c-b535-177c3df228a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Multi-branch pipeline project with Subversion

[Pieter-Jan Busschaert]

Hello,


We have a debian Jenkins server which runs on the latest jenkins PPA 
(currently 2.6). I'm interested to test the Multi-branch pipeline 
functionality, in combination with our SVN server. However, all 
documentation I find about the topic talks about git. The concept of 
branches etc in SVN is significantly different than in GIT. Can someone 
here please answer these questions, based on our typical SVN folder 
structure (see below):

   1. Where should I store the Jenkinsfile? Is there 1 file for all 
   branches or should there be 1 file in each branch?
   2. Which URL should I configure in the job page as the "project 
   repository base"?
   3. What patterns should I put in the include/exclude branches boxes?
   4. Currently we create 2 types of builds for each project : 1 
   incremental build which runs after each commit, 1 clean build which runs at 
   night. How would we do something like that ? Would that need 2 Jenkinsfiles 
   per project ?
   
Background info: our typical SVN layout:


repo_url

-- trunk

 projectA

 projectB

 shared

-- branches

 branch_name_1

-- projectA

-- shared

 branch_name_2

-- projectB

-- shared


The projectA, projectB folders in the above structure contain some 
svn:externals to the shared folder, so I have to define additional 
credentials (which are actually identical as the ones for the main URL) in 
the job config SVN section (don't know if this is relevant for my above 
questions).


Based on the limited information available, I would currently guess the 
answers to my question above to be something like this:

   1. put the jenkins file as repo_url/trunk/projectA/Jenkinsfile (with 
   automatic copies each time I make a branch like: 
   repo_url/branches/branch_name_1/projectA/Jenkinsfile)
   2. configure the repository base as repo_url
   3. include pattern : trunk/projectA, branches/*/projectA
   4. No idea how to do this

Am I close with these guesses? Is there any place where this is documented 
/ explained better that I didn't find?




Kind regards,

Pieter-Jan


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3aa1501c-61f0-4993-a016-eeb0a86b775f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] A new user experience project for Jenkins

[Maciej Jaros]

Stephen Connolly (2016-05-27 12:12):



On 27 May 2016 at 07:59, Craig Rodrigues > wrote:


Hi,

The new Jenkins UI looks nice, and will be a big improvement over
the existing UI.

The original selling point of Jenkins was that even with the
simplistic forms-based UI,
someone could fill out a relatively simple form, and have a
continuous integration pipeline.
I have met people who were general devops and scripting people,
and could use Jenkins quite nicely.

While I understand the motivation for Pipeline (previously known
as Workflow), I can't say I'm very happy with the results.

Here are some of the pain points I've encountered with Pipeline
scripts:

  * Other than the most trivial of scripts, you need to be a
knowledgable Groovy programmer.  For example, to make a global
variable, you need to use a @Field. (What?!)  Most scripting
and devops people that I know don't really know Groovy.

So in my personal opinion, this is a sign of People Doing Things Wrong™

By this I mean that your Jenkinsfile should *not* be doing complex 
things. You should have shell scripts or equivalent to do the complex 
functionality. That lets you test each individual step in the phase on 
local developer machines. Then your pipeline should end up mostly being


But you cannot test everything locally, because you e.g. don't have 
build parameters, you might not have certain SSH credentials defined... 
That said I do tend to move everything to scripts, but this really 
defeats the purpose of almost all Jenkins plugins... And plugins gives 
you some integrations (especially with credentials) you don't have in 
scripts. And it's much easier to add build step for triggering e.g. call 
of another project and passing all parameters to it from current build 
(which BTW is overly hard with Groovy).


Regards,
Nux.

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fac125e7-9e6c-46f1-bbe7-42067660d98c%40mol.com.pl.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] A new user experience project for Jenkins

[Stephen Connolly]

On 27 May 2016 at 11:12, Stephen Connolly 
wrote:

>
>
> On 27 May 2016 at 07:59, Craig Rodrigues  wrote:
>
>> Hi,
>>
>> The new Jenkins UI looks nice, and will be a big improvement over the
>> existing UI.
>>
>> The original selling point of Jenkins was that even with the simplistic
>> forms-based UI,
>> someone could fill out a relatively simple form, and have a continuous
>> integration pipeline.
>> I have met people who were general devops and scripting people, and could
>> use Jenkins quite nicely.
>>
>> While I understand the motivation for Pipeline (previously known as
>> Workflow), I can't say I'm very happy with the results.
>>
>> Here are some of the pain points I've encountered with Pipeline scripts:
>>
>>- Other than the most trivial of scripts, you need to be a
>>knowledgable Groovy programmer.  For example, to make a global variable,
>>you need to use a @Field.  (What?!)  Most scripting and devops people that
>>I know don't really know Groovy.
>>
>> So in my personal opinion, this is a sign of People Doing Things Wrong™
>
> By this I mean that your Jenkinsfile should *not* be doing complex things.
> You should have shell scripts or equivalent to do the complex
> functionality. That lets you test each individual step in the phase on
> local developer machines. Then your pipeline should end up mostly being
>
> node {
>   try {
> sh "..."
> stash ...
>   } catch (...) {
> sh "..."
>   } finally {
> sh "..."
>   }
> }
> input "..."
> node {
>   unstash
>   sh "..."
> }
>
> Ok you may have to chain parameters between steps, etc. but what I see
> people doing instead is building up a whole big set of logic in the
> Jenkinsfile.
>
> Now there is nothing "wrong" in building up that login in your
> Jenkinsfile... but in my view it is Wrong™ because:
>
>- You now can only test this logic by running Jenkins builds.
>- You cannot unit test this logic, you can only run manual acceptance
>tests on the whole script
>- You will need to battle with the script approval process if security
>of your instance is important to you
>- You have tied yourself to Jenkins (which initially seems tempting
>for Jenkins, but people who feel tied to a system are then not free to
>explore other options and probably are more correctly tied to a "specific
>way of doing things", so they cannot even explore alternatives *within
>Jenkins*... then when they finally get fed-up they blame Jenkins rather
>than their choices in how to use Jenkins... so it ends up being a loss of
>Jenkins when people tie themselves to "*their way* of using Jenkins")
>
> For what it is worth, this last point is not just a problem for Jenkins,
we have the same issue with Maven.

Do you not like Maven? Perhaps what you really don't like is that the
people who wrote your pom.xml chose to make it a 10,000+ line epic rather
than encapsulate the logic into custom plugins and a custom lifecycle.

If you are Doing Maven The Right Way™ then your pom.xml should be


  4.0.0
  
  
...
  
  
  ...
  ...
  ...
  *custom-packaging*

  
... *insert dependencies here* ...
  

  

  
...
*custom-plugin*
...
*true*
  

  


If you have anything more that the above *then you have chosen to fight
Maven*. When you fight Maven, Maven *always* wins the war... which means
you loose

Other build systems (i'm looking at you gradle) make it easy to embed small
bits of custom logic and stave off having to stop for a second and think
about that custom logic and then embed that logic into a Maven plugin...
now that is indeed tempting for the once off project... but every time you
release a new version of that project, those are repeated builds. If the
process is really a once-off, just capture the output and check it into
source control ;-)

It is much better to slow down for a couple of minutes and encapsulate that
logic into a custom plugin that can make reuse easier.

(Note I will agree with anyone who complains that writing Maven plugins is
not as easy as it should be... but that is a different story that results
from most people refusing to even try)

>
>>- Documentation for Pipeline scripts isn't that great (although it
>>has definitely been improving).  In all honesty, I cannot point a junior
>>scripting person to write a good Pipeline script for developing a build
>>Pipeline.
>>
>> Documentation will improve.
>
>>
>>- The durable task plugin which invokes shell commands on Unix, and
>>batch jobs on Windows goes through an elaborate method for invoking shell
>>commands.  It is very, very difficult to grab the exit status of commands,
>>stderr, stdout, etc.  For a while, these wrappers would do things like not
>>detect when a command had terminated, etc. (Looks like this has been fixed
>>now)
>>
>> I hear you. It is a trade-off but being restartable 

Re: [Blue Ocean] A new user experience project for Jenkins

[Stephen Connolly]

On 27 May 2016 at 07:59, Craig Rodrigues  wrote:

> Hi,
>
> The new Jenkins UI looks nice, and will be a big improvement over the
> existing UI.
>
> The original selling point of Jenkins was that even with the simplistic
> forms-based UI,
> someone could fill out a relatively simple form, and have a continuous
> integration pipeline.
> I have met people who were general devops and scripting people, and could
> use Jenkins quite nicely.
>
> While I understand the motivation for Pipeline (previously known as
> Workflow), I can't say I'm very happy with the results.
>
> Here are some of the pain points I've encountered with Pipeline scripts:
>
>- Other than the most trivial of scripts, you need to be a
>knowledgable Groovy programmer.  For example, to make a global variable,
>you need to use a @Field.  (What?!)  Most scripting and devops people that
>I know don't really know Groovy.
>
> So in my personal opinion, this is a sign of People Doing Things Wrong™

By this I mean that your Jenkinsfile should *not* be doing complex things.
You should have shell scripts or equivalent to do the complex
functionality. That lets you test each individual step in the phase on
local developer machines. Then your pipeline should end up mostly being

node {
  try {
sh "..."
stash ...
  } catch (...) {
sh "..."
  } finally {
sh "..."
  }
}
input "..."
node {
  unstash
  sh "..."
}

Ok you may have to chain parameters between steps, etc. but what I see
people doing instead is building up a whole big set of logic in the
Jenkinsfile.

Now there is nothing "wrong" in building up that login in your
Jenkinsfile... but in my view it is Wrong™ because:

   - You now can only test this logic by running Jenkins builds.
   - You cannot unit test this logic, you can only run manual acceptance
   tests on the whole script
   - You will need to battle with the script approval process if security
   of your instance is important to you
   - You have tied yourself to Jenkins (which initially seems tempting for
   Jenkins, but people who feel tied to a system are then not free to explore
   other options and probably are more correctly tied to a "specific way of
   doing things", so they cannot even explore alternatives *within Jenkins*...
   then when they finally get fed-up they blame Jenkins rather than their
   choices in how to use Jenkins... so it ends up being a loss of Jenkins when
   people tie themselves to "*their way* of using Jenkins")


>- Documentation for Pipeline scripts isn't that great (although it has
>definitely been improving).  In all honesty, I cannot point a junior
>scripting person to write a good Pipeline script for developing a build
>Pipeline.
>
> Documentation will improve.

>
>- The durable task plugin which invokes shell commands on Unix, and
>batch jobs on Windows goes through an elaborate method for invoking shell
>commands.  It is very, very difficult to grab the exit status of commands,
>stderr, stdout, etc.  For a while, these wrappers would do things like not
>detect when a command had terminated, etc. (Looks like this has been fixed
>now)
>
> I hear you. It is a trade-off but being restartable is too much of a
killer feature, so I view it as worth the pain of some initial bugs.

>
>- It is very hard to figure out how to cancel a running Pipeline job.
>The UI link to "Click here to cancel" a Pipeline job is hidden in the build
>output, and often doesn't work.
>
> I hear you and feel your pain too.


> I understand that Jenkins is going through a big transition period.
> Hopefully at the end of the road, things will be much better.
> However, at this point in time, I would say that in many ways, the current
> direction is *worse* than the old way of doing things with the old
> Jenkins UI.
> The old way has problems, but it was easy to figure out, and didn't have a
> lot of these intermediate layers that try to abstract things out,
> but make things harder to figure out what is going on.
>
> --
> Craig
>
>
>
> On Thu, May 26, 2016 at 3:21 PM, James Dumay  wrote:
>
>>
>> Today we’ve made the source code 
>> available on Github, written a blog post
>>  and created
>> a video  explaining the
>> project in more detail. We will be posting more updates to both the blog
>> and mailing lists when there are more updates to share.
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAG%3DrPVdhtQabPM4PjowXGssk-Rpr7X6%3DfQZASCZo9cq99vTfcQ%40mail.gmail.com
> 

Re: Storing artifacts on file server (Mac+Win)

[Joen Joensen]

Thanks Thomas

I'm aware that an artifact repository is a good thing, however our projects
compile straight off git without grabbing any external dependencies. So
we're only looking to store the builds on a network device.

>> I think you can find the answer to your specific question here
.
Yeah that was exactly what I was looking for.

Thanks for your time,
Joen

On Thu, May 26, 2016 at 6:49 PM, Thomas Zoratto 
wrote:

> I keep this conversation here to possibly help other people with a similar
> question.
>
> ---
>
> It's not the only way but it's the cleanest way in my opinion when you
> have enough artifacts to fill your hard drive.
>
> I think the way you integrate the artifact repository with Jenkins depends
> on your projects. In a Maven project for example, you can configure your
> repository in your pom.xml in order to deploy artifacts on it
> automatically. Then, you can configure Maven to lookout for dependencies in
> your repository (instead of the default one).
>
> Also, there are some plugins (see this one
> )
> that can help to integrate your repo with Jenkins in various ways.
>
> I'm no expert here but I would definitely go for the artifact repository.
> However, if you really don't want it, I think you can find the answer to
> your specific question here
> .
>
> Good luck
>
> Thomas
>
>
> Le 26 mai 2016 à 17:22,  <> a écrit :
>
> Hi Thomas
>
> I know why we're running out of disk space, it's a virtual machine and our
> vm host is quite limited in space so expanding to the degree needed is not
> possible. However we do have plenty of space on our fileserver, just need
> to get jenkins to actually leverage it.
>
> I must admit I was hoping for something less than an artifact repository.
> All we want is for Jenkins to put it's data on our network drive. But if
> that is the only way I guess we'll have to do that.
>
> How does an artifact repository integrate with Jenkins? Will we be able to
> list our builds and grab the artifacts directly from Jenkins?
>
> Thanks for your reply
> Joen
>
> On Thu, May 26, 2016 at 4:54 PM,  <> wrote:
>
>> Hi,
>>
>> First you should check your build's logs policy (maybe you're running out
>> of space because of that).
>>
>> Then, I encourage you to use an artifact repository such as Nexus. You'll
>> be able to store your artifacts easily.
>>
>> Thomas
>>
>> Le 26 mai 2016 à 12:52,  a écrit :
>>
>> Hi Experts,
>>
>> I'm having problems with our master jenkins server running out of disk
>> space. I want to offload the builds to our file server.
>>
>> I'm trying to get Artifact Deployer to work but I'm unable to provide a
>> path that will work both on mac and windows.
>>
>> How can I do that? Any advise is appreciated!
>>
>> Thanks,
>> Joen
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/872270dd-a80f-4866-8b87-666987c28930%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 Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/gSBrn395j3c/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/DF75B476-8B6B-4F79-8767-99FD315AA2CF%40gmail.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 Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/gSBrn395j3c/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/481402f3-ab27-4ca0-b214-83865feed63a%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You 

Re: Re: Re: [Blue Ocean] A new user experience project for Jenkins

[James Dumay]

Don't worry - nothing will disappear :)

On Fri, May 27, 2016 at 6:25 PM  wrote:

> Sorry I meant will NOT disappear
>
>
>
> Von:Michael Neale 
> An:Jenkins Users ,
> Kopie:lars.meynb...@edict.de
> Datum:27.05.2016 10:02
> Betreff:Re: Re: [Blue Ocean] A new user experience project for
> Jenkins
> Gesendet von:jenkinsci-users@googlegroups.com
> --
>
>
>
> Well I hope the old doesn't go away! I don't think that is the intention.
> Pipeline-as-code is just a tidy starting point. There are a lot of
> freestyle jobs that people get a lot of value out of, and will for a long
> time. That non code type of working needs to be supported too, as you say -
> a merge of things.
>
> On Friday, May 27, 2016 at 5:54:46 PM UTC+10, lars.m...@edict.de wrote:
> As the old world will disappear the easy way to create build jobs is still
> available for the non-experts, but for me the new world of
> pipeline-as-code, its great because now we can handle the jenkins logic the
> same well as the rest as our code.
> Yes pipeline scripts are code but thats fine because we're developers.
>
> So for me the merge of old and new world is great for all.
>
>
>
>
> --
>
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to *jenkinsci-users+unsubscr...@googlegroups.com*
> .
>
>
> To view this discussion on the web visit
>
>
> *https://groups.google.com/d/msgid/jenkinsci-users/b230c4c2-2cdc-4c3c-827c-aba2d2c009f1%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 Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/Y9uzX4jVCsw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/OF074E4603.A0BED45A-ONC1257FC0.002E40EC-C1257FC0.002E4722%40gauselmann.com
> 
> .
>
>
> For more options, visit https://groups.google.com/d/optout.
>
-- 
James Dumay
Product Manager
CloudBees, Inc.
Skype: ap_myskype Twitter: i386

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

Antwort: Re: Re: [Blue Ocean] A new user experience project for Jenkins

[Lars . Meynberg]

Sorry I meant will NOT disappear 



Von:Michael Neale 
An: Jenkins Users , 
Kopie:  lars.meynb...@edict.de
Datum:  27.05.2016 10:02
Betreff:Re: Re: [Blue Ocean] A new user experience project for 
Jenkins
Gesendet von:   jenkinsci-users@googlegroups.com



Well I hope the old doesn't go away! I don't think that is the intention. 
Pipeline-as-code is just a tidy starting point. There are a lot of 
freestyle jobs that people get a lot of value out of, and will for a long 
time. That non code type of working needs to be supported too, as you say 
- a merge of things. 

On Friday, May 27, 2016 at 5:54:46 PM UTC+10, lars.m...@edict.de wrote:
As the old world will disappear the easy way to create build jobs is still 
available for the non-experts, but for me the new world of 
pipeline-as-code, its great because now we can handle the jenkins logic 
the same well as the rest as our code. 
Yes pipeline scripts are code but thats fine because we're developers. 

So for me the merge of old and new world is great for all. 







-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b230c4c2-2cdc-4c3c-827c-aba2d2c009f1%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/OF074E4603.A0BED45A-ONC1257FC0.002E40EC-C1257FC0.002E4722%40gauselmann.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] A new user experience project for Jenkins

[James Dumay]

My pleasure :)

On Friday, May 27, 2016 at 5:53:51 PM UTC+10, Dirk Heinrichs wrote:
>
> Am 27.05.2016 um 09:44 schrieb James Dumay:
>
> Tyler was nice enough to get out of bed to deploy the change to jenkins.io 
> - should now be readable on any device.
>
>
> Yes, looks much better now. Thanks a lot for having it fixed so fast!!!
>
> Bye...
>
> Dirk
> -- 
>
> *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
> *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
> *Tel*: +49 2226 159 (Ansage) 1149
> *Email*: d...@recommind.com 
> *Skype*: dirk.heinrichs.recommind
> www.recommind.com
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a8d395b3-dbe1-45ad-b79f-d1e0f8c2ae68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re: [Blue Ocean] A new user experience project for Jenkins

[Michael Neale]

Well I hope the old doesn't go away! I don't think that is the intention. 
Pipeline-as-code is just a tidy starting point. There are a lot of 
freestyle jobs that people get a lot of value out of, and will for a long 
time. That non code type of working needs to be supported too, as you say - 
a merge of things. 

On Friday, May 27, 2016 at 5:54:46 PM UTC+10, lars.m...@edict.de wrote:
>
> As the old world will disappear the easy way to create build jobs is still 
> available for the non-experts, but for me the new world of 
> pipeline-as-code, its great because now we can handle the jenkins logic the 
> same well as the rest as our code. 
> Yes pipeline scripts are code but thats fine because we're developers. 
>
> So for me the merge of old and new world is great for all. 
>
>
>
>
> --
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b230c4c2-2cdc-4c3c-827c-aba2d2c009f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] A new user experience project for Jenkins

[James Dumay]

Ill prepare a post for the mailing list tomorrow showing off some of our 
ideas for a visual editor - we want to make it just as easy to use Pipeline 
jobs as it is to use FreeStyle today. I agree, things are not where they 
are at but we are working hard on it. Ill ask someone to share some ideas 
that we have around making Pipeline easier to author and understand when in 
a Jenkinsfile too.

On Friday, May 27, 2016 at 5:45:10 PM UTC+10, Tom Fennelly wrote:
>
> On Friday, May 27, 2016 at 7:59:41 AM UTC+1, Craig Rodrigues wrote:
>>
>> Hi,
>>
>> The new Jenkins UI looks nice, and will be a big improvement over the 
>> existing UI.
>>
>> The original selling point of Jenkins was that even with the simplistic 
>> forms-based UI,
>> someone could fill out a relatively simple form, and have a continuous 
>> integration pipeline.
>> I have met people who were general devops and scripting people, and could 
>> use Jenkins quite nicely.
>>
>> While I understand the motivation for Pipeline (previously known as 
>> Workflow), I can't say I'm very happy with the results.
>>
>> Here are some of the pain points I've encountered with Pipeline scripts:
>>
>>- Other than the most trivial of scripts, you need to be a 
>>knowledgable Groovy programmer.  For example, to make a global variable, 
>>you need to use a @Field.  (What?!)  Most scripting and devops people 
>> that 
>>I know don't really know Groovy.
>>- Documentation for Pipeline scripts isn't that great (although it 
>>has definitely been improving).  In all honesty, I cannot point a junior 
>>scripting person to write a good Pipeline script for developing a build 
>>Pipeline.
>>- The durable task plugin which invokes shell commands on Unix, and 
>>batch jobs on Windows goes through an elaborate method for invoking shell 
>>commands.  It is very, very difficult to grab the exit status of 
>> commands, 
>>stderr, stdout, etc.  For a while, these wrappers would do things like 
>> not 
>>detect when a command had terminated, etc. (Looks like this has been 
>> fixed 
>>now)
>>- It is very hard to figure out how to cancel a running Pipeline 
>>job.  The UI link to "Click here to cancel" a Pipeline job is hidden in 
>> the 
>>build output, and often doesn't work.
>>
>> I understand that Jenkins is going through a big transition period.  
>> Hopefully at the end of the road, things will be much better.
>> However, at this point in time, I would say that in many ways, the 
>> current direction is *worse* than the old way of doing things with the 
>> old Jenkins UI.
>> The old way has problems, but it was easy to figure out, and didn't have 
>> a lot of these intermediate layers that try to abstract things out,
>> but make things harder to figure out what is going on.
>>
>> --
>> Craig
>>
>
> Hi Craig.
>
> I hear what you are saying. I think your comments are fair and are things 
> that we need to address.
>
> I think you'll agree that the lower level details relating to how specific 
> plugins work (durable task etc) is a "general" Jenkins/pipeline problem 
> that needs to be addressed i.e. is not really specific to the Blue Ocean 
> (BO) project.
>
> As for the usability issues wrt actually "using" Jenkins pipeline 
> (creating flow/execution scripts etc), they are most definitely issues that 
> are very relevant to the BO project. Some prototyping work 
>  was done in this 
> area a while back (and maybe there are other efforts too) and it seems 
> natural that the plan would be to pick one of these up again in some form 
> and build it into BO, making pipeline "author" more of a visual (drag & 
> drop .. fill out a form) kind of process.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e8e9ef9f-5636-4608-a27c-66af41aa0d65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] A new user experience project for Jenkins

[Tom Fennelly]

On Friday, May 27, 2016 at 7:59:41 AM UTC+1, Craig Rodrigues wrote:
>
> Hi,
>
> The new Jenkins UI looks nice, and will be a big improvement over the 
> existing UI.
>
> The original selling point of Jenkins was that even with the simplistic 
> forms-based UI,
> someone could fill out a relatively simple form, and have a continuous 
> integration pipeline.
> I have met people who were general devops and scripting people, and could 
> use Jenkins quite nicely.
>
> While I understand the motivation for Pipeline (previously known as 
> Workflow), I can't say I'm very happy with the results.
>
> Here are some of the pain points I've encountered with Pipeline scripts:
>
>- Other than the most trivial of scripts, you need to be a 
>knowledgable Groovy programmer.  For example, to make a global variable, 
>you need to use a @Field.  (What?!)  Most scripting and devops people that 
>I know don't really know Groovy.
>- Documentation for Pipeline scripts isn't that great (although it has 
>definitely been improving).  In all honesty, I cannot point a junior 
>scripting person to write a good Pipeline script for developing a build 
>Pipeline.
>- The durable task plugin which invokes shell commands on Unix, and 
>batch jobs on Windows goes through an elaborate method for invoking shell 
>commands.  It is very, very difficult to grab the exit status of commands, 
>stderr, stdout, etc.  For a while, these wrappers would do things like not 
>detect when a command had terminated, etc. (Looks like this has been fixed 
>now)
>- It is very hard to figure out how to cancel a running Pipeline job.  
>The UI link to "Click here to cancel" a Pipeline job is hidden in the 
> build 
>output, and often doesn't work.
>
> I understand that Jenkins is going through a big transition period.  
> Hopefully at the end of the road, things will be much better.
> However, at this point in time, I would say that in many ways, the current 
> direction is *worse* than the old way of doing things with the old 
> Jenkins UI.
> The old way has problems, but it was easy to figure out, and didn't have a 
> lot of these intermediate layers that try to abstract things out,
> but make things harder to figure out what is going on.
>
> --
> Craig
>

Hi Craig.

I hear what you are saying. I think your comments are fair and are things 
that we need to address.

I think you'll agree that the lower level details relating to how specific 
plugins work (durable task etc) is a "general" Jenkins/pipeline problem 
that needs to be addressed i.e. is not really specific to the Blue Ocean 
(BO) project.

As for the usability issues wrt actually "using" Jenkins pipeline (creating 
flow/execution scripts etc), they are most definitely issues that are very 
relevant to the BO project. Some prototyping work 
 was done in this area 
a while back (and maybe there are other efforts too) and it seems natural 
that the plan would be to pick one of these up again in some form and build 
it into BO, making pipeline "author" more of a visual (drag & drop .. fill 
out a form) kind of process.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0255e31e-b6d7-4d72-a329-33c8497de0ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] A new user experience project for Jenkins

[James Dumay]

Tyler was nice enough to get out of bed to deploy the change to jenkins.io
- should now be readable on any device.

I owe Tyler a case of beer now...

On Fri, May 27, 2016 at 4:49 PM James Dumay  wrote:

> Fixing the website right now. Sorry about that :(
>
> On Fri, May 27, 2016 at 4:19 PM nicolas de loof 
> wrote:
>
>> source code actually has been moved to
>> https://github.com/jenkinsci/blueocean
>>
>> 2016-05-27 8:16 GMT+02:00 Dirk Heinrichs :
>>
>>> Am 27.05.2016 um 00:21 schrieb James Dumay:
>>>
>>> Today we’ve made the source code
>>>  available on Github, written a blog
>>> post  and 
>>> created
>>> a video  explaining the
>>> project in more detail.
>>>
>>>
>>> Unfortunately, the blog post is not completely readable, because the
>>> schedule on the right side overlapps the text.
>>>
>>> Bye...
>>>
>>> Dirk
>>> --
>>>
>>> *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
>>> *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
>>> *Tel*: +49 2226 159 (Ansage) 1149
>>> *Email*: d...@recommind.com
>>> *Skype*: dirk.heinrichs.recommind
>>> www.recommind.com
>>>
>> --
>>>
>> You received this message because you are subscribed to the Google Groups
>>> "Jenkins Users" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/53fe65f9-348b-f110-c9f6-578d6eaa18be%40recommind.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 Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/Y9uzX4jVCsw/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm_SMmWeS93A7U9x19Z%2BG_4oEzaV_-nMO%3D6Y4pb3v2VGw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> James Dumay
> Product Manager
> CloudBees, Inc.
> Skype: ap_myskype Twitter: i386
>
-- 
James Dumay
Product Manager
CloudBees, Inc.
Skype: ap_myskype Twitter: i386

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

Re: [Blue Ocean] A new user experience project for Jenkins

[Craig Rodrigues]

Hi,

The new Jenkins UI looks nice, and will be a big improvement over the
existing UI.

The original selling point of Jenkins was that even with the simplistic
forms-based UI,
someone could fill out a relatively simple form, and have a continuous
integration pipeline.
I have met people who were general devops and scripting people, and could
use Jenkins quite nicely.

While I understand the motivation for Pipeline (previously known as
Workflow), I can't say I'm very happy with the results.

Here are some of the pain points I've encountered with Pipeline scripts:

   - Other than the most trivial of scripts, you need to be a knowledgable
   Groovy programmer.  For example, to make a global variable, you need to use
   a @Field.  (What?!)  Most scripting and devops people that I know don't
   really know Groovy.
   - Documentation for Pipeline scripts isn't that great (although it has
   definitely been improving).  In all honesty, I cannot point a junior
   scripting person to write a good Pipeline script for developing a build
   Pipeline.
   - The durable task plugin which invokes shell commands on Unix, and
   batch jobs on Windows goes through an elaborate method for invoking shell
   commands.  It is very, very difficult to grab the exit status of commands,
   stderr, stdout, etc.  For a while, these wrappers would do things like not
   detect when a command had terminated, etc. (Looks like this has been fixed
   now)
   - It is very hard to figure out how to cancel a running Pipeline job.
   The UI link to "Click here to cancel" a Pipeline job is hidden in the build
   output, and often doesn't work.

I understand that Jenkins is going through a big transition period.
Hopefully at the end of the road, things will be much better.
However, at this point in time, I would say that in many ways, the current
direction is *worse* than the old way of doing things with the old Jenkins
UI.
The old way has problems, but it was easy to figure out, and didn't have a
lot of these intermediate layers that try to abstract things out,
but make things harder to figure out what is going on.

--
Craig



On Thu, May 26, 2016 at 3:21 PM, James Dumay  wrote:

>
> Today we’ve made the source code 
> available on Github, written a blog post
>  and created
> a video  explaining the
> project in more detail. We will be posting more updates to both the blog
> and mailing lists when there are more updates to share.
>
>

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

Re: [Blue Ocean] A new user experience project for Jenkins

[James Dumay]

Fixing the website right now. Sorry about that :(

On Fri, May 27, 2016 at 4:19 PM nicolas de loof 
wrote:

> source code actually has been moved to
> https://github.com/jenkinsci/blueocean
>
> 2016-05-27 8:16 GMT+02:00 Dirk Heinrichs :
>
>> Am 27.05.2016 um 00:21 schrieb James Dumay:
>>
>> Today we’ve made the source code 
>> available on Github, written a blog post
>>  and created
>> a video  explaining the
>> project in more detail.
>>
>>
>> Unfortunately, the blog post is not completely readable, because the
>> schedule on the right side overlapps the text.
>>
>> Bye...
>>
>> Dirk
>> --
>>
>> *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
>> *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
>> *Tel*: +49 2226 159 (Ansage) 1149
>> *Email*: d...@recommind.com
>> *Skype*: dirk.heinrichs.recommind
>> www.recommind.com
>>
> --
>>
> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>>
> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>>
> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/53fe65f9-348b-f110-c9f6-578d6eaa18be%40recommind.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 Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/Y9uzX4jVCsw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm_SMmWeS93A7U9x19Z%2BG_4oEzaV_-nMO%3D6Y4pb3v2VGw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
James Dumay
Product Manager
CloudBees, Inc.
Skype: ap_myskype Twitter: i386

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

Re: [Blue Ocean] A new user experience project for Jenkins

[nicolas de loof]

source code actually has been moved to
https://github.com/jenkinsci/blueocean

2016-05-27 8:16 GMT+02:00 Dirk Heinrichs :

> Am 27.05.2016 um 00:21 schrieb James Dumay:
>
> Today we’ve made the source code 
> available on Github, written a blog post
>  and created
> a video  explaining the
> project in more detail.
>
>
> Unfortunately, the blog post is not completely readable, because the
> schedule on the right side overlapps the text.
>
> Bye...
>
> Dirk
> --
>
> *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
> *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
> *Tel*: +49 2226 159 (Ansage) 1149
> *Email*: d...@recommind.com
> *Skype*: dirk.heinrichs.recommind
> www.recommind.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/53fe65f9-348b-f110-c9f6-578d6eaa18be%40recommind.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [Blue Ocean] A new user experience project for Jenkins

[Dirk Heinrichs]

Am 27.05.2016 um 00:21 schrieb James Dumay:

> Today we’ve made the source code
> available on Github, written a
> blog post
> and
> created a video
> explaining the project in
> more detail.

Unfortunately, the blog post is not completely readable, because the
schedule on the right side overlapps the text.

Bye...

Dirk
-- 

*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com 
*Skype*: dirk.heinrichs.recommind
www.recommind.com 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/53fe65f9-348b-f110-c9f6-578d6eaa18be%40recommind.com.
For more options, visit https://groups.google.com/d/optout.

Antwort: [Blue Ocean] A new user experience project for Jenkins

[Lars . Meynberg]

Seems to be cool stuff. I tried to install the plugin on our Jenkins as 
where switching to pipeline building at the moment but couldnt find the 
plugin in the update center.
But the readme of the describes it more as a standalone installation:
Running Blue Ocean
$ cd blueocean-plugin
$ mvn hpi:run
Then open http://localhost:8080/jenkins/blue to start using Blue Ocean.



Von:James Dumay 
An: Jenkins Users , 
Datum:  27.05.2016 00:22
Betreff:[Blue Ocean] A new user experience project for Jenkins
Gesendet von:   jenkinsci-users@googlegroups.com



Hi Jenkins users,

Today I am happy to announce the open sourcing of a new user experience 
for Jenkins called Blue Ocean.

We are looking to build an excellent experience around Pipeline and 
Freestyle jobs with a focus on developer experience - how you as a 
developer build better automation, easily diagnose failures, integrate 
with tools like Github, Bitbucket or Slack and onboard new team members. 
These are goals of the uttermost importance to this project.

We realise that we can’t do this alone and it will take more than just 
Jenkins developers to make this effort successful. We need to hear from 
the Jenkins user community about their thoughts on the project, where it 
is heading and how we can help you hone your craft and build better 
software using Jenkins. 

Today we’ve made the source code available on Github, written a blog post 
and created a video explaining the project in more detail. We will be 
posting more updates to both the blog and mailing lists when there are 
more updates to share.

If you have any questions or comments please reply to this post and I’ll 
be more than happy to answer any questions you may have :)

Thanks,
James
-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8da10afa-bbe8-4d6f-812c-b9a286f64569%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 Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/OF918899CD.A13AC5E0-ONC1257FC0.0021DBA1-C1257FC0.00220C48%40gauselmann.com.
For more options, visit https://groups.google.com/d/optout.