Comments (4)
Jenkins Parent Pipeline should print information in this format. This format would be expected by TRSS for parsing the results.
Snippets from Jenkins Parent Pipeline
Benchmark Name: ILOG_WODM Benchmark Variant: 881-4way-Seg5FastpathRVEJB
ITERATIONS=4
INTERLEAVE=TRUE
Test Build: pxa6480sr6-20181217_01
Baseline Build: pxa6480sr5-20180517_01
Test Build Iteration 1/4
[Pipeline] build (Building PerfNext-Child)
Scheduling project: PerfNext-Child
Starting building: PerfNext-Child #68
https://jenkinsServer.com/job/PerfNext-Child/68/console
Baseline Build Iteration 1/4
[Pipeline] build (Building PerfNext-Child)
Scheduling project: PerfNext-Child
Starting building: PerfNext-Child #69
https://jenkinsServer.com/job/PerfNext-Child/69/console
Test Build Iteration 2/4
...
from aqa-test-tools.
I'm posting some sketches for reference from our discussions. Apologies for my terrible writing 😄
from aqa-test-tools.
from aqa-test-tools.
I've posted the outputs and screenshots to show how interleave runs would work.
If you notice the GrandParent build below, it launches parent(s) builds. Each parent would launch children builds. You will notice that Parent build 1 launches child 1 and 3 while Parent build 2 launches child 2 and 4, showing that both baseline and test builds are being interleaved.
Output of PerfNext-GrandParent
Build 53
Started by remote host 9.85.148.226
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] Start of Pipeline
[Pipeline] lock
Trying to acquire lock on [kermit]
Lock acquired on [kermit]
[Pipeline] {
[Pipeline] parallel
[Pipeline] { (Branch: test)
[Pipeline] { (Branch: baseline)
[Pipeline] build (Building PerfNext-Parent)
Scheduling project: PerfNext-Parent
[Pipeline] build (Building PerfNext-Parent)
Scheduling project: PerfNext-Parent
Starting building: PerfNext-Parent #234
Starting building: PerfNext-Parent #235
[Pipeline] }
[Pipeline] }
[Pipeline] // parallel
[Pipeline] }
Lock released on resource [kermit]
[Pipeline] // lock
[Pipeline] End of Pipeline
Finished: SUCCESS
Output of PerfNext-Parent
Build 234
Started by upstream project "PerfNext-GrandParent" build number 53
originally caused by:
Started by remote host 9.85.148.226
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] Start of Pipeline
[Pipeline] stage
[Pipeline] { (Build iteration 1)
[Pipeline] echo
Build Iteration 1/2
[Pipeline] build (Building PerfNext-Child)
Scheduling project: PerfNext-Child
Starting building: PerfNext-Child #572
[Pipeline] echo
https://CustomJenkinsServer.company.com/job/PerfNext-Child/572/
[Pipeline] sleep
Sleeping for 15 sec
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build iteration 2)
[Pipeline] echo
Build Iteration 2/2
[Pipeline] build (Building PerfNext-Child)
Scheduling project: PerfNext-Child
Starting building: PerfNext-Child #574
[Pipeline] echo
https://CustomJenkinsServer.company.com/job/PerfNext-Child/574/
[Pipeline] sleep
Sleeping for 15 sec
[Pipeline] }
[Pipeline] // stage
[Pipeline] End of Pipeline
Finished: SUCCESS
Output of PerfNext-Parent
Build 235
...
Starting building: PerfNext-Child #573
Starting building: PerfNext-Child #575
...
Output of PerfNext-Child
Build 572
Started by upstream project "PerfNext-Parent" build number 234
originally caused by:
Started by upstream project "PerfNext-GrandParent" build number 53
Screenshots with Perf Compare
from aqa-test-tools.
Related Issues (20)
- Release Summary report Rerun link causing a 'comment is too long' issue HOT 1
- Add Netlify attribution to TRSS client page
- Since we upgrade the node, we should upgrade to 18. 16 is out of active support and security support for 16 will end in Sep 2023. HOT 2
- Enhance docker compose in TRSS HOT 1
- Set TRSS link in the Jenkins job HOT 2
- Uncontrolled data used in path expression
- Store and display ML user feedback counts HOT 1
- Bug: JDK21 Build links missing from TRSS pipeline grid view HOT 2
- TRSS server container OOM
- Chatbot for Efficient Issue Triage and Resolution
- Mac test results are not showing up in Grid or Tree views HOT 1
- Release Summary Report should display the Rerun build result
- Not all child jobs showing in Tree and Grid view for release builds HOT 3
- JDK23 builds not showing in Grid view
- Uncaught Error when adding new build via TRSS admin page
- Add support for fips140_2 and fips_3_YYYYMMDD HOT 1
- test targets under different variant are categorized incorrectly HOT 1
- Release summary report can't be gererated HOT 3
- Release summary report with specific platforms, impls HOT 1
- Mac tests running but not displaying in TRSS HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aqa-test-tools.