There is a new PELC subject type that is "component-version", and we need Greenwave to accept this new type.
OK, crazy idea: how about making this:
return ('component-version', '{component}-{version}'.format(**subject[0]))
It's weird. the item is there in component-version messages, but it shouldn't be the subject-identifier. The component and version fields are the more important ones here.
item
component
version
I take this back. The item is there and it already is just the {component}-{version}. It can be used as the subject identifier just fine. Ignore me.
{component}-{version}
Nope, nope. Nevermind me. Leave this as it is. :p
rebased onto 8c87424c503eb52efb3c992a00445e9a3985bcfa
@ralph rebased. Can you please check again? I've dropped the idea of writing functional-tests, I've put just unit tests. It seems easier to me now.
:+1:
Jenkins should be working again. I tried to trigger this one again.
@gnaponie my manual trigger didn't work. But, when you're back can you rebase this to trigger another run and, if jenkins passes, let's merge it!
I did "git commit --amend --no-edit && git push -f" and also manually tried to start the job... but it did not...
rebased onto 0aeb82391870da049477d2e7821a39ac273025c6
rebased onto 86f2c4b05d8cb57e07a14c915b676542df00c81b
Pull-Request has been merged by gnaponie
There is a new PELC subject type that is "component-version",
and we need Greenwave to accept this new type.