From Fedora Project Wiki

(copy template)
 
(Drop direct Test Days category membership)
 
(54 intermediate revisions by 10 users not shown)
Line 1: Line 1:
 
{{Infobox_group
 
{{Infobox_group
 
| name = Fedora Test Days
 
| name = Fedora Test Days
| image = [[File:Echo-testing-48px.png|link=QA/Fedora_19_test_days]]
+
| image = [[File:Echo-testing-48px.png|link=http://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day]]
| caption = [[FIXME|FIXME]]
+
| caption = [[Changes/Jenkins|Jenkins]]
| date = <<FIXME>>
+
| date = 2014-09-30
 
| time = all day
 
| time = all day
| website = [[QA/Fedora_19_test_days]]
+
| website = [http://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day Fedora Calendar ]
 
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
 
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
 
| fedora_mailing_list = test
 
| fedora_mailing_list = test
Line 14: Line 14:
 
== What to test? ==
 
== What to test? ==
  
Today's instalment of Fedora Test Day will focus on '''<<FIXME>>'''
+
Today's instalment of Fedora Test Day will focus on Jenkins. [https://wiki.jenkins-ci.org/display/JENKINS/Meet+Jenkins Read more]
  
 
== Who's available ==
 
== Who's available ==
  
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
 
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
+
* [[User:msrb|Michal Srb]] (msrb)
* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
 
  
== Prerequisite for Test Day ==  
+
== Prerequisite for Test Day ==
  
List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
+
Either of following:
  
* Usb key
+
* bootable USB key or CD/DVD disk with latest Fedora 21 live image
* Usb externally connected HD IDE/SATA
+
* machine or VM with updated Fedora 21
* Empty HD IDE/SATA/SCSI
 
* Free space on HD
 
  
Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
+
== Known issues ==
 +
# Fedora doesn't yet have all core plugins which come by default with upstream Jenkins ([https://bugzilla.redhat.com/show_bug.cgi?id=1147838 rhbz#1147838])
 +
# Attempt to download jenkins-cli.jar or slaves.jar from http://localhost:8080/jnlpJars/jenkins-cli.jar ends with "ERROR 500: Server Error" ([https://bugzilla.redhat.com/show_bug.cgi?id=1147831 rhbz#1147831])
 +
# /var/log/jenkins/jenkins.log contains error message "SEVERE: Failed Inspecting plugin /var/lib/jenkins/plugins/jenkins-icon-shim.jpi due to bug in jenkins-icon-shim package ([https://bugzilla.redhat.com/show_bug.cgi?id=1147821 rhbz#1147821])
 +
# JENKINS_HOME is owned by root ([https://bugzilla.redhat.com/show_bug.cgi?id=1147846 rhbz#1147846])
 +
# Building of "Maven project" always ends with exception ([https://bugzilla.redhat.com/show_bug.cgi?id=1147899 rhbz#1147899])
 +
# Jenkins doesn't handle plugins from RPM very well ([https://bugzilla.redhat.com/show_bug.cgi?id=1147902 rhbz#1147902], [https://bugzilla.redhat.com/show_bug.cgi?id=1147908 rhbz#1147908])
  
* An updated [http://fedoraproject.org/get-prerelease Fedora XX pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
+
== How to test? ==
  
== How to test? ==
+
There are two options. Either you can stick with prepared test cases (below), or you can simply try to use Jenkins and experiment. The second option is probably better for people already familiar with Jenkins. In either case, please report all bugs in https://bugzilla.redhat.com/, component "jenkins". Please always attach Jenkins log file <code>/var/log/jenkins/jenkins.log</code>, if possible. Thanks.
  
High level details on how a contributor can get involved.  This can include (but not limited to):
+
=== Update your machine ===
  
* Areas to target with exploratory testing
+
If you're running Fedora 21, make sure you have all the current updates for it installed, using the update manager.
* A list of pre-defined test cases to execute
+
Also please make sure that you have latest Jenkins and its dependencies installed. Latest version in Fedora repositories is 1.581:
* How to report back results
 
  
Here's another common chunk (again, replace XX as above):
+
<pre>
 +
su -c 'yum update --enablerepo=updates-testing jenkins-javadoc-plugin-1.2-1.fc21 jenkins-junit-plugin-1.1-1.fc21 jenkins-external-monitor-job-plugin-1.2-1.fc21 jenkins-ant-plugin-1.2-1.fc21 jenkins-executable-war-1.29-3.fc21 jenkins-mailer-plugin-1.11-1.fc21 js-yui2-2.9.0-6.fc21 stapler-adjunct-timeline-1.4-3.fc21 jenkins-1.581-2.fc21'
 +
</pre>
  
=== '''Update your machine''' ===
+
=== Live image ===
  
If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
+
The live images are suitable for writing to a USB stick or to a DVD media. They can be used for installing Fedora from scratch, and may also be used to test Fedora directly from the USB stick / DVD media without writing anything to your hard drive. More information on how to use the images is available at [[FedoraLiveCD]].
  
=== '''Live image''' ===
 
  
Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
+
{|
 +
! Architecture !! SHA256SUM
 +
|-  
 +
| | [https://fedorapeople.org/groups/qa/20140930-Jenkins-Test-Day-Live-x86_64.iso 64bit] || 37e85e9dff9c38aaa4acd7ef938ec7f7349de45baea581707849eb18da4f0b5a
 +
|}
  
 
== Test Cases ==
 
== Test Cases ==
  
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see [[:Category:Test_Cases]].
+
 
 +
* [[Msrb:TestDay/Test_1|Jenkins start/stop]]
 +
* [[Msrb:TestDay/Test_2|Freestyle project]]
 +
* [[Msrb:TestDay/Test_3|Command-line interface]]
 +
* [[Msrb:TestDay/Test_4|Script console]]
 +
* [[Msrb:TestDay/Test_5|Plugins]]
 +
* <strike>[[Msrb:TestDay/Test_6|Maven project]]</strike> see [https://bugzilla.redhat.com/show_bug.cgi?id=1147899 1147899]
 +
* [[Msrb:TestDay/Test_7|Security]]
 +
* <strike>[[Msrb:TestDay/Test_8|Slave machines]]</strike> see [https://bugzilla.redhat.com/show_bug.cgi?id=1147978 1147978] [https://bugzilla.redhat.com/show_bug.cgi?id=1147831 1147831]
  
 
== Test Results ==
 
== Test Results ==
 
Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
 
 
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
 
  
 
{|
 
{|
 
! User
 
! User
! [[QA:Testcase_sample_1|Sample test 1]]
+
! [[Msrb:TestDay/Test_1|start/stop]]
! [[QA:Testcase_sample_2|Sample test 2]]
+
! [[Msrb:TestDay/Test_2|freestyle project]]
! [[QA:Testcase_sample_3|Sample test 3]]
+
! [[Msrb:TestDay/Test_3|cmd-line interface]]
! [[QA:Testcase_sample_4|Sample test 4]]
+
! [[Msrb:TestDay/Test_4|script console]]
 +
! [[Msrb:TestDay/Test_5|plugins]]
 +
! [[Msrb:TestDay/Test_6|maven project]]
 +
! [[Msrb:TestDay/Test_7|security]]
 +
! [[Msrb:TestDay/Test_8|slave machines]]
 
! References
 
! References
 
|-
 
|-
 
| [[User:SampleUser|Sample User]]
 
| [[User:SampleUser|Sample User]]
 
| {{result|none}}  
 
| {{result|none}}  
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|pass}}
 
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
 
| {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
 
| {{result|fail}} <ref>{{bz|12345}}</ref>
 
| {{result|fail}} <ref>{{bz|12345}}</ref>
 +
| <references/>
 +
|-
 +
| [[User:amsharma|Amita]]
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|warn}}[https://bugzilla.redhat.com/show_bug.cgi?id=1147963 1]
 +
| {{result|pass}}
 +
| {{result|fail}}[https://bugzilla.redhat.com/show_bug.cgi?id=1147821 1]
 +
| {{result|pass}}
 +
| {{result|fail}}[https://bugzilla.redhat.com/show_bug.cgi?id=1147978 1]
 +
| <references/>
 +
|-
 +
| [[User:Mizdebsk|mizdebsk]]
 +
| {{result|fail}} <ref>{{bz|1147846}}, {{bz|1147875}}, {{bz|1147879}}, {{bz|1147894}}, {{bz|1147897}}, {{bz|1147821}}</ref>
 +
| {{result|warn||1147955}}
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|warn}} <ref>{{bz|1147902}}, {{bz|1147908}}</ref>
 +
| {{result|fail||1147899}}
 +
| {{result|pass}}
 +
| {{result|none}}
 +
| <references/>
 +
|-
 +
| [[User:Mmaslano|mmaslano]]
 +
| {{result|pass}}
 +
| {{result|none}} <ref group="long">Fail to continue, because TestDay virtual froze. I wasn't able to figure out, which component is responsible, but definitely unrelated to Jenkins.</ref>
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| <references/>
 +
|-
 +
| [[User:jkejda|jkejda (32bit)]]
 +
| {{result|fail||1147979}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| <references/>
 +
|-
 +
| [[User:jkejda|jkejda (64bit)]]
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|warn}}
 +
| {{result|pass}}
 +
| {{result|warn}}
 +
| <references/>
 +
|-
 +
| [[User:Vjuranek|vjuranek]]
 +
| {{result|pass}}
 +
| {{result|pass}}
 +
| {{result|none}}
 +
| {{result|pass}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 +
| {{result|none}}
 
| <references/>
 
| <references/>
 
|-
 
|-
 
|}
 
|}
  
[[Category:Test Days]]
+
== Long comments ==
[[Category:QA Templates]]
+
<references group="long" />
 +
 
 +
  [[Category:Fedora 21 Test Days]]

Latest revision as of 21:19, 26 June 2015

Fedora Test Days
Echo-testing-48px.png
Jenkins

Date 2014-09-30
Time all day

Website Fedora Calendar
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

Today's instalment of Fedora Test Day will focus on Jenkins. Read more

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day[edit]

Either of following:

  • bootable USB key or CD/DVD disk with latest Fedora 21 live image
  • machine or VM with updated Fedora 21

Known issues[edit]

  1. Fedora doesn't yet have all core plugins which come by default with upstream Jenkins (rhbz#1147838)
  2. Attempt to download jenkins-cli.jar or slaves.jar from http://localhost:8080/jnlpJars/jenkins-cli.jar ends with "ERROR 500: Server Error" (rhbz#1147831)
  3. /var/log/jenkins/jenkins.log contains error message "SEVERE: Failed Inspecting plugin /var/lib/jenkins/plugins/jenkins-icon-shim.jpi due to bug in jenkins-icon-shim package (rhbz#1147821)
  4. JENKINS_HOME is owned by root (rhbz#1147846)
  5. Building of "Maven project" always ends with exception (rhbz#1147899)
  6. Jenkins doesn't handle plugins from RPM very well (rhbz#1147902, rhbz#1147908)

How to test?[edit]

There are two options. Either you can stick with prepared test cases (below), or you can simply try to use Jenkins and experiment. The second option is probably better for people already familiar with Jenkins. In either case, please report all bugs in https://bugzilla.redhat.com/, component "jenkins". Please always attach Jenkins log file /var/log/jenkins/jenkins.log, if possible. Thanks.

Update your machine[edit]

If you're running Fedora 21, make sure you have all the current updates for it installed, using the update manager. Also please make sure that you have latest Jenkins and its dependencies installed. Latest version in Fedora repositories is 1.581:

su -c 'yum update --enablerepo=updates-testing jenkins-javadoc-plugin-1.2-1.fc21 jenkins-junit-plugin-1.1-1.fc21 jenkins-external-monitor-job-plugin-1.2-1.fc21 jenkins-ant-plugin-1.2-1.fc21 jenkins-executable-war-1.29-3.fc21 jenkins-mailer-plugin-1.11-1.fc21 js-yui2-2.9.0-6.fc21 stapler-adjunct-timeline-1.4-3.fc21 jenkins-1.581-2.fc21'

Live image[edit]

The live images are suitable for writing to a USB stick or to a DVD media. They can be used for installing Fedora from scratch, and may also be used to test Fedora directly from the USB stick / DVD media without writing anything to your hard drive. More information on how to use the images is available at FedoraLiveCD.


Architecture SHA256SUM
64bit 37e85e9dff9c38aaa4acd7ef938ec7f7349de45baea581707849eb18da4f0b5a

Test Cases[edit]

Test Results[edit]

User start/stop freestyle project cmd-line interface script console plugins maven project security slave machines References
Sample User
none
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
Amita
Pass pass
Pass pass
Pass pass
Warning warn
1
Pass pass
Fail fail
1
Pass pass
Fail fail
1
mizdebsk
Fail fail
[1]
Warning warn [2]
Pass pass
Pass pass
Warning warn
[3]
Fail fail [4]
Pass pass
none
  1. RHBZ #1147846, RHBZ #1147875, RHBZ #1147879, RHBZ #1147894, RHBZ #1147897, RHBZ #1147821
  2. RHBZ #1147955
  3. RHBZ #1147902, RHBZ #1147908
  4. RHBZ #1147899
mmaslano
Pass pass
none
[long 1]
none
none
none
none
none
none
jkejda (32bit)
Fail fail [1]
none
none
none
none
none
none
none
  1. RHBZ #1147979
jkejda (64bit)
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Warning warn
Pass pass
Warning warn
vjuranek
Pass pass
Pass pass
none
Pass pass
none
none
none
none

Long comments[edit]

  1. Fail to continue, because TestDay virtual froze. I wasn't able to figure out, which component is responsible, but definitely unrelated to Jenkins.