You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When we add an Infrabox job A with dependency on job B, the dependency job B must be defined in front of the job A. Otherwise we will hit job parse error when pushing the Infrabox json file. Is it possible to eliminate the location order limitation?
Describe the solution you'd like
When we add an Infrabox job A with dependency on job B, we can define the job B before/after the job A which means the location of job B is insensitive.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When we add an Infrabox job A with dependency on job B, the dependency job B must be defined in front of the job A. Otherwise we will hit job parse error when pushing the Infrabox json file. Is it possible to eliminate the location order limitation?
Describe the solution you'd like
When we add an Infrabox job A with dependency on job B, we can define the job B before/after the job A which means the location of job B is insensitive.
The text was updated successfully, but these errors were encountered: