Some background since Autosar <http://autosar.org> isn't standard Jenkins 
environment.
- The produced artifacts are called SWC (Autosar Software Components)
- The interfaces between the SWCs are stored in a database and from that is 
the interface Contract for a specific SWC extracted.
- There are 100+ SWCs and the generation/compilation/tests of those takes 
many hours. 
- The job-history is relevant for each SWC i.e. individual pipelines. 
- A change in the interface database does only affect one or a few of the 
SWCs.
- It is fast to generate extracts of the interface Contract for each SWC 
(and to get the fingerprint) 

I do think you see the goal here; Only rebuild/retest the affected SWCs 
when the interface database is updated.

Below are my ideas but I would like to have your recommendations how to do 
that.
A) Generate Contracts for all SWCs and locate the updated - trigger the 
build job for specific SWC(s). 
    I haven't seen a plugin which can do that and thereby I expect that 
there is a better way to do it.

B) Generate and push the updated Contracts as artifacts to an artifact 
repository and let that trigger the build job (Maven style).

C) Include the Contract fingerprint in the SWC artifact pushed to artifact 
repository. Generate Contracts (as in A) and trigger a job if there is no 
SWC artifact stored with that id.

D) Something completely different...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to