Re: Jenkins 2.7 vs 2.4
Hi James, yes, I'm using the 2.46.1 version. But I can use Blue Ocean only for browsing activity, because our projects are stored under SVN while Blue Ocean seems to support only GIT projects, so I must switch to "classic UI" every time I have to change some build configuration. Bye Filippo Il giorno giovedì 20 aprile 2017 07:57:20 UTC+2, James Dumay ha scritto: > > Hi Filippo, > > Great to hear that you are upgrading to use Blue Ocean :) > > While Blue Ocean is compatible with 2.7.1 and above I do strongly advise > using the latest LTS, 2.46.1, as there have been several nasty security > vulnerabilities. > > All the best, > > James > > On Tuesday, April 18, 2017 at 8:52:14 PM UTC+10, Filippo wrote: >> >> Hello, >> I've installed Jenkins 2.4 on a CentOS server via yum. I would like to >> try Blue Ocean, that runs only with Jenkins v 2.7. >> So I opened the RedHat repository (https://pkg.jenkins.io/redhat/) and >> noticed that the 2.7 rpm is dated 2016/05/29, while the 2.4 is dated >> 2017/02/13. >> The question is: why is the 2.7 so older than 2.4? >> And are the other packages (2.8 and 2.9) also compatible with blue ocean? >> >> 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/bff9c00d-8471-4d2f-8600-c0b929f48ba7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Jenkins 2.7 vs 2.4
Hello, I've installed Jenkins 2.4 on a CentOS server via yum. I would like to try Blue Ocean, that runs only with Jenkins v 2.7. So I opened the RedHat repository (https://pkg.jenkins.io/redhat/) and noticed that the 2.7 rpm is dated 2016/05/29, while the 2.4 is dated 2017/02/13. The question is: why is the 2.7 so older than 2.4? And are the other packages (2.8 and 2.9) also compatible with blue ocean? 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/2d4e92fb-a2b6-46fd-8157-41ea58ffeebe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins 2.7 vs 2.4
My fault, I though that 2.55 was 2.5.5. Sorry. Thanks Il giorno martedì 18 aprile 2017 13:13:35 UTC+2, Richard Bywater ha scritto: > > Not quite sure where you are seeing that date against 2.4. The results > from my view of that list is: > jenkins-2.4-1.1.noarch.rpm 2016/05/15 65.4M > jenkins-2.7-1.1.noarch.rpm 2016/05/29 65.4M > > So 2.7 is newer than 2.4. I believe you'll find that Blue Ocean is 2.7+ so > you should probably grab the latest version that you feel comfortable with > (2.55 is the latest available there) > > Richard. > > > On Tue, 18 Apr 2017 at 22:52 Filippo <filippo...@gmail.com > > wrote: > >> Hello, >> I've installed Jenkins 2.4 on a CentOS server via yum. I would like to >> try Blue Ocean, that runs only with Jenkins v 2.7. >> So I opened the RedHat repository (https://pkg.jenkins.io/redhat/) and >> noticed that the 2.7 rpm is dated 2016/05/29, while the 2.4 is dated >> 2017/02/13. >> The question is: why is the 2.7 so older than 2.4? >> And are the other packages (2.8 and 2.9) also compatible with blue ocean? >> >> 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-use...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/2d4e92fb-a2b6-46fd-8157-41ea58ffeebe%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/2d4e92fb-a2b6-46fd-8157-41ea58ffeebe%40googlegroups.com?utm_medium=email_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins 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/36fdb4c9-e84b-4b0b-b686-75dcbe4436a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: is there any plugins that just sets up a Google cloud environment?
I have not and as awesome as it may look I don't think we're in a position to switch to it right now, thanks tho. On Fri, Apr 12, 2019 at 7:28 PM Jenn Briden wrote: > Have you looked at using Jenkins X? > > On Fri, Apr 12, 2019 at 8:56 AM SpikeX > wrote: > >> Hello, >> >> I'm looking for a plugin that sets up the environment before a job is ran >> so that the job can use gsuti/gcloud utilities and spin up instances/do >> stuff on Google Cloud. >> >> Looking at the plugins on the registry none of them seems to do that >> and/or work. The closest is the Oauth plugin, but that seems more oriented >> to getting the service account set up than prepping an environment and I've >> been unable to get it to work (no secret can even be selected from a >> binding). Also this plugin doesn't work with pipelines and the >> recommendation is to just upload the json key as a secret file. This is >> what I'm doing, however it basically leaves to each build job to duplicate >> the code necessary to set up the environment so that the google sdk works >> with out project. The Google SDK plugin is outdated and when I tried I >> could not get it to work either. All the other plugins seem to work with >> specific subcomponents like storage or the GCE one is oriented to spinning >> up slaves on GCE, not use GCE as part of the build process. >> >> any pointers? >> >> thanks, >> >> Spike >> >> -- >> 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/951ae074-811d-42a1-acbc-e2076857f268%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-users/951ae074-811d-42a1-acbc-e2076857f268%40googlegroups.com?utm_medium=email_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins 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/CAOC%3D136Vg7DqsT6%2Bua5O4aoo%2BwCqY8s3ao40hdnBVS8SkdfB2Q%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CAOC%3D136Vg7DqsT6%2Bua5O4aoo%2BwCqY8s3ao40hdnBVS8SkdfB2Q%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Filippo "Spike" Morelli Xcalar Technical Staff (415)-727-7453 -- 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/CACqu10PGmK-_oNn-Wsxyjo3y_PqoNDceKcmvUGsn-SH4zokdxw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [workflow-plugin] SBT job complete succesfully but the job failed
Hi Jesse, Thanks for your time. Adding the Stage directive on top of the file solves it, is it mandatory? On 12 August 2015 at 22:15, Jesse Glick jgl...@cloudbees.com wrote: On Saturday, August 1, 2015 at 1:18:00 PM UTC-4, Filippo De Luca wrote: Recording test results Running: Allocate node : Body : End Running: Allocate node : End Running: End of Workflow Finished: FAILURE Why? how can I investigate more? Normally the failure cause should be printed to the build log, of course. You can look in the XML files in the build directory to see if there is a hidden explanation. Or if you can reproduce from scratch, file a bug. -- 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/r885XX1w7wY/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/a40e88ba-4144-4abf-9e73-e3e9cd9a976a%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/a40e88ba-4144-4abf-9e73-e3e9cd9a976a%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- [image: --] Filippo De Luca [image: http://]about.me/FilippoDeLuca http://about.me/FilippoDeLuca?promo=email_sig -- 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%2B%2B7rO5P%2BLa6B85-92K9rxPT4-Ob5YUur2qsjqooQ44c%2BfY_4g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[workflow-plugin] SBT job complete succesfully but the job failed
Hi, I have written a simple workflow for a sbt based project. The sbt command complete succesfully but the job failed: [info] Tests: succeeded 59, failed 0, canceled 0, ignored 0, pending 0 [info] All tests passed. [info] Passed: Total 59, Failed 0, Errors 0, Passed 59 [success] Total time: 415 s, completed Jul 31, 2015 5:27:07 PM Running: General Build Step Archiving artifacts Running: General Build Step Recording test results Running: Allocate node : Body : End Running: Allocate node : End Running: End of Workflow Finished: FAILURE Why? how can I investigate more? -- 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/dfe08520-f41f-4da5-82b3-40e6b952d5f9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
