How to use a stream instead of baselines for configurations when using oslcquery on rm projects #77
pauljosephwilson
started this conversation in
General
Replies: 3 comments 4 replies
|
What version of elmclient are you using? And with what version+ifix of DOORS next? |
0 replies
|
I get the 404s you report when I archive a baseline or stream and then run oslcquery. At least in the current version 0.28.0 it doesn't affect function - the missing configs are skipped over with the log message at INFO logging level, but they don't stop it working. If you're not using 0.28.0 update to that and check? |
0 replies
|
Currently 0.28. The jazz instance we are running is 70.2 SR1, iFix032. We only have 1 stream for the project areas but there's a lot of baselines considered out of date. |
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have an RM project with several baselines. When I try to query it using -F 'Stream name" I still get the error 404client error: not found for url XXXXX/rm/cm/baseline/XXXXXXX. Looking through the logs it tries to look at several baselines but I only want it to pull configurations from the currently used stream rather than a baseline. Is there a way to skip this in rm projects? I am able to pull from some rm projects using the default query with only -P and -A flags, but the ones with several baselines are causing an issue. It is an opt in project but the component name used as default is the one I believe I want to be looking at. Any guidance would be appreciated.
All reactions