-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import Pipeline and Job - Inconsistencies and using wrong configuraitons #325
Comments
HOW TO TEST WIP: The release : 2.1.11
If you got this response then It worked fine
For every export / import tasks with corresponding task You then need to check in the saagie platform that the all the job / pipeline that is exported, and the versions for the job or the pipeline is added like it s shown in the job.json/pipeline.json for every job or pipeline in every exported artifact Tested on version : 2.1.11. Worked fine Bug Behavior :
|
When running a integration test suite noticed that the ImportJob was using a wrong configuration and importing old artifacts.
See below output refer to importpython , instead of importing a single python job its importing pipeline. This is a similar issue to caching issue we faced before.
saagies-mbp:Gradle shivakumar$ gradle projectTestAll
FAILURE: Build failed with an exception.
Execution failed for task ':projectExportV1Var'.
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Get more help at https://help.gradle.org
BUILD FAILED in 7m 19s
17 actionable tasks: 17 executed
The text was updated successfully, but these errors were encountered: