Re: Jenkins 2.0 alpha release available

2016-04-11 Thread Fadi Al-Farah
Security needs a little bit of a rework in my opinion. What I mean by that is, I think it's a bad idea to ONLY have one method of logging in. Currently the admin can only choose ONE of the following: - Delegate to servlet container. - Jenkins’ own user database. - LDAP. - Unix user/group

Re: Jenkins 2.0 alpha release available

2016-04-09 Thread Daniel Beck
On 09.04.2016, at 20:21, jenkins user wrote: > I installed it to a Windows box via the msi package. When I try to access it > via the browser, it's asking me about the username and password (basic > authentication prompt). What are the credentials? Did you download the

Re: Jenkins 2.0 alpha release available

2016-04-09 Thread jenkins user
I installed it to a Windows box via the msi package. When I try to access it via the browser, it's asking me about the username and password (basic authentication prompt). What are the credentials? On Tuesday, March 1, 2016 at 1:39:22 AM UTC+2, R Tyler Croy wrote: > > As I mention in this blog

Re: Jenkins 2.0 alpha release available

2016-03-29 Thread Daniel Beck
On 29.03.2016, at 18:44, R. Tyler Croy wrote: > Use the system property `jenkins.install.runSetupWizard` and set to `false` in > your /etc/default/jenkins or wherever your JENKINS_ARGS might be defined Are you sure about that? AFAIU that system property can only enable (to

Re: Jenkins 2.0 alpha release available

2016-03-29 Thread Daniel Beck
On 29.03.2016, at 17:21, Marcos Mendez wrote: > Is there a way to automatically skip/disable that initial setup wizard? I've > got everything already pre-configured and just want to use the new war file. To clarify, is this e.g. a Docker container where you

Re: Jenkins 2.0 alpha release available

2016-03-29 Thread Marcos Mendez
Awesome! Thank you! On Tuesday, March 29, 2016 at 12:44:45 PM UTC-4, R Tyler Croy wrote: > > (replies inline) > > On Tue, 29 Mar 2016, Marcos Mendez wrote: > > > HI, > > > > Is there a way to automatically skip/disable that initial setup wizard? > > I've got everything already pre-configured

Re: Jenkins 2.0 alpha release available

2016-03-29 Thread R. Tyler Croy
(replies inline) On Tue, 29 Mar 2016, Marcos Mendez wrote: > HI, > > Is there a way to automatically skip/disable that initial setup wizard? > I've got everything already pre-configured and just want to use the new war > file. Use the system property `jenkins.install.runSetupWizard` and set

Re: Jenkins 2.0 alpha release available

2016-03-29 Thread Marcos Mendez
HI, Is there a way to automatically skip/disable that initial setup wizard? I've got everything already pre-configured and just want to use the new war file. Regards, Marcos On Monday, February 29, 2016 at 6:39:22 PM UTC-5, R Tyler Croy wrote: > > As I mention in this blog post: >

Re: Jenkins 2.0 alpha release available

2016-03-26 Thread Daniel Beck
On 26.03.2016, at 19:02, David Karlsen wrote: > was it introduced in a specific version? Email-ext plugin 2.41. Not mentioned in its changelog, unfortunately. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To

Re: Jenkins 2.0 alpha release available

2016-03-26 Thread Vincent Latombe
You need the corresponding plugin installed ( https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin). It is mentioned in the documentation but it could be worth adding a link. Vincent 2016-03-26 19:02 GMT+01:00 David Karlsen : > Hm - I followed those links and

Re: Jenkins 2.0 alpha release available

2016-03-26 Thread David Karlsen
Hm - I followed those links and found https://jenkins.io/doc/pipeline/steps/email-ext/#emailext-extended-email but got: "java.lang.NoSuchMethodError: No such DSL method 'emailext' found among [archive, bat, build, catchError, checkout, checkpoint, deleteDir, dir, dockerFingerprintFrom,

Re: Jenkins 2.0 alpha release available

2016-03-26 Thread Daniel Beck
Given the thread title I'd like to point out we're now in beta: https://jenkins.io/blog/2016/03/24/jenkins-2-beta-released/ - On 25.03.2016, at 23:47, E wrote: > I cannot find documentation for the Jenkinsfile DSL format. It should be > linked on the announcement page

Re: Jenkins 2.0 alpha release available

2016-03-25 Thread E
I cannot find documentation for the Jenkinsfile DSL format. It should be linked on the announcement page at (https://jenkins-ci.org/2.0/ and https://jenkins.io/2.0/) so that all the people who come will get a chance to look at it. On Monday, February 29, 2016 at 3:39:22 PM UTC-8, R Tyler Croy

Re: Jenkins 2.0 alpha release available

2016-03-23 Thread Daniel Beck
On 23.03.2016, at 14:31, Guido Zockoll wrote: > In Jenkins 2 i cannot find an option to inject those files into the > Jenkinsfile based Pipeline. I only found an example with references > ~/.m2/settings.xml in the script, but how can i reference a provided settings >

Re: Jenkins 2.0 alpha release available

2016-03-23 Thread Guido Zockoll
I tried alpha-4 and its really a great step. In the meantime i also looked at gitlab-ci (and Travis CI) and i am glad that we now have those job definitions files in Jenkins, too. I am heavily user the config file provider plugin to inject a settings.xml file into my jobs in Jenkins 1. In

Re: Jenkins 2.0 alpha release available

2016-03-22 Thread Daniel Beck
Thanks for your feedback! On 22.03.2016, at 17:03, Truc Nguyen wrote: > 1. Offline executor > > It looks like a Pipeline job does not appear in the left side panel. > It was useful in order to abort a pipeline without having to open the > pipeline job’s page. > Any

Re: Jenkins 2.0 alpha release available

2016-03-22 Thread Truc Nguyen
Hi, I would like to provide some feedback on Jenkins 2.0 alpha releases. So I hope this is the right place to ask questions :-) BTW I really like the highlights that Jenkins 2.0 alpha release already provide. Looking forward to the next steps! Questions 1. Offline executor It looks like a

Re: Jenkins 2.0 alpha release available

2016-03-15 Thread Kohsuke Kawaguchi
I created https://issues.jenkins-ci.org/browse/JENKINS-33557 to track this. Any further confirmations from other people are welcome. 2016-03-14 23:12 GMT-07:00 as_kumlali via Jenkins Users < jenkinsci-users@googlegroups.com>: > alpha-3 still needs -Dhttp.proxyHost and -Dhttp.proxyPort in

Re: Jenkins 2.0 alpha release available

2016-03-15 Thread as_kumlali via Jenkins Users
alpha-3 still needs -Dhttp.proxyHost and -Dhttp.proxyPort in JAVA_OPTS of catalina.bat. Otherwise blank pop-up shows up indefinitely. 9 Mart 2016 Çarşamba 14:47:07 UTC+2 tarihinde Daniel Beck yazdı: > > > On 09.03.2016, at 11:08, as_kumlali via Jenkins Users < > jenkins...@googlegroups.com >

Re: Jenkins 2.0 alpha release available

2016-03-11 Thread R. Tyler Croy
A follow-up on this thread, we released alpha3 today with the new security setup and some other UI improvements, read more about it here: On Mon, 29 Feb 2016, R. Tyler Croy wrote: > As I mention in this blog post: >

Re: Jenkins 2.0 alpha release available

2016-03-09 Thread Sven Schultschik
1.) Sounds good. Is there anywhere a scedule for releases? 2.) Will plugin developement be changed anyhow for Jenkins 2.0? Am Mittwoch, 9. März 2016 13:47:07 UTC+1 schrieb Daniel Beck: > > > On 09.03.2016, at 11:08, as_kumlali via Jenkins Users < > jenkins...@googlegroups.com > wrote: > > > I

Re: Jenkins 2.0 alpha release available

2016-03-09 Thread Daniel Beck
On 09.03.2016, at 11:08, as_kumlali via Jenkins Users wrote: > I figured out that I mixed where and how to define proxy configuration for > Java applications: > http://docs.oracle.com/javase/6/docs/technotes/guides/net/proxies.html > > Adding

Re: Jenkins 2.0 alpha release available

2016-03-09 Thread Sven Schultschik
Hi, we have a very complex network infrastructure and not every computer is allowed to access the internet. So Jenkins should also work without any internet connection. In earlier releases there was no problem when Jenkins doesn't have any internet connection. The interessting part is, that

Re: Jenkins 2.0 alpha release available

2016-03-09 Thread as_kumlali via Jenkins Users
I figured out that I mixed where and how to define proxy configuration for Java applications: http://docs.oracle.com/javase/6/docs/technotes/guides/net/proxies.html Adding -Dhttp.proxyHost, -Dhttp.proxyPort, -Dhttps.proxyHost, -Dhttps.proxyPort and -Dhttp.nonProxyHosts to JAVA_OPTS in

Re: Jenkins 2.0 alpha release available

2016-03-08 Thread as_kumlali via Jenkins Users
Our security team confirmed that; - my requests do not pass through proxy server although I use HTTP_PROXY, HTTPS_PROXY and so. - my computer try to access following IPs which are blocked by our firewall: - 199.193.196.24 (Domain name is 199-193-196-24.contegix.com) -

Re: Jenkins 2.0 alpha release available

2016-03-08 Thread as_kumlali via Jenkins Users
I am also behind proxy and having the same problem. The blank popup is still visible after even minutes. Adding HTTP_PROXY, HTTPS_PROXY, NO_PROXY, http_proxy, https_proxy and no_proxy to catalina.bat do not work. I am going to check with security team whether there is something blocked. When

Re: Jenkins 2.0 alpha release available

2016-03-02 Thread Byron Kim
I should note that I ran the container without mapping and the Initial Setup window did pop up so I guess that should be valid. I can't remember exactly, but I had the config.xml file still in my directory and I think Jenkins was reading that file initially. I can't remember if moving the

Re: Jenkins 2.0 alpha release available

2016-03-02 Thread Byron Kim
I'm using the new Dockerfile and grabbed all the new files. My Dockerfile has some added steps so I put those in as well and I mount it to a specific volume. I ran the new container against the volume mount and can't really "tell" if I'm on the correct release or not. It does say

Re: Jenkins 2.0 alpha release available

2016-03-02 Thread R. Tyler Croy
(replies inline) On Wed, 02 Mar 2016, Mike Bayliss wrote: > OK - I've the debian/ubuntu package - it's at > http://pkg.jenkins-ci.org/debian-rc/binary/jenkins_2.0_all.deb. > > The link needs correcting on the 2.0 landing page. I've corrected this

Re: Jenkins 2.0 alpha release available

2016-03-02 Thread Mike Bayliss
OK - I've the debian/ubuntu package - it's at http://pkg.jenkins-ci.org/debian-rc/binary/jenkins_2.0_all.deb. The link needs correcting on the 2.0 landing page. Mike On Wed, Mar 2, 2016 at 2:59 PM, Mike Bayliss wrote: > Is the Ubuntu package supposed to be available

Re: Jenkins 2.0 alpha release available

2016-03-01 Thread Daniel Beck
On 01.03.2016, at 15:59, kondarre...@gmail.com wrote: > I am behind proxy and a blank popup (I guess the registration screen) is > blocking me from accessing Jenkins web interface. Can you please suggest a > work around. This should actually disappear after a while (30 seconds?) and tell you

Re: Jenkins 2.0 alpha release available

2016-03-01 Thread Daniel Beck
On 01.03.2016, at 17:26, Eric Smalling wrote: > Has anyone posted a Docker Hub image yet? jenkinsci/jenkins:2.0-alpha-2 should be it. I added a link to https://jenkins-ci.org/2.0/ -- You received this message because you are subscribed to the Google Groups

Re: Jenkins 2.0 alpha release available

2016-03-01 Thread Baptiste Mathus
FWIW, jenkinsci/jenkins:2.0-alpha-2 is also available. See https://hub.docker.com/r/jenkinsci/jenkins/tags/ Cheers 2016-03-01 21:08 GMT+01:00 Christophe Furmaniak < christophe.furmaniak...@gmail.com>: > I just published one here: https://hub.docker.com/r/looztra/jenkins-20/ > (just adapted the

Re: Jenkins 2.0 alpha release available

2016-03-01 Thread Christophe Furmaniak
I just published one here: https://hub.docker.com/r/looztra/jenkins-20/ (just adapted the "official" Dockerfile to the 2.0 dl url) Le mardi 1 mars 2016 17:26:26 UTC+1, Eric Smalling a écrit : > > Has anyone posted a Docker Hub image yet? (I see several "jenkins2" named > ones out there, but

Re: Jenkins 2.0 alpha release available

2016-03-01 Thread Nicolas Geraud
Yes, I mean the tabs in the configuration pages. Too late to change, thanks for the reply. Le mardi 1 mars 2016 17:07:47 UTC+1, Kohsuke Kawaguchi a écrit : > > > > 2016-03-01 1:11 GMT-08:00 Nicolas Geraud >: > >> I think that tabs should be on a single row with left and

Re: Jenkins 2.0 alpha release available

2016-03-01 Thread Eric Smalling
Has anyone posted a Docker Hub image yet? (I see several "jenkins2" named ones out there, but the dates on them lead me to believe they are not this.) On Monday, February 29, 2016 at 5:39:22 PM UTC-6, R Tyler Croy wrote: > > As I mention in this blog post: >

Re: Jenkins 2.0 alpha release available

2016-03-01 Thread Kohsuke Kawaguchi
2016-03-01 1:11 GMT-08:00 Nicolas Geraud : > I think that tabs should be on a single row with left and right arrow to > display hidden tabs like in > https://www.google.com/design/spec/components/tabs.html#tabs-usage. > > Is this has been discussed elsewhere ? > I

Re: Jenkins 2.0 alpha release available

2016-03-01 Thread kondarreddy
I am behind proxy and a blank popup (I guess the registration screen) is blocking me from accessing Jenkins web interface. Can you please suggest a work around. Thank you On Monday, February 29, 2016 at 5:39:22 PM UTC-6, R Tyler Croy wrote: > > As I mention in this blog post: >

Re: Jenkins 2.0 alpha release available

2016-03-01 Thread Maciej Jaros
Dirk Heinrichs (2016-03-01 08:31): Am 01.03.2016 um 00:39 schrieb R. Tyler Croy: You can read more about it on the 2.0 landing page (https://jenkins-ci.org/2.0/) The link to "the 2.0 plan" on this page is dead. The link: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0 Fix:

Re: Jenkins 2.0 alpha release available

2016-03-01 Thread Nicolas Geraud
I think that tabs should be on a single row with left and right arrow to display hidden tabs like in https://www.google.com/design/spec/components/tabs.html#tabs-usage. Is this has been discussed elsewhere ? Le mardi 1 mars 2016 00:39:22 UTC+1, R Tyler Croy a écrit : > > As I mention in this

Re: Jenkins 2.0 alpha release available

2016-02-29 Thread Dirk Heinrichs
Am 01.03.2016 um 00:39 schrieb R. Tyler Croy: > You can read more > about it on the 2.0 landing page (https://jenkins-ci.org/2.0/) The link to "the 2.0 plan" on this page is dead. Bye... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*,