Glad it is GA now, but it is still has some issues:
* If i use non core parameter in pipeline, BO ask me to move to classic interface
* If i do not use Github like pipeline, interface become partially useless. It means empty branches, empty PR columns etc. Where is good old custom pipelines?
But anyway it is good move forward!
PS: pipelines itself also has some issues, like really small number of useful steps, literally only sh step used everytime. Also in case of custom pipeline it is still unclear how to abort build in code. And using groovy collections methods is veyr inconvinient (like trying to use .collect to create command like options for next sh step)
Finally!
It was very disappointing that girl that smile and had good relationships with out senior manager had the same salary as me, even if i got the best score in our delivery center.
imo map and set useless. Real advantage of maps only that you can use any type of keys, but really why not convenrt them to string represntation and put to simple object? Map .has method uses === for object search. For set the same, just use object with keys and dummy values.
We fixed this with installing npm proxy mirror. So each install happen from this proxy and if something missing it will be downloaded and saved for later from central.
In this case we always have the same dependencies that we have locally. But of cause this means you need own box with proxy.