Guillaume Ceccarelli So looking at that project type, there are a lot of hacks and some incorrect assumptions on how Branch API is supposed to work. I suspect the plugin maintainer would need to figure out how to correct their usage of Branch API now that the correct usage is documented.
That is assuming the plugin maintainer is still interested in that plugin, given that the wiki page directs towards pipeline I am unsure.
Certainly the code looks to have a lot of hacks enough that I cannot see what it is doing wrong, particularly scary from my PoV is that it doesn't seem to want to ensure that the branch details are stored with each branch job (storing in a property being fragile they way it has been implemented in the plugin, probably better to store in a side-file so that the UI config cannot remove)
There also seem to be some incorrect assumptions about source ids and other things.