Re: Parametrized build for E2E testing in different environments

[Eric Pyle]

Assuming you are using a Freestyle project (not Pipeline) you could use 
the Template Project Plugin 
https://plugins.jenkins.io/template-project/. You create a template job 
which contains all the common functionality, and then in the separate 
job for each environment you add the template job as a build step (Use 
builders from another project).


-Eric

On 5/28/2020 7:39 AM, Alberto Scotto wrote:

Hi,

Long story short: is it possible to have a job which builds another 
job, in particular a parametrized one?


We have a Cucumber+Selenium project which runs E2E tests against our 
different test environments.

Something pretty standard.

For this kind of job, the parametrized build seems to be the best idea.
Otherwise we would have to create one job for each test environment. 
duplicating the job configuration.
Then it would be a nightmare to keep all the job configurations in 
sync, in case we need to change something.


But there's a problem with the build history.
I want to see a separate build history for each environment.
It doesn't make sense to have an interleaved history. It would be messy.

So an easy solution could be to have a job which calls the 
parametrized job passing the actual value for the environment.
This way the build histories would be kept separate, and at the same 
time we would also get to avoid duplication.


Is that possible? Or do you have any other idea/solution?

Thank you very much.

Alberto
--
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/5f64c8d1-db57-4002-9aa7-5e574638b76c%40googlegroups.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/0bca5d47-881f-4b61-1078-fc854c63a1dd%40cd-adapco.com.

Performance plugin - how to use both relative and error threshold?

[David Balažic]

Hi!

Using the post-build action "Publish Performance test result report" from 
the performance plugin [1], is it possible to 
have both relative and error threshold to detect/make build failures?

This is under the evaluation mode / Standard Mode.

If not, where to post RFEs?
I don't see an Issues tab on its github page [2].


[1] https://plugins.jenkins.io/performance/
[2] https://github.com/jenkinsci/performance-plugin

Regards,
David

-- 
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/d0cac7d3-d4f5-4b1c-9a23-caaf74aca113%40googlegroups.com.

Jenkins UI/UX hackfest - Updates and Ideas for contribution

[Oleg Nenashev]

Hi all,


Thanks a lot to everyone who has already contributed to the Jenkins
project! We have delivered a number of important changes which will help
Jenkins users, see the highlights below. So far we’ve got 39 participants
 who have
reported their contributions to the UI/UX hackfest tracking repository. Full
list of reported contributions can be found here
.


If you have not contributed yet and would like to participate, there is
still time to do it! If you are looking for hot issues within our project
tracks
,
here are some hints:

   -

   Newcomer-friendly issues:
   -

  UI/UX issues in Jenkins components
  

  -

  Jenkins Documentation on jenkins.io
  

  -

  Documentation in Jenkins components: Jira
  
,
  GitHub Issues
  

  -

   UX Testing needed:
   -

  Read-only Jenkins Configuration (HOWTO
  

  )
  -

  UI Accessibility: Tables to Divs migration (HOWTO
  

  )
  -

  Dark Theme (HOWTO
  )
  -

   Reviews needed:
   -

  Jenkins Documentation pull requests (see here
  )
  -

  Plugin documentation  migration pull requests (query
  )
  -

  Any other open pull request which improve UI/IX
  -

   Spread The Word
   -

  Report your Jenkins success story on https://jenkinsistheway.io/


*More info and project ideas*


   - We have also had 7 training sessions for Jenkins users and
   contributors. They can help you to get started with particular topics.
   Recordings and Materials can be found here:
   https://github.com/jenkinsci/ui-ux-hackfest-2020/tree/master/presentations
   - You can also find  more info and issue links on the Hackfest website:
   https://www.jenkins.io/events/online-hackfest/2020-uiux/

Hackfest highlights

   -

   Preview release: Read-only Jenkins Configuration -  Announcement Blogpost
   .
   We have got a number of fixes and testing reports from participants, thanks
   all!
   -

   Dark Theme PoC is available for evaluation and testing:
   jenkinsci/dark-theme . There
   were significant changes in the Jenkins core to make it possible and to
   simplify development of UI themes in the future
   -

   Many UX improvements in the Jenkins core and plugins. Major ones:
   -

  Improved management screens for the Credentials plugin
  -

  Script Security: new Approval management UI:
  https://github.com/jenkinsci/script-security-plugin/pull/300
  -

  Folder Authorization plugin
   UI revamp
  -

  Credentials UI navigation improvements
  -

   Documentation migration from Wiki: 40+ user documentation pages are
   migrated to jenkins.io, 16 plugins docs are migrated to
   Documentation-as-Code


Thanks to all contributors who helped these and many other changes to
happen!

Best regards,

Hackfest org team

-- 
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/CAPfivLBDbKmb9PohyWxVyM6oNN6ZgzHqcPNaqxW8zd0rASYb5g%40mail.gmail.com.

Parametrized build for E2E testing in different environments

[Alberto Scotto]

Hi,

Long story short: is it possible to have a job which builds another job, in 
particular a parametrized one?

We have a Cucumber+Selenium project which runs E2E tests against our 
different test environments.
Something pretty standard.

For this kind of job, the parametrized build seems to be the best idea.
Otherwise we would have to create one job for each test environment. 
duplicating the job configuration.
Then it would be a nightmare to keep all the job configurations in sync, in 
case we need to change something.

But there's a problem with the build history.
I want to see a separate build history for each environment.
It doesn't make sense to have an interleaved history. It would be messy.

So an easy solution could be to have a job which calls the parametrized job 
passing the actual value for the environment.
This way the build histories would be kept separate, and at the same time 
we would also get to avoid duplication.

Is that possible? Or do you have any other idea/solution?

Thank you very much.

Alberto

-- 
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/5f64c8d1-db57-4002-9aa7-5e574638b76c%40googlegroups.com.

Re: How to get a list of jobs that are integrated with SonarQube

[Vijay Gongle]

Hi Jan/Dirk,

Tweaking the script worked in charm. Below is the perfectly working script
which gives me the results for any job that has sonarqube integrated or
sonar quality gates integrated.
It might help someone who is in similar boat. I thank a lot lot to you both
for leading me in right direction which helped  in in achieving this.

import hudson.model.*
import hudson.plugins.sonar.*
import jenkins.model.*

// Iterate over all jobs
Jenkins.instance.getAllItems(AbstractProject.class).each {job ->
  def fName = job.getFullName()

  // Iterate over all build wrappers
  if(job.respondsTo('getBuildWrappersList')) {
  for (wrapper in job.getBuildWrappersList()) {
  if (wrapper instanceof SonarBuildWrapper) {
  println(fName + ' has SonarQube configuration.')
  }
  }
  }
  if(job.respondsTo('getPublishersList')) {
  for (String str : job.getPublishersList()) {
//def str = wrapper
if(str.contains("org.quality.gates.jenkins.plugin.QGPublisher")){
  println(fName + ' has Quality Gate plugin')
  }
  }
  }
}
println('Done.')

Thanks,
Vijay

On Thu, May 28, 2020 at 1:35 AM 'Dirk Heinrichs' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Am Mittwoch, den 27.05.2020, 21:33 -0500 schrieb Jan Monterrubio:
>
> Try printing like this:
>
> println(“${job.getFullName()} has soñar configuration”)
>
>
> The script already has a line for this.
>
> Bye...
>
> Dirk
>
> --
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18
> *Email*: dhein...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail sind nicht gestattet.
>
> --
> 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/32fc3047756383f007e116e41011f3fe021eda88.camel%40opentext.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/CAMrMyDna-bhhN%2Br6wYtGWFfPGNDxfwJRKrv72s9GNtgRsidhfg%40mail.gmail.com.

ec2-plugin: now really slow on first build

[James Green]

Hi,

I'm aware that a recent ec2-plugin upgrade has led us to switch to the
"recommended" ssh handshake protocol.

However, my team are now complaining that new EC2 instances are taking
minutes to get started whereas before a couple of weeks ago it was
bearable. Subsequent builds by the same agent instance are snappy.

Jenkins agent logs do show a wait for the ec2 console to print the
fingerprints ahead of connecting. What is not clear, is what I can do to
speed up the provisioning time, other than have constantly running ec2
instances.

Can anyone point me in the right direction?

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/CAMH6%2BaxV_-Wrte8mJ9p0fof_HfA0G6Qtgch7uX3TwfSdXTQQRg%40mail.gmail.com.

Re: slave status as offline on another jenkins master server

[Om Prasad Surapu]

Hi Ivan,

That's correct. I think it works when slave has different home location 
with different user. my doubt was it slaves status were idle after 
upgrading jenkins in new master server.

Thanks,
Om Prasad Surapu

On Wednesday, May 27, 2020 at 10:07:15 PM UTC+5:30, Ivan Fernandez Calvo 
wrote:
>
> Do you mean you have the same agent connected to two different masters 
> with different versions of the core and using the same user with the same 
> home? if so, this is a miracle that works, you are sharing same files 
> between two different instances of Jenkins core that also are in different 
> versions. If you want to connect those instances to both masters (not 
> recommended because you shared resources in a predictable way) you should 
> use different users at least.
>
> El miércoles, 27 de mayo de 2020, 15:10:52 (UTC+2), Om Prasad Surapu 
> escribió:
>>
>> Hi All,
>>
>> We have a jenkins master running with 2.13 version on EC2 instance. As 
>> part of Upgrade, we took AMI of existing jenkins master and provisioned 
>> instance and upgraded jenkins to higher version.
>>
>> After upgrade, all the slave nodes status showing as Idle but few days 
>> later they are offline suddenly. But same slave nodes status as Idle on Old 
>> jenkins master. It was AMI of Old jenkins server so keys were already 
>> copied and can do ssh from new jenkins master to slave node.
>>
>> Has anyone seen similar issue? 
>>
>> Thanks,
>> Om 
>>
>

-- 
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/199f8e5c-6ca0-4239-b5f1-aca3165bbb87%40googlegroups.com.